Fault
Latest
Apple replacing a small number of iPhone 6s batteries
Apple has let a cat out of its bag, the cat in this case being that there's a problem with some iPhone 6s models. According to the company, a fault with the battery is causing a "very small number" of handsets to randomly shut down. If you're rocking a device that was manufactured between September and October 2015, then you're eligible for a replacement. Simply head down to your local Apple Store or authorized service provider to have your serial number checked and, if you qualify, you'll get a replacement battery.
Verizon Samsung Galaxy S5 cameras are failing spectacularly
Well, this is embarrassing: the Samsung Galaxy S5 has only been on the market for two weeks, and it's already developed a major fault -- at least for Verizon customers. "Warning," the devices reads. "Camera failure." The camera module appears to be failing outright, with no hope of being revived. Users have tried restarting their camera apps, rebooting devices and even performing factory resets, but nothing works. For now, the only working fix seems to be replacing a device, but some users are still holding out for a software fix. Fortunately, Verizon and Samsung are both being fairly candid about the issue -- both companies have acknowledged the faulty camera and are asking customers to contact support for troubleshooting and warranty replacements. Most of the failed devices seem to be coming from Verizon specifically, but BGR says it's seen similar reports from Sprint customers, too. Have a faulty device? Skip past the break for Samsung's official response and customer service instructions.
Some 2013 Nexus 7 users report buggy multitouch, Google is investigating
A muddled sense of direction isn't the only problem affecting the new generation of Nexus 7 slates, it seems, as some users are also reporting issues with multitouch on the 1,920 x 1,200 display. The clip below the fold demonstrates the bug, and shows the touchscreen registering phantom inputs before freaking out for a couple of seconds. Over the past few weeks, chatter on the XDA Developers and Google Product forums suggests it's fairly common, with a response from Google on the latter stating: "The Android team is aware of this issue and investigating." We haven't had the same troubles with a 2013 Nexus 7 in our possession (running Android 4.3 build JSS15J, FYI), and while the root of the problem is still up for discussion, let's hope funky software is to blame -- no one wants the hassle of replacing faulty hardware, especially Google, when an OTA fix will do.
Users report new Nexus 7 suffering from GPS issues
The urban-hunchback shuffle is usually demonstrated by commuters slouching over a phone, in search of a pre-meeting coffee-house. But, if you're attempting something similar with the latest Nexus 7, maybe leave a little earlier. Why? Because word is that some users are reporting funky behaviour with the tablet's GPS -- perhaps causing a little deja vu for ASUS slate owners. Issues vary from total flake out, to halting after 10 to 30 minutes. Several attempted fixes -- including complete reinstalls -- haven't fixed things. Google is aware of the problem, and working on a fix -- but no details on when this might be delivered. It's suggested that disabling Google Play Services might help things. This component of Android is used by other apps though, so proceed with caution. Is it affecting you? Let us know in the comments.
Samsung may cough up millions over kaput TVs
A class action lawsuit filed by owners of faulty Sammy TVs has finally reached a settlement. The manufacturer has promised to foot the bill for new repairs, reimburse for previous repairs and hand out up to $300 to customers who no longer possess their broken TVs but can prove they once did. The fault can affects any of the models listed above -- possibly up to seven million sets in total -- and centers on an errant capacitor in the power circuit that stops the TV turning on, makes it slow to turn on, produces a "clicking sound" or makes it cycle on and off. If you think you're affected then check the source link for details on what to do next. Curious to know how much the lawyers got? A cool half-million for their troubles, which means they'll be upgrading to OLED.Update: A Samsung spokesperson offered up the following response, Approximately 1 percent of Samsung televisions sold in the U.S. from 2006 to 2008 have experienced some performance issues caused by a component called a capacitor. Since originally confirming this issue in early 2010, Samsung has voluntarily provided free repairs for U.S. customers with affected televisions. Recently, a nationwide class settlement covering all affected televisions in the U.S. was reached in Russell, et al. v. Samsung Electronics America, Inc., a lawsuit filed in the District Court of Oklahoma County in the U.S.
European Galaxy Nexus owners complain of erratic volume issue (video)
Samsung's new flagship smartphone isn't having the smoothest of beginnings. The strange ROM that cropped up a few days ago turned out to be an isolated incident, but now the forums are abuzz with an audio issue that looks a lot more serious. Essentially, the handset's volume control appears to have a mind of its own, flitting randomly between mute, full blast and everything in between. The problem has so far only been observed on European phones using the GSM 900MHz band, and it's exacerbated by the cellular modem either boosting itself in a low reception area or switching between 2G and 3G connections. A user poll over at the XDA Developers forum suggests around 60 percent of owners have experienced the fault. There's a video after the break, complete with a disappointed kid in the background bugging his dad for answers.
Apple returns a few Verizon iPad 2s to sender (updated: some got through)
Several 9to5Mac readers noticed a rather peculiar phenomenon this last week -- their freshly-ordered Verizon iPad 2 units shipped all the way from China just fine, only to boomerang back to sender right before delivery time. Now, Reuters has the official word: Apple's recalling an "extremely small number" of Verizon iPad 2s which were flashed with a duplicate MEID code. Should they have been delivered, users would probably have found themselves unable to connect to 3G, or booted off before long, as Verizon reportedly can only have one device with that unique identifier on the network at once. We're not sure whether to applaud, but it's good to see manufacturers taking responsibility for their hardware before it hits shelves. Update: We spoke with Apple about this, who wouldn't give us much beyond the official quote -- which is, for the record: "Duplicate MEID codes were flashed onto an extremely small number of iPad units for the Verizon 3G network." That said, we were able to confirm that a few of these 3G iPad 2s sneaked through and got into the hands of customers. Apple is, of course, replacing those free of charge, so if you're in possession of a brand new iPad that was never able to get on 3G... you know who to call. [Thanks to everyone who sent this in]
Apple investigating 3G issues on some Verizon iPad 2s, software fix expected soon
Having trouble hooking up your iPad 2 to Verizon's 3G network? Turns out you're not alone, and thankfully, Apple's well aware of this. In a statement to All Things Digital, Cupertino said it's investigating this CDMA connectivity issue as reported by "a small number of iPad 2 customers," and word has it that a software patch will be available soon. Until then, personal hotspot is your friend, or you could just borrow some mobile WiFi from your actual friends -- protip: a smile goes a long way.
Xperia Play delayed by O2 UK due to software bugs, what are the other carriers doing?
Oh, woe is us. Or, to be more precise, woe is us if we wanted the Xperia Play on the UK's O2 network on the day of its release, April 1st. The British carrier has been candid in admitting it found software bugs on the Play and is holding back release of the gamer-friendly device until those have been ironed out. We appreciate its effort in "testing the phone non-stop for weeks" and its reluctance to grab a quick buck by releasing imperfectly baked goods, but a major question remains -- if this isn't an O2-specific software problem, and we've heard no peep of O2 customizing the Android 2.3 build on the Play, why are no other carriers signaling a similar delay? Vodafone is still aiming to deliver UK pre-orders by April 5th and there seems to be no indication of flawed software from others. Only thing we can think of, given that O2 has the white Xperia Play exclusive, is that the white phone curse has struck again. [Thanks, Ed] Update: Here's what Sony Ericsson has to say on the matter: "Sony Ericsson Xperia™ PLAY will be launching on 1st April across all UK mobile operator partners except for O2, who have decided to prolong the testing period in order to ensure that the software meets the requirements of its procedures. Sony Ericsson will be workingwith O2 over the next couple of weeks to expedite the process and ensure that O2 customers can soon join consumers across the UK in being able to enjoy the world's first PlayStation certified smartphone."
Adobe patches Flash flaw with Acrobat / Reader update
Armageddon averted. Exactly as promised, Adobe has rolled out a fix this week for the zero-day security vulnerability in Flash that had us sweating the world was about to come crashing to an end. It's a somewhat circuitous route to getting your system patched up, however, as you'll need to download an out-of-cycle update for Acrobat and Reader -- the other software affected by this issue. Still, a small price to pay for protecting yourself from the evils of the internets. [Thanks, Paul]
Google patches Flash vulnerability in Chrome, leaves other browsers hanging
Remember that massive security vulnerability that Adobe identified in its Flash Player, Acrobat and Reader software? Well, shockingly enough, it hasn't yet taken over the internet and ground productivity to a halt, but Google's been proactive about it and patched the flaw by itself. Of course, the fix applies only to its own Chrome web browser, Firefoxes and Internet Explorer types will have to wait for Adobe's fix, which is expected any minute now. Still, it's good to know someone's looking out for the security of our data, even if that someone already has access to most of it anyway.
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 pulls Windows Phone 7 update from Samsung phones until it can resolve issues
Such a big load of trouble for such a small update. Microsoft's first WP7 firmware refresh has been causing some unfortunate brick-like behavior in Samsung Omnia 7s and the company has wisely decided to pull the new software back until it can correct whatever's going wrong. An official communiqué to WinRumors says Microsoft has identified the issue at hand and is working to correct it and redistribute the update as soon as possible. For any Samsung WP7 phone owners who haven't been able to resuscitate their device yet, the advised course of action is to go back to the store and swap it for a livelier one. Update: Timo wrote in to let us know that some people are still seeing the update. If that's you, you'd be advised to hold off.
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]
Alienware M11x hinge issues? Yeah, Dell knows
Alienware M11x owners, have you noticed any problems with your hinge? Yeah, that thing that keeps the monitor and the keyboard conne -- no, not that. Not that either. No, that's a mousepad. You know what? Let's just move on. Notebook Reviews has been covering the tales of woe from customers who've noticed their laptop joints have suffered from dislocating, cracking, snapping, and other maladies. Good news, however, Alienware's given an official statement. The company acknowledges the issue and is "engaged the relevant internal teams here at Dell." Take heart, true believers, and consider not m
The apocalyPS3 ends in global resurrection, ARM chip at fault
The early belief that the PSN was spreading a brickitis infection to PS3s around the world has turned out to be not quite accurate. Yes, PSN was inaccessible over that extremely stressful day (for PS3 owners, the rest of us have been quite fine, thank you), but we're hearing from Eurogamer that the villain in this story was an ARM chip inside the console -- the very same one, in fact, that led to a few Zunes losing their minds back in 2008. The big problem here was simply a bit of hardware that couldn't get its bearings straight after expecting 2010 to be a leap year, and the arrival of March 1 "fixed" everything for all eight affected PS3 SKUs (of a total of eleven). That leaves Sony with four years to make sure this problem isn't heard from again, and if it doesn't, we'll be placing blame for the real 2012 apocalypse firmly on Howard Stringer's shoulders.
Laptop reliability survey: ASUS and Toshiba win, HP fails
Boy, do we have a nice slab of data for you to sink your teeth into today. The 3-year service history of more than 30,000 laptops has been pored over, analyzed, and reduced to gorgeous comparative charts, which you know you're dying to know more about. We should note, however, that the service was provided by SquareTrade, whose primary business is selling extended warranties, but that shouldn't completely prejudice us against reaching conclusions on the basis of the presented facts. Firstly, netbooks have shown themselves to be on average 20 percent less reliable than entry-level laptops, which in turn are 10 percent more likely to break down than premium machines. In other words, you get what you pay for -- shocking, right? The big talking point, though, will inevitably be the manufacturer comparison chart above: here ASUS and Toshiba (rather appropriately) share the winners' spoils, while HP languishes in the ignominious last place, with more than a quarter of all laptops expected to suffer a hardware fault of some kind within three years. So, does your experience corroborate / refute this info? Keep it gentlemanly, okay?
Nokia's XpressMusic 5800 troubled with speaker and NAM radio woes?
Seems all's not rosy in North American XpressMusic 5800-land, as tipsters and forums are buzzing with reports that the newly launched touchscreen isn't connecting to 3G. We did a little spelunking on the newly launched set ourselves, and we can confirm that 3G appears to be a complete no-go -- GSM works fine, but apart from a very brief 3.5G blip, we're getting nothing in terms of UMTS or HSDPA. Also on the block in the trouble department is the ongoing speaker failing issue we've heard so much about of late. Apparently the issue stems from a supplier's earpiece units packing it in -- and Mobile-review used science to prove this -- due to humidity. The fix? Grab one made in February, we're told, or if you already have one of the affected Euro-spec units, Nokia has parts in from a new supplier and should be able to sort you out right quick.
MacBook Pros exhibiting locking up with second displays?
Here's another Apple Support forums conundrum for ya: a small group of users are reporting that their Santa Rosa MacBook Pros are locking up sporadically when attaching or disconnecting a second display or projector. This post is currently being typed on a Santa Rosa MacBook Pro, which is regularly hooked up to a Dell monitor sitting on the desk: no problems here. That said, there are several dozen responses on this one thread, so feel free to weigh in if you're seeing these freezing issues too.
Breakfast Topic: This is all your fault and all of you suck
Every single time you're in Alterac Valley and your faction starts losing, someone starts whipping out the blame. Unless you ignore the battleground channel, you will be forced to read all about how you suck, how everyone else in this battleground sucks, how you should have done what they told you to do, and so on. Then, the other guy will pipe up with something like "would you shut up, dude? It's just a game," which sends the first one even deeper into his rage. Eventually he may just leave the match, or else quiet down while someone starts a chorus of "Guys, just let them win! I want to get my mark and go home."Personally, I'm a proud believer in the power of reason. Every time this happens, I find myself giving helpful suggestions, calming tempers, offering insights on how we could improve next time, and generally trying to play the peacemaker. Sometimes I can even find a strategy I think will turn the tide in our favor (and sometimes it works!), but usually I count myself a victor if people just see reason and behave civilly.What's your experience of people in battlegrounds who just can't handle losing? Have you been able to contain their blame explosions?
