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.
Well this really sucks. I've been telling people for a long time that my G5 has been the best phone I've ever had...a true powerhouse. Then came the Nougat update. Since then it's been nothing but problems. I called Verizon, LG (useless), and Google. All said 'try a factory data reset, that should fix everything'. Yeah, right. So after the Ohhhhhhh-so-painful FDR, I still have all the same problems. When plugging in the oem or third party fast chargers (I have two of each), the notifications will simultaneously say "slow charging" and either "charging" or "fast charging" at the same time. Unplugging and reconnecting will fix it every time. Also, I'm getting ghost images when changing screens...I can still see a shadow of the previous screen which eventually fades away. These are both just minor annoyances, but still weren't there before. But also, my NAV appears to have a hard time keeping track of where I am. More annoying. But the biggie is that I can no longer use any of my many Bluetooth headsets for phone calls. You just can't have a Bluetooth conversation anymore. Streaming audio is fine. But calls aren't doable. That's a problem. Since I already tried an FDR to no avail, Verizon is going to send me a new phone. All I can say is if it comes with Marshmallow, I'm leaving it that way. Any benefits that Nougat brought are far outweighed by the problems. I'll wait until they fix it, maybe then. Anybody else been so plagued by this update?
D Dave
I have the same problem.. I have to charge and re-start the phone to make the phone "charging" otherwise it is intermittently connected and disconnected.. I've done factory reset and didn't work out also.. I guess getting a new replacement from T-mobile is the option here.
I got the new phone that Verizon overnighted to me and got it all set up. It thankfully came loaded with marshmallow and is working fine, but keeps prompting me to install Nougat. I'm going to keep postponing the update for now to give them a chance to work the bugs out. Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
I have the charging issue as well and it started with 7.0.
You should report it. They won't fix something if only a couple people report the problem. They sent me a new phone and I've managed to defer the 7.0 update for over a week now. It prompts me everyday, but I just say later! I'll wait awhile to see if they fix it. The unbearable Bluetooth call quality was just totally unacceptable.
Nougat?
My G5 is still on Marshmallow, and does not see that there is any update to Nougat available. So what are you all talking about?
What carrier are you with? I'm on Verizon, so maybe not all carriers have it yet. Or maybe you're one of the lucky ones who wasn't randomly chosen to be a guinea pig and find all the bugs and glitches. ☺
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Dangerous Dave said:
Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
Click to expand...
Click to collapse
Me, totally problem free. No problems of any kind but it did fix one bug, I had an app that wouldn't run in Marshmallow and it's back working normally again with Nougat, who knows why?
jpradley said:
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Click to expand...
Click to collapse
Try to keep up.
I have the G5 on Verizon and am fully updated. The only problem I've had is with storage space. 85% full and I'm lagging frequently. I've deleted as much as I can, to no avail. I can't seem to get anything successfully moved to the SD card, so I'm not sure of its purpose.
I´ve got exactly the same problems and more.... What did you do to fix them in the meantime?
To add another problem, my fingerscanner isn't working 9 out of 10 times.
It became an annoying piece of ****! Please help to get my awesome phone back.
Greetz from the Netherlands
I've had other bluetooth issues... I have to restart bluetooth nearly every day to get it to connect to my devices, it's as if the bluetooth apk is hanging up in the background.
That said... My phone updated to 27A this morning, so I guess I'll find out in the next few days if I have the same problem, lol
Well the 27A update must literally be ONLY the security patch. It didn't fix the bluetooth issues...
Seriously this update has been the worst. I too am experiencing the power cable issue. I'd say 7 out of 10 times it tells me it's slow charging. Simply reseating the cable fixes it every time. The most frustrating part for me is Facebook and Twitter. With the first Nougat update the Facebook app began to bug out. At least once a day it randomly crashes, even when i'm not actively on it, and begins a crash loop that won't stop until I restart the phone. that usually fixes it. I'd say every other week I've had to straight up re-install the FB app to fix the crash loop. and now after the recent update that was pushed the twitter app keeps failing to load some images. Most tweeted images show up fine but profile/banner images will not. Again fixed with a restart. This is really quite frustrating. I don't understand what they did to break Nougat so badly. My friends Pixel hasn't had any of these issues. I'm getting so fed up with my G5. I love it but it just so damn locked down and now this. It really makes me wary of getting another LG phone
Well, it's been over three months since I started this thread. The problems after the Nougat update were just unacceptable, so Verizon sent me a new phone loaded with Marshmallow. I've been deferring the update every day for three months. Last night I accidentally tapped the wrong spot on my screen and it installed the damn Nougat update. I've had the update less than 24 hours now, so haven't tried everything. But I can tell you they haven't fixed the problem with the slow charge/fast charge, as it came back IMMEDIATELY after the update. I called Verizon today to ask why the hell LG couldn't fix that issue in three months time! Verizon called LG for me and inquired if there was a fix. LG said if I send the phone back to them, they'll fix the corrupted files and send it back to me. Really?!? Both my G5s experienced the same problem immediately after the update and they couldn't fix the issue in the download in three months time? Douchebags. Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Dangerous Dave said:
Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Click to expand...
Click to collapse
Unfortunately don't have anything helpful for you, other than to say, you're not alone, and I similarly got sufficiently pissed with this bug today to see if there was a solution yet.
Pretty sure you answered your own question though: they don't actually have a fix because LG has likely stopped developing new releases for the G5 in anticipation of the G6 release. They want you to send it back to them for the "fix" because it's a pain in the ass and transfers the opportunity cost onto you, which hopefully (in their eyes) means they can do absolutely nothing.
I'm just.... beyond frustrated with this ****ing phone. I really wish that I would have limped by on my old HTC M8 until the V20 came out, even with its barely-chargeable battery. At this rate, I would have been better off with a pixel or internal-battery phone for that matter. There is just seemingly no end of software and hardware issues with this phone, and LG's piss-poor customer service gives you almost no recourse for any of them
Hi. G5 VS987 Owner here with a build date of 10/2016 so I've managed to survive the bootloop issues that plagued a great number of us thus far.
My theory is: LG has no clue on how to push an OTA update.
My question(s) are: How many of you updated with the OTA?
And how many updated via LG Bridge or some other flashable method?
I'm wondering what if any difference knowing this makes because while this phone has honestly been the best/fastest/bug free phone I've ever used...the update nagscreen has me wanting to choke the [email protected]!%# out of it. It just won't go away.
I really wanted the Note 7 before they blew up...What to do guys?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Another thing...is there a way to flash back to MM if this update really goes south?
I updated to Nougat OTA with no problems except the power cord which I fixed.
Here's how I did it:
DISCLAIMER! I KNOW this has nothing to do with the problem and cannot possibly fix it but... it did fix it for me so give it a try, OK?
1. When you get the slow charging message look at the power cord, turn it around and plug it in the other way, see if that helps. Once you've determined that plugging the power cord in one way reduces the frequency of the error just keep on doing it that way and in a couple of days the problem will be gone!
I know, I know, but try it, what can it hurt?
Well, interesting update here. Verizon said I could send it back to LG to have corrupt files replaced. I decided that neither option, living with the problem or shipping the phone back to LG, was acceptable. I called Verizon back and told them so, asking for a replacement and hoping it would come with MM. They just sent me a replacement, and it came with Nougat already on board. But would you believe this phone works perfectly! I mean, it rocks! I have NONE Of the problems I had with the last two phones after the OTA update. So maybe the OTA really is a piece of crap. But I gotta say, it's nice to love my phone again.
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:
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.
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.