Editorial: bugs on unreleased phones don’t matter (update: Motorola says phones will ‘ship as scheduled’)

There’s a story going around today about an alleged problem in the power management unit affecting Motorola’s first two dual-core smartphones — AT&T’s Atrix 4G and Verizon’s Droid Bionic — that leads to a hodgepodge of issues: overheating, weird RF fluctuation, the list goes on. Sounds like a tragedy in the making, doesn’t it? Worst yet, the PMU problem is said to be a “major unfixable flaw that will plaque [sic] it forever.” Bummer!

But let’s back up and consider the facts here. First, as best we can tell, the sources are two posters in a HowardForums thread, one of which doesn’t even have the information firsthand — he was allegedly given the news “by someone who is testing the devices.” Furthermore, there’s really no such thing as an “unfixable” bug; you might need to peel away several layers of software and hardware to fix an issue depending on how fundamental the flaw turns out to be, but engineers have proven time and time again that “unfixable” isn’t really in their vocabulary (white paint aside, of course).

Continue reading Editorial: bugs on unreleased phones don’t matter (update: Motorola says phones will ‘ship as scheduled’)

Editorial: bugs on unreleased phones don’t matter (update: Motorola says phones will ‘ship as scheduled’) originally appeared on Engadget on Wed, 26 Jan 2011 14:36:00 EDT. Please see our terms for use of feeds.

Permalink Electronista  |  sourceHowardForums  | Email this | Comments

Nexus S OTA 2.3.2 update rolling out now, your SMS relations will thank you

Embarrassing SMS misdirect bug on your Android device? Nexus S owners should start checking their phones now for an over-the-air update that’s supposed to fix the problem. It’s being rolled out gradually, so just be patient if it’s not there yet. How will we know the problem’s gone for good? We’ll just assume so until we find out otherwise, in some unfortunate manner.

[Thanks to everyone who sent this in]

Nexus S OTA 2.3.2 update rolling out now, your SMS relations will thank you originally appeared on Engadget on Fri, 21 Jan 2011 18:59:00 EDT. Please see our terms for use of feeds.

Permalink @GalaxySSupport (Twitter)  |  sourcexda-developers  | Email this | Comments

Microsoft tracks down ‘phantom data’ bug in Windows Phone 7, points finger at unnamed third party

Tired of your Windows Phone 7 device sending and receiving random bouts of data? Well, Microsoft is, too — and they’ve started to reach some conclusions from that investigation opened a few days ago. Apparently, there’s a “third party” that’s responsible for the misbehavior, and Redmond’s already reached out to help ’em make the necessary fixes; the story isn’t necessarily over, though, because they’re still “investigating additional potential root causes,” which we presume could involve the operating system itself. As for the third party, it seems a “small” number of customers are affected, which probably explains why it’s taken this long for the complaints to come to a rolling boil. Here’s the full statement:

“We have determined that a third-party solution commonly accessed from Windows Phones is configured in a manner that potentially causes larger than expected data downloads. We are in contact with the third party to assist them in making the necessary fixes, and are also pursuing potential workarounds to address the configuration issue in case those are needed. At this point in our investigation, we believe this is responsible for most of the reported incidents.

We are investigating additional potential root causes for the remainder of the reports.

A small (low single-digit) percentage of Windows Phone customers have reported being affected.

We are continuing to investigate this issue and will update with additional information and guidance as it becomes available.”

Microsoft tracks down ‘phantom data’ bug in Windows Phone 7, points finger at unnamed third party originally appeared on Engadget on Wed, 19 Jan 2011 18:38:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceSeattle Post-Intelligencer  | Email this | Comments

Android text messaging bugs acknowledged, fixes detailed

Hear that thunderous roar off in the distance, growing louder (and more frightening) as it persists? That is the sound of excited Android users emailing us to inform their fave gadget site that Google has just sent users an update to that little embarrassing SMS bug that we reported a while back. There seem to be two distinct issues: users have reported both opening one message to have a completely different message appear, and / or sending an text message to one contact yet having it delivered to another contact entirely. We need only say one word: sexting, to highlight just how dangerous this could be! Google promises us that a fix for these two issues are in the works. In the meanwhile, check out the e-mail below to read their response and work-around.

[Thanks Jon, and thanks to everyone else who sent this in!]

Continue reading Android text messaging bugs acknowledged, fixes detailed

Android text messaging bugs acknowledged, fixes detailed originally appeared on Engadget on Wed, 05 Jan 2011 22:21:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceGoogle  | Email this | Comments

Android still has horrible text messaging bugs that’ll get you fired, busted, or otherwise embarrassed

Pardon us if the headline is a little sensational, but this is one that we’ve personally experienced — and it’s not pretty. For at least the last couple versions, Android has been plagued with a couple extremely serious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact — even contacts that you’ve never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don’t notice, you’ll end up firing a message to the wrong person.

More seriously, though, there’s also an open issue in Android’s bug tracking system — inexplicably marked “medium” priority — where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you’ve committed until your boss, significant other, or best friend — make that former best friend — texts you back. There seem to have been some attempts on Google’s part over the year to fix it; we can’t confirm that it still happens in 2.3, but for what it’s worth, the issue hasn’t been marked resolved in Google Code… and it was opened some six months ago.

This is akin to an alarm clock that occasionally won’t go off (we’ve been there) or a car that randomly won’t let you turn the steering wheel — you simply cannot have a phone that you can’t trust to communicate with the right people. It’s a deal-breaker. We’re pretty shocked that these issues weren’t tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we’d like to see Google, manufacturers, and carriers drop every other Android update they’re working on and make sure this is completely resolved immediately.

Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit “Vote for this issue and get email change notifications.”

Android still has horrible text messaging bugs that’ll get you fired, busted, or otherwise embarrassed originally appeared on Engadget on Fri, 31 Dec 2010 13:12:00 EDT. Please see our terms for use of feeds.

Permalink BGR, ZDNet  |  sourceGoogle Code, Android Help  | Email this | Comments

Alienware M17x laptop said to be suffering from power-related GPU issues

Well, it looks like at least some Alienware M17x laptop owners just can’t catch a break. While the previous so-called DPC latency issue has apparently finally been resolved, a number of users are now reporting another issue that’s only become apparent after the earlier problem was fixed. As it turns out, the symptoms are similar to the stuttering caused by the DPC latency issue (hence the confusion), but the new problems are being blamed on power issues — namely, that the GPU is drawing more power than the laptop can provide. Worse still is that it seems like those with the highest-end configuration are the most likely to experience the problem, as they’re effectively maxing out an already maxed-out system. For its part, Dell has apparently fixed the issue in the most recent revision of the laptop, but users on the Notebook Review forums are reporting that the company hasn’t exactly been eager to dish out replacements for everyone affected (which seems to be the only surefire “fix” available).

[Thanks, Adam]

Alienware M17x laptop said to be suffering from power-related GPU issues originally appeared on Engadget on Mon, 20 Dec 2010 05:41:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceNotebook Review  | Email this | Comments

Dell: ‘Venue Pros are being reworked in the factories,’ ship schedule unclear

The Venue Pro delay situation certainly isn’t getting any clearer with Dell’s latest update on its support forums, but we know this much for sure: the new kid on the smartphone block still has a few things to learn about shipping handsets. A post from a Dell moderator says the company is working directly with Microsoft to draft a battle plan and that current Venue Pro owners (those that got their devices early on from Microsoft stores, that is) “might require another hardware swap” to get their issues solved. The rep says that she’s hearing that some orders could still potentially ship this week, but she doesn’t know which ones, and that affected customers are welcome to cancel their orders if they wish. So yeah, kind of a good news / bad news situation there. We’re still clinging to hope that we’ll see these things on the streets before the end of 2010, but it certainly seems like an iffy proposition at this point.

[Thanks, @steveymacjr]

Update: Dell’s posted a new blog entry on the matter, too, though it’s not much help — basically, you could get your phone before January 6th, but it’s anyone’s guess. They’re promising to keep people abreast of the situation as it develops.

Dell: ‘Venue Pros are being reworked in the factories,’ ship schedule unclear originally appeared on Engadget on Tue, 14 Dec 2010 19:04:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceDell Community  | Email this | Comments

HTC responds to HD7 death grip reports, says some signal drop is ‘inevitable’

Oh boy. We’d actually passed over reports that the HTC HD7 suffers from a “death grip” issue this past week, since we think it’s been well-proven that you can get almost any phone to drop some signal if you hold it exactly right, but apparently the furor’s gotten loud enough to merit an official HTC response. Here’s the statement, sent to Computer Weekly:

Quality in industrial design is of key importance to HTC. To ensure the best possible signal strength, antennas are placed in the area least likely to be covered by a person’s face or hands while the phone is in use. However, it is inevitable that a phone’s signal strength will weaken a little when covered in its entirety by a user’s palm or fingers. We test all of our phones extensively and are confident that under normal circumstances reception strength and performance will be more than sufficient for the operation of the phone when network coverage is also adequate.

Yes, that sounds almost exactly like what Apple said during its iPhone 4 Antennagate press conference, but that makes sense — we wouldn’t honestly expect HTC to say anything else, even though John Gruber points out that the company told the Wall Street Journal that Apple’s reception problems were “certainly not common” in July. But we do find it extremely interesting that the HD7 is clearly based on the HTC HD2, a handset which came out over a year ago and suffered from reports of similar reception issues. (In fact, a post at xda-developers in June noted that the HD2 has the same death grip issue as the iPhone 4.) Whatever the case, much of the problem seems to stem from the fact that the HD2 / HD7 antenna is located at the bottom of the phone where it’s most likely to be covered by a user’s hand, so it looks like the ultimate answer for HD7 owners is a familiar one: you’re holding it wrong. Video after the break.

Continue reading HTC responds to HD7 death grip reports, says some signal drop is ‘inevitable’

HTC responds to HD7 death grip reports, says some signal drop is ‘inevitable’ originally appeared on Engadget on Fri, 03 Dec 2010 10:17:00 EDT. Please see our terms for use of feeds.

Permalink Daring Fireball  |  sourceComputer Weekly  | Email this | Comments

Some Apple TV users reporting wacky color problems with Sony, Philips TVs

It doesn’t appear to be especially widespread, but a sizable number of reports are cropping up on the official Apple support forums of some pretty wild issues affecting the new Apple TV when paired with certain Sony and Philips TVs. As you can see above, those issues can include a rather unfortunate pastel color scheme (apparently common on Philips TVs), while others are also reporting inverted colors, and green or black screens. As for Apple, at least some users who’ve contact the company about the problem say it is aware of the issue, but early reports from those who’ve applied the Apple TV 4.1 update suggest they haven’t fixed the problem just yet. Has your Apple TV taken on a new hue? Let us know in comments, and check out a psychedelic video of the problem after the break.

[Thanks, Bea]

Continue reading Some Apple TV users reporting wacky color problems with Sony, Philips TVs

Some Apple TV users reporting wacky color problems with Sony, Philips TVs originally appeared on Engadget on Mon, 22 Nov 2010 21:10:00 EDT. Please see our terms for use of feeds.

Permalink MacStories  |  sourceApple Discussions  | Email this | Comments

Nokia says ‘very small’ number of N8s aren’t turning on, warranty will cover it

We’ve been getting a few tips this week — and seeing a few things on Twitter — saying that N8s are failing in noticeable quantities, but we wanted to hold off until we’d figured out what was really going on. Well, Nokia’s own Niklas Savander is commenting on the situation now — so we’d say it’s definitely real — though he’s insisting the number of affected units is “very small” and that the company’s normal warranty rules apply, so owners of dead units should contact their local support number. That’s all well and good, but getting service on a paperweight is still a bummer, especially when said phone is your primary means of communication — so let’s hope these guys turn around serviced devices in a hurry.

What do you call a dead N8, by the way?

N8 owner: A tragedy
iPhone owner: DOA
Android owner: About as useful as any other N8
N900 owner: A missed opportunity
Store sales rep: Dummy unit
Symbian Foundation employee: Justice
Olli-Pekka Kallasvuo: Karma
A goat: Dinner

[Thanks, John]

Nokia says ‘very small’ number of N8s aren’t turning on, warranty will cover it originally appeared on Engadget on Thu, 18 Nov 2010 17:25:00 EDT. Please see our terms for use of feeds.

Permalink BGR  |  sourceNokia Conversations  | Email this | Comments