I, for one, am getting frustrated.
The CM 12.1 nightlies for the XT907 have been deteriorating in stability/"bootability" since August, despite a very good run since their introduction in January up through at least July. The September 26 build is what finally broke my RAZR M (with spontaneous crashes and reboots) enough to drive me back to CM 11.
I don't know when it happened, but something broke the builds even further since then. I tried the Nov. 16 and Nov. 21 builds (both with and without an Open Gapps package, and with a completely wiped internal storage in the Nov. 21 test), and in all attempts the first boot would crash to a black screen after the first "app optimization" - and then crash and reboot again in the middle of the boot animation when it retried.
The RAZR M has missed all three CM 12.X snapshot builds thus far, and to my knowledge there's no evidence that it will ever be stabilized enough for a snapshot - let alone get CM 13 builds when they eventually arrive. This bothers me, but what really has my blood boiling is this: as far as I know, there has been no word whatsoever from the device maintainer(s) on the status of the builds or why the device got no snapshots. I don't even feel sure that someone is (actively) maintaining the device at all.
Look, I know this is all supported by developers' unpaid spare time. I don't mean to put that down. (And I'd gladly start rolling my own builds and trying to fix what's wrong, but I lack two major things: the hardware (you try building AOSP or CM on a single-core Celeron with 2 GB of RAM) and the know-how.) But I feel like we (as RAZR M owners) are being left in limbo, with builds that haven't worked decently well in months, no recent snapshot to fall back on, and no word on the future of the device.
("So get a new phone and stop complaining, asshole." If you were thinking that, here's what I'm thinking: I was going to until I learned that Verizon's gonna tack on another damn monthly fee if I renew my contract to get a new subsidized phone. It's not yet in my budget to shrug that off, and the signals around here are not yet good enough to jump ship for another carrier.)
So, developers: if the device is being phased out or won't be supported, okay. Fine. Please tell us, and I will attempt to move on. If honest support is still on the table (especially CM 13), please tell us, even if it will be a while before us users can see the results.
Please don't leave us hanging.
I'm not completely sure, but I believe the maintainer of Blisspop (which is a fork of CM) stated that the razr m would be getting cm13 eventually. As for the instability problems, yeah they're annoying but you don't have to update. Your best option is to find the last build that works, and stick with it. This device is getting pretty old now, so it isn't unusual for the developer support to start disappearing.
As for your budgeting issue, if you're in the U.S. I just thought it would be helpful to let you know that you actually save money if you aren't on a contract with Verizon. If your contract has already run out you should go to the nearest verizon store and they'll apply a $15 dollar discount for every line that isn't contracted.
The only CM dev for the Razr M was dhacker, and he stopped supporting the Razr HD/M a long time ago, he moved on to the Nexus 6.
Other then dhacker, I know that kabladan was supporting CM for the Razr HD, but I don't know if he's still around or willing to support the Razr M.
I know I haven't been much help, but at this point there probably won't be much support for the Razr M anymore. As the device get older people move on.
Have you tried a Verizon MVNO like Page Plus?
I thought those reboots when finishing the app optimization were my fault somehow, And now I know nobody is maintaining this device, great. It's annoying, cause I can't actually upgrade, the economic situation in my country is really, really bad. I would try to maintain this device, but I'm on the school, and then I'll start the University, so I will not have enough free time, and also, my computer sucks and my internet is incredibly slow. I hope someone starts maintaining this device, or that magically a box with a nexus appears in the door of my house.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
BTW, is Blisspop more stable than pure CM? I'm just getting tired of wipe cache, fix permissions or flash the whole ROM over and over again...
HaggisIV said:
Your best option is to find the last build that works, and stick with it.
Click to expand...
Click to collapse
Ah, but there's the rub. Each nightly is only kept for a week or two, and then it's gone. The last build I had good luck with was made almost three months ago.
HaggisIV said:
I'm not completely sure, but I believe the maintainer of Blisspop (which is a fork of CM) stated that the razr m would be getting cm13 eventually.
Click to expand...
Click to collapse
Good news, then. My fingers are crossed that the builds will be at least as usable as the early CM 12.1 ones were (or at least, as I remember them). Maybe it'll be a reasonable last stand.
ATTACK said:
The only CM dev for the Razr M was dhacker, and he stopped supporting the Razr HD/M a long time ago, he moved on to the Nexus 6.
Other then dhacker, I know that kabladan was supporting CM for the Razr HD, but I don't know if he's still around or willing to support the Razr M.
Click to expand...
Click to collapse
Well, crud. I know that someone is building msm8960 CM11 builds with a CM12 kernel (works on the RAZR M), but I doubt anyone would go out of their way to dual-support when it involves a separate build.
ATTACK said:
I know I haven't been much help, but at this point there probably won't be much support for the Razr M anymore. As the device get older people move on.
Click to expand...
Click to collapse
Yeah, I know. It also depends on the phone's popularity (despite having no official support and being older than the RAZR M, the Galaxy Nexus is STILL getting unofficial AOSP/CM builds from multiple developers, including experimental AOSP builds for Android 6.0). I guess the phone fell off the radar too quickly.
ATTACK said:
Have you tried a Verizon MVNO like Page Plus?
Click to expand...
Click to collapse
Not yet. I'm actually on a relative's family plan, which is a little cheaper for me overall. I'd been planning for a while now to renew my contract and get a subsidized 2014 Moto X, but then yesterday I learned of Verizon's freaking absurd determination to push people off contracts ...
Maybe I'll just save up and buy something decent off Swappa. It's gonna take time no matter what.
trivialPotato said:
I hope someone starts maintaining this device [...]
Click to expand...
Click to collapse
I keep hoping against hope that maybe we could convince someone to put in enough work for a last hurrah - just one snapshot or snapshot-quality build (even an AOSP one). But it may never happen.
trivialPotato said:
BTW, is Blisspop more stable than pure CM? I'm just getting tired of wipe cache, fix permissions or flash the whole ROM over and over again...
Click to expand...
Click to collapse
I tried the October 7 build for about a week, but it kept spontaneously rebooting on me; that was the real last straw that led me to running CM 11. Maybe they fixed that in more recent builds, but I wouldn't get my hopes up.
Strife89 said:
Ah, but there's the rub. Each nightly is only kept for a week or two, and then it's gone. The last build I had good luck with was made almost three months ago.
Good news, then. My fingers are crossed that the builds will be at least as usable as the early CM 12.1 ones were (or at least, as I remember them). Maybe it'll be a reasonable last stand.
Well, crud. I know that someone is building msm8960 CM11 builds with a CM12 kernel (works on the RAZR M), but I doubt anyone would go out of their way to dual-support when it involves a separate build.
Yeah, I know. It also depends on the phone's popularity (despite having no official support and being older than the RAZR M, the Galaxy Nexus is STILL getting unofficial AOSP/CM builds from multiple developers, including experimental AOSP builds for Android 6.0). I guess the phone fell off the radar too quickly.
Not yet. I'm actually on a relative's family plan, which is a little cheaper for me overall. I'd been planning for a while now to renew my contract and get a subsidized 2014 Moto X, but then yesterday I learned of Verizon's freaking absurd determination to push people off contracts ...
Maybe I'll just save up and buy something decent off Swappa. It's gonna take time no matter what.
I keep hoping against hope that maybe we could convince someone to put in enough work for a last hurrah - just one snapshot or snapshot-quality build (even an AOSP one). But it may never happen.
I tried the October 7 build for about a week, but it kept spontaneously rebooting on me; that was the real last straw that led me to running CM 11. Maybe they fixed that in more recent builds, but I wouldn't get my hopes up.
Click to expand...
Click to collapse
The last build that "worked" for me is really old, like 4 months old, and with "worked" I mean booting without problems, right now every nightly boots whenever it wants, and if it boots I get some nice ANR when I open apps like Keep, Look of Disapproval, WhatsApp, etc... I would love a full working AOSP build, unfortunately I can't actually build it with 2gb of ram, a 2ghz dual core processor and a 120gb hard drive...
Have you tried Exodus ??
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
Thanks man, I'll try it, I hope I can use Keep without wait 10 seconds till the SystemUI reboots.
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
Thanks for the suggestion. I tried it last night, but alas: not even eight hours in, I got a dreaded spontaneous reboot (I pulled the phone out of my pocket to send a message, and found it in the middle of the boot animation). I had the exact same apps installed (save for the Gapps package, of course; I used a Micro Open Gapps package) as my CM 11 installation, which has yet to reboot in that way.
Attached is the output of /proc/last_kmsg, which I dumped to the microSD card before restoring my CM 11 image.
Strife89 said:
Thanks for the suggestion. I tried it last night, but alas: not even eight hours in, I got a dreaded spontaneous reboot (I pulled the phone out of my pocket to send a message, and found it in the middle of the boot animation). I had the exact same apps installed (save for the Gapps package, of course; I used a Micro Open Gapps package) as my CM 11 installation, which has yet to reboot in that way.
Attached is the output of /proc/last_kmsg, which I dumped to the microSD card before restoring my CM 11 image.
Click to expand...
Click to collapse
Thats weird, I'll stick with it, its working perfectly fine for me, I only experienced a reboot when started recording the screen, but that happened with CM anyway. I haven't got a single SystemUI reboot, ANR exceptions or anything. I'll check your log to see if I find something, but you should try formatting your sd card (if you have one on it).
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
works fine not given me problems
When I'm back at work I will attempt to build CM13 for xt907 and just see how bad it goes. I'm not opposed to putting some work in, but with holidays coming up I will be traveling and I also have some large projects due for my senior CSCI project. I do think that the RAZR M is probably approaching end of life as far as software support, as sad is that is.
Sent from my XT1095 using Tapatalk
Nifty.
It would be funny out of a note 3, droid turbo, HTC m8, tab4, and tab 2 that my razrm gets marshmallow first.
Looks like my turbo may be getting it very soon as well.
Sent from my XT1254 using XDA Free mobile app
BlissPop
I tried CM12 in June & July and had nothing but instability. BlissPop has been perfect since August (after some minor regressions in July). Personally, I've found that I enjoy BlissPop on the Razr M more than I enjoy CM12 on my tablets. The only issue I have with BlissPop is that if my phone dies the first time I boot up it can't find my SIM card. But a reboot fixes that .
rockon999 said:
I tried CM12 in June & July and had nothing but instability. BlissPop has been perfect since August (after some minor regressions in July). Personally, I've found that I enjoy BlissPop on the Razr M more than I enjoy CM12 on my tablets. The only issue I have with BlissPop is that if my phone dies the first time I boot up it can't find my SIM card. But a reboot fixes that .
Click to expand...
Click to collapse
That happened me with both CM12.1 and Blisspop.
trivialPotato said:
That happened me with both CM12.1 and Blisspop.
Click to expand...
Click to collapse
How about your cm13?
EzraDi said:
How about your cm13?
Click to expand...
Click to collapse
I haven't tried it cause I haven't found any builds for KKBL, and I dont feel like going back to JellyBean. xd
trivialPotato said:
I haven't tried it cause I haven't found any builds for KKBL, and I dont feel like going back to JellyBean. xd
Click to expand...
Click to collapse
I wanna try cm13 too but I find going back to jb very tedious!
Latest CM12.1 Nightly Build Working Fine.
2016-05-23
I have two Droid Razr M’s both running CM12 for about two years. I just tried to downgrade to JBBL so I could try CM13. No luck, had a boot loop after flashing the JBBL recovery. So I RSD’d back to KK and then to my backup of CM12. When I find a CM12 that works real great, (most have been for the last year) I make a backup. My backup is 05/09. I have updated both phones to 06/27 and they are both running great, no data drops and all my Bluetooth stuff works fun. I hope in the future we can upgrade to CM12 with the KK recovery. These legacy phones are great with the bootloader unlocked.
Related
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
tele_jas said:
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
Click to expand...
Click to collapse
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
mhodak said:
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
Click to expand...
Click to collapse
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
xgerryx said:
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
Click to expand...
Click to collapse
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
mhodak said:
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
Click to expand...
Click to collapse
My thoughts are differently, base on the many issues people are running when trying to get back to stock and the fact they there's 2 B20 versions around (B20 Stock & B20_boot) make things a Little harder to do, like for sample,
I have the B20_boot version and as you can see I uploaded a backup with Xposed debloated and Rooted (I can consider that backup/ Custom ROM) but stock B20 can't use that backup as far as I know... I can easily release a flash able zip base on my backup but (Xposed,Debloated,rooted) but I bet only 5% of the user are using b20_boot.
So till find a way or just way till ZTE release a firmware image we are going to be little stuck with just CM which is getting more stable every day/week
xgerryx said:
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
Click to expand...
Click to collapse
First, the Moto X Pure was widely available. It was not shipped out in smaller batches once a month. When it was released, it was available for everyone to purchase. For the Axon 7, the first batch and second small batches of phones sold out during pre-order, and the third batch hasn't even shipped yet. (and it hasn't received a wide release in Europe yet either, think they just had one small batch)
Also, the Moto X Pure had bootloader unlock available at launch. The Axon 7 did not get a bootloader unlock method until August 11th, less than a month ago. (and at this time, there is no bootloader unlock for the European or Chinese models, just the North American model)
And just as a reminder, the Moto X Pure launched in early September. Dev for CM12.1 started in late September. The first custom ROM, an alpha of CM12.1, was released a month later, in the beginning of October.
Would love to hear of any news regarding any or all custom roms or wips for the Sprint Galaxy S4 in CM 14 (7.0) flavors?
Really hoping that our little three year old device is getting at least a custom version of it. Have been happy with the dev previews and how well googles made it so far.
If there's another threads regarding this or that explain indepth more about it. Do please link me to them.
Would be much appreciated.
-Willy
The first one we will be able to boot will probably be the i9505s Android n. Right now it doesn't work on mine. Then soon after cm14 will come out for it, then a few others. I might Mike a tweaked cm14... but I'm not sure.
RDChase said:
The first one we will be able to boot will probably be the i9505s Android n. Right now it doesn't work on mine. Then soon after cm14 will come out for it, then a few others. I might Mike a tweaked cm14... but I'm not sure.
Click to expand...
Click to collapse
I see, well those do seem to be the bases for most custom roms. At least from what I've see previously, although if they do get it successfully done (have seen some boot and working well). I'll have more faith that this little bugger can last me another year. If not I can always upgrade to a note model and mod that.
Thanks for the reply, really hoping we get someone good working on this.
Yeah, I really hope there can be a CM14 rom for this phone. I can't get a new phone, so I hope for the best, and if not... CM13 isn't that bad I guess.
Cheese014 said:
Yeah, I really hope there can be a CM14 rom for this phone. I can't get a new phone, so I hope for the best, and if not... CM13 isn't that bad I guess.
Click to expand...
Click to collapse
Honestly I'm running CM13 atm, and it's been perfect so far with a couple xposed mods. A couple features could be reworked and fixed. But nonetheless it's been running perfectly, hell even battery got better. The s4 if updated even on cm13 is still gonna last a very very long time. Mine will probably see use well into 2017-2018. Even after I get the note 3 or 4.
But hey lets keep praying and hoping man. I really do hope they can for us, like they just got it running (albeit it not daily) on a 7 year old device made for windows (don't quote me on that). So lets hope
Hey guys,
I used to do ROM Reviews for the Nexus 6 a long time ago but got carried away with work and had to slow down (we all know how much time and effort it can take to wipe and restart with a new ROM). I feel like the reviews helped spark discussion and the responses to the reviews really helped me understand what factors mattered most to the average user.
Anyways, is there any interest in me starting this up for the Pixel? I've used PureNexus for quite some time now and feel like I have a very good grasp on it in terms of features and performance. I'm downloading and configuring Hexa tonight, so I can start with a comparison (outside of stock). If there's interest, I'll plan to post the first review at the end of this next week (around 3/4 Feb).
EDIT: I'm going to wait on this until the GApps issues all get ironed out. I'd love feedback on which ROMs to try, so I can start with the ROMs people want first.
Could use some in-depth reviews here. Perhaps a comparison to stock.
CyberLykan said:
Could use some in-depth reviews here. Perhaps a comparison to stock.
Click to expand...
Click to collapse
Any ROM preference for the first one?
phishfi said:
Any ROM preference for the first one?
Click to expand...
Click to collapse
Hexa would be nice. I've been contemplating flashing it but would like a review to compare it with PN
Sent from my Pixel using XDA Labs
S8ntsHaz3 said:
Hexa would be nice. I've been contemplating flashing it but would like a review to compare it with PN
Sent from my Pixel using XDA Labs
Click to expand...
Click to collapse
So I tried installing Hexa last night. Coming from PureNexus, I played it safe and wiped everything first, didn't even install TWRP (just used fastboot to boot into TWRP every time). Still, I had nothing but issues with Google Play services. I'm also not a fan of all the AOSP apps that LineageOS includes. I wish there was an option during set up where it asks if you want to keep them, so users can decline the ones they'll never use (I'm fine with them including the essentials, like "Messaging", but I can't stand having the AOSP Email app and a bunch of other).
I then tried to install Oct-N, with a number of issues again.
If/when I do this, I'm going to have to wait until the process becomes less painful. I liked PureNexus a LOT, but for the moment (I'll keep trying next weekend) I'm going to stick with stock w/ root.
phishfi said:
So I tried installing Hexa last night. Coming from PureNexus, I played it safe and wiped everything first, didn't even install TWRP (just used fastboot to boot into TWRP every time). Still, I had nothing but issues with Google Play services. I'm also not a fan of all the AOSP apps that LineageOS includes. I wish there was an option during set up where it asks if you want to keep them, so users can decline the ones they'll never use (I'm fine with them including the essentials, like "Messaging", but I can't stand having the AOSP Email app and a bunch of other).
I then tried to install Oct-N, with a number of issues again.
If/when I do this, I'm going to have to wait until the process becomes less painful. I liked PureNexus a LOT, but for the moment (I'll keep trying next weekend) I'm going to stick with stock w/ root.
Click to expand...
Click to collapse
Have you tried Dirty Unicorns yet?
Sent from my Pixel using XDA Labs
for me its either pure nexus or dirty unicorns. DU has a few more options and better battery life currently. at least for me. the pixel doesnt have anywhere near the dev community the nexuses or oneplus3t have. but ill take what I can get.
fix-this! said:
for me its either pure nexus or dirty unicorns. DU has a few more options and better battery life currently. at least for me. the pixel doesnt have anywhere near the dev community the nexuses or oneplus3t have. but ill take what I can get.
Click to expand...
Click to collapse
I don't think that's necessarily true. The Pixel's system is completely different from either of those devices, and it's taking significantly longer for the devs to sort out all of the kinks. It doesn't help that it's MUCH more consumer-focused than any of Google's previous phones or tablets.
I tried DU a long time ago on an older device, but not on my Pixel. Maybe I'll try that next. Does DU have a thing against sharing their builds on XDA?
phishfi said:
I don't think that's necessarily true. The Pixel's system is completely different from either of those devices, and it's taking significantly longer for the devs to sort out all of the kinks. It doesn't help that it's MUCH more consumer-focused than any of Google's previous phones or tablets.
I tried DU a long time ago on an older device, but not on my Pixel. Maybe I'll try that next. Does DU have a thing against sharing their builds on XDA?
Click to expand...
Click to collapse
I dont think a lot of devs have the pixel or xl. they are pretty expensive. but yes I know the new partition scheme is a pita. thats why we dont have a stable twrp yet. ive yet to see another person with a pixel despite it selling well. I mostly see samsungs and iphones.
im not sure what the beef is with DU and xda. they are at devbase. I didnt join the site, just bookmarked for the builds.
fix-this! said:
I dont think a lot of devs have the pixel or xl. they are pretty expensive. but yes I know the new partition scheme is a pita. thats why we dont have a stable twrp yet. ive yet to see another person with a pixel despite it selling well. I mostly see samsungs and iphones.
im not sure what the beef is with DU and xda. they are at devbase. I didnt join the site, just bookmarked for the builds.
Click to expand...
Click to collapse
Fair point, especially if they enjoy the Nexus 6P...
Can you get Oct-N to work and leave a review? Seems interesting.
i have been running DU since it was released and recently flashed purenexus almost a week ago. while the 2 roms have similar mods i feel DU had better battery life. both roms run smooth but battery life is the deciding factor on which rom to use as a daily driver.
Every where i look the Qualcomm moto e4 custom development is stagnant. Not even security updates. Does anyone know if anything's happening for this phone??...............
I've been trying to teach myself everything i can about Android but I'm not at the level where i can code the OS to my preference.
Thank you for any and all help
neojpl said:
Every where i look the Qualcomm moto e4 custom development is stagnant. Not even security updates. Does anyone know if anything's happening for this phone??...............
I've been trying to teach myself everything i can about Android but I'm not at the level where i can code the OS to my preference.
Thank you for any and all help
Click to expand...
Click to collapse
OTAs on stock seem relatively current (XT1768). Toss in Xposed framework and a few well regarded modules and there is no need to muck with a custom ROM and the associated headaches. I know...stock sucks by definition just because it isn't custom or carry a boss name. iDK bro - I kinda like to use my device vs manage it. Radical.
Davey126 said:
OTAs on stock seem relatively current (XT1768). Toss in Xposed framework and a few well regarded modules and there is no need to muck with a custom ROM and the associated headaches. I know...stock sucks by definition just it isn't custom or carry a boss name. iDK bro - I kinda like to use my device vs manage it. Radical.
Click to expand...
Click to collapse
My pc stopped working for no apparent reason. Or i would definitely be back on stock w/xposed. Thanks
neojpl said:
Every where i look the Qualcomm moto e4 custom development is stagnant. Not even security updates. Does anyone know if anything's happening for this phone??...............
Click to expand...
Click to collapse
I was wondering the same thing. Just got a boost xt1766 which (from what I read) I had to put on a custom ROM to get it working with gsm carriers. I flashed the unofficial lineage is 14.1 from @squid2 and its working great, but no security updates since December.
I was wondering if development is not happening for a reason (issue with this device) or is it likely to pick up when Lenovo stops putting out OTAs for it?
astrod said:
I was wondering the same thing. Just got a boost xt1766 which (from what I read) I had to put on a custom ROM to get it working with gsm carriers. I flashed the unofficial lineage is 14.1 from @squid2 and its working great, but no security updates since December.
I was wondering if development is not happening for a reason (issue with this device) or is it likely to pick up when Lenovo stops putting out OTAs for it?
Click to expand...
Click to collapse
For me, it's just been that I had neither time nor the mood to work on it when my father fell ill and later passed away. I've started working on Android again, but it'll probably be a month or two before I get around to revisiting this device (if I do). I'm currently focused on the msm8916 family that i support officially.
squid2 said:
For me, it's just been that I had neither time nor the mood to work on it when my father fell ill and later passed away. I've started working on Android again, but it'll probably be a month or two before I get around to revisiting this device (if I do). I'm currently focused on the msm8916 family that i support officially.
Click to expand...
Click to collapse
I am saddened to learn of your fathers passing. I was aware he took ill but did not know the magnitude. Best wishes to you and family during a difficult time.
squid2 said:
For me, it's just been that I had neither time nor the mood to work on it when my father fell ill and later passed away. I've started working on Android again, but it'll probably be a month or two before I get around to revisiting this device (if I do). I'm currently focused on the msm8916 family that i support officially.
Click to expand...
Click to collapse
Very sorry to hear of your father's passing. I did not want this to be a push for anyone to help, just wondering out loud. Thanks for the response and I wish you and your family my deepest condolences for your loss.
astrod said:
I was wondering the same thing. Just got a boost xt1766 which (from what I read) I had to put on a custom ROM to get it working with gsm carriers. I flashed the unofficial lineage is 14.1 from @squid2 and its working great, but no security updates since December.
I was wondering if development is not happening for a reason (issue with this device) or is it likely to pick up when Lenovo stops putting out OTAs for it?
Click to expand...
Click to collapse
There is a telegram group with more active development. Pm for a link.
You install a new ROM, and get used to it
After a couple months, pretty much everything is working correctly, you don't foresee ever updating the OS again
Six months in, you realize some things aren't working as they should anymore, but you can't tell which app update broke it and google isn't giving you a solution to your weirdly specific issue
You realize that at this point, a clean reinstall of the OS is your best bet
You're going through all that trouble, might as well try an up-to-date ROM
After a couple months...
Been happy with my ZUK for almost half a year since I last had to update the OS, now my music is getting cut off near the end on a lot of players and I don't know how to fix it. The Google Assistant gets stuck confirming a reminder. Clearing caches of all sorts didn't do anything, so here I am.
I hope Pie ROMs are stable, cause my AEX Oreo is bursting at the seams.
CosmicBovine said:
You install a new ROM, and get used to it
After a couple months, pretty much everything is working correctly, you don't foresee ever updating the OS again
Six months in, you realize some things aren't working as they should anymore, but you can't tell which app update broke it and google isn't giving you a solution to your weirdly specific issue
You realize that at this point, a clean reinstall of the OS is your best bet
You're going through all that trouble, might as well try an up-to-date ROM
After a couple months...
Been happy with my ZUK for almost half a year since I last had to update the OS, now my music is getting cut off near the end on a lot of players and I don't know how to fix it. The Google Assistant gets stuck confirming a reminder. Clearing caches of all sorts didn't do anything, so here I am.
I hope Pie ROMs are stable, cause my AEX Oreo is bursting at the seams.
Click to expand...
Click to collapse
This is a tradeoff that everyone of us agrees to, when we flash a custom ROM
We trade a little bit of stability for some really useful customizations and preferred UI
visheshjain25 said:
This is a tradeoff that everyone of us agrees to, when we flash a custom ROM
We trade a little bit of stability for some really useful customizations and preferred UI
Click to expand...
Click to collapse
This is the general case, talking about zuk z2 maybe custom roms are more stable than stock zui ?, and for sure more "Occidental-friendly"
So true for alllllll phones out there.
Only those who don't care about all this at all are best at peace.