Related
So I have the Androidified tpu case which makes the power button kinda hard to press. Also I use NOLED which wont wake with the power button when there is a notification. For these reasons it would be nice to wake the phone with the front face buttons, as long as they dont accidentally get pressed in my pocket
So I was wondering if i could modifiy
system/usr/keylayout/s3c-keypad.kl
and add a few WAKE_DROPPED where wanted and get the desired effect???
Let me know if you've done this already or you know it works. Ive seen similar things done with other phones. If not Ill just try it myself once i get a chance to make an odin backup of my phone.
I've actually found a way to do it. Instead of using the home button tho, all physical buttons work. Its a hack to remove the lockscreen. I actually replaced my lockscreen with Ripple Lock from the market with this. Give a nice Honeycomb style lockscreen with great options. Here's what I did...
Go to the dialer and enter #83786633, then press home.
Go back into the dialer, clear the numbers and enter *#22745927 and enter the SPC code 000000.
Hit the "HiddenMenu Enable Radio" button. Press home.
Go back to the dialer, enter *#7594# and hit the "Shutdown" button, then home.
The lockscreen is now GONE. I have never reversed it to get the lockscreen back tho, I hate the AOSP lockscreen, and Puzzle lockscreens. The Ripple Lock app from the market is very smooth, fluid and has totally replaced them annoying lockscreens. Best of all, any physical button now wakes up my phone I don't have any accidental presses either. Everything is great. Hope this helps!!!!!
Sent from my SCH-I510 using XDA Premium App
interesting...I saw a few other apps that would modify buttons/screens. My only concern is bloating up my rom...would love to do within the system. Also whenever I call numbers and press in codes I feel like I might be giving away my life savings to an anonymous bank account in the Caribbean lol
Tried changing the .kl file. Specifically the home button. Doesnt seem to work. Let me know if anyone figures this out
youngpettyboi said:
I've actually found a way to do it. Instead of using the home button tho, all physical buttons work. Its a hack to remove the lockscreen. I actually replaced my lockscreen with Ripple Lock from the market with this. Give a nice Honeycomb style lockscreen with great options. Here's what I did...
Go to the dialer and enter #83786633, then press home.
Go back into the dialer, clear the numbers and enter *#22745927 and enter the SPC code 000000.
Hit the "HiddenMenu Enable Radio" button. Press home.
Go back to the dialer, enter *#7594# and hit the "Shutdown" button, then home.
The lockscreen is now GONE. I have never reversed it to get the lockscreen back tho, I hate the AOSP lockscreen, and Puzzle lockscreens. The Ripple Lock app from the market is very smooth, fluid and has totally replaced them annoying lockscreens. Best of all, any physical button now wakes up my phone I don't have any accidental presses either. Everything is great. Hope this helps!!!!!
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Have you rebooted your phone since the change? I did this mod. and it worked fine until I rebooted. After a reboot the lock screen fix was still working, but the physical buttons no longer woke up the phone. Others have reported the same issue.
Yes, actually I always turn my phone off at nite, and when I turn it back on, my physical keys work fine to wake up the phone. Haven't had a single problem since. I would rather do it this way instead of going ib the system and screwing something up. Not that good at stuff like that lol.
Sent from my SCH-I510 using XDA Premium App
youngpettyboi said:
I've actually found a way to do it. Instead of using the home button tho, all physical buttons work. Its a hack to remove the lockscreen. I actually replaced my lockscreen with Ripple Lock from the market with this. Give a nice Honeycomb style lockscreen with great options. Here's what I did...
Go to the dialer and enter #83786633, then press home.
Go back into the dialer, clear the numbers and enter *#22745927 and enter the SPC code 000000.
Hit the "HiddenMenu Enable Radio" button. Press home.
The lockscreen is now GONE. I have never reversed it to get the lockscreen back tho, I hate the AOSP lockscreen, and Puzzle lockscreens. The Ripple Lock app from the market is very smooth, fluid and has totally replaced them annoying lockscreens. Best of all, any physical button now wakes up my phone I don't have any accidental presses either. Everything is great. Hope this helps!!!!!
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
When it comes time to enter *#7594# and hit the "Shutdown" button, What is the "shutdown button? I did not see this anywhere.
youngpettyboi said:
Yes, actually I always turn my phone off at nite, and when I turn it back on, my physical keys work fine to wake up the phone. Haven't had a single problem since. I would rather do it this way instead of going ib the system and screwing something up. Not that good at stuff like that lol.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Huh... LUCKY! I'll have to try it again. Maybe I have an app. that's conflicting with my hard buttons.
The "Shutdown" button comes right after u enter *#7594#. Click it when it pops up. Its an onscreen button. Not the physical bottom on the phone.
Sent from my SCH-I510 using XDA Premium App
Or just use WidgetLocker...
{SDCharge Humb£e 1.25}
It runs fine but if I hit the home button, it bypasses the lock screen and just goes to my home screen. The power button works, its just the home button issue. Can anyone share their settings for widget locker or let me know what I'm doing wrong.
Sent from my Nexus 7 using xda app-developers app
I've only been using Widget Locker for a couple of days but try this:
Go to the WidgetLocker app - Press the settings Icon on top right corner - Select Buttons & Inputs - Uncheck Allow Home Button.
See if that works.
I also have a question if anyone can help. How do I get Google now on the Jelly Bean Themed slider. I can get Google Now by setting the app in the unlock screen, but how do I make it look like the stock Google Now app?
Thanks
iPhoneSlayer said:
I've only been using Widget Locker for a couple of days but try this:
Go to the WidgetLocker app - Press the settings Icon on top right corner - Select Buttons & Inputs - Uncheck Allow Home Button.
See if that works.
I also have a question if anyone can help. How do I get Google now on the Jelly Bean Themed slider. I can get Google Now by setting the app in the unlock screen, but how do I make it look like the stock Google Now app?
Thanks
Click to expand...
Click to collapse
That worked thanks!
What's the jelly bean themed slider? If I can find it I can see if I can figure out your answer.
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
That worked thanks!
What's the jelly bean themed slider? If I can find it I can see if I can figure out your answer.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Glad I could help.
The slider I talking about is the slider to unlock the phone. You can chose from a list of slider like honeycomb, ICS, Jellybean, Sense, etc. I want it to look like my N7 tablet where if I slide it up, it goes to Google Now. I can still get Google now by adding the shortcut to google search, but I want the icon to look like the stock look. It's kinda hard to explain, sorry.
iPhoneSlayer said:
Glad I could help.
The slider I talking about is the slider to unlock the phone. You can chose from a list of slider like honeycomb, ICS, Jellybean, Sense, etc. I want it to look like my N7 tablet where if I slide it up, it goes to Google Now. I can still get Google now by adding the shortcut to google search, but I want the icon to look like the stock look. It's kinda hard to explain, sorry.
Click to expand...
Click to collapse
Oh okay yeah. I'm using the JB slider now. Mine has the stock looking "Google" for Google now. It just doesn't have the circle around the word " Google". I can post picture if you want.
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Oh okay yeah. I'm using the JB slider now. Mine has the stock looking "Google" for Google now. It just doesn't have the circle around the word " Google". I can post picture if you want.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Nevermind, I'm dumb. I've been trying to add it as a shortcut, but I should have used WidgetLocker Actions to choose google. Now it's all good.
Thanks
Oh alright good.
Ugh its not working now. Can you go into advance an go to home helper. What do you have there? I think that's regarding the home button. Its weird. Its off an on with it working.
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
Oh alright good.
Ugh its not working now. Can you go into advance an go to home helper. What do you have there? I think that's regarding the home button. Its weird. Its off an on with it working.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think Home helper is for some launcher settings.
If you uncheck Allow Home Button under the Buttons and Inputs, then it should work, however it may be a bug that sometimes causes it not to work. I've noticed that widget locker acts weird if the phone is charging. I have only been using it for a few days so I'm sorry if I wasn't more helpful.
tu3218 said:
It runs fine but if I hit the home button, it bypasses the lock screen and just goes to my home screen. The power button works, its just the home button issue. Can anyone share their settings for widget locker or let me know what I'm doing wrong.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem the other day. Particularly after I updated to 4.1.1. The lockscreen would unlock (once awake) by pressing home.
I solved it by using HomeHelper (widgetlocker settings -> advanced -> homehelper).
1) tick the "HomeHelper component" and choose "WL HomeHelper" as the default.
2) tap "HomeHelper's Launcher" and choose your default launcher (Touchwiz, Nova, AWG, Launcher Pro, etc.)
3) Make sure "HomeHelper Block Home" is checked.
4) (Optional) You can also choice "Block Home in other apps" to return to the lockscreen after opening apps from the notification bar or shortcuts.
HomeHelper worked fine for me, but I got the feeling it was slowing down my system a tiny bit. Most notably, the wallpaper would quickly blink every time I hit the home button (what is effectively happening is that the home button activates HomeHelper, that then activates the launcher). It was not a major deal but I personally found it annoying.
However, I may have stumbled upon the culprit behind all this: S-Voice. Once I upgraded to 4.1.1 I turned off the option to activate s-voice through pressing home twice (S-voice -> menu button -> Settings) because I was happy to use Google Now (aka Voice Search) instead. That is when I had the problem with widgetlocker's lock screen unlocking with the home button. After not liking HomeHelper's performance, I reluctantly went back to the default Touchwiz lockscreen (I maintained my custom launcher though, and reset the home button to default to it).
After Google Now failed embarrassingly to call the right people from my contacts list (most of whose names are foreign), I decided to go back to using S-voice. I reactivated the "press home twice" option. However, I still hated the "slide anywhere to unlock" Touchwiz lockscreen, as well as its inability to silence the ringer in one slide (you have to either hold the power button or open the notification bar first). So I went crawling back to widgetlocker for forgiveness. I activated widgetlocker (I did not meddle with the HomeHelper settings assuming those were already set), and later noticed that the lockscreen was not being unlocked with the home button, while the homescreen wallpaper was no longer blinking. I went into the homehelper settings and made sure it was turned off, and also made sure that the home button was by default linked to the custom launcher (not HomeHelper). I confirmed my theory by deactivating S-voice's double-press home option, and the problem above came back.
tl;dr. I theorize that the problem is caused by turning off S-Voice's quick-access option (double-press home). You can also use Widgetlocker's HomeHelper if you don't want to turn S-Voice back on. I hope my experience is not simply coincidence and someone could confirm this theory.
Found this thread because I was having basically the same problem. Widget locker's lock screen would be bypassed coming from sleep by single pressing home (power button from sleep continued to work normally). I could not fix this using any method mentioned here so far, except for enabling S Voice via double tapping home. I emailed the dev and hope it gets fixed, because I'd like to avoid the lag added to the home button by having double tap for S Voice enabled.
Anyone else have an alternate solution?
netter123 said:
Found this thread because I was having basically the same problem. Widget locker's lock screen would be bypassed coming from sleep by single pressing home (power button from sleep continued to work normally). I could not fix this using any method mentioned here so far, except for enabling S Voice via double tapping home. I emailed the dev and hope it gets fixed, because I'd like to avoid the lag added to the home button by having double tap for S Voice enabled.
Click to expand...
Click to collapse
Oddly enough this fixed it for me too. I had disabled S-Voice yesterday and today noticed that using the home button bypassed Widget locker. I re-enabled S-Voice and all is back to normal. Hopefully the dev will be able to give us an answer soon.
Agh ...I was so excited to get back to WidgetLocker I got used to from my pevious phone, only to find out this little anoying thing. Are there any news, some reply from the dev ?
So I am using widgetlocker, and my home button only wakes to my widgetlocker screen (never see the touchwiz lockscreen). I have s-voice/double-tap disabled.
In widgetlocker settings, under "advanced" I have root checker checked, homehelper component checked, "select system home" is widgetlocker, and "homehelper's launcher" is the launcher I use (nova in my case).
Does that not fix the problem for you all?
(On CleanRom 5.6)
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Does your launcher blink every time you press home button while in the launcher itself ? If yes, then you know why it does not work for us.
JustSomeDude said:
So I am using widgetlocker, and my home button only wakes to my widgetlocker screen (never see the touchwiz lockscreen). I have s-voice/double-tap disabled.
In widgetlocker settings, under "advanced" I have root checker checked, homehelper component checked, "select system home" is widgetlocker, and "homehelper's launcher" is the launcher I use (nova in my case).
Does that not fix the problem for you all?
(On CleanRom 5.6)
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No, these settings don't solve the problem for me. I messed with various combinations of the settings your talking about as well, but no matter what I still bypass the lock screen (and also experience a quick blink every time home is pressed, which would be a secondary concern). I'm also on the latest Cleanrom and use Nova.
netter123 said:
No, these settings don't solve the problem for me. I messed with various combinations of the settings your talking about as well, but no matter what I still bypass the lock screen (and also experience a quick blink every time home is pressed, which would be a secondary concern). I'm also on the latest Cleanrom and use Nova.
Click to expand...
Click to collapse
Hmm, strange... One more setting I have: do you also have "appear on boot" checked under Behavior? Otherwise I'm stumped as to why it works for me and not you.
As for the quick blink, yeah, I have that too - I assume from widgetlocker being assigned as home, thus registering that before going to nova - but I hit home so rarely that I barely notice it.
Sent from my SCH-I535 using Xparent BlueTapatalk 2
JustSomeDude said:
Hmm, strange... One more setting I have: do you also have "appear on boot" checked under Behavior? Otherwise I'm stumped as to why it works for me and not you.
As for the quick blink, yeah, I have that too - I assume from widgetlocker being assigned as home, thus registering that before going to nova - but I hit home so rarely that I barely notice it.
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yeah have that checked too. Must be some setting slightly different somewhere though. Not that big of a deal, I've just been living with the slight lag on home press and sounds like otherwise I'd have to get used to the quick blink.
Btw never got a response from the developer so that's kind of disappointing..
It's working for me but I get the annoying flicker when hitting the home button as well. It's a drag for sure. Go Launcher is my launcher. Shoulda did my homework before paying for this one. Love what the lockscreen can do but has issues with the home button for sure
Dothgar said:
I had the same problem the other day. Particularly after I updated to 4.1.1. The lockscreen would unlock (once awake) by pressing home.
I solved it by using HomeHelper (widgetlocker settings -> advanced -> homehelper).
1) tick the "HomeHelper component" and choose "WL HomeHelper" as the default.
2) tap "HomeHelper's Launcher" and choose your default launcher (Touchwiz, Nova, AWG, Launcher Pro, etc.)
3) Make sure "HomeHelper Block Home" is checked.
4) (Optional) You can also choice "Block Home in other apps" to return to the lockscreen after opening apps from the notification bar or shortcuts.
HomeHelper worked fine for me, but I got the feeling it was slowing down my system a tiny bit. Most notably, the wallpaper would quickly blink every time I hit the home button (what is effectively happening is that the home button activates HomeHelper, that then activates the launcher). It was not a major deal but I personally found it annoying.
However, I may have stumbled upon the culprit behind all this: S-Voice. Once I upgraded to 4.1.1 I turned off the option to activate s-voice through pressing home twice (S-voice -> menu button -> Settings) because I was happy to use Google Now (aka Voice Search) instead. That is when I had the problem with widgetlocker's lock screen unlocking with the home button. After not liking HomeHelper's performance, I reluctantly went back to the default Touchwiz lockscreen (I maintained my custom launcher though, and reset the home button to default to it).
After Google Now failed embarrassingly to call the right people from my contacts list (most of whose names are foreign), I decided to go back to using S-voice. I reactivated the "press home twice" option. However, I still hated the "slide anywhere to unlock" Touchwiz lockscreen, as well as its inability to silence the ringer in one slide (you have to either hold the power button or open the notification bar first). So I went crawling back to widgetlocker for forgiveness. I activated widgetlocker (I did not meddle with the HomeHelper settings assuming those were already set), and later noticed that the lockscreen was not being unlocked with the home button, while the homescreen wallpaper was no longer blinking. I went into the homehelper settings and made sure it was turned off, and also made sure that the home button was by default linked to the custom launcher (not HomeHelper). I confirmed my theory by deactivating S-voice's double-press home option, and the problem above came back.
tl;dr. I theorize that the problem is caused by turning off S-Voice's quick-access option (double-press home). You can also use Widgetlocker's HomeHelper if you don't want to turn S-Voice back on. I hope my experience is not simply coincidence and someone could confirm this theory.
Click to expand...
Click to collapse
Thank you. It is what i want
I have noticed since yesterday's Jelly Bean update (4.1.1) that if you have an app open (say a browser for example) and you let your screen timeout, when you press the home button it will turn the screen on screen up and take you back to your home screen. Used to with ICS it would just turn the screen on and you could continue in the app. Now it takes you all the way back home and you have to re-open the app to continue in it.
I was wondering if everyone is getting this same result or if it is just me.
Thanks!
I just tried it with Google Now and it returned to the app. I tried the Android browser and it returned the app as well. You might want to power down, pull the battery, then restart. Updates can sometimes act a little wonky at first. Occasionally (and unfortunately) a hard reset can FINALLY make an update work correctly.
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Yea, that fixed it. I don't like S-Voice so I had that option turned off. Apparently it works different with this update then it did with ICS.
I've actually went in there and enabled that option then went into Application Management and disabled S-Voice. Now, if I accidently double tap my home button it just goes to a black screen for a second then back to the home screen. (Better than opening up S-Voice)
Thanks for your help!
I've found if you use a pattern password the home button "feature", to go back home works like how it used to
Sent from my SCH-I535 using xda app-developers app
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
I find the lag to be to annoying when s-voice is enabled. A fast press of the power button will wake up the phone without closing the app you are using and you can keep s-voice turned off.
SlimSnoopOS said:
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
grr, I couldnt agree more. I turned off that feature to reduce home button lag in ICS, now it closes any app open. Hopefully theres a fix
We'll find out. I dislike these small, unnecessary changes that Samsung has implemented. Horizontal pinch to expand notifications is another unnecessary change on VRBLK3.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
aromig said:
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
lv2bsilly said:
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
Click to expand...
Click to collapse
I feel your pain i also suffer from this same problem i had ics stock rom upgraded to hpyer drive rl14 and after that my home button only wakes up to a long press nothing seems to work i even reassigned soft keys functions so home would do back option and same thing,
Hello,
After a few days of using the phone, I installed Lightning Launcher and set it as default. I got some bugs with the lockscreen (i'll explain later) so I reverted back to the Xperia original launcher.
Now, after not using LL, I still have that same issue. I'm pretty sure it hasn't anything to do with LL or anything, but I prefer mentionning it just in case.
(tl;dr)
Whenever I press power button, it is supposed to immediately scan the fingerprint. It doesn't anymore and instead of the normal lockscreen I have a completely blank screen, only with Back and Home button.
Finger is not scanned, I can't swipe in any direction BUT, if I press the Home button, lockscreen shows up (it slides from the left side), as if I already swiped to the right.
That's pretty annoying when the purpose of fingerprint scan is to immediately unlock
Got any idea ? Somebody has the same problem maybe ?
EDIT:
Okay my bad. I uninstalled LL completely and the problem didn't show up anymore. I reinstalled because I remembered it can also be used as a lockscreen, and i disabled that in its settings. I'll check if problem continues but if not, I'll come back to inform about it.
Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
Your browser is not able to display this video.
I use Xposed edge pro for system gesture and it's fast AF
abdullaHD said:
Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
View attachment 5589763
Click to expand...
Click to collapse
I'm not seeing much of any delays in your video but maybe its because it's too small on my screen. If you want to speed things up navigating between apps go into developer options and there are 3 parameters you can play with (top 3 in screen shot)
I'm having different issues after updating. I'm on a Verizon S22 Ultra, using Nova Launcher with gestures and power savings mode enabled.
I'm having an issue where, after I use the pull down gesture (swiping downward) on the home screen (for example, if I'm just trying to switch from wifi to mobile data, or trying to turn off Bluetooth, or trying to turn on location) a lot of the time I'll have a delayed and or almost immediate ghost touch input, without touching anything.
Sometimes, even if I don't touch anything and I just swipe down to bring down the pull down ui, it'll act like I used the swipe up gesture and clear the pull down ui and return me to the home screen. Other times it'll act like I pressed the home button icon (there will be a soft white glow that shows up around the home screen icon), even though I never touched the home button icon.
Other times, on the home screen, I'll use the slide down gesture. The pull down comes down, and almost immediately it'll act like I have pressed the recents button and my recent apps pops up. It's like someone else is controlling my phone, but only on the homescreen, very annoying.
This only seems to happen when I'm on my home screen and trying to use the pulldown gesture when power savings mode is enabled. Although, it did happened a couple of times in Samsung Internet Browser Beta when power savings was enabled and prior to the recovery cache clearing. Randomly, the settings ui popped up on me while trying to type in an internet address, but I never touched the hamburger menu icon in the lower right.
This doesn't seem to happen in the Samsung Internet Browser Beta anymore after performing the recovery cache clearing. When it was happening in the browser, I'd try turning off the power saver and the ghost touches seemed to stop.
On the homescreen, once the pulldown comes down, even when pulling down for a second time to fully expand the ui (sometimes almost immediately and or even after a few seconds of not touching anything), it'll either take me right back to the home screen (like I pressed the home button icon or it'll pull up the recent apps ui and I never touched anything). It is wonky.
I've tried clearing cache through the recovery method and it's still acting up when power saving mode is enabled. The only thing that seems to have caused it to stop, is turning off power saver mode.
Anyone else experiencing this issue of ghost touches with power savings enabled along with Nova Launcher's gestures (or on any other 3rd party launcher and or even the stock launcher perhaps?) on the home screen? I haven't had time to record this yet, I'll have to get some video of it, just wanted to see if anyone else is experiencing this or knows of a better workaround perhaps?
Justinphxaz said:
I'm having different issues after updating. I'm on a Verizon S22 Ultra, using Nova Launcher with gestures and power savings mode enabled.
I'm having an issue where, after I use the pull down gesture (swiping downward) on the home screen (for example, if I'm just trying to switch from wifi to mobile data, or trying to turn off Bluetooth, or trying to turn on location) a lot of the time I'll have a delayed and or almost immediate ghost touch input, without touching anything.
Sometimes, even if I don't touch anything and I just swipe down to bring down the pull down ui, it'll act like I used the swipe up gesture and clear the pull down ui and return me to the home screen. Other times it'll act like I pressed the home button icon (there will be a soft white glow that shows up around the home screen icon), even though I never touched the home button icon.
Other times, on the home screen, I'll use the slide down gesture. The pull down comes down, and almost immediately it'll act like I have pressed the recents button and my recent apps pops up. It's like someone else is controlling my phone, but only on the homescreen, very annoying.
This only seems to happen when I'm on my home screen and trying to use the pulldown gesture when power savings mode is enabled. Although, it did happened a couple of times in Samsung Internet Browser Beta when power savings was enabled and prior to the recovery cache clearing. Randomly, the settings ui popped up on me while trying to type in an internet address, but I never touched the hamburger menu icon in the lower right.
This doesn't seem to happen in the Samsung Internet Browser Beta anymore after performing the recovery cache clearing. When it was happening in the browser, I'd try turning off the power saver and the ghost touches seemed to stop.
On the homescreen, once the pulldown comes down, even when pulling down for a second time to fully expand the ui (sometimes almost immediately and or even after a few seconds of not touching anything), it'll either take me right back to the home screen (like I pressed the home button icon or it'll pull up the recent apps ui and I never touched anything). It is wonky.
I've tried clearing cache through the recovery method and it's still acting up when power saving mode is enabled. The only thing that seems to have caused it to stop, is turning off power saver mode.
Anyone else experiencing this issue of ghost touches with power savings enabled along with Nova Launcher's gestures (or on any other 3rd party launcher and or even the stock launcher perhaps?) on the home screen? I haven't had time to record this yet, I'll have to get some video of it, just wanted to see if anyone else is experiencing this or knows of a better workaround perhaps?
Click to expand...
Click to collapse
I use Nova with power saving mode enabled and have no issues with ghost touches. Are you using the latest version of Nova 7? How did you migrate from your old phone (backup and restore Nova settings)?
I used to have this problem with Dr. Ketan's rom but not on samsung's.
March update
abdullaHD said:
Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
View attachment 5589763
Click to expand...
Click to collapse
That's known issue with Gestures and launchers on almost all android phones. I have that issue on Pixel too if I use Nova or other launcher
Rubby1025 said:
I use Nova with power saving mode enabled and have no issues with ghost touches. Are you using the latest version of Nova 7? How did you migrate from your old phone (backup and restore Nova settings)?
Click to expand...
Click to collapse
Okay, cool. I appreciate your input. I'm using Nova 7.0.57. Yeah, I loaded Nova on the phone from my old Note 20 to the S22 Ultra. Things have been fine, no ghost touches. I noticed it happening right after I downloaded and installed the April security patch.
At first I thought it was me going too fast through everything like usual and maybe I was hitting the back button or home button or just off the screen by accident and closing out of the expanded notifications ui. But, it has continued, just not in the Samsung Internet Browser Beta anymore.
Now it's only when I'm on the home screen and I try swiping down to expand notifications, then it acts all wonky and either closes by itself and or takes me to the recents ui.
I don't use nova, but have picked up phantom touches in certain apps....this is after the April update. I would open ambivision app...in the settings menu it would exit out of settings or sub menus in the app...thought it's an app bug, but sometime when swiping down the notification bar I also get phantom swipes closing the pulldown as if I swiped up....few other appa also random swipes/gestures
termdj said:
I don't use nova, but have picked up phantom touches in certain apps....this is after the April update. I would open ambivision app...in the settings menu it would exit out of settings or sub menus in the app...thought it's an app bug, but sometime when swiping down the notification bar I also get phantom swipes closing the pulldown as if I swiped up....few other appa also random swipes/gestures
Click to expand...
Click to collapse
Yup, I thought it was just some apps that had bugs but it's happening on the pull down notifications bar and expanding the notifications too. This all happened after the April security patch update. I didn't have any of this at all prior.
I noticed it immediately after the update, I opened the Samsung internet beta browser, started browsing and had the settings ui popping up and the recents ui pop up. I thought I was just moving through things too fast and hitting buttons. Then on the notification pull downs, they started rolling back up right after I'd pull it down.
It still happens quite a bit and the only thing I've found that seems to stop the phantom touches is turning off power saving mode. Dark mode also seems to slow it down, but it doesn't always stop it. It must have something to do with being in 60hz mode instead of 120hz as power savings reduces the refresh rate to 60hz.
I also picked it up after the update. .also with the pull down of notifications etc
I also started seeing phantom touches after the Apr update - especially with Google News app. I turned off extra dim feature and now I don't get any phantom touches!