Indeed, that's how it's done. Development devices like the emulator have ro.secure=0 in /default.prop which means the adb shell runs as root.
(Development here meaning development of android itself; application development does not require privileges and can be done on a consumer device with ro.secure=1 with the possible exception of some extreme debugging measures) On Dec 7, 3:34 pm, A Curtis <ajcurti...@gmail.com> wrote: > > It seems that the easiest thing to do would be to run the shell as > root during development but non-root for production. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
