[Q] Partial wakelock - Optimus One, P500, V General

I noticed that after charging my phone, after 2 hours it's still awake even if the screen is off (i got no apps running, all idle). Spare parts only shows "partial wakelock:android system" as 100% in the partial wake and running usage. Others are at 0.1%. I didn't do anything yet so I slept and after 8 hours of my sleep, I checked it and the phone is still awake, causing battery drain from 89% to 51%.
I don't have google maps/latitudes or any kind of google trash and syncing apps, what might be the problem? All wifi/gps/other connection is disabled too. Only solution I found is to restart the phone.. Any way how to detect that app in android system and kill it?
-i'm on 3 days with v18fkernel and tried reflashing, no use.

http://forum.xda-developers.com/showthread.php?t=1148099
Can u try this. It will help devs.
Sent from my LG-P500 using XDA Premium App

^Hm might test it later, i'm charging again to see if it causes the same trouble..

Same problem
I'm having the same problem on void #forever. Do you think it's the latest franco kernel (I have v18)? So you didn't have this problem in franco kernel v17 BFS?
Spare parts show the same app usage stats as well. My phone is awake 99% of the time!

^I'm about to try this today, seeing that the dev is active..My phone has been having random awake time's and yeah i got no apps running on bg/syncing off.
I'll post the findings after I try this

Deep Sleep Detective
I am trying it out as well. So far, I can't make sense of the log files.

antifaust said:
I am trying it out as well. So far, I can't make sense of the log files.
Click to expand...
Click to collapse
Well my log are clean too on Franco kernel if post that I get 98% dsp in 7 hours they wont believe me.
Sent from my LG-P500 using XDA Premium App

Isn't cpu_time_in_each_state and other debugging options in the latest franco kernel disabled?
I mean the dsdshutdown task will be going in a loop until it finds a cpu time in each state value and writes a log. (try testing the dsdshutdown task and it will not end)
Haven't tried the other tasks yet. not sure if that's the only task not working, i'm also not sure if it affects the other tasks

Weird
Weird. My phone suddenly starting going to sleep according to Spare Parts. It reflects on the Battery Usage stats in Settings as well. One long stretch of no sleep with huge battery drain (5% per hour or more, without Wi-fi, data, GPS, syncing) then now I've been on 37% for almost 1 1/2 hours now. Might try to roll back to v17 BFS until all this is figured out.

Kira.Lawliet said:
Isn't cpu_time_in_each_state and other debugging options in the latest franco kernel disabled?
I mean the dsdshutdown task will be going in a loop until it finds a cpu time in each state value and writes a log. (try testing the dsdshutdown task and it will not end)
Haven't tried the other tasks yet. not sure if that's the only task not working, i'm also not sure if it affects the other tasks
Click to expand...
Click to collapse
Its working but I m on cm7 stable. (Franco kernel by mik)
Sent from my LG-P500 using XDA Premium App

Resolved itself
Weird behavior. After being awake for several hours straight, my phone started sleeping "normally" and now with no data, no wi-fi, no GPS, I'm getting almost 48 hours out of my phone (void #forever, francokernel v18 BFS, overclocked to 480/710 SMARTASS). Oh well.
Anyway, it looks like Noejn halted development for void #forever. Thinking of trying mik_os CM7 port just so I can get support while waiting if Noejn will resume development on void...

Related

Brainstorming: how to completely disable DataTracker-FD and Fast Dormancy

Being fed up with the random wakelocks that Dialer produced on my Gingerbread P500, I spent a while searching for the cause. It turned out to be DataTracker-FD (found out using the amazing BetterBatteryStats app - http://www.cri.ch/sven/doku.php/computing/android/betterbatterystats ), which deals with Fast Dormancy (http://www.computerworld.com/s/article/9191759/Fast_dormancy_to_improve_smartphone_networking_and_battery_performance_ ).
Now, in theory, Fast Dormancy should be a great feature! But, if your network does not support it, DataTracker-FD will still drain a lot of battery through the wakelock. The SGSII secret code for deactivating it doesn't work on the P500, and neither does the nwk_info.db method. Luckily, you can deactivate (or change its timeout) through the LG hidden menu...
1. Dial 3845#*500#.
2. Go to Modem Setting > PDP Setting > [0] Set Fast Dormancy
3. Select your desired timeout (or "Disabled"). You should now be done! (will look at Battery Usage in a little bit, to see if a reboot/Dialer FC is also needed)
Optional step 4. If you still see no difference, set your desired timeout (or "Disabled") a few more times.
Hope it helps.
/* Edit: It doesn't seem to help, we might be back to square one. Does anyone have any idea on how to completely disable Fast Dormancy? We might need a dev to look at the source code of Dialer and make some modifications... Right now, if your phone stays awake after using Data, the only current workaround is FCing Dialer from Applications. */
EDIT 2: A SECOND TEST, USING THE ABOVE METHOD TO DISABLE FAST DORMANCY, YIELDS POSITIVE RESULTS! THE WAKELOCK IS NOT THERE ANYMORE, EVEN AFTER SEVERAL RECONNECTIONS TO HSDPA!
It needs way more testing though, I will reconnect to data and leave the phone idle (screen off), then see what happens, and I will reboot the phone to see if the setting persists.
EDIT 3: Yes, the setting persists, and the wakelock is still not running! The final test will be done after it has completely charged, because there still is a small possibility that the wakelock is so far not active just because the phone was charging.
Edit 4: Straight after unplugging the phone, DataTracker-FD started running, without being connected to HSDPA (I was in a phonecall). In 17 minutes (of mostly talking on the phone) it drained 1% of the battery - so, it should last for about 29 hours with the same usage. Now I have started HSDPA and left the phone idle for 10 minutes, to see how much it drains and how much it drains after I turn data off. It just might be that, while the phone is still awake, it doesn't drain a large amount of battery. If it actually still drains a lot, this tweak definitely only /seems/ to work while charging (maybe BetterBatteryStats was reporting false data or FD just doesnt' work when charging).
Edit 5: Here's a pleasant surprise. Right after connecting to HSDPA and putting the phone to sleep, the Awake bar in Battery Usage faded out. In 5 minutes of idling with data activated, the phone drained another 1% battery - not sure how well that is, since it amounts to 8 hours of data on a full charge, but it's better than 12 hours of idling with no data on a full charge. Currently repeating the test. Just got an email on Yahoo pushed, I'll get to see the influence on awake time of that as well.
Edit 6: After 10 minutes of idling with data ON, a bit over 1% of the battery is gone. This is a fantastic value, and the Awake bar is only dotted in this period of time. DataTracker-FD seems to be running a bit in the background during the data connection, but stopped once I turned it off. It might just be me, though, because aLogCat still can't find any entries for Fast Dormancy. Now leaving the phone idle with no data for a while to look at the evolution of Awake time.
Edit 7: After about 45 minutes of complete idling, the battery went down 2%. This would mean the battery would last for about a day and a half, which is meh, considering I OC'd the phone to 730 and don't really use a task manager.
The conclusion: YES, disabling Fast Dormancy does work using the above method, and it does help battery life!
Edit 8: After another unrelated reboot, DataTracker-FD is once again awake after using data, but this time it draws significantly less battery. The Battery Usage graph shows no difference between sleep times and awake-because-of-FD times.
Edit 9: During the night, the phone drained 30% battery, once again because of some random action of DataTracker-FD. This is still not a definite fix.
"Connection problem or invalid MMI code" when I dial that number..
I remember that long ago I dialed the number and everything was fine.
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
metalboy94 said:
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
Click to expand...
Click to collapse
When I just type it in dialer, nothing happens.
I see. It might not work on CM.
Updated the OP a couple of times, you might want to read it.
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
masteryx said:
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
Click to expand...
Click to collapse
I didn't have such problems on Froyo either. It MIGHT help, but as you can see from the numerous edits to the OP, it's not a clear win yet.
So it need to be disabled twice to stop working?
I've been looking for this service since using that Battery App but theres not much information of that in the web.
I'm not sure just how many times, but it took about 3-4 times for me until I was completely sure the wakelock stopped running and the phone went into deep sleep each time I locked it.
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
@metalboy94 I mailed LG regarding Fast Dormancy and the reply i got was that P500 does not support fast dormancy. My phone does not switch from H to 3G. I tried enabling it many times using secret menu but it does not work.
I asked him if GB ROM/Baseband supports fast dormancy, he replied saying GB hasn't been released for India
Roqu3 said:
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
Click to expand...
Click to collapse
There are? Thanks a bunch, gonna try those methods as well!
@atulalvenkar: Well, it still draws power from the battery, so at least they could have done something to the Dialer if it's not supported at all.
Edited the OP once again.
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
atulalvenkar said:
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
Click to expand...
Click to collapse
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
metalboy94 said:
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
Click to expand...
Click to collapse
Yeah my operator isn´t there also (I´m on a custom V20g ROM and I´m not from Romania) but i got the flex files from the Froyo stock so im going to try using that information to replace one of the V20g operators.
Also tried putting the Froyo ones on GB but get a lot of FC
Updated the OP again...
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
hey maybe let´s try this:
Code:
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,
have to put that on the build.prop then restart, the values must be changed to your carriers code, you can get that code from adb typing
Code:
adb shell
getprop gsm.operator.numeric
Then the system should show the number
tsuda said:
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
Click to expand...
Click to collapse
But did you see how many MBs the phone used? Cause if it's too much, people will definitely prefer just turning the phone off.
@Roqu3: I think I tried that before and it didn't seem to make a difference.
Worth a shot tho.
I'll try both of your methods if I still have the issue when I get my phone back from the service center.
Sent from a crappy rebranded Huawei using my hands

[Q] Device suddendly doesnt go to sleep

Well, I have my device running for 2days already with no reboot.
I charged it at night and have it running for 5 hours.
I did make 1:30 hours phone calls, a few internet and so, but its awake for the whole 5 hours which doesnt makes any sense..
The only reason I noticed it was how I lost 48% in 5hours.
I have almost nothing running in background, stock task manager shows only messages, gmail & Android market.
the "running" tab in Go launcher shows 250mb free out of 838mb total..
now after reboot its fine again, it goes to deep sleep (i checked with cpu spy)
but the problem is, how do i tell what was the cause for this mess?
BetterBatteryStats showed me that the phone was awake 100.0% of the time..
Check "partial wake locks" in the better battery stats app. Will give you info on what app or process time awake.
Sent from my GT-I9100 using xda premium
Well, in this menu there's nothing suspicious, the highest one takes 2-3mins with not too high count,
and the rest are for less than that & with low count as well.
So what else can I do to check it out?
If its not deep sleeping, what frequency is it stuck on when screen is off?
Is any data connection on, gps etc
There is also an app, "watchdog lite", may help alert you if there are amy rogue apps or processes (depending on config)
https://market.android.com/details?id=com.zomut.watchdoglite
What is your current system setup and config?
Have you made any system changes or installation of apps or themes since it was working fine?
If still no good our out of ideas, Maybe reflash the kernel and no setcpu profiles, UC, OC etc. .......
or at worst full wipe and reflash the lot.
Sent from my GT-I9100 using xda premium
I will try Watchdog.
I have everything the same as before, nothing changed much.
The only serious thing I did in the past week was freezing 1-2 things with TB.
There was nothing running in the background such as download or similar
The freq. used on screen off was 200MHz
What was frozen, and how about unfreeze and test?
Sent from my GT-I9100 using xda premium
It seems like it doesn't use deep sleep again. I didn't di anything serious since the last reboot.
The only things I froze are kies,system update...but I returned them back.
One thing I noticed but not sure if it was like that before or not, is that in the battery info, I have battery idle, operation time is as time from last charge and time without signal is 100%.
Also, when I look at the graph, awake and screen on are synchronized so im getting lost here.
Sent from my GT-I9100 using xda premium
My device is at 100% awake according to betterbatterystats but in watchdog I don't see anything suspicious.
What cab I do?
I removed most of the things I installed lately but it continues
Sent from my GT-I9100 using xda premium
As I said before;
Is any data connection on, gps etc ?
Also, do you have a strong signal, so its not constantly looking for a network or bouncing between 2g / 3g etc.
Put thephone into Flight Mode, so this eliminates connection to your network, wifi,.gps, etc.
If still no good our out of ideas, Maybe reflash the kernel and no setcpu profiles, UC, OC etc. .......
or at worst full wipe (factory data reset,.cache, dalvik etc in CWM and reflash the lot immediately after.
Don't forget to the md5 checksum to ensure your DLs are not corrupted and matching that of the Dev's original.
Sent from my GT-I9100 using xda premium
One member here found social hub was the cause of not deep sleeping. More than likely a config problem.
One of my suggestions was to put into flight mode and test.
Also you can use Droid Wall to block unwanted network connections.
http://forum.xda-developers.com/showthread.php?p=17960865
Sent from my GT-I9100 using xda premium
Well, unfortunately I dont know whats the cause so I dont know how I can configure droid wall.
After 6 hours in night, I had the device for 15 mins awake with no explenation. Partial wakelocks shows the highest activity is *sync* with 1m18s, count:6. The highest count is like...200~, not too critical.
The device was in deep sleep for 6hours but 200mhz for 17mins, which is the time I have no explenation for. In bettery mode you can see that 15~ mins where its awake but screen off.
I have no explenation for this but also dont know what caused it.
The good thing is that I lost only 2% over night, so I cant be too worried about it..
So I still don't know what caused it to be 100% awake.
meanwhile, I have no OC, OV/UV, no setcpu settings at all.
Im on Cognition 1.51 & Speedmod T40. I dont have the Samsung Apps installed at all.
Much better
Sent from my GT-I9100 using xda premium
At the moment, yes
however, the issue wasnt found & solved yet, so I need to keep looking for it.
dunno what else to do, sadly..
Full wipe and reflash does not take a great deal of time, a lot less than troubleshooting in most cases.
Just backup your user apps and data with titanium before hand, and md5 checksum match.
Sent from my GT-I9100 using xda premium
But if I backup all user apps and data, how will it help me ? Isn't one of them the cause for that ?
Sent from my GT-I9100 using xda premium
Just in case. It may be rom our kernel
You always have the option to download fresh from market and just restore the data.
Edit: If it happens again;
Personally, I'd backup, full wipe, flash. Reboot after first boot, and before / after applying themes and after restoring.
Sent from my GT-I9100 using xda premium

[Q] AudioOut_2 wakelock problem

as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
graffixnyc said:
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
Click to expand...
Click to collapse
Yes i have it enabled. in fact all the sound settings i have under settings-sound-system are all enabled. il try disabling them all. its just so weird why its having sound wakelocks even if the phone is not being used or the screen off. thanks for your reply.
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Same problem here, and I don't have the sound enabled.
Sent from my GT-I9300 using xda premium
Ausboy 2011 said:
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Click to expand...
Click to collapse
Im aware your using checkrom from your signature but its on jb..i am running omega 27.1 JB..on the nexus 7 forums some guys are having the same problem too..is it because we are all running JB?
Sent from my GT-I9300 using Tapatalk 2
same problem here using omega 27 with all system sounds off
Anyone track down a solution to this yet?
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
slaphead20 said:
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
Click to expand...
Click to collapse
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
NewAussiefromCanada said:
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
Click to expand...
Click to collapse
that's the thing.....I'm really not sure at all, something in my set up, something I froze with titanium, some sound setting, I really don't know,, I don't use haptic or touch sounds, so that might be linked, but beating in mind if I had tried one thing at a time, then used bbs and let it idle for two hours each time I tried something,I would be at it forever,
I'm dual booting slim and wanamlite, so even more complicated
Sorry to be so vague but I really can't pin it down!
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
puredesire said:
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
Click to expand...
Click to collapse
Did this work for anyone?
themadproducer said:
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
Click to expand...
Click to collapse
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Metalshadowx2 said:
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Click to expand...
Click to collapse
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
michalurban said:
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
Click to expand...
Click to collapse
Same problem here on my note 2... last night before sleep time i killed all apps by holding down the home button.BBS clearly showed audio_out2 as the one which has the partial wakelocks... sigh... no solution yet?
on a side note in sound settings im not using sound and vibration. just keyones. screen lock sound and haptic fb.
Same problem here
All touchsounds disabled and AudioOut_2 did not stop to drain my battery. Maybe it's time to switch to BlackBerry Z10.
for those who are having problems with phone not going to sleep, just go to settings - manage apps - and disable the Samsung TTS app (or freeze it with Titanium Backup). At least this fixed the problem here.
cya

Problem with S3 Battery

When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Start with Better Battery Stats and read the ten million battery posts on XDA .
jje
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
Mine drops about 1.5% every hour whenever it's on standby.
JJEgan said:
Start with Better Battery Stats and read the ten million battery posts on XDA .
jje
Click to expand...
Click to collapse
Better battery stats does not work.dont know why.and i made my own post cause i cannot find the solution of the problem on other posts.try to be more polite to your answers
have you tried downloading the xda version of the better battery stats? if not here it is
http://forum.xda-developers.com/showthread.php?t=1179809
Is your phone rooted? Like others said, try to install the xda-forum version of BBS but it's weird because I did install the one from GPlay.
One of the first lead is the WiFi? Is it always turned on? There's a bug with it. Go into the advanced WiFi settings and set it to 'only if activated' (I don't know the exact spell in English but it's something like that).
But you better have to dl BBS & check the wakelocks.
Sent from my Galaxy S3 with Omega ROM v27.2 / Phenomenal Extreme 4.0 kernel
which rom are you using?
that should be solved flashing another kernel, try it.
dont use a rom...my phone is just rooted
Deleted.
JJEgan said:
Deleted.
Click to expand...
Click to collapse
what?
Underclock when you're not using your phone.
That will save battery.
If ur using stock TW. Put on power saving mode
PM Me if u want to know more.
Try using an app called easy battery saver and only use the cable and plug that came with your galaxy s3 it works for me, today I had eight hours after charge and using internet with 3g nearly continuously.
You would get much more by leaving it on standby.
Also restrict your background data, turn off your automatic updates at play store andturn off WiFi while screen is asleep.
Follow all these for better battery.
Use any battery investigation apk/widget (I'd recommend battery monitor widget) and look what is causing the drain...
may I guess: cell standby or gpsd?
guys i remember you that the cell phone is on flight mode with wifi,gps and data turned off
and, if you have a soft which contains a bug - you'll have such processes running.
It is up to you to install any apk which will contain more detailed statistics what actually is consuming so much juice.
If you do not want - no one would force you.
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
I have the exactly same problem,30% drain overnight.That happens after updating to 4.1.1 JellyBean.With ICS never happened.
Go into the battery page, click on the graph and then post a screenshot of the detailed graph here. It is usually an app or process not letting the phone go into standby. Happened to me when I had my phone on ICS out of the box. I fixed that all up through the individual app settings and all was sweet. Then when I went from ICS to JB, the issue came up again and I had to go through the apps again to change the settings back. It seems that by updating from ICS to JB, certain settings get set back to default, which then does not allow the phone to go into standby.
Culprits that I have found are:
Facebook - set to manual refresh interval
Weather (or any weather widget) - manual refresh interval
Google play store - Turn off Google AdMob Ads
Any form of newsreader (I was using Pulse) - Turn off notification when there are new stories
Wifi advanced settings - Set Keep Wifi on during sleep to "Always"
Samsung account - Turn off sync
Samsung app store - Turn off Update Notification, turn off push notification, turn off ad preferences.
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
Maybe some apps running in background if you are using *viber* delete it
It makes proximity sensor always on.
Try delete apps like that
Thanks
Sent from my GT-I9300 using xda app-developers app
Guys please keep in mind that keeping the stock os without any custom kernel might be not as effective than using an adequate custom rom...
In addition remember, cooler temperatures cause ur battery to lose its charge faster...
So if ur phone is placed on the window shelf and its getting cold during the night it might cause ur battery to drop fast..
I made this observation with my sgs plus....
Hope i helped.

[Q] Battery drain and heat.

Hey,
First of all, i'm on newest Archidroid with boeffla kernel 5.4 on ultrapowersave preset.
And the thing is, when im at home, with wifi,data,sync on + i use 2-3 apps, my battery drain on BBS is really small like 1% per h.
But when i go out to work, where i don't have wifi access, my s3 start to melt battery pretty fast compared to previous version of rom. (~5% per h)
with no usage at all.
PS. i tried to disable FD and finally i left FD enabled, beacuse "in theory" my provider support that. (But honestly, i havent noticed any difference between Enabled or disabled FD, it was transfering data every few sec). I've got greenified all apps that i don't use. i checked BBS log, but i've no idea what is eating that much.
That BBS log starts before i go back to home from work, until now.
I dnt even get that much
Sent from my GT-I9300 using XDA Free mobile app

Categories

Resources