From: dcraw101 <dcr...@ya...> - 2010-09-15 03:51:32
|
I just built the foryo version of rowboat android following the instructions at http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Android. It appears to be working and displays a nice GUI on my palo43 display. But, the touch screen does not appear to be working and the screen flickers whenever I move the mouse. Has anyone been able to get the touch screen working? Is it possible to disable the cursor when I get the touch screen working? I am new to android. Is it even possible to configure android such that it only has the bare minimum core packages? I want to strip away everything related to phone, gps, maps, etc? -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p29715029.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2010-09-15 07:59:33
|
Hi, On Tue, Sep 14, 2010 at 8:51 PM, dcraw101 <dcr...@ya...> wrote: > I just built the foryo version of rowboat android following the instructions > at http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Android. > It appears to be working and displays a nice GUI on my palo43 display. But, > the touch screen does not appear to be working and the screen flickers > whenever I move the mouse. Has anyone been able to get the touch screen > working? Is it possible to disable the cursor when I get the touch screen > working? The CONFIG_TOUCHSCREEN_ADS7846 parameter needed to be built into the kernel rather than being built as a module; I've updated the defconfig file available on the wiki. (Thanks to Elvis Dowson for finding this) Regarding the screen flickering: - did you have the defaultdisplay variable set to lcd43? (I've updated the wiki to clarify details about the u-boot args.) - how bad is the flicker---I'm seeing some marginal jitter when I use the touchscreen on my Chestnut43 but nothing dramatic. -Ash |
From: dcraw101 <dcr...@ya...> - 2010-09-15 17:18:06
|
Ash Charles wrote: > > Hi, > > On Tue, Sep 14, 2010 at 8:51 PM, dcraw101 <dcr...@ya...> wrote: >> I just built the foryo version of rowboat android following the >> instructions >> at http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Android. >> It appears to be working and displays a nice GUI on my palo43 display. >> But, >> the touch screen does not appear to be working and the screen flickers >> whenever I move the mouse. Has anyone been able to get the touch screen >> working? Is it possible to disable the cursor when I get the touch >> screen >> working? > The CONFIG_TOUCHSCREEN_ADS7846 parameter needed to be built into the > kernel rather than being built as a module; I've updated the defconfig > file available on the wiki. (Thanks to Elvis Dowson for finding this) > > Regarding the screen flickering: > - did you have the defaultdisplay variable set to lcd43? (I've updated > the wiki to clarify details about the u-boot args.) > - how bad is the flicker---I'm seeing some marginal jitter when I use > the touchscreen on my Chestnut43 but nothing dramatic. > > -Ash > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > I enabled the touch driver in the kernel and now that is working (although the calibration is reversed in the y axis and I don't see a way to recalibrate in android). But, I still get a bad flicker every time I move the mouse, press a key, or press the touch screen. It is not the whole screen, just a random diagonal region in the lower left corner. When I run any of the Angstrom builds on this device everything works perfectly. The basic Android OS appears to be running ok, I can run calculator and messaging, but contacts and music crash shortly after opening them. The browser runs for a few seconds and displays the Google home page then crashes. I used the rowboat-froyo.xml manifest. I wonder if it would be better to use eclair at this point? -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p29720776.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: dcraw101 <dcr...@ya...> - 2010-09-15 21:32:57
|
dcraw101 wrote: > > > Ash Charles wrote: >> >> Hi, >> >> On Tue, Sep 14, 2010 at 8:51 PM, dcraw101 <dcr...@ya...> wrote: >>> I just built the foryo version of rowboat android following the >>> instructions >>> at >>> http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Android. >>> It appears to be working and displays a nice GUI on my palo43 display. >>> But, >>> the touch screen does not appear to be working and the screen flickers >>> whenever I move the mouse. Has anyone been able to get the touch screen >>> working? Is it possible to disable the cursor when I get the touch >>> screen >>> working? >> The CONFIG_TOUCHSCREEN_ADS7846 parameter needed to be built into the >> kernel rather than being built as a module; I've updated the defconfig >> file available on the wiki. (Thanks to Elvis Dowson for finding this) >> >> Regarding the screen flickering: >> - did you have the defaultdisplay variable set to lcd43? (I've updated >> the wiki to clarify details about the u-boot args.) >> - how bad is the flicker---I'm seeing some marginal jitter when I use >> the touchscreen on my Chestnut43 but nothing dramatic. >> >> -Ash >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > I do have the defaultdisplay set to lcd43. I also enabled the touch > driver in the kernel and now that is working (although the calibration is > reversed in the y axis and I don't see a way to recalibrate in android). > But, I still get a bad flicker every time I move the mouse, press a key, > or press the touch screen. It is not the whole screen, just a random > diagonal region in the lower left corner. When I run any of the Angstrom > builds on this device everything works perfectly. > > The basic Android OS appears to be running ok, I can run calculator and > messaging, but contacts and music crash shortly after opening them. The > browser runs for a few seconds and displays the Google home page then > crashes. I used the rowboat-froyo.xml manifest. I wonder if it would be > better to use eclair at this point? > I installed the Android SGX drivers and that fixed the screen flickering problem. Now the device is working pretty good. The contacts and Music apps are no longer crashing. I still can't figure out how to calibrate the palo43 resistive touchscreen however. Doug -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p29723177.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2010-09-15 22:08:10
|
Hi Doug, Thanks for letting me know about the SGX drivers---I'm glad to hear they work okay. Also, a newer version of the SGX drivers that I've not yet tried is available here: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/3_01_00_07/exports/OMAP35x_Graphics_SDK_setuplinux_3_01_00_07.bin. Let me know if you give it a go. On Wed, Sep 15, 2010 at 2:32 PM, dcraw101 <dcr...@ya...> wrote: > I installed the Android SGX drivers and that fixed the screen flickering > problem. Now the device is working pretty good. The contacts and Music > apps are no longer crashing. I still can't figure out how to calibrate the > palo43 resistive touchscreen however. As far as I understand Android expects the device to be calibrated so it is necessary to either hard code the calibration parameters (say, taken from the same device running Angstrom with tslib) into the driver or add in tslib to do calibration. To get started, I recommend looking at Elvis Dowson's port of Android in the OE tree--it is for 1.5 but he mentioned that he had done something like this to get it working. -Ash |
From: John P. <pa...@gm...> - 2010-09-24 00:05:47
|
So I got rowboat-android booted on overo (water) + tobi. Any pointers on getting mouse and keyboard working as input devices? John On Sep 15, 2010, at 6:07 PM, Ash Charles wrote: > Hi Doug, > > Thanks for letting me know about the SGX drivers---I'm glad to hear > they work okay. Also, a newer version of the SGX drivers that I've > not yet tried is available here: > http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/3_01_00_07/exports/OMAP35x_Graphics_SDK_setuplinux_3_01_00_07.bin. > Let me know if you give it a go. > > On Wed, Sep 15, 2010 at 2:32 PM, dcraw101 <dcr...@ya...> wrote: >> I installed the Android SGX drivers and that fixed the screen flickering >> problem. Now the device is working pretty good. The contacts and Music >> apps are no longer crashing. I still can't figure out how to calibrate the >> palo43 resistive touchscreen however. > As far as I understand Android expects the device to be calibrated so > it is necessary to either hard code the calibration parameters (say, > taken from the same device running Angstrom with tslib) into the > driver or add in tslib to do calibration. To get started, I recommend > looking at Elvis Dowson's port of Android in the OE tree--it is for > 1.5 but he mentioned that he had done something like this to get it > working. > > -Ash > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Ash C. <ash...@gm...> - 2010-09-26 20:35:53
|
Hi John, Using a USB hub, the keyboard works fine for me. The mouse is configured to not to act like a pointing device but is used for its buttons; for now the assumption is that a touchscreen is attached. The relevant code should be in frameworks/base/...input. BTW, I've updated the instructions: http://www.gumstix.net/wiki/index.php?title=RowboatAndroid Feedback welcome :). -Ash On Thu, Sep 23, 2010 at 5:05 PM, John Pauley <pa...@gm...> wrote: > So I got rowboat-android booted on overo (water) + tobi. Any pointers on getting mouse and keyboard working as input devices? > > John > > On Sep 15, 2010, at 6:07 PM, Ash Charles wrote: > >> Hi Doug, >> >> Thanks for letting me know about the SGX drivers---I'm glad to hear >> they work okay. Also, a newer version of the SGX drivers that I've >> not yet tried is available here: >> http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/3_01_00_07/exports/OMAP35x_Graphics_SDK_setuplinux_3_01_00_07.bin. >> Let me know if you give it a go. >> >> On Wed, Sep 15, 2010 at 2:32 PM, dcraw101 <dcr...@ya...> wrote: >>> I installed the Android SGX drivers and that fixed the screen flickering >>> problem. Now the device is working pretty good. The contacts and Music >>> apps are no longer crashing. I still can't figure out how to calibrate the >>> palo43 resistive touchscreen however. >> As far as I understand Android expects the device to be calibrated so >> it is necessary to either hard code the calibration parameters (say, >> taken from the same device running Angstrom with tslib) into the >> driver or add in tslib to do calibration. To get started, I recommend >> looking at Elvis Dowson's port of Android in the OE tree--it is for >> 1.5 but he mentioned that he had done something like this to get it >> working. >> >> -Ash >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: John P. <pa...@gm...> - 2010-09-27 02:39:22
|
Thanks Ash for the info, but mouse clicks and keyboard doesn't seem to do anything. Mouse and keyboard are known good:) I'll keep looking. John On Sep 26, 2010, at 4:35 PM, Ash Charles wrote: > Hi John, > > Using a USB hub, the keyboard works fine for me. The mouse is > configured to not to act like a pointing device but is used for its > buttons; for now the assumption is that a touchscreen is attached. > The relevant code should be in frameworks/base/...input. > > BTW, I've updated the instructions: > http://www.gumstix.net/wiki/index.php?title=RowboatAndroid > Feedback welcome :). > > -Ash > > On Thu, Sep 23, 2010 at 5:05 PM, John Pauley <pa...@gm...> wrote: >> So I got rowboat-android booted on overo (water) + tobi. Any pointers on getting mouse and keyboard working as input devices? >> >> John >> >> On Sep 15, 2010, at 6:07 PM, Ash Charles wrote: >> >>> Hi Doug, >>> >>> Thanks for letting me know about the SGX drivers---I'm glad to hear >>> they work okay. Also, a newer version of the SGX drivers that I've >>> not yet tried is available here: >>> http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/3_01_00_07/exports/OMAP35x_Graphics_SDK_setuplinux_3_01_00_07.bin. >>> Let me know if you give it a go. >>> >>> On Wed, Sep 15, 2010 at 2:32 PM, dcraw101 <dcr...@ya...> wrote: >>>> I installed the Android SGX drivers and that fixed the screen flickering >>>> problem. Now the device is working pretty good. The contacts and Music >>>> apps are no longer crashing. I still can't figure out how to calibrate the >>>> palo43 resistive touchscreen however. >>> As far as I understand Android expects the device to be calibrated so >>> it is necessary to either hard code the calibration parameters (say, >>> taken from the same device running Angstrom with tslib) into the >>> driver or add in tslib to do calibration. To get started, I recommend >>> looking at Elvis Dowson's port of Android in the OE tree--it is for >>> 1.5 but he mentioned that he had done something like this to get it >>> working. >>> >>> -Ash >>> >>> ------------------------------------------------------------------------------ >>> Start uncovering the many advantages of virtual appliances >>> and start using them to simplify application deployment and >>> accelerate your shift to cloud computing. >>> http://p.sf.net/sfu/novell-sfdev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: dcraw101 <dcr...@ya...> - 2010-09-27 16:33:07
|
Ash, on my Palo43 / Gumstix Water setup my USB mouse and touch pad both act as pointing devices. It actually works quite well. If I don't move the mouse then there is no visible cursor and the touch pad still works. As soon as I move the mouse a visible cursor appears and the mouse acts as a pointing device. I did not do anything specifically to enable a USB mouse as a pointing device. In fact, I simply followed your instructions on the Wiki using rowboat-froyo.xml. I did see that you reccomend updating the ts_lib pointercal file for resistive touch screen calibration. I do think this is the correct approach, but I believe it requires some modifications to Android's ads7846.c touch screen driver in the kernel. I simply modified ads7846.c to use the raw touch screen values from my device following the example for the OMAP3EVM (http://groups.google.com/group/rowboat/browse_thread/thread/26839a847107c6c7/c8bb7dee577319fa?lnk=gst&q=dcraw101#). Right now I am trying to figure out how to disable the LCD/backlight after a period if inactivity. Does anyone else have this working? Currently, the LCD is always on. Doug Ash Charles wrote: > > Hi John, > > Using a USB hub, the keyboard works fine for me. The mouse is > configured to not to act like a pointing device but is used for its > buttons; for now the assumption is that a touchscreen is attached. > The relevant code should be in frameworks/base/...input. > > BTW, I've updated the instructions: > http://www.gumstix.net/wiki/index.php?title=RowboatAndroid > Feedback welcome :). > > -Ash > > On Thu, Sep 23, 2010 at 5:05 PM, John Pauley <pa...@gm...> wrote: >> So I got rowboat-android booted on overo (water) + tobi. Any pointers on >> getting mouse and keyboard working as input devices? >> >> John >> >> On Sep 15, 2010, at 6:07 PM, Ash Charles wrote: >> >>> Hi Doug, >>> >>> Thanks for letting me know about the SGX drivers---I'm glad to hear >>> they work okay. Also, a newer version of the SGX drivers that I've >>> not yet tried is available here: >>> http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/3_01_00_07/exports/OMAP35x_Graphics_SDK_setuplinux_3_01_00_07.bin. >>> Let me know if you give it a go. >>> >>> On Wed, Sep 15, 2010 at 2:32 PM, dcraw101 <dcr...@ya...> wrote: >>>> I installed the Android SGX drivers and that fixed the screen >>>> flickering >>>> problem. Now the device is working pretty good. The contacts and >>>> Music >>>> apps are no longer crashing. I still can't figure out how to calibrate >>>> the >>>> palo43 resistive touchscreen however. >>> As far as I understand Android expects the device to be calibrated so >>> it is necessary to either hard code the calibration parameters (say, >>> taken from the same device running Angstrom with tslib) into the >>> driver or add in tslib to do calibration. To get started, I recommend >>> looking at Elvis Dowson's port of Android in the OE tree--it is for >>> 1.5 but he mentioned that he had done something like this to get it >>> working. >>> >>> -Ash >>> >>> ------------------------------------------------------------------------------ >>> Start uncovering the many advantages of virtual appliances >>> and start using them to simplify application deployment and >>> accelerate your shift to cloud computing. >>> http://p.sf.net/sfu/novell-sfdev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America >> contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and >> Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p29815763.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2010-09-27 20:27:23
|
Hi Doug, On Mon, Sep 27, 2010 at 9:33 AM, dcraw101 <dcr...@ya...> wrote: > but I believe it requires some modifications to Android's > ads7846.c touch screen driver in the kernel. I simply modified ads7846.c to > use the raw touch screen values from my device following the example for the > OMAP3EVM > (http://groups.google.com/group/rowboat/browse_thread/thread/26839a847107c6c7/c8bb7dee577319fa?lnk=gst&q=dcraw101#). Actually, it is one of the Android framework/base libraries that looks for a file on boot (/system/etc/pointercal) to configure the touchscreen. Is there any advantage to modifying the ads7846.c file directly? > > Right now I am trying to figure out how to disable the LCD/backlight after a > period if inactivity. Does anyone else have this working? Currently, the > LCD is always on. Excuse the stupid question but I'm guessing changing the screensaver setting within Android doesn't work? Glad to hear the mouse and keyboard are working for you. -Ash |
From: John P. <pa...@gm...> - 2010-09-27 23:03:21
|
not sure what changed, but I rebooted and mouse/keyboard works... Thanks. On Sep 27, 2010, at 4:26 PM, Ash Charles wrote: > Hi Doug, > > On Mon, Sep 27, 2010 at 9:33 AM, dcraw101 <dcr...@ya...> wrote: >> but I believe it requires some modifications to Android's >> ads7846.c touch screen driver in the kernel. I simply modified ads7846.c to >> use the raw touch screen values from my device following the example for the >> OMAP3EVM >> (http://groups.google.com/group/rowboat/browse_thread/thread/26839a847107c6c7/c8bb7dee577319fa?lnk=gst&q=dcraw101#). > Actually, it is one of the Android framework/base libraries that looks > for a file on boot (/system/etc/pointercal) to configure the > touchscreen. Is there any advantage to modifying the ads7846.c file > directly? >> >> Right now I am trying to figure out how to disable the LCD/backlight after a >> period if inactivity. Does anyone else have this working? Currently, the >> LCD is always on. > Excuse the stupid question but I'm guessing changing the screensaver > setting within Android doesn't work? > > Glad to hear the mouse and keyboard are working for you. > -Ash > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: mpatel <mp...@mi...> - 2010-10-06 21:08:38
|
Hello, I'm also using the froyo build from rowboat and the android is running fine. I'm using an Overo fire with chestnut43 and 4.3" lcd from gumstix. I want to be able to use the two buttons on Chestnut 43 which is GPIO14 and GPIO23 and also the leds if possible. But the buttons are more important because the device is not usable since I have no button for back and menu. Can someone help me out? John Pauley-2 wrote: > > not sure what changed, but I rebooted and mouse/keyboard works... > > Thanks. > > On Sep 27, 2010, at 4:26 PM, Ash Charles wrote: > >> Hi Doug, >> >> On Mon, Sep 27, 2010 at 9:33 AM, dcraw101 <dcr...@ya...> wrote: >>> but I believe it requires some modifications to Android's >>> ads7846.c touch screen driver in the kernel. I simply modified >>> ads7846.c to >>> use the raw touch screen values from my device following the example for >>> the >>> OMAP3EVM >>> (http://groups.google.com/group/rowboat/browse_thread/thread/26839a847107c6c7/c8bb7dee577319fa?lnk=gst&q=dcraw101#). >> Actually, it is one of the Android framework/base libraries that looks >> for a file on boot (/system/etc/pointercal) to configure the >> touchscreen. Is there any advantage to modifying the ads7846.c file >> directly? >>> >>> Right now I am trying to figure out how to disable the LCD/backlight >>> after a >>> period if inactivity. Does anyone else have this working? Currently, >>> the >>> LCD is always on. >> Excuse the stupid question but I'm guessing changing the screensaver >> setting within Android doesn't work? >> >> Glad to hear the mouse and keyboard are working for you. >> -Ash >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p29900864.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2010-10-07 18:03:12
|
Hi mpatel, On Wed, Oct 6, 2010 at 2:08 PM, mpatel <mp...@mi...> wrote: > But the buttons are more important because the > device is not usable since I have no button for back and menu. Can someone > help me out? I'm able to use the centre and right mouse buttons to make this work temporarily. I'd love to have a patch to make the GPIO buttons work and it is being worked on atm. The steps likely include: - modifying board_overo.c to export the gpios in SYSFS - modify the keymapping file and perhaps registering these buttons with the Android input framework I found this page interesting: http://source.android.com/porting/keymaps_keyboard_input.html And I though these chunks of code looks relevant: framework-base/services/jni/com_android_server_KeyInputQueue.cpp framework-base/services/java/com/android/server/KeyInputQueue.java framework-base/core/java/android/inputmethodservice/... But this was only from a quick hunt. I'm also not sure how much of the key mapping stuff is for virtual keyboards versus physical buttons on the device. Post back if you find anything interesting. -Ash |
From: Patel, M. <mp...@mi...> - 2010-10-07 18:24:28
|
Ash, thanks for your help. I know I'm close but just not there. I have modified the board_overo.c file. I used a patch that Gizmoforyou uses for their flow device and modified it to use gpio 14 and 23. I also know that I have to modify the .kl and .kcm file in the android filesystem. For the .kl file the instructions are provided by the link you provided. However, I can't figure out which keyscan code I should be using and if there's anything else I need to be doing besides just putting the right keyscan code for menu and back buttons. -----Original Message----- From: Ash Charles [mailto:ash...@gm...] Sent: Thursday, October 07, 2010 2:03 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] rowboat-android on overo Hi mpatel, On Wed, Oct 6, 2010 at 2:08 PM, mpatel <mp...@mi...> wrote: > But the buttons are more important because the > device is not usable since I have no button for back and menu. Can someone > help me out? I'm able to use the centre and right mouse buttons to make this work temporarily. I'd love to have a patch to make the GPIO buttons work and it is being worked on atm. The steps likely include: - modifying board_overo.c to export the gpios in SYSFS - modify the keymapping file and perhaps registering these buttons with the Android input framework I found this page interesting: http://source.android.com/porting/keymaps_keyboard_input.html And I though these chunks of code looks relevant: framework-base/services/jni/com_android_server_KeyInputQueue.cpp framework-base/services/java/com/android/server/KeyInputQueue.java framework-base/core/java/android/inputmethodservice/... But this was only from a quick hunt. I'm also not sure how much of the key mapping stuff is for virtual keyboards versus physical buttons on the device. Post back if you find anything interesting. -Ash ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Ash C. <ash...@gm...> - 2010-10-07 18:50:36
|
Hi Mrugesh, On Thu, Oct 7, 2010 at 11:24 AM, Patel, Mrugesh <mp...@mi...> wrote: > I have modified the board_overo.c file. I used a patch that Gizmoforyou uses for their flow device and modified it to use gpio 14 and 23. Could you send me|pastebin the patch please? I'm curious to take a look. Yes---I was likewise stymied as to how to find the scancodes; scancodes seem to be defined in kernel/include/linux/input.h but I'm not sure how these correspond to GPIOs. Anyone? How do the Flow guys do it? -Ash |
From: Patel, M. <mp...@mi...> - 2010-10-07 18:55:45
|
Ash, Below is the original patch. I modified one of the places below for gpio 14 not 24. --- ~/rowboat-android/tmp/board-overo.c 2009-04-09 15:11:46.000000000 +0200 +++ ~/rowboat-android/kernel/arm/mach-omap2/board-overo.c 2009-04-09 16:39:40.000000000 +0200 @@ -29,6 +29,11 @@ #include <linux/i2c/twl4030.h> #include <linux/regulator/machine.h> +#include <linux/leds.h> +#include <linux/gpio.h> +#include <linux/input.h> +#include <linux/gpio_keys.h> + #include <linux/mtd/mtd.h> #include <linux/mtd/nand.h> #include <linux/mtd/partitions.h> @@ -87,6 +92,8 @@ }, }; +static struct gpio_led gpio_leds[]; + static inline void __init overo_init_smsc911x(void) { unsigned long cs_mem_base; @@ -364,6 +371,62 @@ omap_gpio_init(); } +static struct gpio_led gpio_leds[] = { + { + .name = "palo43::gpio21", + .default_trigger = "mmc0", + .gpio = 21, + .active_low = 1, + }, + { + .name = "palo43::gpio22", + .default_trigger = "heartbeat", + .gpio = 22, + .active_low = 1, + }, +}; + +static struct gpio_led_platform_data gpio_led_info = { + .leds = gpio_leds, + .num_leds = ARRAY_SIZE(gpio_leds), +}; + +static struct platform_device leds_gpio = { + .name = "leds-gpio", + .id = -1, + .dev = { + .platform_data = &gpio_led_info, + }, +}; + +static struct gpio_keys_button gpio_buttons[] = { + { + .code = KEY_F, + .gpio = 23, + .desc = "gpio23", + .wakeup = 1, + }, + { + .code = KEY_F11, + .gpio = 24, + .desc = "gpio24", + .wakeup = 1, + }, +}; + +static struct gpio_keys_platform_data gpio_key_info = { + .buttons = gpio_buttons, + .nbuttons = ARRAY_SIZE(gpio_buttons), +}; + +static struct platform_device keys_gpio = { + .name = "gpio-keys", + .id = -1, + .dev = { + .platform_data = &gpio_key_info, + }, +}; + /* DSS */ #define OVERO_GPIO_LCD_EN 144 @@ -459,6 +522,8 @@ static struct platform_device *overo_devices[] __initdata = { &overo_dss_device, + &leds_gpio, + &keys_gpio, }; static void __init overo_init(void) -----Original Message----- From: Ash Charles [mailto:ash...@gm...] Sent: Thursday, October 07, 2010 2:50 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] rowboat-android on overo Hi Mrugesh, On Thu, Oct 7, 2010 at 11:24 AM, Patel, Mrugesh <mp...@mi...> wrote: > I have modified the board_overo.c file. I used a patch that Gizmoforyou uses for their flow device and modified it to use gpio 14 and 23. Could you send me|pastebin the patch please? I'm curious to take a look. Yes---I was likewise stymied as to how to find the scancodes; scancodes seem to be defined in kernel/include/linux/input.h but I'm not sure how these correspond to GPIOs. Anyone? How do the Flow guys do it? -Ash ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: wilhemina <fmp...@gm...> - 2011-01-15 02:14:45
|
Hello Ash, It took me a while to find this mailing list. This happens to be my first android build so I wasn't too shocked to be running into so many issues.Here's my problem. I also followed this guide in porting android to overo: http://www.gumstix.net/wiki/index.php?title=RowboatAndroid While I have built and copied all the files to the micro-sd card, I stumbled upon this error during boot-up: Waiting for root device /dev/sdb2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address aaaa mmcblk0: mmc0:aaaa SU08G 7.40 GiB mmcblk0: p1 p2 mmc1: new SDIO card at address 0001 libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin libertas: can't load helper firmware libertas: failed to load helper firmware libertas_sdio: probe of mmc1:0001:1 failed with error -2 Now there was no mention in the guide about WIFI issues, I assumed it was nothing to worry about but after waiting for 20 minutes, android bootup did not progress any further so I was forced to post on here. It appears to be a normal problem. - Is there a manual way to copy the libertas files required for wifi to work? Where do I get these files (they were nowhere to be found in the rowboat-android folder) What folder should I place these files in? I have read some posts about rebuilding the kernel with the files included. How is this done? -How can I boot android without necessarily loading these files? Googling seems to suggest that android can run on the Overo fire without WIFI working but the initial bootup seems to require these files being loaded. Thanks so much. -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30676107.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-01-15 16:55:54
|
Hi Wilhemina, On Fri, Jan 14, 2011 at 6:14 PM, wilhemina <fmp...@gm...> wrote: > Now there was no mention in the guide about WIFI issues, I assumed it was > nothing to worry about but after waiting for 20 minutes, android bootup did > not progress any further so I was forced to post on here. It appears to be a > normal problem. In this build, the wifi doesn't work. I've been able to hack the libertas driver into place using some patches posted by hedwin on the RowboatAndroid mailing list 3-4 months ago but have not found a way of deploying this nicely. > - Is there a manual way to copy the libertas files required for wifi to > work? Where do I get these files (they were nowhere to be found in the > rowboat-android folder) What folder should I place these files in? I have > read some posts about rebuilding the kernel with the files included. How is > this done? Typically, you can add files to a build with the 'PRODUCT_COPY_FILES' makefile macro (see the AndroidBoard.mk file in the gumstix/overo directory for an example). > -How can I boot android without necessarily loading these files? Googling > seems to suggest that android can run on the Overo fire without WIFI working > but the initial bootup seems to require these files being loaded. Yes---there is no reason these files need to be loaded for the system to boot. As it looks like the error is coming from the kernel, perhaps trying to disable libertas in the kernel config. would be a reasonable step. I.e., from the top of the kernel tree, do a 'make ARCH=arm menuconfig' and disable the libertas options which would likely be hiding under Device Drivers->Network Device Support->Wireless. Let me know if this works for you. HTH, Ash |
From: Ronald <ra...@gm...> - 2011-01-16 13:29:13
|
unsubscribe |
From: podgib <pa...@gm...> - 2011-02-02 20:07:51
|
Hi Ash Ash Charles wrote: > > > In this build, the wifi doesn't work. I've been able to hack the > libertas driver into place using some patches posted by hedwin on the > RowboatAndroid mailing list 3-4 months ago but have not found a way of > deploying this nicely. > I am also trying to get wifi working on the overo board. I have tried hedwin's patches, but have been unable to get them to work. Could you give me some pointers? Cheers Geoff -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30829755.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-01-16 17:22:58
|
I seems like this response didn't actually make it to the list.....sorry if this is a duplicate post for some. >>>>>> Hi Wilhemina, On Fri, Jan 14, 2011 at 6:14 PM, wilhemina <fmp...@gm...> wrote: > Now there was no mention in the guide about WIFI issues, I assumed it was > nothing to worry about but after waiting for 20 minutes, android bootup did > not progress any further so I was forced to post on here. It appears to be a > normal problem. In this build, the wifi doesn't work. I've been able to hack the libertas driver into place using some patches posted by hedwin on the RowboatAndroid mailing list 3-4 months ago but have not found a way of deploying this nicely. > - Is there a manual way to copy the libertas files required for wifi to > work? Where do I get these files (they were nowhere to be found in the > rowboat-android folder) What folder should I place these files in? I have > read some posts about rebuilding the kernel with the files included. How is > this done? Typically, you can add files to a build with the 'PRODUCT_COPY_FILES' makefile macro (see the AndroidBoard.mk file in the gumstix/overo directory for an example). > -How can I boot android without necessarily loading these files? Googling > seems to suggest that android can run on the Overo fire without WIFI working > but the initial bootup seems to require these files being loaded. Yes---there is no reason these files need to be loaded for the system to boot. As it looks like the error is coming from the kernel, perhaps trying to disable libertas in the kernel config. would be a reasonable step. I.e., from the top of the kernel tree, do a 'make ARCH=arm menuconfig' and disable the libertas options which would likely be hiding under Device Drivers->Network Device Support->Wireless. Let me know if this works for you. HTH, Ash On Fri, Jan 14, 2011 at 6:14 PM, wilhemina <fmp...@gm...> wrote: > > Hello Ash, > It took me a while to find this mailing list. This happens to be my first > android build so I wasn't too shocked to be running into so many > issues.Here's my problem. I also followed this guide in porting android to > overo: > > http://www.gumstix.net/wiki/index.php?title=RowboatAndroid > While I have built and copied all the files to the micro-sd card, I stumbled > upon this error during boot-up: > > Waiting for root device /dev/sdb2... > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new high speed SDHC card at address aaaa > mmcblk0: mmc0:aaaa SU08G 7.40 GiB > mmcblk0: p1 p2 > mmc1: new SDIO card at address 0001 > libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin > libertas: can't load helper firmware > libertas: failed to load helper firmware > libertas_sdio: probe of mmc1:0001:1 failed with error -2 > > Now there was no mention in the guide about WIFI issues, I assumed it was > nothing to worry about but after waiting for 20 minutes, android bootup did > not progress any further so I was forced to post on here. It appears to be a > normal problem. > - Is there a manual way to copy the libertas files required for wifi to > work? Where do I get these files (they were nowhere to be found in the > rowboat-android folder) What folder should I place these files in? I have > read some posts about rebuilding the kernel with the files included. How is > this done? > -How can I boot android without necessarily loading these files? Googling > seems to suggest that android can run on the Overo fire without WIFI working > but the initial bootup seems to require these files being loaded. > > Thanks so much. > > > -- > View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30676107.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: mmeisner <mme...@gm...> - 2011-01-17 18:59:03
|
I am also very interested on running a stripped down android with 4.3 inch touch screen. Please let me know if anyone gets this working. dcraw101 wrote: > > I just built the foryo version of rowboat android following the > instructions at > http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Android. It > appears to be working and displays a nice GUI on my palo43 display. But, > the touch screen does not appear to be working and the screen flickers > whenever I move the mouse. Has anyone been able to get the touch screen > working? Is it possible to disable the cursor when I get the touch screen > working? > > I am new to android. Is it even possible to configure android such that > it only has the bare minimum core packages? I want to strip away > everything related to phone, gps, maps, etc? > -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30676224.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: wilhemina <fmp...@gm...> - 2011-01-22 16:21:31
|
After disabling the wireless option using menuconfig, I didn't get the libertas messages anymore however, the boot process stopped at this point: Waiting for root device /dev/sdd2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address aaaa mmcblk0: mmc0:aaaa SU08G 7.40 GiB mmcblk0: p1 p2 mmc1: new SDIO card at address 0001 and then nothing happens. No more modules no more messages. No android either. I've followed all the instructions in the guide to the letter and I'm really puzzled as to why everyone out there seems to have gotten the overo working using the guide and yet mine is giving so many issues. Most people who had it working seem to be using the palo43 board. I'm using the summit-board with overo fire. Are there configurations steps I might have left out that are not mentioned in your guide? I might eventually have to apply the patches as well but that is somewhat unfamiliar territory for me. Is there a walk-through I can follow? I found the ones relating to IGepv2 that Hedwin posted. Did you tweak them specifically for overo? How do you apply them? Adding the files directly didn't work either. Have you tried building directly with the kernel? I guess since you had to go with the patches that didn't work. I hope I'm not asking for too much but I'm really hoping to get this working so I really appreciate the help. PS: Is it possible to update the guide about all the modules that are not expected to work as well as workarounds? This might make it less of a hassle trying to solve any issues that might arise. > -How can I boot android without necessarily loading these files? Googling > seems to suggest that android can run on the Overo fire without WIFI > working > but the initial bootup seems to require these files being loaded. Yes---there is no reason these files need to be loaded for the system to boot. As it looks like the error is coming from the kernel, perhaps trying to disable libertas in the kernel config. would be a reasonable step. I.e., from the top of the kernel tree, do a 'make ARCH=arm menuconfig' and disable the libertas options which would likely be hiding under Device Drivers->Network Device Support->Wireless. Let me know if this works for you. HTH, Ash -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30737188.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-01-22 17:07:32
|
Hi, On Sat, Jan 22, 2011 at 8:21 AM, wilhemina <fmp...@gm...> wrote: > fter disabling the wireless option using menuconfig, I didn't get the > libertas messages anymore however, the boot process stopped at this point: Okay---this is good to know a workaround for this libertas problem. Thanks :). > > Waiting for root device /dev/sdd2... > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new high speed SDHC card at address aaaa > mmcblk0: mmc0:aaaa SU08G 7.40 GiB > mmcblk0: p1 p2 > mmc1: new SDIO card at address 0001 How long did you wait? I've had the boot appear to stall if the EXT3 filesystem got corrupted on a previous boot and the whole thing needs to be rescanned. I don't think I've ever actually had it stop complete here (max. 5 mins stall). Also, are you using an SD card >=2GB? Informally, I've had issues with SDHC cards on the 2.6.32 android kernel. > > and then nothing happens. No more modules no more messages. No android > either. I've followed all the instructions in the guide to the letter and > I'm really puzzled as to why everyone out there seems to have gotten the > overo working using the guide and yet mine is giving so many issues. Most > people who had it working seem to be using the palo43 board. I'm using the > summit-board with overo fire. Are there configurations steps I might have > left out that are not mentioned in your guide? For summit, make sure you are specifying the right display (i.e. HDMI not LCD). This line, # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43' should be something like # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi' instead. > I might eventually have to apply the patches as well but that is somewhat > unfamiliar territory for me. Is there a walk-through I can follow? I found > the ones relating to IGepv2 that Hedwin posted. Did you tweak them > specifically for overo? How do you apply them? Adding the files directly > didn't work either. Have you tried building directly with the kernel? I > guess since you had to go with the patches that didn't work. I hope I'm not > asking for too much but I'm really hoping to get this working so I really > appreciate the help. There are many tutorials about using diff and patch and for git, I find I can usually get by with git man pages and information from this site:http://progit.org/. I did make some Overo specific changes but these were mostly for the kernel. I've taken patches directly from Hedwin and others commits and applied them to my repository. This includes the kernel directly. Perhaps I'm missing your question here? > > PS: Is it possible to update the guide about all the modules that are not > expected to work as well as workarounds? This might make it less of a hassle > trying to solve any issues that might arise. Please update the guide with your workarounds :). The motivation behind having a wiki is that everyone can help others by improving the collective documentation. -Ash |
From: wilhemina <fmp...@gm...> - 2011-01-22 18:19:57
|
Lol. Well said. I am using a 8Gb microsd card. That's an interesting point you bring up. I'll try it again with a 2Gb and see if that helps. As a test, I pretty much found and downloaded your prebuilt image and filesystem which you posted up sometime ago and tested it to similar results. Yes I also specified dvi in the uboot console. From your comments it would seem you already have the repositories patched which means that after repo sync I should pretty much have your patches applied already to my kernel build (if I understood you correctly). Can you give me an idea of what wifi files I need to build into the kernel and where I can find them? (sd8686_helper.bin etc) I'm going to rerun the build so if I get them working then I would most likely add updates to the wiki. Ash Charles-2 wrote: > > Hi, > > On Sat, Jan 22, 2011 at 8:21 AM, wilhemina <fmp...@gm...> wrote: >> fter disabling the wireless option using menuconfig, I didn't get the >> libertas messages anymore however, the boot process stopped at this >> point: > Okay---this is good to know a workaround for this libertas problem. > Thanks :). > >> >> Waiting for root device /dev/sdd2... >> mmc0: host does not support reading read-only switch. assuming >> write-enable. >> mmc0: new high speed SDHC card at address aaaa >> mmcblk0: mmc0:aaaa SU08G 7.40 GiB >> mmcblk0: p1 p2 >> mmc1: new SDIO card at address 0001 > How long did you wait? I've had the boot appear to stall if the EXT3 > filesystem got corrupted on a previous boot and the whole thing needs > to be rescanned. I don't think I've ever actually had it stop > complete here (max. 5 mins stall). Also, are you using an SD card >>=2GB? Informally, I've had issues with SDHC cards on the 2.6.32 > android kernel. >> >> and then nothing happens. No more modules no more messages. No android >> either. I've followed all the instructions in the guide to the letter and >> I'm really puzzled as to why everyone out there seems to have gotten the >> overo working using the guide and yet mine is giving so many issues. Most >> people who had it working seem to be using the palo43 board. I'm using >> the >> summit-board with overo fire. Are there configurations steps I might have >> left out that are not mentioned in your guide? > For summit, make sure you are specifying the right display (i.e. HDMI > not LCD). This line, > > # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 > omapdss.def_disp=lcd43' > > should be something like > > # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 > omapdss.def_disp=dvi' > > instead. >> I might eventually have to apply the patches as well but that is somewhat >> unfamiliar territory for me. Is there a walk-through I can follow? I >> found >> the ones relating to IGepv2 that Hedwin posted. Did you tweak them >> specifically for overo? How do you apply them? Adding the files directly >> didn't work either. Have you tried building directly with the kernel? I >> guess since you had to go with the patches that didn't work. I hope I'm >> not >> asking for too much but I'm really hoping to get this working so I really >> appreciate the help. > There are many tutorials about using diff and patch and for git, I > find I can usually get by with git man pages and information from this > site:http://progit.org/. I did make some Overo specific changes but > these were mostly for the kernel. I've taken patches directly from > Hedwin and others commits and applied them to my repository. This > includes the kernel directly. > Perhaps I'm missing your question here? > >> >> PS: Is it possible to update the guide about all the modules that are not >> expected to work as well as workarounds? This might make it less of a >> hassle >> trying to solve any issues that might arise. > Please update the guide with your workarounds :). The motivation > behind having a wiki is that everyone can help others by improving the > collective documentation. > > > -Ash > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/rowboat-android-on-overo-tp29715029p30737843.html Sent from the Gumstix mailing list archive at Nabble.com. |