yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] mikeataol:
This is an excellent rom!

my only comment is that I think its absiolutely necessary to resize partitions if you go with this one

using stock partitions

/system partition only had 5 MB (!) free after a normal install

/data around 150 MB

I felt comfortable taking 1GB away from /media and added 300MB to system, and 700MB to /data

with a whole slew of user apps added , I felt better giving those partitions some breathing room.

thanks again.
[Kindle Fire Android Development] wastedlife:
Which gapps did you use? Things shouldn't really grow in the system partition unless you move apps there. Data make sense to increase for sure, though.
[Kindle Fire Android Development] mikeataol:
Hi, I applied the gapps in the first post, but then I let Play Store update everything, and then I cherrypicked several more google apps from play store.

Yes I was kinda surprised at only 5MB free but thats okay, I customize them a lot anyway, and learned a few things along the way...
[Kindle Fire Android Development] Hashcode:
I'm still toying with the final #s. But the upcoming "OtterX" builds will use a combined /data/media storage (data and sdcard combined) and add about 150mb to system to allow for future expansion.

I need to reimplement a better fix for an emmc bug that was bricking devices early on. The fix that is currently in place is ignoring trim/discard requests which adds up to I/O lag over time. This is especially harsh on systems with combined data+sdcard storage, as the /data partition is almost never ever formatted.

A patch was added to the upstream kernel which allows for the regular trim/discard requests but will turn the brick causing requests into a safer alternative erase.
[Kindle Fire Android Development] mikeataol:
Hi (feel free to move this post or point me to a more generalized area where its been covered...)

I'm confused about all the different storage schemes and so far, none of them seem to be the greatest solution.

I know, they really borked things up with permissions to storage in KitKat

CM11 on KF1, seems seemless enough. I like it! (It uses some "fake" USB scheme, right?)

CM11 on KF2 isnt seemless, you need a download manager as an intermediary it appears. Its using emulated storage. I could be wrong as Ive only used it one day.

CM11 on NOOK tablet

requires

an SD card despite more internal storage than both KF1 and KF2 (It uses internal as SDCard0 / SDCard1 ). I havent seen any movement fixing that crippling limitation since it was introduced in January.

each different device is using some a different mount points/partition schemes , and it seems lots of the issues revolve around CM trying to assure that it can assert an update through automatic updating.

so... to the uninitiated (me) ,

there doesnt seeem to be that many potential configs on tablet devices that have to be accounted for.

phones probably vary more widely.

I have the nagging feeling that the need to require "automatic" updating is hindering other things if you have to spend all this time correcting CM updating issues

whats the lay of the land regarding consistency across CM11 implementations, and who makes these calls anyway?

again, im just looking at this as a (power?) user, and trying to understand the bigger picture.

thanks, forgive the ramble.
[Kindle Fire Android Development] Hashcode:
FYI, a trim fix was introduced into the latest nightlies which should greatly improve on the sometimes ultra lag that can be experienced.

I would love some feedback from those users who have had lag problems on cm11 specifically.

To notice an immediate lag relief:

- Install latest nightly

- After booting back into Android, open up the terminal

- Enter the following commands:

su
fstrim /data
fstrim /cache

These commands are only if you have bad lag and want to fix it immediately. The OS will perform these operations correctly from here on out while the device is idle.
[Kindle Fire Android Development] Hedied4me:
Unfortunately upon entering fstrim/data in the terminal emulator I get:

sh: fstrim/data: not found

What am I doing wrong? I did enter su before.

Edit: Oops thanks
[Kindle Fire Android Development] mikeataol:
the command has a space between fstrim and the directory

fstrim (space) /data

fstrim (space) /cache

--------

I installed the 20140323 nightly, and although it was not needed I ran the commands and they both completed without error.
[Kindle Fire Android Development] Anthony96922:
Can you make an AOSP 4.4 rom for us? That be great
[Kindle Fire Android Development] :
For you? Everyone wants it, beside, [MENTION=4243514]Hashcode[/MENTION]said he's completing the 3.4 kernel
[Kindle Fire Android Development] mikeric:
I was having lag problems real bad, my wife wouldn't even use my kindle. Seems to be much better now. Thanks.
[Kindle Fire Android Development] Hashcode:
Google Play Movies streaming fix in tomorrows nightly. It would timeout every 4-5 mins. Thanks to [MENTION=3457922]stargo[/MENTION] who took some time and debugged it.
[Kindle Fire Android Development] lllukas:
Hi, first of all: Many thanks for Your great works !

I have question, can You add new stable release of zzmoove governor with profiles ?

And i had lags too, but after strim command everything works well !

Thanks once again ;)
[Kindle Fire Android Development] lovejoy777:
thanks Hash awsome, i was having alsorts of issues on the m4 build after emmc restore. but since installing the latest nightly and ran fstrim commands it seems completely fixed. thanks again Steve
[Kindle Fire Android Development] :
I have been Testing the Trim Fix and Actually Found it Quite useful. Thanks for the Work.
[Kindle Fire Android Development] sabres032:
[MENTION=5417966]androvista[/MENTION] Will the trim fix work with your InFriction ROM?
[Kindle Fire Android Development] :
You could have posted it in my thread. No, those builds are from march 7 and trim fix came on 23rd. Next Update(On 17th) will have that
[Kindle Fire Android Development] sabres032:
Ooooops, I thought I clicked on the shortcut to your thread. Sorry. No hard feeling [MENTION=4243514]Hashcode[/MENTION].
[Kindle Fire Android Development] lifegap:
Sound laggy when minimizing the app or switching to other app

The ROM is great for my KF1 (20140319 NIGHTLY). But there is still minor bug: when I playing music (Appolo, Google play music or podcast), if minimize the app or swich to other app, the sound is broken, cracking and lagging in several seconds. Do you have similar issue?

One more thing: Apollo app could not link directly to the DSP manager (no option for equalizer of DSP in Apollo setting while Google music have). So I have to minimize the app and run DSP manager seperately and laggy sound happen :(
[Kindle Fire Android Development] MrBrady:
Anyone else having issues with the 4/1 build? I just updated (CM updater) from 3/28 to 4/1 and get nothing but errors upon startup. I had ART enabled, so I'm guessing that's the issue, but it's worked fine on the past two builds I tried.
[Kindle Fire Android Development] Hashcode:
You bring up good point. Somewhere along the way, the audio has an issue with going into low power mode (where its not the primary app). That broken sound is the OS sending either too much sound data or too little compared to what the audio sub system is expecting.

I'll add it to my list. Thanks.
[Kindle Fire Android Development] :
Patiently waiting... OtterX nightlies
[Kindle Fire Android Development] jkt97401:
is ART working on this ROM?

I just inherited a kindle fire 1st gen and I'm trying to make it faster!
[Kindle Fire Android Development] FuZZ__:
I've been testing with this one http://review.cyanogenmod.org/#/c/62128/

Actually that fixes the issue on some devices, such as Nexus 4 or Galaxy Nexus, but not for our tablet,

just end up with a lot of crashes and eats up storage that couldn't fix just revert to dalvik.

Conclusion: Do not even think about it

perhaps that option should be hidden on legacy devices, IMHO

EDIT: forgot to mention, I believe current CM11 build is snappy OOB
[Kindle Fire Android Development] koop1955:
Quoting from the OP:

***********

STEP 2: DOWNLOAD A BUILD OF CM11.0:

DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM

***********

Speaking from my personal experience, enabling ART doesn't make much difference in speed/performance at this point. And it does lead to instability.

If you want to read a comparison of Dalvik vs. Art, check this article out: http://www.androidpolice.com/2013/1...ormance-wont-blow-away-today-will-get-better/

Note the author's conclusion, "Once I've finished this series, I will probably stick to Dalvik for the remainder of KitKat; and I imagine most people will be better served by doing the same."

Update: Yeah, what FuZZ_ said. ^^^^^^ :)
[Kindle Fire Android Development] :
I saw these comments and flashed to test. ART works fine and without any hiccups with PA Micro Modular GApps:cyclops::cyclops::D:D:highfive:
[Kindle Fire Android Development] koop1955:
Did you run any benchmarking software? Results before and after?

If all a user wants to run is minimum GAPPs, then ART might be fine, although I question whether there would be any discernible improvement. Seriously, would Gmail load faster?

If you want to run games or apps, there are whole lists of things that don't work well under ART. For me, both Titanium and Greenify were unhappy. My biggest issue was the email client that I needed for my Exchange email. This was months ago and I know that Greenify at least has been updated, but still...

Here is a searchable database if you want to see if any app or game that you use is still reported as being broken:

http://androidruntime.com/
[Kindle Fire Android Development] thedarksavant:
I ran ART just fine for a while, but then an app I wanted to use/play (Avadon) would not load.

The key is to switch to art, immediately boot into recovery and wipe dalvik.

There are more detailed instructions in this thread.

I did not notice any speed up, but I wasn't looking. I was just experimenting.
[Kindle Fire Android Development] :
No need to wipe dalvik if you have an art compatible gapps
[Kindle Fire Android Development] Roseysdaddy:
Picked up my kindle after 11 days and it was at 60% battery. That's amazing.
[Kindle Fire Android Development] yaconsult:
I had switched back to stock and then tonight wanted to reinstall this rom. After doing so, everything looked fine, but I could not get neworking to work at all - it saw all the routers but could not connect to them. After searching this thread for networking problems (a VERY nice feature of this forum!), I saw that some others had reported networking issues after install and had solved it by dirty-flashing the rom again. So, with nothing to lose, I gave it a try and reflashing did indeed get networking going.

Just wanted to mention this to help out anyone who runs into it. What a nice rom this is on the Fire! Thank you for all the work people have put into it!
[Kindle Fire Android Development] powerpoint45:
Nice job hashcode!
[Kindle Fire Android Development] minix51:
This ROM has OTG support ???
[Kindle Fire Android Development] minix51:
Just install CM11 20131125

successfully install CM11 20131125..Big Thanks to the developer and thread owner..this is my first ROM on Kindle fire first gen., after successfully rooting it yesterday.

I found the default browser a bit laggy..

can I update this normally on the device setting without using TWRP... ??

what would be the best update ...I am considering the latest nightly builds...Thank you...ty :)
[Kindle Fire Android Development] VTCruzer:
EDIT: I guess you can update from Settings. Me and my misinformed mind. Sorry about that I haven't used this ROM in a while :P
[Kindle Fire Android Development] Hashcode:
I highly recommend grabbing the next M release from download.cyanogenmod.com

Should be in the next week.

Then you can update whenever you want in Settings (under Device)
[Kindle Fire Android Development] minix51:
thanks! Your reply is very much appreciated

Right now my chrome browser is not working its keep crashing when I open..but my other gapps work fine..I will try reinstalling it
[Kindle Fire Android Development] draexo:
Rooted the fire a while ago and put CM 10 on there. Had trouble installing CM 11 until I found and read this thread's OP. All seems good now!

Thanks!
[Kindle Fire Android Development] Hashcode:
New audio changes coming in the next nightly (if i made the cut off).

- Added low power support for when the screen is off / cover closed. (Was noticeable as stuttering)

- Debugged some audio record issues (will probably need to revisit MIC recording)

There is probably still an issue where if you are doing 2-3 use cases for audio, it will cut out. I'll see about fixing that up later.

Let me know if you guys see any improvements.

NOTE: This change would also be available in any new OtterX builds as well.
[Kindle Fire Android Development] FuZZ__:
Unfortunately those changes ended up made the issues outstanding, as the volume lower than before...

You shoud have added me as a reviewer before merged those.
[Kindle Fire Android Development] minix51:
---------- Post added at 05:22 PM ---------- Previous post was at 04:47 PM ----------

[/COLOR]

M release you means snapshot release M6 ?
[Kindle Fire Android Development] Hashcode:
The volume on otter speakers was so loud that I felt it was dangerous to the device.

If otter2 needs a spearate mixer_paths.xml then we can split it out.

Which device are you noticing low volume on? And is it speakers or headphones?

Also was there some other issue with the new changes?
[Kindle Fire Android Development] FuZZ__:
First of all sorry about my first roughly impression, maybe that was not a good one...

I'm really appreciated that lower speaker volume change since I was thinking of same things and it seems to be working as intended.

The problem is now the sounds are clipping (distortion?) whenever I play music or youtube video that didn't happen before that change.

I haven't fully tested but confirmed that with built-in speaker on otter and otter2, haven't tested with headphone yet.

I'll test those changes more for next few days.
[Kindle Fire Android Development] Blitzpwnage:
Night 5\4 made my speakers all crackily and degraded the sound

I tried flashing back to the 4/20 nightly and now my home button and notification drawer won't pull down lol any advice?
[Kindle Fire Android Development] Hashcode:
You might need to backup your apps, do a complete wipe and restore apps after the downgrade to 4/20. They pushed theme engine updates which are probably affecting you.
[Kindle Fire Android Development] Hashcode:
Yes, I'm noticing the YouTube distortion now as well. I'll debug and see what I missed in the audio settings.
[Kindle Fire Android Development] Hashcode:
I put this change on gerrit review so you can test before I push:

http://review.cyanogenmod.org/#/c/63394/
[Kindle Fire Android Development] hav22:
Hello,

Does the issue with kernel crash during USB2.0 device connection still remain?

Thanks.

Sent from my Amazon Otter
[Kindle Fire Android Development] Hashcode:
This was pushed today. 1 more bugfix coming for playing music.
[Kindle Fire Android Development] maltydog:
I have been using the Nightlies on these for a while. I have had an issue for about the last week or so. On my status bar, I continously have a downward arrow, if I pull down the status list, I get a message "18 files downloading", and CM Updater listed multiple times. If I click on it, nothing happens. If I open the CM updater, there are no files listed as downloading. I have updated to several new nightlies, I have rebooted a few times, and nothing seems to get rid of this message. Can anyone tell me how to stop it or turn it off? I also looked under Applications running, and I didn't see anything that seemed to have anything to do with it.
[Kindle Fire Android Development] Hashcode:
There are some odd system ui bugs going on in the current nightlies while the new theme engine is being ironed out.

This issue sounds related.
[Kindle Fire Android Development] maltydog:
Thanks for the clarification.
[Kindle Fire Android Development] MrBrady:
I'm currently running CM11 M6. Everything was working fine until last night. I left Pandora playing and went to sleep. I suppose the battery drained completely overnight because I woke up and the Kindle wasn't awake.

Since then I plugged it into the wall with the Kindle charger and it won't charge (no boot screen, no button light). I tried my Galaxy S3 charger and it won't charge. This happened a few weeks ago too, but it ended up charging once I found the original Kindle charger. No such luck this time around.

Anybody have tips on how to get it to charge?

Once I get it up and running again I'll probably jump over to OtterX.

Thank you for the help!

EDIT: Problem solved! For some reason when I plug it into my computer, it fires right up. Very strange. Waiting for a full charge then migrating to OtterX.
[Kindle Fire Android Development] jianC:
I don't think the battery drained completely. I had the same issue, and I held the power button for ~20 seconds to completely shut it off/reset, and turned it on again, and it worked. I'm guessing it froze while sleeping, and it should be the same case for you.
[Kindle Fire Android Development] Hashcode:
FYI, when updating to a new nightly, it seems to be causing device ID resets (all settings get reset and status bar issues start).

The only way to fix this is to do a wipe and re-install apps via TitaniumBackup / Google restore.

It's not something I can fix on my end.
[Kindle Fire Android Development] rogersa2k:
Is this something new? I last updated to a nightly on 05/12 and did not have these issues.

Thanks,

Aaron
[Kindle Fire Android Development] Hashcode:
It's just something I notice randomly when I update. Wanted to make everyone aware of it.
[Kindle Fire Android Development] Hashcode:
Quick update:

- Audio issues should be better in the 5/20 nightly. Let me know how it works for you, if you're testing nightlies.

OTTERX folks: I'll probably run a new build here soon as I get some feedback on the audio changes.
[Kindle Fire Android Development] FuZZ__:
Is it just me but I just realized Google restore completely stop working with clean install.

And Play Store always returns error code '927' whenever I attempt to install any apps, that happens my other devices as well.

I recommend you to do not do a clean install for now.
[Kindle Fire Android Development] Hashcode:
I haven't seen the Play Store error.. but then I don't let Google backup/restore apps.
[Kindle Fire Android Development] FuZZ__:
Hmm, seems the issue has to do with my account then... Anyway, I'm going to restore my environment so that I could test out the audio fixes.
[Kindle Fire Android Development] Icetech3:
Just wanted to say thanks for keeping this device going! I havn't used it in a very long time and kitkat is amazing on it. Wish i would have done this a long time ago rather than get this HDX POS (battery doesn't last a day on standby).. thanks again:)
[Kindle Fire Android Development] For1n:
I can boot into this ROM only first time after i flash it - it runs flawless until reset - if i reboot the tablet it bootloops at CM logo. Even if i wipe cache/dalvik cache in the recovery it still bootloops at logo.

When bootlooping, in the Device manager its detected as Portable Devices/Amazon Otter. No adb access.

fff 1.5 (displays 1.4a tho),twrp 2.7.0.1 otter, newest nightly, i wiped everything except sdcard.

when i try to logcat from the recovery (adb logcat, adb shell logcat...) it returns /sbin/sh: exec: line 1: logcat: not found
[Kindle Fire Android Development] Hashcode:
logcat isn't usable in recovery, but if you do a long press of the power button to shut the device off during the bootloop and then IMMEDIATELY press the power button again and enter recovery, you can sometimes get this command to work:

adb shell "cat /proc/last_kmsg" > last_kmsg.txt

This file "last_kmsg.txt" can be found wherever you're running that on your computer. And it's the kernel log from the failed boot up. So it might help diagnose the issue.
[Kindle Fire Android Development] Hashcode:
Today, I noticed we would end up boot looping (due to a PVR crash) if any sort of higher res bootanimation was selected (via theme manager). Bad bad bad. So to fix that I pushed up some changes in how the bootanimation was being buffered and set it to a slightly easier to handle resolution.

The idea being: I can't control what boot animations are tried out, so they all need to work. If perhaps they stutter slightly, it's better than boot looping.

Enjoy in the next nightly.
[Kindle Fire Android Development] mschumacher69:
Hi [MENTION=4243514]Hashcode[/MENTION], thanks for your great work!

I tried cm-11-20140622-NIGHTLY-otter.zip but WiFi and BT don't seem to be working. Is it just me or is it a known issue? If it is a known issue, what is the latest CM11 build that has both WiFi and BT working?

Thanks
[Kindle Fire Android Development] dokie80:
afaik, kindle fire doesnt have bluetooth...wifi is working on cm11 though
[Kindle Fire Android Development] mschumacher69:
u're probably right about BT. have u tried WiFi on the latest nightly? it doesn't work, unless they fixed it in today's build. I'm on snapshot m7 now and it works fine.
[Kindle Fire Android Development] dokie80:
nope sorry, dunno about wifi issue on latest nightly.. currently use other rom. latest cm i use was snapshot m5 i think.

no intention to try out otterX?
[Kindle Fire Android Development] maltydog:
I've been running these nightlies for several months, and I notice one consistent

bug that has been happening for a while. Icons that I put on the desktop (tablet top?)

keep disappearing when I reboot the device. There are many icons that remain there,

but I haven't been able to add any for a while. Not sure why.
[Kindle Fire Android Development] Sblood86:
I haven't updated my KF in quite awhile but I remember an issue at one point where that was occurring when adding icons while in landscape mode. They would vanish when I reboot or sometimes when transitioning from landscape and portrait. As a work around I wound up placing my icons from portrait mode but that created issues with placement obviously (that isn't an issue on my current install but as I said it's particularly old anyway).

Edit:

just to answer your question in parenthesis there I believe the word you were looking for is homescreen ;)
[Kindle Fire Android Development] maltydog:
Ah, yes, homescreen. I've had this happen multiple times, and I am not sure about whether I was in landscape or portrait every single time it happens, but it's definitely worth checking out. I will take a look. Thanks.

===================================================

Edit: okay, I tried adding icons in the portrait mode, a number of them, rebooted the computer,

and they all disappeared. So it does not seem to have worked.
[Kindle Fire Android Development] Alessioromatm:
Does the CM OTA update wipe the kf or not? Can I safely upgrade?
[Kindle Fire Android Development] tmosxda:
Working perfectly for me. Awesome job. Thanks to the developers.
[Kindle Fire Android Development] maltydog:
I've been running these nightlies for a while, and I have run into an annoying problem for a while now with WiFi. When I move from one WiFi location to another, the WiFi just goes off, and I cannot turn it back on. I have to reboot the device to connect to a different WiFi. Any suggestions on how to fix this?
[Kindle Fire Android Development] yotvb531:
Are we able to start using the otterx builds yet for the first generation kf? They started rolling out weeks ago. I read on Google+ that there was going to be an update-from-otter-to-otterx wiki made, but never saw a link to it, if it exists yet.

Maybe I can just clean flash the otterx build in place of otter?
[Kindle Fire Android Development] Ixthusdan:
You must use the boot loader and the twrp designed for otterx. There is a process for making the switch, as the partition scheme no longer follows Amazon. Please refer to the following thread for detailed instructions:

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

Do not simply install otterx. It is worth doing.