If you are writing a java app then you need to grab a wake_lock to prevent the phone from going to sleep. This message is only harmful if the kernel has crashed going into suspend or on the way back up to resume.
-- Mike On Wed, Jan 13, 2010 at 10:00 PM, <viral....@gmail.com> wrote: > Hi > Thanks for your help. It makes much sense and helped me to understand the > problem a bit more... > > But still the question is, is it harmful?? > > My application is actually stuck up and not going ahead and it was the last > msg from kernel.... In that context, does it tell something fruitful ? > > On 14-Jan-2010 12:02am, Mike Chan <m...@android.com> wrote: >> That message indicates that the device is going into sleep. State 0 is >> >> >> on, I'm not sure what state 2 is, as android should only use states 0 >> >> >> and 3 (3 is suspend). This is being triggered by userspace so most >> >> >> likely the framework is telling the kernel to sleep (probably screen >> >> >> timeout). >> >> >> >> >> >> What kernel are you using? You might want to consider turning on >> >> >> CONFIG_PM_DEBUG and CONFIG_PM_VERBOSE (I think its pm verbose...). >> >> >> >> >> >> Also I've only seen Android try to go from states 0->3 and 3->0 (which >> >> >> is "mem" and "on" for /sys/power/state >> >> >> >> >> >> >> >> >> -- Mike >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Jan 13, 2010 at 9:50 AM, Yi Sun beyo...@gmail.com> wrote: >> >> >> > On Wed, Jan 13, 2010 at 4:06 AM, vkmgeek viral....@gmail.com> wrote: >> >> >> >> Hi list, >> >> >> >> >> >> >> >> I am developing a middle layer service and also using a third party >> >> >> >> kernel driver.... However, everything runs fine on plain linux but as >> >> >> >> soon as I cross-compile and switch to Android, things stop working.. >> >> >> >> >> >> >> > I assume that by the word "plain linux", it means that you have a >> >> >> > vanilla Linux build that is just like the one we used for other >> >> >> > distros (eg, ubuntu) >> >> >> >> This is the last message from kerne, >> >> >> >> android_power: sleep (0->2) at 156039663510.... >> >> >> >> >> >> >> > It depends on the platform and keyboard/mouse/touch/trackball driver >> >> >> > (whatever you have), you may have to check whether the driver pushed >> >> >> > up a right keyevent to wake up the system. Unlike standard Linux, >> >> >> > Android expects a predefined key to be passed to the user level power >> >> >> > management. And then user level power management will try to hold a >> >> >> > wakelock (in kernel if I remember it right) to keep the system awake, >> >> >> > otherwise, the system will be back to sleep after a very short time. >> >> >> > >> >> >> >> Nothing else... What does this message signifies?? Any importance? or >> >> >> >> just one printk from kernel ??? >> >> >> >> >> >> >> >> Any comment would be appreciated >> >> >> >> >> >> >> >> -- >> >> >> >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> >> website: http://groups.google.com/group/android-kernel >> >> >> >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Android-x86 >> >> >> > http://www.android-x86.org >> >> >> > >> >> >> > -- >> >> >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> > website: http://groups.google.com/group/android-kernel >> >> >> > >> >> >> > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel >
-- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
