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

Search This thread

scidon37

Senior Member
Feb 20, 2011
304
134
- Boot animation starts at random points. Sometimes at the very beginning, sometimes after the Cyanogenmod circular arrow has already "exploded." (I hope you know what I mean).

I've noticed this too, but it was actually the backlight not turning on until the animation has already started. I could see the animation VERY faintly until the backlight comes on.

Sent from my SGH-I777 using Tapatalk 2
 

Felnarion

Senior Member
Mar 23, 2011
351
168
Everything is going extremely smoothly, with the exception of the bugs you mentioned in the OP.

A few things I've noticed:

- Boot animation starts at random points. Sometimes at the very beginning, sometimes after the Cyanogenmod circular arrow has already "exploded." (I hope you know what I mean).

- DPI problems still seem to persist. I've noticed that many apps, including Chrome, will switch to the phone interface rather than using their tablet versions. This is also true for Firefox.

That's because of the DPI they've set by default.

Personally, I use a DPI of 120, which you can change by using the DPI settings utilities in the market. You'll get tablet versions of everything then.
 

djkeller3

Senior Member
Jan 15, 2011
628
195
Lexington, KY
That's because of the DPI they've set by default.

Personally, I use a DPI of 120, which you can change by using the DPI settings utilities in the market. You'll get tablet versions of everything then.

Wow. One of the best pieces of advice I've taken in a while. This made EVERYTHING look better!

Sent from my Kindle Fire using XDA Premium
ROM: CM9 Reloaded, 3.22.2012 Build
Kernel: 0xD34D
Overclock: 1.2 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX
 
  • Like
Reactions: rsnoonan

mlpmail

Senior Member
Dec 7, 2005
60
29
Hopefully this helps, but I've noticed that upon flashing hashcode's ROM with CWM, that after the bootloop, when I eventually go back into CWM, the kernel version never changes from 2.6.35.7 (I think that's it, I don't have my device in front of me).

I'd imagine this would show differently if the new kernel version actually took.

The version won't change in CWM because it always loads its Kernel, which is not getting changed. The only time you will see the new Kernel is when the new ROM is running.
 

backspacepc

Senior Member
May 25, 2008
276
36
Denham Springs
Are you sure that only the boot.img was corrupted in the flash attempt? If it's only that, maybe there's something wrong with the updater binary packaged with the zip? :confused:

That'll be one issue I'll be looking into. The rom seems to flash correctly, but you very well could be right.





I wonder if CWRecovery has never flashed kernels correctly.

I mean how would you really tell unless you were doing specific testing?

I've flashed several with CWM, and far as I can tell, it does in fact foul up every so often. Especially if you don't wipe properly, even then traces of the old software gets left behind from time to time. Currently I'm looking into the boot loop issue in TWRP to see if there's something we can do. That way we'll have at least one solid recovery.

Sent from my MB860 using XDA
 

boomn

Senior Member
Feb 2, 2011
275
83
That's because of the DPI they've set by default.

Personally, I use a DPI of 120, which you can change by using the DPI settings utilities in the market. You'll get tablet versions of everything then.

It might not just be DPI. CM9 for the Nook Color had a similar issue for a long time where even with the correct DPI for that screen size and resolution the GPU driver was reporting an incorrect screen size that was smaller than 7". The fix for now was to step back to an older version of that binary driver that reported screen size correctly. I'm not familiar enough with this KF development to know if that might be the case here or not.
 

Sblood86

Inactive Recognized Developer
Apr 18, 2011
415
407
Middle of nowhere, Texas
I've flashed kernels on my cellphone via CWM based recovery of the same version for different variations on testing and never really had any issues with it. Obviously I'm no expert in particular when it comes to kernels but I'm interested in this issue when flashing from CWM as I don't really like the idea of the recovery in my source tree having issues lol.

I'm trying to catch up on the current forum topics but I only have partial internet access atm (my house got struck by lightning); as of yet I haven't really been able to look into the issue yet but I'm requesting those who have to collect that information for me to that effect I opened an issue on my cwm repo, please add all appropriate information there.
 
  • Like
Reactions: vbdss and smirkis

lovejoy777

Inactive Recognized Developer
Dec 30, 2011
3,725
4,541
Nottingham
That'll be one issue I'll be looking into. The rom seems to flash correctly, but you very well could be right.







I've flashed several with CWM, and far as I can tell, it does in fact foul up every so often. Especially if you don't wipe properly, even then traces of the old software gets left behind from time to time. Currently I'm looking into the boot loop issue in TWRP to see if there's something we can do. That way we'll have at least one solid recovery.

Sent from my MB860 using XDA

I've been using cwm for a while and have had issues,
1/ if you use it with the dual boot bootloader cm9 roms have a black pixel flashing on all screens always at the same place?(not with twrp)
2/unmounted sdcard a few times (resulting in a soft brick only way out was to fast boot flash twrp.(not with twrp)
3/ wouldn't install any of your 3k roms (always got stuck in boot animation with back light off.
ReInstalled twrp 2.0 your from flashed and booted 1st time

In a nutshell IMO use twrp:)

Could cwm be getting partitions screwed up in some way and if so would this be a cause to any of the install problems?

Sent from my Amazon Kindle Fire using xda premium
 

leswgnr

Senior Member
Feb 3, 2012
181
45
New York
Looks good

Hashcode - don't want to clutter the thread with me toos-but just flashed the #2 rom with twrp 2.0 and no probs other than those already noted-retina burn :eek: and having to reboot to get wifi after the initial boot, power off-no boot problems, no screen display issues. Will keep testing and will report any new issues.

Updated-Google market, titanium backup and selected apps work fine. Chrome also--

Sorry, should have posed this in the General thread - feel free to delete. Will be more careful.
 
Last edited:

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
TEST BUILD #3 IS READY HERE: http://bit.ly/IShcSq

There are 2 changes for this build:
- HW Codecs are now working.
- Kernel included in this build is running "silicon type performance" mode. Meaning it's a stock overclock to 1.2 Ghz. Please test this as well.

If you have ANY issues with the 1.2 Ghz speed and want to step back down to 1.0 Ghz do the following:
- Enter "Settings"
- Choose "Performance" (at the bottom)
- Click "Ok"
- Select "Processor" (the first item on the right)
- Choose "Maximum CPU frequency"
- Set this to 1008
- Then check the "Set on boot" option
 
Last edited:

UrticantOwl

Senior Member
Jan 20, 2012
59
34
- Kernel included in this build is running "silicon type performance" mode. Meaning it's a stock overclock to 1.2 Ghz. Please test this as well.

It flashed well in TWRP 2.0, and seems to be running well, and the charger appears to be working... (I think...) The battery chart is sloping upward, which isn't something that I got to work for me on the last build.

And the extra 200Mhz hasn't destroyed the device yet. :D I know this has been addressed somewhat before, but is there any significant risk to running an OC'd ROM on the KF? I'll play around on N64oid to see if 20 minutes of Zelda:OOT will cause any heat issues on 1.2Ghz :)
Naturally, the device does seem a *bit* warmer than usual at this point...

Wifi is still being stubborn when you turn it on and off and on again, but I don't think much changed there in this release.
 

acax456

Senior Member
Feb 4, 2011
1,390
261
Hồ Chí Minh
TEST BUILD #3 IS READY HERE: http://bit.ly/IShcSq

There are 2 changes for this build:
- HW Codecs are now working.
- Kernel included in this build is running "silicon type performance" mode. Meaning it's a stock overclock to 1.2 Ghz. Please test this as well.

If you have ANY issues with the 1.2 Ghz speed and want to step back down to 1.0 Ghz do the following:
- Enter "Settings"
- Choose "Performance" (at the bottom)
- Click "Ok"
- Select "Processor" (the first item on the right)
- Choose "Maximum CPU frequency"
- Set this to 1008
- Then check the "Set on boot" option

So h/wa is working now??

Sent from my Kindle Fire using xda premium
 

animefun135

Senior Member
Nov 28, 2011
156
14
yes HW Decoder working like a charm... even on mkv files!!!

Hashcode you're amazing...

also we have problems with usb mass storage, wifi and led indicator.
 
Last edited:

Stevethegreat

Senior Member
Nov 28, 2010
1,199
327
One question if I may: Are the slow USB transfer speeds accounted as a bug?
I'm asking because I haven't found a mention on the OP.

CM7 manages 2MB/s, but the read speeds are 10 times that; IIRC the latest Amazon firmware kind of addresses this issue but not by much (we get 6MB/s write speed).
 

simonbove

Senior Member
Mar 14, 2011
72
14
Svendborg
Hwa works perfect here...
Only have the bugs you mentioned..

Great work hash and others...

Sendt fra min Amazon Kindle Fire med Tapatalk2
 

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.