Related
When i use an AOSP rom, my battery life takes a huge hit, particularly when the phone is in standby. On a stock rom, I get maybe 1% drain per hour in standby, with CM7 im getting 3-5%. Ive read that some people actually get normal battery life, so if thats true, then its gotta be something im doing during the install, or something im installing after. (I try to be careful about both, but maybe something is slipping by me.
The point of this thread is to have a flawless flash, and take any variables out of the equation. I dont care about what apps are installed etc, as long as I can see my phone with normal battery usage after the flash.
Basically I want help with the cleanest install possible, and feedback to where i might be messing up. Im not restoring any apps, or anything like that. Handle the directions according to this:
Assume there is a bad flash on the phone currently, and that I need to completely wipe and reinstall CM7 to eliminate any problems.
After the install, ill list absolutely anything i do to the phone to avoid confusion (example: something as small as changing wifi sleep to never, or unchecking backup to google servers)
I am totally commited to find out whats causing my issues, because I really do like the phone, and dont want to return it because i couldnt solve this problem.
STEPS I TOOK SO FAR (UPDATED FREQUENTLY)
12/4 7:00pm
put Kang build from 12/4/11 on sd along with gapps (checked md5 beforehand)
--didnt wipe SD before install, wanted to, but wasnt near a computer when i flashed, not a big deal
through rom manager - installed newest cwm
charged phone to 100%
booted into recovery
wiped: data, cache, dalvik cache
installed rom
installed gapps
--------reboot------------
added my google account
i chose to NOT have google back up anything to the server
I chose to allow location based services
CM asked me to send usage report, i pressed clear by accident - im sure it will ask me again
installed market
installed gmail
check "unknown sources" in applications
installed swype
installed betterbatterystats and cpuspy
added powercontrol widget
set screen to auto-brightness
changed the battery in the statusbar to percentage
changed wifi sleep policy to never
-----------------
12/4 11:10pm
installed dropbox
changed background from live to black wallpaper
----------
12/5 1:30am
set up adw (just organized screens, changed look a bit)
set alarms
mute camera shutter
touchkey backlight timeout - 2 seconds
leaving led notifications OFF for now...
changed ringtones
turn off low battery sound
screen timeout changed to 30 sec (was 1 min)
----------------------
12/5 4:30PM
installed Teacheraidepro - purchased (for my teams attendance)
8:30pm - sywpe updated itself
--------------------------
12/7 12:30AM
installed google voice app
bought, installed and uninstalled 10 apps. (10cent sale)
setting: applications: development, kill apps via long press of back button (i always do this)
installed doggcatcher (has playback bugs, CM7 nightly/kang issue)
installed stopwatch
installed sleepyjack
installed voice recorder (stock sound recorder doesnt let you lock screen and record)
uninstalled voice recorder (touchscreen wouldnt work in app)
---------Thats it so far----------
Yes im probably listing too much, but i want everyone to see exactly what im doing with my phone.
-Leading up to my current install (the one thats giving me problems) I first installed drivers (Kies_2.0.3.11082_152_4) and then let it update because i guess they weren't the latest. I should not that I have a captivate - is it possible drivers are conflicting?
-made sure phone was charged to 100%
-flashed SGH-I777_ClockworkMod-Recovery_5.0.2.3 through odin
put "update-cm-7.2.0-RC0-Galaxys2ATT-KANG-signed" and newest GAPPS on my phone.
Followed CM instructions about flashing in CWM, (had to choose zip file twice), also installed gapps before rebooting phone for the first time.
Do you have BetterBatteryStats installed to look at wakelocks? How about CPUSpy?
21cdb said:
Do you have BetterBatteryStats installed to look at wakelocks? How about CPUSpy?
Click to expand...
Click to collapse
just installed both, so when i do the fresh install, they will be one of the first things i install.
Im basically going to be running the phone completely stock on CM7.1, so i dont know what could be running on mine thats not running on others.
If anything, i think maybe the problem lies with my install method?
once my phone reaches 100%, im going to reflash, and run the phone stock for a few hours to see if it makes any difference.
My method will be:
-put the newest KANG build on my SD, along with gapps (checked md5 matches)
*** delete mostly everything from sd - leaving only rom and gapps
*** flash cwm through rom manager (how necesay is this? cwm is already installed, and i can just boot into it by holding power and selecting recovery. Im going to flash the one they say to in the guide anyway)
-boot into cwm
-wipe data
-wipe cache
-wipe dalvik cache
(i wont wipe battery stats, i did last time, ive heard its pointless)
-then ill install zip from SD
-choose cm7
-wait for it to go through (do i need to do it twice this time?)
-install gapps
-reboot phone - let phone boot for first time
from here my only changes will be:
add google account
sync contacts, cal, and gmail
install android market
install Betterbatterystats, and cpu spy
install google apps (gmail, maps) (holding off on others for now)
install swype (cant live without it)
wifi sleep policy set to never
add power control widget to home screen
customize stock launcher (move around icons)
set background to plain black image
turn off gps
add home wifi and turn on wifi
check unknown sources in applications
set brightness to 50% (in standby it wont matter)
set volumes, ringtones, etc
turn off display after 30 sec
Thats IT, absolutely nothing else will be put on. I will run the phone like this and report back my results.
Does anyone have any suggestions or changes i should make?
lourivellini said:
wifi sleep policy set to never
add home wifi and turn on wifi
Does anyone have any suggestions or changes i should make?
Click to expand...
Click to collapse
If you have unlimited data, turn wifi off. Wifi uses less power byte for byte when transmitting compared to 3g, but wifi continually transmits data back and forth. 3g, on the other hand, only transmits data when there is something that needs to be transmitted. This is what I found out when I looked into why I my battery drain is lower when I forget to turn off wifi.
Now, if you are constantly transmitting, such as a voip call or downloading a huge file, then turn wifi on momentarily.
SoCaliTrojan said:
If you have unlimited data, turn wifi off. Wifi uses less power byte for byte when transmitting compared to 3g, but wifi continually transmits data back and forth. 3g, on the other hand, only transmits data when there is something that needs to be transmitted. This is what I found out when I looked into why I my battery drain is lower when I forget to turn off wifi.
Now, if you are constantly transmitting, such as a voip call or downloading a huge file, then turn wifi on momentarily.
Click to expand...
Click to collapse
cool, will definitely try. I have unlimited data, so i really just use wifi to not use excessive data. I believe ATT will throttle you of you are in the top 10 percent of data users.
How much of a difference do you experience when having wifi on or off? For me it seemed like wifi helped. In fact in a previous thread, i posted how well my captivate performed with pinnacle, and someone said "oh thats because your on wifi all day" heres the screenshot:
{
"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"
}
lourivellini said:
heres the screenshot:
Click to expand...
Click to collapse
I didn't do a scientific comparison then, but may try one soon. The difference for me added at least 4 hours though. I could barely make it through the day and had to make sure I charge at work, but once I kept wifi off, I can make it through the day. The last time I forgot to charge, I went over a day after moderate use.
Your screen shot tells me that battery drain decreased when your phone signal improved (it wasn't fishing or trying to maintain a hold on a weak signal). The moments your phone was in deep asleep helped too.
As for throttling, it's a hit or miss. Some people go over 10 gigs without being throttled, while some are throttled after 2 gigs (rare instance). If I recall correctly, part of determining if you should be throttled is your data use. If you normally use x gigs, going over it in the future might trigger an alarm indicating that you're using more than your average (this is what happened to the guy throttled after 2 gigs...per the rep he spoke to). He's part of the reason why i'm trying to use more data.
SoCaliTrojan said:
I didn't do a scientific comparison then, but may try one soon. The difference for me added at least 4 hours though. I could barely make it through the day and had to make sure I charge at work, but once I kept wifi off, I can make it through the day. The last time I forgot to charge, I went over a day after moderate use.
Your screen shot tells me that battery drain decreased when your phone signal improved (it wasn't fishing or trying to maintain a hold on a weak signal). The moments your phone was in deep asleep helped too.
As for throttling, it's a hit or miss. Some people go over 10 gigs without being throttled, while some are throttled after 2 gigs (rare instance). If I recall correctly, part of determining if you should be throttled is your data use. If you normally use x gigs, going over it in the future might trigger an alarm indicating that you're using more than your average (this is what happened to the guy throttled after 2 gigs...per the rep he spoke to). He's part of the reason why i'm trying to use more data.
Click to expand...
Click to collapse
I definitely used to get better battery on that rom when i was at home. From looking at that screenshot, you can see from like 7am-2pm a decent drain, because i had barely any service (was in standby the whole time), then after 2 im in a better service area for around 2-3 hours with little use, then i get so-so service, and use the phone a bit so it drains more. Finally i go to sleep with full service, and you can see how slowly the phone drains.
I would kill to get similar results with my gs2 running a AOSP rom. It technically should be better on standby drain, because the battery is bigger than the captivates.
Im usually around 2-3 gigs, primarily because i use pandora quite a bit, and also stream HD youtube over 3g. Im not too worried about being throttled, but like using wifi when i can.
But if leaving it off helps, then i will. Also: does it matter if i leave wifi on even when im not connected? Or does it only affect battery when it is connected? I also have to same question for GPS. I usually leave it off, and then when i rarely want to use gps, ill switch it on, but i noticed that its not really on anyway until you use an app that requests it.
SoCaliTrojan said:
If you have unlimited data, turn wifi off. Wifi uses less power byte for byte when transmitting compared to 3g, but wifi continually transmits data back and forth. 3g, on the other hand, only transmits data when there is something that needs to be transmitted. This is what I found out when I looked into why I my battery drain is lower when I forget to turn off wifi.
Now, if you are constantly transmitting, such as a voip call or downloading a huge file, then turn wifi on momentarily.
Click to expand...
Click to collapse
Wrong, wifi does not do this. (Exception: Access points transmit a periodic beacon, but we are not an access point)
Standby drain for the wifi chip in our devices is VERY low (probably 1/10 of what its predecessor's drain was, if power_profile.xml is to be believed), and between the lower penalty per byte transferred and the avoidance of the 6 second svnet-dormancy wakelock, routing all background data over wifi whenever possible will save significant battery. The only time this does not hold true is when some app uses more data on wifi than it does when on the cellular radio.
Entropy512 said:
if power_profile.xml is to be believed),
Click to expand...
Click to collapse
Don't believe anything power_profile.xml tells you. I'm starting to think samsung just copied the file from another phone model without putting in the proper numbers.
Entropy512 said:
Wrong, wifi does not do this. (Exception: Access points transmit a periodic beacon, but we are not an access point)
Standby drain for the wifi chip in our devices is VERY low (probably 1/10 of what its predecessor's drain was, if power_profile.xml is to be believed), and between the lower penalty per byte transferred and the avoidance of the 6 second svnet-dormancy wakelock, routing all background data over wifi whenever possible will save significant battery. The only time this does not hold true is when some app uses more data on wifi than it does when on the cellular radio.
Click to expand...
Click to collapse
garyd9 said:
Don't believe anything power_profile.xml tells you. I'm starting to think samsung just copied the file from another phone model without putting in the proper numbers.
Click to expand...
Click to collapse
Well either way, i doubt one way or the other is having such a dramatic impact on my battery. I just flashed following the steps i listed in a previous post.
So far im seeing about the same results as i did previously, but its too early to tell.
I flashed the phone at about 630, so after ~5 hours ill report back with results. Im trying not to use the phone, so i can see standby drain. I connected to wifi for a little to install swype, and then disconnected.
Will post any info requested then. Im keeping a log of what im doing on the phone in post #2.
Entropy512 said:
routing all background data over wifi whenever possible will save significant battery. The only time this does not hold true is when some app uses more data on wifi than it does when on the cellular radio.
Click to expand...
Click to collapse
Perhaps more factors come into play (distance to cell tower, etc). In my experience on this phone, wifi drains my battery alot more. I can tell when I forgot to turn off wifi because my battery will be lower in the middle of the day than what I am used to. I also go into every app and make sure to check "download when using either wifi or mobile" rather than "download using wifi only," so I pretty much try to have every app use whatever connection is available.
In my searches, it seems that some people do save alot of power by trying to only use wifi, while others have mentioned that they leave wifi off because it sucks too much power for them. I am guessing phone use comes into play: some people keep picking up their phones every 5 minutes, while others let their phone sit while they do something else.
I do wish wifi saved more power for me...I like to have my phone on my network so that I can use allshare, etc.
By the way, the quotes below are what I have been leaning towards agreeing with (due to my experiences with this phone). I don't know if they are over-generalizing, but the idea of looking at things as power over time as opposed to power per byte is intriguing.
http://www.careace.net/2011/10/06/tip-which-uses-more-battery%E2%80%94wifi-or-3g4g-data-connections/ said:
With regards to 3G, for the most part, your GSM radio is not transmitting. GSM radios operate by occasionally connecting your phone with the network to check up on its connection status to optimize reception quality. If you place or receive a call, it will transmit during the call making sure to keep connected with the strongest cell tower. When you send a text, it will transmit for the duration of the sending process and then stop. If you’ve ever been in a location with spotty reception, you can witness refresh time intervals of the GSM radio trying to reconnect with network. Similarly, when you use 3G data, it flips on the radio switch, activating it for the duration of its use.
WiFi on the other hand is a connection that is always on. WiFi radios will constantly transmit regardless of whether or not data is being sent through the connection. Thus, even though byte-per-byte WiFi radios use less power than GSM radios, they consume more power over time compared to their GSM counterparts.
Click to expand...
Click to collapse
http://nesl.ee.ucla.edu/fw/documents/reports/2007/poweranalysis.pdf said:
WiFi radios have a high wakeup and connection maintenance energy, but low energy per bit
transmission cost and high bandwidth. The power consumption models for a WiFi radio are based on the
experimental model derived in [Context-for-Wireless] for an HTC Wizard phone. It was discovered that if
the WiFi module is left on for more than 15 sec, it is more efficient to shut it down.
....
Cellular radios have low connection maintenance energy, but high energy per bit transmission cost
and low bandwidth.
Click to expand...
Click to collapse
Anyway, I was just throwing out that idea in case it helps OP. I know I hated my phone's battery life and was planning to get an extended battery so that I could make it through a single day, but turning off wifi lets me get through the day while keeping my stock nfc-enabled battery (I want to be ready for when Google Wallet is available to us). If the study and other sites are wrong, I stand corrected, but will keep my wifi off since it is noticeably better for me.
Going to post my results at 11pm.
What should i post here to be helpful? I'm going to post screenshots of my battery stats, not sure what info from those other programs will be of use. Let me know what i can post.
ok so heres how im doing. Note i only have done exactly what is in post 2. I used the phone a little, but not too much.
standby drain seems to be about what it was before. Without factoring in the dips when i had to use it, id say its probably losing 3-4% per hour, which i consider high (compared to i777 roms)
suggestions?
also heres my better battery stats dump, if anyone can make any sense out of it:
===================
General Information
===================
BetterBatteryStats version: 1.4.2.0
Creation Date: 2011-12-04 23:13:25
Statistic Type: (0) Since Charged
Since 4 h 40 m 28 s
VERSION.RELEASE: 2.3.7
BRAND: samsung
DEVICE: galaxys2att
MANUFACTURER: samsung
MODEL: SGH-I777
===========
Other Usage
===========
Awake (): 1 h 11 m 35 s (4295 s) Ratio: 25.5%
Screen On (): 40 m 15 s (2415 s) Ratio: 14.4%
Wifi On (): 38 m 6 s (2286 s) Ratio: 13.6%
Phone On (): 57 s (57 s) Ratio: 0.3%
=========
Wakelocks
=========
SMSDispatcher (Dialer): 3 m 49 s (229 s) Count:50 1.4%
GTALK_ASYNC_CONN (Google Services): 2 m 4 s (124 s) Count:38 0.7%
*sync* (Google Services): 1 m 25 s (85 s) Count:95 0.5%
ActivityManager-Launch (Android System): 1 m 25 s (85 s) Count:408 0.5%
*sync* (com.google.android.gm.Gmail): 1 m 17 s (77 s) Count:11 0.5%
DownloadManager (Media): 38 s (38 s) Count:10 0.2%
GSM (Dialer): 37 s (37 s) Count:61 0.2%
RILJ (Dialer): 35 s (35 s) Count:721 0.2%
DownloadManager (com.google.android.gm.Gmail): 33 s (33 s) Count:36 0.2%
*network-location* (Android System): 32 s (32 s) Count:416 0.2%
*vibrator* (Android System): 20 s (20 s) Count:944 0.1%
*wifi* (Android System): 12 s (12 s) Count:613 0.1%
show keyguard (Android System): 12 s (12 s) Count:43 0.1%
MediaScannerService (Media): 9 s (9 s) Count:3 0.1%
AlarmManager (Android System): 9 s (9 s) Count:1325 0.1%
GTALK_CONN (Google Services): 8 s (8 s) Count:429 0.1%
StartingAlertService (com.android.mms.Messaging): 7 s (7 s) Count:64 0.0%
sleep_broadcast (Android System): 6 s (6 s) Count:570 0.0%
GpsLocationProvider (Android System): 6 s (6 s) Count:438 0.0%
*network-location* (com.android.browser.Browser): 6 s (6 s) Count:3 0.0%
Checkin Service (Google Services): 6 s (6 s) Count:464 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s (5 s) Count:39 0.0%
keyguardWakeAndHandOff (Android System): 5 s (5 s) Count:1078 0.0%
*sync* (com.cooliris.media.Gallery): 5 s (5 s) Count:3 0.0%
SCREEN_FROZEN (Android System): 5 s (5 s) Count:638 0.0%
Browser (com.android.browser.Browser): 2 s (2 s) Count:1 0.0%
GOOGLE_C2DM (Google Services): 2 s (2 s) Count:110 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:120 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:470 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1378 0.0%
NotificationService (Android System): 1 s (1 s) Count:1031 0.0%
================
Kernel Wakelocks
================
"svnet-dormancy" (): 23 m 30 s (1410 s) Cntc/wc/ec)168/0/168 8.4%
"svnet" (): 10 m 3 s (603 s) Cntc/wc/ec)980/0/980 3.6%
"PowerManagerService" (): 7 m 4 s (424 s) Cntc/wc/ec)1267/0/0 2.5%
"radio-interface" (): 3 m 50 s (230 s) Cntc/wc/ec)416/0/0 1.4%
"AudioOutLock" (): 3 m 5 s (185 s) Cntc/wc/ec)49/0/0 1.1%
"sec-battery-monitor" (): 2 m 43 s (163 s) Cntc/wc/ec)523/104/0 1.0%
"event1-2695" (): 40 s (40 s) Cntc/wc/ec)169/38/0 0.2%
"alarm" (): 30 s (30 s) Cntc/wc/ec)252/0/0 0.2%
"alarm_rtc" (): 29 s (29 s) Cntc/wc/ec)57/0/13 0.2%
"deleted_wake_locks" (): 18 s (18 s) Cntc/wc/ec)6784/0/260 0.1%
"power-supply" (): 9 s (9 s) Cntc/wc/ec)524/0/0 0.1%
"prx_wake_lock" (): 6 s (6 s) Cntc/wc/ec)4/0/4 0.0%
"sync_system" (): 3 s (3 s) Cntc/wc/ec)50/0/0 0.0%
"event4-2695" (): 1 s (1 s) Cntc/wc/ec)4/1/0 0.0%
"event7-2695" (): (0 s) Cntc/wc/ec)116876/0/0 0.0%
"vib_present" (): (0 s) Cntc/wc/ec)625/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)16069/0/0 0.0%
"mmc_delayed_work" (): (0 s) Cntc/wc/ec)164/0/3 0.0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)97/0/0 0.0%
"wlan_wake" (): (0 s) Cntc/wc/ec)3778/0/0 0.0%
=========
Processes
=========
suspend (0): Sys: 33 s (33 s) Us: (0 s) Starts: 0
events/0 (0): Sys: 28 s (28 s) Us: (0 s) Starts: 0
com.android.wallpaper (com.android.wallpaper.Android Live Wallpapers): Sys: 1 s (1 s) Us: 8 s (8 s) Starts: 1
com.android.launcher (com.android.launcher.ADW.Launcher): Sys: (0 s) Us: 7 s (7 s) Starts: 1
com.android.browser (com.android.browser.Browser): Sys: (0 s) Us: 6 s (6 s) Starts: 3
com.android.vending (com.android.vending.Market): Sys: (0 s) Us: 5 s (5 s) Starts: 4
com.android.settings (Android System): Sys: (0 s) Us: 4 s (4 s) Starts: 4
*wakelock* (Dialer): Sys: 3 s (3 s) Us: (0 s) Starts: 0
com.android.systemui (Android System): Sys: (0 s) Us: 3 s (3 s) Starts: 1
com.android.mms (com.android.mms.Messaging): Sys: (0 s) Us: 2 s (2 s) Starts: 4
mmcqd (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
com.swype.android.inputmethod (com.swype.android.inputmethod.Swype): Sys: (0 s) Us: 2 s (2 s) Starts: 1
android.process.acore (Android Core Apps): Sys: (0 s) Us: 2 s (2 s) Starts: 3
com.google.process.gapps (Google Services): Sys: (0 s) Us: 2 s (2 s) Starts: 2
android.process.media (Media): Sys: (0 s) Us: 2 s (2 s) Starts: 2
mali-pmm-wq (0): Sys: 2 s (2 s) Us: (0 s) Starts: 0
mediaserver (1013): Sys: (0 s) Us: 2 s (2 s) Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Sys: (0 s) Us: 1 s (1 s) Starts: 4
com.android.phone (Dialer): Sys: (0 s) Us: 1 s (1 s) Starts: 1
*wakelock* (Google Services): Sys: 1 s (1 s) Us: (0 s) Starts: 0
irq/328-mxt224_ (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
tvout resume wo (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.swype.android.installer (com.swype.android.installer.Swype Installer): Sys: (0 s) Us: (0 s) Starts: 1
*wakelock* (com.google.android.gm.Gmail): Sys: (0 s) Us: (0 s) Starts: 0
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.swype.android.inputmethod (com.swype.android.inputmethod.SwypeInputMethod)
Active since: 1 h 23 m 22 s
Last activity: 25 m
Crash count:0
com.bel.android.dspmanager (com.bel.android.dspmanager.HeadsetService)
Active since: 52 s
Last activity: 52 s
Crash count:0
com.cyanogenmod.stats (com.cyanogenmod.stats.ReportingService)
Active since: 60 s
Last activity: 1 h 8 m 28 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 55 s
Last activity: 58 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 52 s
Last activity: 52 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 50 s
Last activity: 50 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 4 h 40 m 15 s
Last activity: 1 h 11 m 22 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 51 s
Last activity: 51 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.PushMessagingRegistrar)
Active since: 2 h 36 m 59 s
Last activity: 34 m 44 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 50 s
Last activity: 52 s
Crash count:0
com.swype.android.inputmethod:SwypeConnect (com.swype.android.connect.ConnectClient)
Active since: 1 h 23 m 22 s
Last activity: 32 m 5 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 60 s
Last activity: 1 h 8 m 53 s
Crash count:0
garyd9 said:
Don't believe anything power_profile.xml tells you. I'm starting to think samsung just copied the file from another phone model without putting in the proper numbers.
Click to expand...
Click to collapse
On some devices it's copied (Infuse is, without a doubt, copied), but on the I777 it seems sensible and the results I get are fairly consistent.
To the OP - I suggest you do a baseline drain test - it's hard to tell whether you've got a problem or not with a mixed usage scenario. See my known battery drainers thread for info, but the basic idea is:
Charge to full before bed
Reboot
Reset timers in CPUSpy (this may not be necessary any more, I think CPUSpy may have fixed the bug that made this step necessary)
Go to bed
Collect data when you wake up
Entropy512 said:
On some devices it's copied (Infuse is, without a doubt, copied), but on the I777 it seems sensible and the results I get are fairly consistent.
To the OP - I suggest you do a baseline drain test - it's hard to tell whether you've got a problem or not with a mixed usage scenario. See my known battery drainers thread for info, but the basic idea is:
Charge to full before bed
Reboot
Reset timers in CPUSpy (this may not be necessary any more, I think CPUSpy may have fixed the bug that made this step necessary)
Go to bed
Collect data when you wake up
Click to expand...
Click to collapse
I think ill try tonight, only im only going to leave the phone alone for 4-5 hours, is that enough?
Any recommendations as far as leaving wifi on or anything else like that?
Phone is charging now....
Also: if i am actually losing 3-5% per hour, would everyone agree that it does seem like a lot? Because so far it is seeming that way...
lourivellini said:
I think ill try tonight, only im only going to leave the phone alone for 4-5 hours, is that enough?
Any recommendations as far as leaving wifi on or anything else like that?
Phone is charging now....
Also: if i am actually losing 3-5% per hour, would everyone agree that it does seem like a lot? Because so far it is seeming that way...
Click to expand...
Click to collapse
for you to compare, i have the latest kang build for cm7, and when i left my phone alone for ~5-6hrs with wifi on i lost about 3%. the only thing that i have running is the google back up and push email
i used BetterBatteryStats to try and see what was killing my battery. in an 8 hour night, i lose 20% battery.. not cool. thats over 2% an hour, with bluetooth off, and gps off, (i leave my wifi connected because ive been told wifi uses less battery than 3G). i turn my brightness all the way down, and call it a night. yet i still wake up so drained.. could someone a little more knowledgeable take a look at my log and see if they can make heads or tails of what are the big drainers here?
ill drop rep for anyone who can offer any input
===================
General Information
===================
BetterBatteryStats version: 1.4.2.0
Creation Date: 2011-12-14 12:19:44
Statistic Type: (0) Since Charged
Since 8 h 11 m 11 s
VERSION.RELEASE: 2.3.4
BRAND: samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
===========
Other Usage
===========
Wifi On (): 8 h 11 m 11 s (29471 s) Ratio: 100.0%
Awake (): 1 h 34 m 14 s (5654 s) Ratio: 19.2%
Screen On (): 50 s (50 s) Ratio: 0.2%
=========
Wakelocks
=========
NetworkLocationLocator (com.google.android.apps.maps.Maps): 38 m 31 s (2311 s) Count:494 7.8%
AlarmManager (Android System): 5 m 10 s (310 s) Count:17937 1.1%
*sync* (com.google.android.apps.reader.Google Reader): 1 m 9 s (69 s) Count:16 0.2%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:1962 0.1%
*network-location* (Google Services): 31 s (31 s) Count:169 0.1%
BWL (com.levelup.beautifulwidgets.Beautiful Widgets): 25 s (25 s) Count:8 0.1%
*network-location* (Android System): 25 s (25 s) Count:48 0.1%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 19 s (19 s) Count:1468 0.1%
FacebookService (com.facebook.katana.Facebook): 13 s (13 s) Count:8 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:2474 0.0%
LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 8 s (8 s) Count:2 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 8 s (8 s) Count:2988 0.0%
*sync* (com.google.android.gm.Gmail): 6 s (6 s) Count:1 0.0%
BackgroundFriendService (com.google.android.apps.maps.Maps): 5 s (5 s) Count:499 0.0%
Event Log Service (Google Services): 4 s (4 s) Count:17 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2978 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:133 0.0%
SyncManagerHandleSyncAlarm (Android System): 2 s (2 s) Count:105 0.0%
ActivityManager-Launch (Android System): 2 s (2 s) Count:37 0.0%
SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:2 0.0%
*backup* (Android System): 1 s (1 s) Count:679 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s (1 s) Count:1 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 48 m 2 s (2882 s) Cntc/wc/ec)8681/0/0 9.7%
"sec-battery-monitor" (): 24 m 16 s (1456 s) Cntc/wc/ec)1580/1205/0 4.9%
"alarm" (): 23 m 21 s (1401 s) Cntc/wc/ec)23255/6/0 4.7%
"svnet" (): 20 m 39 s (1239 s) Cntc/wc/ec)1652/0/1652 4.2%
"wlan_rx_wake" (): 7 m 54 s (474 s) Cntc/wc/ec)676/0/676 1.6%
"wlan_wake" (): 7 m 7 s (427 s) Cntc/wc/ec)9321/358/0 1.4%
"alarm_rtc" (): 6 m 37 s (397 s) Cntc/wc/ec)628/0/48 1.3%
"power-supply" (): 58 s (58 s) Cntc/wc/ec)1581/0/0 0.2%
"radio-interface" (): 31 s (31 s) Cntc/wc/ec)43/0/0 0.1%
"AudioOutLock" (): 3 s (3 s) Cntc/wc/ec)15/0/0 0.0%
"vbus_present" (): 1 s (1 s) Cntc/wc/ec)1/0/1 0.0%
"event1-2655" (): (0 s) Cntc/wc/ec)5/1/0 0.0%
"sync_system" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"mmc_delayed_work" (): (0 s) Cntc/wc/ec)1852/0/1 0.0%
"sec-battery-cable" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)1125/0/0 0.0%
=========
Processes
=========
suspend (0): Sys: 3 m 14 s (194 s) Us: (0 s) Starts: 0
events/0 (0): Sys: 2 m 47 s (167 s) Us: (0 s) Starts: 0
*wakelock* (com.google.android.apps.maps.Maps): Sys: 1 m 8 s (68 s) Us: 5 s (5 s) Starts: 0
tvout resume wo (0): Sys: 16 s (16 s) Us: (0 s) Starts: 0
mmcqd (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
*wakelock* (com.google.android.apps.reader.Google Reader): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.google.android.apps.reader (com.google.android.apps.reader.Google Reader): Sys: (0 s) Us: 1 s (1 s) Starts: 1
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
org.artsplanet.android.pesobatteryfull (org.artsplanet.android.pesobatteryfull.PesoWidgetProvider$WidgetService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.sec.android.fotaclient (com.sec.android.fotaclient.FOTAService)
Active since: 33 s
Last activity: 31 m 10 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 18 s
Last activity: 18 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 17 s
Last activity: 17 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.PushMessagingRegistrar)
Active since: 24 s
Last activity: 24 s
Crash count:0
ch.blinkenlights.battery (ch.blinkenlights.battery.BlinkenlightsBatteryService)
Active since: 30 s
Last activity: 31 m
Crash count:0
com.pandaroid.clockno1cute (com.pandaroid.clockno1cute.PandaClockService)
Active since: 31 s
Last activity: 1 h 36 m 30 s
Crash count:0
org.adw.launcher.notifications (org.adw.launcher.notifications.ADWService)
Active since: 30 s
Last activity: 1 h 8 m 51 s
Crash count:0
com.teslacoilsw.widgetlocker (com.teslacoilsw.widgetlocker.LockerService)
Active since: 29 s
Last activity: 1 h 36 m 31 s
Crash count:0
com.beansoft.keyboardplus (com.beansoft.keyboardplus.LatinIME)
Active since: 17 s
Last activity: 17 s
Crash count:0
com.smlds (com.smlds.smlStartService)
Active since: 24 s
Last activity: 1 h 1 m 15 s
Crash count:0
com.sec.android.providers.drm (com.sec.android.providers.drm.OmaDrmConfigService)
Active since: 25 s
Last activity: 1 h 2 m 2 s
Crash count:0
com.sec.android.app.FileTransferServer (com.sec.android.app.FileTransferServer.FTSService)
Active since: 2 h 36 m 56 s
Last activity: 31 m 57 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 24 s
Last activity: 1 m 11 s
Crash count:0
com.sec.android.app.FileTransferManager (com.sec.android.app.FileTransferManager.FTSRunningChecker)
Active since: 20 s
Last activity: 31 m 57 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.google.android.apps.maps:NetworkLocationService (com.google.android.location.internal.server.NetworkLocationService)
Active since: 29 s
Last activity: 1 h 35 m 20 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 15 s
Last activity: 20 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 20 s
Last activity: 1 m 28 s
Crash count:0
com.rhythm.hexise.task (com.rhythm.hexise.task.TaskService)
Active since: 30 s
Last activity: 30 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.UploadManager)
Active since: 22 s
Last activity: 1 m 28 s
Crash count:0
Click to expand...
Click to collapse
[email protected]
ill drop rep for anyone who can offer any input
better off asking in the better battery stats thread arent you?
wow there is such a thing? lol yeah ill go try and find it
From your stats, I believe your latitude is on.
Go to Latitude, settings (or location reporting), click on sign out of latitude.
Second, just in case if you have a dlink router, turn wifi off.
Now let your phone sits for a couple of hours, everything should be improved.
Sent from my GT-I9100 using Tapatalk
not necessarily latitude, maps can do the same thing.
i had the same problem, and read a solution that i donwt yet know if works, but worth trying: freezing the network location with titanium backup.
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
dikai_yang said:
From your stats, I believe your latitude is on.
Go to Latitude, settings (or location reporting), click on sign out of latitude.
Second, just in case if you have a dlink router, turn wifi off.
Now let your phone sits for a couple of hours, everything should be improved.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
why specifically dlink?
Your gtalk, facebook etc are taking a toll on your battery
D-Link routers have problems with pinging the phone excessively draining the battery. I have the problem with this router and non others (at work, at friends, etc). I don't think a lot of people know about this. They simply accept the battery drain. Turning wifi off when not in use (through juicedefender not wifi sleep policy) is a workaround.
Unless maps is running, the network usage shouldn't stand out at the top unless latitude is signed in.
Facebook drain is unfortunate but normal. Even if notification is set to off, it still wakes the device periodically. Don't try to kill it because when it restarts itself it does a full sync causing a cpu spike.
There are several apps that uses a good amount of cpu even when idle. TVUPlayer, Polaris office, tapatalk, soundhound, goggles translate.
All these are results of a long period of testing on cpu usage and battery analysis.
With that said, not all wakelocks cause battery drain. A lot of people are obsessed with killing / freezing all apps they see as wakelocks in bbs. This is not necessary. Otherwise, don't run Facebook, ebay, skype, push email, then why get a sgs2? Battery monitor widget causes the most wakes in bbs yet it only uses a very small % of battery.
Sent from my GT-I9100 using Tapatalk
so helpful dang.. yeah I logged out of latitude.. I never use it anyways.. should I uninstall Polaris? do apps drain data even if they aren't being used? I mean I know some do.. but even Polaris? dang.. I wonder what other apps I have that use background data when I'm not using them.. is there any way to check?
Sent from my GT-I9100 using XDA App
edit: oh yeah, does having live Widgets (like my live clock panda, and panda battery widget, and other stuff that makes my homescreen super cute) hurt me? I mean anything noticeable?
ok well ty guys
Sent from my GT-I9100 using XDA App
The apps I mentioned above don't necessarily use data in background (in a noticeable amount anyway). What I meant is that after quitting the app (back key), it keeps consuming a fairly small amount of cpu constantly, indefinitely, and is unnecessary. TVU player isvthe worst. Try watching a show for 5 seconds, quit the app, you'll see in System Tuner that it keeps consuming about 5% of battery constantly.
Good workaround. Install System Tuner (requires root), and set it to kill the problematic programs on screen off (problematic programs only). If you kill system apps or Facebook, etc, they'll keep restarting themselves and everytime this happens, more cpu time is consumed.
Widgets (battery, weather, news, etc) don't "drain" your battery. But of course they do make your phone "consume" a bit more battery. With widgets that update, you will see a lot of Alarm Manager wake counts in BBS, which is fine. Battery widget for instance, it polls your battery stay every minute or so, so an internal clock timer will be active at all times. But a several-hour-long cpu usage analysis will show minimal battery usage.
In my experience for fixingbmy own battery drain perceived, biggest killer is wifi on dlink router, latitude, and a few badly written apps that consume cpu even after quitting. All other stuff are not really battery drainers. Bottom line is, the more apps you install, the more battery is used. But 8 hours standby time, there's definitely a battery drain. If you don't touch you phone, expect no more than 2% drop an hour to be normal. My drops about 1.5% every 2 hours after careful tweaking.
Sent from my GT-I9100 using Tapatalk
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
Hi all,
Sorry for the question, but I would really appreciate help in understand if my wife's S2 battery is working OK.
The phone was used by me until a few days ago.
I gave it to her and did master reset.
The phone is 4.1.2 official.
She is complaining that the battery is draining really fast.
For example yesterday, the phone was connected to the charger until 4 in the night (charged to 100%).
Until 7 in the morning it was not used and with wifi/mobile data off.
In 7 in the evening she had about 15% left.
I will add that wifi/mobile data was on from 7 to 7 and when I looked at how much the screen was on, it was about 2.5 hours.
Is it normal? Does she expect too much?
I am also attaching log from last night. Phone was charged to 100%, reached 97% until we went to sleep and was left alone for about 7 hours (wifi/mobile data off).
In the morning it reached 88% (loss of 9%).
Is it normal? Shouldn't it be less?
Thank you so much!
Asaf
shemsha said:
Hi all,
Sorry for the question, but I would really appreciate help in understand if my wife's S2 battery is working OK.
The phone was used by me until a few days ago.
I gave it to her and did master reset.
The phone is 4.1.2 official.
She is complaining that the battery is draining really fast.
For example yesterday, the phone was connected to the charger until 4 in the night (charged to 100%).
Until 7 in the morning it was not used and with wifi/mobile data off.
In 7 in the evening she had about 15% left.
I will add that wifi/mobile data was on from 7 to 7 and when I looked at how much the screen was on, it was about 2.5 hours.
Is it normal? Does she expect too much?
I am also attaching log from last night. Phone was charged to 100%, reached 97% until we went to sleep and was left alone for about 7 hours (wifi/mobile data off).
In the morning it reached 88% (loss of 9%).
Is it normal? Shouldn't it be less?
Thank you so much!
Asaf
Click to expand...
Click to collapse
1) use 'Gemini app manager' to turn off autostart of 'Google map'
2) Use 'GSAM battery managment' app to see which app is causing batt drain while not in use.
3)turn of 'Location' service when not in use.
4)use 'CpuSpy' app to check 'Deepsleep' is Ok or not.
the above things will do help in bringing down the batt consumption for sure, if proper measures are taken accordingly.
I will try it, thanks a lot.
I just want to verify that the battery info I wrote in my post suggests a problem or it's more or less reasonable battery time?
I am now with the Nexus 4, and I am not comparing but with the same conditions as my wife's S2, mine lost about 2 percent at those 7 hours (when her's lost about 9).
Thanks.
Adding some info, hope it's OK.
I really want to understand if my battery has a problem, or this is just how the S2 is.
I am attaching BetterBatteryStats log of the S2 + one for my nexus 4 as reference (since it is in the same conditions) more or less. Also attached gSAM battery screenshots from the S2.
The log is form a different date but it's for about the same time range and hours.
Full logs are attached but I am also pasting a part here. From what I see, the usage is very similar, but while the S2 lost 12%, the nexus lost 3%.
Is there any chance my battery is bad? Can I somehow check it? Maybe by the voltage lost?
S2:
============
Battery Info
============
Level lost [%]: 12 Bat.: 12% (100% to 88%) [1.6%/h]
Voltage lost [mV]: 436 (4183-3747) [59.0%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 56 m 43 s (25003 s) Ratio: 93.9%
Awake (): 35 m 38 s (2138 s) Ratio: 8.0%
Screen On (): 2 m 5 s (125 s) Ratio: 0.5%
No Data Connection (): 7 h 23 m 42 s (26622 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 23 m 42 s (26622 s) Ratio: 100.0%
Screen dark (): 2 m 5 s (125 s) Ratio: 0.5%
Nexus 4:
============
Battery Info
============
Level lost [%]: 3 Bat.: 3% (100% to 97%) [0.4%/h]
Voltage lost [mV]: 9 (4250-4241) [1.3%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 23 m 39 s (23019 s) Ratio: 90.0%
Awake (): 42 m 44 s (2564 s) Ratio: 10.0%
Screen On (): 1 m 44 s (104 s) Ratio: 0.4%
Wifi On (): 1 m 22 s (82 s) Ratio: 0.3%
Wifi Running (): 1 m 22 s (82 s) Ratio: 0.3%
No Data Connection (): 7 h 6 m 22 s (25582 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 6 m 22 s (25582 s) Ratio: 100.0%
Screen dark (): 1 m 44 s (104 s) Ratio: 0.4%
shemsha said:
Adding some info, hope it's OK.
I really want to understand if my battery has a problem, or this is just how the S2 is.
I am attaching BetterBatteryStats log of the S2 + one for my nexus 4 as reference (since it is in the same conditions) more or less. Also attached gSAM battery screenshots from the S2.
The log is form a different date but it's for about the same time range and hours.
Full logs are attached but I am also pasting a part here. From what I see, the usage is very similar, but while the S2 lost 12%, the nexus lost 3%.
Is there any chance my battery is bad? Can I somehow check it? Maybe by the voltage lost?
S2:
============
Battery Info
============
Level lost [%]: 12 Bat.: 12% (100% to 88%) [1.6%/h]
Voltage lost [mV]: 436 (4183-3747) [59.0%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 56 m 43 s (25003 s) Ratio: 93.9%
Awake (): 35 m 38 s (2138 s) Ratio: 8.0%
Screen On (): 2 m 5 s (125 s) Ratio: 0.5%
No Data Connection (): 7 h 23 m 42 s (26622 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 23 m 42 s (26622 s) Ratio: 100.0%
Screen dark (): 2 m 5 s (125 s) Ratio: 0.5%
Nexus 4:
============
Battery Info
============
Level lost [%]: 3 Bat.: 3% (100% to 97%) [0.4%/h]
Voltage lost [mV]: 9 (4250-4241) [1.3%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 23 m 39 s (23019 s) Ratio: 90.0%
Awake (): 42 m 44 s (2564 s) Ratio: 10.0%
Screen On (): 1 m 44 s (104 s) Ratio: 0.4%
Wifi On (): 1 m 22 s (82 s) Ratio: 0.3%
Wifi Running (): 1 m 22 s (82 s) Ratio: 0.3%
No Data Connection (): 7 h 6 m 22 s (25582 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 6 m 22 s (25582 s) Ratio: 100.0%
Screen dark (): 1 m 44 s (104 s) Ratio: 0.4%
Click to expand...
Click to collapse
I've been experiencing the same problem with my SGS2's battery and noticed that it is getting bloated. I purchased a new one to prevent severe damage on my mobile phone.
{
"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"
}
Thanks, that was a problem my friend had, with mine I don't think that's the case. Anyway I ordered an anker battery and I will see if it helps.
Sent from my Nexus 7 using Tapatalk HD
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