• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Camera Fixed..!

I have noticed my camera so much more responsive as well! Love it!! Thank you Google/Moto/Verizon! :D No lens cleaning here! :p
 
shugknight said:
tiny-violin1.jpg
Click to expand...
OMG a GIANT playing a violin!
 
Vance said:
I will say that if Moto wants to come into my phone without my knowledge and do things to it that they believe will enhance my experience . . .

Go right ahead!
Click to expand...
What happens if they decide later that rooting phones is a detriment to the experience they think users should be having and decide to brick rooted phones or to disable the ability to do so?

Weooooooo. Having a choice is a good thing guys. Amazing I know.
 
verbal41 said:
Google's Dan 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.
Click to expand...

I can somewhat verify the validity of this. If you set your phones date/clock to a few days prior, the issues resurface.

Either way, good news to know that the problem is software related and it should be fine to take pictures for the next 24 days or so. That should time perfectly with a December 11th software update.

No need for conspiracy theories. :-)
 
For Christ's sake, asking for notification at the very least over what updates are incoming is not a conspiracy theory.
 
OK everyone, it has been verified that it wasn't a silent OTA, just a bug in the camera driver's autofocus which uses a timestamp. Now we can wait until the dec 11th OTA to have a permanent fix, and I'm sure we will have a choice on whether or not we want to accept it.

KEEP YOUR POSTS ON TOPIC AND NO MORE ARGUING PLEASE.
 
Nycdroid, nice to see it wasn't an auto update though that seems like a odd code issue to have. But then I really know nothing about coding. At least I can use my camera until the real fix is available.

Did they put out information out about this before we all noticed our cameras working? Like don't be surprised if your cameras start working on the 17th or something along those lines?
 
Flowah said:
What happens if they decide later that rooting phones is a detriment to the experience they think users should be having and decide to brick rooted phones or to disable the ability to do so?

Weooooooo. Having a choice is a good thing guys. Amazing I know.
Click to expand...

I understand the issue, but I tend to leave things stock and prefer not to have to mess under the hood. So, since I am buying into the experience they are selling, I would just as soon they make that experience as good as possible, with as little effort on my part as possible.

If I was a tinkerer I would be a bit more concerned and I do understand, but my impression is that Google is dedicated to open source, and NOT doing things like cracking down on modders, etc.
 
Flowah said:
For Christ's sake, asking for notification at the very least over what updates are incoming is not a conspiracy theory.
Click to expand...

Obviously sarcasm wasn't conveyed well via the smiley. Take a breath for a second before typing, it will help. :-)

When we get the official update in December, there will be a notification.
 
I can see that things have improved too, or perhaps I just haven't experimented with it properly. Indoor shots with incandescent lighting are still somewhat poor, you might have to turn on a lot of lights or just not take pictures in small rooms with dark colored walls =P

Here are some examples though of the sunny outdoors!

2009-11-17124003.jpg


2009-11-17124022.jpg


The two outdoor photos are really sharp. But compared to the two indoors (both with lights on and off)

2009-11-17124126.jpg


2009-11-17124145.jpg


They still leave something to be desired. This was all done with focus/white balance/scene in auto mode.
 
This may be an odd question but has anyone else noticed increased battery life? I don't see how it could be related to the camera bug but I seem to be getting much better battery life today.
 
My phone is also taking pictures better. I wondered why my phone woke up randomly last night. I had turned the screen off and when I woke up it was one again. Pretty cool
 
I have NOT installed Shopsavvy at all. My camera now works like a 500 dollar phone camera should be working.

I love it. I will take a silent update anytime if it improves the functionality.
 
Yes I too am seeing much better battery life. My phone has been off the charger since last night around 10 and it is 12 hrs later and I am at 70% remaining and I ran Pandora for about 20 minutes today and e-mail pushing, took pics of many barcodes to show workers that the camera works, etc... Very cool.
 
This was posted on engadet by someone that apparently works on Android for Google.

Dan 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.
 
Mine seems to be focusing, but I can't stand the picture quality. Everything has a glow to it. Very annoying. It's like the whitest parts of the picture are blooming and smearing. Looks like crap.
 
verbal41 said:
Google's Dan 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.
Click to expand...

My head just exploded. Maybe we need a thread on what other forums to keep an eye on before his board turns into Area 51.
 
Hah...I was right, no SW update, the bug is date-related...from HoFo/Engadget:

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.
Click to expand...

But oddly, still doesn't explain why some were working before the date change...
 
Ok, so I don't know if this is proof that it is a date thing and not a camera fix thing.. I just changed my date on my phone to 11/11 and I get the red bars when taking pictures. I then change it back to today and now I get the green bars... Very odd.. But hey even if it is fixed for the next 24.5 days then we will be at the 24th day on the 11th of December just in time for their OTA push. So maybe the launch was timed just right so people would only experience the issue for 10 days, it would then be fixed because of this issue, then that gives them enough time to push out the fix on December 11th just as it is going to switch back. Very nice Verizon if this is true..
 
You must log in or register to reply here.
Back
Top Bottom