Related
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?
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
dalebaxter01 said:
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
Click to expand...
Click to collapse
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
bornlivedie said:
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
Click to expand...
Click to collapse
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
dalebaxter01 said:
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
Click to expand...
Click to collapse
In reality, it means little to the end user. It could theoretically mean that ROMS require less development time, since all roms in theory are based on a single image.
You can kinda of see this with Google's OEM Partners. At Google I/O they listed a number of partner OEMs that were the first to use treble and for the most part they have released upgrades quicker and more reliably then there non-treble counter parts. This also can be extended to the modding community and in general means that porting roms and developing them on a new phone should be easier.
This is all part of a bigger push by Google to gain uniformity across devices. They started requiring security updates in there SLA's and now are pushing treble.
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
https://www.androidpolice.com/2018/05/13/project-treble-impact-android-custom-rom-community/
alwynjoshy said:
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
Click to expand...
Click to collapse
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Oki said:
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Click to expand...
Click to collapse
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
Once you have the Treble framework in place and have then flashed a device specific vendor image you can from that point on flash any GSI ROM. The thing to note is that so far NFound's Treble ROMs have included vendor image files in them which makes them device specific, you need to check for and remove any vendor image files from Treble ROMs created for other devices if you wish to try the ROM on a device other than what it was made for.
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
A treble rom is hardware specific, so you cant flash a treble rom designed for a different device. Only GSIs are compatible with multiple devices, and it is this way since the hardware dependant part is only in the treble rom.
Right now there are not fully treble roms available for the Axon7. The currently available roms labeled as treble are delivered and work as a usual full rom. The treble and system parts are still mixed up in those roms. It will take some time until we could enjoy a fully wotking treble rom in the Axon7.
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.
so after long searching it finally clear to me that
- treble partition and recovery are available
- Can flash GSI/Treble rom but with quirks, e.g. bluetooth, hotspot not working
- Missing shims? Updated vendor partition?
so we need a great dev to work on it??
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
optionalmgrr.la said:
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
Click to expand...
Click to collapse
Who gonna rewrite vendor code? Its not devs work. It comes from vendor and silicon manufacturer. They knows their hardware. So they work closely with google to write vendor blobs.
Why u want treble rom? Flashing gsi doesnt give u more performance and stabilty. They are more buggy than non treble rom. Non treble rom are device specific so have less bugs.
Kenzo will get android 10 and thats enough. After that 5g phones will hit the market and all will rush for it. So dont assume kenzo will survive till 2050 if we make it treble :laugh:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
optionalmgrr.la said:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
Click to expand...
Click to collapse
Do u even know how selinux works.
What do u mean they dont even support selinux.? Every rom has selinux support since kitkat.
Why dont u write ur perfect selinux policy and help to this devs so that it can be enforced on pie.
And whats there in lineage official rom which other roms dont have. Lineage official has its rules which cant be met for older phones which has old vendor blobs. Difficult to get official status.
And Who really give damn about lineage official.
Other roms are more customizable and have far more better and miles ahead in features then los rom.
And what u mean by mess? Xiaomi gave mm blobs coz official miui on android 6. Then from where we will get latest code if qualcomm is not updating code for sd650.
Only stuff is broken on pie is Vilte. If u have selinux priority then use Citrus.
ok thx
Forget about project trouble for our kenzo
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.