yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] k4y0z:
amazon uses set_metadata in their own scripts.

set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);

also it's TWRP that executes these commands not FireOS.

---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------

You can brick the tablet just as likely by flashing single files.

To avoid problems I'd actually recommend flashing a system.img or system.new.dat.
[Fire HD 8 and HD 10 General] Rortiz2:
Yes i know, I wanted to say the updater-script of the fireos .bin.

But if Amazon uses set_metadata why we can not use it?

Ok.
[Fire HD 8 and HD 10 General] k4y0z:
You CAN use it, but of course it will fail, when called on a non-existing file.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've tried more system.imgs than .dat. the only way I could get a system image to flash was an unaltered copy pulled from it as backup. With the images, they are also supposed to be as close to the same size as stock as possible. I could be wrong anout that though.
[Fire HD 8 and HD 10 General] tylerhole:
Well looks like I'm a lil late to the party... had to wait for my flashing pants to dry. Guess I'll try and jump on the test train once you guys figure out the current issue. I'll be around and feel free to PM when you're ready to test too, I'll probably see that sooner than anything! You guys got this!! :D:D
[Fire HD 8 and HD 10 General] ffstudios:
I likewise was tempted to flash that second AOSP update today but am glad I held off. We are getting very close though, I can feel it
[Fire HD 8 and HD 10 General] DragonFire1024:
I don't know...to this day I have been unable to successfully flash the system partition of the HD 10. I can't even count the times I've tried. Now I have not had a problem creating a basic flash zip and flashing the /system directory. So far, anytime I've tried to modify a system.img pulled from the tablet, I was starting over again, no matter how small a modification it was. It also doesn't help the system.new.dat file in amazon bin isn't the same size as the system img when I unpack it. In fact I think it's larger.
[Fire HD 8 and HD 10 General] mrmazak:
So if you flash the unedited image/bin. Then make changes in TWRP file manager, will it boot.

If yes, then Maybe your repacking method is not correct.
[Fire HD 8 and HD 10 General] DragonFire1024:
On Linux, you mount the IMG, give it the permissions to edit, make your edits and done. You have to follow more steps to get that IMG to a .dat.
[Fire HD 8 and HD 10 General] DragonFire1024:
Have you tried an alternate download Manager? I've used this one several times on the 8in https://www.apkmirror.com/apk/dimon.../advanced-download-manager-7-6-70620-release/
[Fire HD 8 and HD 10 General] DB126:
Huh? That's not going to address root cause. Akin to painting over rust.
[Fire HD 8 and HD 10 General] nikothebarber:
Does anyone know any updates on running Xposed with the current magiks root works?
[Fire HD 8 and HD 10 General] DragonFire1024:
Git hub device tree. Don't hate me. It will need some work: https://github.com/DragonFire1024/android_device_amazon_suez
[Fire HD 8 and HD 10 General] Rortiz2:
For get google services working change the brand to google.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
It's a start, though! Maybe we can Frankenstein the two or three sources linked together into one working beast.
[Fire HD 8 and HD 10 General] siochs:
AND commit the whole "Beast" to a seperate github or gitlab repository. I tried to setup a gitlab CI pipeline today. I could not continue because I was just lacking the glue between all those pieces.
[Fire HD 8 and HD 10 General] TheRealIntence:
Don't start bothering with gitlab. Go for GitHub please!
[Fire HD 8 and HD 10 General] siochs:
Why? Gitlab has full integration of the ci runners' output to the platform, therefore i like it. Does github provide the same way of integration? all that i have found so far requires browsing a third party platform/webapp to see the output. and some of the on-premise solutions are quite pricy. Nevertheless, i would also give github a shot when i found the correct tool...!?
[Fire HD 8 and HD 10 General] Rortiz2:
[MENTION=7104332]k4y0z[/MENTION] how did you got the audio working on suez?
[Fire HD 8 and HD 10 General] k4y0z:
Not sure what sense it would make to "Frankenstein" anything together.

AFAIK There is currently only one tree that is actually useful in any way.

So I think it would make more sense to just continue working and improving on that.

I am still planning on working on it, but as said probably no major work before mid August.

As for changing the the brand to google as [MENTION=8978978]Rortiz2[/MENTION] suggested, to get google-services working and for the sdcard I'll see if I can make a new build sooner.

For sdcard I think I either need to use the old sdcard-fuse daemon to have /data/media fuse-mounted to /storage/emulated or port sdcardfs to the kernel.

Next steps in my opinion would be to find a solution for this nasty graphics-glitching and getting the sensors working (for autorotation etc).

What issue do you have with gitlab? It's quite a nice software, although It depends on where it is hosted.

I do host my private gitlab-instance for my private projects and it's CI really is a nice feature.

AFAIK Github also supports CI using Travis for example:

https://github.com/marketplace/category/continuous-integration

Well it is pretty buggy, but AFAIR I had to use audio.primary.mt8173.so from https://github.com/wuxianlin/android_vendor_cube_u1005/tree/lineage-15.1/proprietary/vendor/lib/hw
[Fire HD 8 and HD 10 General] Rortiz2:
So maybe using audio.primary.mt8163.so from my BQ Aquaris M8 (mt8163) will work?
[Fire HD 8 and HD 10 General] k4y0z:
I don't know, I don't think you are having the same issue I was having.

In my case the audio.primary from HD10 didn't produce any errors, but also no sound.

Since I am working on pie and the hd10-lib is lollipop in my case the oreo-lib from the repository helped.
[Fire HD 8 and HD 10 General] Rortiz2:
Ugh as you said no.. So I don't have more ideas for make audio work :)
[Fire HD 8 and HD 10 General] siochs:
One could also have one repo containing one branch for lineage and one for aosp so its quite comfortable to cherry pick from another. But this could also be a bad idea...

Besides what was mentioned already: On GitLab.com you can have private repos. You can also use your github credentials for login.

GitHub "supports" a whole bunchnof CIs. But i dont know if those integrate as well as the gitlab-runner with GitLab. I have to check that...
[Fire HD 8 and HD 10 General] DragonFire1024:
Tried the new build on one of my 10s. I couldn't get past the Google play uncertified warning and it just started to go nuts and wouldn't let me register. The interface just kills me (,no offence to the creators) but I never liked lineage. I have yet to install a lineage ROM that I like, on any device. Something just doesn't and hasn't set well with me and I don't know why.

I have managed to significantly clean up the boot image. Just about the only thing Amazon related I couldn't remove, was the 'amazon components' in the init.environ.rc. too much of them are tied into the systemui and when you remove them, it fully boots...to a black screen. Managed to remove the call to export those though that was in another file. There is a lot less here than I thought of Amazon junk.

Edit: also built the generic run-of-the-mill kernel so that I could take the kernel image and them two sources plug them into aosp and hopefully it will build a kernel and hopefully a bootable ROM. redoing some things in the make files to try and get them as close to looking like the source we have as possible
[Fire HD 8 and HD 10 General] TheRealIntence:
I do not recommend to flash gapps beside the rom.

This isn't something lineage related. You simply can't use Google services if ur device is not certified.

If u want to use them anyway then check out microG.

---------- Post added at 10:39 AM ---------- Previous post was at 10:38 AM ----------

On GitHub you can create private repos too.

I personally hate gitlab. It's slow and in my opinion not well designed. I don't see any benefits over GitHub.
[Fire HD 8 and HD 10 General] k4y0z:
I have already updated the brand to google, but I was also trying to fix the issue with the internal storage yesterday.

It is now being mounted using fuse, but for some reason I am still getting permission-issues.

Once I have that sorted I will upload a new build which hopefully allows downloading files and using google-services.

E AndroidRuntime: java.lang.IllegalStateException: Unable to create directory: /storage/emulated/0/Download

I don't know about the hosting on gitlab.com, but what I like about gitlab is, that it is opensource and you can host your own instance on your private infrastructure.

Although for my android-projects I am also using github (I have updated my repositories BTW ;))
[Fire HD 8 and HD 10 General] TheRealIntence:
I've noticed wrongly set permissions and ownerships aswell. You should be easily able to fix them by adjusting the fusion mount parameters.

Having an own build infrastructure is kind of nonsense for such a project. Setting up a CI on the repo should be enough in my opinion
[Fire HD 8 and HD 10 General] k4y0z:
Well, the issue is that the permissions look correct but even shell-user can't create files for some reason.

I also tried changing from sdcard_r to sdcard_rw, but the issue remains.

130|suez:/ $ ls -l /mnt/shell/emulated/
total 12
drwxrwx--x 16 root sdcard_r 4096 2019-07-06 01:53 0

suez:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc),3011(uhid) context=u:r:shell:s0

suez:/ $ touch /mnt/shell/emulated/0/foo
touch: '/mnt/shell/emulated/0/foo': Permission denied

Yes, that's what I am saying, for this project I am using github as well.
[Fire HD 8 and HD 10 General] siochs:
what is the ouput of the mount command??

Would mount -o remount, rw work to see if it is possible to write through at all?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Getting excited with all the collaborating going on now! Looks like we're getting somewhere!
[Fire HD 8 and HD 10 General] DragonFire1024:
Just a thought doesn't happen to be permission issue within one of the XML files? because that's what it sounds like it sounds like the permissions wasn't added to the platform XML in etc/permissions/platform.xml.
[Fire HD 8 and HD 10 General] k4y0z:
Neither of that was the issue, I think it's just that using FUSE for internal storage isn't really supported on Pie.

So I ditched the idea altogether and went ahead and merged SDCARDFS into the kernel.

We now have full SDCARDFS-support which also solves the mounting and permission issues => Downloading files works now.

I have also changed the brand to google and indeed the play-certification issue has disappeared.

With this build I flashed open_gapps-arm64-9.0-pico-20190706.zip which worked fine.

There is probably lots of proprietary stuff that can be removed from the build, so we can flash larger gapps in the future.

Check out the new build:

lineage-16.0-20190706-UNOFFICIAL-suez.zip
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Dude, you rock! Anything that's broken in this build? Audio working? Video playback good?
[Fire HD 8 and HD 10 General] TheRealIntence:
There's still stuff broken in this buid but at least it's usable right now. Check some posts above. I posted some bugs there.
[Fire HD 8 and HD 10 General] k4y0z:
Well yeah, most stuff is still broken as I have mentioned earlier:

What isn't working (there is probably more):

There are still graphics glitches in navbar and recent apps.

Bluetooth doesn't work

Camera doesn't work

Sensors don't work

What is working:

WiFi

Audio works but is buggy

Video kinda

SDCARDFS / Internal Storage

Google Services

Everything else is mostly untested and probably broken.

I tested the youtube-app and audio seemed to work fine there.
[Fire HD 8 and HD 10 General] DragonFire1024:
In regards to the sensors, I've been trying to clean up Amazon garbage in the boot image. A while back I had taken the disabled tag off of a couple of the sensors to get a reaction from the system and the kernel to see if any of them actually worked, via logcat. Now I know that they wouldn't actually work or give any readings but I wanted to see if they would actually activate. They do turn on but then turn off and constantly restart. I experimented and decided to take some of them and throw them into vendor/bin, which in later versions of Android, seem to be where they go or most of the proprietary bin files anyways. And their reaction was the same. I've included a screenshot of the logs that I get from their readings. I'm not sure if will be any help, but I've also been trying to get them to work and I just can't seem to be able to. Even when I rebuild the kernel and specify a custom driver for the modules they still don't work even if I load them as a module or try and build with them built in. I've even gone as far to add the proper permission files in etc/permissions, also to no avail. I know part of the problem has to do with selinux and since I have a permissive kernel they need a selinux domain set. But even doing that has provided no explanation or no change in their actions. it also appears that it is missing some files or directories in /dev. It doesn't give much more information beyond that so I would probably guess it has to do with a port or a socket or something to that effect possibly.
[Fire HD 8 and HD 10 General] k4y0z:
This build doesn't use the stock boot.img it's all built from source (except of course some proprietary libs and bins)

When I talk about sensors I am mainly talking about the sensors that work on stock (i.e. the accelerometer)

Yes, that's where they should go on newer ROMs, that is mainly due to the separation of vendor-stuff started in oreo with project treble.

But when you do that, the service definitions in the init-files also need to be updated to reflect the new path.

You still seem to have misconceptions about the nature of selinux.

When selinux is permissive, it is basically disabled, you can ignore all of the selinux issues, meaning setting an selinux domain won't do a difference as you noticed.
[Fire HD 8 and HD 10 General] DragonFire1024:
While on the subject, I do notice the projectconfig.mk does list a gps chip. It also says the device supports the 'chip connectivity combo' which should include gps or at least the mediatek implimentation of agps. Can't seem to get any real confirmation either are working despite adding the required drivers and what not in the kernel build I last did in May. I guess I'm wondering if you've looked into that?

I use the stock boot image but your kernel sources. However aside from the init.environ.rc I've removed or commented everything amazon which included all of their 'logd' and 95% of amzn_fos related material as well. So not much left of the stock portion.

I've taken a break the past couple days and haven't done a lot of work. Amongst other things I tweak and fiddle with, I just got too stressed to do anything major. I've got everything reset again to try another build this time with a kernel and this time I made sure my device.mk file properly directed out the proprietary files. If I finish today I'll set for a build before I sleep.
[Fire HD 8 and HD 10 General] k4y0z:
Not sure about the GPS-part but AFAIK the 'chip connectivity combo' refers to wifi + bluetooth.

Before looking into adding support for new hardware that is or isn't there, the first goal should be to get the stuff working that works on stock.

So you are manually repacking the boot image?

Why don't you let the build-system take care of that?

Also some of the services are necessary to get stuff working like WiFi for example.

BTW, I just noticed that your device-tree is based on mine, but instead of forking you reuploaded all the files.

That Isn't good practice as all the commit-history gets lost and it makes it harder to later merge in changes.

So I would like to ask you to do is create a new repository as a fork of mine and then commit your changes on top of that.
[Fire HD 8 and HD 10 General] Rortiz2:
Don't remove amazon services. We done that on HD8 2018 and broke a lot of things..
[Fire HD 8 and HD 10 General] DragonFire1024:
I had meant to do that re GitHub. I was not on my regular PC, and at work at the time so just started to upload. Anyway I can change that? I haven't used GitHub much in this form so I'm am little lost when it comes to it.

I'm only repacking the boot image when I'm using it. I have not actually used a repacked or rebuilt boot image when trying to build this ROM yet. So yes I'm manual repacking it but only if I'm using it.

---------- Post added at 04:35 AM ---------- Previous post was at 04:28 AM ----------

I've removed only the things related to logd and have ran into no problems. I also removed the line that has called for exporting in the Amazon components with no problems. I have also edited to build prop 2 set the value of the Amazon fos to 0 instead of one. and then removed most of the lines that had to do with initiating it and have had no problem. now the interesting part comes is when I go to remove the components in the environment init file. It device boots however the system user interface does not. And you get a black screen. Try reinstalling the system using her face and it will reboot again only this time the whole system user interface completely crashes and you get all your icons in a desktop that's it. That's pretty much all that's in there in relation to the Amazon material that's named directly. The other problem I found is that some of the information in the init files should be in other init files. why Amazon moved a lot of that stuff from one file to the other is something I won't be able to understand. So it is possible that format changed with later versions of Android.
[Fire HD 8 and HD 10 General] k4y0z:
It would probably be best if you delete your repository on github (make sure you still have it locally).

Then head over to my repository and hit the fork-button in the upper right corner.

Then clone the new repository and checkout the lineage-16.0 branch.

Then you probably want to create a new branch, let's call it aosp-9.0 for example (make sure you're on the lineage-16.0 branch before doing that)

git checkout -b aosp-9.0

Now you can add your changes here and push them to github.

I am not sure, I am following you what do you mean by if you're using it?

Of course it makes no sense if you're not using it?!
[Fire HD 8 and HD 10 General] DragonFire1024:
Well I have only been able to get aosp to build without a kernel, because I was lacking the necessary image it needs to proceed. So I've only been building kernels using a standalone toolchain and the ndk, and testing them as I did so. I only just this weekend built another so I can see how the next build goes on aosp. I've also downloaded the 14.1 cm repository, which the device sources is based on, because I can only do so much more of trying through aosp before the failures really start to demotivate me.
[Fire HD 8 and HD 10 General] TheRealIntence:
[MENTION=7104332]k4y0z[/MENTION] The kernel behaviour is very weird after a

fresh install of lineage and open gapps.

CPU usage on all cores is around 100% even without any cpu intensive tasks. Little clusters stick between 100 and 55 percent. Weird thing is that there is no value between the percentages. It's 100 or 55 percent.

1404Mhz is used 95% of the time.

GPU is not measurable in FK Manager.

RAM seems ok.

IO speed is good.

Thermals are bad. mktscpu is always around 63°C or 145 grade fahrenheit even when device is idle.

zRAM is disabled which might be a bad idea for a device with only 2gigs of RAM.

Battery charging is very slow.

Overall performance is very bad which might cause audio bugs because the processing cannot be done fast enough.

Google services works like charm.

Safety net has to be patched because of ctsProfile.

Beside that, good work!! Finally we get something here...
[Fire HD 8 and HD 10 General] k4y0z:
Temp and CPU usage are probably related.

Not sure if thermal_manager and cpu-governors are running, haven't looked into that at all yet.

Not sure about GPU.

ZRAM has pros and cons, will think about that when other major issues are resolved

Don't think anything can be done about ctsProfile.

Would be interesting to compare your results with stock.
[Fire HD 8 and HD 10 General] DragonFire1024:
Sorry I have not had time to fix that mistake. We've had some really bad weather here the past day or two and we're just getting more. So I haven't had my major electronics turned on because of power surges and outages. not to mention we are preparing for possible hurricane in the next week or two or tropical storm so I've been focusing on that as well. Hopefully I will get a chance today to be able to turn everything on and boot everything up and fix a few things before it's all got to come down again. Again I do apologize hopefully in the next day or two things will quiet down enough for a few days that that I will be back in business.
[Fire HD 8 and HD 10 General] TheRealIntence:
I attached my benchmark results.

I was only able to test cpu and io because gpu is so damn slow that it does not load a 3d scene without system freeze.

Someone might feel free to do same tests with stock but i am sure that it will be better compared to LOS
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Your safety (along with family/friends/neighbors) is the most important thing. Take care and be safe with the upcoming weather.
[Fire HD 8 and HD 10 General] Animux:
This is on stock (rooted with magisk, several amazon apps disabled, gapps installed, with microsd card).
[Fire HD 8 and HD 10 General] DragonFire1024:
Alright I think I managed to fix it. let me know if I did anything wrong if anything else needs fixed and again I do apologize and apologize for the amount of time it took me to get it done. https://github.com/DragonFire1024/android_device_amazon_suez
[Fire HD 8 and HD 10 General] k4y0z:
That's better, but it looks like you based it on the master tree instead of the lineage-16.0 tree.

The master tree is very minimal and was only meant to get TWRP up and running.

the lineage-16.0 tree contains a lot more stuff, that is needed for a proper android build.

You should probably rebase onto the lineage-16.0 tree:

git rebase lineage-16.0
git push -f
[Fire HD 8 and HD 10 General] massimo727:
Would be more simple to base linage off what version android fireos is?