I got stock AT&T JB, rooted and installed TWRP. Removed all the bloat via TB Freeze (watching if anything breaks). I have slight hope that battery life could be a bit better, but not so. How's yours?
FYI, I don't play tons of games nor talk a lot on the phone, but I do use these, which I believe sucks battery regardless of what phone I use:
1). 3 Gmail accounts with Push
2). 1 Exchange account with Push
3). Google Now with Location Reporting - lots of wakelock unfortunately.
The phone does have "Deep Sleep", so no issue there.
I could say abouth 10 to 12 hour of use or less but I been getting 1 day of use on mine after the update. Take in mine i work in a office so I don use it much. Just few calls. Texting butbi do se netxflix during my lunch time
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
My battery has been not so good
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
From another thread I posted in;
I'm at 4 hours screen on time and 22 hours on battery with 18% remaining. On my second full charge cycle on this update. I fully charged last night and unplugged from charger. Checked 8 hours later and battery was at 96%. Deep sleeping well. Running stock un-rooted with about 40 apps disabled. My stock battery is fairly new, purchased about a month ago.
I just switched back to CM10 stable this morning...but I made a nandroid of my rooted stock. The battery life, from my little bit of time I had with it, was less than usual and the phone ran pretty hot.
shayneflashindaily said:
My battery has been not so good
Click to expand...
Click to collapse
I froze all the crap and used it for two days and I barely get through the day. And I'm a little more busy so I spend a little less time on phone activites.
I will say I noticed it charges pretty fast.
rsfinsrq said:
From another thread I posted in;
I'm at 4 hours screen on time and 22 hours on battery with 18% remaining. On my second full charge cycle on this update. I fully charged last night and unplugged from charger. Checked 8 hours later and battery was at 96%. Deep sleeping well. Running stock un-rooted with about 40 apps disabled. My stock battery is fairly new, purchased about a month ago.
Click to expand...
Click to collapse
That's really good batery life! I'll be lucky to get 2 hours screen yime with that much standby!
You mentioned new battery, maybe that's what I need to buy. My battery is about 11 months old.
lanwarrior said:
That's really good batery life! I'll be lucky to get 2 hours screen yime with that much standby!
You mentioned new battery, maybe that's what I need to buy. My battery is about 11 months old.
Click to expand...
Click to collapse
Without a doubt the health of the battery makes a big difference. The old battery did not last long and it would stop charging at 30-40%. I replaced the battery and charger (Both OEM) and it was like night and day! I was able to get a little over 5 hours screen time and over a day and a half standby on stock ICS. I'm hoping to get close with this rom after a few more charge cycles. (FYI, I avoid charging the battery or even plugging into a USB until I am able to fully charge the battery. I believe short intermittent charging negatively effects battery life/performance.)
These screenshots are from stock un-rooted 4.0.4 a few charge cycles after I replaced the battery and charger;
I ran into an issue today where my battery went down by about 50% in 3 hours will about 10mins time where the phone wasn't in standby, I went into battery and found that the media service had used almost half of that or around 25% of my battery. rebooted the phone and i'll see where it goes from there. prior to that battery life was fine.
rsfinsrq said:
(FYI, I avoid charging the battery or even plugging into a USB until I am able to fully charge the battery. I believe short intermittent charging negatively effects battery life/performance.)
Click to expand...
Click to collapse
Ah.. that's going to be tough for me. I drive a lot for work and use the Google Navigation. The phone is connected to the USB charger in the car on and off. I.e. 1 hour here...30 min there...
Lithium-ion batteries don't suffer from the memory issues of other battery types. Little bursts of charging won't shorten its life.
But a new battery should always be charged to 100% before using.
Battery wasn't as good as 4.0.4 rooted, debloated, running on Nova prime launcher. I have the exact same setup on 4.1.2. However, it seems to charge a bit faster.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
SKyRocKeting727 said:
Battery wasn't as good as 4.0.4 rooted, debloated, running on Nova prime launcher. I have the exact same setup on 4.1.2. However, it seems to charge a bit faster.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Yes! Thought it was only me. So weird but indeed it charges faster.
And honestly the battery life is about the same. Though I did remove lots of stuff and this is how my application screen looked before restoring all of my apps.
After I restored all the apps I left my phone during the night after full charge with 2 voip apps running. (though keep in mind I slept only for 6 hours and I use that cheap $10 extended battery):
Code:
Battery Info
============
Level lost [%]: Bat.: -6% (100% to 94%) [0.9%/h]
===========
Deep Sleep (): 6 h 13 m 11 s (22391 s) Ratio: 54.0%
Awake (): 10 m 9 s (609 s) Ratio: 2.6%
Screen On (): 3 m 20 s (200 s) Ratio: 0.9%
Wifi On (): 6 h 23 m 20 s (23000 s) Ratio: 100.0%
Wifi Running (): 6 h 23 m 20 s (23000 s) Ratio: 100.0%
No Data Connection (): 6 h 23 m 20 s (23000 s) Ratio: 100.0%
No or Unknown Signal (): 6 h 23 m 20 s (23000 s) Ratio: 100.0%
Screen dark (): (0 s) Ratio: 0.0%
Screen dimmed (): 3 m 20 s (200 s) Ratio: 0.9%
===========
CPU States
==========
384 MHz (): 6 m 9 s 1.6%
432 MHz (): 7 s 0.0%
486 MHz (): 15 s 0.1%
540 MHz (): 9 s 0.0%
594 MHz (): 15 s 0.1%
648 MHz (): 5 s 0.0%
702 MHz (): 3 s 0.0%
756 MHz (): 6 s 0.0%
810 MHz (): 26 s 0.1%
864 MHz (): 11 s 0.0%
918 MHz (): 9 s 0.0%
972 MHz (): 7 s 0.0%
1.03 GHz (): 14 s 0.1%
1.08 GHz (): 6 s 0.0%
1.13 GHz (): 5 s 0.0%
1.19 GHz (): 5 s 0.0%
1.24 GHz (): 1 m 4 s 0.3%
1.3 GHz (): 0.0%
1.35 GHz (): 1 s 0.0%
1.4 GHz (): 0.0%
1.46 GHz (): 0.0%
1.51 GHz (): 24 s 0.1%
Deep Sleep (): 6 h 13 m 11 s 54.0%
=========
rsfinsrq said:
Without a doubt the health of the battery makes a big difference. The old battery did not last long and it would stop charging at 30-40%. I replaced the battery and charger (Both OEM) and it was like night and day! I was able to get a little over 5 hours screen time and over a day and a half standby on stock ICS. I'm hoping to get close with this rom after a few more charge cycles. (FYI, I avoid charging the battery or even plugging into a USB until I am able to fully charge the battery. I believe short intermittent charging negatively effects battery life/performance.)
Click to expand...
Click to collapse
Both my current batteries still charges, it just don't last as long as I hoped to.
BTW, with the kind of battery life you got, are you running the following:
- Multiple GMail Push accounts
- Exchange accounts
- Google Now.
Just 1 Gmail (Using the email app, I disabled the Gmail apk), no exchange, and I am running Google Now. I do not run any memory intensive games, etc. Just web, Tapatalk, simple games, etc. A lot of screen time was spent setting up home screens, widgets, wallpaper, etc. Would be considered light use.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
rsfinsrq said:
Just 1 Gmail (Using the email app, I disabled the Gmail apk), no exchange, and I am running Google Now. I do not run any memory intensive games, etc. Just web, Tapatalk, simple games, etc. A lot of screen time was spent setting up home screens, widgets, wallpaper, etc. Would be considered light use.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the info. I have more background apps running as mentioned above (push emails, Exchange, etc.), so my battery life suffers. I am using an extended battery (thick one) and it doesn't last as long as I hoped to.
So far, it has been:
Battery level: 64%
Battery time: 9 hours, 30 minutes
Screen time: 2 hours, 21 minutes
FYI, this is how bad my battery life is...
Not sure if this is because of Google Now or the fact that I have multiple stuff going on in the background...
I have the same issue as you. The maps app is killing my battery. It is waking the phone every minute it seems. I unchecked all boxes in location services today and my battery is still at 80% with limited useage. What is causing maps to keep activating?
Agoattamer said:
I have the same issue as you. The maps app is killing my battery. It is waking the phone every minute it seems. I unchecked all boxes in location services today and my battery is still at 80% with limited useage. What is causing maps to keep activating?
Click to expand...
Click to collapse
I believe it is Google Now.
My battery drains even when I am using the phone while its plugged into USB wall charger. In general, 2 hours of steady use will drain 75% of my battery. I have 4 total batteries and get roughly the same performance from each.
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
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
Is this normal?
Ok, this is cleanrom 1.6.5 with KT's newest kernel. I have his settings applied. Over night it went from 95% to 85%, at that time i had 30 minutes of screen on.
Then I went to the gym and streamed google play music for about an hour with some web surfing and was using bluetooth headphones. It went from 85% to literally 55% in an hour. Also the screen was about 35% brightness.
Is that normal?? and now it just seems to keep draining. It's like over night it really wasn't at 85% when I work up and the battery just decided to drain all of a sudden when I started using the phone...
Help??
BossJ said:
Is this normal?
Ok, this is cleanrom 1.6.5 with KT's newest kernel. I have his settings applied. Over night it went from 95% to 85%, at that time i had 30 minutes of screen on.
Then I went to the gym and streamed google play music for about an hour with some web surfing and was using bluetooth headphones. It went from 85% to literally 55% in an hour. Also the screen was about 35% brightness.
Is that normal?? and now it just seems to keep draining. It's like over night it really wasn't at 85% when I work up and the battery just decided to drain all of a sudden when I started using the phone...
Help??
Click to expand...
Click to collapse
You should post a log from Better Battery Stats for us to look at for you. Your posted pics look fine to me though.
First set the app up. Hit the settings icon at the top right, scroll down and tap 'Dumpfile'. Check all of the boxes. Back in the settings, tap 'Advanced', and check 'Root features'. In Settings, tap 'Customize Views' and make sure all the boxes are checked. Now the app is setup.
You need to get a log of the phone from a 100% charged state down to about 5 - 20% left. Charge it up to 100, unplug it and open BBS. It will create a reference point of 'Unplugged' and begin logging your usage and what is using the battery, such as Wakelocks, Screen Activty, whether or not it Deep Sleeps properly, etc. Use your phone like you normally would, but don't reboot it or else the log resets, and you've lost the info so far. Once you're down to 5 - 20%, open BBS up, tap the 'Share' icon at the top right, in between the 'Refresh' and 'Settings' icons. 'Text Dumpfile' will be checked. Click 'Save' and it will save the txt log to the root of your internal SD. Post it.
King Ding-a-ling said:
You should post a log from Better Battery Stats for us to look at for you. Your posted pics look fine to me though.
First set the app up. Hit the settings icon at the top right, scroll down and tap 'Dumpfile'. Check all of the boxes. Back in the settings, tap 'Advanced', and check 'Root features'. In Settings, tap 'Customize Views' and make sure all the boxes are checked. Now the app is setup.
You need to get a log of the phone from a 100% charged state down to about 5 - 20% left. Charge it up to 100, unplug it and open BBS. It will create a reference point of 'Unplugged' and begin logging your usage and what is using the battery, such as Wakelocks, Screen Activty, whether or not it Deep Sleeps properly, etc. Use your phone like you normally would, but don't reboot it or else the log resets, and you've lost the info so far. Once you're down to 5 - 20%, open BBS up, tap the 'Share' icon at the top right, in between the 'Refresh' and 'Settings' icons. 'Text Dumpfile' will be checked. Click 'Save' and it will save the txt log to the root of your internal SD. Post it.
Click to expand...
Click to collapse
yeah. i'm running betterbatterystats. I'll load it up for you ... thanks for your help!
Here you go... It's at 40% battery though.
Seems to Deep Sleep properly:
Deep Sleep (): 8 h 32 m 8 s (30728 s) Ratio: 73.9%
You have some wakelocks that are holding the phone awake, even if the screen is off:
"PowerManagerService" (): 1 h 14 m 38 s (4478 s) Cntc/wc/ec)1125/0/0 10.8%
"deleted_wake_locks" (): 37 m 46 s (2266 s) Cntc/wc/ec)253928/0/1552 5.1%
"msm_hsic_host" (): 31 m 53 s (1913 s) Cntc/wc/ec)1178/145/0 4.6%
"bluesleep" (): 30 m 58 s (1858 s) Cntc/wc/ec)8/0/8 4.2%
"msm_serial_hs_dma" (): 30 m 57 s (1857 s) Cntc/wc/ec)13/0/0 4.2%
"msm_serial_hs_rx" (): 30 m 50 s (1850 s) Cntc/wc/ec)31/0/31 4.2%
I'm not exactly sure what some of them are.
Awake time compared to Screen-on:
Awake (): 3 h 1 m 4 s (10864 s) Ratio: 26.1%
Screen On (): 1 h 22 m 47 s (4967 s) Ratio: 11.9%
When you were at the gym listening to music, it was over LTE, that'll drain a good bit.
The phone was awake for 3 h 1 m 4 s, but the screen was only awake for just a little over an hour.
Screen-on used quite a bit, despite being dark, dimmed, or medium for most of it:
Screen dark (): 25 m 41 s (1541 s) Ratio: 3.7%
Screen dimmed (): 10 m 34 s (634 s) Ratio: 1.4%
Screen medium (): 40 m 28 s (2428 s) Ratio: 5.4%
Screen light (): 2 m 34 s (154 s) Ratio: 0.3%
Screen bright (): 3 m 28 s (208 s) Ratio: 0.5%
The SS shows the screen hit you hard.
Facebook is there:
FacebookService (com.facebook.katana.Facebook): 5 s (5 s) Count:10 0.0%
Chrome used quite a bit, despite not showing much usage:
com.android.chrome (com.android.chrome.Chrome): Uid: 10190 Sys: 22 s (22 s) Us: 1 m 5 s (65 s) Starts: 4
Google+ was using the Network quite a bit:
10175 (Wifi) (com.google.android.apps.plus.Google+): 394.0 MBytes 41.6%
Facebook was active for a long time:
com.sec.android.app.sns3 (com.sec.android.app.sns3.svc.sp.facebook.SnsFbService)
Active since: 10 h 4 m 28 s
Last activity: 3 h 46 m 1 s
Crash count:0
Bluetooth was on the whole time:
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 11 h 45 m 13 s
Last activity: 3 h 37 m 35 s
Crash count:0
I may have missed a few things but try this:
Don't flash again until it's figured out
Turn off Greenify then next time you reach 100% charge, and run the phone down to 5 - 20% without Greenify running in the background, get another log.
Don't use any battery saving or task manager apps
Turn off all Location Services, and go into individual apps, disabling it in there too.
Keep Bluetooth off unless you need it.
Use Auto-brightness
Ditch Facebook for Friendcaster Pro (Check PM)
Kernel:
Try Processor 'Asswax' or 'Row' and Scheduler 'Interactive'
Don't UV or OC
Lower your Min CPU Frequency
Hope this helps.
King Ding-a-ling said:
Seems to Deep Sleep properly:
Deep Sleep (): 8 h 32 m 8 s (30728 s) Ratio: 73.9%
You have some wakelocks that are holding the phone awake, even if the screen is off:
"PowerManagerService" (): 1 h 14 m 38 s (4478 s) Cntc/wc/ec)1125/0/0 10.8%
"deleted_wake_locks" (): 37 m 46 s (2266 s) Cntc/wc/ec)253928/0/1552 5.1%
"msm_hsic_host" (): 31 m 53 s (1913 s) Cntc/wc/ec)1178/145/0 4.6%
"bluesleep" (): 30 m 58 s (1858 s) Cntc/wc/ec)8/0/8 4.2%
"msm_serial_hs_dma" (): 30 m 57 s (1857 s) Cntc/wc/ec)13/0/0 4.2%
"msm_serial_hs_rx" (): 30 m 50 s (1850 s) Cntc/wc/ec)31/0/31 4.2%
I'm not exactly sure what some of them are.
Awake time compared to Screen-on:
Awake (): 3 h 1 m 4 s (10864 s) Ratio: 26.1%
Screen On (): 1 h 22 m 47 s (4967 s) Ratio: 11.9%
When you were at the gym listening to music, it was over LTE, that'll drain a good bit.
The phone was awake for 3 h 1 m 4 s, but the screen was only awake for just a little over an hour.
Screen-on used quite a bit, despite being dark, dimmed, or medium for most of it:
Screen dark (): 25 m 41 s (1541 s) Ratio: 3.7%
Screen dimmed (): 10 m 34 s (634 s) Ratio: 1.4%
Screen medium (): 40 m 28 s (2428 s) Ratio: 5.4%
Screen light (): 2 m 34 s (154 s) Ratio: 0.3%
Screen bright (): 3 m 28 s (208 s) Ratio: 0.5%
The SS shows the screen hit you hard.
Facebook is there:
FacebookService (com.facebook.katana.Facebook): 5 s (5 s) Count:10 0.0%
Chrome used quite a bit, despite not showing much usage:
com.android.chrome (com.android.chrome.Chrome): Uid: 10190 Sys: 22 s (22 s) Us: 1 m 5 s (65 s) Starts: 4
Google+ was using the Network quite a bit:
10175 (Wifi) (com.google.android.apps.plus.Google+): 394.0 MBytes 41.6%
Facebook was active for a long time:
com.sec.android.app.sns3 (com.sec.android.app.sns3.svc.sp.facebook.SnsFbService)
Active since: 10 h 4 m 28 s
Last activity: 3 h 46 m 1 s
Crash count:0
Bluetooth was on the whole time:
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 11 h 45 m 13 s
Last activity: 3 h 37 m 35 s
Crash count:0
I may have missed a few things but try this:
Don't flash again until it's figured out
Turn off Greenify then next time you reach 100% charge, and run the phone down to 5 - 20% without Greenify running in the background, get another log.
Don't use any battery saving or task manager apps
Turn off all Location Services, and go into individual apps, disabling it in there too.
Keep Bluetooth off unless you need it.
Use Auto-brightness
Ditch Facebook for Friendcaster Pro (Check PM)
Kernel:
Try Processor 'Asswax' or 'Row' and Scheduler 'Interactive'
Don't UV or OC
Lower Vibration settings some
Hope this helps.
Click to expand...
Click to collapse
Wow great response!!! Seriously, thank you so much! I'll try everything you said!
BossJ said:
Wow great response!!! Seriously, thank you so much! I'll try everything you said!
Click to expand...
Click to collapse
NP man, check your PM box too.
So friendcaster is better than fb app itself eh?
Coderedpl said:
So friendcaster is better than fb app itself eh?
Click to expand...
Click to collapse
It's definately a lot easier on the battery... Try it out, there's a free version...
King Ding-a-ling said:
It's definately a lot easier on the battery... Try it out, there's a free version...
Click to expand...
Click to collapse
Will do
My phone has 4-6%/h battery eating, don't know what it is.
Already reset stweaks, use other settings but still eats battery.
on bbs it says on kernel wakelock:
PowerManagerService.WakeLockks
21 minutes
(there are more, but below 7 min)
Partial WakeLocks:
AudioMix
8 min
(there are more, but below 2 min)
Alarms:
Android: 115 wakeups
com.google.android.gms: 107 wakeups
Whatsapp: 51 wakelocks
(more under 40)
CPU speed:
mostly deepsleep, 200mhz, 800mhz, 400mhz)
Screen on: 1h 50min
Wifi on & running: 10h 50min
Deepsleep: 8h 10m
Awake: 2h 45min
I don't know how to fix these issues.
ps: I am using 2G network (no data) to save battery..
GreekBlood said:
My phone has 4-6%/h battery eating, don't know what it is.
Already reset stweaks, use other settings but still eats battery.
on bbs it says on kernel wakelock:
PowerManagerService.WakeLockks
21 minutes
(there are more, but below 7 min)
Partial WakeLocks:
AudioMix
8 min
(there are more, but below 2 min)
Alarms:
Android: 115 wakeups
com.google.android.gms: 107 wakeups
Whatsapp: 51 wakelocks
(more under 40)
CPU speed:
mostly deepsleep, 200mhz, 800mhz, 400mhz)
Screen on: 1h 50min
Wifi on & running: 10h 50min
Deepsleep: 8h 10m
Awake: 2h 45min
I don't know how to fix these issues.
ps: I am using 2G network (no data) to save battery..
Click to expand...
Click to collapse
ty factory reset or firmware update
bhavstech said:
ty factory reset or firmware update
Click to expand...
Click to collapse
I had this exact problem on RR, then moved to Carbon with fresh install.
I think it was dorimanx kernel, with apolo I get less %/h