On Jan 1, 6:27 pm, Quartz william.qua...@gmail.com wrote:
But basically, I have to start the adb deamon a certain way, as
follows: kill server if running, then sudo adb devices.
Running adb as root is necessary if you don't get the USB permissions
set up right. For example:
% lsusb
[...]
Bus
I was also able to get adb to see my devices as a normal user, but
with a small quirk. Note: I am using Ubuntu Gutsy (7.10).
I have written it up here:
http://william.quartz.googlepages.com/mobile%3Agoogleg1
But basically, I have to start the adb deamon a certain way, as
follows: kill server
Thanks Marc!
That worked for me on Fedora 6. The only thing I had to do different
was:
adb kill-server
adb start-server
Thanks again,
-Chris
On Oct 24, 12:23 am, Wanted unique nickname [EMAIL PROTECTED]
wrote:
Wow, that totally worked. For those who are interested, here is my
complete
Hey,
On Oct 23, 9:23 pm, Wanted unique nickname [EMAIL PROTECTED]
wrote:
Wow, that totally worked. For those who are interested, here is my
complete Suse example:
For those still struggling with OpenSUSE 11, here's mine:
Like Nick's, this goes in
/etc/udev/rules.d/11-android.rules
and
Just a reminder to everyone in case some here are not aware - the G1
won't advertise its 0c02 product id unless you first do the
following on the device:
Settings - Applications - Development - USB debugging = ON
if lsusb returns 0bb4:0c01, not 0bb4:0c02, then this is likely your
problem.
On Oct 28, 11:03 pm, craig3353 [EMAIL PROTECTED] wrote:
I have been unable to connect to a device on Gentoo, and none of the
advice above helped. Here's what worked for me:
1. Get rid of the udev rules. They cause the device node to be created
as a block device for USB storage, and this is
Sorry about that. Major typo. NAME=username should be
OWNER=username.
On Oct 23, 10:23 pm, Wanted unique nickname [EMAIL PROTECTED]
wrote:
Wow, that totally worked. For those who are interested, here is my
complete Suse example:
Before you connect the g1 via usb
[create the udev rules
Same problem on Fedora, with a partial solution:
Try ls -l /dev/bus/usb/* before and after plugging in the device,
and compare that to ls -l /proc/bus/usb/* before and after plugging
in.
Looking through the source code, I noticed adb only scans /dev/bus/
usb, not /proc/bus/usb. On my Fedora
FYI there is a better way to do this than setting the OWNER
attribute, by using pam authentication to give the console user r/w
perms when the device is plugged in. If anyone is still having probs,
try this solution:
https://bugzilla.redhat.com/show_bug.cgi?id=468532
There is more info there
just tried this and it doesn't work on ubuntu. i tried it your way and
the way on googles site but neither work. the device just keeps being
seen as a USB Mass Storage device.
On Oct 23, 10:23 pm, Wanted unique nickname [EMAIL PROTECTED]
wrote:
Wow, that totally worked. For those who are
No joy on Fedora either... the /dev/android link is created but adb
devices doesn't show any devices.
On Oct 24, 1:31 am, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
just tried this and it doesn't work on ubuntu. i tried it your way and
the way on googles site but neither work. the device just
Well, I suggest you check the permissions *and* ownership of /dev/
android.
On my Debian system I used OWNER=username (not NAME=android).
On my Debian system I also had to use SUBSYSTEMS=usb (and not
SUBSYSTEM=usb).
Both are critical. The first is because Debian by default will mount
the usb
It seems that the device needs to be owned by the user running 'adb'.
At a first approximation anyway; I've worked on Android for a full
three days or something. Adding OWNER='yourusername' should fix
it.
Works for me on a Debian (Testing) system where I mount it to to /dev/
sdb (though I
Wow, that totally worked. For those who are interested, here is my
complete Suse example:
Before you connect the g1 via usb
[create the udev rules file, and choose a number lower than the
default rules file]
/etc/udev/rules.d/11-android.rules
[copy the following text to that file, and replace
this sounds like my problem as well.
This really should be mentioned on
http://code.google.com/android/intro/develop-and-debug.html
thanks,
-Ben
On Oct 21, 8:42 pm, nkijak [EMAIL PROTECTED] wrote:
That possibly did the trick. I had to restart the phone. Maybe for
the Debug when USB thing
We just updated the documentation.
Developing on devices is explained here:
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
On Tue, Oct 21, 2008 at 11:45 PM, bhines [EMAIL PROTECTED] wrote:
this sounds like my problem as well.
This really should be
Does anyone know how to perform Step 3 for developing on Suse Linux?
When I run dmesg I get some relevant info, but I don't know enough
about udev to make this work on Suse...
usb 1-10: new high speed USB device using ehci_hcd and address 10
usb 1-10: new device found, idVendor=0bb4,
I was able to write the following udev rule, but running adb devices
does not show any device. What does adb look for when its scanning
for devices?
Here is my rule in /etc/udev/rules.d/11-android.rules
SUBSYSTEM==usb, ATTRS{idVendor}==0bb4, ATTRS{idProduct}==0c02,
MODE=0666, NAME=android
Great news - thanks! It works on my Vista machine. Installed,
restarted and bingo. That means I can start programs. Debugging does
not seem to work. The G1 displays a message Waiting for Debugger and
it keeps waiting for a long time. Nothing happens. I am trying to run
the Sudoku example from the
You have to add android:debuggable=true to the application tag in
your AndroidManifest.xml.
On Wed, Oct 22, 2008 at 10:35 PM, marstein [EMAIL PROTECTED] wrote:
Great news - thanks! It works on my Vista machine. Installed,
restarted and bingo. That means I can start programs. Debugging does
I've put together a list of instructions to debug from eclipse right
on the G1 (for Windows):
http://href.to/eIM
Regards, plusminus
http://anddev.org
# Worlds largest Android Development Community / Tutorials
On 23 Okt., 01:35, marstein [EMAIL PROTECTED] wrote:
Great news - thanks! It works
That possibly did the trick. I had to restart the phone. Maybe for
the Debug when USB thing to take effect?
Thanks
On Oct 21, 11:33 pm, Xavier Ducrohet [EMAIL PROTECTED] wrote:
To debug on devices you need to set the 'debuggable' attribute of the
application node to true (in
To debug on devices you need to set the 'debuggable' attribute of the
application node to true (in AndroidManifest.xml).
Make sure to set it back to false before releasing your application.
Xav
On Tue, Oct 21, 2008 at 8:24 PM, nkijak [EMAIL PROTECTED] wrote:
I can't seem to get the eclipse
23 matches
Mail list logo
