Do you also face touch problem in your K3 note - K3 Note Q&A, Help & Troubleshooting

I'm facing a very annoying problem in my k3 note, that some areas of screen randomly stop responding. In my phone its mostly limited to bottom right part of my screen where backspace on keyboard is located. Rest of phone is responsive except this region. Restarting the phone fixes it temporarily.
But strange part is it doesn't happen on all ROMs, I first noticed it in some AOSP MM ROM, then i think it was Andronium VUI ROM (based on dev 1628) and now on s433 rom which leads to believe its some software thing not hardware thing.
Are there others also which face similar issue ? Any possible solution except switching to different rom ?

Mafioso said:
I'm facing a very annoying problem in my k3 note, that some areas of screen randomly stop responding. In my phone its mostly limited to bottom right part of my screen where backspace on keyboard is located. Rest of phone is responsive except this region. Restarting the phone fixes it temporarily.
But strange part is it doesn't happen on all ROMs, I first noticed it in some AOSP MM ROM, then i think it was Andronium VUI ROM (based on dev 1628) and now on s433 rom which leads to believe its some software thing not hardware thing.
Are there others also which face similar issue ? Any possible solution except switching to different rom ?
Click to expand...
Click to collapse
Yes, I have this problem with the screen also. I've heard from others with similar issues on other forums. It seems it is a hardware fault or possibly an issue with the way software interacts with the screen controller. In my case the screen is periodically unresponsive around the letter E or R on the keyboard and I have to tap the area with greater pressure. Sometimes it gets very buggy and very frustrating.
There is another possibly related problem when scrolling a web page or dragging - larger areas of the screen become unresponsive. Turning the screen off and then back on fixes the problem for the next 2 or 3 minutes. This issue has also been fixed for me with the kernel from daniel_hk here http://forum.xda-developers.com/k3-...rnel-dc-mtk-m1-kernel-vibeuiv3-51631-t3483573 - the only proviso is you apply it to Vibeui 1631. So while the scrolling issue seems to be fixed, the unresponsive areas around letters E and R on the keyboard remain.
I've noted the problems above would temporarily go away after flashing a new ROM however they eventually return. I've considered buying a new screen but not really sure if its a hardware or software issue - possibly both!

EpicSauce said:
Yes, I have this problem with the screen also. I've heard from others with similar issues on other forums. It seems it is a hardware fault or possibly an issue with the way software interacts with the screen controller. In my case the screen is periodically unresponsive around the letter E or R on the keyboard and I have to tap the area with greater pressure. Sometimes it gets very buggy and very frustrating.
There is another possibly related problem when scrolling a web page or dragging - larger areas of the screen become unresponsive. Turning the screen off and then back on fixes the problem for the next 2 or 3 minutes. This issue has also been fixed for me with the kernel from daniel_hk here http://forum.xda-developers.com/k3-...rnel-dc-mtk-m1-kernel-vibeuiv3-51631-t3483573 - the only proviso is you apply it to Vibeui 1631. So while the scrolling issue seems to be fixed, the unresponsive areas around letters E and R on the keyboard remain.
I've noted the problems above would temporarily go away after flashing a new ROM however they eventually return. I've considered buying a new screen but not really sure if its a hardware or software issue - possibly both!
Click to expand...
Click to collapse
hmmm it's interesting that different people have different areas of unresponsive screen. It seems more like software issue to me, as I started noticing this issue more on newer dev roms only. Today, I've reverted to dev ui 3.1 1622st as I remembered it didn't have it. Will report in couple of days of how it goes, so far haven't noticed it.

I have been facing touch problems for quite some time on the ROW version of the ROM s433. The touch starts acting weirdly, i.e random things start getting touched automatically and this happens mostly in the lower half of the screen. I turned on the show pointer location option from developer settings and it shows the pointer stuck at one point on the screen showing erratic behaviour. Turning the screen off and then back on solves the problem but very temporarily. Restarting solves for a longer time but the problem pops back up.

Related

Screen Issues fixable by software?

Why doesn't google respond to this http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
A ton of people are complaining and I really can't see why this could be a hardware problem when it goes away after you lock and unlock the phone. This happens a lot to me and is super annoying. Here is a video of it:
http://www.youtube.com/watch?v=4DmVV_B-SE8
What do you think can we pinpoint this?
I really think this issue has to do with accelerometer. When your screen goes crazzy try using it in other position, the behavior changes a little until it dissapear without turning off the screen.
im having similar issues, when i tap, say, in the middle of the screen it registers as a tap on the bottom, this is only occasional, and rebooting seems to temprerarily(sp?) fix this issue, however it is quite annoying, and in op's link there are a bunch of other users having the same problem. now, what happens to us that have unlocked the bootloader if this is NOT a software issue. i have only had my nexus for a week and i would be quite depressed if this is a hardware issue and it cannot be fixed/replaced because of a manufacturer defect.

[Q] Occasionally no response lower right screenside CM9 and CM10

I have experienced a really strange phenomenon. Just got a new Galaxy S GT-I9000 and decided to give CM10 a shot.
The main problem I am facing is some sort of a lag or better no response at all randomly. Problems are visible when:
1. I type on my keyboard
2. I scroll down long lists
The Problem.
Sometimes the device doesnt respond to my "tap" at all. The bug just occurs on the right half of the keyboard so you could say lower right half of the screen in a certain area around [k, i, l , j] buttons. When scrolling down lists my thumb is normally in that area so even when scrolling down the screen simply does not react from time to time and when I lift my thumb up and tap again everything works as normal.
This problem is extremely frustrating because I am not able to type properly anymore. First i was afraid its not the Firmware BUT my phone. But on stock rom I dont experience any of this at all.
Does anyone have an idea? Why can't I find something about this problem in the Forums. CM9 should be stable and nobody seems to experience this problem but doesnt the fact that it works on a stock rom prove, that its can't be the hardware?
Greetings

ghost swipes / input on various ROMs?

Folks,
unsure what might be causing this: I am rather frequently experiencing ghost swipes and ghost input on my Optimus 4X HD. Right now I am back to cm11 nightlies and see this behaviour same as on the stock ROM or any other ROM I tried so far. Behaviour's all the same: At some point the phone will start responding to phantom input - randomly starting applications from the launcher, randomly entering text in case I am in writing a message, randomly scrolling up or down in the current application, randomly opening and pinch-zooming-in-out pictures, ... . Usually, powering screen off and on again two or three times resolves this, but it's kinda annoying especially in situations in which the phone starts randomly making calls...
Any idea what could be causing this? Hardware issue? Defect? Dirty display? Issues with using a screen protection foil? Any input or feedback greatly appreciated.
Cheers and thanks,
Kristian
Not sure whether _anyone_ else does experience this on this device. My insights, so far, is that ghost swipes and this kind of input issues seem to be shared by other users on other devices, too, but they don't seem to appear on all devices of a certain kind running a certain piece of software. As far as I am concerned, these issues still happen then and now - but considerably less often after upgrading my p880 to another ROM (using EuphoriaOS 5.1 unofficial instead of nightly CM builds now). So if you see this problem on a p880, maybe this might help you too.

Touch issues / Sensitivity issues after Nougat update

Okay so I wanted feedback regarding this whether someone else is experiencing this or not.
I have gradually observed during the last few days that a lot of my touches to click have gone unresponsive in Nougat. Initially it was something that I hadnt quite noticed but slowly the trend became obvious. Now dont get me wrong, this would happen a few times here and there with lollipop and MM as well, but the rate is far higher now on Nougat. Especially when typing on the keyboard this means mis-spelled words, missed letters, and accuracy is far worse now.
Has anyone else observed this or is it just me?
Just got my xcover 4 with nougat installed i have the same issue.
The sensitivity is low and i need to press a bit higher finger force to respond.
Even with sensitivity (glove mode) set to on things get worse.
I'm seeing the same thing. What is strange is that I'll see the button highlight/depress, but no action occurs. This is on multiple apps.
On what device/OS?
Sprint Note 5 on Nougat
Did you try gloves mode? Does it work?
the same for me on 920cd and the same iusse using S pen
I contacted samsung Greece about the existing problem.
I reported the problems me and you guys have and the tech support told me that your problems exist because you did not factory reset the devices before upgrading to nougat.
Anyone tried to contact samsung about the problem?
They dont know anything about it.
facing same issue screen lagging in note 5 sm-n920s also tried custom rom but still lagging in typing and scrolling on facebook
I have the same problem on my xcover 4 here!!
When I run the the touch screen test, touch screen responds well, but when I want to write a message or to scroll the home screen Its very annoying. It looks like software problem.
please help
Hi guys.
I have 2nd piece of Xcover 4 SM-G390F (first was change by seller for new one) and had the same problem. First 2-3 days all work perfect.. I have installed my applications, work perfect for two days, but after this... --After wake, display react only in centre area, 1 centimeter from display border no reaction or react on xxx touch. After few seconds (20-30) display react on full range, but with lags... So... I go for support to Samsung official at CZE.
Support tells me, that they don't know about this problem, that I'm 1st who has this problem... And some other bull... about unofficial sell and any other. So I post them IMEI and they let me know, if my distribution is official or not, and we'll see what next. They recomend me to go to service center, where somebody looks on my SM. So I see tomorrow.
ROM - official Android 7 Nougat from start using (not updated from other version)
Deleting apps - no effect
Safe mode - no effect
Factory reset - no effect
Apps to calibrate screen - no effect

Intermittent loss of touch response

Just retired my 2 XL and got a like-new 4 XL. Loving it so far, except one nagging issue.
Randomly the top 30-50% of the display stops registering taps (touch). It's easy to fix by turning the display off then back on, but I'm concerned it may be a hardware issue.
Interestingly, when this happens and something that is full screen and scrollable such as a contact list or app drawer is in the foreground, I can drag from below the "no touch area" to the top of the screen, but I can't start a drag at the top. So, it can sense touch in the troubled half, it just won't register taps.
I have done tons of searches. I see lots of people saying Android 12 had touch issues out of the gate, but was supposedly fixed. I disabled the block_untrusted_touches. I have checked any app that has draw over other apps permissions. I have tried with high touch sensitivity on and off. I have paid attention to running apps when it happens. I installed a LogCat reader looking for touch related issues when the problem occurs. I tried safe mode, but due to the intermittent nature of the problem, and the fact that safe mode disables most functionality, it really wasn't a good long term test.
I have yet to pinpoint this.
Sometimes it doesn't happen for a day, other times it's multiple times per day. So trial and error takes time because just when you think you licked the problem, it rears it's ugly head again.
I'm running LineageOS 19.1 at the moment (which I had also run on my 2XL with no issues). It is rooted. No apps force closing or crashing.
Has anyone else seen this on the 4XL?
Definitely interesting, never heard of that. I had some touch issues, specially if the display gets wet where it register touch, but poorly to the point I need to restart the device and dry out the screen. Though in my case the creen is completely cracked, so I suspect that's the cause as it didn't happened before.
Though I had a similar to yours but with the battery.
The problem was that the phone would randomly shut down, and that would happen more often when it was on my pocket.
This made the phone very un stable as sometimes I would have the phone completely off and didn't even know about it.
So I decided to open it and have a look at it. It turn out that the problem was the flex cable that connected the battery with the logic board, it was just slightly tore on one side, but just a tiny I couldn't nearly see it, I had to use another phone to zoom in.
As it was torn, depending on the way the phone was changed the force the gravity made over the cable, causing that sometimes it not enough energy got the phone, causing it to shut down.
Once I replaced it, it never happened again, not a single time.
Maybe you have a similar problem, though as you are rooted and using a custom ROM, that may be the reason, my case was extremely rare.
anyway, good luck

Categories

Resources