Related
This is an invitation to all developers, compilers and testers of Moto X (2014).
We know that probably our device will not receive officially Nougat update and this is really bad, assuming that our strong Snapdragon 801 can smoothly run without any problems.
My suggestion it's to all developers and compilers from any country work together to sync AOSP from Nougat, adapt device tree and bring up our first AOSP 7.0 rom.
I know that CyanogenMod is working on CM14 for victara... But the idea is bring up pure Android. I never see any pure AOSP rom for our device and would be awesome if we have this now. CM14 maybe will delay a bit and I think that all users here want to feel Nougat experience
Some rumours at internet had saying that Snapdragon 800/801 will not have drivers for Nougat... But I know that this is possible because Nexus 5 had Snap 800 and developers already bring an functional AOSP (link: http://forum.xda-developers.com/google-nexus-5/orig-development/wip-aosp-nougat-nexus-5-t3446875 ). Our developers can check device tree from Nexus 5... See their adaptions in device tree for working Nougat and try to do the same for our Moto X. Maybe disabling Vulkan API for now and we can use same drivers and device tree of Marshmallow!
That's all guys, thanks for reading and we are really expecting an AOSP Nougat for our Moto X before CM14!
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
I agree, we have small team of developers. And this one more objective of this post: attract more developers.
I think that Moto X doens't have too much developers because we had officially updates since Android 4.4... Numbers of people that goes to custom ROMs is really minimal, because the stock of Motorola doens't give reasons to search custom ROMs (like bloatwares or lags).
But now, we are going to road of needing custom ROMs. Now we have more reasons to search for these ROMs, because we'll probably not receive Nougat. Moto X2 XDA Forum go clog of peoples trying to got Nougat.
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
cpvm said:
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
Click to expand...
Click to collapse
Would be awesome
Pls devs we need some nougat !!!
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
Dan(Invisiblek) is working on CM14 for Victara. http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_victara+branch:cm-14.0
and our CM13 Nighly builds is very close to a Snapshot build NO BUGS for me xt1092 very stable as Snapshot build.
Yes it's true . I have been using the nightly builds of CM 13 for Victara and it runs really smoothly. I would encourage developers to work on the Nougat ROM for Victara. We will appreciate it. Thanks
I really hope to see Nougat in this phone, sadly I have no knowledge to help in development, but for sure I will test as it become usable material (its my daily phone, so would be nice that alarm at least works as expected)
We already has an bootable CM14 guys! here's link: http://forum.xda-developers.com/showpost.php?p=68555035&postcount=100
Is it possibile to upgrade to Android 6.0?
No, Yota Devices have no intention of upgrading it to Marshmallow so it won't be possible.
Amplificator said:
No, Yota Devices have no intention of upgrading it to Marshmallow so it won't be possible.
Click to expand...
Click to collapse
As Y2 is pretty similar to Nexus 5 - wouldn't it be possible to use its system files (and therefore even updating to Nugat)? I'm aware of loosing the functionality of epd screen, just curious what would happen.
Building Lollipop AOSP from source would not be an issue and you would do it the same way that you build any other AOSP rom.
The problem is drivers and software for later versions of Android than KitKat and Lollipop, so no matter what, you would be losing out on the functionality of the secondary display as Yota Devices will not release proprietary code.
I fixed up the Lollipop kernel sources and did a few fixes to make it work and patched the Dirty COW security issue: https://bitbucket.org/Amplificator/android_kernel_yota_yotaphone2/
The driver for the e-ink display is in the kernel, of course, but if you decide to build AOSP for it, the secondary screen would just be showing the same image as when the device is turned off.
So if you intend to play around with AOSP sources you can use this kernel as a starting point and adapt it to whatever you figure out.
Another choice is to just modify the stock rom but then you'd obviously still be on Lollipop, but seeing as stock roms are are so clean I see no point in modifying it when it would be easier to just root your device and do modifications using Xposed or whatever you'd want to achieve.
Hello guys,
My query might seem totally obvious to some, but believe me it's genuine. And yes I've spent multiple hours on the internet searching about this but didn't find any satisfactory answer.
Now to the actual query, I wanna know what lineage os really is and how it is different from aosp. And I'm not talking about some fancy customisation tricks and additional features like button remapping or live display. I wanna know what is the difference at system level.
As most of the noticable features can be cherry picked and a ton on aosp roms also have those. How they are different at their very core, or are they not? What lineage os based offers over aosp roms?
Like most of the professional tech reviewers are so hyped about aosp roms but isn't lineage better ( except for some bugs) ?
PS- I first posted this on a lineage os rom thread, but then i realised it belongs more here.
AOSP is pure android, directly from google, without any modifications.
If you're talking about lineage as a mere software, it is just AOSP + some basic extra features added on top of it.
If you're talking about what all lineage is all about and why it's so famous and respected, read on.
AOSP or pure android needs hardware specific code patches [eg from CAF for snapdragon devices] for working on any device, so it's difficult to build it . While lineage has all these patches already present [Thanks to the hard working developers at lineage], so all you've to do is compile and enjoy . The work lineage guys do is massively used by almost ALL custom ROMs, yes you heard that right, without which those ROMs won't be possible.
I hope it clears your doubts
impulsar said:
AOSP is pure android, directly from google, without any modifications.
If you're talking about lineage as a mere software, it is just AOSP + some basic extra features added on top of it.
If you're talking about what all lineage is all about and why it's so famous and respected, read on.
AOSP needs hardware specific code patches [eg from CAF for snapdragon devices] for working on any device, while lineage has all these patches already present [Thanks to the hard working developers at lineage], so all you've to is compile and enjoy . The work lineage guys do is massively used by almost ALL custom ROMs, yes you heard that right, without which those ROMs won't be possible.
I hope it clears your doubts
Click to expand...
Click to collapse
Okay, so if I understood it right, lineage is basically just a less broken version of newly released aosp distros with some features and all. They basically share the main software core.
Do correct me if i misinterpreted this.
The main reason I had this query was that roms like miui mess with aosp core too much. So I just wanted to know why lineage os is different from aosp?
And also thank you for the detailed explanation.
xEcuTR said:
Okay, so if I understood it right, lineage is basically just a less broken version of newly released aosp distros with some features and all. They basically share the main software core.
Do correct me if i misinterpreted this.
The main reason I had this query was that roms like miui mess with aosp core too much. So I just wanted to know why lineage os is different from aosp?
And also thank you for the detailed explanation.
Click to expand...
Click to collapse
Yes you got it right
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
No... You are misinformed, there is no official build of AOSP or source code available, just kernel source like many devices. This is not a developer device and Moto does not treat it as one. Even stock factory images are difficult to get at times. That said, the device is very "basic" and has few things added on top of AOSP code, it is very close to "pure".
That said, there are lots of ROM options that are unofficial, both pre-built and as source code you can build yourself.
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
I don't now if you know the unlegacy android project , it's a PURE AOSP experience, nothing extra "not required" options. I used it on my samsung nexus (replaced by the G5+) and on my nexus 7 '12 ( it runs very smooth), different devices are supported. I find it fantastic, stable and light (my nexus7 flies and it is an old device).
It will be a great rom for our potter.
acejavelin said:
No... You are misinformed, there is no official build of AOSP or source code available, just kernel source like many devices. This is not a developer device and Moto does not treat it as one. Even stock factory images are difficult to get at times. That said, the device is very "basic" and has few things added on top of AOSP code, it is very close to "pure".
That said, there are lots of ROM options that are unofficial, both pre-built and as source code you can build yourself.
Click to expand...
Click to collapse
Thank you for the info! I'll check out a different device.
tlamb96 said:
Thank you for the info! I'll check out a different device.
Click to expand...
Click to collapse
TBH... About the only choices that fit your requirements are Google Pixel or OnePlus, at 3+ times the price. Your call and good luck.
tlamb96 said:
I'm interested in playing around with the AOSP and I heard that the Moto G5 Plus is one of the best phones to do so. Before I buy one, I want to make sure that I can do a full AOSP build. I looked around and found a few resources. Their GitHub (MotorolaMobilityLLC) has bits an pieces of components that would be in the AOSP, but not a comprehensive repo for a device. My questions are:
1) Is it possible to get a full AOSP build from *official* sources for this phone?
2) If so, do I just download the AOSP and patch together the components from their GitHub until I get a working build?
Thanks!
Click to expand...
Click to collapse
You're skipping a lot here, that's not how AOSP works... "For this phone" means it's already code that's been worked on by other developers, a distribution of Android (and not AOS itself). The only "official" Android source for this phone would be Motorola's stock distribution, all the others would be third-party like Lineage...
https://en.wikipedia.org/wiki/List_of_custom_Android_distributions
If you want to start your own distribution for the G5 Plus, that's a much bigger problem to solve and countless hours of work, but I suspect if you really knew about this you wouldn't have asked the question to begin with
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.