Related
About 2 weeks ago, my camera simply stopped working. Any app that uses the camera simply opens to a black screen and then becomes unresponsive.
I've tried a full factory reset to no avail. Before sending the camera for repair, is there anything else I can try. I did check the forum and elsewhere to see if this was a known issue with the DHD or an individual firmware vesion, but nothing obvious.
I'm running 1.72.405.3
Thanks for any pointers
Daz
Hi Daz,
It does sound like your camera's sensor has failed. I had a similar issue with my HTC Hero when I got that many moons ago. This would be covered by the manufacturers warranty so you'd be entitled to a replacement or repair.
Did the camera only fail once the update had been applied? As i think and i'm not 100% but i think that the cam is one of the things which the update is for, maybe you could try a custom rom to see if the update has caused it, I can't see why but it could be.
My Hero's camera would not work with anything over 1.5, any custom rom or even the stock 2.1 update would cause my phone to reboot after every second usage of the phones camera, it was very annoying and because it was a persistent problem which was no fault of my own, i didn't pay for the replacement, so maybe look into it, it may save you a few bob getting it fixed, unless your getting it for free.
Just a thought.
To be honest it could well have been after an update, I just can't tie the two events together in my head.
The phone will be fixed for free as it's still under warrantee, I was just wondering if there was anything I could do to avoid having to send it away for what could be weeks. I do suspect it's a hardware issue so prob best just to let HTC deal with it and send me back a working phone.
Thanks all.
Daz
I also have this problem, any updates on the issue? I really don't want to be without my phone for weeks! The camera only stopped working after I flashed from Leedroid 1.2 to cyanogenmod 6.1.3 then flashed back to Leedroid
Hi,
I'm afraid I don't know just yet. I sent the phone away for repair and it's still being worked on. I'll let you know what they said when I get it back.
Daz
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
This is a last-ditch effort to get some input before I go blow some money on a new phone. Hoping someone can help! It's possible that I haven't found an answer yet because what I'm doing is futile but I'll go through the story just in case...
Looks like quite a few internet people are having trouble with their HTC Incredible 2 cameras, and over Christmas I joined the fray. Upon launching camera or camcorder, I only see a black screen. The only thing I can think that could have prompted a camera failure was a short (<2ft) drop, but there’s no damage otherwise.
At first I tried but had no success with:
Restarting the phone
Clearing cache, clearing data, and/or force stop in Applications/Manage Applications/All/Camera/ (it’s running v3.00.000.120826.605 if that matters at all)
Restarting the phone in safe mode
Performing a factory reset
Unmounting SD card
Using diagnostic apps (some combination of doms diagnostic tools, androsensor, and msherlock) I’ve confirmed that although both front and rear cameras are recognized by the phone, accessing them for diagnosis freezes the diagnostic app. Strangely, the flash diagnostic tool freezes also, although the flashlight app works fine. Since I don’t think my drop could have busted both cameras and the flash at once, I guess there are two options: it DID wiggle loose a wire that does all the camera-related stuff, or it’s a software problem.
Since my warranty is a few months expired I figured I’d root the phone today, just to be double-dog sure it’s not something easily fixable. I followed http://forum.xda-developers.com/showthread.php?t=1931096, http://forum.xda-developers.com/showthread.php?t=1687590, used Android Commander to look at system files. On recommendation from http://androidforums.com/incredible-2-all-things-root/433350-camera-problem.html#post3361181, I tried to delete the current system/apps/HTCCamera.apk and replace with a different one; both one from http://www.teambamf.net/topic/1737-romgb-skyraider-zeus-13-inc2-update-11222011/ and also a standalone MiuiCamera.apk download were tried, but to no success.
I (attempt to) work with fortran77 during my day job so I can’t say I’m super happy to have blown a Saturday on yet more programming work. Unfortunately I’m a complete noob at this, and am not really sure how to further mess around with anything camera-related. It seems like the only thing I haven’t tried is to install a different ROM, but would it even be useful to do so? Have I missed anything? The Verizon agent I spoke to told me just to replace my phone, but since everything else works okay I wanted to be completely sure there wasn’t anything else I could do to fix the camera function. Does seem like I’m toast, though…
Thanks so much!
Excellent first post.
I have no idea how to help you. I would, However flash a ROM just to be sure. Tsm sense or andybonestock come to mind. It wouldn't hurt, you know?
Sent from my Incredible 2 using xda app-developers app
If that doesn't work try a aosp ROM like dkstunnas cm9 for a last ditch effort. I believe it interacts a Lil different with the camera then sense roms. Maybe
The camera is a replaceable part, so if you cant get it working a new one is less than $20.
Thanks for your suggestions!
I've learned a lot this week (like SMS Backup + should have been installed before the Verizon guy factory reset my phone...whoops, bye texts) and also tried to download "an app that uses the camera but not as a camera" as per http://forum.xda-developers.com/showpost.php?p=36239149&postcount=2 but that didn't work.
Looking at videos that take apart Dinc2's (http://www.youtube.com/watch?v=Qk91u3aqGAQ) I think replacing the camera would be quite outside my comfort zone...also, since both cameras and the flash refuse to work, that seems like a bigger job than I could handle. Unless they're like xmas lights where one goes out and they all go out, but still. I've only soldered maybe once in my life...
On to ROM switching, then. I used this tutorial to guide me through: http://www.incredibleforum.com/forum/htc-incredible-hacks/5514-flashing-roms-tutorial.html#post49612.
I've seen some threads about asop camera weirdness so I figured I'd try the strange one (http://forum.xda-developers.com/showthread.php?t=1932573) first. But, after a few different tries, I couldn’t get it to work…just got stuck on the white htc screen. After 25 minutes of waiting, I pulled out the battery and did the power-voldown thing to get to a menu. Then did a clockworkmod restore and tried andybonestock (http://forum.xda-developers.com/showthread.php?t=1392516) instead, which was successful in booting but not successful in starting my camera (BOO, but who is surprised). Went back to the asop a few more times (aeroevan kernel v14 and v15) as I’m thinking it has the best shot at a camera back door, but I just couldn’t get it to flash. White screen every time. I thought about doing ViperINC (http://forum.xda-developers.com/showthread.php?t=1953899) just for some variety but it uses more things I’m not familiar with (twrp? aroma? boot.img?) and I’m feeling done with this for the day. In any case it was a long shot, and if one ROM flash and a bunch of data clearing didn’t help, probably nothing will.
Looking like I may use this phone as a backup VOIP in the apartment (http://forum.xda-developers.com/showpost.php?p=34335798&postcount=20). Off to probably get an Incredible 4G LTE. Maybe all of the steps outlined in this thread will help someone with a less-severe camera issue…
Woke up this morning and to my avail the rear facing camera is not working. The front camera works fine, but the rear camera has a black screen and after about 3 to 5 seconds the error message pops up and the camera app shuts down. I've tried everything but a factory reset to fix it; called LG for basic support, deleted snapchat (as I know this app is all jacked up on the G4), looked up old solutions for the same issue on G3 variant, all to no avail. Also, I tried running google camera and when that starts up I get the message "Can't connect to the camera."
No apps have updated. Last night before I went to bed it was working perfectly fine.
I've been scouring the net about this happening on the G4, I've seen a couple posts (one of them was posted just today as well) about the issue.
I guess the only next step is to do a factory reset (UGH.) So I guess I'm asking 2-3 questions: A) Has this happened to you, and if so, any solutions? B) What to the best FREE back up software for the factory reset.
BTW, I am on a Verizon Best Buy model..
Thaaaaanks!
Have you tried wiping camera data?
Use the built in LG Backup tool.
Sent From My LG G4
Same thing happened to me. I restarted the phone, cleared the cache, factory reset, ran it in safe mode, etc... but nothing worked. I just went to the Verizon store and exchanged the phone. My phone right now is working fine.
You can always open the back and see if the ribbon came loose off of the board. It'll take like 5 minutes to do and if that's the issue, you'll avoid having to factory reset and exchange and all...
Sent From My LG G4
Rydah805 said:
You can always open the back and see if the ribbon came loose off of the board. It'll take like 5 minutes to do and if that's the issue, you'll avoid having to factory reset and exchange and all...
Sent From My LG G4
Click to expand...
Click to collapse
Ya, I checked everything. It seems like the camera went out. Did a complete factory reset and back up and the camera is doing the same thing. Even the backup lost a BUNCH of data I had on it. What a shame. Had the phone about 2 months and the camera goes out....hardly used the camera much, maybe once a day. And if it goes this quickly..............do I smell a note 5 in my future?
ghostbustaj said:
A) Has this happened to you, and if so, any solutions?
Click to expand...
Click to collapse
I can tell you my experience with the K zoom. when i got a similar message.
I decided i wanted to rearrange the way the different modes were displayed, instead of one line and scrolling have them display in a grid. There was an option. Did that and all looked good. Went to a party a few hours later and kept getting this message. no modes were available except auto.
So whatver photos i took were in auto and not able to tweak setting the way i would have liked.
Got back the next day and started checking. And then i realised it was that damn setting that crashed the camera.
My guess as to what the problem is ? a software bug. think back to whether you changed any settings in options and revert them.
Otherwise it could be something else maybe hardware related.
One Twelve said:
I can tell you my experience with the K zoom. when i got a similar message.
I decided i wanted to rearrange the way the different modes were displayed, instead of one line and scrolling have them display in a grid. There was an option. Did that and all looked good. Went to a party a few hours later and kept getting this message. no modes were available except auto.
So whatver photos i took were in auto and not able to tweak setting the way i would have liked.
Got back the next day and started checking. And then i realised it was that damn setting that crashed the camera.
My guess as to what the problem is ? a software bug. think back to whether you changed any settings in options and revert them.
Otherwise it could be something else maybe hardware related.
Click to expand...
Click to collapse
I never messed with the settings. Heck, I only once tried Manual mode. Always in auto.
Ya wake up and the camera is shot? This is unacceptable.
Do you use any apps that make use of the camera, you mentioned snapchat, any other messaging apps ?
Some app has messed with it somehow is my guess.
If anyone has the Verizon variant with the update that was released a bit ago, whats the software version again? I forgot it. Mine is VS98611A. The phone wont let me update to the newest unless, that is the newest....
One Twelve said:
Do you use any apps that make use of the camera, you mentioned snapchat, any other messaging apps ?
Some app has messed with it somehow is my guess.
Click to expand...
Click to collapse
The only other app I had that uses the camera is Instagram and I guess Twitter? But I uninstalled them both, reset the phone, and tried it again before doing the factory reset.
And after a factory reset what is the result ?
One Twelve said:
And after a factory reset what is the result ?
Click to expand...
Click to collapse
Camera still doesnt work.
I did just notice something....when I have the rear facing camera activated (which crashes the app.) What I assume is the laser focus (the red lights next to the camera) stays on, solid, until the app crashes.
Just took the phone to verizon, they are sending me a phone. The guy wasn't sure if it was a new or refurbished phone. Wtf? How do they not know?
Happened to my wife's Samsung Grand Prime, camera couldn't launch as it kept saying media server failed.
Googled and came up with a solution.
Take out the battery for 10 minutes and reboot.
All good.
Try it.
I have the G4 but didn't have this problem.
Cheers!
ghostbustaj said:
Just took the phone to verizon, they are sending me a phone. The guy wasn't sure if it was a new or refurbished phone. Wtf? How do they not know?
Click to expand...
Click to collapse
Normally when phones are sent out, they're refurbished. They send out refurbished phones before brand new phones. That's just how companies work.
I've wondered how the refurbs are checked. Especially if the phone was returned because of an intermittent problem, and the store didn't clearly document what the problem was.
Would the refurb group look at it, decide/assume it was fine, and just send it back out?
Checking over a phone with an obvious problem, like a dead screen, is easy, but not all scenarios are that clear-cut.
I just don't understand why they would send a referb to me when it was not at all any fault mine. I can understand if the customer lost, broke the device. This is a hardware issue.
so...
ghostbustaj said:
Woke up this morning and to my avail the rear facing camera is not working. The front camera works fine, but the rear camera has a black screen and after about 3 to 5 seconds the error message pops up and the camera app shuts down. I've tried everything but a factory reset to fix it; called LG for basic support, deleted snapchat (as I know this app is all jacked up on the G4), looked up old solutions for the same issue on G3 variant, all to no avail. Also, I tried running google camera and when that starts up I get the message "Can't connect to the camera."
No apps have updated. Last night before I went to bed it was working perfectly fine.
I've been scouring the net about this happening on the G4, I've seen a couple posts (one of them was posted just today as well) about the issue.
I guess the only next step is to do a factory reset (UGH.) So I guess I'm asking 2-3 questions: A) Has this happened to you, and if so, any solutions? B) What to the best FREE back up software for the factory reset.
BTW, I am on a Verizon Best Buy model..
Thaaaaanks!
Click to expand...
Click to collapse
verizon model could do it.
ghostbustaj said:
I just don't understand why they would send a referb to me when it was not at all any fault mine. I can understand if the customer lost, broke the device. This is a hardware issue.
Click to expand...
Click to collapse
Last time I sent it back to LG for repairs, they sent my same phone back. Don't do it through Verizon if you don't want a refurb.