so I've had my OPO for around half a year now, and I had to replace the screen recently. but now whenever I open any app that uses the back camera, the entire phone crashes and reboots. also, with any camera utilizing app, I cannot focus at all. I have tried multiple different ROMS to see if it was a software issue. but the problem is still present.
I am currently running the official CM12s and have a 64GB model if that helps.
I made sure that I was careful when replacing the screen, I grounded myself before touching the phone. to my knowledge I did not damage the internals in any way.
I have lived with this issue for about a month now, and can no longer handle the crashes.
any help would be appreciated
P.S. I cannot get a replacement model as I did not get the phone off of the OnePlus site. (I got it brand new off ebay)
Open the dialer app, and type *#*#7378423#*#* to open the Service Menu, from there go to Service Tests and scroll down until you find Fingerprint test.
Please post the results here with your device model number (J8110, J9110, J8170), device build number (55.x.x.x.x), age of your device and whether or not you have issues with the fingerprint scanner.
Trying to figure out a pattern and it seems like XDA is more active (in comparison) than other forums for Sony devices.
Thanks.
J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.
iArvee said:
J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.
Click to expand...
Click to collapse
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?
MeltdownSpectre said:
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?
Click to expand...
Click to collapse
It works 90% of the time for me. Especially after I "trained" the fingerprint sensor. Basically open up the fingerprint settings, then constantly tap your finger, moving your finger slightly with each tap to cover your whole thumb.
IMO the update is fine! Well at least for me. I did a software reset after updating.
OTA updates fine Haven't tested out the dual sim, but I'm assuming it won't work. The only time I had to flash a new build was when I updated from Pie to 10, because I usually do a full wipe during a major update.
I'm using J9110 with latest stock EU firmware. The sensor does not work at all. Even weirder, there is no option to test the sensor in service menu and I cannot find fingerprint scanner in device options. Out of the box the sensor worked great, but gradually started failing after 1 year of use.
Update: I took some screenshots and compared them to other Sony device with working FPS - there is clearly something fishy going on.
The third screenshot is what happens when I launch Fingerprint Manager with Activity Launcher app and try to register a new fingerprint.
@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.
b1nly said:
@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.
Click to expand...
Click to collapse
Same thing as mine, it is completely dead and no longer works.
Already try repair with sony companion but nothing work
@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there
LoneWolfL4rs said:
@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there
Click to expand...
Click to collapse
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.
problem is same, fingerprint menu is gone.
J9110
build 55.1.A.12.28
anyone solved this problem? please share ..
Since new firmware 55.2.A.4.47, fingerprint works for 1hour, then just start detecting ton of wrong prints even without finger on the sensor, and shut down completely until the phone is restarted. FingerprintTest showing "NOT OK" at this time. FingerprintTest showing OK after a restart.
I'm so sad I'm not able to get Flashtool working to go back to previous firmware. The fingerprint was working really great for the last 10 months (first months were really hit or miss tho).
if u are on Android 11 now u can't downgrade to Android 10 anymore...u can but it's not working well anymore.!
i tried many times going back to Android 9 after updated to Android 10.
after flashing older Android 9 fw Gyroscope sensor isn't working anymore on lower version of Android
I succeed to revert back to Android 10, but it didn't solve the issue with the fingerprint. If you got some issue with another sensor, I will guess that the "drivers" for the sensor can be changed by an update but are not rolled back correctly, thus the creating issue or not solving mine since the faulty "driver" for the FP reader stay the same.
After a day of not even having the fingerprint management in the security options, Support asked me to do a forced reboot (volume up + power) to see if it solves momentarily the reader, there is a well known issue and they are working on a fix. It did solve the issue momentarily so I guess my FP reader is not completely dead (it was my conclusion seing it was still an issue once reverted to Android10) and I just have to wait for a fix.
thehumble1 said:
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.
Click to expand...
Click to collapse
Sorry for really late answer. Yes I updated to 11 right after it came out.
To prove the theory of update bricking it I bought a replacement sensor from AliExpress (when it arrived, it was clearly a new one, in OEM packaging) and it didn't work either.
In the process of replacement I accidentally broke the screen (because was really hard to replace, at least with my experience, way harder than battery, motherboard, etc.). So I really don't recommend trying this to anyone.
Now there is no point to downgrading, heh.
And no, on 11 firmware shutting the phone down completely or force reboot does not help. I tried everything I could before going for replacement, including full data wipe and disconnecting the battery with inside connector for some time.
Been having the same issue but I can get the fingerprint sensor to work sometimes after booting into safe mode and then booting normally, read that from another post somewhere but can't seem to find it. Mine also keeps disconnecting from LTE and drops to H+ and has been doing that a lot recently I hope that they will update some of this soon getting pretty frustrated with it, any of you been seeing that in addition to the fingerprint issue?
My fingeprint sensor on XPERIA 1 is there in menu but it is not working at all. Can't recognize my finger at all. Resset didn't help as well as restart to safe mode. I gess it is dead. Or is there something else wrong?
The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)
vantrung1_2 said:
The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)
View attachment 5431097
Click to expand...
Click to collapse
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem
Elysiumx said:
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem
Click to expand...
Click to collapse
So, the warranty on mine was over and they asked me 335 euro for "REPLACEMENT FRONT COVER WITH FINGERPRINT READER" (also change the internal fingerprint reader module)
According to them so it is a hardware problem, but at that price certainly not worth it to repair it.
Hi there!
First off: I used the search, but am not confident I haven't overlooked something.
If so I'm sorry!
I have a google pixel with lineage-for-microg, whose battery I had replaced some months ago.
Afterwards I wanted to reflash stock android to start afresh and then reflash lineage.
I'm back on lineage 17 (derived from Android10) and have the following problem:
During calls the microphone in speaker mode doesn't work at all, meaning, the person on the other side doesn't here a thing.
The same happens for speaker calls in other apps.
What still works, is audio in videos I take with the camera.
Also the ambient light sensor seems to have stopped working as the automatic luminosity doesn't work and I have to set the light by hand.
And then the proximity sensor during calls doesn't work.
I'd like to fix these and therefore I would like to find out, whether it is more probably a software or a hardware problem.
I found on this forum that it may have to do with the persist.img, that may have been corrupted by twrp.
Unfortunately I don't know where to get a hopefully working persist.img to try that out.
Things that are maybe relevant are these:
1. The battery was changed, so maybe the engineer doing that broke something
2. During reinstallation of lineage17 I had some problem with twrp not working. Afterwards using lineage recovery worked for installing lineage, but I'm not sure, twrp might have broken something.
3. The same issue also is there on stock android 10.
Can anyone point me in some direction?
I realized that the easiest check for software/hardware distinction would be to just flash a new persist.img.
Is anybody out there, that has a pixel sailfish device with working android 10 that would drop me a message? I should be able to just transplant your persist.img to my pixel sailfish.
I would greatly appreciate it!
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Bongzerker said:
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Click to expand...
Click to collapse
Nonetheless, thanks for your time!
If I may ask for even more of it:
Not sure, whether Pixel XL and Pixel are similar when it comes to their hardware ( I have a Pixel, not a Pixel XL), but if you have repaired many of them, do you think it is at all possible, that the hardware shop that changed my battery somehow broke these sensors or forgot to reattach a cable to them?
I don't plan to hold them accountable, as I really like them, just would like to have a hint, whether going to the hassle of bringing my phone there and thus not having it for a few days has a reasonable chance of success.
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.
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.