I need a little help. I just ran PowerTOP and my wakeups-from-idle are super high. What can I do to reduce these? I'm currently running Fresh Evo 0.5.3 and everything is great with the exception of pretty poor battery life. I have to think that the high number of W-F-I is the reason, but I am not well versed in Linux or PowerTOP and I'm not sure what I can to to reduce these. On the report there are tips on what can be done, but as I'm not really sure what they mean, they might as well be written in Latin.
{
"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"
}
BB15 said:
I need a little help. I just ran PowerTOP and my wakeups-from-idle are super high. What can I do to reduce these? I'm currently running Fresh Evo 0.5.3 and everything is great with the exception of pretty poor battery life. I have to think that the high number of W-F-I is the reason, but I am not well versed in Linux or PowerTOP and I'm not sure what I can to to reduce these. On the report there are tips on what can be done, but as I'm not really sure what they mean, they might as well be written in Latin.
Click to expand...
Click to collapse
here is my powertop. Similar prob as you are having....
friggin audiotrack and gp timer.... bastards!!!
Code:
Wakeups-from-idle per second : 722.3 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
56.1% (392.6) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)
39.6% (277.1) <interrupt> : gp_timer
0.7% ( 5.2) <interrupt> : msm_i2c
0.7% ( 5.1) <interrupt> : msm_hsusb
0.4% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
0.3% ( 2.1) WebViewCoreThre : futex_wait (hrtimer_wakeup)
0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)
Curious too as to what the tweaks are to get it into the 50-80 range.
Mine is at 369.3 with top 2:
34.0% (114.0) <interrupt> : msm_i2c
22.3% ( 75.0) <interrupt> : gp_timer
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
That could be the culprit. Will try that out and report back.
nebenezer said:
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
Click to expand...
Click to collapse
def not while it's awake. left it for a min before posting my stats....
Hmm, I didn't think about that!
I'll give this a try when I get home and report back.
nebenezer said:
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
Click to expand...
Click to collapse
The readings below are after letting it sit for about 30 sec with the screen off.
Edit: Image wouldn't attach, I'm at about 125
Edit2: ran it again and now I'm at about 118
I just plugged my phone in and let it sit for about 5 minutes. Ran PowerTOP and got 156. Better than the 250+ I was getting before, but still more than what Flipz mentioned as "normal". Since the phone is responsive and quick I wonder how much of an issue this actually is. My battery life sucks, but not abnormally so (I get about 10 hours with moderate use).
I had same issue on flipz rom. I went back to damage control and now am 50 or lower my batery life is AMAZING. Something is real wrong with fresh rom.
fallentimm said:
I had same issue on flipz rom. I went back to damage control and now am 50 or lower my batery life is AMAZING. Something is real wrong with fresh rom.
Click to expand...
Click to collapse
I really like Flipz's work with Fresh ROMs, but I may have to give DC a try.
Similar Results here:
C:\android-sdk-windows\tools>adb shell dcpowertop
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
/sbin/modprobe: not found
Collecting data for 15 seconds
< Detailed C-state information is not available.>
P-states (frequencies)
576 Mhz 0.0%
499 Mhz 0.0%
461 Mhz 0.0%
384 Mhz 0.0%
245 Mhz 100.0%
Wakeups-from-idle per second : 645.3 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
61.8% (391.3) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)
35.2% (222.9) <interrupt> : gp_timer
0.7% ( 4.2) <interrupt> : msm_hsusb
0.5% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
0.3% ( 2.1) er.ServerThread : futex_wait (hrtimer_wakeup)
0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)
0.3% ( 2.0) SearchDialog : futex_wait (hrtimer_wakeup)
0.2% ( 1.0) m.android.phone : futex_wait (hrtimer_wakeup)
0.2% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
0.1% ( 0.5) Thread-95 : futex_wait (hrtimer_wakeup)
0.1% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)
0.1% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer_fn)
0.1% ( 0.4) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)
0.1% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)
0.0% ( 0.2) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)
0.0% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)
0.0% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)
0.0% ( 0.1) er.ServerThread : update_timer_locked (alarm_timer_triggered)
0.0% ( 0.1) <kernel core> : queue_delayed_work (delayed_work_timer_fn)
0.0% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn)
0.0% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)
0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)
xrandr: not found
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.
Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.
This option is required to get power estimages from PowerTOP
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
By the way, I am on the latest DamageControl Rom:
C:\android-sdk-windows\tools>adb shell top -n 1 -t
User 3%, System 5%, IOW 0%, IRQ 0%
User 11 + Nice 0 + Sys 19 + Idle 299 + IOW 0 + IRQ 0 + SIRQ 0 = 329
PID TID CPU% S VSS RSS PCY UID Thread Proc
1560 1560 8% R 1028K 544K fg root top top
460 1399 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1421 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1456 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1170 0% S 319696K 53140K fg system SearchDialog system_server
460 1493 0% S 319696K 53140K fg system AudioTrackThrea system_server
7 7 0% S 0K 0K fg root suspend
Ok, so I flashed the latest DC ROM, set it up identical to how I had Fresh EVO 0.5.3 set up and ran a PowerTOP. I came in at 67 wakeups per second. A significant and obvious improvement. Seems the issue may indeed be with the Fresh ROM. Hopefully Flipz can get it figured out and fixed because I really do like his ROMs a lot.
BB15 said:
Ok, so I flashed the latest DC ROM, set it up identical to how I had Fresh EVO 0.5.3 set up and ran a PowerTOP. I came in at 67 wakeups per second. A significant and obvious improvement. Seems the issue may indeed be with the Fresh ROM. Hopefully Flipz can get it figured out and fixed because I really do like his ROMs a lot.
Click to expand...
Click to collapse
Exactly howe things should be. Try batery saver mode in dconfig, I swear by it
I found the culprit on my system: Audible Selection
I was able to turn this off and on several times and recreate the high number of wakes with it on.
Since this is a part of the OS, can anybody recreate this?
MCLFLN said:
I found the culprit on my system: Audible Selection
I was able to turn this off and on several times and recreate the high number of wakes with it on.
Since this is a part of the OS, can anybody recreate this?
Click to expand...
Click to collapse
How do I turn off audible selection?
Nevermind... Found it. It was already off when I posted my results
I was having a problem with my wakes from idle. I returned the phone for screen separation and with my new 003 (previous was an 002) and everything else the same it was down to around 75-85. With the new Fresh 1.0.1 it's down to around 45-55.
ausch30 said:
I was having a problem with my wakes from idle. I returned the phone for screen separation and with my new 003 (previous was an 002) and everything else the same it was down to around 75-85. With the new Fresh 1.0.1 it's down to around 45-55.
Click to expand...
Click to collapse
Got mine knocked down by turning off the sounds in the swype keyboard. My high wake ups was being caused by audio track thread and narrowed it down to swype.
shad0w77 said:
How do I turn off audible selection?
Nevermind... Found it. It was already off when I posted my results
Click to expand...
Click to collapse
How do you turn it off? I'm getting 736 on wake on idle. I turned off all audible sound on swype and all other keyboards.
Related
I'm on the latest DC rom set at performance (like always)
I'm not sure why i've been getting a high WFI.
It used to always be really small, even in the 30's!
Yesterday I recalibrated the battery according to cyanogen's wiki.
Afterwards I got a bunch of "test/analysis apps" such as system, watchdog, and watts, just to see how things were going.
Overnight with the screen off I went from 100% to 0%(shutdown).
Probably due to the apps I installed..
So I checked my WFI and it was in the several hundreds 3-400!
I got rid of some possible rogue apps which has brought it down to the 80-120 range.
How can I get it back where it was before?
More specifically how can I target the specific apps which are causing me problems!
powertop -d
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
/sbin/modprobe: not found
< Detailed C-state information is not available.>
P-states (frequencies)
998 Mhz 1.2%
576 Mhz 0.0%
499 Mhz 0.0%
384 Mhz 0.6%
245 Mhz 98.2%
Wakeups-from-idle per second : 116.0 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
38.1% ( 38.9) <interrupt> : gp_timer
10.6% ( 10.9) <interrupt> : smsm_dev
9.8% ( 10.0) ruqqq.quickdesk : futex_wait (hrtimer_wakeup)
5.5% ( 5.6) Unknown : schedule_hrtimeout_range (hrtimer_wakeup)
5.4% ( 5.5) <interrupt> : msm-sdcc (cmd)
4.9% ( 5.0) <interrupt> : msm_hsusb
2.9% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
2.5% ( 2.6) er.ServerThread : futex_wait (hrtimer_wakeup)
2.4% ( 2.4) <interrupt> : msm_i2c
2.2% ( 2.3) <kernel core> : hrtimer_start (tick_sched_timer)
2.0% ( 2.0) SearchDialog : futex_wait (hrtimer_wakeup)
2.0% ( 2.0) Thread-39 : futex_wait (hrtimer_wakeup)
1.7% ( 1.7) <interrupt> : msm-sdcc (pio)
1.4% ( 1.5) Unknown : futex_wait (hrtimer_wakeup)
1.0% ( 1.1) <interrupt> : msmdatamover
1.0% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
1.0% ( 1.0) wpa_supplicant : schedule_hrtimeout_range (hrtimer_wakeup)
0.7% ( 0.7) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_
timer)
0.7% ( 0.7) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)
0.7% ( 0.7) Thread-31 : schedule_timeout (process_timeout)
0.5% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)
0.5% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer
_fn)
0.5% ( 0.5) watchdog/0 : __enqueue_rt_entity (sched_rt_period_timer)
0.3% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)
0.3% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)
0.2% ( 0.2) rild : queue_delayed_work (delayed_work_timer_fn)
0.2% ( 0.2) <kernel core> : page_writeback_init (wb_timer_fn)
0.2% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) dhd_dpc : dhd_os_wd_timer (dhd_watchdog)
0.1% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)
0.1% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) <kernel core> : addrconf_verify (addrconf_verify)
0.1% ( 0.1) dhd_dpc : schedule_timeout (process_timeout)
0.1% ( 0.1) Thread-9 : neigh_add_timer (neigh_timer_handler)
0.1% ( 0.1) ActivityManager : futex_wait (hrtimer_wakeup)
0.1% ( 0.1) <interrupt> : bcmsdh_sdmmc
0.1% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)
0.1% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)
xrandr: not found
Suggestion: increase the VM dirty writeback time from 6.00 to 15 seconds with:
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
This wakes the disk up less frequently for background VM activity
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.
Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.
This option is required to get power estimages from PowerTOP
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
# powertop -d
powertop -d
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
/sbin/modprobe: not found
< Detailed C-state information is not available.>
P-states (frequencies)
998 Mhz 1.3%
576 Mhz 0.0%
499 Mhz 0.0%
461 Mhz 0.1%
245 Mhz 98.6%
Wakeups-from-idle per second : 118.0 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
35.2% ( 37.1) <interrupt> : gp_timer
14.6% ( 15.4) <interrupt> : smsm_dev
9.5% ( 10.0) ruqqq.quickdesk : futex_wait (hrtimer_wakeup)
5.9% ( 6.2) <interrupt> : msm-sdcc (cmd)
5.2% ( 5.5) Unknown : schedule_hrtimeout_range (hrtimer_wakeup)
4.8% ( 5.1) <interrupt> : msm_hsusb
2.8% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
2.5% ( 2.7) er.ServerThread : futex_wait (hrtimer_wakeup)
2.1% ( 2.2) <kernel core> : hrtimer_start (tick_sched_timer)
2.0% ( 2.1) <interrupt> : msm-sdcc (pio)
1.9% ( 2.0) SearchDialog : futex_wait (hrtimer_wakeup)
1.9% ( 2.0) Thread-39 : futex_wait (hrtimer_wakeup)
1.5% ( 1.6) <interrupt> : msm_i2c
1.5% ( 1.5) Unknown : futex_wait (hrtimer_wakeup)
1.1% ( 1.2) <interrupt> : msmdatamover
0.9% ( 1.0) wpa_supplicant : schedule_hrtimeout_range (hrtimer_wakeup)
0.9% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
0.8% ( 0.9) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)
0.6% ( 0.7) Thread-31 : schedule_timeout (process_timeout)
0.6% ( 0.6) watchdog/0 : __enqueue_rt_entity (sched_rt_period_timer)
0.6% ( 0.6) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_
timer)
0.5% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer
_fn)
0.5% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)
0.3% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)
0.3% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)
0.2% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)
0.2% ( 0.2) <kernel core> : page_writeback_init (wb_timer_fn)
0.1% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)
0.1% ( 0.1) dhd_dpc : dhd_os_wd_timer (dhd_watchdog)
0.1% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)
0.1% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) rild : queue_delayed_work (delayed_work_timer_fn)
0.1% ( 0.1) er.ServerThread : update_timer_locked (alarm_timer_triggered)
0.1% ( 0.1) <interrupt> : bcmsdh_sdmmc
xrandr: not found
Suggestion: increase the VM dirty writeback time from 6.00 to 15 seconds with:
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
This wakes the disk up less frequently for background VM activity
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.
Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.
This option is required to get power estimages from PowerTOP
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Click to expand...
Click to collapse
EDIT: It just went down 5% from 100% to 95% in about 1-2 minutes..
Theres something wrong here!
Someone, kindly help me out.
It also seems that no matter what i uninstall or close the phone never idles!
It is constantly "awake".
The uptime and awake time are always equal!!
How can I solve this?
I tried using spare parts but it just shows that the partial wakelock is caused by android system!!
You started this thread a few days ago, just wanted to let you know that the topic is already being discussed here
http://forum.xda-developers.com/showthread.php?t=716343
Obviously new at this rooting and seem to be having battery issues, is there a reason my gp timer is at 45%...thanks in advance for the input!
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
/sbin/modprobe: not found
< Detailed C-state information is not available.>
P-states (frequencies)
998 Mhz 1.5%
576 Mhz 0.0%
499 Mhz 0.0%
384 Mhz 0.0%
245 Mhz 98.5%
Wakeups-from-idle per second : 91.6 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
45.0% ( 31.1) <interrupt> : gp_timer
10.0% ( 6.9) <interrupt> : smsm_dev
5.4% ( 3.7) <interrupt> : msmdatamover
4.5% ( 3.1) <interrupt> : msm-sdcc (cmd)
4.3% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
4.0% ( 2.8) er.ServerThread : futex_wait (hrtimer_wakeup)
3.5% ( 2.4) <interrupt> : msm_hsusb
3.4% ( 2.3) <kernel core> : hrtimer_start (tick_sched_timer)
2.8% ( 1.9) <interrupt> : msm-sdcc (pio)
2.0% ( 1.4) dhd_dpc : dhd_os_wd_timer (dhd_watchdog)
1.4% ( 1.0) WebViewCoreThre : futex_wait (hrtimer_wakeup)
1.4% ( 1.0) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)
1.4% ( 1.0) wpa_supplicant : schedule_hrtimeout_range (hrtimer_wakeup)
1.4% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
1.2% ( 0.8) <interrupt> : msm_i2c
0.8% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer
_fn)
0.8% ( 0.5) <interrupt> : bcmsdh_sdmmc
0.7% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)
0.6% ( 0.4) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_
timer)
0.5% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)
0.5% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)
0.4% ( 0.3) dhd_dpc : schedule_timeout (process_timeout)
0.4% ( 0.3) watchdog/0 : __enqueue_rt_entity (sched_rt_period_timer)
0.4% ( 0.3) dhd_watchdog : msmsdcc_request_end (msmsdcc_busclk_expired)
0.4% ( 0.3) <kernel core> : queue_delayed_work (delayed_work_timer_fn)
0.3% ( 0.2) Transaction : futex_wait (hrtimer_wakeup)
0.3% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)
0.2% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)
0.2% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)
0.2% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)
0.2% ( 0.1) ActivityManager : futex_wait (hrtimer_wakeup)
0.2% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) Thread-48 : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) NetworkLocation : update_timer_locked (alarm_timer_triggered)
0.1% ( 0.1) dhd_dpc : sk_reset_timer (tcp_delack_timer)
0.1% ( 0.1) GTalkConnWorker : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn)
0.1% ( 0.1) HeapWorker : futex_wait (hrtimer_wakeup)
0.1% ( 0.1) Thread-85 : sk_reset_timer (tcp_write_timer)
0.1% ( 0.1) dhd_dpc : neigh_add_timer (neigh_timer_handler)
0.1% ( 0.1) Timer-0 : futex_wait (hrtimer_wakeup)
0.1% ( 0.1) Thread-88 : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.1) er.ServerThread : update_timer_locked (alarm_timer_triggered)
0.1% ( 0.1) Thread-88 : schedule_timeout (process_timeout)
xrandr: not found
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.
Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.
This option is required to get power estimages from PowerTOP
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
download spare parts from the market. Go to battery history and hit the first dropdown and select partial wake usage. That should tell you what the culprit is or at least narrow it down.
Hello users,
How do i turbo boost my Android OS on my HOX?
When i rooted it it feels very fast, but when i restored all my apps it was noticeable slower than before.
How can i make it a lot faster and closer to the 'fasteness' of a fresh installed os without losing many apps?
maybe there is a list of apps that are very CPU and RAM intensive?
Here is the list of all my 3 party apps that i have installed:
Code:
cm.aptoide.pt
com.QuiteHypnotic.SilentTime
com.Tim.Koers.Silence (App i made my self)
com.Tim.Koers.beatbooster (App i made my self)
com.Tim.Koers.minitoolbox (App i made my self)
com.Tim.Koers.notebook (App i made my self)
com.Tim.Koers.wifiinfo (App i made my self)
com.beepbeepgo.pilot
com.brother.mfc.brprint
com.chrome.beta
com.cleanmaster.mguard
com.creativemobile.DragRacing
com.desaxedstudios.bassbooster
com.dotsandlines.carbon
com.ea.bf3bl.bv
com.fingersoft.hillclimb
com.gameinsight.airport
com.gameinsight.mycountry
com.gameinsight.mycountry2020
com.gau.go.launcherex.gowidget.taskmanagerex
com.google.android.apps.authenticator2
com.google.zxing.client.android
com.instagram.android
com.integer3d.dirtroadtrucker
com.jrummy.apps.memory.manager
com.jrummy.busybox.installer
com.keramidas.TitaniumBackup
com.macropinch.pearl
com.metago.astro
com.mobage.ww.a560.tinytower_android
com.mobage.ww.a987.PocketPlanes_Android
com.mxtech.ffmpeg.v7_vfpv3d16
com.mxtech.videoplayer.ad
com.news.rssfeedreader
com.nianticproject.ingress
com.nxp.taginfolite
com.path
com.paypal.android.p2pmobile
com.reader.androidworldtab
com.rerware.android.MyBackup
com.rockolabs.adbkonnect
com.rootuninstaller.free
com.sgiggle.production
com.skype.raider
com.snapchat.android
com.socialquantum.acityint
com.sparklingsociety.cityislandairport
com.tapatalk.tapatalk4
com.ttxapps.dropsync
com.utorrent.client
com.viber.voip
com.whatsapp
com.xuecs.ContactHelper
com.yandex.store
deezer.android.app
evz.android.wifi_credentials_recovery
me.youichi.realtimelogcat.ad
net.roamler
nl.sanomamedia.android.nu
nl.schoolmaster.meta
org.exobel.routerkeygen
org.projectvoodoo.otarootkeeper
robj.floating.notifications
Active services (couldn't show the 3 party active packages/services if somebody knows how to do that please comment!):
Code:
Found 80 services:
0 sip: [android.net.sip.ISipService]
1 htctelephony: [com.android.internal.telephony.IHtcTelephony]
2 phone: [com.android.internal.telephony.ITelephony]
3 htctelephonyinternal: [com.android.internal.telephony.IHtcTelephonyInternal]
4 iphonesubinfo: [com.android.internal.telephony.IPhoneSubInfo]
5 simphonebook: [com.android.internal.telephony.IIccPhoneBook]
6 isms: [com.android.internal.telephony.ISms]
7 nfc: [android.nfc.INfcAdapter]
8 wireless_display: [com.htc.service.IWirelessDisplayService]
9 commontime_management: []
10 userbehavior: [com.htc.utils.ulog.IUserBehaviorLoggingService]
11 samplingprofiler: []
12 diskstats: []
13 appwidget: [com.android.internal.appwidget.IAppWidgetService]
14 backup: [android.app.backup.IBackupManager]
15 uimode: [android.app.IUiModeManager]
16 serial: [android.hardware.ISerialManager]
17 usb: [android.hardware.usb.IUsbManager]
18 audio: [android.media.IAudioService]
19 wallpaper: [android.app.IWallpaperManager]
20 dropbox: [com.android.internal.os.IDropBoxManagerService]
21 search: [android.app.ISearchManager]
22 country_detector: [android.location.ICountryDetector]
23 location: [android.location.ILocationManager]
24 SUPL_SERVICE: []
25 devicestoragemonitor: []
26 display: [android.os.IDisplayService]
27 notification: [android.app.INotificationManager]
28 updatelock: [android.os.IUpdateLock]
29 throttle: [android.net.IThrottleManager]
30 servicediscovery: [android.net.nsd.INsdManager]
31 connectivity: [android.net.IConnectivityManager]
32 usbnet: [com.htc.net.usbnet.IUsbnetController]
33 wifi: [android.net.wifi.IWifiManager]
34 wifip2p: [android.net.wifi.p2p.IWifiP2pManager]
35 netpolicy: [android.net.INetworkPolicyManager]
36 netstats: [android.net.INetworkStatsService]
37 textservices: [com.android.internal.textservice.ITextServicesManager]
38 network_management: [android.os.INetworkManagementService]
39 clipboard: [android.content.IClipboard]
40 statusbar: [com.android.internal.statusbar.IStatusBarService]
41 device_policy: [android.app.admin.IDevicePolicyManager]
42 lock_settings: [com.android.internal.widget.ILockSettings]
43 mount: [IMountService]
44 gesture: [com.htc.service.IGestureService]
45 accessibility: [android.view.accessibility.IAccessibilityManager]
46 input_method: [com.android.internal.view.IInputMethodManager]
47 bluetooth_a2dp: [android.bluetooth.IBluetoothA2dp]
48 bluetooth: [android.bluetooth.IBluetooth]
49 input: [android.hardware.input.IInputManager]
50 window: [android.view.IWindowManager]
51 alarm: [android.app.IAlarmManager]
52 htchardware: [android.os.IHtcHardwareService]
53 vibrator: [android.os.IVibratorService]
54 battery: []
55 hardware: [android.os.IHardwareService]
56 content: [android.content.IContentService]
57 account: [android.accounts.IAccountManager]
58 permission: [android.os.IPermissionController]
59 cpuinfo: []
60 dbinfo: []
61 gfxinfo: []
62 meminfo: []
63 activity: [android.app.IActivityManager]
64 package: [android.content.pm.IPackageManager]
65 scheduling_policy: [android.os.ISchedulingPolicyService]
66 telephony.registry: [com.android.internal.telephony.ITelephonyRegistry]
67 htcdeviceinfo: [android.app.IHtcDeviceInfoManager]
68 HtcAppUsageStatsService: [com.android.internal.app.IHtcAppUsageStatsService]
69 usagestats: [com.android.internal.app.IUsageStats]
70 batteryinfo: [com.android.internal.app.IBatteryStats]
71 power: [android.os.IPowerManager]
72 entropy: []
73 sensorservice: [android.gui.SensorServer]
74 media.audio_policy: [android.media.IAudioPolicyService]
75 media.camera: [android.hardware.ICameraService]
76 SurfaceFlinger: [android.ui.ISurfaceComposer]
77 media.player: [android.media.IMediaPlayerService]
78 media.audio_flinger: [android.media.IAudioFlinger]
79 drm.drmManager: [drm.IDrmManagerService]
If somebody has recommendations about apps and how to make them consume less CPU and RAM, feel free to post. and you'll help me and a lot more people!
Thanks,
Tim
Use the TURBO BOOST MOD from Android Development section.
Sent from my HTC One X using Tapatalk 4 Beta
Is that a custom ROM or do you need to flash anything? I'd like to have my system as original as posible.
But i'll take a look!
Thanks
EDIT: Does it really works that well?
tim687 said:
Hello users,
How do i turbo boost my Android OS on my HOX?
When i rooted it it feels very fast, but when i restored all my apps it was noticeable slower than before.
How can i make it a lot faster and closer to the 'fasteness' of a fresh installed os without losing many apps?
maybe there is a list of apps that are very CPU and RAM intensive?
Here is the list of all my 3 party apps that i have installed:
Tim
Click to expand...
Click to collapse
tim687 said:
Is that a custom ROM or do you need to flash anything? I'd like to have my system as original as posible.
But i'll take a look!
Thanks
EDIT: Does it really works that well?
Click to expand...
Click to collapse
Turbo boost is not a custom rom. It works as an 'add-on' to your existing rom and does not change anything on the ui of the phone. If you didn't know it was installed you would not know it was there, except the phone maybe more responsive. Basically it uses the spare cache, data and system memory as the swap file instead of the SD card. This (in theory) improves the read/write time for the swap file as phone memory is much faster.
To install it just down load the zip file and flash it from recovery. During the setup you select how much memory you want to use (it gives a recommendation though) and thats it.
http://forum.xda-developers.com/showthread.php?t=2145133
Hello guys, last night I charged my phone full, went to sleep and 7 hours later I woke up to find it was already on 82% of the battery. The phone only had WIFI on at that moment.
When I check GSAM, it says android kernel was responsible for 44% of the drain. Here is the report:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Apr 25, 2015 10:49:52 AM
Usage Details
CPU Usage:19m 56s
Bytes Sent:976.10 KB
Bytes Received:459.30 KB
App UID:0
Wakelock Detail
Included Packages
Included Processes
init
kthreadd
ksoftirqd/0
rcuc0
rcun0
sync_supers
bdi-default
khubd
irq/365-max7769
irq/359-max7768
kswapd0
ksmd
ecryptfs-kthrea
s3c-fb
s3c-fb-vsync
file-storage
irq/387-melfas-
kcompcached
irq/352-SSP_Int
ssp_sensorhub_t
mc_fastcall
mmcqd/0
mmcqd/0boot0
mmcqd/0boot1
mmcqd/1
irq/395-sec_tou
ueventd
jbd2/mmcblk0p16
flush-179:0
healthd
vold
netd
debuggerd
zygote
ddexe
daemonsu
loop0
kauditd
dhd_watchdog_th
dhd_dpc
kworker/u:5
kworker/u:7
kworker/u:20
kworker/0:3
kworker/0:0
kworker/0:1
rcuc3
ksoftirqd/3
kworker/3:1
rcuc2
ksoftirqd/2
kworker/2:1
kworker/u:0
rcuc1
kworker/1:1
Thanks in advance.
Tested to today and the problem still persist, left the phone at 99% last night and when i woke up, it was at 87%. Android Kernel drained 46% .
More information please. .
What device. ..rom....kernel. ..mods. you've done. ..etc.
That's a big pond of info we need to narrow down a bit...g
Hello,
I have a Samsung Galaxy Note 2, GT-N7108.
I have been using it for over a year with out problems. Since last couple of weeks the problem of phone screen started. Screen would not go to sleep even though I press the sleep button, it would wake up immediately. It would keep doing that for ever. I read all the answers related to this problem on internet and tried all, the problem disappeared shortly but it reappeared. Due the screen being constantly switched on the battery drains very fast!
I clean installed the OS, I cleared the cache partition, changed several settings on the phone, finally I seek your help by posting the Better Battery Stats log file. I will be glad to answer your questions, thank you in advance for the help! I really appreciate that.
Let me know if you see something with the BBS log dump file below:
Code:
===================
General Information
===================
BetterBatteryStats version: 2.1.0.0
Creation Date: 2016-01-20 05:13:54
Statistic Type: Unplugged to Current
Since 5 h 47 m 49 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE:
MANUFACTURER: samsung
MODEL: GT-N7108
OS.VERSION: 3.0.31-2848223
BOOTLOADER: N7108ZMUEOI3
HARDWARE:
FINGERPRINT:
ID:
TAGS: release-keys
USER:
PRODUCT:
RADIO:
Rooted: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -63%(66% to 3%) [10.9%/h]
Voltage lost [mV]: (3861-3589) [47.0%/h]
===========
Other Usage
===========
Awake (Screen Off) (): 47 s 0.2%
Screen On (): 5 h 47 m 49 s 100.0%
Screen dark (): 5 h 47 m 49 s 100.0%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
RILJ (Phone): 2 m 22 s Count:4189 0.7%
AlarmManager (Android System): 1 m 23 s Count:2998 0.4%
ActivityManager-Sleep (Android System): 1 m 11 s Count:5346 0.3%
TimaService (Android System): 48 s Count:3105 0.2%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 20 s Count:2438 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 13 s Count:6 0.1%
AudioOut_2 (1013): 8 s Count:2 0.0%
WifiSuspend (Android System): 1 s Count:4028 0.0%
================
Kernel Wakelocks
================
"battery-update" (): Cnt:(c/wc/ec)45/0/45 0.0%
"unknown_wakeups" (): Cnt:(c/wc/ec)1/0/1 0.0%
"PowerManagerService.Broadcasts" (): Cnt:(c/wc/ec)1293/0/0 0.0%
"sync_system" (): Cnt:(c/wc/ec)1303/0/0 0.0%
"PowerManagerService.Display" (): Cnt:(c/wc/ec)631/0/0 0.0%
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
system (Android System): Uid: 1000 Sys: 27 s Us: 60 s Starts: 0
surfaceflinger (Android System): Uid: 1000 Sys: 12 s Us: 2 s Starts: 0
sensorhubservice (Android System): Uid: 1000 Sys: 5 s Us: Starts: 0
mc_fastcall (0): Uid: 0 Sys: 4 s Us: Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10151 Sys: 1 s Us: 3 s Starts: 0
com.sec.android.app.launcher (UID): Uid: 10103 Sys: Us: 2 s Starts: 0
com.android.systemui (com.android.systemui.System UI): Uid: 10136 Sys: Us: 2 s Starts: 0
su (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10151 Sys: 2 s Us: Starts: 0
com.android.phone (Phone): Uid: 1001 Sys: Us: 1 s Starts: 0
mmcqd/0 (0): Uid: 0 Sys: 2 s Us: Starts: 0
gpsd (1021): Uid: 1021 Sys: 2 s Us: Starts: 0
kworker/0:4 (0): Uid: 0 Sys: 2 s Us: Starts: 0
daemonsu:10151 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:2 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.sec.android.widgetapp.alarmclock (com.sec.android.widgetapp.alarmclock.Simple Alarm Clock): Uid: 10130 Sys: Us: 1 s Starts: 1
kworker/0:3 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:1 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:1 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.app.clockpackage (com.sec.android.app.clockpackage.Clock): Uid: 10020 Sys: Us: Starts: 1
com.sec.android.app.keyguard (com.sec.android.app.keyguard.com.sec.android.app.keyguard): Uid: 10061 Sys: Us: Starts: 12
com.sec.android.widgetapp.digitalclock (com.sec.android.widgetapp.digitalclock.Clock (digital)): Uid: 10025 Sys: Us: Starts: 12
rild (Phone): Uid: 1001 Sys: Us: Starts: 0
com.samsung.inputmethod (Android System): Uid: 1000 Sys: Us: Starts: 1
kworker/u:2 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:26 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.widgetapp.activeapplicationwidget (com.sec.android.widgetapp.activeapplicationwidget.Active Apps Manager): Uid: 10107 Sys: Us: Starts: 2
kworker/u:3 (0): Uid: 0 Sys: Us: Starts: 0
com.android.nfc (com.android.nfc.Nfc Service): Uid: 1027 Sys: Us: Starts: 1
mediaserver (1013): Uid: 1013 Sys: Us: Starts: 0
zygote (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.favoriteappwidget (com.sec.android.favoriteappwidget.Favorite Apps): Uid: 10108 Sys: Us: Starts: 2
kworker/u:4 (0): Uid: 0 Sys: Us: Starts: 0
jbd2/mmcblk0p16 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:29 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.widgetapp.favoriteswidget (UID): Uid: 10103 Sys: Us: Starts: 2
com.kingouser.com (com.kingouser.com.SuperUser): Uid: 10149 Sys: Us: Starts: 12
com.wsdm (Android System): Uid: 1000 Sys: Us: Starts: 12
servicemanager (Android System): Uid: 1000 Sys: Us: Starts: 0
kworker/0:5 (0): Uid: 0 Sys: Us: Starts: 0
com.samsung.android.providers.context (com.samsung.android.providers.context.ContextProvider): Uid: 10021 Sys: Us: Starts: 1
com.android.mms (com.android.mms.Messaging): Uid: 10121 Sys: Us: Starts: 1
com.sec.android.widgetapp.dualclockanalog (com.sec.android.widgetapp.dualclockanalog.Dual Clock (analog)): Uid: 10033 Sys: Us: Starts: 2
com.sec.android.app.SPenKeeper (com.sec.android.app.SPenKeeper.SPenKeeper): Uid: 10101 Sys: Us: Starts: 12
com.android.email (com.android.email.Email): Uid: 10115 Sys: Us: Starts: 1
com.android.contacts (Android Core Apps): Uid: 10008 Sys: Us: Starts: 1
com.wssyncmldm (Android System): Uid: 1000 Sys: Us: Starts: 12
/init (0): Uid: 0 Sys: Us: Starts: 0
s3c-fb (0): Uid: 0 Sys: Us: Starts: 0
flush-179:0 (0): Uid: 0 Sys: Us: Starts: 0
s3c-fb-vsync (0): Uid: 0 Sys: Us: Starts: 0
======================
Alarms (requires BATTERY_STATS permissions)
======================
android (): Wakeups: 1323 (3.8 / min)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 1313, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: NETWORK_STAT_LRU
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 11, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.sec.android.widgetapp.favoriteswidget/com.sec.android.widgetapp.favoriteswidget.SeniorFavoriteWidgetProviderSmall}
Alarms: 0, Intent: edm.intent.action.elm.cleanrecords
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 0, Intent: com.android.internal.policy.impl.Keyguard.LANDSCAPE_WAKE_TIME_LIMIT_EXPIRED
com.sec.spp.push (): Wakeups: 5 (0.9 / h)
Alarms: 5, Intent: {com.sec.spp.push/com.sec.spp.push.notisvc.alarm.AlarmEventManager}
com.sec.esdk.elm (): Wakeups: 1 (0.2 / h)
Alarms: 1, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG
======================
Network (requires root)
======================
0 (Mobile) (0): 2.0 MBytes 50.0%
1021 (Mobile) (1021): 2.0 MBytes 50.0%
==========
CPU States
==========
1.6 GHz (): 12 m 7 s 3.5%
1.5 GHz (): 9 s 0.0%
1.4 GHz (): 1 m 8 s 0.3%
1.3 GHz (): 12 s 0.1%
1.2 GHz (): 23 s 0.1%
1.1 GHz (): 1 m 34 s 0.5%
1 GHz (): 16 s 0.1%
900 MHz (): 11 s 0.1%
800 MHz (): 8 m 2.3%
700 MHz (): 31 s 0.1%
600 MHz (): 16 s 0.1%
500 MHz (): 7 m 51 s 2.3%
200 MHz (): 5 h 18 m 37 s 91.6%
========
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
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 16 s
Last activity: 16 s
Crash count:0
system (com.android.server.DrmEventService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.sec.spp.push (com.sec.spp.push.PushClientService)
Active since: 27 s
Last activity: 5 h 32 m 15 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 14 s
Last activity: 4 h 30 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.btservice.AdapterService)
Active since: 13 s
Last activity: 18 s
Crash count:0
com.tencent.engine (com.tencent.engine.InterceptEngineService)
Active since: 20 s
Last activity: 29 s
Crash count:0
com.sec.android.app.keyguard (com.sec.android.app.keyguard.KeyguardClockWidgetService)
Active since: 60 s
Last activity: 5 h 33 m 49 s
Crash count:0
com.sec.android.widgetapp.digitalclock (com.sec.android.widgetapp.digitalclock.DigitalClockService)
Active since: 28 s
Last activity: 5 h 32 m 48 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 19 s
Last activity: 19 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.baidu.map.location (com.baidu.map.location.BaiduNetworkLocationService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.policydm (com.policydm.ObserverService)
Active since: 25 s
Last activity: 5 h 33 m 4 s
Crash count:0
com.samsung.inputmethod (com.samsung.inputmethod.SamsungIME)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.android.phone (com.sec.enterprise.mdm.services.simpin.EnterpriseSimPin)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.samsung.android.providers.context (com.samsung.android.providers.context.ContextService)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.android.phone (com.sec.android.app.bluetoothtest.BluetoothBDTestService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.samsung.inputmethod (com.samsung.inputmethod.service.xt9.SimeDecoderService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.android.widgetapp.alarmclock (com.sec.android.widgetapp.alarmclock.ClockAlarmWidgetService)
Active since: 22 s
Last activity: 28 s
Crash count:0
com.android.phone (com.android.phone.BluetoothPhoneService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.sec.knox.seandroid (com.sec.knox.seandroid.service.SEAndroidLauncher)
Active since: 25 s
Last activity: 25 s
Crash count:0
com.tencent.engine (com.tencent.engine.DemoSecureService)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.sec.esdk.elm (com.sec.esdk.elm.service.ElmAgentService)
Active since: 24 s
Last activity: 5 h 44 m 59 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 18 s
Last activity: 18 s
Crash count:0
system (com.android.location.fused.FusedLocationService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.android.phone (com.android.phone.BluetoothVoIPService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.baidu.map.location (com.baidu.location.f)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.wssyncmldm (com.wssyncmldm.XDMService)
Active since: 27 s
Last activity: 5 h 33 m 33 s
Crash count:0
com.sec.knox.eventsmanager (com.sec.knox.eventsmanager.ContainerEventsRelayManager)
Active since: 15 s
Last activity: 15 s
Crash count:0
org.simalliance.openmobileapi.service:remote (org.simalliance.openmobileapi.service.SmartcardService)
Active since: 15 s
Last activity: 26 s
Crash count:0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.services.EventWatcherService)
Active since: 27 s
Last activity: 5 h 51 m 13 s
Crash count:0
com.wsdm (com.wsdm.DMService)
Active since: 27 s
Last activity: 5 h 33 m 17 s
Crash count:0
system (com.sec.knox.containeragent.service.notification.EnterpriseNotificationCenter)
Active since: 24 s
Last activity: 25 s
Crash count:0
com.sec.android.pagebuddynotisvc (com.sec.android.pagebuddynotisvc.PageBuddyNotiSvc)
Active since: 25 s
Last activity: 25 s
Crash count:0
com.android.phone (com.samsung.sec.android.application.csc.CscUpdateService)
Active since: 23 s
Last activity: 30 s
Crash count:0
com.kingouser.com (com.kingouser.com.service.RunningService)
Active since: 23 s
Last activity: 5 h 33 m 59 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 26 s
Last activity: 26 s
Crash count:0
com.android.nfc:handover (com.android.nfc.handover.HandoverService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.android.app.SPenKeeper (com.sec.android.app.SPenKeeper.SPenKeeperService)
Active since: 25 s
Last activity: 5 h 32 m
Crash count:0
system (android.hardware.location.GeofenceHardwareService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.phone (com.sec.phone.SecPhoneServiceCPOnUPG)
Active since: 23 s
Last activity: 5 h 32 m 32 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.hfp.HeadsetService)
Active since: 16 s
Last activity: 19 s
Crash count:0
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 7 m 54 s (Wl: 8 elements; KWl: 17elements; NetS: 2 elements; Alrm: 3 elements; Proc: 9 elements; Oth: 5 elements; CPU: 14 elements)
ref_custom: Reference ref_custom created 12 m 13 s (Wl: 9 elements; KWl: 17elements; NetS: 2 elements; Alrm: 3 elements; Proc: 12 elements; Oth: 5 elements; CPU: 14 elements)
ref_current: Reference ref_current created 5 h 55 m 44 s (Wl: 11 elements; KWl: 11elements; NetS: 2 elements; Alrm: 4 elements; Proc: 52 elements; Oth: 4 elements; CPU: 14 elements)