I am having a major issue with multi touch, and it happened on stock so I don't think it's the rom I'm running (CleanRom Dev).
If I let go of my second touch, the screen loses the first touch location. So, if I am playing Minecraft or Shadowgun, I'll use one touch to move forward, that works, then I'll use one touch to move the screen, that works, but as soon as I let go of that second touch, I stop moving; even though the first touch is still being held on the screen. This happens in any game I play, even with the HTC Gestures off.
I saw a couple other people were having issues with multi touch, but I'm wondering if this is a problem with the kernel or the device. I saw that h8rift mentioned that the kernel's multi touch is a hacky implementation.
Any information is appreciated,
Thanks.
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Edit:
Issue keeps coming back a few minutes after rebooting.
thebest said:
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Click to expand...
Click to collapse
Yeah, same here. It took me forever to figure out that it was HTC gestures that was the culprit
Sent from my HTC One X
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
edit: already said
ThisWasATriumph said:
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
Click to expand...
Click to collapse
Hmmm, maybe this should be under CleanRom development then. I may not have had it on stock, I thought I did, but I wasn't on stock for very long
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
rohan32 said:
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
Click to expand...
Click to collapse
Good to know, I was just worried that my phone was jacked up D: lol
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
I use Holo Locker does that cause issues?
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
Wow, that was the problem. Disabling Holo Locker, then turning the screen off and on resolved the problem. Weird....
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
You're a genius! Holo Locker was causing the issue. Thanks so much.
Yeah I had that problem too, it was being caused by HTC Gestures. I just turned it off because I didn't ever see myself using them.
now me too..but..
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
david244 said:
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
Click to expand...
Click to collapse
GOT IT. :silly::silly::silly:. (after alot of factory resets)
The trigger of the bug is If you select:
Personolize -> Lock screen style -> No lock screen
Try it.
you want to uncheck HTC Gestures. it is used for another purpose not what you think it is only used for when your phone is connected to tv.
Related
I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?
Ken98045 said:
I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?
Click to expand...
Click to collapse
I have experienced this before, where the backlight wont even activate from pressing a button, and the keyboard certainly isnt typing anything on the screen either. Although usually i can fix this by sliding the keyboard back in, and then out again.... annoying yes, but its only happened twice in the month i have had my ATT Fuze, and i havent had to reboot like you mentioned.
When running my stock AT&T rom, I had this happen almost daily. Now that I flashed a new rom, I have yet to experience it again. I had to turn off/on my device in order for it to go away before.
Same problem here.
Sliding in and out does not work any more.
Resetting doesn't work anymore either...
Time to flash to original Roms?
Keyboard lock up
This happens to me too. I noticed that it happens more frequently when I set my wifi to best performance, and then try to type something. Keyboard becomes completely unresponsive. I usually have to soft reset.
I had the problem with stock ATT rom, NATF rom, and now with RRE 4.5SE Rom. I have tried the T9 dissabler, but it also did not work. My Fuze is only a few days old...
I notice this seems to be a common problem... No one seems to have answered this in any of the posts I've read. Is there a cab or patch or reg tweak that some one has come up with to deal with this? Can some one look into this???
Thanks so much in advance!
Mitch
*Edit*
Forgot to mention that this my second Fuze, sent the other one back because it was doing the same thing...
same unsolved issue here (wants me to crack my fuze)
Ive noticed this too... but what I do to correct the problem is hit the window key. It then activates the start menu. Then press it again to exit the start menu and the keyboard magiclly works again. At least for me anyway.
I have this problem occasionally, maybe twice with the ATT stock ROM, an once with the RRE 4.5SE ROM, mine rights itself after the application is closed and re-opened after a minute or so, so Im not that bothered, it is annoying though.
Nice, I'll try that..
Try the NATF ROM
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.
tried NAFT v4 already with the same hq keyboard lock/die/shut down issue
Ken98045 said:
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.
Click to expand...
Click to collapse
Same issue here, happened with both stock rom and NATF 4.1
It goes away after doing some random things like others have mentioned, but still annoying.
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect
Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app
same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .
You could try increasing the voltage.
ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.
just stopped using a custom kernel. i stopped using them cause of freezing issues.
So i have a Samsung Galaxy S3 with Paranoid Android 3.1 (March 1st build) and I also have Nova Launcher!
My home button used to always take me to the home screen! or main page! but randomly it keeps just opening recent apps! No matter what i do it just keeps opening recent apps i even went into nova launcher and assigned home to go to the home screen and still doesnt work! Any help or ideas!?
*EDIT
I just reset my phone and i think the problem seems to be Widget Locker which i used to replace my lockscreen, not 100% sure but it seems to be a bit buggy on 4.2 devices... it could even be some setting in it not 100% any help because this might happen again!?
Badouken said:
So i have a Samsung Galaxy S3 with Paranoid Android 3.1 (March 1st build) and I also have Nova Launcher!
My home button used to always take me to the home screen! or main page! but randomly it keeps just opening recent apps! No matter what i do it just keeps opening recent apps i even went into nova launcher and assigned home to go to the home screen and still doesnt work! Any help or ideas!?
*EDIT
I just reset my phone and i think the problem seems to be Widget Locker which i used to replace my lockscreen, not 100% sure but it seems to be a bit buggy on 4.2 devices... it could even be some setting in it not 100% any help because this might happen again!?
Click to expand...
Click to collapse
That happened to me before even on CM10.1; I believe the feedback is sometimes unresponsively accurate.
But if you use Nova Launcher, you can manually take off "recent apps" and replace with "home". But, sometimes it thinks your quick press is a hold, haha. I just know reboot will quickly fix it... for now.
PARAVEX said:
That happened to me before even on CM10.1; I believe the feedback is sometimes unresponsively accurate.
But if you use Nova Launcher, you can manually take off "recent apps" and replace with "home". But, sometimes it thinks your quick press is a hold, haha. I just know reboot will quickly fix it... for now.
Click to expand...
Click to collapse
AGH it happened again! and ya i think it just keeps glitching and thinking that my quick press is a hold! oh well a quick reset every now and then cant be that annoying... Thanks for the input!
What kernal are you running? I've had this issue as well and have wondered if it's kernal related. The only thing I could do to remedy the problem was reboot the phone.
Adamsaudio said:
What kernal are you running? I've had this issue as well and have wondered if it's kernal related. The only thing I could do to remedy the problem was reboot the phone.
Click to expand...
Click to collapse
Rebooting the phone seems to always fix it, I was running the included kernel along with Nova launcher and would run into it after about a half day runtime
I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated
It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk
Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?
nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that
hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol
ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk
ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.
Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.
Alright so, I haven't the slightest clue what caused this problem. I just happened to have rebooted my phone into bootloader mode as a way to ensure something I did didn't get transmitted when I re-enabled my Wifi which I happened to have disabled before rebooting and then re-enabled afterwards.
Anyways after I press reboot from the HBOOT menu, when my phone booted up the motion gestures would not work and I had an AOSP lockscreen...(take note im running ViperROM 1.8.0 on 4.4.3 firmware) oddly enough this isn't even enabled in the Viper Tweaks or any other tweaking apps I have. Soo why do I all of a sudden have these? It's as if I'm on an AOSP ROM but with Sense and a non Sense kernel? Even though NOTHING has changed today?? I haven't even been on my phone hardly at all besides that...
Why and how would I fix it?
Edit: Ok the tap to wake and swipe to wake actually work but double tap to turn screen back off is blocked because of the way the AOSP lockscreen functions. Swipe to shut screen off still works too. I just can't figure out how to remove this lockscreen
S1L3nTShaDoWz said:
Alright so, I haven't the slightest clue what caused this problem. I just happened to have rebooted my phone into bootloader mode as a way to ensure something I did didn't get transmitted when I re-enabled my Wifi which I happened to have disabled before rebooting and then re-enabled afterwards.
Anyways after I press reboot from the HBOOT menu, when my phone booted up the motion gestures would not work and I had an AOSP lockscreen...(take note im running ViperROM 1.8.0 on 4.4.3 firmware) oddly enough this isn't even enabled in the Viper Tweaks or any other tweaking apps I have. Soo why do I all of a sudden have these? It's as if I'm on an AOSP ROM but with Sense and a non Sense kernel? Even though NOTHING has changed today?? I haven't even been on my phone hardly at all besides that...
Why and how would I fix it?
Edit: Ok the tap to wake and swipe to wake actually work but double tap to turn screen back off is blocked because of the way the AOSP lockscreen functions. Swipe to shut screen off still works too. I just can't figure out how to remove this lockscreen
Click to expand...
Click to collapse
I had this same issue yesterday. I went to bed sat shut phone off with sense lock screen. Woke up Sunday powered on phone to see a aosp lock screen. I was like huh...I had to go to the play store an download HTC lock screen app they recently put in play store. Downloaded that then rebooted an sense lock screen is back. Try that out
Tigerstown said:
I had this same issue yesterday. I went to bed sat shut phone off with sense lock screen. Woke up Sunday powered on phone to see a aosp lock screen. I was like huh...I had to go to the play store an download HTC lock screen app they recently put in play store. Downloaded that then rebooted an sense lock screen is back. Try that out
Click to expand...
Click to collapse
The thing is..I already have that for some odd reason? It's right here and I never had this before either, it just randomly appeared and wanted me to update it a few days back. Strangely enough it was right after I downgraded back from 2.4.0 Viper ROM to 1.8.0 with a Nandroid. Should I just restore the Nandroid again*? it's literally exactly the same as this, I was gonna do it last night but it was far too late and I was tired.
S1L3nTShaDoWz said:
The thing is..I already have that for some odd reason? It's right here and I never had this before either, it just randomly appeared and wanted me to update it a few days back. Strangely enough it was right after I downgraded back from 2.4.0 Viper ROM to 1.8.0 with a Nandroid. Should I just restore the Nandroid again*? it's literally exactly the same as this, I was gonna do it last night but it was far too late and I was tired.
Click to expand...
Click to collapse
Try uninstalling that app via titabackup then go to play store an redownload it an reboot. If that don't work yeah I would definitely restore back up. But this solved my issue an it sounds like same as yours. Crazy tho huh?
Tigerstown said:
Try uninstalling that app via titabackup then go to play store an redownload it an reboot. If that don't work yeah I would definitely restore back up. But this solved my issue an it sounds like same as yours. Crazy tho huh?
Click to expand...
Click to collapse
"To finish updating lock screen please reboot now!"
Ohhhhh!! aaaaand...??? Waiting........................................................still booting...................dotdot....dotdotdotdotdot............still there
Firing the ion cannonz and restoring system backups, revert in process! *bzzzt---syste--msss faiiilllllinnngggg*
Seriously though it didn't work, restoring backups now LOL
S1L3nTShaDoWz said:
"To finish updating lock screen please reboot now!"
Ohhhhh!! aaaaand...??? Waiting........................................................still booting...................dotdot....dotdotdotdotdot............still there
Firing the ion cannonz and restoring system backups, revert in process! *bzzzt---syste--msss faiiilllllinnngggg*
Seriously though it didn't work, restoring backups now LOL
Click to expand...
Click to collapse
Well that's bs lol. You should have seen me when I woke up an seen this I was like wtf. So I went a removed sense toolbox an it was still there. I was totally lost. I did just what I told you to do an it came back an stayed. You would think if it worked for me it work for you u know. Hope your backup is alright. I like the fact HTC is dropping apps in play store so the don't have to wait on carrier to push ota to update a few things. But they should male sure it works rt..if you read all the reviews in playsotre bout this app. Not good at all some stock an locked users r in a bootloop from this updating an their only choice was factory reset. Not good
Tigerstown said:
Well that's bs lol. You should have seen me when I woke up an seen this I was like wtf. So I went a removed sense toolbox an it was still there. I was totally lost. I did just what I told you to do an it came back an stayed. You would think if it worked for me it work for you u know. Hope your backup is alright. I like the fact HTC is dropping apps in play store so the don't have to wait on carrier to push ota to update a few things. But they should male sure it works rt..if you read all the reviews in playsotre bout this app. Not good at all some stock an locked users r in a bootloop from this updating an their only choice was factory reset. Not good
Click to expand...
Click to collapse
Well I figured out the problem. When I restored it it was indeed solved or so I thought but I noticed the update was still available in the Play Store so I decided to back the original HTC LS in Titanium Backup and update to it. After having updated and rebooting I ended up with the AOSP lockscreen again, restoring the app in Titanium and rebooting again resulted in getting the original back.
Perhaps they intended this? Maybe it's their new lockscreen just with some faults, one being double tap to sleep doesn't work?
S1L3nTShaDoWz said:
Well I figured out the problem. When I restored it it was indeed solved or so I thought but I noticed the update was still available in the Play Store so I decided to back the original HTC LS in Titanium Backup and update to it. After having updated and rebooting I ended up with the AOSP lockscreen again, restoring the app in Titanium and rebooting again resulted in getting the original back.
Perhaps they intended this? Maybe it's their new lockscreen just with some faults, one being double tap to sleep doesn't work?
Click to expand...
Click to collapse
I use greenify to put my device to sleep. Works great just slide up from bottom of phone line you were going to use google search as I don't have that installed so greenify puts phone to sleep I like it.