Question Screen turning on and off (blinking) - OnePlus 9

Hi,
Recently my screen started turning on and off suddenly (like this video). However the blinking does not happen in Recovery Mode or Bootloader. Also doesn't happen in Ambient mode. So I opened logcat and I see this:
Code:
03-10 12:06:34.915 1044 1191 I SDM : HWEventsDRM::HandlePanelDead: Received panel dead event
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,1
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,mIrisServiceMode:0
03-10 12:06:34.915 1044 1191 I SDM : HWCSession::DisplayPowerReset: Powering off display = 0
03-10 12:06:34.915 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 56-0, teardown = 1
03-10 12:06:34.916 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_OFF(2)
03-10 12:06:34.916 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-998>
03-10 12:06:34.916 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -998 end
03-10 12:06:34.917 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 76, target: 1000, cmd id: 11
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.929 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.929 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: active 0-0 state 0-0 pending_power_state_ 0
03-10 12:06:34.947 1044 1191 I SDM : HWCSession::DisplayPowerReset: Setting display 0 to mode = 2
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 56-0, teardown = 0
03-10 12:06:34.949 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_ON(3)
03-10 12:06:34.949 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-999>
03-10 12:06:34.949 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -999 end
03-10 12:06:34.949 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 77, target: 1000, cmd id: 11
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.960 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.960 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:35.072 1044 1191 I SDM : StrategyImpl::SetIdleTimeoutMs: Idle timeout set to zero for command mode panels
03-10 12:06:35.072 1044 1191 I SDM : DisplayBase::SetDisplayState: active 1-1 state 1-1 pending_power_state_ 0
03-10 12:06:35.072 1044 1191 I IRIS_LOG_SERV: SetColorModeRI(7, 0)
03-10 12:06:35.080 1044 1210 I SDM : HWCColorModeStc::ApplyCurrentColorModeWithRenderIntent: Applying Stc mode (gamut 1 gamma 1 intent 1), curr mode 7, render intent 0, hdr present 0
It happens exactly every 5 seconds. I tried different solutions, tried flashing new rom, tried factory reset, but the problem remains. Also whenever the screen blinks it turns yellow. If I open a full screen app the screen is back to normal colors then turns yellow again after it blinks. Screen is not yellow in recovery so I'm not sure what the problem is. Anyone has any advice?

thethiny said:
Hi,
Recently my screen started turning on and off suddenly (like this video). However the blinking does not happen in Recovery Mode or Bootloader. Also doesn't happen in Ambient mode. So I opened logcat and I see this:
Code:
03-10 12:06:34.915 1044 1191 I SDM : HWEventsDRM::HandlePanelDead: Received panel dead event
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,1
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,mIrisServiceMode:0
03-10 12:06:34.915 1044 1191 I SDM : HWCSession::DisplayPowerReset: Powering off display = 0
03-10 12:06:34.915 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 56-0, teardown = 1
03-10 12:06:34.916 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_OFF(2)
03-10 12:06:34.916 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-998>
03-10 12:06:34.916 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -998 end
03-10 12:06:34.917 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 76, target: 1000, cmd id: 11
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.929 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.929 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: active 0-0 state 0-0 pending_power_state_ 0
03-10 12:06:34.947 1044 1191 I SDM : HWCSession::DisplayPowerReset: Setting display 0 to mode = 2
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 56-0, teardown = 0
03-10 12:06:34.949 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_ON(3)
03-10 12:06:34.949 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-999>
03-10 12:06:34.949 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -999 end
03-10 12:06:34.949 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 77, target: 1000, cmd id: 11
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.960 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.960 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:35.072 1044 1191 I SDM : StrategyImpl::SetIdleTimeoutMs: Idle timeout set to zero for command mode panels
03-10 12:06:35.072 1044 1191 I SDM : DisplayBase::SetDisplayState: active 1-1 state 1-1 pending_power_state_ 0
03-10 12:06:35.072 1044 1191 I IRIS_LOG_SERV: SetColorModeRI(7, 0)
03-10 12:06:35.080 1044 1210 I SDM : HWCColorModeStc::ApplyCurrentColorModeWithRenderIntent: Applying Stc mode (gamut 1 gamma 1 intent 1), curr mode 7, render intent 0, hdr present 0
It happens exactly every 5 seconds. I tried different solutions, tried flashing new rom, tried factory reset, but the problem remains. Also whenever the screen blinks it turns yellow. If I open a full screen app the screen is back to normal colors then turns yellow again after it blinks. Screen is not yellow in recovery so I'm not sure what the problem is. Anyone has any advice?
Click to expand...
Click to collapse
Definitely need to run the msm tool on your device. This will fix. Some reason your display is being powered off intermittently. Msm tool will return to stock condition. Google how to use. https://onepluscommunityserver.com/list/Unbrick_Tools/

mattie_49 said:
Definitely need to run the msm tool on your device. This will fix. Some reason your display is being powered off intermittently. Msm tool will return to stock condition. Google how to use. https://onepluscommunityserver.com/list/Unbrick_Tools/
Click to expand...
Click to collapse
Thank you I'll let you know when I try it.
Edit: Same problem unfortunately.

Related

[Q]Transformer keeps waking up

My transformer keeps waking up. About once every minute the screen will turn on and show the lock-screen, until it times out and the screen turns off again.
I tried restarting and had a look at running apps but didn't see anything suspicious.
My transformer isn't rooted. So I'm running stock ICS with the latest updates.
Any ideas?
Interesting that you post this...it happened to me once yesterday!
Swyped from my Nexus Uno
Doesn't anybody know how to fix this?
I'd rather not do a hard-reset but it seems like the only option left for me at this point...
me too
Mine started doing this when I updated to 9.2.1.17
For me it started a few days after the 9.2.1.17 (WW) update, I think...
It is same here.
After update to 9.2.1.17. Only in dock. Without dock, this never happen.
Here is log from another user from another forum:
Code:
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/AlarmManager( 166): Triggered Alarm 4144aa18 RTC_WAKEUP IntentSender{41804ce8: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=1117631ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1204K, 16% free 7160K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 462K, 17% free 7115K/8519K, paused 2ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 83K, 13% free 7435K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 130K, 10% free 7706K/8519K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 216K, 8% free 7888K/8519K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 245K, 6% free 8038K/8519K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 445K, 7% free 8026K/8583K, paused 2ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{419f6e40 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5286ms Battery<C,V>: <35,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/dalvikvm( 166): GC_FOR_ALLOC freed 1136K, 22% free 17763K/22727K, paused 82ms
V/alogcat (20906): save instance
V/alogcat (20906): paused
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/dalvikvm( 5588): GC_CONCURRENT freed 2094K, 39% free 17346K/28295K, paused 2ms+9ms
D/BatteryService( 166): level:34 scale:100 status:4 health:2 present:true dock_status:1 dock_level:0 dock_ac_online:false voltage: 7 temperature: 255 technology: Li-ion AC powered:false USB powered:false icon:17302840 invalid charger:0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 1
D/AlarmManager( 166): Triggered Alarm 419f6e40 RTC_WAKEUP IntentSender{413f93a0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9727ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
I/alogcat (20906): new intent: android.intent.action.MAIN
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1244K, 16% free 7275K/8583K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 581K, 18% free 7114K/8583K, paused 1ms+2ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 80K, 14% free 7442K/8583K, paused 3ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 113K, 10% free 7739K/8583K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 251K, 8% free 7905K/8583K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 244K, 7% free 8051K/8583K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 451K, 7% free 8020K/8583K, paused 1ms+5ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/AlarmManager( 166): Added alarm Alarm{419341d8 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:23
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5283ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/TaskWidgetDataUtils(20018): In trigger refresh list utils
D/TaskWidgetDataUtils(20018): getWidgetData()
D/AlarmManager( 166): Triggered Alarm 419341d8 RTC_WAKEUP IntentSender{415b2b60: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9741ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1247K, 15% free 7356K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 580K, 17% free 7223K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 97K, 13% free 7551K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 167K, 11% free 7780K/8647K, paused 2ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 227K, 9% free 7948K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 310K, 8% free 8025K/8647K, paused 1ms+3ms
D/dalvikvm(20906): GC_CONCURRENT freed 473K, 9% free 7945K/8647K, paused 1ms+7ms
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41b76e60 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:24
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Screen Bright {true -> false}
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
I/power ( 166): *** set_screen_state 0
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 0
E/ ( 166): handle : 4 en: 0
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 0 dmp_started: 1
V/ ( 166): Stopping DMP
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: suspending sensors to 0000
D/SurfaceFlinger( 88): About to give-up screen, flinger = 0x583958
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_suspend: Will resume next to 0070
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
D/PowerManagerService( 166): @PowerManagement: Screen turned off mScreenOnTime=5288ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
V/TransportControlView( 166): Create TCV [email protected]
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
V/alogcat (20906): save instance
V/alogcat (20906): paused
D/EthernetService( 166): stopPolling
D/Ethernet( 166): Screen Off
D/FlexLabs(20141): Widget count: 1
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/power ( 166): *** set_screen_state 1
V/ ( 166): virtual int MPLSensor::enable(int32_t, int)
V/ ( 166): handle : 4 en: 1
E/ ( 166): handle : 4 en: 1
V/ ( 166): sensor state change what=4
V/ ( 166): void set_power_states(int, bool)
V/ ( 166): enabled_sensors: 16 dmp_started: 0
V/ ( 166): Starting DMP
D/AlarmManager( 166): Triggered Alarm 41b76e60 RTC_WAKEUP IntentSender{412e2dd0: PendingIntentRecord{419ae270 com.tabletapps.wallpapers broadcastIntent}}
D/PowerManagerService( 166): @PowerManagement: Screen Bright {false -> true}
D/PowerManagerService( 166): @PowerManagement: Screen turned on mScreenOffTime=9725ms Battery<C,V>: <34,7>
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
D/PowerManagerService( 166): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=2
I/MPL-mldl_cfg_mpu:( 166): inv_mpu_resume: Resuming to 0070
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 200
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 39 200000000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
V/ ( 166): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 166): setDelay handle: 4 rate 66
V/ ( 166): virtual int MPLSensor::update_delay()
V/ ( 166): set fifo rate: 13 66667000
I/MPL-fifo( 166): Actual ODR: 25000 mHz
D/WindowManager( 166): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/PowerManagerService( 166): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
I/WindowManager( 166): Lock screen displayed!
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=1
I/alogcat (20906): new intent: android.intent.action.MAIN
D/alogcat (20906): stopping ...
D/alogcat (20906): canceling periodic saves
D/alogcat (20906): stopped
D/alogcat (20906): starting ...
V/alogcat (20906): resumed
D/dalvikvm(20906): GC_CONCURRENT freed 1226K, 17% free 7259K/8647K, paused 1ms+4ms
D/SurfaceFlinger( 88): Screen about to return, flinger = 0x583958
D/dalvikvm(20906): GC_CONCURRENT freed 470K, 17% free 7229K/8647K, paused 2ms+2ms
D/dalvikvm(20906): GC_CONCURRENT freed 55K, 13% free 7586K/8647K, paused 2ms+5ms
D/dalvikvm(20906): GC_CONCURRENT freed 144K, 10% free 7834K/8647K, paused 3ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 256K, 8% free 7979K/8647K, paused 2ms+4ms
D/dalvikvm(20906): GC_CONCURRENT freed 271K, 7% free 8096K/8647K, paused 2ms+3ms
D/OpenGLRenderer( 166): Flushing caches (mode 0)
D/PowerManagerService( 166): @PowerManagement: 'keyguard' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
I/TabletStatusBar( 361): DISABLE_CLOCK: no
V/TabletStatusBar( 361): setLightsOn(true)
D/dalvikvm(20906): GC_CONCURRENT freed 499K, 8% free 8034K/8647K, paused 2ms+7ms
I/TextType( 465): TextType = 0x0
W/InputManagerService( 166): Window already focused, ignoring focus gain of: [email protected]
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(20906): endBatchEdit on inactive InputConnection
D/PowerManagerService( 166): @PowerManagement: 'KEEP_SCREEN_ON_FLAG' releaseWakeLock when screen locked
D/AlarmManager( 166): Added alarm Alarm{41a6bd00 type 0 com.tabletapps.wallpapers} type:RTC_WAKEUP when: At 22.3.12 21:34
D/Ethernet( 166): Connect is not possible because : ETHERNET not ENABLE,
D/PowerManagerService( 166): @PowerManagement: 'AdControllerWakeLock' releaseWakeLock when screen locked
D/PowerManagerService( 166): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
D/FlexLabs(20141): Widget count: 1
V/ ( 166): void cb_onMotion(uint16_t)
Same here; mine is docked and next to my desk at work with wifi on.
i thought it was the "disconnect network during sleep" battery saving option (mine is checked); unchecking it doesn't seem to stop the device from waking up though.
found this in another forum, hopefully it helps!
http://www.transformerforums.com/fo...help/18466-tf101-ics-4-0-3-wake-up-issue.html
I can't even believe all this bs...
Ok, so i cannot even believe I am posting this - I have a tf101 docked, with the same issue - 9.2.1.21 (very latest).
Anyone know the fix?
/between this, the RR's, and the stupid unfixable SOD, i'm about ready to chuck this pos out the window.
Wakelock to fix SOD
Auto-Airplane mode to (probably) fix wakeup issues. (or just turn on airplane mode)
Both are apps in market.
If A-A doesn't fix, then an app/widget is triggering the problem.
This is a problem with the last update from ASUS, you can try the methods above, deal with it, or flash a custom kernel.

E\ThermalDaemon from ICS logcat

does anyone know what this ThermalDaemon is for? and why its giving me so many errors in my logcat...
Code:
E/ThermalDaemon( 6881): Fusion modem thermal mitigation available.
E/ThermalDaemon( 6881): Sensor setup:[pm8058_tz]
E/ThermalDaemon( 6881): Unable to open /sys/devices/virtual/thermal
E/ThermalDaemon( 6881): No thermal zone device found in the kernel for sensor pm
8058_tz
E/ThermalDaemon( 6881): Sensor setup:[tsens_tz_sensor0]
E/ThermalDaemon( 6881): Unable to open /sys/devices/virtual/thermal
E/ThermalDaemon( 6881): No thermal zone device found in the kernel for sensor ts
ens_tz_sensor0
E/ThermalDaemon( 6881): tsens: unexpected NULL
E/ThermalDaemon( 6881): Failed to setup at least one sensor for monitoring
I/ONCRPC ( 6881): xdr_std_msg_send_call: Received Reply Xid: 0, Prog: 300100b5,
Ver: 00020001, Proc: 00000000
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
I/ONCRPC ( 6881): oncrpc_xdr_call_msg_start: Prog: 300100b5, Ver: 00020001, Pro
c: 00000004
I/ONCRPC ( 6881): xdr_std_msg_send_call: Sent Xid: 1, Prog: 300100b5, Ver: 0002
0001, Proc: 00000004
I/ONCRPC ( 6881): xdr_std_msg_send_call: Received Reply Xid: 1, Prog: 300100b5,
Ver: 00020001, Proc: 00000004
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
I/ONCRPC ( 6881): oncrpc_xdr_call_msg_start: Prog: 300100b5, Ver: 00020001, Pro
c: 00000003
I/ONCRPC ( 6881): xdr_std_msg_send_call: Sent Xid: 2, Prog: 300100b5, Ver: 0002
0001, Proc: 00000003
I/ONCRPC ( 6881): rpc_handle_rpc_call: for Xid: 820, Prog: 310100b5, Vers: 0002
0001, Proc: 00000001
I/ONCRPC ( 6881): rpc_handle_rpc_call: Find Status: 0 Xid: 820
I/ONCRPC ( 6881): oncrpc_proxy_handle_cmd_rpc_call: Dispatching xid: 820
I/ONCRPC ( 6881): xdr_std_msg_send_call: Received Reply Xid: 2, Prog: 300100b5,
Ver: 00020001, Proc: 00000003
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
I/ONCRPC ( 6881): Setup RPC Call for task 4010c270
E/ThermalDaemon( 6881): ONCRPC communication terminated.
E/ThermalDaemon( 6881): Thermal daemon exited
E/ThermalDaemon( 6888): Thermal daemon started
E/ThermalDaemon( 6888): Threshold 0 Action[0] : none
E/ThermalDaemon( 6888): Threshold 1 Action[0] : none
E/ThermalDaemon( 6888): Threshold 2 Action[0] : none
E/ThermalDaemon( 6888): Threshold 0 Action Info[0] : 768000.000000
E/ThermalDaemon( 6888): Threshold 1 Action Info[0] : 368640.000000
E/ThermalDaemon( 6888): Threshold 2 Action Info[0] : 245760.000000
E/ThermalDaemon( 6888): Threshold 0 Action[0] : none
E/ThermalDaemon( 6888): Threshold 1 Action[0] : none
E/ThermalDaemon( 6888): Threshold 2 Action[0] : none
E/ThermalDaemon( 6888): Threshold 0 Action Info[0] : 768000.000000
E/ThermalDaemon( 6888): Threshold 1 Action Info[0] : 368640.000000
E/ThermalDaemon( 6888): Threshold 2 Action Info[0] : 245760.000000
E/ThermalDaemon( 6888): Number of cpus :2
E/ThermalDaemon( 6888): CPUFreq not enabled for CPU[1]
E/ThermalDaemon( 6888): Establishing ONCRPC communication.
porbably used to monitor battery/phone temp, and shut down if too hot
oh the irony in post title and username
Haha well played sir.
So is anyone else getting this? Its constant.
Sent from my SAMSUNG-SGH-I727 using XDA
theHOTNESS said:
Haha well played sir.
So is anyone else getting this? Its constant.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
+1 for me. Not sure if its causing the battery drain issue I'm trying to troubleshoot, though.
---------- Post added at 06:36 PM ---------- Previous post was at 06:21 PM ----------
What's your config?
I'm running Smooth Ice 1.5 with kernel from mohan_kr.
---------- Post added at 06:57 PM ---------- Previous post was at 06:36 PM ----------
I backed /system/bin/thermald up and deleted it. I think somethings missing from the kernel that reads the sensor. Log messages are gone now...we'll see what this does.
e.g. No thermal zone device found in the kernel for sensor
was running the odin leak stock deodexed with a couple of framework and apk edits. although it was happening even before meddling.
anyway i think you're right about it being a kernel problem...
yeah so apparently
"PM8058™ power management IC" is used in Qualcomm chips. some sort of power management thing.
Code:
E/ThermalDaemon( 6881): Sensor setup:[pm8058_tz]
E/ThermalDaemon( 6881): Unable to open /sys/devices/virtual/thermal
E/ThermalDaemon( 6881): No thermal zone device found in the kernel for sensor pm
8058_tz
E/ThermalDaemon( 6881): Sensor setup:[tsens_tz_sensor0]
E/ThermalDaemon( 6881): Unable to open /sys/devices/virtual/thermal
E/ThermalDaemon( 6881): No thermal zone device found in the kernel for sensor ts
ens_tz_sensor0
seems to be the root of the problem, we either dont have the sensor or the kernels not setting it up correctly. my guess is the sensors are declared somewhere so thermaldaemon is trying to monitor them but were missing some files in /sys/devices/virtual/thermal or somewhere else in the kernel

[Q] TF101 Freezes

Problem:
I have this TF101, which freezes in virtually every ROM I've tried. When I'm playing a game, refreshing Twitter timeline by dragging down, or sometimes even simply viewing settings, the screen freezes. The sound and logcat however continue. I can also turn the screen on and off by pressing the power button, but the lockscreen does not show up. When I press the volume buttons, sometimes logcat says it's registering the presses, but ignores them: I/InputDispatcher(141): Dropped event because input dispatch is disabled.
Here's a Youtube video showing the problem.
Analysis:
As said, logcat continues while the freeze is happening. Here are two logcats of the freeze and a traces.txt:
Device info: Stock ROM
Android version: 3.1
Kernel version: 2.6.36.3-00011-g3eb19ec [email protected] #1
Build number: HMJ37.WW_epad-8.4.4.11-201107011
S/N: B70.........
Problem: Freeze as mentioned before.
Logcat
Device info: Stock ROM after 2 ASUS updates
Android version: 4.0.3
Kernel version: 2.6.39.4 [email protected] #1
Build number: IML74K.WW_epad-9.2.1.24-20120503
S/N: B70.........
Problem: Freeze as mentioned before, but now the device reboots itself short time later.
Logcat
Device info: Prime! 1.8 ROM flashed using NVFlash
Android version: 2.3
Kernel version: 2.6.36.4-g565dea1 [email protected] #20110816
Build number: HTJ85B.prime_epad-1.8-20110821
S/N: B70.........
Problem: Freeze as mentioned before. This is the ROM in which the freezes less frequently happen, but they still happen.
Traces.txt
Solution:
I have no idea. That's why I came here. Any help is appreciated.
Reading the logs, it looks like a wifi/notification related issue in the first, and notification in the second. I'm thinking system problem...
If this happens alot, have you tried putting a Custom ROM on and applying guevor's kernel?
I've flashed Guevor's kernel 17c, and afterwards Megatron 1.1.6.
New device info:
Android version: 4.0.4
Kernel version: 2.6.39.4-00022-g482ca04 [email protected] #1 SMP PREEMPT Sat Mar 17 02:10:06 CST 2012
Build number: cm_tf101-userdebug 4.0.4 IMM76I eng.ze.20120521.230325 test-keys
My laptop doesn't recognize the tablet (no device discovered in device manager), so I can't view ADB logcat, but still the freezes occur after which the tablet reboots.
Any more thoughts?
-Edit-
I've tried the prime 1.8 ROM using nvflash. So far so good. Only drawback is Android 3.2.
So eventually I got freezes with this ROM as well. Only the screen freezes, sound and logcats continue.
I've tried some other ROMs with several kernels (megatron 1.0.0 and 1.1.6 with guevor 17c & 20), but these freeze within a minute, always in settings menu. The Prime! 1.8 ROM lasts a lot longer before a freeze, this occurs mostly in a game, sometimes in Dolphin, Play Store, Settings, etc..
Device info:
Android version: 3.2
Kernel version: 2.6.36.4-g565dea1 [email protected] #20110816
Build number: HTJ85B.prime_epad-1.8-20110821
S/N: B70.........
Does anyone have a suggestion?
If you need some more info, I'm happy to provide it.
YT video: http://www.youtube.com/watch?v=NlSKa0qVkhQ&feature=youtu.be
I've edited the first post, I've added a traces.txt of the crash. Any help is appreciated!
Anyone? Could this be hardware related?
Prime is a good, but really old rom. Try ARHD, AOKP, or Megatron. With guevor's latest 21.4/6 ARHD is often said to be the most stable, give that a go.
Make sure you COMPLETELY WIPE EVERYTHING, when you install, or you'll always have problems (Superwipe script available in ARHD thread)
Thanks for your suggestion!
I've tried the latest ARHD with guevor's 21.4 kernel, still the freezes.
I'm gonna try AOKP now.
I had the similar SOD problem, and had tried several roms (ARHD,Revolver,AOKP,CM9) and guevor's kernel, but the problem persists...
The situation is once i turn off the screen, there's a high chance that my TF101 will freeze, and the battery drain faster than normal. It really got me frustrated.
The logs and ramdump are here, and i doubt it's something wrong with tegra_pwm.
ramdump
Code:
<4>[ 662.548529] kxtf9_resume-
<4>[ 662.548561] MPU_RESUME IOCTL-
<4>[ 662.549537] MPU_SUSPEND IOCTL+
<4>[ 662.549574] kxtf9_suspend+
<4>[ 662.550719] kxtf9_suspend-
<4>[ 662.550749] MPU_SUSPEND IOCTL-
<4>[ 662.551010] MPU_RESUME IOCTL+
<4>[ 662.551045] kxtf9_resume+
<4>[ 662.552194] kxtf9_resume-
<4>[ 662.552225] MPU_RESUME IOCTL-
<4>[ 662.552512] MPU_SUSPEND IOCTL+
<4>[ 662.552546] kxtf9_suspend+
<4>[ 662.553682] kxtf9_suspend-
<4>[ 662.553712] MPU_SUSPEND IOCTL-
<4>[ 662.553950] MPU_RESUME IOCTL+
<4>[ 662.553983] kxtf9_resume+
<4>[ 662.555232] kxtf9_resume-
<4>[ 662.555264] MPU_RESUME IOCTL-
<4>[ 662.555705] Touch: PQ7 is 1
<4>[ 662.575252] Disp: brightness= 0
<4>[ 662.575315] tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.576060] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<6>[ 662.588092] [mmc]:mmc_rescan:1637 mmc2: finished, extend_wakelock 0
<4>[ 662.595155] Disp: brightness= 0
<4>[ 662.595217] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.595937] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<4>[ 662.616412] Disp: brightness= 0
<4>[ 662.616471] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.618712] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<4>[ 662.635326] Disp: brightness= 0
<4>[ 662.635369] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.635952] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<4>[ 662.655190] Disp: brightness= 0
<4>[ 662.655231] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.655714] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<4>[ 662.665203] Touch: force release position
<4>[ 662.675255] Disp: brightness= 0
<4>[ 662.675298] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.676757] Can't update brightness 'cause of "bl->props.fb_blank != FB_BLANK_UNBLANK"
<4>[ 662.69 炧牸{c蓜揠岸 罝?m忧Y0dc-U?辽?f彸`凘?A?玉_r>d?ij蟔
d??!e??莠缞娧?僥>覷p劰<!y脎浩姭]橃譂 δ晭夜|橭倹-€櫰旬?鈳偼瓴跇賒猡馕?|?
=芨oO?鍶琄 褴(9l陭P$忘kY"蹗)蠥?-蚛]$歙?蕮4ki劓J(7宺D"个^菆损?嗿綆x?駖肐W鳐<苰wg剩姛葆 662.754968] Disp: brightness= 0
<4>[ 662.754987] tegra_pwm tegra_pwm.2: pwm_disable called on disabled PWM
<4>[ 662.755932] Can't update brightness 'cause o
logcat
Code:
W/InputManagerService( 154): Starting input on non-focused client [email protected] (uid=1000 pid=423)
D/OpenGLRenderer( 423): Flushing caches (mode 1)
I/TextType( 395): TextType = 0x0
D/dalvikvm( 1054): GC_CONCURRENT freed 3644K, 44% free 9801K/17479K, paused 2ms+11ms
D/dalvikvm( 1054): GC_FOR_ALLOC freed 132K, 45% free 9731K/17479K, paused 22ms
I/dalvikvm-heap( 1054): Grow heap (frag case) to 11.437MB for 1958648-byte allocation
D/dalvikvm( 1054): GC_FOR_ALLOC freed 598K, 37% free 11045K/17479K, paused 22ms
D/dalvikvm( 1054): GC_FOR_ALLOC freed 1920K, 40% free 10581K/17479K, paused 19ms
D/dalvikvm( 1054): GC_CONCURRENT freed 95K, 33% free 11821K/17479K, paused 1ms+5ms
D/dalvikvm( 1054): GC_CONCURRENT freed 2679K, 38% free 10862K/17479K, paused 3ms+3ms
D/dalvikvm( 1054): GC_CONCURRENT freed 881K, 35% free 11393K/17479K, paused 2ms+2ms
I/ActivityManager( 154): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.bvalosek.cpuspy/.ui.HomeActivity} from pid 1054
I/ActivityManager( 154): Start proc com.bvalosek.cpuspy for activity com.bvalosek.cpuspy/.ui.HomeActivity: pid=1592 uid=10070 gids={}
D/WindowManager( 154): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
D/dalvikvm( 88): GC_EXPLICIT freed 36K, 5% free 6538K/6851K, paused 1ms+3ms
D/dalvikvm( 88): GC_EXPLICIT freed <1K, 5% free 6538K/6851K, paused 2ms+2ms
D/OpenGLRenderer( 1054): Flushing caches (mode 1)
D/dalvikvm( 88): GC_EXPLICIT freed <1K, 5% free 6538K/6851K, paused 1ms+2ms
D/OpenGLRenderer( 1054): Flushing caches (mode 0)
I/TextType( 395): TextType = 0x0
W/InputManagerService( 154): Starting input on non-focused client [email protected] (uid=10033 pid=1054)
D/dalvikvm( 395): GC_CONCURRENT freed 513K, 27% free 7061K/9607K, paused 4ms+2ms
I/ActivityManager( 154): Displayed com.bvalosek.cpuspy/.ui.HomeActivity: +301ms
D/PowerManagerService( 154): @PowerManagement: Auto-dim timeout
D/PowerManagerService( 154): @PowerManagement: Screen Bright {true -> false}
D/PowerManagerService( 154): @PowerManagement: Screen Bright {false -> true}
I/ActivityManager( 154): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/com.android.launcher2.Launcher} from pid 154
D/dalvikvm( 154): GC_FOR_ALLOC freed 1094K, 17% free 11610K/13895K, paused 58ms
D/WindowManager( 154): adjustConfigurationLw, config:{1.0 0mcc0mnc (no locale) layoutdir=0 sw800dp w1280dp h752dp xlrg land ?uimode ?night finger -keyb/v/h -nav/v} mLidOpen:-1 mHasDockFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:2
I/TextType( 395): TextType = 0x0
D/PowerManagerService( 154): @PowerManagement: Sleep state requested, reason:2
D/PowerManagerService( 154): @PowerManagement: Screen Bright {true -> false}
I/power ( 154): *** set_screen_state 0
D/SurfaceFlinger( 87): About to give-up screen, flinger = 0x16cf958
V/ ( 154): virtual int MPLSensor::enable(int32_t, int)
V/ ( 154): handle : 4 en: 0
E/ ( 154): handle : 4 en: 0
V/ ( 154): sensor state change what=4
V/ ( 154): void set_power_states(int, bool)
V/ ( 154): enabled_sensors: 0 dmp_started: 1
V/ ( 154): Stopping DMP
I/MPL-mldl_cfg_mpu:( 154): inv_mpu_suspend: suspending sensors to 0000
D/PowerManagerService( 154): @PowerManagement: Screen turned off mScreenOnTime=31272ms Battery<C,V>: <74,7>
D/PowerManagerService( 154): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
I/MPL-mldl_cfg_mpu:( 154): inv_mpu_suspend: Will resume next to 0070
V/ ( 154): virtual int MPLSensor::update_delay()
V/ ( 154): virtual int MPLSensor::setDelay(int32_t, int64_t)
E/ ( 154): setDelay handle: 4 rate 66
V/ ( 154): virtual int MPLSensor::update_delay()
V/TransportControlView( 154): Create TCV [email protected]
D/PowerManagerService( 154): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
D/Ethernet( 154): Screen Off connect_policy = 0 ; bTethered = false
D/Ethernet( 154): Screen Off
D/PowerManagerService( 154): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
I/TabletStatusBar( 308): DISABLE_CLOCK: yes
The AOKP ROM seems very stable, no freezes in a couple of hours now!
Thanks a lot!

[Q] How reliable is loadavg

From a shell:
Code:
$ cat /proc/loadavg
1.60 1.31 1.26 2/1446 19315
According to a.o.
https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-proc-loadavg.html, 2/1446 means that I have 2 CPUs and 1446 tasks waiting to be run.
1446 tasks? On a heavily loaded workstation I seldom see more than a couple of 100 tasks. A simple server shows just over 100 tasks. So how come the Note has so many tasks? Besides,
Code:
$ps|wc -l
224
Given that I sometimes get load values of around 80 I start getting doubts that the numbers produced by /proc/loadavg are useful.
Does anyone have any ideas what could cause these high numbers for loads and tasks?
sciurius said:
Does anyone have any ideas what could cause these high numbers for loads and tasks?
Click to expand...
Click to collapse
Threads. Run "adb shell top -t" and you'll break out each thread:
Code:
User 31%, System 4%, IOW 0%, IRQ 0%
User 111 + Nice 297 + Sys 62 + Idle 828 + IOW 0 + IRQ 0 + SIRQ 0 = 1298
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
3670 11496 2 22% R 504052K 49724K bg u0_a25 MediaScannerSer android.process.media
11192 11192 1 1% R 1792K 1164K shell top top
9091 9114 0 1% S 487544K 40000K bg u0_a170 Thread-416 com.mobidia.android.mdm:remote
2342 5579 3 1% S 701848K 101820K fg system Binder_D system_server
2342 2342 1 1% S 701848K 101820K fg system system_server system_server
2342 2430 0 0% S 701848K 101820K fg system ActivityManager system_server
2342 4431 1 0% S 701848K 101820K fg system Binder_A system_server
3957 4175 0 0% S 549604K 47424K bg u0_a16 NetworkLocation com.google.process.gapps
2342 3887 1 0% S 701848K 101820K fg system Binder_5 system_server
7563 7563 2 0% S 492308K 37216K fg u0_a39 ndroid.calendar com.google.android.calendar
2342 5594 2 0% S 701848K 101820K fg system Binder_E system_server
3555 3555 3 0% S 534276K 67664K fg u0_a121 ndroid.systemui com.android.systemui
2342 4165 1 0% S 701848K 101820K fg system Binder_6 system_server
690 690 0 0% S 0K 0K root ksmd
<snip>
I see. I'm used to applications that have one or two threads, but a typical Android app seems to have at least 10. That adds up quickly.

[Q] [HELP] Touch Compatibily Patch Little Help

I followed this guide to install CyanogenMod.
http://forum.xda-developers.com/showthread.php?t=2343531
Since I have to have at least 10 posts to write on that topic ask here who can tell me which patch to use as the touch does not work.
Thanks in advice
PS: This is the result of lsmod whit the STOCK ROM of the tablet
Android 4.0.4 ICS
Kernel: 3.0.8+
Code:
[email protected]:/ $ su
[email protected]:/ # lsmod
8188eu 621112 0 - Live 0xbf279000
8192cu 575431 0 - Live 0xbf1d1000
mxc622x 6310 0 - Live 0xbf1cb000
rtl8150 10305 0 - Live 0xbf1c4000
mcs7830 7581 0 - Live 0xbf1be000
qf9700 9152 0 - Live 0xbf1b7000
asix 24601 0 - Live 0xbf1ab000
sun5i_csi0 33355 0 - Live 0xbf19d000
gc0308 18608 1 - Live 0xbf194000
camera 61054 1 sun5i_csi0, Live 0xbf180000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf17b000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf171000
cedarx 9351 0 - Live 0xbf16a000
mali 115330 8 - Live 0xbf140000
ump 34309 17 mali, Live 0xbf131000
gslx680 359718 0 - Live 0xbf0af000
pixcir_cxx 23546 0 - Live 0xbf0a4000
gt811 15930 0 - Live 0xbf09c000
byd693x_ts 9094 0 - Live 0xbf08d000
zet622x 17831 0 - Live 0xbf07f000
ssd253x_ts 21452 0 - Live 0xbf075000
ft5x02 61964 0 - Live 0xbf055000
inet_ctp 2227 7 gslx680,pixcir_cxx,gt811,byd693x_ts,zet622x,ssd253x_ts,ft5x02, Live 0xbf039000
nand 169582 8 - Live 0xbf000000
[email protected]:/ # getevetn -lp /dev/input/event0
sh: getevetn: not found
127|[email protected]:/ # getevent -lp /dev/input/event0
add device 1: /dev/input/event0
name: "sun4i-keyboard"
events:
KEY (0001): KEY_ESC KEY_ENTER KEY_HOME KEY_VOLUMEDOWN
KEY_VOLUMEUP KEY_MENU KEY_SEARCH
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event1
add device 1: /dev/input/event1
name: "axp20-supplyer"
events:
KEY (0001): KEY_POWER
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event2
add device 1: /dev/input/event2
name: "mxc622x"
events:
ABS (0003): ABS_X : value 7, min -128, max 128, fuzz 0, flat 0, resolution 0
ABS_Y : value 3, min -128, max 128, fuzz 0, flat 0, resolution 0
ABS_Z : value 0, min -128, max 128, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event3
add device 1: /dev/input/event3
name: "gt811"
events:
ABS (0003): ABS_HAT0X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT1X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT2Y : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT3X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_DISTANCE : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_MT_TOUCH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_WIDTH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
ABS_MT_TRACKING_ID : value 0, min 0, max 5, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event4
add device 1: /dev/input/event4
name: "gslx680"
events:
ABS (0003): ABS_MT_TOUCH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_WIDTH_MAJOR : value 0, min 0, max 200, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
ABS_MT_TRACKING_ID : value 0, min 0, max 11, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ #
D:
No one can help me? :crying:

Categories

Resources