yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Updated rom is on AFH
[Fire HD 8 and HD 10 Original Android Development] PixelatedApe:
Attempting to flash this one with TWRP throws up an error of 'Zip file is corrupt!' 7zip on desktop also gives two warnings, 'There are some data after the end of the payload data' and 'Data error: system.new.dat.' Did re-download in an effort to make sure the problem wasn't at my end, with the same results.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I will fix it it seems the zip uploaded partially
[Fire HD 8 and HD 10 Original Android Development] DB126:
Yep-same error.
[Fire HD 8 and HD 10 Original Android Development] Xinto:
You can set smallest width in Dev settings
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Yeah... Unfortunately new build didn't solve any crashes
[Fire HD 8 and HD 10 Original Android Development] DB126:
I have rolled back to FireOS. While Lineage interface is preferred it is relatively easy to tame stock once rooted/unlocked. Like all custom ROMs it's the last 5% (typically hardware support) that's the toughest to stabilize and refine. Too many tweaks are needed for my tastes to roll with Lineage on this pup. In the end I prefer to use my devices vs manage them.

FWIW - full Play Store access is easy on FireOS v6 using Onn 8 fingerprint as hardware is nearly identical. Toss in Nova and it's hard to tell the two devices apart in daily use unless wallowing around in settings. HD8 has the edge in battery life and audio quality; Onn 8 has a bit more memory (although not as well managed), Android 9 core and a slighty better panel...although the latter is quite subjective.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Thank you for testing! I'm working with OP to test back to October build and incrementally add commits until we find what's causing it. This newest build was an attempt to fix this dpi crash bug without having to do all of that.

If looking for stability in the meantime, I'd suggest the October build with flashed headphone enabler, flashed OMX. I'll edit this and add direct links to each.

OMX patch fix by [MENTION=9906981]Ziona[/MENTION]

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-14-1-t3973703/post80762749#post80762749

Headphone enabler [MENTION=7433470]peterli99[/MENTION]

https://github.com/workit247/karnak/raw/master/karnak_LOS141_headphonefix-556.zip

lineage-14.1-20191006-UNOFFICIAL-karnak

https://github.com/mt8163/android_d...s/tag/lineage-14.1-20191006-UNOFFICIAL-karnak
[Fire HD 8 and HD 10 Original Android Development] Xinto:
I have to make an edit here, if you are using YouTube Vanced like me, do not flash OMX patch as it will cause issues while playing videos in 60 fps and sometimes even makes videos to lag while in background. Haven't tested on stock YouTube but this is just a caution, you can ignore this and patch ROM depending on your needs. Thanks for reading and thank you spelcheck for helping OP in solving some serious issues. Also this may sound like I'm being smarter than you (which I'm clearly not) but can you guys try downgrading kernel back to 3.18.19?just to chill down my dumb ass which thinks that kernel is the cause. Thanks again
[Fire HD 8 and HD 10 Original Android Development] mattgyver:
Thread cleaned. Behave. OS choice is a CHOICE. There is no universally 'better' OS, as everyone's needs, wants, and expectations differ. If FireOS doesn't work for you, you have options, because ANDROID.

Keep it civil and I won't have to do more than just clean the thread. :good:
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
I can say I did experience this issue with youtube vanced when I had used the OMX patch and it even made the xfinity app start to have issues where the video would freeze to just a picture but the audio would keep going. the vanced issue was fixed by turning off VP9 Codec and Ex player v2 in the vanced settings idk any fix for the Xfinity issue

maybe next time a guy shouldn't attack me for simply stating fireos is bad and then going to mods as if he did nothing wrong
[Fire HD 8 and HD 10 Original Android Development] elpoblano:
So I flashed lineage onto 3 tablets I gave my kids- the only problem I'm having is I can't seem to get plex running. It crashes just after startup. Anyone else have a similar problem?
[Fire HD 8 and HD 10 Original Android Development] Xinto:
There are many apps crashing in later builds but I'm sure that would not occur in October builds, OP and spelcheck are working on a fix and I'm pretty sure they'll find the fix. Stay tuned
[Fire HD 8 and HD 10 Original Android Development] mattgyver:
Or maybe, instead of the continual back of forth, you both could have taken the humble route, said ok, and just moved on. And don't assume that the other user thought he didn't do anything wrong. He knew his posts were just as off-topic as yours.

Either way - it was off topic for the thread, so it's been handled. If you want to still debate it, do so in it's own thread (civily) so as not to hijack someone else's thread. :good:
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
We are in the process of elimination on tracking down that dpi bug (and others) and kernel will be a part of that process.

Very good info that Vanced YouTube doesn't play nice with OMX fix for 60fps. There was some talk about including OMX fix in a future release, but info like this is helpful in making decisions like that. Definitely don't want to make fix one thing and break another.
[Fire HD 8 and HD 10 Original Android Development] elpoblano:
Thanks for the heads up. I'm happy to do whatever I can, if they need error logs or whatever.
[Fire HD 8 and HD 10 Original Android Development] DB126:
:svetius: :rolleyes:
[Fire HD 8 and HD 10 Original Android Development] Sleeepy2:
Do you have a guide for switching back to stock? I can't seem to find one.

I have HD 8 2018 version.

Thanks
[Fire HD 8 and HD 10 Original Android Development] Xinto:
I'm sorry but have I missed something? When did 9th gen release?
[Fire HD 8 and HD 10 Original Android Development] Sleeepy2:
oops, typo thanks.
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Oh, no problem. There is a guide in K4y0z's post
[Fire HD 8 and HD 10 Original Android Development] Sleeepy2:
Thanks, looks like there is no way to go back just using twrp.

I will need to set my pi back up to do this.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
You should be able to download the bin (rename to a zip) from amazon and flash from TWRP. How far back to stock you looking to go? back to stock recovery too? If you made a backup before flashing, this would be really simple...
[Fire HD 8 and HD 10 Original Android Development] Sleeepy2:
Oh really. Sweet. I just want to go back to the stock rom and try it. I've been on Lineage the day I got it.

I just downloaded the stock bin update-kindle-NS6301_user_1638_0001309042308 so renaming to .zip and using TWRP it should boot...
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I believe so, make a full backup to be safe. Try flashing it and test... do not connect to the internet until you have blocked updates. The risk may be you have to open it up to short it back, but unlikely... If you want root, i would also flash magisk. You should have a unlocked bootloader if you are at this point and should be able to fix any issues. Why go back to stock though? Stock is so laggy...
[Fire HD 8 and HD 10 Original Android Development] kegang:
Experiencing Gboard crashing with the latest build :(
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Just wanted to give you guys an update that [offline] we have rolled back some of the more recent commits and are testing all of the apps you guys have mentioned were crashing or had issues. Something obviously broke a few things since the October 6th release (dpi issues and some codec-related) and we'll track that down and leave whatever it is out of the next release. So far we've tested everything mentioned and they're all launching fine, even streaming apps like Disney+ are playing video without any OMX fix.

Use the links above to install October 6th build and headphone enabler if you need things to be stable in the meantime, but otherwise hang tight.

@AlienTechnology | [MENTION=4914529]Michajin[/MENTION] | [MENTION=8742527]thewanderinganon235[/MENTION] | @blushad0w | [MENTION=3472630]SHKaminski[/MENTION] | @elpoblano | [MENTION=7958411]Xinto[/MENTION] | [MENTION=9546252]lovaduck[/MENTION] | @DB126
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Yeah, I updated to the latest (dirty flash) from 10/6 and running MagiskHide props config and everything is working this time. I'm on 12/28/17. I am running without issues... I downloaded Disney+, no crashing. I havent had a crash yet.
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
just an fyi don't replace the TWRP recovery menu with stock recovery or you might have to jump through hoops to root or get a custom rom again

I don't get why people want Gboard when AOSP keyboard its just about the same but without phoning home all the time. it even has a hidden "activities" menu that lets you change settings such as theme
[Fire HD 8 and HD 10 Original Android Development] DB126:
No guide but looks like others have addressed the question. I simply restore the last backup (image) made in TWRP. Makes it easy to toggle back and forth between ROMs.

Like most stock ROMs you'll need to toggle (disable) a few things to get the best out of the environment. I won't detail those here for FireOS as this is a Lineage thread. The generic procedure is to observe what apps/services are consuming 'excess' (operative word) resources and decide if you want/need the functionality provided by that app. If not disable with a tool like SD Maid. Don't go crazy out of the gate; it's easy to form a negative impression if you disable/delete a bunch of stuff at once and can't isolate where the problem is should things go wrong.

The one item you'll want to tackle right away is OTA updates. Simply rename the file 'DeviceSoftwareOTA.apk' to something like 'DeviceSoftwareOTA.bak'. Volla, no more OTA shenanigans. Or use the Amazon Toolbox to disable.

FireOS cleans up nicely and is optimized for the hardware/kernel which none of the custom ROMs are for this device. That said, Lineage is quite popular and is my go-to choice on many devices when the build is mature/stable. Really boils down to personal preference and what you are willing to put up with as nothing is perfect.

Good luck. Ask questions outside this thread if FireOS oriented. Lineage Qs should remain here.

---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------

There is extended functionality/settings in Gboard such as long press duration and clipboard history that have yet to be ported to AOSP keyboard. If you don't use/care about those features then AOSP remains a fine choice IMHO.

---------- Post added at 05:15 AM ---------- Previous post was at 04:58 AM ----------

FireOS (v6) itself isn't excessively laggy. It's the preloaded apps and services that suck the life out of some devices. Kill the major offenders and FireOS is just as snappy as most custom ROMs. BTW, that's not a pitch for Amazon's heavy skin; you either like or dislike the FireOS metaphor. But the ROM itself is not a native pig as claimed by some. This is true all the way back to v3 based on Android Jellybean. Unfortunately, v3/v4 (and to a lesser degree v5) had a number of underlying deficits that made them quite distasteful when paired with Google components. On those devices a custom ROM like Lineage was all but essential to have a favorable experience. My favorite was Fire Nexus; lean, mean and highly customizable w/Xposed. Everything else felt bloated.
[Fire HD 8 and HD 10 Original Android Development] mostlydave:
I was experiencing Audible crashing on start, but installing and logging into the Kindle app fixed the problem.
[Fire HD 8 and HD 10 Original Android Development] SHKaminski:
Logs for Apps Crashing Due to System DPI Settings

OK. It took a few days, but I did the tests of the listed apps at each DPI and recording the logcat for each in the attached zip. I summarized the results in grid in the attached image.

14.1-20191216

GApps stock for Android 7.1

Magisk 20.1

Please let me know if any other info would help.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Nice work! Exactly what was needed. We believe we might be over a hurdle and can start testing specific cases so perfect timing on this info. Happy New Year!
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Confirming that the 01/02/2020 release fixed the Chrome crashing issues due to dpi. Reset Developer Options > Smallest Width to 800 and then changed Accessibility > Display Size to Larger, Thank you for the hard work! Happy New Year :D
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Thanks for testing. Also an issue from previous builds that I'm hoping *might* be also fixed with this build is: "wifi/bluetooth on wake, wifi can't authenticate until BT is turned off OR airplane mode is toggled"

With wifi and bluetooth on (BT not necessarily connected to anything), please let us know if after a week of use any of you have any issue with wifi not being able to authenticate on wake.
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
I use a BT keyboard consistently with my tablet, so I was running into the issue a lot when switching between wifis (work vs. home). I can monitor it over the next couple days and let you know what I experience. Previously, I would almost always have to reboot my tablet to connect to wifi when changing from work to home or vice versa.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
2020-01-02 build is up if you haven't already flashed it.

Dirty flash seemed to work aok for me from Oct6th build, and also the Dec16th build. Additionally no OMXfix is needed anymore as all streaming apps we've tested worked including Disney+. We now recommend the 'aurora store' method for Disney+ as it seems to work every time [MENTION=8742527]thewanderinganon235[/MENTION]. All mentioned google apps, nytimes, flipboard, were tested at all dpis.

Note: On clean flash, Disney+ shows a black screen when playing. A one time reboot fixes it for some reason.

Testers: Please test Vanced YouTube 60fps and other non-standard streaming cases.
[Fire HD 8 and HD 10 Original Android Development] quikt:
Disney+ was doing the black screen to me on the October build jfyi. Just started happening.

---------- Post added at 08:37 PM ---------- Previous post was at 08:16 PM ----------

Dirty flash went good no crashes so far thanks gents!
[Fire HD 8 and HD 10 Original Android Development] SHKaminski:
So far, so good. Apps are working at various DPI settings. I haven't tried everything at every DPI yet, but it's off to a good start!

Thank you!
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Flash newest 01-02-2020 build. I didn't have issues running stock play store Plex in previous builds, but we've done extensive testing on this most recent build and it's running well.

On suez however that is an issue that I haven't been able to work around, so I'm mentioning that in case you might be in the wrong thread. Otherwise, flash newest and profit!
[Fire HD 8 and HD 10 Original Android Development] xantiux:
So I just found this, and am loving it! It's silky smooth. Everything seems to work - Bluetooth, WiFi... Also, it reads microSD cards formatted as exFAT. Thank you so much!
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
just ran into the BT and wifi issue again. This time, wifi said "Connected No Internet", so I turned off wifi and turned it back on. Wifi would not connect, so I was forced to restart my tablet. Before, it would not say "Connected No Internet", instead it would just fail to connect entirely.

---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------

This is was done using a dirty flash
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
If the problem went away I would have been surprised, but I was hoping! Some background on that issue is that it is a combination issue between wifi and BT. Turning BT off should allow wifi to do it's thing after a few seconds. Alternatively I found the fastest way to get back on track was to toggle airplane mode on then off. You shouldn't have to reboot in my experience.

If you find this to happen consistently when doing a specific thing (like going from wifi to wifi with something connected over BT) then let us know how to recreate it. That's gold in the troubleshooting world (consistent bug) because we have a good chance of fixing it.

No need to test on clean flash, it's better that you are able to get the issue to happen on demand consistently so we can come up with a fix. Thanks!
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Almost always happens while having BT on and switching wifis. Might not always happen when moving from wifi_1 to wifi_2 but is almost guaranteed to break when going wifi_1 -> wifi_2 -> wifi_3 or wifi_1 -> wifi_2 -> wifi_1
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Is the tablet off between the switching of wifi networks, or does this happen when switching between wifis at a single location without time for the tablet to lock or sleep?
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
This scenario only really happens when going to and from work, so the tablet definitely locks / sleeps while making the wifi change
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Just had the issue happen with a totally different scenario. BT and wifi were on, tablet was asleep for a long time. BT keyboard wouldn't wake up the device, so I manually woke the tablet. I saw tried turning off / on BT to repair the device. At this moment both wifi and BT cut out and did not work. After turning on / off airplane mode, everything was back to normal. Is there any way for me to easily pull device logs?

---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM ----------

100% different note that I figured would be worth mentioning, installing the newest magisk update AFTER upgrading to the newest Lineage release caused a soft brick. I dirty installed Lineage on top of the soft brick and this fixed everything while keeping magisk up to date.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Were you sure to install/update magisk via TWRP? Using our unlock method, we must use TWRP for everything magisk install/update related.

As for BT/WIFI no logs needed at the moment, I should be able to test this if it happens consistently. Thanks!
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Sounds good on the logs. For magisk, I installed using the in-app installation method... probably should have checked the magisk install method here first XD
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Yeah installing or updating anything magisk related in-app will do that. Always download and flash in TWRP :svetius:. This is specific to our devices, on other devices in-app might work fine.
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
google play movies

Hi. I use Netflix, YouTube, Prime Video and Hulu with no issues very happy. However I can't get video on Google Play Movies, only audio. I did a quick search but can't learn anything about my issue. Can someone aim me in the right direction? thanks
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
That is one we hadn't tested. I'll take a look.
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
I appreciate it a ton. You guys rock.
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
just tested out the new update and apps such as opera no longer crash and even video streaming in browsers has been fixed
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
The Google Play Movies interface is soo confusing. To watch anything it wants to install Crackle, DisneyNow, Tubi TV, WatchABC, Hulu, Netflix... looks like anything I have installed and others. This appears to be some kind of video aggregator? Anyways, all trailers are playing correctly. What steps exactly should I take to see this issue? I'd rather not pay $1.99 per episode to test Google Play Movies :eek:
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
That is so weird. I just watched a trailer with no problems. But the movies I've purchased and are in my library still will not show video only audio. If there is a log that would help let me know. She has over 50 movies on there. We just got angry birds 2 man :laugh::cool: I'm using the October rom with headphone fix. If you want to pm your Gmail address i can add to my family library to test it.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
No family login required but thank you for the offer. I purchased one of my favorite movies, Penguins of Madagascar because I felt bad they've never received any money from me. Tested and libMtkOmxVdecEx.so from Ziona's OMXfix makes it work, but I don't yet know if this would break any other apps. I'll test and get back to you, but wanted to let you know that it's possible :svetius:
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
I appreciate it thoroughly. we just watched that movie last weekend on DVD. freakin' hilarious
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Here's a fix, no flashable uninstall but it does back up the original files as vendor/lib/*.orig. I re-tested all of the video streaming apps and didn't see any negative effects. This might be rolled into the next release so long as it still works with YouTube Vanced. If someone running Vanced could test, I'd appreciate it.

karnak_LOS141_googlemovies_fix_754.zip

Files from [MENTION=9906981]Ziona[/MENTION] OMX fix: libMtkOmxVdec.so & libMtkOmxVdecEx.so
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
I flashed Ziona's OMXfix and can confirm Google Play Movies, Hulu, Prime Video, YouTube and even PBS Kids Video app all have picture and sound. After a reboot everything still worked. Thanks a bunch :highfive:

---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------

I just saw this after I posted my post. :o
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
* Note the patch above is only using 2 of the 15 libraries that make up the entire "Ziona OMX fix". If we used the entire OMX fix, it's possible it would leave some things broken. YouTube Vanced has been reported as having issues when using the full OMX fix, but I haven't tested others.
[Fire HD 8 and HD 10 Original Android Development] jonpjingleheimler:
I used the entire OMX fix from the thread. I use the regular YouTube. I didn't see your post until after I found his thread.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
No worries my dude, so long as the apps you use on the daily work then do what works for you. I also don't use Vanced YouTube so I'm in the same boat. Honestly when it comes to testing it's better to have some people running one or the other so they can report on things. Happy we could get Play Movies working!
[Fire HD 8 and HD 10 Original Android Development] Ziona:
The two earlier omx libs mentioned from you are the decoders for basically mpeg4 , h263 , h264 / avc.secure , hevc , vc1 , vpx , vp9 , divx , dixv3 , xvid , s643 codecs. You didn't add the encoder omx lib for those above.

Just about all the others libs except OMX core are for different audio codecs like flac , alac , gsm , mp3 , adpcm.dvi , wma an so on decoders with also some of their encoders .

All OMX libs tested an worked also using YouTube vanced .