Reply
Thread Tools
Posts: 12 | Thanked: 23 times | Joined on Jul 2008
#11
Originally Posted by solca View Post
No, I didn't, was Google.
OK, should we try changing it to 0xDEED? That might make working with the SDK a bit easier.
 
zehjotkah's Avatar
Posts: 2,361 | Thanked: 3,746 times | Joined on Dec 2007 @ Berlin - Love this city!!
#12
Originally Posted by Thesandlord View Post
Good store here: andapps.com

"AndApps is website for those who don't have access to the Android Marketplace. Here will be uploaded as much as possible free and/or open source applications for the Android platform."
I've found the android market client on that site you've posted:
http://andappstore.com/AndroidPhoneA...ions/apps/7661
But for me it's too late today. Maybe someone would like to try out, if it works...
 
solca's Avatar
Posts: 109 | Thanked: 196 times | Joined on Sep 2008 @ Guatemala
#13
Originally Posted by Vid View Post
OK, should we try changing it to 0xDEED? That might make working with the SDK a bit easier.
I belive that newer SDKs (as those built with the Android source) supports both IDs, at least my adb in Linux works painlessly. Are you trying with the SDK 1.0r2?
__________________
NITdroid
 

The Following User Says Thank You to solca For This Useful Post:
Posts: 1,213 | Thanked: 356 times | Joined on Jan 2008 @ California and Virginia
#14
Yeah, Linux works fine, but the damn Windows drivers don't play nice. The "Cupcake" release has broken the Windows drivers...
__________________
----------------------------------------------------

www.ezschool.com - The best online educational experience.
 
Posts: 12 | Thanked: 23 times | Joined on Jul 2008
#15
Originally Posted by solca View Post
I belive that newer SDKs (as those built with the Android source) supports both IDs, at least my adb in Linux works painlessly. Are you trying with the SDK 1.0r2?
Yes, I was trying with the adb binary from SDK 1.0r2 but from MacOS 10.4. I've managed to get Linux working with the cupcake userspace under Linux, although I had to make a small change to the instructions at http://code.google.com/android/intro...devicehardware. I changed the vendor ID from 0bb4 to 18d1 in /etc/udev/rules.d/50-android.rules:

Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
After that, my tablet works fine with either the adb from SDK 1.0r2 for Linux, or with the adb from http://guug.org/nit/nitdroid/.

BTW, after I flashed the new cupcake userspace (and kernel) onto my tablet it is now showing up as product ID 0x0002. At least that's what is in /sys/bus/usb/devices/1-8/idProduct when I plug the tablet into my Linux system. Perhaps we need to change the product ID in gowen's modified android_usb.inf, and reinstall the driver?
 

The Following 2 Users Say Thank You to Vid For This Useful Post:
Posts: 1,213 | Thanked: 356 times | Joined on Jan 2008 @ California and Virginia
#16
OK, for me, it worked plug-and-play under Ubuntu

For Windows, I modded the .inf file.

See attached
Attached Files
File Type: zip android_usb.zip (1.3 KB, 395 views)
__________________
----------------------------------------------------

www.ezschool.com - The best online educational experience.
 

The Following User Says Thank You to Thesandlord For This Useful Post:
Posts: 12 | Thanked: 23 times | Joined on Jul 2008
#17
Originally Posted by Thesandlord View Post
OK, for me, it worked plug-and-play under Ubuntu

For Windows, I modded the .inf file.

See attached
Yep, a one-line addition worked for me too:

Code:
myhost:android_usb_windows> diff android_usb.inf.gowen android_usb.inf
57a58
> %USB\VID_18D1&PID_0002&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_18D1&PID_0002&MI_01
I guess the Windows (and probably MacOS) versions of adb are more picky about matching the device than the Linux version.
 
Posts: 11 | Thanked: 2 times | Joined on Jan 2007
#18
Originally Posted by Vid View Post
Yes, I was trying with the adb binary from SDK 1.0r2 but from MacOS 10.4. I've managed to get Linux working with the cupcake userspace under Linux, although I had to make a small change to the instructions at http://code.google.com/android/intro...devicehardware. I changed the vendor ID from 0bb4 to 18d1 in /etc/udev/rules.d/50-android.rules:

Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
After that, my tablet works fine with either the adb from SDK 1.0r2 for Linux, or with the adb from http://guug.org/nit/nitdroid/.

BTW, after I flashed the new cupcake userspace (and kernel) onto my tablet it is now showing up as product ID 0x0002. At least that's what is in /sys/bus/usb/devices/1-8/idProduct when I plug the tablet into my Linux system. Perhaps we need to change the product ID in gowen's modified android_usb.inf, and reinstall the driver?
Thanks man, adding that rule to udev made my adb work again and....don't ask me why, I didn't touch anything else but this time it connected automatically to my Wifi. Without putting in the password for the WPA2!!!!!!!!

EDIT: A yeah, my bad, I put the config of my wifi yesterday as it wasn't scanning anything, it wouldn't connect or anything but it explains now why it autoconnected hehe

Also, the OnScreen Keyboard works fine now, no strange reappearance of letters after having deleted them.

Last edited by kender; 2008-12-21 at 11:29. Reason: bad memory
 
Posts: 19 | Thanked: 0 times | Joined on Oct 2007
#19
Silly question: Does the Google Mail/Calendar/Contacts stuff work out of the box? I heard a nasty rumor that they were not available... SAY IT AIN'T SO!
 
Posts: 2 | Thanked: 0 times | Joined on Aug 2008 @ Silicon Valley
#20
so what needs to be done to get it working in osx?
 
Reply

Tags
android, nitdroid


 
Forum Jump


All times are GMT. The time now is 14:02.