Can you guys download a multitouch tester app of anykind and test your screen, because its only showing me 2 touches.
i also turned on the "show touches" option in the developer option and i can actually see that there are about 10 touches that show.
and when i turn on the "pointer location" option, it works fine if i move 2 fingers simultaneously, but if i put 3 fingers on at the same time - it freezes, and if i continue to move all three fingers simultaneously, it crashes and reboots.
So clearly, something's wrong here but im just wondering if guys get this too.
i need your feedback guys, ASAPPPPPPPPP. thankssssss
Dar Targaryen said:
Can you guys download a multitouch tester app of anykind and test your screen, because its only showing me 2 touches.
i also turned on the "show touches" option in the developer option and i can actually see that there are about 10 touches that show.
and when i turn on the "pointer location" option, it works fine if i move 2 fingers simultaneously, but if i put 3 fingers on at the same time - it freezes, and if i continue to move all three fingers simultaneously, it crashes and reboots.
So clearly, something's wrong here but im just wondering if guys get this too.
i need your feedback guys, ASAPPPPPPPPP. thankssssss
Click to expand...
Click to collapse
OHMYGAD GUYS HAHAHAHAHA ITS FIXED, turns out it only recognizes 2 touches if you turn on the "three finger screenshot" option in the setting.
I'm using note 9s. This screenshot is multi touch test.
Related
feel lag on when is unlocking. did any one having a same problem with me??
please delete this post...
The unlock swipe would lag for the following reasons:
1. Your wifi was turned on but is off because of screen being off. You turned on the screen which makes the phone re-enable wifi and connect to a network. This process will lag the swipe animation.
2. You used some kind of app (ie. JuiceDefender) that would disable APN (3G) when your screen is off. Turning the screen on again will make the phone to try to reconnect to 3G and this will also lag the swipe animation.
3. You just turned on your phone and because things are still loading at startup, doing the swipe will lag.
Tip: Try to wait for 5 seconds after turning the screen on and then do the swipe motion. It should go back to normal.
If none of that applies to you, do a factory reset =)
this is my second time to hard reset it but still the same.
I often find that swiping doesn't unlock the phone; the arrow won't go all the way to the edge of the screen (it sometimes just stops halfway). When that happens, I press the power button to lock the screen, then try the process again. 9 times out of 10 it'll work fine the second time.
This happens when the WiFi is off, and I am not using any APN software, nor have I just switched the phone on.
It doesn't really bother me, unless this happens when a call comes in, and I can't answer it! (it often takes me a few swipes to answer a call, and I have to swipe it slowly and carefully)
shanespencer said:
I often find that swiping doesn't unlock the phone; the arrow won't go all the way to the edge of the screen (it sometimes just stops halfway). When that happens, I press the power button to lock the screen, then try the process again. 9 times out of 10 it'll work fine the second time.
This happens when the WiFi is off, and I am not using any APN software, nor have I just switched the phone on.
It doesn't really bother me, unless this happens when a call comes in, and I can't answer it! (it often takes me a few swipes to answer a call, and I have to swipe it slowly and carefully)
Click to expand...
Click to collapse
you might have a problem with your screen where some parts wont respond to your touch
download any drawing programs " i find magic marker " is the best from the market place. its free. and tap dots all over your screen, if there is/ are parts that doesnt response to your tap from the first time, that means u have problem with the screen and its not accepting your touch input. which is why your swipe doesnt go all the way sometimes.
Yes there is lag on the unlock screen. I see it as just bad programming by SE.
-------------------------------------
Sent via the XDA Tapatalk App
My swype keep changing direction, anyone nows how to set it to a particular side?
@mirdones - it changes sides when you start with your finger at the top of the swipe arc and slide your phone across the screen (left to right or right to left)..
@everyone - my swipe unlock occasionally stops about 3 quarters of the way along.. all I do is re-swipe from where it stopped and it's fine - that said, it doesn't happen as much now that I have stopped using task killers and startup auditor.
I find that instead of a slow swipe more of a flick works well for me.
Does anyone know if its possible to disable the se lock and just use the android one?
gavriel18 said:
Does anyone know if its possible to disable the se lock and just use the android one?
Click to expand...
Click to collapse
...would love to know this too
When I make a call or receive one while talking I notice different apps will open, usually beginning with the world clock??? It seems to be due to touching my face to the screen. Can anyone give me suggestions?? My service provider is Sprint, last phone was a G nexus never experienced this problem with that phone.
I noticed this too. I found out (personal experience) was that it has a ton to do with having a larger screen and not giving the screen time to turn off or pressing the home key so I wouldn't hit the dialer. My solution was a quick tap of the power key to turn off the screen and no more apps popping up.
DarqAnshin said:
I noticed this too. I found out (personal experience) was that it has a ton to do with having a larger screen and not giving the screen time to turn off or pressing the home key so I wouldn't hit the dialer. My solution was a quick tap of the power key to turn off the screen and no more apps popping up.
Click to expand...
Click to collapse
Thanks', I'll give that a try, guess this must not be a big problem, wonder if it may be an issue with our phones, not all S 4??
There is a setting in my device/call to enable Turn off screen during calls. The only trick with that is trying to access the pull down menu while in a call. You just have to make sure you avoid the proximity sensor so it doesn't turn off the screen.
Sent from my SPH-L720 using Tapatalk 4 Beta
So this is my second going on my third Note 3. The first one had a faulty speaker right out of the box (very scratchy and low in volume). Bang my second one in and less than a week later... the phone is acting up. The bottom 1/4 of the screen doesn't work properly. For example: if you open a text message thread and try to tap the box to open the keyboard it wont work! I found my self tapping it repeatedly over and over again. Sometimes it will eventually open.
Problem 2: typing. If i hit space bar, it will double space, hit the letter b or v or both. Also if i am using any keys at the bottom it will either miss my input or hit 3 others.
Problem 3: Happens rarely. The phone goes beserk once you tap it. For example. I dailed 0 and all of a sudden #* 0 191 etc were hitting dozens of times. Apps opened closed at lightening speed.
One test I can do that works all the time is hold the Q button on the keyboard and slide my finger along the keyboard working my way down. It shouldn't hit any other keys and it should just slide.. but once i head south of the H button all the keys I slide my finger across start going bezerk...
anyway im going to return my note 3 in hopes for a better working one...
2JZ said:
So this is my second going on my third Note 3. The first one had a faulty speaker right out of the box (very scratchy and low in volume). Bang my second one in and less than a week later... the phone is acting up. The bottom 1/4 of the screen doesn't work properly. For example: if you open a text message thread and try to tap the box to open the keyboard it wont work! I found my self tapping it repeatedly over and over again. Sometimes it will eventually open.
Problem 2: typing. If i hit space bar, it will double space, hit the letter b or v or both. Also if i am using any keys at the bottom it will either miss my input or hit 3 others.
Problem 3: Happens rarely. The phone goes beserk once you tap it. For example. I dailed 0 and all of a sudden #* 0 191 etc were hitting dozens of times. Apps opened closed at lightening speed.
One test I can do that works all the time is hold the Q button on the keyboard and slide my finger along the keyboard working my way down. It shouldn't hit any other keys and it should just slide.. but once i head south of the H button all the keys I slide my finger across start going bezerk...
anyway im going to return my note 3 in hopes for a better working one...
Click to expand...
Click to collapse
Just bad luck buddy... Maybe the store you got from got a bad batch. Good luck this time....
Hello
Touching twice to wake up my P8, no longer works.
I made a complete reset, still nothing.
fredpom21 said:
Hello
Touching twice to wake up my P8, no longer works.
I made a complete reset, still nothing.
Click to expand...
Click to collapse
Does the trigger turn on correctly?
Or it turns off as soon as you touch it?
Everything works normally, except touching it twice.
Okay, let's try to understand what's going on with the touch.
In the developer options turn on "show touches".
In fact, double tap to wake also works when you want to turn off the screen (by the lockscreen).
So press the lateral button to turn on the screen, and double tap.
You should see your tap with a little white circle.
Try out and let us know what you see.
Some basic info before i begin:
Phone: Moto X Style/Pure on android 5.1.1 (XT1572)
It is rooted, but no custom roms are installed.
So basically what happened was I dropped by phone, then all of a sudden the on screen (Home, Back and Multitasking) buttons started to become unresponsive and started ghosting. I have restarted so many times just to exit an app. After several restarts, my on screen (home, back and multitask) buttons have stopped working.
Firstly my basic and short term solution was to install a 3rd party on screen button app from the play store, this would put a second set of on screen buttons above the stock on screen buttons. But before this I noticed that the on screen buttons actually worked when rotated so that instead of being on the bottom of the screen they would be on top. The on screen buttons also work when i boot into recovery mode, my custom recovery is TWRP. I also wiped dalvik cache and reinstalled my apps through the recovery setup.
I dont know whats going on, I even made it so that when my on screen buttons moved to the top of the screen, i would click on apps from the bottom of the screen and it would work. It doesnt seem to be a hardware issue as i have confirmed it to be working through TWRP and tapping on apps from the bottom of the screen, confirming that my touch screen is working perfectly. The on screen buttons also work and it being detected when TalkBack is enabled.
Help me plez.
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
valest said:
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
Click to expand...
Click to collapse
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Houndz said:
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Click to expand...
Click to collapse
The touch screen issue of this device is hardware related, born with such flaw, you will have it even you didn't drop it.
No sure how it happened, but it helps if you can take it apart and clean the connector a bit and make sure you reconnect it firmly, if that doesn't work, you will have to replace the touch screen part or the whole screen and touch screen and rear frame and stuff, but do notice: it's likely to happen again.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049