yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] 50CalPotato:
Everything is going extremely smoothly, with the exception of the bugs you mentioned in the OP.

A few things I've noticed:

- Boot animation starts at random points. Sometimes at the very beginning, sometimes after the Cyanogenmod circular arrow has already "exploded." (I hope you know what I mean).

- DPI problems still seem to persist. I've noticed that many apps, including Chrome, will switch to the phone interface rather than using their tablet versions. This is also true for Firefox.
[Kindle Fire Android Development] twa_priv:
No, unfortunately not. This is driving me nuts.

Please let me know if you find a fix.
[Kindle Fire Android Development] veeman:
Have you tried moving those files from the stock rom to the cm10 rom?

Edit: by stock rom I mean the aosp jellybean rom
[Kindle Fire Android Development] GTvert90:
Anyone having charging issues? I'm on the 7-9 or 7-10 build. When plugged in and in use it will still die.. when you stop using it, it will charge
[Kindle Fire Android Development] StarkCity:
Same thing for me on that build. Quit using it.

Sent from my Beast
[Kindle Fire Android Development] twa_priv:
highfive :) ... this was like giving birth to figure that one out
[Kindle Fire Android Development] jamminjon82:
Need a tester?
[Kindle Fire Android Development] twa_priv:
Too early ... I finally got it to boot up successfully without zygote restarting constantly.

And at the moment it pretty much looks like vanilla aosp anyway since most of the CM customizations aren't merged yet.
[Kindle Fire Android Development] jamminjon82:
Okay if and when you do shoot me a pm
[Kindle Fire Android Development] wws12:
Hey Hash, I have a question on the development of the 3.0 kernel. How are things coming along? Will the charging issues be fixed soon? I know you probably get this question alot but I was just wondering how much progress is being made. (Note: I posted this in the Jellybean thread but Pkt_Lnt told me to ask it here. Wasn't sure what thread to post it on.)

Thanks!

wws
[Kindle Fire Android Development] GTvert90:
Which are you using now? Its for the gf's mom so it needs to have a volume slider and be stable.. thanks
[Kindle Fire Android Development] veeman:
What did you do for it to work?
[Kindle Fire Android Development] twa_priv:
I running another test build at the moment to make sure I know exactly what fixed the error. I'll post it then.
[Kindle Fire Android Development] twa_priv:
This is the workaround I came up with:

frameworks/base

diff --git a/Android.mk b/Android.mk
index 41a75c7..f72ac98 100644
--- a/Android.mk
+++ b/Android.mk
@@ -35,7 +35,6 @@ SECONDARY_FRAMEWORKS_SUBDIRS := \
core/java/android/test \
core/java/android/gesture \
core/java/android/speech/srec \
- media/java/android/media/videoeditor \
media/java/android/media/audiofx \
media/mca/effect/java/android/media/effect \
media/mca/effect/java/android/media/effect/effects

And of course at the same time I managed to fix it this post appears - would have saved me a lot of time...
[Kindle Fire Android Development] twa_priv:
This is probably a better and the correct fix:

device/amazon/otter

diff --git a/root/init.rc b/root/init.rc
index e8a1455..90c63a4 100644
--- a/root/init.rc
+++ b/root/init.rc
@@ -33,7 +33,7 @@ loglevel 8
export ANDROID_DATA /data
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
- export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
+ export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar

# Backward compatibility
symlink /system/etc /etc

Testing now (a SGT7 build :)) - however, wifi had issues so far but maybe I was able to fix it.
[Kindle Fire Android Development] :
Tried the aosp 4.1.1 also by hash. It was overheating the KF... this from just works much better for Me... flashed cm9 7-5 and not looking back
[Kindle Fire Android Development] jkhayworth:
What, you people are still here on ICS? What's wrong with u, get on the jellybean train with lithium and hashcode? LOL im just kidding, but seriously I haven't had any overheating issue and jellybean is like fifty times smoother than any rom you've ever used (except maybe glazed) and I'm guessing that Hash might neglect this rom for a little while as he works on his jellybean aosp.
[Kindle Fire Android Development] StarkCity:
+1

Sent from my Beast
[Kindle Fire Android Development] :
kind of weird that you post that, because its simply not true. This rom is much smoother, and much more ready for daily use. Cant even argue that. This rom breathed new life into my KF, 4.1.1 took it away.
[Kindle Fire Android Development] kenikh:
I've used them all and if ICS, in any flavor, is running smoother than a Jellybean build, there's an issue with the JB ROM deployment. I have done every optimization I can on most ICS ROMs and nothing provided the top-to-bottom smoothness and RAM efficiency I've experienced on the latest AOSP JB ROMs. From the UI threading to the Open GL layer, everything seems to run more efficiently on JB.

JB is my daily now...no looking back.
[Kindle Fire Android Development] :
Well thats your opinion and i dont agree. None of the JB roms are ready for prime time like this ics rom. Thats MY opinion... So instead of filling this dev forum with silliness lets agree to disagree respectfully.. I only posted my experience here first so i could share it...and to the other poster.. This is an ICS thread not JB thread
[Kindle Fire Android Development] kenikh:
No one's here to piss in your punchbowl. I was simply suggesting that you may want to research (if you care) potential issues with the JB ROM you deployed, as you seem to be the only person on record seeing better performance on ICS than JB.

Having run fresh deployments (full wipes) of the CM9 and JB ROMs on my KF, I've seen first hand how both should run, given perfect set up. JB wins and it's not even close. If there are issues with a build or deployment, dev should know.

That's all.
[Kindle Fire Android Development] twa_priv:
This is the kernel DEV thread.
[Kindle Fire Android Development] kenikh:
updated
[Kindle Fire Android Development] :
I just modified and erased a long nasty response to you. Its just not worth it nor is it worth putting the nice people on xda through.
[Kindle Fire Android Development] kenikh:
I got it anyway via instant notification. It was a good one.

I am always amazed by how the written word can transform something meant as constructive and helpful into something taken as mean spirited. Again, was just trying to be constructive. Validating a potential issue that might help the core development was the only goal here.
[Kindle Fire Android Development] :
Well i am sorry publicly. It is indeed ery hard to translate trxt. That is why whenever you are mad at a friend or family member, call them, dont email. I appologize, again
[Kindle Fire Android Development] kenikh:
Yep, sorry here, too. Back to the regularly scheduled programming. :)
[Kindle Fire Android Development] e495957:
It seems Hashcode is swaped with this, JB, and the Droid3 development.

I can't believe he's doing this by himself. He needs some help! With CM releasing RC2 we are nowhere in site :(

Do you think we could convince some devs to come over and help with the charging issue and porting this to CM's official servers?
[Kindle Fire Android Development] jamminjon82:
Or be patient?
[Kindle Fire Android Development] ProfEngr:
+1

Sent from my Thunderbolt using one opposable thumb.
[Kindle Fire Android Development] sthomas38:
RCs are just renamed nightlies...

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] e495957:
Right but we're only allowed to report RC and above bugs to the official bugtracker page:

http://code.google.com/p/cyanogenmod/
[Kindle Fire Android Development] sthomas38:
Just a question: I'm wondering if Vsync and triple-buffering on JB are working right now? I read that pawitp, the official CM maintainer for the SGS, was waiting for Nexus S sources to get Vsync and some other Butter stuff working by updating the kernel :).

Thanks ;).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] Hashcode:
Not working yet. I need a binary from TI still before I can swap to the new kernel.
[Kindle Fire Android Development] zenzi:
I can't mount SD card in PC.Please help
[Kindle Fire Android Development] southbird:
That is not helpful. Provide information. Tells us what you've done. Also search this thread, because people have talked about mass storage issues repeatedly.
[Kindle Fire Android Development] veeman:
Boot into TWRP and mount USB.
[Kindle Fire Android Development] incognico:
Or just use AirDroid.
[Kindle Fire Android Development] veeman:
AirDroid is pretty slow. But handy for small files.
[Kindle Fire Android Development] Hashcode:
Today, I received a new 512MB ducati binary from TI to support the full 3.0.31 kernel I have in the 4AI.5-dev branch on GitHub.

I'm going to be re-working the AOSP Jelly Bean build a but and will put something new out when it's ready.

DEVS: Please consider the device tree on Github experimental until further notice :) sync up at your own risk.
[Kindle Fire Android Development] rysk29:
Awesome work hash you are the kindle fire savior!
[Kindle Fire Android Development] astmario:
Did you used libDCE until now, or some modified version of Ducati?

What this new binary means for HD video decoding, vertical sync and stuff?
[Kindle Fire Android Development] kls2k:
I'm guessing we will see an improvement in battery life as well from this ducati.

The one thing I like on stock/modaco is that deep sleep works great.

Thank you Hash for all your hard work
[Kindle Fire Android Development] :
Will we still get any future updates on the CM9 rom or is this 7/5 build the last one coming?
[Kindle Fire Android Development] andTab:
CM9 is much better than JB.

JB is so full of bugs, it's hard to give an opinion (eg browser crashes, device reboots, gapps crashes, etc)
[Kindle Fire Android Development] Krunk_Kracker:
Other than the first few iterations, in haven't had any more issues with JB than I had with ICS.
[Kindle Fire Android Development] collindv:
I am always amazed at how widely varied folks' opinions/experiences are. I have been running jb from day 1 and have not experienced any of these issues.

That being said, I also don't find it to be much better (if at all) than ics. Just have to give hash some more time to work his magic I think :)
[Kindle Fire Android Development] Aesrys:
I'd agree. JB has been running really well for me overall (I've been using Twa_priv's ROM mostly, though I have tried others). Few to no crashes, Google Now works (except voice), and it runs very smooth. For anyone having problems, I'd strong suggest doing a full wipe (factory, system, caches) just to make sure everything is clean. And either use the 7-11, or the new 7-26 gapps, not the 7-17 (is that the right date? can't remember) one, since that seems to really be the buggy one.
[Kindle Fire Android Development] Ch4m3l30n:
I agree with the last 3 comments. JB has been great for me... I just miss some of the AOKP features.
[Kindle Fire Android Development] aegrotatio:
Have you tried a MOT debug cable mod, also called a "factory cable?" It forces the KF to look at USB and adb while booting.

Discussion is here:

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

And here:

http://xdaforums.com/showthread.php?p=20380015#post20380015

You can cut up a cable or use a breadboard like this one. Make sure you get one of the MALE boards.

https://www.sparkfun.com/products/10031
[Kindle Fire Android Development] e495957:
twa_priv, wouldyou consider become the official CM maintainer for CM9 and CM10? It looks like Hashcode can't do it anymore.
[Kindle Fire Android Development] sthomas38:
But he can.
[Kindle Fire Android Development] :
None of these builds are official and twa has a cm10 build... Hash worked on the kernel
[Kindle Fire Android Development] twa_priv:
I do not understand why it is so important for some to be officially supported by CM.

Beeing official doesn't make the ROM any better - and unofficial ROMs will always have some more fixes/features/tweaks anyway - or include fixes that either won't get and are not yet merged to CM.
[Kindle Fire Android Development] :
I am on the same page as you... You know i am a big supporter of your work... Was just responding something that was posted
[Kindle Fire Android Development] Hashcode:
I haven't gone anywhere. Its been a busy summer and I've been trying to bring another 512mb phone device up to speed.

I'll be back with more time to work out the bugs on a new build-base here soon.

CM folks said they would merge in the Kindle Fire as soon as the charging issues were worked out.
[Kindle Fire Android Development] MizzouBrent:
Battery drain is still a known issue on ics and jb right? I get it while the kf sleeps no matter my setup. No wakelock just consistent battery drain.
[Kindle Fire Android Development] :
Hash:

Will you post a CM9 build for us when you release the new kernel?
[Kindle Fire Android Development] kls2k:
Yep, still an issue. Stock/Modaco rom are the best regarding sleep battery.
[Kindle Fire Android Development] jamminjon82:
New build up on rombot.org
[Kindle Fire Android Development] Hashcode:
OP updated for new CM10 alpha. It does have a bootanimation issue I'm working through but you are free to test and report issues.

I'm considering this ALPHA.
[Kindle Fire Android Development] Aesrys:
Thanks for the hard work Hash, I know we've all been looking forward to the change. Is there a separate file for the kernel only, or is it potentially only compatible with your ROM?
[Kindle Fire Android Development] gunza:
Thanks Hash! Downloading now!
[Kindle Fire Android Development] Hashcode:
Right now these changes would break any existing ROM. I will be doing kernel only updates where I can going forward, and I'm sure most devs won't pick this kernel up till the vsync/bootanimation issue is fixed.

I will post a new local_manifest and talk to twa_priv about maintaining a custom framework to include Kindle specific changes that the community wants (like tablet mode switch).
[Kindle Fire Android Development] Aesrys:
Thanks, again, we all appreciate it. If you had to make a rough guess, how much difference would you say the new changes would affect battery life for a typical cm10 rom?
[Kindle Fire Android Development] pbailey212:
I got a 6127 antutu benchmark score. That's 600 points higher than I was getting. Every thing seems to be running smoothly so far

sent from my Nokia 5110
[Kindle Fire Android Development] rorogio:
what version antutu? versions below v 2.9.1 had wrong low CPU numbers with JB
[Kindle Fire Android Development] wws12:
Hey Hash! Great work on the new update. Few questions though, how is battery life compared to your JellyBean AOSP? And, will I have to do a full wipe if I flash this? Thanks!

wws12
[Kindle Fire Android Development] pbailey212:
You will probably need to do a full wipe, its going from apsp to cm10, and I'm guessing he updated the device tree. I just make a backup in twrp, do a full wipe, flash the Tom and gapps and let it boot, then I go back in to Twrp and restore the data from the backup I just did and *poof* all your apps are back
[Kindle Fire Android Development] Uejji:
I'm glad you're making these. Performance is really nice. However, the lack of a tablet mode switch means I can't really use this as a daily driver.

I'll definitely keep my eye on this though,
[Kindle Fire Android Development] wws12:
Is battery life better on this ROM than AOSP JellyBean?
[Kindle Fire Android Development] powerpoint45:
Good job #code ur freakin amazing
[Kindle Fire Android Development] riverzhou:
"bootanimation issue" is because of omap hwc.

It seems init external hdmi display first and then back to lcd.
[Kindle Fire Android Development] jsisaev:
where can i get the source of this new kernel?
[Kindle Fire Android Development] riverzhou:
I got a 6749 antutu benchmark score at my ROM.

It's use old kernel .

https://github.com/riverzhou/device_otter.git
[Kindle Fire Android Development] sergmurtazin:
Guys, plz can someone give me a 2.** kernel for CM10?

3.** have outreached energy consumption :(
[Kindle Fire Android Development] pbailey212:
The 2.0 kernel is not any better for battery life, and it won't be compatible with current roms. Plus you will lose hardware acceleration. I dont think There are any cm10 roms that will work with it. You would have to find an old cm9 rom if that's the route you really wanted to go.

sent from my Nokia 5110
[Kindle Fire Android Development] pbailey212:
I found a bug, whenever I go in to app info to delete an app, I get a "this process has stopped" error. Then the system UI completely freezzes up. When i reboot the device it goes in to an endless bootloop. If i to in recovery and wipe dalvik it will boot up normally again. When i get home I will post a log cat. Can someone else try to reproduce this to see if its just me. Thanks

sent from my Nokia 5110
[Kindle Fire Android Development] twa_priv:
I got the same on my own build using the new kernel/device/vendor sources. First boot after flashing (including dalvik & cache wipe) is fine. But subsequent reboots end up in endless bootloops/restarts.
[Kindle Fire Android Development] Hashcode:
Thanks, definitely need logs so I can debug the new kernel and get it daily ready.

Riverzhou: yes, hwc needs api 3, where I was getting a blank screen. I need to trace why fb data is sent to external display and not lcd2.
[Kindle Fire Android Development] Hashcode:
This ROM is not about performance tweaks yet. Trying to update to 100% TI kernel source for future improvements.

Tho 6700 is a nice score.
[Kindle Fire Android Development] twa_priv:
Once you put TARGET_USE_KRAIT_BIONIC_OPTIMIZATION back the score will be about the same :)
[Kindle Fire Android Development] Hashcode:
Yeah I like to play it safe when I do a lot of big changes. :)
[Kindle Fire Android Development] twa_priv:
Hey Hash,

In case it helps - attached a logcat and kmsg output taken during a reboot cycle. The device eventually booted up successfully after rebooting itself a few times.

I noticed a bunch of kmsg "Out of memory" errors.

Thanks
[Kindle Fire Android Development] pbailey212:
Thanks. I was trying to do that, but alogcat. would force close when i tried to reproduce process stopped error. I will dust off my PC and get adb running to get a lofcat that way. Has anyone been successful installing/uninstalling apps? I might try another full wipe install and see if it still happens. I do have to say there are a lot of improvements in the responsiveness

sent from my Nokia 5110
[Kindle Fire Android Development] Tbbo514:
dude id thank you 1000 times if i could this is awesome
[Kindle Fire Android Development] dgg4:
Very nice ROM --- btw, so far no issues with charging. The charging light comes on when I plug it it, but shuts off if I power off the screen. But that's just a visual change...it charges just fine (about 30% per hour). And the battery life has been very good. I read for about 8 hours yesterday with just a few breaks and while I don't recall the exact battery drain, it was definitely not more than 70% over that time. In short, it's working just they way I'd hoped!

Many thanks!
[Kindle Fire Android Development] wws12:
Do you mean you had 70% remaining or 70% used up at the end of your reading session? Also, do you have any special settings configured to get this kind of battery life?
[Kindle Fire Android Development] :
So does this mean CM9 won't receive a kernel update?
[Kindle Fire Android Development] wws12:
Is the battery life better on this ROM than JellyBean AOSP? Also, what new features will I see as an end user if I update to this ROM from AOSP JellyBean?
[Kindle Fire Android Development] pbailey212:
After another fresh install things seem to be working properly (besides the known boot issues) I'm excited to see where this goes. Thanks for everything haschcode

sent from my Nokia 5110

---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------

Its only been out for a day. There is really no way to tell if battery or performance is better yet, both seem improved but too early to tell. Give it a try. The only new feature that I can see is the screen shot in power menu is back

sent from my Nokia 5110
[Kindle Fire Android Development] merwin:
Battery life is good for me... at least as good as the previous rev. The OS is smooth as butter and it benchmarks close to a Galaxy S2 now (not sure what it was before).
[Kindle Fire Android Development] razz1:
As always nice work Hash!! Lovin all the work your putting into the Kindle and Bionic. If it weren't for your knowledge, the Bionic would be dying and the Kindle just wouldn't be so exciting.

Thanks man!!!

0x48 0x65 0x6c 0x70 0x20 0x6d 0x65 0x21 0x21
[Kindle Fire Android Development] koroshbhasabrain:
Rombot is down

Hey Hash! Thank you for all your hard work! Unfortunately, I cannot enjoy it because ROMBOT is down.

Can you upload a mirror link, like dropbox or something?

Or, if you still have access to it, why am I not able to access rombot?

THANKS!!!!!
[Kindle Fire Android Development] Hashcode:
Finding a new home for the ROMs. Be a day or so while I work it out.
[Kindle Fire Android Development] JaViJeC:
Can be Goo.im

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Kindle Fire Android Development] koroshbhasabrain:
Thank you Hash!
[Kindle Fire Android Development] :
Dropbox
[Kindle Fire Android Development] diba320:
DropBox would be a bad idea, because they close accounts having too much traffic.
[Kindle Fire Android Development] sthomas38:
Goo.im is very good :).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] sagnam:
goo.im is too unreliable. I'm not surprised devs are looking elsewhere for hosting.
[Kindle Fire Android Development] e495957:
It's a shame the CM team can't host it yet. That dang pesky charger issue. I can't believe they won't host us because of that.
[Kindle Fire Android Development] sthomas38:
Do you think CM would be CM if they were officialy supporting buggy devices? Even the 0.5 second white screen when you wake up the device is an enough big issue for them to not support the Kindle Fire. CM is the reference ROM in the Android world and it's a ROM meant to work better than stock for every device, without noticeable issue for each of them, even the most low end ones :). Only very few devices have official CM10 nightlies, or even CM9. So be happy with Hash's nightlies, he's the man :p.
[Kindle Fire Android Development] twa_priv:
Not true - the KF is not more or less buggy than other devices officially supported by CM.

For example the GT 10.1 is officially supported but also has some ugly bugs - like sleep of death while charging ...

But again ... who cares about beeing official or not. Does not make any difference at all.
[Kindle Fire Android Development] sthomas38:
Ahah so...:p
[Kindle Fire Android Development] anactoraaron:
A while back I started a thread for KF users (In the KF General area) to discuss their observed behavior in regards to this 'charger issue'. From various accounts, and based on my own observations, everytime you plug in the KF it WILL charge. The only issue is whether the charging indicator will come on (not that important) or whether or not the os will detect the device is plugged in (also not that important). I personally don't see any charging issue as my KF always charges when plugged in and honestly don't care if the indicator comes on (it's really bright) or if the charging icon is displayed (I'm focusing my eyes elsewhere). I also agree that we don't need CM to be official for this device to be great- it already is!
[Kindle Fire Android Development] december.underground:
Where do I download just the kernel?