I got the Pixel 10 Pro, installed GrapheneOS, and also have T-Satellite enabled. Hoping to test it out this coming weekend. Any tips on any diagnostics data I should gather if it doesn't work?
Technically, I think it should work. None of the ways the satellite "stack" is different appear to be missing in GOS, but I could be wrong.
- (starting for the network level) They do QOS at the Starlink network level - transparent.
- The satellite "base stations" broadcast a different network, but this is effectively a roaming partner for T-Mobile - nothing not already supported in AOSP.
- The phone's modem supports 3GPP Release 17 (or even later versions) to do a clever handshake with the satellite and determine the best frequency compensation for the Doppler shift. And also other cool stuff, but all of this is in the modem firmware which is unmodified by GOS. No reason this should not just work out of the box.
- On the Android OS level, there are satellite APIs which tell apps they are on a satellite connection so they can adjust their behavior (enter low-bandwidth mode). These APIs are apparently part of AOSP, so again, they should exist in GOS as well.
So all of this should just work. But again, happy to gather any data on what could be failing if it doesn't.
Also addressing some other comments - there is data through T-Satellite too, and there is a limited, but not short list of apps supported - WhatsApp, AllTrails, Google Maps, AccuWeather, CalTopo, onX, X and more coming too (I hear Signal too).
In fact WhatsApp is advertised as supporting voice and video calls over satellite too! To be clear, the Starlink direct to cell beam has a total bandwidth of 10 Mbps for a circle with a diameter of up to 20 miles. So it depends on how busy this area gets, but this is only for the remotest parts of the US with no cell service, so by definition they are the opposite of busy. Also this being LEO satellites, latency should actually be pretty good, 20-60 ms, which is a lot better than a 56k dial up connection with expected latency of 100-300 ms so very much contrary to a prior comment by @23Sha-ger.