Deep sleep issue - Galaxy S II Q&A, Help & Troubleshooting

Hi all, am running stock ROM 4.0.3 (not rooted), lately my device is not going into deep sleep.. I have disabled all apps that i could disable .. Unmounted SD card.. And removed most zip files ... I have done everything that could cause this issue but no luck...
Im not planning to root my device therefore i cant use BetterBattertStatus which in any will not understand its info
Is it known issue?
How could i solve it ?
Please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9100 using Tapatalk 2

Why don't you want to root your device, especially when you know it could possibly fix your problem.
You can try to use bbs without root, you just can't see a couple of categories. I think it would still be helpful though
Sent from my GT-I9100 using xda premium

kilometers4 said:
Why don't you want to root your device, especially when you know it could possibly fix your problem.
You can try to use bbs without root, you just can't see a couple of categories. I think it would still be helpful though
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Because this issue is not material compared to issues could be caused due to root !
Am running firmware 4.0.3 and wipping via CWM would cause hard brick ... Anyways am having very important data and dont want to lose especially that Im traveling to another country and dont have enough time to setup the devise again and again
Re bbs, its in Chinese
Deep sleep used to work perfectly .. I seriously tried everything that could solve the issue without luck
Sent from my GT-I9100 using Tapatalk 2

Jordanyme said:
Because this issue is not material compared to issues could be caused due to root !
Am running firmware 4.0.3 and wipping via CWM would cause hard brick ... Anyways am having very important data and dont want to lose especially that Im traveling to another country and dont have enough time to setup the devise again and again
Re bbs, its in Chinese
Deep sleep used to work perfectly .. I seriously tried everything that could solve the issue without luck
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It's 4.0.4 that has the brick possibility, not 4.0.3.
4.0.3 is safe.

Jordanyme said:
Because this issue is not material compared to issues could be caused due to root !
Am running firmware 4.0.3 and wipping via CWM would cause hard brick ... Anyways am having very important data and dont want to lose especially that Im traveling to another country and dont have enough time to setup the devise again and again
Re bbs, its in Chinese
Deep sleep used to work perfectly .. I seriously tried everything that could solve the issue without luck
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Bbs is not in Chinese.. Search xda app section for the apk. A rogue app might be causing it. Have you installed any apps recently before the problem started?
Sent from my Nexus 7 using xda premium

kilometers4 said:
Bbs is not in Chinese.. Search xda app section for the apk. A rogue app might be causing it. Have you installed any apps recently before the problem started?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I actually think he's saying it's in Chinese because he can't understand what it's telling him.

ctomgee said:
I actually think he's saying it's in Chinese because he can't understand what it's telling him.
Click to expand...
Click to collapse
And ok, didn't even think of that.
---
If you want to post a bbs dump I can tell you what's going on.
Sent from my Nexus 7 using xda premium

kilometers4 said:
Bbs is not in Chinese.. Search xda app section for the apk. A rogue app might be causing it. Have you installed any apps recently before the problem started?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The following message shown when i try to run the app
I found BetterBattertStatus and download the app.. But wonder which categuery i have to look at
Your help is highly appreciated
Sent from my GT-I9100 using Tapatalk 2

Jordanyme said:
The following message shown when i try to run the app
View attachment 1500876
Click to expand...
Click to collapse
LOL. That IS Chinese. But that's not the BBS he was talking about.
Jordanyme said:
I found BetterBattertStatus and download the app.. But wonder which categuery i have to look at
View attachment 1500886
Your help is highly appreciated
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
This is the BBS he was talking about. In that app, press menu > More > Dump to file. Post here the file that is generated.

ctomgee said:
LOL. That IS Chinese. But that's not the BBS he was talking about.
This is the BBS he was talking about. In that app, press menu > More > Dump to file. Post here the file that is generated.
Click to expand...
Click to collapse
Ahaaaa BBS belongs to same app that i just found
This is the generated log
===================
General Information
===================
BetterBatteryStats version: 1.9.2.1
Creation Date: 2012-11-22 00:40:55
Statistic Type: (3) Since Unplugged
Since 5 h 1 m 59 s
VERSION.RELEASE: 4.0.3
BRAND: samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
OS.VERSION: 3.0.15-I9100JPLPF-CL644992
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/JPLPF:user/release-keys
ID: IML74K
TAGS: release-keys
USER: dpi
PRODUCT: GT-I9100
RADIO: I9100XXLPX
Rooted: false
============
Battery Info
============
Level lost [%]: 45
Voltage lost [mV]: 444
===========
Other Usage
===========
Awake (): 5 h 1 m 59 s (18119 s) Ratio: 100.0%
Wifi On (): 5 h 1 m 49 s (18109 s) Ratio: 99.9%
Wifi Running (): 5 h 1 m 46 s (18106 s) Ratio: 99.9%
No Data Connection (): 4 h 59 m 40 s (17980 s) Ratio: 99.2%
No or Unknown Signal (): 4 h 59 m 40 s (17980 s) Ratio: 99.2%
Screen On (): 1 h 58 m 49 s (7129 s) Ratio: 39.3%
Phone On (): 1 h 2 m 16 s (3736 s) Ratio: 20.6%
Moderate Signal (): 21 s (21 s) Ratio: 0.1%
Poor Signal (): 2 s (2 s) Ratio: 0.0%
Good Signal (): (0 s) Ratio: 0.0%
=========
Wakelocks
=========
AudioOut_1 (1013): 42 m 32 s (2552 s) Count:282 14.1%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 4 m 53 s (293 s) Count:7 1.6%
AudioIn_742 (1013): 1 m 32 s (92 s) Count:285 0.5%
AudioIn_790 (1013): 1 m 30 s (90 s) Count:29 0.5%
AudioIn_748 (1013): 1 m 30 s (90 s) Count:13 0.5%
AudioIn_784 (1013): 1 m 30 s (90 s) Count:18 0.5%
AudioIn_766 (1013): 1 m 30 s (90 s) Count:15 0.5%
AudioIn_754 (1013): 1 m 30 s (90 s) Count:24 0.5%
AudioIn_778 (1013): 1 m 30 s (90 s) Count:3 0.5%
AudioIn_772 (1013): 1 m 30 s (90 s) Count:26 0.5%
AudioIn_760 (1013): 1 m 29 s (89 s) Count:10 0.5%
ActivityManager-Launch (Android System): 1 m 12 s (72 s) Count:443 0.4%
AlarmManager (Android System): 31 s (31 s) Count:1045 0.2%
sendinactive (com.whatsapp.WhatsApp): 23 s (23 s) Count:9 0.1%
RILJ (Phone): 22 s (22 s) Count:148 0.1%
sleep_broadcast (Android System): 11 s (11 s) Count:517 0.1%
PhoneWindowManager.mBroadcastWakeLock (Android System): 9 s (9 s) Count:454 0.1%
[email protected]/android_talk729c004e78d9 (Google Services): 9 s (9 s) Count:258 0.1%
DownloadManager (Media): 7 s (7 s) Count:1 0.0%
AudioIn_796 (1013): 6 s (6 s) Count:6 0.0%
ConnectivityService (Android System): 6 s (6 s) Count:1048 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 6 s (6 s) Count:237 0.0%
NetworkStats (Android System): 5 s (5 s) Count:82 0.0%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 4 s (4 s) Count:2 0.0%
show keyguard (Android System): 4 s (4 s) Count:19 0.0%
fullsync (com.whatsapp.WhatsApp): 3 s (3 s) Count:10 0.0%
*backup* (Android System): 3 s (3 s) Count:537 0.0%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 2 s (2 s) Count:2 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:221 0.0%
WifiStateMachine (Android System): 2 s (2 s) Count:541 0.0%
GSM (Phone): 1 s (1 s) Count:1 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:529 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:252 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:10 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1103 0.0%
================
Kernel Wakelocks
================
"fuel_alerted" (): 3 h 25 m 29 s (12329 s) Cntc/wc/ec)0/0/0 59.8%
"deleted_wake_locks" (): 10 m 53 s (653 s) Cntc/wc/ec)39868/0/776 3.1%
"wlan_rx_wake" (): 6 m 36 s (396 s) Cntc/wc/ec)792/0/791 1.9%
"PowerManagerService" (): 2 m 19 s (139 s) Cntc/wc/ec)1121/0/0 0.7%
"AudioOutLock" (): 1 m 6 s (66 s) Cntc/wc/ec)316/0/0 0.3%
"multipdp" (): 44 s (44 s) Cntc/wc/ec)6/0/6 0.2%
"secril_fd-interface" (): 25 s (25 s) Cntc/wc/ec)15/0/0 0.1%
"l2_hsic" (): 20 s (20 s) Cntc/wc/ec)699/0/0 0.1%
"umts_ipc0" (): 16 s (16 s) Cntc/wc/ec)626/0/626 0.1%
"rpm_hsic" (): 12 s (12 s) Cntc/wc/ec)698/0/0 0.1%
"radio-interface" (): 11 s (11 s) Cntc/wc/ec)87/0/0 0.1%
"pno_wake_lock" (): 9 s (9 s) Cntc/wc/ec)1/0/1 0.0%
"power-supply" (): 9 s (9 s) Cntc/wc/ec)514/0/0 0.0%
"alarm" (): 5 s (5 s) Cntc/wc/ec)584/0/0 0.0%
"wlan_wake" (): 5 s (5 s) Cntc/wc/ec)182408/0/0 0.0%
"prx_wake_lock" (): 2 s (2 s) Cntc/wc/ec)7/0/7 0.0%
"sec-battery-monitor" (): (0 s) Cntc/wc/ec)514/0/0 0.0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)265/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)66772/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)1668/0/0 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)24/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.2 GHz (): 12 m 36 s 3.7%
1 GHz (): 1 m 1 s 0.3%
800 MHz (): 21 m 23 s 6.2%
500 MHz (): 49 m 52 s 14.5%
200 MHz (): 4 h 18 m 38 s 75.3%
Deep Sleep (): 0.0%
==================
Reference overview
==================
Custom: Reference custom_ref created 2012-11-21 18:52:30 (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since charged: Reference since_unplugged_ref created 2012-11-21 18:57:22 (Wl: 0 elements; KWl: 9elements; NetS: 0 elements; Alrm: 1 elements; Proc: null; Oth: 6 elements; CPU: 6 elements)
Since screen off: Reference since_screen_off created 2012-11-21 18:52:30 (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since unplugged: Reference since_unplugged_ref created 2012-11-21 18:57:22 (Wl: 0 elements; KWl: 9elements; NetS: 0 elements; Alrm: 1 elements; Proc: null; Oth: 6 elements; CPU: 6 elements)
Click to expand...
Click to collapse
Sent from my GT-I9100 using Tapatalk 2

Power off your phone. Remove external SDcard and battery. Wait few minutes. Put battery in and power on phone (without sd). After some time when all startup process will end their work reset CPUSpy history and check deep idle state. If it is ok than power off gs and mount your sd card.
Sometimes it could be media scanner problem. Sometimes dirty battery or USB connectors. You can try to clean them wit dry and clean toothbrush.

SirKunon said:
Power off your phone. Remove external SDcard and battery. Wait few minutes. Put battery in and power on phone (without sd). After some time when all startup process will end their work reset CPUSpy history and check deep idle state. If it is ok than power off gs and mount your sd card.
Sometimes it could be media scanner problem. Sometimes dirty battery or USB connectors. You can try to clean them wit dry and clean toothbrush.
Click to expand...
Click to collapse
Yeh ... Removing SD card seems help
I have installed app called Picart .. Its installed on SD card by default and i think it keeps my device awake
Will try removing it
Really thanks mate
Sent from my GT-I9100 using Tapatalk 2

same issue on JB..
hi.. can anyone help? i was on jelly bean with philz kernel 4.35 and i saw an update to 4.64 and flashed it using recovery. since then my phone hasn't been going into deep sleep except for a few minutes just after boot. i have tried resetting and reflashing to rom and kernel [with clearing dalvik cache and fix permissions]. nothing has helped. tried freezing some apps like samsung push service and maps, didn't help either.
can anyone help me with this?

ss03101991 said:
hi.. can anyone help? i was on jelly bean with philz kernel 4.35 and i saw an update to 4.64 and flashed it using recovery. since then my phone hasn't been going into deep sleep except for a few minutes just after boot. i have tried resetting and reflashing to rom and kernel [with clearing dalvik cache and fix permissions]. nothing has helped. tried freezing some apps like samsung push service and maps, didn't help either.
can anyone help me with this?
Click to expand...
Click to collapse
Post you BBS screens to find out what's keeping it awake.

here..
gastonw said:
Post you BBS screens to find out what's keeping it awake.
Click to expand...
Click to collapse
it says audioout_2 has been keeping my device awake. but i haven't been using anything. tried removing the sd card too. no sounds at all. no audio, no video, no games nothing open in the background, no key press sounds or notifs.. everything set to silent.. please advise..
also, it's not always that this happens. like i turned my screen on to take these screen shots.. no deep sleep.. i turned it off after this.. 90% plus deep sleep.. again after that no deep sleep.. not alternating.. just random.. formatted.. tried 2/3 kernels.. nothing helps..

ss03101991 said:
it says audioout_2 has been keeping my device awake. but i haven't been using anything. tried removing the sd card too. no sounds at all. no audio, no video, no games nothing open in the background, no key press sounds or notifs.. everything set to silent.. please advise..
also, it's not always that this happens. like i turned my screen on to take these screen shots.. no deep sleep.. i turned it off after this.. 90% plus deep sleep.. again after that no deep sleep.. not alternating.. just random.. formatted.. tried 2/3 kernels.. nothing helps..
Click to expand...
Click to collapse
Disable juice defender, it keeps your device awake.
And disable fast dormacy.
Power saving mode on right?
Sent from the little guy

gastonw said:
Disable juice defender, it keeps your device awake.
And disable fast dormacy.
Power saving mode on right?
Sent from the little guy
Click to expand...
Click to collapse
uninstalled JD. power saving is on, yes. and i don't use mobile network. the tests were all on flight mode. trying a different stock JB rom. or might just go back to ICS.

ss03101991 said:
uninstalled JD. power saving is on, yes. and i don't use mobile network. the tests were all on flight mode. trying a different stock JB rom. or might just go back to ICS.
Click to expand...
Click to collapse
And how are your stats now?
Sent from the little guy

gastonw said:
And how are your stats now?
Sent from the little guy
Click to expand...
Click to collapse
just about the same. i was thinking of a new app/update i had installed recently. i think i got it. it was viber. i uninstalled it and rebooted. no probs since then. i updated it a few days ago. if i use viber my phone doesn't sleep till i reboot (that too if viber is forced stop at boot) so maybe some problem with the app.
phone's fine now. i'll keep you posted if something comes up.

Check viber settings.
Sent from the little guy

Related

[Q] short battery

I'm having problems with my sgs 2 battery life.. I recently installed litening rom and did a battery calibration and usually my phone lasts for atleast a day and a half, but suddenly my battery began to have a short life, causing it to end after about 9 hours.. any ideas to why?
Thank you!
Post up your battery usage screenshot, and download betterbatterystats for wakelocks, sounds as though you have wakelocks without logs we can't tell.
Sent from my GT-I9100 using Tapatalk
i have battery monitor, last night it lasted about 15 hours because i put it in battery saving mode (phone runs really slow and brightness up to 0).
how do i take photos? when i know i'll be more then happy to post
thanks!
clashed said:
i have battery monitor, last night it lasted about 15 hours because i put it in battery saving mode (phone runs really slow and brightness up to 0).
how do i take photos? when i know i'll be more then happy to post
thanks!
Click to expand...
Click to collapse
To take screenshots just push simultaneously the Power and Home button.
You will find the screenshots on your internal sd card in ScreenCaptures folder.
wakelocs log is very very long.. which part should I post?
clashed said:
wakelocs log is very very long.. which part should I post?
Click to expand...
Click to collapse
Go to pastebin website paste into that and post link.
Sent from my GT-I9100 using Tapatalk
I know I'm really problematic, but how can i copy and paste wakelocs log, i can't copy the text i can see it in pictures.
if that's the case which part of to log should i upload, or should i upload all of it?
clashed said:
I know I'm really problematic, but how can i copy and paste wakelocs log, i can't copy the text i can see it in pictures.
if that's the case which part of to log should i upload, or should i upload all of it?
Click to expand...
Click to collapse
Within app, press the menu button, select actions then Dump to File. It'll create a log file on the sdcard, copy and paste into pastebin or upload the log file.
I found 2 files after I did the file to dump, 1 is battery history.txt: http://www.mediafire.com/?71aqcz2kzl3xeh1
and the other is BetterBatteryStats.txt:
http://www.mediafire.com/?0m6ilysr06ucey5
Many thanks for helping! your help is much appreciated!
*network-location* (com.androidapps.widget.weather2.Weather & Toggle Widgets): 30 m 36 s (1836 s) Count:308 5.4%
ActivityManager-Launch (Android System): 3 m 35 s (215 s) Count:610 0.6%
led_lck (com.devuni.flashlight.Flashlight): 1 m 47 s (107 s) Count:10 0.3%
GSM (Dialer): 1 m 35 s (95 s) Count:34 0.3%
swift CPU (com.samsung.swift.app.kiesair.Kies air): 1 m 20 s (80 s) Count:2 0.2%
AlarmManager (Android System): 1 m 6 s (66 s) Count:3139 0.2%
*sync* (Google Services): 60 s (60 s) Count:12 0.2%
StartingDockService (Android System): 40 s (40 s) Count:1098 0.1%
SMSDispatcher (Dialer): 39 s (39 s) Count:22 0.1%
RILJ (Dialer): 33 s (33 s) Count:1621 0.1%
*network-location* (com.bumptech.bumpga.Bump): 30 s (30 s) Count:10 0.1%
sleep_broadcast (Android System): 29 s (29 s) Count:1057 0.1%
StartingAlertService (com.android.mms.Messaging): 23 s (23 s) Count:36 0.1%
GTALK_CONN (Google Services): 17 s (17 s) Count:607 0.1%
show keyguard (Android System): 16 s (16 s) Count:45 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 10 s (10 s) Count:5 0.0%
*backup* (Android System): 9 s (9 s) Count:1118 0.0%
SCREEN_FROZEN (Android System): 8 s (8 s) Count:1090 0.0%
ScoSocket (Dialer): 7 s (7 s) Count:10 0.0%
*sync* (com.google.android.gm.Gmail): 7 s (7 s) Count:1 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:456 0.0%
keyguardWakeAndHandOff (Android System): 6 s (6 s) Count:1195 0.0%
GTALK_ASYNC_CONN (Google Services): 6 s (6 s) Count:3 0.0%
fullsync (com.whatsapp.WhatsApp): 5 s (5 s) Count:2 0.0%
*network-location* (Google Services): 4 s (4 s) Count:436 0.0%
MediaScannerService (Media): 4 s (4 s) Count:2 0.0%
*network-location-cell-update* (Google Services): 4 s (4 s) Count:424 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:300 0.0%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:3244 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 2 s (2 s) Count:2 0.0%
Proximity Partial (Android System): 1 s (1 s) Count:50 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:434 0.0%
WifiService (Android System): 1 s (1 s) Count:1108 0.0%
Browser (com.android.browser.Internet): 1 s (1 s) Count:4 0.0%
Highlighted in bold, main culprit your weather widget, kept awake for 30mins. Either remove those or decrease intervals. Other than that it's not that bad to be honest.
P.S you should update to a newer 2.3.5 rom, improved to 2.3.4, better battery life using another kernel as well like Speedmod.
Same here from past fews days my battery only lasts for 8 to 9 hours
Sent from my GT-I9100 using xda premium
Alright, thank you very much! one last question, how can i decrease these intervals as you said?
and btw, if I flash a new kernal do i need to perform a full wipe?
When I used Lightning I had the same battery problem, it only lasted for 9hrs MAX with normal use.
Installed this one and now it gives me 26hrs the most ! But still a huge improvement over the old F/W.
http://forum.xda-developers.com/showthread.php?t=1124396
clashed said:
Alright, thank you very much! one last question, how can i decrease these intervals as you said?
and btw, if I flash a new kernal do i need to perform a full wipe?
Click to expand...
Click to collapse
Kernel? No. Wipe both the cache.
Decreasing the intervals? Reduce the refresh time of the weather widget. If you don't use kies air. You could freeze it with TB.

Smart Screen Off LITE (helps ics screen wake)

Ok pretty cool app I found, it really helps your battery if you are running any of the ICS roms/kernels. What it does is use your light sensor to see if your screen should be on or not. So if you put your phone face down on your desk, or you put it in your pocket, your screen automatically turns off without you pressing the button, and it stays off until you take it out.
Good idea, but I'd use it in conjunction with Better Battery Stats to see if it will hold a wakelock.. sounds like it might
I am testing this as we speak, only had it for 1/2 hour but when i look in battery stats there is no longer any indication of screen on and awake. Need to look inti the better batt stats app more though.
Code:
===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-03-23 10:42:17
Statistic Type: (3)
Since 1 h 57 m 12 s
VERSION.RELEASE: 4.0.3
BRAND: Samsung
DEVICE: galaxys2
MANUFACTURER: samsung
MODEL: SGH-I777
RADIO: unknown
BOOTLOADER: unknown
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys
HARDWARE: smdk4210
ID: IML74K
Rooted: true
===========
Other Usage
===========
Wifi On (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Wifi Running (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Bluetooth On (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Awake (): 29 m 51 s (1791 s) Ratio: 25.5%
Screen On (): 16 m 40 s (1000 s) Ratio: 14.2%
=========
Wakelocks
=========
AudioOut_1 (1013): 2 m 54 s (174 s) Count:49 9.7%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 1 m 18 s (78 s) Count:14 4.4%
SyncLoopWakeLock (Android System): 59 s (59 s) Count:688 3.3%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 30 s (30 s) Count:17 1.7%
[email protected]/android_talk9bec91c984d3 (Google Services): 28 s (28 s) Count:15 1.6%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 22 s (22 s) Count:213 1.3%
sleep_broadcast (Android System): 14 s (14 s) Count:216 0.8%
ActivityManager-Launch (Android System): 10 s (10 s) Count:84 0.6%
RILJ (Phone): 9 s (9 s) Count:261 0.5%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 9 s (9 s) Count:4 0.5%
*sync*_com.twitter.android.provider.TwitterProvider_Account {name=HaruSoul, type=com.twitter.android.auth.login} (com.twitter.android.Twitter): 7 s (7 s) Count:2 0.4%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:5 0.4%
AlarmManager (Android System): 7 s (7 s) Count:583 0.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 6 s (6 s) Count:7 0.3%
Proximity Partial (Android System): 5 s (5 s) Count:15 0.3%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 s (4 s) Count:1 0.3%
GTALK_CONN (Google Services): 3 s (3 s) Count:203 0.2%
ConnectivityService (Android System): 3 s (3 s) Count:585 0.2%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:640 0.2%
AudioOut_1281 (1013): 3 s (3 s) Count:3 0.2%
NetworkStats (Android System): 2 s (2 s) Count:52 0.1%
DownloadManager (Media): 2 s (2 s) Count:2 0.1%
*sync*_com.google.android.apps.docs_Account {[email protected], type=com.google} (com.google.android.apps.docs.Docs): 1 s (1 s) Count:2 0.1%
DocsSyncAdapter (com.google.android.apps.docs.Docs): 1 s (1 s) Count:3 0.1%
GpsLocationProvider (Android System): 1 s (1 s) Count:95 0.1%
*vibrator* (Android System): 1 s (1 s) Count:248 0.1%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
Not sure where I should be looking, or if 2 hours is a long enough time table to test.
Was it face down or in your pocket the entire two hours? Or did you use it for 16 min?
twiggums said:
Was it face down or in your pocket the entire two hours? Or did you use it for 16 min?
Click to expand...
Click to collapse
Used it for 16. I can do a fresh test tonight without using it and post it tomorrow.
I just tested this for 15mins, and CPUspy reports 90% deep sleep. This may be totally valid.
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Ashhong said:
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Click to expand...
Click to collapse
Carry a mini flashlight with you and point it at your device.
Ashhong said:
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Click to expand...
Click to collapse
Oh...

Tips for wifi management?

I'm suffering from poor battery life on my S3 - worse than my S2 with the same set of user-installed apps. I suspect that it's because I tend to leave wifi switched on. Could someone provide guidance on a power-efficient way of managing wifi?
I want to receive notifications of incoming emails, and would like this to be done via wifi wherever possible. I have wifi both at home and at work. If I'm away from home and work ideally I don't want the phone to hunt for wifi signals.
Can anyone recommend the best way of achieving the above in the most power-efficient way?
You can try tasker or llama to manage a lot ou things in various conditions... Like Wifi off when Screen off... Etc....
Envoyé depuis mon GT-I9300 avec Tapatalk
Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.
Past SG models WiFi has been found to drain battery when searching for networks .
If i turn my router off then SGS is searching for networks .
jje
That's true.
However it's the same for all wiieless data connectionsz sensing across frequencies costs more battery than keeping a connection alive.
I'd recommend JuiceDefender Beta since it can manage all data connections and additronally automatically toggle 3g/2g upon requirement.
The app's cost of a few bucks is in no relation to the worth of a longer-living battery on your 600USD phone
Sent from my GT-I9300 using xda premium
d4fseeker said:
Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.
Click to expand...
Click to collapse
Here's the output from BetterBatteryStats, for a period of about 3 hours after unplugging the phone. During this time it was turned on very briefly a couple of times to check notifications, and was within 10 feet of the wifi router.
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-07-06 12:43:46
Statistic Type: (3) Since Unplugged
Since 3 h 19 m 46 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
BOOTLOADER: I9300XXALE8
FINGERPRINT: samsung/m0xx/m0:4.0.4/IMM76D/I9300XXALE8:user/release-keys
HARDWARE: smdk4x12
ID: IMM76D
TAGS: release-keys
USER: se.infra
PRODUCT: m0xx
RADIO: I9300NELE4
Rooted: true
===========
Other Usage
===========
Wifi On (): 3 h 19 m 46 s (11986 s) Ratio: 100.0%
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
Deep Sleep (): 2 h 54 m 59 s (10499 s) Ratio: 87.6%
Awake (): 24 m 47 s (1487 s) Ratio: 12.4%
Wifi Running (): 16 m 8 s (968 s) Ratio: 8.1%
No Data Connection (): 15 m 14 s (914 s) Ratio: 7.6%
No or Unknown Signal (): 15 m 14 s (914 s) Ratio: 7.6%
Screen On (): 15 s (15 s) Ratio: 0.1%
=========
Wakelocks
=========
*sync*_gmail-ls_Account {name=EM, type=com.google} (com.google.android.gm.Gmail): 4 m 48 s (288 s) Count:47 2.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 53 s (53 s) Count:79 0.4%
SyncLoopWakeLock (Android System): 52 s (52 s) Count:485 0.4%
*backup* (Android System): 27 s (27 s) Count:84 0.2%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 26 s (26 s) Count:10 0.2%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 23 s (23 s) Count:3 0.2%
FacebookService (com.facebook.katana.Facebook): 23 s (23 s) Count:6 0.2%
AlarmManager (Android System): 17 s (17 s) Count:291 0.1%
sleep_broadcast (Android System): 8 s (8 s) Count:80 0.1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 8 s (8 s) Count:9 0.1%
*sync*_com.android.contacts_Account {name=EM, type=com.google} (Google Services): 7 s (7 s) Count:62 0.1%
GTALK_CONN (Google Services): 6 s (6 s) Count:221 0.1%
DHCP (Android System): 5 s (5 s) Count:81 0.0%
DownloadManager (Media): 4 s (4 s) Count:2 0.0%
GOOGLE_C2DM (Google Services): 4 s (4 s) Count:49 0.0%
NetworkLocationBurstCollector (com.google.android.apps.maps.Maps): 4 s (4 s) Count:11 0.0%
My Tag (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 4 s (4 s) Count:49 0.0%
RILS (com.sec.phone.SecPhone): 4 s (4 s) Count:1 0.0%
EM/android_talk14c111ed2ffe (Google Services): 3 s (3 s) Count:1 0.0%
Push Thread:6866 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:45 0.0%
Push Thread:6793 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:55 0.0%
Push Thread:6831 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:44 0.0%
AudioOut_1 (1013): 2 s (2 s) Count:1 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:229 0.0%
NetworkStats (Android System): 1 s (1 s) Count:23 0.0%
Push Thread:6865 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:50 0.0%
Push Service:1 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:18 0.0%
Push Thread:6669 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:1 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:94 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:76 0.0%
================
Kernel Wakelocks
================
"multipdp" (): 18 m 3 s (1083 s) Cntc/wc/ec)97/0/96 9.0%
"secril_fd-interface" (): 9 m 32 s (572 s) Cntc/wc/ec)153/0/0 4.8%
"PowerManagerService" (): 8 m 37 s (517 s) Cntc/wc/ec)370/0/0 4.3%
"l2_hsic" (): 5 m 13 s (313 s) Cntc/wc/ec)830/75/829 2.6%
"battery-monitor" (): 3 m 7 s (187 s) Cntc/wc/ec)186/0/187 1.6%
"alarm_rtc" (): 1 m 42 s (102 s) Cntc/wc/ec)178/0/65 0.9%
"wlan_rx_wake" (): 1 m 3 s (63 s) Cntc/wc/ec)50/0/49 0.5%
"alarm" (): 46 s (46 s) Cntc/wc/ec)213/0/0 0.4%
"rpm_hsic" (): 46 s (46 s) Cntc/wc/ec)638/0/0 0.4%
"GPS" (): 43 s (43 s) Cntc/wc/ec)1/0/0 0.4%
"wlan_wake" (): 16 s (16 s) Cntc/wc/ec)149802/110/0 0.1%
"tx_hsic" (): 11 s (11 s) Cntc/wc/ec)1021/0/0 0.1%
"umts_rfs0" (): 8 s (8 s) Cntc/wc/ec)3/0/3 0.1%
"AudioOutLock" (): 4 s (4 s) Cntc/wc/ec)1/0/0 0.0%
"umts_ipc0" (): 3 s (3 s) Cntc/wc/ec)10/0/10 0.0%
"vib_present" (): 3 s (3 s) Cntc/wc/ec)2/0/0 0.0%
"radio-interface" (): 2 s (2 s) Cntc/wc/ec)4/0/0 0.0%
"event1-2108" (): 1 s (1 s) Cntc/wc/ec)2/0/0 0.0%
"efsd-interface" (): (0 s) Cntc/wc/ec)6/0/0 0.0%
"event10-2108" (): (0 s) Cntc/wc/ec)1848/0/0 0.0%
"event4-2108" (): (0 s) Cntc/wc/ec)865/0/0 0.0%
"secril_rfs-interface" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"event5-2108" (): (0 s) Cntc/wc/ec)604/0/0 0.0%
"sync_system" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)216/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)22/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)239/0/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%
Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)
d4fseeker said:
Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)
Click to expand...
Click to collapse
Presumably it's the wifi signal that's weak, not the GSM signal?
I don't use a case with the S3, and it was sat on my desk all morning 10 feet from the wifi router, so I don't understand why the signal would have been weak :0(

Bad battery life on my S3

Hey
I installed CM10.1 on my S3 and since then I have been getting terrible battery life. Sometimes lucky to make 10 hours with low use. Low being like 1 phone call along with up to 15 mins of Facebook.
Any help with this issue would be appreciated.
Sent from my GT-I9300 using xda app-developers app
spatian116 said:
Hey
I installed CM10.1 on my S3 and since then I have been getting terrible battery life. Sometimes lucky to make 10 hours with low use. Low being like 1 phone call along with up to 15 mins of Facebook.
Any help with this issue would be appreciated.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It would be good if you could run the betterbatterystats app (you can find it for free to dl here on XDA) and post some screenshots after 1 day.
It will help you as well as us to analyse the battery consumption. It seems that Media is consuming most of it, maybe the famous media scanner issue?
Alrighty. I'll search and install that app and post it
Thanks
Sent from my GT-I9300 using xda app-developers app
spatian116 said:
Alrighty. I'll search and install that app and post it
Thanks
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I linked it for you above. Good luck!
Thank you
Sent from my GT-I9300 using xda app-developers app
chrismast said:
It would be good if you could run the betterbatterystats app (you can find it for free to dl here on XDA) and post some screenshots after 1 day.
It will help you as well as us to analyse the battery consumption. It seems that Media is consuming most of it, maybe the famous media scanner issue?
Click to expand...
Click to collapse
Alright. It is lasting a bit better than yesterday but this is what the app came up with overnight and with a bit of morning use
I'm kind of just hoping this forum support s the code tags lol
Code:
=================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC7
Creation Date: 2013-01-29 12:00:02
Statistic Type: Unplugged to Current
Since 10 h 4 m 19 s
VERSION.RELEASE: 4.2.1
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
OS.VERSION: 3.0.31-CM-g126b49a
BOOTLOADER: I9300TDUBLH1
HARDWARE: smdk4x12
FINGERPRINT: samsung/m0xx/m0:4.1.1/JRO03C/I9300XXDLIB:user/release-keys
ID: JOP40D
TAGS: test-keys
USER: unknown
PRODUCT: m0xx
RADIO: I9300TDULH1
Rooted: true
============
Battery Info
============
Level lost [%]: 73 Bat.: 73% (100% to 27%) [7.2%/h]
Voltage lost [mV]: 633 (4306-3673) [62.9%/h]
===========
Other Usage
===========
Deep Sleep (): 5 h 7 m 18 s (18438 s) Ratio: 50.9%
Awake (): 4 h 57 m 1 s (17821 s) Ratio: 49.1%
Screen On (): 36 m 55 s (2215 s) Ratio: 6.1%
Wifi On (): 10 h 4 m 19 s (36259 s) Ratio: 100.0%
Wifi Running (): 10 h 4 m 19 s (36259 s) Ratio: 100.0%
No Data Connection (): 10 h 3 m 10 s (36190 s) Ratio: 99.8%
No or Unknown Signal (): 10 h 3 m 10 s (36190 s) Ratio: 99.8%
Moderate Signal (): 1 m 9 s (69 s) Ratio: 0.2%
Screen dark (): 43 s (43 s) Ratio: 0.1%
Screen dimmed (): 36 m 11 s (2171 s) Ratio: 6.0%
=========
Wakelocks
=========
MediaScannerService (Media): 2 h 1 m 40 s (7300 s) Count:168 20.1%
com.outlook.Z7.ApacheHttpClientEasConnector (com.outlook.Z7.Outlook.com): 52 m 1 s (3121 s) Count:256 8.6%
MediaScanner (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 37 m 11 s (2231 s) Count:335 6.2%
NetworkLocationLocator (Google Services): 5 m 30 s (330 s) Count:159 0.9%
AudioOut_2 (1013): 5 m 19 s (319 s) Count:96 0.9%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 60 s (60 s) Count:149 0.2%
AlarmManager (Android System): 39 s (39 s) Count:1001 0.1%
ActivityManager-Launch (Android System): 36 s (36 s) Count:292 0.1%
DownloadManager (Media): 30 s (30 s) Count:169 0.1%
FacebookService (com.facebook.katana.Facebook): 18 s (18 s) Count:11 0.1%
RILJ (Phone): 13 s (13 s) Count:515 0.0%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 12 s (12 s) Count:202 0.0%
[email protected]/android_talkf06b1dfe9d8a (Google Services): 12 s (12 s) Count:22 0.0%
LocationManagerService (Android System): 11 s (11 s) Count:210 0.0%
*sync*_com.android.chrome_Account {[email protected], type=com.google} (com.android.chrome.Chrome): 9 s (9 s) Count:8 0.0%
AlarmManager (com.cyanogenmod.lockclock.Chronus): 9 s (9 s) Count:418 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 9 s (9 s) Count:11 0.0%
GpsLocationProvider (Android System): 7 s (7 s) Count:306 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 5 s (5 s) Count:107 0.0%
AlarmClock (com.android.deskclock.Clock): 5 s (5 s) Count:10 0.0%
*vibrator* (com.android.deskclock.Clock): 5 s (5 s) Count:6 0.0%
*vibrator* (Android System): 5 s (5 s) Count:371 0.0%
MQTT (com.facebook.katana.Facebook): 4 s (4 s) Count:108 0.0%
AlarmManager (Google Services): 4 s (4 s) Count:633 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 4 s (4 s) Count:18 0.0%
AlarmManager (com.outlook.Z7.Outlook.com): 4 s (4 s) Count:296 0.0%
AlarmManager (com.fingersoft.hillclimb.Hill Climb Racing): 4 s (4 s) Count:70 0.0%
NetworkStats (Android System): 2 s (2 s) Count:69 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:477 0.0%
*sync*_subscribedfeeds_Account {[email protected], type=com.google} (Google Services): 2 s (2 s) Count:479 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:324 0.0%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.0%
AlarmManager (Phone): 2 s (2 s) Count:81 0.0%
*sync*_com.android.contacts_Account {[email protected], type=com.google} (Google Services): 2 s (2 s) Count:1 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:266 0.0%
RingtonePlayer (com.android.systemui.System UI): 1 s (1 s) Count:24 0.0%
show keyguard (Android System): 1 s (1 s) Count:12 0.0%
C2DM_LIB (com.facebook.katana.Facebook): 1 s (1 s) Count:26 0.0%
ConnectivityService (Android System): 1 s (1 s) Count:1002 0.0%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 1 s (1 s) Count:4 0.0%
AudioIn_F5 (1013): 1 s (1 s) Count:100 0.0%
StartingAlertService (com.android.calendar.Calendar): 1 s (1 s) Count:27 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 1 s (1 s) Count:47 0.0%
*backup* (Android System): 1 s (1 s) Count:386 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1090 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 3 h 34 m 38 s (12878 s) Cnt:(c/wc/ec)1023/0/0 35.5%
"wlan_rx_wake" (): 57 m 59 s (3479 s) Cnt:(c/wc/ec)2290/0/2289 9.6%
"battery-monitor" (): 19 m 55 s (1195 s) Cnt:(c/wc/ec)1223/0/1223 3.3%
"l2_hsic" (): 12 m 21 s (741 s) Cnt:(c/wc/ec)1528/99/1528 2.0%
"wlan_wake" (): 8 m 15 s (495 s) Cnt:(c/wc/ec)140299/816/0 1.4%
"alarm_rtc" (): 5 m 23 s (323 s) Cnt:(c/wc/ec)717/39/64 0.9%
"alarm" (): 3 m 15 s (195 s) Cnt:(c/wc/ec)1447/9/0 0.5%
"mmc1_detect" (): 2 m 54 s (174 s) Cnt:(c/wc/ec)1258/0/229 0.5%
"umts_ipc0" (): 1 m 38 s (98 s) Cnt:(c/wc/ec)347/0/347 0.3%
"radio-interface" (): 50 s (50 s) Cnt:(c/wc/ec)135/0/0 0.1%
"multipdp" (): 16 s (16 s) Cnt:(c/wc/ec)7/0/7 0.0%
"rpm_hsic" (): 15 s (15 s) Cnt:(c/wc/ec)302/0/0 0.0%
"umts_rfs0" (): 11 s (11 s) Cnt:(c/wc/ec)4/0/4 0.0%
"pno_wake_lock" (): 10 s (10 s) Cnt:(c/wc/ec)1/0/1 0.0%
"tx_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)1455/0/0 0.0%
"efsd-interface" (): 1 s (1 s) Cnt:(c/wc/ec)8/0/0 0.0%
"secril_rfs-interface" (): 1 s (1 s) Cnt:(c/wc/ec)4/0/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)31/0/0 0.0%
"sync_system" (): (0 s) Cnt:(c/wc/ec)15/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)1816/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)15754/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)1241/163/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1258/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.4 GHz (): 2 h 1 m 13 s 20.1%
1.3 GHz (): 6 m 28 s 1.1%
1.2 GHz (): 8 m 21 s 1.4%
1.1 GHz (): 11 m 12 s 1.9%
1 GHz (): 18 m 2 s 3.0%
900 MHz (): 10 m 1 s 1.7%
800 MHz (): 29 m 5 s 4.8%
700 MHz (): 4 m 20 s 0.7%
600 MHz (): 2 m 15 s 0.4%
500 MHz (): 4 m 46 s 0.8%
400 MHz (): 12 m 2 s 2.0%
200 MHz (): 1 h 9 m 9 s 11.4%
Deep Sleep (): 5 h 7 m 18 s 50.9%
==================
Reference overview
==================
Custom: null
Since charged: Reference ref_charged created 4 h 48 m 38 s (Wl: 0 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
Since screen off: Reference ref_screen_off created 14 h 43 m 18 s (Wl: 38 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 61 elements; Oth: 10 elements; CPU: 13 elements)
Since unplugged: Reference ref_unplugged created 4 h 48 m 37 s (Wl: 0 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
Since boot: null
Sent from my GT-I9300 using xda app-developers app
spatian116 said:
Alright. It is lasting a bit better than yesterday but this is what the app came up with overnight and with a bit of morning use
I'm kind of just hoping this forum support s the code tags lol
Code:
=================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC7
Creation Date: 2013-01-29 12:00:02
Statistic Type: Unplugged to Current
Since 10 h 4 m 19 s
VERSION.RELEASE: 4.2.1
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
OS.VERSION: 3.0.31-CM-g126b49a
BOOTLOADER: I9300TDUBLH1
HARDWARE: smdk4x12
FINGERPRINT: samsung/m0xx/m0:4.1.1/JRO03C/I9300XXDLIB:user/release-keys
ID: JOP40D
TAGS: test-keys
USER: unknown
PRODUCT: m0xx
RADIO: I9300TDULH1
Rooted: true
============
Battery Info
============
Level lost [%]: 73 Bat.: 73% (100% to 27%) [7.2%/h]
Voltage lost [mV]: 633 (4306-3673) [62.9%/h]
===========
Other Usage
===========
Deep Sleep (): 5 h 7 m 18 s (18438 s) Ratio: 50.9%
Awake (): 4 h 57 m 1 s (17821 s) Ratio: 49.1%
Screen On (): 36 m 55 s (2215 s) Ratio: 6.1%
Wifi On (): 10 h 4 m 19 s (36259 s) Ratio: 100.0%
Wifi Running (): 10 h 4 m 19 s (36259 s) Ratio: 100.0%
No Data Connection (): 10 h 3 m 10 s (36190 s) Ratio: 99.8%
No or Unknown Signal (): 10 h 3 m 10 s (36190 s) Ratio: 99.8%
Moderate Signal (): 1 m 9 s (69 s) Ratio: 0.2%
Screen dark (): 43 s (43 s) Ratio: 0.1%
Screen dimmed (): 36 m 11 s (2171 s) Ratio: 6.0%
=========
Wakelocks
=========
MediaScannerService (Media): 2 h 1 m 40 s (7300 s) Count:168 20.1%
com.outlook.Z7.ApacheHttpClientEasConnector (com.outlook.Z7.Outlook.com): 52 m 1 s (3121 s) Count:256 8.6%
MediaScanner (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 37 m 11 s (2231 s) Count:335 6.2%
NetworkLocationLocator (Google Services): 5 m 30 s (330 s) Count:159 0.9%
AudioOut_2 (1013): 5 m 19 s (319 s) Count:96 0.9%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 60 s (60 s) Count:149 0.2%
AlarmManager (Android System): 39 s (39 s) Count:1001 0.1%
ActivityManager-Launch (Android System): 36 s (36 s) Count:292 0.1%
DownloadManager (Media): 30 s (30 s) Count:169 0.1%
FacebookService (com.facebook.katana.Facebook): 18 s (18 s) Count:11 0.1%
RILJ (Phone): 13 s (13 s) Count:515 0.0%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 12 s (12 s) Count:202 0.0%
[email protected]/android_talkf06b1dfe9d8a (Google Services): 12 s (12 s) Count:22 0.0%
LocationManagerService (Android System): 11 s (11 s) Count:210 0.0%
*sync*_com.android.chrome_Account {[email protected], type=com.google} (com.android.chrome.Chrome): 9 s (9 s) Count:8 0.0%
AlarmManager (com.cyanogenmod.lockclock.Chronus): 9 s (9 s) Count:418 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 9 s (9 s) Count:11 0.0%
GpsLocationProvider (Android System): 7 s (7 s) Count:306 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 5 s (5 s) Count:107 0.0%
AlarmClock (com.android.deskclock.Clock): 5 s (5 s) Count:10 0.0%
*vibrator* (com.android.deskclock.Clock): 5 s (5 s) Count:6 0.0%
*vibrator* (Android System): 5 s (5 s) Count:371 0.0%
MQTT (com.facebook.katana.Facebook): 4 s (4 s) Count:108 0.0%
AlarmManager (Google Services): 4 s (4 s) Count:633 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 4 s (4 s) Count:18 0.0%
AlarmManager (com.outlook.Z7.Outlook.com): 4 s (4 s) Count:296 0.0%
AlarmManager (com.fingersoft.hillclimb.Hill Climb Racing): 4 s (4 s) Count:70 0.0%
NetworkStats (Android System): 2 s (2 s) Count:69 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:477 0.0%
*sync*_subscribedfeeds_Account {[email protected], type=com.google} (Google Services): 2 s (2 s) Count:479 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:324 0.0%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.0%
AlarmManager (Phone): 2 s (2 s) Count:81 0.0%
*sync*_com.android.contacts_Account {[email protected], type=com.google} (Google Services): 2 s (2 s) Count:1 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:266 0.0%
RingtonePlayer (com.android.systemui.System UI): 1 s (1 s) Count:24 0.0%
show keyguard (Android System): 1 s (1 s) Count:12 0.0%
C2DM_LIB (com.facebook.katana.Facebook): 1 s (1 s) Count:26 0.0%
ConnectivityService (Android System): 1 s (1 s) Count:1002 0.0%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 1 s (1 s) Count:4 0.0%
AudioIn_F5 (1013): 1 s (1 s) Count:100 0.0%
StartingAlertService (com.android.calendar.Calendar): 1 s (1 s) Count:27 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 1 s (1 s) Count:47 0.0%
*backup* (Android System): 1 s (1 s) Count:386 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1090 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 3 h 34 m 38 s (12878 s) Cnt:(c/wc/ec)1023/0/0 35.5%
"wlan_rx_wake" (): 57 m 59 s (3479 s) Cnt:(c/wc/ec)2290/0/2289 9.6%
"battery-monitor" (): 19 m 55 s (1195 s) Cnt:(c/wc/ec)1223/0/1223 3.3%
"l2_hsic" (): 12 m 21 s (741 s) Cnt:(c/wc/ec)1528/99/1528 2.0%
"wlan_wake" (): 8 m 15 s (495 s) Cnt:(c/wc/ec)140299/816/0 1.4%
"alarm_rtc" (): 5 m 23 s (323 s) Cnt:(c/wc/ec)717/39/64 0.9%
"alarm" (): 3 m 15 s (195 s) Cnt:(c/wc/ec)1447/9/0 0.5%
"mmc1_detect" (): 2 m 54 s (174 s) Cnt:(c/wc/ec)1258/0/229 0.5%
"umts_ipc0" (): 1 m 38 s (98 s) Cnt:(c/wc/ec)347/0/347 0.3%
"radio-interface" (): 50 s (50 s) Cnt:(c/wc/ec)135/0/0 0.1%
"multipdp" (): 16 s (16 s) Cnt:(c/wc/ec)7/0/7 0.0%
"rpm_hsic" (): 15 s (15 s) Cnt:(c/wc/ec)302/0/0 0.0%
"umts_rfs0" (): 11 s (11 s) Cnt:(c/wc/ec)4/0/4 0.0%
"pno_wake_lock" (): 10 s (10 s) Cnt:(c/wc/ec)1/0/1 0.0%
"tx_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)1455/0/0 0.0%
"efsd-interface" (): 1 s (1 s) Cnt:(c/wc/ec)8/0/0 0.0%
"secril_rfs-interface" (): 1 s (1 s) Cnt:(c/wc/ec)4/0/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)31/0/0 0.0%
"sync_system" (): (0 s) Cnt:(c/wc/ec)15/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)1816/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)15754/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)1241/163/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1258/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.4 GHz (): 2 h 1 m 13 s 20.1%
1.3 GHz (): 6 m 28 s 1.1%
1.2 GHz (): 8 m 21 s 1.4%
1.1 GHz (): 11 m 12 s 1.9%
1 GHz (): 18 m 2 s 3.0%
900 MHz (): 10 m 1 s 1.7%
800 MHz (): 29 m 5 s 4.8%
700 MHz (): 4 m 20 s 0.7%
600 MHz (): 2 m 15 s 0.4%
500 MHz (): 4 m 46 s 0.8%
400 MHz (): 12 m 2 s 2.0%
200 MHz (): 1 h 9 m 9 s 11.4%
Deep Sleep (): 5 h 7 m 18 s 50.9%
==================
Reference overview
==================
Custom: null
Since charged: Reference ref_charged created 4 h 48 m 38 s (Wl: 0 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
Since screen off: Reference ref_screen_off created 14 h 43 m 18 s (Wl: 38 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 61 elements; Oth: 10 elements; CPU: 13 elements)
Since unplugged: Reference ref_unplugged created 4 h 48 m 37 s (Wl: 0 elements; KWl: 28elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
Since boot: null
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Its the media scanner issue, i suggest you go to apps, and clear cache and data from the media scanner.
You can also try using this app, from play store, it disables the media scanner, and when you add new media to your phone, you can enable it so it can scan them for you then disable it again.
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
oae08 said:
Its the media scanner issue, i suggest you go to apps, and clear cache and data from the media scanner.
You can also try using this app, from play store, it disables the media scanner, and when you add new media to your phone, you can enable it so it can scan them for you then disable it again.
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Click to expand...
Click to collapse
Thank you. I have installed that app and will report back tomorrow with the results
Sent from my GT-I9300 using xda app-developers app
spatian116 said:
Thank you. I have installed that app and will report back tomorrow with the results
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No problem also I advise you to post your dump in the bbs thread, they know more there and can help you even better
http://forum.xda-developers.com/showthread.php?t=1179809
Sent from my GT-I9300 using xda premium
Unfortunately even with it disabled I'm losing a lot quickly still D:
But I will check out the link you posted
Sent from my GT-I9300 using xda app-developers app
spatian116 said:
Unfortunately even with it disabled I'm losing a lot quickly still D:
But I will check out the link you posted
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Don't use battery draining reducing apps or something of this sort they only make it worse. And check the bbs thread and post youe dump there.
Sent from my GT-I9300 using xda premium

SGSII Battery Drain

Hi,
Since 6 months i have a big battery drain issue with my i9100. I have tried changing my kernel, ROM, baseband, battery, whatever, this f**king drain is still here.
I joined some screenshots of my battery usage, which is (for me) pretty stange because i haven't used alot my phone today.
And the Better Battery Stats log :
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0_RC1
Creation Date: 2013-11-18 18:39:38
Statistic Type: Unplugged to Current
Since 11 h 49 m 32 s
VERSION.RELEASE: 4.3.1
BRAND: Samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
OS.VERSION: 3.0.64-CM-g7b9279e
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys
ID: JLS36I
TAGS: test-keys
USER: jenkins
PRODUCT: GT-I9100
RADIO: I9100XXMS3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -58% (100% to 42%) [4,9%/h]
Voltage lost [mV]: (4194-3728) [39,4%/h]
===========
Other Usage
===========
Deep Sleep (): 8 h 13 m 24 s (29604 s) Ratio: 69,5%
Awake (): 3 h 36 m 7 s (12967 s) Ratio: 30,5%
Screen On (): 28 m 4 s (1684 s) Ratio: 4,0%
Phone On (): 2 m 39 s (159 s) Ratio: 0,2%
Wifi On (): 2 h 32 m 21 s (9141 s) Ratio: 21,5%
Wifi Running (): 2 h 32 m 21 s (9141 s) Ratio: 21,5%
No Data Connection (): 34 m 21 s (2061 s) Ratio: 4,8%
No or Unknown Signal (): 34 m 21 s (2061 s) Ratio: 4,8%
Poor Signal (): 1 m 26 s (86 s) Ratio: 0,1%
Moderate Signal (): 2 h 54 m 42 s (10482 s) Ratio: 14,0%
Good Signal (): 7 h 48 m 10 s (28090 s) Ratio: 37,5%
Screen dark (): 9 m 7 s (547 s) Ratio: 1,3%
Screen dimmed (): 18 m 56 s (1136 s) Ratio: 1,5%
=========
Wakelocks
=========
NlpCollectorWakeLock (Services Google): 27 m 48 s (1668 s) Count:6854 3,9%
NlpWakeLock (Services Google): 13 m 3 s (783 s) Count:2651 1,8%
LocationManagerService (Système Android): 4 m 27 s (267 s) Count:777 0,6%
FbClientConnManager (com.facebook.katana.Facebook): 2 m 33 s (153 s) Count:111 0,4%
WakefulIntentService[GCoreUlr-LocationReportingService] (Services Google): 2 m 18 s (138 s) Count:6081 0,3%
WakefulIntentService[GCoreUlr-LocationReceiverService] (Services Google): 2 m 15 s (135 s) Count:7970 0,3%
PhoneApp (Téléphone): 1 m 45 s (105 s) Count:6 0,2%
AudioOut_2 (1013): 1 m 33 s (93 s) Count:21 0,2%
RILJ (Téléphone): 1 m 29 s (89 s) Count:5596 0,2%
AlarmManager (Système Android): 1 m 25 s (85 s) Count:2036 0,2%
ActivityManager-Launch (Système Android): 51 s (51 s) Count:869 0,1%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.apps.plus.Google+): 33 s (33 s) Count:10 0,1%
GsmConnection (Téléphone): 28 s (28 s) Count:139 0,1%
AlarmManager (Services Google): 26 s (26 s) Count:5353 0,1%
*sync*_com.evernote.evernoteprovider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.evernote} (com.evernote.Evernote): 19 s (19 s) Count:15 0,0%
SyncService (com.evernote.Evernote): 15 s (15 s) Count:8 0,0%
StartingAlertService (com.android.calendar.Agenda): 15 s (15 s) Count:3 0,0%
NlpLocationReceiverService (Services Google): 13 s (13 s) Count:4139 0,0%
*sync*_com.android.calendar_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.syncadapters.calendar.Synchronisation de Google Agenda): 11 s (11 s) Count:5 0,0%
*vibrator* (Système Android): 11 s (11 s) Count:1181 0,0%
*sync*_subscribedfeeds_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 9 s (9 s) Count:2675 0,0%
*sync*_com.google.android.location.reporting_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 8 s (8 s) Count:2822 0,0%
show keyguard (Système Android): 8 s (8 s) Count:28 0,0%
Checkin Service (Services Google): 8 s (8 s) Count:6221 0,0%
LocationManagerService (Services Google): 7 s (7 s) Count:6060 0,0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Stockage de l'agenda): 7 s (7 s) Count:248 0,0%
AlarmManager (com.facebook.katana.Facebook): 6 s (6 s) Count:949 0,0%
*backup* (Système Android): 6 s (6 s) Count:1216 0,0%
ServiceStateTracker (Téléphone): 5 s (5 s) Count:134 0,0%
*sync*_com.android.contacts_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 5 s (5 s) Count:4141 0,0%
AlarmManager (com.android.providers.calendar.Stockage de l'agenda): 5 s (5 s) Count:124 0,0%
ezl (Services Google): 4 s (4 s) Count:8672 0,0%
fullsync (com.whatsapp.WhatsApp): 4 s (4 s) Count:24 0,0%
Event Log Service (Services Google): 3 s (3 s) Count:6910 0,0%
*sync*_com.android.browser_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 3 s (3 s) Count:5354 0,0%
GCM_CONN_ALARM (Services Google): 3 s (3 s) Count:2819 0,0%
*sync*_com.google.android.gms.people_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 3 s (3 s) Count:1 0,0%
NetworkStats (Système Android): 2 s (2 s) Count:73 0,0%
SyncLoopWakeLock (Système Android): 2 s (2 s) Count:2206 0,0%
ActivityManager-Sleep (Système Android): 2 s (2 s) Count:2067 0,0%
AlarmClock (com.android.deskclock.Horloge): 2 s (2 s) Count:128 0,0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count:7 0,0%
ConnectivityService (Système Android): 2 s (2 s) Count:2037 0,0%
WakefulIntentService[GCoreUlr-SettingsChangedService] (Services Google): 2 s (2 s) Count:2674 0,0%
GOOGLE_C2DM (Services Google): 2 s (2 s) Count:6864 0,0%
AlarmManager (Téléphone): 2 s (2 s) Count:243 0,0%
MQTT (com.facebook.katana.Facebook): 2 s (2 s) Count:139 0,0%
*sync*_com.google.android.ears.heard.EarsContentProvider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.ears.Recherche audio pour Google Play): 1 s (1 s) Count:1 0,0%
GCM_CONN (Services Google): 1 s (1 s) Count:6951 0,0%
Checkin Handoff (Services Google): 1 s (1 s) Count:2815 0,0%
AlarmManager (com.whatsapp.WhatsApp): 1 s (1 s) Count:23 0,0%
SyncManagerHandleSyncAlarm (Système Android): 1 s (1 s) Count:904 0,0%
SCREEN_FROZEN (Système Android): 1 s (1 s) Count:936 0,0%
RingtonePlayer (com.android.systemui.IU système): 1 s (1 s) Count:17 0,0%
GpsLocationProvider (Système Android): 1 s (1 s) Count:912 0,0%
================
Kernel Wakelocks
================
"multipdp" (): 1 h 25 m 2 s (5102 s) Cntc/wc/ec)662/0/662 6,8%
"deleted_wake_locks" (): 1 h 19 m 30 s (4770 s) Cntc/wc/ec)98765/0/3176 6,4%
"PowerManagerService.WakeLocks" (): 53 m 53 s (3233 s) Cntc/wc/ec)6734/0/0 7,6%
"secril_fd-interface" (): 50 m 35 s (3035 s) Cntc/wc/ec)986/0/0 4,1%
"l2_hsic" (): 44 m 27 s (2667 s) Cntc/wc/ec)7098/530/7098 6,3%
"radio-interface" (): 30 m 44 s (1844 s) Cntc/wc/ec)1978/0/0 4,3%
"umts_ipc0" (): 27 m 28 s (1648 s) Cntc/wc/ec)3506/0/3506 3,9%
"alarm_rtc" (): 16 m 20 s (980 s) Cntc/wc/ec)1708/0/325 2,3%
"sec-battery-monitor" (): 10 m 25 s (625 s) Cntc/wc/ec)1826/1138/0 1,5%
"rpm_hsic" (): 8 m 40 s (520 s) Cntc/wc/ec)5039/0/0 1,2%
"alarm" (): 4 m 31 s (271 s) Cntc/wc/ec)2716/4/0 0,6%
"tx_hsic" (): 4 m 30 s (270 s) Cntc/wc/ec)31790/5/0 0,6%
"PowerManagerService.Display" (): 2 m 23 s (143 s) Cntc/wc/ec)47/0/0 0,3%
"power-supply" (): 15 s (15 s) Cntc/wc/ec)1800/0/0 -0,1%
"prx_wake_lock" (): 13 s (13 s) Cntc/wc/ec)8/0/8 0,0%
"PowerManagerService.Broadcasts" (): 12 s (12 s) Cntc/wc/ec)94/0/0 0,0%
"secril_fmt-interface" (): 12 s (12 s) Cntc/wc/ec)17916/0/0 0,0%
"sync_system" (): 5 s (5 s) Cntc/wc/ec)51/0/0 0,0%
"unknown_wakeups" (): 1 s (1 s) Cntc/wc/ec)4/0/4 0,0%
"mmc1_detect" (): 1 s (1 s) Cntc/wc/ec)2245/0/0 0,0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)2245/0/0 0,0%
"KeyEvents" (): (0 s) Cntc/wc/ec)13397/0/0 0,0%
"client-interface" (): (0 s) Cntc/wc/ec)20/0/0 0,0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1,2 GHz (): 9 m 2 s 1,3%
1 GHz (): 41 s 0,1%
800 MHz (): 20 m 32 s 2,9%
500 MHz (): 27 m 37 s 3,9%
200 MHz (): 2 h 38 m 13 s 22,3%
Deep Sleep (): 8 h 13 m 24 s 69,5%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 8 h 59 m 28 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 6 elements)
ref_charged: Reference ref_charged created 8 h 59 m 28 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 6 elements)
ref_current: Reference ref_current created 20 h 49 m (Wl: 55 elements; KWl: 29elements; NetS: null; Alrm: null; Proc: 22 elements; Oth: 13 elements; CPU: 6 elements)
Hope you can help me with this, i'ts pretty annoying and it never drained battery like that. I've powered it up only for checking hour/sending a SMS, not for playing games or stuff like that...
Thanks
(And sorry for my english, as you can see, i'm French )
Have you tryed to see if phone is going to deep sleep. It may be a cause for that. There are apps that can tell you that.
Yep, that seems correct (70% of deep sleep checked with CPUSpy) and that's also on the BetterBatteryStats log
11 hours seem pretty good to me, please take note that you are on a nightly ROM, battery consumption can increase or decrease, no one can know what will happen on a nightly ROM, if you want to watch your battery consumption you should flash a stock rom first because that will be your medium. That said, there are no problems with 11 hour battery life and still %41 at all.
How is the radio signal in your area? That has a massive influence on battery performance.
If you have a radio signal problem, you can try disabling fast dormancy, pretty easy with this app: https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300&hl=en_GB
11 hours is yes, pretty good if I use a little bit my phone.
The problem is that my battery is drained even if my phone is locked and stay in my pocket.
I tried to let it locked for a night when I was sleeping, un-plugged it when he was at 100%, didn't set an alarm, and zero app loaded in RAM.
For 10 hours of sleep, my phone drained about 50 percents of battery.
So the problem is not my use, it's the phone itself.
Don't ****ing know where the problem can be, but today I saw this in BBS.
Something is keeping your phone awake. You can take a look at this app: https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver
Or you can wipe everything and flash a new rom, since we have no idea what causes this.
6th time that I change my ROM, and does nothing. I'll try to get @Stock with the aaaa-weeee-sssooome (lulz) TouchWiz laggy stock rom, and i'll try to see if that changes something...
Dakura said:
Something is keeping your phone awake. You can take a look at this app: https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver
Or you can wipe everything and flash a new rom,
Click to expand...
Click to collapse
These battery savers are less helpful. These just turn off radio on scheduled time and does not prevent culprit app from draing battery which actually is required to save battery. the apps which actually are helpful for conserving battery can be found here under battery section.
since we have no idea what causes this.
Click to expand...
Click to collapse
I agree because there are many factors which are responsible for drainage of battery and with couple of screenshots, one can hardly figure what exactly the problem is.
I could have described those factors in detail but this is not a correct place to do so.
crystaldabuu said:
11 hours is yes, pretty good if I use a little bit my phone.
The problem is that my battery is drained even if my phone is locked and stay in my pocket.
I tried to let it locked for a night when I was sleeping, un-plugged it when he was at 100%, didn't set an alarm, and zero app loaded in RAM.
For 10 hours of sleep, my phone drained about 50 percents of battery.
So the problem is not my use, it's the phone itself.
Don't ****ing know where the problem can be, but today I saw this in BBS.
Click to expand...
Click to collapse
Buddy from the information and screenshot you have shared, I would say network is one of the reason or main reason in drainage of your battery. What you can do to minimize this is, avoid keeping your device where strength of network is less. Fluctuations in network contributes very much in drainage of battery. Also if you will keep data mode on and turn off the screen then too it will awake your cpu at regular intervals. So no matter your screen is off, you will face battery drain. Also when not needed, stay at 2G as 3G with data mode on, drains battery very much.
There may be/may not be other factors but this network factor is certainly there. You should keep your device on flight mode and see if battery drains highly!
Hope this helps
Nobody who's posted to this thread so far has mentioned the ****load of wakelocks in the BBS stats (I.E the bleeding obvious). You have a ton of them. This is causing the drain you're seeing.
OP - If you really want to resolve this, post your BBS stats to the BBS thread on here & ask for help there, people who post to that thread regularly should be able to help you you. If you keep posting to this thread at the current rate, you'll still be running round in circles in a month's time.
Thank you, i'll try this
-> Tryed to switch off Fast Dormancy, didn't noticed any change... so... useless option with my carrier, who, I think, doesn't allow his antennas to be compatible with this thing
Hi,
I update this thread because i have resolved my problems... and they came back in two days.
I flashed a new Rom, Cyanogenmod 10.2, and my battery was fine on tuesday (It looked like this https://pbs.twimg.com/media/BawCU2pIUAAJyrj.png:large).
1 day after, tadaam! battery drain came back. https://pbs.twimg.com/media/BawCdu0IcAAHUmC.png:large
Help me please, i really need this phone working.
I have looked around baseband/RIL problems.
I want to test another baseband but I can't choose one, I live in a town where the reception is good, my actual baseband is the i9100XXMS3.
I'm in 10.2 with DorimanX kernel.
Can you advise me one please ?
Thanks

Categories

Resources