[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]
- Thread starter Hashcode
- Start date
I can't test it since I live in Denmark, but it should do, so far everything have worked.. Flash in browser, video player, YouTube hd, television via flash and all games...
So netflix should work, but there are still other bugs, and it's not a daily kernel yet...
Sendt fra min Amazon Kindle Fire med Tapatalk2
There really isn't much risk in overclocking. I don't know how the voltage is set up on the fire, but most likely it runs at the same voltage on 1009 and 1200 MHz. Some processors handle it better than others. Worst case scenario your fire will reboot when pushing it too hard
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Sent from my Kindle Fire using Tapatalk 2 Beta-5
And the extra 200Mhz hasn't destroyed the device yet.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
Finally another N64oid player. I'm getting my KF next week, and I wanted to know if you could use N64oid on other ICS roms. I'm not sure if it needs HWA.
Sent from my myTouch_4G_Slide using Tapatalk
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
That's just a few issues ive noticed, currently looking at how the recovery was built, next step is going to be putting a few modded files into it specific to our fires.
I love auto correct!!!
Sent from my MB860 using XDA
I'd like to repeat:
PLEASE BE AWARE OF THE CURRENT BATTERY DRAIN ISSUES WITH THIS KERNEL. IT DOES NOT DEEP SLEEP WHILE THE DEVICE IS NOT IN USE.
So best to power it off when not in use (long press the power button after the OS has shutdown for about 20 seconds to completely turn the device off)
Also, I'm merging the code back into the "ics" branch of the KFire-Android github here:
https://github.com/organizations/KFire-Android
So please double check your local_manifest.xml files and your device/amazon/otter branch if you have a custom build going.
PLEASE BE AWARE OF THE CURRENT BATTERY DRAIN ISSUES WITH THIS KERNEL. IT DOES NOT DEEP SLEEP WHILE THE DEVICE IS NOT IN USE.
So best to power it off when not in use (long press the power button after the OS has shutdown for about 20 seconds to completely turn the device off)
Also, I'm merging the code back into the "ics" branch of the KFire-Android github here:
https://github.com/organizations/KFire-Android
So please double check your local_manifest.xml files and your device/amazon/otter branch if you have a custom build going.
I haven't really gotten around to the USB tuning yet. :/ In general we have many issues right now with USB:
- Not showing charge correctly in OS
- MTP / mass storage not working
- Speed tests, etc all in progress
- Possibly looking to add drivers for bluetooth adapters, etc once the kernel is stable.
I understand well that the kernel is rather in alpha stage and in fact the progress made thus far is commendable, but I can't help and remark "Wow, bluetooth adapter support! Giving us back what Amazon so cruelly
p) prevented us from having"...When complete this Kernel can seriously transform what the Fire is supposed to be and what is capable of
... not bad for a $200 piece of hardware. Keep up the good work
"Wow, bluetooth adapter support! Giving us back what Amazon so cruelly
Actually I thought it was pretty much electrically proven that, despite earlier assumptions, there is no built-in Bluetooth capability? (Unless something else was found since I last looked this up.) The chip in use in the KF does not actually have an embedded Bluetooth component. (See here, post #23 and onward) So, assuming that's correct, Amazon didn't cruelly keep us from having Bluetooth. It was never there in the first place.
I'm guessing Hash meant possibly having Bluetooth USB adapters??
Yeah that's what I meant as well (hence the smiley), sarcasm doesn't translate well over the net. Anyhow this is a development thread so I'll make sure to keep my posts out.
Again thanks for your great work.
I'll post this in both threads but:
TO ENABLE MASS STORAGE GO TO:
"Settings -> Storage" and then click on the 3 dot "menu" icon in the upper right.
Choose the only option "USB computer connection"
Checkmark "Mass Storage"
I'll get that set as a default in the next build.
TO ENABLE MASS STORAGE GO TO:
"Settings -> Storage" and then click on the 3 dot "menu" icon in the upper right.
Choose the only option "USB computer connection"
Checkmark "Mass Storage"
I'll get that set as a default in the next build.
nice work hash. question, do u think the cwm flashing issue could be due to it being the gb branch?
Sent from my HTC Glacier using xda premium
Sent from my HTC Glacier using xda premium
Saw that a lil too late and thought my dog gone computer was cranking out uselessness. Thanks hash, still digging into CWM to see if I can come up with a viable solution. I've confirmed that its not the unzip binaries, it is in fact an issue with CWM.
Sent from my MB860 using XDA
No. I have phones which use the GB branch for CW Recovery and flash ICS-based ROMs.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
434STEP 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-21150UPDATED 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 otter44[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.42New 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.
