[Xperia Arc Android Development] _cheh_:
Help needed

Hey Guys,

i need your help:

I'm using the latest version on my sk17i (mango).

Since yesterday i've got a strange problem: every time i slide out the hardware keyboard the display 'splitters'.. means it tries to go to landscape mode but stops working during this process so that it looks really broken and is not responding any more.

if i use the keyboard during this time, it works as normal but the display does not show any change.

The only thing to get the phone working again is sliding the hardwarekeyboard in again and turn the display off. after i've inserted the lock screen pattern i can use the phone (in vertical rotation) normal. If i turn on the automatic rotation, the phone works in landscape rotation too but just if the hardware keyboard is not slid out.

I tried to format the whole system and to install every thing new but that doesn't fixed the problem. If i'm viewing the logcat logs after the 'problem' had happened it shows the following: (i do not know if it is because of the error..)

[..]

06-19 19:37:59.659 W/art ( 1482): Long monitor contention event with owner method=boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int) from Binder.java:4294967294 waiters=0 for 156ms

06-19 19:38:00.172 E/qdoverlay( 231): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument

06-19 19:38:00.184 E/qdoverlay( 231): MdpCtrl failed to setOverlay, restoring last known good ov info

06-19 19:38:00.184 E/qdoverlay( 231): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=2

06-19 19:38:00.184 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=15 MDP_RGBX_8888

06-19 19:38:00.184 E/qdoverlay( 231): src_rect mdp_rect x=1 y=25 w=318 h=454

06-19 19:38:00.184 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=24 w=320 h=456

06-19 19:38:00.184 E/qdoverlay( 231): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=2

06-19 19:38:00.184 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=13 MDP_RGBA_8888

06-19 19:38:00.184 E/qdoverlay( 231): src_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.184 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.184 E/qdoverlay( 231): Ctrl commit failed set overlay

06-19 19:38:00.186 E/qdhwcomposer( 231): configureLowRes: commit failed for low res panel

06-19 19:38:00.233 E/qdoverlay( 231): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument

06-19 19:38:00.233 E/qdoverlay( 231): MdpCtrl failed to setOverlay, restoring last known good ov info

06-19 19:38:00.233 E/qdoverlay( 231): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=2

06-19 19:38:00.233 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=15 MDP_RGBX_8888

06-19 19:38:00.233 E/qdoverlay( 231): src_rect mdp_rect x=1 y=25 w=318 h=454

06-19 19:38:00.233 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=24 w=320 h=456

06-19 19:38:00.233 E/qdoverlay( 231): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=2

06-19 19:38:00.233 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=13 MDP_RGBA_8888

06-19 19:38:00.233 E/qdoverlay( 231): src_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.233 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.233 E/qdoverlay( 231): Ctrl commit failed set overlay

06-19 19:38:00.233 E/qdhwcomposer( 231): configureLowRes: commit failed for low res panel

06-19 19:38:00.249 E/qdoverlay( 231): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument

06-19 19:38:00.249 E/qdoverlay( 231): MdpCtrl failed to setOverlay, restoring last known good ov info

06-19 19:38:00.249 E/qdoverlay( 231): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=2

06-19 19:38:00.249 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=15 MDP_RGBX_8888

06-19 19:38:00.249 E/qdoverlay( 231): src_rect mdp_rect x=1 y=25 w=318 h=454

06-19 19:38:00.249 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=24 w=320 h=456

06-19 19:38:00.249 E/qdoverlay( 231): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=2

06-19 19:38:00.249 E/qdoverlay( 231): src msmfb_img w=320 h=480 format=13 MDP_RGBA_8888

06-19 19:38:00.249 E/qdoverlay( 231): src_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.249 E/qdoverlay( 231): dst_rect mdp_rect x=0 y=0 w=320 h=480

06-19 19:38:00.249 E/qdoverlay( 231): Ctrl commit failed set overlay

06-19 19:38:00.249 E/qdhwcomposer( 231): configureLowRes: commit failed for low res panel

06-19 19:38:01.036 W/Settings( 734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

06-19 19:38:01.086 W/Settings( 734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

06-19 19:38:01.401 W/Settings( 734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

06-19 19:38:01.740 W/Settings( 734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

06-19 19:38:01.882 W/Settings( 734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

06-19 19:38:02.188 W/art ( 568): Long monitor contention event with owner method=void com.android.server.wm.WindowAnimator$1.run() from WindowAnimator.java:130 waiters=0 for 192ms

06-19 19:38:02.228 W/art ( 568): Long monitor contention event with owner method=void com.android.server.am.ActivityManagerService.onWakefulnessChanged(int) from ActivityManagerService.java:10203 waiters=0 for 351ms

06-19 19:38:02.275 W/art ( 568): Long monitor contention event with owner method=void com.android.server.am.ActivityManagerService.onWakefulnessChanged(int) from ActivityManagerService.java:10203 waiters=1 for 373ms

06-19 19:38:02.275 W/art ( 568): Long monitor contention event with owner method=void com.android.server.am.ActivityManagerService.onWakefulnessChanged(int) from ActivityManagerService.java:10203 waiters=2 for 363ms

06-19 19:38:02.310 W/InputMethodManagerService( 568): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@6173eaf attribute=null, token = android.os.BinderProxy@1b15f92b

06-19 19:38:02.745 W/WindowManager( 568): Timeout waiting for drawn: undrawn=[Window{8480338 u0 StatusBar}]

06-19 19:38:03.050 W/OpenGLRenderer( 734): Incorrectly called buildLayer on View: DismissViewButton, destroying layer...

06-19 19:38:03.903 W/art ( 568): Long monitor contention event with owner method=void com.android.server.am.ActivityManagerService.trimApplications() from ActivityManagerService.java:18855 waiters=0 for 385ms

06-19 19:38:04.040 E/WifiStateMachine( 568): cancelDelayedScan -> 61

06-19 19:38:04.425 E/WifiStateMachine( 568): cancelDelayedScan -> 62

06-19 19:38:06.335 W/InputMethodManagerService( 568): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@131b1d54 attribute=android.view.inputmethod.EditorInfo@287344fd, token = android.os.BinderProxy@1b15f92b

06-19 19:38:07.066 W/art ( 970): Long monitor contention event with owner method=java.lang.Boolean com.touchtype.report.TouchTypeStats.saveStatisticsInternal() from TouchTypeStats.java:387 waiters=0 for 395ms

06-19 19:38:08.582 E/AudioTrack( 568): AudioTrack::set : Exit

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

06-19 19:38:08.585 E/AudioPolicyManager( 261): unknown stream type 13

[..]

06-19 19:38:10.282 E/su ( 4579): SU from: u0_a61

i hope you can tell me how to fix the problem. i really realy like the hardware keyboard phone... don't want to loose it. but without the hardware keyboard it's somehow useless because the keyboard is the unique feature i love it for...

thanks guys..