My Moto G5S XT1792 had overheating problems since I bought it 9 months ago but I considered it a "feature" and that Motorola would not admit it was a problem. The phone would get severely hot when using GPS and 4G at the same time.
But then, overnight, the battery bulged and raised the screen out of its frame! Finally, the battery was replaced under warranty.
Since the replacement, the battery is lasting many hours more and the phone is barely getting warm even when charging under turbo charge. I am in love with my Moto G5S again.
The normal response of the fingerprint is to vibrate and then either lock or unlock.. Or, if the finger is not recognized, it vibrates and a message is displayed.
My setting is to use the fingerprint sensor as navigation button ("One Button Nav" under Moto Actions Settings).
But when my phone is being charged, the fingerprint sensor becomes erratic. If I try a sequence of lock and unlock fingerprint procedures, giving a few seconds after each retry, many times the sensor does not respond as expected. It becomes a trial and error: sometimes it works, sometimes not. Sometimes the navigation commands are recognized (swipe left and right, quick press).
It seems that this erratic behavior is not common because I could not find other users complaining about it. I wonder if my fingerprint sensor was damaged because of the overheating problems I had since I bought the phone or maybe during the battery replacement.
I would like you to try a sequence of lock/unlock fingerprint procedures while using the original AC charger in your phones and let me know if you experience the behavior I described above.
I want to get more feedback before I request a screen replacement under warranty.
Thanks!
This is not uncommon with charging phones, and is due to interference from your big, water containing body, and the AC power ground loop, on the capacitive finger print sensor. Some phones, houses, chargers and people are more or less susceptible.
Try charging from a DC source (battery bank) if you have one, and see if the problem goes away. There isn't much that you can do about it, and I probably wouldn't bother myself with it anyway, to be quite honest.
Related
Does anyone else have weird touchscreen issues when charging their device? It only happens after you charge your device. You're gone for a few hours and when you come back to unlock the device, the screen is not responsive (the lockscreen for example rubber bands back). Sometimes, the capacitive buttons don't work. So far, locking and unlocking the device fixes the issue.
I'll just like to know if it's a general problem or a problem specific to my S II that may warrant an exchange.
Happy holidays all
-steven
edit: Doh, I should have used better search terms like separating touchscreen into 2 words. Found similar problems that way. It appears to be an issue with the included charger and not the device itself:
http://forum.xda-developers.com/showthread.php?t=1333258&highlight=charging+touch+screen
Hi everyone,
I've had my Desire Z for little over 2 years now and two months ago (was running CM7.2 at the time) I started getting a weird issue where my touchscreen would only be responsive when the keyboard was slid out (so the opposite problem of what quite a few other people have reported where the touchscreen becomes unresponsive when the keyboard is out). The status LED would also stay off whenever the keyboard was closed, and the keyboard backlight didn't come on anymore at all. Also, I had to make sure that the keyboard was slid out during boot, if the phone booted without the keyboard out the screen would not become responsive at all until after another reboot. My earpiece speaker stopped working around the same time so I was wondering whether it was just an issue with the flex cable becoming a bit loose, but the touchscreen would consistently start working again when I flipped the keyboard out, and also the physical scroll button on the top bit would always work, so I was still hoping it would be some weird software issue.
I then upgraded to Flinny's (amazing) Andromadus ROM (build 22, complete data+dalvik wipe) after which the keyboard backlight started working again, but the rest remained pretty much the same. Since then the touchscreen issues have been getting worse, so that I sometimes have to flip the keyboard in and out again a few times, or turn the screen on or off with the power button several times before it becomes responsive again, but then it tends to work fine until I lock the screen again, with no noticeable dead spots anywhere on the screen. I've had days where it worked all day without problems (except having to flip out the keyboard, that's been a constant for the past two months), and then today I haven't been able to get the screen to do anything at all even after dozens of reboots.
I've already bought a new digitizer and am all ready to put it in (I'll have to replace the broken earpiece anyway), but was wondering whether anyone has any thoughts on whether it could still be a software issue after all, or if anyone has experienced anything similar? The thing with having to flip the keyboard out to get not only the touchscreen but also the status LED to work is just so weird and makes me doubt that it's a pure broken digitizer or lose flex cable issue, so I'm wondering whether it would be better to first try reverting to a stock ROM before taking on the messy sticky glue stuff (I should be fine but still, never done it before)?
Many thanks!
From what you describe my best guess would be the main flex cable is what needs to be replaced. Flash a touch based recovery and see if you have the issue there as well, if so its very unlikely that its anything but a hardware fault
Sent from my Nexus 4 using Tapatalk 2
Thanks for the heads-up, I've been playing around a bit more with software and I do manage to get the screen working again occasionally, typically after the second boot into a newly flashed ROM or restoring a backup, and only until one or two reboots later when it becomes completely unresponsive again. I've tried CM 7.2.0 as well as Flinny's Andromadus 10, and it is only complete flashing that does the trick, cache wipe or factory reset alone does nothing. The two occasions where the touchscreen worked were still limited to when the keyboard was flipped out, and it also had to be flipped out during boot, otherwise nothing would work. I've learned to navigate my way around the phone by just using the hardware navigation button, but I'll have a close look at the flex cable when I take it apart to replace the earpiece speaker tonight...
Hello,
so I took my dear phone apart yesterday to replace the broken earpiece - everything went fine but after reassembly the replacement earpiece isn't working either, which leads me to think that all those little broken bits might actually be related to some contacts being a bit lose, all in the same region. Should've thought about that earlier really since the earpiece and the LED (only works when keyboard flipped out) are both in that top region that the digitiser data presumable also has to run through before passing through the flex cable.
In any case, I also took a picture of the flex cable which is slightly bent but doesn't seem straightforwardly damaged (see attachment, that thing on the right is *not* a rip). Think it's worth trying to replace it anyway?
What was truly bizarre is that after the first boot following reassembly the touchscreen worked quite consistently for the entire evening - I thought I might've fixed a lose contact by un- and replugging the digitiser cable, but then the screen went nonreactive again at some point. I wonder if the working screen was again actually related to some software reset caused by the battery being taken out for so long? In the meantime the actual screen and trackball are still working away perfectly. Bizarre.
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
obstacle3 said:
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
Click to expand...
Click to collapse
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
fireball0093 said:
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
Click to expand...
Click to collapse
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
obstacle3 said:
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
Click to expand...
Click to collapse
That's not a bad cost at all. I know I'm going to have to replace my keyboard in probably 2 months or so (maybe sooner) because some buttons are starting to not work. Other than that fact my phone is currently still going strong for being going on a 3 and a half year old phone
My proximity sensor is pulsating not while on call but while screen is off and in good light conditions. When ambience is dimmed, it stops. Why is it doing this, any fix? Using dome glass.
Weird, but maybe somehow the glue and glass are indeed interacting with the sensor under certain conditions, I was wondering if with this new under display sensor wouldnt be this kind of issues, reading about your case, then I will not use any
Any other insight or possible solution?
I need to make a correction to my question. This behaviour happens when AOD is on and light is good. Funny enough I don't see it on call. But screen turns off just fine on call.
Same here. Even with AOD off. Seems to turn on randomly and flicker. When I wave in front of it, then it stops.
If I turn off the AOD, it stops doing this.
I also have this..sometimes it keeps flickering even after I have unlocked the screen. If I put my finger over it then it goes
I had to turn off tap to wake as the phone kept coming on in my pocket despite the phone being faced towards my leg, to me the proximity sensor in the 10+ is just wrong.
I turned off adaptive AOD brightness and it stopped doing this.
Interesting. I don't see this behavior.
With AOC on a slightly than 1% per hrs battery usage seems to be nominal operation.
This circuit uses little current I suspect anyway.
Unless it's using more battery than I stated it doesn't matter.
It wouldn't harm the OLED... cool find.
Whenever I'm charging, I feel the screen scrolling being "heavier" than normal, like having a slow response and being more sluggish. Sometimes gestures are registered as just taps and sometimes when I'm glide typing on a keyboard, the touch response stops, and shows as if I lifted my finger. Doesn't do it all the time and is not consistent. Used the S-Pen to draw all over the screen to check if there are any dead spots, but there aren't any. I'm on the Exynos model, and I'm using the original charger, and also a Samsung wireless charger which also displays the same behaviour. I also believe it does it during a call as well, but I'm not too sure. Have tried with and without a case, increased and decreased the screen sensitivity, removed and reinserted the s-pen, and it still does it. Any ideas or anyone having the same issue?
Well, no, my exynos10+ behaves the same, charging or not charging
From what you're explaining it sounds like something is spiking your cpu periodically.
Probably an app or a setting you've made eg. Sync/backup when charging
I have not seen this on the note 10, but this has been reported on and off as an issue since samsung started making android phones.
Best practice to never use this phone when charging.
It will completely skew the charging power curve resulting in slow charging and warmer running especially with fast charging.
Hi there,
I recently changed the screen of my OP 3 because it fell on the floor and did not show anything afterwards (I don't know if this only damaged the screen or also other parts of the phone).
Now, the screen works very well and and the phone does turn on as well (I even type this with my OP3). But I now have two problems:
1) My phone shuts down almost immediately after I lock it (after one or two seconds I can still unlock it but after 5 seconds or so it is dead). It does not shut down while the screen is on, though.
2) It heats quite a lot during using and especially during charging. I know, this seems to be a general issue with older OP phones and happened to me as well, but never to that extent (after charging 30 min it gets overheated which never happened before).
Plus, there are two issues that might or might not be related to these to problems so I add them as well: My volume control buttons did not work before the screen replacement, which is quite odd, because the power button works well. And I think I have destroyed the home button/fingerprint scan while changing the screen.
What do you think, is there any hope of solving these problems without having to buy a new phone?
Best, thank you all!
Clemens
Oneplus 3's sides buttons assembly is really fragile. When i was replacing my screen i replaced it too. With my second display, i broke the replacement button ribbon and installed the original one. So you might broke it.
For screen issue, are you using latest OxygenOS? Because some custom roms have issues with third party displays.
clemenssayshi said:
Hi there,
I recently changed the screen of my OP 3 because it fell on the floor and did not show anything afterwards (I don't know if this only damaged the screen or also other parts of the phone).
Now, the screen works very well and and the phone does turn on as well (I even type this with my OP3). But I now have two problems:
1) My phone shuts down almost immediately after I lock it (after one or two seconds I can still unlock it but after 5 seconds or so it is dead). It does not shut down while the screen is on, though.
2) It heats quite a lot during using and especially during charging. I know, this seems to be a general issue with older OP phones and happened to me as well, but never to that extent (after charging 30 min it gets overheated which never happened before).
Plus, there are two issues that might or might not be related to these to problems so I add them as well: My volume control buttons did not work before the screen replacement, which is quite odd, because the power button works well. And I think I have destroyed the home button/fingerprint scan while changing the screen.
What do you think, is there any hope of solving these problems without having to buy a new phone?
Best, thank you all!
Clemens
Click to expand...
Click to collapse
Most likely a hardware issue. To confirm, clean flash OOS latest version (9.0.6 I think) and check. If it is ok, your problem is solved. If not, there are too many variables (screen, volume, home button and any other thing that you disturbed while replacing the screen) to trouble-shoot.