Wow. Just wow. I mean, this phone has got to be at least nine months old by now. And guess what - I haven't seen a stable build of CM11 yet. In fact, I haven't seen a build where audio even works as it should, and in the latest nightly, the audio derped out completely, even in calls. GPS doesn't work. WiFi drops every 5 minutes or so. Mobile data doesn't activate for about half an hour, even then it drops out every 5 minutes, just like the WiFi.
Cyanogenmod is beyond a joke. The Moto G runs stock android out of the box, so there is literally nothing for the CM team to modify to get CM to work on it. They should at least get audio and GPS working - in contrast there is an unstable, unofficial build for the Samsung Galaxy Ace "s5830" of CM11 that has more things working than the current "official", "stable" build on the Moto G.
I thought CM was meant to be about bringing Stock android to all devices, on Google's schedule, long after OEMs and carriers have dropped support for these devices. What's crazy here is that the Moto G's "stock" software has had a version of 4.4.4 available for months; Motorola have finished it, and carriers have got round to rolling it out - and it's been on my phone for several weeks now.
My point is, Motorola (who are very lazy when it comes to updates) have finished 4.4.4, given the update to carriers, who then procrastinated about rolling it out for weeks before finally rolling it out, and still, despite all this, Cyanogenmod haven't even got a stable build of kitkat at all, let alone 4.4.4, to offer. They are literally worse than OEMs and carriers at updating their phones on time.
If you have a Moto G, please do not ruin it by installing cyanogenmod on it. It is useless beyond belief, and you will cry for days about having turned your phone into an expensive paperweight. On the bright side, if that corner of your piece of paper just won't stick down, go ahead and install CM.
Is this is a complain or something like that lol? BTW I don't have any issues with CM or CM based ROMs.
Here we go. At this point, I am also waiting for a more stable version of CM 11 for Falcon. Yes, there are issues with it. Some are pretty notable, others are barely (or not at all) notable.
The thing here is that you are using open sourced software. There are some really, really experienced developers working on CM 11 to make it better for us, the end users. However, and I have seen this happen before, some lesser-experienced developers might forget about something every once in a while causing issues on the devices. This can happen. It happens to everyone, Motorola developers included (just look at the reports of battery drain issues across the Android versions).
CyanogenMod is a great team and are introducing features that improve Android in small, yet very useful ways. These features, in themselves, are working brilliantly. The only quirk with this is that CyanogenMod is trying to get each and every different phone to run Android in combination with those features. I might be wrong here, but that seems like that's causing a lot of trouble over some different devices, including the Moto G. If CyanogenMod adds a new feature to (for recent issues' sake) audio for devices CyanogenMod support (an update library for example), there's always a chance that gets pushed to the Moto G, and there's something with the Moto G that makes it not function properly. This is really notable in the Nightly releases. The most recent Nightly releases, 07-24 and 07-25 contain an issue that makes it so that audio isn't functioning properly. This is always a possibility. It's a Nightly, unstable, release. You cannot complain that it's not working on a version that's not intended to be stable.
This brings me to another point, the "Stable" release category. Moto G's most recent "Stable" release, M6, is really pretty stable. On everyday use, I could not see any one issue with it. The reason for there not being a M7 or M8 "Stable" release, is that there's issues with them, so CyanogenMod decided that it shouldn't be classed "Stable" for our device and therefor did not release them. I'm sure that, when there's a new safe-to-be-called-Stable release, CyanogenMod will push that to our device as well.
CyanogenMod is open source. There are bugs in it. You sign up for that in exchange for some new features and continued support from the developers. For the most part, the core software is stable. It's the "drivers" for the phone that are causing issues. Also, the new features have to be tested and the bugs that are in them should get reported to CyanogenMod so that the team can fix them. If you don't report the bugs, how would they get squashed? I have reported the audio issue on the most recent Nightly releases to CyanogenMod, which brings it to their attention and, while it is being fixed, the Nightly releases are temporarily postponed until the issue is fixed to prevent any further harm that this issue might cause. That is what CyanogenMod is about. They release something, obtain feedback, fix it, release that fix, obtain feedback, fix it and release that fix. That cycle keeps continuing. If they don't obtain feedback, they will just keep doing what they are doing -- add new features, which might cause the bugs you found to keep being there forever and ever.
And you may say that trying to report stuff in Nightly releases isn't 'allowed' on their feedback site, you're looking in the wrong place. You should look in the Nightly Regressions section of the CyanogenMod JIRA -- not the regular Issues section.
If you have any comment on what I just stated, please do reply to me. If there's anything that's wrong with what I just stated, please do correct me. If you dislike anything about what I just stated, please do not just post a hate comment on it -- actually explain what you don't like and why so I can, in turn, respond to that as well.
Thanks for reading.
I've never had problems with CM11 i'm using xt1032 btw
Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.
I've just heard they've stopped development for the Moto G entirely. Motorola and the various carriers their phones are on have got their act together and released 4.4.4, CM haven't finished... ...anything.
moto_g_n00b said:
Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.
Click to expand...
Click to collapse
Whoa… No need to swear. I'm not flaming on you. I even partially agree with you. I just provided you with what I think about the matter, and nothing negative about any of what you commented. There's absolutely no need to go crazy about what a few members comment on your post.
Have a great day, sir, and lighten up a bit.
Related
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
We're not going to get official support for 5.0 if that's what you mean. As for custom ROMs, I'm sure it will happen eventually.
Once Android 5.0 L is officially released, we intend to bring this latest upgrade to many of our other Motorola devices, as well. This includes Moto X (1st and 2nd Gen), Moto G (1st and 2nd Gen), Moto G with 4G LTE, Moto E, Droid Ultra, Droid Maxx and Droid Mini. We're still working out the details on timing and the upgrade depends on our partners' support so stay tuned to our software upgrades page for the latest and greatest.
Click to expand...
Click to collapse
http://www.motorola-blog.blogspot.hu/2014/10/nexus-6-from-google-and-motorola-more.html
...and it begins...Took less than a day for someone to ask. It's not even released yet. Coming to the Razrs? Not a snowball's chance in hell. Unofficial, maybe? These things are at EOL and they received a barely functioning official KK update.
Sent from my HTC6525LVW using Tapatalk
Moto kind of hinted at the possibility of having other devices on Lollipop, but I'm not holding my breath this time.
derpyherp said:
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
Click to expand...
Click to collapse
We're not even going to get KK 4.4.4 officially. The only way we have that is via custom ROMs like CM11.
Those of us in the soak test were told that this latest OTA (.15 release) was the FINAL release for this phone. No more updates. That came straight from a Motorola person in the private soak test forums.
So, don't hold your breath for an "official" Lollipop release. As others have stated, you might see it via Cyanogen or some other custom ROMs, but that will only be for those who have unlocked bootloaders. Those who have already upgraded to the latest OTA without unlocking are screwed forever.
Besides, CM11 for this phone has just recently become completely stable. L isn't even out yet.
here's is how its going to go down.
L comes out nov 3.
cyanoagen inc /PA will merge the code to their repos; take about a month before the first nightly comes out. cm11 is EOL as they move to Lollipop.
gummy slim and others will take the cm base and fork to get their ROMs running too.
then dhacker epinter etc. our great maintainers will port to our devices; first nightly will be for the very brave.
about 2-3 months of bug fixes until it becomes usable.
give or take by feb we have a daily driver of android L
question is with the f* ups of jjbl and kkbl which kernel will be supported to L, i'm sure cm will use a custom kernel just like it did with cm11 before the moto kk ota.
paranoid android to make l for msm8960 unified
just saw a reply from cj360 he will be working on l for msm8960 devices jbbl and kkbl. he said dont hold your breath ait will take a while
Gr8 stuff so far!
I'm enjoying my recently renewed phone anyways!
Btw, this L inspired Nova Pro customizable theme rocks and ART runtime is superb!
Sent from my Razr HD, Unlocked KKBL, latest CyanogenMod CM11 KK 4.4.4 ROM, ART runtime.
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
the build
cartpig said:
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
Click to expand...
Click to collapse
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
derpyherp said:
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
Click to expand...
Click to collapse
No, it has issues. Blue-tooth is wonky and Netflix and Google Play Movies won't work (you can't watch anything).
DHacker told me via Twitter that it's due to the DRM libraries. He hasn't figured out the right combination yet to get it working,
But, other than that, it works well.
11/16 has the battery percentage in the notification icon.
11/17 apparently has radio issues. Some people have reported that it works for 5 minutes and then the radio dies. A reboot fixes it for about 5 minutes, and then it dies again. Might want to stay away. I'm going to test it, and if I see the same issues, I'll go back to 11/16.
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Not_A_Dev said:
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Click to expand...
Click to collapse
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Click to expand...
Click to collapse
Thanks. Just posted my impressions of running the 11/16 build on that thread.
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad? Xposed doesn't work on it, and if you're running a custom ROM you're already more than likely modified beyond anything that "Android L" is going to give you...
Other than "material design" and "ART" (along with being near impossible to root without an unlocked bootloader) I haven't even read up on what is so special about L that everyone is creaming their pants over it. Please someone enlighten me to the goodness of L other than "it's Google's lastest software".
EDIT: An acceptable answer would be to get off of the botched up KK Moto gave us... twice... Thus why I am sporting DU now - never going back.
LifeAsADroid said:
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad?
Click to expand...
Click to collapse
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Not_A_Dev said:
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Click to expand...
Click to collapse
Lol I will totally agree with you on the battery life thing! I thought my phone was on its way out with how fast the stock KK versions were draining my battery. Constantly had to keep the phone on a charger when I was in one place. I will say that the battery life on DU was one of the things that really caught my attention from the start. Phone makes it through the day, can make it through the night if I forget to charge it overnight, and no more does the phone heat up to 125-140F. Highest I've seen, even with charging, screen on, streaming movies or TV over LTE, has been 98F. Night and day compared to the stock KK ROMs Moto vomited at us. I'd be surprised if other custom KK ROMs for our phones didn't have much improved battery life over that failed attempt at a PR stunt giving us stock KK.
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
+1 for dirty unicorn dev
Not_A_Dev said:
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
Click to expand...
Click to collapse
I used to be huge into XDA and loved getting involved with the community. I started all the way back on a Samsung Vibrant. After being so busy with life and all I kinda fell out of it but saw Lineage OS and wanted to get into it again. After looking at the device list I picked up the H830 and got to rooting but looking at the community here, it doesn't seem like many members are trying it out. If you are can I get some of your feedback on it? I tried to flash once but got stuck in the bootloop so I hope to get it soon. Any advice would be much appreciated.
OldHemp said:
I used to be huge into XDA and loved getting involved with the community. I started all the way back on a Samsung Vibrant. After being so busy with life and all I kinda fell out of it but saw Lineage OS and wanted to get into it again. After looking at the device list I picked up the H830 and got to rooting but looking at the community here, it doesn't seem like many members are trying it out. If you are can I get some of your feedback on it? I tried to flash once but got stuck in the bootloop so I hope to get it soon. Any advice would be much appreciated.
Click to expand...
Click to collapse
You won't see much on T-Mobile threads as all the ROMs and even kernels are pretty much posted in main g5 threads. As far as which ROM to use, I recommend RR (and I've tried all available ROMs for our device too), although it may or may not continue to get updated, will depend if me or someone else pick up doing builds, whereas Los will continue to be updated on a weekly basis but those are not tested before release and may end up in bootloops like you stated you had. If wanting to run LOS and you end up in bootloops with latest build, I recommend downloading an earlier build and install that. Also, no matter what ROM based on lineageos you decide to use will have a couple issues. No NFC, some report issues with Bluetooth and some issues with camera (camera quality especially in low light isn't as good as stock, recently issues with saying videos). Hopefully this helps Any other questions feel free to ask.
jeffsga88 said:
You won't see much on T-Mobile threads as all the ROMs and even kernels are pretty much posted in main g5 threads. As far as which ROM to use, I recommend RR (and I've tried all available ROMs for our device too), although it may or may not continue to get updated, will depend if me or someone else pick up doing builds, whereas Los will continue to be updated on a weekly basis but those are not tested before release and may end up in bootloops like you stated you had. If wanting to run LOS and you end up in bootloops with latest build, I recommend downloading an earlier build and install that. Also, no matter what ROM based on lineageos you decide to use will have a couple issues. No NFC, some report issues with Bluetooth and some issues with camera (camera quality especially in low light isn't as good as stock, recently issues with saying videos). Hopefully this helps Any other questions feel free to ask.
Click to expand...
Click to collapse
I loved using the this device but unfortunately mine started the continuously boot loop. Even after going back completely to stock the problem persisted so I had to get a different device. But the community was awesome for the day I got to be a part of it.
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Lineage 14.1, Official. Installed the 'official way' (motorola unlock code). Not rooted. For me, working like a charm
You should try a different rom. AOSP Extended is based on AOSP-CAF. When I used a different ROM but also based on AOSP-CAF (purenexus) I faced the same problem.
Right now I’m on unofficial Lineage 15 (it still has some issues: random reboots sometimes but that seems to be an upstream issue as Pixels are also rebooting and having to use Footej camera to record video).
As @krondar said official LineageOS should be your best choice even though it doesn’t have some other more advanced custom ROM features. (Or just stock ROM from Motorola if you’re OK with Marshmallow)
Quantumstate said:
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Click to expand...
Click to collapse
AOSP Extended is one of the best you can find here. But the version you are using is very old. I would recommend you clean flash the latest version and I believe you will love it.
I tryed Cyanogenmod 13 and it was awesome, and now I'm with Lineage 14.1 and everything is ok... no bugs,
Over the years I've tried every firmware from MIUI to Paranoid Android to CarbonROM to Cyanogenmod to ResurrectionRemix, and all have one set of basic problems or another. And worse, seem to deteriorate over time!
This should never, never happen with an advanced OS in the 21st Century. So I moved to the AOSPs and find the same syndrome! This implies a basic problem with Android -- after so many years it can not be gotten right. It's alarming.
Why is Lineage better? What is it based on? How is it different that it doesn't have these problems? How do you find out that one ROM is working better than all the others?
I've been using purenexus ROM for a few month and never faced any issue,not even a little one. It was 100% stable for me and the perfect ROM for a daily driver. AEX Is very good though and lineage OS 14.1 too.
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Quantumstate said:
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Click to expand...
Click to collapse
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
V-Droid said:
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Click to expand...
Click to collapse
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Quantumstate said:
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Click to expand...
Click to collapse
If you don't have time to be 'bit-twiddling' on your phone then why did you bother on unlocking the boot loader and flashing a custom firmware?
Personally I haven't tried pure nexus, but it is very possible that 5 months ago pure nexus had the same bugs as AOSP Extended. Since they are custom firmwares, they are susceptible to bugs, that's why mainteiners push out weekly or monthly updates.
If you think that pure nexus or any other rom will deteriorate over time then you should probably restore the stock firmware of whatever device you are using, well... That of you have time, if not than don't blame maintainers remember they are not being paid for anything.
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Cobvetsely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Conversely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another (hidden) unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly. Doesn't realize how silly he looks.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Quantumstate said:
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Click to expand...
Click to collapse
Friend we share similar views and sentiments on this subject. We also seem to share in the philosophy that The Due Process Clause, Equal Protection of the Law, and safeguards against unreasonable searches and seizures have essentially all been trampled through the mud when it comes to our privacy and expectations to privacy with respect to our smartphones. Law enforcement having the authority to compel a man (or woman) to unlock their device without constitutional safeguardsl, is synonymous of the police being permitted to kick down the door to a man's house upon a "whim" or a "hunch". Or a cop conducting a traffic stop and subsequent warrantless search of the driver's person and vehicle merely because the cop feels like it. I take great pride in knowing with 100% certainty that any law enforcement who attempts to track or trace my mobile IP, or tries to monitor anything about incoming or outbound data packets on any of my devices is chasing Casper the Ghost. But, anymore I can't be so certain about John Q Law's legal authorization (or ability) to stick his long snout into my device's internal storage. I'm working the final kinks out of a simple process that will completely wipe and heavily encrypt the wiped storage with multiple layers of random binary (with the morbidly numerous anticipation that they actually can and will spend countless man hours and resources on decrypting utterly blank and random blocks of binary jibberish). All with a self determined series of keyfob button presses.
Yeah I know I'm ranting and perhaps being a bit overzealous. But, just like you said, regardless of state or federal appellate court adjudications giving authorities such authorizations, such decisions run afoul of a handful of the most rudimentary tenets of constitutional safeguards.
Word.
Most have given up and acquiesced. But not me. Never. I use Tor to get here, and just about everywhere else. Because I know what can be done.
Most will say that their words are not important enough and so they don't worry. But they do not know that what is Ok today, may not be tomorrow. I used to be in intelligence, and most here would not believe what can happen (and has happened in other nations).
BTW, there is an excellent TV series called The Americans, which I think is as good as the old Mission Impossible series (which came way before Tom Cruise). Although it can never compete with the old Secret Agent ('Danger Man') series, and the John LeCarre series', it is a high-grade and carefully-wrought storyline.
I agree with you that seems no ROM is stable; In fact if your phone is important for you as production device, I would suggest you stick with stock ROM or keep testing until a ROM which works for you and stay there! New version introduce new bug, that's the usual case on Software side, there is no way to avoid.
If you are so sensitive to bugs then stick onto stock rom instead of blaming the developers. Your fault that you can't keep meddling with your device. If you want a totally bugles device then you try to develop a rom by yourself then you will understand what it is to be a developer
MotoJunkie01 said:
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
Click to expand...
Click to collapse
Better than my XT1540, rooted, no other mods except modified host file for ad removal, stock kernel. I have an average 1 bug report a week.
So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?
Nazo said:
So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?
Click to expand...
Click to collapse
The reduction in development is probably partly due to lack of manpower on the official LineageOS team and fewer developers owning certain devices(if there are no developers that own the device, that device doesn't receive any development). It is also partly due to devices becoming more and more secure, this leads to fewer people creating development and fewer devices that are capable of being customized.
It isn't just devices being dropped from development, the size of the XDA community and amount of overall activity on this whole website is also declining.
Sent from my SM-S767VL using Tapatalk