camera is not responsive after taking a picture

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Take a picture
2. Play with setting, example: focus change to macro and vise versa
3. Take another picture, this time the phone wont even respond to screen touch 
or camera button

What is the expected output? What do you see instead?
Camera can shot another picture

What version of the product are you using?
11.15

Original issue reported on code.google.com by superbiji on 16 Nov 2010 at 12:20

[GoogleCodeExporter]

Original comment by kabal...@gmail.com on 16 Nov 2010 at 11:51

• Added labels: Version-0.04
• Removed labels: Version-0.03

[GoogleCodeExporter]

+1 on this one. The camera (and the phone) is very slow after taking a picture. 
Picture size is appr. 1 MB each, so perhaps quality settings are to high and 
thus system gets stuck?

Also, there are no options for reducing quality and/or resolution (e.g. 2 
MPixel instead of 5).

Original comment by doc.pa...@gmail.com on 18 Nov 2010 at 10:45

[GoogleCodeExporter]

The quality setting is there - in the scroll menu of the topmost button...

Original comment by kabal...@gmail.com on 18 Nov 2010 at 10:59

[GoogleCodeExporter]

OMFG, THAT WAS A SCROLL MENU ?!?

SORRYYYY! (^___^)

Indeed the slowdown was caused by high quality pictures (Standard setting: 5 
MPixel + extra fine jpg). Setting the picture quality to 2 MPixel + fine jpg 
solved it. Camera is very responsive now and does NOT freeze the system at all.

BR & thnx!!!

Original comment by doc.pa...@gmail.com on 18 Nov 2010 at 6:08

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry... have to report again, the camera make me mad
after taking one picture, it start unresponsive to touch, and also i can see 
lots of:

I/ActivityManager( 1690): Low Memory: No more background processes.
and anr.txt dumping

this issue happened randomly

Original comment by superbiji on 27 Nov 2010 at 1:52

[GoogleCodeExporter]

I also have the problem. Moreover, most of the time, the camera take the 
picture but save only a black image... (sometime it does'nt even save it).

Original comment by clement....@aef.info on 6 Dec 2010 at 1:17

[GoogleCodeExporter]

Well, if you've set the launcher to be memory persistent, so it can't be killed 
no matter what in order to free the memory which is urgently needed for the 
foreground application, then you can't be surprised that the memory suffering 
app will crash...

Original comment by kabal...@gmail.com on 6 Dec 2010 at 3:53

[GoogleCodeExporter]

actually i have disabled memory persistance for launcher. and also using 
DSPManager, Life wallpaper, K9 Mail in background. i think the camera app is 
too big for our milestone. Or wait until there's a solution for compcache 
(compressed ram) or swap memory..

Original comment by superbiji on 7 Dec 2010 at 3:54

[GoogleCodeExporter]

I've got the problem too. But in my case its even worse. The phone doesn't only 
reboot!
It reboots with a damaged SD-card notice. 

Original comment by addi...@gmail.com on 22 Dec 2010 at 3:03

[GoogleCodeExporter]

Same here. Usually i get ok 1 picture but then i have to take battery out if it 
doesnt reboot.

Original comment by auremoni...@gmail.com on 2 Jan 2011 at 11:18

[GoogleCodeExporter]

Issue 288 has been merged into this issue.

Original comment by kabal...@gmail.com on 4 Jan 2011 at 10:43

[GoogleCodeExporter]

did you guys who still experience the not responsive issue able to take video 
successfully?

my case is the camera work fine on video recording, but when come to photo, 
once i click on the shutter(touch or physical button). it will hang the screen 
and go to reboot automatically...

Original comment by kakit....@gmail.com on 5 Jan 2011 at 3:01

[GoogleCodeExporter]

I found a solution for that issue:
Increase your vsels for all steps by 2. If it isn't enough add an additional 
value of 2 (repeat this step if it still isn't working properly).

Original comment by addi...@gmail.com on 5 Jan 2011 at 3:09

[GoogleCodeExporter]

Actually, for me - with CM 6.1.2 - decreasing vsel to 52 (for 900MHz, leaving 
it the same for all others) improved the behaviour of the camera considerably - 
I couldn't crash it now.

Original comment by gus...@gmail.com on 5 Jan 2011 at 4:55

[GoogleCodeExporter]

newbies question.. how can i set vsels? need to use shell command or something 
like that? or i can set it at the open recovery?

Original comment by kakit....@gmail.com on 6 Jan 2011 at 2:56

[GoogleCodeExporter]

I don't know if there's any better way to do it, but I edit the overclocking 
script:
1. Use a root capable file manager
2. remount /etc for read-write
3. Edit /etc/init.d/10overclock - if you don't understand what it says, consult 
your nearest search engine ;-)

Original comment by gus...@gmail.com on 7 Jan 2011 at 9:27

[GoogleCodeExporter]

This is with a decently fresh install of 0.07, no overclock, no themes, but no 
factory reset (coming from 0.06 with HONO's theme added, so some stuff was 
still themed but not most of it).

1. Start camera
2. Take 3 or 4 pictures ( a litle slow between pictures, but not too bad)
3. try to switch to camcorder
4. FC

"D/CameraHal( 3876): Wait for buffers to free up" appears about a bazillion 
times.

Original comment by alanpa...@gmail.com on 2 Feb 2011 at 4:14

Attachments:

• [Camera logcat.txt](https://storage.googleapis.com/google-code-attachments/cyanogenmod4milestone/issue-221/comment-18/Camera logcat.txt)

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Low memory: Do you have the Launcher set be always persistent in memory? That 
is not a good choice... Are you using a lot of widgets?
You can also disable JIT (it trades memory for the speed) and you can also try 
to change the VM heap size in CyanogenMod Performance settings.

Original comment by kabal...@gmail.com on 2 Feb 2011 at 9:24

[GoogleCodeExporter]

In CyanogenMod 7 RC1 0.07-11.02.18 if i take a picture or sometimes two the OS 
will hang. 

Original comment by scottand...@gmail.com on 21 Feb 2011 at 7:15

[GoogleCodeExporter]

I have the same problem with my camera and I use in VGA

Original comment by urachich...@gmail.com on 28 Feb 2011 at 5:57

[GoogleCodeExporter]

0.07-11.03.12 RC3
The same problem - after taking photo nothing happens - photo is frozen on 
screen and only home button works. Photo is not saved on SD card. Checked on 
differend compression levels.

Original comment by kopyc...@gmail.com on 14 Mar 2011 at 2:36

[GoogleCodeExporter]

Taking Picture or making video , just hangs every now and than , 
RC1 7.1

Original comment by atif....@gmail.com on 11 May 2011 at 6:34

[GoogleCodeExporter]

Please test the 7.1.0 RC2 and check also the new 4M Pixels (wide) picture mode 
and widescreen video.

Original comment by kabal...@gmail.com on 11 May 2011 at 7:34

[GoogleCodeExporter]

Issue 387 has been merged into this issue.

Original comment by kabal...@gmail.com on 14 May 2011 at 11:06

[GoogleCodeExporter]

Issue 415 has been merged into this issue.

Original comment by kabal...@gmail.com on 14 May 2011 at 11:07

[GoogleCodeExporter]

Issue 468 has been merged into this issue.

Original comment by kabal...@gmail.com on 14 May 2011 at 11:08

[GoogleCodeExporter]

Issue 522 has been merged into this issue.

Original comment by kabal...@gmail.com on 14 May 2011 at 11:17

[GoogleCodeExporter]

Please test the CM 7.1.0 RC3 release.
Also, report if there is a difference when you have GPS enabled or disabled, 
thanks.

Original comment by kabal...@gmail.com on 15 May 2011 at 1:26

• Changed state: Started
• Added labels: Version-7.1.0RC3
• Removed labels: Version-0.04

[GoogleCodeExporter]

I have tested the camera and seems to be laggy, however I disable some 
background app that were consuming some ram and the camera worked better. I 
have an sms app kept in memory in build.prop and Low Memory Killer Levels set 
at 6,8,26,28,30,32 and launcher hard to kill with this script 
http://forum.xda-developers.com/showthread.php?t=991276

After disable those 2 apps I tested it again but sometimes the camera takes 
like a double shot or something like that when I restart it or at random times.

I assume that the performance is affected with my apps and widgets. Changing 
the VM heap to a higher value would increases it?

Original comment by hjv...@gmail.com on 18 May 2011 at 12:42

[GoogleCodeExporter]

Seems fixed for me since the last few releases. Well, if there's enough free 
RAM anyway. When the phone is in low free RAM state (which is bound to happen 
if the phone has been running for a few days), it hangs as usual...

Original comment by abiya.wy...@gmail.com on 23 May 2011 at 5:09

[GoogleCodeExporter]

I just updated to RC5 and I still experience the problem with the phone 
freezing up completely after taking a couple pictures. If I can be more helpful 
with my description please let me know.

(For the people who say they had to pull their battery: use sift + alt + delete 
to reboot your phone. Easiest way to press them all is hold left shift and then 
use your thumb and index finger to press right alt and delete while the phone 
is laying on a table or somewhere flat.)

Original comment by ellianth@gmail.com on 25 May 2011 at 5:17

[GoogleCodeExporter]

Sorry for the double post, I can't find an edit button.

I set the camera to 4mp wide and superfine quality and that seems to make it 
stop freezing.

Original comment by ellianth@gmail.com on 25 May 2011 at 5:30

[GoogleCodeExporter]

Issue 419 has been merged into this issue.

Original comment by kabal...@gmail.com on 29 May 2011 at 10:13

[GoogleCodeExporter]

4M Pixels (wide) mode is working well for me.

Same issues with camera are known on Droid CM7 build. Both me and cvpcs (droid 
cm maintainer) are looking into it.

Original comment by kabal...@gmail.com on 29 May 2011 at 10:17

• Added labels: Priority-High, Version-7.1.0RC7
• Removed labels: Priority-Medium, Version-7.1.0RC3

[GoogleCodeExporter]

when this happened, memory extremely low (from running services). I found 
killing: 

killall android.process.acore 

will make camera normal again. acore will respawn automaticly later, i dont 
know why acore not being killed when camera need more memory

Original comment by superbiji on 29 May 2011 at 1:58

[GoogleCodeExporter]

RC7. I try 4mpix mode but without result. Because I have same problem on other 
cameras, I make some test on cameras like ZoomFx and Camera360 and I noticed 
one remarkable thing, that camera lags when they have turn on auto save 
options. When I switch off this option everythink is ok. I do not know if it 
helps but it is always a some clue.

Original comment by daniel.k...@gmail.com on 29 May 2011 at 6:07

[GoogleCodeExporter]

Should be fixed in 7.1.0-RC8-11.06.02.
Please don't report issues if you're altering the low memory killer parameters 
from the defaults, or if you are using sys.keep_app_X properties to keep some 
app always in RAM.
The Lock home in memory/Lock messaging app in memory enabled in CM 
settings>performace are OK, though.

Original comment by kabal...@gmail.com on 3 Jun 2011 at 10:44

• Changed state: Fix_proposed

[GoogleCodeExporter]

The camera works mostly fine in RC8 - Its a bit laggy while taking pictures,
compared to the original 2.2 rom, and when trying to exit it freezes for
about 30 seconds. But this behavior is miles better then in 7.0.1 where it
was touch and go if the picture taken was even stored.

Original comment by gus...@gmail.com on 10 Jun 2011 at 1:39

[GoogleCodeExporter]

Still have the problem in RC10. After a fresh reboot the camera works fine, but 
on a day-to-day basis where I actually use the phone, taking pictures is a 
no-no and most of the time I actually have to remove the battery to get my 
phone back. Not the picture just taken though.

Original comment by switch...@gmail.com on 21 Jun 2011 at 10:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I can also confirm, that this camera problem still exits in RC10. Taking a pic 
freezes my milestone. Sometimes for about one minute, sometimes completly. 
Mostly the pic is not been saved.

Original comment by MarvelAr...@gmail.com on 6 Jul 2011 at 1:52