[ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [08/12 ICON DRAG FIX]

Search This thread
By:
Advanced…
Androidaholic

Androidaholic

Senior Member
Oct 16, 2010
86
34
Houston,Tx.
Thank You !

I wanted to say how much I appreciate you working on this Hashcode. I do not know you but what I do know is that I have the Kindle Fire HD 8.9 and it is a marvelous device that needs a full blown Android OS on it. I have 2- 7" tablets a 10" and this 8.9" Fire and I like the Fires size the best. Anyway looking forward to any progression of this project and to show my appreciation I just sent a little something your way. As time goes on and things progress I will send some more. Thanks
 
ddem1

ddem1

Senior Member
Dec 25, 2010
69
31
tapebrain.com
:victory: You are a great man Hashcode :victory:

Actually I bought Kindle yesterday from a friend only because I saw this thread and that some development was happening. Great job.

It may lack some polish at this point but works great for basic stuff, especially since the Amazon UI was just horrible. Ebook reading apps like Moon+ work great out of the box for example.

Looking forward to future updates, I'll be sure to chime in with some donations! :good:
 
A

arda99

Senior Member
Jan 4, 2011
340
215
found a small bug:
lots of this msg on logcat:

E/OMAP PowerHAL( 309): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device


still there even after I changed CPU governor to conservative.

Edit:
set conservative on boot and reboot the tablet, the error msg is now gone.
 
Last edited:
T

Technogen

Senior Member
Jul 15, 2008
193
55
aaron.a said:
kfhd 8.9 =)

everything went fine. the twrp installed. i used it to create a backup then flashed cm10. after the flash i got nothing but the orange logo so i restored the system img from onemeila then reinstalled twrp from scratch and restored my back up lol

no idea why cm10 doesn't boot on my device.
Click to expand...
Click to collapse

I had the same issue, what I did was put the back up image I made back on, whole works. Then did ALL the steps over again including freedom, now I'm back to a working CM10.1. I had no way of pulling any logs off the system to see what was going on to figure out the issue itself though.
 
rootedkfirefan

rootedkfirefan

Member
Jan 25, 2013
19
3
Hashcode said:
Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***


BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://xdaforums.com/showthread.php?t=2128175


Download Information:
[02/02] ALPHA CM10.1 + 3.0.50+ KERNEL
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130201-UNOFFICIAL-jem.ziphttp://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130201-UNOFFICIAL-jem.zip
md5sum: 36a6ec8df79b6dedbe56692ee2f07391

Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jem/cm10.1/

Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)

Older builds are found here (under my "Jem" folder on goo.im):
http://goo.im/devs/Hashcode/jem/cm10.1/

PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)

Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.

CHANGES:

  • [02/01] First release

CURRENT KNOWN ISSUES:
  • AUDIO DOES NOT WORK. I'm still troubleshooting and working on a custom audio HAL (if needed)
  • I need to tweak the build.prop settings so that more apps are compatible.
  • Camera crashes at the moment
  • Bluetooth function turns on, but is largely untested.
  • Haven't touched HDMI yet
  • I don't have an LTE version so this is untested. Tho much of the RIL files are in place as well as APNs.

FEATURES:
  • [02/01] 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
  • [02/01] PowerVR Graphics Drivers: DDK 1.9@2166536 for Android (Jellybean compatible)
  • [02/01] Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
  • [02/01] Wifi
  • [02/01] Bluetooth pairing (no audio)
  • [02/01] Sensors
  • [02/01] HWAcceleration
  • [02/01] HD Codecs for YouTubeHD and Netflix


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 Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code: 
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
Click to expand...
Click to collapse

Hello Hashcode,

I am setting up the android kitchen. Lot's and lots of downloading. Anyway, is it required to download android's Master branch then the Cyanogen Mod or can you just download the Cyanogen Mod.

Thanks
 
T

Technogen

Senior Member
Jul 15, 2008
193
55
One thing I noticed is that when I hit the volume up button for the first time it pops up the warning asking me if I want to raise volume above the safe levels, even though it's at mute.
 
Born2BeMild

Born2BeMild

Senior Member
Mar 5, 2011
89
8
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]

Bringing down the notifications window and touching the time at the top crashes the UI if you have clock disabled.

Sent from my Amazon Kindle Fire HD
 
Last edited:
fungflex

fungflex

Senior Member
Oct 19, 2005
553
69
38
Denville, NJ
Hashcode said:
No need to download the AOSP branches, just CM.

Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse

Just wanted to see if any progress had been made with Audio. Honestly, this thing runs so flawlessly its a shame to even think about going back. I use it primarily for reading my digital comics right now but would love to add hulu / netflix to that.

Thanks!!!
 
gunnyman

gunnyman

Senior Member
Apr 12, 2010
7,998
2,668
Greenville SC
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]

Does otg work or has amazon decided to not provide power to the port?

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
 
twa_priv

twa_priv

Senior Member
Feb 10, 2011
1,701
4,472
You must log in or register to reply here.

Similar threads

Hashcode
[ROM-AOSP] OFFICIAL CM11.0 KFire HD 8.9 (KK 4.4.2) [05/20 AUDIO/CAMERA FIXES]
Replies
338
Views
142K
alexandero11
alexandero11
Hashcode
[ROM-AOSP] Unofficial CM10.2 (JB 4.3.1) [11/15 CM REFRESH]
Replies
122
Views
55K
arctophile
arctophile
transi1
[ROM][7.1][LineageOS(CM)14.1 and CM13][UnOfficial] (Nougat) [jem]
Replies
327
Views
106K
P
puqui
Hashcode
[LTE][ROM-AOSP] Unofficial CM10.2 (JB 4.3) [08/07 LTE TEST #3]
Replies
86
Views
36K
E
efxguy
Hashcode
  • Sticky
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 8.9 [06/24 CM12.1/TWRP 2.8.x]
Replies
479
Views
255K
skdubg
skdubg

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 107
    Hashcode
    Hashcode
    Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9

    *** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***


    BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
    http://xdaforums.com/showthread.php?t=2128175

    AUDIO: DO NOT ENABLE "LOCK SCREEN AUDIO" OR "TOUCH SOUNDS" IN SOUNDS MENU. THIS *CAN* BREAK AUDIO.

    CyanogenMod Changelog (DO NOT DOWNLOAD ANY .ZIP FILES -- FOR OFFICIAL DEVICES ONLY)
    http://changelog.bbqdroid.org/

    Download Information:
    [LATEST][08/12] BETA CM10.1 + 3.0.50+ KERNEL
    Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
    Mirror 2: d-h.st/xMG
    md5sum: 6a717e9b085909e6407cab486f585b54

    [07/26] BETA CM10.1 + 3.0.50+ KERNEL
    Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130726-UNOFFICIAL-jem.zip
    Mirror 2: d-h.st/4Uc
    md5sum: 41d6331a9492ddc2dd576c6cad71c8f5

    [07/17] ALPHA CM10.1 + 3.0.50+ KERNEL
    Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130717-UNOFFICIAL-jem.zip
    Mirror 2: http://d-h.st/XxG
    md5sum: 1a1204e8e74211213fd1414ebca80194

    [07/13] ALPHA CM10.1 + 3.0.50+ KERNEL
    http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130713-UNOFFICIAL-jem.zip
    md5sum: 5050e8c31851162a117d87d17a1b6806

    Older builds can be found in the same folder on goo.im:
    http://goo.im/devs/Hashcode/jem/cm10.1/

    Download Google Apps:
    Http://goo.im/gapps
    (For Android 4.2.1/CM 10.1 use the top row gapps)

    PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
    (It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)

    Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.

    CHANGES:
    • [08/12] Includes a Trebuchet patch to fix the screen flip-flop when trying to drag an icon in landscape (by XDA user Wickets^)
    • [08/12] Headphone volume raised (set to 114)
    • [07/26] Fixed occasional drawables issue with background / etc reverting to HDPI graphics
    • [07/26] More Dalvik VM changes
    • [07/17] Dolby: [WIP] Initial work for Dolby support in CM10.1 -- Still troubleshooting audio effect pre-gain handling
    • [07/17] Audio: Fixed MIC initialization -- works perfectly now, everytime.
    • [07/17] Camera: cleaned up DCC file handling for a bit more "Amazon"-like performance.
    • [07/13] USB Vendor ID / Product ID's have been reset to match the Amazon OS / TWRP values. Should help keep Windows drivers from going bonkers.
    • [07/13] Some Audio issues have been resolved. It shouldn't stop when swapping apps, etc. Still low volume currently where Dolby decoder is used.
    • [07/13] CM refreshed which includes several well-known security exploit patches
    • [07/13] PVR/SGX driver updated to 1.9@2291151 fixing several games and Google Earth
    • [07/13] Enabled "dirty region" rendering which helps 2d rendering quite a bit.
    • [07/13] Fixed a Bluetooth issue: stuck in TRANSITION mode till it's enabled/disabled after a reboot. This was causing extra battery drain.
    • [07/13] Some tweaks to Android vm allocations. Still needs work, but less apps are being killed off on the boot.
    • [06/04] CM refresh for changes (no device updates)
    • [05/14] New android OS audio driver. MIC works but may need to be stopped / re-started once (WIP)
    • [05/11] Camera should be working again
    • [05/08] Fixed orientation for HDMI output (requires a /data wipe) -- sound is W.I.P.
    • [05/08] Fixed default landscape orientation (was backwards)
    • [05/08] Fixed power HAL to retain current max CPU freq (original code by twa_priv, patched by Hashcode)
    • [05/07] Raised headphone volume by 10%
    • [04/20] [Thanks to Javabugs] Bluetooth firmware is now renamed correctly so that it loads and should work
    • [04/05] Basic audio function is now working. This means volume adjustable speaker output and headset output. NO input works yet -- still WIP.
    • [04/01] Basic camera function now working, tho after video recording is stopped, camera will FC during thumbnail creation. Video is recorded successfully tho. Panorama crashed out entirely still WIP.
    • [02/25] Updates to CM10.1 (4.2.2_r1)
    • [02/01] First release

    FEATURES:
    • 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
    • PowerVR Graphics Drivers: DDK 1.9@2291151 for Android (Jellybean compatible)
    • Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
    • Audio
    • Camera
    • Wifi
    • Bluetooth
    • Sensors
    • HWAcceleration
    • HD Codecs for YouTubeHD and Netflix
    • HDMI video out is now correct and work across several resolutions. YMMV


    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 Android projects by doing the following:
    (This manifest allows for building Kindle Fire 1st and 2nd gen as well)
    Code: 
    mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
    View
    37
    Hashcode
    Hashcode
    So, I'm not really happy with this current build.

    Is it more flexible than the Amazon OS? Yes, of course. But is it really "better"? No. Absolutely not.

    1. I see tons of IOWAIT for no real reason and it ends up as lag everywhere. It's not the device. It's something in the kernel which is causing it. End result: the device doesn't feel snappy at all. :/ You go to unlock the screen and it sits for a good second or 2. Open an app.. it sits for a second or 2, etc. I'm guessing that there's some driver in the kernel which is hard looping or something.
    2. I hate the current sensor setup. It's all proprietary Amazon files and the gyroscope is backwards causing more issues. To fix it, I need to be able to compile my own sources for the sensors. Which means using open source IIO-based Invensense drivers which I found in the Nexus 10 kernel. So thats: backport them to 3.0 kernel or move the entire device over to 3.4 kernel and use them there. Either way, new sensor driver for the kernel and then I can use the IIO-based Invensense sensor source from AOSP (with a little re-work).
    3. Sound issues are still pretty big at the moment. Background audio clocking issues, odd audio buffer setup or more audio android layer debugging are all needed. And it'll probably be a good week or 2 of more dedicated debugging on the audio system to really root out the "whys" and "hows" of our current audio issues.
    4. Power driver is lacking a ton of features in my opinion. It does exactly what it's supposed to and nothing else. It detects a power source and turns on charging. We're missing the entire OTG implementation.
    5. Camera quality is currently: terrible. I know it's a very cheesy camera built for video chat basically, but it can be better.

    How to solve these issues in the best way possible? Still mulling over my options. The 3.4 kernel I'm working on for the 1st gen Kindle Fire is nearly done. So that's a viable option. But, there's a huge amount of back tracking and device setup before it even gets back to the current state. And if we do move to the 3.4 kernel: the camera is instantly broken until I can completely re-write the driver using V4L2 interface in Android -- so that becomes additional work in #5.

    All in all, I'm very frustrated at the amount of work that I'm putting into the Fire HD's and the amount of progress they're showing. :/

    So I'm venting. :p I'll post later on my any direction changes I'm taking.
    View
    25
    Hashcode
    Hashcode
    djluis48 said:
    Dude if you get the sound working on this, i will buy one of these. :p
    Click to expand...
    Click to collapse

    Oh it's my top priority. I work every night on it at least an hour or 2 debugging how stock is connecting to the audio codec in the kernel. And what commands its sending during the setup and anytime volume is adjusted in the stock OS.

    I'm using this information to reverse engineering a Jellybean audio userspace driver.

    Eventually, it'll all be a beautiful thing.
    View
    23
    Hashcode
    Hashcode
    CURRENT KNOWN ISSUES:
    • When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
    • Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
    • AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
    • AUDIO: Headset volume still may be lowish. Testing better ways of increasing volume w/o distortion. It's a WIP.
    • 3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
    • Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
    • I don't have an LTE version so this is not enabled in current builds.

    CURRENT KNOWN APP/GAME ISSUES:
    • Need For Speed Most Wanted: Crash
    • EZPDFReader: PDF close = Crash
    View
    22
    Hashcode
    Hashcode
    I'll put out a new build soon with some minor updates:

    1. (CM updates obviously)

    2. I rebuilt the current KFireHD 8.9 w/o mobile data support and it seems to be much better on the battery (I know there's LTE users out there, and we'll setup a jem-wlan device just for you at some point). I was seeing large amounts of battery usage by telephony type stuff (probably looping).

    3. I AM still working on audio fixes, but I decided to take a quick gander at the camera and see if it was an easy fix. Right now it's about 80% from working, so I'll probably do the new build once that's good.

    4. And I can probably get HDMI going if I put a little more effort into it. But it seems like I should be spending 100% of my Kindle time on the audio issues... we'll see.
    View

New posts