Related
Guys,
I recently bought a Moto E(XT1022). Being the curious tinkerer that I am, I started poking around the forums here for custom ROMs. Found quite a lot of them. One of the devs released an unofficial port of Carbon ROM for moto e. Cybojenix recently released an early build of of Slimkat ROM based on Android KitKat4.4.4. He also said that he will release an unofficial build of CM11 for moto e. But the problem with all of these ROMs is that they work only on single sim variants of moto e. I tried PMing dhacker29 the official dev of CM11 for Moto G unified Build about help to get these working on dual sim variants but to no avail. Same with JackpotClavin. So are there any other devs willing to take this up for us. Also I read on the Moto G forums about flashing XT1032 firmware on XT1033 to get only one working sim and to use single sim supported Roms. Is it anyway possible to do this with Moto E and is it practicak . The main problems being faced here are SystemUI crashes, not working radio etc.. There must be some work around.Hope we find it real soon.
yeah me too waiting for that but many users flashed the us moto e rom and result was none of the sims are working hope so we get some help
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
subham99 said:
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
Click to expand...
Click to collapse
BTW @cybojenix just released a cm11 fix for dual-sim versions. Single-sim works for me.
:good:
Check cm11 thread for more info.
Hey guys,
I'm a developer for the Optimus Black p970 and the creator of Aeroi rom. I am getting this phone soon and plan on developing it, any news from sources from Motorola? Have they released them yet?
The LTE model is known as Styx LTE. It's sources are available on GitHub:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop-5.0.2-release-styxlte
The LTE model uses an MSM8916, so use the msm8916_defconfig.
The 3G model is similar to the Moto G and previous Moto E. It uses a MSM8212 SoC. Motorola hasn't released a kernel for the 3G variant, but the previous Moto E's kernel sources might work. They haven't released Lollipop sources specifically for the old E either, but this kernel *might* work when built for msm8610_defconfig:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop—5.0.2-release
I'm working on a kernel for the LTE model, but I don't have anything that I consider worth releasing yet.
Should we be seeing better dev support for the LTE model soon?
Any news / expected availability of official CM/PAC for the LTE model?
Official CM doesn't mean better support.
I'm the maintainer of the moto E 2014 with @percy_g2.
Once I have a fully working CM for moto E 2015 build I'll push for getting the device official. The only change will be that the builds will be done by CM servers and you'll have the updates form CM. Also pushing changes to the repo will have to go through the grit system.
This is the same for PAC. PAC device tree and kernel can be easily done based on cm one.
I really hope that CM and PAC become official. Thanks for helping out.
I'm a serious and long term tester of custom ROMs for various devices, but more recently the 1st gen (Condor) and 2nd gen (Surnia) moto e.
I'm looking for your experiences, comments, tips and tricks of stock firmware (lollipop and marshmallow) verses the many custom ROMs available for the 2nd gen moto e.
Tell me what you find the best ROM.
What's the most stable? Has the best battery life?
What ROM can you make lots of modifications without affecting performance?
What's the worst ROMs? What ROMs have the most bugs?
This is not a post asking for your opinions so I can go out to find the best ROM, personally I have found what I consider the best ROM/set up/configuration for my E2 and am looking to see if other users agree with me.
Many thanks
Sent from my XT1524 using XDA-Developers mobile app
I personally fell in love with the Stock ROM on my XT1521 it has the best performance and is extremely stable. Some may have had issues because they flashed the stock ROM on some other device rather than the device this ROM was made for. Though it has been reported that the UK version has started to receive the 6.0 update. I request everybody to downgrade to the 5.0.2 stock ROM and update to 6.0 through the OTA update.
Again this is my experience and don't bash me for this.
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
I personally fell in love with the Stock ROM on my XT1521 it has the best performance and is extremely stable. Some may have had issues because they flashed the stock ROM on some other device rather than the device this ROM was made for. Though it has been reported that the UK version has started to receive the 6.0 update. I request everybody to downgrade to the 5.0.2 stock ROM and update to 6.0 through the OTA update.
Again this is my experience and don't bash me for this.
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
I won't bash you, your reply is exactly the reply I wanted.
Personally, I'm having better luck right now with the stock rom, but my personal preference is the last build of CM12.1 (17th April security update)
3 day battery life, very fast and the most stable my moto e has ever been.
Less luck with my 1st gen moto e, currently running CM13, it's laggy and very unstable
Sent from my KAZAM Trooper 455 using XDA-Developers mobile app
ivan39 said:
I won't bash you, your reply is exactly the reply I wanted.
Personally, I'm having better luck right now with the stock rom, but my personal preference is the last build of CM12.1 (17th April security update)
3 day battery life, very fast and the most stable my moto e has ever been.
Less luck with my 1st gen moto e, currently running CM13, it's laggy and very unstable
Sent from my KAZAM Trooper 455 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did u get the official 6.0 update???
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
Did u get the official 6.0 update???
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
No, I just flashed it from the firmware thread here, only after cm13 played hell with me!
Sent from my XT1524 using XDA-Developers mobile app
ivan39 said:
No, I just flashed it from the firmware thread here, only after cm13 played hell with me!
Sent from my XT1524 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just try and flash the 5.0.2 Stock ROM for ur model no. and see if u received the 6.0 update cause someone posted that they received it. Also in the past when I tried the stock ROM designed for another model I didn't get great performance but when I flashed the stock ROM designed for my model no. I got the desired performance.
Sent from my MotoE2(4G-LTE) using Tapatalk
ayush rao said:
Just try and flash the 5.0.2 Stock ROM for ur model no. and see if u received the 6.0 update cause someone posted that they received it. Also in the past when I tried the stock ROM designed for another model I didn't get great performance but when I flashed the stock ROM designed for my model no. I got the desired performance.
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
I apologise for not explaining this fully, meaning you made a completely unnecessary and incorrect reply (only because I gave you incomplete information)
So let me explain fully.
My moto e had issues around the 05/04 build of CM13.
After an upgrade from 04/04 to 05/04 via "dirty" flash (only wiping dalvik and cache) the moto e "hung" and got stuck on the "splash" screen and would not boot.
Returning to twrp to wipe system/data/internal storage was futile, it still would not boot past the Motorola boot logo.
Several people suggested I return my moto e to stock, so I duly returned it to stock BY FLASHING THE EU RETAIL 5.0.2 FIRMWARE FOR XT1524-(the variant of moto e I have)
This was completely unsuccessful as although I returned to stock, I left the bootloader unlocked and re rooted and reflashed twrp as soon as I had successfully returned the device to stock.
After booting into 5.0.2 I checked everything was fully working but found the device to be very slow, extremely laggy and stuttery.
Further research suggested UK users who had manually flashed the 5.1.1 update (you must remember UK has NEVER been offered the 5.1.1 update, as Motorola announced in December 2015 UK was skipping 5.1.1 to go straight to 6.0) got the OTA update after successfully flashing said 5.1.1 EU firmware.
This was again unsuccessful, with the device not quite as slow and laggy as 5.0.2 but now was running a firmware it should NOT have ever received.
Concerned this was my issue and sceptical of the advice I had received about the 5.1.1 firmware, I flashed the EU retail 6.0 stock ROM
I found it
Slow
Battery intensive
Laggy and stuttery, there was no fluidity, the screen movements were at best "jerky"
Ringtone volume reduced to the point I missed incoming calls.
Random reboots.
One point I must make to you and anyone else reading this is to
NEVER FLASH FIRMWARE FOR ANOTHER DEVICE OR FLASH INCOMPATIBLE/FIRMWARE NOT DESIGNED FOR YOUR DEVICE.
That is a very big no no and should not be attempted for any reason.
For example, if I flashed firmware for an XT1521 on my XT1524, I would permanently brick my device.
Same if I flashed XT1527 or XT1523 firmware.
No one should be attempting to flash incompatible firmware.
And to someone who messaged me asking if he could flash a "no carrier" firmware from an XT1526 on to an XT1524 to make this a no carrier unlocked device is simply "NO!"
Flashing a no carrier firmware on a carrier locked device will brick it.
Flashing XT1526 firmware on an XT1524 will brick it.
There may not seem much difference between these variants of devices but I'm told they are quite different, that's why they are numbered in such a way to make them different to the continents for which they are designed for.
This is not my opinion, this is fact, openly found here on XDA and read many times after people have knowingly flashed the wrong firmware on the wrong device and suffered a permanent brick!
I'm pretty sure most of my problems came from flashing 5.0.2 and 5.1.1, and since I had upgraded to 6.0.1 running CM13, I simply made the problem worse but not downgrading modem/bootloader.
I hope this explains my situation fully, but I've found the last security update to CM12.1 (17/04) the most stable custom ROM available for Surnia although I am now back and happy finally with CM13.
Regards.
Sent from my XT1524 using XDA-Developers mobile app
Cm13 22/04 is very good, just as good as CM12.1 17/04 that I came from (clean install, not using any mods other than squid kernel)
Do not use open gapps with CM13, squid has posted various warnings over the past several days to avoid using them as they have broken cm13.
I'm using caf 6.0.1 rom, before I was using aosp 5.1.1 with squid kernel and imo those are the best roms. Sure they don't have any custom features but they don't have every day updates (like cm) too so everything is pretty much polished with decent package of gapps. Both roms are fully stable and basically bug free. I wouldn't change my caf for any other rom.
@ivan39 you're not right. I remember that when there was no 5.1 update in Europe you could easily flash us firmware on Xt1524 changing only one radio file. BTW bugs that you had on stock 6.0 are probably caused by bad flash/not clean flash or something. It's impossible that stock firmware causes random reboots.
Thanks for that, I did not know its possible to flash US firmware on XT1524, so I stand corrected and hanging head in shame.....
Really, thanks for the info, something else I've learned.
Ref 6.0 stock, I assumed a bad flash, reflashed 3 times over 3 days, made no difference.
Agree with everything you said and will definitely look at the roms you mentioned
have you made full wipe after flash?
iks8 said:
have you made full wipe after flash?
Click to expand...
Click to collapse
Yes.
Stock 6.0 wasn't for me.
Back on Cm13
ivan39 said:
I'm a serious and long term tester of custom ROMs for various devices, but more recently the 1st gen (Condor) and 2nd gen (Surnia) moto e.
Click to expand...
Click to collapse
First of all, thanks for your contributions towards the device and the community, Moto E is an underdog but potent device which can really use a helping hand from enthusiasts like us
ivan39 said:
I'm looking for your experiences, comments, tips and tricks of stock firmware (lollipop and marshmallow) verses the many custom ROMs available for the 2nd gen moto e.
Tell me what you find the best ROM.
What's the most stable? Has the best battery life?
What ROM can you make lots of modifications without affecting performance?
What's the worst ROMs? What ROMs have the most bugs?
This is not a post asking for your opinions so I can go out to find the best ROM, personally I have found what I consider the best ROM/set up/configuration for my E2 and am looking to see if other users agree with me.
Click to expand...
Click to collapse
Stock vs Custom ROMs (CM in my case)
My device originally came with Android 5.0, but by that time CM 12.1 (5.1 based) was already available. The jump from Stock 5.0 to CM 12.1 was NOT very exciting. There was an immediate performance drop at the cost of added features. I moved back and forth between Stock and CM just to realise that CM 12.1 RAM usage was way higher than Stock 5.0 RAM usage. I stuck to CM 12.1 due to the extra features and over time, learnet to live with the performance drop.
A few months back, I thought of giving Stock ROM another try, and by that time Stock 5.1 had arrived. Going back to Stock 5.1, to my surprise, I found that the snappiness of Stock 5.0 was gone. I realised that between 5.0 and 5.1, something fundamental changed at Stock ROM/Kernel level and now the Stock 5.1 RAM usage was equal to CM 12.1 RAM usage. That also explained my initial experience, where CM 12.1 RAM overhead was simply because of AOSP 5.1 changes, and not CM additions. At this point, it was only sensible to stick to CM 12.1 as performance drop from Stock 5.1 was minimal.
Recently I tried Stock 6.0, but IMHO it feels rushed, it exists only for the sake of existing. Moreover, I can not believe Motorola/Lenovo can be serious about the software of their lowest-end nearing-end-of-life phone. They had to release 6.0 only to avoid lawsuits for false update promises (made in advertising and on retail boxes).
A final point: I'd prefer CM over Stock any given day simply because of community involvement in development, testing and bug fixing. Being Open Source and hugely popular, CM bugs are reported and fixed much much faster than AOSP bugs. You might say that AOSP is also Open Source, but it's only one way. You can fork, but they don't accept changes back. Overall, I have HUGE trust in CM community than AOSP/OEMs which are only concerned about making more and more money.
Choosing between various Custom ROMs
Most Custom ROMs are developed only in following 2 ways:
AOSP/CAF based
CM based (which is itself AOSP/CAF based)
Type 1 ROMs simply can not match the community involvement and release frequency of CM. Most ROMs I've seen fade away after 1-2 months of updates/support while CM keeps going forever. I see added features only as extra bits that has to be maintained. Moreover, most of the extra features of Type 1 ROMs are already in CM, or available as Xposed modules, or available as root-supported apps. So these ROMs don't bring anything extra to table.
Type 2 ROMs also fail to match the release frequency and long time updates/support offered by CM. Moreover, the added features are also questionable for the same reasons as stated above.
A valid point for considering any custom ROM except CM would either be totally reskinned ROMs, or the ones which are based on other AOSP forks (MIUI etc.). Personally, I fail to see the point of reskinned ROMs. Once you start installing Play Store Apps, you'll quickly realise that Play Store Apps are based on Material (AOSP) UI guidelines. Hence, you'll end up with a system where user apps looks/behave completely different from System apps. That's too much of an eyesore for me.
Some say that ROM X is much faster that CM, but I'm yet to see such a ROM. Benchmarks aside, I've tried almost all ROMs available in our forums and their real world performance is more of the same. For a ROM X claiming to be faster than CM, I'd be very interested to see which code changes have resulted in such a gain and if so, why they haven't been added to CM already.
---
So that's what I think. Let me know what do you guys think. Thanks for raising such a discussion
---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------
ivan39 said:
last build of CM12.1 (17th April security update)
Click to expand...
Click to collapse
https://download.cyanogenmod.org/?device=surnia only shows last 5 builds, where can I download this one? I'm still on 0324 build
gameSTICKER said:
First of all, thanks for your contributions towards the device and the community, Moto E is an underdog but potent device which can really use a helping hand from enthusiasts like us
Stock vs Custom ROMs (CM in my case)
My device originally came with Android 5.0, but by that time CM 12.1 (5.1 based) was already available. The jump from Stock 5.0 to CM 12.1 was NOT very exciting. There was an immediate performance drop at the cost of added features. I moved back and forth between Stock and CM just to realise that CM 12.1 RAM usage was way higher than Stock 5.0 RAM usage. I stuck to CM 12.1 due to the extra features and over time, learnet to live with the performance drop.
A few months back, I thought of giving Stock ROM another try, and by that time Stock 5.1 had arrived. Going back to Stock 5.1, to my surprise, I found that the snappiness of Stock 5.0 was gone. I realised that between 5.0 and 5.1, something fundamental changed at Stock ROM/Kernel level and now the Stock 5.1 RAM usage was equal to CM 12.1 RAM usage. That also explained my initial experience, where CM 12.1 RAM overhead was simply because of AOSP 5.1 changes, and not CM additions. At this point, it was only sensible to stick to CM 12.1 as performance drop from Stock 5.1 was minimal.
Recently I tried Stock 6.0, but IMHO it feels rushed, it exists only for the sake of existing. Moreover, I can not believe Motorola/Lenovo can be serious about the software of their lowest-end nearing-end-of-life phone. They had to release 6.0 only to avoid lawsuits for false update promises (made in advertising and on retail boxes).
A final point: I'd prefer CM over Stock any given day simply because of community involvement in development, testing and bug fixing. Being Open Source and hugely popular, CM bugs are reported and fixed much much faster than AOSP bugs. You might say that AOSP is also Open Source, but it's only one way. You can fork, but they don't accept changes back. Overall, I have HUGE trust in CM community than AOSP/OEMs which are only concerned about making more and more money.
Choosing between various Custom ROMs
Most Custom ROMs are developed only in following 2 ways:
AOSP/CAF based
CM based (which is itself AOSP/CAF based)
Type 1 ROMs simply can not match the community involvement and release frequency of CM. Most ROMs I've seen fade away after 1-2 months of updates/support while CM keeps going forever. I see added features only as extra bits that has to be maintained. Moreover, most of the extra features of Type 1 ROMs are already in CM, or available as Xposed modules, or available as root-supported apps. So these ROMs don't bring anything extra to table.
Type 2 ROMs also fail to match the release frequency and long time updates/support offered by CM. Moreover, the added features are also questionable for the same reasons as stated above.
A valid point for considering any custom ROM except CM would either be totally reskinned ROMs, or the ones which are based on other AOSP forks (MIUI etc.). Personally, I fail to see the point of reskinned ROMs. Once you start installing Play Store Apps, you'll quickly realise that Play Store Apps are based on Material (AOSP) UI guidelines. Hence, you'll end up with a system where user apps looks/behave completely different from System apps. That's too much of an eyesore for me.
Some say that ROM X is much faster that CM, but I'm yet to see such a ROM. Benchmarks aside, I've tried almost all ROMs available in our forums and their real world performance is more of the same. For a ROM X claiming to be faster than CM, I'd be very interested to see which code changes have resulted in such a gain and if so, why they haven't been added to CM already.
---
So that's what I think. Let me know what do you guys think. Thanks for raising such a discussion
---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------
https://download.cyanogenmod.org/?device=surnia only shows last 5 builds, where can I download this one? I'm still on 0324 build
Click to expand...
Click to collapse
Have a look on the cm12.1 thread, I'll post you a link
CM12.1-unoffical-20160417
Wow, thanks for such a detailed reply, I really appreciate you taking the time to offer your experiences!
Stock 6.0 in my experience was awful, I hated it, and can say nothing good about it, even though many users have disagreed with me or told me I'm wrong or did not install it properly.......yeah.....right.......
CM13 is better than it has been of late but just lacks a bit of "polish"
Its way more stable now but it still seems to have "hizzy" fits for no reason, or go totally bonkers for no obvious reason......
Let me take time to say I have been using xposed and various customisation yo make my moto e more like the android n developer preview, and these mods where just a little bit too much for it, it would run fast, fine with no issues for 24-36 hours and then just give up and take over 20 minutes to load a web page or drop a call I was making several times before connecting on the third or four attempt.
Things were better when these mods were removed, but still not learning my lesson, I started experimenting with various launchers and lockscreens just because I love to customise my phone.
Again, this has not helped in my quest to find the ultimate user experience for my E2.
CM12.1
I've found this the most stable, fluid and "fastest" ROM of all.
I agree no ROM is faster than another, but everything just happens a bit faster in the ROM than others.
This ROM is my back up, fail safe and emergency, if I get a bad nightly with CM13 or CM13 misbehaves, I just drop back.
In my experience the difference in looks and behaviour between CM12.1 and CM13 is negligible.
The only difference I see is the adaptive storage in CM13.
Other ROMs.
I found resurrection remix a very good ROM, again, it would work flawlessly for several days and then just go stupid, in the end I gave up using it because it was no better or worse than CM13 (being CM13 based)
No other ROM I tested came close to CM but I have to mention Tipsy OS as a very good rom!
I have a 1st gen moto e that was my original personal daily driver until my work phone (given to me by my employers-A Sony Xperia M2) updated to lollipop and the touchscreen failed.
So my E1 took on the duty of becoming my work phone, I had to get it unlocked from Tesco to take my work Vodafone sim, but at a small cost.
My wife brought me the E2 last December as an early Christmas present (I suspect because it had £20 off the retail price hahaha) and I lost no time modding it, unlocking the bootloader, flashing twrp and installing CM12.1 within the first 24 hours of getting it home.
The E2 is way better than the E1 but the E1 copes with damp and dusty conditions at work, runs CM13 by squid flawlessly and even though its nowhere near as fast or fluid as the E2, it just copes with CM13.
The E2 copes better with anything you throw at it. I'm not a fan overlayed ROMs either but I'm running Xpirits excellent port of sense 7 and blinkfeed on my E2, and its totally fine.
I just wish the ringtone was louder on the E2, I have modded mp3s with various apps but I find them too distorted to use as ringtones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Blinkfeed/sense 7 port by Xpirit on my moto E 2nd gen [emoji41]
Here my take on this subject:
I feel as if the moto e is better now with running cm13 on mine. Stock wasn't bad, just I never been a big fan of xposed(shocker I know) and the longevity of the phone increases for me as I can run the latest android os thanks to the hard work of the devs.
Now I haven't flashed another rom except stock MM. but I feel very contempt for now with cm13 and how it performs for my needs with this phone. Last part off topic:
I also feel as if this could be the last moto e from Motorola(lenova whatever blah) and I also feel like that the moto g will just come in cheaper models that will replace the e. So this phone could be the last of a solid running android phone with stock android under 5inch that's actually worth the money!
Sent from my XT1526 using XDA-Developers mobile app
For me, nothing beats stock 6.0 with squid kernel. I've tried CM13 but the battery life wasnt even similar to stock 6.0 (yes, also with squid kernel installed). I dont play games, i only care about battery life and stock 6.0 is the best for that (at least for me).
pd: CM12.1 and stock 5.1.1 are great too if i install squid kernel + xposed + greenify + powernap. Stock 6.0 doesnt need so much work to give me great battery life.
903tex said:
Here my take on this subject:
I feel as if the moto e is better now with running cm13 on mine. Stock wasn't bad, just I never been a big fan of xposed(shocker I know) and the longevity of the phone increases for me as I can run the latest android os thanks to the hard work of the devs.
Now I haven't flashed another rom except stock MM. but I feel very contempt for now with cm13 and how it performs for my needs with this phone. Last part off topic:
I also feel as if this could be the last moto e from Motorola(lenova whatever blah) and I also feel like that the moto g will just come in cheaper models that will replace the e. So this phone could be the last of a solid running android phone with stock android under 5inch that's actually worth the money!
Sent from my XT1526 using XDA-Developers mobile app
Click to expand...
Click to collapse
I always use the Stock ROM since I faced serious issues with CM13 (But that's another story). I think the official firmware is much more stable compared to CM13, moreover it has Moto display and the audio effects EQ I can't live without. There will be a next Moto e (that's what the rumours suggest. Search Motorola affinity on the web) though it has been reported that it will feature a mediatek chip. This means ROM development will be slow and there will never be official CM13 on that device.(Since Cyanogenmod officially support only snapdragon chips).
Sent from my MotoE2(4G-LTE) using Tapatalk
Heavily based on the WIP LineageOS port for the Moto E4 (Qualcomm) [perry] -- for more information about that, click here.
Known working:
Booting
Connecting to Sprint's 1xRTT network (2G data, voice, SMS)
Fingerprint sensor
WiFi
Broken:
Sound
Sprint 3G data and LTE (need to add in Sprint network blobs)
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
ReimuHakurei, squid2, Alberto97
Source Code: https://github.com/ReimuHakurei/android_device_motorola_owens
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-10-31
Last Updated 2017-10-31
Uploaded another build that seems to get LTE on Sprint. All of the menus are still broken so you presumably need to be activated on stock before flashing.
Is there any way to make the fingerprint function to wake up / close screen to work with out requiring a pin/pattern/code to be active? That'd be an awesome feature
Installed on my XT1775 briefly and except for the sound this looks pretty good. I'm on AT&T and LTE worked fine, etc. I just can't live without sound as I need my phone for work teleconferences. I will *definitely* use this as soon as I can daily drive it!
I have tried (and failed) to get CDMA data properly working. Once someone gets CDMA/Sprint support working properly on one of the other devices in this family, it should be simple enough to port whatever the fix may be, but until that happens, this will likely remain as-is.
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
fix-this! said:
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
Click to expand...
Click to collapse
I need to repair my shattered Moto X Pure so I have a working phone to use while developing before I can do much more work here (ie: on fixing audio). This was mainly a proof-of-concept to make sure I was, in fact, able to get the thing to boot, before I spent too much work fixing other things.
For CDMA, I think the root of it is the new architecture Sprint is using in preparation for CDMA+VoLTE; I tried porting over files from the Moto X Pure's LineageOS port, but it uses older tech for CDMA internally. The Moto G5S has the same ISIMv2 SIM card on Sprint so should be similar software-side, and the Moto G5S will almost certainly have a pretty active community judging from past Moto G series phones. Moto X4 should be similar as well.
I am likely to be pretty busy for the next month or so, though, so probably won't have time to do any work on this until then.
so does someone plan to pick back up development on this? really surprised there isnt more devs on the plus model. much better build, camera, cpu and that big ?.
What exactly did you have to do to get this to work. I'm considering trying to port a few roms from perry over to owens, but if it's too hard, or just practically impossible I'm not going to bother.
Which version seems to have LTE working? I currently have no LTE just call(no sound) and txt lol
So I am attempting to build my first rom for the Moto e4 plus Qualcomm. I'm just following the build instructions on lineageos's website. I'm stuck now because there is not a device tree in the lineageos git. I see that the OP has a device tree on git and I also see that there is now a Moto kernel on git. I am unsure what the next step is? I'm unsure how to make the device tree part of my local git and also how to mix the new kernel posted from Moto. Any help and I will post what I create. Thanks.
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
FlagersXDA said:
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
Click to expand...
Click to collapse
Yes please! I really want to use this rom but I use my phone for listening to music all the time. Will some please fix the sound?
Bump, can someone please fix this?
Thank you for releasing this!
+1 for no sound or mic on xt1775
I tried Bluetooth and wired audio devices and sound/mic is not functioning for them either.
I am able to connect to the Verizon network with a their Sim through net 10, but only 3g (EvDo-rev.A, by choosing global auto) and not LTE after trying various modes in the 4636 menu. With the same Verizon Sim through net 10 my Nexus 5x h791 does connect to LTE .
Besides the issues above, this appears to be working well!
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that. After I flashed twrp, instead of the Motorola bootloader unlocked screen, all I see is the white text "N/A" on a black background in the top left corner during bootup. Also, after I installed twrp I could no longer boot to the os until I installed this unofficial lineageos rom. I'm not sure if that is expected. Since I didn't make a backup of the system partition and boot before flashing twrp, I'm unable to restore the stock os. Lesson learned... immediately after making the mistake. I did make a backup of the boot and system partitions after flashing twrp before installing this unofficial lineageos rom(when I was already having the boot up issue), but when I restore them I have the same issue where the phone will not boot into the os. This is what I expected, at that point anyways.
Thanks again!
For Mediatek Variant
Sir,Any custom rom for Mediatek variant of this handset
fllannell said:
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that.
Click to expand...
Click to collapse
I'm not sure if its the exact same variant, but @_maerk released stock images for the retail (snapdragon) e4 plus. Even if yours is carrier specific, as long as your bootloader is unlocked and you have the Qualcomm version you should still be good. I remember on my old Sprint Moto E from 2015 I could still flash the OS/Recovery/Boot images from the retail version, just not the modems or bootloader.
Update: I was able to restore to stock using the following link.
SCROLL TO POST # 10 for directions for Moto E4 Qualcomm (Owens) retail unlocked:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
Then I flashed Reiku's version of TWRP for the phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Then I installed this unofficial Lineage version:
[ROM][UNOFFICIAL][owens] LineageOS 14.1 for Moto E4 Plus (Qualcomm)
https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197
Then I installed OpenGAPPs and AddonSu. The only hiccup I had through the process was that I got an ERROR Code: 64 when trying to install the ARM 64 version of openGapps in TWRP, so I used a non 64 version without issue.
Thanks to everyone for all of your efforts on these projects.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance