I have an S20 US Unlocked and after updating to OneUI 3, the google dialer beta app stops allowing me to mark calls as spam or to block. It just boots me out and crashes the app.
Has anyone had similar issues? Any fixes?
mstras said:
I have an S20 US Unlocked and after updating to OneUI 3, the google dialer beta app stops allowing me to mark calls as spam or to block. It just boots me out and crashes the app.
Has anyone had similar issues? Any fixes?
Click to expand...
Click to collapse
Yes, same. Not sure how to fix. Everything else within the app works perfectly fine.
Me too, tried it and it was buggy.
Though I am curious, the app is available in the Google Play Store but there's the Magisk module for dialer framework. Maybe if you get both it works.
Bumping to see if anyone has found a fix.
Related
I just got the 1/5/17 beta version of the Google app today (via the play store beta channel). Will work one time for a voice command, then a second voice command will be heard by the app, immediately followed by a hang, then short delay, then force close message. Clearing app data will allow another single successful voice command, followed by the and hear then hang behavior.
Anyone else seeing this behavior?
I have uninstalled updates to run the stock included version (which is behaving fine) to work around the problem for now.
Here's the offending build:
My Google app did similar when I had the recent security update. Try clearing the cache from the app and see if it helps after a reboot. Mine only fixed itself when the app update to a regular (non-beta version).
Someone else said to remove and re-add your google account, although I didn't end up needing to do that.
emailrob said:
My Google app did similar when I had the recent security update. Try clearing the cache from the app and see if it helps after a reboot. Mine only fixed itself when the app update to a regular (non-beta version).
Someone else said to remove and re-add your google account, although I didn't end up needing to do that.
Click to expand...
Click to collapse
Clearing cache didn't help me. Clearing all app data (including cache) reset it so it worked once.
I have a fully functional solution just uninstalling app updates - was just curious if I was the only one having the issue (would point to something in my configuration causing the issue) or if everyone was (indicating a problem with the app)
dandrumheller said:
Clearing cache didn't help me. Clearing all app data (including cache) reset it so it worked once.
I have a fully functional solution just uninstalling app updates - was just curious if I was the only one having the issue (would point to something in my configuration causing the issue) or if everyone was (indicating a problem with the app)
Click to expand...
Click to collapse
Hard to tell. Mine was definitely related to the recent security update - it stopped working right after that.
emailrob said:
Hard to tell. Mine was definitely related to the recent security update - it stopped working right after that.
Click to expand...
Click to collapse
Gotcha. Google beta app updated to 1/9 version yesterday, haven't had a chance to test it yet.
Edit: newest beta (1/9) appears to have resolved the crash issue I was having, and it can also now speak inbound text content in hangouts (that hadn't worked for me for a while).
Anyone else having issue with Facebook notifications?
Every other app works fine - Google+, Twitter, LinkedIn..etc.
I checked my app settings and notification settings within Android and everything seems to be in order. Even re-installed the Facebook app and still no dice.
When I open the app I see I have notifications, however my phone isn't notifying me of anything related to Facebook. I have open the app to see the notifications within the app.
Anyone else having the same problem?
I am on Pixel 2 XL 8.1 stock.
Did you disable background activity for the app?
laureanop said:
Did you disable background activity for the app?
Click to expand...
Click to collapse
No, it is active.
Having the same issue. Also there are times the app doesn't recognize that the phone is connected to WiFi. The app continues to update the feed, but the videos won't auto play until I turn off WiFi then back on.
Have you ever cleared the cache and data under the Google Framework Services trying to push the OTA update? It is said that would break GCM things.
solohsu said:
Have you ever cleared the cache and data under the Google Framework Services trying to push the OTA update? It is said that would break GCM things.
Click to expand...
Click to collapse
I have not, but the problems have been since day 1 of getting the phone. I'll give it a try and see if there is an improvement.
hey have you got a solution to the problem i am facing the same problem
Similar problem with bootleggers on my Redmi note 5 pro
I've searched the Google a few different times, but the wording leads to unrelated results.
I thought it was just a glitch / conflict with my rooted Z2 Play, not receiving notifications from Google Play, when app updates are available.
I have auto update turned off for two reasons. I absolutely hate the new cartoon version of Waze (v4+) and I like to know when apps update, in case I have issues, I can more easily identify suspects.
I fired up my backup phone, VZW Z2 Play and the same thing. No notification with plenty of app updates waiting.
Anyone else experience this?
pizza_pablo said:
I've searched the Google a few different times, but the wording leads to unrelated results.
I thought it was just a glitch / conflict with my rooted Z2 Play, not receiving notifications from Google Play, when app updates are available.
I have auto update turned off for two reasons. I absolutely hate the new cartoon version of Waze (v4+) and I like to know when apps update, in case I have issues, I can more easily identify suspects.
I fired up my backup phone, VZW Z2 Play and the same thing. No notification with plenty of app updates waiting.
Anyone else experience this?
Click to expand...
Click to collapse
Clean cache of Playstore maybe?
alienyd said:
Clean cache of Playstore maybe?
Click to expand...
Click to collapse
I'm thinking about clearing data.
I found that as a solution for other issues with Google Play, but thought I'd wait for responses here.
Thanks!
even better! if you are still receiving push notification, then Playstore app/service is malfunctioning. Cleaning it up should help.
So, I reset the watch, updated all apps, checked the phone etc, reinstalled Wear OS.
When I tell Assistant (After "Ok Google" or holding the button) "Call [name]", it says "Calling [Name] at work." And the call doesn't initiate, but a message pops up "something went wrong."
But if I try to make a phone call with the Phone or Contact apps, calling works just fine.
Any ideas?
My Huawei is also experiencing the same situation
chicko0l said:
My Huawei is also experiencing the same situation
Click to expand...
Click to collapse
I checked with another Huawei Watch owner - same problem. Did they update Google app on the watch with a new bug?
When will Google fix their....? GRRRR
Same here, it was working fine before..
So I guess it's a wide issue. Hopefully there's a fix soon because the watch is now useless. If there's a fix I hope someone posts soon.
After receiving an update on my watch
For both Google and wear os few minutes ago, looks like everything has been sorted out and the watch is working as it should.
I can confirm that the most recent Google app update on the watch fixed the issue.
What version Google app works fine???
My version is 8.4.8.25 and doesnt work
eilex17 said:
What version Google app works fine???
My version is 8.4.8.25 and doesnt work
Click to expand...
Click to collapse
My version is 8.3.15.25arm.
Which means they rolled it back.
No matter how many times i delete/retrain the voice model, diaable/renable/update the Google app, the Google app never actually activates the 'Access with Voice Match' option as seen in the picture. It's not 'greyed out' per se, but when i select it and click 'yes I'm in and 'finish', nothing actually happens and it just remains deactivated, as seen in the picture. Any advice would be welcome.
Uninstall google app updates from play store. Enable google voice. Update google app. All will be good.
Sent from my ONEPLUS A5010 using Tapatalk
1stHTCphone said:
Uninstall google app updates from play store. Enable google voice. Update google app. All will be good.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
When I remove update and go to the voice settings, the option is truly greyed out, see screenshot.
I had the exact same problem as you before. It allows me to enable it after I remove all google update. Try clear cache and reboot? Good luck.
Sent from my ONEPLUS A5010 using Tapatalk
marcsmv3 said:
When I remove update and go to the voice settings, the option is truly greyed out, see screenshot.
Click to expand...
Click to collapse
If you are rooted try this out
intoxicated.mad said:
If you are rooted try this out
Click to expand...
Click to collapse
I am. No luck, just tried.
I have the same issue! Removing the update fixes it, but once Google app updates itself it's turned off again. I submitted a bug report, you should do the same! Hopefully it gets fixed.
Same for me on ob31
What i did was to uninstall updates for google app and disable autoupdate from playstore
Also if you uninstall the update and retain voice settings, the voice commands will still work if you update again but you don't open google assistant settings
Makerrr said:
Same for me on ob31
What i did was to uninstall updates for google app and disable autoupdate from playstore
Also if you uninstall the update and retain voice settings, the voice commands will still work if you update again but you don't open google assistant settings
Click to expand...
Click to collapse
Would work if I could get the setting to activate in the first place at all, but like I said, whether I remove the update or not it's either greyed out or just plain doesn't activate.
freyrnygaard said:
I have the same issue! Removing the update fixes it, but once Google app updates itself it's turned off again. I submitted a bug report, you should do the same! Hopefully it gets fixed.
Click to expand...
Click to collapse
Do you remember when it last worked? I remember it working before OOS 9.0.5 I think...
marcsmv3 said:
Do you remember when it last worked? I remember it working before OOS 9.0.5 I think...
Click to expand...
Click to collapse
Well i am on ob31, and last worked on beta 29 i think
1stHTCphone said:
I had the exact same problem as you before. It allows me to enable it after I remove all google update. Try clear cache and reboot? Good luck.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Tried clearing cache/reboot after downgrading, option still greyed out.
Also having similar issue, I get voice recognition after initial reboot, but then does not recognize voice thereafter.
Great news! OOS 9.0.7 has fixed this issue for me completely. I am now changing channels on SiriusXM app via OK Google voice command while listening through my car stereo's Bluetooth and shifting gears at the same time. Brilliant.