Posted 21 October 2012 - 09:29 AM

Well I spoke too soon, I had not used sleep mode and wanted to check the system_server cpu load, it was low around 2% so I put my box to sleep and left it for a couple of minutes. once I woke the box it went to 100% then hovered around 100-90%. I shutdown the box and guess what, you got it! it would not boot back up, it hung at the Mele logo.

Do you think the two problems may be related?



Here we are... sadly :/Do you have the F10 remote? I think the 100% CPU phenomenon is linked with the device driver of the F10 remote (USBRemote_Sensor_1915_af11).Because I got a bit further:Here is the logcat command when suspending the device (power button from the F10 remote).system_server gets 100% CPU at the same time as I see:D/Sensors ( 155): Sensor data: t x,y,z: 0.000000 0.000000, 0.000000, 0.000000D/Sensors ( 155): Sensor data: t x,y,z: 3387016.000001 0.000000, 0.000000, 0.000000...I/EventHub( 155): Removing device '/dev/input/js0' due to inotify eventI/EventHub( 155): Removing device '/dev/input/event4' due to inotify event...in logcat. /dev/input/js0 and /dev/input/event4 are removed as soon as I unplug the USB dongle of the remote.I tried again, but just after suspending the device, I unplugged the USB dongle immediately after that.After several minutes, plugging again the usb dongle and going out of suspend shows a system_server reasonably sleeping.For the second problem (never reboots), I cannot say it is related or not. Seems that the system gets short in RAM and kills essential processes.It may be linked to some overhead in startup scripts, like /system/bin/preinstall.sh that is usefull only for the first boot (installs /system/preinstall/ application at first run) but no more for next boots.Just remove it (requires a busybox mount -o remount,rw /system ; busybox rm /system/bin/preinstall.sh) after it has done its job at first start.