• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [ROM][4.0.4] AOKP ICS B40/M6/Mods (7/8)

elmerjr128 said:
If anyone is experiencing battery life issues with Build 23, read on.

Build 23 has an issue with SDM chewing up battery life. If you have Better Battery Stats, you can see this in the partial wakelocks.

Simple fix - Use Titanium Backup to either freeze or delete SDM 1.0. If you don't have Titanium Backup (you should!) then you can navigate to system/apps and delete it there.

Also, don't forget to sign out of Google Talk! You are signed in by default after doing a factory reset and signing back into your Google account.

I froze SDM and signed out of Google Talk and my battery life is on par with, or better than the battery life I was getting on Milestone 3.
Click to expand...

I freeze SDM 1.0 with TiBu after each flash since M3. Thx for pointing this out. I leave Talk active though I need it active. Still super pleased with battery life I charge once every 2 days unless I have an abnormally heavy usage day.
 
otter said:
In and around the city yes, but now that I think about it yesterday it did say "miles" for the last turn, however I wasn't downtown at that time. I was in the suburbs
Click to expand...

So odd! So have you learned the metric system yet :p
 
jbdan said:
I freeze SDM 1.0 with TiBu after each flash since M3. Thx for pointing this out. I leave Talk active though I need it active. Still super pleased with battery life I charge once every 2 days unless I have an abnormally heavy usage day.
Click to expand...

Is freezing SDM required on M3? I don't see it showing up in BBS. Looks like google talk is 15% of my awake time :eek: I do occasionally use it, but I think I'll freeze it and see if battery improves.

Anyone see anything else "bad" in my BBS dump?

===================
General Information
===================
BetterBatteryStats version: 1.6.1.0
Creation Date: 2012-02-14 15:21:13
Statistic Type: (0) Since Charged
Since 14 h 12 m 52 s
VERSION.RELEASE: 4.0.3
BRAND: google
DEVICE: toro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
===========
Other Usage
===========
Wifi On (): 14 h 12 m 52 s (51172 s) Ratio: 100.0%
Awake (): 1 h 36 m 9 s (5769 s) Ratio: 11.3%
Screen On (): 23 m 52 s (1432 s) Ratio: 2.8%
Phone On (): 4 m 48 s (288 s) Ratio: 0.6%
=========
Wakelocks
=========
GTALK_ASYNC_CONN_josh.carroll@gmail.com/android_talk96f0e6b5f700 (Google Services): 7 m 19 s (439 s) Count:221 0.9%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 6 m 56 s (416 s) Count:272 0.8%
*backup* (Android System): 2 m 4 s (124 s) Count:673 0.2%
*sync*_gmail-ls_Account {name=josh.carroll@gmail.com, type=com.google} (com.google.android.gm.Gmail): 1 m 38 s (98 s) Count:73 0.2%
RILJ (Phone): 1 m 37 s (97 s) Count:384 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 1 m 31 s (91 s) Count:75 0.2%
ActivityManager-Launch (Android System): 1 m 12 s (72 s) Count:365 0.1%
Checkin Service (Google Services): 1 m 7 s (67 s) Count:388 0.1%
ConnectivityService (Android System): 56 s (56 s) Count:1829 0.1%
NetworkLocationLocator (Google Services): 53 s (53 s) Count:423 0.1%
SMSDispatcher (Phone): 48 s (48 s) Count:11 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 46 s (46 s) Count:27 0.1%
AudioOut_1 (1013): 39 s (39 s) Count:15 0.1%
AlarmManager (Android System): 34 s (34 s) Count:1806 0.1%
CDMA (Phone): 28 s (28 s) Count:390 0.1%
sleep_broadcast (Android System): 23 s (23 s) Count:643 0.0%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 s (15 s) Count:76 0.0%
GpsLocationProvider (Android System): 14 s (14 s) Count:495 0.0%
DownloadManager (Media): 12 s (12 s) Count:2 0.0%
GTALK_CONN (Google Services): 12 s (12 s) Count:1142 0.0%
NetworkStats (Android System): 9 s (9 s) Count:219 0.0%
StartingAlertService (com.android.mms.Messaging): 8 s (8 s) Count:29 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 7 s (7 s) Count:3 0.0%
TunnyBrowser (UID): 7 s (7 s) Count:2 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:521 0.0%
SCREEN_FROZEN (Android System): 6 s (6 s) Count:654 0.0%
SyncLoopWakeLock (Android System): 6 s (6 s) Count:2217 0.0%
*sync*_com.google.android.apps.plus.content.EsGooglePhotoProvider_Account {name=josh.carroll@gmail.com, type=com.google} (com.google.android.apps.plus.Google+): 5 s (5 s) Count:1 0.0%
*sync*_com.android.calendar_Account {name=josh.carroll@gmail.com, type=com.google} (com.google.android.calendar.Calendar): 3 s (3 s) Count:3 0.0%
*vibrator* (com.android.mms.Messaging): 2 s (2 s) Count:6 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1879 0.0%
*sync*_subscribedfeeds_Account {name=josh.carroll@gmail.com, type=com.google} (Google Services): 1 s (1 s) Count:1143 0.0%
*sync*_com.android.browser_Account {name=josh.carroll@gmail.com, type=com.google} (Google Services): 1 s (1 s) Count:1173 0.0%
*sync*_com.android.contacts_Account {name=josh.carroll@gmail.com, type=com.google} (Google Services): 1 s (1 s) Count:492 0.0%
================
Kernel Wakelocks
================
No reference since charged yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
=========
Processes
=========
mobi.mgeek.TunnyBrowser (UID): Sys: 1 s (1 s) Us: 16 s (16 s) Starts: 4
surfaceflinger (Android System): Sys: 3 s (3 s) Us: 2 s (2 s) Starts: 0
rild (Phone): Sys: 3 s (3 s) Us: 2 s (2 s) Starts: 0
com.android.mms (com.android.mms.Messaging): Sys: (0 s) Us: 3 s (3 s) Starts: 3
*wakelock* (Google Services): Sys: 1 s (1 s) Us: 1 s (1 s) Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Sys: (0 s) Us: 2 s (2 s) Starts: 2
/init (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
ksoftirqd/0 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Sys: (0 s) Us: 1 s (1 s) Starts: 1
kworker/u:2 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
mediaserver (1013): Sys: (0 s) Us: (0 s) Starts: 0
com.google.android.apps.maps:NetworkLocationService (com.google.android.apps.maps.Maps): Sys: (0 s) Us: (0 s) Starts: 3
======================
Alarms (requires root)
======================
No reference since charged yet (): Wakeups: 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 ActivityManager.RunningServiceInfo | Android Developers
com.android.smspush (com.android.smspush.WapPushManager)
Active since: 2 m 33 s
Last activity: 2 m 33 s
Crash count:0
com.android.phone (com.samsung.dmexthandler.PhoneDataService)
Active since: 2 m 38 s
Last activity: 1 h 39 m 6 s
Crash count:0
com.samsung.syncservice (com.samsung.syncservice.SyncmlService)
Active since: 2 m 38 s
Last activity: 1 h 45 m 59 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 2 m 33 s
Last activity: 2 m 33 s
Crash count:0
com.google.android.talk (com.google.android.videochat.VideoChatService)
Active since: 2 m 37 s
Last activity: 2 m 37 s
Crash count:0
com.TEST.android.lvh (com.TEST.android.lvh.AudioEffectsService)
Active since: 2 m 36 s
Last activity: 2 m 36 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 2 m 31 s
Last activity: 2 m 31 s
Crash count:0
com.preinvent.batteryleft (com.preinvent.batteryleft.BootUpService)
Active since: 2 m 41 s
Last activity: 1 h 58 m 4 s
Crash count:0
com.android.bip (com.android.bip.BIPService)
Active since: 2 m 36 s
Last activity: 1 h 35 m 2 s
Crash count:0
com.google.process.gapps (com.google.android.location.internal.server.NetworkLocationService)
Active since: 2 m 33 s
Last activity: 2 m 34 s
Crash count:0
br.com.bott.droidsshd (br.com.bott.droidsshd.system.DroidSSHdService)
Active since: 2 m 41 s
Last activity: 1 h 35 m 7 s
Crash count:0
com.sec.android.internal.ims (com.sec.android.internal.ims.IMSService)
Active since: 2 m 35 s
Last activity: 2 m 35 s
Crash count:0
com.noshufou.android.su (com.noshufou.android.su.service.ResultService)
Active since: 18 h 50 m 30 s
Last activity: 2 h 36 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 2 m 31 s
Last activity: 2 m 31 s
Crash count:0
com.google.android.apps.maps:NetworkLocationService (com.google.android.location.internal.server.NetworkLocationService)
Active since: 2 m 41 s
Last activity: 1 h 40 m 36 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 2 m 33 s
Last activity: 2 m 33 s
Crash count:0
com.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 2 m 32 s
Last activity: 1 h 42 m
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 2 m 32 s
Last activity: 2 m 32 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 2 m 37 s
Last activity: 1 h 57 m 48 s
Crash count:0
com.extendedcontrols (com.extendedcontrols.service.ECService)
Active since: 2 m 42 s
Last activity: 1 h 58 m 44 s
Crash count:0
Click to expand...
 
jkc120 said:
Is freezing SDM required on M3? I don't see it showing up in BBS. Looks like google talk is 15% of my awake time :eek: I do occasionally use it, but I think I'll freeze it and see if battery improves.

Anyone see anything else "bad" in my BBS dump?
Click to expand...

SDM has been causing wakelock issues on several ROM's afaik. It happens randomly, one build has it the next doesn't, and so on. So I freeze it. I have no clue if it has affected me, I just follow the gang ;)

Google Talk has been another one, but I use the video calling on it often and like to leave it active.

I gather all this while I read. I don't monitor my battery with all these apps that show wakelocks etc...I just use my phone through the day and see how it lasts for me.

Sorry I have no idea how to read all that betterbattstat stuff I've never used the app.
 
Geesh? What is SDM?

Anyway, I'm on M3 and found it in the system/app folder along with a SDM.apk.old file. I guess this was done by the ROM developer eh?
 
gapi said:
Geesh? What is SDM?

Anyway, I'm on M3 and found it in the system/app folder along with a SDM.apk.old file. I guess this was done by the ROM developer eh?
Click to expand...

Samsung Download Manager so I'm told. It has to do with OTA updates, which we'll never get anyways, so I freeze it with no ill effects. A lot of folk just uninstall it. Your choice. btw freeze it with TiBu. Open up TiBu, at the top tap "Backup/Restore" then scroll to SDM 1.0, click it and freeze it. You can defrost it later if you think you might need it.
 
gapi said:
Gotcha..... Does everyone have an SDM.apk.old file in the list also?
Click to expand...

I don't know. I just have one in the TiBu list. I've never looked for it in /system/app which is where I think it resides.

edit: just checked with root explorer yup I got the geezer one in there too
 
jbdan said:
SDM has been causing wakelock issues on several ROM's afaik. It happens randomly, one build has it the next doesn't, and so on. So I freeze it. I have no clue if it has affected me, I just follow the gang ;)

Google Talk has been another one, but I use the video calling on it often and like to leave it active.

I gather all this while I read. I don't monitor my battery with all these apps that show wakelocks etc...I just use my phone through the day and see how it lasts for me.

Sorry I have no idea how to read all that betterbattstat stuff I've never used the app.
Click to expand...

So, if you freeze Google Talk, is the messenger app part of G+ still functioning? I use G+ a lot, chat only occasionally, but I'm not sure if I could still do that with Talk frozen since G+ duplicates its functionality. Does that make any sense? I'm very tired.
 
quiklives said:
So, if you freeze Google Talk, is the messenger app part of G+ still functioning? I use G+ a lot, chat only occasionally, but I'm not sure if I could still do that with Talk frozen since G+ duplicates its functionality. Does that make any sense? I'm very tired.
Click to expand...

Makes total sense. I wouldn't freeze Talk though, I'd just sign out. A lot of people have experienced better deep sleep on their GN when signed out of Talk.
 
I don't know how I feel about the Button Savior nav buttons. Looks like they may be a pain to bring up sometimes. Definitely a cool mod, though!
 
elmerjr128 said:
I don't know how I feel about the Button Savior nav buttons. Looks like they may be a pain to bring up sometimes. Definitely a cool mod, though!
Click to expand...

Does look a little fidgety. I've seen several threads over the past month in the general GN forum asking "why can't I use the full screen?". This is new, maybe a feature that will be developed as time goes. Either way the full screen is gorgeous on the GN I love pulling up a HD youtube video for people in 1280x720
 
I flashed this Rom version 23 yesterday and before flashing it I hooked it up to my pc and transferred the files to my Gnex. Now, today I went to and hooked up my Gnex to the same pc and now that pc does not recognize my Gnex. Before flashing this Rom I was running CNA 1.0.2 and my Gnex would connect and show up every time on my Windows 7 pc.

Is there some kind of a setting in this Rom I have to turn on/off to make it work?
 
darkcyber said:
I flashed this Rom version 23 yesterday and before flashing it I hooked it up to my pc and transferred the files to my Gnex. Now, today I went to and hooked up my Gnex to the same pc and now that pc does not recognize my Gnex. Before flashing this Rom I was running CNA 1.0.2 and my Gnex would connect and show up every time on my Windows 7 pc.

Is there some kind of a setting in this Rom I have to turn on/off to make it work?
Click to expand...

Try turning on USB Debugging under Developer Options in the main phone settings menu.
 
darkcyber said:
I flashed this Rom version 23 yesterday and before flashing it I hooked it up to my pc and transferred the files to my Gnex. Now, today I went to and hooked up my Gnex to the same pc and now that pc does not recognize my Gnex. Before flashing this Rom I was running CNA 1.0.2 and my Gnex would connect and show up every time on my Windows 7 pc.

Is there some kind of a setting in this Rom I have to turn on/off to make it work?
Click to expand...

settings> storage> menu (3 dots)> usb computer connection> check MTP

This is just a minor overlook...it is disabled by default on B23, but is normally and will normally be enabled. I listed this in the OP next to the changelog :)
 
elmerjr128 said:
I don't know how I feel about the Button Savior nav buttons. Looks like they may be a pain to bring up sometimes. Definitely a cool mod, though!
Click to expand...

The app Button Savior makes everything a little laggy, but there is a nice work around. I've been running this mod for a couple hours now. The GN screen is impressive in it's full 1280 x 720 res. I'll post a thread on the MOD and how to use it ;)
 
jbdan said:
settings> storage> menu (3 dots)> usb computer connection> check MTP

This is just a minor overlook...it is disabled by default on B23, but is normally and will normally be enabled. I listed this in the OP next to the changelog :)
Click to expand...

MTP is what I was thinking of, not debugging. Thanks for clearing that up jbdan!
 
blkbeltkid17 said:
you you how could you do this to me AHHHHHHHHHHHHHHHHHHHHHH i almost started doing it the manual way and then i saw GSM ... you sir ... grrrr
Click to expand...


I wouldn't worry too much. Zaphod posted this over at Rootz a few min ago:

MaTHn.png
 
You must log in or register to reply here.
Back
Top Bottom