yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] jamminjon82:
You don't yet
[Kindle Fire Android Development] cultofrobots:
From a few pages back:
[Kindle Fire Android Development] smirkis:
I concur. we have official builds for the nexus 7 but there so buggy I run all the unofficial ones. I know they're just nightlies but still, other devs are putting out solid unofficial builds. thank god for devs, if we all had to wait for officials, we would be waiting for a while for a nice rc.
[Kindle Fire Android Development] kls2k:
Does anyone have a mirror of the 08/17 build?
[Kindle Fire Android Development] jamminjon82:
Put on my minus for a bit

http://min.us/mHEzsHplb/1
[Kindle Fire Android Development] MayfairDROID:
Says file not found :'(
[Kindle Fire Android Development] jamminjon82:
Try now
[Kindle Fire Android Development] Hashcode:
NEW build is ready! See OP for details. Quick Summary: This is STOCK CM10 using the new TI 4AI.1.7 kernel (3.0.31 mainline) + TI ducati binary for HD codecs, and updated TI-based source for the hardware portions of JellyBean.

BUILD #2 (BETA) ROM DOWNLOAD:

http://bit.ly/QxvbKC

md5sum: 3485237c5da884f05babf9ef2dbe0252

JELLYBEAN GAPPS

http://goo.im/gapps

Use CyanogenMod 10.0.x

Same 2 open items as CM9:

- Charging isn't showing correctly in the OS

- MIC input isn't working

Enjoy.
[Kindle Fire Android Development] animefun135:
hi Hash, can we just flash kernel only?
[Kindle Fire Android Development] jamminjon82:
Running great with my highest antutu to date(6711). Thanks for all of your hard work!
[Kindle Fire Android Development] rysk29:
Awesome nice antutu scores.. 6779 here... any way to get outa phone mode?

My kindle is going to sleep in middle of flash video... and back button doesn't exit full screen.. possible bugs? (Only happens with stock browser... firefox doesn't have these bugs.)

Also i have seen talk on here about ghosting on screen with replaced screen.. i have never replaced my screen, and bought new at walmart, but im getting ghosting also.. seems to only take a few seconds leaving screen stationary for icons to ghost.. why is that.. had this prob since cm9.
[Kindle Fire Android Development] collindv:
I second the ghosting issue. I have been getting it on twa's version for awhile now. Not a big deal, thought I was the only one though!
[Kindle Fire Android Development] BizzaBoy:
I had this ghosting with the stock Amazon ROM as well. IMHO this is really a HW issue.
[Kindle Fire Android Development] pbailey212:
Is there any kernel changes with this update? Or is it same kernel just a fresh cm sync?
[Kindle Fire Android Development] cultofrobots:
As did I. Eventually it got so bad it looked like burn-in. Fortunately they exchanged it hassle free.
[Kindle Fire Android Development] wws12:
What are the changes in this new update?

wws12
[Kindle Fire Android Development] Hashcode:
This is a full working version of the 1st CM10 update that I did a few days back.
[Kindle Fire Android Development] rysk29:
I had to revert back to cm9 4 now.. battery life was not good 4 me... other than that an a few bugs, it's a gr8 rom.. cant wait til stable.. thanks again hash
[Kindle Fire Android Development] Hashcode:
Odd. I'm seeing slightly better battery life (maybe?).
[Kindle Fire Android Development] collindv:
Certainly no worse than ics
[Kindle Fire Android Development] december.underground:
Is there a certain Bluetooth dongle to use to get it working with the otg cable? Or a certain way of getting it to work? Mine is and old broadcom chip set... Also will this ever support tablet mode?
[Kindle Fire Android Development] mrdeli:
Hi,

At first thank you hashcode for your great Work. :)

I have got two problems with your cm10 Rom.

1. I came from your ics rom and i am missing a fast way to toggle the volume.

2. The Menu on the Top (dont know the name). Sometimes when i open it, it instantly disapears to come back a second later only to disapear the second after again.. . To de- or activate WLAN for example i have to click in the Wright moment.

Maybe you have a solution for me. :)

Thanks deli
[Kindle Fire Android Development] wws12:
Anyone else getting this problem? com.android.phone has stopped. It keeps coming up and is driving me crazy! I tried force stopping Play Store and Google Voice but that didn't make a difference. Please help!

---------- Post added at 09:29 AM ---------- Previous post was at 09:13 AM ----------

Never mind, fixed it. It happens when you enable silent mode for some reason. Bug report!
[Kindle Fire Android Development] Glasairmell:
This is by far the best running ROM I have flashed on my Kindle Fire. I set it up just like my Nexux 7 and it is running like a champ.

Regards!
[Kindle Fire Android Development] wws12:
How exactly did you set it up "just like your Nexus 7?" Do you mean you installed the same apps or changed some settings?
[Kindle Fire Android Development] Glasairmell:
Did not change any CPU settings etc. but did change some interface etc. Guess I meant I can pick one up or the other and not feel handicapped with the KF on most tasks.

1. Nova Launcher

2. WidgetLocker

3. FireFox Beta and Flash Player side loaded for flash sites

4. SwiftKey 3 Tablet

5. Volume+ (headset settings do not seem to work)

6. SuperSU ( Superuser was asking every time on some apps )

7. AdAway

8. Google Voice for texting.

9. Beautiful Widgets

10 And then my personel utility apps for navigation, media, comunication etc.

The kindle with Hashcodes work does not make you feel like the Nexus 7 walks away from it, unless you are heavy gaming I would guess. Of course no GPS or mic Knocks the KF down a notch but it is still a fine tablet.

BTW I tried to use Stickmount but could not get it to work.
[Kindle Fire Android Development] astmario:
Since new kernel uses Ducati binary instead Archos+ that free codec, can anyone try MKV files HW acceleration?
[Kindle Fire Android Development] Jacktheskipper:
the rom works amazing for me, the battery life is really really improved in standby, takes about 5% in ~10hours when I`m away ...

only bugs I experienced so far are the following:

- when I was playing jetpack joyride and paused the game and pressed the home "button" systemui force closed

- certain widgets dissappear after restart (widgets hd, business calendar)

thanks so much for all the hard work! :good:
[Kindle Fire Android Development] wws12:
That's amazing! Could you tell me what your settings are that allow you to get this kind of battery life? Cause mine right now is getting about the same amount I had on AOSP JellyBean. Thanks!
[Kindle Fire Android Development] koroshbhasabrain:
Glasairmell:

You need to have a POWERED USB hub and an OTG cable. Have the KF powered off when you plug the stuff in. It should work that way - it's the same way I got it to work for me.

Hey Hash, I have another problem: Every time I try to Install this, it "crashes" and takes me back to the main TWRP screen. I'll see if I can post a Youtube vid on this. I triple checked the md5 sum (because I am paranoid :) ) and it matches. I do not know what is wrong; but I did install the new FFF 1.4 . Would that be the problem? Anyway, Thank you so much for all this hard work. Thank you for enlightening all us non-programmers with the wonders of Jellebean!
[Kindle Fire Android Development] Glasairmell:
Flashing did this to me too, after the third try I just rebooted it to see if by some chance it flashed and after a minute up came the boot animation and I was good to go.

ADDED: Jacktheskipper yes Beautiful widgets disappear for me too after a restart.
[Kindle Fire Android Development] Jacktheskipper:
Used it with the "out of the box" settings it came with and turned off the Wifi, that`s all as far as I remember ... if there are any settings you wanna know about specifically, let me know and I`ll tell you asap ... you can also drop me a pm any time so we don´t take room away in the dev thread.
[Kindle Fire Android Development] koroshbhasabrain:
No, not like that....

No, I meant on the actual TWRP flash page. I choose the zip file, press flash, and it takes me back to the main page. Video will be up in 30 mins.

EDIT: I got it to flash as I was taking the video.

But, I've seen in sgt7's linaro build that theirs an option to get the status bar Down near the NAV buttons like ICS. Is there any to do that on this build? I tried the build.prop DPI thing, but that didn't work.
[Kindle Fire Android Development] Glasairmell:
Swiftkey 3 Tablet is not defaulting on reboot. Have to reset it to default keyboard each shutdown and boot.
[Kindle Fire Android Development] twa_priv:
http://code.google.com/p/android/issues/detail?id=34880
[Kindle Fire Android Development] Glasairmell:
Well that is interesting but it (#1518 and #1521) does not do it on the Nexus 7 and JB CleanROM 1.1. Wonder what scrosler did to fix it. Thanks for the link.

Regards!
[Kindle Fire Android Development] twa_priv:
It might not happen on your N7 but it's definitely the bug you are facing.

I had my HD Widget widgets disappear after every reboot - backing up the app with TB, uninstalling it and then restoring using TB fixed it. Because TB doesn't restore the app to /mnt/asec but to /data/app, which fixes the issue.

It also depends on the play store version you happen to have. Some recent versions install in /mnt/asec, some don't.
[Kindle Fire Android Development] Glasairmell:
Using Titanium BU worked perfectly thank you!

Regards!
[Kindle Fire Android Development] Jaimemex:
Will be testing out the new beta later...thanks again hash for your hard work! =]
[Kindle Fire Android Development] walts:
I flashed 20120824 last night. All of the important stuff is working fine so far.

The charging LED which had been working with the 0713 build has stopped working. I understand the comments in the OP! I'm just curious! It's kind on comforting to see that orange glow as I drift off to sleep. It seems the original Kindle code is a real mess, but is there any chance of lifting the code from the 0713 build to get this working again?

The OP says that the new kernel replaces some code by "Archos" but I can't find any information about "Archos" in the Android Development forum. What was replaced and what are we gaining from it?

I'm not complaining... just trying to learn.

Walt
[Kindle Fire Android Development] koroshbhasabrain:
The Status bar

Hi! In sgt7's linaro build, there was an option to get the status bar down near the NAV buttons, ICS style. Is there an option like that in this ROM? Thank you!
[Kindle Fire Android Development] fox_dye:
Archos is another tablet that uses 512mb ram and hash originally used their binaries and what not to get the video working on the ICS builds. He has switched to the ti binaries which work a lot better because they were built to run on 512mb ram from the chip set manufacturer. Less hacking means a better overall experience and less inconsistencies.
[Kindle Fire Android Development] entaled:
Settings -> System -> Status Bar -> Tablet Mode
[Kindle Fire Android Development] Hashcode:
New kernel/ROM based on the 4AI.1.7 release are getting a lot better (IMHO) so I'm probably going to do another kernel/ROM release here soon.

Here's an update of what's coming in the next release:

1. Kernel Audio source: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now.

2. Audio HAL module: updated to TI's latest source to help with #1 and future support for USB audio, etc.

3. Lights HAL module: removed conflicting battery light operations. The kernel manages the battery light entirely. The OS should almost never do anything with it.

4. (NEW to JB) Power HAL module: used by the OS for temporarily kicking up the CPU during certain events (using the interactive governor) -- this makes the system more responsive. This feature is also still under development over time and I'll continue to update it.

5. HW acceleration / graphics buffer system: Completely updated sources from TI for the hwcomposer, libion and other graphics / buffer systems

6. Along w/ #5 I was able to roll up to the latest PowerVR driver 1.9@2130229 (up from 1.8@945322 in the last build). I noted right off the bat

less GL issues and smoother game play.

I may take a night or 2 and continue to play with the MIC settings to see if we can get it working, and that would be the delay in this release (if any).

But, in general, the build for the Kindle Fire is a getting a lot cleaner (IMHO). And that's always a good thing.

Still working on:

- Memory management: I'm still not happy with how the OS is unloading certain processes at times (acore?!), and I'll be working with some of the ROM devs to setup better memory management in this main sources at GitHub. No reason why every dev should need to work that stuff out.

- MIC function. Getting close, but I need to probably spend 2-3 more nights following audio routes and watching the OS setup the Audio input devices when the headset is plugged in.

- Charger function. This is the big kahuna. Been a while since I worked on it, probably time to jump back into it.
[Kindle Fire Android Development] twa_priv:
Thanks Hash.

Yeah, I noticed that Google Now doesn't FC anymore on a vanilla build using your latest sources - your audio changes must have fixed that.

I'm still having issues though with wifi not reconnecting after waking up from deep sleep. Attaching a logcat & kmsg in case you want to have a look.

Thanks

Edit: While I'm at it I'd like to ask you if you know how to fix this error caused by HBO Go when launching the app.

W/dalvikvm( 2990): threadid=1: thread exiting with uncaught exception (group=0x40d5b300)
E/AndroidRuntime( 2990): FATAL EXCEPTION: main
E/AndroidRuntime( 2990): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.HBO/com.hbo.tablet.HBO}: java.lang.SecurityException: No permission to prevent power key: Neither user 10032 nor current process has android.permission.PREVENT_POWER_KEY.
E/AndroidRuntime( 2990):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2185)
E/AndroidRuntime( 2990):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2210)
E/AndroidRuntime( 2990):	at android.app.ActivityThread.access$600(ActivityThread.java:142)
E/AndroidRuntime( 2990):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1208)
E/AndroidRuntime( 2990):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2990):	at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2990):	at android.app.ActivityThread.main(ActivityThread.java:4928)
E/AndroidRuntime( 2990):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2990):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2990):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 2990):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 2990):	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2990): Caused by: java.lang.SecurityException: No permission to prevent power key: Neither user 10032 nor current process has android.permission.PREVENT_POWER_KEY.
E/AndroidRuntime( 2990):	at android.app.ContextImpl.enforce(ContextImpl.java:1343)
E/AndroidRuntime( 2990):	at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1372)
E/AndroidRuntime( 2990):	at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:448)
E/AndroidRuntime( 2990):	at android.view.Window.setFlags(Window.java:755)
E/AndroidRuntime( 2990):	at com.hbo.core.d.d(DeviceChromeMgr.java:110)
E/AndroidRuntime( 2990):	at com.hbo.tablet.HBO.g(HBO.java:76)
E/AndroidRuntime( 2990):	at com.hbo.core.LaunchCoreActivity.onCreate(LaunchCoreActivity.java:98)
E/AndroidRuntime( 2990):	at com.hbo.tablet.HBO.onCreate(HBO.java:68)
E/AndroidRuntime( 2990):	at android.app.Activity.performCreate(Activity.java:5008)
E/AndroidRuntime( 2990):	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
E/AndroidRuntime( 2990):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2139)

I don't think it's an issue with the app because it works fine on my GT 10.1.

Thanks again
[Kindle Fire Android Development] Hearnbiz:
Not sure if anyone has already mentioned this but I downloaded a app called keyboard manager from the play store and set it to boot with swiftkey tablet (my keyboard of choice as well) and this solved my problem... Also just for good measure I uninstalled the android keyboard but swiftkey comes up after every boot with no problems.
[Kindle Fire Android Development] Hashcode:
From what I'm seeing HBOGO is having JB compatibility issues still. It seems to work on some devices and not on others. I'm looking into the error as well. The specific source that causes this error is here:

https://github.com/CyanogenMod/andr...ybean/core/java/android/view/Window.java#L753

On your wifi issue:

- From what i see it looks to be connected to an AP at the end (or the OS thinks it's connected anyway):

"I/wpa_supplicant( 520): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='{some SSID}' freq=2412 MHz)"

"I/wpa_supplicant( 520): wlan0: Associated with xx:xx:xx:xx:xx:xx"

- But there are some messages that I can look into:

"CTRL_IFACE monitor[1]: 2 - No such file or directory"

""wlan0: Failed to initiate AP scan"
[Kindle Fire Android Development] twa_priv:
Are you saying you do not have this wifi not reconnecting problem?

Because I can reproduce it fairly certain by:

- Pressing the power button so that the screen goes off

- Wait about 10 minutes

- Turn the device on - this time it usually reconnects

- Press the power button again to turn the screen off

- Wait another 10 or so minutes

- Now when I turn the device on it doesn't reconnect

Thanks

Edit: Just to clarify - I'm running CM10 on my GT 10.1 (and not stock or some other ROM) and HBO works.
[Kindle Fire Android Development] Hashcode:
Yeah for me, mine stays connected. That's not to say that I wont find something if I dig around.

Do you use the latest ti wlan firmware in you're sgt builds?
[Kindle Fire Android Development] twa_priv:
I actually have this wifi issue on a complete vanilla build (no sgt7 or linaro) using your latest cm-private manifest. If I have weird issue I always try to rule out it's an issue with the stuff I'm adding :)

And yes, my 8/24 SGT7 new kernel build I've put out, where a few other people were also having wifi reconnect issues, was using same firmware you had in your 8/23 build.
[Kindle Fire Android Development] webdroidmt:
@twa,

I'm on your 8/24 new kernel build, just tried the 10 min thing that you mentioned above and my wifi stayed connected. Don't know if it makes a difference but I use green power to turn off wifi when screen off and it overrides system settings.

Mike T
[Kindle Fire Android Development] twa_priv:
Right ... I hade quite a lot of 8/24 rom downloads. And just a few complaints about wifi in my thread (sorry hash for highjacking your thread here). It really doesn't seem to affect everybody - just a minority it seems.
[Kindle Fire Android Development] wws12:
So when the new kernel/ROM comes out, will I be able to use something like this

http://www.amazon.com/HDE®-Mini-3-5mm-Flexible-Microphone/dp/B00284VD02/ref=pd_cp_pc_2

And have it work with Skype or voice recording apps?

Thanks!

wws12
[Kindle Fire Android Development] Hashcode:
That's the basic idea. :) Tho I'm not sure how a MIC w/o a headset will work.
[Kindle Fire Android Development] wws12:
Could you recommend a headset that you are pretty sure will work?
[Kindle Fire Android Development] sthomas38:
IIRC, Apple headset worked on CM7 :).
[Kindle Fire Android Development] Hashcode:
QUICK UPDATE:

This kernel is out in the wild now. Twa_priv has it in his new CM10-based build here:

http://xdaforums.com/showthread.php?t=1778010

So if you're dying to see it in action, then I recommend you hop on over and take a peek at his build.

I've been using stock CM10 as a base-line ROM to test kernel changes, and keep the device/vendor trees in good working condition so that other devs can quickly pick up the device and get to work.

QUESTION:

1. Should I continue to build a stock CM10 base ROM like I've been doing.

2, Or, considering twa_priv is keeping his CM10-based ROM up-to-date with the latest CM10 changes, should I swap to a different style ROM that has never really been presented before: a TI OMAPZOOM-based build of JB sources which is more of a test bed for new features and optimizations specifically for our hardware.

THOUGHTS?

Footnote: I am in no way dropping support for CM. I consider it one of the primary build-bases and am going to repeat: I am working towards a merge of the Kindle Fire into the CM sources.
[Kindle Fire Android Development] webdroidmt:
Considering that aside from twa's builds, others are also using his build as a base for their own rom, I would like to see a different style as noted in Question 2. As always, thanks for your outstanding contributions.

Mike T
[Kindle Fire Android Development] twa_priv:
Yeah, would be interesting to see how an omapzoom based build performs.
[Kindle Fire Android Development] ammubarak:
Hashcode

Thank you for your excellent. It is a good idea to continue building stock CM-10 based ROM to allow for testing of new kernel features and provide alternative ROM for the community.
[Kindle Fire Android Development] leswgnr:
Definitely #2. New features and optimizations are why I'm flashing new ROMs in the first place. Should be more interesting for you to work on too.

Thanks to you and twa_priv both.
[Kindle Fire Android Development] wws12:
I would like stock Cm10
[Kindle Fire Android Development] rorogio:
I would also prefer a new ROM base, especially if it gives more options for perfomance and usability.

But will the new kernel be compatible with the CM10? This would be important if CM10 ROM would be more stable?
[Kindle Fire Android Development] jamminjon82:
Omap would be exciting for sure!
[Kindle Fire Android Development] VaksenDK:
Definitely 1, a clean and purely stock cm10.

(Or 3, an aokp build.) :)
[Kindle Fire Android Development] pbailey212:
A well maintained aokp would be nice. It looks like miui is getting up and running on rootz, so that would give us the main 3 available
[Kindle Fire Android Development] al mon:
#1 for sure. TWA_Priv's seems to have a lot of variablity. CM10 pure is the way to go. Maybe publish a manifest on how you do TWA's and build both branches?
[Kindle Fire Android Development] yangtsesu:
I'd like you just Make the kernel work.Let anyother to build the ROM.Or maybe you can try to port other os like b2g to kindle fire.
[Kindle Fire Android Development] shahabk818:
Download link? where is it?
[Kindle Fire Android Development] Glasairmell:
Can not seem to find the DL link either. Would rather flash 9/1 then wipe and go over to twa_priv.

Your Rom build was perfect for me.

My vote for that would be yes.

Thanks!
[Kindle Fire Android Development] incognico:
OMAP build, with twa_privs ROM we already have a very good CM10 one.
[Kindle Fire Android Development] epedrosa:
I say 2

And thanks for your work :)
[Kindle Fire Android Development] andPS2:
please a PURE unmodified AOSP ROM

(as the ROM based on that is still the

best working for me)
[Kindle Fire Android Development] justauser:
option 1

I'd prefer option 1. Like a version of the clean base. The modders will give us the variations.

BTW, is there a d/l link?
[Kindle Fire Android Development] buberlo:
as i long as Twa_priv is dependable and there will be no problems with CM10 i would love to see something different from you!
[Kindle Fire Android Development] ironlady:
maybe you could make an alpha of omapzoom and see if it goes well enough to continue? :D
[Kindle Fire Android Development] :
No offense because I love your work... But i prefer twa priv cm builds because the updates are so often... Would love to see q combo of your work on the kernel plus twa dailies
[Kindle Fire Android Development] SpudsterZ:
TWA updates more often because he uses Hash's sources but includes additional enhancements whereas Hash's ROM is strictly "barebones". It's an "apples to apple pie" comparison. :)