[Kindle Fire Android Development] Cl3Kener:
All linar experimental build + responses to posts

Hey Everyone,

So I've been busy trying to optimize this Kindle Fire by creating a Linaro arm-eabi toolchain for kernel compiling. I originally only compiled parts of the framework with Linaro and left the Kernel compiler as the usual gcc-4.7 used by Google, CM, etc. Now I've made a complete Linaro 4.8.3 build with my first attempt to optimize the kernel. It seems that it works quite well but I know I can do better than this so I'm going to keep playing around with the different crosstool-ng parameters until I find the best kernel toolchain settings possible!!! :D Here is my current testing build. http://xdaforums.com/devdb/project/dl/?id=2446 You'll probably have to clean flash because of the many changes I made in this build. (I know that I at least had to clean flash to get it to work right and to stop the RR madness) Don't expect it to be perfect yet but you'll feel the difference in performance. Probably the smoothest my kindle has ever run! I did not upload it to goo because I don't want it bugging you to update because this isn't really an update yet it is still very experimental so if you want it you'll have to grab it frorm devdb. If you experience instability or RRs try and grab a log. Thanks!

Now to address all of your concerns all at once.

1) WiFi doesn't work? I don't have a fix for the WiFi issue but if you ask me it seems due to weird permissions issues possibly from the recovery you're using or simply do to SELinux which finally was introduced to the Kindle Fire in 4.4.x. My solution to fixing it is to wipe everything but your SD card and then clean flash ROM and gapps. If you boot up and still don't have WiFi. Try repeating the procedure. I lost WiFi on a dirty flash and a full wipe and clean flash solved that. Unfortunately SELinux is more complicated to fix permissions issues. It used to be your could just run a fix permissions script and all would be well but now those scripts don't seem to work with SELinux so if a flash messes up those permissions the best was to fix them is by reflashing.

2) Will you be building weekly? Yes! We also will bring back as many features as possible. There have been set backs due to build server outages but we hope to really get the ball rolling over the next few weeks.

3) Gapps won't flash? Gapps mess everything up? I've found that Goo Manager doesn't work correctly right now for flashing with my Kindle Fire (Works on my phone though so I do know what it is like when it works). I use it as an OTA update notifier so you know when there is a new update without having to wake up every morning and check. I recommend that you do things the old school way and reboot to recovery and flash the files that way. Also with regards to gapps please make sure that you select a gapps package that is for 4.4.x KK not JB!!! If you know of an ART compatible gapps that you find works with these ROMs please either post here or PM me so I can update the OP with a link to them instead.

4) Changes to device trees? Rather than making changes to device trees via HellKat repositories I will probably submit any patches I find via CM to help all CM based ROMs and not just this one. I believe in helping everyone have better ROMs.

5) Qualcomm-optimized dalvik and bionic files, is there something similar for the Kindle Fire? I've done lots of studying up on the CPU we have here for Kindle Fire to optimize a linaro toolchain for it. Seems we have a generic OMAP Cortex-a9, ARMv7 processor. I've never heard of any optimized dalvik and bionic files for this. It isn't qualcomm so the ones you mentioned wouldn't work. Try this new ALL Linaro build and see what you think. The difference is quite noticeable and I think optimization from the direction I'm choosing might deliver similar results to what you've witnessed on your S3.

Hope this helps clarify a few things.

Cheers!

Cl3Kener