Thanks Anders, this was actually a near-hardware issue. Now, we were able to show off Sean's and the others great work to Mike Jennings from the Android team right now mentioning the FreeRunner port it in his talk on Android @Oredev!
Keep it up! /peter http://www.oredev.se - Be there or be gone. GTalk: neubauer.peter Skype peter.neubauer ICQ 18762544 Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. On Fri, Nov 21, 2008 at 2:58 AM, AndersHedberg <[EMAIL PROTECTED]> wrote: > > it was the /app directory in the ext3 partition, just place the .apk > file there and you have a virtual keyboard! (running debian on vmware > on my windows xp machine, I can mount the SD card, but not connect > directly to the Freerunner) > > On 21 Nov, 02:18, AndersHedberg <[EMAIL PROTECTED]> > wrote: >> I solved my immediate problem by placing the .apk file on the SD card >> in several locations (in both partitions, don't know which place was >> correct, but it do show up with all other applications), rebooted and >> now I have a virtual keyboard on the freerunner! - >> seehttp://groups.google.com/group/android-developers/browse_thread/threa... >> >> On 21 Nov, 01:31, AndersHedberg <[EMAIL PROTECTED]> >> wrote: >> >> > On 6 Nov, 09:51, "Cédric Berger" <[EMAIL PROTECTED]> wrote: >> >> > > On Thu, Nov 6, 2008 at 04:57, Sean McNeil <[EMAIL PROTECTED]> wrote: >> >> > > > Mike Lockwood wrote: >> > > >> On Wed, Nov 5, 2008 at 5:53 AM, cedric.berger >> > > >> The Windows driver should work as long as you edit the VID and PID in >> > > >> the .inf file to match the values in android_adb.c: >> >> > > >> #define DRIVER_VENDOR_ID 0x18D1 >> > > >> #define DRIVER_PRODUCT_ID 0x0001 >> > > I indeed changed the >> > > .inf with the VID / PID I picked in windows manager when neo was >> > > plugged : I added >> >> > > ; For XP and later >> > > [Google.NTx86] >> >> > > ; Neo >> > > %USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev, >> > > USB\VID_1457&PID_5117 >> > > %USB\VID_1457&PID_5117&Rev_0212.DeviceDescRelease%=androidusb.Dev, >> > > USB\VID_1457&PID_5117&Rev_0212 >> >> > If adb.exe expects to use the Driver ID of 0x18d1 and we need to tell >> > windows to use a VID of 1457 to recognize the USB device, the >> > Freerunner is apparently telling the windows PC it is a VID 1457 USB >> > device. If the 0x18D1 is hardcoded into adb.exe someone need to >> > recompile it with the Freerunners VID (or change the VID used by the >> > Freerunner, but that is unwise as VIDs should be unique...). To >> > summarize - the lines >> >> > #define DRIVER_VENDOR_ID 0x18D1 >> > #define DRIVER_PRODUCT_ID 0x0001 >> >> > in android_adb.c must be changed to the VIDs and PIDs in the .inf file >> > to let adb work with the Freerunner under windows. >> >> > Best regards, >> > Anders Hedberg > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
