yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Thank you [MENTION=9906981]Ziona[/MENTION]! I was only cautioning because of a single post by [MENTION=7958411]Xinto[/MENTION]. I'll quote it here and maybe he can give more specifics. I'll note that 60fps on these tablets is a fringe test case, but to each their own. We had a bad release recently so we're doing our best to minimize odd issues, otherwise I'd just promote the complete OMX fix every time.
[Fire HD 8 and HD 10 Original Android Development] Ziona:
Don't know if he tested before the omx patch & after because with my knowledge you mainly need this patch for playback with YT etc. to begin with.

I think also that maybe an incomplete test statement solely because what we all experienced is this lineage 14.1 on many if not all fire tablets can't play 720p @ 60fps . The ROM hardware acceleration an or kernel sames to not be fully optimized for it like previously before on 12.1 or stock .
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
only issue I find with the codecs is they seem to over use the cpu in some apps such as xfinity or browsers. this was fixed in the newest update but it came back when I tried to test the OMX patch.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
I wouldn't engage, no offense. Expectations are hard to manage, and use cases can be fringe. Also some compare to what they were able to do with rooted stock, sadly. What is normally the case is if in one build someone is able to do a fringe use case successfully, regardless of whether it *should* work, they often expect it will continue to work in future builds (which I don't fully agree with, but I give it a college try to support). I don't mean to be harsh about expectations, and I know a lot of you are just being helpful and providing testing info, which is appreciated! Hey if we can get everything working, even if it takes some workarounds, why not try.

[MENTION=9906981]Ziona[/MENTION] I'm honestly amazed these shared libraries are even able to be used on soo many different devices, on 12.1 *and* 14.1. I wouldn't hold it against the libraries to have different effects on different devices, different builds, kernels. Having this many options of usable apps for video is only because you found em in the first place.

Edit: I can't help myself, going to try out Vanced YT ;)
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Confirmed in both YouTube and Vanced YouTube - if you are in need of OMXfix for a specific app to work, you will lose 720p 60fps in YouTube. Thank you for the report [MENTION=7958411]Xinto[/MENTION]!
[Fire HD 8 and HD 10 Original Android Development] quikt:
Disney+ black screen fixed itself today. Did not update app or make any changes so assuming its an issue on their end.
[Fire HD 8 and HD 10 Original Android Development] Ziona:
Each one teach one we're all here for learning not hating .

Yes different devices different outcomes.

If you are successful in having YouTube with 720p [MENTION=7825661]60fps[/MENTION] in this built before flashing omx fix me being u i would remove the libMtkOmxCore. so within the zip an use your original one then test again or add just that file back if you already flashed . I test files one by one if need be .

Also if you happen to need the so called nougat OEM blob/libs with most all the original mtk .so files for video & audio let me know.
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
something that worked for me with that issue is turning off VP9 codec and Exoplayer v2 which are both found in Vanced settings
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
For sure I agree. So I tested before and after replacing stock libMtkOmxVdec and libMtkOmxVdecEx only for this one use case for Google Play Movies. When using them to get Google Play Movies to display video (instead of black screen with audio), I found that replacing only libMtkOmxVdecEx resulted in video, but initial video quality would be very low until HD stream kicked in (during the initial automatic quality detection phase, Netflix and Prime are good examples). When also replacing libMtkOmxVdec, initial video quality was as expected, SD but not abysmal. So the only 2 libraries I was using to get it working as expected were libMtkOmxVdec and libMtkOmxVdecEx. You mentioned those two shared libraries essentially make up the entire decoder functionality so would be out of options, though I'd definitely be up for trying more recent suez blobs from stock. Otherwise if users need to use the current flashable OMXfix (or even just parts of it) to get video working on an app, then they can't eat their cake too at 720p 60fps in YouTube. Not a big deal imo.

I'm up for additional testing though.. will grab newer blobs from suez OTA. What version FireOS are these libs from in the flashable zip?
[Fire HD 8 and HD 10 Original Android Development] Ziona:
That's the thing i decovered many omx mtk blobs are kinda universal for that (soc) chipset regardless of the mtxxxx versions , few can work from even higher rom versions for example say oreo omx libs may work for like nougat . I think they were from my Samsung or Alcatel , I had them a while can't remember the exact mtk device , I used them to fix a few devices video on custom ROMs an also are fire tablets like Ford, Austin , Suez etc . their very useful am glade I tested them an found that out .
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
for me back with I first tried the OMX fix both options were turned on and both 720p 60FPS and 1080p 60FPS were crazy choppy. those options seemed like the only two that could effect it so I turned them both off force closed vanced and when I opened it back up both 720p and 1080p were working smoothly. idk what else could have fixed it for me if it wasn't those two options

EDIT: just tested it right now with the same results super choppy with them on and super smooth with them off
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
I'll PM, very interesting you're able to get it to work.
[Fire HD 8 and HD 10 Original Android Development] Ziona:
[deleted]
[Fire HD 8 and HD 10 Original Android Development] glate:
Post title needs an update again :)
[Fire HD 8 and HD 10 Original Android Development] gregd72002:
Anyone managed to get wifi 5ghz to work? Mine somehow does not find any 5ghz networks.
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Yes, I use 5 on every wifi
[Fire HD 8 and HD 10 Original Android Development] gregd72002:
Is there a special setting that needs to be activated? I'm on the current build 20200102 and defo it is not showing any 5ghz networks. Got other mobiles and computers nearby and they are happily connected to the 5ghz one.
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
I didn't have to do anything in particular at all. My setup is Lineage@2020-02-01 and I also have Magisk installed (follow OP's instructions on properly installing Magisk to avoid soft bricking your device). Other than that, it might be a router issue. Login into your router and check what channel 5gz iis set to. If it is set to "Auto", try setting it to 165. Remember all configuration changes you make in case it causes other network issues so that you can revert easily (screenshots are a smart idea).
[Fire HD 8 and HD 10 Original Android Development] ermacwins:
So hows the rom guys? I have the Fire 8 to the old man but stock is really slow so thinking of flashing this rom.
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
reading through the posts on this forum should give a good idea of where the ROM stands
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Device failed to connect to my BT keyboard today. Toggled airplane mode and restarted, neither would allow the device to reconnect to the BT keyboard. Had to forget the device ad reconnect. Nothing in particular comes to mind about what could've caused this on my user end
[Fire HD 8 and HD 10 Original Android Development] Skilling:
Hey! Great work you're doing here!

What about Fire HD 8 7th generation (2017, I think)?

I have the Kids Edition, but Amazon's parental control and apps support is very limited, would be amazing to go to a stock Android, and hopefully take advantage of Family Link.

Thanks!
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Since it doesn't have unlockable BL there's no development. I'm trying to compile cm12.1 for it, but I can't promise anything.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Update:

I have tried to get the audio to work but the patches wont work. I'm thinking of making a patch zip file to make audio to work.

[MENTION=7104332]k4y0z[/MENTION], I have provided you a logcat above and I see that there is something wrong with the audio codec. And the video codec too. [MENTION=5749760]ggow[/MENTION] is there anyway that I can find some audio and video patches. I already used the mediatek nougat patches.
[Fire HD 8 and HD 10 Original Android Development] ggow:
You don't need any patches to make audio work. The device tree you are working from isn't setup correctly. Start by making it more like a standard aosp or lineage tree then building it up from slowly from there. There are a lot of mediatek libs your relying on which are not needed.
[Fire HD 8 and HD 10 Original Android Development] troy_77:
Finally got my new tablet today and got this installed without any issues. I mainly use these as a wall mounted touch screen to control lights and other home automation. Having this instead of Fire OS is absolutely perfect now! There was always a few tradeoffs getting a cheap tablet but dealing with limitations of Fire OS and this my friend, resolves all those issues! :victory:

I really can't thank you (and everybody else who made other parts like unlocking possible) enough! Thank you again!

If this makes its way to the HD 10 I'll be looking forward to try it there as well
[Fire HD 8 and HD 10 Original Android Development] oscar13sd:
In case this is useful information, I am able to get video (no audio) to work using MX Player.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
What I'm going to do is the thing for the audio is that I can put amazon's audio policy libs and other stuff to make the video work. I don't know why that there is something missing to make the video work. Also im going to to release the june security patched rom today.
[Fire HD 8 and HD 10 Original Android Development] glate:
Just wanted to give this thread a bump as it’s very exciting stuff and I’ve been checking back often. Thanks again for all your hard work!
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
We still working on it. It's very hard to solve the audio and OMX issue and we need expert help.. Please, be patient..
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Ok, we definitely need help from some expert ... [MENTION=7104332]k4y0z[/MENTION] [MENTION=5749760]ggow[/MENTION] ..

We have done everything but the audio still does not work.

This is the last thing we have achieved (bootlop):

29 20:33:39.710 1064 1064 W EffectsFactory: loadLibrary() failed to open /system/vendor/lib/soundfx/libswdap.so 06-29 20:33:39.710
1064 1064 W EffectsFactory: loadLibrary() failed to open /system/lib/soundfx/libaudiofx.so
06-29 20:33:39.710 1064 1064 I DlbDlbEffect: getDescriptor(uuid=9D4921DA-8225-4F29-AEFA-39537A041337, pDescriptor=0xf6934600)
06-29 20:33:39.710 1064 1064 I DlbDlbEffect: getDescriptor() Returning descriptor for DAP
06-29 20:33:39.711 1064 1064 W EffectsFactory: loadEffect() could not get library ds
06-29 20:33:39.711 1064 1064 W EffectsFactory: loadEffect() could not get library audiofx
06-29 20:33:39.711 1064 1064 I BufferProvider: found effect "Multichannel Downmix To Stereo" from The Android Open Source Project

That's the full logcat:

https://drive.google.com/file/d/1-2bOrNKYk8wtb4kmL42_ibWuqQg6Zg8Z/view

And sorry for bother you guys.

Thanks.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
[MENTION=5749760]ggow[/MENTION] [MENTION=7104332]k4y0z[/MENTION] I have tried to get the audio libs and the video libs to work like I have tried some patches from other GitHub. And what's taking me alot of time because I'm adding the mtk_aosp_echancment lines https://github.com/488315/mt8163-frameworks-av. It's wasting alot of my time but I don't know it will work or anything. What is the main cause of this. I've tried to clean up the vendor and rebased my tree..... I think I'm not a successful developer because I'm not really an expert. I have learned alot but not by coding. Is there anything I can do about this? The encoder tab in device info hw is not showing anything too.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I haven't had time to look into this. I don't understand why your having issues like this with audio. On a cursory look at the structure of the libs etc in the stock ROM. It should be possible to get Audio working by selecting the right libs from stock and building the right ones from aosp/lineage.

I am working on Fire 7 and Kindle HDX stuff for a while then I'll take a look at building for karnak.
[Fire HD 8 and HD 10 Original Android Development] ryulian:
This is amazing. Thank you very much.

I installed your development on my hd8 successfully.

It works very fine except audio.

I'm waiting fully working version.

Thanks again!
[Fire HD 8 and HD 10 Original Android Development] Danvep:
I am trying to download this version of the os but the link says item not found. How do I download it?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I fixed it.. you can try now
[Fire HD 8 and HD 10 Original Android Development] Danvep:
Do you think the audio/ video will ever be fixed? Do you think this will actually become a good os for the fire hd 8?
[Fire HD 8 and HD 10 Original Android Development] DB126:
Lol.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Kernel sources provided by Amazon are incomplete so solve the audio is th most difficult thing. We still trying but it can take a long time to solve it.

And please no more ETA.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
[MENTION=5749760]ggow[/MENTION] [MENTION=7104332]k4y0z[/MENTION] finally we got audio and video working XD.

We will upload in a bit.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Good work! :good:

BTW, you are building 32-bit are you?

Why not switch to 64 bit?
[Fire HD 8 and HD 10 Original Android Development] Xinto:
A logcat would be useful in this scenario
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Mind quickly explaining how i can get a log cat? I would love to send one
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Connect tablet to a pc with adb installed, 3nable USB debugging on tab and on your PC type

adb logcat > logcat.txt

This will save logcat in Documents directory on your PC

Make sure to take logcats straight after thing happens, because on restart logcat is "restarting" too
[Fire HD 8 and HD 10 Original Android Development] gregd72002:
> adb shell
$ logcat

---------- Post added at 07:19 PM ---------- Previous post was at 07:11 PM ----------

I continue to have poor Wifi issues.

a) 5ghz not showing - minor issue for me [RESOLVED - it turned out the channels offered by my AP are quite different to the channels on the tablet]

b) when connected to 2.4ghz, it occasionally stops to transfer packets

The logcat shows:

01-08 19:09:02.397 20017 20017 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private commands, error msg: Out of memory
01-08 19:09:02.413 555 20032 D DhcpClient: Broadcasting DHCPDISCOVER . [many times]

Eventually it connects. Or sometimes I have to do a reboot.

When I get the Wifi errors I run meminfo:

adb shell "cat /proc/meminfo"
MemTotal: 1406136 kB
MemFree: 77220 kB
MemAvailable: 544244 kB
Buffers: 9656 kB
Cached: 522540 kB
SwapCached: 13000 kB
Active: 444856 kB
Inactive: 438308 kB
Active(anon): 306184 kB
Inactive(anon): 58048 kB
Active(file): 138672 kB
Inactive(file): 380260 kB
Unevictable: 3544 kB
Mlocked: 256 kB
SwapTotal: 262140 kB
SwapFree: 146900 kB
Dirty: 8 kB
Writeback: 0 kB
AnonPages: 353012 kB
Mapped: 223340 kB
Shmem: 9976 kB
Slab: 69024 kB
SReclaimable: 24900 kB
SUnreclaim: 44124 kB
KernelStack: 19680 kB
PageTables: 21904 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 965208 kB
Committed_AS: 30195888 kB
VmallocTotal: 260046784 kB
VmallocUsed: 97532 kB
VmallocChunk: 259858128 kB
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Are you using latest build(January 2 build)?
[Fire HD 8 and HD 10 Original Android Development] gregd72002:
Yes
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Hmm, I flashed this build today and haven't had any problems with Wi-Fi. Make sure that other devices work fine, if they don't, you have to blame the router or even ISP
[Fire HD 8 and HD 10 Original Android Development] DB126:
Lineage build for this device is largely ok but has its quirks. If you opt to stay on FireOS know that it's the Amazon add-ons that make it a dog, not the core OS which is quite responsive once the other stuff is disabled. Really depends on what experience you are seeking and where you want to spend time fixing issues - red car vs blue car.
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Well, only downside here is that volume is a little low comparing to FireOS, otherwise crashes fixed, rom is fast and snappy, and biggest feature is flasheable gapps, plus some safety net adjustments and you have a 40 dollar tablet with LineageOS and TWRP. But of course, that's a personal preference
[Fire HD 8 and HD 10 Original Android Development] DB126:
Yep - love Lineage and recognize remaining issues (radios, audio and video) are minor to most and characteristic of mating custom ROMs to Amazon's quirky kernels. Penning this on a 3rd gen HDX rocking Lineage 14.1; many of the same minor issues present there as well. Same with 2nd and 5th/7th gen gizmos. Goes with the territory.

As an aside, no issues flashing gapps on FireOS (with unlocked bootloader) although the Toolbox subset is quite serviceable and easier for most to implement.
[Fire HD 8 and HD 10 Original Android Development] ermacwins:
Primary use will be YouTube and earphones need to be working. Does it crash a lot?
[Fire HD 8 and HD 10 Original Android Development] Xinto:
It doesn't crash, like no crash even at first builds, headphones work and YouTube does so.
[Fire HD 8 and HD 10 Original Android Development] Xinto:
First of all, I'm not a Dev and I can't give a fix, however I found something about HAL on Android source site

https://source.android.com/devices/tech/connect/wifi-hal
[Fire HD 8 and HD 10 Original Android Development] gregd72002:
Just to add, the problem seems to be affected by the [setting->Wifi->Configure WiFi->Keep Wi-Fi on during sleep] set to Never or Only when plugged in.
[Fire HD 8 and HD 10 Original Android Development] Xinto:
I now see why I don't have any errors, I keep wifi on during sleep. Try with that setting and reboot.
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
the audio is only lower due to the FireOS using Dolby by default (though locked to only a few apps while others will still be extremely low) while LineageOS uses "AudioFX" which is subpar in comparison. one of the first things I did was removed AudioFX and "CM Audio Service" and installed Dolby Atomos which sounds even better than Dolby on FireOS
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Hmm, I couldn't find Dolby Atmos, only found DDP. If you have one, would you mind sharing a link?
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
https://xdaforums.com/crossdevice-d...-themes-and-apps/dolby-atmos-devices-t3320468

thats the one I have installed you need to at least freeze the other apps though or it won't work as they will override it
[Fire HD 8 and HD 10 Original Android Development] marras:
Wow that worked surprisingly well! Thank you
[Fire HD 8 and HD 10 Original Android Development] astrod:
Dumb question: what's your favorite method for disabling AudioFX? Thanks!
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
I use debloater in magisk to avoid breaking safetynet
[Fire HD 8 and HD 10 Original Android Development] ermacwins:
Thanks. The only way to unlock the bootloader is with linux right?
[Fire HD 8 and HD 10 Original Android Development] DB126:
Stability has never been in question. To the best of my knowledge early deficiencies that may have degraded your experience (given stated usage) have been fully addressed.

---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------

Let's just say it can't be unlocked (at this time) using Windows. Best best is a Live (bootable) USB drive...sometimes referenced as a LiveCD. Windows subsystem won't do it; VMs are a PiTA unless experienced with USB interface settings.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Yes, but for one-offs like this I just install VirtualBox and grab an Ubuntu image from osboxes.org. Boot into it, run the commands in the instructions. The one tricky thing is you'll need to have it take over the USB connection when your tablet is plugged in. You'll do this by clicking the USB icon in the bottom right of the vm and checking the checkbox next to the recognized Amazon/Mediatek device to take over. There are times when you'll need to plug into different USB ports to get it to take over. If you run into issues this wouldn't be the thread to post to though, you'll want https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-8-2018-karnak-amonet-3-t3963496
[Fire HD 8 and HD 10 Original Android Development] DB126:
While VMs are great I think creating a 'Live' (bootable) USB drive is easier for one-offs and (most importantly) devoid if messing with quirky USB interface nuances. Procedure below; choose the method that best fits your personality and technical skill set.

https://tutorials.ubuntu.com/tutorial/tutorial-create-a-usb-stick-on-windows#0
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
I used VMware Workstation and didn't have to do anything like that it was just a simple plug in and it was detected fine

its always funny seeing you trying to demean other peoples posts with info that takes even more work to do or assuming people have a usb drive to do it in the first place (or wanting to waste money on such) not to mention assuming they want to mess with boot time loading of a usb drive which doesn't always work the same on every computer. your method is actually much less convenient than just using a virtual machine
[Fire HD 8 and HD 10 Original Android Development] Xinto:
Having a virtual machine gives you a risk of permanently bricking device as there's a chance that not all payload packets will be sent to device. Everything you do is at your own risk.
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
if this was actually a reality then with the amount of devices I've unlocked I should have had some bricks by now this sounds more like a scare tactic
[Fire HD 8 and HD 10 Original Android Development] Xinto:
If it worked for you, that doesn't mean it will work for everyone and for other situations.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Thread to continue this pleasant conversation in:

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-8-2018-karnak-amonet-3-t3963496
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
I'd love for you to explain how its even a possibility beyond what scare tactics you might have heard
[Fire HD 8 and HD 10 Original Android Development] Xinto:
You can check out the thread linked above you and see some users who bricked their devices with VM. Post something there if u have questions
[Fire HD 8 and HD 10 Original Android Development] deathblade200:
user error vs virtual machine aren't the same the usb is literally mounted to the virtual machine through the host as a guest but I'll leave it as its not worth arguing about
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
[MENTION=3946657]xanthrax[/MENTION]