[ROM/KERNEL] CM11 (Android 4.4) + 3.0.72 Kernel for Kindle Fire 2 [NIGHTLIES]

STEP 1: DOWNLOAD TWRP 2.6.3.1 W/ SELINUX .ZIP and UPDATE TWRP(REQUIRED FOR 4.4):
http://goo.im/devs/Hashcode/otter2/recovery-zip/zip-otter2-twrp-2.6.3.1-recovery.zip

Boot into your existing recovery and flash the recovery update zip. Then reboot again and re-enter recovery. You *SHOULD* see "Team Win Recovery Project v2.6.3.1 at the top.


CyanogenMod 11 for the Kindle Fire 2nd-Edition

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***

THIS ROM REQUIRES A 2ND-BOOTLOADER / RECOVERY BE INSTALLED ON YOUR KINDLE FIRE 2. FOLLOW INSTRUCTIONS HERE:
http://xdaforums.com/showthread.php?t=2100963

*** PSA: Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2.
ONLY FLASH ROMs/KERNELS that are made for the Kindle Fire 2. ***


Automated CM Builds:
http://get.cm/?device=otter2

GAPPS (For Android 4.4/CM11 builds):
NEW! http://d-h.st/mDt

CHANGES:

• [12/09] 1st Build -- UNTESTED (I don't own a KFire2)

OLDER GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip


CURRENT KNOWN ISSUES:

• CM11: sdcard access needs a bugfix.
• The headphone MIC input is not functioning correctly yet. Work in progress.
• Virtual keyboard input on Jellybean is terrible. Needs a protocol update or something. Fixing. For now use an alternate keyboard like Swype

KERNEL FEATURES:

• [08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
• [01/06] WLAN Firmware R5.SP3.06
• [11/07] Updated to SGX/IMG DDK 1.9@2166536 for Android (via omapzoom 18 hours ago)
• [11/07] WLAN Firmware R5.SP3.03
• [09/05] Updated to SGX/IMG DDK 1.9.RC2@2139099 for Android
• Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire

DEVS
BUILDING THIS ROM:

First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html

Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 11)
repo init -u https://github.com/CyanogenMod/android -b cm-11
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter2

RESERVED FOR NOTES

Clarke33 said:

Yeah, I read something about that. All I've tried are problematic and I've restored to my favorite, JB Sourcery Encore. It runs like a top.

Click to expand...

Click to collapse

There are 2 main issues with all OMAP devices now.

1st is that only vendors with actual devices in production put out updated blobs. So putting out OS updates we will be harder and harder over time.

I sort of combat this by getting to know as many devs as I possibly can - and hope that we share info about which device can be the source for the next round of updates. As well as staying in contact with ex- TI devs now employed by other companies

The 2nd issue is more about kennel development (and this is where the GNex is caught). Given an unlimited amount of time, a good dev can re-base their device's kernel against a more up-to-date vendor-based branch which is easier to maintain.

In this case 3.0.31-dev was the last public dev branch for the OMAP4s. And GNex doesn't have a kernel based on that branch. So challenges for the next OS version are always high.

Sent from my SM-N900V using Tapatalk

As you some of you may have noticed: I have a new job working with Linaro Mobile Group beginning 9/1/2014.

This is a HUGE change in my professional career, and I want to be 100% focused on my current duties.

This means, that I will be ending my support for the Kindle Fire devices as official CM maintainer.

Over the next few weeks, I'll be working with CM to get a replacement dev to step in and continue updates / tweaks to the device.

For more information:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b

Lastly, ending my support for the Kindles was a VERY difficult choice. My TODO list is long and extensive with plans for updates well into next year ... To not get around to really polishing many of these builds makes me a bit sad.

BUT, this is where YOU (the community) can step in and make a difference. Continue to push these devices onward. I wish you all well.

Hashcode said:

There are 2 main issues with all OMAP devices now.

1st is that only vendors with actual devices in production put out updated blobs. So putting out OS updates we will be harder and harder over time.

I sort of combat this by getting to know as many devs as I possibly can - and hope that we share info about which device can be the source for the next round of updates. As well as staying in contact with ex- TI devs now employed by other companies

The 2nd issue is more about kennel development (and this is where the GNex is caught). Given an unlimited amount of time, a good dev can re-base their device's kernel against a more up-to-date vendor-based branch which is easier to maintain.

In this case 3.0.31-dev was the last public dev branch for the OMAP4s. And GNex doesn't have a kernel based on that branch. So challenges for the next OS version are always high.

Sent from my SM-N900V using Tapatalk

Click to expand...

Click to collapse

TLDR translation :

1.
Vendors don't care about you once you buy their gear, it's always on to the next device to sell you because the longer a device is current and usable the less devices are sold. Selling devices is after all the purpose of their company no matter how many "We change the world with our super cool devices that you always must have the latest version of to be cool". Actually it's not too far from the Apple sales model. The upside is this constant churn of new product creates competition and innovation.

2.
Hashcode and the other less visible developers do their best to keep our devices current, usable, fast and reliable despite the minor amount of support from these multi billion dollar industry of manufacturers (in comparison to what they are capable of doing for support) . Every time we turn on our Kindle 2 or any number of aged electronics remember the gift we are given by Hashcode and those like him.

Some do it because they are technology purist at heart and want tech to be the leverage that improves our lives, others hope it will give them the experience to someday join the industry in a meaningful and hopefully highly paid way, more still do it because they simply can and are curious.


The truth is I bought this off eBay for $60 because I knew the popularity of the first Kindle fire and was betting we would draw a few devs to keep solid content on our device until the next nexus tablet, etc. The longevity actually surprises me still. I was completely shocked that we got one 4.4 rom much less several.

Make sure to thank our developers and hit the thank button every time they post, show our community who is respected and who is grateful.





Sent from my Kindle Fire 2 using xda app-developers app

NIGHTLIES FOR CM10.2 ARE UP!

Automated CM Builds:
http://get.cm/?device=otter2

GAPPS (For Android 4.3/CM10.2 builds):
NEW! http://goo.im/gapps/gapps-jb-20130813-signed.zip

CHANGES:

• [08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)

Enjoy and I'll continue to weedle at build issues as we go.