Dell confirms protected WiFi problems, mislabeled batteries on the three Venue Pros sold so far

If you detected a hint of anger in our headline, please forgive us, but we’re sure many of you are going through the same rollercoaster of emotions — after all, Dell’s lovely portrait QWERTY Venue Pro has only been sold in ridiculously limited quantities through Microsoft’s seven retail stores so far, making them virtually impossible to buy for most of us. Anyhow, in the event you were lucky enough to get one, you’ll be pleased to know that Dell is aware of the problems you might be having connecting to secure WiFi networks, and the next batch won’t be afflicted — which might explain why they haven’t offered a steady stream of devices through the stores this week. They also mention it’s a “software glitch,” but there’s no mention of timing on an update for phones in the field.

There’s also been a problem with batteries on these inaugural devices being labeled as “engineering samples,” apparently, but Dell assures that they’re production-quality cells that have simply been mislabeled. They say that customers wanting an exchange either for the WiFi issue or the mislabeled battery can get one at their local store “beginning at the end of next week,” so we’d take that to mean there won’t be any stock filtering in for anyone until then. Patience continues to be a virtue we don’t believe in.

Dell confirms protected WiFi problems, mislabeled batteries on the three Venue Pros sold so far originally appeared on Engadget on Thu, 11 Nov 2010 13:04:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceDell  | Email this | Comments

Roku ‘disallows’ PlayOn, cites ‘possibility of legal exposure’

Bummer. Just a few short days after PlayOn support was apparently added to Roku’s stable of set-top boxes, it looks as if the fun has come to an abrupt halt. Based on quotes from both PlayOn and Roku staff members, it sounds like the PlayOn channel will no longer work on those who try to get it installed, but those who managed to slip in early may be in the clear. Jim, a PlayOn staffer, stated that his company was “contacted today by Roku and told that they were going to disallow this channel,” and because neither the Roku channel developer nor Roku “are affiliated with PlayOn, [they] have no control over the situation.” On the Roku side, one Patrick has confirmed that “while… many of you are excited about a PlayOn-compatible Channel and may be using it, it unfortunately presents the possibility of legal exposure for us; as a result, the current PlayOn channels have been removed and are no longer available to add to your Roku player.” If your bubble has just been popped in the worst possible way, we’d probably start looking into that 30-day return policy — for you early birds, is PlayOn still working on your Roku box? Hit us up in comments below.

[Thanks, Brian]

Roku ‘disallows’ PlayOn, cites ‘possibility of legal exposure’ originally appeared on Engadget on Fri, 29 Oct 2010 09:55:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourcePlayOn, Roku  | Email this | Comments

Clearwire throttling at-home WiMAX users?

Ah, throttling. Can’t ever seem to fully shake it, can we? Just weeks after hearing about a similar issue with the Epic 4G, scores of Clear at-home WiMAX users are now up in arms over apparent throttling on certain accounts. As the story goes, it seems as if the company is pulling back on upload and download speeds (from 10Mbps to around 0.25Mbps) for users who have consumed between 7GB and 10GB in a month, which is comically low even compared to Comcast’s hated 250GB / month usage cap. Forum users are finding customer service lines to be no help whatsoever, and some digging has found that this may all be a part of a network traffic administration program that’s ongoing within Clearwire. Have any of you seen similar issues? How much data are you sucking down per month? Does your usage clock still show up in your account profile? Let us know in comments below.

[Thanks to everyone who sent this in]

Clearwire throttling at-home WiMAX users? originally appeared on Engadget on Wed, 29 Sep 2010 10:35:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceClear Forums (1), (2)  | Email this | Comments

Sony A55 / A33 video recording limited by overheating sensor

So this is why the promo video accompanying Sony’s launch of the A55 and A33 was set against a snowy backdrop. It turns out that these oh-so-revolutionary translucent mirror shooters can’t keep their cool for any longer than 11 minutes when recording video at a temperature of 20 degrees Celsius with Image Stabilization turned on. The A55 is even quicker to overheat at 9 minutes, though it’s worth noting that with IS switched off you can obtain the maximum of nearly half an hour of footage — provided the weather doesn’t heat up. Sony blames this on the APS-C-sized sensor within, and it’ true that plenty of DSLRs come with artificial time limits — our D5000 won’t let us get past five minutes however we try to sweet-talk it — but it’s an irksome limitation to consider if you’re thinking of buying either of these Alphas for their otherwise awesome video capabilities.

Continue reading Sony A55 / A33 video recording limited by overheating sensor

Sony A55 / A33 video recording limited by overheating sensor originally appeared on Engadget on Wed, 29 Sep 2010 04:19:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceSony Japan  | Email this | Comments

Halo Reach requires hard drive to play in co-op mode, Microsoft working on this ‘temporary issue’

The Halo series has always been about addictive multiplayer experiences, so it’s most disturbing to find out that campaign co-op gaming on the latest title is a non-starter for people without a hard drive attached to their 360. An issue has been identified by users of the 4GB Xbox 360, whereby attempts to team up on the baddies with your buddies — whether locally or via Xbox Live — is met with an error message saying that a HDD is “required for this game type.” This affects both Halo: Reach and the earlier Halo: ODST. Adding extra memory via USB has been found to be ineffective, but at least Microsoft has stated that it’s aware of the limitation and is “quickly working to resolve it.” Standard multiplayer is predictably unaffected, so we suggest taking your rage out on some newbies while the MS techs figure out their caching algorithms.

Halo Reach requires hard drive to play in co-op mode, Microsoft working on this ‘temporary issue’ originally appeared on Engadget on Tue, 21 Sep 2010 02:54:00 EDT. Please see our terms for use of feeds.

Permalink Joystiq  |  sourceNukezilla, Eurogamer  | Email this | Comments

Did iOS 4.1 introduce in-car USB playback problems for you?

As with almost any software update, Apple has seemingly introduced a few new issues while ironing out a couple of others. Automotive forums around the web are ablaze with talk that iOS 4.1 has introduced any number of playback problems, with the bulk of complainers citing scratching, crackling or random disconnects when piping audio from their device to their vehicle via the dock connector. We’ve tested two iOS 4.1-equipped iPhone 4 handsets in two separate vehicles here at Engadget HQ, and we saw no quirks whatsoever, but we’ve no doubt that the issue is real to some extent. Prior firmwares have caused permanent incompatibilities between our iPods and vehicles before, and we’re about at our wit’s end. We know it’s impossible for the software engineers at Cupertino to test new builds on every car adapter out there, but we’re starting to wonder if they bother to plug ’em into any vehicles at all. Tell us below if you’ve pulled any hairs out in recent days, won’t you?

[Image courtesy of Murphy5156 / TiPb]

View Poll

Did iOS 4.1 introduce in-car USB playback problems for you? originally appeared on Engadget on Wed, 15 Sep 2010 10:01:00 EDT. Please see our terms for use of feeds.

Permalink iLounge  |  sourceApple, Prius Chat  | Email this | Comments

iOS 4.1: any problems for you?

Okay, so we’ve given you about a day to download, install, and tear iOS 4.1 into microscopic shreds. What’s the end result? We’ve been tipped on a handful of troublesome nuances in the update, ranging from unsolved proximity sensor woes to a sudden onslaught of voicemails — and we’re trying to get a feel for how widespread they all are. Care to chime in? Follow the break!

Continue reading iOS 4.1: any problems for you?

iOS 4.1: any problems for you? originally appeared on Engadget on Thu, 09 Sep 2010 13:32:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

How would you change Apple’s iPhone 4?

We know, half of you aren’t even going to read past the headline before you start angrily banging away about Apple’s admitted antenna gaff and the still-not-totally-fixed proximity sensor, but we’re urging you to look deeper. Think harder. Critique your criticisms. In all seriousness, Apple’s iPhone 4 garnered more attention (negative or otherwise) than any other phone released this calendar year, and for good reason — in fact, Apple itself had to hold an emergency press event just to announce what could’ve been announced in a PR blast: everyone’s getting a free case. That said, Cupertino has still managed to move millions of units in just a few months, and that demand doesn’t seem to be dropping off at any significant rate. If you’re one of the lucky (or unlucky) ones that have managed to procure Apple’s latest iPhone, we’re overly anxious to hear your thoughts on changing it. How would you have addressed the antenna issue? Would you have preferred a less drastic departure from the 3GS form factor? Would you have offered more colors than white and black? Thrown in Bluetooth 3.0 for kicks? Go ahead, the floor’s yours — just don’t abuse it, cool?

How would you change Apple’s iPhone 4? originally appeared on Engadget on Fri, 27 Aug 2010 22:58:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Samsung says GPS is ‘tested and validated’ on Epic 4G, our testing agrees

If you own a Galaxy S anywhere in the world or you’re thinking of buying one, you’re probably well-acquainted at this point with the GPS issues it’s been suffering that prevent you from getting anything close to a precise lock on your location — it might not be a deal-breaker for some, but for anyone planning on using their phone for turn-by-turn nav or fitness tracking (for instance) it’s a big deal. Samsung’s already committed to updating released versions of the phone in September, but what about the upcoming Epic 4G? Our testing suggests that it’s functional — Google Maps was able to give us extremely precise positions very quickly — and a statement we’ve received from Samsung seems to corroborate that:

“We have tested and validated both Network Assisted (indoor) and Autonomous (outdoor) GPS on the Epic 4G. With regards to Vibrant and Captivate, we are currently testing software updates which will optimize GPS performance. We expect to be able to make the updates available in September and will communicate more information and download instructions in the next few weeks.”

In other words, the Captivate and the Vibrant have the bug and will be fixed next month; the Epic, meanwhile, should be good to go when it launches on the 31st. Cheers to that, we say.

Samsung says GPS is ‘tested and validated’ on Epic 4G, our testing agrees originally appeared on Engadget on Wed, 18 Aug 2010 20:19:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Blue Screen of Death amongst issues that plagued Deepwater Horizon

A recent report in the New York Times details a myriad issues that led up to the eventual explosion that started the mess known as the “BP oil spill,” but aside from obvious mishandling of warnings and red flags, one particular issue was troubling those working on the Deepwater Horizon oil rig long before April 20th. Mike Williams, the rig’s chief electronics technician, has come forward with a multitude of icky details surrounding the negligence that was involved in the catastrophe, with the one most germane to our discussion being the following: “For months, the computer system had been locking up, producing what the crew called the Blue Screen of Death.” Williams continued, noting that “it would just turn blue,” with “no data coming through.” Of course, it’s not as if BSODs are totally uncommon out in the working world — Microsoft’s Windows powers the vast majority of systems that corporations rely on daily — but this one rubs just a wee bit differently. Hit the source link for the full spill.

[Image courtesy of Ultrasaurus]

Blue Screen of Death amongst issues that plagued Deepwater Horizon originally appeared on Engadget on Fri, 23 Jul 2010 22:52:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceNew York Times  | Email this | Comments