Umm... Eclipse *does* use adb. Perhaps the Eclipse plugin doesn't "su"? Perhaps that works talking to the emulator, but not when talking to an actual device? I think it is probably a bug.
-blake On Jan 11, 12:23 am, Rafael Fernandes <luizraf...@gmail.com> wrote: > in fact is supposed to be like that, this prevents an app to access > data from another... > even the user is different, if you wanna do such dir navigation and/or > install apps > you should use adb, something like... > 1 - adb shell (connect to your device) > 2 - su - (become super user on the shell) > 3 - now you can do whatever you want... > > cheers, > rafa > > On Jan 11, 1:50 am, blake <blake.me...@gmail.com> wrote: > > > I'm, at long last, working with a real phone, instead of just the > > emulator. > > > I've noticed that the Eclipse File Explorer doesn't seem to be able to > > actually explore files on the G1. It shows three top level > > directories: data (empty), sdcard, and system. If I use adb, I can > > see that data does, in fact, have stuff in it. I can't install apps > > with the File Explorer either. I can with adb. They go into the data > > folder (which the Explorer still thinks is empty) > > > Anybody else see this? Better yet, anybody know how to fix it? > > > Thanks, > > -blake --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
