RevAaron

@zillah That's a joke, right? There's a reason Google stopped selling them- they aren't in high demand. If anything, your resale value has dropped, as most folks aren't keen on committing to a phone without a future...

Hopefully they still have a good stock of refurb units for replacements- I'm about to send in my third Nexus One to get my fourth. Replaced for dust under the screen yet again, and a cellular modem that abruptly stops working left and right...

Updates won't come forever, at least not through official channels. A support case I opened 10 days ago ended up with the statement that all engineering has been terminated by Google, and that no further engineering or debugging of software and drivers specific to the Nexus One will be done. Sorry to burst the bubbles of @snowrid3r and @JL, but we will be forced to void our warranties to get Android 3.0, and most likely for any updates coming to us before that...

@jlaudio27 don't listen to him- don't root your Nexus One! It'll void your warranty completely and utterly- you won't be able to get your phone repaired or replaced even for physical problems like discoloration of the screen or dust under the screen. I've already had to return mine twice for the dust problem- and I've been told by three different HTC folks that I wouldn't be able to get it replaced under warranty if I had unlocked the boot loader, which is needed to root the phone...

Wow, HTC really knows how to do capacitive touchscreens!

I got a Nexus One two months ago. I'm on my third N1 right now- two were sent back for having dust show up under their screens over the course of two weeks. HTC says it is because internal seals weren't fitted well, but maybe it's the same problem as the EVO here is having...

Fortunately, HTC is covering this under warranty... The biggest reason NOT to root your HTC Android phones- your warranty is voided, and you are stuck with a phone with all sorts of physical design/build flaws. WOOHOO!

Aaron

This is nothing new. I've had this problem with the Nexus One since day one, or at least something quite similar. I've had it on all three of the Nexus Ones I've owned (two sent back for dust under the screen).

My general experience is that the touchscreen is flaky and often recognizes taps as slightly off, but when the N1's touchscreen problem is happening almost all taps are registered at the bottom of the screen.

I wonder if the problems on the Droid Incredible and EVO are derived from the same source as the problem on my Nexus One. The N1's touchscreen problems appear to be primarily in software; turning the phone off and turning it back on *usually* fixes it; a reboot in some cases is needed. This problems with the EVO and Incredible sound more like a mechanical problem.

Does the Droid Incredible use the same last-generation touchscreen sensor that the N1 uses? I really wish that HTC and Google had ponied up for a quality touchscreen sensor rather than a middling sensor from the last gen. :/

Aaron

As a Nexus One user, I sure as hell AMOLED isn't the wave of the future. I'll take the somewhat washed out color on an iPhone 3GS- or hell, an iPAQ 3600!- to having a screen that's almost unusable outdoors. Even at the brightest setting I need to get a shadow cast over my N1's screen to be able to use it- and even then it's a pain.

Man, these kinds of comments make me laugh. All OL-like, even.

For people who seem to think anyone who uses a Mac or iPod is some foaming at the mouth fanboy, you Zune/MS fanboys sure are irrationally exuberant. Christ, MS's software runs on the majority of computers on this planet- yet you still find something to whine about?

I mean, bias? WTF? Sure, Engadget is biased compared to the kind of unbiased gadget blog that ZuneGuy and a few of you clowns would write. Perhaps that's the answer? I'm sure you guys would cover non-MS products in a *very* unbiased, objective manner! Let's see it happen- the sky's the limit, etc, etc.

/me is wondering why all the Zune fanboys aren't telling MIcrosoft to just to buy a Nintendo DS instead of adding on a shitty API to their PMP. You guys were just telling me that the Zune is such a hardcore PMP that it doesn't and shouldn't have a clock, that putting a clock item burried in the settings menu would be adding too much clutter.

Maybe we can add games to our Zunes, but they'll just be invisible games, with no menu items through which to access them?

I've got an idea- the first game for the Zune will be... a clock! Then I'll sell it on the Marketplace, and we'll see how many of you anti-clockite deviants sell out your ideals and buy it. :D

Just a little hint: Mr. Gates and his company didn't get to be King of the Hill by whining.

...still no clock? Christ, how hard could it be? I've written clocks widgets for embedded GUIs a few dozen times- even just raw framebuffers. There is no excuse.

I'm still WTFing over this one. I was going to stay with the pre Zune 2 firmware- I wouldn't go so far as to say I was happy with it, but I knew I didn't want to upgrade... but no! We don't get things called "options."

And with firmware 2 and 2.5 we still get no fucking clock, eh?

The Zune's software is such an incompetent proof of concept aimed at hipster tennieboopers. At one point, the iPod made Apple a great target for "Form over Function" criticism, but Microsoft has taken that to a nauseating extreme. Well, at least they beat Apple at *something*.

OK, I have to ask- what's the big deal about the Touch? I mean, I have a WM6 phone, a Mogul on Qwest, and like it quite a bit. I wouldn't mind have a Touch-ish phone, in the sense of a not-recessed glass screen like the iPhone and the HTC Touch, but with the HTC Touch it just seems like a gimmick. Unless there is some drastically better new ROM that the Sprint store hadn't installed yet, it seemed like it aped various iPhone functionality in a poor way. Things like scrolling, using my finger, was clumsy as hell, just as bad (or good?) as using the utility meant to duplicate it for other WM6 devices. It certainly didn't have the kind of usefulness in that regard as the iPhone or using Picsel or Opera on a WM6 device.

What gives?

I've often wondered- is there anyway to use an EV-DO WM6 phone to do this? That is, allow my Qwest Mogul/HTC 6800 to take its EV-DO TCP/IP connection and share it with another device via wifi, acting as an access point. This would let a lot of devices get online through my phone that otherwise can't. Something I often could've used, but sort of hard to Google for.

Similarly, does anyone of something along those lines being worked out for the iPhone by homebrewers? Take the TCP/IP EDGE connection and share it through the iPhone's wifi. For me, the lack of the ability to use the iPhone as a modem, as a device to get online with my computer via BT is a showstopper.

I used to have an app on my Newton 2100 that came in handy during a few emergencies... I had a modem for my Newton, but not for my desktop, and a handy app just routed between the Newton's port to the modem; the G4 tower then had a serial to USB adapter. It was slow as hell, but better than not having any net access whilst I waited for the cable to get connected! :)