m8 back camera and flash wont work after update - One (M8) Q&A, Help & Troubleshooting

hi
i updated to 6.0 stock firmware before i could use the new viperone rom but now i have issues with my back camera and flash light wont work. i came originaly from older viper rom.
i googeld but i could not find anny good solution on this issue and what i could find it did not help me. i tryd to go back to 5.0 stock witch i got with the phone but no lock.
i really hope someone can help me with this issue
Ps front camera works but only in selfie and booth mode.
Best regards
Eldin

Related

[Q] Telus Desire rooted with 2.2 new radio no camera

Can anyone help i have a telus desire fully rooted, custom rom latest radio updated and my camera n camcorder will not work.
What Rom? I used Official FroYo Market Fixed found here:
http://forum.xda-developers.com/showthread.php?t=741775
Everything works fine for me. Gonna try a Sense-less ROM next and see how that feels (my first Android phone).
Have you got Flashlight widget installed if so unistall there seems to be a problem with that so the camera doesen't work...hope i could help lg
btw: you could have found that by tryin the search ^^

How to fix Camera?

Hey
I updated my motorola defy quiet a while back and have been using it without cam and its come to that time where i actually need the camera working
I was wondering if anyone could shed light on hoaw i could get this back up and running i was originally on 2.1 UK t-mobile rom and lost camera whilst going to my current 2.3 Jboggie rom..
Any download links & Advice would be much appreciated
Thanks
-Jabba
What is the camera prob exactly? does it not work not at all?
Well then you have to use the cameraFix and flash it with RSDLite 4.9
The camera fix is foundable in this forum,or via this link.
[URL="http://dl.dropbox.com/u/22524651/Camera%20fix%282%29.zip"/URL]
http://dl.dropbox.com/u/22524651/Camera%20fix%282%29.zip

[Q] Camera Problem with Custom Roms

i tried Cyanogenmod 11 nightly, , CM11 Linaro and SlimKat 4.4, and everywhere i have the same problem, only the front camera works. in stock roms like LRS, everything is fine, as expected. i tried different camera apps, but the problem remains the same, the camera doesn't work, only the front camera does. there isn't even a button in the camera app to switch between back and front camera, as if i only have one.
is there a fix or a workaround for this? not having a camera is a dealbraker for me, but i really don't want to stay stock. i flashed multiple times, used different gapps versions, did factory resets and reboots, nothing seems to help, the stock version was 4.4.2 v50020. anyone else experiencing such problems?
WEIRD!!!!
I'm having the same problem. My Gpad came from the factory with 4.4.2 installed. and when I try to put any custon rom, this problem is with the camera. any solution? :crying:
Yes. The same problem. Maybe cyanogen team (Bug: CYAN-4444) can find solution.
same problem here, tryied every rom and kernel and nothing. only stock firmware back camera works.. can anyone help us?
read in one SlimKat thread that using the Google Camera from play store would work with all the custom roms, since it uses a different API than other apps.
Haven't tried myself, but you can give it a try
Google camera doesn't work better for me. This is very annoying
effraie said:
Google camera doesn't work better for me. This is very annoying
Click to expand...
Click to collapse
For me neither. Also in the latest builds where infected said the back camera should be fixed, it doesn't work for me.
The problem with camera is present on not only custom roms. It exists on official v50010a firmwares after downgrade. Possibly it's driver\kernel problem, which is caused distinction in camera's modules. Maybe new revisions of the G Pad use some other modules, than older ones.
Any directions to fix it ?
IMHO, they need to get out driver for camera from official 20a. But how it function with kernel, this is the big question that must be solved.
So, there is nothing i can do, except waiting somebody solving that issue ? No mistake on my side ?
Having no back camera is really not a problem to me, but i can't stand having something misconfigured...
Both cameras working for me slimkat 6.2
Not for me....
Some have problem... most don't, something different about your gpads ?
Sent from my Kin[G]_Pad ™
Rear camera not working too
Hi
For me the rear camera won't work too.
My G Pad is a V50020d with stock 4.4.2. I installed the Cyanogenmod 11 via CWM Philz Touch.
Same problem here
tried cm11, paranoid e now um on mahdi, no back camera on any of 3 roms
I haven't tested other custom roms, but Infected's CM11 M9 won't fix the back camera for me.
My G Pad (stock V50020a) is made in Brazil, there might be something to do with this driver or component-wise.
There is a source codes of the last firmware and kernel for the g pad on the lge site.
Maybe, it will help developers to add support for our camera module in the cyan kernel.
Same problem here... Spanish lg g pad 1 month of use

Bad camera on 4.4.3 roms (GLITCH)

Hi
on the new 4.4.3 roms from ARHD and Maximus i get the glitch shown in the picture.
Does anyone know why ?
At first i flashed the rom with the 1.54 firmware. then i noticed the glitch. then i updated the firmware and installed the rom again with full wipe .
but the glitch still persists.
does anyone how i can get this fixed ?
thanks
i mean the grey frame around the settings ^^
i have the international phone
What has this got to do with the camera?
the glitch only appears in camera

[Q] Camera Issue after reverting to stock

HTC M8 international .. rooted and installed CM11 for 3 weeks .. i decided to revert back to i flashed latest stock the problem is the camera quality sucks so blurry same as it was on cm11 .. i compared with another m8 .. i definitely have problem with mine ... is there any chance that cm11 did something with the camera firmware ? i flashed 2 stock roms with same problem ?
is there any way to flash camera firmware or something ?
So you noticed that the camera was blurry, suspected it was CM11, ruled out that it was CM11 by flashing stock, and now you're still asking if it was CM11?
I'll ask you a question: Do you think it's possible it wasn't caused by CM11?

Categories

Resources