I would like it if a developer like nayan deka or amarc78 would provide an Android Oreo (8.1, NOT 8.0) custom ROM for the Moto E4 (Qualcomm), like a RR-O, Pixel Experience 8.1, Lineage OS 15.1, or AICP 13.1.
Any of those would be greatly appreciated. Thank you for your consideration.
I'd really like that too! I'm really disappointed with Motorola lately. Ever since Lenovo bought them it's been downhill. I know the E4 is a budget phone, but come on Moto, just one major update, please?
Its under construction,,,also place this thread in Q&A section
It's a WIP currently, not to mention a lot of Oreo ROM sources such as Dot, MoonOS, etc. are still WIP too. We'll try when we can ^.^
nayan deka said:
Its under construction,,,also place this thread in Q&A section
Click to expand...
Click to collapse
Ok. Question: if you were to take a Lineage OS 15 ROM, and port it for the e4, approximately how long would it take to successfully port it?
Scholeggo said:
Ok. Question: if you were to take a Lineage OS 15 ROM, and port it for the e4, approximately how long would it take to successfully port it?
Click to expand...
Click to collapse
We try not to ask for eta here. It's actually against the rules. Besides, it's not a matter of porting. It's about creating a device tree for Oreo for this device. That is pretty involved, and there are folks working on it. Sit tight, and try not to ask for eta, it kinda rude. It will happen when it happens. Remember, we don't even have ANY official nougat ROMs yet.
madbat99 said:
We try not to ask for eta here. It's actually against the rules. Besides, it's not a matter of porting. It's about creating a device tree for Oreo for this device. That is pretty involved, and there are folks working on it. Sit tight, and try not to ask for eta, it kinda rude. It will happen when it happens. Remember, we don't even have ANY official nougat ROMs yet.
Click to expand...
Click to collapse
I applied for maintainership of DotOS, once Oreo trees are up and LTE is patched into the trees for it to work without flashing anything then there's a chance Dot will be official. I'm also in the process of applying to have crDroid official for the Perry and also the Falcon. Seems like a few ROM sources are waiting for Oreo builds for devices before bringing on maintainers now that Oreo seems to be the main focus of development
fireball0093 said:
I applied for maintainership of DotOS, once Oreo trees are up and LTE is patched into the trees for it to work without flashing anything then there's a chance Dot will be official. I'm also in the process of applying to have crDroid official for the Perry and also the Falcon. Seems like a few ROM sources are waiting for Oreo builds for devices before bringing on maintainers now that Oreo seems to be the main focus of development
Click to expand...
Click to collapse
Yeah I've been following that too. But he still deserves a slap on the wrist for asking for an ETA. Lol
Scholeggo said:
Ok. Question: if you were to take a Lineage OS 15 ROM, and port it for the e4, approximately how long would it take to successfully port it?
Click to expand...
Click to collapse
No ETA buddy
Scholeggo said:
I would like it if a developer like nayan deka or amarc78 would provide an Android Oreo (8.1, NOT 8.0) custom ROM for the Moto E4 (Qualcomm), like a RR-O, Pixel Experience 8.1, Lineage OS 15.1, or AICP 13.1.
Any of those would be greatly appreciated. Thank you for your consideration.
Click to expand...
Click to collapse
Did this really need a request? Oreo (wait...only 8.1; none of that 8.0 crap) will come when prerequisites are in place and the *volunteer* ROM maintainers have time to address. Until then you'll need to 'suffer' through one of the numerous Nougat based alternatives...including stable, fully featured stock. Toss in Xposed framework and a couple modules and you have everything Oreo brings to the table.
madbat99 said:
We try not to ask for eta here. It's actually against the rules. Besides, it's not a matter of porting. It's about creating a device tree for Oreo for this device. That is pretty involved, and there are folks working on it. Sit tight, and try not to ask for eta, it kinda rude. It will happen when it happens. Remember, we don't even have ANY official nougat ROMs yet.
Click to expand...
Click to collapse
nayan deka said:
No ETA buddy
Click to expand...
Click to collapse
madbat99 said:
he still deserves a slap on the wrist for asking for an ETA. Lol
Click to expand...
Click to collapse
Sorry, guys. I'm a newb here; didn't know that was illegal.
fireball0093 said:
I applied for maintainership of DotOS, once Oreo trees are up and LTE is patched into the trees for it to work without flashing anything then there's a chance Dot will be official. I'm also in the process of applying to have crDroid official for the Perry and also the Falcon. Seems like a few ROM sources are waiting for Oreo builds for devices before bringing on maintainers now that Oreo seems to be the main focus of development
Click to expand...
Click to collapse
Nice. Can't wait!
Scholeggo said:
Sorry, guys. I'm a newb here; didn't know that was illegal.
Nice. Can't wait!
Click to expand...
Click to collapse
no problem mate
Scholeggo said:
Sorry, guys. I'm a newb here; didn't know that was illegal.
Nice. Can't wait!
Click to expand...
Click to collapse
It's all good, I was the same when I first joined xD If you have any other questions that aren't quite allowed here and also for the occasional test build/test Kernel, feel free to join the Telegram group we have. The link is in my signature for quick reference
fireball0093 said:
It's all good, I was the same when I first joined xD If you have any other questions that aren't quite allowed here and also for the occasional test build/test Kernel, feel free to join the Telegram group we have. The link is in my signature for quick reference
Click to expand...
Click to collapse
Any testing builds in the Google+ group?
Well, with Lineage OS 15.1 now out in the wild, I can't wait to see it being ported to the E4 soon.
I chose to watch the e4, because of all the phones shown in MetroPCS free offer deal (gonna switch from Sprint soon), the E4 looked more like it could take Lineage OS 15.1. I looked for even LOS 14.1 ROMs, and not one of these phones could provide me with an accurate result, except the e4.
Question: with all these ROMs now developing from Lineage OS 15.1, which ROM would you recommend I flash when I get the phone? RR, AICP, AEX, DotOS, or plain ol' Lineage?
I'd like it if one of the LOS 15.1 developers for the E4 were to make their builds official. It could really help with OTAs.
Scholeggo said:
Well, with Lineage OS 15.1 now out in the wild, I can't wait to see it being ported to the E4 soon.
I chose to watch the e4, because of all the phones shown in MetroPCS free offer deal (gonna switch from Sprint soon), the E4 looked more like it could take Lineage OS 15.1. I looked for even LOS 14.1 ROMs, and not one of these phones could provide me with an accurate result, except the e4.
Question: with all these ROMs now developing from Lineage OS 15.1, which ROM would you recommend I flash when I get the phone? RR, AICP, AEX, DotOS, or plain ol' Lineage?
I'd like it if one of the LOS 15.1 developers for the E4 were to make their builds official. It could really help with OTAs.
Click to expand...
Click to collapse
Dude, it's more involved than you think to make rom official. You don't get to just "make" it official. LineageOS has very strict criteria for it becoming official (especially since 15). Just relax. We're still waiting for an Oreo common tree to be made. All of the nougat ROMs work fine on the metro e4.
It could be weeks before we see anything Oreo related. Maybe you should try learning to build something. You'll see what it takes for an official build. You have to have everything functioning, apply for maintainership, have it reviewed, be responsible for building it weekly, making sure everything stays functioning with every update, etc. Etc.
The roms that are available now are great. These guys do it in their spair time, because they like it.
Scholeggo said:
Well, with Lineage OS 15.1 now out in the wild, I can't wait to see it being ported to the E4 soon.
I chose to watch the e4, because of all the phones shown in MetroPCS free offer deal (gonna switch from Sprint soon), the E4 looked more like it could take Lineage OS 15.1. I looked for even LOS 14.1 ROMs, and not one of these phones could provide me with an accurate result, except the e4.
Question: with all these ROMs now developing from Lineage OS 15.1, which ROM would you recommend I flash when I get the phone? RR, AICP, AEX, DotOS, or plain ol' Lineage?
I'd like it if one of the LOS 15.1 developers for the E4 were to make their builds official. It could really help with OTAs.
Click to expand...
Click to collapse
madbat99 said:
Dude, it's more involved than you think to make rom official. You don't get to just "make" it official. LineageOS has very strict criteria for it becoming official (especially since 15). Just relax. We're still waiting for an Oreo common tree to be made. All of the nougat ROMs work fine on the metro e4.
It could be weeks before we see anything Oreo related. Maybe you should try learning to build something. You'll see what it takes for an official build. You have to have everything functioning, apply for maintainership, have it reviewed, be responsible for building it weekly, making sure everything stays functioning with every update, etc. Etc.
The roms that are available now are great. These guys do it in their spair time, because they like it.
Click to expand...
Click to collapse
With Lineage 15.1 for the E4, it's likely similar to how it is with the Moto G4 Play I also have. Only Squid can have Official LOS 15.1 on the Harpia, it'll probably be the same with the Perry especially since he does a lot on the device tree side of things. Plus most devs create ROMs they'd use such as myself (not everyone of course). I'm personally only unofficially maintaining the ROMs I'd personally use and there's no guarantee that I'll be able to become an official maintainer either in the future, it's all up to the ROM source maintainers and also almost every little thing has to be working flawlessly and there's still a few things that need to be worked on for Nougat. I do understand the excitement for a new Android release in the custom rom world, trust me I can't wait to get Oreo running on the E4 after using it on my G4P and I was hella excited for Lollipop on my old Nexus 4 years ago, however after developing I've more than learned it does take time. Madbat's right too, there are a good bit of custom Nougat roms out that will do the job for now and he's also right that it takes a lot to become a maintainer. As for which rom to recommend, all I gotta say is flash a few Nougat roms and experiment with them to see what suits your preferences the most. I might recommend Slim7 or Dot, and you might end up not liking them and like something entirely different. It'll come. Might be a few weeks, might be a month or two from now at least. But I tell you what as soon as trees are all up, expect Dot, MoonOS and possibly SlimROM. I have absolutely no ETA at this point either, just going with the flow right now ^.^
Ok. I heard from recent MetroPCS customers that the battery isn't the best, calls get hung up (and reception isn't good), and multitasking isn't great, there can be some network issues, and unfortunately, a bit more here.
If I were to buy the phone, and flash a one of the Nougat ROMs available, how would they improve the phone, concerning these problems found on the stock ROM? And how good was the gameplay for AR games like Pokemon Go, and graphic-demanding games, like Asphalt 8?
Scholeggo said:
Ok. I heard from recent MetroPCS customers that the battery isn't the best, calls get hung up (and reception isn't good), and multitasking isn't great, there can be some network issues, and unfortunately, a bit more here.
If I were to buy the phone, and flash a one of the Nougat ROMs available, how would they improve the phone, concerning these problems found on the stock ROM? And how good was the gameplay for AR games like Pokemon Go, and graphic-demanding games, like Asphalt 8?
Click to expand...
Click to collapse
It's a budget phone. It is what it is. I can say from experience, battery life and multitasking are just fine. Reception depends on location. Metro has a pretty big network, and they merged with t mobile.
It's one of the best budget devices around.
madbat99 said:
It's a budget phone. It is what it is. I can say from experience, battery life and multitasking are just fine. Reception depends on location. Metro has a pretty big network, and they merged with t mobile.
It's one of the best budget devices around.
Click to expand...
Click to collapse
Ok. How were the high-end graphics games?
Related
Guys Motorola just released list of devices that will be officially supported for Android 7.0.Unfortunately Moto Turbo did not make into that list.Now i see no chances in future too Although Droid Turbo 2 made into that list
The Droid Turbo is still waiting on Marshmallow, let alone Nougat. Its international model, the Maxx, didn't even get MM until earlier this year. We'll probably be lucky if we get official MM at all.
Speaking of which, the Maxx isn't on the list either, which doesn't bode well. Probably going to have to wait and hope someone builds CM14 for our phone, if you want Nougat.
CM14 (Nougat) will come for Quark
cure25 said:
Guys Motorola just released list of devices that will be officially supported for Android 7.0.
Unfortunately Moto Turbo did not make into that list.
Now i see no chances in future too although Droid Turbo 2 made into that list
Click to expand...
Click to collapse
You are referring to this updated Nougat device list from Motorola:
http://motorola-blog.blogspot.co.uk/2016/10/n-is-for-nougat-android-70-is-coming-to.html
There was an earlier list 3 months ago, with more devices to be added at a "later date". Yeah, no Quark phones made the updated list.
Of course, the Droid Turbo XT1254 made the Motorola "Marshmallow" list back on October 2, 2015 but Verizon deigned not release it to Droid Turbo owners (yet or maybe ever).
Septfox said:
The Droid Turbo is still waiting on Marshmallow, let alone Nougat. Its international model, the Maxx, didn't even get MM until earlier this year. We'll probably be lucky if we get official MM at all.
Speaking of which, the Maxx isn't on the list either, which doesn't bode well. Probably going to have to wait and hope someone builds CM14 for our phone, if you want Nougat.
Click to expand...
Click to collapse
That someone is our CM dev @Skrilax_CZ, and he has already committed to that.
Quark got Lollipop before Motorola gave it to us (March 2014 vs April 2015), Marshmallow before Motorola gave it to us (February 2016 vs July 2016) and will get Nougat. He's just waiting until nightlies for any CM14 ROM starts rolling out.
20th September 2016, 12:34 AM
Skrilax_CZ said:
I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier
Click to expand...
Click to collapse
Then, after Quark CM14 -- especially the kernel work -- other ROMs can build on that framework. We have 7 custom Marshmallow ROMs for the Quark (maybe 8 depending on how you count) -- they work on ALL Quarks, thanks to our CM dev. '
No reason we won't have just as many Nougat based ROMs.
Here's hoping that CM14 fixes the signal issues of CM13
I unlocked my bootloader (SU4TL-49) but now puzzled if I should wait for CM14 or install CM13 now...
I am new to installing a custom ROM and don't know if it is worth the time to install a soon-to-be outdated ROM.
Also, if the recommendation will be to still install now, which ROM to get. Just sick of Verizon and Motorola crap.
Thanks
a_cipher said:
I unlocked my bootloader (SU4TL-49) but now puzzled if I should wait for CM14 or install CM13 now...
I am new to installing a custom ROM and don't know if it is worth the time to install a soon-to-be outdated ROM.
Also, if the recommendation will be to still install now, which ROM to get. Just sick of Verizon and Motorola crap.
Thanks
Click to expand...
Click to collapse
Install now. CM13 (Marshmallow) was in "beta"/preview the first month. (And that "first month" for CM14 Quark ROM may not be until November.) Whereas CM12.1 (Lollipop) was rock solid. I didn't switch to a Marshmallow ROM for awhile, from CM12.1.
Go with the stable ROM (CM13) or other Marshmallow ROM for now. You can always change by end of the year.
You may even like Marshmallow Bliss or Resurrection Remix ROMs better than CM13. They seem to be the two most popular right now.
Edit: changed a word with a synonym so it would be understood without a negative connotation:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are filled with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
ChazzMatt and mrkhigh,
I can't thank you enough for quick and detailed responses!
Sounds great, I'll do some more reading on those roms and decide which one to get.
Thanks!
mrkhigh said:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are "bloated" with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
Click to expand...
Click to collapse
Bliss isn't "bloated", it has the smallest footprint of any ROM I've built or used. And it reboots in under 30 seconds, my Keurig isn't that fast. @bhb27 is constantly working on RR, and it's the most popular/downloaded ROM we have, no doubt about it.
VoLTE is something you have to sacrifice in order to use a custom ROM. bhb is trying to fix that too, but unfortunately, he lives in Brazil and is not a VZW customer.
I know that you know what you're talking about (been around long enough to see that), but to say Bliss is "bloated"...
My apologies. You took it wrong... I said it was bloated with features.... Meaning lots and lots of features.
They are features I don't use. So for me they are by definition 'bloat' but i did then say that's not a bad thing.
Probably a poor choice of words since it is often used negatively. Kinda like the word ignorant sounds bad but it would be completely correct to say "I'm ignorant in Pascal coding."
Bliss is an amazing rom. Just like cm rr and mokee.
---------- Post added at 12:47 PM ---------- Previous post was at 12:41 PM ----------
Edited statement above so nobody else would mistake what I was trying to say. It now reads filled
mrkhigh said:
My apologies. You took it wrong... I said it was bloated with features.... Meaning lots and lots of features.
They are features I don't use. So for me they are by definition 'bloat' but i did then say that's not a bad thing.
Probably a poor choice of words since it is often used negatively. Kinda like the word ignorant sounds bad but it would be completely correct to say "I'm ignorant in Pascal coding."
Bliss is an amazing rom. Just like cm rr and mokee.
---------- Post added at 12:47 PM ---------- Previous post was at 12:41 PM ----------
Edited statement above so nobody else would mistake what I was trying to say. It now reads filled
Click to expand...
Click to collapse
Words are funny like that, yes? Everyone has their own opinion when it comes to a custom ROM (good thing we have many to choose from, lol), I just misinterpreted your meaning of "bloat", so: My apologies to you as well :highfive:
mrkhigh said:
Edit: changed a word with a synonym so it would be understood without a negative connotation:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are filled with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
Click to expand...
Click to collapse
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
kingersj1 said:
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
Click to expand...
Click to collapse
Neither. If you want those things, you'll need to install the latest official Motorola release for your Droid Turbo, and nothing else. The latest update to SafetyNet broke the workarounds that were used in CM-based ROMS (Brazilian stock never passed SafetyNet at all, even without root or xposed installed). I think suhide might still work, but only on a stock marshmallow ROM that passes SafetyNet, and we don't have that.
EDIT: Never mind. I might be wrong about all of that. Check out Resurrection Remix. The dev has added a companion app called iSu that works as of 3 days ago for hiding root (stock CM root, do not install SuperSU), and apparently it passes safetynet.
JFYKI, I haven't tried out Bliss yet but I noticed that ROM size is 330mb for Bliss while RR is 273mb. I am quite satisfied with latest version of RR on XT1254.
The size of the system partition, if I'm not mistaken and assuming you have not manually resized it, is about 3 GB. So I'm pretty sure neither Bliss nor RR is going to fill that up anytime soon. But if you can somehow fill up that partition with mods that need over 10 times the space of the base OS, you are my hero.
The system partition is 1.94gb and I haven't ever resized the partition. With stock based ROMs, I was struggling with space on system partition. You're correct that with almost everything installed that I need, there's still 500+mb available.
kingersj1 said:
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
Click to expand...
Click to collapse
RR is your best bet. Use the iSU app and you can "keep" root
I'm currently using it due to that exact reason.
With nexus you'll have to simply "unroot" I left that ROM because face book kept locking up?!
And I would ASSUME the Brazil ROM would work out of the box since I do not believe it includes root.
Resurrection remix works just fine
Fwiw I think Brazil ROM no root would be a great choice as well. Nexus was buggy with Facebook for some reason but unrooted it passed safety net
Cm13 will NOT pass even unrooted. No idea why.
Brazilian does not play nice with Xposed...
See: https://forum.xda-developers.com/g4/development/lineageos-unofficial-builds-h815-t3726177
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Wuddelchen said:
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Click to expand...
Click to collapse
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Bleuzen said:
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Click to expand...
Click to collapse
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Wuddelchen said:
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Click to expand...
Click to collapse
Nobody knows. The bug exists since 2017-04-30, but nothing happens. And until the bug is not fixed, we don't get new official builds.
If you want to take the time to wipe and (re)setup your device is your decision.
But if you have the time, I would recommend it, mainly because of the security updates.
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
tulen_kobi said:
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
Click to expand...
Click to collapse
No, I didn't know that
Uh, there is work going on? This is great! I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Great to her that there is still developing going on
Well, I help where I can. But I'm new to Android.
I have experience with Linux, use it every day, and now I know how to build LineageOS. I also can do Java programming.
But I never developed something with Android already. So I don't know how much I can help.
Bleuzen said:
I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Click to expand...
Click to collapse
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Exabyter said:
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Click to expand...
Click to collapse
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Bleuzen said:
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Click to expand...
Click to collapse
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Exabyter said:
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Click to expand...
Click to collapse
Yep, looks good. I already tryed Oreo but it isn't complete already. But I'm looking forward to use and recommend it as new daily driver when it's ready
Hey guys! Some very talented developers have been working on unofficial releases for a while already, and I am unsure whether to go for their takes or wait until an Official version is released. Any predictions on when this might happen? Or should I just void my warranty and go for Vache's build? Thanks!!!
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
jtull89 said:
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
Click to expand...
Click to collapse
I have been using Vache's/fAIyaZ 7.1.2 build for some days now. Only found one bug, Skype wouldn't manage to access the camera for video-chatting, but I found a solution for it (activating Camera 2 API from this thread: https://forum.xda-developers.com/g5-plus/themes/potentially-google-camera-port-t3684264 ). Other than that, everything works perfectly (and a lot better than the Moto built-in tracking suite they ship the phone with).
Applying an unofficial fix to an unofficial port sounds a bit problematic. Do you think it would be possible for Vache/fAlyaZ to fix this in their port somehow? Or would it be more of a gapps thing? Or neither?
It seems so insane to me that there is no official LineageOS for Potter yet? I couldn't have even imagined that it wouldn't be released quickly when I bought the Moto G5 Plus - I though it is such a popular phone, so well reviewed for the price, able to be unlocked, etc. How can it no be better supported by the LineageOS team?
Sorry to necro this thread, but Oreo has now been officially released for Potter, after seemingly forever. What are the chances of getting an official 15.1 build for Potter any time soon?
I know Vache's unofficial build is much loved on here, and I think there's a 16.0 unofficial build I've seen flowing around as well, but some of us would rather go with an official build if one is available.
Don't mean to be a d*ck, but just follow the trending topics on the forum and you'll see where everyone has flocked to. At the moment I believe there's no need to program Lineage for Pie, when we have one extremely good AOSP based version online. Install the Pie version of the system that can be shot from a bow and never look back... Vache did a great job for as long as he did it, and a couple of other contributors too, so <3 thank you
now everyone seems to be somewhere else, that's how it goes
all the previous versions and knowledge gained from them kept being passed forward to ports from the next version of Android as well, so you'd have to look at Lineage Pie. Lineage16 seems to still be too raw for Potter, which means you likely won't see any official version soon. With Pie out, everyone's efforts turn to it, so you can see also that the 15.1 thread is pretty much dead.
I am looking for some basic information. Does the second screen work in the latest official nightly build of Lineage OS. Now that a legit android 8 is releasing for this phone, will there likely be official support for lineage 15.1?
Edit: Also, I just realized I posted this is the wrong place. Mods feel free to move it to q and a or wherever. Sorry, it's late.
johnwaynegacy said:
I am looking for some basic information. Does the second screen work in the latest official nightly build of Lineage OS. Now that a legit android 8 is releasing for this phone, will there likely be official support for lineage 15.1?
Edit: Also, I just realized I posted this is the wrong place. Mods feel free to move it to q and a or wherever. Sorry, it's late.
Click to expand...
Click to collapse
Official? No, development of the second screen is for lineage 15.1, and there are currently unofficial builds with it working pretty well (landscape mode still doesn't work and a handful of other minor issues) done by both our lineage maintainer x86cpu and by the second screen developers themselves. Official lineage 15.1 support will come at some point when things are super stable, right now things are still in flux a bit, one big thing is working on enabling full project treble support.
Phoenix591 said:
Official? No, development of the second screen is for lineage 15.1, and there are currently unofficial builds with it working pretty well (landscape mode still doesn't work and a handful of other minor issues) done by both our lineage maintainer x86cpu and by the second screen developers themselves. Official lineage 15.1 support will come at some point when things are super stable, right now things are still in flux a bit, one big thing is working on enabling full project treble support.
Click to expand...
Click to collapse
Thanks, I use my phone for business purposes and I need a stable rom. What do you recommend? I am looking at super-rom.
johnwaynegacy said:
Thanks, I use my phone for business purposes and I need a stable rom. What do you recommend? I am looking at super-rom.
Click to expand...
Click to collapse
Eh I suppose stock based roms like super and alpha rom are a a bit more stable than lineage. I mean lineage 15.1 is solid, but has some minor issues and quirks, while stock based roms have been rock solid.
The Osprey Oracle
It's been a while.
If you don't know me, I was active here a few years ago and created the FAQ thread.
I got out of the community for a while but I'm amazed at how strong the osprey development still is, so I plan to Frankenstein my model up to a 16GB/2GB and get back into it. So in that spirit, I want to go back to my RC roots and create a thread for everyone with the most up-to-date info to help keep this device alive.
I've called it the Osprey Oracle as it's more catchy than Moto G 2015 Oracle, but Merlin stuff will be here too.
My general philosophy in compiling this is to create a database of currently maintained or at least recent development, to enable users to find a ROM that is secure and supported. This means, more specifically, ROMs which are still being updated with the latest security patches; this is why you'll find some older versions such as Nougat in this list, because some very generous members are still compiling them with these patches. That means lots of things will be missing, however; if you disagree and would like a fuller, more historical database, let me know.
GUIDES:
To learn how to unlock bootloader, root, etc., I'll point you first towards my own FAQ Thread as it's all in there
For repairs, check out ifixit; eBay is the best place to buy parts
RECOVERIES:
Official TWRP 3.x.x-x for osprey
Unofficial TWRP 3.x.x-x for osprey/merlin with support for separate vendor partition
Unofficial red themed TWRP 3.x.x-x for osprey
ROMS:
Android Q
Official LinageOS 17.1 for osprey
Official crDroid 6.x for osprey
Unofficial LineageOS 17.1 for merlin
Official MalluOS 1.x for osprey
Unofficial MalluOS 1.x for merlin
Unofficial FlokoRom v 3.0 for osprey
Pie
Unofficial LineageOS 16.0, hardened w/ microG or just security patches
Unofficial LineageOS 16.0 for osprey
Official Resurrection Remix 7.0.2 for osprey
Official crDroid 5.x for osprey
Unofficial Resurrection Remix 7.0.2 for merlin
Everything below is no longer updated but kept for reference:
Oreo
Unofficial LineageOS 15.1
Nougat
Unofficial LineageOS 14.1, hardened w/ microG or just security patches
Unofficial LineageOS 14.1
Non-Android
Sailfish OS for Osprey
Stock (Lollipop - Marshmallow)
Motorola ROM Collection
Thank you very much for your thread.!!!
It is what I was looking for. I am trying to make quicker a relative´s Moto G 2015 and your thread has been very useful.
Warm greetings.
Good list but can you include the 14.1 stock images
I think under Nougat you should also include the link to the Stock 14.1 LinageOS + patches. Not everyone is concerned about Google and replacing them with microG.
Personally I've found sticking with Android 7.1 is best with this model of phone. Everything works out of the box, and it doesn't slow down.
Thread: https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246
JohnSmithXT885 said:
I think under Nougat you should also include the link to the Stock 14.1 LinageOS + patches. Not everyone is concerned about Google and replacing them with microG.
Personally I've found sticking with Android 7.1 is best with this model of phone. Everything works out of the box, and it doesn't slow down.
Thread: https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246
Click to expand...
Click to collapse
Just added, didn't realise anybody was still building it with the latest patches. fyi MSe1969's microG build simply provides the option of using microG if you want, you still have the choice to then actually install the microG apps or just flash GApps as normal.
Interesting, I've been very happy on Android 10.0 but as I don't use GApps that's a significant resource reduction before any other apps are installed, of which I don't have many. Recently upgraded my Osprey to the 2GB RAM version as well, which helps.
It's great we have so many options though, all the way from 7.1 - 10! Which is what I hope this thread will show and help members with.
Is Lineage OS 17.1 official now? I can see it on the Lineage OS website.
contructor0 said:
Is Lineage OS 17.1 official now? I can see it on the Lineage OS website.
Click to expand...
Click to collapse
Oh yeah it is! Thanks for reminding me, will update the list
Hey all, a chance for opinions if anyone has any before I go ahead:
In terms of Pie ROMs, LineageOS 16 (as well as the hardened micro G version) and Resurrection Remix 7 are no longer updated. The former is a few months old but the latter getting on for a year. So not terrible in terms of security updates compared to an OEM, but given that TheForce is still maintaining a crDroid Pie ROM would people be happy with me going ahead and removing LineageOS and Resurrectiong Remix from the list? Other option is to add a 'Pie' heading to the 'no longer updated' list I've added to the bottom? I want the main point to be that you can see secure and updated ROMs easily at the top but I understand people are interested in tinkering so might want them there for archival purposes.
That aside, just added FlokoRom, another one TheForce is maintaining, and MalluOS. Decent smattering of 5 up-to-date Android 10 ROMs for the Moto G3 now! Pretty amazing.
HTCDreamOn said:
Hey all, a chance for opinions if anyone has any before I go ahead:
..
would people be happy with me going ahead and removing LineageOS and Resurrectiong Remix from the list? Other option is to add a 'Pie' heading to the 'no longer updated' list I've added to the bottom? I want the main point to be that you can see secure and updated ROMs easily at the top but I understand people are interested in tinkering so might want them there for archival purposes.
Click to expand...
Click to collapse
I think it would be nice to keep old roms listed, for historical reasons.
In my case, I'm still on resurrection remix 5.7.4 (MM 6.0.1) with squid kernel 23. It's running nicely, and I'm still reluctant to upgrade it because I'm afraid of losing some functionality (camera and viper4Android both are doing great in this Rom and kernel)
Thanks for maintaining this list. I'd like it to also include a list of kernels
Cheers
gg2001 said:
I think it would be nice to keep old roms listed, for historical reasons.
In my case, I'm still on resurrection remix 5.7.4 (MM 6.0.1) with squid kernel 23. It's running nicely, and I'm still reluctant to upgrade it because I'm afraid of losing some functionality (camera and viper4Android both are doing great in this Rom and kernel)
Thanks for maintaining this list. I'd like it to also include a list of kernels
Cheers
Click to expand...
Click to collapse
Hmmm I'll think about kernels, main reason I hadn't is because there aren't any still maintained, and none for ROMs post Oreo afaik. Would go against the ethos of the list and I don't want to get into just making a massive archive, when you get the same effect searching "kernel" in the dev forums. Whereas with ROMs it can be tricky for new users to differentiate which are currently maintained, getting security updates etc.
HTCDreamOn said:
Hmmm I'll think about kernels, main reason I hadn't is because there aren't any still maintained, and none for ROMs post Oreo afaik. Would go against the ethos of the list and I don't want to get into just making a massive archive, when you get the same effect searching "kernel" in the dev forums. Whereas with ROMs it can be tricky for new users to differentiate which are currently maintained, getting security updates etc.
Click to expand...
Click to collapse
Isn't smartpack kernel currently maintained? (by someone in the Brazilian osprey group in telegram. It's currently in version 12.1 iirc and it's for Oreo, Pie and Q)
I understand that mixing kernel list here may be a little excessive, specially when most of them are abandoned.. but then it took me some time to get to smartpack kernel, because in xda it appears as abandoned, but it's currently maintained.
HTCDreamOn said:
so I plan to Frankenstein my model up to a 16GB/2GB and get back into it.
Click to expand...
Click to collapse
May I ask how you're going to do that? I've been interested in doing that for a long time, I have a 16GB/1GB version and I'd love to upgrade to a 16GB/2GB SoC.
AhReLocazo said:
May I ask how you're going to do that? I've been interested in doing that for a long time, I have a 16GB/1GB version and I'd love to upgrade to a 16GB/2GB SoC.
Click to expand...
Click to collapse
I just bought a 16GB/2GB osprey with a smashed screen (so v cheap) and swapped the motherboard. I suppose rather than upgrading it, I replaced the phone itself and performed a screen repair... depends how you want to look at it aha. It's a very easy phone to take apart though, just be careful with your plectrum when you pry the screen off because if you do it too quickly you can end up with bright spots / dead pixels where you've accidentally pulled the exterior glass away from the LCD. A soldering iron makes a good pseudo-heat-gun if you don't have one of those to melt the screen glue.
HTCDreamOn said:
I just bought a 16GB/2GB osprey with a smashed screen (so v cheap) and swapped the motherboard. I suppose rather than upgrading it, I replaced the phone itself and performed a screen repair... depends how you want to look at it aha. It's a very easy phone to take apart though, just be careful with your plectrum when you pry the screen off because if you do it too quickly you can end up with bright spots / dead pixels where you've accidentally pulled the exterior glass away from the LCD. A soldering iron makes a good pseudo-heat-gun if you don't have one of those to melt the screen glue.
Click to expand...
Click to collapse
Oh I didn't think about a mobo replacement, easier than a SoC replacement I was thinking hahaha
The G3 wasn't sold by carriers where I live so it would be pretty difficult to find a 2GB/16GB model. I guess I'll try ebay or similar.
Regarding the bright spots, for some reason mine has some even though it wasn't taken apart.
I'll try doing the same as you, wish me luck finding a donor device hahaha
Thanks for the reply!
Can you add these MERLIN ROMs to the list -
Project Sakura 2.Q (support is dropped now but its just a month old)
link - https://sourceforge.net/projects/projectsakura/files/merlin/
https://projectsakura.xyz/download.html
MalluOS 1.3 Chicken
link - https://forum.xda-developers.com/2015-moto-g/development/rom-malluos-1-3-chicken-t4162203
CrDroid v6.9 ( there is no xda thread )
link - https://androidfilehost.com/?fid=8889791610682922059
Charlie-117 said:
Can you add these MERLIN ROMs to the list -
Project Sakura 2.Q (support is dropped now but its just a month old)
link - https://sourceforge.net/projects/projectsakura/files/merlin/
https://projectsakura.xyz/download.html
MalluOS 1.3 Chicken
link - https://forum.xda-developers.com/2015-moto-g/development/rom-malluos-1-3-chicken-t4162203
CrDroid v6.9 ( there is no xda thread )
link - https://androidfilehost.com/?fid=8889791610682922059
Click to expand...
Click to collapse
Thanks, I'm not adding Project Sakura because I won't list ROMs that get 1 release and no further development. I think I'll give crDroid a miss also as there is no thread.
I'll add MalluOS though, thanks.
HTCDreamOn said:
Thanks, I'm not adding Project Sakura because I won't list ROMs that get 1 release and no further development. I think I'll give crDroid a miss also as there is no thread.
I'll add MalluOS though, thanks.
Click to expand...
Click to collapse
Understandable , also about Project Sakura the maintainer (me) dropped it because the Gapps survival script wasn't working while dirty flashing , users would have to wipe system partition completely and then re-flash the Rom and Gapps package or the device would bootloop. To make sure nobody loses their data I chose to drop official support the last OTA wasn't pushed either. OTA updates might have worked but then i wouldn't be able to test the Rom first myself for errors (by dirty flashing).
Thank you.
Edit: I don't want you to include the link but just wanted to tell you why the development was dropped.