Database Info

Upgrade to 8.1 RT is ready for Surface! Do it or not?

Hey,
The upgrade for my Surface is ready, and I am thinking what to do with that. Right now I have unlocked (jailbraked) system, I know that after installing upgrade I will have to stick for a while with locked one. How about you guys? Are you installing asap or waiting for unlock solutions?

From a fellow surface RT owner that has just moved back after installing the 8.1 update preview, I wouldn't recommend it for one reason - standby battery life.
I kept installing the updates assuming that the battery life would improve.
Suffice to say that my standby battery life has jumped from about 12 hours to about 12 days.
In fact my battery life on 8.1 was so poor (even with Bluetooth on) that my surface could actually last longer if I was working on it all day.
Unless Microsoft bothers to fix this enormous issue, I'm staying well away from the update.
On a connected note - if anyone downloads the update, please let me know if this issue gets fixed, I assume it isn't already.

feygor said:
From a fellow surface RT owner that has just moved back after installing the 8.1 update preview, I wouldn't recommend it for one reason - standby battery life.
I kept installing the updates assuming that the battery life would improve.
Suffice to say that my standby battery life has jumped from about 12 hours to about 12 days.
In fact my battery life on 8.1 was so poor (even with Bluetooth on) that my surface could actually last longer if I was working on it all day.
Unless Microsoft bothers to fix this enormous issue, I'm staying well away from the update.
On a connected note - if anyone downloads the update, please let me know if this issue gets fixed, I assume it isn't already.
Click to expand...
Click to collapse
Yeah, i read about battery issue. But I wonder if the final version differs from the preview in this issue? Can anyone confirm or deny? And what about the RTM version? Is the final 100% is the same as the RTM?

ell82 said:
Yeah, i read about battery issue. But I wonder if the final version differs from the preview in this issue? Can anyone confirm or deny? And what about the RTM version? Is the final 100% is the same as the RTM?
Click to expand...
Click to collapse
I doubt the official Windows RT 8.1 RTM release for the Surface RT is the same as the community-built RTM version for ir. Remember, it had to have some drivers injected? And this release suffers from Touch Cover issues after the Oct 15 firmware update, and you need to do a refresh to solve it. I think that you would still need to do a refresh every time you do a reinstall.
I am pretty confident that the real release wouldn't cause any such problems, that's why I am looking forward to someone doing the upgrade and uploading it's image for us, the early RTM users, to restore our devices to official-spec.
By the way, I have really noticed the poor standby time. My guess would be that some Windows 8.0 background features were purposely limited to compliment the missing support for the 5th battery-saving core, and that Windows 8.1 brought many of them back without fixing the issue with this 5th core. And I doubt that Microsoft is ever going to fix it even though it's obvious now that the 5th battery-saving core is really needed to achieve reasonable stand-by times. Or they might just limit this background stuff again (make tile updates much-less-often, for example).

OP, do you install apps to the sd card? If you do, then wait, unless the released ISO is really that different from the community release version, the functionality of installing to the sd card is broken.

DO IT. IE 11's performance is notably improved. The Surface RT couldn't break 1000ms on SunSpider when it first came out
Edit: It got 889.6ms, btw. Sorry if it's too small to read.

I have no plans to upgrade/update. For me having an unlocked desktop is worth far more than any changes I've seen so far in RT 8.1. I don't need Outlook thankfully. I do hope a way to changing the signing restrictions in 8.1 will be found and wish those working on it the best of luck!

I didn't do anything with the 'jailbreak' so I upgraded. IE is noticeably faster. Also keyboard auto correct/suggest is a million times better. Hard to tell if the rest of the system is any faster or if its just in my head now and too early to comment on battery life. I wish it had swype. No problems with my touch keyboard.

Thanks for replays. I think I will stick with 8.0 for a while until there will be possibility to unlock 8.1 for not signed apps.

al2fast said:
I didn't do anything with the 'jailbreak' so I upgraded. IE is noticeably faster. Also keyboard auto correct/suggest is a million times better. Hard to tell if the rest of the system is any faster or if its just in my head now and too early to comment on battery life. I wish it had swype. No problems with my touch keyboard.
Click to expand...
Click to collapse
Could you please create a USB recovery using the (Recovery section in settings) and share it?

jtg007 said:
DO IT. IE 11's performance is notably improved. The Surface RT couldn't break 1000ms on SunSpider when it first came out
Edit: It got 889.6ms, btw. Sorry if it's too small to read.
Click to expand...
Click to collapse
I still running RT (not 8.1) and got 9xxms both on Desktop and Metro IE.
Try to upgrade to 8.1 but it disappear from store today. I see it yesterday and can't get it back. Really annoy.

You should be able to use this link:
http://windows.microsoft.com/en-gb/windows/download-shop
Sent from my SAMSUNG-SGH-I317 using xda premium

Can anyone who has updated to 8.1 confirm or deny that the standby battery issue has been fixed, does the surface last overnight? This is a real issue that I want to know is fixed, as well as the god awful bugs that plagued the beta version of IE11
Edit: Not that it matters now, Microsoft have pulled the update due to an error with the boot configuration files. Looks like we might be waiting a bit longer for that upgrade (Unless one of you lucky upgrades feel like sharing your recovery drive files...)

Can confirm standby drain is still happening after a refresh and all updates even

johnchad14 said:
Can confirm standby drain is still happening after a refresh and all updates even
Click to expand...
Click to collapse
As I feared, guess I'll be sticking with good old 8.0 for the foreseeable future, it's very disappointing to see MSFT pushing an update that cripples their own hardware and claim blind ignorance to it. There's no feature in 8.1 that's worth giving up a week standby battery. TBH there's no device nowadays that can excuse a device that only lasts about 12 hours on standby.

feygor said:
As I feared, guess I'll be sticking with good old 8.0 for the foreseeable future, it's very disappointing to see MSFT pushing an update that cripples their own hardware and claim blind ignorance to it. There's no feature in 8.1 that's worth giving up a week standby battery. TBH there's no device nowadays that can excuse a device that only lasts about 12 hours on standby.
Click to expand...
Click to collapse
If it's of any use for you guys, I'm on 8.1 now and on standby at night (wifi connected, bluetooth disconnected, logged in) it drops from 98% to 92%. If I turn Plane mode on and log off, it stays at 99% or maybe drops 1%.
The first night when I got it 2 weeks ago with Windows 8.0 it stayd at the same % over night (logeed in, wifi on), but the next nights it would drop from 70% to 0%
I think it was solved disabling lockscreen notifications to avoid background usage. I planned to do a refresh with 8.1, but since it's working fine for me, I don't need to.

I think I did try that before but not since last updates. I'll give that a go and see how it drains over the next few days

antonio1475 said:
If it's of any use for you guys, I'm on 8.1 now and on standby at night (wifi connected, bluetooth disconnected, logged in) it drops from 98% to 92%. If I turn Plane mode on and log off, it stays at 99% or maybe drops 1%.
The first night when I got it 2 weeks ago with Windows 8.0 it stayd at the same % over night (logeed in, wifi on), but the next nights it would drop from 70% to 0%
I think it was solved disabling lockscreen notifications to avoid background usage. I planned to do a refresh with 8.1, but since it's working fine for me, I don't need to.
Click to expand...
Click to collapse
Almost the same here, In my case it has been in standby for about 18 hrs, everything on, but disconnected... and it did from 100% to 95%.
I'm running rt 8.1

[Q] Nexus 5 Sudden Battery Throttle

So, I don't know if my problem here in particular is unique or new, but this issue started about a week ago.
My Nexus 5, is rooted, and running Cyanogenmod 11, (was) running with ART Runtime, and I was getting pretty decent battery life with the phone. Usually nothing less than 2-3 hours of screen on time, with pretty typical settings (location off, sync off, etc).
Out of nowhere, about last week my battery life began to be much worse. It'll drain from full to 20% in a matter of 5 or 6 hours, and none of my usage really changed at all. I'm well aware of the mm-qcamera-daemon, but according to my battery usage page, it still isn't really in use or bothering my battery life.
What could cause this sudden change? I'm here at work plugging my phone in half way through the day, when normally I can go about 2 days without charging.
I've tried factory resetting, I've turned off ART, I've tried changing the governor on the CPU, and many other things. Is my battery simply going bad?
If anything has a solution for me, it'd be a blessing.
Thanks.

speedanderson said:
So, I don't know if my problem here in particular is unique or new, but this issue started about a week ago.
My Nexus 5, is rooted, and running Cyanogenmod 11, (was) running with ART Runtime, and I was getting pretty decent battery life with the phone. Usually nothing less than 2-3 hours of screen on time, with pretty typical settings (location off, sync off, etc).
Out of nowhere, about last week my battery life began to be much worse. It'll drain from full to 20% in a matter of 5 or 6 hours, and none of my usage really changed at all. I'm well aware of the mm-qcamera-daemon, but according to my battery usage page, it still isn't really in use or bothering my battery life.
What could cause this sudden change? I'm here at work plugging my phone in half way through the day, when normally I can go about 2 days without charging.
I've tried factory resetting, I've turned off ART, I've tried changing the governor on the CPU, and many other things. Is my battery simply going bad?
If anything has a solution for me, it'd be a blessing.
Thanks.
Click to expand...
Click to collapse
If i was on your place I'd return it back to stock and see how my phone would react. Afterwards if issue has to do anything with hardware I'd unroot + relock bootloader and give it to my provider for a warranty and explain them my problems.

MaCroX95 said:
If i was on your place I'd return it back to stock and see how my phone would react. Afterwards if issue has to do anything with hardware I'd unroot + relock bootloader and give it to my provider for a warranty and explain them my problems.
Click to expand...
Click to collapse
Hmm..
That's not a bad idea. I think I'll flash stock back on to it when I get home tonight. You know, I have insurance on the phone, but I was expecting to have to exchange it for breaking the phone's screen, not for my battery going bad. I hope Stock ROM fixes the problem, or hell.. maybe whenever 4.4.3 ROMs start coming out, that might do the trick to. I've been careful to take care of this phone, since I broke my Nexus 4 two months after I got it.
Thanks.

speedanderson said:
Hmm..
That's not a bad idea. I think I'll flash stock back on to it when I get home tonight. You know, I have insurance on the phone, but I was expecting to have to exchange it for breaking the phone's screen, not for my battery going bad. I hope Stock ROM fixes the problem, or hell.. maybe whenever 4.4.3 ROMs start coming out, that might do the trick to. I've been careful to take care of this phone, since I broke my Nexus 4 two months after I got it.
Thanks.
Click to expand...
Click to collapse
You're welcome. I hope that you solve your problem as soon as possible. If you take a look how your phone does with stock on your diagnose of a problem would be much easier and from than on if the problem was in software you can try some other roms and kernels. I personally am not really a fan of cyanogenmod 11 at least not for nexus 5 since I've had few bugs using for a few days.

MaCroX95 said:
You're welcome. I hope that you solve your problem as soon as possible. If you take a look how your phone does with stock on your diagnose of a problem would be much easier and from than on if the problem was in software you can try some other roms and kernels. I personally am not really a fan of cyanogenmod 11 at least not for nexus 5 since I've had few bugs using for a few days.
Click to expand...
Click to collapse
Well, I really liked Paranoid Android for my Nexus 4, and I've had no issues until recently with CM11. :\
I guess stock is going to be my best bet though. I just really hope I can deal with the battery drain issue from mm-qcamera-daemon or whatever.

speedanderson said:
Well, I really liked Paranoid Android for my Nexus 4, and I've had no issues until recently with CM11. :\
I guess stock is going to be my best bet though. I just really hope I can deal with the battery drain issue from mm-qcamera-daemon or whatever.
Click to expand...
Click to collapse
I've been using SlimKat in combination with Faux's custom kernel for a few days now and I must say that peformance is as smooth as it was never before, speed is absolutely phenomenal and my battery life is more than pleasing (around 24H + 3-4 Hrs of screen on time).

MaCroX95 said:
I've been using SlimKat in combination with Faux's custom kernel for a few days now and I must say that peformance is as smooth as it was never before, speed is absolutely phenomenal and my battery life is more than pleasing (around 24H + 3-4 Hrs of screen on time).
Click to expand...
Click to collapse
Well, that sounds like exactly I want. I'm not opposed to trying another custom ROM either. Can you PM me a link to the thread with whatever particular build you're using?
If it's efficient and up to 4 hours of on screen time, sounds like exactly what I need.
I'm more than happy to ditch my ROM if I can get better performance, haha.

speedanderson said:
Well, that sounds like exactly I want. I'm not opposed to trying another custom ROM either. Can you PM me a link to the thread with whatever particular build you're using?
If it's efficient and up to 4 hours of on screen time, sounds like exactly what I need.
I'm more than happy to ditch my ROM if I can get better performance, haha.
Click to expand...
Click to collapse
ROM: http://www.slimroms.net/index.php/d...4-slim-hammerhead-4-4-2-build-4-official-3700
KERNEL: http://faux.romhost.me/hammerhead/kk44/
I'm using non-ultimate version of the kernel which means that it doesn't support overclocking and I'm also using a bit older build which is very stable and works flawlessly for me.

Ah, great. I'm actually going to download it now, while I'm here at work. Also, does this particular ROM work at all with ART Runtime, because if possible, I'd like to continue using it.

speedanderson said:
Ah, great. I'm actually going to download it now, while I'm here at work. Also, does this particular ROM work at all with ART Runtime, because if possible, I'd like to continue using it.
Click to expand...
Click to collapse
It does support ART. I didn't try it on this ROM though so I cannot tell exactly whether it's working or not. You'll have to test it by yourself but I am pretty sure that if your phone doesn't have any hardware issues that you won't be disappointed with the performance of ROM + Kernel with or without ART! Hit thanks if I helped you anyhow :laugh:
PS: Though since the ART is still in beta phase of development there is a possibility that it has caused you so much trouble with battery =)

speedanderson said:
So, I don't know if my problem here in particular is unique or new, but this issue started about a week ago.
My Nexus 5, is rooted, and running Cyanogenmod 11, (was) running with ART Runtime, and I was getting pretty decent battery life with the phone. Usually nothing less than 2-3 hours of screen on time, with pretty typical settings (location off, sync off, etc).
Out of nowhere, about last week my battery life began to be much worse. It'll drain from full to 20% in a matter of 5 or 6 hours, and none of my usage really changed at all. I'm well aware of the mm-qcamera-daemon, but according to my battery usage page, it still isn't really in use or bothering my battery life.
What could cause this sudden change? I'm here at work plugging my phone in half way through the day, when normally I can go about 2 days without charging.
I've tried factory resetting, I've turned off ART, I've tried changing the governor on the CPU, and many other things. Is my battery simply going bad?
If anything has a solution for me, it'd be a blessing.
Thanks.
Click to expand...
Click to collapse
Batteries Can't throttle. However the do degrade with use. You can replace the battery with ease.

New phone battery life

Hi!
I am new to the nexus 5 community and I just got my nexus 5 about 2 days ago
After fully charging it I started using it , I have heard that nexus 5 has battery issues and that's why I only want you people to help me tell how the battery life of my phone is for a brand new device by seeing the screenshots of my usage.
Here are the screenshots:

Looks normal to me. What's ingress? A game?

K****ij Agrawal said:
Hi!
I am new to the nexus 5 community and I just got my nexus 5 about 2 days ago
After fully charging it I started using it , I have heard that nexus 5 has battery issues and that's why I only want you people to help me tell how the battery life of my phone is for a brand new device by seeing the screenshots of my usage.
Here are the screenshots:
Click to expand...
Click to collapse
Not bad. I would disable Wi-Fi always scanning available (even if Wi-Fi is off), location to start. That's not bad though and is about what I get, but you might be able to get better SOT.

the nexus 5 does not have battery issues, at all. it stupid people that themselves have issues, not the phone.

Seems normal to me ,I bought mine month ago

There are no issues with battery on nexus 5. I charge mine usually once in 3 days, my record without charge is about a week.
It really depends on how you use it. Under constant 100% load I think battery can be depleted under 5 hours, as in every other device.

i can use my phone very heavily, and deplete my battery in 6-8 hours. but ill still get 5+ hours screen on time.

simms22 said:
the nexus 5 does not have battery issues, at all. it stupid people that themselves have issues, not the phone.
Click to expand...
Click to collapse
wow Simms, you're everywhere lol

xnormskix said:
wow Simms, you're everywhere lol
Click to expand...
Click to collapse
not quite, but in the n5 and n4 forums I am :angel:

Have you tried running the phone down till it switches off? I know it's not good practice to do that often but I like to do it with a new phone relatively early as it makes sure it's calibrated - sometimes phones can either switch off at 5% or, conversely, run on 1% for hours...

surrealjam said:
Have you tried running the phone down till it switches off? I know it's not good practice to do that often but I like to do it with a new phone relatively early as it makes sure it's calibrated - sometimes phones can either switch off at 5% or, conversely, run on 1% for hours...
Click to expand...
Click to collapse
You don't ever need to do that as it calibrates every time you charge the phone. Also he just got the phone and isn't having any battery issues.

bblzd said:
You don't ever need to do that as it calibrates every time you charge the phone. Also he just got the phone and isn't having any battery issues.
Click to expand...
Click to collapse
He means to break in a LIon battery the first three times you kill the battery and then don't take it below 20% after that.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
He means to break in a LIon battery the first three times you kill the battery and then don't take it below 20% after that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's not helpful and does more harm than good. Li-Po never needs to be user calibrated in any way.

Thanks!
Thanks a lot guys for taking your time and helping me , nexus 5 is truly an amazing phone.
@Ben36 yes , ingress is a game and its a location based so it keeps running in the background and uses location services.
Guys , I have some questions relating to the vibration motor , is it fine if I ask here or am I supposed to make a new thread?
Thaks a lot once again

simms22 said:
the nexus 5 does not have battery issues, at all. it stupid people that themselves have issues, not the phone.
Click to expand...
Click to collapse
I was just about to start a thread about something then I read this. So here's the deal. I agree that it's almost always user error and/or over expectation when it comes to battery. Stupid people are here to stay. I'm neither stupid nor expecting too much from my battery.
I've always been intrigued by how some experienced users get great battery and some get not so great. Has to be user error I always thought. I thought this because I was one of the experienced users getting great battery life. I mean GREAT. Way over 7 SOT all the time.
So a few weeks ago my first phone had an audio port issue that I had RMA'd. I received the new phone and set it up. It had crap battery. I'm talking less then 2 hours SOT. Same ROM, same kernel, same apps, same coverage for mobile and data, same usage. I set about looking for wakelocks and they all where the same as the first phone. Nothing was wrong on my end. I spent over a week troubleshooting. CPU frequencies and time in state where normal. Temps where normal. CPU benching was the same. Awake vs screen on was almost identical. The phone is sleeping like a baby when not in use.
So, using Occam"s razor, it would lead me to believe that not all batteries in the N5 are created equal. After getting off the phone with a google support supervisor a few hours ago he agreed. Another RMA process has been set up and I was promised this phone would make it's way back to LG so they can actually analyze the battery.
Like I said, I used to think the same way you do. Now I'm not so sure.

theesotericone said:
I was just about to start a thread about something then I read this. So here's the deal. I agree that it's almost always user error and/or over expectation when it comes to battery. Stupid people are here to stay. I'm neither stupid nor expecting too much from my battery.
I've always been intrigued by how some experienced users get great battery and some get not so great. Has to be user error I always thought. I thought this because I was one of the experienced users getting great battery life. I mean GREAT. Way over 7 SOT all the time.
So a few weeks ago my first phone had an audio port issue that I had RMA'd. I received the new phone and set it up. It had crap battery. I'm talking less then 2 hours SOT. Same ROM, same kernel, same apps, same coverage for mobile and data, same usage. I set about looking for wakelocks and they all where the same as the first phone. Nothing was wrong on my end. I spent over a week troubleshooting. CPU frequencies and time in state where normal. Temps where normal. CPU benching was the same. Awake vs screen on was almost identical. The phone is sleeping like a baby when not in use.
So, using Occam"s razor, it would lead me to believe that not all batteries in the N5 are created equal. After getting off the phone with a google support supervisor a few hours ago he agreed. Another RMA process has been set up and I was promised this phone would make it's way back to LG so they can actually analyze the battery.
Like I said, I used to think the same way you do. Now I'm not so sure.
Click to expand...
Click to collapse
oh, no, I 100% agree with you. just like our devices, that all aren't equal, that are all assembled in differing places, that all have smaller parts that are made in more different factories.. the batteries themselves will differ as well. it'll even probably fall onto a bell curve, where most are near the center, and less with better or worse. but 100% they vary.

theesotericone said:
I was just about to start a thread about something then I read this. So here's the deal. I agree that it's almost always user error and/or over expectation when it comes to battery. Stupid people are here to stay. I'm neither stupid nor expecting too much from my battery.
I've always been intrigued by how some experienced users get great battery and some get not so great. Has to be user error I always thought. I thought this because I was one of the experienced users getting great battery life. I mean GREAT. Way over 7 SOT all the time.
So a few weeks ago my first phone had an audio port issue that I had RMA'd. I received the new phone and set it up. It had crap battery. I'm talking less then 2 hours SOT. Same ROM, same kernel, same apps, same coverage for mobile and data, same usage. I set about looking for wakelocks and they all where the same as the first phone. Nothing was wrong on my end. I spent over a week troubleshooting. CPU frequencies and time in state where normal. Temps where normal. CPU benching was the same. Awake vs screen on was almost identical. The phone is sleeping like a baby when not in use.
So, using Occam"s razor, it would lead me to believe that not all batteries in the N5 are created equal. After getting off the phone with a google support supervisor a few hours ago he agreed. Another RMA process has been set up and I was promised this phone would make it's way back to LG so they can actually analyze the battery.
Like I said, I used to think the same way you do. Now I'm not so sure.
Click to expand...
Click to collapse
Well I feel that there are always some exceptions , some phones may have a manufacturing defect and maybe the phone you are talking about did have one , but these manufacturing defects are mostly really rare.

You should be good to go...just keep an eye on it! Happy Flashing

bblzd said:
That's not helpful and does more harm than good. Li-Po never needs to be user calibrated in any way.
Click to expand...
Click to collapse
I was just explaining what he said. The rumor is (supposedly backed up) that you kill the battery 3 times in a row but never take it close to dying after that and you get the best battery life possible because the battery works best if you only charge it between 20 and 80%. I think there may be something to it because new phones only last like half a day on the first charge but after a week last a day or longer for me. I won't derail this thread though as that's a debate that always loves to go on and I've never found hard proof either way but people who just write websites who supposedly sound smart and can word it quite eloquently.
That being said, I didn't necessarily agree with it, but I was clarifying what was said.

MrObvious said:
I was just explaining what he said. The rumor is (supposedly backed up) that you kill the battery 3 times in a row but never take it close to dying after that and you get the best battery life possible because the battery works best if you only charge it between 20 and 80%. I think there may be something to it because new phones only last like half a day on the first charge but after a week last a day or longer for me. I won't derail this thread though as that's a debate that always loves to go on and I've never found hard proof either way but people who just write websites who supposedly sound smart and can word it quite eloquently.
That being said, I didn't necessarily agree with it, but I was clarifying what was said.
Click to expand...
Click to collapse
Thanks for clarifying. Keeping the battery between 20% and 80% is said to help with battery degradation, which after a year or two might affect how much one could get out of a full charge. Most won't find it practical to limit them self to only 60% of their total available battery pool though.
Even hitting 0% isn't as big of a problem as some may think as there is a reserve charge for protection. For instance, mine has full died on me twice due to a power outage (I even attempted a boot up) and I always full charge with no noticeable degradation after 8 months.

battery has become utter trash since 8.1 update

anyone else notice it? first off, I'd be at like 40 minutes screen on time before I'd drop to 99 percent... now, it drops immediately after unplugging, and that 40 min screen on time, I'll be at like 69 percent now. it's absolutely ridiculous. battery drains like crazy now, but nothing is running in the background that shouldn't be. everything is identical to pre 8.1 update. today I was at right under 60 min screen on time, at like 59 percent. I looked at old screenshots pre 8.1, and I'd be at like 2.5 hours screen on time at 59 percent. it's absolutely ridiculous that Google is purposely ruining the phone with each update in terms of battery life. I'm not the only one, either. it's on reddit as well. planned obsolescence? yep, I'm starting to think so.
Sent from my Pixel 2 using Tapatalk

Man. Do you live off grid or something and can only charge every 2 days or something. If you want 3+ hours of SOT than you would have to be close to a charger anyways and that's with any phone. All these phones that have come out late 2016 early 2017 have the same battery set up...use your phone and charge it fast and use your phone some more.
My pixel 2 same as my Moto z2 force and my s8

jayochs said:
anyone else notice it? first off, I'd be at like 40 minutes screen on time before I'd drop to 99 percent... now, it drops immediately after unplugging, and that 40 min screen on time, I'll be at like 69 percent now. it's absolutely ridiculous. battery drains like crazy now, but nothing is running in the background that shouldn't be. everything is identical to pre 8.1 update. today I was at right under 60 min screen on time, at like 59 percent. I looked at old screenshots pre 8.1, and I'd be at like 2.5 hours screen on time at 59 percent. it's absolutely ridiculous that Google is purposely ruining the phone with each update in terms of battery life. I'm not the only one, either. it's on reddit as well. planned obsolescence? yep, I'm starting to think so.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I really doubt it's any different than it was. It's more likely the battery wasn't reporting correctly in 8.0. When I was on 8.0 the battery would sit at 100% for at least an hour, maybe 2, all the while I was using the phone. Yes, since 8.1 it drops much faster when I first start using it after removing it from the charger but at the end of the day I still have pretty much the same battery percentage left as I did when I was on 8.0. It drops faster to begin with but in the end, it's the same as before. Rather than planned obsolescence, it's more likely they simply fixed something that wasn't working properly before. There's no way you can use one of these things for an hour or more and not have the battery drop below 100%. Just my two cents worth.

Can't complain. Forgot twice to plug it in at night, woke up both times with 45% left. At my regular use that is good. My previous S7 would have been down to <20%. BTW, this:
jayochs said:
it's absolutely ridiculous that Google is purposely ruining the phone with each update in terms of battery life.
Click to expand...
Click to collapse
is just utter BS, maybe you should reinforce you aluminum hat...

I can't say my battery life has been bad or gotten worse with 8.1. If anything it got better. I didn't plug mine in last night, woke up with 38% left. That was about 20 hours since last charge. I don't think Google is purposely obsoleting their newest phones a couple months after release either.....
Edit: I should mention, I have my AOD always on, I have Now Playing enabled, double-tap-to wake is disabled, and I use one of the prepackaged Pixel 2 live wallpapers (Marvelous Marble). The only ting I really do thinking of the battery is turn the phone face down when I go to bed since that shuts off the display.

so i guess the fact that my screen on time has dropped by over an hour means I'm the one who's crazy, and the phone is perfectly fine.... riiiiiggghht.
Sent from my Pixel 2 using Tapatalk

jayochs said:
it's absolutely ridiculous that Google is purposely ruining the phone with each update in terms of battery life. I'm not the only one, either. it's on reddit as well. planned obsolescence? yep, I'm starting to think so.
Click to expand...
Click to collapse
jayochs said:
so i guess the fact that my screen on time has dropped by over an hour means I'm the one who's crazy, and the phone is perfectly fine.... riiiiiggghht.
Click to expand...
Click to collapse
I'm pretty sure this part of your post is the crazy part. Your battery drain is probably real. Have you confirmed it exists on a clean install without any apps installed or system configurations changed? Only then should you entertain that this is Google's fault. Even then, accusing them of doing it on purpose runs dangerously close to tinfoil hat territory.

I feel my battery life has gone down slightly going from 8.0 to 8.1. Though, I'm running all the bells and whistles this phone has to offer, along with tasker profiles. I also agree with the previous statement. Perhaps the system wasn't accurately measuring the battery life.
I did have horrible battery life for a bit when I was playing with a new kernel and dirty flashing some things to get Viper4Android working.
I have two Pixel 2 phones (non XL), and honestly they are amazing at battery compared to my HTC M8s (again two) . Are they perfect? No. Are they better than any phone I've ever had? Yes.
Sent from my Pixel 2 using Tapatalk

As has been said above, the battery no longer sticks at 100% for the first hour or so of screen on time, but that was always obviously nonsense anyway so a fair conclusion is that it's now better calibrated. But I've noticed no difference overall in battery life: yesterday was the first time I tried running for 2 days rather than charging overnight, and when I plugged it at night it had run for 41 hours with 6 and a quarter hours screen on and 7% remaining, so really not a problem there.

If you're having trouble with an update:
- Use BetterBatteryStats to figure out if any apps are acting up (or just top off the battery, use phone normally, and check Google's battery stats for Apps Using Battery, standby drain and screen on time)
- Clean flash the factory image, set up phone as new, go through charge cycle and check stats.
I'm not having any issues with battery on 8.1 (clean installed factory image). Easily get 4 - 6 hours SOT. As a matter of fact, my battery life is shockingly excellent for a smaller device like this.
Google is not making battery worse on purpose with their brand new flagship device.

I don't have any issues with the battery after the 8.1 update. It doesn't stay on 100% for a long time like it used to, but like everyone else is saying, that must have been buggy before. It isn't realistic for the battery to stick on 100% with 40 mins of SOT. Overall I don't see a reduction in battery life and I'm quite happy with the 8.1 update.

I was checking BBS and couldn't tell much. Do you still need to install it as a system app?
Ra6idr0y said:
If you're having trouble with an update:
- Use BetterBatteryStats to figure out if any apps are acting up (or just top off the battery, use phone normally, and check Google's battery stats for Apps Using Battery, standby drain and screen on time)
- Clean flash the factory image, set up phone as new, go through charge cycle and check stats.
I'm not having any issues with battery on 8.1 (clean installed factory image). Easily get 4 - 6 hours SOT. As a matter of fact, my battery life is shockingly excellent for a smaller device like this.
Google is not making battery worse on purpose with their brand new flagship device.
Click to expand...
Click to collapse

530farm said:
I was checking BBS and couldn't tell much. Do you still need to install it as a system app?
Click to expand...
Click to collapse
Not sure. I haven't used it for quite a while. The built in battery info works well enough for me, I haven't been having issues. It's good for checking wakelocks and some more advanced stuff but I think it needs a few cycles/days before it can analyze properly.

I think it's just the way oreo is. Ever since 8.0 it just drains the battery very aggressively. 8.1 the OS runs smoother, but battery drain is still high. Been the case though since 8.0 for me, nothing new.
I haven't clean flashed in over 6 months though. Just been on 7.1 and been rolling up the OTAs and chugging along. I found using Naptime by Franco helps a bit.

530farm said:
I was checking BBS and couldn't tell much. Do you still need to install it as a system app?
Click to expand...
Click to collapse
No
Sent from my Pixel 2 using XDA-Developers Legacy app

IMO battery life has never been great on the Pixel 2. It's the same on 8.1 as it was on 8.0 for me.

Right now I'm trending towards 6 hours SOT (3 hrs SOT at 50%), and I have been BT streaming audiobooks most of the day. I also watched Netflix for 30 min on full brighness. That's better than 8.0 for me, I was lucky to get 5 hrs SOT max.
I would say the calibration is more accurate now, it hung on 100% for too long, so it may appear to drain faster but so far in practice I've gained battery.
Battery life isn't as good as my OP5, but that has a big battery compared to the Pixel 2. I think for it's size it's doing a good job.

mikeprius said:
I think it's just the way oreo is. Ever since 8.0 it just drains the battery very aggressively. 8.1 the OS runs smoother, but battery drain is still high. Been the case though since 8.0 for me, nothing new.
I haven't clean flashed in over 6 months though. Just been on 7.1 and been rolling up the OTAs and chugging along. I found using Naptime by Franco helps a bit.
Click to expand...
Click to collapse
I guess you are talking about one of your other devices here, rather than the Pixel 2.

I am getting horrible battery life since going to 8.1
I installed the update the night of the 13th. The past 2 days my battery drains to 20% in about 8 hours. At that point whatever is causing it was stopped by the battery saver mode or the reboot I did when I discovered the phone was in battery saver mode.
Light use at work, staring at my phone is not a thing I have time for. No streaming, no surfing. Just checking texts and emails here and there. Prior to the update I'd get home 12 hours after I left the house and be around 75-80%. Not rooted, not unlocked. Bone stock.
Built in battery stats say 'system' is the culprit. Digging deeper I see Google Play Services app used 70% of my battery from about 7am to around 4 or 5pm this evening. I'd post a screen shot but I didn't to think of taking one before I plugged it in. I just installed BBS and will monitor it for a day.

Large Hadron said:
I guess you are talking about one of your other devices here, rather than the Pixel 2.
Click to expand...
Click to collapse
I thought this was the 5x forum for some reason. Pixel 2 no issues. It was my 5x

Question Android System Intelligence overheating and battery drain

I've had the Pixel 7 pro since December 2022. Ever since then whenever I had the newest version of Android System Intelligence installed this phone would overheat to the point where touching it got uncomfortable, it would thermal throttle, the pixel launcher would lag and the battery would drain way to quickly. I know that uninstalling the updates for Android System Intelligence from the PlayStore and locking it so it doesn't auto update fixes the problem, but my question is. Is there really nothing I can do about this? Will I really have to keep an older build of Android System Intelligence installed just to properly use my phone?

Try in safe mode as it may be a 3rd party app causing the issue. Try clearing data in that app and any associated apps.
Otherwise...
If you really want to go nuts, factory reset then try the updated version. Might get the same result though.
I don't upgrade or update my N10+; it's still running on the same load from 3 years ago with no issues and almost zero down time.
If it's fulfilling its mission let it be...

blackhawk said:
Try in safe mode as it may be a 3rd party app causing the issue. Try clearing data in that app and any associated apps.
Otherwise...
If you really want to go nuts, factory reset then try the updated version. Might get the same result though.
I don't upgrade or update my N10+; it's still running on the same load from 3 years ago with no issues and almost zero down time.
If it's fulfilling its mission let it be...
Click to expand...
Click to collapse
I appreciate the suggestion, however going into safe mode won't fix this. I already reset the device to no success, it sucks as I am really enjoying my p7p, if only it weren't for this issue.

Dark8812 said:
I appreciate the suggestion, however going into safe mode won't fix this. I already reset the device to no success, it sucks as I am really enjoying my p7p, if only it weren't for this issue.
Click to expand...
Click to collapse
I would just use the version that works unless that doesn't work either.
If the latter is the case it might be a huge can of worms...

blackhawk said:
I would just use the version that works unless that doesn't work either.
If the latter is the case it might be a huge can of worms...
Click to expand...
Click to collapse
I'm thankful version T.10.sysimg.pixel7.477131528 of ASI seems to be stable, but yes if this were the case for all versions I wouldn't have hesitated returning this when I had the chance

Really?
Going to test this out over the next couple days. My device previously used to run pretty cool, even though the weather got hotter, but now I'm never underneath 32°C even when idle, lol.

I'm not sure if this affects everyone. I talked to a friend that also has a pixel 7 pro and according to him he doesn't have this problem.
Yeah, it got to the point where even if I left my phone idle, it would be warm to the touch and hot whenever I started using it, even if all I was doing was texting someone.
https://play.google.com/store/apps/details?id=com.google.android.as
Uninstalling the updates makes it stable again, you might have to restart your device for changes to fully take effect though.
Another thing I could mention is, that going into the battery settings and seeing which app uses the most amount of battery it would end up showing the pixel launcher not ASI, having looked online and trying things out myself I figured ASI was the real culprit and not pixel launcher. Basically I think that features like at a glance, which are integrated into the pixel launcher make use of ASI and for some reason newer versions just like using up a lot of performance in the background, resulting in pixel launcher being reported as a huge battery drainer to android when in reality it's ASI

Curiousn00b said:
Really?
Going to test this out over the next couple days. My device previously used to run pretty cool, even though the weather got hotter, but now I'm never underneath 32°C even when idle, lol.
Click to expand...
Click to collapse
What's the ambient temperature? If it's running warm now a few days won't help unless you track down the cause. If found, boom, the excessive cpu cycles and heat will stop.
Is global power management active? If so try disabling it.
Are any services disabled? Dependencies...
Try temporarily disabling Google play Services and see if that tones it down. Backup Transport, Playstore and Gmail are dependencies.

blackhawk said:
What's the ambient temperature? If it's running warm now a few days won't help unless you track down the cause. If found, boom, the excessive cpu cycles and heat will stop.
Is global power management active? If so try disabling it.
Are any services disabled? Dependencies...
Try temporarily disabling Google play Services and see if that tones it down. Backup Transport, Playstore and Gmail are dependencies.
Click to expand...
Click to collapse
Pretty much the same usage day by day, but even with the heat being hotter and the A/C being on, that warmth is just there.
I run strictly custom roms currently, so my device is normally pretty barebone on apps nowadays.
I rolled back to a version from March, as April/May is when the heating did start. I'm actually sitting at 29°C right now as I type this, compared to the 33-35 from the first couple minutes of Telegram.
Going to test it out for a few days and see how it manages on the go and whatnot.

Curiousn00b said:
Pretty much the same usage day by day, but even with the heat being hotter and the A/C being on, that warmth is just there.
I run strictly custom roms currently, so my device is normally pretty barebone on apps nowadays.
I rolled back to a version from March, as April/May is when the heating did start. I'm actually sitting at 29°C right now as I type this, compared to the 33-35 from the first couple minutes of Telegram.
Going to test it out for a few days and see how it manages on the go and whatnot.
Click to expand...
Click to collapse
Looking at the milliampere usage real time can yield clues. At idle I want to see it sink below 100ma and go to 70ma or lower occasionally couple times a minute. If I see a lot of high spikes or it's averaging in the 3-400's or higher at idle with no apps open, something's up.
A logging firewall can help pin down which app is sucking the juice.
Custom roms are harder to troubleshoot than stock. If you're rooted you have more monitoring and diagnostic tools available though if you use them.

blackhawk said:
Looking at the milliampere usage real time can yield clues. At idle I want to see it sink below 100ma and go to 70ma or lower occasionally couple times a minute. If I see a lot of high spikes or it's averaging in the 3-400's or higher at idle with no apps open, something's up.
A logging firewall can help pin down which app is sucking the juice.
Custom roms are harder to troubleshoot than stock. If you're rooted you have more monitoring and diagnostic tools available though if you use them.
Click to expand...
Click to collapse
While I completely agree about everything, apparently, ASI turned out to be the culprit... I'm now at 25°C. I haven't been this low since before the April update. Who would've thought it was that simple, lol.
I've previously tried even stock and on my end, I had only Whatsapp with 2 other apps installed, but I still couldn't get under 33°C. The second I downgraded my ASI, my temps dropped. Everything the OP was experiencing has been my experience that I've been explaining here and there on Telegram as well.

Curiousn00b said:
While I completely agree about everything, apparently, ASI turned out to be the culprit... I'm now at 25°C. I haven't been this low since before the April update. Who would've thought it was that simple, lol.
I've previously tried even stock and on my end, I had only Whatsapp with 2 other apps installed, but I still couldn't get under 33°C. The second I downgraded my ASI, my temps dropped. Everything the OP was experiencing has been my experience that I've been explaining here and there on Telegram as well.
Click to expand...
Click to collapse
Yay! So how how did you correct it?
I keep all social media, shopping and banking apps off the phone. I use by browser login only.
WhatsApp I avoid entirely.

blackhawk said:
Yay! So how how did you correct it?
I keep all social media, shopping and banking apps off the phone. I use by browser login only.
WhatsApp I avoid entirely.
Click to expand...
Click to collapse
Not sure about kernels for thermals, but currently running Sultan's kernel, and I installed the ASI from March 31st(didn't want to be too outdated. Not sure what version comes preinstalled)
This one
I'm going to see how the device deals with mobile data tomorrow on the go.

Curiousn00b said:
Not sure about kernels for thermals, but currently running Sultan's kernel, and I installed the ASI from March 31st(didn't want to be too outdated. Not sure what version comes preinstalled)
This one
I'm going to see how the device deals with mobile data tomorrow on the go.
Click to expand...
Click to collapse
I wouldn't worry about it being "outdated".
The only thing that counts is if it runs well, is a joy to use and is fulfilling its mission.
This N10+ is still running on Pie. It's current load is 3yo now, still fast and stable with minimal maintenance. More play time, less down time.

My day yesterday, I didn't go over 37°C while I was out all day surprisingly and the phone never felt warm in hand.
I wonder if it felt warm previously since something was wonky, but now since it seems more settled, it's not as warm but even at the highest temp(35-37), it feels normal to hold.

Curiousn00b said:
My day yesterday, I didn't go over 37°C while I was out all day surprisingly and the phone never felt warm in hand.
I wonder if it felt warm previously since something was wonky, but now since it seems more settled, it's not as warm but even at the highest temp(35-37), it feels normal to hold.
Click to expand...
Click to collapse
Likely something you did. Problem is -what- if it reoccurs
Always best if you can find to root cause. For a frequently reoccurring problem a reboot is not the answer even though it may temporarily solve it. Androids should may able to run days, weeks with no reboot or issues.
Once you find it the solution will seems simple... but when the issue is causing high battery drain the pressure is on. That's what took out my first battery, got less then 16 months on it before it failed (and I do mean failed!). You never want a warm idling phone as it is trouble; robs you of performance... and batteries

НIt's 27 degrees outside. The phone heats up to 36-42 degrees on LTE. Cleaned the device and set it up as new a week ago. June firmware, everything is updated

Dark8812 said:
I've had the Pixel 7 pro since December 2022. Ever since then whenever I had the newest version of Android System Intelligence installed this phone would overheat to the point where touching it got uncomfortable, it would thermal throttle, the pixel launcher would lag and the battery would drain way to quickly. I know that uninstalling the updates for Android System Intelligence from the PlayStore and locking it so it doesn't auto update fixes the problem, but my question is. Is there really nothing I can do about this? Will I really have to keep an older build of Android System Intelligence installed just to properly use my phone?
Click to expand...
Click to collapse
How big is the drain?
The Battery usage shows indeed ASI and Pixel Launcher for almost whole time span (~6h), but the battery drain is respectively 2% and 1%, were 20 minutes of Opera Browser used 19%, so it looks minimal. My phone does not get warm in idle or even in light usage, while the ambient temperature is ~25-26 celsius.

oko17 said:
How big is the drain?
The Battery usage shows indeed ASI and Pixel Launcher for almost whole time span (~6h), but the battery drain is respectively 2% and 1%, were 20 minutes of Opera Browser used 19%, so it looks minimal. My phone does not get warm in idle or even in light usage, while the ambient temperature is ~25-26 celsius.
Click to expand...
Click to collapse
From what it seems this doesn't seem to be affecting everyone, a friend of mine also owns a pixel 7 pro and he told me he doesn't have these problems. On average Pixel Launcher would use about 40% Battery and my phone wouldn't last longer than 6 hours even with barely any usage. I am running stock newest June update and have not rooted this device so I can't for sure say what the cause is other than ASI

Dark8812 said:
From what it seems this doesn't seem to be affecting everyone, a friend of mine also owns a pixel 7 pro and he told me he doesn't have these problems. On average Pixel Launcher would use about 40% Battery and my phone wouldn't last longer than 6 hours even with barely any usage. I am running stock newest June update and have not rooted this device so I can't for sure say what the cause is other than ASI
Click to expand...
Click to collapse
During a production run they sometimes substitute smaller chipsets. This can lead to instruction set incompatibilities in the firmware.
Since it only involves a few hundred units tracking down this kind of issue is a ***** and the manufacturer's fault. Samsung is known to do this and they're not the only ones...