[Q] Unusual awake time on BBS - Nexus 4 Q&A, Help & Troubleshooting

Hey guys can you take a look at the following attachments below. The first pic shows that I have 55% battery left after 15 hours. However, on the second attachment the Screen on its only around 1 hour and 26 minutes and that awake time is around 3 hours and 40 minutes. I said to myself "hey maybe there were lots of wake locks. So I checked and there was no unusual wake lock in the partial wake lock section and there was even no kernel wake lock indicated .
So the thing is, I didn't use my phone that much today (only a cumulative of 1 hour and 26 minutes but it used half of my battery and awake time is too big but BBS wake locks does not indicate the culprit for keeping my phone awake for such a long duration of 3 hours and more. What seems to be the problem? Thanks guys!

Related

Can those with a GSM Hero check their awake time?

The CDMA version is having issues with the phone's status displaying as 100% awake time after sending a text message. It is thought that a text triggers a lock on the dialer to remain awake even after putting the phone to sleep, leading to the horrid 12 hour battery life with our Heroes. Using Spare Parts we can see that the dialer is near 100% of the Partial wake usage once a text is sent. We are fairly positive that this is the culprit, but I have yet to read if anyone has actually checked the other version.
To rule out another cause, would any of you out there with a GSM hero check/test if this is the same for you?
The simple test is to:
1. restart the device
2. send a text (using the default HTC app)
3. check your awake time status (settings-->about phone-->status-->awake time)
4. put the phone to sleep for a few minutes
5. check again
Thank you
HERE is the thread with the problem if you care to read up on it.
hi, been sending texts all day and havnt had a problem on my gsm hero
up time is at 42.43.22
awake time : 12.29.55 (29%)
after restarting and sending a text, i waited a few minutes and checked again
up time 8 mins
awake time 7.27 (92%)
so no problem there
on a side note,when i brought the hero it had crap battery life, less than a working day but after an update all was fine
Thanks for the info. It seems like we need an update as well
Do you by chance have Spare Parts installed and can check on the "Partial wake usage"?
yeah
just to let you know
up time is now 1.54.37
awake time is 0.29.30 (26%)
now to spare parts partial wake usage
android system 3mins 29 secs
net counter(app) 51 secs
facebook 40 secs
dialer 36 secs
i have end button behaviour set as " go to sleep"
phone hasnt really been used much since i booted it last
Great! Thanks again for all the help.
And the fact that you haven't used the phone much in the last few hours exactly demonstrates our ****ty problem

Problem with wake lock (awake time really high), maybe even battery

Ok, this may sound a little bit strange, but once, maybe twice a day, I see a long bar on the Awake status in the Battery Use screen, indicating that something is keeping the phone awake for some time, usually a couple of hours.
Straight example:
I charged my phone to 100% on 8 April, around 22:30.
It's 10 April, 14:35 now, so it's on for about 1d 16h.
It still has 26%, with screen brightness set at 10%.
The alarm was set to 9:00 on 10 April.
Usage statistics:
- Display 28% (2h 16m)
- Cell Standby 22% (1d 15h 44m)
- Android System 17% (51m keep awake)
- Phone Idle 9% (1d 13h 28m)
- Android OS 5%
- OS Monitor 5%
- Voice calls 4% (7m 24s)
- Google Services 3% (16m keep awake)
- Google Search 2%(12m keep awake)
- Launcher PRO 2%
On the battery graph, I clearly see the flat line part of the last night (10 April, 00:00 till 10 April, 9:00), where I was asleep, indicating that there was no awake state, and the battery wasn't drawn of power.
But, because I was to lazy to get up when the alarm rang at 9:00, I consecutively put it to snooze about 8-10 times. That meant from 9:00 till ~10:30. After the last time on snooze, I completely turned the alarm off. I got up at 13:30 (yea, I know, I was kinda of lazy today).
Well, the problem consists in the fact that, even after 10:30, when I shut the alarm down for good, it was still awake. The awake bar in the graph points from the first time I put it on snooze till when I got up. That means from 9:00 to 13:30.
I installed OS Monitor from the Market and analyzed the logs. Indeed, from 13:15 till 13:30, the wakeup wake lock was triggered about 15 times only for alarm. So, the process was still on, even after i turned it off. What gives ?
Is it normal to even stay awake after snooze ? Can't it just wake up right when the snooze time ends ? I can't believe that it really needs to stay on all the time. And what about AFTER I turned it off ? Why the hell does it need to stay awake then !?!?
It's so unbelievable, that I actually don't think it's something Google-related (Android code fail, I mean), maybe something to do with MY phone in particular, though that would be stupid as well, I know. So what the hell is going on here ?
PS: Oh, I almost forgot. It's not only the alarm. One night it started to stay in awake mode from ~01:00 midnight till 10:00 in the morning. Unfortunately, I didn't have OS Monitor installed then. But I can give you another 7 processes that bust the wake up, besides alarm. Those would be the following: mmc_delayed_work, gpio_input, modem_fmt, modem_ip_rx, KeyEvents, PowerManagerService, max8998-charger (WTF IS THIS !>!>!>>!>!?!>!>!!?!?!?!?)
PPS: About the battery, I think it's faulty, because I have barely used it in the last 1d 16h and it has 26% left. What do you think ?
Dont think its a faulty battery. I get 17-18hrs n I use the hell outta my phone (200-500 text/day, gtalk, twitter, reading news articles, a couple YouTube videos n maybe a phone call or 2...)
Yea, well... if I send 200-500 text/say + gtalk + etc. etc. those 1d 16h would drop to about 8-10h. Compare that to your 17-18h. It's not really good now, is it ?
What's your screen brightness and how long does your screen stay up ?
Well, I have an update for 1 process from the list of 7:
gpio_input, is a process that handles physical buttons. To be more precise, every time you press the power button to wake up the device, the process is being activated.
Furthermore, after I pressed 2 times Volume Up + 1 time Volume Down + Power button, with a total of 4 button presses, it would fire up 4 distinctive gpio_input processes. So, for every physical button pressed, another process would fire up.
So no need to worry about this one. Let's see the others. The alarm one is still present all over the freaking place !
PS: Forgot to mention something: the always-awake state has gone sometime during the day. I think it was right after I did a restart. Dunno why... it just ended. Pff.
I think this is a bug because I see it on my nexus one too. Over night I'll see solid line for hours showing my phone woke up. But interestingly no battery drain happens, its just reported as being awake.
RogerPodacter said:
I think this is a bug because I see it on my nexus one too. Over night I'll see solid line for hours showing my phone woke up. But interestingly no battery drain happens, its just reported as being awake.
Click to expand...
Click to collapse
Exactly.
As for the battery, I've calculated my usage of 3G talk-time (10 mins of talk time on my phone representing 4% of battery), compared to the official stated talk-time (of 400 mins):
Oficial:
400mins = 100%
10 mins = x%
x = 2.5% from the total battery level (x represents how much % of battery level should 10mins of 3G talk eat juice, after Google standards)
Real stats:
10 min = 4% out of 95% battery level
Phone = 4/100*95= 3.4% from the TOTAL 100% battery
y mins = 100%
10 mins = 3.4%
y = 1000/3.4 = 294mins ~= 300mins REAL TALK TIME
So, after calculations, it seems that for MY phone, the 3G talk time is actually 300mins, not 400 as Google states. That's an argument for WHY I actually believe my battery sucks. Well, it doesn't TOTALLY suck, as some of your batteries here on the forum... but it is indeed below the standard. Isn't it ?
Yep, it happened again. No problems during the night, but in the morning, when the alarm started, the always awake state has begun. It now shows a long blue bar that spans for about 3-4 hours. What is peculiar is that the wake lock alarm is on during the hole day, even if the alarm is completely off.
LE: Surprisingly, after a restart, it would sleep normally. I can't think of any other possibility besides the alarm (I mean, if you put the alarm to snooze, it will keep your phone in permanent awake state onwards from that point.)
What is even more interesting, is that you don't need to restart the device to finally put it back to sleep, as I stated above. I've charged it to max and the always-awake state was gone. Interesting, isn't it ? Guess it's just a glitch... If, somehow, someone knows the answer to this, I would gladly listen to it. Until then, well... I guess I'll just forget about it and never bother again. Hope you guys don't have problems with this and/or something similar. Cheers !
I have the same on Acer Liquid Metal.
Any remedy foud?
Tried to track down with aLog, but useless
I'm not quite sure... but I think maybe Maps is the cause. Again, I'm not sure at all, I'm just seeking a pattern every day I use it, and this far, Maps has been the best bet for this glitch. Can you confirm that ?
LE: Forgot. The remedy is, well... just go to Task Manager and stop the app.
Also, I have seen 3 instances of this process:
- com.google.android.apps.maps
- com.google.android.apps.maps:NetworkLocationService (I think this one is the problem)
- com.google.android.apps.maps:Friends (or something like this; and wondered what the hell it is for...)
For me the culprit is definitely maps. And that effect is doubled when I'm signed in to latitude. Just by signing out of latitude I can double my battery life and by disabling "wireless networks" in the location settings my battery life can be tripled! There is something really wrong with the maps app here.
Sent from my Nexus S using XDA App
anirudh.pullela said:
For me the culprit is definitely maps. And that effect is doubled when I'm signed in to latitude. Just by signing out of latitude I can double my battery life and by disabling "wireless networks" in the location settings my battery life can be tripled! There is something really wrong with the maps app here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks a lot for the input, really appreciate it. Unfortunately, I don't use Latitude, so I can't confirm that part. Neither the wireless networks part, I haven't notice that before... but I'll see what I can come up with.
Still searching what to stop
All you said was already deleted/frozen but problem persist

Phone Awake

Hello guys
I have an issue, BetterBatteryStats says that my phone is awake for 2 hours while my screen time on is only 1 hours 10 minutes and in the partial wakelocks it states:
-GTALK_ASYNC_CONC
3 minutes 30 seconds
And I don't have gtalk installed??
Even though how do I know whats keeping my phone from going into deep sleep?? Battery usage only show high Android OS
Please help
Thank you
Sent from my GT-N7000

How much and quick should G2 deep sleep when off

I am pretty impressed with the G2 battery especially while in use. I originally got the phone and was in awe how it would go 3 hours from full charge with still 100%. So last 2 nights wanted to see what it was like all night. It looses about 2% per hour. Not terrible but Gsam shows the phone is awake for like 7 hours. I have messed with some setting and such and I will turn off for an hour then recheck. Right now it shows it was awake for 42 minutes and off the charger for 43 minutes. Woke device 8 times with 127 wakelocks. Cache update service for 42 minutes. 2% in 45 minutes battery. So the question is, how quick does the phone go into deep sleep.
tw557 said:
I am pretty impressed with the G2 battery especially while in use. I originally got the phone and was in awe how it would go 3 hours from full charge with still 100%. So last 2 nights wanted to see what it was like all night. It looses about 2% per hour. Not terrible but Gsam shows the phone is awake for like 7 hours. I have messed with some setting and such and I will turn off for an hour then recheck. Right now it shows it was awake for 42 minutes and off the charger for 43 minutes. Woke device 8 times with 127 wakelocks. Cache update service for 42 minutes. 2% in 45 minutes battery. So the question is, how quick does the phone go into deep sleep.
Click to expand...
Click to collapse
it sounds like you have the 'wakelock' problem. is it google services or android system thats taking up all the power? i have that problem on my wifi at work, for whatever reason. when im on that wifi, NLPwakelock is constantly waking my phone and keeping it from going to sleep so my battery drains quickly. if im on my wifi at home or on 4G LTE then i dont have that problem.
trying turning off wifi. if you are still having the problem, you might need to turn off location reporting and location history under google settings -> location, and access to my location under settings-> location access. see if that helps.

Honor 6 Battery Stats

Hello, put here your stats from battery
How much you get hours on the screen etc.
Never took a screenshot after full drain...normally with an hour of asphalt 8 and few hours of browsing with wifi,couple of hours of videos on local storage and other things altogether i get 6 hours screen time with a standby of 35 to 40 hours with 50 to 60% brightness on manual brightness...that is after draining the battery to 7%.always i have location services turned on with battery saving and googlenow too turned on all the time..wifi i turn only wheni turn the screen on...without gaming i get 7 hours screen on time with same standby time...i donot use whatsapp and autosync is turned off..if we try to push it hard with just one app like a news reader open we can see 10 hours screen on time with this phone..because when reading through just one battery drop is 1% for 8 mins..have attached images i took with 32% battery remaining...
I managed to get 4 days standby with 4 hours on screen time. Phone was charged for 10 minutes during this from my PC (extracting a file from it) which shouldn't have made much of a difference as it takes a lot to charge the phone (2a).

Categories

Resources