Download the
Tom's Guide App from the AppsStore
News and trends on internet
/ mobile / "sound & picture" / IT
Yes No

Verizon Accused of Remotely Controlling Droid

- By - Source : Tom's Guide US

Verizon was accused of secretly accessing Motorola's Droid to quietly fix the auto-focusing bug.

Recently Verizon was accused of remote-controlling Motorola's new Droid smartphone. Evidently, a bug cropped up concerning the built-in camera's auto-focus. However the problem mysteriously resolved itself in thousands of phones, leading many to believe that Verizon snuck in through the back door and secretly corrected the issue.

But apparently that wasn't the case at all. As Wired points out, the root of the problem is much more stranger than Verizon cleaning up its mess behind the scenes. In fact, the overall problem was a definite bug, but on behalf of the Android OS. Android developer Dan Morrill sent in an explanation as to what went afoul, saying that the issue was date-related.

"There's a rounding-error bug in the camera driver's auto-focus routine (which uses a timestamp) that causes auto-focus to behave poorly on a 24.5-day cycle," he told Engadget. "That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again."

He also added that the 17th is the start of a new "works correctly" cycle, allowing the camera to work correctly until the cycle ends. Morrill said that a permanent fix is in the works. The bug itself is quite unusual, however Wired told curious Droid owners to turn the clock back a few days if they want to bathe in the glory of a non-focusing camera.

Get more tech and gaming news by hitting me up on Twitter here.

Share:
25
Comments
X

Comments

bdcrlsn 11/20/2009 12:05 PM
Hide
-14+

I'm still wondering why an "auto-focus routine" would have the time in it...

ikefu 11/20/2009 12:05 PM
Hide
-20+

They have to fix the auto-focus. The government spies who watch you through your phones camera don't like watching blurry video...

/tinfoilhat

michaelzehr 11/20/2009 12:27 PM
Hide
-5+

This sounds almost as good as the old 'phase of the moon bug' in a LISP program at MIT. I doubt if the auto-focus has the time in it, but rather a timestamp prepared to save with the photo overruns a buffer and stomps on something the auto-focus routine needs.

Note that 24.5 days is very close to 2^^31 milliseconds. Probably a signed/unsigned math bug causing the problem.
(Could also be an exception trap throwing off RT scheduling of the auto-focus, but that's pure speculation since I don't know much about embedded phone programming.)

maestintaolius 11/20/2009 12:39 PM
Hide
-0+

I can't help if its a RNG that uses the timestamp based seed for the autofocus PID loop starting point. Granted, I'm looking at is as a ChemE and not an EE, so it could lots of things. I remember that being an issue years ago on KOTOR I on the original xbox, if your system date was a date was a day that the game actually didn't exist yet (like Jan 1, 1990 or whatever) the loot generator would cause the system to crash when you opened up a box.

deadlockedworld 11/20/2009 12:57 PM
Hide
-8+

"more stranger" is not proper English. Perhaps Tom's needs an editor.

m3kt3k 11/20/2009 1:50 AM
Show
anamaniac 11/20/2009 6:57 AM
Hide
--3+

They fixed a problem without telling you, the issue is?

godnodog 11/20/2009 11:09 AM
Hide
-1+

Now this is weird, seriously, can any1 please explain why an auto-focus need to be date related? There is no need for a camera to have access to time and date, you may need auto-shoot, but that would only need an clock counter (not sure about how to call it) not a full clock and calendar LOL

I may be wrong, but this is like if the microphone to work properly the time and date of the phone need to be correct.

Sorry for my english

theuerkorn 11/20/2009 1:11 PM
Hide
-0+

"...the problem is much more stranger than..."

as strange as the writing?

Anonymous 11/20/2009 1:18 PM
Hide
-0+

Photo files have a date and time stamp built into the exif file. It also can be used to sync the photo with a gps location based on the time the photo was taken.

sunflier 11/20/2009 1:45 PM
Hide
-3+

Quote :Recently Verizon
was accused of remote-controlling Motorola's new Droid smartphonehumans into thinking the Droid smartphone is fixed when in reality its not
.


There, fixed it.

cushgod 11/20/2009 2:05 PM
Hide
-1+

LOL sunflier!!

Regulas 11/20/2009 2:53 PM
Hide
-0+

ikefu :
They have to fix the auto-focus. The government spies who watch you through your phones camera don't like watching blurry video.../tinfoilhat


Funny but something like that coming from the FEDS would not surprise me in the least.

zak_mckraken 11/20/2009 3:09 PM
Hide
-0+

Droid, the first phone with PMS.

That explanation is BS. I really can't figure why an auto-focus feature would rely on a timestamp!

mirkos 11/20/2009 3:49 PM
Hide
-0+

"There's a rounding-error bug in the camera driver's auto-focus routine (which uses a timestamp) that causes auto-focus to behave poorly on a 24.5-day cycle,"

I don't think that this is accurate. the true problem was:
"asynchronous inode failure" or "parallel processors running perpendicular" or anything else you can figure out from the Excuse Board

But clearly Verizon DIDN'T snuck in through the back door and secretly corrected the issue.

hellwig 11/20/2009 4:52 PM
Hide
-1+

I think michaelzehr hit it on the head. They probably use the timestamp just as a randomizer for something, and unfortunately when that timestamp has the high-bit set (or when it doesn't) it screws with their calculations.

Honis 11/20/2009 5:50 PM
Hide
-1+

When you have an embedded piece of software it is more efficient to call current time and compare it the the previous time that section of code was accessed. The alternative is asking the OS to keep track of when you should access which isn't consistent or efficient.

They do this for any number of reasons. The biggest reason is they don't want the auto focus to auto focus every time the code loops (why auto focus 1000 times a second and bog down the interface when 2 times a second in more than enough and allows for more time for gui processing).

How you can screw something up like that and get a negative number ever month for a month is beyond me. Miss placed if/else statement?

counselmancl 11/20/2009 6:13 PM
Hide
-0+

We need a cyber bill of rights to combat this intrusiveness. Just because I own a product, that does not give the manufacturer or service provider the right to surreptitiously access it in any way, form or fashion. All interactions should be visible and approved. Burying the authorization somewhere in an obscure twenty page license agreement doesn’t count.

The more we allow ourselves to become comfortable with such actions the less secure we will be in our possessions or privacy. As the world moves towards a more data dominated society we can no longer consider these actions anything less than a provocation. Don’t stand for it!!! This leads nowhere good.

Platypus 11/20/2009 6:25 PM
Hide
-0+

counselmancl :
We need a cyber bill of rights to combat this intrusiveness. Just because I own a product, that does not give the manufacturer or service provider the right to surreptitiously access it in any way, form or fashion. All interactions should be visible and approved. Burying the authorization somewhere in an obscure twenty page license agreement doesn’t count. The more we allow ourselves to become comfortable with such actions the less secure we will be in our possessions or privacy. As the world moves towards a more data dominated society we can no longer consider these actions anything less than a provocation. Don’t stand for it!!! This leads nowhere good.

You should really try to read the article first and not just post your feelings based on the title alone. There was no intrusion. It was some ridiculously inferior coding with timestamps.

jtt283 11/20/2009 7:44 PM
Hide
-0+

Counselmancl has a very valid point, it just didn't apply here.
Anyway, maybe the autofocus routine is tied to whatever puts the date and time on your shots. Maybe sometimes it looks at those pixels when it shouldn't.

counselmancl 11/20/2009 7:55 PM
Hide
-0+

Platypus :
You should really try to read the article first and not just post your feelings based on the title alone. There was no intrusion. It was some ridiculously inferior coding with timestamps.



Fixing code is a very minor action yes, accessing a personally owned device without consent to do it is not. Just because we are dealing with 1’s and 0’s doesn’t mean it wasn’t an intrusion into personal property.

Where does it end? A line must be drawn.

counselmancl 11/20/2009 8:01 PM
Hide
-0+

But your right, I read the article wrong. I thought they did access the phones, but I know I have read that companies have done this in the past. Looking for the article...

necronic 11/20/2009 8:13 PM
Hide
-0+

Good lord Tom, maybe next time you can not use a sensationalist title? In the article itself you give the official (and perfectly reasonable) explanation for the resolution of the error, and yet youre title makes it seem like they actually did the backdoor access.

That is some seriously irresponsible journalism. FFS, just look at these comments, you have a lot of people here talking about privacy issues which is exactly what DIDN'T happen.

Unless of course you don't believe their explanation, but if that's the case go ahead and say it, don't imply it in such a sensationalist manner.

AtuBrian 11/20/2009 11:31 PM
Hide
-0+

vorless :
WHAT THE FUCK


did u even read the thread

sailfish 11/21/2009 5:35 AM
Hide
-0+

Sounds like Auto-Focus Hocus-Pocus to me.