
Originally Posted by
catchmyjetta
Did you guys see this in the engadget responses to their article. Interesting...
AlexL @ Nov 17th 2009 9:13AM
Here's a crazy theory. What if there was no silent fix pushed out, but rather the autofocus code was broken because specific states of the clock was interfering with the operation of the autofocus code? So when a certain time/date passed, the issue no longer exists and the code became functional by itself. Sounds crazy I know, but not without precedent (something like this happened to first generation Zunes). Maybe someone can try setting the date to an earlier one and see if the autofocus magically breaks again.
Reply
Neutraltravisw @ Nov 17th 2009 11:15AM
Just changed the date back to 11/11 and got red boxes. Went back to 11/17 and got green boxes again. Could be something to it.
NeutralMatt Cutts @ Nov 17th 2009 11:24AM
AlexL, is there an easy way to set the time or date or the Droid? I don't have one myself.
NeutralDan Morrill @ Nov 17th 2009 11:26AM
Yes, this is exactly what is happening.
There's a rounding-error bug in the camera driver's autofocus routine (which uses a timestamp) that causes autofocus to behave poorly on a 24.5-day cycle. That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again.
The 17th is the start of a new "works correctly" cycle, so the devices will be fine for a while. A permanent fix is in the works.
Bookmarks