So I'm still on stock 25R build. I never got the 300 update OTA but today I got an update for the "300 incremental update". Is this just the large 300 update combined with the small Incremental update that was released shortly after? I'm holding off from updating Bc of all the battery drain issues I've read about. Can anyone advise?
Sent from my One using XDA Free mobile app
Is it possible to see the build date before updating ? If not do a nandroid backup , do update and see the build date. If it is 11th August , roll back to the nandroid backup. If after 11th August i guess battery drain is fixed.
Both 30O updates were merged into one and this week you get the OTA in a single file. And no, it does not have the battery drain fixes yet.
dayanandgp said:
Is it possible to see the build date before updating ? If not do a nandroid backup , do update and see the build date. If it is 11th August , roll back to the nandroid backup. If after 11th August i guess battery drain is fixed.
Click to expand...
Click to collapse
Battery drain is not fixed at all.
They've noticed the battery drain and solve it but, they will put the fix in the next ota (end of this month i guess). They are waiting that google verifies the ota.
Castore said:
Battery drain is not fixed at all.
They've noticed the battery drain and solve it but, they will put the fix in the next ota (end of this month i guess). They are waiting that google verifies the ota.
Click to expand...
Click to collapse
Google has nothing to do with OTAs on the OPO. They are waiting for the OTA to be quality assured and tested by the QA team and then verified by OnePlus as well as finalizing any other problems which are some pretty crucial problems that needs to be fixed before release.
zephiK said:
Google has nothing to do with OTAs on the OPO. They are waiting for the OTA to be approved by partners/OnePlus as well as finalizing any other problems which are some pretty crucial problems that needs to be fixed before release.
Click to expand...
Click to collapse
If it's correct what I know, if you preinstall gapps you have to pass google control. At least is what has told me in cm11s thread.
Castore said:
If correct what I know, if you preinstall gapps you have to pass google control. At least is what has told me in cm11s thread.
Click to expand...
Click to collapse
Shrug.. I just know that there are still a lot of other kinks to be worked out, the biggest problem right now is that the newest commits are causing a problem with headset detection. I'm pretty sure that they're going to work out those issues before it gets sent to Google if Google is apart of the process.
None of us are employees at OnePlus or Cyanogen, so we're not really 100% certain about the OTA process. Either way, its coming.. if OP can't wait, then flash the nightlies or a custom ROM/kernel with these fixes already in place
zephiK said:
Shrug.. I just know that there are still a lot of other kinks to be worked out, the biggest problem right now is that the newest commits are causing a problem with headset detection. I'm pretty sure that they're going to work out those issues before it gets sent to Google if Google is apart of the process.
None of us are employees at OnePlus or Cyanogen, so we're not really 100% certain about the OTA process. Either way, its coming.. if OP can't wait, then flash the nightlies or a custom ROM/kernel with these fixes already in place
Click to expand...
Click to collapse
Now I'm using Cm11 nightly that runs a lot better than 11s. At least no battery drain at all but, 11s has a lot features and optimization that are missing in Cyano "vanilla"
For example, my piston headset are not recognized with cm11, I have to use normal headset, no problem at all with 11s.
But the battery drain is too huge.
Castore said:
Now I'm using Cm11 nightly that runs a lot better than 11s. At least no battery drain at all but, 11s has a lot features and optimization that are missing in Cyano "vanilla"
For example, my piston headset are not recognized with cm11, I have to use normal headset, no problem at all with 11s.
But the battery drain is too huge.
Click to expand...
Click to collapse
Thats what I meant by one of the crucial bugs happening right now with the nightlies. If OnePlus shipped the OTA with this problem, it'd fix some problems and arise new ones.
The workaround to the problem is to put your headset in half way to hear a static (have auto play music on) and then music should play, wait 2-3 secs and then insert it fully. Its being looked into as I've reported it. Not having any battery drains here, flash a kernel like Franco Kernel
Merged the latest patches from CM which fix the high battery drain during idle that was introduced in the latest 30O OTA
Click to expand...
Click to collapse
If you still have battery problems then its user fault with wakelocks.
Related
To help sort out good nightlies from buggy ones, please post your best choice CM7 nightly here. This will help others who want to test nightlies to try out good ones for best time utilization.
CyanogenMod-7-110819-1459-NIGHLY-Jordan
I prefer this one.
Battery consumption is very high, 12 hours maximum.
-rsp1
Happily using 0826, no issues. Its pretty hard to have a decisive recommendation as users are running so many different apps and configurations..
last boot179-4 1650-i forgot date...august ???
This seems to the correct thread to ask this question. I have tried few nighties randomly dome are very stable and some are not. But none of them have given exceptional battery life. Has anyone come across a stable nightly with great battery life.
Sent from my MB525 using Tapatalk
have you Undervolted? That can give you the battery life you are looking for.
cm7-110716-0105-BOOT179-Jordan.zip
Hi,
I can recommend this version:
cm7-110716-0105-BOOT179-Jordan.zip
This version runs perfekt with very long battery life and works perfekt for me (cam, gps, wlan, battery...). But it is only version 2.3.4. I use this rom since a few weeks and I have no problems.
sg3707 said:
..
Has anyone come across a stable nightly with great battery life.
..
Click to expand...
Click to collapse
Ok, even am hunting for that, and i found 110814 wrking very good for me.
Its 2days,5hr, still 55% left
In my case, my sim was 6yrs old, so replaced it with new1 and that has given me better battery.
my configuration: check this thread
http://forum.xda-developers.com/showthread.php?t=1105506&page=9
And thanks to cm7defy devs for making such a wounderful rom.
...110822 boot179-4 nightly, very stable, works like a charm!
From main CM7 thread:
sentree said:
Besides that, I've tested the 110822-1650 nightly for a week now and I get 4d6h37m (4% left) on battery, love it!
3G and sync always on, a few calls, some surf, mail und sms, say normal use
Click to expand...
Click to collapse
I really doesn't understand this "myth" of the "best nightly"...
As far as I can tell the development is pretty much straight forward, and the best version is always the last - with bugfixies and new features who will get their bugfixies in a later version.
the best version is not necessarily the last one, we all have seen pretty screwed up nightlies. but now im using 110822 boot179, and i havent noticed any bugs yet, and it runs smooth, no lags, very good battery life.
sent from my cm7 defy...
Software dev is not that straight forward. With an OS it is actually hugely complex and anything changed might have unexpected consequences. The idea of posting here is to ID those ones that get a consistent good report.
I am currently on 110826-2119- NIGHTLY-Jordan.
Can I flash 0822 boot179-4 nightly directly on top of this and clear Dalvik and cache or is there any other procedure.....
sg3707 said:
I am currently on 110826-2119- NIGHTLY-Jordan.
Can I flash 0822 boot179-4 nightly directly on top of this and clear Dalvik and cache or is there any other procedure.....
Click to expand...
Click to collapse
sure.. boot builds are made for that.. like Rc
rainbowsixpro1 said:
CyanogenMod-7-110819-1459-NIGHLY-Jordan
I prefer this one.
Battery consumption is very high, 12 hours maximum.
-rsp1
Click to expand...
Click to collapse
jep, can confirm the high battery consumption on this nightly...
but would say that it's not the best rom at all
Well... I wait everyday for the latest nightly... And I can say I'm happy everyday. Haven't seen a sensive decrease in battery life ou system stability in any of the nightlys, only improvements
I update my defy with latest nightly version every ten days; I can't find any obvious issue yet.
lycheejet said:
I update my defy with latest nightly version every ten days; I can't find any obvious issue yet.
Click to expand...
Click to collapse
not me when 179-4 is uploaded wifi is better, the last have a fix for SD Card .
But it's my Nightly i prefer because i can use Total Recall
i have to correct myself: 110822 boot179 nightly has battery drain issues, i only could last about 14 hours w/ normal use in the last 2 days... but i hear the 110830 is very good. can somebody pls confirm that?
sent from my cm7 defy...
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch
I'm on the latest CM10 Nightly and the included Torch works fine.
LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10
tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze
Hi.
It's been 2 months that I have used my one plus one and I still have the original/vanilla build 22R.
Now I'm curious is it worth to update to the newer versions? I have heard so much bad feedback regarding battery life and other bugs.
What are the pro's and con's?
Right now I'm enjoying 3 days battery life, 5h screen time. But microphone gain for videos is bad also for sound recording. WiFi and the antenna for RF seems to be buggy and not working properly.
Thanks in advance,
Zekenka
Sent from my One using XDA Free mobile app
Just update. Updates are good. Don't listen too much the blaming people cause a lot of them just confuse themselves by doing tests right after the update.
I agree with the previous poster, update your phone, don't worry about the negative Nellies, it's usually user error anyway.
Transmitted via Bacon
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
ek69 said:
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
Click to expand...
Click to collapse
What about the battery life etc? I have heard like terrible stories(ofcourse myabe their nellies) but i kinda like the long one right now and I doubt there will be possibility to rollback unless i unlock my bootloader and install TWRP/CWM .
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
ek69 said:
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
Click to expand...
Click to collapse
Would unlocking bootloader cause any stuff related to wakelocks? Right now It is perfect 0 drain over night and no terrible wakelocks,
I remember with daily SGS2 build there were terrible wakelocks with up to 20% drain over night
Unlocking bootloader won't do that. Updating or flashing ROM might, no guarantees. My experience is good with latest update, some others have problems most I would say don't. It's your phone and your choice what to do with it lol.
Just update, dont ask to much. Phone is working great on 44S. You will see when you update, battery life is great for me.
When I tried 5.0 and 5.0.1 ROMs I had severe battery drain problems, so I went back to 4.4.4
I don't have time to waste flashing a ROM which hasn't solved the battery life issue which many (not all, I know, but MANY) people have encountered in Lollipop.
My question is this: NOT referring to your own personal setup, but regarding the N5 community as a whole - is there still a battery life problem prevalent on 5.0.2 ROMs for lots of people?
A simple yes or no will suffice. Thank you.
No. There never has been even on the L preview releases
Also there is no 5.0.2 for our device
Yes, there are definitely battery drain issues. I am not too sure it's related to the ROMs themselves but rather the radio. I have tried all Lollipop radios with a very basic set up on both stock ROMs and Cyanogenmod. At some point, I will get idle drain in the region of 2-4% an hour - way higher than I would expect.
There are no wake-locks - the device seems to sleep well - it's just idle drain is horrible. Go back to the radio from 4.4.2 and the drain ceases.
If one more person points to the Battery Life Q&A thread I might swear.
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
naien said:
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I've not had any compatibility issues with any radio/ROM combo thus far. You can grab the radio image from the within stock factory images here https://developers.google.com/android/nexus/images or go straight to the radio (in both img and flashable zip format) here http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems
For ref, KOT49E is the one I use. Technically this is 4.4.1 but 4.4.2 shared the same one.
The KRT16M the 4.4.2? If so i have a flashable zip if you want it
naien said:
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Radios are device-specific and rom-agnostic. You can flash any N5 radio with any rom.
Is it confirmed that the battery life using the old radio is better?
t3al said:
Is it confirmed that the battery life using the old radio is better?
Click to expand...
Click to collapse
There is no confirmation.
There are too many variables, the biggest being location....
What's better for one can be completely different for another.
Test several for your usage and location. You may also find little or no difference as well
If you are still getting 'drain', narrow down the issue by logic: work out what is actually using the battery, they don't drain by themselves. Apply this thinking to any device
eddiehk6 said:
... narrow down the issue by logic: work out what is actually using the battery, they don't drain by themselves. Apply this thinking to any device
Click to expand...
Click to collapse
I believe my issue is poor signal at home on my desk causing battery drain overnight. By flashing an older version of radio will this improve my battery life in anyway?
There is no such "drain" in Lollipop. People just have wakelock issues with their own setup, the same as on KK or any version of Android. They simply put the blame on Lollipop and say there is nothing wrong with their wakelock issues.
[Battery Life Help] Troubleshoot battery issues here!
Lethargy said:
There is no such "drain" in Lollipop. People just have wakelock issues with their own setup, the same as on KK or any version of Android. They simply put the blame on Lollipop and say there is nothing wrong with their wakelock issues.
[Battery Life Help] Troubleshoot battery issues here!
Click to expand...
Click to collapse
It's a little narrow-minded to rule out all issues based on personal experience. My device, with current set up, sleeps like a baby. I don't use location services nor social apps like Facebook. My signal strength is fine.
On a Lollipop radio, idle drain after 1 or 2 days uptime will increase to around 4% an hour. On the radio from 4.4.2, my uptime can be a week or two and idle remains at about 1% an hour, everything else being equal.
Radios don't cause wakelocks, enable location services or install Facebook.
I do agree with one thing though - it's not Lollipop itself causing the battery issues. Some problem is deeper than that.
surrealjam said:
It's a little narrow-minded to rule out all issues based on personal experience. My device, with current set up, sleeps like a baby. I don't use location services nor social apps like Facebook. My signal strength is fine.
On a Lollipop radio, idle drain after 1 or 2 days uptime will increase to around 4% an hour. On the radio from 4.4.2, my uptime can be a week or two and idle remains at about 1% an hour, everything else being equal.
Radios don't cause wakelocks, enable location services or install Facebook.
I do agree with one thing though - it's not Lollipop itself causing the battery issues. Some problem is deeper than that.
Click to expand...
Click to collapse
Radio's are an entire different story.
Different ones work better for different people.
Nor are they Android version related - there is no "Lollipop radio", its just a radio version that will work with any version of Android, and was the latest one so it was packaged with the latest factory images. Again, nothing to do with Lollipop
Lethargy said:
Radio's are an entire different story.
Different ones work better for different people.
Nor are they Android version related - there is no "Lollipop radio", its just a radio version that will work with any version of Android, and was the latest one so it was packaged with the latest factory images. Again, nothing to do with Lollipop
Click to expand...
Click to collapse
Cool. That's why I said "it's not Lollipop itself causing the battery issues".
Lethargy I disagree mainly because there are a few bugs in Lollipop that need work to make it a bit more stable. They have pushed the fixes into AOSP for the ones that have been found but it seems like custom ROMs on Lollipop or a majorly tweaked stock ROM do better.
A lot of it too I think is how poor Google Play Services is with battery. I feel like I have to jump through hoops just to get Google Play Services to behave.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Lethargy I disagree mainly because there are a few bugs in Lollipop that need work to make it a bit more stable. They have pushed the fixes into AOSP for the ones that have been found but it seems like custom ROMs on Lollipop or a majorly tweaked stock ROM do better.
A lot of it too I think is how poor Google Play Services is with battery. I feel like I have to jump through hoops just to get Google Play Services to behave.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
What bugs are there in Lollipop that affect battery life? Enlighten me.
And what does Google Play Services specifically have to do with Lollipop?
Lethargy said:
What bugs are there in Lollipop that affect battery life? Enlighten me.
And what does Google Play Services specifically have to do with Lollipop?
Click to expand...
Click to collapse
The RAM leak bug: https://code.google.com/p/android/issues/detail?id=79729
It causes app restarts and extra CPU churn.
MrObvious said:
The RAM leak bug: https://code.google.com/p/android/issues/detail?id=79729
It causes app restarts and extra CPU churn.
Click to expand...
Click to collapse
This is the only reason I've decided to go back to 4.4.4 as I'm writing this. I seriously have to reboot phone 5 plus times a day. Ashley every time I get into car and maps loads this is like a instant trigger. Maybe I have to many background tasks idk, but it didn't happen on kk...
Since upgrading to lollipop (have tried many roms, from 5.0.2 to 5.1.1, now getting it on Cynaogen OS 12 ) i get really high battery drain because some apps like facebook, sometimes xda keep mobile radio data active until i force close them. Has anyone else noticed this issue or got a clue what might be causing this? Because i was getting this bug on different versions of lollipop with different apps, i think this might rather be a lollipop issue than the fault of apps. I have also tried flashing different modems, nothing helped. I will post screenshots below
Sent from my A0001 using XDA Free mobile app
I have the same problem xd with oxygen and cm12s
https://code.google.com/p/android/issues/detail?id=165558
Sent from my A0001 using XDA Free mobile app
I have recently joined the mobile radio battery drain club running latest version of COS12 with the latest incremental update being about 2 weeks ago. since that "update" that was only supposed to fix touch screen issues I have had this radio bug. A full battery life cycle will only afford me 4-5 hours of use..... heavy use is MUCH worse! Like 3-4 hrs....
Anyone hear of a patch/fix/work around? I am also bone stock without root, never rooted, etc..... only stock updates on COS....
sick_DMP said:
I have recently joined the mobile radio battery drain club running latest version of COS12 with the latest incremental update being about 2 weeks ago. since that "update" that was only supposed to fix touch screen issues I have had this radio bug. A full battery life cycle will only afford me 4-5 hours of use..... heavy use is MUCH worse! Like 3-4 hrs....
Anyone hear of a patch/fix/work around? I am also bone stock without root, never rooted, etc..... only stock updates on COS....
Click to expand...
Click to collapse
Unfortunately it's a core google OS bug and only google can fix it. It'll happen if you use Mobile Data and there's no solution at all. Either switch to KK or pray that they'll fix it on Android M. Or get used to it like me
Yeah, I've just been using battery save mode and this has been very helpful. Although it does effect performance and gets rid of all the fun animations that make lollipop so enjoyable. It's definitely worth having at least 7-8 hours of use. But, I admit even on battery saver mode I'm noticing extreme battery issues start to effect this profile as well.
Crossing my fingers that Google does roll out a fix of some sort bcuz I'm seeing new apps and Google services show up on my battery stats!
So has anybody been looking at this outside of Google? Some of us are developers, after all, and if the bug is in the Android code and not Google Play Services, we should be able to find it. I haven't seen too many attempts, so far...
acwest said:
So has anybody been looking at this outside of Google? Some of us are developers, after all, and if the bug is in the Android code and not Google Play Services, we should be able to find it. I haven't seen too many attempts, so far...
Click to expand...
Click to collapse
I have read from a number of people that only Google can fix this problem since it is a low level android bug. And it is also supposedly in the beta versions of android M as well. The only current solution I have found to this problem is to stay on Kitkat. And not buy a phone that comes stock with lollipop (or M) until this problem is fixed, assuming you want the best battery life, since it is likely that there will not be any KK roms available for any new phone.
You can help by starring the issue at https://code.google.com/p/android/issues/detail?id=165558
As fars as I can tell, the bug should be in code we have access to, so it doesn't have to be Google that fixes it. I've fixed bugs in the Linux kernel before, and it doesn't get any more low level than that...
They have to accept the fix and include it for it to be much use, but that is an entirely separate issue...