If you are correct, I wouldn't know where to start - looks like I'm stuck with stock until someone who knows how to fix this comes up with a solution.
[ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [08/12 ICON DRAG FIX]
- Thread starter Hashcode
- Start date
If you are correct, I wouldn't know where to start - looks like I'm stuck with stock until someone who knows how to fix this comes up with a solution.
The Logcat entry that appears when the movie fast forwards is :-
04-18 04:15:27.178 D/dalvikvm(6273)
GC_CONCURRENT freed 4605K,65% free 4154K/11708K, paused 4ms+3ms, total 26ms
WAIT_FOR_CONCURRENT_GC blocked 13ms
04-18 04:15:28.295 D/dalvikvm(6273)
GC_CONCURRENT freed 606K,67% free 3882K/11708K, paused 36ms, total 37ms
04-18 04:15:28.295 I/dalvikvm-heap(6273)
Grow heap (frag case) to 5.101MB for 589840-byte allocation
04-18 04:15:28.334 D/dalvikvm(6273)
GC_CONCURRENT freed 4K,62% free 4454K/11708K, paused 6ms~+5ms, total 43ms
WAIT_FOR_CONCURRENT_GC blocked 25ms
04-18 04:15:28.373 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,58% free 5030K/11708K, paused 34ms, total 43ms
04-18 04:15:28.412 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,58% free 5606K/11708K, paused 32ms, total 32ms
04-18 04:15:28.451 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,48% free 6182K/11708K, paused 31ms, total 32ms
04-18 04:15:28.498 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,38% free 7335K/11708K, paused 33ms, total 33ms
04-18 04:15:28.537 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,27% free 8559K/11708K, paused 31ms, total 31ms
04-18 04:15:28.545 I/dalvikvm-heap(6273)
Grow heap (frag case) to 9.667MB for 589840-byte allocation
04-18 04:15:28.576 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,26% free 9135K/11708K, paused 33ms, total 33ms
04-18 04:15:28.584 I/dalvikvm-heap(6273)
Grow heap (frag case) to 10.230MB for 589840-byte allocation
04-18 04:15:31.638 I/Choreographer(6273)
Skipped 30 frames! The application may be doing too much work on it's main thread
04-18 04:15:31.521 D/dalvikvm(6273)
GC_CONCURRENT freed 6238K,70% free 3985K/12868K, paused 43ms, total 43ms
I hope this helps someone understand what's going on because it took me ages to type this in (going cross-eyed here)
04-18 04:15:27.178 D/dalvikvm(6273)
GC_CONCURRENT freed 4605K,65% free 4154K/11708K, paused 4ms+3ms, total 26ms
WAIT_FOR_CONCURRENT_GC blocked 13ms
04-18 04:15:28.295 D/dalvikvm(6273)
GC_CONCURRENT freed 606K,67% free 3882K/11708K, paused 36ms, total 37ms
04-18 04:15:28.295 I/dalvikvm-heap(6273)
Grow heap (frag case) to 5.101MB for 589840-byte allocation
04-18 04:15:28.334 D/dalvikvm(6273)
GC_CONCURRENT freed 4K,62% free 4454K/11708K, paused 6ms~+5ms, total 43ms
WAIT_FOR_CONCURRENT_GC blocked 25ms
04-18 04:15:28.373 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,58% free 5030K/11708K, paused 34ms, total 43ms
04-18 04:15:28.412 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,58% free 5606K/11708K, paused 32ms, total 32ms
04-18 04:15:28.451 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,48% free 6182K/11708K, paused 31ms, total 32ms
04-18 04:15:28.498 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,38% free 7335K/11708K, paused 33ms, total 33ms
04-18 04:15:28.537 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,27% free 8559K/11708K, paused 31ms, total 31ms
04-18 04:15:28.545 I/dalvikvm-heap(6273)
Grow heap (frag case) to 9.667MB for 589840-byte allocation
04-18 04:15:28.576 D/dalvikvm(6273)
GC_CONCURRENT freed <1K,26% free 9135K/11708K, paused 33ms, total 33ms
04-18 04:15:28.584 I/dalvikvm-heap(6273)
Grow heap (frag case) to 10.230MB for 589840-byte allocation
04-18 04:15:31.638 I/Choreographer(6273)
Skipped 30 frames! The application may be doing too much work on it's main thread
04-18 04:15:31.521 D/dalvikvm(6273)
GC_CONCURRENT freed 6238K,70% free 3985K/12868K, paused 43ms, total 43ms
I hope this helps someone understand what's going on because it took me ages to type this in (going cross-eyed here)
Just to let you know. Javabugz has provided two patches which Hash included in source (didn't test/build it myself):
- MXPlayer gets some buffer
- Bluetooth will work
Source: Link
So expect a new release including those changes. Thanks Javabugz & Hash
Edit:
- Can confirm Bluetooth to be working, tried with my GPS receiver and "bluetoothGPS" app. Small build script adjustment required (just for those building from source)
- MXPlayer gets some buffer
- Bluetooth will work
Source: Link
So expect a new release including those changes. Thanks Javabugz & Hash
Edit:
- Can confirm Bluetooth to be working, tried with my GPS receiver and "bluetoothGPS" app. Small build script adjustment required (just for those building from source)
Last edited:
Try Archos Video player, it doesn't seem to exhibit this issue - I've watched a couple of movies now that work OK that had problems with MX Player. The Plus here is that it has a much enhanced UI which I really like - so a 2 way win for me - one of those instances when a 'bug' has a good outcome.
Ooops, movies now having speedup/slomo probs in archos player as well - hope Hashcodes latest release has fixed this.
Last edited:
That is great news.
So the pending items are:
1. Audio input to get the mic working(for skype , Google video chat etc)
2. Hdmi: as soon as the HDMI cable is connected the orientation changes to landscape. But then picture is tilted in TV( pic attached).
3. The UART sleep issue which is affecting the standby time.
Sent from my Amazon Kindle Fire HD using xda app-developers app
So the pending items are:
1. Audio input to get the mic working(for skype , Google video chat etc)
2. Hdmi: as soon as the HDMI cable is connected the orientation changes to landscape. But then picture is tilted in TV( pic attached).
3. The UART sleep issue which is affecting the standby time.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Attachments
New update in the OP. For some reason my thread post didnt save last night. And I'll fix the date in the thread title as well when I'm back in.
Sent from my DROID4 using Tapatalk 2
Sent from my DROID4 using Tapatalk 2
Just did a dirty flash(adb side load using recovery - my preferred flash method
) and tested with a A2DP headset. Bluetooth works flawlessly. Tested HDMI again. As I said before everything works as expected only thing is that it is tilted 90 degrees.Sent from my Amazon Kindle Fire HD using xda app-developers app
Thanks Hashcode for this update, much appreciated.
I'm still having problems playing videos, is there a file I could edit to see if I can fix the problem ?
Thanks in advance.
I'm still having problems playing videos, is there a file I could edit to see if I can fix the problem ?
Thanks in advance.
Thanks Hashcode, your work is appreciated. Just a silly question. Is this update with the latest CM?
Thank you,
Ray
Thank you,
Ray
yes, it also includes latest sync with CM
Sent from my DROID RAZR HD using Tapatalk 2
Sent from my DROID RAZR HD using Tapatalk 2
I don't know, all of the movies i've tried are DVD rips that i've made from my own disks :-
The Hobbit
The Lord of the Rings Trilogy
Dredd
Zulu Dawn
to name a few
As a matter of interest, all of the above work OK on the stock kindle rom and all other android devices I own (7 in total)
I'll see if I can download something that exhibits the same problem.
Hashcode
Sorry for the delay - I've just downloaded about 1Gb of .mp4 astronomy podcasts trying to find a publicly available file as an example of the problems I am having, I have just watched all of them with no problems, typical, so I tried The Hobbit again and have just watched the whole movie with no problems - the exact same file that kept speeding up and slowing down last night !! - it is just so random and unpredictable I don't know what to do next.
Is there an apk or anything that I can install to try and catch/trace what's happening - if/when it happens again ?
Last edited:
Here is a smaller gapps that works on hash's build.
http://xdaforums.com/showthread.php?t=2012857
http://goo.im/devs/BaNkS/GApps/GApps 4.2.2 Minimal.zip
http://xdaforums.com/showthread.php?t=2012857
http://goo.im/devs/BaNkS/GApps/GApps 4.2.2 Minimal.zip
Just want to join in and praise hashcode work, not only is it free but everything so much faster!
One small side issue I've had is with audio though. After the cm10 install I get a kind of hissing sound when I use earphones, and lower audio quality compared to stock. Anyone recognizes this?
One small side issue I've had is with audio though. After the cm10 install I get a kind of hissing sound when I use earphones, and lower audio quality compared to stock. Anyone recognizes this?
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.
