search

GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
339 stars 18 forks source link

GrapheneOS SUPL/PSDS proxies location is off versus Google servers #3691

Closed neelchauhan closed 2 weeks ago

neelchauhan commented 3 weeks ago

In NYC and Stamford, CT on a Pixel 8, the GrapheneOS SUPL/PSDS proxies give an inaccurate location and the dot keeps moving in Google Maps. This happens on both T-Mobile and Verizon (US Mobile MVNO) SIMs.

When I switch to the Google default servers, the location is very accurate even when indoors. I know GrapheneOS won't serve every user's demand, but inaccurate SUPL/PSDS servers made it hard to traverse NYC public transit.

I won't do screenshots unless absolutely needed as I won't leak my location.

thestinger commented 3 weeks ago

SUPL and PSDS are only A-GNSS. They don't determine location themselves but rather accelerate GNSS. Both are exactly the same data with the GrapheneOS services. SUPL is simply a passthrough proxy to supl.grapheneos.org. PSDS is a cache of exactly the same data, which can be verified. There's short server side caching too so sometimes one or the other has a file that's slightly older but they're valid for much longer than the possible difference. Ours tend to update faster than their comparable mirror. It sounds like you're talking about sandboxed Google Play network location which wouldn't work better when using the Google SUPL/PSDS servers.

This is the script output:

Broadcom

gllto.glpals.com
/7day/v5/latest/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus4.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto/v1/latest/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/rto/v2/latest/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

agnss.goog
/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/pad/xto/prod/rto/2/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

broadcom.psds.grapheneos.org via 0.grapheneos.network
/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/pad/xto/prod/rto/2/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

broadcom.psds.grapheneos.org via 1.grapheneos.network
/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/pad/xto/prod/rto/2/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

broadcom.psds.grapheneos.org via 2.grapheneos.network
/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/pad/xto/prod/rto/2/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

broadcom.psds.grapheneos.org via 3.grapheneos.network
/lto2.dat
0d3fbd5afed15e11b480142e6edb02f65decb86ae9568e5847f66a265b773b22
/rtistatus.dat
ce8790a44bf36aee9f383c8021c55e1d5bd1f9a86536d1c7445b7178f2f6432d
/rto.dat
a1385b66fe5d2ec45fa42b446d7eb2a660da16e61422f90268313ba57a94abff
/pad/xto/prod/rto/2/rto.dat
5d444725bbc512c0e18516f330a14168966cde6931acd3a1f515330803c3622e

Samsung

1.ssiloc.com
/p4/42F3
0cc80577ae9f0b9cd5e23e6049a77749d24a38955ea28692dfabb6d9494e06b7

1.ssiloc.com via 0.grapheneos.network
/p4/42F3
0cc80577ae9f0b9cd5e23e6049a77749d24a38955ea28692dfabb6d9494e06b7

1.ssiloc.com via 1.grapheneos.network
/p4/42F3
0cc80577ae9f0b9cd5e23e6049a77749d24a38955ea28692dfabb6d9494e06b7

1.ssiloc.com via 2.grapheneos.network
/p4/42F3
0cc80577ae9f0b9cd5e23e6049a77749d24a38955ea28692dfabb6d9494e06b7

1.ssiloc.com via 3.grapheneos.network
/p4/42F3
0cc80577ae9f0b9cd5e23e6049a77749d24a38955ea28692dfabb6d9494e06b7

Qualcomm

path1.xtracloud.net
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

path2.xtracloud.net
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

path3.xtracloud.net
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

qualcomm.psds.grapheneos.org via 0.grapheneos.network
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

qualcomm.psds.grapheneos.org via 1.grapheneos.network
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

qualcomm.psds.grapheneos.org via 2.grapheneos.network
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78

qualcomm.psds.grapheneos.org via 3.grapheneos.network
/xtra3Mgrbeji.bin
218e176553c8ad616021645cb3a7b9b0e2bc0e846f622eeb4b2dce1406329f78
thestinger commented 3 weeks ago

Going to have to close this because it doesn't make sense that it would behave differently. We do know that GrapheneOS SUPL isn't working yet on the Pixel 8a and that's resolved for the next release of GrapheneOS by including the Let's Encrypt roots for the Samsung gnssd configuration. Only the Pixel 8a has Samsung GNSS and this isn't relevant to the other devices where it works fine.

thestinger commented 2 weeks ago

Pixel 8a issue was fixed and there should be no other differences.