Hello All, I am checking the time taken for the device to goto OFF mode in OMAP4430 Blaze board with L27.13.1 release (http://www.omappedia.com/wiki/L27.INC1.13.1_OMAP4430_GingerBread_ES2.2_Release_Notes)
The time taken from the moment the power key is pressed to suspend the device, to actually goto suspend is around 30secs. Is this an expected behavior? Is there is a way to reduce the time taken to goto OFF mode? Please see the below logs: --------------------------------------------------------------------- [ 47.261199] request_suspend_state: sleep (0->3) at 47787445239 (2000-01-01 00:58:43.466430851 UTC) 01-01 00:58:43.453 I/power ( 1536): *** set_screen_state 0 01-01 00:58:43.570 W/ProcessStats( 1536): Skipping unknown process pid 1823 [ 47.389404] omapdss HDMI: powerchg (a=0,v=1,s=0/0)->(a=0,v=1,s=1) = (0:S) [ 47.588195] <dss_mgr_disable> disabling tv [ 47.592590] omapdss HDMI: pwrchanged => (0,S) = 0 [ 47.597900] active wake lock PowerManagerService [ 47.602752] active wake lock uart_wake_lock, time left 432 01-01 00:59:00.023 W/ActivityManager( 1536): finishReceiver called but active receiver is different [ 77.433410] suspend: enter suspend [ 77.437316] PM: Syncing filesystems ... done. [ 77.443267] Freezing user space processes ... (elapsed 0.02 seconds) done. [ 77.477355] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. [ 77.508544] Suspending console(s) (use no_console_suspend to debug) --------------------------------------------------------------------- Any pointers to this will be helpful. Thanks, Mohan -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
