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

Search This thread

Feorch

Member
Jun 26, 2013
20
2
Download flashify from the play store and flash the IMG. BTW you guys are screwed of anything happens to your tablet because you have not taken the time to learn how to do things by command line. I promise you it's worth the effort and time

Sent from my VS980 4G using Tapatalk

i did it using the app flashify, thx.
 

mikeataol

Senior Member
Nov 21, 2013
672
334
video streams

I loaded the M8 , then followed it up with the 20140714 nightly.

Happy that location issues seem to be resolved.

I am seeing more than one app (news stations) that fail to stream video .
seems like the video "just" starts, then chokes

CNN, youtube, and some other news apps work fine, the apps in question havent been a problem on earlier releases.

Does anyone have any hints on what to try?
I tried individually

in developer options:
Force GPU rendering
Disable hardware overlays

in Performance options:
Enable 16 bit transparency

------------------------------------------------------------------
Thanks! @ hashcode, this is an awesome build.
 
Last edited:

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
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.
 

goingcrazy614

Senior Member
Nov 8, 2012
288
59
columbus
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.

Wish you the best!!!!!!!!!!!!!!!!
 

elitelemming

Member
Apr 6, 2013
17
0
Edinburgh
Anyone else having network connection problems with M10? Only seems to connect to my wifi properly 1 in five attempts or so, usually connects but failed to find/set DNS meaning local IPs are reachable but no domains, anyone have any ideas?
 

jamminjon82

Senior Member
Mar 9, 2012
845
269
Gloucester
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.







Are you planning on porting CM12?
Read this quote


Sent from my VS980 4G using Tapatalk
 

Eelviny

Member
Mar 31, 2012
40
11
LG Nexus 5X
Xiaomi Poco F1
With CyanogenMod dead, and there is unlikely to be any support from Lineageos, I'll just post some download links here to keep you guys going!
Development is completely dead on the CM side, so I've linked the archive.org backup of the last produced nightly.

CyanogenMod 20160815: https://web.archive.org/web/2016122...kins/174310/cm-11-20160815-NIGHTLY-otter2.zip
Latest gapps: http://opengapps.org/?arch=arm&api=4.4&variant=nano

I've moved from Amazon OS 10.5.1 to CM with only one hitch - I used the Kingroot app to gain root access, and from there you can follow the normal instructions. Make sure you have the most up to date TWRP, or the CM zip will fail!
 
Last edited:

derlbear

Senior Member
Jun 25, 2009
202
0
I've moved from Amazon OS 10.5.1 to CM with only one hitch - I used the Kingroot app to gain root access, and from there you can follow the normal instructions. Make sure you have the most up to date TWRP, or the CM zip will fail!
I was happy to see your post, especially when reading the "ONLY ONE HITCH". What are the NORMAL instructions? Nearly everything seems to be down.
 
Feb 27, 2012
40
9
Berlin
Hey Guys

I just compiled the latest LineageOS 11 (Android 4.4) with security patches from june:

lineage-11-20170708-UNOFFICIAL-otter2: https://mega.nz/#!doN2mY5L!HjXPmYaAhAa3oUJNn8a178_kOPW2XdUNKR8SUvYKSvw
GApps: http://opengapps.org/?arch=arm&api=4.4&variant=nano

Screenshot
See attachment

I JUST COMPILED THAT. ALL THE WORK WAS DONE BY @Hashcode AND ALL OTHER CONTRIBUTORS. USE AT YOUR OWN RISK! BACKUP EVERYTHING!

Troubleshooting
If you have problems with WiFi try to set the right wifi region code (Settings -> Wifi -> Advanced -> Wifi Region Code).
 

Attachments

  • Screenshot_2017-07-08-12-57-29.png
    Screenshot_2017-07-08-12-57-29.png
    83 KB · Views: 157

mikeataol

Senior Member
Nov 21, 2013
672
334
Hey Guys

I just compiled the latest LineageOS 11 (Android 4.4) with security patches from june:

lineage-11-20170708-UNOFFICIAL-otter2: https://mega.nz/#!doN2mY5L!HjXPmYaAhAa3oUJNn8a178_kOPW2XdUNKR8SUvYKSvw

Hi, just some positive feedback.
Installs and boots fine, I used an older gapps to start, one that was closer to the release of the original CM11's.... I haven't had luck with brand new opengapps on cm11 roms.
updates to the latest play store just fine.

The rom runs fine, I was hoping for screen casting drivers to have somehow magically appeared, but wont happen I guess....
I had no problems with WiFi

Thanks for providing it.
 

jaramosp

Member
Apr 30, 2015
15
1
Hey Guys

I just compiled the latest LineageOS 11 (Android 4.4) with security patches from june:

lineage-11-20170708-UNOFFICIAL-otter2: https://mega.nz/#!doN2mY5L!HjXPmYaAhAa3oUJNn8a178_kOPW2XdUNKR8SUvYKSvw
GApps: http://opengapps.org/?arch=arm&api=4.4&variant=nano

Screenshot
See attachment

I JUST COMPILED THAT. ALL THE WORK WAS DONE BY @Hashcode AND ALL OTHER CONTRIBUTORS. USE AT YOUR OWN RISK! BACKUP EVERYTHING!

Troubleshooting
If you have problems with WiFi try to set the right wifi region code (Settings -> Wifi -> Advanced -> Wifi Region Code).

Do you can update too the Kindle Fire HD 8.9 (JEM)? I use the old Hashcode 4.4 rom. Thanks!
 

bothered

Senior Member
Jul 12, 2010
306
65
Samsung Galaxy S6
Samsung Galaxy S7
Just compiled the latest version of LineageOS 11 (security patch December, but still shows November...). lineage-11-20180208-UNOFFICIAL-otter2: https://mega.nz/#!wllkhIqR!IQmSExATGjhA5z6dzaZrAMq29LgShvnuJ4BoRrE5axk
For example WPA KRACK is now fixed :D For more information see two replies above.

Thank you so much.....Just a couple of things

I used this guide (2nd bootloader etc)
https://xdaforums.com/showpost.php?p=75445443&postcount=568111

but this recovery
-otter2-twrp-2.6.3.1-recovery.img
(2.7 didnt work)

and this gApps (between rom and gapps install i might have had to wipe dalvik cache first)
-open_gapps-arm-4.4-pico-20180828.zip
(latest open_gapps-arm-4.4-pico-20180910.zip didn't load google play)

and downloaded this youtube apk directly and installed
-September 9, 2018 armeabi-v7a Android 4.2+ 160dpi (might have been 240dpi try )
(as from google play the youtube didnt work properly - this may have just been me though. After apk install not sure if then signing into google play improved anything/settled system down)

but all happy with it, so enjoy
 
Last edited:

mikeataol

Senior Member
Nov 21, 2013
672
334

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    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
    6
    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.

    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
    5
    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.
    5
    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



    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
    4
    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.