Monday, October 4, 2010

Unable to connect Samsung Vibrant to App Inventor on Ubuntu9.04

The good news is that almost 2.5 months after I applied for access to Google Android App Inventor, I got the access on 1st October.

Now the bad news is that I am unable to connect my Samsung Galaxy S Vibrant to App Inventor on my machine running Ubuntu 9.04. Here is what I have tried till now after installing App Inventor Extras software for Linux:

I ensured the below settings were done before connecting the phone:
  1. Settings > Applications > Unknown sources is checked
  2. Settings > Applications > Development > USB debugging is checked
  3. Settings > Applications > Development > Stay awake is checked
  4. Settings > Sound and display > Orientation is un-checked

On connecting the phone, I see the USB Icon which mentions that USB is connected and also a Red exclamation alert icon mentioning that USB debugging is connected. I also ensured that OpenJDK is also not installed on my machine as that is known to cause clashes with Android SDK.

Then I opened a shell, logged in as root (using sudo -s) and then did the following:

# lsusb | grep 'Sam'
Bus 001 Device 003: ID 04e8:681c Samsung Electronics Co., Ltd 
# vi /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="681c", MODE="0666"

Now rebooted the machine and again with sudo -s, ran the following commands:

# /etc/init.d/udev restart
 * Stopping kernel event manager...                                      [ OK ]
 * Starting kernel event manager...                                      [ OK ]
# cd /usr/google/appinventor-extras/commands-for-Appinventor
# ./adb kill-server
# ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

# ./adb usb
error: device not found

I tried the above sequence of steps with these versions of UDEV rules as well, but to no avail:
# vi /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"


# vi /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb_device", SYSFS{idVendor}=="04e8", MODE="0666"

Here is the log from the Java console:

Creating the REPL controller
Changing the REPL communication button text to Communicating...
Disabling REPL communication button.
********* Actually invoking CreateAndSend
Restarting repl controller (true)
ReplController sending (begin (require  (setup-repl-environment "<<" ":" "@@" "Success" "Failure" "=="">>" '((">>""&2")("<<""&1")("&""&0"))))
**** devicesPluggedIn: 0 isPluggedIn: false connectionHappy: false
************************** commIndicator was unexpectedly
connected!!!! COMMUNICATING
Changing REPL communication button to Connect.
Re-enabling REPL communication button.
Communication with REPL failed: App Inventor
cannot find any phones.
Please plug in a phone and try again.

I am at a loss as to what else to check as all these steps are a compilation of the knowledge in the google groups as well as other blogs on the topic. If anyone has any ideas/pointers/suggestions, please let me know - Thanks.

1 comment:

FreePlay said...

I have the same message with my droid 2 it's driving me nuts...tell me if you figure it out


Related Posts Plugin for WordPress, Blogger...