yashsingh1/xdaforums huggingface dataset:
[8.9" Kindle Fire HD Android Development] monster1612:
1) Backup your data (use Titanium Backup and/or TWRP's backup capabilities).

2) Download the latest 6.0 ARM opengapps (doesn't matter which version, but stock and higher will NOT work without a custom config file) if you use them.

3) Reboot into recovery. Do NOT reboot until you're done flashing everything.

4) Flash your CM ROM, then gapps (if used), then any other mods (like SuperSU, Xposed, etc.), wipe cache, THEN reboot.

5) Profit.
[8.9" Kindle Fire HD Android Development] alexander_32:
NEW BUILD (MOB31E)

https://www.androidfilehost.com/?fid=24591000424964051

Installation: Full wipe/flash ROM + Open GApps

SUPERSU INSTALLATION
[8.9" Kindle Fire HD Android Development] redhonker:
Does the camera work for anyone on 20160827? Mine still gets error. So does the Clock app.
[8.9" Kindle Fire HD Android Development] :
Camera works fine; use open camera or another app, cm camera won't work. Clock also works fine; if you use gapps then choose not to replace cm clock with google clock via config.
[8.9" Kindle Fire HD Android Development] redhonker:
OK, I will try another camera app.

I've already flashed gapps. How do I replace the clock then?

Thanks
[8.9" Kindle Fire HD Android Development] :
Reflash the rom.
[8.9" Kindle Fire HD Android Development] redhonker:
Without re-flashing gapps? Or do I need to flash a version of gapps w/o the clock?

thanks
[8.9" Kindle Fire HD Android Development] :
Reflash the rom and then gapps. If you're using a package that includes google clock, use a .gapps-config file to exclude it. If you flashed a smaller package that already didn't include google clock, then I don't know what your issue could be.
[8.9" Kindle Fire HD Android Development] windsurfer7:
there seems to be an issue with the wifi, i have 5ghz wifi set to channel 149 and for some reason the tablet wont find any network with the channel higher than 48, any idea how to solve this? for me using a channel lower than 149 is not an option.
[8.9" Kindle Fire HD Android Development] :
This is a limitation of the 2012 kindle hardware, not a rom bug. I tend to stick to 2.4Ghz since my speed tests cap out around 60/60 on the device on either band.
[8.9" Kindle Fire HD Android Development] redhonker:
re-flashed 20160827 and then gapps-micro. clock is working.

20160827 boots much faster (less than 2 min) and the system overall is more responsive. However, the game graphics is still quite slow. Is there any other tweaks?
[8.9" Kindle Fire HD Android Development] alexander_32:
NEW BUILD (UBERTC 4.9 and 3.0.101 kernel version)

https://www.androidfilehost.com/?fid=24727369092695267

Installation: Full wipe/Flash ROM + OpenGApps
[8.9" Kindle Fire HD Android Development] dcahoe:
Installed and opengapps mini gave error saying not enough system space. Went back to 0827 for now. May try with opengapps micro.
[8.9" Kindle Fire HD Android Development] alexander_32:
You should tried opengapps micro first.
[8.9" Kindle Fire HD Android Development] :
Take a look at the slowly growing size difference in any device's cm package and you'll realize you can't use a large gapps package on a device with just 1GB of system space. It won't be getting any smaller either. The solution is to use a config file and exclude gapps you don't want and include removal for stock cm apps you don't need (like CMUpdater, HexoLibre, etc). I would recommend excluding gapps that get updated frequently and downloading them from the playstore directly since they end up taking space on your data partition quickly anyway.
[8.9" Kindle Fire HD Android Development] redhonker:
What's new in this build?

Thanks
[8.9" Kindle Fire HD Android Development] :
Aside from the upstream changes to cm up to the date of the build, just the newer kernel version and the use of the UBER gcc 4.9 toolchain during compilation.
[8.9" Kindle Fire HD Android Development] jaramosparra:
I think that the question must be: what doesn't work in this rom?
[8.9" Kindle Fire HD Android Development] ijustknow:
My router sends out both 2.4 GHz and 5.0 GHz, Jem works both fine.
[8.9" Kindle Fire HD Android Development] alexander_32:
NEW BUILD (M4B30X)

https://www.androidfilehost.com/?fid=385035244224384526

Installation: Full wipe/Flash ROM + OpenGApps
[8.9" Kindle Fire HD Android Development] jeetkunejoe:
No Wifi disconnects (5ghz) on this build. This was a frequent problem on previous builds. Camera seems to work perfectly too. Great job alexander_32!
[8.9" Kindle Fire HD Android Development] alexander_32:
PLEASE VISIT UPDATED THREAD

http://xdaforums.com/kindle-fire-hd/8-9-development/rom-cyanogenmod-t3482396

THANKS
[8.9" Kindle Fire HD Android Development] windsurfer7:
On which 5ghz channel is your wifi set on? My issue was with the high channels 149 151 etc.. the Kindle fire wont recognize them on any cm13 based rom
[8.9" Kindle Fire HD Android Development] psycho_asylum:
Hello! I just picked up a Fire HD 8.9 from a second-hand store for $40, looks brand new and is running Fire OS 8.5.1. I'd like to install this CM13 ROM. I've tried Windows and Linux to get this thing to load into fastboot and it's not working. I see the Jem-PVT-Prod-04 show up in device manager briefly and it seems to have a driver installed, but then the device boots normally. All of the root threads are old and seem to be relatively outdated. Anyone got an idea on where I can start with this one? Much appreciated.
[8.9" Kindle Fire HD Android Development] ipdev:
Jem-PVT-Prod-04 is only 4 years old? (Nov. 20th 2012)

- Seems like I've had mine for more than that.. :silly:

Both of these work, even if a little old, and give links to the files needed. (Grab newer twrp from link below.)

https://web.archive.org/web/20161224194648/https://wiki.cyanogenmod.org/w/Install_CM_for_jem

(wiki.cyanogenmod.org/w/Install_CM_for_jem - no longer available - link to web archive site.)

http://xdaforums.com/showthread.php?t=2128175

I didn't use either of these originally but, the files were the same and mostly the same steps.

(You should have no problems from linux. If you have an issue, su and run as root.)

Currently running on mine. (Just re-flashed it tonight.)

kfhd8-twrp-3.0.2-2-recovery.img

cm-13.0-20161107-UNOFFICAL-jem.zip

open_gapps-arm-6.0-pico-20161111.zip

twrp (Link should be in last post by [MENTION=6677866]alexander_32[/MENTION] :svetius: )

http://xdaforums.com/kindle-fire-hd...very-twrp-3-0-0-touch-recovery-t3324640/page4

rom (Link from [MENTION=5991981]manu3193[/MENTION] :svetius: )

http://xdaforums.com/kindle-fire-hd/8-9-development/rom-cyanogenmod-t3482396/page2

opengapps (What would we do without these .. :svetius: )

https://github.com/opengapps/arm/releases/

My install log

http://pastebin.com/RzH5vcyU

Thank you [MENTION=6751354]transi1[/MENTION] for all you've done for our tate's and jem's :) :svetius: :good:

Edit :

Updated cm install link.
[8.9" Kindle Fire HD Android Development] psycho_asylum:
Thanks. I got Linux Mint set up on an old laptop I had sitting around and was able to get into fastboot. For some reason, the drivers don't work for me in Windows 10. Once I got TWRP installed I was good to go.
[8.9" Kindle Fire HD Android Development] transi1:
Coming ;)
[8.9" Kindle Fire HD Android Development] wizard_mini:
Waiting for cm14.1
[8.9" Kindle Fire HD Android Development] transi1:
CM14.1: https://www.mediafire.com/folder/5olnizsgh2jz5/jem
[8.9" Kindle Fire HD Android Development] bapi28:
CM 14.1 Nougat on jem

Thanks transi1!!! Quite a bumpy install but I can confirm it eventually works!

The experience and performance is similar to the AICP 12.1 from the other thread, but the install process is much more weird.

After flashing, there first was a series of 4-5 successive bootloops with nothing more to see than a black screen (sometimes long, sometimes short) after the blue Kindle Fire logo.

Finally, as I was about to give up and flash something else, the blue blinking CM logo finally showed up for a good while...

...which eventually led to the usual "first run / welcome assistant" but somehow it was stuck/frozen (unresponsive to touchscreen) and rebooted all by itself after 20-30 seconds...

...then it came back after rebooting and this time it accepted touchscreen input and eventually everything went through! Amazing!!

Subsequent 2 reboots seemed to go straight through without bootlooping (but that was before flashing SuperSU, see below).

Main specific problem I bumped into: the root access does not seem to work (although it is enabled for both apps and adb under developer options), maybe I'm missing something?

This is unlike the AICP 12.1 from the other thread, which had root access enabled and working right from the beginning.

I attempted to flash the latest "system mode" SuperSU (SR5) from TWRP, but (as reported by others in other threads with other ROMs) it

cripples everything

(endless boot with flashing CM logo).

I can't understand whether root access is actually "baked in" CM or not? I'd be glad if an expert can explain a bit more about this.

Also, the previous CM 13.0 builds from alexander_32 apparently needed to flash SuperSU to enable root (despite CM being theoretically pre-rooted) ?

Other more or less minor "glitches" I noticed are mostly the same as with the AICP 12.1 ROM:

- camera app does not work (can't enable camera, no big deal)

- weirdness of battery status display and icons not following settings and not properly reflecting charger plugging

- vertically stretched screenshots in "recents" switcher apps display (holding tablet in portrait mode)

- can't find where to enable new Nougat "split screen" function (setting is present but greyed out)

- the "invert colors" function has no effect

- some video apps complain about missing Widevine DRM
[8.9" Kindle Fire HD Android Development] bapi28:
CM14.1 Nougat on jem update

UPDATE (and solution about root access)...

I did the whole process again:

- advanced wipe data, cache and system

- re-install ROM + latest OpenGapps pico

- wipe cache and Dalvik

- reboot

This time it needed only a single bootloop for the blue CM logo to appear, so this bootloop phenomenon on newly installed ROMs seems rather random (?).

I got the freeze and crash/reboot again during the "first run / welcome" assistant just like the first time (this time it happened during Wifi network selection, on previous install it was during language selection).

After reboot, again, everything goes well without any problem, just like the previous install process. Booting time is really not bad (much faster than RR 5.7.4, maybe even faster than AICP 12.1).

Here's an approximate timing of the booting process:

- after less than 5 seconds: switch from the orange to the blue Kindle Fire logo

- after another (longish) 40 seconds: switch from the blue Kindle Fire logo to the flashing CM alien logo

- after another 20 seconds: switch to CM welcome / lock screen

So that's a little more than 60 seconds overall, really not bad at all.

However, I noticed that there is still a tendency to bootloop, so sometimes it will need to cycle 2-3 times between the orange and blue Kindle Fire logos (40-50 seconds each time) before it actually manages to launch the ROM.

So in case of bad luck the boot-up time can be increased to 3-4 minutes. This is not specific to this ROM: previous ROMs had similar bootloop behaviour.

About root access: this time, I enabled developer options right away after first boot. Just after I did that, root access was already enabled in the developer settings (for both apps and adb).

It seemed strange to me that this setting would be enabled by default so I first disabled it, and then immediately re-enabled (for apps only, don't know if that matters).

I got a warning / confirmation prompt and pressed OK. ==> This time it worked!! Yay!!

So there is no need for SuperSU btw. I wonder what this SuperSU thing is about: I'm still interested for expert's insight about this.

---------- Post added at 05:39 PM ---------- Previous post was at 05:15 PM ----------

About the "Widevine DRM" annoyance...

This is very unclear for a noob like me, but there is apparently some valuable information in the PDF under this URL:

https://storage.googleapis.com/wvdocs/Widevine_Modular_DRM_Getting_Started_CDM_for_Android.pdf

They say there was a progressive policy change regarding this DRM between Android K, L, M and N.

Now, under Android N, there is a mandatory new procedure regarding integration of this "Widevine" stuff.

My understanding is that the library should be "baked in" the ROM at compile time but that a supplementary step (and license agreement) is required before you can actually fetch the source code.

This may be the reason why independent ROM developers don't include it in their builds...? Maybe only big manufacturers can apply for their developer program?

Transi1 (and others who know): what do you think?
[8.9" Kindle Fire HD Android Development] bustr85:
It's odd - Gmail doesn't recognise my account, but when I try to add it it says it exists.
[8.9" Kindle Fire HD Android Development] bobcat131:
I need help! I flashed via TWRP the Supersu.zip and now my device is stuck at the Kindle Fire Logo (orange) not animating or moving at all. The device connects to the computer for a micro second and then disconnects so I have no adb or fastboot. Is there any way to get this to boot or is it bricked permanently?
[8.9" Kindle Fire HD Android Development] bapi28:
You're not alone: I also have this.

Couldn't find a solution yet (tried to remove my account and add it again but same problem).
[8.9" Kindle Fire HD Android Development] sirp0p0:
I had this problem on one of the other ROMs. Delete the Gmail app and go onto APKmirror and download an older version of Gmail. I used version 2.something. Install, setup the account, then upgrade from the Play Store.
[8.9" Kindle Fire HD Android Development] bustr85:
Sorted, installed version 5.x and updated. Thanks a lot
[8.9" Kindle Fire HD Android Development] bapi28:
Indeed, it works!! Thanks [MENTION=4594340]sirp0p0[/MENTION] for the tip!!
[8.9" Kindle Fire HD Android Development] ijustknow:
It is always amazing when I come back to this thread.

Jem is the oldest device of mine but the first to get Nougat.
[8.9" Kindle Fire HD Android Development] ludwigmace:
Installed 14.1 with the pico gapps and it runs nice and fast (flashed the ROM first then the gapps). Thanks!
[8.9" Kindle Fire HD Android Development] Dnorris55:
I did the same thing, and was able to recover it.

Had to use Linux to get the tablet into bootloader mode. Then I reflashed the bootloader, ROM(CM14.1) boot image, and TWRP.
[8.9" Kindle Fire HD Android Development] bobcat131:
OK, thanks for reply. I will try Linux soon. Merry Christmas!
[8.9" Kindle Fire HD Android Development] js290:
Device just crashed while adjusting the LiveDisplay night time color temperature; daytime color adjustment seems to be fine. It rebooted and came back. Attaching logcat, bugreport, and kmsg output as it was crashing.
[8.9" Kindle Fire HD Android Development] mr.galaxys:
(cm version 14.1-20160827-UNOFFICIAL-jem) nougat 7.1 got it on my kindle everything seems to running good but - camera app does not work (can't enable camera, tried using open camera still didn't work would like skype etc doesn't work any help would be appreciated god bless happy new years ) thanks for keeping my kindle 8.9 alive
[8.9" Kindle Fire HD Android Development] transi1:
LineageOS coming...
[8.9" Kindle Fire HD Android Development] mr.galaxys:
https://github.com/LineageOS/android_device_amazon_jem

yup it seems interesting to bad CyanogenMod CyngnOS seems be closing down and lineageOs take it place

but anyone figure out how fix camera in nougat 7.1
[8.9" Kindle Fire HD Android Development] transi1:
LineageOS build 20161231: http://www.mediafire.com/file/qzcgdp4lge39a1o/lineage-14.1-20161231-UNOFFICIAL-jem.zip
[8.9" Kindle Fire HD Android Development] Dnorris55:
Thanks. I've tried installing several times, just get a bootloop (orange fire - blue fire - Android). Clean install, with and without Gapps.
[8.9" Kindle Fire HD Android Development] ipdev:
I had to flash the boot image from RR-N-v5.8.0-20161226-jem-unofficial to get it to work. :confused:

(Most of the time, if boot.img works with twrp I do not worry about it.)

Still playing with it but, I can tell you lineage-14.1-20161231-UNOFFICIAL-jem seems to be working nice so far.

Setup steps used on my jem :

- fastboot

erase cache

erase userdata

flash bootloader kfhd8-u-boot-prod-8.1.4

flash recovery kfhd8-twrp-3.0.2-2-recovery

flash boot.img ( from lineage-14.1-20161231-UNOFFICIAL-jem )

- twrp

(Wipe - Formats Data - Reboot Recovery - Wipe Factory Reset - Reboot Recovery)

adb sideload lineage-14.1-20161231-UNOFFICIAL-jem

adb sideload open_gapps-arm-7.1-pico-20161230

(Reboot Bootloader)

- fastboot

flash boot boot.img ( from RR-N-v5.8.0-20161226-jem-unofficial )

Hope this helps. ;)
[8.9" Kindle Fire HD Android Development] Dnorris55:
Thanks, and Happy New Year!

I skipped the fastboot & ADB stuff, and did everything from TWRP.

Updated TWRP from 3.0.1 to 3.0.2

Wiped all but internal storage

Flashed Lineage rom

Reboot to recovery

Flashed nano 7.1 Gapps

Flashed boot.img from Lineage rom (wouldn't boot)

Flashed boot.img from RR-N-v5.8.0-... Rom

Boots & runs OK
[8.9" Kindle Fire HD Android Development] js290:
Mine just goes through the "Kindle Fire" logo colors about 3 cycles and finally boots. Did the same on the last cm14.1 build.
[8.9" Kindle Fire HD Android Development] wizard_mini:
LineageOS tested：HDMI output error and youtube if long time played, the sound may	be	aberrant.
[8.9" Kindle Fire HD Android Development] mr.galaxys:
so how do I get my camera on my tablet to work agin no 3rd party apps work I have go back to cm-13.0-20160218-UNOFFICIAL-jem.zip?
[8.9" Kindle Fire HD Android Development] ijustknow:
Downloading the LineageOS, so excited about burning it into my JEM.
[8.9" Kindle Fire HD Android Development] ijustknow:
Exactly the same situation as yours.

My last version is CM14.1 in this thread.

Maybe we should wipe?
[8.9" Kindle Fire HD Android Development] transi1:
r25: https://www.mediafire.com/folder/iiuqc32f8z6ce/jem

ps SU - after flash and boot rom need enable root in dev. options and install SuperSU or Magisk from Play Store
[8.9" Kindle Fire HD Android Development] bighead2k:
Works already quite well (only Flightradar App is not working). Thanks for porting.

Is jem going to become part of the nightly build process?
[8.9" Kindle Fire HD Android Development] transi1:
no :p

new build on mediafire
[8.9" Kindle Fire HD Android Development] justanumber:
Have Lineage on my phone and very happy, so really happy to see lineage for my FireHD 8.9:)

Have very old TWRP 2.7.0.0 on FHD now. Not sure it will work with LineageOS ?

Like to update TWRP but not so sure how and see many people in bootloops trying.

Any chance I am wrong and LineageOS will flash with TWRP 2.7.0.0 ?

Thanks in advance.
[8.9" Kindle Fire HD Android Development] ong14:
I was on TWRP 2.7.0.0 with unofficial LineageOS 14.1 20170308 build, it worked without any problems.

But I update it to 2.8.7.0 then 3.0.2.0.
[8.9" Kindle Fire HD Android Development] justanumber:
Hey, thanks much for info. Very good to know.

Did you have to do anything special to upgrade from 2.7.0.0 to 2.8.7.0?

Do not see older versions on teamwin site, only https://twrp.me/devices/amazonsoho.html which requires at least 2.8.4 to use TWRP method.

Thanks again.
[8.9" Kindle Fire HD Android Development] ong14:
No, just flash a zip file.

TWRP 3.0.2.0 is in img format, which cannot be flashed with TWRP older than 2.8.7.0.

That is why I have to update to 2.8.7.0 (zip format) and then 3.0.2.0 (img format).
[8.9" Kindle Fire HD Android Development] justanumber:
Thanks, perfectly clear now.
[8.9" Kindle Fire HD Android Development] transi1:
new build
[8.9" Kindle Fire HD Android Development] FireCulex:
Bluetooth doesnt work, have a wireless keyboard.

opengapps 7.1 mini won't install either, says insufficient space.

MTP doesn't work, when the device is plugged in PC recognizing the device, shows it in my computer, but no Internal Storage inside of Amazon Jem.
[8.9" Kindle Fire HD Android Development] ripee:
[MENTION=6751354]transi1[/MENTION], I'm trying to build both jem and tate and I keep running into this error:

FAILED: /bin/bash -c "(make clean -C hardware/ti/omap4/pvr-source/eurasiacon/build/linux2/omap4430_android ) && (cp kernel/amazon/bowser-common/drivers/video/omap2/omapfb/omapfb.h /home/ripee/android/lineage-14.1/out/target/product/jem/obj/KERNEL_OBJ/drivers/video/omap2/omapfb/omapfb.h ) && (make -j8 -C hardware/ti/omap4/pvr-source/eurasiacon/build/linux2/omap4430_android ARCH=arm KERNEL_CROSS_COMPILE=arm-eabi- CROSS_COMPILE=arm-eabi- KERNELDIR=/home/ripee/android/lineage-14.1/out/target/product/jem/obj/KERNEL_OBJ TARGET_PRODUCT=\"blaze_tablet\" BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.0 ) && (mv /home/ripee/android/lineage-14.1/out/target/product/jem/obj/KERNEL_OBJ/../../target/kbuild/pvrsrvkm_sgx544_112.ko /home/ripee/android/lineage-14.1/out/target/product/jem/system/lib/modules ) && (/arm-eabi-strip --strip-unneeded /home/ripee/android/lineage-14.1/out/target/product/jem/system/lib/modules/pvrsrvkm_sgx544_112.ko )"

This is the roomservice.xml file I'm using:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="transi/kernel_amazon_bowser-common" path="kernel/amazon/bowser-common" remote="github" revision="cm-14.1" />
<project name="transi/android_device_amazon_omap4-common" path="device/amazon/omap4-common" remote="github" revision="cm-14.1" />
<project name="transi/android_device_amazon_bowser-common" path="device/amazon/bowser-common" remote="github" revision="cm-14.1" />
<project name="transi/android_device_amazon_jem" path="device/amazon/jem" remote="github" revision="cm-14.1" />
<project name="transi/android_device_amazon_tate" path="device/amazon/tate" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_amazon" path="vendor/amazon" remote="github" revision="cm-14.1" />
</manifest>

Any suggestions? Thank you!
[8.9" Kindle Fire HD Android Development] ijustknow:
Excitedly installed the new build as the last one build 20161231 does not work on my Jem.

Installation was smooth and lasts about 10 minutes, then booted into the system.

No desktop showed, only black.. Shut it down and reboot.

The same, no desktop, only black. i can use the notification bar to adjust brightness, go into setting to modify the wallpaper.

but once i went back the home, only black. No app icons, no drawer icons, so i cannot use any app.

Any clue?
[8.9" Kindle Fire HD Android Development] bighead2k:
What has changed so far beside new lineageos sources?

Could you list known problems?

As far as it reads here:

- bluetooth doesn't work

- Some Apps don't work (flightradar24)

- For me sound sometimes goes mad misteriously. Restart of app solves the problem.

Thanks for your work :)
[8.9" Kindle Fire HD Android Development] transi1:
hi,

only https://review.lineageos.org/#/q/status:merged
[Moto 360] airjordan223:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.

After a few days of the update pestering me I decided to go for it.

Now there are 2 things that are very annoying.

The first, whenever the screen comes on, there is a slight delay in the watch face.

It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.

I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.

The second thing is that the watchface doesnt turn on when I receive texts anymore.

The vibrate function still works, but the screen won't light up.

Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.

Thanks
[Moto 360] moeozman:
Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.
[Moto 360] Darkwing77:
Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.