Sure, everyone should give back to the community - in the most efficient way. So far I have very basic knowledge of Android (as the KFHD is the first device I really own) - I worked with it a little bit during a school project. It would take me a while to get to the point where I can help a dev solving problems (e. g. with drivers). There are many people out there that already have more knowledge - because of work or because they have a better understanding of UNIX systems in general. That's why I think the most efficient way for me to contribute to the community is by non-monetary donations.
[ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [08/12 ICON DRAG FIX]
- Thread starter Hashcode
- Start date
Sure, everyone should give back to the community - in the most efficient way. So far I have very basic knowledge of Android (as the KFHD is the first device I really own) - I worked with it a little bit during a school project. It would take me a while to get to the point where I can help a dev solving problems (e. g. with drivers). There are many people out there that already have more knowledge - because of work or because they have a better understanding of UNIX systems in general. That's why I think the most efficient way for me to contribute to the community is by non-monetary donations.
All I'm saying is if you're not at least trying to learn in such a way that you will eventually be able to contribute in a way that can benefit everyone, and you are happy to just sit back and benefit from others' hard work, then be happy with what you get.
I am just giving you hell BTW, and my remark wasn't only directed at you, but it does get rather annoying to see so many people lose their patience over something they were never really intended to have in the first place.
Just my two cents...take it for what it's worth.
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [02/25 4.2.2 UDPATE]
Hopefully, my backlog of dev with the Motorola Droids is slowing down soon, and I'll be able to give this a bit more attention.
Sent from my DROID RAZR HD using Tapatalk 2
Hopefully, my backlog of dev with the Motorola Droids is slowing down soon, and I'll be able to give this a bit more attention.
Sent from my DROID RAZR HD using Tapatalk 2
Thanks Hashcode, just wanted to chime in as a daily user of CM10.1 on my KFHD8.9 that any attention at all is appreciated, but I also understand you are a great help to a great number of devices beyond what I use and appreciate your continued contribution and development for all of us here at XDA.
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [02/25 4.2.2 UDPATE]
Hashcode, 7x7 grid size of home screen is kind of not enough for this tablet, is that possible for you to make it bigger so we can put more icons on a single home screen?
Thanks a lot for your work.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
Hashcode, 7x7 grid size of home screen is kind of not enough for this tablet, is that possible for you to make it bigger so we can put more icons on a single home screen?
Thanks a lot for your work.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
Great build. With audio it'll be perfect.
I'm solely using your build which seems to be perfect (except for audio)- many thanks for your efforts
I'm solely using your build which seems to be perfect (except for audio)- many thanks for your efforts
I agree this build is great. Audio is a no brainer, but honestly, other than that, it runs great. I don't use bluetooth and even when I skype I never use video...just audio so I'm ok with that. I too needed the audio though so I went back to a stock rom.
Hi from the land of OZ. I have looked at all the requirements for my tab use in car and due to the width restrictions for my application I am limited to the Kindle HD LTE version (need gps, bt and 3g/4g as well as highest DPI achievable all at the same time).
I have read through the entire thread and I see there is not one person that appears to be using the LTE version of the kindle and even development may be hindered for the LTE version.
I would just like to voice my support and request to not stop the dev for the LTE version
I hope to get it mine in Australia by this month and will be able to provide notes and testing once that happens of course.
Thanks again and great work :good:
Mario
I have read through the entire thread and I see there is not one person that appears to be using the LTE version of the kindle and even development may be hindered for the LTE version.
I would just like to voice my support and request to not stop the dev for the LTE version
I hope to get it mine in Australia by this month and will be able to provide notes and testing once that happens of course.
Thanks again and great work :good:
Mario
Ran into a bit of a strange issue on my device. Went to update to the latest build 2/27 and I had an issue where wifi stopped working. I tried reflashing back and I got myself stuck in a handful of boot loops.
Ended up going back to stock temporarily and am using Nova / and old school Android market with decent results, but I will gladly retry this build when the next update gets pushed.
Ended up going back to stock temporarily and am using Nova / and old school Android market with decent results, but I will gladly retry this build when the next update gets pushed.
This happened to me when I jumped from the previous 0202 build to the latest 0227, then I restored to Amazon stock under fastboot mode and reflashed to 0227 based on Amazon official. It runs very well now. I don't know why I got stuck from 0202 to 0227. At that time I can not even use ADB mode but thank god fastboot is still good.
Hey Hash code, are you still there? Been using your latest build from the beginning. Please don't forget us - only missing sound. Thanks for your work.
Couldn't keep myself from flashing CM10.1 - All went as expected following the threads found here and here (this thread).
However - 2 problems:
ADB stopped working - Yellow ! in device manager
WiFi wont turn on.
So - I'm a little dead in the water here, until I get ADB working again...
Anyone else with ADB problems (who's found a way to fix it)?
<edit>Well, of course - So used to using ADB to transfer stuff to/from my devices, I completely forgot you can use good old Windows drag&drop to copy previous (cm-10.1-20130202-UNOFFICIAL-jem.zip) version to the Kindle and install that instead. And wouldn't you know - Now both WiFi and ADB works. No shadow over Hashcode, but there's something not 100% ok with the 0225 build... </edit>
However - 2 problems:
ADB stopped working - Yellow ! in device manager
WiFi wont turn on.
So - I'm a little dead in the water here, until I get ADB working again...
Anyone else with ADB problems (who's found a way to fix it)?
<edit>Well, of course - So used to using ADB to transfer stuff to/from my devices, I completely forgot you can use good old Windows drag&drop to copy previous (cm-10.1-20130202-UNOFFICIAL-jem.zip) version to the Kindle and install that instead. And wouldn't you know - Now both WiFi and ADB works. No shadow over Hashcode, but there's something not 100% ok with the 0225 build... </edit>
Last edited:
Glad you worked through the update! You're right - there is a problem with the 0225 build, at least with regards to WiFi. Hit Hashcode's link and install the 0227 build - WiFi works perfectly.Couldn't keep myself from flashing CM10.1 - All went as expected following the threads found here and here (this thread).
However - 2 problems:
ADB stopped working - Yellow ! in device manager
WiFi wont turn on.
So - I'm a little dead in the water here, until I get ADB working again...
Anyone else with ADB problems (who's found a way to fix it)?
<edit>Well, of course - So used to using ADB to transfer stuff to/from my devices, I completely forgot you can use good old Windows drag&drop to copy previous (cm-10.1-20130202-UNOFFICIAL-jem.zip) version to the Kindle and install that instead. And wouldn't you know - Now both WiFi and ADB works. No shadow over Hashcode, but there's something not 100% ok with the 0225 build... </edit>
http://goo.im/devs/Hashcode/jem/cm10.1/
Thank you - Yes, that was a better experience. Wifi and ADB working nicely. Also, Play Store seems to be much more kind to this build than to the 0202 version.
Coincidentally, 0227 is my birthday, so I consider it a personal gift from Hashcode to me
Now, once there's audio (and BlueTooth!) I'm more than satisfied.
Happy birthday!Thank you - Yes, that was a better experience. Wifi and ADB working nicely. Also, Play Store seems to be much more kind to this build than to the 0202 version.
Coincidentally, 0227 is my birthday, so I consider it a personal gift from Hashcode to me
Now, once there's audio (and BlueTooth!) I'm more than satisfied.
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.
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.
great news!
Thanks for all your efforts. Been checking here many times a day. Felt like I hit the jackpot with your message.
Thanks for all your efforts. Been checking here many times a day. Felt like I hit the jackpot with your message.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
107Unofficial 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 jem37So, 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. I'll post later on my any direction changes I'm taking.25Dude if you get the sound working on this, i will buy one of these.
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.23CURRENT 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
22I'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.
