issue
Latest
Updated Windows Phone 7 update isn't updating some Samsung phones for March update (updated)
Man, talk about a flustercuck. After missing a cycle with its mobile phone strategy, the last thing Microsoft needed was a support fiasco related to its very first Windows Phone 7 software update. But after re-releasing a patched software update meant to solve the update issues seen by some Samsung owners, we're now seeing reports of a new issue on Twitter and in a variety of support forums and blog comments. At the moment, there's no clear fix to the dilemma characterized by a wonderfully descriptive "error code 800705B4." Unfortunately, what solves the problem for some (reboots, removing apps, freeing up space on the handset) doesn't work for others. Microsoft's official Windows Phone 7 Support Twitter account has responded to one frustrated customer saying, "We are aware of the error code and are looking into it right now," telling another to hold off on the update while MS investigates. Funny thing is, this minor WP7 update wasn't meant to do anything except prepare phones for the first feature update scheduled for early March. Not funny ha ha. Update: Microsoft has issued an official workaround that involves removing all media. If that doesn't work you can try removing all your installed apps and then all of your installed games. Yes, that does sound a lot like shooting in the dark but hey, it's official. [Thanks to everyone who sent this in]
Google restores Gmail access to one-third of affected users
If you've been following the seemingly-massive Gmail outage, you'll know that it's actually not as massive as it sounds. Google's revised its estimate again to say that only "0.02% of Google Mail users" -- roughly about 38,000 by our calculations -- were affected by the issue in total, claims that a full third of them have already had access restored, and expects the issue "to be resolved for everyone within 12 hours." As to the fate of years worth of email, Google reps wouldn't say, but promised us that engineers are working "as quickly as possible" to see the data restored as well. Keep hanging on, folks.
Vodafone's UK network taken down by a break-in (update: some services restored)
Some of our UK readers have woken up to the less than awesome discovery this morning that their phones have lost all connectivity to the outside world. 3G, 2G, SMS, and BlackBerry services on the Vodafone UK network are all down for what seems like a significant proportion of its user base -- an issue the carrier has since identified as being caused by a break-in at its Basingstoke exchange center. No further details have been provided, though work is naturally underway to repair the damage done and we're assured customers' private data has remained so. We can't imagine quite such a service disruption being caused by a random act of vandalism or burglary, perhaps a disgruntled employee felt the need to vent his or her frustrations in grand style? Or has O2 gone gangster on the competition? [Thanks to everyone who sent this in] Update: Vodafone got in touch to say that 2G and 3G voice connectivity has been restored as of lunchtime in the UK and text and data services should be up within "the next couple of hours." The company estimates the issue has affected "a couple of hundred thousand users", though it expects that number to drop to zero before the day is through.
Microsoft details Windows Phone 7 update problem, 'small number' of Samsungs affected
Redmond is opening up and offering a few facts, stats, and tips around its first update to Windows Phone 7 -- an update that didn't go smoothly for everyone -- and it sounds like there are at least three distinct failure modes, two of which are pretty simple to fix. The company figures that somewhere around 10 percent of users attempting the upgrade encountered a problem, but of those, "nearly half" failed because they lacked a proper internet connection or enough disk space (turns out the update process takes a backup of the phone's contents just in case something goes horribly awry). Most of the remainder may have been swept up in the issue affecting "a small number" of Samsung devices, an issue that the company says it's working to fix as quickly as possible -- and in the meantime, they've turned the update off for those models. Put simply, when you get prompted to install the update, Microsoft simply recommends that you've got plenty of hard drive space on your PC (you can't do this one over the air) and a solid connection to the interwebs; some 90 percent succeeded in installing the new code, which isn't too shabby considering this is the very first update to the platform they've attempted so far. Let's just hope that brick rate is down to zero by the time the good stuff comes, right?
First Windows Phone 7 update not going smoothly for some Samsung handsets (update: Microsoft suggests temporary fix)
So this is why they do phased rollouts, eh? If Twitter is the font of truth and reality that we suspect it to be, it sounds like users of some Windows Phone 7 models by Samsung are struggling with that minor first update that Microsoft started pushing this week. Basically, it sounds like the update isn't consistently completing; it some cases, users get an error message, and there doesn't appear to be any way to roll back or restore the prior firmware and get the phone back to a working state. Mass bricking is probably the greatest fear of software engineers before deploying handset updates to the field, so it's a good thing they're taking it slow; of course, that's not much consolation to the folks who are stuck making a call (on someone else's phone) to Samsung support. [Thanks, jdog25] Update: the::unwired is reporting information straight from Microsoft on how to fix a "bricked" device that doesn't complete the update, and it's deceptively simple: just pull the battery, put it back in, and turn the phone on. Failing that, perform a hard reset. Either way, the company is recommending you don't attempt the update again until the phone reminds you, which it says will happen in about three days.
Momentus XT hybrid drive causing headaches, Seagate working to fix
All's not well in hybrid solid state storage land, as owners of Seagate's Momentus XT are facing serious issues with their drives -- despite glowing initial reviews, a number of long-term users claim that the drives chirp, crash, stutter, and freeze with alarming regularity, particularly when installed in a Mac. Seagate forumgoers speculate these are symptoms of the XT's magnetic platters spinning down inappropriately, due to an overzealous power management scheme. That's the bad news -- and it sounds pretty bad -- but the good news is this: Seagate's owning up to the issues, and is actively involved in getting them fixed. So far, a pair of new firmware updates have addressed some symptoms, a third is on the way, and a Seagate engineer known only as STX_NB is proactively chatting with affected customers about possible fixes. That's what we call technical support -- take notes, tech companies.
Windows Phone 7 camera settings keep going to default, Microsoft says it was 'a decision by the team'
"It's not a bug, it's a feature" is one of the time-honored mantras of computer engineering, and Microsoft is using it to full effect with a behavior occasionally cursed by users of Windows Phone 7 devices: the camera settings return to their defaults every time you load the camera app. Responding to a comment in the official Windows Phone Blog, a Microsoft rep says that the settings reset was actually "a decision by the team," noting that if you need to pull out your phone for a quick shot, you'd rather not have to fiddle with whatever wacky settings you had set up on the prior use. Continuing, he writes that "feedback from folks like [the commenter] has the team seriously looking at that option to see if there is a more optimal option," so it could change -- so your dream of shooting absolutely everything in sepia tone might be realized with a little less strife down the road.
Nexus S suffering from random data loss, reboots? (updated: fixes coming!)
Lots of people have lots of problems with lots of things, but to say that we've been getting lots of complaints about Nexus S issues would be an understatement. Hundreds have chimed in on the Google Mobile Help forum indicating that their handsets are frequently losing data signal and, once lost, a reboot is required to reconnect. It's been said this could be related to an issue that's been around since 2009 (issue 2845), but a new issue in the Android bug tracker has been created, 14672, which specifically deals with the Nexus S. You might want to star 'em both if you're affected -- or feeling charitable. Finally, and perhaps even more troubling, is the phone rebooting. By itself. In the middle of a call. You can imagine how this might be a little annoying. That issue is number 13674 and it's linked down there too. Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item. [Thanks to everyone who sent this in]
Intel's partners can resume shipping Sandy Bridge laptops... if they agree to a workaround
Fret not, to-be Sandy Bridge buyer -- it looks as if the laptop delays won't be as severe as expected. According to Intel, it's working hard (read: coercing) with OEMs to keep Sandy Bridge laptops flowing from the factory, and apparently, that involves a pinky swear that partners won't utilize the four affected ports. That means that existing machines can be shipped with the first two SATA ports on the mainboard enabled, and considering that most lappies have just a single HDD, one optical drive and no eSATA sockets, the vast majority of 'em should be able to ship sans issue. An Intel spokesperson wouldn't confirm to Laptop the exact vendors who were agreeing to the terms, but at least Chipzilla is now aiming to have newly designed (and unmarred) parts in the channel by "mid-February."
Yahoo: nonstandard IMAP implementation to blame for Windows Phone 7 data leak
Finally, what the world's been waiting for: an explanation from Yahoo regarding its role in Windows Phone 7 Data Leakage-gate. (And we suppose that you have a better suggestion?) Here it is, in full: Yahoo! Mail is widely available on tens of millions of mobile phones, including those running on Apple iOS, Android, Nokia Symbian, and RIM. The issue on the Windows Phones is specific to how Microsoft chose to implement IMAP for Yahoo! Mail and does not impact Yahoo! Mail on these other mobile devices. Yahoo! has offered to provide Microsoft a near-term solution for the implementation they chose, and is encouraging Microsoft to change to a standard way of integrating with Yahoo! Mail, which would result in a permanent fix. Now, we know what you're thinking: why is everyone always picking on IMAP? But at least they're working hard on a fix, and in the end that's what really matters.
Dell, Gigabyte and MSI pull products in wake of Sandy Bridge chipset flaw, HP faces delays (updated)
Every time we write about Intel's flawed Sandy Bridge chipset and the need for it to be physically replaced, the financial costs go up. Intel initially projected a $300 million hit to revenues, but then it set aside $700 million to cover repairs and replacements, which together brings us to the current estimate of $1 billion lost in "missed sales and higher costs." Those missed sales will be coming directly from guys like MSI and Gigabyte, two of the major motherboard makers, who have stopped selling their Sandy Bridge-compatible models until Intel delivers untainted stock, and also Dell, who has nixed availability of its Alienware M17x R3 gaming laptop. CNET did spot that HP and Dell were still selling laptops with the offending chipset in them yesterday, but we imagine both will get their online stores straightened out in due course. For its part, HP says it's pushing back a business notebook announcement due to this news, much like NEC has had to do. Moral of the story? Don't let faulty chips out of the oven. Update: Dell says the M17x R3 is just the tip of the iceberg here: "This affects four currently available Dell products, the XPS 8300, the Vostro 460, the Alienware M17x R.3 and the Alienware Aurora R.3, as well as several other planned products including XPS 17 with 3D. We're committed to addressing this with customers who have already purchased one of the four products and will provide further details on this as it becomes available." [Thanks, geller]
Android Market acting weird -- is it a precursor to tomorrow's event?
We've gotten a bunch of tips in the past hour or so that the Android Market is doing weird things, and we can corroborate this on our Nexus S here -- we're just not able to download stuff. Apps look like they're starting to download, then they suddenly vanish into thin air without a trace and without an error message. Our Droid 2 is still fully functional, though, so this definitely isn't consistent; really, we're just wondering if this outage might have something to do with tomorrow's Android-themed festivities at the Google campus, which -- naturally -- we'll be attending. So how is everyone faring out there tonight? [Thanks to everyone who sent this in]
Intel Sandy Bridge chipset flaw identified as a rogue transistor affecting SATA ports
Intel raised quite a few eyebrows yesterday by disclosing that its Cougar Point chipsets suffer from an incurable design issue that would potentially degrade Serial ATA transfers over time. AnandTech has gone to the trouble of getting in touch with Intel to seek more information and the problem, as it turns out, is a single transistor that's prone to a higher current leakage than tolerable. This can not only diminish performance over the 3Gbps SATA ports, it can actually make them fail altogether. There is more comforting news, however, in that the pair of 6Gbps SATA ports on the chipset are untroubled by this ailment, so devices and users that never plug into the 3Gbps connections can just carry on as if nothing's ever happened. For everyone else, a repair and replacement service is taking place now, with Intel's budget for dealing with this problem said to be a generous $700 million.
Windows Phone 7 'phantom data' leaker unmasked as Yahoo Mail, fix due in 'coming weeks'
J'accuse... ! Remember the unnamed third party that Microsoft had found to be abusing 3G data on Windows Phone 7? Secret's out, and the culprit is none other than Yahoo Mail. According to a statement obtained by Microsoft guru Paul Thurrott, a fix is expected in the "coming weeks," but in the interim, you can mitigate the pain by going into settings and choosing less taxing options for "Download new content" and "Download email from" -- say, for example, "manually" and "the last 7 days," respectively. At least now you know exactly at whom you should wag your finger.
Nexus S reboot bug could be fixed within 'one to two weeks,' sez Google
Some percentage of Nexus S units in the field are afflicted with random reboots; there doesn't seem to be any rhyme or reason to when it happens, how often it happens, or what causes it -- but needless to say, a phone that could restart itself at any moment is not the best situation. After a few weeks of angry threads in the official Nexus S support forums, Google employee Ry Guy has chimed in with this encouraging tidbit: "The initial results of our tests look very promising. At this rate we will most likely be rolling out an OTA to resolve this issue within one to two weeks. We really appreciate your patience as we do our final verifications on this fix before sending it out." So that's a good thing -- and in the meantime, we just hope you enjoy occasionally seeing the awesome Nexus boot animation by surprise.
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).
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]
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."
Halo: Reach co-op hard drive requirement unresolved, no ETA on fix
Following the launch of Halo: Reach, we reported that the game's co-op functionality requires an Xbox 360 hard drive. This was of particular concern to those who had purchased one of the newly released 4GB Xbox 360 S models. At the time, we were told that the issue was "temporary" and that Microsoft was "working to resolve it." Repeated attempts to confirm with Microsoft when the situation will be resolved have been met with assurances that the company would let us know when there's an update, though no further details have been provided. It's currently unclear if and when the issue will ever be fixed, so consider this a PSA: If you've been holding off on picking up Reach until this particular shortcoming is addressed, you may want to start shopping for hard drives instead.
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!]
