diff options
| author | r3g_5z <june@girlboss.ceo> | 2023-03-29 21:29:52 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2023-04-03 07:28:50 -0400 |
| commit | 0c17a7d60b35506c1f0652fa8126f2745f04b27a (patch) | |
| tree | ec8b5d512acd876959349617e636f73453d062a1 | |
| parent | 195cd8772f187ff323bd8752e4faf914d6120c73 (diff) | |
update GSMA TS.43 spec link
Android docs now also reference v9.0 at https://source.android.com/docs/core/connect/ims-service-entitlement
Signed-off-by: r3g_5z <june@girlboss.ceo>
| -rw-r--r-- | static/usage.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/static/usage.html b/static/usage.html index fa052cc9..a9c3b315 100644 --- a/static/usage.html +++ b/static/usage.html @@ -1286,7 +1286,7 @@ GrapheneOS will never add support for this.</p> <p>Android 12 introduced support for the - <a href="https://www.gsma.com/newsroom/wp-content/uploads//TS.43-v8.0-3.pdf">GSMA + <a href="https://www.gsma.com/newsroom/wp-content/uploads//TS.43-v9.0.pdf">GSMA TS.43</a> standard, where provisioning for VoLTE, VoNR, Wi-Fi calling may be handled by Google Firebase. Currently it is very rare for carriers to be using Firebase to handle this. It is unlikely, but technically possible, that with such |