Have you benchmarked your 8.9 yet? I doubt that there is going to be a problem with "drivers" for this tab once we are in Beta.
CM10 development for Kindle Fire HD 8.9"
- Thread starter verygreen
- Start date
-
- Tags
- cm10 rom development
Have you benchmarked your 8.9 yet? I doubt that there is going to be a problem with "drivers" for this tab once we are in Beta.
Development for the KFire HD 8.9 is progressing rather nicely to my point of view. I just haven't released anything yet. 
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 2
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 2
Best gift in this holiday. Are all hardware working?
Sent from my KFJWI using Tapatalk 2
Development for the KFire HD 8.9 is progressing rather nicely to my point of view. I just haven't released anything yet.
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 2
Sent from my KFJWI using Tapatalk 2
Last edited:
Development for the KFire HD 8.9 is progressing rather nicely to my point of view. I just haven't released anything yet.
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode, thank you for the update. Nice to know this project is taking shape. You need to spend some Holiday time away from all this and feed other needs. I am sure all of us can wait a little while longer for something we hoped for sometime during the coming year.
Merry Christmas
F@@dog
Development for the KFire HD 8.9 is progressing rather nicely to my point of view. I just haven't released anything yet.
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 2
it is compatible with KF 7' ?...
There is another thread for the CM10 development for the KFHD 7. Please use the search function. It is starting to get a little old people posting, "will this work on my version kindle" every 5 posts in every thread.
Thank you Hashcode for the update.
I'm hoping maybe someone can help; my build process keeps stopping with this message:
On the same note, when I run the command:
Thanks
EDIT: Seems like the term.apk got removed from original git hub location, I had to edit the "get-prebuilts" script like such:
Thanks to user sevenrock in this thread for discovering this http://xdaforums.com/showthread.php?p=35921520
However, I'm still getting the "make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/autumn/android/system/out/target/product/bowser/system/app/Term.apk'. Stop.
make: *** Waiting for unfinished jobs...." error and can't compile.
EDIT 2: I'm back in business had to cd to vendor/cm and run ./get-prebuilts the command: . vendor/cm/get-prebuilts didn't seem to work -maybe my environment is different.
Code:
make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/autumn/android/system/out/target/product/bowser/system/app/Term.apk'. Stop.
make: *** Waiting for unfinished jobs....On the same note, when I run the command:
Code:
autumn@WS03:~/android/system$ . vendor/cm/get-prebuilts
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 223k 100 223k 0 0 380k 0 --:--:-- --:--:-- --:--:-- 471k
Archive: ./proprietary/Term.apk
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
Archive: ./proprietary/Term.apk.zip
caution: filename not matched: lib/armeabi/libjackpal-androidterm4.soThanks
EDIT: Seems like the term.apk got removed from original git hub location, I had to edit the "get-prebuilts" script like such:
Code:
# Get Android Terminal Emulator (we use a prebuilt so it can update from the Market)
curl -L -o $BASEDIR/proprietary/Term.apk -O -L http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk
unzip -o -d $BASEDIR/proprietary $BASEDIR/proprietary/Term.apk lib/armeabi/libjackpal-androidterm4.soThanks to user sevenrock in this thread for discovering this http://xdaforums.com/showthread.php?p=35921520
However, I'm still getting the "make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/autumn/android/system/out/target/product/bowser/system/app/Term.apk'. Stop.
make: *** Waiting for unfinished jobs...." error and can't compile.
EDIT 2: I'm back in business had to cd to vendor/cm and run ./get-prebuilts the command: . vendor/cm/get-prebuilts didn't seem to work -maybe my environment is different.
Last edited:
I compiled a build and played around with this a few hours yesterday and all I can say is: Wow!. So fast and smooth. I can't bare going back to stock with Apex launcher but seeing how many things still don't work, I had no choice. Thanks for offering us a way to play around with this, Verygreen.
Thanks !
Will be looking forward to this ! The Kindle fire HD 8.9 is one fine piece of Hardware. Only problem is it is to restricted right now. I appreciate your work on this. I recognize you from the Nook Color forum !
Will be looking forward to this ! The Kindle fire HD 8.9 is one fine piece of Hardware. Only problem is it is to restricted right now. I appreciate your work on this. I recognize you from the Nook Color forum !
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
27Development for the KFire HD 8.9 is progressing rather nicely to my point of view. I just haven't released anything yet.
I'm working on Android 4.2.1. And the kernel is fully migrated to 3.0.50 (which matches AOSP kernel/common)
Right now I have display running a newer version of the gfx blit system + powervr libs built for jellybean, bluetooth, hw accelleration, and sensors.
I'm currently updating the wifi driver to match AOSP, and then I need to troubleshoot codecs/camera, graphics memory allocation and audio.
Almost every facet of the device is running updated drivers.
Sent from my DROID RAZR HD using Tapatalk 225Hi all!
Without much ado I am presenting you this repo for CM10 that lets you build somewhat functional CM10 ROM for Kindle Fire HD 8.9".
(Obviously this is not end-user friendly yet. If you don't know how to compile CM10 yourself, you are not a target audience for this yet, sorry. Many things don't work to make it viable main ROM yet anyway)
Build instructions (assuming you met all other CM10 build dependencies).
Download code:
Code:mkdir android/system cd android/system curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo chmod a+x ~/repo repo init -u git://github.com/CyanogenMod/android.git -b jellybean wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/bowser-jb/local_manifest.xml repo sync -j16
Build:
Code:. build/envsetup.sh lunch cm_bowser-userdebug . vendor/cm/get-prebuilts mka bacon
In the out/target/product/bowser output dir you'll have two important files generated:
recovery.img and cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip
For the first install only:
Step 0; Connect kindle to your computer, have android sdk installed and adb and fastboot in the path.
Step 1: (very important) Back up raw partitions from kindle responsible for recovery, boot and system.
(this requires root, though root-less installation is also possible, you will need the backups to return to stock!)
This last command will stop waiting for the fastboot device to appear. Do not unplug the kindle from USB.Code:adb shell su -c "chmod 777 /dev/block/*" adb pull /dev/block/mmcblk0p9 adb pull /dev/block/mmcblk0p10 adb pull /dev/block/mmcblk0p11 [code] Save these block images. Step 2: Prepare and run CWM: [code] rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\x00\x50\x7c\x80' >>/tmp/stack ; done adb push /tmp/stack /data/local/tmp/ adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot bs=6519488 seek=1" adb shell su -c "chmod 777 /cache" adb push /path/to/cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip /cache/ adb shell su -c "echo 0 > /sys/block/mmcblk0boot0/force_ro" adb shell su -c "echo -n 3 | dd of=/dev/block/mmcblk0boot0 bs=1 count=1 seek=4104" fastboot flash recovery /path/to/recovery.img -i 0x1949
Now reboot kindle: either power it off and on via it's GUI, or do adb reboot from a different terminal session (do not interrupt fastboot command still waiting!)
You'll see a "fastboot mode" on the screen and fastboot command started earlier will finally finish after writing the image onto the kindle.
Reboot kindle again via fastboot:
This will reboot you into CWM recoveryCode:fastboot reboot -i 0x1949
Step 3: In CWM recovery, do install from sdcard and install the cm-10...zip file we transferred in the previous step.
the /data/ settings from stock amazon install are not compatible with CM10, but (very important)Do not reformat /data/ and /cache from CWM, this will result in a corrupted filesystem due to 3.0.21 kernel currently used by amazon not having necessary fs features!!!
Instead, clean /data via adb while booted to CWM:
Step 4: Now, installation is complete, you may reboot and it will bring you to your freshly-installed CM10 - enjoy.Code:adb shell "mount /data" adb shell "rm -r /data/*"
(note by default this CM10 install starts with adb disabled, so you'll need to enable it in settings again).
How to reflash back to stock
Step 1: Remember where did you put those backups from step 1 during install.
Step 2:
Now either connect a powered off kindle, or reboot an already connected kindle.Code:fastboot flash recovery /path/to/mmcblk0p9 -i 0x1949
(note: I don't remember if stock rom is smart enough to wipe /data in this case or if it bootloops, so you might want to do rm -r /data/* before the final reboot)
once Kindle enters fastboot mode and recovery image is written, write the other two images too:
Now you are back to factory stock.Code:fastboot flash boot /path/to/mmcblk0p10 -i 0x1949 fastboot flash system /path/to/mmcblk0p11 -i 0x1949 # This one will take a few minutes fastboot reboot -i 0x1949
Not so short video on the install starting from somewhere around step 3 for those who cannot perform the steps, but need to ensure this ROM is not for them yet:
Many things don't work yet:
- Sound
- Video playback
- Sensors (no rotation)
- Camera
- BT
- probably some other stuff I have not noticed yet.
Please do send in your patches/fixes.12from hashcode@twitter, seems that everything else is good to go now except audio.
https://twitter.com/Hashcode0f/status/291949787551518720
@klescuts soon as I get audio working, ill release cm10.1 for KDHD8.911I've decided to release my current 2nd-bootloader setup + CM10.1 ROM even though the audio is not working yet.
You can find all of the information in these 2 threads:
2nd-bootloader install for coming from Amazon stock OS:
http://xdaforums.com/showthread.php?t=2128175
CM10.1 ROM for install in custom recovery:
http://xdaforums.com/showthread.php?t=2128201
Enjoy and please read through the OP's before starting the installs.11
Process is being made. Trust me, it'll be worth the wait.
If you are a Kindle Fire 2 owner, don't think we forgot about you!
