One more observation: when we type the command "setprop
persist.service.adb.enable 1", target goes in "hang" state.
-Vrukesh
On Mar 4, 1:17 pm, Al Sutton wrote:
> Yup, kill-servered, re-installed drivers, muttered secret incantation of
> the frustrated smartphone user.
>
> Nothing worked.
>
> So
Yup, kill-servered, re-installed drivers, muttered secret incantation of
the frustrated smartphone user.
Nothing worked.
So I've written it off until a new driver appears.
Al.
mark.ka...@gmail.com wrote:
> Ah the joy of Vista... Did you try running 'adb kill-server' several
> times while th
Hi Al, Mark,
We are using Windows XP.
Vrukesh
On Mar 4, 2:37 am, mark.ka...@gmail.com wrote:
> Ah the joy of Vista... Did you try running 'adb kill-server' several
> times while the device is unplugged, then replugging it? I've had to
> do that to see the device once in a while, but I'm not u
Ah the joy of Vista... Did you try running 'adb kill-server' several
times while the device is unplugged, then replugging it? I've had to
do that to see the device once in a while, but I'm not using Vi$ta .
On Mar 3, 2:58 am, Al Sutton wrote:
> If you're using Vista there is no fix.
>
> It's
If you're using Vista there is no fix.
It's been broken for a while;
http://groups.google.com/group/android-developers/browse_thread/thread/5c9b33eb9373327f
Al.
vrukesh wrote:
> Hi,
>
> We are using Android 2.6.25 Linux Kernel on ARM-based chip and have
> Android SDK 1.0r2 on PC.
>
> When buil
5 matches
Mail list logo
