Hi guys,
Here are the symptoms
My Galaxy Nexus（GSM) was rooted with wutfresh 1.4, and flashed with AOKP 4.0.4, everything went OK, except for the camera. it will take pictures, but nothing was saved in Gallery. when I try to record video, the app just quit on its own. ppl suggest re-flashing it. so I flashed it with 4.1 Jelly Bean. funny thing is problem persist. so i guess something went wrong with rooting it?
I'm totally new to this rooting thing. so please help
someone help plz
Try deleting Gallery.apk in /system/app and reinstalling a fresh one maybe (don't forget to change permissions)?
Related
Hello everyone, im new to the forum. I rooted my phone about a month ago. I am not using a custom rom or anything and my camera stopped working properly about 2 weeks ago. Everytime I open the camera app, it does not give a clear picture. everything is in purple and blue. Has anyone ever had this problem?
Thanks for any help
-John
So I take it your a on stock rom with root access? Try flashing another rom, or restore a backup?
Yea I am on a stock rom. I did restore it the first time that happened and it worked for 2 weeks, but it happened again.
Are you changing any settings? You may want to try sprint lovers rom, its pretty much the exact stock rom you're on now. I'm not too familiar witht he camera just stopping on ya.
Hey,
I know there are a few threads on this but I haven't found one that followed through to a reported solution.
G2 rooted with CyanogenMod 6.1.1 since January of this year. Tried google goggles and the app locked up. I finally realized that was because the camera has stopped responding. When I pressed on the camera help, nothing changes for a few seconds, then it goes to a black screen. Eventually, (pressing on the back key helps) I'll get a force close/wait screen. Camera had been working fine the previous day.
I've tried clearing caches, using a different SD card with no changes. Used the opportunity to finally upgrade to CyanogenMod 7.0.3 and cleared all the caches as part of the flash. Tried the camera the first chance I could get the phone to that point. Same response from the camera (hesitate, black screen, force close).
So, is there anything else to try or is this a hardware camera failure?
Thanks for any help.
Try flashing some other rom. If that fails, then try flashing another radio.
I'd suggest taking a rooted stock rom and a stock radio just to be sure.
Thanks, but I'm trying to understand what any of that would do to fix the camera over what I've already tried.
I guess I'm looking for anyone that actually had a similar problem and either fixed it or failed to fix it.
Thanks.
Well for once the stock rom uses HTCcamera.apk to open the cam. Since you are using CM7 its a completely different apk.
Radio is somethign that is responsible for almost every device on your phone. Then the drivers that are in the Kernel, and then the ROM which has the apk, that uses the driver from the kernel to start the camera that is defined in the radio.
Well, nothing worked. Unrooted and back to stock (camera still doesn't work). Replacement phone is on it's way.
Camcorder crash. Every time I try to record the camera app crashes..
I've tried a lot of roms. Aokp, cm9,bugless beasts and more
Can someone please help me?
Sent from my Galaxy Nexus using xda premium
What build and rom are you using .. ask them for a fix ...
Hi there,
i have the same problem:
Everytime i try to start video-mode, the app crashes.
When i open and close the app a few times, the cam crashes, too.
Switching from back to front cam sometimes fails, the back cam is active again (after some freeze-time).
Everything worked fine with 4.0.3 stock (open bootloader,root and cwm with GNToolKit).
The problem occurred with the update to 4.0.4. stock (IMM76D & IMM76I)
(I had to do a full wipe, cause i encrypted the phone and cwm could not load the updatefile from encrypted sdcard).
So what i've tried till now:
- clear app cache and data
- extracted camera .apk and .odex from stock 4.0.3 and moved it to /system/app but that didn't work
- Tried other cam-apps (crash)
- installed open bootloader and rooted again (GNToolKit)
- removed flashlight app
- wipe cache /dalvik cache
I don't know, what i should try next, so please help me
Thanks so far...
P.S. Since 4.0.4. all taken photos have a yellow spot. Maybe i should go back to 4.0.3.....
Galaxy Nexus with ICS 4.0.4 IMM76I
Update:
Wiped all and then installed 4.0.2 stock. Everything worked fine with the cam.
Updated OTA to 4.0.4 and now it's the same again... cam crashes if i want to take a video.
Update:
What helped? I got a new one, now everything works fine.
I did go back to stock then it began to work, now it works with any rom again
Sent from my Galaxy Nexus using xda premium
I flashed the newest update. 4.0.4 from google
Sent from my Galaxy Nexus using xda premium
i tried all variants.
Bit strange, that cam worked with 4.0.2 but not with 4.0.4.
Maybe they changed cam-api or something.
With my new gNex, cam works fine
The problem I had wasn't that the camera/video didn't work but that it couldn't save to SD . It had something to do with the permissions and the videocam crashed when I switched . The camera couldt save pictures
P.S I locked my bootloader and then opened it when I did the factory restore
Try to go back to factory a couple of times
Do u have the thumbnail in camera app?
Mine was missing..
I played a lot with the tablet mod, maybe its have something to do with it or maybe because I flashed a lot of roms. I have never seen this before.. it was kind of weird
Sent from my Galaxy Nexus using xda premium
I flashed stock rom, and i think it overwrote all permissions set before.
I locked bootloader, unrooted phone, unlocked it again, then locked it again.. several times. Nothing changed.
My new gNex came with an open bootloader, i was wondering...
The bootloader is still opened and i am root again
I think i had a hardware problem. with 4.0.4. all images i took, had a yellow spot in it. I had thumbnails, too.
maybe you were just unlucky and got a gnex with errors. Was just glad I did't have a hardware failure. I went from 4.0.2 stock ROM to a 4.0.3 costume rom. It then worked fine! when I later upgraded to 4.0.4 costume rom it went wrong . isn't the bootloader always locked? by default?
Sent from my Galaxy Nexus using xda premium
Yes, bootloader is locked by default. I don't know what they did before with this gNex.
Maybe it's not a new gNex, but one, who came back from a user, who didn't want it.
The main point is, it works
First of all, my English is not that good, so I hope everybody understand me
I'm a flashoholic (i think this is the right expression); i flash a new ROM almost every two weeks. And, from some days ago to now i'm experiencing some problems. Here's my problem:
Problem: my phone "stucks" when I let it locked for more than some 5, 10 seconds. I lock it now, and... dead. I have to press the power button until it restarts. My phone is having trouble to find operator's network and it's EXTREMELY lagged too. It almost stucks when i try to write something on the keyboard, or draw/write my passwords on my lockscreen.
Here's my "ROM timeline", too:
ROM Timeline: MIUIBrazil v4 [4.1.2] >> P.A.C MILESTONE [4.2.2] >> TigraROM/Hurricane [4.3 leaked] >> MIUIAndroid v4 [4.1.2] >> MIUIBrazil v4 [4.1.2]
Underline = i think that this is the point
Bold = problem started
So, let me explain my history: flashing ROM's as always, I decided to change things a bit and go AOSP for a while. So I flashed P.A.C. Milestone. Actually, I've flashed first the Nightly version, but it was a bit unstable. I went to P.A.C and everything went fine. But, hey, where are the Samsung functionality? I missed it. So, after some trouble finding the right ROM to me, the 4.3 from Samsung leaked. I tried it, then. First the Hurricane, afterwards the TigraROM (Note 3 functions ). And it was ok, but was lagging a lot. Too much launchscreen redraws to handle, so I went back to MIUI (not the first MIUI on the timeline, because I've decided to go right from scratch), and then, i've noticed a lot of problems.
It was not booting up.
I've flashed A LOT of ROM's trying to solve this problem. What it was? EFS folder. I went to the TWRP file manager on Recovery and noticed that the EFS folder was empty. And no backup. I went crazy until i found an old backup stored on my PC. Restored it right away, and everything was fine for a while... until it started doing some strange things like extreme lag and dead when locked.
And, when I went to recovery to look again to the EFS folder, it was always empty... i restored it again, again and after locked... BAM, disappeared. But some strange things are happening, like:
My bluetooth doesn't turn on.
My IMEI was fine, even with this EFS showing and hiding like that.
I'm almost finishing. Let me put here some basic questions that I know everyone will ask:
Q: have you tried to wipe everything and go from zero?
A: yep. It didn't worked.
Q: is your IMEI ok?
A: yep. But some things that are on the EFS folder doesn't wok, like Bluetooth. The MAC address of the bluetooth is there, but it doesn't show up when I write *#*#232337#*# on my Phone app (this code shows up Bluetooth address and try to turn it on... to me it tries to turn on forever).
Q: do you know that thing about the new modems? Click here to go to the post
A: yes, but only read it when i've had the problem. But i've restore that backup, and it was from the original ROM. So it doesn't seem to be this, because the backup was before this leak. Very very very before, actually.
I hope you guys can help me, and that I don't need to go to the Samsung support with the phone wiped. Thanks,
~imatheussm
When you say you've tried from zero, do you mean you've flashed a stock rom?
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
When you say you've tried from zero, do you mean you've flashed a stock rom?
Click to expand...
Click to collapse
When I had this problem, the second/third thing I did was flashing the stock ROM. But it was with these problems too, and with some other weird things: the S Note and the Samsung Keyboard giving FC almost every second.
~imatheussm
Well I guess if you're getting these issues when completely on stock I reckon you need the service centre?
Sent from my GT-N7105 using xda app-developers app
Have you try formatting your internal sd? I got similar problem too when flashing 4.3 mj5 leak.
Also got a uid mismatch when the phone start. I format my internal sd then flashing 4.1.2 firmware back.
Not a problem after that.
Howdy folks, first post
I have 2 Samsung Galaxy S3 I747Ms from Bell running stock 4.1.2, and have recently rooted both.
On the first one, everything is running fine, despite the horribly cracked screen.
On my better-condition phone, every time I try to use the front-facing camera, it hangs for 10-15 second then displays the "Camera Failed" popup.
It did not do this before rooting, I have flashed back to bell's stock 4.1.2 FW several times, all of which fixed the camera.
It only fails when it's rooted, so no hardware suggestions pls.
Anything I can do, such as copying system files from the good S3 to the other?
Thanks in advance for any help you may provide
I don't see how rooting breaks the camera?
Ajdope said:
Howdy folks, first post
I have 2 Samsung Galaxy S3 I747Ms from Bell running stock 4.1.2, and have recently rooted both.
On the first one, everything is running fine, despite the horribly cracked screen.
On my better-condition phone, every time I try to use the front-facing camera, it hangs for 10-15 second then displays the "Camera Failed" popup.
It did not do this before rooting, I have flashed back to bell's stock 4.1.2 FW several times, all of which fixed the camera.
It only fails when it's rooted, so no hardware suggestions pls.
Anything I can do, such as copying system files from the good S3 to the other?
Thanks in advance for any help you may provide
Click to expand...
Click to collapse
If it's only a root and not a custom rom flash, then there's no reason your camera would stop working. I'm thinking hardware defect.
Update
polobunny said:
If it's only a root and not a custom rom flash, then there's no reason your camera would stop working. I'm thinking hardware defect.
Click to expand...
Click to collapse
It turned out to be software somehow. Fixed it, but Still baffled.