Question Ghost Touch at the Center Part of the Display - Motorola Moto G100 / Edge S

Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.

ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Haven't noticed personally. Using a screen protector?

I removed the screen protector to check if is causing it but still the same. It happens rarely though.

ijuanp03 said:
I removed the screen protector to check if is causing it but still the same. It happens rarely though.
Click to expand...
Click to collapse
Hmm. It happens during use or in charging or ?.

Shadowthor said:
Hmm. It happens during use or in charging or ?.
Click to expand...
Click to collapse
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.

Try safe mode.
I would ditch Waze app and flipboard.
Try clearing the system cache.
See what's running in the background when it happens.
Use the factory diagnostic touch screen test to see if it may be hardware caused. Not sure how you access it it on that phone.

ijuanp03 said:
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.
Click to expand...
Click to collapse
Hmm that's weird. Did it happen recently? Did you install any new apps?
Hopefully it's not hardware related.
You can use cqa test to check the hardware. *#*#2486#*#*

Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.

ijuanp03 said:
Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.
Click to expand...
Click to collapse
A new update got pushed out?

Not entirely new. The latest software update RR31.Q2-12-14-7.
Shadowthor said:
A new update got pushed out?
Click to expand...
Click to collapse

ijuanp03 said:
Not entirely new. The latest software update RR31.Q2-12-14-7.
Click to expand...
Click to collapse
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?

Shadowthor said:
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?
Click to expand...
Click to collapse
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.

ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Could be a blown sim card. Replace both and follow ESD protocol when handling them, always.
Handle like a stick of ram.
Excessive ESD exposure can cause random failures immediately or worse, days, weeks even years latter. These cards are dirt cheap but a delayed failure can cost you dearly...

ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Hmm weird. Haven't tested out dual Sim but it shouldn't cause this issue.

I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html

nullschool said:
I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html
Click to expand...
Click to collapse
And so I thought mine is an isolated case. Motorola is yet to confirm if this is hardware or software related.

ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Hello everyone!
I have this same problem here on my brazilian Moto G100 and in the same place almost in the center of the screen. After removing the screen protector, the problem is more difficult to happen, but it still happens rarely, requiring a cleaning of the screen for the problem to stop happening for a while.
I noticed that the problem happens several times when I leave the smartphone leaning against metallic surfaces or other electronic devices.
Is it necessary to use the warranty to replace this screen or can a firmware update solve this problem?
Regards!

I'm Chinese user.My device have this problem.Our forum many people reaction to this problem

I can confirm I have the same problem. I don't know if it's hardware or software yet

wow I haven't had any problem, but if you find any solution or coment from motorola sopport please post it

Related

Touchscreen sensitivity issue

Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
drakester09 said:
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
Click to expand...
Click to collapse
It is different than ghost-touches.
I noticed there is a topic on xda about this problem already: Click
I hope this can be fixed with a software update.
joeyzbg said:
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Click to expand...
Click to collapse
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
DuckMcQUack said:
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
Click to expand...
Click to collapse
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
joeyzbg said:
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
Click to expand...
Click to collapse
It really may be...just get used to New display settings and you will be out of problem too then!
Inviato dal mio One utilizzando Tapatalk
I have the exact same issue with my OnePlus after 3 weeks of use. At first it was the swype issue where the phone wasn't picking up swypes properly on the middle left side of my screen. I use a pattern unlock so it's annoying when the dots don't connect.
The next thing was not picking up my touches properly so when ever I use SwiftKey and they recommend words, I could never properly select it because the touchscreen wasn't registering properly.
I did a factory reset and it solved the problem at first but it's now back after 2 days. It's not as bad as before but still persistent. There are tons of people on Redit, Cyanogen and the OnePlus forums that are reporting the same problem.
The good news is it seems like a software and not hardware issue, hopefully the permanent fix can come soon.
Possible solution to the supposed OnePlus One touch sensitivity problem
Settings→Developer Options→ Scroll About Half Way and UNcheck "block gesture touch events"
Also try and see if unchecking "Adaptive backlight" in Settings→Display & lights→ Adaptive backlight, helps.
Of course none of these are permanent solutions. And this problem is real. But maybe the "solutions" above help.
ive not had these issues just yet. but i do get annoyed by gesture control
This still needs to be addressed. It's almost as bad as an old capacitive touch screen!
I got my phone maybe a month after it was released. After exactly 4 months the touchscreen input died and lost all sensitivity. Typing became impossible. After going back and fourth with support for 2 months they finally sent me another one. The new one was excellent for EXACTLY FOUR MONTHS!! Almost to the DAY! My damn touch is broken again and I can't type. I'm furious! I'm also 1wk outside warranty.
With the first phone I tried every hack, crack, rom, reformat, anything I could find. Nothing would restore the touch. I assume it's a hardware issue. I've been looking around for a solution but haven't found anything. If there is anything, I would appreciate some direction.
Sorry for everyone that ever wasted their money on OnePlus, I won't be getting any more products from them...

Back button Ghosting/pressing itself

Hi, I have a galaxy s6 and its back button is pressing itself, without me touching it, closing apps and making it unusable. Using warranty isnt an option as it was bought abroad.
What are my options? Is this necessarily a hardware problem or could it be software related?
me too have this problem
vitalianoleone said:
me too have this problem
Click to expand...
Click to collapse
I had similar then found that the animations (in developer) were set to 0.25, reset them to 1, used rebooted a few times and now its OK. Could be coincidence but tried reboot, clearing cache etc before the Animation setting?? Weird but may be worth trying.
gmlogan said:
I had similar then found that the animations (in developer) were set to 0.25, reset them to 1, used rebooted a few times and now its OK. Could be coincidence but tried reboot, clearing cache etc before the Animation setting?? Weird but may be worth trying.
Click to expand...
Click to collapse
ill try, but i dont think itll help much...
dgershko said:
ill try, but i dont think itll help much...
Click to expand...
Click to collapse
my phone is already set to animation 1s
I change launcher and now the problem seems to be less frequent (I install nova at the place of next launcher)
I think that the problem maybe depend by some app not perfectly compatible with lollipop 5.1.1.
I had this problem on my S6 and when I googled it, it seemed to be a recurring issue on Samsung phones. Poor insulation causes the radio to leak into and trigger the captive buttons in weak signal areas. What eventually fixed it for me was replacing my tempered glass screen protector with another one, as non-unrelated as it sounds.
keijikage said:
it seemed to be a recurring issue on Samsung phones. Poor insulation causes the radio to leak into and trigger the captive buttons in weak signal areas.
Click to expand...
Click to collapse
Mine never made that, even in poor/nonexistent areas... I believe that has massively to do with the production quality of every particular product. Some of them might be a little bit better fabricated than others.
I had this problem. Luckily I was on warranty and just switched it out. I would try factory reset tbh, that's the only thing I didn't try

Just me? "The iris sensor is not responding. Try again later"

Once or twice a day so far, my iris scanner stops working. The red scanner light does not come on when it should, and I get an error pop-up that says "The iris sensor is not responding. Try again later". This happens both from the lock screen and from Samsung Pay when I use iris verification.
Sometimes it recovers after a few minutes. Sometimes it doesn't recover until I reboot the phone, but then it works immediately.
Do I have a defective phone that needs to be exchanged, or is this just a software glitch? Does anyone know of a workaround to reset the sensor when it fails, without having to reboot?
I'm guessing it's probably a software issue. I think there's a system app called "Iris" try force stop on that an see what it does. Has it been happening out of the box or since an update?
Otherwise this could probably get fixed with an update but don't expect them to adress this issue as quick, if you can i would recommend you to just replace the device.
eniorodriig said:
I'm guessing it's probably a software issue. I think there's a system app called "Iris" try force stop on that an see what it does.
Click to expand...
Click to collapse
Thanks, good suggestion. I'll try that next time.
Has it been happening out of the box or since an update?
Click to expand...
Click to collapse
I got the AQD9 update on the first day I had the phone, so there wasn't time for the issue to come up before that.
Otherwise this could probably get fixed with an update but don't expect them to adress this issue as quick, if you can i would recommend you to just replace the device.
Click to expand...
Click to collapse
Yes, unless most other people are encountering the same problem. That's why I wanted to ask here first.
It happened to me once I rebooted and it never happened again. I haven't taken any updates.
My suggestion is , wait until this week's update starts rolling out, if by then you still find an issue I'd recommend you replace the device while you can :good:
eniorodriig said:
My suggestion is , wait until this week's update starts rolling out, if by then you still find an issue I'd recommend you replace the device while you can
Click to expand...
Click to collapse
Which update are you referring to? As I mentioned, I've received AQD9.
Gary02468 said:
Which update are you referring to? As I mentioned, I've received AQD9.
Click to expand...
Click to collapse
Samsung is due to release a major update this week that will fix mostly the red screen issue,wifi issues and mostly first day issues that users are finding. This update will fix major bugs i believe so, so if you're lucky it might just fix the issue you're having but i wouldn't have high hopes. If you get the update this week and the problem persist just get it replaced.
eniorodriig said:
Samsung is due to release a major update this week that will fix mostly the red screen issue,wifi issues and mostly first day issues that users are finding.
Click to expand...
Click to collapse
Great, I'll see how that goes.
More of the same
Like everyone above has stated, I'm sure Samsung will be updating the iris sensor in the near future. I hope they figure out the issue of using it in direct sunlight but as its and IR sensor, it may be impossible.
Force-stopping the Iris system app doesn't fix it when it stops working. Neither does clearing that app's cache. I'll try clearing its data and re-registering my irises, but I'm not optimistic.
As of this morning, I get a slightly different error message, "Can't use iris recognition", when the red light doesn't turn on. It seems to happen most often following a prolonged idle period (e.g. overnight). Rebooting always fixes it immediately.
I notice other threads describing a similar problem with the fingerprint sensor. I've only encountered it with the iris scanner. But if it occurs with both, and both are fixed by rebooting, that makes it more likely to be a software issue.
RootTheS8+ said:
Like everyone above has stated, I'm sure Samsung will be updating the iris sensor in the near future. I hope they figure out the issue of using it in direct sunlight but as its and IR sensor, it may be impossible.
Click to expand...
Click to collapse
Won't happen unfortunately. The sun emits a lot of infrared and I assume it would look very similar to how your own camera sees the sunlight, with massive glares forming on the lense making it hard to see any other details with a lense flare taking up most of the image. I have a filter to allow more infrared but less visible light to pass through the lense, maybe I'll tape it on and see if it works better, but it's doubtful.
Bump. Any insight on this issue? I just experienced "Can't use iris recognition" for the first time on my week-old S8+ (latest stock firmware).

Fingerprint swipe on sensor flaky

Just got my Pixel 3 the other day and have started to put it to regular use, I'm coming from a Pixel OG that only missed swipes if my finger was damp or such. At first I thought it was due to my case but even without it on the swipe gesture on the fingerprint sensor is more miss than hit. I'm not talking about unlocking which happens every time, but trying to pull down notifications or quick settings with a swipe on the fingerprint sensor (yes it's enabled).
Anyone else with this issue or do I possibly have a finicky sensor?
Thanks
I've had some issues with mine but not a ton, yet. It works fine for unlocking as you said but sometimes swiping down doesn't do anything and I have to swipe a few times or just pull the shade with the screen. I believe I saw a post here or on reddit about it a few weeks ago. Not sure if it's something that can be addressed via software fixes or not.
That's not encouraging to hear, that's a feature I use all the time. And on my pixel OG it worked flawlessly so this is definitely not usual performance.
fury683 said:
I've had some issues with mine but not a ton, yet. It works fine for unlocking as you said but sometimes swiping down doesn't do anything and I have to swipe a few times or just pull the shade with the screen. I believe I saw a post here or on reddit about it a few weeks ago. Not sure if it's something that can be addressed via software fixes or not.
Click to expand...
Click to collapse
hwshi said:
That's not encouraging to hear, that's a feature I use all the time. And on my pixel OG it worked flawlessly so this is definitely not usual performance.
Click to expand...
Click to collapse
It's not "usual" and likely not working as intended but it's not a problem specific to your device. Assuming it's something they can adjust with software it should be fixed in an update vs an RMA for your specific phone. That's kind of what I was getting at with my reply.
Yes I understood it as it being a problem on more than mine but made me think it could be a hardware issue. Hopefully that's something that can be addressed with software.
fury683 said:
It's not "usual" and likely not working as intended but it's not a problem specific to your device. Assuming it's something they can adjust with software it should be fixed in an update vs an RMA for your specific phone. That's kind of what I was getting at with my reply.
Click to expand...
Click to collapse
only time i had the issue was with a case on. other than that.. its been perfect
I've noticed similar behavior on mine. If I slow my finger down a bit it's typically 100%. But if my finger moves too fast, it doesn't always work.
works 1 out of 3 times for me. I'm using a skin, no case. Anyways, i would only use the feature in "one-hand-mode", and it's a big stretch for my finger the way that i carry the phone...

Ghost Touches

Has anyone experienced ghost touches and gestures? I know the oneplus launcher has a sensitive edge so if your palm was touching the edge it would bring up the notification bar, had to disable that feature, but has anyone else experienced random ghost touches or is it just me and I should return the device?
I'm experiencing it also, and I'm using Nova so I think it's the phone a d not the launcher.
Fatmonk8 said:
I'm experiencing it also, and I'm using Nova so I think it's the phone a d not the launcher.
Click to expand...
Click to collapse
I've noticed it randomly when the phone is not even being touched, I'm not sure if it has something to do with gestures, I've see reviews on TMobile that someone had the same issue that was much worse than I described and returned the phone.
I have to have a case on our I got the screen. Artifact of the curved glass
Yeah I've noticed on some cases it can cause issues, but this is something a firmware update can fix.
I've had this issue also and it seems to be app dependent. Cpu-z triggers it. Check this out: https://drive.google.com/file/d/1-8-O6UchZGLGUA95yJLjQSaqKhbYjljo/view?usp=drivesdk
Using Nova Pro and no never had this issue yet.
Yeah I've had random apps trigger it but then it won't do it at all, not sure how I can even replicate it.
Happens to me too. Interesting sidenote: Switching to 60hz fixes the problem for me.
Yep. Also seeing this issue. Have had it happen twice now, once yesterday and once today. No idea how to replicate. Seems random.
You think it's a hardware issue? Or software?
No such issue, maybe faulty phone. I'd return immediately
haven't had this issue either.
Could you try the CPU-Z app with 90hz enabled? Just keeping this app open makes my 1+ go crazy.
Try taking off the screen protector
I too am having the issue. At first I thought it was the screen protector as well, but taking it off didn't fix anything and I immediately regretted it. The issue is pretty sporadic and going to 60hz does help. I mostly noticed the issue inside the Google Messages app (my primary texting app). And also the CPU-Z trick worked too, my screen went ape sh*t. I'm gonna give OP a week to fix this through software or I'm gonna have to do an exchange.
No issues here. Using Google messaging app n Nova pro.
I've got this issue on mine as well. Started an RMA. If it's not fixed within 2 weeks, I'm sending it back.
https://www.youtube.com/watch?v=GT1U8ilxy4k
Short clip showing the fault:
https://www.youtube.com/watch?v=N-7GnF7AUpQ
I actually had an issue today where I was watching YouTube and my phone started freaking out like I keep touching the screen, something is definitely wrong, but I don't want to go thru T-Mobile to replace it.
NukeBomB3000 said:
Happens to me too. Interesting sidenote: Switching to 60hz fixes the problem for me.
Click to expand...
Click to collapse
Can confirm switching to 60Hz fixes it.
If you enable "Show taps" and "Pointer location" in Developer options it's quite easy to see when it happens. No idea what triggers it, but CPU-Z is definitely the worst one.

Categories

Resources