Database Develop

Camera and camcorder force close after upgrading to Cyanogen 4.2.12.2

Just today I upgraded to the latest Cyanogen release (4.2.12.2) on my G1 from pre-4.1.99, and any time I attempt to open either the Camera or Camcorder, it Force Closes, and returns me to the home screen.
I've tried cleaing the cache/data for both the Camera and Camcorder, but that didn't appear to fix the issue. I've also run the fix_permissions command as well, which didn't help either.
Any ideas on what might help fix this problem?

run fix_permissions from console... and post in correct section next time

I apologize for having posted this in the wrong section - where does it belong?
Also, I stated in my OP that I ran the fix_permissions command; from the console was implied.

In the 4.2.12.2 thread.

Thread Moved to Q&A.

I just tried two things: first just wiping and flashing the Cyan Rom again, and that didn't fix it.
Then, I wiped, installed the 1.6 base rom, and then Cyan Rom on top of that, and I still get Force Closes for both the camera and camcorder.
So, I'm still stuck. Any more ideas?

Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.

borodin1 said:
Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.
Click to expand...
Click to collapse
I tried running these commands in the Terminal Emulator, and after the reboot, I still get FCs when trying to open the Camcorder and Camera.
I collected the log, and have attached what I believe to be the relevant portion of it to this message.
Any more ideas?

same here!!!
I am having the exact same issue as you show in the log file
have had some success in reflashing base rom but it only works for a day or so (or hours in some cases)
believe it to be an issue with the drivers but something is killing the camera every time
have removed all apps and reflashed but now it just keeps fc
if any of the devs working on camera issues could have a look please help
cheers
j.

Same thing here.

Same problem here, sucks.

Same HEre 2 =[

Androiid=D said:
Same HEre 2 =[
Click to expand...
Click to collapse
same here, and I tried:
going back to 4.2.8 (where camera last worked for me, before going straight to 4.2.13),
I tried wiping,
I tried removing and and re-making the ext3 partition
I tried reflashing the radio (2.22.19.26I from http://code.google.com/p/sapphire-port-dream/)
My camera is still dead (force closes)

If you have the same issue (camera force closing, flashing older OS not fixing the issue), PLEASE go to Cyanogenmod project Google Code website and click the star next to "Vote for this issue and get email change notifications" on the bottom of the page. You have to be signed into your Google account.
Voting for this issue will raise it's priority (crucial, as it seems to affect a small number of units so far, but it's a show stopper).
Cyanogenmod project Google Code website:
http://code.google.com/p/cyanogenmod/issues/detail?id=1037
Thanks!
Blaz

Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..

legend221 said:
Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..
Click to expand...
Click to collapse
Ummm, I've only one issue: camera not working. Thanks for the pennies tho

blazzr said:
Ummm, I've only one issue: camera not working. Thanks for the pennies tho
Click to expand...
Click to collapse
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.

legend221 said:
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.
Click to expand...
Click to collapse
have tried other roms but i still get the force close so not really a cyan problem methinks

cqms13 said:
have tried other roms but i still get the force close so not really a cyan problem methinks
Click to expand...
Click to collapse
I too a while back had problems installing roms and constantly seeing FCs on my phone. .
The way I fixed that problem was using a bigger/better/faster microSD card I already had.
( @Cqms: I see you already have a newer microSD however, perhaps formatting it after backing up your contents first suits you and then copying everything back once finished. Finally wipe completely/flash Rom and you're set).
Formatted it fat32, since I copied my data on the pc first I copied what I had to the new one.
And finally installed what in my opinion to be one of the best Roms (see my signature) through the wipe/flash procedure and have been extremely happy since.

Camera is back (sort of!!)
Ok as suggested by Legend in above post - wiped formatted etc and flashed super D ROM
Camera comes back but has some kinda solarisation effect which I cant seem to get rid off.
Added to this is my contacts and dialer keep fC ing on me so this ROM is a non runner for me even with a semi working camera
getting closer to the fix though
maybe ima try reflashing cyanogens latest again and see if i can sort the weird effect on the camera
heres hoping
j.

[mod] D3 and Stock GB Camera CWM installers

Attached are working CWM installers for the D3 and stock GB camera apk's.
These install correctly on picrust/cherrypi 0.6 and ninja 4.5 sf, but they should work on any 4.5.91 OTA or newer gingerbread based rom outside of cm7 right now.
Step 1)
boot into cwm (romracer's is prefered)
Step 2)
advanced > wipe dalvik cache, go back > wipe cache
Step 3)
install zip from sdcard > flash respective zip
Step 4)
reboot
It does take some time on initial load of either camera after the flash.
D3 - If you switch to 5mp you get stuck on 5mp. This is not rom specific. If I manage to find a better version I will update the cwm.
**disclaimer**
If you break your phone, I am not responsible. As pointed out later in the thread, yes all this does is push the corresponding apk file, this just makes it a flashable cwm and speeds up the process.

Nice, should this work on stock 4.5.91 ?

it should, I havent tested it directly but the stock gb camera is from that.

diedemus said:
it should, I havent tested it directly but the stock gb file is from that.
Click to expand...
Click to collapse
doesn´t work on Kenn´s beta 4.5.
after installed d3 camera it doesn´t show any camera or video app.

link me the thread you got it from and ill see whats up

diedemus said:
link me the thread you got it from and ill see whats up
Click to expand...
Click to collapse
ok:
http://forum.xda-developers.com/showthread.php?t=1159385&highlight=beta+4
it is practically stock gingerbread 2.3.4

that is the build the stock camera came from, what cwm did you use to flash it?

diedemus said:
that is the build the stock camera came from, what cwm did you use to flash it?
Click to expand...
Click to collapse
Romracer´s CWM

I just did a fresh install of ken's gingerbread beta and both install correctly following the instruction in the op.
I am on romracers atrix 2 cwm, but I dont think that should make a difference in this particular case.
do either of them work for you?

only d3 camera didn´t work

its possible the file got damaged in the download, or didnt flash right. give it another shot and see if it still does it.

i flashed three times with no luck and also tried changing app permissions with root explorer.
fixed permissions with CWM... no luck.
i don´t know what else can do

did you redownload the file though?

diedemus said:
did you redownload the file though?
Click to expand...
Click to collapse
yes, of course

I have no idea why it won't flash for you then, I will look into it further when I wake up.

This will not work unless the rom is made from the 2.3.4 91 OTA/retail SBF . So Alien/Cherrypie/R-9 etc
Most of the new roms have it or have the option on the respective thread.

this is actually in response to people having problems with the ones linked in their respective threads, the update script was changed in the zip files.

Worked fine for me running Alien v3... put on the stock GB camera... tho it took quite a while to bootup so beware... I was thinking I fried the thing...
Tho I have a question... why do pics look so bad and pixelated on this...?? Also the size of the pictures is less than 1mb usually ... isn't it generally the bigger the size the better the quality...??
What,settings should one keep for the best possible picture quality...?? Is widescreen better or 5mp...??
Sent from my Motorola Atrix

Im not sure why they would be pixelated, unless the gallery you are using is the cause. Pictures being less than 1mb would mean they are being taken at one of the lower settings.

diedemus said:
Im not sure why they would be pixelated, unless the gallery you are using is the cause. Pictures being less than 1mb would mean they are being taken at one of the lower settings.
Click to expand...
Click to collapse
I'm completely sure they are set to 5mp or widescreen yet when checking the picture info they are usually like 800kb around... and by pixelated I don't mean like that terrible but not as crisp as what you would expect or what IV seen on my other phones like the SGS...
Sent from my Motorola Atrix

[Q] Can't copy files larger than 3MB to root folder

Yes I know the title is a bit long, but there's no other way to say it.
After updating my rom to android revolution hd 84,I've encountered a small problem: I can't copy single files larger than 3-4MB to some of my root folders.
I discovered this when I tried to change my kernel and my phone restated. I thought it was incompatible but then it happened again when I tried to change my bootanimation.
Basically whenever I try to copy a single file larger than 3-4MB to some of my root folders, my phone auto-deletes it and restarts.
And yes, I've unlocked my bootloader, rooted my phone and I have busybox.
EDIT: Also forgot to mention, I'm using X-Plore as a file manager, and all root folders have a little purple circle on their corner. I can do whatever I want normally in those folders. However, most folders have a red circle and coincidentally, those are the folders which restart my phone and delete all files over 3-4MB that are put into them.
Does anyone have any ideas how to fix this?

Bump, has anyone got any ideas?

kik4444 said:
Bump, has anyone got any ideas?
Click to expand...
Click to collapse
sounds like the kernal to me, you seem to have write protection, have you tried changing the permissions on the folder your trying to write files too or even try another kernal.

I tried a lot of different permissions, nothing works. And since it's got write protection, I CAN'T change the kernel.
EDIT: also, not sure if it matters, but when I updated my rom to a newer version, I didn't wipe the userdata partition, since it's the same rom, just a newer version.
I was thinking of maybe making another nandroid backup, reinstalling the rom AND wiping the userdata partition to try if it fixed anything, and if nothing is fixed, I'll just restore the backup to before I reinstalled the rom.

kik4444 said:
I tried a lot of different permissions, nothing works. And since it's got write protection, I CAN'T change the kernel.
Click to expand...
Click to collapse
This shouldnt stop you from flashing another kernal in recovery, this only effects what you do when booted into the rom.

It's the same thing. Did you read my 1st post? I discovered this when trying to change my kernel, which I can only do through recovery. I use TWRP. I tried flashing a custom kernel and the phone just rebooted without any changes. Then later I tried flashing another bootanimation and the phone again rebooted with the default bootanimation. And it still does it when trying to manually change the bootanimation by replacing it with a file manager.
In conclusion, I get the same problem even in recovery.

kik4444 said:
It's the same thing. Did you read my 1st post? I discovered this when trying to change my kernel, which I can only do through recovery. I use TWRP. I tried flashing a custom kernel and the phone just rebooted without any changes. Then later I tried flashing another bootanimation and the phone again rebooted with the default bootanimation. And it still does it when trying to manually change the bootanimation by replacing it with a file manager.
In conclusion, I get the same problem even in recovery.
Click to expand...
Click to collapse
Of course I read your first post, just didnt quite understand the restart part, thought you meant it restarted itself out of your rom, I would try what you said, rather than a dirty flash, try with a clean slate after backing up, there maybe parts of your old modifications to the system in the data partition.

Also, I'm not sure it can technically be called "write protection", since I can copy\delete\move, etc files just fine, but I can't copy files above 3MB. And due to that I can't change my bootanimation and kernel. As for the bootanmation, I also tried changing it manually and still the same thing happens - my phone reboots and deletes the file I copied. Needless to say, the same thing happens even when trying to flash it with TWRP.

Ok, reinstalling rom, will report back with results.
Edit 1 - install complete, rebooting....
Edit 2 - doing the setup thing at the 1st startup
Conclusion - Strangely enough, doing a clean flash of my rom fixed everything. Weird. Well, guess now I have a lot of things to set up again.

Well, thx for everything, even if I managed to fix everything by myself in the end. Though, I'd still much appreciate it if anyone could tell me what the problem was so I can be ready for any similar problems I might have in the future.

kik4444 said:
Well, thx for everything, even if I managed to fix everything by myself in the end. Though, I'd still much appreciate it if anyone could tell me what the problem was so I can be ready for any similar problems I might have in the future.
Click to expand...
Click to collapse
Did you not read my last post ? Of course I read your first post, just didnt quite understand the restart part, thought you meant it restarted itself out of your rom, I would try what you said, rather than a dirty flash, try with a clean slate after backing up, THERE MAYBE PARTS OF YOUR OLD MODIFICATIONS TO THE SYSTEM IN THE DATA PARTITON.
I never dirty flash, and the reason, your problems, even if im switching to a newer version of the same rom.

[desperately need help]Camera keep FC/ cannot be detected

Hi all, i am having a big trouble about the camera.
So i was using the official CM12, but since recently the camera keep FC or it kept saying can't connect to camera,
i decided to change to the other ROM. However, when i changed to Titan Prime 1.1, i can open the camera ONCE. After that same issue happen!!
it is not only the camera, also the screenshot function is not working! It kept saying due to limited storage the screenshot couldn't be taken
So i tried the following methods:
1. Force stop camera app, clean cache+data, reboot => didn't work
2. Install the CameraFiles-Signed.zip => didn't work
3. Wipe the system, data, cache and davik cache and install different versions of CM or Titan Prime 1.1 =>didn't work
Does anyone has the problem or know how to solve this??
Thanks!

Boseinstein said:
Hi all, i am having a big trouble about the camera.
So i was using the official CM12, but since recently the camera keep FC or it kept saying can't connect to camera,
i decided to change to the other ROM. However, when i changed to Titan Prime 1.1, i can open the camera ONCE. After that same issue happen!!
it is not only the camera, also the screenshot function is not working! It kept saying due to limited storage the screenshot couldn't be taken
So i tried the following methods:
1. Force stop camera app, clean cache+data, reboot => didn't work
2. Install the CameraFiles-Signed.zip => didn't work
3. Wipe the system, data, cache and davik cache and install different versions of CM or Titan Prime 1.1 =>didn't work
Does anyone has the problem or know how to solve this??
Thanks!
Click to expand...
Click to collapse
Try flashing stock with correct fast boot commands ..!! This should work

dj krishna said:
Try flashing stock with correct fast boot commands ..!! This should work
Click to expand...
Click to collapse
You mean flash back to the original motorola ROM?
what commands should i put??
Thanks!

you don't have a camera problem you have a file permission bug...
see here.

baybutcher27 said:
you don't have a camera problem you have a file permission bug...
see here.
Click to expand...
Click to collapse
Thanks for the help!
I tried the first method and it didn't work. And i used this http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167 method to restore to Stock.
But both method doesn't work still. When i open camera on stock rom, it said camera is busy. If this repeat please power off and restart your phone,
but the screenshot is now functioning.
I tried to flash just the Titan Prime 1.1 rom without PA Gapps, camera worked once. But after i install the gapps camera fc again.
Again i tried to restore to stock ROM, problem keeps occur. Then even i flash the Titan Prime again without gapps,
camera fc again !
It appears to be crashed with gapps and i don't know what to do next....

Boseinstein said:
Thanks for the help!
I tried the first method and it didn't work. And i used this http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167 method to restore to Stock.
But both method doesn't work still. When i open camera on stock rom, it said camera is busy. If this repeat please power off and restart your phone,
but the screenshot is now functioning.
I tried to flash just the Titan Prime 1.1 rom without PA Gapps, camera worked once. But after i install the gapps camera fc again.
Again i tried to restore to stock ROM, problem keeps occur. Then even i flash the Titan Prime again without gapps,
camera fc again !
It appears to be crashed with gapps and i don't know what to do next....
Click to expand...
Click to collapse
power off, and remove yours sd card.
power on and give a try.
if no good factory reset without the sd card and give a try.
you may have something in the sd causing it.

baybutcher27 said:
power off, and remove yours sd card.
power on and give a try.
if no good factory reset without the sd card and give a try.
you may have something in the sd causing it.
Click to expand...
Click to collapse
Oh my god you are right! how can you know that?
There is something wrong about the path for the camera to save photos.
Now the camera is smooth again!
Thank so much!!

Boseinstein said:
Oh my god you are right! how can you know that?
There is something wrong about the path for the camera to save photos.
Now the camera is smooth again!
Thank so much!!
Click to expand...
Click to collapse
Don't know was guess...
But i remember now, that my camera not the phone camera a digital camera that i have do that some times to some SD cards, probably from that i guess it.
Good that works. Try to format the card or use other to see if the problem is 100% resolved. Maybe a file in the SD is causing it, so be careful to what files you put back in the card.

baybutcher27 said:
Don't know was guess...
But i remember now, that my camera not the phone camera a digital camera that i have do that some times to some SD cards, probably from that i guess it.
Good that works. Try to format the card or use other to see if the problem is 100% resolved. Maybe a file in the SD is causing it, so be careful to what files you put back in the card.
Click to expand...
Click to collapse
It was the DCIM folder from older version of the rom caused it. I moved that folder to my pc and problem resolved.
I think the path just messed up. Thanks for the help anyway. I tried to fix it for two days!

Boseinstein said:
It was the DCIM folder from older version of the rom caused it. I moved that folder to my pc and problem resolved.
I think the path just messed up. Thanks for the help anyway. I tried to fix it for two days!
Click to expand...
Click to collapse
Hi guys i need help again. After a few week, without flashing any new roms, the problem pops out again.
Could it be problem about the path of camera? It is no longer in system/app
And if so how should i move it?
I searched for a long time and people said it could be permission problem.
I tried to use TWRP to fix ( which ends up in bootloop even with busybox),
and i try to clean wipe and install rom,
or even restore to stock rom, it still doesn't work.
Anyone can help.....?

the camera error
Hi guys so i tried to capture the error.
It said something about getting nullpointer, anyone know how to fix this?
I switched to CM12 rom, it has camera2. apk in system/app.
But it seems that the system still can't find the camera!

My camera has a really poor quality since I updated from 5.1

I've tried 6.1 and 7.0 (currently) and the camera quality is way worse than when I had 5.1
Obviously I don't want to go back to the 5.1, so what are my options?
All I care about is to don't lose the security and battery improvements that 7.0 brought to my phone.
Thanks in advance
EDIT: Example -> imgur. com/a/nD4qW (without the space, I can't post links yet)

I'm on 7.0 too and have same issues with camera. It's really bad from Samsung to do that with their software

Mind telling how its bad? Examples? Usual stuff like that

Porcupineomg said:
Mind telling how its bad? Examples? Usual stuff like that
Click to expand...
Click to collapse
Sure.
imgur. com/a/nD4qW (without the space, I can't post links yet)
As you can see the "before" pics have the average quality for a Note 5, but the other 2 are way below the quality one would expect from this phone
It happened right after I updated, that's why I think that's the reason. But maybe it was just a coincidence and my camera got broken.

mihajlo1 said:
I'm on 7.0 too and have same issues with camera. It's really bad from Samsung to do that with their software
Click to expand...
Click to collapse
I updated the OP with an album with pictures before and after.
Mind telling me if the quality of your pics are similar to mine?

I think its more of a hardware issue than a software. If you haven't rooted your phone yet i will recommend you to do so. Flash TWRP and wipe data, system, cache, dalvik cache, Internal Storage and then Flash a new ROM with tge corresponding Kernel for your phone model. After all those steps check if your phone's camera got fixed. Btw when wiping internal storage you should backup everything from your phone and have an OTG cable with a USB thumbdrive to flash the downloaded ROM & Kernel for your phone.

luisoriera said:
I think its more of a hardware issue than a software. If you haven't rooted your phone yet i will recommend you to do so. Flash TWRP and wipe data, system, cache, dalvik cache, Internal Storage and then Flash a new ROM with tge corresponding Kernel for your phone model. After all those steps check if your phone's camera got fixed. Btw when wiping internal storage you should backup everything from your phone and have an OTG cable with a USB thumbdrive to flash the downloaded ROM & Kernel for your phone.
Click to expand...
Click to collapse
Thanks for the answer.
I will try all that right away.
EDIT: my note 5's bootloader is locked (At&t). Will I be able to do that?
EDIT2: aparently not

Well... Your only chance is to go to AT&T and make a claim to repair it. Or better, change it. Good luck man.

I have the same problem, first it thought it's only me.. but after I saw your uploaded photos .. I started to think it's a software issue.. I'll try a downgrade and I'll inform you with the results.

bassam M said:
I'll try a downgrade and I'll inform you with the results.
Click to expand...
Click to collapse
Yes please!!
I cannot downgrade my phone to Lollipop because my bootloader is locked (AT&T) so it would be nice if you could confirm that this problem is related with the android version.

Pictures are exactly like mine. We have same problem.

from the photos I see the image is blurred because the glass on the camera is scratched or has oil,moisture on it try to clean the glass of the camera well then try to recapture the photos I don't think it's a software issue

Hi again, Sorry for being late,
I was able to downgrade only to Marshmallow due to Binary issue (can't downgrade to smaller binary number),
the photos are better now but from time to time I got this Fairy tale blurred effect (and believe me the camera cover is clean).. but if I lowered the lighting (long press on the screen and slide down) the image return to normal.. !!!
so.. the downgrade helped but didn't solve the problem 100%.. and I'l stick with marshmallow for now..

Same issue with Camera quality when upgraded to 7.0 from a custom rom based on 7.0