Is anyone having an issue in the Moto camera app where it seemingly won't sense touch on the video capture and camera switch buttons? I've tried reinstallingclearing, and clearing data +cache for the app. I noticed upon reinstallation it wont let me touch next keys in tutorials either.
Related
EDIT: Well, I fixed it. I used Jishnu's Camera mod "return to stock" zip and it fixed things thankfully.
Thanks
-----
When attempting to use the standard camera app on my Nexus, I get this error. I've had a Nexus 5 since launch and had NO issues whatsoever with the camera until recently. No matter what I try to do, the camera app doesn't load. Not from the lockscreen, not from the app, etc.
What's odd is that I CAN use apps like camera zoom fx or the built in snapshot feature in the facebook app for example, and the camera works then. I can also use hangouts and I've verified the front facing camera works. Oddly though, using the camera within the Google+ app crashes the camera too.
I've tried clearing cache, dalvik cache, force stop camera, disabling and re-enabling and no dice. A friend of mine postulated that it could be the HDR mode messing up. I DID have HDR active the last time the camera worked. But with no way of resetting the application/toggling the HDR switch (because the camera won't load to that point), I'm SOL.
Here is a screen cap video I took demonstrating the issue. Don't mind the artifacting at the start of the video, I'm not sure what caused that.
My current phone build is in my sig, except I'm running the most up to date Franco Kernel (iirc r37).
First off, I have not seen this anywhere else, but appologies if i've missed it!
Even on a completely clean install of the M preview, upon opening camera, and once passed the 'OK, GOT IT' button, camera closes. Every time. Regardless of what i do, clear cache, update, remove updates etc. Happens on Preview 1 and 2. Doesnt happen in 5.0/5.1/5.1.1. I thought it might be the fact the camera was damaged being reported in some new way to the system, forcing the closure (i ripped the cable slightly when repairing another part (i know, dumb, but i slipped)), but have since replaced with a new part and still have issues.
Has anyone else had this, and fixed it? Thanks!
Hello, I have the same problem. Unfortunately, my problem persists on older versions of android. My problem seems to be the front facing camera, because with a third party app, the rear camera works. I replaced the front camera, but it still does not work in any app, and the Camera app still does not start. Tried removing the front camera - app again stops working.
That is the same for me. Snapchat will use the rear camera fine, but doesn't register the phone as even having a front camera
ishamm said:
That is the same for me. Snapchat will use the rear camera fine, but doesn't register the phone as even having a front camera
Click to expand...
Click to collapse
Same here! I can take photos through Tinder, and download them to my phone (although sometimes the Tinder app will crash too). But whenever I open the Camera app I get the "Unfortunately, Camera has stopped" message. I've tried multiple reboots, closing the app, not closing the app, resetting the cache, etc. Nothing works.
I believe this all started when I tried to take a "selfie" one time (I guess that's God's way of telling me never to do that again). When I switched to the front camera all hell broke loose. Now I'm guessing it's "stuck" on the front camera and I can't run the app even to switch it back!
I've searched here and on other forums but can't find an answer to some camera related problems.
I'm using 15.1 Osprey June, 1st build on my Moto G3 2Gb Ram (XT1543).
PROBLEM 1: front camera not working.
This is happening for a long time, since I was using stock ROM (my phone came with 6.0, but that time both camera worked fine).
Don't know when this starts, cause i didn't use front camera very often, but when on 6.1 this already happened, the change camera icon simply disappeared.
I've tried all tricks, format the phone, boot on safe mode, clear chaces, etc.
I've used Lineage 14 for a while and now I've made a clean install of 15.1 and same thing.
Back camera works fine for photo and video using Footej Camera — the first time I opened this app, there was the change camera icon; I clicked and get that camera error message, and now the icon disappeared again. Installed MotoCamera_Mod_6.2.5.16 and same thing: back camera fully functional, front camera no icon or options.
Didn't drop my phone, but i'm considering some hardware problem.
Anyone has a link to a DIY fix (or at least try)?
Here in my country, the cost of the repair probably does not pay...
PROBLEM 2: Instagram stories not working
photos works fine, a click the button and can add to my story, but when I record video, after it's finished the buttons doesn't appear and the app freezes.
on "hands free" the image freezes during record, when try to make a boomerang "an error occurs" message appears and the **** goes like this...
I've removed and install back the app, have the last update, etc.
Is someone else having this problem?
thanks!
problem solved!
if someone else is having similar problems, here's the (obvious) solution:
just do a clean flash!
I did it and everything is working now (instagram stories, other camera apps functions and GPS).
except the front camera, probably due to some hardware stuff.
I have the Verizon Pixel 3, and ever since I updated to the November 5 version I have had nothing but trouble with my camera. The native camera app works great, but if I attempt to use any other app on the device that accesses the camera, I get nothing but a black screen. Apps I have on my device that I've tested include
- Messenger
- Snapchat
- Ibotta
- QR Scanner
Once one of the apps attempt to use the camera, the native camera app only gives me a black screen until I restart the device. Once restarted, the native app will work until another app attempts to use the camera, and then it's right back to the black screen.
Has anybody else had this issue yet? I ran across another post where a different user had the same issue, and they had reset their device a couple of times to no resolution.
On latest (nov 5th update) on pixel 3. Camera works fine in Textra for me.... you shouldn't need QR Scanner anymore with the google camera, just hit the lens button, or enable lens all the time in camera settings.
I'm now having this same issue as of a few hours ago. Nothing changed as far as I can tell but any app other than the default camera app trying to access the camera locks the entire thing up.
Guys my main camera stopped working.
The process is not blocked by any other app.
I tried service menu and test camera, it doesn't perform the test, it fails.
Only way to take pictures is to use gcam v1.4 and manually choosing wide or zoom camera.
When u choose 1x camera it stays black and crashes.
Any ideas?
collller said:
Guys my main camera stopped working.
The process is not blocked by any other app.
I tried service menu and test camera, it doesn't perform the test, it fails.
Only way to take pictures is to use gcam v1.4 and manually choosing wide or zoom camera.
When u choose 1x camera it stays black and crashes.
Any ideas?
Click to expand...
Click to collapse
Have you factory reset?
I got the same problem. Just got a black screen and camera app would freeze. Did a factory reset, camera was extremely choppy for a minute or so and now back to nothing.
Tried another factory reset. It seems like if you change the default resolution settings to anything (even tapping on 'FullVision' in settings), it almost breaks the camera. Best to leave it at default 4:3 12 MP resolution.
Seems like a "driver" issue, good work LG.
Did any of you ever find a fix for this? Just got a Korean V50 Thinq and the camera is 99% of the time crashing. I tried installing gcam mods as well and they also crash, primarily while using the main camera.
Got it repaired via LG warranty. They replaced the main/motherboard. Phone has been fine ever since.
Same thing happened to my phone and warranty is expired. I tried the hard reset and may other ways, but nothing helped. Did anyone find a solution for it?