Related
Hello everyone. I know android 4.3 adds multi-user support, however as I've found out over the past week each device has its own rom's (before I thought it was like an OS, one OS to rule them all).
From searching, I found that Cyanogen Mod 10.1 supports multi-users and that I'll probably need a multi-user app share from the app store to make everything work.
Right now my device is running stock firmware (4.1.2 I believe, it's upstairs charging), so I'm wondering what my best bet would be:
1) Find a custom ROM like CM 10.1 and go from there
2) Wait for official 4.3 (I believe I shouldn't hold my breath for this?)
3) Find a way to get 4.3 on the device now. I've seen some people have signatures that mention they're running 4.3 on it.
I kind of know how to do the first, but where can I find a feature listing for custom roms? Everything has been jumbled and confusing. I'd rather be taught to fish then just given a fish. Also is there any advice/recommendations on other rom's out there? (I'm not asking for the best, just a few to take a look at if there isn't a global list)
I have no clue how to do the third. I recently (this week) had to restore a Galaxy S2 phone and I put a good 30 hours before getting it to a state where it's usable. My biggest problem ended up finding the proper rom to use.
Thank you.
CyanogenMod 10.1 is stable and is what I recommend you use. CyanogenMod 10.2 is running 4.3, and from the majority of reports is usable as a daily driver! Don't count on seeing an official 4.3 release ;]
http://en.m.wikipedia.org/wiki/Android_version_history
I've been using PAC ROM. Pretty nice if you know what you're doing. More of a learning curve to get it set up just how you want it, but once you do it's great.
Sent from my Nexus 4 using XDA Premium HD app
dynospectrum said:
CyanogenMod 10.1 is stable and is what I recommend you use. CyanogenMod 10.2 is running 4.3, and from the majority of reports is usable as a daily driver! Don't count on seeing an official 4.3 release ;]
http://en.m.wikipedia.org/wiki/Android_version_history
Click to expand...
Click to collapse
Thanks, it looks like my best bet would be to wait for 10.2 to get completed and then throw that on there.
When should we expect the release of KitKat for the Relay?
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.
Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk
Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app
I'm just wondering what the rooting/ROM'ing experience is like on the Moto G LTE. Is it very straightforward? Is the custom ROM support good? (eg. regular updates?) Any good kernels like Leankernel for the Samsungs?
My Galaxy S3 is on it's way out (or it's already gone, depending on how you look at it)...so with a tight budget my options are this phone, or the Nexus 5. I'm trying to get an idea of what the ROM'ing community is like for this phone since I will probably want to flash Carbon or CM as soon as I take it out of the box. Rooting for the Samsung's has been a real pain since the latest Touchwiz update, so I would like something that's much friendlier.
Thanks
nubreed000 said:
I'm just wondering what the rooting/ROM'ing experience is like on the Moto G LTE. Is it very straightforward? Is the custom ROM support good? (eg. regular updates?) Any good kernels like Leankernel for the Samsungs?
My Galaxy S3 is on it's way out (or it's already gone, depending on how you look at it)...so with a tight budget my options are this phone, or the Nexus 5. I'm trying to get an idea of what the ROM'ing community is like for this phone since I will probably want to flash Carbon or CM as soon as I take it out of the box. Rooting for the Samsung's has been a real pain since the latest Touchwiz update, so I would like something that's much friendlier.
Thanks
Click to expand...
Click to collapse
the experience is overall good i guess..
Rooting Easy
nubreed000 said:
I'm just wondering what the rooting/ROM'ing experience is like on the Moto G LTE. Is it very straightforward? Is the custom ROM support good? (eg. regular updates?) Any good kernels like Leankernel for the Samsungs?
My Galaxy S3 is on it's way out (or it's already gone, depending on how you look at it)...so with a tight budget my options are this phone, or the Nexus 5. I'm trying to get an idea of what the ROM'ing community is like for this phone since I will probably want to flash Carbon or CM as soon as I take it out of the box. Rooting for the Samsung's has been a real pain since the latest Touchwiz update, so I would like something that's much friendlier.
Thanks
Click to expand...
Click to collapse
Rooting the LTE is very easy. There are a few ROMs available, but at present (in my case) the have too many significant bugs - wifi only works on some routers, RAM freezes after a couple of days use.
Carbon and CM are very stable except for the above two bugs for me. But others users are either having no problems or different ones.
SlimKat has just been added to the official page so hopefully they'll get that up and running but it currently just bootloops for me.
It works out alright I guess at least on CM and Carbon (same core dev). Be warned, if you are on 4.4.4 you won't be able to return to stock since there is no image file out there. Downgrading to 4.4.3 is not possible as far as I know.
Slim also just came out with a first build of peregrine. Works pretty well so far, but does not yet support moving apps to the SD card ... next build or two hopefully. The phone only came out in June, so the work is still in progress.
First of all, thanks to iBolski for kindly pointing the finger into the right direction and help me unlock and reflash my recently bought phone.
Now now....
I understand that all or most of the Qualcomm MSM8960 motorola phones share the same rom/s so my question is not about which one would be the correct for this phone model., but for me.
I just landed here but i'm not new to xda, i come from a Galaxy Ace 2 (i8160), great machine using Teamjanica's rom (and that's how is going to stay), i had an LG p990 on which i also put a custom rom (can't remember wich one now...) So i'm not unfamiliar with CM, CWM, reflashing etc... And i know there's always some roms that work better than others or have more/less features than others, I just would love to avoid being the next month or so testing, erasing and starting all over again as ussual.
This is the thing: I'm searching for stability (Under KitKat??? -> my i8160 is flawless and fast!)) smoothness and responsivity.
I have my xt926 flashed with slimrom and is kind of laggy, twitchy, it has some issues with playing music, stutters, freezes, etc... So is quite not what i'm looking for. (And i don't like Nova Launcher, i'm more of Trebuchet or Apex)
The Official JB and KitKat "from Verizon" were lightnings and after taking out all the bloatware they became even better, but there was several things that i didin't like (mainly it's launcher) and there are a lot of things that i love from CM. (Apollo and the DSP manager to name a couple)
So, considering this (and that you are tired of reading me) could the experienced people here point to some light but not skinny, smooth but not sleepy rom that is not filled with "features" (other than the ones that come with vanilla CM -i like the buttons "pie" actually-)
P.S. I can't flash the "official" CM build because CWM 6.0.4.8. says that CM is for a (bunch of phone) and my phone is a ""
I would like to read your suggestions. Thanks in advance.
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