search

dezertdawg / urukdroid

Automatically exported from code.google.com/p/urukdroid
0 stars 0 forks source link

adb is not working #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Enable USB Debug Development mode
2.Using USB cable link up Archos 101 & PC
3.Open a terminal and using adb devices to check whether Archos could be 
connected.

What is the expected output? What do you see instead?
After typing the command, it should return the serial of the connected device.

Did previous version of UrukDroid did it right? Does it work on Archos
default OS correctly?
Previous version never been installed. It works well under Archos default 
firmware (2.3.26).

What version of UrukDroid are you using? What version of Archos device?
Version 1.0; Archos 101it

Please provide any additional information below.

dmesg showed some error had been detected as below:

adb_release
adb_open
init: sys_prop: permission denied uid:2000  name:adb.connected
usb_switch_print_state: 3 ATTACHED_HOST

usb_switch_print_state: 3 ATTACHED_HOST

disabling adb
adb_release

Original issue reported on code.google.com by shuk...@gmail.com on 3 Jul 2011 at 1:45

GoogleCodeExporter commented 8 years ago 
Same problem for me. adb works with standard android installation but not when 
URUK is booted.
Cannot mount usb either, not sure if this is connected

dmesg:

[10906.710065] usb 2-1.3: new high speed USB device using ehci_hcd and address 
10
[10906.795948] usb 2-1.3: New USB device found, idVendor=0e79, idProduct=1419
[10906.795952] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[10906.795955] usb 2-1.3: Product: A101it
[10906.795956] usb 2-1.3: Manufacturer: Archos
[10906.795958] usb 2-1.3: SerialNumber: A10-72F40002-9FF80000-0160AE29-15016029
[10906.796908] scsi11 : usb-storage 2-1.3:1.0
[10907.796603] scsi 11:0:0:0: Direct-Access     ARCHOS   A101it           0000 
PQ: 0 ANSI: 2
[10907.796769] sd 11:0:0:0: Attached scsi generic sg4 type 0
[10907.797347] scsi 11:0:0:1: Direct-Access     ARCHOS   A101it           0000 
PQ: 0 ANSI: 2
[10907.797453] sd 11:0:0:1: Attached scsi generic sg5 type 0
[10907.805547] sd 11:0:0:0: [sdd] Attached SCSI removable disk
[10907.807240] sd 11:0:0:1: [sde] Attached SCSI removable disk

Original comment by walter.k...@gmail.com on 5 Jul 2011 at 11:37

GoogleCodeExporter commented 8 years ago 
I have tested the usb connection working well when using windows vista. The 
archos 101 could be connected directly by "adb shell" command. Anyway, I am 
using sshd to access archos console. The problem seems related to linux udev 
only. Good luck

Original comment by shuk...@gmail.com on 6 Jul 2011 at 10:13

GoogleCodeExporter commented 8 years ago 
Does the problem exist in UD1.5?

Original comment by adrian.s...@gmail.com on 15 Aug 2011 at 7:19

GoogleCodeExporter commented 8 years ago 
Just download UD1.5. Result will be provided ASAP.

Original comment by shuk...@gmail.com on 20 Aug 2011 at 11:18

GoogleCodeExporter commented 8 years ago 
I just want to test the ADB connection by UD1.5, however the system was crashed 
when proceed upgrade. Now I our must re-install every; I think ....

Original comment by shuk...@gmail.com on 20 Aug 2011 at 12:39

GoogleCodeExporter commented 8 years ago 
You don't have to reinstall "every" - just root 
(http://code.google.com/p/urukdroid/wiki/EasyInstall#ReInstall_UrukDroid). I've 
asked people to test ADB (on dev thread). They claim it's working. However it 
does not work for me (on Linux) - but my USB was broken and I can't be sure if 
it's not because of this. Now my device gets RMA...

Original comment by adrian.s...@gmail.com on 22 Aug 2011 at 3:30

GoogleCodeExporter commented 8 years ago 
At last I have reinstall UD1.5 to my Archos 101 under recovery mode. However, 
the adb commands still cannot connect to such device as before. I have check 
with others device and it proofed that the USB port is working properly. Those 
capture messages for three different devices is attached for your reference. 

First is archos 101 - adb devices : show nothing
Second is HTC desire - adb devices : show "HT05PPL06??? device"
Third is Huawei Ideos - adb devices : show "F4C714211??? device"
Then archos 101 tried again and it is same as before

Original comment by shuk...@gmail.com on 24 Aug 2011 at 2:31

Attachments:

GoogleCodeExporter commented 8 years ago 
Are you sure your adb service on Archos is running? (ps -ef | grep adb).
Could you check errors messages from firs error report on UD 1.5?

Original comment by adrian.s...@gmail.com on 27 Aug 2011 at 8:58

GoogleCodeExporter commented 8 years ago 
It seems the adb service could not be started on Archos; since I cannot get any 
result from ps. However, I do get from dmesg showing some activity of adbd had 
been executed as per attached file. It seemed something was going wrong when 
adbd was startup.

However, after second time re-plug the USB to the Archos, I could get the adbd 
was running as listed below.

# ps -ef | grep adb
29079 2000       0:00 /sbin/adbd
29088 root       0:00 grep adb

Though the command on my linux workstation "adb devices" still shows nothing.

Original comment by shuk...@gmail.com on 27 Aug 2011 at 4:15

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi everybody, the problem finally was resolved. It is my fault. I should have 
update my android SDK first. 
I was doubtful, since the tablet could be access thru' adb under windows 
condition and I had checked the message before and after the usb cable was 
connected. The message of the tablet showed similar under window & linux. On 
the other hand, my linux workstation could access other android devices (2 
Huawei phone, 1 HTC and 1 samsung) without any problem. 
Today after I have update my SDK, I try again and it was working. I don't know 
why  UrukDroid must be using latest SDK. 
Anyway my problem is solved. Good luck to everybody

Original comment by urukdr...@gmail.com on 12 Oct 2011 at 3:53

GoogleCodeExporter commented 8 years ago 
So I close the issue now.

Original comment by adrian.s...@gmail.com on 4 Nov 2011 at 10:22

GoogleCodeExporter commented 8 years ago 
Of course,  adb could access UD1.5 device without any problem

Original comment by shuk...@gmail.com on 5 Nov 2011 at 5:43