The latest release of GrapheneOS is significant because it now has official support for using RCS in Google Messages. This is to try and address the ongoing RCS disconnect users on both stock and non-stock Android have been experiencing worldwide.
Some technical analysis of the disconnect can be found in later messages in this long-term RCS thread:
I don't think this is newsworthy at this point. My Pixel 6 and Pixel 7 both are unreliable when trying to call 911, calling with an over the top app or dialing the PSAP's number directly are the only workarounds.
Google doesn't give a fuck about this issue. I have filed repeated support cases over the past year with Google about this when using T-Mobile or Verizon.
That makes little sense. "It's the users who are wrong" ideology applies when you tell the customers they are holding the iPhone 4 wrong. Or when you ask them whether they don't have phones when you reveal the next Diablo as mobile-only.
No company would argue that users are wrong and that they are not supposed to dial emergency services.
Club of Rome often lamented human overpopulation, so the user you’ve been replying to will undoubtedly share some far-fetched conspiracy theory that won’t make a lick of sense.
Most interesting is a user story[1] shared giving an idea of how often this happens: 3 times over 8 months, with ~5 calls a week. We could round it at around 1% error rate. It's both relatively low (as a chance it happens to you), and extremely high (I can't imagine how many people might have the issue and not be aware of it!).
I'm sure there are other conditions that aren't identified here, but this definitely warrants more regulatory scrutiny.
Looking through my spam box for the ones I had to manually report it looks like maybe close to one a week, and they tend to be very similar, usually wrapped around a popular pharmacy store chain (no attachments). I also have noticed they tend to be sent from gmail.com addresses, which may suggest why they're not getting trapped by the spam filter.
I can't answer for iOS devices, but I do know that on Android, the Google Messages app[1] comes with the ability to filter SMS messages that are spam. I am constantly surprised both with how many spam messages my number receives as well as how I never see them because the filter catches them almost perfectly. My carrier, Verizon, also has a spam reporting service that works in tandem with the filter, so occasionally I go through and report all the ones the filter catches. I also believe, as a side note, that a possible upcoming feature will be categorization of text messages [2] which I certainly look forward to being on my phone as the number of SMS messages I receive daily increases.
As for email, in my personal experience Gmail's spam filter is slipping more (as in allowing spam into my inbox) than in previous year, but I think it remains as good as it's going to get for the average user. I also use Yahoo Mail and its spam filter is a tad over-aggressive, I have to manually check spam once in a while and fish out the emails that are in the clear.
I'm curious if this may apply to other sms apps, I have my default set to Signal, and haven't received any spam messages yet - I never noticed much on my previous iPhone. Currently using a Pixel 6, so I'll have to look more into this. Thank you.
I submitted this article because I find it interesting how quickly Asus is launching new product lines while, in my personal experience and in the reviews of others [1], these flagship models are quite buggy. In late 2019 I purchased their high-end GT-AX11000 router having done research and anticipating the support for mesh networks was optimal for my large house. In early 2021 I again purchased their brand new high-end GT-AXE11000 router thinking it would resolve the bugginess I had long experienced with the first router. I was sadly mistaken, and less than a year after its purchase, fighting with crashing and disconnects on wifi and LAN, I sent the AXE for repair (under warranty but I'm paying for shipping), swapping back in the AX during its absence, and already I'm back to experiencing disconnects (I plan to send that one in for repair once the AXE is sent back to me).
I look at this submitted article announcing the new current flagship and I am completely put off. I have trawled the relevant Asus forums [2] for months and seen report after report of people experiencing the same issues I have with their last two flagships, and there is no reason to suspect any difference with this upcoming one.
Some technical analysis of the disconnect can be found in later messages in this long-term RCS thread:
https://discuss.grapheneos.org/d/1353-using-rcs-with-google-...