Related
My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work
BUMP Help!
You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.
I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.
Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.
dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.
any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?
hi, had my desire z about a year now, since ive had it, quite rarely ive had a problem of it seeming to have a mind of its own, for example, icons may be selected, or the home screen will slide accross by itself etc. ive always put this down to a trackpad problem.
the other day (after having a miui rom installed for about 2-3 weeks, which was fine untill now), it started acting up strangely, the above problem started happening, but more severe, also the touch screen and softkey buttons would stop working for periods of time (or stop completely untill reset), but screen rotation etc would still be working, which shows that the O/S has not frose and is still working behind the scenes (making me think its a hardware problem).
now, i think ive worked out that this seems to be triggered (mostly) when i open the keyboard. (as also, when the touchscreen stops working etc, sometimes, sliding the keyboard open and close several times, will sometimes seem to unfreeze the touchscreen etc, and will be back to normal, for a while). ive tried doing full wipe and reflashing etc, but i still have the same problems mainly when using the slide out keyboard, which again, makes me think its hardware (possibly keyboard ribbon cable?)
i really dont want to send it off as that means getting it all back to stock etc, and last time i needed the screen replaced, took 6 weeks to get it back!
if anyone could pinpoint the likely source of the problem, id rather replace the part myself..
would anyone have any ideas, as they would be very much appriciated... Thanks...
anyone at all?
I got 2 Zs meanwhile but dont have any problem with the keyboard.
But sometimes when its charging i got the same issues like you - no touch is working and the screens are sliding nearly automatically.
I think this has nothing to do with the keyboard...
Hope this had helped you a bit
Sent from my HTC Vision using XDA Premium App
thanks for the reply, unfortunately im still no closer to finding source of the problem, its intermittant, happened lots yesterday, not so much today, maybe the digitiser? its like there is another invisible finger touching the screen..
This would happen when i was on stock froyo, like it would cause the home screen to hang, but if i was ion an app it worked fine. I would use it to refresh of sorts when my phone was hung up or i need to reload my apps from sd lol. Sounds weird I know, but even with stock froyo i had problems with my keyboard but with the prerooted GB its as smooth as butter...
still going on, and getting more frequent, i dont think it is to do with the keyboard anymore. im now guessing it is the digitizer, its like someone is pressing an invisible finger on the screen, roughly in the center. it comes and goes, it happens for about 3 days, then goes away for a couple of days etc.
also there is very little info anywhere on the net that can help, including replaceing the digitizer itself
anyone ever replaced one on a disire z/g2?
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
OGP was getting laggy so I restored to factory stock. I was surprised though that the phone remained rooted, which I guess is good. I then installed FreeGee and went with CWM, same as it was before the restore.
Now, a few weeks later, I'm having some issues with the keyboard and the Home screen wallpaper. About once or twice a day (on most days), for some unknown reason, my keyboard will revert to the Android keyboard (AOSP) from the LG keyboard that I have it set to. When I "correct" it to the LG keyboard, sometimes the "Extended keyboard" option is checked and other times it's not (I always leave the extended keyboard checked). I also will occasionally get a notification on the pull-down that I need to select a keyboard.
The other issue is that the Home screen wallpaper also seems to change itself back to the default blueberry paper. This only happens on the home screen, and it does not affect the lock screen wallpaper. The wallpaper issue seems to happen at different times than the keyboard issue.
I've also had the phone reboot itself once or twice since the restore...both times while in its holster. Only reason I know this is that I hear the AT&T boot music playing in the background. Upon viewing the phone, it's verified that it is in fact rebooting.
Anyone else having these issues, or know the cause?
andygold said:
OGP was getting laggy so I restored to factory stock. I was surprised though that the phone remained rooted, which I guess is good. I then installed FreeGee and went with CWM, same as it was before the restore.
Now, a few weeks later, I'm having some issues with the keyboard and the Home screen wallpaper. About once or twice a day (on most days), for some unknown reason, my keyboard will revert to the Android keyboard (AOSP) from the LG keyboard that I have it set to. When I "correct" it to the LG keyboard, sometimes the "Extended keyboard" option is checked and other times it's not (I always leave the extended keyboard checked). I also will occasionally get a notification on the pull-down that I need to select a keyboard.
The other issue is that the Home screen wallpaper also seems to change itself back to the default blueberry paper. This only happens on the home screen, and it does not affect the lock screen wallpaper. The wallpaper issue seems to happen at different times than the keyboard issue.
I've also had the phone reboot itself once or twice since the restore...both times while in its holster. Only reason I know this is that I hear the AT&T boot music playing in the background. Upon viewing the phone, it's verified that it is in fact rebooting.
Anyone else having these issues, or know the cause?
Click to expand...
Click to collapse
Guess nobody else is having this issue.
The spontaneous rebooting has stopped, as has the "extended keyboard" issue.
What remains is the wallpaper and default keyboard changing issues. They both change at the same time now, about once a week.
What I was able to nail down is that this happens after every time titanium backup (free version) does its weekly thing. I have no idea what setting(s) I may have enabled to cause this. Anyone have an idea they can help out with?
I have the exact same problem with my home screen wallpaper changing. Ive had my optimus since about july and the first time it did it was like 2 weeks after i got the device. Kept doing it even tho i would change it back and not do anything with it regarding the screen. Wasnt sure what to make of it but whatever. It didnt do it again until yesterday (24th) and it wouldnt stop. Had to change my screen back like 5 times, and i just woke up a little bit ago and it was different again. The phone was just laying there. Didnt touch it so i have no clue. Ive tried going thru the settings to see if maybe i had checked something or whatever and im pretty sure i didnt. Only thing i can think of is that is just a glitch with the phone. I like the phone too much so thats not enough to get me to wanna get rid of it.
WHOvianFanGirl said:
I have the exact same problem with my home screen wallpaper changing. Ive had my optimus since about july and the first time it did it was like 2 weeks after i got the device. Kept doing it even tho i would change it back and not do anything with it regarding the screen. Wasnt sure what to make of it but whatever. It didnt do it again until yesterday (24th) and it wouldnt stop. Had to change my screen back like 5 times, and i just woke up a little bit ago and it was different again. The phone was just laying there. Didnt touch it so i have no clue. Ive tried going thru the settings to see if maybe i had checked something or whatever and im pretty sure i didnt. Only thing i can think of is that is just a glitch with the phone. I like the phone too much so thats not enough to get me to wanna get rid of it.
Click to expand...
Click to collapse
Are you running Titanium Backup?
If all else fails, you can always restore to stock and reinstall your apps and other items. Then maybe you will be able to determine what is causing the issue.
Hi everyone, I hope someone here can help me.
I'm experiencing a bug on my phone that's bothering in several situations.
Apps in landscape mode switch to portrait and come back to landscape (or not):
http://imgur.com/gallery/vfgSCPn
Voice notes in WhatsApp get interrupted:
http://imgur.com/gallery/yXIlFbI
(you'll see that the navigation bar briefly goes white)
I've factory-wiped my phone, gradually reinstalled the apps and double-checked that there are no weird or potentially dangerous apps.
The tricky part here is that I can't find a pattern, as it randomly happens (for instance, my keyboard went down when writing this actual post).
Has anyone else experienced this problem with their phone? Any idea on what I can do? It's really hurting my experience with Samsung.
Thanks!
You might try another Android version.
Clear system cache on the boot menu.
You can try a hard reboot as well.
Test the sensor(s) that controls that (it could be an intermittent failure, the worst kind to diagnose).
Does manually locking it to landscape mode stop it?
If it's a brand new phone, get it replaced as this is not a normally seen glitch.
Reloads generally don't cure settings or hardware issues and useless it's an old load or has a worm, trojan, etc are generally a waste of time.
As invariably the original issue just gets triggered again... eventually.