Related
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.
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
I compile a kernel from the CM 10.1 source for my N7108, but baseband unknown.and kernel version unavailable
Who can help me to solve this problem?please.
https://github.com/wctliu/Samsung-kernel-N7108/blob/master/adb-full-log.txt
a part of the log
Code:
--------- beginning of /dev/log/main
I/installd( 1856): installd firing up
I/DEBUG ( 1849): debuggerd: May 22 2013 02:49:39
--------- beginning of /dev/log/system
I/Vold ( 1846): Vold 2.1 (the revenge) firing up
D/Vold ( 1846): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1846): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)
I/Netd ( 1848): Netd 1.0 starting
W/InterfaceController( 1848): Error (Symbol not found: ) while searching for the interface command fini function
D/Vold ( 1846): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
D/macloader( 1859): Deleting file /data/.cid.info
D/DirectVolume( 1846): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 49, PARTN 1
D/Vold ( 1846): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/SurfaceFlinger( 1851): SurfaceFlinger is starting
I/SurfaceFlinger( 1851): use dithering
I/SurfaceFlinger( 1851): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/gpsd ( 1860): main()
D/gpsd ( 1860): argv[0] = '/system/bin/gpsd'
D/gpsd ( 1860): argv[1] = '-c'
D/gpsd ( 1860): argv[2] = '/system/etc/gps.xml'
D/gpsd ( 1860): onRilCustomConfig(Test for unsupported parameters, )
D/gpsd ( 1860): onRilCustomConfig(FactoryTestFilePath, /data/)
D/gpsd ( 1860): onRilCustomConfig(TISEnabled, true)
D/gpsd ( 1860): onRilCustomConfig(LPmode, false)
D/gpsd ( 1860): onRilCustomConfig(cp-cold-start, false)
D/gpsd ( 1860): onRilCustomConfig(cp-guard-time-sec, 1)
D/gpsd ( 1860): Create : called
I/gpsd ( 1860): RildClient : called
D/gpsd ( 1860): RildClientSamsung : called
I/gpsd ( 1860): start : called
D/gpsd ( 1860): onRegisterModules : called
I/gpsd ( 1860): RildClientModule : called
D/gpsd ( 1860): RildClientModuleFreqSync : called
I/gpsd ( 1860): RildClientModuleFreqSyncSamsung : called
D/gpsd ( 1860): registerModule : pModule = 0x130ad58
D/gpsd ( 1860): onRegisterModule : called
I/gpsd ( 1860): RildClientModule : called
D/gpsd ( 1860): RildClientModuleControlPlane : called
D/gpsd ( 1860): RildClientModuleControlPlaneSamsung : called
D/gpsd ( 1860): registerModule : pModule = 0x130ad80
D/gpsd ( 1860): onRegisterModule : called
D/gpsd ( 1860): onStart : called
D/gpsd ( 1860): SecRildClient : called
D/gpsd ( 1860): initialize : called
D/gpsd ( 1860): connect : called
I/gpsd ( 1860): connect: Connect_RILD failed. (4) Retry number : 0
D/libEGL ( 1851): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 1851): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 1851): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 1851): Device driver API match
E/ ( 1851): Device driver API version: 17
E/ ( 1851): User space API version: 17
E/ ( 1851): mali: REVISION=Linux-r3p1-01rel1 BUILD_DATE=Mon May 6 11:20:56 KST 2013
I/gralloc ( 1851): using (fd=21)
I/gralloc ( 1851): id = s3cfb
I/gralloc ( 1851): xres = 720 px
I/gralloc ( 1851): yres = 1280 px
I/gralloc ( 1851): xres_virtual = 720 px
I/gralloc ( 1851): yres_virtual = 2560 px
I/gralloc ( 1851): bpp = 32
I/gralloc ( 1851): r = 16:8
I/gralloc ( 1851): g = 8:8
I/gralloc ( 1851): b = 0:8
I/gralloc ( 1851): width = 69 mm (265.043488 dpi)
I/gralloc ( 1851): height = 123 mm (264.325195 dpi)
I/gralloc ( 1851): refresh rate = 58.30 Hz
I/SurfaceFlinger( 1851): Using composer version 1.0
W/SurfaceFlinger( 1851): getting VSYNC period from fb HAL: 17152364
W/SurfaceFlinger( 1851): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
E/Trace ( 1851): error opening trace file: No such file or directory (2)
W/SurfaceFlinger( 1851): WARNING: EventThread not started, ignoring vsync
I/SurfaceFlinger( 1851): EGL informations:
I/SurfaceFlinger( 1851): vendor : Android
I/SurfaceFlinger( 1851): version : 1.4 Android META-EGL
I/SurfaceFlinger( 1851): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 1851): Client API: OpenGL_ES
I/SurfaceFlinger( 1851): EGLSurface: 8-8-8-8, config=0x60000014
I/SurfaceFlinger( 1851): OpenGL ES informations:
I/SurfaceFlinger( 1851): vendor : ARM
I/SurfaceFlinger( 1851): renderer : Mali-400 MP
I/SurfaceFlinger( 1851): version : OpenGL ES-CM 1.1
I/SurfaceFlinger( 1851): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 GL_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_OES_texture_cube_map GL_EXT_discard_framebuffer GL_EXT_robustness
I/SurfaceFlinger( 1851): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 1851): GL_MAX_VIEWPORT_DIMS = 4096 x 4096
D/SurfaceFlinger( 1851): Screen acquired, type=0 flinger=0x408f8318
D/AndroidRuntime( 1852):
D/AndroidRuntime( 1852): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1852): CheckJNI is OFF
D/libEGL ( 2069): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2069): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2069): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2069): Device driver API match
E/ ( 2069): Device driver API version: 17
E/ ( 2069): User space API version: 17
E/ ( 2069): mali: REVISION=Linux-r3p1-01rel1 BUILD_DATE=Mon May 6 11:20:56 KST 2013
E/Trace ( 2069): error opening trace file: No such file or directory (2)
I/mediaserver( 1855): ServiceManager: 0x40feae70
D/SecTVOutService( 1855): SecTVOutService instantiate
E/ ( 1855): fb_open: fb[0] open failed
E/ ( 1855): bool android::SecHdmi::create(int, int):Failed to open default FB
E/SecTVOutService( 1855): android::SecTVOutService::SecTVOutService()::mSecHdmi.create() fail
D/SecTVOutService( 1855): SecTVOutService r=0
I/AudioFlinger( 1855): Using default 3000 mSec as standby time.
I/CameraService( 1855): CameraService started (pid=1855)
V/CameraWrapper( 1855): camera_get_number_of_cameras
V/CameraWrapper( 1855): check_vendor_module
D/SecCameraHardware( 1855): LSIHAL int android::HAL_getNumberOfCameras()
I/AudioPolicyManagerBase( 1855): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
E/Sensors ( 2231): Light old sensor_state 65, new sensor_state : 1 en : 0
I/PowerManagerService( 2231): Going to sleep due to screen timeout...
D/PermissionCache( 1851): checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (233 us)
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/SurfaceFlinger( 1851): Screen released, type=0 flinger=0x408f8318
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/WindowManager( 2231): Lock screen displayed!
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/NfcService( 2426): NFC-C OFF
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
E/Sensors ( 2231): Acc old sensor_state 1, new sensor_state : 0 en : 0
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/dalvikvm( 2231): GC_CONCURRENT freed 1657K, 20% free 11198K/13980K, paused 3ms+3ms, total 33ms
D/dalvikvm( 2231): WAIT_FOR_CONCURRENT_GC blocked 23ms
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/dalvikvm( 2231): GC_FOR_ALLOC freed 527K, 14% free 12074K/13980K, paused 23ms, total 23ms
D/dalvikvm( 2231): GC_FOR_ALLOC freed 27K, 14% free 12605K/14532K, paused 21ms, total 21ms
D/dalvikvm( 2231): GC_FOR_ALLOC freed 11K, 13% free 13342K/15268K, paused 22ms, total 22ms
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/dalvikvm( 2231): GC_FOR_ALLOC freed 34K, 12% free 14289K/16188K, paused 22ms, total 22ms
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/keystore( 1857): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
W/ThrottleService( 2231): unable to find stats for iface pdp0
W/SocketClient( 1848): write error (Broken pipe)
anyone? help me .thanks.
wctliu said:
anyone? help me .thanks.
Click to expand...
Click to collapse
1: be sure to had back-upped your EFS files
And i had this problem, and after days of ignorance of the community and self-research i decided to download the proprietary files from https://github.com/TheMuppets/ instead of extracting them myself and that did the trick.
thanks for your reply
how to back-upped EFS files ?
I tested many times, that this issue should be related with the kernel, rather than rom
wctliu said:
thanks for your reply
how to back-upped EFS files ?
I tested many times, that this issue should be related with the kernel, rather than rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1308546 loads of other topic on the case.
Mod move this out of developers board?
Factionwars said:
1: be sure to had back-upped your EFS files
And i had this problem, and after days of ignorance of the community and self-research i decided to download the proprietary files from https://github.com/TheMuppets/ instead of extracting them myself and that did the trick.
Click to expand...
Click to collapse
Factionwars said:
http://forum.xda-developers.com/showthread.php?t=1308546 loads of other topic on the case.
Mod move this out of developers board?
Click to expand...
Click to collapse
EFS should be independent of it.
When I was in exchange for the official kernel and rom. All normal.
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)
Hello,
a while ago, I started having an issue with my s4 mini (serranolte).
Basically, the screen turns itself on very often. For example, I press the power button to turn it off and after a second or so it turns itself on, stays on for ~10 seconds, turns off due to screen timeout, turns on by itself and so on.
I tried both with Lineage OS 14.1 and crDroid v4.4 (android 8.1) and the issue persists.
Here's a copy of the logcat taken while this happens:
Code:
07-15 12:49:42.350 531 634 I PowerManagerService: Going to sleep due to power button (uid 1000)...
07-15 12:49:42.377 531 558 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.378 531 558 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-15 12:49:42.384 531 558 W Adreno-EGL: <qeglDrvAPI_eglQueryContext:4373>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.827 531 558 I DisplayPowerController: Blocking screen off
07-15 12:49:42.827 531 558 I DisplayPowerController: Unblocked screen off after 0 ms
07-15 12:49:42.827 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.827 531 558 D Sensors : activate: handle=0, enabled=0
07-15 12:49:42.843 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.843 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:42.857 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
07-15 12:49:42.858 241 241 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb364e000
07-15 12:49:42.861 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.879 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:42.918 531 634 I PowerManagerService: Waking up from dozing (uid=1000 reason=android.policy:KEY)...
07-15 12:49:42.922 531 558 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
07-15 12:49:42.923 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:42.923 531 558 D Sensors : setDelay: handle=4, delay=250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setSensorDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.923 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:42.927 289 289 D audio_hw_primary: adev_set_parameters: enter: screen_state=off
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.964 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.979 1148 1148 I chatty : uid=10030(com.android.systemui) identical 2 lines
07-15 12:49:42.979 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:43.019 531 615 D Sensors : LightSensor readEvents x = 37.000000, raw = 37
07-15 12:49:43.020 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.020 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:43.021 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.021 531 558 D Sensors : setDelay: handle=4, delay=1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setSensorDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.021 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:43.021 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:43.022 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:43.120 531 615 D Sensors : LightSensor readEvents x = 39.000000, raw = 39
07-15 12:49:43.335 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 0 on display 0
07-15 12:49:43.344 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:43.345 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
07-15 12:49:43.363 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:43.368 241 241 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb364e000
07-15 12:49:43.368 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
07-15 12:49:43.981 531 556 W WindowManager: Timeout waiting for drawn: undrawn=[Window{afd67f u0 StatusBar}]
07-15 12:49:43.983 531 549 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.983 531 549 D Sensors : setDelay: handle=0, delay=66667000
07-15 12:49:43.984 531 549 D Sensors : activate: acc_enable=1, mag_enable=0
07-15 12:49:43.984 531 549 D Sensors : activate: handle=0, enabled=1
07-15 12:49:44.054 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
07-15 12:49:44.055 531 558 I DisplayPowerController: Unblocked screen on after 1133 ms
07-15 12:49:44.063 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:44.079 531 558 W PowerManagerService: Screen on took 1160 ms
07-15 12:49:44.081 1148 1148 I Choreographer: Skipped 63 frames! The application may be doing too much work on its main thread.
07-15 12:49:44.120 531 615 D Sensors : LightSensor readEvents x = 35.000000, raw = 35
07-15 12:49:44.132 289 389 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
Hoping someone can help
Ask me if you need to know anything else, I really hope this isn't an hardware issue...
Thanks, have a nice day
I've also tried flashing an older ROM, Pacman ROM (android 4.3) and I get the same issue.
This leads me to think it is an hardware related issue. Here's the Sensors output:
Code:
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=0
D/Sensors ( 836): LightSensor enable = 0
D/Sensors ( 836): LightSensor enableSensor = 0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
D/Sensors ( 836): activate: acc_enable=0, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=1
D/Sensors ( 836): setDelay: acc_delay=200000000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=1
D/Sensors ( 836): LightSensor enable = 1
D/Sensors ( 836): LightSensor enableSensor = 1
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=200000000
D/Sensors ( 836): LightSensor setDelay = 200000000
D/Sensors ( 836): LightSensor setSensorDelay = 200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
If you know of anything that could solve this, please let me know. Thanks.