Hi,
Google Messages (both the beta and the standard version) keeps crashing. On my Fold 1st gen, I never had any issue...
For now I reverted back to Samsung messages but the RCS doesn't work (even though the setting is there) so I'd rather go back to Google Messages...
Anyone else having the same issue?
I tried clearing both the Google Play Services and Google Messages storage, doesn't make a difference as after a few seconds I get the Android message that Messages keeps crashing.
For what it's worth, I was able to fix my issue by installing the Google app "Carrier Services" which was missing from my Fold2 and is apparently used by the RCS protocol of Google Messages...
Now it's all good
Related
I've found a few threads to this problem but since they're a little older and no solution was found yet I thought I'd give it another shot.
My phone is a XT1032, retail bought in Germany. Kitkat 4.4.4, no root and just a few apps from the Playstore, nothing special at all.
It seems that ever since I switched from the built-in Motorola (?) Messaging app to Google Hangouts my texts get sent twice, meaning a few people complain about getting them twice even though Hangouts shows just a single message. My settings are changed to use Hangouts as my default messaging app, and I'm using Hangouts (as Messaging before) with read receipts turned on.
To get on to this weird behaviour I changed my default app back to Messaging plus uninstalled all Hangouts updates. And now it works fine.
I'd rather use Hangouts, though. Any suggestions?
I hope this'll be fixed in Lollipop...
Nope it's a long problem... try deleting Google framework cache
Thanks for your response. I tried it out, but it didn't work. I keep using Messaging for now and set my hopes in Lollipop.
Phone Services has a notification of a single new voice message constantly running in my notification tray.
I tapped it to enter into my voice messages when I initially listened to the message and deleted it. The notification still stayed up.
I force stopped Phone Services. It still comes back up even though my voice messages are emptied.
I double checked to ensure Play Services is up to date.
I downloaded an updated version of phone services from the Play Services apk mirror. When I opted to install it, the install was unsuccessful, responding with a message of "App not installed. The package conflicts with an existing package by the same name."
Then I downloaded a more recent update of Phone Services but the same result occured.
I cleared the cache and data from Phone Services; no improvement.
I can't even swipe the notification away.
I'm running Android 7.1.1
on a Motorola Moto Z Force Droid.
Play Services is up to date.
My device system is up to date.
Who else has experienced this?
What's the solution?
Call yourself and leave a new voice mail. Then go in and listen and delete. It.
This has been known to happen from time to time.
My watch suddenly stopped being able to send an SMS using 'ok google', 'send a text to <contact name>' . it now tells me "Something went wrong. That's not available on this device". I have un-installed 'google' and reinstalled it on my watch. I have factory reset the watch, and installed a new messenger app on my phone/watch (google message) etc. Nothing is working unfortunately. Unsure what else to do.
Any ideas?
I have the same problem! Happened since friday, before it always worked fine. Also other messages like whatsapp same problem...i guess it has something to do with an update of play services or google assistant....
Replying fortunately still works. But initiating new messages not...
glenner05 said:
I have the same problem! Happened since friday, before it always worked fine. Also other messages like whatsapp same problem...i guess it has something to do with an update of play services or google assistant....
Replying fortunately still works. But initiating new messages not...
Click to expand...
Click to collapse
Exactly same. I also went over all of the security settings etc for each app on wear and phone. I use my watch a lot to initiate sms conversations so hopefully this will be fixed soon.
I have an older model of the Huawei Smartwatch and just recently I'm experiencing the same thing-- however my husband's newer version (but not Smartwatch 2) can still send text messages and make voice calls. I'm hoping this Google update has not my Smartwatch obsolete.
Same issue, but with phone not watch (SOLUTION)
I had this same exact problem... started about a week ago. I finally sat down the other morning and spent a few hours trying ever solution I could find until BOOM... I found the issue, the "Google Web and App Activity" was turned off!! I hadn't been in my Google Account setting for years, so my guess is that this was a recent Privacy Policy update rolled out by Google recently. Anyway, here are my notes on how to turn it back on for yourself (provided you have permissions to manage your own Google account):
Go into Google Home App
Hamburger Menu
Settings
Google Assistant Settings
Prompted about "Web and App Activity" settings that needed to be turned on, I had never turned them off, but they were off, I had previously logged into Google Admin for the account and turned it "on for everyone" earlier, so maybe do this first.
Then was prompted with a "I'm In" pop-up. I clicked on that button I was taken to the standard Google Account Setting Page.
I exited and tried "ok google" again, it worked
the google app updated on my watch today and now the issue seems to have been resolved.
curious to see if any one else has this issue.
when I say (or even type) something to the affect of, "Read my text messages", Google app just force quits. When I try immediately again, I get the "Google keeps stopping" with choices of App Info, Close App, or Send Feedback. I have all permissions enabled, only Android Messages installed (thus being my one and only choice as the default messaging app). I have tried to disable the dns.adguard and disabling advance chat features. I have also tried other apps, but to no avail.
If I say, "read me my email", it properly lists and reads my latest e-mail messages.
so why is this not working for the messaging app?
I have the Pixel 3 on VZW with the latest 9.0 installed. I have using both the beta google/messaging apps and without.
this happens on both WiFi and mobile data. I do have a Huawei Watch 2 (Wear OS) running - and trying the same command through the watch yields similar undesirable results.
any help would be greatly appreciated.
thanks!
I have a 256Gb S22 Ultra Exynos running Android 13, S908BXXU2BVJA - latest October 2022 update.
I recently tried my sons iphone and he had sms autofill working nicely so I thought lets have a go on my phone.
I cannot remember the last time that SMS Autofill was working on my phone.
I will go through the settings I have:
Settings/General management
/Passwords and autofill
Autofill service - Dashlane
/Dashlane
Autofill - ON
Keyboard Autofill - ON
Settings/Google/Auto-fill
/Auto-Fill with Google
Use Auto-Fill with Google ON
/SMS Verification Codes
Autofill Service ON
Default Browser ON
Every time I install a system update, I always clear cache in recovery mode
I have uninstalled and reinstalled Google Play Services
I have cleared data for Google Play Services
I have disabled and then re-enabled 'SMS' permissions in Google Play services, with a restart to see if that would help.
All to no avail.
I hate having to reset Google Play Services because it means that my Galaxy Watch 4 needs to be reset for it to be resynced back to the phone.
I have tried using Samsung Messages, Samsung Keyboard and Samsung Internet as a combination just in case it only works on Samsung apps, but the SMS autofill doesn't work.
I prefer using Google Messages, Gboard and Google Chrome because I like the way it's all set up also to see if the google sms autofill services only work on their apps, but the SMS autofill doesn't work.
I have uninstalled Dashlane (it's a password manager) to see if that was interfering, but uninstalling it, and restarting it (just in case) still the SMS autofill doesn't work.
Is anyone able to shed some light on this? What am I doing wrong?
Is it something I have to live with?
I have not seen any threads on here that have a fix that I have not tried, yes I have searched, but I wonder if there is someone on here who may have had this issue and fixed it.