[HTC One S] The Setlaz:
EDIT1: Okay, here is the logcat for the black-screen sliding after unlock with pattern/PIN : http://pastebin.com/f4uwErFR

I was running Opera mini when I get into sleep.

Funky stuff starts line 114-115 then huge stuff line 131 to 250...

And then line 329 - 332 where it should get back to Opera but instead kind of exit and get back to Homescreen.

243: [ 02-27 23:50:00.248 659: 946 I/ActivityManager ] Activity reported stop, but no longer stopping: ActivityRecord{420e9bf8 u0 com.sand.airdroid/.ui.fmp.TakePicActivity_ t5}
318: [ 02-27 23:50:00.768 659: 679 W/ResourceType ] Skipping entry 0x7f040000 in package table 0 because it is not complex!
329: [ 02-27 23:50:01.109 659: 679 I/ActivityManager ] Timeline: Activity_windows_visible id: ActivityRecord{423fb7e8 u0 com.opera.mini.android/.Browser t4} time:338467
332: [ 02-27 23:50:02.660 1216: 1366 V/BufferedAnalyticsState ] Not ready for upload, 260 seconds left.

Note: the 2.5seconds that elapsed between line 329 to 332 pretty much match the black-screen delay after unlocking and waiting for the screen to slide back to the Home-screen

Seems something is not ready and makes Android going back to the log screen instead of the app I was running.

Having said that, from the logcat, it seems Airdoid is trying to do something with the Camera ?

-----------------

EDIT2: Okay, after a reboot, the bug got back, here is the logcat : http://pastebin.com/XBR7xYBS

It's pretty straightforward: it detects the screen orientation change on line 29. Reckon Window freeze timeout on line 55, try to clear orientation line 59.. App Freeze on line 71... and then, I pressed power button and wait for hard reset. One thing that strikes me here is the "Switching descriptor 32 to /dev/null" line 40...

29: Device reconfigured: id=11, name='atmel-touchscreen', size 540x960, orientation 3, mode 1, display id 0
56: [ 02-28 00:21:12.089 669: 685 W/WindowManager ] Window freeze timeout expired.
58: [ 02-28 00:21:12.089 669: 685 W/WindowManager ] Force clearing orientation change: Window{41a192f0 u0 StatusBar}
...and such for keyguard, image wallpaper and launcher
71: [ 02-28 00:21:12.089 669: 685 W/WindowManager ] App freeze timeout expired.
74: [ 02-28 00:21:12.089 669: 685 W/WindowManager ] Force clearing freeze: AppWindowToken{42108940 token=Token{421ddbe8 ActivityRecord{421dd970 u0 com.anddoes.launcher/.Launcher t1}}}

com.anddoes.launcher seems to refer to Apex Launcher though... But even when I installed it, I had the bug... is that possible ?

Anyone running Apex Launcher + Lockscreen ?

And here is the logcat when the rotation is performed without bug: http://pastebin.com/HyHqEDiK

Lot of stuff gets updated... But they look pretty different...

--------------------

And a last one: Screen-on rotate froze, but recovered after a moment. Here is the logcat: http://pastebin.com/0Uvn5wat

95: [ 02-28 22:54:12.108 665: 680 W/WindowManager ] Window freeze timeout expired.
98 : [ 02-28 22:54:12.108 665: 680 W/WindowManager ] Force clearing orientation change: Window{42123b10 u0 StatusBar}
...and such for keyguard, image wallpaper and launcher
110: [ 02-28 22:54:12.118 665: 680 W/WindowManager ] App freeze timeout expired.
113: [ 02-28 22:54:12.118 665: 680 W/WindowManager ] Force clearing freeze: AppWindowToken{42217348 token=Token{42215690 ActivityRecord{42215418 u0 com.anddoes.launcher/.Launcher t1}}}
116: [ 02-28 22:54:12.128 665: 680 I/WindowManager ] Screen frozen for +13s456ms due to Window{42123b10 u0 StatusBar}
119: [ 02-28 22:54:12.188 1038: 1038 I/Choreographer ] Skipped 714 frames! The application may be doing too much work on its main thread.
186: [ 02-28 22:54:19.505 665: 807 W/InputDispatcher ] channel '42123b10 StatusBar (server)' ~ Consumer closed input channel or an error occurred. events=0xd
189: [ 02-28 22:54:19.505 665: 807 E/InputDispatcher ] channel '42123b10 StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!
... and such for ImageWallpaper, Keyguard
249: [ 02-28 22:54:19.515 665: 2749 I/WindowState ] WIN DEATH: Window{42123b10 u0 StatusBar}
... and such for ImageWallpaper, Keyguard
304: [ 02-28 22:54:19.585 665: 680 V/WindowManager ] Removing keyguard window (Did it crash?)

Again, it mentions com.anddoes.launcher which is Apex Launcher but this time, reckons frozen screen and somehow manage to get out of it. Why it didn't manage to do so on the previous logcat ? Was the root-cause really the same ? The previous one does not mention the launcher, and as I said earlier, even with the launcher uninstalled, it does it ast too...

I'm gonna get rid of the launcher and see how it goes...

--------------------

EDIT: Okay, no Apex anymore and still freeze-on-rotate. See logcat: http://pastebin.com/L4K3EnW5

It also recovered eventually.

29:[ 02-28 23:48:04.164 668: 813 I/InputReader ] Device reconfigured: id=11, name='atmel-touchscreen', size 540x960, orientation 3, mode 1, display id 0
35: [ 02-28 23:48:04.354 3344: 3344 W/Launcher ] setApplicationContext called twice! old=com.android.launcher3.LauncherApplication@418de358 new=com.android.launcher3.LauncherApplication@418de358
41: [ 02-28 23:48:09.370 668: 684 W/WindowManager ] Window freeze timeout expired.
44 : [ 02-28 23:48:09.370 668: 684 W/WindowManager ] Force clearing orientation change: Window{421e8b18 u0 StatusBar}
... and such for ImageWallpaper, Keyguard
53: [ 02-28 23:48:09.380 668: 684 W/WindowManager ] App freeze timeout expired.
56 :[ 02-28 23:48:09.380 668: 684 W/WindowManager ] Force clearing freeze: AppWindowToken{421ee818 token=Token{421ec950 ActivityRecord{421ec6d8 u0 com.cyanogenmod.trebuchet/com.android.launcher3.Launcher t1}}}
58: [ 02-28 23:48:09.380 668: 684 I/WindowManager ] Screen frozen for +5s310ms due to Window{421e8b18 u0 StatusBar}
62: [ 02-28 23:48:09.390 3344: 3344 I/Choreographer ] Skipped 282 frames! The application may be doing too much work on its main thread.

Very similar to the previous one with Apex Launcher... Apex just got replaced with com.cyanogenmod.trebuchet here... Would the status bar be actually the problem ?? (and that would explain why it doesn't happen on 19/01 with the same set of settings and apps...)

I really hope that will shed some lights upon my issues and gives some ideas to debug :). ( [MENTION=1815755]intervigil[/MENTION] )

Thanks,

Damien