[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
@Mighty

i can take a log from lineageos but not from UA, since lineageos supports wireless debugging, but UA does not. (i lost my 30pin cable, only have an iphone one for charging, no data)

ive been looking through my own lineageos log (see below for a trimmed version with the segment where it tried to power on the display) but i cant come to any proper conclusion. (adb logcat -b all showed some more interesting errors, see below)

01-19 14:27:27.304 397 563 I PowerManagerService: Waking up from sleep (uid=1000 reason=android.policy:POWER)...
01-19 14:27:27.308 397 563 E LightsService: Light requested not available on this device. 2
01-19 14:27:27.311 397 397 I screen_toggled: 1
01-19 14:27:27.313 397 397 I power_screen_broadcast_send: 1
01-19 14:27:27.366 397 481 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
01-19 14:27:27.395 397 478 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
01-19 14:27:27.361 885 885 D StatusBar: disable<e i A s b H R c S q >
01-19 14:27:27.403 178 178 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb0b36000
01-19 14:27:27.404 178 229 E IMGSRV : :0: HWC_DSSCOMP_ContextVSyncControl: OMAPFB_ENABLEVSYNC ioctl failed (-1)
01-19 14:27:27.404 178 229 E IMGSRV : :0: HWCUtilVSyncThread: Failed to enable HW vsync events
01-19 14:27:27.455 397 563 I InputReader: Reconfiguring input devices. changes=0x00000004
01-19 14:27:27.497 397 803 I dvm_lock_sample: [system_server,0,WifiStateMachine,11,ActivityManagerService.java,19932,int com.android.server.am.ActivityManagerService.broadcastIntent(android.app.IApplicationThread, android.content.Intent, java.lang.String, android.content.IIntentReceiver, int, java.lang.String, android.os.Bundle, java.lang.String[], int, android.os.Bundle, boolean, boolean, int),-,23426,void com.android.server.am.ActivityManagerService.trimApplications(),2]
01-19 14:27:27.576 397 481 I DisplayPowerController: Unblocked screen on after 210 ms
01-19 14:27:27.578 397 481 I sysui_multi_action: [757,198,758,1,759,0,793,328]
01-19 14:27:27.578 397 481 I power_screen_state: [1,0,0,0,328]
01-19 14:27:27.578 397 481 W PowerManagerService: Screen on took 328 ms
01-19 14:27:27.657 397 397 I device_idle: [0,screen]
01-19 14:27:27.657 397 397 I device_idle_light: [0,screen]
01-19 14:27:27.661 397 468 I device_idle_off_start: screen
01-19 14:27:27.662 397 468 I device_idle_off_complete:
01-19 14:27:27.734 970 970 D DCT : [0]screen on
01-19 14:27:27.734 970 970 D DCT : [0]stopNetStatPoll
01-19 14:27:27.814 397 397 I power_screen_broadcast_done: [1,501,1]
01-19 14:27:28.049 397 2716 E IMGSRV : :0: DeferFlushOpWorker: Timed out waiting for ops to flush
01-19 14:27:28.353 885 2251 E IMGSRV : :0: DeferFlushOpWorker: Timed out waiting for ops to flush

IMGSRV : :0: HWC_DSSCOMP_ContextVSyncControl: OMAPFB_ENABLEVSYNC ioctl failed (-1) does sound alot like it failed to initialize the display.

oh and yeah, the device doesnt crash at all. the whole thing still functions in the background (even going as far as to try and set the brightness of the display, so the drivers havent crashed either, but it fails too for whatever reason) and plays music too.

without a log from UA, i cant compare to see what its supposed to look like, and i can only really speculate, especially since this is basically the only omap device ive ever attempted to work on (and this seems like an issue with omap).

so could anyone get a log from simply unlocking and locking their device in UA? (make sure to use the command "adb logcat -b all" to display all logs, as that little omapfb error didnt show up without it.)

@Alotheone could you try to capture a logcat from UA for me?

side note: very strange that this only occurs in lineageos, if it were related to something as low level as omapfb, i would've expected it to crash in all versions related.

very puzzling issue..