Doing a dmesg or cat /proc/kmsg over adb after few seconds (considering no screen task is there) after screen has hit off (this is called ealy suspend). Note : you will not hit suspend if you connected over adb (usb is active) so connect after suspend might have hit and got failed. Check for the last log print that says wakelock or similar xxxlockxx (wakelock variable name)... Usually its a wakelock (type of software lock, so long a process is holding it system dosent hit suspend) which stops from suspend.
A common kernel log print indicating last prints of suspend is like "freezing ......'. So look for anyting just above it which says suspend fail , wake lock etc.. On Thursday, July 18, 2013 11:22:07 PM UTC+5:30, ngujason wrote: > > Hi, > > Is there a way to find out which task (or related information) when system > suspend/resume fails? > > Thanks. > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
