I’ve tried Google’s Messages for Web, Microsoft’s Phone Link, and KDE’s Connect. They all seem to have the same problem: they lose connection constantly and have to be unpaired and re-paired. Is this a problem inherent to the way that Android works? Has anyone managed to solve it, or is there a setting to fix it?
Thanks!
One other thought is to use Google Voice.
At least in that case, everything runs through a Google server, rather than through some possibly janky connection between your desktop and phone.
The drawback is that, if you have an existing phone number, you’d have to port it over to Google Voice (or maybe Google Fi can port that number to an actual cell phone; not sure if it can).
You can forward your Google voice number to your cell number, but I’m not sure how that applies for texts. I haven’t used Google voice in a long time. In fact, they reclaimed the number recently lol
It doesn’t apply to texts. That’s fine with me though, I’ve only sent like 3 actual texts from a smartphone. I started using GrandCentral before it became Google Voice, and at that time I still had a dumbphone.
The only complaints I have are that for one, since it did register as a voip, for some arcane reason that I don’t understand, done systems don’t like that and will force you to enter a number with a traditional service. No idea why it matters to them at all.
The other complaint is that for another reason that is literally unexplainable, they never implemented RCS with it, so it feels like texting back in the 00s.
Google made the RCS standard, yet in the app they designed from the ground up they didn’t implement it. That’s a wtf for me. Maybe because it’s still usable by dumbphones? If be more than ok with dropping support for those if it means the majority of the world gets a better experience.