Basically android does a sync, an emergency remount (if specified in the flags) and then call to reboot.
Like I've said, I've tried to eliminate anything to do with the remount, and completely temporarily commented out the the call to emergency_remount_ro... I do appreciate any ideas though... thanks for responding. On Friday, January 10, 2014 6:30:44 AM UTC-8, Alvin Wong wrote: > > I am not familiar with the Android architecture, but if you list the > mounted partitions after the emergency remount, all non-tmpfs/ramfs should > be remounted as ro. Check if there are any that is still rw, because the > reboot code system/core/libcutils/android_reboot.c basically checks for > this. You can also try placing log output to see where it got stuck at. -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" 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.
