I was on the last update of the device and everything was running fine if a bit slow and sluggish. Until two days ago when the camera stopped working. The camera app would just show a black screen and every other app that could use the camera like WhatsApp and signal would also not be able to use the camera. Weirdly enough the torch wouldn't work either and it would say that the camera is in use. I did the following things to troubleshoot:
1. Wiped camera app cache, disabled then enabled the app, and finally restarted the phone. This worked for a bit and the camera would work for a few minutes but then it would stop working again.
2. Full system wipe. Didn't help at all.
3. Installed Lineage OS 20. Didn't help either, well the phone works much faster and snappier now plus it went from android 11 to 13 but the camera still has the same issue.
What else can I try? Will installing a custom kernel help?
Does the second camera (front/rear) work?
If so, take a look here
OnePlus 6 Repair
The sixth iteration of OnePlus's flagship smartphone and successor to the OnePlus 5T. Released May 2018.
www.ifixit.com
and consider whether you can handle the replacement.
ze7zez said:
Does the second camera (front/rear) work?
If so, take a look here
OnePlus 6 Repair
The sixth iteration of OnePlus's flagship smartphone and successor to the OnePlus 5T. Released May 2018.
www.ifixit.com
and consider whether you can handle the replacement.
Click to expand...
Click to collapse
None of the cameras are working. This feels like a bug where whenever an app tries to grab the camera it gets denied and told that the camera is already in use. As for repair, if a physical repair can solve this then I'd be definitely willing to try, I'm pretty confident with electronics tinkering.
It is rather unlikely that both cameras were damaged at the same time. So perhaps the damage (overheating of the chipset) is on the motherboard. In that case, it may not be cost-effective to repair.
ze7zez said:
It is rather unlikely that both cameras were damaged at the same time. So perhaps the damage (overheating of the chipset) is on the motherboard. In that case, it may not be cost-effective to repair.
Click to expand...
Click to collapse
Oh wait a minute, a few days ago I did feel that my phone got a lot hotter than it usually does for around 10-15 minutes. And these problems started after that.
Have you tried using the camera app while plugged into a wall charger? If the battery is older, maybe it isn't able to supply enough on-demand load for the camera.
Related
Dear all,
A few days ago, my N5's camera stopped working and none of the usual solutions (reboot, clean data and cache of camera app, even complete wipe and change of ROM) did anything to fix the problem. So I went on ebay, and bought a replacement back camera, fitted it and all was well...for a day!!! It looks like after just one day (and nearly no use at all) the new camera has already stopped working. Is anyone aware of what may be causing it, and of a way to fix it? or is it time for a new phone?
Thanks for your help!!
Is it possible the camera connction on the motherboard is a bit flaky?
audit13 said:
Is it possible the camera connction on the motherboard is a bit flaky?
Click to expand...
Click to collapse
Thanks for your reply. I thought that too after the second camera went wrong. I re-opened the phone and checked the connection, and from what I can see it seems quite solid. I am not sure what could possibly be going wrong that causing 2 camera modules to go bad in quick succession though. While the rest of the phone works perfectly.
Maybe it's just coincidence. I guess you could try a third camera to see what happens.
Can't connect to camera
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Maybe it because of your sd card
dixie600mhz said:
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Click to expand...
Click to collapse
Initially I thought this may be a normal issue of age of the phone, but the fact that a few of us are bumping into this so shortly after the marshmallow upgrade makes me think maybe the 2 things are related.
I suppose I could try and install a lollipop rom and buy yet another camera module.
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
wangdaning said:
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
Click to expand...
Click to collapse
Thanks for your reply. Done, but to no avail. Infact when you flash from fastboot the camera app is not even installed and the torch does not show up in the notification bar.
It is definitely a hardware issue, which is not resolved by simply replacing the camera module, as that seems to break again in a short amount of time. Not sure if I feel investing in a new mainboard and a new camera module.
Just like that, out of the blue no more rear camera. When you try to launch app, it just instantly crashes. This happens with 3rd party camera apps as well.
When I'm checking hardware with apps like aida64, droid info and devcheck there are no rear camera, it's not detectable.
Cache clear, app disable, safe boot, hard reset does not solve this issue.
I see two options: 1) Google in last system update included firmware upgrade for camera that totally screwed it up; 2) it's really faulty rear camera (I hope not)
Apparently I'm not alone, but I couldn't find anywhere on the web complaining about it. Is it really isolated case?
whitealien said:
Just like that, out of the blue no more rear camera. When you try to launch app, it just instantly crashes. This happens with 3rd party camera apps as well.
When I'm checking hardware with apps like aida64, droid info and devcheck there are no rear camera, it's not detectable.
Cache clear, app disable, safe boot, hard reset does not solve this issue.
I see two options: 1) Google in last system update included firmware upgrade for camera that totally screwed it up; 2) it's really faulty rear camera (I hope not)
Apparently I'm not alone, but I couldn't find anywhere on the web complaining about it. Is it really isolated case?
Click to expand...
Click to collapse
I'm on the latest system update, and have had no camera problems. Sounds like you may have a faulty camera.
I'm on the latest as well with no issues. As mentioned, this screams failed camera. When repairing other phones and leaving a camera ribbon disconnected I experienced the exact same crashes with camera related apps.
Exokan said:
I'm on the latest as well with no issues. As mentioned, this screams failed camera. When repairing other phones and leaving a camera ribbon disconnected I experienced the exact same crashes with camera related apps.
Click to expand...
Click to collapse
Can it be that small slide from bed to floor could break camera? I would be shocked if that is true. Pixel phones are even more fragile than iphones.
whitealien said:
Can it be that small slide from bed to floor could break camera? I would be shocked if that is true. Pixel phones are even more fragile than iphones.
Click to expand...
Click to collapse
Apparently it can.
Brought today to repair shop. Guy said that camera socket had cold solder joints. This would explain why small drop would cause socket failure, but should I believe him? Lets see after repair. This will offset me for 70€ , ouch. Also, he said that flash was burned???? What? Phone is month old and I never used flash.
It seems that Google phones have issues with quality control.
whitealien said:
Apparently it can.
Click to expand...
Click to collapse
That's a bummer. Sorry dude, good luck with the repairs!
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Hopefully the next gen will be better.
I didn't have an issue with mine , but sold it today. I prefer the slick oneplus 8 pro. Less pork and more of an on point device.
Snapdragon or Exynos?
socalstagetech said:
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Click to expand...
Click to collapse
I would like to take over for FREE. Lol
Sent from my SM-N986U1 using Tapatalk
socalstagetech said:
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Click to expand...
Click to collapse
Ever considered you've gotten a lemon? I've literally had zero of those issues since the launch date
Sent from my SM-N986U using Tapatalk
I had the same Bluetooth connection issues with the s20 ultra same 5g issues an poor picture quality.
That would be nice if it was just a lemon. I'm going to spend the day tomorrow with t-mobile.
The fast charger also died withing the first two weeks.
They want me to drive 40 miles to pick a new one up.
Really over samsung. Over priced and undelivered.
socalstagetech said:
I had the same Bluetooth connection issues with the s20 ultra same 5g issues an poor picture quality.
That would be nice if it was just a lemon. I'm going to spend the day tomorrow with t-mobile.
The fast charger also died withing the first two weeks.
They want me to drive 40 miles to pick a new one up.
Really over samsung. Over priced and undelivered.
Click to expand...
Click to collapse
I feel you. Samsung support sucks; it's not your imagination.
I have a 10+ and have been eyeballing the 20U as an upgrade. There do appear to be display issues on some of these phones.
As for bt, try a network reset; it's relatively painless and may help.
Clear the system cache on the boot menu.
Double check all settings.
Turn off all power management except the power mode; set to optimize.
In Developer options>standby apps, if all buckets show as active, power management is disable. See if Android will manage them better with no assigned buckets.
Look for apps using up bandwidth/battery, cloud apps including Google Transport are prime offenders.
Disable Samsung, carrier and Google feedback.
Consider adding a package disabler like PD MDM the shutdown the bloatware.
See if that helps... play with it.
socalstagetech said:
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Click to expand...
Click to collapse
I've had mine for months and haven't experienced a single issue you experienced, just get another phone if you're unhappy and stop the whining
btmusicman313 said:
I've had mine for months and haven't experienced a single issue you experienced, just get another phone if you're unhappy and stop the whining
Click to expand...
Click to collapse
That doesn't help.
Depending on the carrier firmware the same model can behave much different.
Took me close to 6 months to dial in my AT&T 10+, it was a handful. Running hot, chewing up the battery.
Today, a year latter, it's a totally different animal; fast, stable with good battery life and no glitches.
These phones are complex with a lot of settings plus added carrier and 3rd party apks not to mention the Samsung apks. No configuration is the same.
If you don't play with them you'll never get it optimized and you'll just be along for the ride... wherever it goes.
blackhawk said:
I feel you. Samsung support sucks; it's not your imagination.
I have a 10+ and have been eyeballing the 20U as an upgrade. There do appear to be display issues on some of these phones.
As for bt, try a network reset; it's relatively painless and may help.
Clear the system cache on the boot menu.
Double check all settings.
Turn off all power management except the power mode; set to optimize.
In Developer options>standby apps, if all buckets show as active, power management is disable. See if Android will manage them better with no assigned buckets.
Look for apps using up bandwidth/battery, cloud apps including Google Transport are prime offenders.
Disable Samsung, carrier and Google feedback.
Consider adding a package disabler like PD MDM the shutdown the bloatware.
See if that helps... play with it.
Click to expand...
Click to collapse
Thank you very much for the helpful suggestions! I'm going to try it and see how it goes.
I very much appreciate the helpful reply.
socalstagetech said:
Thank you very much for the helpful suggestions! I'm going to try it and see how it goes.
I very much appreciate the helpful reply.
Click to expand...
Click to collapse
You're welcome.
A hard reboot (simulating pulling the battery) may get it too if you haven't try it. Again clearing the system cache can cure many gremlins like magic, easy to do and worth trying.
Another possibility is the phone was infected with a virus or trojan, this is very unlikely though unless you inadvertently downloaded or loaded it.
Scan it with Malwarebytes and Trojan Scanner.
If in doubt reload.
Normally reloads aren't a solution unless it's an old load or if compromised by a virus.
If you reload check the system before you load anything except from Playstore; assume the SD card or computer backups could be compromised as well.
If you reload avoid doing any updates at first as one of these could be causing the erratic behavior.
If you did a firmware update this could be the cause; clearing the system cache may fix it but a reload is better. I disable autoupdates especially from the carrier for this reason among others.
More than likely you get it sorted out or at worst return for repairs.
Reload it though before you return it. Fixable software/settings issues* are common on these phones.
Lol, Androids wuv to be played with... good luck
*if you have a clean load it's always preferable to find the cause of the malfunction rather than reloading as the same issue may well happen again from the same apk or incorrect setting(s).
socalstagetech said:
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Click to expand...
Click to collapse
Not even a single issue I have faced so far. Two month with me now. Fabulously amazing in every bit of it. Are you sure you have Samsung Galaxy Note 20 Ultra there [emoji848]?
Sent from my SM-N9860 using Tapatalk
socalstagetech said:
The 5g is horrendous
The Bluetooth sucks doesn't connect or work for half my devices any other cheap phone works flawlessly.
Phone freezes up on web pages constantly.
This phone is absolute trash.
I feel so ripped off for as much as I payed for this hunk of junk it should work.
The pictures are **** too... blurry an ****ed off.
When I call people they can't hear a word I say...
What else could go wrong?
Really wish I had waited for the pixel 5.
Even a 3 year old pixel smokes this trash.
Click to expand...
Click to collapse
Honestly, I would have it exchanged if you are having that many problems with it, sounds like you may have a defective unit, it happens, could be something as simple as a faulty motherboard causing all those issues that a quick exchange would solve
Got to say this is the best phone I've ever owned so I'm extremely surprised you're having all those problems, contact whoever you bought it from, tell them what you told us and get a replacement unit sent out
socalstagetech said:
Thank you very much for the helpful suggestions! I'm going to try it and see how it goes.
I very much appreciate the helpful reply.
Click to expand...
Click to collapse
*Detection* said:
Honestly, I would have it exchanged if you are having that many problems with it, sounds like you may have a defective unit, it happens, could be something as simple as a faulty motherboard causing all those issues that a quick exchange would solve
Got to say this is the best phone I've ever owned so I'm extremely surprised you're having all those problems, contact whoever you bought it from, tell them what you told us and get a replacement unit sent out
Click to expand...
Click to collapse
Could be a bad mobo but it's easier to reload then to exchange it and then have the exact same issues.
Happened to me with the 10+, bt audio was horrible.
Return it and at first it was running normally then boom the exact same thing. I knew it was software but I didn't manually toggle it!
Samsung tech zero help, same-same with AT&T tech support.
The problem goes back at least as far as the N9 and that's where I found the solution.
It was a glitch in the advanced audio settings that sometimes toggles on by it's self probably due to a glitch in Wearables.
Samsung finally fixed it about a half year about with a Wearables update. It took them over 2 years.
If you knew about it, it was easy to simply untoggled it occasionally, if not it was an audio nightmare.
The only other way to reset it was a pointless reload.
I like the shotgun get it done approach but you can needlessly spend time without a solution if you don't first try to verify if it's hardware, bad flash or an issue that's pure software.
Out of the box this AT&T 10+ was a puking, bandwidth/battery eating, hot running mess besides the bt glitch.
Today with the same OS version and a lot of optimizing it's stable, fast, gorgeous looking platform with good battery life.
It wasn't even close to this out of the box...
If you don't take the time to play with these phones you'll miss the functionality they're capable of and put up will a lot of unpleasant experiences needlessly.
A misbehaving Android is an opportunity to learn new tricks. Just dive in... and see where it takes you.
I can confirm on pics being blurry. Also Samsung should calibrate their displays like Apple. Its shouldn't be left for users to find the right setting. Also the screen is not crisp in fhd mode. My Xr with 820p looked sharper.
RISHI RAJ said:
Also the screen is not crisp in fhd mode. My Xr with 820p looked sharper.
Click to expand...
Click to collapse
Increase minimum DPI in developers options for way better sharpness / clarity
RISHI RAJ said:
I can confirm on pics being blurry. Also Samsung should calibrate their displays like Apple. Its shouldn't be left for users to find the right setting. Also the screen is not crisp in fhd mode. My Xr with 820p looked sharper.
Click to expand...
Click to collapse
I try to take pics of my plants and it takes a ton of shots to get one nice clear one. I have a pixel 3 and the camera taking the same pics in the same lighting are beautiful and easy to capture perfectly the first time.
My screen just froze while typing this reply ?
Whole thing freezes up and you have to hit home button or the current running apps then pop back in to get it to come back.
*Detection* said:
Increase minimum DPI in developers options for way better sharpness / clarity
Click to expand...
Click to collapse
Exactly where is that setting at in developer options?
RISHI RAJ said:
I can confirm on pics being blurry. Also Samsung should calibrate their displays like Apple. Its shouldn't be left for users to find the right setting. Also the screen is not crisp in fhd mode. My Xr with 820p looked sharper.
Click to expand...
Click to collapse
socalstagetech said:
I try to take pics of my plants and it takes a ton of shots to get one nice clear one. I have a pixel 3 and the camera taking the same pics in the same lighting are beautiful and easy to capture perfectly the first time.
My screen just froze while typing this reply
Whole thing freezes up and you have to hit home button or the current running apps then pop back in to get it to come back.
Click to expand...
Click to collapse
Android color calibration (ie no calibration) sucks.
When will they get the message?
After 5+ years you would think they would know better?
I could calibrate my color throughput/monitor on Windows 15 years ago...
Make sure Bixby Vision and Bixby Vision Framework are not disabled; needed by the cam, the rest of Bixby can be disabled.
Check cam settings and manually set the AF lock point if you aren't. Try a data reset on the app and clear the system cache. Could be hardware but more likely user, settings, software or firmware related.
My browser will lock up if too many windows are open (52 open now) or if the browser cache gets too large or corrupted. Might the browser; my primary one is Brave. The Samsung browser handles about 15 or so open windows.
I chased down dozens of issues on my 10+ to get it where it is today over mostly a 6 month period.
I'm careful about all updates and new apps as these can cause havoc especially the former.
Still running on Pie because it's fast, stable, secure enough for my setup and everything is now running well.
Constantly upgrading is time consuming at best and the outcome not always an improvement. I use the factory load for a bunch of apks still... with good results.
blackhawk said:
Android color calibration (ie no calibration) sucks.
When will they get the message?
After 5+ years you would think they would know better?
I could calibrate my color throughput/monitor on Windows 15 years ago...
Make sure Bixby Vision and Bixby Vision Framework are not disabled; needed by the cam, the rest of Bixby can be disabled.
Check cam settings and manually set the AF lock point if you aren't. Try a data reset on the app and clear the system cache. Could be hardware but more likely user, settings, software or firmware related.
My browser will lock up if too many windows are open (52 open now) or if the browser cache gets too large or corrupted. Might the browser; my primary one is Brave. The Samsung browser handles about 15 or so open windows.
I chased down dozens of issues on my 10+ to get it where it is today over mostly a 6 month period.
I'm careful about all updates and new apps as these can cause havoc especially the former.
Still running on Pie because it's fast, stable, secure enough for my setup and everything is now running well.
Constantly upgrading is time consuming at best and the outcome not always an improvement. I use the factory load for a bunch of apks still... with good results.
Click to expand...
Click to collapse
You don't need Bixby Vision and Bixby Vision Framework enabled for the camera to work.
Not sure why but recently this is happening a couple times a week now.
I'll go to open the camera and its just a black screen and says the phone needs to be restarted or ill open snapchat, instagram, etc. (Any app that uses the camera) and, same thing, black screen and it says restart camera/phone.
Anyone else experience this ? Should I factory reset The phone ? It has never been dropped or anything out of the ordinary use. I don't have many apps installed either.
Factory resets are a waste of time unless it's an old load or a virus, trojan etc.
If you do a hard reset to cure this issue and it's not due to the above reasons it will likely reoccur.
Take the time and trouble to track down the root cause... to save time and trouble.
Try clearing the system cache on the boot menu.
Try a hard reboot.
Try clearing cam data.
Disable Bixby and any automation junk.
Look closely at all 3rd party apps that use the cam... that may well be the trouble.
You can try resetting settings but this is pretty drastic global action as you will lose all your settings... try not to do this! Plus it may not work.
It's a samsung bug that has to do with camera access, mine happens when switching to live focus video but works normal after camera restarts.
There's nothing we can do to fix it except write to internet publications to shame samsung into cleaning up their code.
My best friend is a regional manager for tmobile and they have tons of calls about it.
coilbio said:
It's a samsung bug that has to do with camera access, mine happens when switching to live focus video but works normal after camera restarts.
There's nothing we can do to fix it except write to internet publications to shame samsung into cleaning up their code.
My best friend is a regional manager for tmobile and they have tons of calls about it.
Click to expand...
Click to collapse
If not all phones of that tmobile variant are effected it's probably related to settings too.
Try disabling all power management except for the screen. Don't set that to it's max power saving setting (set to medium or high performance).
Power management causes a lot of issues.
All buckets in standby apps should show as active otherwise power management is active.
blackhawk said:
If not all phones of that tmobile variant are effected it's probably related to settings too.
Try disabling all power management except for the screen. Don't set that to it's max power saving setting (set to medium or high performance).
Power management causes a lot of issues.
All buckets in standby apps should show as active otherwise power management is active.
Click to expand...
Click to collapse
Ugh search the forums, all variants have been affected, I think most people don't report it because it's so rare, or want to justify the illusion of their perfect $1000+ phone .
It's Samsung's software being half baked and not cleaned up as usual.
Literally the problem probably is the difference between the TOF and Laser autofocus systems because samsung in their lazynes have code and references to the s20 series in their n20u (n10+ too) systems.
coilbio said:
Ugh search the forums, all variants have been affected, I think most people don't report it because it's so rare, or want to justify the illusion of their perfect $1000+ phone .
It's Samsung's software being half baked and not cleaned up as usual.
Literally the problem probably is the difference between the TOF and Laser autofocus systems because samsung in their lazynes have code and references to the s20 series in their n20u (n10+ too) systems.
Click to expand...
Click to collapse
The laser AF is cool... took Sammy over a year to finally fix the Buds firmware but they did.
Samsung products aren't solid like Denon or Canon products. No support either compared to a top shelf company like Canon or Denon.
Though unlikely it could be a hardware issue or a bad flash especially if no one else has this issue.
Had a $6G Canon pro cam like that; no one could believe it had random glitches (including myself at times). It did. Canon finally replaced it.
It was a little bugger.
Most likely though it's settings, 3rd party app, cache or app corrupted.
If you have any cam updates try going back to the factory load version. This regression repair can work alarmingly well.
Play with it, and more than likely you'll find the cause. Androids wuv attention...
blackhawk said:
The laser AF is cool... took Sammy over a year to finally fix the Buds firmware but they did.
Samsung products aren't solid like Denon or Canon products. No support either compared to a top shelf company like Canon or Denon.
Though unlikely it could be a hardware issue or a bad flash especially if no one else has this issue.
Had a $6G Canon pro cam like that; no one could believe it had random glitches (including myself at times). It did. Canon finally replaced it.
It was a little bugger.
Most likely though it's settings, 3rd party app, cache or app corrupted.
If you have any cam updates try going back to the factory load version. This regression repair can work alarmingly well.
Play with it, and more than likely you'll find the cause. Androids wuv attention...
Click to expand...
Click to collapse
Ok, weird..
I never faced that issue on my N986U1 since I bought it. Maybe it's an factory issue.
tl;dr: I flashed to 11.0.7.1 which rendered the camera/torch unusable, only 9.5.11 should I try flashing back to the latest OxygenOS or rather use some custom ROM?
I was using the OnePlus 7 Pro I got a few months back used for ~200 EUR quite happily, except the front camera wasn't working (it pops up but the software freezes, keeps popping back and forth until I quit the camera app), which was probably somehow damaged by the previous user. We didn't discuss it, as he also didn't say anything about quite noticeable AMOLED Burn-in, cause he used the always-on navigational buttons... Something everyone should check when browsing through used deals.
I guess I was using the latest 11.0.6.1.GM21BA without issue, then the security patch and a few people on Reddit said their battery life improved, so I tried it.
All seemed fine, but the camera app has just thrown an error that the camera is damaged and I should go for repairs, torch in the quick menu said "Camera in use" so I did a backup and factory reset, which I recall I had to do in the previous update as well. But that didn't help. So in the angry rush, I said to hell with Oxygen OS and flashed cDroid, but there was the same issue there.
Finally using this great guide I managed to reflash to OxygenOS 10, but the issue still persisted. But with OxygenOS 9.5.11 finally, the camera works again. I didn't even put the phone online and I wanted to try upgrading to the latest OxygenOS 11 again, but I fear the issue will happen again.
Maybe OS9 somehow made the camera unstuck and unless I install the 'corrupting OxygenOS 10/11' and install rather some custom ROM it might be fine?
I will try later, I wasted too many valuable hours on this crap.
Googling in rage and reading other posts I see a similar camera issue happened across multiple OnePluses from 6 to 8. This really disappoints me and I'm sure I won't be looking for a used OnePlus ever again. Good thing I got a spare older OnePlus 5 for now.
Thanks for your testimony.
I indeed have this issue too. It appeared on June 10th. I tried to factory reset my phone yesterday and nothing changed.
I will also add that my front camera isn't working anymore since April. Can't figure out if this is software or hardware related
I really don't want to downgrade to OOS 9 but until the contrary is proved (by a fix or a comment by OnePlus), I would call it a case of planned obsolescence.
From now on I will keep my distance with this brand. Quite sad to admit because I was fond of their phones, but the management of issues / updates for the more dated ones isn't an example to follow anymore
klediouron said:
Thanks for your testimony.
I indeed have this issue too. It appeared on June 10th. I tried to factory reset my phone yesterday and nothing changed.
I will also add that my front camera isn't working anymore since April. Can't figure out if this is software or hardware related
...
Click to expand...
Click to collapse
Has your front camera stopped working after an update or during normal use?
It would make "sense" for OS 10+ to check if there is an issue with the front camera to disable all cameras altogether. Even if only to rush you into a repair shop...
I requested a repair which is in neighboring Poland, but they didn't wait for confirmation and requested UPS shipping from me right away.
I will check with them if the price would be within 50 EUR (from other posts not sure where in the world it was ~ 30 EUR if I recall correctly), then I'll get it repaired.