What I have observed is that when adb does not have sufficient privileges, the device window shows the connected device as:
???????????? ?? unknown When in this state, attempting to run/deploy an Android application from Eclipse results in a null pointer exception. This will also occur regardless of the presence of other valid devices/emulators in the device window, so I suspect that the deployer interrogates the list of connected devices and throws the null pointer when it hits the "unknown" device. I am pretty new to this, but I outlined a work around that worked for me here: http://notannoidwithdroid.blogspot.com/ //Nicholas On Nov 7, 2:28 pm, PJ <[email protected]> wrote: > To help narrow down the problem, please tell us: > > 1. Have you ever launched *any* app successfully before? (This lets > us know if we are dealing with an Eclipse/Android SDK setup/emulator > issue, or an issue with your app.) > > 2. If yes to #1, have you ever launched *this particular app* > successfully before? (This lets us know if we are dealing with an > issue with creating your project initially, versus an issue where your > project was working before, but you changed something such as your > AndroidManifest.xml file.) > > 3. In Eclipse, in the "Problems" tab at the bottom, do you have any > errors? > > -- PJ > > On Nov 7, 3:11 am, Marton Kodok <[email protected]> wrote: > > > Hello, > > > What might be wrong? > > > eclipse.buildId=M20090917-0800 > > java.version=1.6.0_14 > > java.vendor=Sun Microsystems Inc. > > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=hu_HU > > Framework arguments: -product org.eclipse.epp.package.java.product > > Command-line arguments: -os win32 -ws win32 -arch x86 -product > > org.eclipse.epp.package.java.product > > > Error > > Sat Nov 07 11:06:58 EET 2009 > > An internal error occurred during: "Launching test1". > > > *java.lang.NullPointerException* > > at > > com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.launch( > > Unknown > > Source) > > at > > com.android.ide.eclipse.adt.internal.launch.LaunchConfigDelegate.doLaunch(U > > nknown > > Source) > > at > > com.android.ide.eclipse.adt.internal.launch.LaunchConfigDelegate.launch(Unk > > nown > > Source) > > at > > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurat > > ion.java:853) > > at > > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurat > > ion.java:703) > > at > > org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.ja > > va:866) > > at > > org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069) > > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > > and second error > > *Unable to restore source lookup path - unknown type source container type > > specified: org.eclipse.cdt.debug.core.containerType.mapping* > > > -- > > Márton -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
