Avatar
GrapheneOS (RSS Feed)
2306b336f168f4add8da924dae907d2a6b9c13fb0a06672bd7708295dec75da7
Public posts from @GrapheneOS@grapheneos.social https://grapheneos.social/@GrapheneOS

@gvs (https://rebelbase.site/users/gvs)@cliffwade (https://allthingstech.social/@cliffwade) Their response to corrections to inaccurate claims they made about the sandboxed Google Play compatibility layer and microG is to claim that accurate information is propaganda with no basis since it doesn't align with their views. Simply read the available documentation for the projects involved about how Google Play works and how microG works. Can see that Google Play is still running in each app using it, and that is within the same app sandbox used for sandboxed Google Play.

https://grapheneos.social/@GrapheneOS/110392637179138243

There's already a standard Mock Location feature and we'll be providing a non-developer interface for using it along with providing similar built-in functionality for Camera and Microphone. We'd also like to split the Camera permission for front and rear cameras. Steady progress.

https://grapheneos.social/@GrapheneOS/110382193158208508

We also plan to replace the need to grant the Camera and Microphone permissions. Our Sensors permission already largely avoids compatibility issues to the extent possible since zeroed data is returned. Network permission similarly pretends that the network is down when revoked.

https://grapheneos.social/@GrapheneOS/110382190391651337

We published experimental support for the Pixel 7a within 2 days of it launching. Experimental tag was dropped shortly after on May 14th. This is the first production release supporting and will hopefully make it to stable channel, as long as nothing is wrong with Contact Scopes.

https://grapheneos.social/@GrapheneOS/110382189501028453

This was already the case on all the recommended devices (6th and 7th generation Pixels) since they use the Tensor SoC and a separate Broadcom GNSS chip rather than a Qualcomm SoC. However, it's now also the case for 4th and 5th generation Pixels and future Qualcomm SoC devices.

https://grapheneos.social/@GrapheneOS/110319929962498708

There are no longer any default connections to non-GrapheneOS servers other than the network-provided DNS resolvers. We document default connections at https://grapheneos.org/faq#default-connections (https://grapheneos.org/faq#default-connections) along with a section below covering connections triggered by using a carrier or installing apps, etc.

https://grapheneos.social/@GrapheneOS/110319926323827467

We've already been hosting a Qualcomm PSDS cache since March which we're in the process of integrating:

https://github.com/GrapheneOS/grapheneos.network/commit/6e213e84c881d6afc64c3c54a8ea8aeab03dcb9a (https://github.com/GrapheneOS/grapheneos.network/commit/6e213e84c881d6afc64c3c54a8ea8aeab03dcb9a)

xtra-daemon setting User-Agent is entirely unnecessary so we'll stop it from doing that instead of only preventing it from including any hardware IDs.

https://grapheneos.social/@GrapheneOS/110284476618921673

Default connections made by GrapheneOS are documented at https://grapheneos.org/faq#default-connections (https://grapheneos.org/faq#default-connections) including Qualcomm PSDS (XTRA) for 4th/5th gen Pixels.

On 6th/7th gen Pixels, GrapheneOS only uses GrapheneOS services by default since we use our own PSDS cache for Broadcom GNSS (GPS, etc.).

https://grapheneos.social/@GrapheneOS/110284470841828658