It seems that every few days my Sprint Nexus S gets hung on the home screen, and I can no longer swipe to change screens. If I hit the bottom right and left buttons, I can manually change the screen, but swiping left or right changes nothing.
Has anyone else noticed this? I wonder if it's getting too bogged down with open apps. Coming from the Epic, I was constantly closing apps from the Program Monitor, which isn't on the Nexus S.
When I turn the screen on to check notifications and i expand a notification: text, facebook message, etc..
Even while my finger is touching the screen the screen turns off. This occurs both in power save mode and with power save mode turned off.
Its quite annoying, especially if i just want to read real quick what an email says.
Anyone else getting this?
Nope. Try doing a hard reset
Tried a second s6 and resetting the device. I get the same thing. I also have the unlock effect turned off.
My phone is also giving me problems on the lockscreen. I don't have an unlock effect either so I'm thinking be the problem. I notice when I turn on any other option my problem goes away. It just darkens my wallpaper to almost black. Did a hard reset as well.
I also noticed a huge lag when i tap a notification and then try to unlock. I'm also unable to double tap a notification on lock screen to open that specific app.
I tried using the buble unlock affect and still get the same problem. turn on screen->expand notification of given app while still holding my finger on the screen, then seconds later screen turns black
tlxxxsracer said:
I also noticed a huge lag when i tap a notification and then try to unlock. I'm also unable to double tap a notification on lock screen to open that specific app.
I tried using the buble unlock affect and still get the same problem. turn on screen->expand notification of given app while still holding my finger on the screen, then seconds later screen turns black
Click to expand...
Click to collapse
I see what you're saying about holding the finger on the screen and it still times out. Is it not like this on other lollipop phones, this is my first go with lollipop so I don't know? ...No lag for me, and I can tap then unlock and I'm in the app asap.
Sent from my SM-G900T using AllianceR(●)m
tenxo said:
I see what you're saying about holding the finger on the screen and it still times out. Is it not like this on other lollipop phones, this is my first go with lollipop so I don't know? ...No lag for me, and I can tap then unlock and I'm in the app asap.
Sent from my SM-G900T using AllianceR(●)m
Click to expand...
Click to collapse
Well maybe its cause i came from an AOSP rom on my Lg g2 but i would think if your finger it touching the screen it should stay on anyways.
I wish i could just double tap the notification and it opens the app versus tapping the notification and then having to swipe to unlock.
the lag when trying to unlock after tapping the notification is a little, its not instant like how it would when tapping on a heads-up notification
tlxxxsracer said:
Well maybe its cause i came from an AOSP rom on my Lg g2 but i would think if your finger it touching the screen it should stay on anyways.
I wish i could just double tap the notification and it opens the app versus tapping the notification and then having to swipe to unlock.
the lag when trying to unlock after tapping the notification is a little, its not instant like how it would when tapping on a heads-up notification
Click to expand...
Click to collapse
I just tried again...If you swipe down on the notification to read it, it should go up to like another screen (not literally) but the notification slides up basically were the clock and weather would be. There it doesn't time out until the screen time out you have set under display is reached, and you can read the other notifications too. What you are doing is pulling down the notification without letting go then it times out. Swipe the notification and let go of the screen.
Sent from my SM-G900T using AllianceR(●)m
Somehow I keep accidentally activating it, but it's basically just a dim blank screen that only shows the time and date, and the two tabs for the edge screen?
It happens every time I pick my phone up..thanks. I can't seem to find it anywhere.
This is the quick notification from the edge alerts. You can swipe the tabs on the side towards the middle of the screen to see what they contain.
Hello. So i made the switch to the S10e and i've been running into this issue where if i accidentally hold my phone with my finger just touching the selfie camera (or any part of the status/notification bar at the top of the screen), any and all other touch inputs just get disabled.
Any solutions to this? I assume Android thinks i'm going to pull it down and disables every other touch or something, but is there an option not to do that but still keep the draggable status bar? This also happens in all apps and the home screen/apps etc. no matter the screen.
Activating Show Taps in developer shows that the OS DOES see both my taps, the status bar and anything else, just that the software-side blocks other inputs once that initial status bar touch is seen and still active. It does NOT happen with the back/home/apps bar or generally anywhere else. I have tried making sure Nova launcher isn't doing anything. Tried Accidental touch protection On and Off and a host of other settings. Confirmed this is a status bar issue with hiding it in Samsung Internet and repeating the test.
Tried EdgeTouch with NiceLock but it only really helps for the sides which aren't really my issue.
Rarely this sometimes happens with stuff on screen too in the OS itself and in apps. Usually it's with triggering a function like holding the phone with touching the left hand of the screen and accidentally 'dragging' a menu' into view a few pixels, and then that disables all other input until it's gone. But that's fine since it's very rare. It's more more often than the status/notification bar is my main issue.
Cosmitz said:
... i accidentally hold my phone with my finger just touching ...
Click to expand...
Click to collapse
Do you use a case? That's what help'd me with accidental screen touches. An "ultra slim" case was all it took for me. Hope you find what works for you.
I am really against cases, as i really want a compact fone, and there are extremely few which get launched with AMOLED nowdays. I'd rather solve this via software.
Up?
Up?
Up?
up?
Up.
Up.
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!