Google messages icon changed.

[alarsen77]

I am on Android 11 and I am on the beta version of google messages and today the icon changed to a blue plus with white corners. Screenshot attached it is the middle icon on my dock. Anyone else notice this icon change?

 

[ironass]

I am on stable Android 11 and using Google Messages Beta, v7.1.080 (Hickory_RC06.phone.openbeta_dynamic), and my icon is the usual white speech bubble on a blue background.

 

[alarsen77]

Hmm weird I wonder why mine is different.

 

[mustang7757]

Do you use a icon pack ?

 

[alarsen77]

No icon pack either. I just uninstalled and reinstalled the app and it's back to normal.

 

[mustang7757]

Ok good

 

[B. Diddy]

That kind of looks like the Samsung Accessibility Menu icon. Hopefully that glitch doesn't come back.

 

[mlblack16]

I am on Android 11 and I am on the beta version of google messages and today the icon changed to a blue plus with white corners. Screenshot attached it is the middle icon on my dock. Anyone else notice this icon change?//uploads.tapatalk-cdn.com/20201211/12cbebc03ea47b0d53ffcf0d647b5918.jpg

Yes! It does that and I forget what triggers it to happen.

Watch something on youtube at 1080 and see if it goes back to normal.

My question for you is...are you still able to get chat services? After the upgrade, I had the bright idea to change my Google Messages to regular (instead of beta) because of this funky image occurring. Well, in doing so, I have lost chat. I even went back to beta and still cannot get it to connect. It just hangs at "trying to verify your number."

I have done all the things recommended online, including using the Google dialer to get into the settings and turn all RCS switches on, and using an activity launcher, but it's literally missing the RCS flags in the app.

 

[Libra420]

delete data and cache from carrier services and uninstall. delete data and cache from messages and uninstall(if possible). reinstall carrier services, then messages(beta) and check..

 

[mlblack16]

delete data and cache from carrier services and uninstall. delete data and cache from messages and uninstall(if possible). reinstall carrier services, then messages(beta) and check..

Done all that, and far, far more. I've gone into app settings using an activity launcher, and using the Google dialer to access hidden menus and it still won't connect to chat.

 

[mustang7757]

I think gotta be something with beta version acting up , you try uninstalling the update?

 

[tube517]

What version is your carrier services?

 

[mlblack16]

What version is your carrier services?

Not sure if you guys are asking me or the OP (haha) but here's my version. It's just dead and not doing anything. I can't clear cache or force stop, because the beta Messages isn't trying to use it. When I went into the settings using activity launcher, there's no RCS flags to turn on. Also, when I went into settings using the Google dialer and code, there was the LTE profile and emergency services but no RCS.

I don't know what's going on, unless Verizon removed that part from the update or it somehow was left out. I wouldn't put it past Verizon to do something slimy like that, freaking douchebags.

 

[tube517]

Not sure if you guys are asking me or the OP (haha) but here's my version. It's just dead and not doing anything. I can't clear cache or force stop, because the beta Messages isn't trying to use it. When I went into the settings using activity launcher, there's no RCS flags to turn on. Also, when I went into settings using the Google dialer and code, there was the LTE profile and emergency services but no RCS.

I don't know what's going on, unless Verizon removed that part from the update or it somehow was left out. I wouldn't put it past Verizon to do something slimy like that, freaking douchebags.

I was asking you since you were having RCS/Chat issues. I had issues last week and it was because the carrier services was on version 50 and it was a flawed version and broke android messages app and chat. I couldn't get chat to activate for a couple of days. It's fixed now.