request_suspend_state: sleep (0-3) at 234899703 (2011-09-08
01:41:52.45700 UTC)
Queue work: early_suspend_work
Start: early_suspend_work
early_suspend: call handlers
enter - aml_gc0308_early_suspend
lcd_suspend
osd_suspended
sys_suspend
early clk HHI_VID_CLK_CNTL(105f) off
early pll
Where's the problem? The system is just suspending when asked by
Android and seems to be doing it properly.
Regards
-- Ashwin
On Thu, Oct 14, 2010 at 12:16 AM, liu guoqing lgqg...@gmail.com wrote:
i have ported android-2.1 to my s3c6410 platform
but when it start after a moment,it print
did u meant no UI? seems all services are launched atleast., can u
share logcat log?
if system suspend is bothering, u can block by holding a wakelock
echo test /sys/power/wake_lock
later, release it via
echo test /sys/power/wake_unlock
On Thu, Oct 14, 2010 at 6:26 PM, Ashwin Bihari
here is the logcat :
the application calendar storage(process com.android)
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
pm_op():
Set the no_console_suspend flag in U-Boot while booting Android and
that'll tell you if Linux is failing for any particular reason while
suspending..
Regards
-- Ashwin
On Thu, Oct 14, 2010 at 7:06 PM, liu guoqing lgqg...@gmail.com wrote:
here is the logcat :
the application calendar
i have ported android-2.1 to my s3c6410 platform
but when it start after a moment,it print follow
request_suspend_state sleep (0-3) at 286838669063 (2029-06-12
15:19:00.243719470 UTC)
I/power ( 695): *** set_screen_state 0
PM: Syncing filesystems ... done.
