1. Download our Official Android App: Forums for Android!

S2 munchin CPU

Discussion in 'Android Devices' started by jsw666, Oct 25, 2012.

  1. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    Galaxy S2 GTI9100
    4.04
    siyah 6.0b2+
    neat rom lite 3.5

    Ive been trying to track down why my phone barely if ever goes onto deep sleep and constantly uses cpu.
    better battery stats shows some general wakelocks which never covers the whole time its not in deep sleep.
    This seems to be the same using different roms/kernels.
    Heres a task manager cpu log.

    SEQ:0 201210251634
    system[2235]: 13.90%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
    com.sec.android.app.controlpanel[9265]: 5.88%
    ---[0]com.sec.android.app.controlpanel
    surfaceflinger[1907]: 4.28%
    com.sec.android.app.twlauncher[3566]: 1.60%
    ---[0]com.sec.android.app.twlauncher
    com.sec.android.inputmethod.axt9[3533]: 1.07%
    ---[0]com.sec.android.inputmethod.axt9


    SEQ:1 201210251635
    system[2235]: 18.25%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
    com.sec.android.app.controlpanel[9265]: 2.19%
    ---[0]com.sec.android.app.controlpanel


    SEQ:2 201210251635
    com.sec.android.app.controlpanel[9265]: 2.79%
    ---[0]com.sec.android.app.controlpanel
    system[2235]: 1.68%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
    keystore[1914]: 0.56%
    com.android.phone[3553]: 0.56%
    ---[0]com.android.stk
    ---[1]com.samsung.sec.android.application.csc
    ---[2]com.android.providers.telephony
    ---[3]com.sec.android.app.bluetoothtest
    ---[4]com.android.phone


    SEQ:3 201210251636
    com.sec.android.app.controlpanel[9265]: 2.35%
    ---[0]com.sec.android.app.controlpanel
    system[2235]: 1.41%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
    even.Z7.service[6144]: 0.94%
    s3c-fb-vsync[710]: 0.47%
    ueventd[1249]: 0.47%


    SEQ:4 201210251636
    com.sec.android.app.controlpanel[9265]: 22.22%
    ---[0]com.sec.android.app.controlpanel
    system[2235]: 11.11%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings


    SEQ:5 201210251637
    com.sec.android.app.controlpanel[9265]: 4.17%
    ---[0]com.sec.android.app.controlpanel
    system[2235]: 1.67%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
    init[1]: 0.83%
    com.android.contacts[5479]: 0.83%
    ---[0]com.android.contacts


    SEQ:6 201210251638
    com.sec.android.app.controlpanel[9265]: 5.61%
    ---[0]com.sec.android.app.controlpanel
    system[2235]: 1.87%
    ---[0]com.android.providers.security
    ---[1]android
    ---[2]com.android.providers.settings
     

    Advertisement

  2. ExtremeNerd

    ExtremeNerd Android Enthusiast
    Rank:
    None
    Points:
    93
    Posts:
    744
    Joined:
    Aug 7, 2012

    Aug 7, 2012
    744
    237
    93
    Male
    IT Staff Accountant
    STL
    Since you're running a custom ROM, it would be best to bring your issues with it to the developer int he ROM's thread. This isn't something we can easily support since it isn't mainstream software.
     
  3. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    As i said, i get this with any custom or stock rom.
     
  4. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    ===================
    General Information
    ===================
    BetterBatteryStats version: 1.11.0.0RC7
    Creation Date: 2012-10-26 11:18:50
    Statistic Type: (6) Since Boot
    Since 1 h 2 m 24 s
    VERSION.RELEASE: 4.0.4
    BRAND: samsung
    DEVICE: GT-I9100
    MANUFACTURER: samsung
    MODEL: GT-I9100
    OS.VERSION: 3.0.31-Siyah-s2-v5.0b2+
    BOOTLOADER: unknown
    HARDWARE: smdk4210
    FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.4/IMM76D/XWLPY:user/release-keys
    ID: IMM76D
    TAGS: release-keys
    USER: dpi
    PRODUCT: GT-I9100
    RADIO: I9100XXLPX
    Rooted: true
    ============
    Battery Info
    ============
    Level lost [%]: 11 Bat.: 11% (100% to 89%) [10.6%/h]
    Voltage lost [mV]: 180 (4124-3944)
    ===========
    Other Usage
    ===========
    Awake (): 1 h 2 m 23 s (3743 s) Ratio: 100.0%
    Screen On (): 9 m 23 s (563 s) Ratio: 15.0%
    Good Signal (): 19 s (19 s) Ratio: 0.5%
    Deep Sleep (): (0 s) Ratio: 0.0%
    =========
    Wakelocks
    =========
    ActivityManager-Launch (Android System): 12 s (12 s) Count:133 0.3%
    RILJ (Phone): 8 s (8 s) Count:247 0.2%
    GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 8 s (8 s) Count:28 0.2%
    BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 7 s (7 s) Count:9 0.2%
    AlarmManager (Android System): 6 s (6 s) Count:246 0.2%
    Browser (com.android.browser.Internet): 6 s (6 s) Count:1 0.2%
    AudioOut_1 (1013): 4 s (4 s) Count:2 0.1%
    NetworkStats (Android System): 3 s (3 s) Count:91 0.1%
    MediaScannerService (Media): 3 s (3 s) Count:3 0.1%
    sleep_broadcast (Android System): 3 s (3 s) Count:16 0.1%
    show keyguard (Android System): 1 s (1 s) Count:24 0.0%
    ===================================
    Kernel Wakelocks (!!! discrete !!!)
    ===================================
    "sec-battery-monitor" (): 6 m 57 s (417 s) Cnt:(c/wc/ec)1229/1206/0 10.9%
    "l2_hsic" (): 5 m 8 s (308 s) Cnt:(c/wc/ec)1380/1/1380 8.1%
    "radio-interface" (): 1 m 20 s (80 s) Cnt:(c/wc/ec)84/0/0 2.1%
    "suspend_backoff" (): 17 s (17 s) Cnt:(c/wc/ec)2/0/2 0.5%
    "multipdp" (): 16 s (16 s) Cnt:(c/wc/ec)3/0/3 0.4%
    "alarm" (): 14 s (14 s) Cnt:(c/wc/ec)29/20/0 0.4%
    "alarm_rtc" (): 7 s (7 s) Cnt:(c/wc/ec)10/0/4 0.2%
    "PowerManagerService" (): 4 s (4 s) Cnt:(c/wc/ec)7/0/0 0.1%
    "secril_fd-interface" (): 3 s (3 s) Cnt:(c/wc/ec)2/0/0 0.1%
    "tx_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)4/0/0 0.0%
    "AudioOutLock" (): (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
    "sync_system" (): (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
    "rpm_hsic" (): (0 s) Cnt:(c/wc/ec)3/0/0 0.0%
    ======================
    Alarms (requires root)
    ======================
    com.sec.android.app.controlpanel (): Wakeups: 10
    Alarms: 10, Intent: com.sec.android.app.controlpanel.intent.RUN

    com.google.android.gsf (): Wakeups: 9
    Alarms: 1, Intent: com.google.android.intent.action.MCS_HEARTBEAT
    Alarms: 6, Intent: com.google.android.intent.action.SEND_IDLE

    com.android.vending (): Wakeups: 2

    com.google.android.apps.maps (): Wakeups: 1

    ======================
    Network (requires root)
    ======================
    10059 (Mobile) (com.android.browser.Internet): 3.0 MBytes 94.7%
    0 (Mobile) (0): 90.0 KBytes 2.3%
    10051 (Mobile) (com.android.vending.Google Play Store): 40.0 KBytes 1.0%
    10031 (Mobile) (com.google.android.googlequicksearchbox.Google Search): 33.0 KBytes 0.9%
    10010 (Mobile) (Google Services): 20.0 KBytes 0.5%
    10079 (Mobile) (com.google.android.youtube.YouTube): 11.0 KBytes 0.3%
    10090 (Mobile) (com.dropbox.android.Dropbox): 9.0 KBytes 0.2%
    ==========
    CPU States
    ==========
    1.6 GHz (): 0.0%
    1.5 GHz (): 0.0%
    1.4 GHz (): 0.0%
    1.3 GHz (): 0.0%
    1.2 GHz (): 2 m 18 s 3.7%
    1.1 GHz (): 7 s 0.2%
    1 GHz (): 13 s 0.4%
    900 MHz (): 18 s 0.5%
    800 MHz (): 22 m 25 s 35.7%
    700 MHz (): 30 s 0.8%
    600 MHz (): 9 s 0.2%
    500 MHz (): 1 m 26 s 2.3%
    400 MHz (): 5 m 20 s 8.5%
    300 MHz (): 0.0%
    200 MHz (): 29 m 59 s 47.7%
    100 MHz (): 0.0%
    Deep Sleep (): 0.0%
    ==================
    Reference overview
    ==================
    Custom: Reference custom_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since charged: Reference since_charged_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since screen off: Reference since_screen_off created 1 h 3 m 19 s (Wl: 15 elements; KWl: 13elements; NetS: 8 elements; Alrm: 5 elements; Proc: 9 elements; Oth: 6 elements; CPU: 17 elements)
    Since unplugged: Reference since_unplugged_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since boot: Reference since_boot created 46 s (Wl: 6 elements; KWl: 0elements; NetS: 3 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 4 elements; CPU: 17 elements)
     
  5. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    Does anyone have any ideas?
     
  6. Hawker

    Hawker Android Expert
    Rank:
     #50
    Points:
    433
    Posts:
    4,096
    Joined:
    Aug 2, 2011

    Aug 2, 2011
    4,096
    1,911
    433
    Male
    UK
    Try taking your battery out for 3 minutes then reboot
     
  7. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    Still the same:-(
    In battery settings, Android OS keep awake is usually the amount of time the phones been on..
     
  8. Hawker

    Hawker Android Expert
    Rank:
     #50
    Points:
    433
    Posts:
    4,096
    Joined:
    Aug 2, 2011

    Aug 2, 2011
    4,096
    1,911
    433
    Male
    UK
    What firmware were you on before Neat?
    did you do a full wipe prior to Neat?

    The problem appears to be with the program that actually monitors your battery usage.

    I would take a CWM backup then do a full wipe (eg run my GS2ROMWipe script) then flash XWLPY STOCK ROM from SamMobile through Odin. Make sure the reboot option is not ticked, so when the firmware has flashed, flash Siyah 4.1.4. (the .tar version) This will auto root on boot. then reboot into CWM recovery to flash Neat
     
  9. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    Thanks for the advice, i will give it a try.
    Although I dont think it will make a difference as I have the same problem running resurection remix on a 2nd rom which im guessing would be a completely clean install apart from sharing the same kernel?

    I have done a full wipe prior to neat coming from a stock rom.
     
  10. Hawker

    Hawker Android Expert
    Rank:
     #50
    Points:
    433
    Posts:
    4,096
    Joined:
    Aug 2, 2011

    Aug 2, 2011
    4,096
    1,911
    433
    Male
    UK
    A full wipe, maybe, but not a fresh install from stock firmware via odin. There IS a difference.
     
  11. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    I am going to give this a go and hope for the best.

    Where can I get XWLPY stock rom?
    The latest stock rom I can find for my country/carrier on SamMobile is I900VODLPB 4.0.3.

    Edit: found I9100XWLPY_I9100H3GLP7_H3G.zip, but not sure what H3G is :-/

    If I reboot into CWM recovery and run your rom-wipe script, how do I get from there to download mode to flash the stock rom? Do I just remove the battery?

    Oh and do you think I should run the Rom Wipe or Nuke to be sure?

    Thanks again..
     
  12. Hawker

    Hawker Android Expert
    Rank:
     #50
    Points:
    433
    Posts:
    4,096
    Joined:
    Aug 2, 2011

    Aug 2, 2011
    4,096
    1,911
    433
    Male
    UK
    If you run ROMWipe or ROMNuke, that's up to you. All the information is in the thread mate.

    Once you have run either, then just run the reboot option in CWM and during the reboot hold VOL-DOWN+HOME+POWER to get into download mode to allow an Odin flash
     
  13. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    SamMobile Firmware Page

    This seems to be the latest and correct stock rom for me in the UK..
    Can i use this or does it have to be XWLPY?
     
  14. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    I tried what you said Hawker, but it hasnt made any difference.
    I used the I9100XWLPT stock rom that i mentioned in my previous post and RomNuke
    I have disabled everything I can think might be causing this but ive ran out of ideas.
    In settings-battery, it generally shows as sleeping when it should be but cpu spy and bbs shows less than 5% over times when nothing should be running. gsam shows high percentages from kernel and android system which includes lots of kworkers.
    il let it run out and post another bbs log.
     
  15. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
    ===================
    General Information
    ===================
    BetterBatteryStats version: 1.11.0.0RC7
    Creation Date: 2012-11-11 12:43:59
    Statistic Type: (6) Since Boot
    Since 2 h 35 m 42 s
    VERSION.RELEASE: 4.0.4
    BRAND: samsung
    DEVICE: GT-I9100
    MANUFACTURER: samsung
    MODEL: GT-I9100
    OS.VERSION: 3.0.15-Siyah-s2-v4.1.5+
    BOOTLOADER: unknown
    HARDWARE: smdk4210
    FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.4/IMM76D/XWLPY:user/release-keys
    ID: IMM76D
    TAGS: release-keys
    USER: dpi
    PRODUCT: GT-I9100
    RADIO: I9100NELP4
    Rooted: true
    ============
    Battery Info
    ============
    Level lost [%]: 44 Bat.: 44% (96% to 52%) [17.0%/h]
    Voltage lost [mV]: 266 (4002-3736)
    ===========
    Other Usage
    ===========
    No Data Connection (): 2 h 35 m 42 s (9342 s) Ratio: 100.0%
    No or Unknown Signal (): 2 h 35 m 42 s (9342 s) Ratio: 100.0%
    Awake (): 2 h 25 m 6 s (8706 s) Ratio: 93.2%
    Screen On (): 23 m 18 s (1398 s) Ratio: 15.0%
    Wifi On (): 23 m 15 s (1395 s) Ratio: 14.9%
    Wifi Running (): 23 m 12 s (1392 s) Ratio: 14.9%
    Deep Sleep (): 10 m 35 s (635 s) Ratio: 6.8%
    Phone On (): 2 m 41 s (161 s) Ratio: 1.7%
    =========
    Wakelocks
    =========
    AudioOut_1 (1013): 4 m 7 s (247 s) Count:29 3.4%
    android.media.MediaPlayer (com.sec.android.app.music.Music player): 1 m 59 s (119 s) Count:2 1.6%
    MusicPlayer-Sleep (com.sec.android.app.music.Music player): 1 m 59 s (119 s) Count:1 1.6%
    ConnectivityService (Android System): 1 m 55 s (115 s) Count:479 1.6%
    RILJ (Phone): 23 s (23 s) Count:182 0.3%
    ActivityManager-Launch (Android System): 21 s (21 s) Count:140 0.3%
    FacebookService (com.facebook.katana.Facebook): 19 s (19 s) Count:5 0.3%
    BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 19 s (19 s) Count:19 0.3%
    SMSDispatcher (Phone): 13 s (13 s) Count:6 0.2%
    DownloadManager (Media): 13 s (13 s) Count:4 0.2%
    Browser (com.android.browser.Internet): 12 s (12 s) Count:2 0.2%
    AlarmManager (Android System): 11 s (11 s) Count:463 0.2%
    StartingAlertService (com.android.mms.Messaging): 11 s (11 s) Count:23 0.2%
    DHCP (Android System): 8 s (8 s) Count:226 0.1%
    sleep_broadcast (Android System): 7 s (7 s) Count:208 0.1%
    NetworkStats (Android System): 5 s (5 s) Count:82 0.1%
    MediaScannerService (Media): 5 s (5 s) Count:2 0.1%
    WifiStateMachine (Android System): 4 s (4 s) Count:231 0.1%
    GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 s (2 s) Count:48 0.0%
    show keyguard (Android System): 2 s (2 s) Count:12 0.0%
    PhoneWindowManager.mBroadcastWakeLock (Android System): 2 s (2 s) Count:162 0.0%
    GSM (Phone): 2 s (2 s) Count:8 0.0%
    reset keyguard (Android System): 1 s (1 s) Count:216 0.0%
    SCREEN_FROZEN (Android System): 1 s (1 s) Count:223 0.0%
    Event Log Service (Google Services): 1 s (1 s) Count:7 0.0%
    ================
    Kernel Wakelocks
    ================
    "l2_hsic" (): 44 m 57 s (2697 s) Cnt:(c/wc/ec)5383/9/5383 28.7%
    "sec-battery-monitor" (): 30 m 52 s (1852 s) Cnt:(c/wc/ec)5299/5139/0 19.7%
    "PowerManagerService" (): 6 m 26 s (386 s) Cnt:(c/wc/ec)472/0/0 4.1%
    "power-supply" (): 3 m 37 s (217 s) Cnt:(c/wc/ec)5300/0/0 2.3%
    "radio-interface" (): 1 m 28 s (88 s) Cnt:(c/wc/ec)122/0/0 0.9%
    "alarm" (): 1 m 18 s (78 s) Cnt:(c/wc/ec)245/41/0 0.8%
    "umts_ipc0" (): 1 m 10 s (70 s) Cnt:(c/wc/ec)189/0/189 0.8%
    "wlan_rx_wake" (): 47 s (47 s) Cnt:(c/wc/ec)88/0/88 0.5%
    "alarm_rtc" (): 23 s (23 s) Cnt:(c/wc/ec)28/0/10 0.3%
    "suspend_backoff" (): 19 s (19 s) Cnt:(c/wc/ec)2/0/2 0.2%
    "AudioOutLock" (): 7 s (7 s) Cnt:(c/wc/ec)27/0/0 0.1%
    "wlan_wake" (): 4 s (4 s) Cnt:(c/wc/ec)13679/14/0 0.0%
    "sync_system" (): 3 s (3 s) Cnt:(c/wc/ec)18/0/0 0.0%
    "tx_hsic" (): 2 s (2 s) Cnt:(c/wc/ec)1983/0/0 0.0%
    "rpm_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)103/0/0 0.0%
    "prx_wake_lock" (): 1 s (1 s) Cnt:(c/wc/ec)2/0/2 0.0%
    "vib_present" (): 1 s (1 s) Cnt:(c/wc/ec)10/0/0 0.0%
    "mmc1_detect" (): (0 s) Cnt:(c/wc/ec)5286/0/0 0.0%
    "secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)1563/0/0 0.0%
    "KeyEvents" (): (0 s) Cnt:(c/wc/ec)13381/0/0 0.0%
    "mmc0_detect" (): (0 s) Cnt:(c/wc/ec)5286/0/1 0.0%
    "event4-2159" (system, eu.chainfire.supersu): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
    "ApmCommandThread" (): (0 s) Cnt:(c/wc/ec)93/0/0 0.0%
    ======================
    Alarms (requires root)
    ======================
    com.google.android.gsf (): Wakeups: 18
    Alarms: 2, Intent: com.google.android.intent.action.GTALK_RECONNECT
    Alarms: 11, Intent: com.google.android.intent.action.SEND_IDLE

    com.facebook.katana (): Wakeups: 4
    Alarms: 1, Intent: com.facebook.katana.service.8
    Alarms: 1, Intent: com.facebook.katana.service.31
    Alarms: 1, Intent: com.facebook.katana.service.7
    Alarms: 1, Intent: com.facebook.katana.service.6
    Alarms: 1, Intent: com.facebook.katana.service.12
    Alarms: 1, Intent: com.facebook.katana.service.24

    com.android.vending (): Wakeups: 3

    com.fingersoft.hillclimb (): Wakeups: 2

    android (): Wakeups: 2
    Alarms: 157, Intent: android.intent.action.TIME_TICK
    Alarms: 5, Intent: com.android.server.action.NETWORK_STATS_POLL
    Alarms: 2, Intent: android.content.syncmanager.SYNC_ALARM
    Alarms: 15, Intent: com.android.server.ThrottleManager.action.POLL

    com.sec.android.providers.downloads (): Wakeups: 1
    Alarms: 1, Intent: android.intent.action.DOWNLOAD_WAKEUP

    ======================
    Network (requires root)
    ======================
    1013 (Wifi) (1013): 25.0 MBytes 31.3%
    10019 (Wifi) (Media): 22.0 MBytes 28.4%
    10059 (Wifi) (com.android.vending.Google Play Store): 17.0 MBytes 21.7%
    10074 (Wifi) (com.android.browser.Internet): 12.0 MBytes 16.0%
    0 (Wifi) (0): 1.0 MBytes 1.4%
    10030 (Wifi) (com.facebook.katana.Facebook): 565.0 KBytes 0.7%
    1019 (Wifi) (1019): 323.0 KBytes 0.4%
    10066 (Wifi) (com.dropbox.android.Dropbox): 79.0 KBytes 0.1%
    10012 (Wifi) (Google Services): 10.0 KBytes 0.0%
    10065 (Wifi) (com.fingersoft.hillclimb.Hill Climb Racing): 8.0 KBytes 0.0%
    10062 (Wifi) (com.gsamlabs.bbm.GSam Battery Monitor): 4.0 KBytes 0.0%
    10047 (Wifi) (com.mxtech.videoplayer.ad.MX Player): 3.0 KBytes 0.0%
    1000 (Wifi) (Android System): 1.0 KBytes 0.0%
    ==========
    CPU States
    ==========
    1.6 GHz (): 0.0%
    1.5 GHz (): 0.0%
    1.4 GHz (): 0.0%
    1.3 GHz (): 0.0%
    1.2 GHz (): 4 m 33 s 2.9%
    1.1 GHz (): 18 s 0.2%
    1 GHz (): 1 m 5 s 0.7%
    900 MHz (): 13 s 0.1%
    800 MHz (): 23 m 1 s 14.8%
    700 MHz (): 1 m 6 s 0.7%
    600 MHz (): 25 s 0.3%
    500 MHz (): 1 h 36 m 45 s 62.0%
    400 MHz (): 0.0%
    300 MHz (): 0.0%
    200 MHz (): 17 m 51 s 11.5%
    100 MHz (): 0.0%
    Deep Sleep (): 10 m 35 s 6.8%
    ==================
    Reference overview
    ==================
    Custom: Reference custom_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since charged: Reference since_charged_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since screen off: Reference since_screen_off created 2 h 30 m 41 s (Wl: 26 elements; KWl: 22elements; NetS: 13 elements; Alrm: 7 elements; Proc: 48 elements; Oth: 8 elements; CPU: 17 elements)
    Since unplugged: Reference since_unplugged_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
    Since boot: Reference since_boot created 44 s (Wl: 6 elements; KWl: 0elements; NetS: 3 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 6 elements; CPU: 17 elements)
     
  16. jsw666

    jsw666 Newbie
    Thread Starter
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Sep 22, 2012

    Sep 22, 2012
    20
    0
    15
  17. Dieben

    Dieben Android Enthusiast
    Rank:
    None
    Points:
    43
    Posts:
    258
    Joined:
    Sep 25, 2012

    Sep 25, 2012
    258
    41
    43
    TMI - Too Much Information :D

    "App Usage" (App Sucker) in GSam Battery Monitor presents simpler listings.

    Use the dropdown triangle at the upper right to select "View time held awake" and "View num times waking device"

    Click on the individual items in the lists for detailed information.
     

    Attached Files:

  18. TheChief657

    TheChief657 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    4
    Joined:
    Aug 10, 2012

    Aug 10, 2012
    4
    0
    5
    Hi
    I'm getting the same issue with my S2, the L2_HSIC process is causing the battery to only last around 12 hours at a time. Have looked online and not found any solution to it, the process seems to be tied in with the 3G/WiFi connectivity but I have not found a way of stopping it from running so the phone can go into deep sleep. Any advice or potential fixes would be appreciated
     

Share This Page

Loading...