[Q] Wake up laf fix - Galaxy Note II Q&A, Help & Troubleshooting

Hello there,
I found a solution to the wake up lag, I tried everything before but nothing did the work. Its an app called wakelock, so far so good, batter drain is not that big, about 8% in 8 hours idle, I can live with that. I'm worried if there's a side effect to this? being the cpu constantly on, will this shorten its lifetime? Thanks.

Going from the name of the app and a quick peek, what it does is use a wakelock(!) to prevent the phone going to deep sleep. My guess is it will shorten battery life by around 20%, but I can't see how it should do any damage to the cpu.
Sent from my GT-N7100 using Tapatalk 2

It's not an amazing solution tbh, as it's keeping your CPU awake all the time. If the CPU doesn't enter deep sleep, there is no wake-up lag.
I don't imagine you'd immediately notice any major issues with it, but longer term nobody can really say - I don't think you will have a problem in a normal period of usage of the CPU such as a year or two. But at the end of the day, any time you change things like this, there's a risk, regardless of how small.

Related

setcpu uv settings

i was hoping somebody had optimal setcpu uv settings. i'm trying to squeeze every last drop from my battery but i really don't know how to set it up. any help would be great.
Read this.
I'm using these settings and my phone lasts for 5 days (no gaming ofc. )
thanks. trying those settings now
Theres no such thing as optimal settings...everyones phone has different tolerances...
Go down in steps of 25 and stress test is the best way...Trail and error.
This belongs in Q&A ...not here
Sent from my GT-I9100 using XDA App
yea i used the settings in the link as a starting point and managed to lower them a little. is it just me or does that 4 days on a charge seem a little too good to be true? the best i can get seems to be around 1.5% of a 1650mah battery per hour in standby. about as good as my hd2 running gbx 12 got. the phone does go into deep sleep (76% since reboot) but i don't get anywhere near the tiny battery drain some do. the setcpu uc and uv adjustments did help some but not as much as i had hoped for, guess i'm just gonna have to get a bigger battery.
i put it here 'cause it was a setcpu question. i know its turning into something else. sorry 'bout that.
Thats because you have wakelocks. In deep sleep, I get a maximum of 5% battery usage over a 10-12h period. Check if some apps are keeping your phone from going into deep sleep.
yea i have quite a few wakelocks but they only are "active?" for a few seconds. k-9 was the biggest culprit but a bunch were system processes. i set k-9 now to not poll but i don't know what do do for the rest.
how do you know if the wakelock is a partial or is locked? do the partial ones keep the phone from sleeping all the time or only when the app/service is active? is there any way to suspend/overide partial wakelocks on a per case basis so email and such can update but still blocking some? i've done a little reading but this seems more complicated than it should be.

Battery meter is just useless

Hi,
On my One-X battery meter is completely inaccurate. Sometimes it sits for hours on one value (e.g. 90%) and then suddenly drops (with no CPU/data activity whatsoever) to for example 80%. This results with very jerky battery use graph (attached mine). I am on 1.29.401.7 and done multiple full discharge/charge cycles, but it does not make any difference.
I have never seen such bad battery meter behavior on any other Andoid phone. Have you got similar problem?
I have the exact same problem actually.
Same here. It's as if it doesn't update the battery meter when it's in sleep (fifth core running). I suspect it's because of the T3 architecture and power management. As soon as you wake it, after maybe a minute, it updates the battery status...
Mines does it. Can sit on a %age for an age then with little use it will plummet.
@Op,
No I didn't notice such a problem on a unrooted One X and with no modifications running the latest OTA update 1.29.401.11.
Did you play with battery apps or did you modify something yourself which could cause this issue? Did you investigate what could cause it?
How long do you have your device, did you install apps? Can you provide more info about it maybe? Do you softreset your device?
Did the problem exist when you bought the device?
Thanks.
So it must be general problem then. It happens to me not only in sleep mode, but when browsing the web, etc.
I think these sudden percentage jumps and meter inaccuracy also contribute to all these battery life complains from various people. I was personally shocked when after a few minutes of web browsing battery dropped instantly from 30 to 20%. It looks like crappy battery, but in fact seems to be just dodgy meter...
Laurentius26 said:
@Op,
No I didn't notice such a problem on a unrooted One X and with no modifications running the latest OTA update 1.29.401.11.
Did you play with battery apps or did you modify something yourself which could cause this issue? Did you investigate what could cause it?
How long do you have your device, did you install apps? Can you provide more info about it maybe? Do you softreset your device?
Did the problem exist when you bought the device?
Click to expand...
Click to collapse
I have got the phone for almost a week now and I am pretty sure this problem has been there from the very begining. I initially though this is because a couple of full charge / discharge cycles are required to calibrate the meter, but it did not make any difference. My phone is not unlocked, no mods or battery apps. I did not try soft reset though.
It looks to me that meter is somehow not updating during the sleep. When device wakes from sleep, after a couple of minutes value drops significantly. This problem is probably a reason for various false claims that One X does not consume a single percent of battery during the overnight sleep.
Yeah, i have the same thing. Sometimes my battery drops about 2 or 3 percent at once, sometimes 10 percent...pretty annoying.
Thanks for your reply.
I'm new to Android but I do have some Windows Mobile experience.
It's weird to me seeing people having such problems because I realy don't experience it.
My battery meter is constant, also after a night sleep.
Maybe it's because I use my device different as others I don't know, it's strange to see all these reports in XDA forum as the One X to my opinion is a very cool device.
Maybe you could try some battery percentage apps and see if it realy is that insufficient?
aszu said:
I have got the phone for almost a week now and I am pretty sure this problem has been there from the very begining. I initially though this is because a couple of full charge / discharge cycles are required to calibrate the meter, but it did not make any difference. My phone is not unlocked, no mods or battery apps. I did not try soft reset though.
It looks to me that meter is somehow not updating during the sleep. When device wakes from sleep, after a couple of minutes value drops significantly. This problem is probably a reason for various false claims that One X does not consume a single percent of battery during the overnight sleep.
Click to expand...
Click to collapse
No problems with the battery monitor whatsoever (unrooted) 1.28.161.9
Laurentius26 said:
Thanks for your reply.
I'm new to Android but I do have some Windows Mobile experience.
It's weird to me seeing people having such problems because I realy don't experience it.
My battery meter is constant, also after a night sleep.
Maybe it's because I use my device different as others I don't know, it's strange to see all these reports in XDA forum as the One X to my opinion is a very cool device.
Maybe you could try some battery percentage apps and see if it realy is that insufficient?
Click to expand...
Click to collapse
I used your excellent ROMs on my HD2 in dark WM6.5 ages . I am glad to see you here with One X!
I installed Battery Meter Widget and (if the readings are correct), my One X consumes about 10-15mA during the sleep with Wifi and 3G on. I will keep an eye on the percentage.
Don't get me wrong - besides of erratic GPS and dodgy battery/power management problems, I really love this device.
I really wished that international One X version was based on S4 SoC (superb GPS with GLONASS and great power management as S4 is a 28nm chip). It is such a shame that dodgy Tegra 3 ruins this excellent device...
Hello, maybe this behaviour is only due to the voltage sampling/display ...
Someone here says the native battery app was only at 5% precision at display
and it looks like it updates in long time samples too ( 5 minutes ? ) ...
Knowing that Li-Ion goes from 3600 mV ( 0% ) to 4200 mV ( 100% ),
it means 600 mV of voltage variation from empty to full, with 1 mV precision.
So 1 millivolt is 0.2% of battery charge.
The display should be really more precise if all voltage precision was used.
aszu said:
Hi,
and then suddenly drops (with no CPU/data activity whatsoever)
Click to expand...
Click to collapse
looking at that screenshot you have posted the sudden drops appear to be perfectly aligned to the 'screen on' or 'awake' periods so the most likely (and obvious) cause is that using the phone causes most battery use. I have seen this with many phones, I think its normal. Being in standby doesnt use much power at all but lighting the massive 4.7" screen and running a quad core processor does, so when you use the phone it uses loads more juice... thats my analysis anyway
f_padia said:
looking at that screenshot you have posted the sudden drops appear to be perfectly aligned to the 'screen on' or 'awake' periods so the most likely (and obvious) cause is that using the phone causes most battery use. I have seen this with many phones, I think its normal. Being in standby doesnt use much power at all but lighting the massive 4.7" screen and running a quad core processor does, so when you use the phone it uses loads more juice... thats my analysis anyway
Click to expand...
Click to collapse
No, this is different. Drop in fact seem to be related to wake up from deep sleep, but the point is that this drop is massive and instant i.e. battery instantly drops from 30 to 20, bypassing all other percent states in between. Also, I am sure battery state does not update properly in deep sleep in many cases. At some point I left my phone for almost a day alone (wifi, 3g, Gmail and exchange sync, etc) and it did not lose a single percent, but as soon as started using it I observed instant 20% drop.
Same problem here even after hard reset
Sent from my HTC One X using XDA
d33f said:
Same problem here even after hard reset
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
+1
And I have even worse problem, can anyone help me?
Take a look at my thread (not highjacking yours, just want some help too), my current widget never reads a real value AFAIK.
It stay with -850 for more than an hour at times...
And my battery life is dismal...
So this means that seeing no battery discharge throughout the night in sleep mode isn't due to excellent power saving feature of the companion core but is in fact poor battery meter?
And yes, my One X shows fast and huge discharge (3-5% at once) when I use after being in long sleep mode
samuelong87 said:
So this means that seeing no battery discharge throughout the night in sleep mode isn't due to excellent power saving feature of the companion core but is in fact poor battery meter?
And yes, my One X shows fast and huge discharge (3-5% at once) when I use after being in long sleep mode
Click to expand...
Click to collapse
I think it too. Phone on sleep with data and sync on for 1 or 2 hours and % don't change. Use it for 2 min. and it suddently goes down by 5/10%
In my opinion the battery meter lacks of accuracy. This brings to inaccurate real time current calculations and wrong information about what's consuming power when we use it. That's bad!
I'm also seeing these big drops. For me it seems to happen between 100%-60% battery, battery level will drop anything from 5%-10% chunks at a time. After 60%, it does seem to be more stable and drop in 1-2% increments.
I've recalibrated the battery through CWM a couple of times but still get this issue.
It almost seems like there's a bug in the code that is causing the fuel gauge to not update.
I can tell you this, I modified other HTC phones battery driver. The nexus one driver for example updates volt, percent, temp, every 50 seconds while the screen is on. When off the sample poll changes to 10 minutes per update. This is real easy to see in the driver code, and you can filter dmesg log for "batt" and see the time stamps do in fact match this.
But the one x looks to be getting hung up on that part. Anyone know if kernel code has been released yet?

[Q] Initial charge?

I hate to be the guy that asks this, but I just want to make sure as from what I understand this is different from phone to phone. From what I understand, Li-Ion batteries, like the GN2's, do not have a memory effect of any kind? And thus all battery calibration rituals and nonsense are entirely pointless for this handset?
The reason I ask is because I wasn't able to charge the device to 100% before use like I was always told to do with new phones. My device was turned on and used until it drained to around 10% at which point it was charged to 100%.
Now, after 2 weeks of use, I feel that my battery is not as good as it should be. I'm barely able to get more that 12 hours. I'd be happy to post some battery graphs in the morning.
One last thing, if I did mess up my battery, or if my battery is messed up or less functional than it should be, would buying a new battery fix all my problems?
Youvare right. All that calibration stuff is nonsense.
I have never charged my phone to full before using and draining the battery and my phone still lasts all day on mostly heavy use.
Could you post your batt stats?
Sent from my GT-N7100 using xda premium
Today I ran my phone with the "lowest" possible settings, that is lowest brightness, CPU power saving, and no haptic feedback. I did not turn off wifi. Doing this I was able to get a surprising 16 hours, although you can see from the graph that I didn't use my phone as much. Attached I have a screenshot of what it's like with the highest possible settings (no power saving stuff, and brightness all the way up, but no GPS). Sorry I don't have a pic of the percentages for the high settings, I never thought to do that.
What concerns me the most is this: even with the lowest settings, I'm only getting 2 hours screen time. (last pic)
What's interesting is that you would think that if I'm getting such poor screen time, there would be something else using a lot of battery, but there isn't. This led me to believe the problem was with the battery. I discovered a pretty big scratch on my screen the other day, and I have some monthly insurance plan from best buy, so I was thinking of just getting a new one. The longer I wait to get a new one, the harder it will be to set up everything again. lol
I noticed that compared to other GN2s, mine seems to wake up a lot when the screen isn't on. The awake periods tend to correspond with drops in battery and also when I have a poor signal. Could this be caused by my phone trying to look for signal and using battery?
Yes poor signal that results in the phone searching for better 3g/2g will drain the batteey faster.
Can you try using it in airplane mode with wifi only for a day and see how that goes?
Also install Better Battery Stats and after a day or so of normal usage check your partial unlocks to see if a rogue app is preventing deep sleep and sucking your juice.
Sent from my Nexus One using xda app-developers app
Yeah it us definitely your signal playing a role. Also you have a lot of wakelocks showing up
Sent from my GT-N7100 using xda premium
Dude you have major wakelocks that eat up 80 % of your battery!
Go to application manager and remove all the apps you don't use.
K, I agree with my week signal using battery. I only have 75 apps on my phone and they're all pretty mainstream, no obscure apps. Right now im in school with 86% battery, I'm turning on airplane mode now. I have noticed however that when I clear my ram it closes like 50-60 processes each time. I am always closing my apps, but 50 seems extremely high. im gonna turn on airplane mode and see how that goes...
thanks!
Yes, you do have poor signal but that's not all. You have terrible wakelocks pal. Install BBS and monitor which apps are the culprit. It's not about 75 apps, even 2 or 3 bad apps, which have hidden advertisement going on could suck your battery flat in no time.
So first thing, install BBS. 2h screen on time is horrible!
Btw- If you're on 3G, try to switch to 2G. Difference will be unthinkable.
Sent from my GT-N7100
Thanks everyone! I'm really loaded with school work, so I don't have a lot of time right now. But long story short, airplane mode saves my battery like crazy. I started school with 86%, turned on airplane mode, and I'm at 79% right now! more later
Is it safe to say I fixed it?
3h screen over 2 days isnt bad right? Perhaps just a bit worse than what others are getting?
Sent from my SCH-I605 using xda app-developers app

[Q] Battery consumption while playing music + charging question

Might seem an odd question, but how much should I expect the battery to drain on the M8 while playing music?
Reason I ask is because I use my phone to help me sleep (brown noise) every night.
I use an app called "Chromadoze" which has been fine for me up until now.
My old Nexus 5, which I partially got rid of because of the battery life, would drain approx 25% in 8 hours using Chromadoze.
However, using the same app on the M8 drains 50% in 8 hours, which seems excessive for a phone touted as having far better battery life (and indeed it normally does under normal use).
Thinking it might be the app, I generated a (59 minute) brown noise file and converted to FLAC and copied to the phone, and set that to play on repeat. This still gave a drain equivalent to 50%. I thought the Snapdragon 801 was mean't to be very economical on the battery for music, but that ain't happening here. I even have the phone in flight mode (as always). The battery stats are telling me that indeed the "music" is to blame.
I'm disappointed with this as I could stream actual music from the cloud all night on the Nexus and get less drain than that.
The other thing thats proved to be disappointing is the time it takes to charge. I have a 2A blackberry charger that I used on my N5 that charged it in just over an hour, but this M8 takes well over 2 hours on the same charger. I realise it has a bigger battery, but its still only 10% difference and it should probably only take an extra 10 minutes or so, not double the time. Can I enable fast charging on this device, after all, the 801 again is supposed to be able to support it.
I am a tad disappointed with my move to the M8 so far because of these issues; it has better battery life overall but these issues make it significantly less useful to me.
I have such an issue with this phone, that whenever I use (so deep sleep isn't allowed) the 50% of the cpu time is always at 1036mhz, which is too much even for listening to music.
Check out by yourself, how the cpu is working, by installing cpu spy (additionally you can install wakelock detector).
If it's the cpu's fault then you may try to set custom settings (max speed) for cpu when the screen is off.
Sent from HTC One m8, or maybe not anymore
Thanks for the reply. I'll check those apps out you recommend.
My next move is to try again with the power saver turned on, and see how it goes, failing that as well, I could try without the boomsound activated, as I'm sure extra EQing will use CPU power.
I hope I can resolve it, as it will be disappointing if not, especially as I really liked the Nexus as a phone but thought this would be a nice upgrade in most respects (bar camera).
I personally think that this power saving mode just sucks, all it does is that it saves data, but not cpu, as it doesn't put apps to sleep, as stamina mode on xperia devices does.
Just make a quick test, turn on your app, then switch to cpu spy, reset the statistics (so you get statistics only while using your app) and turn off the screen and wait few minutes.
Sent from HTC One m8, or maybe not anymore
When your listening to music at night is your WiFi on and connected?
Ive noticed a strange bug on my device.
When my device is in stand by mode and wifi is connected my CPU usage never drops below 30%. I use SystemPanel Pro to check that.
Now with WiFi off and in stand by mode my CPU usage is between 3-7% with spikes to 10-15% every 20-30 minutes. To me that seems normal.
So if you do have WiFi on while its playing music for those 8 hours test it with WiFi off.
Hi, I would normally use Airplane mode, so no radios at all, unless I wanted to stream from cloud, I've not done that yet since I had the phone, though.
I've just done my first test with CPUspy as suggested, Over 35 minutes it spent 10 minutes @ 1,036 MHz and the remaining time (about 67%) @ 300 MHz.
I'm trying it again with the supposed "Power Saving" function on.
Result with Power Saving on
1,036 MHz - 7:32 - 17%
300 MHz - 24:29 - 57%
Deep sleep - 8:29 - 19%
BUT, i have a feeling the power save mode may have killed it off to go to sleep but I couldn't confirm as it hadn't occurred to me until I had messed about.
So it is slightly better provided it didn't kill the music.
All of this was with a program called "7digital" which appears to be built in. Going to try in PowerAmp next.
PowerAmp seems to look much more economical.
95% (just over an hour) spent @ 300 MHz with just 2:26 spent at 1036 MHz.
Tried my brown noise last night and it drained 34% in 6 hours. Still a pretty poor performance.
Looks like I'm going to have to try and find an alternative way to do this.
I do wonder if the Google play ROM would help as I never had a problem on the nexus 5.
Are those the statistics when your phone hasn't been used at all or was your program running at this time?
If the program wasn't running and you have such a cpu usage then it is probably some deep sleep issue (wakelock detector should help identifying the app responsible for that).
Anyway, just use some app to limit the cpu usage while the screen is off.
This phone likes to be stuck at 1036mhz and for example you could limit it to about 500mhz.
Ps. Power saving mode won't kill these apps, so don't worry.
Sent from HTC One m8, or maybe not anymore
mr.loverlover said:
Are those the statistics when your phone hasn't been used at all or was your program running at this time?
If the program wasn't running and you have such a cpu usage then it is probably some deep sleep issue (wakelock detector should help identifying the app responsible for that).
Anyway, just use some app to limit the cpu usage while the screen is off.
This phone likes to be stuck at 1036mhz and for example you could limit it to about 500mhz.
Ps. Power saving mode won't kill these apps, so don't worry.
Sent from HTC One m8, or maybe not anymore
Click to expand...
Click to collapse
Those statistics were with the music player 7digital running a brown noise file, but nothing else was being used on the phone.
Later I used PowerAmp which does give a more efficient performance, but sadly, still not good enough really considering my N5 was OK under the circumstances.
I find myself in two minds as to whether to try the GPE ROM anyway, as I don't find the phone as responsive as the N5 either... and maybe it will help with this issue too.
tameracingdriver said:
Those statistics were with the music player 7digital running a brown noise file, but nothing else was being used on the phone.
Later I used PowerAmp which does give a more efficient performance, but sadly, still not good enough really considering my N5 was OK under the circumstances.
I find myself in two minds as to whether to try the GPE ROM anyway, as I don't find the phone as responsive as the N5 either... and maybe it will help with this issue too.
Click to expand...
Click to collapse
GPE (and other non-stock based ROMs) will be much faster, that's damn sure, however I don't think this will solve the problem, as HTC one m8 has some weird issue with it's CPU.
I also don't know why it's using this 1036mhz continously, but you can't go below 300mhz if the device is working (like playing music).
Tty to limit your CPU at all the time (not only when the screen is off), that should also save some battery, however the battery life is still nothing considering the one from Xperia Z1.
In case anyone is interested, I did the conversion to GPE. Much better, now feels as fast or faster than my n5, but it now charges much faster and the battery life seems as good as before. Will try and test with some music at some point in the coming week to see if there is any improvement but I have my suspicion that it won't make much difference as I think it could possibly be the more powerful output and boomsound that increases battery drain... But.... We'll see.
Final post from me on this thread.
Its been several weeks now since I've had the GPE firmware installed on my HTC One M8, and I don't regret it one bit.
The battery life is at least as good, but I possibly think better, I'm generally always averaging 4+ SOT, whereas it would be just shy of that with the Sense ROM. The phone is also noticeably quicker at all times...
Finally though, the high battery usage during music IS cured. Using the Chromadoze app I talked about in post #1 results in 20% drain in 8 hours (compared to 50% on a Sense ROM). That is much better. I also no longer wake up to a warm / hot phone. And it charges faster.
So, in summary, the GPE ROM turns the M8 into the phone it should have been since day 1. I just wish it had the Sense camera, but the stock one is perfectly usable.

Battery last nothing, insane drain

I need help with the kernel auditor to get better battery life, i have installed last cm nighties nad last NJ2 band, i read that if u change the kernel you can get better battery stats, the battery drop really fast, with low brightness and wi-fi off, just LTE data, without GPS. I use the app called "Root Booster" and the Calibrate Battery but it's the same. I need help with the kernels.
Sorry for the bad english, is not my native lenguage
B
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
jason2678 said:
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
Click to expand...
Click to collapse
Explain me more about "gettin into deep sleep"
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
jason2678 said:
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
Click to expand...
Click to collapse
Perfect answer, that give me a lot of info i dont know about it, thanks a lot dude i will use the app and check what is the problem here!

Categories

Resources