Related
i have herems 100 and last rom i had was tnt 2 it was untill two days ago the screen somtimes doesnt close sometime open only white and when it works fine the screen view is shifted down i see parts of the soft keys at the top of the screen
i also have another problem s that the bottons at the buttom doesnt work sometimes.
the phone didn't fell down from me or hit
please if any one can help
MMM
Same problem....
I'm experiencing the same problem on my herm100. It has been like this for a few weeks now. I'm running the latest T-mobile test rom. I have problems with the buttons and also the screen both going white sometimes and shifted down a little. So I also see some little part of the softkeys at the top of the screen.
Anyone know what is causing this, and how to get it solved???
Originally Posted by nosgergj
I have this same issue, but i also have a white-out problem which I am trying to fix first. Like you the problem is intermittant at best - whilst it happens all the time, I cannot put my finger on a sequence that actually causes it. I am trying to fix this other problem that is more annoying at the moment, but if I stumble across a solution, i'll be sure to put it on here.
regards,
i found this on http://www.4winmobile.com/forums/he...llment-black-5atin-normal-medium-light-7.html
i'll keep looking there hoping to find a solution
MMM
http://forum.xda-developers.com/showthread.php?t=297994&highlight=buttons+Hermes+solved
MMM
after flashing three different roms then coming back tnt beta the problem went now am very happy
hope this could be the solution for you too
MMM
problem came back and it's worse now
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
Hello guys,
My G3's touch screen has been acting up for a week now and I am seeking help to pin point if it is a hardware issue or a software issue that can be fixed.
Whilst typing (have used different keyboards) I cannot seem to press the letter 'k' and the letter 'r' or any keys directly above or below those keys. I wondered what the problem was and started swiping my screen to see if I can flow through the UI of the phone smoothly. Suffice to say that it didn't which then prompted me to turn on the "Show touch" & "Show touch data" within the developer settings of the phone.
After turning on those two options, I could clearly see that the screen does not recognise any input on two parts of the screen. This can be seen in the screenshots I have posted.. As it shows when swiping on the screen it skips an entire column of the screen on both left and right sides of the screen .
I was hoping someone could shed some light in this issue since I have been trying to troubleshoot this problem with no avail for the past week. If this is hardware related then what would be the best course of action?
Additional Info:
* Have tried different firmware and roms
* Have tried other keyboards like google keyboard and swiftkey
* Have tried to clear cache and factory reset
* Have taken it to phone repair store and they said they would have to replace the LCD.. Thought I'd post here before I go that route.
Any help would be greatly appreciated.
You're gonna have to replace the digitizer. Unfortunately I had the same issue with my nexus 4. That's why I have the g3 now.
StatusUnknown? said:
You're gonna have to replace the digitizer. Unfortunately I had the same issue with my nexus 4. That's why I have the g3 now.
Click to expand...
Click to collapse
Thank you for your reply.
Was hoping I would not have to go through that route but it seems inevitable .
Is the G3's digitizer and LCD stuck together? If so it'll be a costly replacement :crying:
That I do not know. I know the frustration though. It might be a big charge
Does anyone's S6 edge have this problem where you are typing a text, at least 10 words long or more, and the screen don't recognize touch input just once, but it happens every 15 to 20 words? Its freaking annoying and I've since switched to the google keyboard and this problem don't happen as much, but the problem is still there, its caused me to misspell at least 7 words so far that the keyboard has auto corrected. This is so damn annoying and I hope I'm the only one that has this problem that way I can take this phone back and get it replaced.
I guess I'm the only one
Happens to me sometimes, but not all the time. It's probably a RAM problem. I usually clean/close some opened apps with Cleanmaster to prevent lag. Hope the next update will fix memory management problem.
I'm on Android 5.1.1 and it supposedly has fixed the RAM issue and the problem still exists. I don't think it's a RAM issue. I think it's a software issue that when you type too fast it stops recognizing the presses. Hapes mainly with the backspace key. If I tap that button like 20 times it will stop pressing it no matter how hard I press.
I want to say this is a Edge thing not a S6 thing.
Try a different keyboard from play store, also try closing apps in background.
I haven't noticed the ever on this incredible phone.
Running stock no root yet, with 3 pages of apps disabled.
Pp.
I apologize for resurrecting this thread but, I've been searching for a while with no avail. Since I've upgraded to 5.1.1 I've been experiencing this issue. Has anyone in the time of this thread found a possible fix for this?
I've tried multiple things, maybe going to have to resort to cleaning up with a factory reset.
This phone is so beautiful, yet functions like a POS, minus the camera. It just sits on desk collecting dust. I too have the aforementioned issue, along with dozens of others. First phone I've ever regretted buying.
Hi guys
I bought a cheap OnePlus 5t. It's had a hard life, but everything seems to be working ok.
Except- 3 or 4 times a day it starts having phantom/ghost touches. Usually at the edge of the screen (I put touch tracking on) -I've rebooted, factory reset, but no improvement.
Anyone know the best way forward? Don't think I'll get warranty, so is it likely to be hardware or software? Unlock it and put a new Rom/kernal on? Or try fitting a new screen?
Is there any way to know whether it's software or hardware?
Any experience or suggestions gratefully received
Thanks
What rom are you on? I used to be on custom roms and I noticed phantom touches. It wasn't till I went back to oxygenOS and disabled nav bar completely did I fix this. I found that having a nav bar greatly worsens phantom touches because when you type on the keyboard you tend to touch one of the nav bar buttons.
Also maybe check to make sure you are on the right firmware
Thanks for the reply.
I was on stock, I'm now on lineage. It hasn't fixed it.
The touches are always up the left of the screen... When they happen theyre happening hundreds of times a second, as in its not one touch... The screen becomes in unusable because there's so many touches on the top left of the screen -
It lasts for about a minute, or untill I force restart it...
It's driving me nuts to be honest. I've even taken out apart to see if re-seating the screen would help but it didn't.
Would a custom kernal help?
I don't have any experience with custom kernals. And this problem seems a little different than the one I had which was more a single phantom touch.