Available for a limited time only - £10 off a £20 spend at eXpansys! For more details visit this topic!

Please Log In or Register - it's FREE!

 
Reply to this topicStart new topic
 StowAway / iGo driver (multiplatform) compliance tests
Menneisyys
post Feb 4 2008, 16:00
Post #1


Addict
Group Icon

Group: Moderator Team
Posts: 862
Joined: 3rd December 2006
Member No.: 216,586

Device(s): a lot



Upon my fellow blogger Tim Hillebrand’s report and because I’ll need to quickly enter a lot of info at MWC (and I don’t want to lug around my desktop replacement and, therefore, pretty heavy IBM Thinkpad a31p just for inputting text), I’ve installed the latest StowAway / iGo Bluetooth drivers on all my mobile devices (even non-Windows Mobile ones) to find out whether the drivers available HERE are (still) compatible with the latest operating system / firmware versions. I’ve found out the following:

Windows Mobile

Pocket PC’s (a.k.a. WM6 Classic / Professional):

HP iPAQ hx4700 (WM5 AKU 3.5.2; selecting & using the Widcomm driver, NOT the MS one); HTC Universal (WM6), Dell Axim x51v (WM5 official A12 (AKU 2.3) ROM with the MS BT stack), HTC Wizard (mfrazzz’ XDA Mobile 6 Release 5 FINAL) and the WM2003 HP iPAQ 2210: all work OK with the factory, default driver.

(Note that, as far as mfrazzz’ XDA Mobile 6 releases are concerned, version 3 was a no-go at all: it didn’t even try to connect. Pressing the Disable built-in HID support doesn’t help at all – unlike with all my other test devices or the same Wizard running Release 5.)

Smartphones (a.k.a. WM6 Standard)

HTC Vox / s710 (factory WM6 Smartphone ROM); no native driver; therefore, I tested it with the s620 / Excalibur / MteoR driver (they’re the same – actually, it seems ALL HTC Smartphones have the same drivers, unlike with WM5 and pre-WM5 Pocket PC’s): OK

HTC Oxygen / s310 with the above MS SP drivers (no native driver): the config app doesn’t even load (“Keyboard driver not functioning!”); then, after closing it, I started to get system errors about the keyboard driver DLL not responding.

Blackberry:

BB 8800 (4.2.1.101 / 2.3.0.80, T-Mobile): Works OK; program invocation hotkeys also work as expected.

Palm OS:

Palm T3: Works OK, albeit some of the program invocation shortcuts (apart from the most basic calendar/ contacts / inbox) take you to some other program, not the default one (unlike with the WM or the BB version). Otherwise, it’s OK.

Symbian:

Nokia N95 (firmware version v20): No native N95 (or any new – the latest ones are dated from 03/2007; the Palm / WinMo / BB drivers have been released a bit later; for example, the BB one in 07/2007) drivers from ThinkOutside; however, the N92 driver works just great on the N95. All the shortcuts work (as opposed to the built-in drivers). Note that the green Fn + Backspace terminates the connection (unlike on WinMo), which, then, must be re-enabled by just re-invoking the wireless keyboard applet. Also note that, unlike with Windows Mobile, Alt+keys directly enters accented characters, which are a bit more cumbersome to bring up under WinMo.

Note that the built-in Tools / Connectivity / Wlss Keyboard works without the need to install any third-party driver – apart from the complete lack of program / task switcher shortcuts and the lack of the English Pound, Japanese Yen and Euro entry.

Conclusion

All in all, the drivers are fully compatible with even the latest devices / firmware versions on all mobile platforms. On Windows Mobile, all the tested WM6 devices, Smartphones and Pocket PC’s alike, worked just great.

That is, you don’t need to be afraid of purchasing the keyboard – it WILL (almost surely) work. The only device not compatible was the HTC Oxygen / s310 low-end MS Smartphone. This doesn’t mean there aren’t other WinMo devices incompatible with the existing drivers, though - it's just that I haven't found one.
Go to the top of the page
 
+Quote Post
eAngel
post Aug 28 2008, 01:11
Post #2


Newbie
Group Icon

Group: Posters
Posts: 2
Joined: 27th August 2008
Member No.: 420,405

Device(s): Moto Q9h



huh.gif I might have gotten into a pickle. I purchased the ThinkOutside iGo Stowaway Ultra-Slim Bluetooth Keyboard for Smartphones...as a b-day gift for Mom, who has the AT&T Palm Treo 750. Silly me, I bought it online, trusting the "compatibility" list the vendor supplied. Hmmm. Anyway, it's clear that the device software is only intended to support up to WM5.0 smartphones. In general, the keyboard connects well. The general "typing" functions well. But, the shortcut keys are a no go. So, I'm hopeful that you guys are familiar with this predicament, and possibly have a creative solution. I am ever-hopeful, and ever-grateful! Any help would be soooo very appreciated!



QUOTE(Menneisyys @ Feb 4 2008, 12:00) *
Upon my fellow blogger Tim Hillebrand’s report and because I’ll need to quickly enter a lot of info at MWC (and I don’t want to lug around my desktop replacement and, therefore, pretty heavy IBM Thinkpad a31p just for inputting text), I’ve installed the latest StowAway / iGo Bluetooth drivers on all my mobile devices (even non-Windows Mobile ones) to find out whether the drivers available HERE are (still) compatible with the latest operating system / firmware versions. I’ve found out the following:

Windows Mobile

Pocket PC’s (a.k.a. WM6 Classic / Professional):

HP iPAQ hx4700 (WM5 AKU 3.5.2; selecting & using the Widcomm driver, NOT the MS one); HTC Universal (WM6), Dell Axim x51v (WM5 official A12 (AKU 2.3) ROM with the MS BT stack), HTC Wizard (mfrazzz’ XDA Mobile 6 Release 5 FINAL) and the WM2003 HP iPAQ 2210: all work OK with the factory, default driver.

(Note that, as far as mfrazzz’ XDA Mobile 6 releases are concerned, version 3 was a no-go at all: it didn’t even try to connect. Pressing the Disable built-in HID support doesn’t help at all – unlike with all my other test devices or the same Wizard running Release 5.)

Smartphones (a.k.a. WM6 Standard)

HTC Vox / s710 (factory WM6 Smartphone ROM); no native driver; therefore, I tested it with the s620 / Excalibur / MteoR driver (they’re the same – actually, it seems ALL HTC Smartphones have the same drivers, unlike with WM5 and pre-WM5 Pocket PC’s): OK

HTC Oxygen / s310 with the above MS SP drivers (no native driver): the config app doesn’t even load (“Keyboard driver not functioning!”); then, after closing it, I started to get system errors about the keyboard driver DLL not responding.

Blackberry:

BB 8800 (4.2.1.101 / 2.3.0.80, T-Mobile): Works OK; program invocation hotkeys also work as expected.

Palm OS:

Palm T3: Works OK, albeit some of the program invocation shortcuts (apart from the most basic calendar/ contacts / inbox) take you to some other program, not the default one (unlike with the WM or the BB version). Otherwise, it’s OK.

Symbian:

Nokia N95 (firmware version v20): No native N95 (or any new – the latest ones are dated from 03/2007; the Palm / WinMo / BB drivers have been released a bit later; for example, the BB one in 07/2007) drivers from ThinkOutside; however, the N92 driver works just great on the N95. All the shortcuts work (as opposed to the built-in drivers). Note that the green Fn + Backspace terminates the connection (unlike on WinMo), which, then, must be re-enabled by just re-invoking the wireless keyboard applet. Also note that, unlike with Windows Mobile, Alt+keys directly enters accented characters, which are a bit more cumbersome to bring up under WinMo.

Note that the built-in Tools / Connectivity / Wlss Keyboard works without the need to install any third-party driver – apart from the complete lack of program / task switcher shortcuts and the lack of the English Pound, Japanese Yen and Euro entry.

Conclusion

All in all, the drivers are fully compatible with even the latest devices / firmware versions on all mobile platforms. On Windows Mobile, all the tested WM6 devices, Smartphones and Pocket PC’s alike, worked just great.

That is, you don’t need to be afraid of purchasing the keyboard – it WILL (almost surely) work. The only device not compatible was the HTC Oxygen / s310 low-end MS Smartphone. This doesn’t mean there aren’t other WinMo devices incompatible with the existing drivers, though - it's just that I haven't found one.
Go to the top of the page
 
+Quote Post
Menneisyys
post Aug 28 2008, 21:31
Post #3


Addict
Group Icon

Group: Moderator Team
Posts: 862
Joined: 3rd December 2006
Member No.: 216,586

Device(s): a lot



dunno why it isn't working - I have a LOT of WinMo devices, even WM6 ones and shortcut keys worked just great with most of them...
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic

Collapse

Similar Topics

  Topic Replies Topic Starter Views Last Action
No New Posts Topic has attachmentsIGO 8
13 pcbinternet 2,686 9th November 2008 - 13:25
Last post by: ivanxxx
No New Posts Here is a download location for Omnia CDMA driver
This one will work with XP for ROM Upgrades
3 miles_muso 906 Yesterday, 22:57
Last post by: picky-picasso
No New Posts igo mobile 8
working on X1?
2 dwj 396 17th November 2008 - 21:15
Last post by: Strongarm
No New Posts Free Jabra 2010 Bluetooth Headset Driver Pack with any mobiles.co.uk purchase
0 Paul (MVP) 241 12th November 2008 - 12:53
Last post by: Paul (MVP)
No New Posts Igo 8 Crashes my phone everytime ?
0 Omniamon 110 21st November 2008 - 15:53
Last post by: Omniamon
No New Posts Samsung modem driver still needed?
3 respider 196 30th November 2008 - 13:51
Last post by: Dj iCE

1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 


RSS hit counter Lo-Fi Version Time is now: 3rd December 2008 - 04:40

Please visit our 'Plus Partners' - these companies support MoDaCo through 'MoDaCo Plus' - Click Here for more details!

ActiveKitten | Aiko Solutions | Ateksoft | Binaryfish | Conduits | DeveloperOne | eSoft Interactive | FTouchSL | Inesoft | Lingvosoft |

monocube | Mykesoft | OmegaOne | Omnisoft | Opera Software | Resco | SBSH | Slipstream Solutions | SPB Software House |

Splashdata | Sprite Software | Syncdata | Teksoft | VITO | WebIS | z4soft

Would your company like to become a 'Plus Partner'? Click Here to contact us!