Hi all
As i already mentioned in another thread i found a new problem on my device, wich i believe to have since the beginning.
All the Edges of my screen are unresponsive and instead respond on a wrong position, more to the middle of the screen.
I first realized this when i wanted to try chrome, i couldn't use the tab feature (when you swipe left to right or right to left), but it worked on a friends HOX.
so i tested my screen in the "dev tools" app and noticed that all the edges are not responding correctly.
this is exactly why i can't use wave launcher, either :/
Who has this problem? Or someone even knows a fix?
Original Post: http://forum.xda-developers.com/showpost.php?p=28364968&postcount=960
D4rkSoRRoW said:
Hi all
As i already mentioned in another thread i found a new problem on my device, wich i believe to have since the beginning.
All the Edges of my screen are unresponsive and instead respond on a wrong position, more to the middle of the screen.
I first realized this when i wanted to try chrome, i couldn't use the tab feature (when you swipe left to right or right to left), but it worked on a friends HOX.
so i tested my screen in the "dev tools" app and noticed that all the edges are not responding correctly.
this is exactly why i can't use wave launcher, either :/
Who has this problem? Or someone even knows a fix?
Original Post: http://forum.xda-developers.com/showpost.php?p=28364968&postcount=960
Click to expand...
Click to collapse
Hi, I had said in that other thread that I had the same problem. I have since discovered that it was a bad app (draw something) cutting a couple of mm of the sides. In all test apps the screen is responsive right to the edge. Sorry, I can't shed any light on your problem.
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Ettepetje said:
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Click to expand...
Click to collapse
have you tried beta 4.3
tonytownsend said:
have you tried beta 4.3
Click to expand...
Click to collapse
Am doing so as we speak type. Nope, still buggy (same bugs).
I must be using the iPad too often because I find I'm unable to select words and then, afterwards, apply strike.
Edit: It also inserts spaces after it erroneously inserted "[ strike][ /strike]" (without the spaces) at the start of the post, in stead of around "speak", making me have to edit "[ QUOTE=tonytownsend" afterwards... Hopefully most of this is solvable in future.
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying touchscreen issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds without moving them
- If the touch indicators suddenly disappear, you have the same touchscreen issues
Kizune said:
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying multi-touch issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control. Single-finger operations and the S Pen kept working fine, though.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds
- If the touch indicators suddenly disappear, your touchscreen has multi-touch issues
Click to expand...
Click to collapse
I sure hope not. I started a whole topic on the Note 3 forum because I discovered it had a multitouch problem. Haven't been able to produce that type of multitouch issue on any of my other gear besides a Nexus 7. Will check with your method to see what it gives.
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
I discovered that my fingers got remembered (stayed) on the screen if I left 5 of them on the screen. Happened only ones though. Then I tried puting my whole hand on it for a few seconds and then the multitouch algorithm went bananas. Tried with different Multi-touch app too. I think this is a software issue, from the looks of it.
SwiftKey has been giving me problems on my 2014 Note 10.1 from day 1, but they had become 10 times worse today. I just rebooted my Note and it now behaves as normal (still somewhat buggy SwiftKey, like before). I think there are some issues in the Multitouch driver which can be triggered by the "whole hand" method described above, and possibly by other means. My MT driver had already become unstable, hence I could reproduce a defect (finger touches remaining on the screen) without the "whole hand" thing.
Kizune said:
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
Click to expand...
Click to collapse
Kizune, I included your video in a topic about this Multi-touch issue, I hope you don't mind.
Of course it's okay. Let's just hope that Samsung will fix the problem ASAP, it annoys the hell out of me.
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Itchiee said:
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Click to expand...
Click to collapse
I will very probably be doing the same. Thanks for getting back on topic.
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Sent from my HTC One using XDA Premium HD app
SlimJ87D said:
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Click to expand...
Click to collapse
I use the same (Tablet) version. Possibly it is caused by a combination of settings. I have most (aiding) options switched off. If I find the time I will experiment.
Try "Touchpal"..it's similar to Swiftkey.. it's free and has plenty of thenes. I actually like it better
Sent from my SAMSUNG-SM-N900A using xda premium
Newest SwiftKey is running perfectly for me on the Note 2014. It's so nice to be able to have a compact keyboard you can undock and move from any part of the screen to another. So convenient for applications. Highly recommended, please try it if you haven't
Since I've purchased my G3 and changed all roms, from official to stock, from kitkat to lollipop (all LG based) I've always been having same 2 problems.
They are really annoying and I have no idea how to get rid of them and I don't see anyony else complaining about it so it could be just my phone in particular.
1. When lockscreen is set on swipe, sometimes it doesnt unlock from first try, animation follows as my finger goes but after it stays locked. I got big hands and I can do long swipe (in case if somebody was to say I didnt swipe long enough).
2. This is even more annoying. This was on both Kitkat and Lollipop. In recents sometimes I get displayed all recently used apps and sometimes I see only last one used. When I swipe to clean that one app and enter recents again, the previous app shows up alone. then for 3rd again, then 4th, etc. On Kitkat it was pretty rare, but on Lollipop it happens to me all the time.
Is it just me or this happens to you too?
Hi, I have official 20F rom. I haven't encountered any of the 2 issues you mentioned.
Tomogitarist said:
Since I've purchased my G3 and changed all roms, from official to stock, from kitkat to lollipop (all LG based) I've always been having same 2 problems.
They are really annoying and I have no idea how to get rid of them and I don't see anyony else complaining about it so it could be just my phone in particular.
1. When lockscreen is set on swipe, sometimes it doesnt unlock from first try, animation follows as my finger goes but after it stays locked. I got big hands and I can do long swipe (in case if somebody was to say I didnt swipe long enough).
2. This is even more annoying. This was on both Kitkat and Lollipop. In recents sometimes I get displayed all recently used apps and sometimes I see only last one used. When I swipe to clean that one app and enter recents again, the previous app shows up alone. then for 3rd again, then 4th, etc. On Kitkat it was pretty rare, but on Lollipop it happens to me all the time.
Is it just me or this happens to you too?
Click to expand...
Click to collapse
I've recently flashed IronRom onto my tablet. It's been in the closet for a year. Only been in use for less than a month. Today, I was listening to music on the tablet. It was steady in a specific position. I had to skip one track and so I unlocked the tab using my fingerprint and went onto tap the next button. But to my surprise, it did not respond. In fact, it completely stopped responding to any touch instructions. I thought it might have been a rom related problem but then I checked TWRP rec and the problem was present there too. Really weird, cause the tab hadn't even moved an inch from the location it was working perfectly before. So how could this be a loosened wire? Any help, guys (other than sending it for repair)?
I have a HTC One m8 and the top half inch of the screen does not respond but occasionally it does sometimes for a little while. The top half inch generally tends to work when the battery is charged to 100% but sometimes that doesn't happen either. if it helps I use a tempered glass as a screen protector and the screen does not have any physical damage and it doesn't help when u boot into safe mode. I have also tried a hard reset.
Coincidentally i am working on a phone with the same problem (not mine). After a lot google research the owner decided to use another Launcher (Smart Launcher). This did not fix it entirely, if you are in Apps you can use the statusbar, but its not working on homescreen. I dont know why it behaves like that, but surprisingly many people get problems like that. I tend to believe that there is some software problem involved, because changing Launcher or using custom rom has been reported helpfull/fixing the problem (not allways tho..).
Now he had some other troubles with this phone and in the process i did a reset, that did not fix things as you said. I will install a custom rom next and will report back next week.
So i was wrong with saying a new lauchner solved the problem. Statusbar(sb) was accessible in home screen but not in app, said it wrong in the other comment. Now i had some time to test this and i can say that at least the phone i was working on is broken.
The top part does not recognize any touch input. The reason the sb showed some reactions is, that the launcher had a bigger trigger area (i guess), so you could pull it down. But still the top part was not responding. I tested it with stock, S-Rom and one Nougat Rom (dont remember), none of that showed an input in the top part.
Solution for now is different launcher or app that pulls down the bar. There are still some problems in daily usage, that this will not fix, so i guess its time for a new phone.
I am facing same problem. Is it any update which was pushed by HTC which makes the top 1 inch unresponsive ocassionally.. Indirectly, a marketing gimmick to push us by a new phone. So if it is really like that, who would buy a HTC phone again anticipating same problem again. Might go for Samsung (my own preference). huh !!!