Help me fix my AOSP battery woes -FIXED?!?!!? (see post 26) - AT&T Samsung Galaxy S II SGH-I777

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