11
Apr
bart scream

Some of you who've played The Simpsons: Tapped Out, Electronic Arts' Springfield-themed Sim City clone, may have noticed a lack in features when compared with the slightly older iOS version. Namely, it lacked the ability to sync saved games (towns) over Origin, EA's much-derided social gaming platform and store. The latest update to the Android version adds Origin syncing... while leaving at least some players without a town to sync.

TAPPED OUT

While plenty of players were ecstatic at the ability to play Tapped Out across multiple devices and operating systems, at least a few let out a cry of "glavin" at the inexplicable loss, as evidenced by recent reviews in the Play Store and our own tips box.

09
Apr
wmp

Earlier this morning, something strange happened. A handful of paid Disney games – including Where's My Water?, Temple Run: Brave, and Wreck-it Ralph, among others – suddenly showed up as free in the Play Store. Naturally, stories started popping up in the Android world that a bunch of fairly popular games were suddenly available without charge for no apparent reason. Perhaps Disney decided that it was time to give some titles away – but that didn't make much sense, as the "lite" versions of most titles were still present alongside their formerly-paid counterparts.

1

Turns out it was just a glitch, and the games are once again donning their original $0.99 price tags.

30
Nov
trans_thumb

Earlier today, we noticed a bug report for a very strange issue with multiple user accounts on the Nexus 7. Apparently, certain applications are displaying the underlying screen - be it the wallpaper, app tray, or the Play Store (depending on where the app was launched from) - through the foreground app. But here's the kicker: it's only happening on secondary accounts. Yeah, it's confusing and strange.

There's also a Reddit thread that confirms this is happening, and it seems to only be affecting apps that call on some sort of transparency. To make sure it's not just a N7 bug, though, I grabbed the N10 to see if it suffers the same issue.

18
Jun
ATTOneX_thumb_thumb

Update: According to HTC, this problem is currently only affecting the Tegra 3 (international) version of the One X - not the Rogers/AT&T One X or international One XL. HTC advises those affected to contact customer support, though the channel through which you purchased your device is a good bet as well, especially if it was from a carrier or brick and mortar store where they can exchange the unit immediately.

If you're a One X owner (or an avid XDA reader), you're probably aware that some poor souls have been basically unable to reliably use Wi-Fi on their devices because of a manufacturing defect.

30
Sep
0WB0Jl_thumb_thumb1

The DROID BIONIC, it's no secret, hasn't been launched bug-free. In fact, there's a number of bugs, particularly the dreaded data connection drop, that make using the BIONIC a major annoyance at times. Verizon has apparently been keeping track, and has a very detailed list of the glitches currently afflicting the phone, given to a customer in a support e-mail (weird, we know). The good folks over at Droid-life have compiled a "Top 10" bug list along with all the reported issues (here), and we've excerpted a few that we've noticed most:

1.  Issue:  4G/3G Service – Data Connectivity

  • Marginal 4G to 3G transition:  Loss of data connectivity – The device may display 3G service indication but no data connections are possible.

30
Sep
google_nexus_s_21-500x540

If you've downloaded or had the Android 2.3.6 update pushed to your AT&T, T-Mobile, or unlocked Nexus S recently without issue, consider yourself lucky. None of this applies to the Nexus S 4G on the Sprint network.

While we reported that the update was breaking Wi-Fi and USB tethering initially, it seems something much, much worse is happening to some users who have received 2.3.6 OTA.

If you check out this Google thread, you'll see a number of poor souls have had all cellular connectivity stripped from their devices after updating. The easiest solution so far? Roll back to Android 2.3.4 (or earlier), which almost inevitably requires a full wipe of the device.

23
Sep
k83012_Not Amused

Update: After receiving a distraught email from Team ACS, it has been brought to our attention that their root method may not be the cause of signal loss on the Epic 4G Touch. We're currently researching the details and will update this post accordingly.

Update x2: According to new information we received, there have been reports of this same issue happening on non-rooted phones. We're not sure how things got twisted around to point the finger at rooted devices, but we do know that Sprint is looking into it.

Have you rooted your Epic Touch 4G? Apparently, some users who have tried to flash Zedomax and ACS's custom kernel have experienced a loss of signal bug.

22
Sep
Evil

When I switched from AT&T from Verizon and swapped my aging, battered, and bruised Nexus One for a DROID BIONIC, the possibility of buyer’s remorse was not on my mind. I was coming from AT&T - America’s single least reliable network in terms of dropped calls. So, I thought the last thing I’d end up doing was wishing I was back there. And now, at least part of me does.

If you own a Verizon 4G LTE handset, you’ve probably experienced an issue exactly or approximately like this one: You put your phone in your pocket or let it sit overnight, take it out some time later or the next morning, and there’s no data connection.

20
Jun
EVO-4G-3
Last Updated: June 5th, 2012

Update: As promised, this update is rolling out now. Here is the official changelog, per Sprint's forums.

  • Corrects voicemail notification issue (from 4.22.651.2)
  • Corrects issue with hearing aid compatibility menu disappearing (from 4.22.651.2)
  • Netflix compatibility (from 4.22.651.2)

You heard it here first, folks - the EVO 4G is receiving an update in just 5 short days to address two of the major problems that users have experienced after the jump to Gingerbread. Specifically, non-working Netflix (boooo), and odd Visual Voicemail notification behavior. The turnaround time in getting this update out is pretty impressive, considering the Gingerbread OTA landed just a little over 2 weeks ago.

25
May
htc_thunderbolt

When we leaked the official ROM and radio image for the HTC Thunderbolt's Gingerbread update last week, users were understandably excited. An official Sense, Gingerbread ROM was probably highest on the list of demands for Thunderbolt users (aside from better battery life, perhaps).

Unfortunately, at this time, we have to officially advise anyone using any ROM based on this leak to revert to a Froyo build or to CyanogenMod 7 as soon as possible. This includes any and all third-party Gingerbread ROMs for the HTC Thunderbolt not based on CM7.

We don't take announcing this lightly, but we do so erring on the side of caution because of the extent to which this problem bricks the phone.

Page 1 of 212