• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[CHAT] HD10 (2017) - custom ROM brainstorming:

Search This thread

Rortiz2

Senior Member
Mar 1, 2018
2,183
1,454
Barcelona
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.

Sent from my Amazon KFSUWI using XDA Labs

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.
 
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.

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.

Sent from my Amazon KFSUWI using XDA Labs
 

Justsnoopy30

Member
Mar 18, 2018
41
4
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.


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.

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?
 
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?

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.

Sent from my Amzn Fire using XDA Labs
 
  • Like
Reactions: Justsnoopy30
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.

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.

Sent from my Amzn Fire using XDA Labs
 
Last edited:

Justsnoopy30

Member
Mar 18, 2018
41
4
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.

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?
 
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?

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.

Sent from my Amazon KFSUWI using XDA Labs
 
@DragonFire1024 you were working on a marshmallow ROM afaik. Any progress on that?

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.

Sent from my Amzn Fire using XDA Labs
 
Any progress on the pie rom @k4y0z ?

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.
 
So just an update of what I've been doing. I'm trying to get us off of the current kernel we have and onto something new. I've essentially been trying to build one from scratch. Which is going well, except for a few things and errors that I can't figure out. so it still seems like I'm trying to accomplish The impossible. The latest one being something along the lines of:

Code:
"No rule to make .config needed by out/target/product/suez/obj/KERNEL_OBJ/.config"

I know it's looking for suez_deconfig which it clearly finds, and build the kernel according to that configuration, builds the said modules, then proceeds to tell me that it can't find the configuration that it just built the kernel from. so I'm assuming it has to do with where that configuration is going after the kernel is built, which is clearly not in the place it should be. So I need to know what I am missing in my BoardConfig.mk that should send that file to where it needs to go. Because at this point after all is said and done really the only thing left to do is build most of the applications. I have been able to get past all previous errors which have been errors of my own. This one isn't necessarily an error but something I am missing. not much comes up in the terms of a Google search and what I have found I have incorporated into the BoardConfig if needed or seemed a logical, but clearly did not help since I am asking this question. any guidance would be greatly appreciated so I can finally move on to the next step.

Sent from my Amzn Fire using XDA Labs
 
  • Like
Reactions: avalst
So I have finally surpassed all the errors and everything has continued to build. So at this point the kernel is built, and a significant portion of the applications are built and that's pretty much all that's left. now assuming I have finally got it right this time it should be just a hour or so and we'll have another ROM on nougat, with a full blown CM kernel.

Sent from my Amzn Fire using XDA Labs
 

thejoker954

Member
Feb 5, 2012
30
7
LG V40
Wow, if you get that kernel working that would be amazing. I like my hd 10, but Amazon's hack job of both the kernel and the os makes using it (even for basic stuff)a pain in the ass.

I'm glad you haven't gotten discouraged.
 
Wow, if you get that kernel working that would be amazing. I like my hd 10, but Amazon's hack job of both the kernel and the os makes using it (even for basic stuff)a pain in the ass.

I'm glad you haven't gotten discouraged.

Hey @ggow what are the odds my kernel for cm/lineage 14 would work on your rom?
 

Spektre99

Member
Jul 12, 2012
16
0
If you have an Fire HD 10 (2017) what are the current options for putting a more stock Android on the tablet? I read a LineageOS version was available but the ones I've seen here in the forums specifically state not for the HD10. If a ROM exists, how is the experience? Is most everything working?

Thanks.
 

Michajin

Senior Member
Oct 23, 2012
1,263
508
If you have an Fire HD 10 (2017) what are the current options for putting a more stock Android on the tablet? I read a LineageOS version was available but the ones I've seen here in the forums specifically state not for the HD10. If a ROM exists, how is the experience? Is most everything working?

Thanks.

Not sure if you are reading right in the threads here. There are 2 very stable...

Lineage 12.1
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677

Lineage 14.1 (needs a couple tweaks and patches, but stable) No camera or disney+ though
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-14-1-t3973703
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Just dropping this here...
    14
    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?

    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.

    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.

    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.

    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
    10
    Guys, I am following this thread for quite a while and I have the feeling it is getting somewhat emotional now.
    From my point of view, "learning" is something totally individual so please do it the way it suits you best :)
    I am impressed of all the time and passion DragonFire puts into this project, so please keep going :good:

    By the way, I am willing to contribute somehow. I would like to reproduce your build, but some things are not clear to me or are scattered around this thread. It would be nice to have a compilation of what your have right now:
    - Which kernel source(s) did you use and did you merge them to upstream?
    - Which module(s sources) did you enable/use for build?
    - Which environment options or arguments did you use for build?
    - Any further steps to bring the kernel into the ROM.
    I have some good hardware around and some really nice collegues which might support me to reproduce your build.
    If this question is out of scope or just too much to answer, please ignore this post.

    Here are the sources I have. If anyone can expand on them...
    TWRP device tree for Amazon Fire HD10 (2017) https://github.com/chaosmaster/android_device_amazon_suez
    Kernel source https://github.com/chaosmaster/android_kernel_amazon_suez and https://www.amazon.com/gp/help/customer/display.html?nodeId=202194760
    MT8173 Source https://github.com/Goayandi/mediatek_mt8176_development
    Device tree https://github.com/488315/android_device_amazon_suez/tree/cm-14.1
    Proprietary https://github.com/488315/android_vendor_amazon_suez
    Kernel patches https://github.com/488315/Linux-Patches
    Possible portable ROM, stock Hi9 tablet (nearly identical to our build) android 7.0 https://drive.google.com/file/d/1mneBbR8eYceXrqxgVbBa6bBLZm7J7NTp/view?usp=sharing
    MT8173 Kit to make an LK, bootloader, preloader and boot.img https://drive.google.com/file/d/1i_xcl1RQwHJVLBvX3uDVFlcddcaLp8mf/view?usp=sharing

    I'll upload to github what I have been working on in terms of a ROM. I am reformatting my make files (they were bad) and it will take a hot minute.
    8
    Just giving a general update. I am almost done reformatting the makefile(s). There's a lot we have to import from the vendor area. and again because a profile to this extent has not existed for this device I'm stuck with making it all from scratch.

    There were some other things that I wanted to see if I can add in terms of mediatek proprietary applications that will allow for certain features to exist on a possible lollipop ROM that would not otherwise exist on a lollipop ROM. For some reason, in all the sources we have for this particular mediatek device, they do not seem to contain their proprietary applications, aside from ones that would normally be in the LK (fastboot et Al). That will take a minimum amount of time to add the device make file. The longest process is just simply adding all the lines of all the enormous amount of stuff we have to import from the rest of vendor. It weren't for that this would have been done long ago.

    Now that I have the next few days off I can focus on finishing that up and and making sure everything is in place to try another build.

    Sent from my Amazon KFSUWI using XDA Labs
    8
    I have a good feeling about this build. It's going to actually finish this time....the rom that is. I have no idea how long it has left to build but it's not long.

    Sent from my Amazon KFSUWI using XDA Labs