[OnePlus 3 & 3T Cross Device Development] Crashlooper:
Oneplus 3 screen unresponsive after locking screen

Ok so the former build from october didn't work out: freezes and bootloop.

Guess i'll be going back to may build and tinker around?

I also managed to pull a logcat from my former screen unresponsive episodes (only pulled logcat while the problem was occuring-did not occur while plugged in USB --no deep sleep probably?--)

I have no idea where to look or what to highlight? But i believe the problem starts when he leaves "dozing" (and i don't know whether leaving dream is only when i press the power button).

I DreamManagerService: Entering dreamland.

09-05 15:42:29.802 1034 1322 I PowerManagerService: Dozing...

09-05 15:42:29.804 1034 1317 I DreamController: Starting dream: name=ComponentInfo{androidsystemuiandroidsystemuidozeDozeService}, isTest=false, canDoze=true, userId=0

09-05 15:42:30.041 1034 1300 I WindowManager: OverscanTimeout run

09-05 15:42:31.121 1034 1516 I PowerManagerService: Waking up from dozing (uid 1000)...

09-05 15:42:31.123 1034 1322 I DisplayPowerController: Blocking screen on until initial contents have been drawn.

09-05 15:42:31.186 1034 1319 I DisplayManagerService: Display device changed state: "Ingebouwd scherm", ON

09-05 15:42:31.191 1034 1555 D LiveDisplay: Set color balance = 0 (temperature=8000)

09-05 15:42:31.269 1034 1516 I WindowManager: Suppressed redundant power key press while already in the process of turning the screen on.

09-05 15:42:31.456 1034 1322 I DisplayPowerController: Unblocked screen on after 334 ms

09-05 15:42:31.462 1034 1322 I VrManagerService: VR mode is allowed

09-05 15:42:31.463 1034 1322 I DreamManagerService: Gently waking up from dream.

09-05 15:42:31.472 1034 7250 I DreamManagerService: Leaving dreamland.

09-05 15:42:31.472 1034 1317 I DreamController: Stopping dream: name=ComponentInfo{androidsystemuiandroid.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0

09-05 15:42:32.684 1034 2312 I ActivityManager: Setting hasTopUi=true for pid=1589

09-05 15:42:33.850 1034 7250 I ActivityManager: START u0 {flg=0x10000000 cmp=MapsActivity} from uid 10103 on display 0

09-05 15:42:33.857 1034 3784 E ActivityManager: applyOptionsLocked: Unknown animationType=0

09-05 15:42:33.918 1034 1941 E BatteryStatsService: no controller energy info supplied

09-05 15:42:33.938 1034 1941 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

09-05 15:42:34.356 1034 3784 I ActivityManager: Setting hasTopUi=false for pid=1589

09-05 15:42:36.183 1034 2370 I ActivityManager: Setting hasTopUi=true for pid=1589

09-05 15:42:37.417 1034 7255 W InputMethodManagerService: Window already focused, ignoring focus gain of: android.internal.view.IInputMethodClient$Stub$Proxy@71786e6 attribute=null, token = android.os.BinderProxy@9858c4d

09-05 15:42:37.428 1034 7245 I ActivityManager: Setting hasTopUi=false for pid=1589

09-05 15:42:39.019 1034 1515 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=.launcher.GEL (has extras)} from uid 1000 on display 0

09-05 15:42:39.308 1034 1284 E BatteryStatsService: no controller energy info supplied

09-05 15:42:39.331 1034 1284 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

09-05 15:42:39.600 1034 2327 I ActivityManager: START u0 {flg=0x10804000 cmp=android.systemui/.recents.RecentsActivity} from uid 10028 on display 0

09-05 15:42:42.367 1034 2370 E ActivityManager: applyOptionsLocked: Unknown animationType=0

09-05 15:42:42.391 1034 2322 W AlarmManager: Suspiciously short interval 10000 millis; expanding to 60 seconds

09-05 15:42:44.338 1034 7257 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=MapsActivity} from uid 10107 on display 0

09-05 15:42:44.414 1034 2357 E BatteryStatsService: no controller energy info supplied

09-05 15:42:44.434 1034 2357 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

09-05 15:42:51.765 1034 1516 I PowerManagerService: Going to sleep due to power button (uid 1000)...

09-05 15:42:52.240 1034 1298 I VrManagerService: VR mode is disallowed

09-05 15:42:52.289 1034 1319 I DisplayManagerService: Display device changed state: "Ingebouwd scherm", OFF

09-05 15:42:52.405 1034 7258 E BatteryStatsService: no controller energy info supplied

09-05 15:42:52.419 1034 7258 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

09-05 15:42:52.520 1034 1322 I DreamManagerService: Entering dreamland.

09-05 15:42:52.520 1034 1322 I PowerManagerService: Dozing...

plz help! would be much appreciated!! - i will try naptime too