yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] sakibstark:
I hope We will be able to use the New ROM today. Well done lads.
[Fire HD 8 and HD 10 General] DragonFire1024:
I should have left it when it built but I get carried away and curious minds like to know things. Whether they work or not in the end is an entirely different story. With that said I wish I wasn't tinkering around and we probably would have had one already. But any one of you that have spent enough time around here know I like to tinker with things.
[Fire HD 8 and HD 10 General] sakibstark:
So excited for this.
[Fire HD 8 and HD 10 General] desidude2000:
Really looking forward to this. Thank. You [MENTION=8165603]DragonFire1024[/MENTION] for pulling this off.
[Fire HD 8 and HD 10 General] DragonFire1024:
Currently building now. Fingers crossed....?
[Fire HD 8 and HD 10 General] Rortiz2:
Luck for you. My build for other device (bq) stopped at 94% XD

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] DragonFire1024:
Now you know how I feel when I was having the problems with library files. That's about as much as I had left to go to when I was going through that crap.
[Fire HD 8 and HD 10 General] sakibstark:
how's it going? ??
[Fire HD 8 and HD 10 General] DragonFire1024:
Your ears must have been ringing. So far everything looks to be pretty good it's going to finish. it looks to be the only thing left to do are a few things left in the framework and the system applications and private apps. I assume the kernel is compile during all this as well. Nonetheless it's just about ready to start creating the images. So it's getting very close.

Took a look inside of various folders and directories and everything looks like it's being put in its proper place. So if the damn thing does not boot now, then the only thing I can think of is a kernel problem. However we shall see probably in about 2 hours or so give or take.
[Fire HD 8 and HD 10 General] sakibstark:
Awesome mate.
[Fire HD 8 and HD 10 General] DragonFire1024:
I ran into the library file weirdness again. However I finally know what it is. Amazon replaced the system image system webview with their own. On 5.1 and earlier, that webview is a permanent device feature. The library doesn't go in lib...well it does, but in the apk lib path in private app. Lucky for me, I have the right one. You would be surprised the headache that actually causes. And if the build misses it then a whole bunch down the line errors out at some point to seemingly no end.
[Fire HD 8 and HD 10 General] sakibstark:
Well that's a bummer. Hope this time it will build.
[Fire HD 8 and HD 10 General] DragonFire1024:
It does, did. Everything built except for one thing, the kernel. We have all the images. But it just won't build kernel. I don't know if it's me and not putting files in the right place but it'll make the boot image just not with the kernel. So the whole system is built. Eerything is where it needs to be except that. I'm just at a loss and honestly I'm really truly frustrated. I can build a stand-alone kernel on my own day in and day out.
[Fire HD 8 and HD 10 General] Rortiz2:
Are you using Kernel Source or prebuilt?

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] DragonFire1024:
Source. Kernel/Amazon/Suez/ and that has the source files/directories.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
I'm just curious here... will any potential ROMs be given their own threads once they are released or will they be posted in this thread?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
ROMs get their own thread, mainly to categorize it in the correct soon-forum, for easier searching/browsing, and to get more exposure. But most likely will be first linked in this thread.
[Fire HD 8 and HD 10 General] DragonFire1024:
We've usually been posting test ROMs in this thread. I wish I could say I have at least posted one. but the only thing that is stopping it from actually working properly is the kernel. Otherwise it seems I have a perfectly built system. What a goddamn shame and how frustrating. To get literally so close yet so far and the majority of those applications in that system are useless now because half of them can't be used or implemented into custom firmware because they fail signatures.

I'm going to try a different route today. I have downloaded a slimrom repo and set up another device through that and it seems to be a lot easier to set up. So I'm going to try my luck with that and see how it goes. [MENTION=5749760]ggow[/MENTION] I am curious how you got a system ROM 2 flash in flash fire without using a boot image. Or a new Colonel for that matter. it would make all the difference at least to get that far just to get off the damn fire OS.
[Fire HD 8 and HD 10 General] DragonFire1024:
In case anyone is interested, there is no particular place to put this. I have been able to extend, so to speak, wifi throughout the house, using any one of the tablets. You can use PdaNet app to create a WiFi hotspot with WiFi. It does so through the android VPN, acting as a repeater. So you can get her WiFi with WiFi. Is pretty cool because I've been trying to find a way to extend it further into the back yard.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Well, at least you've not given up on our dream!
[Fire HD 8 and HD 10 General] DragonFire1024:
Well I believe I found out what was causing the issue anyways. And why it wasn't building a kernel. I was completely misunderstanding the error it was spitting out about the kernel. As such I kept putting it in the wrong spot. However that doesn't matter anymore now that I have discovered a couple of build scripts in device/common that not only create the template make files for you, it also creates the proper folder directories. At that point all there is left to do is add your information to your make files that it didn't add for you. That's generally device information and specs. And that process it also generates the vendorsetup.sh which adds the lunch commands. I was doing a lot more work than I really actually had to do. So hopefully this time it will work.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Good luck, bud! We're almost there!
[Fire HD 8 and HD 10 General] DragonFire1024:
More than 75% anyways. So close yet so far
[Fire HD 8 and HD 10 General] moosefist:
That's still 75% closer than we were months ago. Exciting times. Thanks for your continued support with these devices.
[Fire HD 8 and HD 10 General] k4y0z:
Is it though? :laugh:

SCNR
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm going as quick as I can. I've asked for help in the past and only a few have stepped forward. It's not easy since all of us are teaching each other as we go along.

With that said, I only have so much time on work days to get any closer. However when I left the house this evening the computer screen said that the last build I did was successful and the statistics on the blocks that completed and where to put the stuff looked very promising and better than previous builds which suggests to me it probably finally properly created a boot image which means if that's the case it likely properly created the kernel. I did not have time to check before I went to work though. But let's assume I properly created everything. Hopefully the thing well at least just boot into something so it can get somewhere.
[Fire HD 8 and HD 10 General] sakibstark:
Hope this will boot. Well done mate, at least the build isn't failing.
[Fire HD 8 and HD 10 General] DragonFire1024:
The only reason why the build was failing was because some Library files were missing that were not included in the pre-made make files we have. Luckily I was able to understand the errors enough to track them down in the stock ROM and replace them. My other problem was forgetting to do that amongst a couple of other things if I needed to redownload the repo. It also takes a lot more time because it will stop the build at only one error at a time. So if you have several errors that you have to wait for each one and fix each one individually before moving on to the next or before the build will complete. But a complete Bill does not necessarily mean the thing will boot. With that said and all those errors fixed, my issue is just been getting the system to build a kernel. Tomorrow we'll have more news.
[Fire HD 8 and HD 10 General] k4y0z:
It's not that I haven't given you advice, but you seem to ignore it.

There are working sources on my github, which build fine and create a ROM that boots.

You just need to look at them, how to do things properly.

I wouldn't place my bets on it.
[Fire HD 8 and HD 10 General] DragonFire1024:
Been using yours. It's not set up for aosp direct, not all the files are listed in the make files like .so files, I don't know why I get certain errors while others don't. Ive tried other repos, slimrom for example and the results aren't much different. As I said before, there's basically no issue building the system. It's the kernel I'm having most trouble with. I won't have time til tomorrow to check though and see how the build went I did yesterday.
[Fire HD 8 and HD 10 General] DB126:
https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677
[Fire HD 8 and HD 10 General] sakibstark:
any updates from the AOSP ?
[Fire HD 8 and HD 10 General] Rortiz2:
ggow made a very stable LOS 12.1 that is like AOSP:

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677
[Fire HD 8 and HD 10 General] DragonFire1024:
Have to admit it's really good. Just flashed it onto one of my test tablets. Going to give a quick rundown of what I did so everyone can make their own decisions.

We finally have a full arm64 device so no more hacking things to get them to work on here. That also includes SuperSU. Which for the first time ever on this device works flawlessly. So I went ahead and install the ROM downloaded the nano arm64 gapps package and flashed both of those. Downloaded the super user removal flashable zip from the lineage OS website and the last or latest SuperSU zip, flashed the removal zip first then SuperSU. Then rebooted the system and everything booted perfectly the first time. SuperSU works 100% without any modifications and that is without the modified zip we've been using.

So far I can only find one complaint out of the 30 minutes that I've been setting this up and that is the volume. As it stands without any modifications you can barely hear anything unless you decide to use a bit of an obnoxious notification, or you have to set an annoying sounding alarm like I do. The Wi-Fi seems to be pretty stable. Be prepared for the Google apps and their components to update the second they get the chance so don't think it's broken but it will return to normal and be Tip-Top shape once they're done.

So far everything is as smooth as can be and I cannot find any bugs or flaws other than the single one I listed above so far. Absolutely impressive.
[Fire HD 8 and HD 10 General] sakibstark:
I hope yours will be even better.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've been trying and still am. I don't have nearly as much time as I'd like to be able to accomplish as much as I want to. Still pretty much in the same spot with the exception of I have finally got the repo to build the kernel. Just not the whole thing. So now that I finally have everything situated and have properly extracted the blobs thanks to [MENTION=5749760]ggow[/MENTION], I seem to have missed typed one character in one of the various make files in the device path. And I have for the life of me not been able to track down that typo. According to the air I constantly receive, it is on a single line and that line is supposedly missing a ')'. Yes a single parentheses. The problem is it doesn't look like it should go anywhere on that line. So if I can't track it down I will have to rewrite the make files again.

I am so close I can watch the entire process finish and build every single thing needed however the boot image just won't let the device boot. It's really disheartening to see everything in order only to be so far away. I've posted some screenshots below of the air and the makefile it's in. Maybe somebody can tell me where it goes. I'm at work now so I can't fix it and I'm sorry if the pictures are not very good quality.
[Fire HD 8 and HD 10 General] errorcheckaccount:
6th line from the bottom endef is missing a closing parentheses
[Fire HD 8 and HD 10 General] NeuromancerInc:
I love that someone took the time to create an account and post this single comment :laugh:
[Fire HD 8 and HD 10 General] Justsnoopy30:
Has anyone made a (somewhat) working nougat or higher rom for the hd 10?
[Fire HD 8 and HD 10 General] DragonFire1024:
There is an HD 10 ROM for Android 9.0 but there was never an official thread made for it and I'm not sure exactly which thread to discussion of it took place in and that's where the link to it would be. there is a 5.1 right now and I am currently working on a marshmallow ROM which hopefully if everything has finally been corrected because I'm dumb (not really just dumb mistakes I stupidly overlooked) then in two days or less will have a functioning marshmallow ROM.
[Fire HD 8 and HD 10 General] Justsnoopy30:
So does anyone have a link to that android pie rom?
[Fire HD 8 and HD 10 General] DragonFire1024:
I think [MENTION=5417447]Legitsu[/MENTION] made it if I recall correctly. He would be the best one to provide the link.
[Fire HD 8 and HD 10 General] Rortiz2:
[MENTION=7104332]k4y0z[/MENTION] made it..

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] Justsnoopy30:
I have searched both's recent posts and threads and not found anything about it.

Can anyone link me?

---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------
[Fire HD 8 and HD 10 General] Justsnoopy30:
One question, why is there so "low" system partition space according to gapps? Using twrp -> wipe -> advanced wipe -> system -> Repair/resize -> Available memory = 357. I tried flashing gapps stock, full, mini, micro, nano, and finally pico worked. Micro zip size is smaller than the free system partition space. It is insanely small. Is there any way to resize the system partition to be bigger?
[Fire HD 8 and HD 10 General] DragonFire1024:
Have you debloated any apps? because nearly all of Amazon's apps running in the background all of the time in some capacity or another. I don't even know if the right memory is displayed properly on fire OS. Though I can safely say I have never had a problem with memory or storage with any of the things I have done or been doing on stock fire OS. The biggest memory hogs in terms of the Google applications will be the Google app and Google Play services.
[Fire HD 8 and HD 10 General] DB126:
Nope, unless you want to go deep with a high probably of borking your device. Assuming you have write access to the system partition find a tool (app) that accurately displays size and content. Eliminate a few Amazon hogs and you'll have more than sufficient space for most GApps 'core' builds (albeit perhaps not stock). Stuff that doesn't fit can be added separately via Play Store; those components will get installed in the data partition.
[Fire HD 8 and HD 10 General] Justsnoopy30:
I mean that the android pie rom is taking up so much space in the system partition, not amazon stock rom.
[Fire HD 8 and HD 10 General] Kctucka:
Lineage also comes with a lot of apps you don't need, if you are planning on using GApps. You can uninstall them for more space too.
[Fire HD 8 and HD 10 General] Justsnoopy30:
I'm not home, but I'll try that when I am.
[Fire HD 8 and HD 10 General] k4y0z:
The LOS Pie rom still contains lots of unneeded binary-blobs that should be removed.

But then again it's still very alpha and I haven't had much time to work on it further.
[Fire HD 8 and HD 10 General] Justsnoopy30:
The last date the pie rom was updated was 7/6. Did [MENTION=7104332]k4y0z[/MENTION] stop working on it?

---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------

Ok. The major issue I noticed was the graphics being glitchy and slow.

Oh, I sent that before I saw the previous message.
[Fire HD 8 and HD 10 General] DragonFire1024:
The problem I have now is I can't get the build system to accept configurations for gapps. So it won't go past building anything until it can get the sources for gapps or related applications. Does anybody know how to do that because I'm at a loss and I can't find too much
[Fire HD 8 and HD 10 General] Justsnoopy30:
[MENTION=7104332]k4y0z[/MENTION] When you have time, can you try to fix sensors on the pie rom? Until then, it can't auto-rotate, nor manually rotate.
[Fire HD 8 and HD 10 General] Kaijones23:
[MENTION=7104332]k4y0z[/MENTION]use this commit https://github.com/mt8163/android_d...b45c323#diff-c23f7ab876ac167e05468ef79f046cb7
[Fire HD 8 and HD 10 General] k4y0z:
I told you to do that, remember?

Doesn't really make sense though until the graphics are fixed.
[Fire HD 8 and HD 10 General] DragonFire1024:
CM13 will not build. There is a maven repository module both the original CM and Lineage CM repositories that's required to build certain apps. Neither of the two will acknowledge the module instructions despite it being part of the source code. I've tried all the 'fixes' I can find, and none of them seem to make a difference. So I am going to go back to straight AOSP and see what happens over there.
[Fire HD 8 and HD 10 General] Rortiz2:
IDK what are you doing wrong. I just started compiling cm12.1 for douglas and compiled without errors. Are you using k4y0z tree? What errors you get? Also AOSP is worse than CM since it has less support for mtk.
[Fire HD 8 and HD 10 General] DragonFire1024:
It asks for a classes.jar file in vendor/cm/ambientsdk. The source doesn't want to fetch the maven repo that ambientsdk needs to produce core apps like calendar and contacts provider. The android.mk checks out, however the repo is archived. It lists various repo links, which differ slightly from the source. The only thing I haven't tried is changing that repo link to the one the archive lists. In regards to the rest of the build, I can assume to fix it with the fixes I tracked down (none have worked) and the build will continue, for a short time before it reoccurs. I've downloaddd a .aar file that contains the classes.har for an older version of maven. I was able to track down the same file for the latest issues release. Though it recognizes the .jar, the build will continue, and error at the same spot, and ask for a classes.jack. that's where the road ends. I've got nothing beyond that. The kernel builds, so it seems. The only hindering obstacle at this moment is ambientsdk. Otherwise the system appears to build everything else that doesn't rely on that. The problem is finding out when everything has finished aside from that and the related files.
[Fire HD 8 and HD 10 General] Justsnoopy30:
I don't get it... Why is everyone focusing on using old Clockword mod for this device? Why not focus on the pie rom, that has more issues to fix and uses up to date lineageos 16?
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm going to take a shot in the dark and say because it's not easy by any stretch of the imagination. I can see we're frustration can set in very quickly. I imagine given what we have to work with it doesn't get easier as Android gets higher. Maybe it's easier to solve problems at this level and have a ROM we're pretty much everything works with the exception of small annoyances and little things here and there that may or may not be our issue at all, or have a ROM or no ROM where many things are non-functioning and or broken in some form or another not to say it's a bad ROM. But you need a good base to start from and a lollipop ROM is a good base because it's something we can already work with and no relatively well where things go and what works and what doesn't and how that can build a functioning ROM. For the moment I am happy and ecstatic but also very frustrated as I'm fighting with the source that does not want to cooperate no matter what happens. Time to switch over to just plain old AOSP try from there and if I can't get anywhere else then I I'm at a loss.
[Fire HD 8 and HD 10 General] DragonFire1024:
Tried changing the link no luck. So I just deleted the repo and when I get home from work tomorrow morning I'll download AOSP again and start from there and see what I come up with. I'm sick of just one or two single errors dragging my progress. Especially when it's just only one or two errors and it's not even my fault. I mean literally that is all that is keeping this thing from finishing the build.
[Fire HD 8 and HD 10 General] Justsnoopy30:
It's probably not easy making a pie rom on a normally lollipop based device, but ggow already made a stable cm 12.1 lollipop rom that works mostly perfectly, so what's the point of trying to get cm 12/13 working if it's already done, instead of working on the pie rom?
[Fire HD 8 and HD 10 General] DragonFire1024:
Because the kernels are a mess. Need a lot of work. The HD 8 is in a worse position when it comes to their kernel. It's a matter of getting things to work. The advantage of having a cm13 ROM over a 12, is the possibility flashing a Kali Linux kernel to the tablet after a cm13 ROM is built. I don't think we'll be able to update any of the kernels on any of the tablets much less roll them back so we can. Amazon has just screwed them up too much. Though I think the HD 10 is the least worst of the bunch I could be wrong.

I'm back in business I can build through AOSP direct again with no issues except it does not build the kernel. Well it did on the first try most of it. Then it built less of them the second time around. I think I know what the issue is though and I have to look over a couple of other make files to check. If what I think is the only thing that's keeping the specific folders and directories from being built is just simply on commenting a couple of things then hopefully everything will be good tomorrow. Kind of sad and irritating having to see a whole build that's perfectly good on one end having to get thrown out because the other half does not work.
[Fire HD 8 and HD 10 General] DragonFire1024:
working on it as we speak and as usual I'm getting errors because who knows why it's me. For some reason I cannot get it to automatically build a kernel properly. So at the end of the build as long as I manually run in the command line to make the boot image it will build properly. but I haven't been able to test it because I'm getting some kind of intermediates are and I can't figure out where it's coming from or how to fix it yet I'm afraid I might have to download the whole source again. go figure I can finally build the boot image properly from source and now the system won't build. FML.
[Fire HD 8 and HD 10 General] Justsnoopy30:
Any progress on the pie rom [MENTION=7104332]k4y0z[/MENTION] ?
[Fire HD 8 and HD 10 General] DragonFire1024:
There are a few including me working on various ROMs. Pie is going to be hard. There are a lot of bugs and issues we have to figure out.

In regards to my progress: i have finally gotten cm to build a proper kernel and boot.img. everything builds perfectly up until it builds the apps. Then it crashes because it won't odex them. I have a feeling I know why, but I won't be able to test my theory until tomorrow. Its likely I have to redownload the whole source again because I'm pretty sure I broke the build.