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, wrote:
> Hi
> Thanks for your help. It
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 ?
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
On Wed, Jan 13, 2010 at 4:06 AM, vkmgeek 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 w
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..
This is the last message from kerne,
android_power: sleep (0->2) at 156039663510.
