"Messages for web" becoming less-reliable

[955450]

I like typing with ten fingers instead of a couple, and so love the "messages for web" feature with google phones.

Except the thing needs to be restarted and kicked more often than a circa 2004 computer trying to run Windows 10.

I can see if I've been off my phone for hours. But often, even if I've used the phone, or Messages for Web, just minutes before, I'll go to MFW and get the "spinning Windows wheel," and eventually a graphic on the web that says "Not connected to phone. Make sure your phone is on and connected to wifi or your mobile network."

My phone is ALWAYS on, and connected to wifi or mobile data.

This problem, by the way, seems to be more prevalent when the phone is on wifi, but of course if my wifi was goofed up, so would my computer internet connection.

Why can't google make messages for web work right all the time?

And, more realistically, what can I do - phone and/or web - to minimize this type of stuff happening?

 

[B. Diddy]

When this happens, have you tried closing the Messages for Web window and then opening it again?

 

[955450]

When this happens, have you tried closing the Messages for Web window and then opening it again?

I am sure I have. And sometimes it's worked sometimes not, eventually resolves itself - just like if I futz with my phone, eventually it works out.

But my goal is to just have MFW work, without jiggering the phone or the web window.

 

[B. Diddy]

I've experienced this issue as well, but have not yet figured out what might be associated with it. I do use the Messages for Web on multiple machines, so I wonder if that might be an issue. Are you using it on only one machine?

 

[955450]

I've experienced this issue as well, but have not yet figured out what might be associated with it. I do use the Messages for Web on multiple machines, so I wonder if that might be an issue. Are you using it on only one machine?

I do use it on two machines, sometimes concurrently (start the day at home, then go to work with home session still active).

But the problem occurs even on weekends, or days when I choose to work from home, and MFW is then only running at home (I close my browser, both at work and home, at end of day, and restart the computer).

 

[mayconvert]

switch to MacOS and iOS and it just works. all the time. without effort on the users part. android will never get messaging fixed.
it's been a train wreck for years and that continues into 2020. you can get an iPhone for same price as pixel 3a (iphone 8 or wait for new SE that will be out any minute)

 

[B. Diddy]

switch to MacOS and iOS and it just works. all the time. without effort on the users part. android will never get messaging fixed.
it's been a train wreck for years and that continues into 2020. you can get an iPhone for same price as pixel 3a (iphone 8 or wait for new SE that will be out any minute)

Nah, that's not a particularly useful comment in an Android forum. Many people here (including me) aren't interested in switching. Thanks anyway!

 

[Kizzy Catwoman]

switch to MacOS and iOS and it just works. all the time. without effort on the users part. android will never get messaging fixed.
it's been a train wreck for years and that continues into 2020. you can get an iPhone for same price as pixel 3a (iphone 8 or wait for new SE that will be out any minute)

OK. That's pretty harsh. Messages is a great app when you can get it to work. I wouldn't move to the Apple ecosystem just for a messaging app.