yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Edit: I went into exact detail.XD

I won't be going into exact detail, but this should get you on the right track if you haven't done it before.

If 100% stock, I would follow the following method for unlocking and installing TWRP in one shot: https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639/

From there make a backup in TWRP of whatever stock setup you have if needed for later. Then in TWRP wipe system, data, cache and install ("flash") the 14.1 build zip from the start of this thread. Install the recommended google apps from the first post [5th post? arm64 7.1 nano], boot it up and get the basics set up, maybe install an audio streaming app, streaming video app for testing audio.

Headphones, when plugged in, should have no sound at this point.

Reboot to recovery ("TWRP") and make a backup of this minimal installation of LOS14.1 and then flash the headphone fix zip that I send you over PM (or possible it'll be ready to release by then.). If all goes well, you'll have LOS14.1 running on your hd10 with headphones working.

The testing involves trying to break it. Minus the issues that are listed under "Known Issues" in the release page of the fix, you'll be trying all different combinations of plugging it in, unplugging, trying different apps, rebooting with headphones plugged in, unplugging them while playing audio, trying headset with mic, trying normal headphones, trying bluetooth speakers and headsets, turning Bluetooth off while playing audio while having headphones plugged in to see if they fall back to headphones correctly... try to make it do something unexpected. PM me with questions, happy to help.

Bonus would be after that 14.1 testing to wipe system data and cache, then flash LOS 12.1 and do the same. Install recommended google apps, minimally set up, backup then flash the headphone fix and try your best to break it then report back.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
[suez] alsa_trigger - headphone enabler

https://github.com/workit247/suez/releases/tag/v1.0-beta

Flashable zip, using alsa_trigger method customized specifically for SUEZ lineageos 12.1 & 14.1 builds to enable headphone jack. Flash to install, flash to uninstall.

Note to testers:

Nothing functional was changed since latest v.04-alpha pre-release. Also THANK YOU for your help.
[Fire HD 8 and HD 10 Original Android Development] BeniS98:
Flashed it now in TWRP and it works like a charm. Excellent work spelcheck!
[Fire HD 8 and HD 10 Original Android Development] toidimaet:
Thanks Spelcheck, excellent work. Checked BT as a sink and headset (made brief recording), everything working as intended alongside headphone jack on 14.1.
[Fire HD 8 and HD 10 Original Android Development] sga999:
Great job, Spelcheck! Your efforts and results are greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Anyone? Anything?
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Try com.netflix.mediaclient_4.16.4_build_200217_minAPI19_maxAF, that's what I'm using on all my suez and karnak. Correct, it won't show up in play store without changing the "signature/fingerprint" of the device, as amazon has their own version that's in their app store. The version apk above was the last version that I found worked.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
That's the one I have installed but it doesn't have the download feature.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Common problem w/custom ROMs. You'll need to change device fingerprint with Magisk props module (or similar) and possibly take additional steps to obfuscate device characteristics such as root. It is a cat & mouse game that requires constant tweaking. I tire of such antics and choose to stream with inexpensive stock devices such as the Onn 8 that have a clean Android build. Problem solved.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
And how would I do that?
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Install it via Magisk, open a terminal emulator, run "props", and follow the instructions.

Choose the fingerprint of known devices that pass these checks. I typically go with the Nexus 7 2012 for my fire tablets.
[Fire HD 8 and HD 10 Original Android Development] DB126:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Read-up on module use. I typically find Nexus 7 or Samsung devices work best. Good luck.
[Fire HD 8 and HD 10 Original Android Development] dooderooni:
Works perfectly for me, great work spelcheck :good:
[Fire HD 8 and HD 10 Original Android Development] bsnipes:
I am still on 12.1 but the below works on it and lets me download:

https://apkpure.com/netflix/com.netflix.mediaclient/download/31696-APK?from=popup/version
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Without fingerprint spoofing on 14.1, I get the 'This app is not compatible with your device' error.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Weird. Works perfectly here. I'll take a look at it. Do you happen to use the live display settings?

Edit: I was using 'Lux Auto Brightness pro' up until I made that fix. I haven't needed it since.
[Fire HD 8 and HD 10 Original Android Development] bsnipes:
Good to know. I guess I will stick with 12.1 for now. I wonder if any of the other versions will work: https://apkpure.com/netflix/com.netflix.mediaclient/versions
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Is there something I'm missing here? I set the device fingerprint to Nexus 7 2012 WiFi, and rebooted, and I still don't see Netflix on the Play Store. I also get the "this package may be corrupt" error when trying to install a newer one from APKMirror/APKPure.

EDIT: Changed it to Nexus 9 WiFi, this time with the su command first. Passes SafetyNet check now. Can't see if it's certified because that's not showing in the Play Store settings right now for some reason. Netflix listing on the Play Store still says it's incompatible. Buuuuuuut.... I CAN install the app from APKMirror, but when I launch it it says it's not compatible with my device. So it looks like I'm stuck with 4.16 or whatever version that is. Which blows. Can't download any shows with that version.
[Fire HD 8 and HD 10 Original Android Development] AJS1986:
You're probably best downgrading to 12.1 if you want to download on Netflix
[Fire HD 8 and HD 10 Original Android Development] TheDevil259:
No, I don't use live display nor any apps that might interfere with adaptive brightness.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I'd really rather not. For one, that's an older version of Android, which some of my apps don't work with; and two, that requires me to wipe my device and start all over again. I'd rather upgrade to a newer Android version on this tablet, if that ever happens any time soon.

So far only v4.16 works, and that SHOULD have the download option, as the earliest version to have it was v4.12. Supposed to have a download quality setting and a storage location selector. Yet this is what my options menu looks like. Pretty featureless.
[Fire HD 8 and HD 10 Original Android Development] DB126:
While I do not have any explicit guidance I would encourage lite tinkering with fingerprints and permissions until you find a combo that works. Lack of Play Store certification is a big waving yellow flag. That said, your experience is typical for many devices with custom ROMs. One reason why I always keep an stock/unrooted device at the ready for streaming and (some) financial transactions. I can usually work around the egregious restrictions with time and effort (hence the encouragement to keep tinkering) but I tire of the continuous cat-and-mouse game and prefer to actually use my devices vs manage them. Good luck.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Well, I did manage to get the device certified now, but the device is still incompatible. I believe this might be because of the Android version being 7.1.2. The newer versions of Netflix don't support Nougat or below.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Not so sure; there is no indication Netflix 7.3.6.x is unsupported on Nougat (Android 7.x). Minimum/target SDKs are 21 and 29, respectively. My guess is other prerequisites are missing/invalid.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
It states on this help page, where you can download the only supported version for Nougat:

Implying that newer versions don't support anything older than 8.0 (Oreo).
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
I haven't found a version of Plex or Hulu that work as expected, so I'm on 12.1. I get your frustration, but I think a lot of us are in the same boat. I don't want to spam the thread, but that being said if you know of a version of Hulu and Plex that work without issue on 14.1 suez, tag me heh.
[Fire HD 8 and HD 10 Original Android Development] DB126:
My interpretation is the older build only works on the range of builds cited and perhaps is more tolerant of deviations in device configuration than newer builds. I'll test that theory later today (if time permits) by trying to download the new build onto a fully stock moto phone running 7.1.2.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I noticed in the permissions folder some of the camera permissions are missing as well as proximity and light sensor. I added all of the camera permissions available as well as the proximity sensor and various other ones. I also didn't delete the data from lux auto brightness. And sense the sensor or at least auto brightness was not functioning at the time it used the camera as a base for brightness. maybe if I were to take a guess I would say it had to do with those permissions being present and allowing lux auto brightness to use the camera (front facing if I recall) for the light sensor. that's about the only thing I can think of as all of the required code inside the framework and settings is already present as long as the bool in framework says config_autoBrightnessAvailable=true. I also added a few more configurations that are not in the framework that I released earlier, including config_QuickSettingsEnable=true which if that menu isn't already in the settings application will put one there and add a few other configurations including auto-brightness as well. I don't know if toggling that one has any effect from the other ones or not. All I know is it's working on my device and based on those assumptions above it could be any one of those or none.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I'll do a screen record later or tomorrow when I have a chance. I was just sitting here putting my thumb over the sensors, and using a lighter in front of it, and everything react as it should. Brightness goes down when covered, brightness goes off when lighter in front of sensor. However with that being said, I don't know if it's using the camera or the actual light sensor. Nonetheless it is working.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
I just found an easy way to enable t2w (tap/gesture to wake) on suez. Working on 12.1 & 14.1. I'll see if I can make it flashable.

Add the following line to /system/etc/init.d/90userinit then reboot.

echo 1 > /sys/bus/i2c/devices/7-0038/ftsgesturewakeup

I initially got into these fire tablets for use with actiontiles in fully kiosk browser, which has a built in wake-on-motion feature. Normally people have these tablets mounted to the wall, so the power buttons aren't accessible, hence the need for the motion wake. The thing is, you can't use that feature unless you're in fully kiosk browser. So if you are using it in a way where power button isn't convenient or accessible, this will help you out. I have mine on a stand on a side table so fumbling for the power button just pushes it off the stand, etc.

Note: Though 'Support Double Tap Wake' framework config is enabled in 14.1 (visible in display settings as 'Tap to wake'), it doesn't actually do anything, with or without the mod above. I was hoping force enabling ftsgesturewakeup in addition to enabling dt2w in framework would limit wake to double-tap but that's not the case.

Enable ftsgesturewakeup for single/any touch to wake, or don't and use the power button. Again I'll try to make flashable, hope this helps a few people.
[Fire HD 8 and HD 10 Original Android Development] BeniS98:
Is somebody about to create a color profile for the screen or take the one from Fire OS? In my opinion the color temp of the screen is too warm so white pages appear pretty yellow.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Have you messed around with Settings > Display > LiveDisplay > Color Calibration? Knocking red and green down 5-10% might do the trick for you.
[Fire HD 8 and HD 10 Original Android Development] BeniS98:
That was it! Thanks.

---------- Post added at 11:08 PM ---------- Previous post was at 10:52 PM ----------

It's not working for me too. It does not change brightness even when i set the brightness to max and put my thumb on the ambient sensor and the camera after that.

But another question: Why the original framework has 23 MB of size whilst your modded one is only 8 MB small?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I'll have to upload the permissions from the ETC folder. That's probably why it works because I'm pretty sure the permission for the light sensors and the ambient light sensor does not exist inside the ROM. and I haven't done a factory reset and I didn't add those permissions in a modified ROM using any other tools. I also still mean to do a small screen cast to show that it does work on mine. Have not had time to do much I've been sick and on top of work I have not been able to do anything in this area lately. As for the size of the framework I have no idea I did not even notice. If I had to guess I would say it's whatever apktool does when it compiles the framework again. I also note that this appears to be the case with all my other modified frameworks.
[Fire HD 8 and HD 10 Original Android Development] ismael.valencia:
Hi, [MENTION=9906981]Ziona[/MENTION]. I have the same problem. I cant play videos on mx player with hw decoding, and with SW or HW+ decoding it always looks "jumpy". Is there a way to be able to decode using HW on mx player and get playback on Prime Video or netflix app? I dont really care for youtube.

thanks!
[Fire HD 8 and HD 10 Original Android Development] desidude2000:
spelcheck, thank you for carrying forward on addressing some of the limitations of this ROM while ggow is focusing (rightfully so) on his personal life. I am currently on 12.1 and the headphone fix is working well with no issues. i would love to move to 14.1, however, video playback using HW acceleration isn't exactly working despite having loaded the OMX libraries from the discussion earlier. With 14.1 ROM, 1080p playback is working on websites like Netflix and YouTube, however, clearly in MX Player and Kodi, it is insisting on software acceleration and won't honor HW acceleration. I wouldn't mind software acceleration (even if it comes at the expense of CPU cycles), however, higher bit plus frame rate 1080p video isn't playing smoothly.

As noted by a couple of other folks above, this problem doesn't exist in 12.1 ROM, so clearly there is something at play here (or lack thereof, pun intended). With your extensive experience in MTK devices, if you could kindly look into this, that would tremendously help a number of us move forward from 12.1 to 14.1.

thanks again for your contributions.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
I'd love to help more but I'm not an expert by any means with MTK or even AOSP in general.. I was able to bridge the gap with the headphones, but beyond that I know nothing about C programming and absolutely despise java. My 10-years-ago self totally gets why people would want a newer version of android just out of principle, but 12.1 is running soo well as a daily driver I have no reason to stress over 14.1. Sorry I can't help more, I would if I could!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
here are the permissions I added in /system/etc/permissions. You can skip the ones that already exist EXCEPT tablet_core_hardware.xml. You have to overwrite the existing xml. This is not a flashable zip. Also make sure you have the framework mod installed.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Would you like some assistance making this flashable? I think it's to the point where it's complicated enough that not many people will be giving this a shot. Someone got adaptive brightness working fine on Suez 12.1 with only framework-res.apk, so maybe the same type of modifications are possible on 14.1 without changes to additional files.
[Fire HD 8 and HD 10 Original Android Development] Ziona:
Am currently on a new project rite now so am away from fire tablets at this moment I have really help alot on these for now, but you can try this lil trick for hw accelerated video playback with MX player ( for your local vidz ) with a root file explorer navigate to root > system > etc an find - media_codecs_google_video.xml . change the ending (xml) to bak , reboot an test MX player . when ready to play web base videos (youtube) again just change that file ending from bak to xml again an reboot.
[Fire HD 8 and HD 10 Original Android Development] fprhqkrtk303:
I think permissions are not the problem. Did you add brightness level manually in arrays.xml in framework-res.apk/res/value?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Yes I did. And I tried for the life of me to get a screen capture of it, but I cannot get screen record to work. Any of the files that saves to the device will not be played by any of the players I have. So I will have to use the camera from my tablet on 12.1, and do a small video of the tablet on 14.1. I also went through all the other XML to make sure nothing else needed to be added. And so far as I saw that was all that it needed. I just added what was already available through the general Android source code.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
It's not really so much about assistance as I just didn't have time to make flash full zip yes I know how easy they are. If anyone wants to go and do that they're more than welcome to. But I'm pretty sure the files were already available in the permissions folder on that 12.1 ROM. And if I also recall correctly, the configurations for adaptive brightness or ambient lighting were already present in the framework. The only thing that really needed to be done was change the value from false to true.and yes you are correct they should be available without any additional changes so I'm kind of stumped on why it's working for me but nobody else. But it won't hurt to put any of those permissions in that folder to test the theory. Unfortunately none of them actually get the camera to fully function. It does have some functionality because lux auto brightness was able to use the camera as the light sensor when auto brightness or ambient lighting or whatever you want to call it was not available.
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
Did we ever get to fix the video playback issue? cause Other than that this os was great.
[Fire HD 8 and HD 10 Original Android Development] chrizzk:
here you go https://xdaforums.com/showpost.php?p=80762749&postcount=248

but on mine choppy with 1080p60 on Youtube app, so i went back to 12.1
[Fire HD 8 and HD 10 Original Android Development] desidude2000:
While above OMX libraries are useful, they still do not provide HW Video Acceleration. Yes, YouTube and Netflix 1080p works, but you can see the decoding happening in SW and CPU being utilized. Hence, this fix is not a complete fix to get playback working. 12.1 is solid with Kodi/MX player and all other players, utilizing HW Acceleration.

This is the only thing stopping me from moving forwarding with 14.1. If some kind soul could actually fix this issue, that would be awesome.
[Fire HD 8 and HD 10 Original Android Development] retora:
Hm, what use do you think the omx libraries from Ziona's post do have if not hardware acceleration? On my device with omx libraries the MX Player plays videos with HW and HW+ acceleration without problems. Also 1080p youtube-videos (in firefox or youtube vanced app) are smooth.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Install 'Codec Info' app by KN-Soft, click through the video decoding codecs and tell me which ones you think should be hardware accelerated. For good measure, do this on stock and then we can compare. That's the only way to show that you're missing something now with LOS.
[Fire HD 8 and HD 10 Original Android Development] fprhqkrtk303:
OMX patch doesn't support 1080p60 videos and MPEG-2 stream files (.ts), which works flawlessly on 12.1.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Doesn't support as in bad performance or errors out? That 'codec info' utility will display capabilities per type with framerates. If someone could click share icon and pastebin it from 14.1 I'll compare to 12.1. Possible it's something simple that could be improved on.
[Fire HD 8 and HD 10 Original Android Development] fprhqkrtk303:
Both plays with SW decoding at MX Player. Trying to switch to HW/HW+ only gives error.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
If you pastebin the codec info dump I'd be happy to take a look.
[Fire HD 8 and HD 10 Original Android Development] fprhqkrtk303:
Without Patch: https://pastebin.com/69CyEb5g

With Patch: https://pastebin.com/aKgqw9A5

Actually, fewer codecs are visible after patching the device.
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
Thanks! Also is there anyone on stock (or anyone willing to go back to stock momentarily) that could dump 'codec Info' to pastebin? We need a baseline.
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
i added both of the patches. It works great for all apps that I use. Love this. The only issue is when You go split screen there's a weird bug that hides content for firefox. Plus It feels a little slower than LOS 12
[Fire HD 8 and HD 10 Original Android Development] djdave37:
HEADPHONE jack issue

Hello

I'd like to know if today there's a way to install Lineage OS 14 on Fire HD 10 2017 with HEADPHONE JACK working ?

Thanks for your help
[Fire HD 8 and HD 10 Original Android Development] retora:
Is 'Codec Info' by KN-Soft really a reliable tool? I'm asking because in fprhqkrtk303's omx-patched example in post #474 "OMX.google.h264.decoder" and "OMX.google.mpeg4.decoder" are listed without hardware acceleration, but my MX Player plays those files with HW or HW+ acceleration. And all other codec info apps I've tested have no information about hardware acceleration, they are only listing the codecs.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Have you not read the last page or two?
[Fire HD 8 and HD 10 Original Android Development] djdave37:
Yes, i've read the 48 pages and i've understood there's something like a patch to install on Lineage 14, but this "workarround" could be erased/lost in case of OS update.

But maybe my understanding is not so good ?
[Fire HD 8 and HD 10 Original Android Development] spelcheck:
You are in the wrong thread, you're looking for "suez" not karnak.

Edit: 2017 hd10 is Suez, not Douglas.
[Fire HD 8 and HD 10 Original Android Development] djdave37:
Sorry, Can you explain what is Douglas / Karnak ?

Thanks

---------- Post added at 07:30 PM ---------- Previous post was at 06:46 PM ----------

It looks Fire HD 10 2017 is suez.

But i can't find any inventory for suez / karnark / douglas / ...
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Douglas and Karnak are the other code names for the other tablets.