Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Luefox said:
Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Click to expand...
Click to collapse
I also have this issue. I thought locking the keyboard in the memory would resolve it but nope. No idea what causes it. I managed to fix it a while back but I have no idea what I did that fixed it.
Luefox said:
Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Click to expand...
Click to collapse
Clear the app data for Google Keyboard. That seems to have fixed it for me.
hillbeast said:
Clear the app data for Google Keyboard. That seems to have fixed it for me.
Click to expand...
Click to collapse
This works for me temporarily, but it's usually within a day or two that the keyboard becomes slow to respond again.
If left alone for long enough without clearing the data, it becomes slow to respond just switching between apps too.
Related
Hey all,
I'm curious if any of you are having this issue.
Basically, I'll lock my phone then get a text, groupme, or hangouts message and then unlock and swipe down to see my notifications/messages, then I will tap on one to respond and then go to type and nothing will appear. The word suggestions at the top of the keyboard are accurate to what I'm typing, but nothing appears.
If I close the app and re-open that resolves the issue.
Sometimes re-locking and waiting a bit will resolve the issue as well.
This has also occurred in Safe Mode for me.
Nexus 5
4.4.4
Stock
Apex Launcher
Textra, Hangouts, Groupme
Stock Google Keyboard
I created this thread because I couldn't find anything else already posted: https://productforums.google.com/fo...footer#!msg/hangouts/4K5CH4O4v-w/MOuJ3Q3PRMkJ
Similar thread from 2012: http://forum.xda-developers.com/galaxy-nexus/help/keyboard-type-unlock-whatsapp-t1557459
Thank you,
-Fo
Not exactly what you're going through, but when I try to type in Chrome (forum replies, reddit, etc) my keyboard will lock up for a good 30-45 seconds and I have to wait for it to catch up. It's completely frustrating.
FoRealz said:
Hey all,
I'm curious if any of you are having this issue.
Basically, I'll lock my phone then get a text, groupme, or hangouts message and then unlock and swipe down to see my notifications/messages, then I will tap on one to respond and then go to type and nothing will appear. The word suggestions at the top of the keyboard are accurate to what I'm typing, but nothing appears.
If I close the app and re-open that resolves the issue.
Sometimes re-locking and waiting a bit will resolve the issue as well.
This has also occurred in Safe Mode for me.
Nexus 5
4.4.4
Stock
Apex Launcher
Textra, Hangouts, Groupme
Stock Google Keyboard
I created this thread because I couldn't find anything else already posted: https://productforums.google.com/fo...footer#!msg/hangouts/4K5CH4O4v-w/MOuJ3Q3PRMkJ
Similar thread from 2012: http://forum.xda-developers.com/galaxy-nexus/help/keyboard-type-unlock-whatsapp-t1557459
Thank you,
-Fo
Click to expand...
Click to collapse
entropism said:
Not exactly what you're going through, but when I try to type in Chrome (forum replies, reddit, etc) my keyboard will lock up for a good 30-45 seconds and I have to wait for it to catch up. It's completely frustrating.
Click to expand...
Click to collapse
Not the same issue, but I also have the same issue in Chrome and Firefox. So you are not alone, but that's not the issue I'm referring to for this thread.
Hi.
I'm experiencing a nasty little bug when I try to reply to a message from a quick reply window when the screen is locked.
This is what happens:
If the screen is off and I get message in an app that has the quick reply feature in lock screen enabled, as soon as I tap the text field the screen starts flickering horribly, like switching very rapidly between the lock screen and the quick reply window trying to open the keyboard. It feels like the phone is going to explode. I first noticed this when trying out Telegram, I thought it was an issue with that particular app, but then I enabled the feature in Whatsapp just to test, and the same thing happened.
Could this be a Lollipop bug? I don't know much about this stuff, hopefully someone can shed some light here.
I'll try to upload a screen record later in case I'm not explaining myself (which is likely due to my limited English vocabulary).
EDIT: Ok, here's the screen record -> https://www.youtube.com/watch?v=KI9d_PiQ9zA&index=1&list=UUJBPMHNSOxSqUiEkqtQiTRg (I know I should've covered my contact's name but I didn't know how to. I trust you won't murder her )
Thanks in advance.
__________
Nexus 5 running Android 5.0 - No root
Ok, the problem is with the Keyboard (Swiftkey), Google keyboard works fine in this situation. It has already been reported in the Swiftkey forum.
lollipop flickers when replying whatsapp messages at lock screen
I do not have swiftkey installed in my nexus 5 but also having issue of flickering.
gmk101 said:
I do not have swiftkey installed in my nexus 5 but also having issue of flickering.
Click to expand...
Click to collapse
Hmm. Also with quick reply windows in lock screen?
Correct. Try to reply whatsapp message at the lock screen and the screen goes crazily flickering. It flickers then get frozen for 10 seconds or so. If I agree to send a report to Android, it allows me to unlock the phone, then minimize the reporting screen, goes into whatsapp to reply.
gmk101 said:
Correct. Try to reply whatsapp message at the lock screen and the screen goes crazily flickering. It flickers then get frozen for 10 seconds or so. If I agree to send a report to Android, it allows me to unlock the phone, then minimize the reporting screen, goes into whatsapp to reply.
Click to expand...
Click to collapse
Have you tried with other apps with quick reply feature? If not, try it just to see. Also, what keyboard do you use? I don't see this with the Google stock keyboard
Adrianrff said:
Have you tried with other apps with quick reply feature? If not, try it just to see. Also, what keyboard do you use? I don't see this with the Google stock keyboard
Click to expand...
Click to collapse
I use a keyboard called TouchPal. The problem only occurs when the screen gas security lock. If the screen is not locked, no issues.
I have the same issue with Nexus 4 and Swiftkey. Had to switch back to Google keyboard.
Exact same problem, different variables.
I have this EXACT same issue on my OPO. It occurs with my handcent popups windows and I use TouchPal. It looks like its flickering back and forth between the on screen notification of incoming texts and the popup window. If I disabled the notifications, the popup window still flickers.
From the sounds of the above posts, its not limited to which keyboard or app popup but more likely the lollipop lockscreen.... (I am running latest CM12 nightly but its been happening ever since Ive gone to lollipop)
Cant wait until this problem is pinned down.
Am I going crazy, or is there no way to stop notifications from waking the screen? Everytime I get any sort of notification, my screen wakes up to display the notification on the lock screen, and then goes back to sleep a second later. I would like to turn this off and it drains battery.
Sauveur said:
Am I going crazy, or is there no way to stop notifications from waking the screen? Everytime I get any sort of notification, my screen wakes up to display the notification on the lock screen, and then goes back to sleep a second later. I would like to turn this off and it drains battery.
Click to expand...
Click to collapse
I've noticed this happens to me when I receive an SMS, but nothing else. I don't think this is the default behaviour. Do you have an app installed that maybe does this? LightFlow?
Well I did install Snaplock for a hot second but I've since uninstalled it. Maybe it changed some setting somewhere that I can't find?
Any help for this? It's driving me crazy.
Sauveur said:
Any help for this? It's driving me crazy.
Click to expand...
Click to collapse
I have tried to find a solution for this, but I haven't been able to. I am guessing it is just unconfigurable behaviour of the Samsung messaging app.
Yep. I installed 8sms and Textra. Both allow you to disable the screen wake. Decided on 8sms for the long haul.
Help
Ok, so I am also irritated by the same issue with the screen waking up every time I get a text. My phone is usually in my pocket, and by trying to take it out to see the text, my camera or dial screen is opened cause I touched it while the screen was on. I have tried downloading Textra, Handcent, and 8sms to use instead, but in every one of those, when I try to send a photo, it fails, and I have dug through all the settings in those apps as well. I can send them on the stock messaging app just fine.
Has anyone found out how to turn the screen wake up off yet, or what am I missing on the other apps that is preventing pictures to send?
The other thing that is bothering me is that in the stock messaging app, it is displaying a call back # on every text I receive. Is there a way to turn this off?
Any suggestions would be greatly appreciated,
-Nick
I'm also trying to find the solution to this. G920I with Vodafone Australia.
Did anyone find a resolution to this issue? My phone turns on with every notification, not just sms.
I don't have my phone on me, but check settings > lockscreen and security > Show information or
settings > lockscreen and security > other security settings > notification access
I disabled all lock screen notifications and the screen still turns on randomly. I thought it may have been facebook so I disabled notifications then uninstalled the app with no luck. This problem is very annoying to say the least, when I go for a run I take my phone to stream music etc and can end up taking a few hundred pics of my pocket; lol.
Yeah I've this problem too, samsung didn't include the option to disable it :\
Are you saying there is no way to stop the screen from coming on?
Doesn't look like you can disable it, sadly. Nothing stock in touchwiz that gives that functionality. Or am I wrong? I just searched the entire settings on my phone..
Sent fra min SM-G920F via Tapatalk
another annoyed user, looking for a solution
The inability to prevent the wake-up is annoying not only because of the instant battery usage, but because when the phone is in pocket it then causes all kinds of mispresses which lead to unintended app openings, changes, and screen staying on much longer. Samsung needs to provide option to disable screen wake on notification.
Samsung we have f#%$*ng RGB LED for notification!
Try the Screen Notifications free app
Try the Screen Notifications free app. I did and meantime it's OK. Looks it may work for the desperate people like we are....
https://play.google.com/store/apps/details?id=com.lukekorth.screennotifications
Sauveur said:
Am I going crazy, or is there no way to stop notifications from waking the screen? Everytime I get any sort of notification, my screen wakes up to display the notification on the lock screen, and then goes back to sleep a second later. I would like to turn this off and it drains battery.
Click to expand...
Click to collapse
I remember asking about this in a thread a long time. Ago. Good news, (if the other suggested fixes aren't working), I know how to fix this. First, you have to be rooted (naturally). 2nd, install another text app, I just use google's Messenger text app, nice and basic and I like it. Open that app and let it set itself as default or do it manually in settings. That step might not be necessary, but should do it just in case or possibly be left with no text app by accident. Finally, go to system > priv-app > SecMms_Delight-Open > Copy the app which is our stock messaging app and it has the screen wake function built in and paste it somewhere else like a backup folder in the priv-app directory so you know where it goes back to. Delete the app inside the SecMms-Delight-Open directory and reboot. You'll notice the yellow stock messaging app is gone from desktop and app drawer and now when you get a text, no screen wake! :good:
This annoyed me quite a bit because for a living I deliver catering orders and each time I get an order, it sends a text to let me know to check the browser for order info. So I was getting like 12 to 20 texts a day in addition to all the normal texts from friends and family. It was waking a lot!
I wish the build my edge came on was rootable. Sad face for sure. No root, no downgrade, no happy.
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.
I just added videos of the issue to the OP.
That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.
I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.