Android App Inventor: Working on Linux?

[Guest lord_alan]

Has anyone managed to get the App Inventor working on the Streak from a Linux Computer?

In fact I'm not getting passed the sdk tool the sdk and the "adb devices" command to even SEE my Streak.

I'm on the (unrooted) 2.1-update1 6941 Build.

On the App Inventor Forums all the talk is of using the Dell PC USB driver:

http://groups.google.com/group/appinventor...9cfca96131c6622

That's useless for Linux.

TIA

Al

[Guest fards]

My works fine, been playing with the tutorials all day and made an enhanced version of the paint apparently for my daughter using it on my ubuntu/mint/ldxfm mishmash at work

Have you set the 51android rules correctly as per the instructions?

I have found that having a term open to adb kill-server|adb start-server helps as it doesn't want to reconnect after a phone call.

If you're using Linux, it is possible that the system is not configured to recognize the device. The following actions might help SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666" Modify the idVendor code and idProduct values to match your device ( list of codes)

"

Dell is 413c idVendor

from http://appinventor.googlelabs.com/learn/troubleshooting.html

Edited August 25, 2010 by fards

[Guest lord_alan]

My works fine, been playing with the tutorials all day and made an enhanced version of the paint apparently for my daughter using it on my ubuntu/mint/ldxfm mishmash at work

Have you set the 51android rules correctly as per the instructions?

Thanks for the reply.

I stupidly followed the Getting Started page (http://d.android.com/guide/developing/device.html#setting-up) where the udev rule looks like this (I did change the Vendor ID to 413c BTW):

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

But there are no mentions of any version of Ubuntu later than Hardy on that page so I was a tad sceptical!

However, the link you sent looked far more promising...

According to lsusb, my Streak has the following vendor and product IDs:

Bus 002 Device 004: ID 413c:b007 Dell Computer Corp.

So I created a udev rule that looks like this:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="413c", ATTRS{idProduct}=="b007", MODE="0666"

But adb devices still returns nothing after unplugging and plugging back in, starting and stopping the adb server etc.

In syslog though, I notice an interesting set of errors I've not seen before:

This is plugging in the Streak:

Aug 26 08:56:20 lobsang kernel: [ 3490.224795] usb-storage: device found at 10

Aug 26 08:56:20 lobsang kernel: [ 3490.224797] usb-storage: waiting for device to settle before scanning

Aug 26 08:56:25 lobsang kernel: [ 3495.224974] usb-storage: device scan complete

Aug 26 08:56:25 lobsang kernel: [ 3495.225714] scsi 12:0:0:0: Direct-Access Dell Mini5 0000 PQ: 0 ANSI: 2

Aug 26 08:56:25 lobsang kernel: [ 3495.226602] sd 12:0:0:0: Attached scsi generic sg2 type 0

Aug 26 08:56:25 lobsang kernel: [ 3495.234474] sd 12:0:0:0: [sdb] Attached SCSI removable disk

This is me running sudo adb start-server:

Aug 26 08:57:53 lobsang kernel: [ 3583.568015] usb 7-2: new full speed USB device using uhci_hcd and address 46

Aug 26 08:57:54 lobsang kernel: [ 3583.770038] usb 7-2: unable to read config index 0 descriptor/all

Aug 26 08:57:54 lobsang kernel: [ 3583.770042] usb 7-2: can't read configurations, error -84

Aug 26 08:57:54 lobsang kernel: [ 3583.884012] usb 7-2: new full speed USB device using uhci_hcd and address 47

Aug 26 08:57:54 lobsang kernel: [ 3584.066026] usb 7-2: unable to read config index 0 descriptor/all

Aug 26 08:57:54 lobsang kernel: [ 3584.066031] usb 7-2: can't read configurations, error -84

Aug 26 08:57:54 lobsang kernel: [ 3584.180011] usb 7-2: new full speed USB device using uhci_hcd and address 48

Aug 26 08:57:54 lobsang kernel: [ 3584.315017] usb 7-2: unable to read config index 0 descriptor/all

Aug 26 08:57:54 lobsang kernel: [ 3584.315022] usb 7-2: can't read configurations, error -84

Aug 26 08:57:54 lobsang kernel: [ 3584.428011] usb 7-2: new full speed USB device using uhci_hcd and address 49

Aug 26 08:57:54 lobsang kernel: [ 3584.535067] usb 7-2: unable to read config index 0 descriptor/all

Aug 26 08:57:54 lobsang kernel: [ 3584.535072] usb 7-2: can't read configurations, error -84

Aug 26 08:57:54 lobsang kernel: [ 3584.536981] hub 7-0:1.0: unable to enumerate USB device on port 2

Further investigation leads me to think is just because I am choosing not to mount the sd card from the Android Alert. If I do choose to mount it, this error does not occur. But adb devices still returns nothing. :huh:

Below is the verbose output of lsub for my Streak in case this provides any useful data.

If you have any other ideas as to what might be the issue I'd be grateful for them. Im running Ubuntu 10.04 32bit with a stock kernel:

uname -a returns:

Linux lobsang 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:12:52 UTC 2010 i686 GNU/Linux

Thanks in advance.

Al

Bus 002 Device 011: ID 413c:b007 Dell Computer Corp.

Device Descriptor:

bLength 18

bDescriptorType 1

bcdUSB 2.00

bDeviceClass 0 (Defined at Interface level)

bDeviceSubClass 0

bDeviceProtocol 0

bMaxPacketSize0 64

idVendor 0x413c Dell Computer Corp.

idProduct 0xb007

bcdDevice 2.24

iManufacturer 1 Dell Incorporated

iProduct 2 Dell Mini 5

iSerial 3 0354000030051777

bNumConfigurations 1

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 55

bNumInterfaces 2

bConfigurationValue 1

iConfiguration 0

bmAttributes 0x80

(Bus Powered)

MaxPower 500mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 8 Mass Storage

bInterfaceSubClass 6 SCSI

bInterfaceProtocol 80 Bulk (Zip)

iInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x01 EP 1 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 1

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 1

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 255 Vendor Specific Class

bInterfaceSubClass 66

bInterfaceProtocol 1

iInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x82 EP 2 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x02 EP 2 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 0

Device Qualifier (for other device speed):

bLength 10

bDescriptorType 6

bcdUSB 2.00

bDeviceClass 0 (Defined at Interface level)

bDeviceSubClass 0

bDeviceProtocol 0

bMaxPacketSize0 64

bNumConfigurations 1

Device Status: 0x0000

(Bus Powered)

[Guest fards]

afraid I don't know.

I did follow the setting up page as well, so I don't think it's that.

my udev rule is

SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"

I have to admit changing it to the other one made no difference.

did you do chmod a+r /etc/udev/rules.d/51-android.rules

I'm running same kernel version

I never run adb as sudo, I don't think it's needed but doubt that's your issue.

there should be no need to mount the sdcard.

is everything else you connect working? just wondering if its a usb thing?

[Guest lord_alan]

afraid I don't know.

I did follow the setting up page as well, so I don't think it's that.

my udev rule is

SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"

I have to admit changing it to the other one made no difference. did you do chmod a+r /etc/udev/rules.d/51-android.rules

Yep. All the files in the rules.d directory are -rw-r--r-- root root

I'm running same kernel version I never run adb as sudo, I don't think it's needed but doubt that's your issue. there should be no need to mount the sdcard.

Yeah, I wasn't sure either so I tried with and without sudo.

is everything else you connect working? just wondering if its a usb thing?

No. Other USB devices work just fine - I just plugged in a 2G stick and a 3G Dongle. Both work as expected. Thanks anyway. I'm not sure where to go from here... Maybe I will try a different computer. One last question, what Java versions do you have installed on your system? For example. If I do

which java

I get

/usr/bin/java

running

java -version

gives me:

java version "1.6.0_20"

Java(TM) SE Runtime Environment (build 1.6.0_20-b02)

Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)

Just a thought.

Cheers

Al

[Guest fards]

on this machine I'm running

java version "1.6.0_18"

OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1)

OpenJDK Client VM (build 16.0-b13, mixed mode, sharing)

at home I'm on 1.6.0.20

[Guest jamezwarner]

I've been waiting for weeks for a beta entry - how did you guys get hold of one?

[Guest fards]

I've been waiting for weeks for a beta entry - how did you guys get hold of one?

mine came through on tuesday evening, I signed up when it was first announced

[Guest lord_alan]

mine came through on tuesday evening, I signed up when it was first announced

I got mine on the 13th August.

Shame it doesn't bloody work! Although this afternoon I shall try it on a different PC and report my findings...

[Guest lord_alan]

Shame it doesn't bloody work! Although this afternoon I shall try it on a different PC and report my findings...

I had exactly the same experience on another machine.

However, I just installed the full SDK and the adb command from there works!

I'm just setting up Eclipse with the ADT and such like, but I suspect that all will be fine once I'm finished.

It looks like it's an issue with the limited tools provided in the App Inventor kit.

Hey ho.

Cheers

[Guest fards]

I had exactly the same experience on another machine.

However, I just installed the full SDK and the adb command from there works!

I'm just setting up Eclipse with the ADT and such like, but I suspect that all will be fine once I'm finished.

It looks like it's an issue with the limited tools provided in the App Inventor kit.

Hey ho.

Cheers

Lol ok. I presumed you had the sdk installed