Develop Bugs

hardware problem?

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?

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

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!

[Q] Screen lost sensitivity until lock/unlock phone

Hi All,
Just got my One X and I'm quite impressed. Sadly, I discovered an issue with the phone even after having done factory reset.
While using the phone with any application, it will randomly loses the sensitivity. What I mean is that no matter what I do on the screen, nothing will happen - I can't drag, I can't click, the buttons don't work etc. However, if I lock the phone and then unlock it, the screen will work again, the sensitivity is back.
This problem occurs very often but at different point in time. Sometimes it would happen right after I start using an application. Sometimes it doesn't happen until I have been using an application for a good while (5mins+).
I plan to return the phone for repair/replacement. However, before doing so, I would like to check if anyone has experienced similar problems previously and if it is indeed a hardware issue. It would be great if I can have some insights, so that I can describe to the customer service assistant who is (more often than not) clueless about what I'm talking about. Also, since the problem doesn't seem to occur with a pattern, I am wondering if/how the engineer will be able to detect the issue and provide a fix (or even better to offer a replacement).
Thanks guys

this happens to me too not as often as you describe and not as severe but even yesterday i was in twitter suddenly touchscreen loses sensibility and for example scrolling takes me 5 swipes to move a tweet off the screen but usually restarting the App fixes it
Sent from my HTC One X using Tapatalk 2

Did you use it while charging?
sometime the bad power supply will make your phone freeze

I think it's a Tegra 3 issue, because my Asus Transformer Pad 300 does this sometimes, aswell.

[Q] Intermittent Touch Input Issues

Right now my wife and I both have the note 8.0 (I used to have the note 10.1 until it slid off my roof on the interstate), and there have been a periodic issue with it not responding to touch input.
Intermittently, and at random intervals, the touch input just stops responding. It doesnt delay response or respond incorrectly, it just acts like it never recieved the touch input at all. Playing games, searching on google, typing an email, using s note, etc. It can happen anywhere and anytime.The game or application continues to run, the only hiccup seems to be the touch input not being recognized. Usually, it only lasts for a few seconds, 1-5 I would estiamte.
I have tried a number of settings changes, and even a master reset, and the issue persists. I have a few thoughts on the matter, but don't seem to be able to resolve it.
Has anyone else been experiencing this?

phoenixbennu said:
Right now my wife and I both have the note 8.0 (I used to have the note 10.1 until it slid off my roof on the interstate), and there have been a periodic issue with it not responding to touch input.
Intermittently, and at random intervals, the touch input just stops responding. It doesnt delay response or respond incorrectly, it just acts like it never recieved the touch input at all. Playing games, searching on google, typing an email, using s note, etc. It can happen anywhere and anytime.The game or application continues to run, the only hiccup seems to be the touch input not being recognized. Usually, it only lasts for a few seconds, 1-5 I would estiamte.
I have tried a number of settings changes, and even a master reset, and the issue persists. I have a few thoughts on the matter, but don't seem to be able to resolve it.
Has anyone else been experiencing this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2338394
Its a known problem, an update to 4.2.2 seem to have fixed it. But if you are using the AT&T LTE model(Like me) or Rogers then you'll have to wait for the update which god knows how long the carriers will take. Personally I am trying to see if I can isolate the issue.

Havent yet looked at the 4.2.2 and dint really know it was available. Havent had much time to do much with my devices in the last couple of months. My wife and I are both using the wifi only models.
I tend to believe the issue is primarily happening due to a slowdown on the system while processing certain sync functions or i/o functions. I tend to notice it more while connected to wifi and have also noticed at least one cloud sync error when the issue happened.

SwiftKey not working well on 2014 Note 10.1

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