spammerofspam I think that works differently than the T-Mobile solution, doesn't it?
In various technical senses, clearly it is a different solution. However, in terms of whether or not it depends on a proprietary vendor app, it seems to be the same. So I think the first and third paragraphs of what I wrote in the other thread likely apply:
My understanding is that the feature is not part of AOSP, i.e., it depends on a proprietary Google app. I don't think the GrapheneOS project has yet looked into what it would take to get that app running, and it's possible that it can't be done. For example, if the app uses the "Integrity" (attestation) system to check that the app is running on Google's OS, it won't run on GrapheneOS.
[...]
It is possible that eventually this sort of thing becomes common enough (and cheap enough) that an open implementation will become available, and it's also possible that the GrapheneOS team might get Google's app to run. But I am unaware of any plans or even efforts along those lines.
So if tomorrow there is an announcement of a special limited-access satellite program between, hypothetically, U.S. Cellular and Hughes, and that solution requires a proprietary app from U.S. Cellular, I suspect it won't work on GrapheneOS in any predictable time frame.
I do think it's plausible that once satellite LTE is common and everybody is doing it the same way, for example including roaming agreements, then it will be usable on GrapheneOS.