[Galaxy Note GT-N7000 Original Android Development] Roland_SGN:
I updated from 3.60 to 3.69 and I am happy to see, that the whole phone works much better and more stable:fingers-crossed: Anyway, I still got similar issues as mentioned before, that the screen-orientation change, especially for camera has a laggy impact. With laggy I mean the following excerpt from the USB-Debug:

07-26 16:54:38.815: D/Tasker(4088): 16.54.38#M: this item ptime: 1 qcpt now 1
07-26 16:54:39.375: W/WindowManager(2214): Window freeze timeout expired.
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{4191b7e0 u0 SystemBar}
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{4189f870 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{4192b2b0 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{418f94c8 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{414d80a0 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{4158f828 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{4188ec78 u0 }
07-26 16:54:39.375: W/WindowManager(2214): Force clearing orientation change: Window{41baca48 u0 com.android.systemui.ImageWallpaper}
07-26 16:54:39.545: D/lights(2214): set_light_buttons off
07-26 16:54:39.650: I/Choreographer(2385): Skipped 126 frames! The application may be doing too much work on its main thread.
07-26 16:54:40.035: I/dalvikvm-heap(32643): Grow heap (frag case) to 26.626MB for 4518160-byte allocation
07-26 16:54:40.320: D/Tasker(4088): 16.54.40#M: pi: time since last process end: 1508, reset qcpt

Laggy in that sense, that I started to change orientation at 54:38.815 and ended around 54:40.0xx. So, the orientation change is about 1.200 ms which I perceive as much in sense of user-experience. And I wonder, if system-crashes might happen out of the reason that the response for orientation change takes too long.

Also an additional note to the log: I notice that before the WindowManager prints out the messages, I see there almost everytime at least one process died, e.g.

07-26 16:41:51.070: I/ActivityManager(2214): Process com.fingersoft.cartooncamera (pid 31061) has died.
07-26 16:41:51.190: E/AppsCustomizePagedView(2531): Widget ComponentInfo{com.sisedi.widgets.screentimeout/com.sisedi.widgets.screentimeout.screenTimeoutWidget} has invalid dimensions (0, 0)
07-26 16:41:51.580: I/ActivityManager(2214): Process com.google.android.apps.plus (pid 31112) has died.
...
07-26 16:42:49.305: I/ActivityManager(2214): Process com.google.android.gsf.login (pid 31367) has died.
07-26 16:42:49.310: I/ActivityManager(2214): Process com.android.gallery3d (pid 30158) has died.
07-26 16:42:49.320: I/ActivityManager(2214): Process com.android.email (pid 31186) has died.
...
07-26 16:44:38.045: I/ActivityManager(2214): Process com.android.gallery3d (pid 31703) has died.
...
07-26 16:47:39.805: I/ActivityManager(2214): Process com.keramidas.TitaniumBackup (pid 32380) has died.
07-26 16:47:39.935: I/ActivityManager(2214): Process net.nurik.roman.dashclock (pid 32400) has died.
07-26 16:47:40.025: I/dalvikvm-heap(32643): Grow heap (frag case) to 19.183MB for 898720-byte allocation
07-26 16:47:40.190: I/ActivityManager(2214): Process com.google.android.googlequicksearchbox (pid 32234) has died.
07-26 16:47:40.390: I/ActivityManager(2214): Process com.google.android.gms (pid 32292) has died.

Is this normal? But anyway, 3.69 runs much, much smoother and I see a great improvement.