I gather this is a bug introduced in the 1.4 firmware. Let's hope it gets fixed soon.

nz - can you confirm if adb is working on Linux with fw 1.4.09 ?

It stopped working for me when I upgraded to firmware where the unit began to respond with id's 0e79:1361.

I see Archos have posted drivers for Windows (they worked ok now when I tested on XP), will you support Linux as well ?

Same problem, same software, save device IDs, same desire for support.

I note that Ubuntu is doing its thing. My rules.d line is:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666", SYMLINK+="android_adb"

I note that after connection, the symlink /dev/android_adb is in fact created, so I think I got the syntax right.

I wonder if the timing of the update which seems to have cut this off is in any way related to the recent recipes for copying Google's apps and marketplace to the Archos 5.

Jim M.

I would rather guess the majority of Archos dev team actually develop on Vista (or XP Pro ?) and assume this is what the world needs. BTW: I was surprised to see some renowned device geek reviewers are involved in popularising those APK hacks. It's similar to how Google private APK's got illegally redistributed with some popular mobile phone ROM images recently, and where Google stepped in. Here it's also a threat to the Appslib. But from what I have seen the hacks involve using Windows USB drivers and adb provided by Archos for Windows. And these files work for setting up on device debugging with Eclipse and the Android SDK on XP, Win7 or Vista. Those already underway busy developing on Linux are likely quite disturbed in case they happened to reflash to the irrevocable newest release.

I definitely rather develop om Linux due to a much more robust and reliable environment. And good performance.

Hi everyone,

I can't set my archos on device debugging :cry:

I've read all the post and replies and still can't find the correct way to do it, my device is:

$ lsusb | grep Archos
Bus 002 Device 007: ID 0e79:1361 Archos, Inc.

The rule I'm using is:

$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666", SYMLINK+="android_adb"

Once I connect the device, it creates the link:

lrwxrwxrwx 1 root root 15 2009-12-12 00:20 /dev/android_adb -> bus/usb/002/009

So far, so good, however when I look for devices using the adb I get nothing:

# adb devices
List of devices attached

#

For more references I'm using:

Firmware 1.4.09
Ubuntu 9.04
Android Debug Bridge version 1.0.25

Any idea what I'm doing wrong?

Regards,

Question: Is "adb push" command a simple copy? or does it have more inside?

If I connect my archos I can see all the files and folders (including /system)

$ pwd
/media/ARCHOS5

$ ls -l
total 512
drwxrwxrwx 2 10006 10006 4096 2009-12-11 17:36 albumthumbs
-rw-rw-rw- 1 root root 288408 2009-09-29 10:38 AppsLib9-29.apk
-rw-rw-rw- 1 root root 59288 2008-04-14 06:00 autorun.inf
drwxrwxrwx 3 10026 10026 4096 2009-12-11 09:34 data
drwxrwxrwx 2 root root 4096 1969-12-31 18:11 Data
drwxrwxrwx 3 10006 10006 4096 2009-12-11 09:13 DCIM
-rw-rw-rw- 1 root root 79680 1969-12-31 18:22 DevIcon.fil
-rw-rw-rw- 1 root root 10814 1969-12-31 18:22 DevLogo.fil
drwxrwxrwx 2 10027 10027 4096 2009-12-11 14:10 download
drwxrwxrwx 2 root root 4096 1969-12-31 18:22 Downloads
drwxrwxrwx 2 root root 4096 1969-12-31 18:11 Flash
drwxrwxrwx 2 root root 4096 2009-09-14 13:14 Info
drwxrwxrwx 2 root root 4096 2009-12-12 00:48 lost+found
drwxrwxrwx 17 root root 4096 2009-12-11 09:22 Music
drwxrwxrwx 2 root root 4096 1969-12-31 18:11 PDF
drwxrwxrwx 3 root root 4096 1969-12-31 18:07 Pictures
drwxrwxrwx 2 root root 4096 2009-09-14 13:15 Playlists
drwxrwxrwx 3 root root 4096 2009-10-01 15:22 RECYCLER
drwxrwxrwx 5 root root 4096 2009-12-12 00:50 System
drwxrwxrwx 4 root root 4096 1969-12-31 18:22 Video

Warm regards,

Updated firmware to 1.4.16 and no changes. ./adb devices doesn't show any compatible devs.

Canthis be used for windows XP also , because I tried just about everything to get this thing recognized in ADB mode and quite frustrated as of now

Yeah, I'm having the same issue here. Device is showing up as 0e79, but adding that into my rules and restarting udev isn't doing anything. Have they suddenly disabled adb or something? Any suggestions, or anyone having any more luck than I? Using ubuntu 8.04 with firmware 1.4.25.

Go here: http://ubuntuforums.org/showthread.php?t=667720 and follow the outlined directions

Cheers

I still think it's important that Archos respond regarding the lost support for ADB on Linux.

What happened and why did you decide to abandon those who were developing Android apps for the Archos Internet Tablet using Ubuntu ??

Apparently when you fixed that "incorrect vendor ID" something changed that had ADB stop working on Linux.

Is there a way we can get ADB functionality back for Ubuntu ?

Hi guys,

using this trick the 5IT is not recognized by my computer (gentoo):

http://androidtobe.blogspot.com/2009/12/archoss-solution-to-adb-connection-bug.html

Same, I can confirm this doesn't work on Ubuntu 8.04/1.6.X firmware.

Rectification: it works!

I first added the udev rules as indicated somewhere else, then added 0x0e79 in ~/.android/adb_usb.ini, and voila:



gentoo, kernel 2.6.31, x64, and firmware 1.6 on the archos

Thanks laustmcgregor.

I can confirm that after manually adding 0x0e79 in ~/.android/adb_usb.ini this also works in Ubuntu.

Sigh, still no luck on my end. The rules are there, udev and adb have been restarted, it's plugged in with debugging mode on, the line is in ~/.android/adb_usb.ini - still no dice. What kind of voodoo do I need to do?! :P

This is getting me frustrated because it works just fine in windows with the replacement adb :roll: but unlike every other android device I have, just doesn't seem to want to work with ubuntu.

* Googatrix: you're welcome! Now unleash your dev power ;-)

* devo: Did you try threatening an A5IT doll with nails?

Have you double checked your configuration? The tiniest mistake in the writing can have the most disastrous effects (ok maybe that's a bit too dramatic).
Also, you can send me your udev rule, output of lsusb, and adb_usb.ini by mp for "independent" review if you want (given many eyeballs etc..).

laustmcgregor/gunnar-medial/anybody else who's been poking around: couple of questions!

1) I was expecting to find su under /system/xbin but it's not there. does not find anything. Does this mean no root access, even through adb?

2) Same story with the sqlite executable, cannot find it. Any thoughts?

Did you do that in an adb shell? I did and got:



Can't find sqlite though

Yes, through I ran the same in adb shell, there's no su in my tablet.

1) What firmware have you got? Mine is 1.4.25 with Google Market.

2) Did you try running su - (or /system/xbin/su -)? Does it let you login as root?

3) To check for sqlite can you run the following (I think the executable should be sqlite3). On mine it only find a directory ./sqlite_stmt_journals which is empty.