[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]
- Thread starter Hashcode
- Start date
Yeah, just noticed when synching my repo...JB source is out.
Envoyé depuis mon GT-I9000 avec Tapatalk
https://plus.google.com/117962666888533781522/posts/aRVWBbuWQar
Good news.
Envoyé depuis mon GT-I9000 avec Tapatalk
Good news
.Envoyé depuis mon GT-I9000 avec Tapatalk
A
AndroidSlave
Guest
Has nothing to do with whether it's on ICS or JB.
Sent from my Amazon Kindle Fire using Tapatalk 2
I think he knows that, what he meant was coolbeans jellybean source is out, but he would be content with just his charging working properly. btw why is any of this posted in the dev thread? xP
I assumed he was saying charging needs to be fixed on ICS first. I wasn't being a jerk
Sent from my Amazon Kindle Fire using Tapatalk 2
I'll be making sure that the device compiles and operates correctly under Jelly Bean tonight.
The charger is a WIP as always.
The charger is a WIP as always.
I'll be making sure that the device compiles and operates correctly under Jelly Bean tonight.
The charger is a WIP as always.
AHMAGERD!
Sent from my Amazon Kindle Fire using Tapatalk 2
Hey hash,I'll be making sure that the device compiles and operates correctly under Jelly Bean tonight.
The charger is a WIP as always.
Just finished downloading the source .... and I would love to start playing around with a build.
However, my build/compile experience is pretty much limited to CM ... but I guess the readme of the kfire/android_local_manifest aosp branch is a good start.
If there's anything else I need to be aware of please let me know.
Thx
I'll be making sure that the device compiles and operates correctly under Jelly Bean tonight.
The charger is a WIP as always.
If jellybean arrives on the kindle fire before the Nexus 7 my wife ordered does somebody is getting another donation ;-)
First everyone please type correctly. Second this kernel should not be used as a daily driver. It is a WIP! Bug reporting is great. But don't chastise faulty behavior from a WIP! Expect many bugs, I mean like a lot of bugs .that is the point of these guys beta testing you know? Flash the new kernel, check for bugs , report , and then flash back to the old kernel until the proprietor fixes the issues for a final release. That is it. The only reason developers release software into the wild is for the public to test for bugs on devices and then to report back with bug reports. Please stop the nonsense.
P.S: this was only for those impatient, non-supporting freeloading sacks that love to criticise great progress.
Sent from my CM9 Kindle fire using Tapatalk 2. Don't be shy and hit thanks
Last edited:
Of course this kernel can be used as a daily driver - and it is by many, either running this or another rom based on hashcode's work.First everyone please type correctly. Second this kernel should not be used as a daily driver. It is a WIP! Bug reporting is great. But don't chastise faulty behavior from a WIP! Expect many bugs, I mean like a lot of bugs .that is the point of these guys beta testing you know? Flash the new kernel, check for bugs , report , and then flash back to the old kernel until the proprietor fixes the issues for a final release. That is it. The only reason developers release software into the wild is for the public to test for bugs on devices and then to report back with bug reports. Please stop the nonsense.
P.S: this was only for those impatient, non-supporting freeloading sacks that love to criticise great progress.
Sent from my CM9 Kindle fire using Tapatalk 2. Don't be shy and hit thanks
Everyone needs to type correctly? Really?!?First everyone please type correctly. Second this kernel should not be used as a daily driver. It is a WIP! Bug reporting is great. But don't chastise faulty behavior from a WIP! Expect many bugs, I mean like a lot of bugs .that is the point of these guys beta testing you know? Flash the new kernel, check for bugs , report , and then flash back to the old kernel until the proprietor fixes the issues for a final release. That is it. The only reason developers release software into the wild is for the public to test for bugs on devices and then to report back with bug reports. Please stop the nonsense.
P.S: this was only for those impatient, non-supporting freeloading sacks that love to criticise great progress.
Sent from my CM9 Kindle fire using Tapatalk 2. Don't be shy and hit thanks
I'll be making sure that the device compiles and operates correctly under Jelly Bean tonight.
The charger is a WIP as always.
we/he knows.
Sent from my MyTouch 4G using xda premium
Update:
I've created new device/vendor branches for Jelly Bean (jb)
And, right now I'm working from this setup:
https://github.com/KFire-Android/android_local_manifest
It's not quite there yet. But it's getting there.
I've created new device/vendor branches for Jelly Bean (jb)
And, right now I'm working from this setup:
https://github.com/KFire-Android/android_local_manifest
It's not quite there yet. But it's getting there.
Troubleshooting a kernel hard reset during init. Seems like it's a chmod 666 on /dev/dce.. odd that this all worked in ICS.
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.
