Have you previously connected your phone to the computer before turning on
the ability to allow unsigned applications and USB debugging?
I found out the hard way that if you don't have those options on the very
first time you connect your phone to a Windows machine then there are all
sorts of hoop
Yes, I did connect it before, whit the fancy Samsung software. It even
behave strange with it, because it always see two device instead of
one.
No idea if adb should work with the SDK drivers or if I have to lookup
some specific samsung drivers. I did post to Samsung forum as well,
but no solving
Try this link:
http://www.anddev.org/debugging-installing_apps_on_the_g1_windows_driver-t3236.html
Step 5 most likely will not happen. If it does not then try the
following:
- Open Device Manager
- You should see something mentioning your Galaxy, or an ADB
Interface, or perhaps even just somethi
Thanks Justin!
Your tip worked. As you said, step 5 did not happen, but manually
"Upgrading" the driver in device manager, and choosing "have disk"
definitely works !
Thanks again!
Felix
On 1 Set, 09:10, Tikoze wrote:
> Try this
> link:http://www.anddev.org/debugging-installing_apps_on_the_g1_
Glad I could be of assistance!
Yeah, there are lots of potential problems with Windows machines and getting
started with developing for Android... particularly if you connected your
phone before turning on debugging (AFAIK, there is no documentation about
that little tidbit of information, either
5 matches
Mail list logo
