Hasta La Gadget!

What once was there now is gone. Earlier today, Google Voice was just two clicks away in the iOS App Store. Now, all that remains is a page cache (at the source link below) and versions of the app that were already installed on iPhones and iPod touches. Vincent Paquet, Senior Product Manager for Google Voice confirmed that the app had been pulled, explaining “our last update of this week had a bug that caused the app to crash at sign in. We removed it so it did not affect additional users until the fix gets published.” We’ve been using the most recent version — 1.3.0.1771 — on an iPhone 4 running iOS 5 without issue, but recent reviews cite the reported crashing, so it’s definitely affecting at least some users. We don’t have an ETA for when you can expect the app to return, so if you don’t already have it installed, you’ll need to hang tight for the time being. The service should function normally otherwise, assuming your phone number has already been registered, though you won’t be able to begin new text threads or make outgoing calls using your Google Voice number.

Google Voice pulled from App Store following iOS 5 crash originally appeared on Engadget on Sat, 15 Oct 2011 18:33:00 EDT. Please see our terms for use of feeds.

Permalink   |  Google Voice (cache)  | Email this | Comments

Has your Thrive been acting more like sleeping beauty, and less like the tablet you paid for? Before embarking on a mythical tale, whereupon you eventually find its more charming compatriot, know help from Toshiba is forthcoming: “We’re aware of the issue and are working on a fix.” No further details on when it’ll land, or what exactly it’ll fix, but if you’re anything like us, you’re just happy it won’t end up where another Tosh tablet did — in eternal slumber.

Toshiba acknowledges Thrive’s sleep addiction, fix apparently in the works originally appeared on Engadget on Tue, 19 Jul 2011 04:34:00 EDT. Please see our terms for use of feeds.

Permalink   |  PCWorld  | Email this | Comments

ASUS’s mighty morphing Eee Pad Transformer might be a commercial success (even despite early delays) but, it seems, there’s something amiss with the shape shifting tablet. Earlier today, the company admitted to an issue relating to the slate’s keyboard dock. A post to ASUS’ UK Facebook page reads:

Apologies to anyone who has encountered issues with their Transformer keyboard dock (power drain and charging). The issue is related to the way we configured the device’s power management in/out of sleep mode. We will shortly be announcing details on how this will be resolved for our customers.

We’d say that’s about as vague a promise as a company could offer, but we’ll keep you posted as ASUS opens up.

Update: Looks like the Transformer is set to join the Xoom on the Android 3.2 bandwagon, as ASUS’ Twitter account announced that the company is testing the latest Honeycomb build on the Transformer as we speak, and ASUS hopes to release it “soon.”

ASUS promises fix for Eee Pad Transformer power drain, keeps the apologies coming (update: Android 3.2 is coming “soon”) originally appeared on Engadget on Wed, 13 Jul 2011 19:07:00 EDT. Please see our terms for use of feeds.

Permalink Android Community  |  ASUS (Facebook), @ASUS (Twitter)  | Email this | Comments

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 returns a few Verizon iPad 2s to sender (updated: some got through) originally appeared on Engadget on Sat, 11 Jun 2011 18:11:00 EDT. Please see our terms for use of feeds.

Permalink   |  9to5 Mac, Reuters  | Email this | Comments

You know what’s cool? Handing out 5,000 Android tablets to your most loyal developers at Google I/O. You know what’s not cool? Handing out 5,000 Android tablets that can’t have files loaded onto them. Believe or not, that’s exactly what happened at this week’s I/O conference, where hordes of developers were handed a Galaxy Tab 10.1 Limited Edition that cannot currently interface with OS X, and has a whale of a time doing so with Windows 7. During our initial preview of Music Beta, we noticed that our MacBook Pro (OS X 10.6) wouldn’t actually recognize the tablet, even after installing Android File Transfer. Given that we didn’t actually need that functionality for the purpose of said article, we threw it on the backburner.

For those unaware, Android File Transfer is a small app that’s required to transfer content between OS X and Android 3.0. Avid users of Froyo and Gingerbread may be appalled that any Honeycomb device they buy will require a piece of software to interface with it, but hey — there it is. At any rate, it seems to us that the latest build of Android File Transfer doesn’t include the device ID for Samsung’s heretofore unreleased Tab 10.1; if you’ll recall, the standard edition of this thing isn’t slated to hit consumer hands until June 8th. Regardless of what tricks we tried (installing a Mac version of Kies Mini, for example), we couldn’t get a single Apple in our stable to recognize the thing. In one instance, a Mac viewed the device as a “Samsung Modem” within the Networking pane — that’s as close as we could come to getting the two to mingle. AllThingsD‘s Ina Fried said her Tab 10.1 LE was merely recognized as a camera-like device within Aperture.

Over on the Windows side, things are only marginally less awful. We’ve had a couple of Wintel boxes outright refuse to play nice with this “mysterious USB device,” while others required multiple reboots and driver searchers to finally mount it as an external storage device — and only with USB Debugging disabled. The upside is that those with patience (and a Windows 7 rig) can look forward to a single method of transfer, but it’s certainly less than ideal.

We’re surmising that Google’s cooking up a new version of Android File Transfer as we speak that’ll take care of the compatibility issues, hopefully long before consumers start seeing these in early June. But for developers in the here and now? Stop wasting your afternoon trying to figure out why your Mac just won’t cooperate, and give that Win7 system a little love.

Update: After a bit of additional digging, we noticed that it’s possible to access the Tab’s file system from a Mac or Windows PC by using the Android SDK, putting the tablet in USB debugging mode, and running ddms. It’s not the most convenient solution if you want to quickly and conveniently transfer some content to / from the device, but it should work until AFT sees an update. Alternatively, we’re hearing that XNJB — an older open source project originally built for Creative Nomads — enables files to be transferred whenever it’s in a good mood.

Galaxy Tab 10.1 Limited Edition not seen in Android File Transfer, Windows usability is spotty originally appeared on Engadget on Fri, 13 May 2011 15:10:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments