Guest Chrimbow Posted September 15, 2005 Report Posted September 15, 2005 has anyone any experience of using the XDA2i (the newer XDA with no slide out keyboard and the faster chip) as im trying to decide wether to go for the xda2i or xda2s (with the keyboard). The i would be better for me as the better quality camera would be useful for work, but im concerned with how it works with tomtom. any idaes/advice? maybe a plug-in keyboard?
Guest Pondrew Posted September 15, 2005 Report Posted September 15, 2005 The threads I've read are inconclusive on whether the XDAIIi will run TomTom without problems. Some peeps have claimed it won't while others say they have no problems. Might be best to check with TomTom support to see what the official word of the moment is... You can definately get a plug in keyboard although I don't know how practical it would be. A friend recently brought over his XDAIIi and proudly showed off the Bluetooth infrared keyboard (projects a keyboard onto a surface which you can type on) he'd bought. Not all that if you ask me... didn't want to respond very well on my kitchen worksurface!
Guest Chrimbow Posted September 15, 2005 Report Posted September 15, 2005 Hmmm, interesting. What about the xda2s with the keyboard? Ive seen threads about people having probs with the slideout keyboard entering postcodes as the umbers are on a shift button and tomtom wont recognise the the shift key
Guest Chrimbow Posted September 15, 2005 Report Posted September 15, 2005 tomtom's site lists xda2i as compatable but im not convinced, any users out there reading this with any advice? (pretty please!)
Guest Pondrew Posted September 15, 2005 Report Posted September 15, 2005 Hmmm, interesting. What about the xda2s with the keyboard? Ive seen threads about people having probs with the slideout keyboard entering postcodes as the umbers are on a shift button and tomtom wont recognise the the shift key <{POST_SNAPBACK}> If I remember right there was a problem with compatibility between the XDAIIs keyboard and TomTom but I believe that problem was resolved in the latest TomTom release.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now