Bug -- Engadget Mobile

bug posts

Bug in Motorola CLIQ's OpenGL implementation breaks a few games

by Chris Ziegler posted Nov 3rd 2009 @ 9:29AM

If you've run into trouble trying to load up Hexage's Buka or Totemo on your CLIQ, you're not alone -- it seems that some wonky handling of a few OpenGL API calls on Motorola's first Android device are causing heartache for users and developers alike. It's not clear how many apps in total make use of the calls, but we'd imagine they're in line to be fixed -- and thanks to the CLIQ's support for over-the-air updates, we're hoping those fixes come sooner rather than later. In the meantime, we suppose that DROID's always an option, right?

[Via I4U and Android and Me]

iPhone OS 3.0 bug allows deleted emails to rise from the dead

by Nilay Patel posted Aug 17th 2009 @ 5:31PM

Get ready for another big glitch in iPhone OS 3.0: it seems like the Spotlight search cache doesn't sync message status with the mail client, so you can still pull up old messages with Spotlight if you know the subject line. Yeah, that's not okay -- we just verified that the bug exists on our phones, using both POP and IMAP. We're not sure when the search cache finally deletes emails, but it doesn't appear to happen quickly: Matt Janssen, who discovered the bug, says he's been able to pull up emails three or four months old. We've heard whispers its fixed in iPhone OS 3.1, but until there's a confirmed fix we'll be using the Gmail web interface, thanks. Video after the break.

Continue reading iPhone OS 3.0 bug allows deleted emails to rise from the dead

Palm quietly improving Pre build quality, tweaking hardware

by Nilay Patel posted Aug 12th 2009 @ 6:23PM

It's not the most comprehensive survey, nor is there any official confirmation, but the crew at PreThinking has checked in with a number of new Pre owners and discovered that Palm's apparently building its webOS handset better lately -- and what's more, it's even made some minor improvements. The biggest change appears to be a fix for that nasty bug that caused the Pre to reset or turn off when the keyboard was closed -- that bit of grey foam pictured was added to the battery compartment to tighten up the battery connection. There's a also word that the screen cracking and unintended rotation issues have been addressed, although time will tell on those, and the button color has changed from pearl to silver. As for improvements, well, there's a new battery model, and the Palm logo is now embossed on the carrying case. Yep, just little stuff, but it's good to see Palm addressing the build issues on the Pre, which are by far the most common complaint about the device. Let us know if you've spotted anything else, would you?

Palm Pre trouble roundup

by Chris Ziegler posted Jun 7th 2009 @ 8:52PM

So we've been doing this whole gadget blogging thing for a while now, and we've noticed a timeline trend with these major, buzz-filled launches. They tend to go something like this:

T minus 2 hours: lines reach critical mass across the country; odds are you'll find some of us in those lines. Camaraderie amongst line-waiters is at a high, but it's a guarded emotion -- the scene'll turn ugly the second inventory runs out.
T minus 30 minutes: for morning lines (particularly those where folks have waited overnight), store managers come out and offer coffee and pastries. Anything less is uncivilized -- don't hesitate to complain.
T minus 0 minutes: the gizmo goes on sale.
T plus 1 hour: the first teardowns and cost estimates hit the web.
T plus 4 hours: mass (or at least loud) complaints of manufacturing defects, bugs, and shortcomings start cropping up.

It's still too early to tell whether the Pre is more, less, or equally as defective as any other blockbuster product in recent memory, but as you might expect, there are plenty of issues being sporadically reported in the first weekend of availability and it'll be interesting to see how Palm spins and handles them. Here are a few we're tracking:

A good number of early adopters are reporting "splotchy," distorted, or discolored displays (we've seen reports of dead pixels, too, though we'd actually be more weirded out if there weren't). See examples here, here, and here.
We've also heard reports of unexpected system shutdowns (like those reported in the LAPTOP piece above) that require a battery pull to resolve. We're hearing that you can also patch this up by holding down the power button and toggling the ringer switch three times, but your mileage may vary. If we had to guess, this'll be fixed up with a firmware update at some point, which really drives home the value of OTA capability.
Text fields in the web browser don't seem to support symbols that aren't on the keyboard (that is, symbols you need to hold down "Sym" to access). We've independently verified this one, and it's nasty -- it'll be particularly bad once the phone launches internationally, so we'd also expect this to be patched sooner rather than later.

If you've noticed anything else, drop us a line in comments -- we think Palm and Sprint are both motivated to make this launch a smooth one, and something tells us their ears are firmly planted to the ground right now.

[Thanks to everyone who sent these in]

Epic Android bug interprets your typing as system commands

by Chris Ziegler posted Nov 8th 2008 @ 8:42PM

The philosophy goes something like this: the great thing about Linux is that it's secure, and the great thing about open-source software is that it's thoroughly and constantly vetted for robustness. So to that end, Android should be pretty rock solid, right? Perhaps, but the overwhelming enormity of this particular bug definitely gives us pause. It turns out that G1 firmware revisions RC29 and earlier literally interpret everything you type as command-line operations, so if you happen across a legit command, it's going to get executed -- with superuser permissions, no less. No, seriously. Just go to the messaging app, the browser, or anywhere else a text box is convenient, type "reboot," press the enter key, and watch magic happen. We've tested this on two G1s, both with RC29 firmware, and have gotten this to consistently work on one of the two, so your mileage may vary -- but either way, this needed to get patched on the double. Fortunately, Google's been quick about it, rolling a fix into the RC30 build that's being rapidly pushed to users as we speak, but man... how did that get through?

RIM finds security flaw in BlackBerry Enterprise Server

by Sean Cooper posted Jul 27th 2008 @ 11:18PM

RIM has issued a security warning to BES admins about a problem with the BlackBerry Attachment Service and PDF files. The flaw apparently allows would-be hackers to execute malicious code with a specially crafted PDF file. The Waterloo messaging behemoth has listed BES versions 4.1 SP 3 through 4.1 SP5, and BlackBerry Unite! as affected and rated the severity as 9 out of a possible 10 -- with 10 being the highest level of fail. Thankfully a workaround is available on RIM's site involving disabling the processing of PDF files until RIM can issue a fix for the misery. Hit the read link for the dirty details.

[Via PCWorld]

Driver trouble makes angry mobile owners rush castle HTC with burning torches

by Sean Cooper posted Jan 19th 2008 @ 6:43PM

We're seeing a serious flow of tips from people upset with supposed performance issues on a good pile of HTC's newest sets. Handsets like the HTC TyTN II, Touch Dual, Touch Cruise, Wings, Titan, Vogue, Libra, and Iris are all apparently affected by underperforming video drivers which in turn slow the device significantly. The list -- and length -- of threads covering this is snow-balling at the well known XDA-Developers forum pages, as is talk of class-action suits. A site has now been set up called HTCClassAction to help people sort through all the buzz and get the nitty gritty details, so hit the read link if you're inspired to learn more. Of course we'll hopefully hear something official from HTC on this in the near term and will be sure to fill you in as we do.

[Thanks to everyone who sent this in]

Sprint Rumor actually pulled because of lingering issues, unreleased fix?

by Nilay Patel posted Jan 6th 2008 @ 1:38AM

So even though Sprint has come out and officially said the reason for the LG Rumor's disappearance is the "high sales volume" of the handset, it doesn't look like anyone's really buying it -- and there's still a lot of credible chatter out there that firmware-resetting keystroke bug is indeed the real reason the Rumor went MIA. Although there's apparently a fix on deck, Sprint still hasn't decided on when to release it to existing customers -- we're assuming that its inevitable popularity is causing fits at Sprint HQ.

Update: PhoneNews is reporting that the update is now available to Sprint Rumor owners under Menu > Settings > Others > Update. It'll be interesting to see how this affects the Rumors availability.

iPhone 1.1.1 "bug" unleashes music over Bluetooth

by Paul Miller posted Sep 29th 2007 @ 5:20PM

The iPhone 1.1.1 update has a hidden little surprise for y'all: Bluetooth audio streaming is now available off of your iPhone for whatever you darn please, meaning you can finally listen to music from the phone wirelessly. Oddly enough, this "function" has been unleashed by a Visual Voicemail bug that leaves Bluetooth audio on even after you've left the Voicemail interface. Of course, it's only mono audio, and the audio keeps playing out of your built-in speaker -- if you plug in headphones to cut off the speaker you'll lose Bluetooth streaming as well -- but it's nice to see Apple forking over some "should have been there in the first place" functionality accidentally to go along with all that stuff of the same ilk 1.1.1 took away from us.

Safari exploit gives hackers full control over iPhones and possibly PCs and Macs

by Thomas Ricker posted Jul 23rd 2007 @ 3:05AM

Oops, researchers just unveiled a pretty serious security vulnerability in the iPhone. More specifically, it's Apple's Safari web browser which exhibits the vulnerability. Researchers at Independent Security Evaluators have used the vulnerability to take malicious control of the iPhone from rogue websites loaded with the exploit. Once in, researchers have full administrative access over the phone allowing them to listen in on room audio or snatch the SMS log, address book, call history, email passwords and more -- we're talking full access to your phone. Researchers note that the only way to stay safe is to check those URLs and only visit sites that you trust (which isn't very reassuring) and "may or may not be exploitable" from Mac and PC versions of Safari -- the same vulnerability exists only they haven't written the proof-of-concept exploit to test it yet. Apple has been notified of the vulnerability and a proposed fix with full public disclosure coming at the BlackHat conference on August 2nd. You listening InfoSec Sellout? That's how you report a bug. Check the exploit in video form after the break.

[Via MacRumors]

Continue reading Safari exploit gives hackers full control over iPhones and possibly PCs and Macs

First batch of Toshiba G900s plagued with issues?

by Chris Ziegler posted Jul 14th 2007 @ 1:31PM

As smartphones become ever more complex and powerful, simple math dictates that the incidence of severe software issues is going to go up. Sad as it is, that's to be expected, and we can't really recall the last time we extensively used a smartphone -- regardless of brand or platform -- that didn't exhibit some bugs. That being said, when a phone won't frickin' come out of standby, you'd think they'd be able to catch that before shipping. Many owners of Toshiba's ultra-powerful G900 Windows Mobile 6 Professional handset seem to be reporting a hodgepodge of problems that are necessitating returns, chief among them being that once the phone goes to sleep, it doesn't want to wake up until a reset is performed. Toshiba's apparently promising a fix in the next few weeks, but for folks trying to make this beauty their primary mobile, that's little consolation for the moment.

[Thanks, Gudmundur]

HTC patches P3300's microSD issues

by Chris Ziegler posted May 12th 2007 @ 12:03PM

Apparently, HTC's P3300 Artemis microSD-handling capabilities fall well short of its ability to look good (yeah, it's hot -- this one definitely left a lasting impression on us when we saw it at last year's Fall CTIA). Users have been reporting a variety of issues with the P3300's slot, ranging from an inability to correctly read directory structures on expansion cards all the way to data corruption. Help's on the way, though, in the form of a freshly-released update straight from HTC itself that should clear those pesky microSD woes right up. If you're into trackballs, navigation, and a Palm V-esque form factor, you probably own one of these things, so go patch 'er up, will ya?

[Via the::unwired]

Korean carriers to offer anti-eavesdropping service

by Darren Murph posted Jan 16th 2007 @ 3:35PM

Just as Japan announces that it'll pretty much have an eye on every single cellphone user in the nation, Korea is going against the grain somewhat by offering up an anti-eavesdropping service on users' handsets. SK Telecom, KTF, and LG Telecom will all be offering private long code service, a digital encryption system to keep voice snoopers at bay, and will dub the service "Voice Private." Marketed primarily towards people of utmost importance, such as politicians, public officials, journalists (ahem), and CEOs, the luxury will purportedly operate on any mobile phone and will cost between W1,500 ($1.60) and W2,000 ($2.13). Interestingly, it wasn't noted if these fees were a monthly charge (less likely) or a per-call exaction (more likely), but regardless, the service should go live just as soon as the Ministry of Information and Communication approves it.

BlackBerry Pearl won't ring in your pocket

by Chris Ziegler posted Sep 17th 2006 @ 12:53PM

Anyone who's had the good fortune of seeing a Pearl in the flesh knows that it's one extraordinarily good looking phone, particularly by BlackBerry standards. Unfortunately, where we come from, phones that don't ring are called "paperweights" -- which is exactly what the Pearl becomes when the trackball gets nudged. You know, like if it's in your pocket, or your purse, or pretty much anywhere besides a stationary counter top. As it turns out, when the phone rings, the handset immediately silences the ringer with even the slightest movement of the trackball, regardless of whether keylock is enabled. While we do appreciate the Pearl taking the initiative for us and ignoring phone calls so we don't have to, there is an occasional situation where we like to make the decision ourselves, and until RIM issues a fix users simply don't have that option. Strangely, two Engadget editors patiently attempted to explain the issue to a RIM representative this week at CTIA for several minutes without success; we think the first step to RIM issuing a fix would be for the company to understand the problem, so we could be in for a bit of a wait. Maybe the words we were using were too big?

Treo 700w daylight savings time bug?

by Ryan Block posted Apr 1st 2006 @ 1:56PM

Nope, this ain't no April Fool's joke, people, this is the real deal: when everybody's clocks skip forward an hour for Daylight Savings Time this year (at 2:00AM on the first Sunday in April -- i.e. early tomorrow morning), your Treo 700w's calendar appointments may not. Like putting your WinMo phone in travel mode to another time zone, apparently a bug in the 700w may cause your appointments to time-shift back one hour -- so your noon appointment will stay put, so to speak, at 11:00AM. Palm's got some workarounds on their site so you shouldn't be too put out, so make sure you sort it out soon before Monday morning when you're an hour early to all your meetings. Of course, this wouldn't be a problem if America would just get rid of DST -- Arizona, Hawaii, and portions of Indiana excepted, of course.

[Via TreoCentral]