Haven’t willfully submitted to the CLIQ’s new update yet? Well, you might want to hold off, because it looks like the new code is causing more heartache than good. A variety of reports on T-Mobile’s official support forums echo the same overarching complaint, which is that messaging is a disaster zone ever since version 1.3.18 took hold — long freezes when using the messaging app or widget, messages not getting sent or being sent multiple times — basically all the things you really don’t want to happen on a device that touts its social connectedness. For what it’s worth, we’ve personally seen this happen on a CLIQ since the update, so we know there’s something going on here; T-Mobile says that the complaints have been “forwarded… to the appropriate people,” so hopefully we’ll see some resolution soon. In the meantime, users experiencing issues are advised to not perform a master reset — important advice, considering that’s one of the first fixes many users might entertain.

Update: Follow the break for the full details from Motorola — it looks like a date issue where the year gets stuck on 1969 is priority one for them, but they’ve got a workaround set up until a new OTA update’s ready. Messaging issues may be alleviated by clearing out your backlogs — if you’ve got too many old messages, it sounds like this could be bogging things down.

Continue reading Motorola CLIQs falling victim to latest firmware? (updated with official statement)

Motorola CLIQs falling victim to latest firmware? (updated with official statement) originally appeared on Engadget on Fri, 26 Feb 2010 12:02:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

Looks like someone at Google should fast forward those Nexus One design videos to the radio integration portion and figure out what went wrong, because it seems like the 3G coverage problem still hasn’t been fixed, even after that last big OTA update. What’s more, many in Google’s support forums are noting that the phone will drop a weaker 3G signal merely when held by the bottom, as the video below clearly shows. Oops. We’re not at all sure what’s going on here, but we’re hoping this issue can yet be solved with a software patch — things are going to get messy if this is purely a hardware issue.

[Thanks, Geathan]

Continue reading Nexus One 3G problems persist after update — is it a design problem?

Nexus One 3G problems persist after update — is it a design problem? originally appeared on Engadget on Thu, 11 Feb 2010 12:45:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

Okay, so we were under the impression that Facebook login credentials were a locally-managed affair, but it looks like almost anything can break when AT&T’s involved — according to CNET, the carrier just fixed “several problems” that had users logging into the wrong Facebook account from their phones. The issue was apparently related to subscriber identification numbers being mistranslated into bad URL session IDs, and AT&T says it’s taken some security measures to prevent it from happening again, while Facebook’s just shut off the automatic login feature that used the ID number entirely. Excellent work all around. Unfortunately, there’s also a pesky incident in Atlanta where someone was able to login to another Facebook account from an AT&T phone due to a bad cookie, but AT&T says that was an “isolated” case and that it’s “unclear how this cookie was set on the phone.” How very reassuring. Back to Friendster!

AT&T fixes bug that logged users into random Facebook accounts originally appeared on Engadget on Mon, 18 Jan 2010 23:04:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments