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

Search This thread

Airbag888

Senior Member
May 5, 2010
326
63
Where do u change it in? Root explorer?

Sent from my HTC Evo 4G using xda premium

if you got a keyboard like swiftkey you can use vi itself.

open a console on the kindle with Connectbot (for example)

#su
#vi /system/build.prop
--use the arrow keys to get to the proper char
--hit A
--type in Amazon space making sure it reads Amazon Kindle Fire
--touch the screen then touch on screen Esc button
type :w
then :q

and you're done
 
  • Like
Reactions: Jaimemex

nathris

Senior Member
Aug 18, 2010
63
28
Victoria
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.


I think its charging, just not at full power. I had mine plugged in to USB and was watching Netflix. After 1 hour the battery only dropped 2%. I unplugged it and continued watching and it dropped another 15% after about 40 minutes.
 

moriz1

Senior Member
Dec 4, 2011
187
8
Keep in mind that the stock kindle fire can barely be charged by a computer's USB port. This is because the computer's USB port can only manage .5A. This is why the fire ships with a charger that does 1.7A.
 
  • Like
Reactions: tipzilla

TechIsCool

Member
Jan 4, 2011
11
2
The reason the name was is changed was my fault I guess it was showing up in the amazon play store as amazon amazon kindle fire vs just amazon kindle fire and we both thought that it was because Hash had typed to name wrong so he changed to what you guys see now. It will get updated.

ON7yE.png
 
Last edited:

southbird

Senior Member
Feb 12, 2010
249
100
You're right; happens in Google's store too (see attachment.) Guess we'll have to take a silly looking name for the sake of compatibility.
 

Attachments

  • aakf.png
    aakf.png
    4.1 KB · Views: 993

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
The reason the name was is changed was my fault I guess it was showing up in the amazon play store as amazon amazon kindle fire vs just amazon kindle fire and we both thought that it was because Hash had typed to name wrong so he changed to what you guys see now. It will get updated.

ON7yE.png

I reverted the name change on github and fixed the 04-22 ROM build which was broken here:
http://rombot.droidhive.com/ROMs/otter/cm9


Sent from my XT894 using XDA
 
Last edited:

ma.da.ladla

Senior Member
Apr 13, 2012
92
4
heat issue didn't subside

Sent From my Kindle Fire
Setup:Details are Below
Cm7 Barebones+Raven's Kernel
Minimum:300 Higher 1200mhz
Go launcher Ex With MIUI Theme
Games:MC3,Fifa 2012,Real Racing 2,Stick Cricket,Gangster Rio....
Apps:Mx Video Player,JetVid,Titanium Backup,Opera Mobile,Dolphin HD,Adobe Reader
 
Last edited:

Jaimemex

Senior Member
Jan 11, 2010
407
55
heat issue didn't subside

Sent From my Kindle Fire
Setup:Details are Below
Cm7 Barebones+Raven's Kernel
Minimum:300 Higher 1200mhz
Go launcher Ex With MIUI Theme
Games:MC3,Fifa 2012,Real Racing 2,Stick Cricket,Gangster Rio....
Apps:Mx Video Player,JetVid,Titanium Backup,Opera Mobile,Dolphin HD,Adobe Reader

Same here the lower back of my kindle over heats pretty bad on wifi...

Sent from my HTC Evo 4G using xda premium
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
You should have made a version change, even for this small fix: 4-22a or something like that.

It would be clearer. BTW, thanks for your kernel, I do really enjoy my KF.

I completely agree in theory.

The reality is that that some of the links are posted around the internet and people will continue to download the wrong ROM (not knowing there's an update).

So in this case, I tend to over-write the offending file.
 

AlexDeGruven

Senior Member
Mar 24, 2008
685
213
Ann Arbor
www.structuredthought.org
Been thinking about touch sensitivity quite a bit today as I've been demoing AOKP 33r2 and 34 to coworkers (who are still too chicken to do this to their Fires).

I've noticed that touching works perfectly if you just barely make contact with the screen, rather than the normal 'push' action that we're used to with touch screens. A quick tap also seems to have the same effect.

I get the most errant scrolling when I try and push like there's an actual button there.

This leads me to believe that one of two things might be going on:

1. The polling interval for the digitizer might be set too fast, and is reading a push multiple times (initial contact, then the wider contact patch of a full-on press).
2. The software that determines whether a touch action is a touch or slide is tuned too sensitive and is reading the wider contact patch as a movement.

These could also be the same thing, just two sides of the same symptom.
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
Been thinking about touch sensitivity quite a bit today as I've been demoing AOKP 33r2 and 34 to coworkers (who are still too chicken to do this to their Fires).

I've noticed that touching works perfectly if you just barely make contact with the screen, rather than the normal 'push' action that we're used to with touch screens. A quick tap also seems to have the same effect.

I get the most errant scrolling when I try and push like there's an actual button there.

This leads me to believe that one of two things might be going on:

1. The polling interval for the digitizer might be set too fast, and is reading a push multiple times (initial contact, then the wider contact patch of a full-on press).
2. The software that determines whether a touch action is a touch or slide is tuned too sensitive and is reading the wider contact patch as a movement.

These could also be the same thing, just two sides of the same symptom.

I have source for a linux mainline v3.3 Ilitek Touchscreen driver and as soon as things slow down I'm probably going to implement it for 2 reasons:
- The code is more generic and easier to upgrade for the future
- It's an ICS compatible touchscreen driver (where the current is more Gingerbread compatible and we use additional settings to make it work)

Once that's in-place I can work with a group of testers to craft the "perfect" settings for our device. Going to be a bit tho. :/
 

ma.da.ladla

Senior Member
Apr 13, 2012
92
4
i second that

Sent From my Kindle Fire
Setup:Details are Below
Cm7 Barebones+Raven's Kernel
Minimum:300 Higher 1200mhz
Go launcher Ex With MIUI Theme
Games:MC3,Fifa 2012,Real Racing 2,Stick Cricket,Gangster Rio....
Apps:Mx Video Player,JetVid,Titanium Backup,Opera Mobile,Dolphin HD,Adobe Reader
 

dnathan13

Senior Member
Sep 17, 2010
828
221
Hash if you are going to work on the driver, you will implement the multitouch too?

Last I heard it had been decided the kindle couldn't do more than two touches due to hardware issues so I don't think the drive will help. Feel free to correct me if I am wrong

Sent from my Kindle Fire using xda premium
 

southbird

Senior Member
Feb 12, 2010
249
100
Last I heard it had been decided the kindle couldn't do more than two touches due to hardware issues so I don't think the drive will help. Feel free to correct me if I am wrong

The difference is between a "driver" and "firmware" -- the touchscreen hardware has firmware which only supplies a two-point touch. The "driver" is merely what interfaces the hardware with the operating system. The driver might interact with the hardware better, but it will not alter its core capability as a new firmware would. AFAIK we don't have access to the touchscreen firmware so at this point it's a solid "no" going forward.
 

EVOlvedAndroid

Senior Member
Oct 27, 2010
533
472
Los Angeles
My kindle is dead and whenever I try to charge it, It boots to bootloader for a second shuts off and repeats over and over and over. If you can help PLEASE REPLY.

Using this kernel with AOKP
 

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.