Related
Hey guys,
Before you completely write off this thread, just know this is a serious inquiry and is coning from someone with experience in many different devices (rooting, flashing etc.)
My question is, are there any huge benefits to deviate from stock? The reason behind this question is that on the devices I have had in the past, most roms (and even themes) tend to end up trying their hardest to emulate the aosp experience. Some roms (cm7) even do this really well.
Since this device is the aosp experience, essentially being the flagship android device, what benefits would result in flashing something over stock? I know there are potentials for a little more snappiness, battery life, but are they big differences?
Basically I am new to this particular device, am happy with it, and just want to know if the custom software has really taken the phone to 11?
Sent from my Nexus S using XDA Premium App
Any input or recommendations are appreciated.
Sent from my Nexus S using XDA Premium App
Because this phone is AOSP, there is less of a reason to root and ROM. However, there are just a few things stock doesn't provide that I absolutely need (while you may not).
Such things are the notification widgets and BLN.
Other little tweaks I like is the built-in screenshot ability, long press back to kill apps, some status bar modding and a little underclocking.
As you can see, there is little benefit if these things aren't important to you as there isn't a MUST HAVE feature among us that requires root. I'd say BLN is a must have but I notice many people don't need or like it so again, it's all based on preference.
Most ROMs are basically updated versions of the stock experience.
Since I'm using the NxS I tried a lot of different ROMs, but only 3 are on my list that I'd come back to any day. Mostly because they have visible features/improvements and aren't "just" (don't take this negative) modified under the hood.
Those 3 are: Stock ROM, MIUI and CM. Stock ROM for being the source, MIUI for being the most themed ROM with a unique (yaya, I know iPhone-ish) look and CM for all it's changes and new additions (camera button, lockscreen etc). Not putting down the other AOSP ROMs out there, but they don't give me personally enough to choose them over Stock.
So as far as underclokcing roms... large battery improvements?
What is BLN?
Sent from my Nexus S using XDA Premium App
acPIZZA said:
So as far as underclokcing roms... large battery improvements?
What is BLN?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
BLN = Backlight Notifications
This is when the soft keys (Back, Menu, Search, Home) on the front of the phone light up when there is a notification. An invaluable feature if you ask me considering Samsung always skimps out on the notification LED.
As for underclocking, I find that I can underclock less on my Nexus S than with my Captivate. I could underclock my Captivate to almost -150s before a reboot while I can only do -50s with the Nexus. As such, I don't think it's that great of an improvement but every little bit counts right? I can see many people thinking -50 isn't worth the hassle but it could just be my phone that is adverse to UC.
acPIZZA said:
So as far as underclokcing roms... large battery improvements?
What is BLN?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
BLN = BackLight Notification, basically the 4 software buttons below the display will light up/blink on a notification.
Underclocking alone doesn't slice the bread, you need to undervolt to save meaningful amounts of battery life. Using the kernel in my signature compared to stock I'm saving noticable amounts of battery life (no, it won't turn your Android phone into a dumbphone, in terms of battery life). Head over to development section for more kernels.
/EDIT: ok Enhanced is taking care of that now
Awesome. Sounds good and the BLN are a great idea.
Sent from my Nexus S using XDA Premium App
Dear developers,
I'm just wondering, is it just me or is everyone else facing the same problem. I felt that my Nexus 5 battery is draining so fast. In 1 day I can charge my phone twice. Sure, I played Asphalt for a bit. But I think the battery drain is still too quick.
I'm using Cataclysm ROM and Franco Kernel.
Should I use kernel controller such as FKU full version?
Any other tips maybe?
Have you tried setting the Wifi such that it is off when your phone is asleep. How about the setting to always allow scanning for Wifi networks? Did you turn off Google location history? One thing I've found is that the Wifi radio eats through the battery like crazy, even at idle, and changing these settings seems to make the biggest difference of anything.
flamechamp said:
Dear developers,
I'm just wondering, is it just me or is everyone else facing the same problem. I felt that my Nexus 5 battery is draining so fast. In 1 day I can charge my phone twice. Sure, I played Asphalt for a bit. But I think the battery drain is still too quick.
I'm using Cataclysm ROM and Franco Kernel.
Should I use kernel controller such as FKU full version?
Any other tips maybe?
Click to expand...
Click to collapse
I'm assuming you're on the latest 4.4.2? It's a common issue with the nexus devices so you're not alone there. But what you can do to minimize it is that to set your cpu governor to something modest like 'conservative' and put your i/o scheduler to "row" those settings have worked for me on my s4 to reduce battery drainage. If you have the ktoonservativeq option for Cpu governor then that's a good choice as well.
joemon871 said:
I'm assuming you're on the latest 4.4.2? It's a common issue with the nexus devices so you're not alone there. But what you can do to minimize it is that to set your cpu governor to something modest like 'conservative' and put your i/o scheduler to "row" those settings have worked for me on my s4 to reduce battery drainage. If you have the ktoonservativeq option for Cpu governor then that's a good choice as well.
Click to expand...
Click to collapse
Which apps should I use to change those settings? FKU full version?
Post here your problem and they might help you fix it
There's plenty of free apps out there that'll do the job. But for example, in cyanogenmod roma if you have developer settings enabled, there will be an option all the way down at the bottom that says Performance. You can change some settings over there as well
Sent from my SGH-M919 using Tapatalk
joemon871 said:
There's plenty of free apps out there that'll do the job. But for example, in cyanogenmod roma if you have developer settings enabled, there will be an option all the way down at the bottom that says Performance. You can change some settings over there as well
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
some example would definitely be a great help
which one you suggest too.
I'm not using CM yet
Playing a game like asphalt will drain your battery in no time, that's to be expected, if you play san Andreas is still worse
Try using greenify to greenify your apps through it's widget, I'm on beanstalk with Franco kernel and i get around 24 hours playing games like clash of clans and battle of zombies, but if play San Andreas i get only like 45 minutes, probably an hour
Sent from my Nexus 5 using Tapatalk
flamechamp said:
some example would definitely be a great help
which one you suggest too.
I'm not using CM yet
Click to expand...
Click to collapse
I can finally post links! Lol but here it is, hope that helped
http://rootzwiki.com/topic/15733-wh...ed-and-governor-on-kernel-other-than-francos/
Sent from my SGH-M919 using Tapatalk
Hey,
Having a problem with my N5 draining my battery @ 4% / hr even when idle. According to the battery screen in settings the culprit is Android OS @ 32%.
I'm running CM M2 (stock kernel) on TMobile. I've got WiFi + Bluetooth on. NFC is off.
For comparison the phone has been on battery for 6hrs with only a few minutes screen on time and is at 61%.
Thoughts?
Sent from my Nexus 5 using xda app-developers app
Any apps draining that shouldn't be? Turn auto brightness off and keep around 30%. Screen always takes the most.... clearly. Could be fault of CM since they are nightlies and those are always a work in progress. Post in CM thread, always read previous post in that thread for battery issues.
I'm running stock ROM, and getting the same amount of battery drain as you. I'm pretty sure this is coming from wlan_rx_wake wakelocks if you have wifi on while this is draining. Though having data on doesn't help me, I just get bam_dmux_wakelocks. Try better battery stats to see what wakelocks are keeping your phone awake. I have tried everything to get wlan_rx_wake to stop, yet it hasn't. Would love if someone knew how to fix this battery drain.
Just installed better battery stats. Will report back in a few days.
I do suspect WiFi as well. I was out on LTE all day yesterday and the drain was < 1% / hr and after 12+ hrs I was at 80%.
I have geenified a lot of apps. No luck so far
Sent from my Nexus 5 using xda app-developers app
Turn off bluetooth. Android OS being the main culprit means an app is keeping it awake. Also, I've bad experience (at least in my s3 days) with CM with regards to battery. Try switching ROMS and try franco kernel as well (great battery life without gimping performance)
Your coverage can have a huge impact on battery drain. At work I have poor coverage and my battery will be low by the end of the day at home its good I will have less battery drain with more usage.
Sent from my Nexus 5 using Tapatalk
Cpudan80 said:
Just installed better battery stats. Will report back in a few days.
I do suspect WiFi as well. I was out on LTE all day yesterday and the drain was < 1% / hr and after 12+ hrs I was at 80%.
I have geenified a lot of apps. No luck so far
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I think the easiest thing to see if it's ROM related or app related is to just backup your current ROM and re-flash the ROM without anything (besides your basic absolute must need app but try and avoid if possible) and try it for a day. If you still have the battery drain, then it's the ROM, in which case, I suggest using a different ROM. I recommend Omni or Cataclysm. If not, then it might be an app burning through your battery then.
I am not able to let my phone go on for 24 hours without charging. I definitely need to charge it daily. I tried turning off the wifi and data and all background apps and services, just the android stuff is running, still can't go over 24 hours. At most is around 20 - 22 hours on standby.
I'm having same issues. On stock rom.
Sent from my Nexus 5 using xda app-developers app
And I thought that getting 5.5% / h is normal (with LTE on) with syncing accounts and stuff.
Mine used to be so good. What's happened
Does the above screen shot mean anything?
Sent from my Nexus 5 using xda app-developers app
kraven001 said:
And I thought that getting 5.5% / h is normal (with LTE on) with syncing accounts and stuff.
Click to expand...
Click to collapse
Anything over 1% per hour while idling, whether wifi or lte, is unacceptable.
Post your BBS logs people. If you're going to post screenshots, at least post all of the screens. Less work for you to hand over the log.
Aerowinder said:
Anything over 1% per hour while idling, whether wifi or lte, is unacceptable.
Click to expand...
Click to collapse
+1 just disable feauteres you don't use. I have auto-sync enabled but I check only the very necessary syncing (gmail for me). Disable location report from google, Google now, OK Google hotword detection... And even greenify those battery killing apps (check partial wakelocks and alarms)
I have the same behavior with about 4% drain per hour screen
off idle when I use a CM nightly from about the last 10 days with bricked kernel. So I'm still with my january 07th. CM Nightly which has no drain at all.
The culprit for me is an EntriesRefresh wakelock coming from google.quicksearchbox. No idea what that is -- but it appears to be a common source of problems on KK ROMs across all devices.
i do like Google Now so I don't want to greenify that. Hopefully google will fix the app soon enough.
Anyone have any other thoughts/suggestions?
-- Dan
If I disable everything on my phone , maybe I can get the 1% / hour, but frankly I don't see the point.
I like google now, I like my emails syncing and getting notified about things - that's why I use a darn smartphone, otherwise I would get a "dumb" phone that idles.
How do you export all on bbs?
Sent from my Nexus 5 using xda app-developers app
Does your battery screen for Android OS look like this -
Or this -
Sent from my Nexus 5 using Tapatalk
Cpudan80 said:
The culprit for me is an EntriesRefresh wakelock coming from google.quicksearchbox. No idea what that is -- but it appears to be a common source of problems on KK ROMs across all devices.
i do like Google Now so I don't want to greenify that. Hopefully google will fix the app soon enough.
Anyone have any other thoughts/suggestions?
-- Dan
Click to expand...
Click to collapse
Google Now isn't inherently bad on battery. Are you using GEL?
I do Greenify it, but only because it has no purpose for me.
Aerowinder said:
Google Now isn't inherently bad on battery. Are you using GEL?
I do Greenify it, but only because it has no purpose for me.
Click to expand...
Click to collapse
Not using Google Experience Launcher just the regular AOSP launcher, but Google Now is enabled and the search box is on my launcher (but its not voice activated.)
What is the quick search box exactly? When I went to greenify it, greenify said that it was a system app and that greenifying it could cause problems.
-- Dan
I am debating on whether to buy the pro version and flash Franco's Kernel for my Nexus 5 and 7 (2013). I just want to know what I bits of extra I can really do with it.. And if its worth it. I'm more worried about stability than anything I guess. I don't want to run into little issues whether it be audio, video, whatever it may be. Also I have never flashed a kernel or another ROM, I've always stuck with stock. I am running 4.4.2 right now utilizing Gravity Box and Wanam Kit, and a few other modules. Any input would be greatly appreciated. If this thread has been done before, my apologies. I am a brand new forum user, never really get on the computer.
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
I am debating on whether to buy the pro version and flash Franco's Kernel for my Nexus 5 and 7 (2013). I just want to know what I bits of extra I can really do with it.. And if its worth it. I'm more worried about stability than anything I guess. I don't want to run into little issues whether it be audio, video, whatever it may be. Also I have never flashed a kernel or another ROM, I've always stuck with stock. I am running 4.4.2 right now utilizing Gravity Box and Wanam Kit, and a few other modules. Any input would be greatly appreciated. If this thread has been done before, my apologies. I am a brand new forum user, never really get on the computer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well to be honest the stock kernel allready is very good, the only downsides of it are batterylife/screenontime and colors are not very vibrant. These 2 aspects are substantialy better with Franco kernel. Screenontime and batterylife is improved by at least 50% or more for some (check out the Franco thread). Also you can raise the speaker/mic/in-call volume as you wish and load a color profile for better and more vibrant colors.
if you want stability stick with stock
gee2012 said:
Well to be honest the stock kernel allready is very good, the only downsides of it are batterylife/screenontime and colors are not very vibrant. These 2 issues are substantialy better with Franco kernel. Screenontime and batterylife is improved by at least 50% or more for some (check out the Franco thread). Also you can raise the speaker/mic/in-call volume as you wish and load a color profile for better and more vibrant colors.
Click to expand...
Click to collapse
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If you are having trouble making a decision... just flash the kernel with fastboot and give it a test run. Can the free version of FKU auto flash? I'm not sure, you would have to investigate.
If you decide you like it (and the updates that go along with it), then maybe consider buying the app.
But yes, screen on time is better with FK due to the way the clock speeds scale. A lot better. Even with the stock settings, though I find even those to be a bit aggressive.
wardawgmalvicious said:
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Most users report a screenontime of about 5-7 hours while stock is about 3,5 hours. Don`t know about the Xposed module but color controll in the Franco kernel updater app is realy good and there are various preloaded settings available. Link thread http://forum.xda-developers.com/showthread.php?t=2508284. Backup your current kernel in the FKU before you flash a Franco kernel, so you can restore it if need be.
Aerowinder said:
If you are having trouble making a decision... just flash the kernel with fastboot and give it a test run. Can the free version of FKU auto flash? I'm not sure, you would have to investigate.
If you decide you like it (and the updates that go along with it), then maybe consider buying the app.
But yes, screen on time is better with FK due to the way the clock speeds scale. A lot better. Even with the stock settings, though I find even those to be a bit aggressive.
Click to expand...
Click to collapse
I believe you can, I'll look into when I get home.
So do you underclock or undervolt? I don't know the differences between the two, my apologies. If I do get Franco I think I will just leave it at the stock settings it comes with before I make any changes, still got learning to do. Thank you for sharing your knowledge!
Sent from my Nexus 5 using Tapatalk
gee2012 said:
Most users report a screenontime of about 5-7 hours while stock is about 3,5 hours. Don`t know about the Xposed module but color controll in the Franco kernel updater app is realy good and there are various preloaded settings available. Link thread http://forum.xda-developers.com/showthread.php?t=2508284. Backup your current kernel in the FKU before you flash a Franco kernel, so you can restore it if need be.
Click to expand...
Click to collapse
That's pretty awesome, definitely gonna try it out. I have a backup somewhere on my device, I think in Flashify, but I'll make another, can never hurt lol.
And thanks for the thread and all the other info!
Sent from my Nexus 5 using Tapatalk
Stick with stock for at least long enough to give yourself a baseline to judge other ROMs/kernels against.
Wakamatsu said:
Stick with stock for at least long enough to give yourself a baseline to judge other ROMs/kernels against.
Click to expand...
Click to collapse
I've had my Nexus 5 for roughly 2 months now I think, are you saying I should wait it out or do more research first? It is very scary for me lol. I'm always afraid to be making major internal changes without some form of consultation and research.
Sent from my Nexus 5 using Tapatalk
Also quick question, I don't need to back anything else up correct? Flashing a kernel does not mess with anything else does it?
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
I've had my Nexus 5 for roughly 2 months now I think, are you saying I should wait it out or do more research first? It is very scary for me lol. I'm always afraid to be making major internal changes without some form of consultation and research.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I wouldn`t mess with the kernel settings like UV/OC besides color and sound optimisations. The stock settings are allready good enough for most users, only xperienced users should do that imo.
---------- Post added at 06:21 AM ---------- Previous post was at 06:18 AM ----------
wardawgmalvicious said:
Also quick question, I don't need to back anything else up correct? Flashing a kernel does not mess with anything else does it?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, flashing kernels or recovery`s don`t wipe data.
gee2012 said:
I wouldn`t mess with the kernel settings like UV/OC besides color and sound optimisations. The stock settings are allready good enough for most users, only xperienced users should do that imo.
Click to expand...
Click to collapse
That's what I'll do then, what kind of sound optimizations are there? Just the mic volume and whatnot? Or are there some for playing music, I have poweramp and use that equalizer, so just wondering.
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
That's what I'll do then, what kind of sound optimizations are there? Just the mic volume and whatnot? Or are there some for playing music, I have poweramp and use that equalizer, so just wondering.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.
gee2012 said:
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.
Click to expand...
Click to collapse
Alright guess I'll just have to carefully play around with a bit. Thanks for your help!
Sent from my Nexus 5 using Tapatalk
gee2012 said:
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.
Click to expand...
Click to collapse
Oh last question, do you know of any stability issues with Franco Kernel? That is my number one concern, so just checking with you real quick before I go with it finally.
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
Oh last question, do you know of any stability issues with Franco Kernel? That is my number one concern, so just checking with you real quick before I go with it finally.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I haven`t had FC`s when i used the kernel, most issues of users we`re caused by undervolting too much.
gee2012 said:
I haven`t had FC`s when i used the kernel, most issues of users we`re caused by undervolting too much.
Click to expand...
Click to collapse
Alright sounds good! I'll let you know how it goes!
Sent from my Nexus 5 using Tapatalk
wardawgmalvicious said:
Alright sounds good! I'll let you know how it goes!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oke, good luck and enjoy
gee2012 said:
Oke, good luck and enjoy
Click to expand...
Click to collapse
OK maybe a stupid question, should I use auto flash or flash via recovery?
Sent from my Nexus 5 using Tapatalk
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...