My Q1 is more than a year old now and while it’s still in good shape, it is showing some signs of aging. My power brick died just before our road trip. Fortunately I had a spare (1 for work, 1 for home) and the replacement arrived while I was gone.

I’m a little worried about the door for the VGA slot. It’s held up well but it’s feeling a little flimsy these days. I’ve blogged before about how I broke my Q1 Keyboard and Organizer Pack. I fixed the KB by cannibalizing the windows button. I find I don’t really use it much. I’m holding on to the Organizer Pack to see if it’s still useful. There’s a chunk of plastic missing near the power connection. I have no idea how that happened. Super glue continues to hold together my kick stand. It’s been at least 8 months since the kick stand incident and the super glue continues to hold fine.

Despite it’s aging signs, I haven’t found a compelling replacement. The Q1P comes closest to being what I want but that’s such a small move up it’s not gonna happen. The Q1 Ultra just doesn’t seem to have the horsepower I want and I’m not a thumb keyboard junkie. The Asus R2H or a Tablet Kiosk model would simply a feature set trade and I only bring up the OQO 2 when I want to fight with my wife over money.

So I think I’ll stick with the old reliable Q1.

RSS feed | Trackback URI

1 Comment »

Comment by R.Fernandez
2007-07-18 20:39:06

Would you recommend it for a newbie to buy even now, especially considering that the HTC Shift may be coming in late 3Q? I really can’t wait for the Shift to come, but by all accounts of those in the UMPC know, it seems that the Q1P is the best all-around of the current selection. There are opportunities out on eBay to pick one up, and I am awfully tempted…I’m not sure that I could wait until the Shift comes! Any suggestions?

 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> in your comment.