Hi,
I've got a Samsung Nexus S device with the stock ROM, version 2.3.4. The device is not rooted.
I was debugging an application that sets the wallpaper, when suddenly the device rebooted. Since it came back up, I can't access the device. The screen locks itself after 30 seconds (my settings) without being able to unlock it.
I can still access the device using "adb shell". Running "top -m 10 -t" shows that "WindowManagerPolicy" takes almost 100% of the CPU time.
When I hit the lock button the screen doesn't turn on, but logcat shows "D/KeyguardViewMediator( 110): wakeWhenReadyLocked(26)"
When I get an incoming call, the device vibrates but there is no sound. I can't answer the call though.
When I plug/unplug the USB cable the screen turns on for 30 seconds, but it does not respond to my fingers.
Is there anything I can do without performing a hard reset?
Is there any way to kill a thread from shell or lower it's priority (remember there are no root permissions).
I've got a Samsung Nexus S device with the stock ROM, version 2.3.4. The device is not rooted.
I was debugging an application that sets the wallpaper, when suddenly the device rebooted. Since it came back up, I can't access the device. The screen locks itself after 30 seconds (my settings) without being able to unlock it.
I can still access the device using "adb shell". Running "top -m 10 -t" shows that "WindowManagerPolicy" takes almost 100% of the CPU time.
When I hit the lock button the screen doesn't turn on, but logcat shows "D/KeyguardViewMediator( 110): wakeWhenReadyLocked(26)"
When I get an incoming call, the device vibrates but there is no sound. I can't answer the call though.
When I plug/unplug the USB cable the screen turns on for 30 seconds, but it does not respond to my fingers.
Is there anything I can do without performing a hard reset?
Is there any way to kill a thread from shell or lower it's priority (remember there are no root permissions).