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

HUGE Camera Bug on low battery tested on 2 different droids

Does your droid experience this issue?

  • Yes!

    Votes: 5 20.0%
  • No

    Votes: 20 80.0%

  • Total voters
    25
lol i never knew writing HUGE would annoy so many picky people that take serious offense to having that adjective placed for something that i find to be a HUGE problem... none of the flamers are indicating whether this happens on their droid or not

I don't intend to test mine because I never allow any of my phones to get down to 15% battery life left. I tried to explain the somewhat technical reason why this behavior isn't surprising. My second post was to make you understand why your making such a big deal out of this is frankly childish. I gave you an answer why this seems quite normal behavior to me. Take it or leave it.
 
I didn't want to let my battery drain down to the 10% or 15% level so I took the battery out and was able to confirm that the camera would not take a photo. Can anyone else confirm the camera does not work if their battery is out?
 
I didn't want to let my battery drain down to the 10% or 15% level so I took the battery out and was able to confirm that the camera would not take a photo. Can anyone else confirm the camera does not work if their battery is out?

Weird it doesnt work! when i try to power it up i get a sign that says "Death to all Trolls"
 
I didn't want to let my battery drain down to the 10% or 15% level so I took the battery out and was able to confirm that the camera would not take a photo. Can anyone else confirm the camera does not work if their battery is out?

you're right... this is HUGE! :)
 
Good golly, whats everyone's problem, lighten up a little, cant really understand whats up your droid holes. This is a forum for discussion, is it not?

On topic: I discovered the incremental chopping off of the picture as I continued to take pictures. Just going to have to live with it I suppose, oh well, still love the droid though.

And I love letting my battery get down to 1%, makes me feel like I am skydiving into a time warp of adrenaline and mermaids. Might even check my email on wifi rite at the cusp of oblivion.
 
Good golly, whats everyone's problem, lighten up a little, cant really understand whats up your droid holes. This is a forum for discussion, is it not?

On topic: I discovered the incremental chopping off of the picture as I continued to take pictures. Just going to have to live with it I suppose, oh well, still love the droid though.

And I love letting my battery get down to 1%, makes me feel like I am skydiving into a time warp of adrenaline and mermaids. Might even check my email on wifi rite at the cusp of oblivion.

Yea tell me bout it, anywho what percent was your battery at when you noticed camera issue?
 
It was 15% when I tried it out and got the incremental chopping, got down to 10% while messing around. Then gave up on it. I don't think its a defect or a "feature", battery just cant pump enough juice to the camera. I bet everyone's droid does the same, seems were the only ones who care about it though, lol.
 
It was 15% when I tried it out and got the incremental chopping, got down to 10% while messing around. Then gave up on it. I don't think its a defect or a "feature", battery just cant pump enough juice to the camera. I bet everyone's droid does the same, seems were the only ones who care about it though, lol.

I think Luke Skywalker once replied ... "I care".

-Just messing with you guys... I think the majority of people understand that wierd things happen when electronics get low on power.
 
My guess is that Motorola considers 15% the "safety" point and starts dedicating less resources to "non-essential" functionality. In that case unless they add a convenience setting to disable and allow it to run 100% til battery is dead you wont see a fix.

It's a phone so obviously Radio has priority. Then data most likely will work as well since it's the 2nd priority in general (IMHO). The camera is most likely considered a convenience device, and while sure some use it a LOT it is going to be at the bottom of the list.

So as the battery power gets lower and lower it gets less resources assigned to it to maximize the main feature... the fact that it's a phone, and a data oriented one at that.

Annoying if you need it? Sure
A bug? Doubtful as many other phones do similar things with their design to keep their key features working as long as possible.

Sure I understand your frustration, but on the flip side... as you can see by these posts you're in the minority of users who think the camera is "key" over radio longevity in low battery situations.
 
Let us enumerate all the events that happen during a photo in this phone (applies to all other phones and digital cameras):

1. Screen has to be on.
2. Camera's CCD has to be powered up and engaged.
3. Data from the camera's CCD is processed by the CPU, transferred to the display controller, processed by the display controller, and output to the display. This occurs continuously while you the camera mode is engaged.
4. After you press the shutter button, the focusing motor engages. The CPU must now process a sequence of images acquired during the focusing algorithm and produce one with the highest edge definitions. The camera lens is moving during this time.
5. After focus has been achieved and confirmed, the flash is engaged (assuming low light conditions). The CPU processed light information to determine when to cut off flash power (this happens when the correct exposure has been achieved).
6. CPU processes the CCD data set using the preset file size, color profile, etc. It packages the finalized data set in a .jpeg file, and sends it to the flash memory controller. RAM is also actuvely engaged during this step to handle the intermediate data storage duties.
7. The flash memory controller sequentially writes the data into the flash memory card.

ALL of these events require power way beyond standby levels. If one of the devices involved does not receive sufficient current and/or voltage to complete the task, it shuts down immediately. A memory controller cannot resume a write operation if it has been interrupted, it is a fairly simple device. Thus, any interruption in the sequence due to low power levels will cause the image to be incomplete. The .jpeg file header specifies the image size corresponding to the camera resolution setting; the software that displays the image processes the missing spatial data as black pixels (pixels with no color/intensity information). This happens everywhere. If I am ever stupid enough to pull memory card out of my DSLR or suddenly interrupt the power connection, the same exact thing happens (file with part data, part black area).

The operating system may include algorithms that reserve power for crucial low-level hardware tasks such as processing radio signals or handling system tasks (thus, your radio works). Taking a photo requires a lot more power than launching and running a program, so the camera application is ver understandable left out in the cold when the power levels are low.

This is not an OMFG GIGANTURISTILICIOUS BUG, it's a natural occurrence in the camera-processor-storage chain under insufficient power conditions. Your obsession with being able to produce an image under low power and low light conditions is downright silly. You wouldn't expect your car to be able to reliably play radio at full volume, engage the windshield wipers, power the high beams, AND start when the battery is almost dead. I do not understand why you would expect your cell phone to do the equivalent. So stop snooping around night clubs with a dead phone, bring a charger along, and cheer up :) We are not here to insult or demean your concern. You are simply blowing it out of proportion to the point of being silly.
 
i am simply asking if this is a common problem to droids or not and according to the poll 14 say no and 1 says yes, is it possible that this is a hardware defect, perhaps a bad battery that is not allowing it to do all those things you wrote?? If it is then it is my concern to see if this might be a possible defect in my device. I understand now the theory of why this is occuring... im not saying you guys are wrong.. i just want to know if its an issue that all droid users have to deal with. I dont know how many times i have to repeat this, but i just want input from you guys if you guys experience the same thing and so far only ONE person has came through.. if you dont want to drain your battery at this level to test it then dont... im only asking people who are willing to check this what appears to me as a "bug". I appreciate filling me in on reasons why this is happening.
 
It is extremely unlikely to be a hardware problem. When a battery discharges, its voltage output drops. This happens with all batteries, no exceptions. Voltage does not suddenly drop off when a battery is fully discharged, it decays gradually with use within a charge cycle (sure, there is a large dropoff at the very end, but the voltage doesn't hold steady before then, either). Frankly, this is how a battery charge level is measured. So the problem with electronics is that the circuits are finely tuned to work within an acceptable range of voltages supplied by the battery. When the battery voltage gets below the bottom threshold, there is absolutely no guarantee all circuits would work to their specifications. In order to work for as long as possible, phones are designed to limit certain services in order to decrease the overall power draw of the system. Some phones (like BlackBerry and Windows Mobile phones) shut off the radio in order for the phone to work longer. Like we speculate here, Motorola and/or Google may have implemented a hierarchy of system processes that get priority "funding" when the battery levels are very low. It is wrong to treat the phone as a system that is either fully functional or doesn't power off at all; rather, certain functions are sacrificed in order to make the phone operate a little while longer.
 
WHAT YOU SAY:
My guess is that Motorola considers 15% the "safety" point and starts dedicating less resources to "non-essential" functionality.

WHAT I HEAR:
Capt Droid: I need full power to the camera, Tassy!
Tassadar: I'm giving her all she's got cap'n!
Capt. Droid: Reroute energy from non-essential funtions. I need that flash working now.
:D
 
i am simply asking if this is a common problem to droids or not and according to the poll 14 say no and 1 says yes, is it possible that this is a hardware defect, perhaps a bad battery that is not allowing it to do all those things you wrote?? If it is then it is my concern to see if this might be a possible defect in my device. I understand now the theory of why this is occuring... im not saying you guys are wrong.. i just want to know if its an issue that all droid users have to deal with. I dont know how many times i have to repeat this, but i just want input from you guys if you guys experience the same thing and so far only ONE person has came through.. if you dont want to drain your battery at this level to test it then dont... im only asking people who are willing to check this what appears to me as a "bug". I appreciate filling me in on reasons why this is happening.

The reason why you're getting smashed is because people have been telling you it's NOT a bug but you keep insisting that it is. Also the title is also a bit sensationalist.

And I tested, did not get chopping but I did not drain my battery all the way down. Just tried a few pictures when I saw the 15% notice.
 
And I tested, did not get chopping but I did not drain my battery all the way down. Just tried a few pictures when I saw the 15% notice.

Seems like it may just be unique to a few phones then? Did you try it in complete darkness? I just had it happen to me today at 40% battery life once, then it went away...
 
took it to best buy, swapped my battery into one of their droids took pictures at the same battery level where i was experiencing cut off issues on my old droid and NO cutoffs... even at red blinking LED whatta ya know, it is hardware defect... thanks
 
Hey, so I got the OTA update last night and tested it again. I don't have the issue anymore, I took pictures with flash and some videos with the battery all the way down to 5% and did not experience any chopping. Say the least I'm very happy about that. My model is 42/09. I'm going to be testing it again, to make sure, although now I have a seriously improved battery life after the update so it will take a while to drain it. :)
 
Back
Top Bottom