yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] zmfl:
Tnx, I'll post the update.

Also, good to hear you have it working :)
[HTC Sensation] undercover:
No, it does not resolve issues. I just got rid of mine again today. If anything, it caused it to come back in my case, as on previous FW I didn't have it for ages. And I do know what I'm talking about, zmfl is a dad of the fix, while I'm a grandad ;)
[HTC Sensation] andyjb103:
Since updating my firmware I have had zero problems with touchscreen responsiveness on ANY rom GB based and ICS based. My phone was almost unusable before, sometimes took 10 or so attempts to unlock from the lockring, during normal use swipes were registered as touches.. totally unusable. The firmware update fixed it for me. I guess everyone will update to latest ICS firmware eventually, so would be interested to hear if it resolves the problem for anybody else. It was this touchscreen issue that brought me to XDA in the first place!!!!
[HTC Sensation] 02CWRX:
I too am now running the ICS firmware (with a GB ROM) and can also confirm it maintains my touch screen responsiveness the same as the official OTA update.
[HTC Sensation] Alfaifi:
Used to have this problem before, now im using 2.3.5 Sense3.5 and haven't had this problem for a while
[HTC Sensation] SsBloodY:
I can't understand what is the grounding for can someone explain what is it's purpose. And if the problem is from the grounding why the touchscreen continues to work without a problem with the back-cover removed? Asking just of curiosity.
[HTC Sensation] zmfl:
About 6 months ago I got involved with this issue, and to this date nobody gave a particularly clear answer to that. I do understand some of it, but not enough to give a clear explanation.

One thing is certain... It does work :)

LOL :)

Also, crap... But it obviously works for some folks, so it's worth something.
[HTC Sensation] cortexdk:
Year

Thanks it fix the problem :D
[HTC Sensation] alex.bat98:
I did all steps correctly, but I didn't notice any changes. Can anyone explain me what happens?
[HTC Sensation] tobis:
Touch Test

I have the same problem described in the first post. I tried the alu foil trick and prying the pin but dare not overextend it.

Neither fixed my problem.

Having tried an app called Touch Test i found that 2 1cm wide vertical bars are unresponsive, instead pushing my touch to the sides of said bars giving me 2 percieved touch points.

See screenshot where i use 2 thumbs giving me 2 points at either side on both unresponsive bars of where Im actually pushing (and dragging to make the unresponsive bars show).

Does this help in anyway to find a solution?

Sorry if Im posting stuff noone cares about.

edit: Stock rom, latest official software.
[HTC Sensation] zmfl:
Did you try the charging/disscharging with no touching cycle a few times?

Since you have the issue constantly, I wouldn't say it's grounding related... Perhaps it's a bad digitizer? You might have to visit a service center....
[HTC Sensation] tobis:
Solved

Yes twice.

Tried it a third time now over night(while I wrote my previous post and Its fixed!!!!

Complete discharge, leave battery out for a good while, insert battery, charge to green light and never touch the display till I pulled the charge cable out. Pull charge cord and turn on. For what its worth having read the related thread and this: charged with HTC supplied USB cable from PC.
[HTC Sensation] decebal12345:
I'm glad for you. I will try your solution.
[HTC Sensation] zmfl:
Nice! I keep learning new ways this issue can manifest itself :)
[HTC Sensation] rexdino:
Great Post!

That info is really helpful, thanks dude!
[HTC Sensation] Skolotaie:
Thats just Briliant i had Issues in Some Apps and Many Times in the Appdrawer and now it Works Fine Thanks! :D
[HTC Sensation] PePiTo.:
Wow Thanks now i know how to fix my phone when i have that problem :D
[HTC Sensation] tobis:
I spoke too soon. The issue came back after a few hours.

Its now in for repairs. 2-4 weeks...
[HTC Sensation] zmfl:
That makes more sense... Unfortunately :/
[HTC Sensation] xdaco:
I was going crazy with my touch screen crazy behavior. Thanks a lot . By putting a metallic foil solved the problem. Thanks a lot.!!!!!
[HTC Sensation] NesoConQueso:
Wow, i just joined these forums, and this is great. My sensation sometimes doesn't even respond to touch. So hopefully this does the trick. :D
[HTC Sensation] SteKru:
Since you guys did a lot on touchscreen issue perhaps somebody has an idea.

http://xdaforums.com/showthread.php?t=1469012

Touchscrren fully working in 4ext, but after boot its not on PIN screen.

appreciated

thx
[HTC Sensation] zmfl:
That doesn't sound like the grounding issue. Just try a different rom or re-flash the firmware. Probably... :)
[HTC Sensation] SteKru:
I know, but thought this topic might be worth a try.

new install did not help.
[HTC Sensation] ilko__83:
thanks for clarification !
[HTC Sensation] Sebastian768:
My two cents.....while using a TPU case, I have no touch screen issues, never had. When I remove the case, I almost immediately get issues. Example: I can't slide across to the next screen, doing so will zoom out or in. I can't open or close the dockbar.

I'm also using a screen protector...

My Incredible S never had this issue...

S
[HTC Sensation] Albino Sousa:
thanks a lot for the info :D
[HTC Sensation] maumont:
Have you tried cleaning it?

Have you updated all?

Have you tried deactivating "Tell HTC"?

regards
[HTC Sensation] zaki0saad:
thanks, this was a downright pain in the butt and hopefully HTC wont do this again :p
[HTC Sensation] Datfoooo:
hey i just replaced my digitizer and now my phone is non responsive when turning on the phone. you can se the ring move when trying to unlock it but after trying for 10sec it starts working 100%. do you think this fix will work?

firmware updated to the latest. im on ICS
[HTC Sensation] joshv06:
I am in the exactly same situation as you. I just put a new digitizer on min, rooted, put ICS. And it doesn't work until 5-10 seconds after. On a side note, wifi is stuck on "turning on" but never does, anyone know how to fix?
[HTC Sensation] acesabe:
Just chipping in with my experience, since switching to an adapter with USB socket and using my USB micro-b cable this issue is gone. I had been using el cheapo charger bought from a phone accessories stand in the shopping centre/mall, when I first got the phone as it came without a charger, the generic type of charger with stretched diamond shaped red/green LED light on the back. Presumably some people are still getting this issue with the original HTC charger right?
[HTC Sensation] CZroe:
I just replaced the LCD and touchscreen glass digitizer in this phone for an ex-coworker who had the phone before I met him in September 2011 (yes, he was gone that quick!). Anyway, he never mentioned this problem. When I first booted the phone I grabbed the ring without issue. After I left it charging off my Apple USB charger + extension cord + random microUSB cord I had laying around, I realized that it was very difficult to unlock the phone. Usually, grabbing the ring would cause it to bounce and my finger would grab another icon nearby. I'm guessing that this is what is described here.

Anyway, the OP tells me to try an update first, but this is not my phone and there is no SIM, and the downloadable update for Gingerbread doesn't work:

SD Checking...

Loading...PG58DIAG.zip

No image

Loading...PG58DIAG.nbh

No image or wrong image!

Loading...

PG58IMG.zip

[New Screen]

Checking PG58IMG.zip

I'm going to try the hardware fix but I already know it won't be instant because using it without the battery cover doesn't fix it.

Thanks for all the research, guys!

Edit: Somehow got the OTA update over WiFi and the screen works great now. Thanks guys!
[HTC EVO 3D] scottlam1:
is it possible to put the htc flashlight app and odex into the evo 3d i dont know why they took it out of the android os i miss it
[HTC EVO 3D] athasian:
You can download the flashlight application from htc hub.
[HTC EVO 3D] jgalan14:
Yup what he said I would recomend the flashlight app in the market tho cause it has a nice widget the way you don't have to open the app
[Nexus S Android Development] reddv1:
Does this depend on screen dimmer code? Cause I'd like to maybe remove screen dimmer and just have this mod.

Also, thanks for putting all this time on these mods. Love your work.
[Nexus S Android Development] Ezekeel:
The patch file I have provided is for a kernel already including BLD 3 and Screen Dimmer 1 (+ all bugfixes), but the code of Touch Wake does not depend on either Screen Dimmer or BLD - so you can enable BLD, Screen Dimmer and Touch Wake independently from each other in the kernel config and also could remove one tweak entirely from the kernel source if you want.
[Nexus S Android Development] morfic:
Can you stop copy pasting this "couldn't reach morfic"

That would be awesome.
[Nexus S Android Development] Ezekeel:
Fixed BLN not working properly anymore.

Bug fix: http://www.pastie.org/2446398
[Nexus S Android Development] Enhanced:
This sounds amazing.

Probably the biggest "mod" to our phones since BLN.

If the battery drain isn't terrible with this mod, I think you have a winner on your hands.

Goodjob. :)

EDIT: Think you should make an app that allows users to easily change the values. I could see this catching on as much as BLN has.
[Nexus S Android Development] jjhrrsn:
Bump sounds ballin
[Nexus S Android Development] simms22:
works great!

pinned a shortcut to the on/off script onto my homescreen using gscripts. one press turns it on, second press turns it off..
[Nexus S Android Development] rejanmanis:
I think those are deleted already. lol.

cool stuff.

so... I presume, when the screen dimmed. the crt animation will appear as well ? :cool:

and to mr simms and mr reddv1 , can i have ur test kernel included this TouchWake MOD for any ROM since i used MIUI ROM
[Nexus S Android Development] nbeebe24:
Sounds like an awesome mod
[Nexus S Android Development] tonno16:
what is this kernel??? the file touchwake there isn't in my rom.

please help me.
[Nexus S Android Development] Maximilian Mary:
http://xdaforums.com/showthread.php?p=17104132
[Nexus S Android Development] Ezekeel:
Fixed the problem with the proximity sensor not reactivating the screen when making calls. Also, since I was in the neighborhood I also fixed the problem with BLD on the i9023.

Bug Fix: http://www.pastie.org/2457092
[Nexus S Android Development] reddv1:
Thanks for the quick fix. Is this a combined bugfix for proximity sensor and i9023 bld?
[Nexus S Android Development] Ezekeel:
Yeah, they both needed modifying of include/linux/input.h and instead of having two patch files in two different threads which would need to be applied in a certain order I decided to simply make one patch for both problems and put it in this thread. It does not make a difference for you guys and if later people want to include this in their kernel they probably simply pull the up-to-date files from my git instead of applying these gazzilion patches one after each other.

Hope this really fixes the problem with the i9023. I had to guess what the problem was and if this does not solve it, I am all out of ideas. Unfortunately, I do not know anyone with a i9023 I could borrow. The next best thing would be to get someone on gtalk or similar with a i9023 who is willing to go through a painful process of flashing a test kernel with debug statement and passing the logs on to me, then wait until I have compiled the next test kernel... rinse and repeat - lets say about ten times. Not really looking forward to this.
[Nexus S Android Development] kecinzer:
If it will be nessecary I can help on Google Talk. But I'm not capable to compile kernel. If we go for this, you have to send me flashable zip :)
[Nexus S Android Development] Enhanced:
Using Touch Wake right now with the Lucid kernel and it works perfectly.

Not sure if this is possible, but here's my idea:

Is it possible to somehow wake the phone through touching the touch keys when BLN is active (as in touch keys are on)?

I thought of this as you said that the touch keys (and screen) are not suspended when Touch Wake is active. So now I'm going further to assume that maybe the touch keys are also not suspended when BLN is active so that maybe it can be coded to allow touching the keys to wake the phone?

I know nothing about programming so I may be talking out of my ass here but just an idea.

Thanks!
[Nexus S Android Development] reddv1:
I think I found a bug with Touch Wake. I'm on 9020, with latest touch wake bugfixes.

After the screen goes off and the touch wake timer has passed, if I touch the soft keys they light up and stay lit while the phone sleeps. I tried to grab a logcat with the phone plugged in to my PC, but the bug can't be replicated while the phone is plugged in.

Sent from my Nexus S
[Nexus S Android Development] Maximilian Mary:
It seems having bln installed (and disabled for me) solves this
[Nexus S Android Development] Ezekeel:
I would be possible, however this could lead to the possible problem of accidentally unlocking the device when you carry it around in a pocket and get a notification. I do not think it is worth the trade-off

I cannot reproduce the problem with my reference kernel. Does it happen every time you try it?
[Nexus S Android Development] reddv1:
Your right, I disabled bln and it stopped happening. Then I re-enabled bln and it still didn't happen. I guess disabling then re-enablinh bln fixes the problem.

Sent from my Nexus S
[Nexus S Android Development] Jonathon Grigg:
I have put together a quick app for enabling/disabling Ezekeel's various mods included in many kernels, for those who dislike playing around with scripts. You can find it at RootzWiki (with support) - http://rootzwiki.com/showthread.php?4526 or here at XDA (without support) - http://xdaforums.com/showthread.php?p=17282651
[Nexus S Android Development] Enhanced:
I don't think the small chance of this happening should devalue a feature that would be very useful. Many people don't put their phones in their pockets or could just put their phones facing outwards in the pocket (away from your leg). The reason I would love this mod is because most of the time, the phone is on my desk right beside me. When I get a notification, it's such a drag to reach over and push the power button. Instead, I'd rather just be able to touch the keys to wake the phone.

Many times people unlock their phones is for a notification anyways, so a mod that allows you to just tap on the touch keys to wake it would be so much more convenient then reaching over to the power button all the time.

Considering all the mods you have released, any chance that this could get a look at when you are less busy? Assuming this implementation isn't too difficult, I think a lot of people would like the option of something like this despite it's perceived drawbacks.

EDIT: Or, how about making it have a duration as well. For example, when a user gets a notification, BLN comes on and so does Notification Wake (random name I'm gonna give this idea) for a user defined time (we'll say 45 seconds here). Once the 45 second delay has elapsed, the touch keys cannot wake the phone anymore but is still lit as there's a notification. Something like this would greatly reduce the chance that people can wake the phone from their pockets.

Thanks.
[Nexus S Android Development] Maximilian Mary:
What happens when you set touchwake/enabled to 1 and touchwake/delay to 0?
[Nexus S Android Development] Ezekeel:
I cleaned up the code a bit for all three mods BLD, Screen Dimmer and Touch Wake.

Bug fix: www.pastie.org/2488785
[Nexus S Android Development] DrSpanky:
Or just a feature to have the buttons wake the screen whenever it's charging. That way you don't have to keep the screen on all the time through the feature that's already in the ROM and you won't have the chance to have it accidentally unlock in your pocket.
[Nexus S Android Development] Enhanced:
Yes, I forgot.

I assume this may save battery too as the screen doesn't have to be suspended while Notification Wake piggybacks on BLN which is suspended the keys anyways. Since BLN makes the touch keys active (as in you can touch them and they respond, while they don't do anything), you may as well leech off of that. Thus, in turn, hopefully this wouldn't kill that much more battery then having BLN on.

In theory I assume.
[Nexus S Android Development] Ezekeel:
Fixed the BLD problem for the i9023 of the touchkey backlights not being re-enabled on touchkey press. A big thanks to reddv1 and the Lucid users to help me track the problem down and all i9023 owners for their patience.

Bug fix: http://www.pastie.org/2499956
[Nexus S Android Development] endursa:
thanks :) i just posted in the touchkey backlight thread that the problem still persists, but i hope lucid includes the fix in a new kernel version asap :)
[Nexus S Android Development] cabstrak:
First, sorry if this is going to sound confusing but..

My touch key lights back up too when I press like the part where launcher docks. Is this supposed to work that way or is it just my phone acting weird? :D

(imagine using any launcher - stock, go, adw, launcherpro, those docks on homescreen..) whenever I touch around that area (when playing games for example), the touch key lights back up too.

I thought it was supposed to light back up only when I touch those keys and not the screen? O.o
[Nexus S Android Development] reddv1:
Yeah that was a problem at first, but the new parch fixes touching the bottom of the screen. What kernel are you using? It might not have been update to the latest patch or the patch needs to be modified more.

Sent from my Nexus S
[Nexus S Android Development] Ezekeel:
800 was too low, so in the official patch I have set this value to 830. Might still need some adjusting; we will see...
[Nexus S Android Development] kecinzer:
I found issue with touch wake.

I use TEUV 08092011 kernel and with this mod enabled I found, that my screen don't react on touches for 1 - 2 seconds after phone uses proximity sesnsor - mainly after I end a call (put phone from my ear) and want to tap on "end call", phone don't reacting for some time and mentioned.

Can you look at it Ezekeel?
[Nexus S Android Development] Ezekeel:
Good catch. I forgot that the proximity sensor also is capable of putting the device to sleep. Of course, in this case the touchcontrols should be disabled right away and not be kept enabled for some time, since otherwise you probably will activate the touchcontrols during the call with your cheek and strange stuff can happen. ;)

Bug fix: http://www.pastie.org/2528577
[Nexus S Android Development] formaldehyde:
I have this exact same problem on my i9023. When running Multitouch Visible Test from the market, it shows that the buttons light up when my fingers cross the y=700px line, not the 800px (or 830px) mentioned in this thread.

It happens at least on both, Trinity "TUV-Any-NS+4G-12092011" and on Lucid 2.1y.
[Nexus S Android Development] reddv1:
Can you try this kernel I adjusted it 900px, its lucid-2.1y http://www.mediafire.com/file/2sng8i91drz7oax/Lucid-nexus-2.1-test-y-cm7-NS-2.3.5.zip
[Nexus S Android Development] formaldehyde:
Now it's much better, but it still lights up the buttons a bit too early. The app says it happens now at about y=759. That's about in the middle of the LauncherPro dock icons.
[Nexus S Android Development] reddv1:
Try this one 950px http://www.mediafire.com/file/h0ajpqc8q4znjkc/Lucid-nexus-2.1y-test2-cm7-NS-2.3.5.zip

Try this one 975px http://www.mediafire.com/file/4444br65t0a10j6/Lucid-nexus-2.1y-test3-cm7-NS-2.3.5.zip

Try this one 999px http://www.mediafire.com/file/ta68te4ixs5pxix/Lucid-nexus-2.1y-test4-cm7-NS-2.3.5.zip
[Nexus S Android Development] formaldehyde:
The 950px one works perfectly!
[Nexus S Android Development] reddv1:
Great, I'll update the kernels to 950px soon.

Anyone else want to confirm that it works the same on their i9023?

Sent from my Nexus S
[Nexus S Android Development] Ezekeel:
Ah, I see. There seems to be some coordinate scaling happening since the digitizer has a different DPI than the screen. The value of 840 defined in the source code as the center of the virtual touchkeys must have been in screen coordinates, not digitizer coordinates.

Bug fix: http://www.pastie.org/2544546
[Nexus S Android Development] Ezekeel:
Small patch:

Call the suspend function a bit earlier to prevent a rare hiccup happening when the touch controls are pressed in exactly the same moment the screen is disabled.

Bugfix: http://www.pastie.org/2641540
[Nexus S Android Development] KalimochoAz:
Thanks as always good job Ezekeel
[Nexus S Android Development] timeToy:
TouchWake sticky on Stock Rom

How can I get TouchWake to stick after a reboot with the stock ROM ?
[Nexus S Android Development] timeToy:
Solved my own issue by creating a Script Manager based script at boot.
[Nexus S Android Development] kuldaoo:
Nice, can you share it? :-)
[Nexus S Android Development] reddv1:
The best way to get it to work on a stock rom is to enable unit.d script support. To do that just flash one of the lucid kernels for stock rom then flash any kernel you wanna use. Unit.d scripts will work from then on.

Sent from my Nexus S
[Nexus S Android Development] Ezekeel:
Got a new patch for BLD, Screen Dimmer and Touchwake.

Use mutex_trylock instead of mutex_is_locked/mutex_lock combo to avoid race conditions.

Bugfix: http://www.pastie.org/2710096
[Nexus S Android Development] Rafael Cadina:
Ezekeel, I'm running Matr1x v10 here and i've noticed problems when using touchwake. The other mods are running just fine, even deep idle is ok. When i turn on Touchwake my phone begins to have random reboots. Is it possible to know what's causing it?
[Nexus S Android Development] Ezekeel:
Since I do not know what other devs have implemented in their kernel that might interfere with my mods, if you have trouble with one of my tweaks try the reference kernel in my signature first. If this does solve the issue for you, the problem is most likely not with my mod, but with the other kernel - contact the corresponding dev and let him know.
[Nexus S Android Development] Rafael Cadina:
OK. Thank. I'm gonna do that ;)
[Nexus S Android Development] nathanson666:
Disabling touch wake with proximity sensor

Would it be possible to disable touch wake when the proximity sensor is covered (like when the phone is in a pocket)?

I think this could help with having the screen stay on unnecessarily when its in a pocket and the power button gets accidentally pressed.
[Nexus S Android Development] Ezekeel:
Good idea. However I think this is not possible since afaik the proximity sensor is normally deactivated and only gets activated when actually needed. I will look into it.
[Nexus S Android Development] bioan:
I've just flashed your kernel and I have enabled the Touchwake mod.

I really do not know how this thing should work. I've searched all around here and read the entire thread.

Should the screen come up when I touch the soft keys or the touchscreen ?

Thank you !
[Nexus S Android Development] suksit:
When your screen is off by the timer i.e. not by pressing the power button, you'll have a short period of time (I think default is 45 sec.) that you can re-activate the screen by simply touching it.
[Nexus S Android Development] nathanson666:
Maybe touch wake could only be activated after the screen is unlocked. Although I have a feeling that something like that would have to be put into a ROM.