Related
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
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.
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
I'm getting this weird issue where when I dismiss notifications from gmail, they will immediately come back and then dismiss themselves again one by one.
Easier to show than to explain, so here's a video: https://photos.app.goo.gl/PnGCYlIdcX5ua4Ji2
It's really annoying, especially since the notifications are also sent to my gear S2 watch which then just buzzes like crazy as my phone is cycling through all the notifications.
I've used all the google-fu I know and came up with pretty much nothing, so I'm hoping someone here can help me figure this out.
Potentially related: I get notifications for new e-mails pretty much as soon as they come in, but if I go to gmail on my computer and read or delete that e-mail, the notification won't update. It definitely used to, and I'm not really sure when that changed.
Any help would be really appreciated. Thanks!
I'm unable to play the video to see the notification . . . my internet is terrible right now. Perhaps you could just put up a single photo of the notification, or enter the text into your original post?
Check your setting for "Notification Reminders" under the Accessibility tab & find what you may have unknowingly switched on.
Happened to me once, I know how annoying it can be lol.
Hope this helps!
I get the same thing. Seems to be nothing to do to stop it however you may be able to reduce it to one notification in the gmail app settings just go to the app settings tap your email then about halfway down tap inbox, sound and vibrate and make sure notify for every msg is unchecked. Hope this helps.
I appreciate all the suggestions, unfortunately none of them seem to be the solution for me ...
JeffDC - A photo won't show anything, it will either show notifications there, or not, while the issue is when I dismiss a notification, it then comes back again after ~1 sec as another notification, then dismisses again after another couple of seconds, instead of properly dismissing the first time around.
og21 - Notification reminders were already off in accessibility settings.
wombat_combat - Notify for every message is already unchecked.
I get the same, haven't found a fix, but haven't looked hard either.
I suppose theirs still no solution? Been happening to me for months.
Same thing here. Haven't been able to find a solution. Galaxy S10 and only happens for my work email inside the secure folder.
Tagging this one again since it appeared on my google search.
On my previous Galaxy S8+ when I dismissed the notifications (notification shade) occasional a gmail notification (one just dismissed) would pop back up then immediately dismiss itself.
On my new S20 FE when I dismiss the notifications occasionally a gmail notification (one just dismissed) pops back up as if it was a new notification and stays there until dismissed again.
This happens when I clear it from the notifications and as soon as I swipe up the Gmail notification shows again. It's been happening for a while and I don't know how to tell them to fix it.
2021, this is still happening to me all the time. Gmail notifications come back to haunt me after clearing them. Sometimes they disappear after a few seconds, sometimes I have to dismiss them again.
Pixel 5.
I do have a suspicion it might be caused by Samsung Wear, maybe I'll remove notification access from it to see...
Update: ^ didn't work -.-
Same here. Stock Pixel 4a. Only one Google Account set up (which is a quite old Google Apps account).
Edit: The issue was also present on my former mobile, a Nokia 6.1, also running Stock firmware.
I'll bump this, too - same issue for months, Gmail notification pops (w/audio) immediately after I dismiss it. Have also tried all the "Google-fu" I know.
Pixel 4 XL - A11, stock and updated.
November 2021.
Still the same..
This is getting annoying AF.
Android should be better than IOS because it let the users control everything.
But what is with this crap.
I could not find any solution to let the notification notify ONLY when something new comes....
But I haven't tried hard either...
Anyone got any solution on this?
Go to your Gmail settings. General settings. Click on account. Scroll down to "nudges". Turn off. Repeat for each account.
armedzerox said:
November 2021.
Still the same..
This is getting annoying AF.
Android should be better than IOS because it let the users control everything.
But what is with this crap.
I could not find any solution to let the notification notify ONLY when something new comes....
But I haven't tried hard either...
Anyone got any solution on this?
Click to expand...
Click to collapse
Go to your Gmail settings. General settings. Click on account. Scroll down to "nudges". Turn off. Repeat for each account.
Shart-Pooter said:
Go to your Gmail settings. General settings. Click on account. Scroll down to "nudges". Turn off. Repeat for each account.
Click to expand...
Click to collapse
Go to your Gmail settings. General settings. Click on account. Scroll down to "nudges". Turn off. Repeat for each account
SinéadO said:
I'll bump this, too - same issue for months, Gmail notification pops (w/audio) immediately after I dismiss it. Have also tried all the "Google-fu" I know.
Pixel 4 XL - A11, stock and updated.
Click to expand...
Click to collapse
Go to your Gmail settings. General settings. Click on account. Scroll down to "nudges". Turn off. Repeat for each account
Hello, on my new zfold2 the incoming call screen does not show when calls arrive. The phone rings, but the lock screen remains, basically i cannot answer the call until I unlike the device, go to the pull down menu and then see the incoming call to be able to answer it. I've searched whether there is a setting for this, but nothing...anyone can help me? thanks.
Same here. Fix?
dgardel said:
Same here. Fix?
Click to expand...
Click to collapse
I have not found anything yet. Must be a setting issue, i Hope!
Same here.
I've been using the Google dialer since using this phone and have had no issues. Not sure if this is really the answer that you're all looking for, but it may be a workaround for you until the stock phone app is updated.
https://play.google.com/store/apps/details?id=com.google.android.dialer
I too was facing issues with the stock phone dialer, though the issue was different. It was not registering my touch or registering it after repeated attempts while wanting to make calls. Touch screen otherwise works fine.
Using a different Dialer now - True Phone app. and all issues of touch have been sorted out.
I had that problem, turns out for my problem was that I had do not disturb turned on. Doubt that's the same for you guys but just thought id share. Thanks.
Have you found any solution?