Related
Hi, I want to share my experience with a Nexus 7 2013 which bought to me a friend in USA (I'm from Spain).
It is made in China, June, and it has every touch problem described here: maps rotate, multi-touch with only 2 fingers, Swype keyboard problem (the draw was continuously cut off), the screen didn't recognize my finger, and sometimes ghost pulsations.
Well, I sent the tablet to the tech support and today is back.
The report says:
Problem: Touch Screen Function Error
Replaced part: LCD + Front + GPS module
Note the Gps module replaced which I didn't referred.
Now everything is ok and screen works without problems. And all of this with the J compilation.
Clearly, my experience indicates that the Nexus problem is a hardware problem, and Asus knows perfectly the problem.
Cheers.
Enviado desde mi Nexus 7 usando Tapatalk 4
threepwood960 said:
Hi, I want to share my experience with a Nexus 7 2013 which bought to me a friend in USA (I'm from Spain).
It is made in China, June, and it has every touch problem described here: maps rotate, multi-touch with only 2 fingers, Swype keyboard problem (the draw was continuously cut off), the screen didn't recognize my finger, and sometimes ghost pulsations.
Well, I sent the tablet to the tech support and today is back.
The report says:
Problem: Touch Screen Function Error
Replaced part: LCD + Front + GPS module
Note the Gps module replaced which I didn't referred.
Now everything is ok and screen works without problems. And all of this with the J compilation.
Clearly, my experience indicates that the Nexus problem is a hardware problem, and Asus knows perfectly the problem.
Cheers.
Enviado desde mi Nexus 7 usando Tapatalk 4
Click to expand...
Click to collapse
What I don't understand is if that was the case there would be a lot of perfect ones out there. They should call for a recall if you have a certain date of the bad batches. This is how it should be done. If you bought it from Best Buy then best buy should be getting good batches for exchange. With reciepts still. I am over my 15 days now. 2nd of all I just don't believe that this is hardware. I had a perfect screen for 15 days then this update destroyed it. HMMMMMMM doesn't make sence. It is software issues thats going on.
I think what Asus is doing is recieving your Nexus 7 and istalling the proper drivers for the screen it has in it. The next update that comes out will destroy it again and again till you get tired of this crap.
threepwood960 said:
Hi, I want to share my experience with a Nexus 7 2013 which bought to me a friend in USA (I'm from Spain).
It is made in China, June, and it has every touch problem described here: maps rotate, multi-touch with only 2 fingers, Swype keyboard problem (the draw was continuously cut off), the screen didn't recognize my finger, and sometimes ghost pulsations.
Well, I sent the tablet to the tech support and today is back.
The report says:
Problem: Touch Screen Function Error
Replaced part: LCD + Front + GPS module
Note the Gps module replaced which I didn't referred.
Now everything is ok and screen works without problems. And all of this with the J compilation.
Clearly, my experience indicates that the Nexus problem is a hardware problem, and Asus knows perfectly the problem.
Cheers.
Enviado desde mi Nexus 7 usando Tapatalk 4
Click to expand...
Click to collapse
I'm happy they fixed your touch screen issue, I'm thinking about having my n7 sent to be repaired too because ts10 helped a lot but it still doesn't feel 100% fixed.
Does your nexus feel solid and one piece like it did out of the box? I'm worried about having the screen feel like it could detach if they replace it.
I would like to see people start putting pictures of the paper work for this problem. Meaning the paper they send back with your tablet saying it is a defective screen or digitizer. Then we need to do something to get a replacement. Not sending it off. Exchanges at retail stores.
I have now the Q compilation with root and unlocked, and the touch screen is ok still. I don't see anything different to the original product (when I opened the box), but I think they exchange the screen and GPS, as they told me.
threepwood960 said:
I have now the Q compilation with root and unlocked, and the touch screen is ok still. I don't see anything different to the original product (when I opened the box), but I think they exchange the screen and GPS, as they told me.
Click to expand...
Click to collapse
Hi! Thanks for the info, i might be sending my nexus 7 for replacement too.
Could you maybe try this app to check if the touchscreen problem persists? if it's not too troublesome for you of course! :good:
http://forum.xda-developers.com/showthread.php?t=2449612
RMA'd mine for touch-screen issues. Getting it on Monday, will report my experience with it then. This post makes me optimistic that it will actually be fixed
potofgold said:
Hi! Thanks for the info, i might be sending my nexus 7 for replacement too.
Could you maybe try this app to check if the touchscreen problem persists? if it's not too troublesome for you of course! :good:
http://forum.xda-developers.com/showthread.php?t=2449612
Click to expand...
Click to collapse
I tested it already and the screen gets crazy. But I think this app is a fake, isn't it?
Certainly, my screen now respond without any problem, similar as in my Nexus 7 2012.
WackyClash said:
RMA'd mine for touch-screen issues. Getting it on Monday, will report my experience with it then. This post makes me optimistic that it will actually be fixed
Click to expand...
Click to collapse
When I sent my tablet to the tech support I was worry too. But as I say, the result was the best possible. Good luck!
threepwood960 said:
I tested it already and the screen gets crazy. But I think this app is a fake, isn't it?
Click to expand...
Click to collapse
Dude, read the description! It is NOT test app. It is showing (simulates) bad touch so you can compare it with your device.
Nothing more, nothing less.
Please show me the sentence which is saying that. I am reading this desciption totaly different.
Gesendet von meinem GT-I9300 mit Tapatalk 4
Bad news. The problems are back. I have discovered it with Swype keyboard, and confirmed with Maps and the app Paint Kids:
https://www.youtube.com/watch?v=6KDk0keD6Uc&feature=youtube_gdata_player
My happiness was for less than one week.
Bought mine a week ago. Worked perfect until i installed JSS15R yesterday, now im experiencing a touch freezes and random doubletaps
threepwood960 said:
I tested it already and the screen gets crazy. But I think this app is a fake, isn't it?
Certainly, my screen now respond without any problem, similar as in my Nexus 7 2012.
Click to expand...
Click to collapse
hmm, since the app creator figured out how to replicate the problem by simply displaying a certain image in fullscreen, so i was wondering if a replaced touchscreen would solve the problem. but i guess not..
Thanks for your help though!
threepwood960 said:
Bad news. The problems are back. I have discovered it with Swype keyboard, and confirmed with Maps and the app Paint Kids:
https://www.youtube.com/watch?v=6KDk0keD6Uc&feature=youtube_gdata_player
My happiness was for less than one week.
Click to expand...
Click to collapse
I knew it. I found something out last night. Mine works perfect if its on a hard surface like a wooden table. If I put it on my couch or lay it on any cloth type material it has dead spots on typing. Mine is in a slimline Moko case. This is tested without holding it and unplugged. Touching the screen with one finger and hand only.Type real fast on each letter and they drop out touches.Like I said it works perfect now.
potofgold said:
hmm, since the app creator figured out how to replicate the problem by simply displaying a certain image in fullscreen, so i was wondering if a replaced touchscreen would solve the problem. but i guess not..
Thanks for your help though!
Click to expand...
Click to collapse
Shure it would help, but exchange for another better type of screen/toch combo :/
But i think cleaning an touching ang cleaning help.. mine is a lot better than it was on a first day (with a same ROM).
Cleaning a cache in my case Cruselite TPU with antistatic cleaner helped, too I think
Butt "some jittering remins" its hard to pickup icons to move "icons"... As nexus mean i move or tap the finger..
threepwood960 said:
Bad news. The problems are back. I have discovered it with Swype keyboard, and confirmed with Maps and the app Paint Kids:
https://www.youtube.com/watch?v=6KDk0keD6Uc&feature=youtube_gdata_player
My happiness was for less than one week.
Click to expand...
Click to collapse
Take your Nexus 7 out of the case and lay it on a nice wooden hard surface and retest the screen. Mine works perfect on hard surfaces only.im thinking it could be the digitizer flexing or the wireless charging coils causing the problems.
The previous video was recorded before I sent the tablet. As it is shown it worked in a terrible way. Now is something subtle, because it only fails sometimes and mainly on hard surfaces.
It is strange, before to tech support it failed each second. Now, I can be swyping several minutes and it doesn't fail, and in other moment it fails 1 out of 10 words.
I will try to update to R compilation (I have the Q) and I will tell you.
Hi i am using stock rom on moto x play indian edition dual sim.
From 2-3 days sensor is not working. No automatic brightness working. No auto rotate working. Please help me
I have also check by going in test mode with *#*#2486#*#*
And it showing proximity sensor is disabled :crying:
HuzefaChalla said:
Hi i am using stock rom on moto x play indian edition dual sim.
From 2-3 days sensor is not working. No automatic brightness working. No auto rotate working. Please help me
I have also check by going in test mode with *#*#2486#*#*
And it showing proximity sensor is disabled :crying:
Click to expand...
Click to collapse
Any chance that you have a screen protector installed and it's blocking the sensor?
Yes i have a screen protector. But it doesn't cover sensor
Before 2-3 days it was just working fine even with screen protector.
And now suddenly it's not working.
Same here guyz. WIth stock 6.0.1 latest update, i think mostly all sensors are behaving erroneously. Any one knows the solution for this irritating daily problem.
Any fixes guys ? My proximity, rotation sensor stopped working suddenly today. Tried factory reset as well. Not helping. No screen protector or case! Any fixes ?
vampire36 said:
Any fixes guys ? My proximity, rotation sensor stopped working suddenly today. Tried factory reset as well. Not helping. No screen protector or case! Any fixes ?
Click to expand...
Click to collapse
Same thing happened with mine as well. It was 6 months ago. I tried almost everything possible like factory resets (multiple times), soft restarts, reboots, rooting, installing N, then again coming back to stock ROM MM 6.0.1. But nothing worked. Proximity and other sensors are dead. So be prepared....
harykishan said:
Same thing happened with mine as well. It was 6 months ago. I tried almost everything possible like factory resets (multiple times), soft restarts, reboots, rooting, installing N, then again coming back to stock ROM MM 6.0.1. But nothing worked. Proximity and other sensors are dead. So be prepared....
Click to expand...
Click to collapse
Crap thats such a pain! Now moto display doesnt work and calls have become a pain! Guess time to move to next phone
vampire36 said:
Crap thats such a pain! Now moto display doesnt work and calls have become a pain! Guess time to move to next phone
Click to expand...
Click to collapse
Looks like your phone is infected with blood cancer which is flowing into all parts of it
For me it was just with the sensors...rest of all were absolutely fine. For a company like motorola, this kind of bugs in sw are pathetic and not to have.
Finally after a long 6 months pain, and wasting lot of hours on research, I went back to my old trusted Samsung Galaxy phone. Never will own again a Moto!!!
My light sensor stopped working last evening.... Tried going back to 5.1.1, 6.0.1 and 7.1* but no avail, guessing it's a hardware failure
isene said:
My light sensor stopped working last evening.... Tried going back to 5.1.1, 6.0.1 and 7.1* but no avail, guessing it's a hardware failure
Click to expand...
Click to collapse
I broke my head for almost 6 months figuring whether this behaviour was a hw failure or sw failure. I lost my peace and lot of hours (trying to fix and figure out) with these sensor deaths on moto x play. Had lot of respect for moto. Now you can understand how i treat it. Noting solved. So my kind and wise suggestion for you would be to try all your trials to restore it - but only once!!! If they don't work at first try, they will never come alive again!!!
Few days ago i fell back to my trusted Samsung Galaxy J7 (by exchanging my moto x play with J7). Peace restored.
I will for sure get scared to go for any Moto devices. Period.
Thank me if these words of experience are helpful to you.
harykishan said:
I broke my head for almost 6 months figuring whether this behaviour was a hw failure or sw failure. I lost my peace and lot of hours (trying to fix and figure out) with these sensor deaths on moto x play. Had lot of respect for moto. Now you can understand how i treat it. Noting solved. So my kind and wise suggestion for you would be to try all your trials to restore it - but only once!!! If they don't work at first try, they will never come alive again!!!
Few days ago i fell back to my trusted Samsung Galaxy J7 (by exchanging my moto x play with J7). Peace restored.
I will for sure get scared to go for any Moto devices. Period.
Thank me if these words of experience are helpful to you.
Click to expand...
Click to collapse
The sensors are solderd to the motherboard which means to restore a faulty sensor you will have to replace the whole board.... or have the patience and skill to desolder/deflow and solder/reflow the sensors which is a prety delicate practice
isene said:
The sensors are solderd to the motherboard which means to restore a faulty sensor you will have to replace the whole board.... or have the patience and skill to desolder/deflow and solder/reflow the sensors which is a prety delicate practice
Click to expand...
Click to collapse
Agreed. I have even got that done with experts here. But the board of Moto x play is so thin like a paper!!! This makes it much more worse. So, avoid getting any hw soldering jobs on moto boards. They are not like samsung boards. I even had multiple visits to Moto service here in Bengaluru, but everytime they only suggest me to replace the complete board. Moto service is pathetic!!!
I now do have enough experience and wisdom on these matters. Please keep posted here if you still try meddling with your board and the results.
sensors off
I just buy this phone, from a woman, 70 bucks, and i noticed just now my 2 sensor r off - light and proximity - on andorid 6.0.1 .... so this is seriously ****, sensor r f..ed up after update to andorid marshamloow only? they will dont work when i downgrade to andorid 5?
I just dropped it off at my reseller within warranty.
Flashed everything back to stock, with no unlocked bootloader warnings.
So hopefully they will repair it within warranty (Netherlands) because it's a hardware failure for sure
miss5tability said:
I just buy this phone, from a woman, 70 bucks, and i noticed just now my 2 sensor r off - light and proximity - on andorid 6.0.1 .... so this is seriously ****, sensor r f..ed up after update to andorid marshamloow only? they will dont work when i downgrade to andorid 5?
Click to expand...
Click to collapse
Sorry to hear that buddy. Ya, Moto X has this tendency and it is very much inline with moto upgrades faulty sensors with Marshmallow. I even went back and reflashed to stock lollipop (and even locked back bootloader and removed the bootloader unlocked warnings), but nothing worked.
Try your luck and post it here.
For me it was sure a hardware damage!!! but not sure how software can damage hardware. I will stay away from Motos for the rest of my life. I am very happy with my Samsung Galaxy.
---------- Post added at 04:23 PM ---------- Previous post was at 04:17 PM ----------
isene said:
I just dropped it off at my reseller within warranty.
Flashed everything back to stock, with no unlocked bootloader warnings.
So hopefully they will repair it within warranty (Netherlands) because it's a hardware failure for sure
Click to expand...
Click to collapse
That sounds good and bad as well. Good part is they took your mobile to fix it.
Bad part is, here in India before even touching my mobile they asked for IMEI numbers of my mobile. They key-in these in their testing software and boom there they go. They found that my device's bootloader was unlocked and rooted. With this info they rejected to even touch my mobile.
Not sure, if you lock it back after unlocking once, will the status really be locked even in their software??? If yes, its good news again.
If no, they simply hold your device for a week or so, and return it back with the same reason.
So my suggestion is you double-check whether they replace the entire board or not. Also, keep periodically finding out the current status of the replacement.
harykishan said:
That sounds good and bad as well. Good part is they took your mobile to fix it.
Bad part is, here in India before even touching my mobile they asked for IMEI numbers of my mobile. They key-in these in their testing software and boom there they go. They found that my device's bootloader was unlocked and rooted. With this info they rejected to even touch my mobile.
Not sure, if you lock it back after unlocking once, will the status really be locked even in their software??? If yes, its good news again.
If no, they simply hold your device for a week or so, and return it back with the same reason.
So my suggestion is you double-check whether they replace the entire board or not. Also, keep periodically finding out the current status of the replacement.
Click to expand...
Click to collapse
In The Netherlands and the rest of Europe there is a law about warranty.
The manufacturer must be 100% sure the flaw is caused by unlocking and flashing custom firmware, if they can't prove this 100% they must fix the issue under waranty. <== TL;DR of the law
Source (31999L0044)
I know for sure this problem isn't caused by a unlocked bootloader because it's unlocked from the start without problems.
Oh wow.. are the sensors of all moto x play failing now ?? because mine light and proximity sensors are also not working since last few days..!!
Wonder if this is a strategy by Motorola to disable sensors after certain period of owning
LOL Jk..
Moto hardware and software both are crap. Now we all practically know why google sold it off to chinese.
harykishan said:
Moto hardware and software both are crap. Now we all practically know why google sold it off to chinese.
Click to expand...
Click to collapse
by your logic, Volvo are crap too.
Just wanted to report that my sensors are also dying/dead. A week ago my vibration motor died, and a few days ago my proximity sensor and brightness sensor died, so now my screen is stuck at maximum brightness.
Even disabling auto brightness, the screen is stuck at max brightness, so it's likely more than just the sensor that died, but also some circuiting. I can tolerate no vibration, but once I was left using my phone with max brightness all the time, I said screw it. Hurts my eyes too much, especially at night.
I bought a Moto G5 Plus to replace this one. Hopefully it survives longer.
Had the screen replaced on my MiA1 recently.
Initially when I got it back the fingerprint sensor worked, but seemingly not as well as it had. I put it down to the hot weather. Now, 3days later it's not working at all
Could this be related to the screen repair? (Assuming yes), if so, is it a fix I can do myself out do I need to try argue it out with the shop?
Ta
Sent from my Mi A1 using Tapatalk
vaderag said:
Had the screen replaced on my MiA1 recently.
Initially when I got it back the fingerprint sensor worked, but seemingly not as well as it had. I put it down to the hot weather. Now, 3days later it's not working at all
Could this be related to the screen repair? (Assuming yes), if so, is it a fix I can do myself out do I need to try argue it out with the shop?
Ta
Click to expand...
Click to collapse
open back cover
check fingerprint connector attached or not....its very simple....
Silly question maybe but is there any instructions on removing the back cover??
Sent from my Mi A1 using Tapatalk
For some reason, I just can't unlock my phone with my left thumbprint. It works perfectly with my right one. I've removed and re-added my left fingerprint several times. Sometimes up to 3 copies of it. Regardless of what I do, it will not unlock with the left one.
Sent from my ONEPLUS A6013 using Tapatalk
Did you try another finger?
Maybe your device is not accepting a second finger, but trying 3 times the same thing is not helping to isolate the "problem"
ledvedder said:
For some reason, I just can't unlock my phone with my left thumbprint. It works perfectly with my right one. I've removed and re-added my left fingerprint several times. Sometimes up to 3 copies of it. Regardless of what I do, it will not unlock with the left one.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N9005 using Tapatalk
I have the same issue with my left finger, not entirely useless but it is much more difficult to use it.
I had that issue when I was using 9.0.5, it works sometimes with my left thumb, but works perfectly fine with my right thumb .
After updating to 9.0.6, I decided to remove all my fingerprints and re-add them, and now it works fine.
Give it a try if you have updated to 9.0.6.
I did actually, removed all of them and readded them in a dark room.. again I have the same behaviour. It's not that frustrating because I also have face unlock and the right finger but....
Same issue here and at least now I know I'm not alone. Right thumb works fine Everytime yet left works maybe 5pct of the time, or less . It's very frustrating
Same for me. I added both thumbs and both index fingers. Only my R thumb (the one I use 90% of the time) works reliably. I've tried deleting and re-adding the other fingers multiple times without effect, but I haven't tried since the upgrade to 9.0.6
Re-did my fingerprints on 9.0.6, now all 4 work. Could be a coincidence.
CUBENSIS said:
Re-did my fingerprints on 9.0.6, now all 4 work. Could be a coincidence.
Click to expand...
Click to collapse
I did the same and it still isn't working for me.
Sent from my ONEPLUS A6013 using Tapatalk
jeff7424 said:
I had that issue when I was using 9.0.5, it works sometimes with my left thumb, but works perfectly fine with my right thumb .
After updating to 9.0.6, I decided to remove all my fingerprints and re-add them, and now it works fine.
Give it a try if you have updated to 9.0.6.
Click to expand...
Click to collapse
I will try this! I'm on 9.0.6 and gave the same issue with my left thumb. Thanks!
In my case I added three different fingers and had no issue with any so far. Of course it hasn't the fast response of the regular fingerprint readers but is not that bad.
CUBENSIS said:
Re-did my fingerprints on 9.0.6, now all 4 work. Could be a coincidence.
Click to expand...
Click to collapse
A day later my other 3 fingers have stopped working again. Frustrating. R thumb still working well
CUBENSIS said:
A day later my other 3 fingers have stopped working again. Frustrating. R thumb still working well
Click to expand...
Click to collapse
I've seemed to notice that the angle must have to be exactly how one of the prints was recorded. Even with this, I can only get it to work 20pct of the time .
I'd much rather have a dedicated print reader like my v30
Had same issue. Only one finger working consistently. I just changed the wallpaper back the original one it shipped with and the scanner issue has resolved!
I'm pretty sure I read somewhere that the fingering reader is a learning type, so the more you use it the more it recognizes what produces failed and successful attempts. It's quite possible that we're just not using our left thumb as often and that the algorithm doesn't necessarily differentiate right from left, but just knows what the different prints look like, which ones to accept and which ones take priority in the line to make more accurate. This might be something worth sending OnePlus feedback on.
So far I think OP should really optimize whatever can be done in software to be more forgiving of different angles. If the angle is the same, the reader works always and fast. So it's entirely capable of reading fingerprints correctly. Why are the "regular" readers not having problems with different angles is beyond me and I suspect (and hope) it has to do with software.
To be honest I fail to see how the reader could be "learning". If it doesn't unlock there is no mechanism to tell the system that the finger was correct. If it does unlock there is no way to tell it if/when (hopefully never) it shouldn't have.
So what could it be learning from, I don't get it.
gorman42 said:
So far I think OP should really optimize whatever can be done in software to be more forgiving of different angles. If the angle is the same, the reader works always and fast. So it's entirely capable of reading fingerprints correctly. Why are the "regular" readers not having problems with different angles is beyond me and I suspect (and hope) it has to do with software.
To be honest I fail to see how the reader could be "learning". If it doesn't unlock there is no mechanism to tell the system that the finger was correct. If it does unlock there is no way to tell it if/when (hopefully never) it shouldn't have.
So what could it be learning from, I don't get it.
Click to expand...
Click to collapse
Actually in coding I'm pretty sure anytime something receives an input value it gives an output. Something happens from the moment the scanner realizes there's an object waiting to be scanned, it produces some kind of expected coded result which causes this or that particular activity to happen or not happen. It isn't that difficult to see how it could be storing particular information to "learn" from.
Has anyone tried replacing the stock screen protector or removing it completely to see if that affects the fingerprint scan behavior?
I think you guys are just more coordinated with your right thumb so you place it perfectly everytime but when it comes to the left one which in sure you rarely use it's more difficult. I would suggest just using your left thumb for a day or 2. Then see if it improved
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
i7vSa7vi7y said:
I think you guys are just more coordinated with your right thumb so you place it perfectly everytime but when it comes to the left one which in sure you rarely use it's more difficult. I would suggest just using your left thumb for a day or 2. Then see if it improved
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can confirm that training sessions for my left thumb, after initially registering it, helped immensely. Whether the reader was trained, or I was, or both, is a matter of some debate. [emoji106]
Sent from my ONEPLUS A6013 using Tapatalk
I am using oneplus 5 more than 1 year now. But 2 months back, suddenly it started hanging like crazy. I tried to reboot, it was even hanging in the reboot. (I have never rooted device and I was on android oreo 8.1.0 and Oxygen OS 5.1.6).
After that, I visited oneplus's two different service centers, both did the same thing. First, they flashed/wiped my phone to factory reset then they checked the hardware. Both said that there is something wrong with hardware so they need to change motherboard which will cost around 2/3 cost of the whole phone. When I asked about the specific problem in hardware, they said they are not sure but the problem will be resolved once the motherboard will be changed.
As I didn't want to spend that much on the repair I tried a few things myself. I tried downgrading Oxygen OS to 5.1.5 and to my surprise my phone was started working normally again. But after 1 week it started hanging again. After that I have tried almost everything like clearing cache, factory reset the phone, downgrade Oxygen OS, upgrading OS to the beta version, now to latest OS 5.1.7 but it was same.
One thing that surprises me that it starts working normally randomly for 1-2 days then it goes back to hanging. It happens randomly and happened 7-8 times till now.
Last night I rooted my device to see if anything will change but it was of no use. My device was hanging like the same. Guys, please help me what should I do?
Did it start lagging even after factory reset(no 3rd party apps installed) or after you install apps/restoring backups?
strongst said:
Did it start lagging even after factory reset(no 3rd party apps installed) or after you install apps/restoring backups?
Click to expand...
Click to collapse
It started hanging soon after factory reset , even before taking backup or installing any third party app.
My mom had an HTC one x years ago and after a couple years it started lagging really bad. She gave it to me when she got her new phone, even after a full wipe it still lagged and eventually started rebooting under load. I assume it was a motherboard problem in that case and possibly in yours also.
Sent from my ONEPLUS A5000 using Tapatalk
They've identified a motherboard issue. The same thing happened to my OP3. Unfortunately, there is no coming back from that. Like you, I tried different firmware, ROMs, settings, sim card, etc... Nothing you will do with software will fix your issue which is hardware.
After two months, I sold my OP3 for parts and bought a used OP5.
digger16309 said:
They've identified a motherboard issue. The same thing happened to my OP3. Unfortunately, there is no coming back from that. Like you, I tried different firmware, ROMs, settings, sim card, etc... Nothing you will do with software will fix your issue which is hardware.
After two months, I sold my OP3 for parts and bought a used OP5.
Click to expand...
Click to collapse
Thanks for info man. I think I will have to do the same
350Rocket said:
My mom had an HTC one x years ago and after a couple years it started lagging really bad. She gave it to me when she got her new phone, even after a full wipe it still lagged and eventually started rebooting under load. I assume it was a motherboard problem in that case and possibly in yours also.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I was told at the service center. I think I will have buy a new device
No no. What you do is buy one from eBay with a broken screen that's not blacklisted and swap the motherboard. It's around $100
godkingofcanada said:
No no. What you do is buy one from eBay with a broken screen that's not blacklisted and swap the motherboard. It's around $100
Click to expand...
Click to collapse
That's a great idea man, Thanks. I will try this. Now I just need to find cheap oneplus 5 with working motherboard and a skilled technician who can swap motherboards.
abhishektejan said:
That's a great idea man, Thanks. I will try this. Now I just need to find cheap oneplus 5 with working motherboard and a skilled technician who can swap motherboards.
Click to expand...
Click to collapse
It's not too hard to swap. It's just opening the phone that is a pain. This new glue things together is no fun.
I don't think the OnePlus 5 is glued together. It's just really tight clips that appear to be even harder to get open than the glue used in the iPhone's. (I just replaced the screen in my girlfriend's IPhone 6s and also opened up an iPhone 6 I am replacing the screen). Despite having cracked screens they came open pretty easy, just slice through the glue with your opening tool. Watching the videos the OnePlus has no glue but appears to be much tighter than the iPhone's.
I'm replacing the battery and charging port in mine soon so I can let you know how it goes. The battery is down to 81% health and dash charging isn't working anymore. It still can last 2 days despite the battery health drop so I'm not in a rush.