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

Search This thread
By:
Advanced…
Hashcode

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
gruuvin said:
There has been a bit of wondering if it would be possible at the kernel level to fix an issue that has stood in the way for some apps to access the mic input. One speculation is that full duplex audio is not enabled with the stock kindle kernel/audio driver. This was speculated because of possible evidence that only applications that would not simultaneously stream audio output will enable audio input stream (mic). Voice recorder and Grooveshark accept an input stream while Skype, Groove IP w/Google Voice do not.

Here is a thread discussing it a bit: http://xdaforums.com/showthread.php?t=1652311

Groove IP with Google Voice and synced Google Contacts makes for a really nice "phone" on the Kindle Fire. With a mic/headphone combo plugged in, you can call up anybody in your contact list, and you can hear them, but sadly they can not hear you :( Man it would be awesome if this could be fixed in the kernel!!

I did a quick search on audio full-duplex support for android and found a TI-Android-ICS-PortingGuide wiki (http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide) that mentioned in the "Audio" section support for simultaneous playback and record (full-duplex mode) for an AM335xevm that uses AIC31 audio codec. I believe our kindles use the AIC3110 audio chip, so maybe this is good news.
http://processors.wiki.ti.com/index.php/UserGuideAudioDriver_PSP_04.02.00.07
http://processors.wiki.ti.com/index.php/AM335x_Audio_Driver's_Guide
Click to expand...
Click to collapse

Thank you! I'll bookmark this post and read through the info as soon as the charger driver is in better shape. This is next on "the list"(tm).

Sent from my Amazon Kindle Fire using Tapatalk 2
 
  • Like
Reactions: Jaimemex, Simon.Otst, shravbits and 13 others
T

Techlyfe

Senior Member
Aug 20, 2011
327
124
Jersey City, NJ
T-Mobile Samsung Galaxy Note 8
AluminumHaste said:
The 3 dot icon is not there but thanks for trying anyways.
Click to expand...
Click to collapse

I believe the three dots will only be there if there is a valid usb connection, that happened with my wifes kindle when she was at work complaining about not being able to hook it to her pc. She swore the three dots were not there. And then she realized, the kindle wasn't even hooked up to the pc, it was connected to the OEM charger... Check the Cable, then, check the drivers.
 
lovejoy777

lovejoy777

Inactive Recognized Developer
Dec 30, 2011
3,725
4,541
Nottingham
the three dots were not on any aokp rom when I last tried them, only cm9 roms seem to have the dots.

Sent from my Amazon Kindle Fire using xda premium
 
S

sthomas38

Senior Member
Feb 9, 2012
695
524
I've built a fully vanilla kang today including the latest source changes. If Hash allows me to, I can post it here :).
 
S

southbird

Senior Member
Feb 12, 2010
249
100
Trojan38 said:
I've built a fully vanilla kang today including the latest source changes. If Hash allows me to, I can post it here :).
Click to expand...
Click to collapse

Wouldn't put it -HERE- since this is the dev thead for the KERNEL ... would it make more sense to have a Kang / 3.0 thread? At the very least, probably the user alternate thread.
 
S

sthomas38

Senior Member
Feb 9, 2012
695
524
Yes you're right but this is also a ROM thread :D...

But okay, I'll create a thread.
 
Last edited:
A

AluminumHaste

Senior Member
Sep 4, 2011
167
21
Techlyfe said:
I believe the three dots will only be there if there is a valid usb connection, that happened with my wifes kindle when she was at work complaining about not being able to hook it to her pc. She swore the three dots were not there. And then she realized, the kindle wasn't even hooked up to the pc, it was connected to the OEM charger... Check the Cable, then, check the drivers.
Click to expand...
Click to collapse

Nope still not there, tried on 2 kindles. However, both these kindles are running ReloadedROM latest + 3.0 kernel 10a
 
Y

YaKillaCJ

Senior Member
Jul 16, 2010
249
97
Miami
Thanx Hashcode. Kernel is great. Few more things left will makes our device a example of what Ice Cream Sandwhich should be. After the charging issue. I believe tackling the audio is kool.
Not that its my place but I request that the audio driver itself gets fixed b4 the Voip. I mean as U described yourself, the audio drivers are janky. DSP manager doesnt work and thats my only pet peave messing with my ICS experience.
 
A

AlexDeGruven

Senior Member
Mar 24, 2008
685
213
Ann Arbor
www.structuredthought.org
AluminumHaste said:
Nope still not there, tried on 2 kindles. However, both these kindles are running ReloadedROM latest + 3.0 kernel 10a
Click to expand...
Click to collapse

The dots are the menu trigger. This is not kernel level stuff, so any behavior like this on a ROM other than that posted in this thread is irrelevant .

If the menus are not available, take it up with the appropriate ROM thread.

Sent from my Amazon Kindle Fire using Tapatalk 2
 
  • Like
Reactions: powerpoint45, AluminumHaste, lovejoy777 and 1 other person
A

AluminumHaste

Senior Member
Sep 4, 2011
167
21
Strange, the discussion had led me to believe that USB connectivity wasn't working because of this kernel, not because of the rom, but I see what you are saying, the 3 dots should be there because that's part of the ROM.
 
K

kernelsandirs

Senior Member
Aug 21, 2008
57
12
Los Angeles
Battery Life - Governors?

So what is the best governor to use to get good battery life, I seem to get fairly less battery life once I flipped the switch and moved to to the AOKP with kernel 3.0 #10a.

Battery life is not horrific or anything but just wondering how others are best managing their battery, with governors etc?

I am at 1008Mhz and "On Demand"
 
Nightly Suicide

Nightly Suicide

Senior Member
Feb 28, 2012
59
12
Arizona
ONDEMAND

Min 300 MHz
Max 1200 MHz

I have pretty good battery life. Even the deep sleep does well. I use Apex Lanucher so I don't really need a high min.
 
K

koroshbhasabrain

Member
Dec 2, 2011
30
3
San Diego
Random Bug Rant....

Hey guys! Hash, with your newest ROM and kernel, I noticed these bugs (these are probably known by now...

1: Random reboot (obviously)
2: Sometimes everything goes extremely jerky and nothing responds
3: The "Battery" tab in the settings shows 'Charging' when it's plugged in, but the battery icon shows nothing (also well known)

I'm happy to lend a hand in any way, just tell me what I should do.

PS: I might sound like a total noob, but what do the governor settings mean and do in the overclock tab? Thanks!!
 
Nightly Suicide

Nightly Suicide

Senior Member
Feb 28, 2012
59
12
Arizona
koroshbhasabrain said:
Hey guys! Hash, with your newest ROM and kernel, I noticed these bugs (these are probably known by now...

1: Random reboot (obviously)
2: Sometimes everything goes extremely jerky and nothing responds
3: The "Battery" tab in the settings shows 'Charging' when it's plugged in, but the battery icon shows nothing (also well known)

I'm happy to lend a hand in any way, just tell me what I should do.

PS: I might sound like a total noob, but what do the governor settings mean and do in the overclock tab? Thanks!!
Click to expand...
Click to collapse

1 & 2 has never happen to me with gedeROM. 3 is fine, just minor GUI stuff...

Sent from my Kindle Fire using xda premium
 
P

phufford

Member
Apr 19, 2012
25
11
koroshbhasabrain said:
Hey guys! Hash, with your newest ROM and kernel, I noticed these bugs (these are probably known by now...

1: Random reboot (obviously)
2: Sometimes everything goes extremely jerky and nothing responds
3: The "Battery" tab in the settings shows 'Charging' when it's plugged in, but the battery icon shows nothing (also well known)

I'm happy to lend a hand in any way, just tell me what I should do.

PS: I might sound like a total noob, but what do the governor settings mean and do in the overclock tab? Thanks!!
Click to expand...
Click to collapse

I've had no reboots ever. I've run into particular programs that are jerky and slow, but usually it's because they're misbehaving (Facebook, looking at you). The battery thing is well known and top of the fixes list.
 
A

ammubarak

Senior Member
Dec 31, 2011
156
32
Safwa, Saudi Arabia
koroshbhasabrain said:
Hey guys! Hash, with your newest ROM and kernel, I noticed these bugs (these are probably known by now...

1: Random reboot (obviously)
2: Sometimes everything goes extremely jerky and nothing responds
3: The "Battery" tab in the settings shows 'Charging' when it's plugged in, but the battery icon shows nothing (also well known)

I'm happy to lend a hand in any way, just tell me what I should do.

PS: I might sound like a total noob, but what do the governor settings mean and do in the overclock tab? Thanks!!
Click to expand...
Click to collapse

I have been using the latest Hahcode's CM9 four the last ten days with no random reboot or a lack of response due to either kernel or ROM.

To optimize the autonomy of the battery, I have changed the screen brightness to approximately 33% and configured the CPU performance to 800 MHz and 1008 MHz on demand.

Sent from my Amazon Kindle Fire using Tapatalk 2
 
lovejoy777

lovejoy777

Inactive Recognized Developer
Dec 30, 2011
3,725
4,541
Nottingham
no reboots or lag here either. did you do a clean install or did you restore old data etc?
iv'e been running hashes full setup for a couple of weeks and it has been silky smooth.:)

edit. if im not mistaken, lowering the screen brightness doesn't help battery as the back light is on or off, i think the back light is dimmed by a layer, not by dropping the brightness of the back light. (in other words altering the brightness still means that the back light is on full).
if this info is incorrect please post amendments.

thanks
steve
Sent from my Amazon Kindle Fire using xda premium
 
Last edited:
You must log in or register to reply here.

Similar threads

V
  • Locked
[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only]
Replies
2K
Views
2M
Moscow Desire
Moscow Desire
twa_priv
[ROM] CM10/SGT7 for the Kindle Fire [20130117]
Replies
4K
Views
1M
sd_shadow
sd_shadow
twa_priv
[ROM] [JB 4.2.2] CM10.1/SGT7 for the Kindle Fire [20130724]
Replies
2K
Views
632K
t3chwizard
t3chwizard
Hashcode
[ROM-AOSP] [OLD] Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10]
Replies
887
Views
646K
S
spartan77
whistlestop
CM7 for Kindle Fire (aka standing on the shoulders Giants)
Replies
1K
Views
507K
S
Stevethegreat

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 434
    Hashcode
    Hashcode
    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
    View
    150
    Hashcode
    Hashcode
    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
    View
    44
    Hashcode
    Hashcode
    [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.
    View
    42
    Hashcode
    Hashcode
    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
    View
    42
    Hashcode
    Hashcode
    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.
    View

New posts