yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] DragonFire1024:
All right I'm playing around with the new ROM on a spare HD 10. Just some things I have noticed bug wise: Developer options does not work when tapping on the build number. Luckily I know how to fix that. Just sideload settings database editor and Grant it the proper permission. Then open the app tap on the drop-down menu and tap global. Tap add new setting:

development_settings_enabled

with a value of

1

Or sideload terminal emulator or use ADB and type this code after getting a root shell:

settings put global development_settings_enabled 1

Developer options will then appear in the main settings menu in the section above about device.just tap it and then tap advanced and developer options will be there.

The setup wizard crashes when you select 'skip' to turn on a mobile network or insert a SIM card. And then refuses to finish even after selecting wifi. You can of course go into TWRP and disable SetupWizard.apk in priv-app by renaming it to SetupWizard.apk_ and when your tablet reboots you will have to open a root shell or settings database editor and add these:

Terminal:

settings put secure user_setup_complete 1

settings put global device_provisioned 1

Do the same if using settings database editor you just have to have everything. despite the issue with the setup wizard gaps does appear to flash quite nicely without any warnings to register because the device uncertified. At least that is the case before you sign in I have not done that yet. You'll have to scour Google but there is a build prop edit you can make that will specify the setup wizard has run. that will come in handy if for whatever reason you're screwing around with something and you need to reset the tablet.

Sound is a bit buggy. There are some delays quite a bit of the time especially when pressing buttons. The animation is a little slow it seems even after tweaking the settings and developers options.

For ****s and giggles I decided to try superuser.I downloaded the lineage extra zip that you can flash on TWRP that removes the stock superuser. But When flashing the latest version of SuperSU and version 2.76, it does not detect the boot image and aborts the flashing.

The notifications or pull downs do not center. I've seen it once on the right hand side of the screen but it mostly remains on the left side. It could be a little bit bigger as it seems to be quite a bit narrow for the amount of screen space we have. I have not tried Xposed or anything else like that yet. No complaints with the Wi-Fi as of the moment. I have not tried Bluetooth.

That's just what I noticed at first glance. But aside from those things the ROM does appear to be nice. The visual user interface however does need work.
[Fire HD 8 and HD 10 General] k4y0z:
Most likely yes, but that would be Android 5.1 so I'd rather try and get 9.0 working :p

Tapping on build-number to enable developer-settings works just fine for me :confused:

I haven't tried skipping it, but it works fine when you complete it.

Need to disable SIM-card anyway, since this device obviously doesn't have one.

Yes sound is buggy, I think it has to do with AudioEffects and likely also with the current state of CPU-consumption.

SU isn't installed by default if you don't install the lineage extra zip that installs it.

I most likely need to patch the symlinks for the partitions for SuperSU to work, just as I have done in TWRP.

It will be looking at the wrong boot-partition currently.

The notifications come down, wherever you put your finger to pull them down ;)

I think the width is default like this on Pie and I think it is fine the way it is.

As previously noted bluetooth doesn't work yet.
[Fire HD 8 and HD 10 General] Syco54645:
Do you have binary blobs for 9.0? Probably will pick up an hd10 on prime day so. Hopi g you get this worked out. Amazing how much better my son's fire7 runs with stock Android vs fireos.
[Fire HD 8 and HD 10 General] k4y0z:
No, I don't.

I have some oreo-libs from a different device, but not all of them can be used.

Otherwise stuck with the 5.1-libs.

Let's hope Amazon gives the device an update to FireOS 6 so we at least get nougat libs.
[Fire HD 8 and HD 10 General] DragonFire1024:
Weird about developer options. On another note the navigation bar on the bottom is also screwed up and blurry and pixelated. Most of the time it's scrambled. Sometimes when you go to swipe recent apps closed you can't swipe them you have to go all the way to the end and press clear all I don't know if that's standard or not. Also sometimes the appearance of those applications in recent apps are also pixelated and scrambled.

sorry I did not see the part about Bluetooth does the same also go for location services? Because even with settings database editor I cannot get them to turn on. Sounds like it could be a framework issue. Possibly missing the default package assignment but would be something like 'com.android.location.fused' as an array setting.

I like the dark mode. I think that's really neat and I like how it automatically accents the background colors. However live display does not work. So I could not toggle automatic brightness.

---------- Post added at 11:36 PM ---------- Previous post was at 11:30 PM ----------

I now believe I am clearly trying to reinvent the wheel building through AOSP directly. But I've tried the CM repo and I still didn't have any luck I will have to take some time to look over how that's formatted so I can remake the make files for it. The problem versus lollipop and all the versions of Android in terms of this device and it being mediatek, a lot of the proprietary files are not in the same places. Whereas in newer versions of Android the proprietary items are stored in the vendor area whereas on lollipop they are stored in their other various directories such as system, etc and so on. I'm beginning to think that this chipset was never designed to run on lollipop and I would not be surprised if it was never expected to. It's very possible Amazon moved all of the files on their own when building, because aside from their products, lollipop is non-existent on any device with an mt8173 chipset. All other devices with this chipset run Android 6.0 or greater. In fact from my research almost all of them run 7.0 and of course now we have a 9.0. I've only seen 1 ROM with the same chipset running Android 6.
[Fire HD 8 and HD 10 General] k4y0z:
I have listed some known working/not-working things here

TLDR: This is very alpha and most stuff is untested/not working.

The graphics glitches in navbar and recent apps are known, so far I have no idea how to fix them.

I haven't noticed any issues with swiping in recent apps though.

I don't think this device has a brightness sensor, so automatic brightness will likely never work.

BTW [MENTION=7617234]TheRealIntence[/MENTION] regarding the CPU consumption:

400%cpu 69%user 0%nice 259%sys 72%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
1104 u0_a5 10 -10 3.3G 89M 62M S 103 4.8 3:27.72 com.android.launcher3
606 u0_a20 20 0 3.3G 112M 79M S 103 6.1 3:34.68 com.android.systemui
256 system -2 -8 2.1G 18M 12M S 103 1.0 4:40.33 surfaceflinger

I think it's an issue with the graphics
[Fire HD 8 and HD 10 General] Syco54645:
I wonder how hard Oreo would be to compile. I'm sure someone will do it at some point. Worst case we can always just fall back to 5.x though if you are going to spend dev time may as well do it for the newest. If a working pie ROM gets built for this then it could be a fantastic budget tablet.
[Fire HD 8 and HD 10 General] DragonFire1024:
It should have a sensor for brightness. This has an adaptive brightness toggle, and yes it does work. I'm pretty sure it has a proximity sensor too, however I think broken as the logs just show the same thing every few minutes in red ,but for some reason has stopped the error altogether when I decide I need to look at it.
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm just waiting for it to finish but I'm kind of excited because I have managed to get what looks to be a pretty good boot image, kernel and system built through AOSP. All the files look like they have been placed properly and it's just in the final stages are creating the applications. Everything actually looks to be in order this time minus a typo or two that didn't prevent the build from proceeding. a few files were misplaced and some weren't put in at all. That took a bit of additional time, but at least I didn't have to start over not once. There were a few errors which seem to pop out in their own little groups, but according to the Google they are nothing to worry about and will not appear in the final build.

I do have a few questions. It created a ramdisk.img which I know is just a fancy way of saying a ramdisk and you candy compile at and get your goodies. It also created a recovery image. however I am not even anywhere near bold enough to try flashing that. It also created a cache a image and I will presume it will also create a user data image if it hasn't already. No I have a pretty good idea of what to do with the ramdisk, and what not to do with the recovery image, but what do I do with the cash and the user data images? It also created a system image but also a system folder. I would like to know that in the board config I change false to true to allow for a sparse image to be built. If it does build a sparse image as opposed to an ext4, will that be a problem when I need to compile the zip. I have been able to create and use for various other things a set_metadata zip, that's where the system folder directory comes in play. But it seems that assistant flashes better when flashing a zip with a system.new.dat file instead. I've been using python to create those images to put into a zip or I can run it through superr's tool. Now presuming that this is all built properly I don't want to screw it up at this point. If I just compile it using the tool then I can create several zips of a several different natures and flash each one if the first one doesn't work. so I guess I just want to know am I using the right tools to get this done or should I be doing this another way? As far as I know and correct me if I'm wrong [MENTION=7104332]k4y0z[/MENTION] but we still can't flash a system image through fastboot? I know we can use the DD command in a shell and that would probably be best done through recovery if it all.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
My spine is tingling at the thought of possibly having AOSP on my Fire HD 10! Can't wait!
[Fire HD 8 and HD 10 General] k4y0z:
Oreo will probably not be any less work than Pie, so I'll just stick to Pie.

Interesting, I'll have to check again, I didn't see anything that looks like a brightness/proximity-sensor on the tablet.

Not sure why you are making life so complicated.

If all is done right the build-system should spit out a flashable zip-file. No reason to manually convert anything and create zip-files.
[Fire HD 8 and HD 10 General] sakibstark:
How's it going. Can't wait. Did the AoSp boot?
[Fire HD 8 and HD 10 General] DragonFire1024:
Everything built properly but it gets right at the very end and suddenly this happens: libwebviewchromium.so failed. Needed by "out/target/product/Suez/obj32/shared_libraries/libwebviewchromium_intermediates/libwebviewchromium.so" error 1 (paraphrased as I just read it a few things that started to build over).

Aside from the library file issue again everything is in the right spot the only errors that happen that I can't seem to get rid of that don't affect the build our language translation errors in strings. Those are literally the only errors I see now besides the damn libraries.
[Fire HD 8 and HD 10 General] DragonFire1024:
Got home and I was down and out before I could even count so I have had no time to turn on my computer screen and see how the build went. however when I had left the house yesterday it appeared to have successfully created the various images that needs to create a zip. So I'm kind of excited and hoping that everything went well. I'm very close nonetheless. if I can't get past these damn library file hurdles I'm going to need some help or we're stuck in the mud. So we'll know tomorrow

Edit: I also want to know this is the first time that I've had any build build every image that it needs. Up until this point I was only able to get the thing to build a system image even though it never worked. So if none of this actually works it wouldn't really matter because I'm closer than I've ever been getting it done. Though everything looks to be in almost near-perfect order,with the luck I've had and the history of these devices and others, I'm not holding my breath or expecting anything. Because anytime I do it never goes well. So I'm expecting worst and hopefully this time we'll get the best.
[Fire HD 8 and HD 10 General] jeepers007:
Is that package already in vendor? It could also be in the device make files (having checked the code myself). If so, maybe just a symlink issue.
[Fire HD 8 and HD 10 General] thejoker954:
it does have a light sensor. physically it's to the right of the selfi cam. stock auto brightness works, but like most other things with the hd 10 it's wonky. I use Lux auto brightness, and I have to use a camera as sensor as Lux receives a reading of 0 when using the actual light sensor.
[Fire HD 8 and HD 10 General] k4y0z:
You are of course right, I just noticed it while shining a flash_light on it (I mean to be able to see it, not to test it)
[Fire HD 8 and HD 10 General] DragonFire1024:
I do apologize cuz I thought I had mentioned this before as well and it turns out I clearly did not. Still trying to understand why it appears the sensors are on device in bin, but don't work. I'm missing something and I can't figure out what it is.

The same can be said for GPS I'm still at a loss. Now I know they at least turn on because I've seen them in the log do so, but they either crash right away or shut off right away and they repeat the process every few minutes or less. I also know that technically speaking they're not in the right spot so as to whether they work when they're put in their proper places I have no idea.

---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------

I've done that with two and it seemed to have worked. I just have to wait for the build to get to the next one and then do the same. Haven't had much time to do anything the past few days I've been working far too much. I'll have two days off this week where all be able to hopefully accomplish more.
[Fire HD 8 and HD 10 General] DragonFire1024:
I also forgot to mention that I'm pretty sure the adaptive brightness toggle was not a stock setting on fire OS. I'm pretty sure I was able to bring out the feature back when I hacked the FireTabletSettings APK and was able to readd some of the Android stock features. When decompiling the APK, there is a file in unknown folder that contains a list of restrictions for certain fragments. All I had to do was remove the restrictions and then re-add the fragments back to the settings xml if they were missing or redirected. I'm 98% sure that adaptive brightness was one of those settings I had to remove the restrictions from. It was listed as restricted because the device can be used by children. At least that's Amazon's reasoning.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Well, we're not children, Amazon! Jeez, they have a separate tablet for kids, why not just leave the restrictions for that one? They need to add in the feature to disable kids' mode entirely so we have access to this stuff!
[Fire HD 8 and HD 10 General] DragonFire1024:
It's more to do with the fact that the device has managed accounts. So I can see the reasoning behind it to some extent but to completely block out the feature is kind of ridiculous in my opinion. There's other things to that they've restricted access to that I have not been able to bring out, but I believe some of those features were already active but redirected to Amazon settings which I had fixed in my hacking release. Though some of those settings also cannot be changed because it will crash the menu that is opens for them for some strange reason. Something I was never able to actually figure out. I imagine there might be other settings like this embedded in other APK is that I have not noticed or in some that I've never even took the time to decompile look through. and because I've never seen inside of some of those apks or look at any of the files it is possible that some of those settings can't be activated because the APK has been uninstalled or removed. And when that happens unfortunately those settings will hold no matter what you do. take Amazon photos for example if you uninstall it while using my hacked settings APK, you won't be able to tap on the wallpaper menu in display settings without the settings APK crashing. That will still be the case even if you reinstall Amazon photos, make it a system application, the same exact version, or a backup of the one that was already on your device.
[Fire HD 8 and HD 10 General] DragonFire1024:
So I'm having a problem to which I can't understand. And I can't seem to fix it yet. For some reason when system goes to build art, that's when everything starts to go downhill. For some reason it always stop working and building when I call is for the dex2oat, patchoat and the other one I can't remember off the top of my head cuz I'm not sitting at my desk. No I had realized I forgot to add those binaries as part of the vendor area. So I added them and I also edited the device make file to acknowledge and move them properly, but even after cleaning the build cleaning cache, I even downloaded bleachbit no matter what I do it's still will not go past those binaries.

Edit I may have spoken too soon so hold off on the above cuz I may have actually fixed it this time.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Hoping you got it fixed. :fingers-crossed:
[Fire HD 8 and HD 10 General] DragonFire1024:
I think so. Now that the library file issue is done. The dex2oat was apparently broken build scripts. So I just deleted the folders/directories with the problems and did repo sync. Setup the environment, ran lunch and I found a reference to one of the errors to try to use this instead of 'make' to build: LANG=C make. I didn't apply a -j because it was suggested to try it that way. So far literally 0 errors across the board. It's going to go quite slow, but everything is moving smoothly.
[Fire HD 8 and HD 10 General] Shadow Death:
*Insert non-productive WOOT! here* :D
[Fire HD 8 and HD 10 General] dillonb:
Apologies if I missed it earlier in the thread, but would you mind posting the source/device tree you're working off of currently? I have development experience and access to some fast build servers, and I'd like to help out in any way I can.
[Fire HD 8 and HD 10 General] DragonFire1024:
I forked the source [MENTION=7104332]k4y0z[/MENTION] put together and I have been modifying it to build via aosp direct. https://github.com/DragonFire1024/android_device_amazon_suez

It however needs to be updated as I haven't worked on much it, until the past few days spending hours and hours getting the kinks out 1 by 1.
[Fire HD 8 and HD 10 General] DragonFire1024:
Alright the hefty building is pretty much done. Now is the part where I see what I'm missing in vendor. Turns out, more than I thought. The only annoying thing is having the build start then stop and restarting it over and over as it errors out because it's missing a file. I was most of the way through the libs when I had to leave for work.

I learned a valuable thing today. I can save a lot of time and aggravation by just deleting the folder directories that contain scripts that break during builds, and resyncing the repo rather than trying to fix the actual scripts. It is also handy to do that when you forget where you put things.
[Fire HD 8 and HD 10 General] DragonFire1024:
Drum roll...looks like tomorrow we'll have a completed aosp build. I finished resolving the missing libraries. If nothing else goes amiss, then it should have finished building by now. Unfortunately I had to venture into work so we'll see how it went in the AM. It was looking really good when I left :D

---------- Post added at 02:41 AM ---------- Previous post was at 02:21 AM ----------

Notes: newer Android's, 6+, are usually these days built with clang as opposed to GCC. Older versions use GCC. I I think most of my problems stemmed from that fact. By specifying the option: LANG=C make, that tells the repository to build using GCC as opposed to clang. that seems to have solved pretty much all the problems I had especially with library files. From what I read after that, it's just a matter of making sure the proper packages and libraries and other required files are installed on the host system and detected by Android. I've also read that you should not specify a -j option on the first round. However not doing that makes the first build take anywhere between 12 and 13 hours to complete. If completed successfully then future build can include that option and take significantly less time to complete. That's just what I've been reading and I can concur that it does work.
[Fire HD 8 and HD 10 General] Rortiz2:
Dude, is your PC prepared for build? It's taking so long... How much time spent building? 1 DAY? lol.

BTW: Glad that is working at least.
[Fire HD 8 and HD 10 General] DragonFire1024:
I just don't have time to do anything. I've been working (real life job) so much and so many hours. That doesn't include travel to and from my job either. For now, unless I'm off, I literally just go home to sleep. So I have time to start a build and go to bed. When I get home I check it, try to fix said error and start it again. Rinse wash repeat. So it takes ME a day to press the buttons. Lately it seems there's always something going on in Florida and it's always in fort Lauderdale or nearby which also affects my job which also makes me having to stay longer. trust me I very much would like to be able to have more time on my hands unfortunately that's just not the case right now. So I'm going only as quick as I can go. Also my PC was originally built for bit coin pool mining. So it's not a PC problem though I would rather blame it on that lol.
[Fire HD 8 and HD 10 General] Rortiz2:
Oh dang.. I'm sorry. Well at least it compiles. I have an I3 and it takes hours to build a recovery:silly:
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Either way, I'm refreshing this thread every fifteen minutes or so!
[Fire HD 8 and HD 10 General] DragonFire1024:
Sometimes building breaks the process. At least that's what I can gather from two of the errors I've seen. So the solution I found was to delete the problem directory altogether and re-sync the repo. It would have been nice to see that a few weeks ago. Definitely saved me a lot of time this few days as now yes it does compile.
[Fire HD 8 and HD 10 General] DragonFire1024:
Drum roll again... we got one. Take a look below. Screenshot build completed successfully. Building from AOSP direct does not create a zip. It creates series of all the images as you can also see below. It also created a boot image what should contain the kernel and everything else. I have not unpacked it yet or looked inside. But everything seems to be in order. Now since there is no zip to flash I'm obviously going to have to create one. Does anyone have any recommendations or advice before I go about my own way of trying? because I don't want this to be a perfectly good build and then me to give up on it and start over again because I can't create a proper zip format or some other stupid thing. Cuz this is it were there or at least we should be:
[Fire HD 8 and HD 10 General] Rortiz2:
For make zip: mka bacon

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Any news?
[Fire HD 8 and HD 10 General] DragonFire1024:
I was playing around like a kid and made a small edit somewhere and have to find where, because I don't remember. I know what it was I just have to find where I put it. Small experiment gone extremely bad. And if it's not the edit I made then it's the kernel source.