Time to talk about Android O for our device - Moto G 2015 Q&A, Help & Troubleshooting

First question does Osprey's hardware support Android O ?

Prob does but we'll prob not be able to have some features

Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too

Our device is in list to get los 15 ie. android O

androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.

adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli

Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english

Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .

Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli

Have faith on our awsome developer we will surely have android O

Well, Android Oreo is out. I really hope that Osprey will get it soon.

https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices

That would be amazing. Let's wait for a developer opinion.

I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"

android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.

adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this

rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2

adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information

I want to know about Merlin.. is it gonna get Android O? And if yes , when?

Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA

Related

Discussion Android 8.0 [Oreo]

First of all thanks to all the developers for making so many good rom's for our phone Gt-S758X. I am just curious to know about if our phone is going to have android 8.0 Which google releasing on may 2017 Maybe. So is our phone is capable of getting android Oreo?
Thanx for reading the post
Reserved
maybe yes bro
when source release , our dev will work on it
WeW finally someone replied. And i know when you're with us. this device gonna get every possible android ROM. well currently waiting for your yunos ROM @1111111111111111111111
dev here
no.
Why? ;_; I know our phone architecture is bit old but if we can get naught then why not oreo?
no one maintain it, it get harder and harder to get things work properly, i'm started develop for it since cm11 but stopped since cm13 because of compatibility issue with webview, it's currently maintained by ishant but he told me he will stop at N since it's getting unstable and more random bugs
Thanx Mate for your contributions for this device i really appreciate your work and your roms' ^-^ Maybe @DodoGTA and @1111111111111111111111 will work on this. thanx for all those beautiful ROMs @sandpox
Well.. Most people using ishant and my device tree/patch of CM (including dodogta) to build various of other android custom rom so if ishant refuse to work on the next android version then I don't think it will happen
Make it boot? Probably yes, fully make it functional? No
I'll try to make LOS 15 fully functional
Whats the problem with webview? Is it because of our phones hardware? I think all Lollipop++ ROMs having issues with webview?
@Anonymouspal GPU drivers are the cause of WebView issues
Yes
Yayyy. Our Saviour is here.??
?????
Yes
You're A developer?
@mahmoud_helal isn't a developer
Any dev will release Android "O" for our device?!
No man i'm not a developer
I had tried to learn the programming language but I stopped because of the study and I have a friend who is studying at the College of Computing and Programming and I think he can help

Andriod O for Z5?

Guys, I can't find any Oreo roms for my Z5.
Is it possible to build one with Xperia Open Devices Project?
yes it is but will take you a long time
XperiaDev has not updated the sources to support Oreo.
This means that you will not be able to compile AOSP.
GreyLeshy said:
XperiaDev has not updated the sources to support Oreo.
This means that you will not be able to compile AOSP.
Click to expand...
Click to collapse
yep, any support official (Sony) or "unofficial" (SonyXperiaDev) got abandoned,
so community needs to step in ...
There could be a way to get the phone part, etc. working from what I read (sonyxperiadev)
HOWEVER that would leave out the camera from the equation (something similar is currently happening for the M4 Aqua where burtcubbins is porting the device to 4.4 kernel)
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
zacharias.maladroit said:
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
Click to expand...
Click to collapse
Maybe @Myself5 could help!
shehabskull said:
Maybe @Myself5 could help!
Click to expand...
Click to collapse
How about No?
I was part of the stock based bringup for a reason. That reason was to never ever touch the SODP Kernel along with the Z5 ever again.
So the answer is No.
Absolutely Not.
No.
@Myself5 I understand you dont want to help because you have done a lot but ocasiaonly peaks and tests or edits would not hurt would it and to any developer reading this please just try
Quantumkk123 said:
@Myself5 I understand you dont want to help because you have done a lot but ocasiaonly peaks and tests or edits would not hurt would it and to any developer reading this please just try
Click to expand...
Click to collapse
Mate, he already said "NONONONONONONO", lol
EugenStanis said:
Mate, he already said "NONONONONONONO", lol
Click to expand...
Click to collapse
I know but I am trying my luck here
zacharias.maladroit said:
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
Click to expand...
Click to collapse
Do you have Telegram? Contact me @EnesSastim
EnesSastim said:
Do you have Telegram? Contact me @EnesSastim
Click to expand...
Click to collapse
Thanks, unfortunately I don't have telegram and I won't sign up in the near future
zacharias.maladroit said:
Thanks, unfortunately I don't have telegram and I won't sign up in the near future
Click to expand...
Click to collapse
I'll try to make oreo device tree, if you can make the kernel we can build Oreo.
EnesSastim said:
I'll try to make oreo device tree, if you can make the kernel we can build Oreo.
Click to expand...
Click to collapse
even the other devs (seemingly ?) aren't really sure what commits are needed to get the full/enhanced functionality - the basics might be there but perhaps something's missing
in any case the repo is at: https://github.com/sony-msm8994
I'm right now not interested in working on Oreo or any other matter,
I've flashed to Marshmallow again on the Z5 and do some investigation related to battery consumption and others there.
Currently not much time for flash-testing and ROM development.
I remember having seen kernels with commit changes from Nougat to Oreo but not sure which exact kernels those were,
bullhead, angler , oneplus2 - some of those must have been
We really want you guys to do it. Oreo port would be a beast of ROM <3
Not having the updated kernel sources (probably) shouldn't be a problem
since we can (attempt to) port the Oreo ROM from Xperia X and add the missing kernel changes from the Xperia X device (kernel diff)
https://forum.xda-developers.com/xperia-x/development/ub-xgen-rom-1-0-5-xperia-x-t3778738
HOWEVER
after reading the following:
https://forum.xda-developers.com/xperia-x/help/upgrade-via-ota-to-oreo-terrible-t3754928
it's rather pointless to try anything related to porting or updating to a higher Android version:
best battery for now (at least in my experience) use a modded Nougat or Marshmallow ROM with Stock kernel + Stock kernel modules,
that'll get you the best battery runtime when e.g. listening to Music, browsing, etc.
Also: I've done countless passes of different kernel releases and each time as soon as security updates, enhanced performance, etc. is added to the picture at some point (couldn't pinpoint exactly how or why, I suspect it's somehow perhaps looping inside the kernel) it miraculously starts to drain like it had a 4000 mAh battery
- this is ridiculous !
There simply isn't much potential to be gained in this device ( /me peers at the Note 3 and its improvements over time ... /sigh )
hi @zacharias.maladroit so is there still development for the z5 oreo rom or is there no point? I will try port that rom for xperia z5 just like i did for z3+ because believe it or not it actually works and i wll see how it goes
---------- Post added at 05:21 PM ---------- Previous post was at 05:11 PM ----------
also are you developers already trying to copy to the z5 cos if so it would be appreciated as i am a noob and just discovered the files are a lot different so now i need to actually learn
Quantumkk123 said:
hi @zacharias.maladroit so is there still development for the z5 oreo rom or is there no point? I will try port that rom for xperia z5 just like i did for z3+ because believe it or not it actually works and i wll see how it goes
---------- Post added at 05:21 PM ---------- Previous post was at 05:11 PM ----------
also are you developers already trying to copy to the z5 cos if so it would be appreciated as i am a noob and just discovered the files are a lot different so now i need to actually learn
Click to expand...
Click to collapse
Not that I'm aware of, just noticed the similarities in hardware between the X and Z5, Z5 series and did a superficial quick comparison
So not sure if others are currently working on it ...
@Quantumkk123
https://forum.xda-developers.com/android/help/tut-how-to-convert-dat-br-to-dat-t3723926
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
https://source.android.com/devices/architecture/vintf/comp-matrices
https://source.android.com/devices/architecture/vintf/resources
Well, a lot of files would need adaptation, and then there's the question if the GPU could be driven ... at all
the file and folder structure looks quite different ...
vendor/ueventd.rc
vendor/manifest.xml
vendor/qcril.db -> vendor/radio/qcril_database/qcril.db (?)
msm8994 specific hardware bits / drivers, thermal (very important !, or we're relying on third-party thermal driver solutions to try avoiding any potential issues)
touchscreen (also synaptics clearpad?)
and that's only looking at the vendor folder

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

With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked

androud Q GSI

Hi guys, So how I can install this ?
https://www.xda-developers.com/android-q-gsi-project-treble/amp/?__twitter_impression=true
I don't know if unmodified gsi will work for us, as treble requirements have been changed since our phone shipped. May be possible to modify but that is for smarter people than me. Google is apparently doing beta program again probably starting with beta 3 so maybe better to wait for that
M.
mattman83 said:
I don't know if unmodified gsi will work for us, as treble requirements have been changed since our phone shipped. May be possible to modify but that is for smarter people than me. Google is apparently doing beta program again probably starting with beta 3 so maybe better to wait for that
M.
Click to expand...
Click to collapse
Ok we'll see if it's possible , if I know something I'll Post it here .
Thanks
It boots but lots of bugs and not usable at the moment for our phone. Google's version doesn't work you have to use efrans version. If you want to keep up with it here's the telegram link.
https://t.me/androidqgsi
tember1214 said:
It boots but lots of bugs and not usable at the moment for our phone. Google's version doesn't work you have to use efrans version. If you want to keep up with it here's the telegram link.
https://t.me/androidqgsi
Click to expand...
Click to collapse
Thanks anyway, can you say something when it will be usable :fingers-crossed:
Sure

Our devices is dead??? No more rom support?

Hi, since Xiaomi decided to depreciate rom support for our mi4c, everyday i try to find a replacement firmware. But here is what i found: official lineage removed mi4c since april, last rom is 0209 because they no longer support 14.1 version. AICP lastest version is 2702, no longer update. There're many unofficial roms on 4pda, but all of them now have their support ended because the devs move to new devices. There's only Mokee that support nightly 9.0 and release 8.1 version everyday and monthly. I try to find something like "mi4c treble" but no hope, the repository is created but empty, not like mi4 that has unofficial treble support. Maybe i need to buy a new phone? But my phone is still in good condition with no problem so far... :crying::crying::crying:
Yeah, sad but true. I also gave up on new rom, so i still use the 15.1 LineageOS one (20180810). Good rom, no problems here, but wouldnt mind some security updates.
The phone works nicely though and apart from battery lasting a day, i dont see any problems. I guess we will have to move to new phone if we want to see some updates rom.
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
dla5244 said:
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
Click to expand...
Click to collapse
Thank you, i'm waiting for your topic
AgiZ10 said:
Yeah, sad but true. I also gave up on new rom, so i still use the 15.1 LineageOS one (20180810). Good rom, no problems here, but wouldnt mind some security updates.
The phone works nicely though and apart from battery lasting a day, i dont see any problems. I guess we will have to move to new phone if we want to see some updates rom.
Click to expand...
Click to collapse
Is that the one without vibration support?
https://gitlab.e.foundation/e/wiki/en/wikis/device/libra/install
it's a fork of LineageOS, still being updated
haven't tested it yet
This is update of lineage-16.0.
https://androidfilehost.com/?w=files&flid=289411
wRAR_ said:
Is that the one without vibration support?
Click to expand...
Click to collapse
Yes, that is the one.
Tfgru said:
https://gitlab.e.foundation/e/wiki/en/wikis/device/libra/install
it's a fork of LineageOS, still being updated
haven't tested it yet
Click to expand...
Click to collapse
Anyone tested it yet? It seems /e/ is sort of microg. how is it different?
Autines said:
This is update of lineage-16.0.
https://androidfilehost.com/?w=files&flid=289411
Click to expand...
Click to collapse
Why is this not on this forum, and where is the development thread being discussed? Are there any problems with it? Anyone tested it?
dla5244 said:
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
Click to expand...
Click to collapse
Great news, we're waiting for
AgiZ10 said:
Anyone tested it yet? It seems /e/ is sort of microg. how is it different?
Click to expand...
Click to collapse
/e/ is a fork of lineage and based on lineage 14.1 for our phone, with microg pre installed. They use a different default launcher, bliss
It works well and is easy to tweak if we dont like the launcher or default apps.
Anyway since our phone is no longer maintained i've decided to build lineage 14.1 for myself.
I'll do it once or twice a month when there are updates.
If anyone need it check here :
androidfilehost.com/?w=files&flid=299596
corwinux said:
/e/ is a fork of lineage and based on lineage 14.1 for our phone, with microg pre installed. They use a different default launcher, bliss
It works well and is easy to tweak if we dont like the launcher or default apps.
Anyway since our phone is no longer maintained i've decided to build lineage 14.1 for myself.
I'll do it once or twice a month when there are updates.
If anyone need it check here :
androidfilehost.com/?w=files&flid=299596
Click to expand...
Click to collapse
thanks
Mokee have a good android 9 ROM, been using it for months and no issues:
https://download.mokeedev.com/libra.html
Also WJXXBSH recently published new Lineage 16 and even 17! https://androidfilehost.com/?w=files&flid=299149
I have not tried it yet, but at least WJXXBSH is keeping our device live.
how about lineage 16 from havoic 3.1 (https://sourceforge.net/projects/havoc-os/files/libra/)
At least it work fine for me on mi4c

Categories

Resources