[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]

Search This thread

Techlyfe

Senior Member
I ****ing hate each and every one of you that is incapable of reading the above. If this was respected, I would have had to go backwards from PAGE 59 to PAGE 16 just to find the goddamn ROM.


Isn't the ROM on that is linked to on page 16 test version 2?

Shouldnt you be using the ROM that is linked in the first post?


04-17: TEST BUILD #3 CAN BE FOUND HERE: http://bit.ly/IShcSq
md5sum: 2985189c98d1534709aecf6bf2acce1b
SUMMARY OF CHANGES FOR BUILD #3 ARE HERE: http://xdaforums.com/showpost.php?p=24955869&postcount=155


Or maybe i'm wrong. <shrugs>
 
  • Like
Reactions: HeWhoWas

HeWhoWas

Senior Member
Oct 17, 2007
53
66
Thank you both for helping me out. I still stand by my original point though: This should be for development only, as stated in the original post. I will be making it my daily mission to remind every single person of this when they post in the wrong place.
 
  • Like
Reactions: simonbove

dnathan13

Senior Member
Sep 17, 2010
828
221
Thank you both for helping me out. I still stand by my original point though: This should be for development only, as stated in the original post. I will be making it my daily mission to remind every single person of this when they post in the wrong place.

Wait... Like you just did twice? What are you developing? ;) Sorry I couldn't resist. :D

Sent from my SPH-D700 using xda premium
 

HeWhoWas

Senior Member
Oct 17, 2007
53
66
I'm not saying I've contributed much, but I have a day job that has to take precedance :) I did help a little during the infancy of the KF CM9 build with JC, but kernel work is above and beyond my level of experience. And yes, I know I'm just as guilty but at this point I feel like it's pissing in the ocean :p
 

intersectRaven

Senior Member
Mar 13, 2010
2,260
1,558
www.intersectraven.net
O...k...my post also got cleaned in the process, anyways, to sum it up:

Please post HOW TO FIX PROBLEMS ENCOUNTERED on this thread. For REPORTING ENCOUNTERED PROBLEMS, please post on the sister thread of this thread located in the GENERAL SECTION.

Hashcode, me and other contributors regularly read BOTH threads so be assured that we are on top of things. Please be PATIENT as hashcode and most of the contributors don't do this as their job and just work on it at their leisure or at their free time. :)
 
Last edited:

twa_priv

Senior Member
Feb 10, 2011
1,701
4,472
Hey Hash,

Seems like Netflix doesn't like your recent device naming changes (Amazon Kindle Fire -> Kindle Fire). The window which is supposed to play the video just pops up for a second and then closes.
I verified this by changing ro.product.model back to Amazon Kindle Fire in build.prop and voila, netflix works again :)

https://github.com/KFire-Android/device-amazon-otter/commit/b130d49e25461a642aad9b122a6b5f0853802501
https://github.com/KFire-Android/device-amazon-otter/commit/e1202a33fbbceb087f6ff7c5fecc54fd51f87bb1

The new boot animation looks good btw. Thanks
 
Last edited:

southbird

Senior Member
Feb 12, 2010
249
100
Hey Hash,

Seems like Netflix doesn't like your recent device naming changes (Amazon Kindle Fire -> Kindle Fire). The window which is supposed to play the video just pops up for a second and then closes.
I verified this by changing ro.product.model back to Amazon Kindle Fire in build.prop and voila, netflix works again :)

[EDIT: Sorry, this was ROM #6 with Kernel #7, didn't realize the change was so recent.] Is there maybe a legal/support reason that Hash changed the name? It seems like it was deliberate and I'm guessing he had good cause.
 
Last edited:

twa_priv

Senior Member
Feb 10, 2011
1,701
4,472
When I installed Netflix by APK, I got the immediate close. When I installed Netflix via the Play Store, it worked perfectly. Is there maybe a legal/support reason that Hash changed the name? It seems like it was deliberate and I'm guessing he had good cause.
I also uninstalled/reinstalled netflix from the play store and it didn't work. Which rom are you on? I tried hash's latest cm9-kfire-3.0-hashcode-04-22.zip and also my own build - same issue. Only changing the device name in build.prop fixed it.
 

southbird

Senior Member
Feb 12, 2010
249
100
I also uninstalled/reinstalled netflix from the play store and it didn't work. Which rom are you on? I tried hash's latest cm9-kfire-3.0-hashcode-04-22.zip and also my own build - same issue. Only changing the device name in build.prop fixed it.

Never mind, I didn't realize how recent this was. I was running ROM #6 with Kernel #7 when I tried Netflix. Hash did mention a Netflix issue he was looking at, maybe this was it. Still, wondering why he "fixed" it as such, and still wondering if it had to do with some kind of lash back from Amazon or something.
 

nathris

Senior Member
Aug 18, 2010
63
28
Victoria
Where do u change it in? Root explorer?

Sent from my HTC Evo 4G using xda premium

That's one way. I prefer to use adb, although it does require you to have the Android SDK.

From the command line:

Remount /system in read/write mode
Code:
adb remount

Copy build.prop to your PC, it will show up in the same directory as adb.exe
Code:
adb pull /system/build.prop

Edit build.prop using notepad or your preferred text editor

Push build.prop back to the device
Code:
adb push build.prop /system/build.prop
 

tedr108

Senior Member
Dec 3, 2011
416
138
Los Angeles area, CA
Where do u change it in? Root explorer?

Any simple text editor should be fine. You can get to it thru Root Explorer or ES Explorer, etc.

Edit: You would probably end up having to change permissions to do it this way, so use the adb method mentioned by nathris above. That's actually the way I normally do things like this, though I am typically booted into recovery while this is being done.
 
Last edited:
  • Like
Reactions: Jaimemex

djkeller3

Senior Member
Jan 15, 2011
628
195
Lexington, KY
Where do u change it in? Root explorer?

Sent from my HTC Evo 4G using xda premium

I use the build.prop editor tool in Root Tools. You can get Root Tools from Google Play. I think its free. :)

Sent from my Kindle Fire using XDA Premium
ROM: CM9 ReloadedROM v1.2H
Kernel: Hashcode 3.0.21(#7)
Overclock: 1.0 GHz Max, 1.0 GHz Min. Performance
Launcher: ADW EX
 
  • Like
Reactions: Jaimemex

AlexDeGruven

Senior Member
Mar 24, 2008
685
213
Ann Arbor
www.structuredthought.org
A note on charging.

While on a standard USB2 plug (or other <1A USB plug), it doesn't appear to charge while powered on (charges fine while powered off).

I was able to get it to show charging when I plugged in to a USB3 port on my UD3 motherboard, but I am having some driver wonkiness with ADB which really freaked my system out.

So, it would appear, if you want to charge via USB, do it via USB3 (with the extra power availability.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 434
    STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
    EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
    http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
    Flash with the following adb commands:
    Code:
    adb shell
    su
    idme bootmode 4002
    reboot
    # back in your PC shell
    fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img

    If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
    Mirror 1: Download (Goo.im)

    BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.

    STEP 2: DOWNLOAD A BUILD OF CM11.0:
    DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM

    NIGHTLIES:
    http://download.cyanogenmod.org/?device=otter

    GAPPS (Use Version "CM 11" row):
    http://wiki.cyanogenmod.org/w/Gapps

    Older builds are found here:
    http://goo.im/devs/Hashcode/otter/cm10/
    http://goo.im/devs/Hashcode/otter/cm10.1/
    http://goo.im/devs/Hashcode/otter/cm10.2/

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

    CHANGES:
    • [05/15] More audio updates to fix low-power states (screen off / background music)
    • [11/25] Released updated build for cm11.0
    • [08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
    • [07/30] Updated to CM10.2 build
    • [05/26] Backlight driver update to help w/ SODs
    • [05/24] Sensor updates (includes light sensor now usable in Android OS
    • [05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
    • [05/14] New audio driver (WIP)
    • [03/27] Reboot Recovery mode is now fixed
    • [01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing 1.9@2166536)
    • [01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
    • [01/07] Battery life / sleep improvements
    • [01/06] Update to 3.0.50 kernel
    • [01/06] Update wifi firmware to R5.SP3.06
    • [12/16] Fixed Deep Sleep
    • [12/15] Added multi-profile fix

    CURRENT KNOWN ISSUES:
    • The headphone MIC input is not functioning correctly yet. Work in progress.

    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)
    • [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
    • Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
    • Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
    • MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
    • Many bugfixes pulled down from TI's omapzoom sources.

    RESERVED FOR NOTES

    XDA:DevDB Information
    Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire

    Contributors
    Hashcode
    ROM OS Version: 4.4.x KitKat

    Version Information
    Status: Stable

    Created 2014-05-01
    Last Updated 2014-05-21
    150
    UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1

    DEVELOPER BUILDING:
    Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
    Patch 1: http://review.cyanogenmod.org/#/c/53917/
    Patch 2: http://review.cyanogenmod.org/#/c/54562/

    And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
    Won't get a decent build till that's all done.



    KNOWN BUGS:
    1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
    6. Headset recording via the MIC input jack doesn't work


    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 10.2)
    repo init -u https://github.com/CyanogenMod/android -b cm-10.2
    repo sync
    vendor/cm/get-prebuilts
    . build/envsetup.sh && brunch otter
    44
    [09/16] CM10 STOCK + 4AI.1.7 KERNEL [STABLE]
    Download Here
    md5sum: b5746745f62c20ed5f6a2520ca506982

    Changes for 09/16:
    • Charging is now fixed. Including basic OTG support. Test away and I can make tweaks as needed. There may be a bug where adb doesn't restart after OTG devices are enabled.
    • Backlight / Panel driver updated. This was probably causing some of the battery drain.

    EDIT: "now" fixed.

    Enjoy.
    42
    I just wanted to do a quick update:

    Got my new device yesterday, and immediately put twrp, fff 1.4a and ICS on it.

    Should be good to pick up where I left off w/ the kernel now.

    Hope to have a new version in a few days.

    Sent from my Amazon Kindle Fire using Tapatalk 2
    42
    New kernel/ROM based on the 4AI.1.7 release are getting a lot better (IMHO) so I'm probably going to do another kernel/ROM release here soon.

    Here's an update of what's coming in the next release:

    1. Kernel Audio source: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now.
    2. Audio HAL module: updated to TI's latest source to help with #1 and future support for USB audio, etc.
    3. Lights HAL module: removed conflicting battery light operations. The kernel manages the battery light entirely. The OS should almost never do anything with it.
    4. (NEW to JB) Power HAL module: used by the OS for temporarily kicking up the CPU during certain events (using the interactive governor) -- this makes the system more responsive. This feature is also still under development over time and I'll continue to update it.
    5. HW acceleration / graphics buffer system: Completely updated sources from TI for the hwcomposer, libion and other graphics / buffer systems
    6. Along w/ #5 I was able to roll up to the latest PowerVR driver 1.9@2130229 (up from 1.8@945322 in the last build). I noted right off the bat
    less GL issues and smoother game play.

    I may take a night or 2 and continue to play with the MIC settings to see if we can get it working, and that would be the delay in this release (if any).

    But, in general, the build for the Kindle Fire is a getting a lot cleaner (IMHO). And that's always a good thing.


    Still working on:

    - Memory management: I'm still not happy with how the OS is unloading certain processes at times (acore?!), and I'll be working with some of the ROM devs to setup better memory management in this main sources at GitHub. No reason why every dev should need to work that stuff out.
    - MIC function. Getting close, but I need to probably spend 2-3 more nights following audio routes and watching the OS setup the Audio input devices when the headset is plugged in.
    - Charger function. This is the big kahuna. Been a while since I worked on it, probably time to jump back into it.