1
 
 

I use a pixel 8 pro with gos and whenever I try to mirror to a TV the device doesn't find anything to mirror to. I'm assuming that its a GOS issue …

2
3
 
 

cross-posted from: https://lemmy.world/post/54064630

Just Curious: How small are the chances of next year's Fairphone supporting GrapheneOS?

WARNING:

I have NOT done any research in any of the info provided ij this post, only info that I just so happened to sumble upon, so please take this post with a grain of salt

What happened?

With the Motorola Signiture 27, GrapheneOS finally broke free from being Pixel-exclusive. However, a good question meeds to be asked for me: How slim are the chances that next year's Fairphone could support GrapheneOS?

Why I even considered it as a possibility

I've seen some people saying Fairphone will support GrapheneOS, but there's lots of evidence against it, saying that the bare minimum requirements

Why I think it's unlikely:

Fairphone has historically lacked in terms of specs. While I don't have a shoot out of the camera or ANY specs like most people (my bare minimum res quality is 240p lol), as long as the technology used for the hardware stays modern, however I heard GrapheneOS had specific requirements in order to gain support for a device model. Idk what those are other than a relockable bootloader. While this year's hardware improvements have been much bettet than the past, I don't think it will be enough even if 5he pace is kept or even improved next year

Comment down what you found or correct what I've missed or done wrong in the comments

4
5
 
 

According to Grapheneos mod on Grapheneos discuss, the attack is unpreventable on vanadium (if I'm reading this right):

"Reducing the number of ads by blocking known patterns does not completely eliminate ads or especially overall third party content. Third party content can also be included server side.

Vanadium has default enabled ad blocking so adding DNS filtering won't generally improve much for the default browser. The in-browser filtering can block more than DNS filtering."

As I understand it, the whole supposed reasoning for Vanadium to not have a strict addblocker (like Mozilla) is so that it will be identified by internet systems to appear as chromium and move smoother. I find more sites work on vanadium (for me) than on ironfox.

But now it seems all JavaScript advertisemens are a liability.

Are we at the point where we need a set up where java should almost always be off?

https://discuss.grapheneos.org/d/42850-gosvanadium-vs-zero-click-malware-from-targeted-ads-via-javascript/10

6
7
8
 
 

cross-posted from: https://lemmy.world/post/52271584

Has anyone noticed the VPN disconnecting when charging the phone? Using IVPN, but I saw reports of Proton VPN too.

Happens every time. The VPN app has all permissions and unrestricted battery use.

I can't enable "Always On VPN" because Android Auto needs the split bypass, and breaks if that is enabled.

9
10
 
 

I'm not particularly technically knowledgeable so forgive me if this answer is obvious.

If I'm deleting my cookies/browser data, my OS Mac address is random when using vanadium, I'm using a vpn, and, it's not like I have a vanadium profile I'm logged into, how does the Lumo page "know" that I've maxed out the amount of times I've used it without having a Lumo profile? Shouldn't I be unrecognizable to the page?

11
12
 
 

The latest update, released to stable today, adds a long awaited feature to automatically start recording phone calls.

I saw the release notes a few days ago, but there were one or two versions pushed to alpha and beta before it was released to stable. I've been using various third party apps to do call recording, so it's nice that this feature is native in grapheneos.

To enable, open the Phone app and go to Settings -> Call Recording. You can enable automatic call recording for all non-contact numbers, but strangely you can't just enable it for all calls. If you want to auto record numbers you have in your contact list, you have to add them one by one.

Hopefully, they'll update the feature to allow for a blacklist as well, so that you can just record every single call, except calls to specifically listed numbers.

Aside from that strange design choice, I'm really glad the team added this feature. Thanks, dev team!

13
14
 
 
15
16
17
18
19
 
 

Join Josh from Side Of Burritos and our Community Manager, spring-onion in a live conversation about everything GrapheneOS on July 20th!

Monday, July 20, 2026

Time zone 24-hour 12-hour
PDT (US Pacific Daylight Time) 10:00 10:00 AM
EDT (US Eastern Daylight Time) 13:00 1:00 PM
UTC (Coordinated Universal Time) 17:00 5:00 PM
BST (British Summer Time) 18:00 6:00 PM
CEST (Central European Summer Time) 19:00 7:00 PM

To accommodate for different preferences the stream will be available simultaneously on both YouTube and a self-hosted instance of Owncast.

https://www.youtube.com/watch?v=56-DCAHU29Y
https://sideofburritos.com/live/

Additionally, we will also be watching for your questions and comments in the media channels within our Discord and Matrix chats:
https://grapheneos.org/contact#community-chat


Cross-platform posted thread announcements:
https://discuss.grapheneos.org/d/40485
https://grapheneos.social/@GrapheneOS/116946765689545308
https://reddit.com/r/GrapheneOS/s/LuFn4HroVI
https://x.com/GrapheneOS/status/2078826970687930810
https://bsky.app/profile/grapheneos.org/post/3mqytmbu6tk2h

20
 
 

Hoping to use osmand + [redacted] as a way to track my phone, after a near miss dropping it in a park the other day.

But the only options for location are, "don't allow," "aak every time," or "allow while using the app."

I thought maybe granting "run in background" might help, but OsmAnd doesn't request that permission

21
 
 

Hi everyone

Writing this on my new (second hand) pixel with grapheneos. Have been watching this project for a few years and stoked to finally be here. I'm getting closer and closer to the online life I want all the time.

I have a few questions:

  1. Sourcing apps - is it safer to use f-droid (in my case I like the neo-store) or obtainium?

  2. For non open-source apps, Aurora or sandboxed google play?

  3. Is it OK to use WiFi at my work? Or at the mall? What are the risks? I've got a VPN but using it prevents me from accessing my server via tailscale

  4. WhatsApp - I've tried to set up whatsapp but I get stuck at retrieving the backup from google drive. I'm seeing conflicting views on weather or not this is possible. It'd be great but its a price I'm willing to pay if it means not using WhatsApp

  5. Can any app be sandboxed?

  6. What else should I know about operating the phone? I'm effectively an absolute beginner to grapheneos

  7. My phone now won't connect to the internet without the VPN, is this normal?

Any advice appreciated, thank you

22
 
 

Upgrading this release from a release not yet based on Android 17 requires using the standard over-the-air update system rather than ADB sideload. For users who only update via ADB sideload, we'll be releasing a special Android 16 QPR2 release with a backported fix for the upstream Android bug causing the issue. This bug also exists in the Pixel OS for both Android 16 QPR3 and Android 17 too but it bypasses it through being bloated enough to always trigger a fallback path. We confirmed adding a 1GiB randomly generated file to GrapheneOS would bypass the issue similarly to the stock Pixel OS but we'll be fixing the issue instead.

Tags:

  • 2026062100 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a, emulator, generic, other targets)

Changes since the 2026061800 release:

  • disable MTE for Widevine Rikers service since it's incompatible with it (issue predates Android 17)
  • Sandboxed Google Play compatibility layer: avoid opening extra file descriptions to obtain Play services data prefix paths to avoid a compatibility issue with anti-tampering code used by the Kia Connect app and likely others (issue predates Android 17)
  • separate GrapheneOS framework resource IDs from AOSP resource IDs to avoid incompatibilities with Pixel vendor components (issue predates Android 17)
  • kernel (Pixel 10): fix for an upstream Broadcom Wi-Fi bcm4383 driver memory corruption bug to avoid invalid memory accesses caught by the kernel hardware memory tagging enabled by GrapheneOS
  • disable UBLK feature flag for over-the-air updates due to it likely causing update reliability issues for devices with support for it (6.6 kernel or newer)
  • disable UBLK for generated over-the-air update packages to force disable it for updates from the initial Android 17 release
  • increase the maximum size of log events in production builds to match debug builds to avoid the kernel panic message and traceback being cut off
  • use DevicePolicyManager.MAX_PASSWORD_LENGTH PIN length limit for the new upstream SystemUI PIN user interface for entering the PIN outside of the lockscreen to fix support for the expanded limit of 128 on GrapheneOS instead of using Android's limit of 16 (this didn't apply to passwords and it was straightforward to work around it by changing the PIN to a password)
  • Settings: show night light settings even when Pixel Comfort View is enabled since we're missing the settings for it (currently only relevant to the 10th gen Pixels other than the Pixel 10a)
  • allow using the new flashlight quick tile while locked (GrapheneOS requires unlocking by default for system quick tiles)
  • SystemUI: avoid crashing when trying to edit a screen recording without a video editor app
  • fix upstream bug causing the security scan in the Settings app to take much longer in Android 17 (also impacts the stock OS)
  • fix compatibility issue breaking resetting permissions for apps with special-runtime permissions (Nearby Devices is now split to have Local Network access enabled by default for compatibility for apps not targeting Android 17 and there are bugs with how this is handled)
  • Launcher: remove quick search bar from showing on large display devices since Android 17
  • Launcher: remove space reserved for the quick search bar since Android 17
  • add Pixel Comfort View settings for supported devices (Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold)
  • add back error message for entering an incorrect 2nd factor PIN for the GrapheneOS 2-factor fingerprint unlock feature
  • fix compatibility with the native zygote spawning system added by Android 17 which isn't enabled yet (this was added to provide more lightweight sandboxed renderer processes for Chromium and will benefit Vanadium even more due to having finer-grained process isolation but isn't used by Chromium/Chrome yet and our secure spawning will need to be ported to it)
  • GmsCompatConfig: update to version 171

All of the Android 17 security patches from the current July 2026, August 2026, September 2026, October 2026, November 2026 and December 2026 Android Security Bulletins are included in the 2026062101 security preview release. List of additional fixed CVEs:

  • Critical: CVE-2026-28591, CVE-2026-28604, CVE-2026-28639, CVE-2026-28662, CVE-2026-28666, CVE-2026-45515, CVE-2026-45531
  • High: CVE-2025-22442, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2026-28582, CVE-2026-28584, CVE-2026-28588, CVE-2026-28593, CVE-2026-28594, CVE-2026-28599, CVE-2026-28600, CVE-2026-28602, CVE-2026-28603, CVE-2026-28606, CVE-2026-28607, CVE-2026-28612, CVE-2026-28613, CVE-2026-28614, CVE-2026-28617, CVE-2026-28619, CVE-2026-28620, CVE-2026-28622, CVE-2026-28623, CVE-2026-28624, CVE-2026-28626, CVE-2026-28630, CVE-2026-28631, CVE-2026-28633, CVE-2026-28634, CVE-2026-28635, CVE-2026-28638, CVE-2026-28643, CVE-2026-28650, CVE-2026-28652, CVE-2026-28655, CVE-2026-28657, CVE-2026-28658, CVE-2026-28660, CVE-2026-28663, CVE-2026-28664, CVE-2026-28665, CVE-2026-28667, CVE-2026-28668, CVE-2026-28671, CVE-2026-45513, CVE-2026-45514, CVE-2026-45516, CVE-2026-45517, CVE-2026-45518, CVE-2026-45519, CVE-2026-45520, CVE-2026-45521, CVE-2026-45523, CVE-2026-45524, CVE-2026-45525, CVE-2026-45527, CVE-2026-45528, CVE-2026-45529, CVE-2026-49880
  • Unclassified: CVE-2026-28653

For detailed information on security preview releases, see our post about it.

23
 
 

Changes in version 171:

  • disable default enabled theft protection notification in Android 17
  • update Gradle to 9.6.0

A full list of changes from the previous release (version 170) is available through the Git commit log between the releases (only changes to the gmscompat_config text file and config-holder/ directory are part of GmsCompatConfig).

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release.

24
 
 

This command belkw isn't working in adb to to force immersive mode. Was wondering if there are any workarounds. The status bar is such a waste of space on my Pixel 10 Pro Fold. I tried in Settings>Display>Display Size reducing the slider but didn't help.

adb shell settings put global policy_control immersive.full=*

25
 
 

This is the initial release of GrapheneOS based on Android 17.

Due to an upstream Android 17 bug, updating to this release via ADB sideload to recovery from a previous release is unavailable. There will be no issues updating to it over-the-air and we'll provide instructions in our testing channels for early experimental testing prior to Alpha. We've added a workaround resolving updating via ADB sideload from this release to a future release. We're working on a resolution to updating via sideload from a previous release. If necessary, we could make a final release based on Android 16 QPR2 with the same workaround solely released for people who only update via sideloading.

Tags:

  • 2026061800 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a, emulator, generic, other targets)

Changes since the 2026061600 release:

  • full 2026-06-05 Pixel security patch level (released with Android 17)
  • rebased onto CP2A.260605.016 Android Open Source Project release (Android 17)
  • revert in-process Opus codec sandboxed with LFI (Lightweight Fault Isolation) to dedicated sandboxed process in order to restore compatibility with hardware memory tagging and avoid likely holes in LFI
  • Sandboxed Google Play compatibility layer: add stubs for BluetoothLeBroadcast methods
  • Vanadium: update to version 149.0.7827.159.0

All of the Android 17 security patches from the current July 2026, August 2026, September 2026, October 2026, November 2026 and December 2026 Android Security Bulletins are included in the 2026061801 security preview release. List of additional fixed CVEs:

  • Critical: CVE-2026-28591, CVE-2026-28604, CVE-2026-28639, CVE-2026-28662, CVE-2026-28666, CVE-2026-45515, CVE-2026-45531
  • High: CVE-2025-22442, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2026-28582, CVE-2026-28584, CVE-2026-28588, CVE-2026-28593, CVE-2026-28594, CVE-2026-28599, CVE-2026-28600, CVE-2026-28602, CVE-2026-28603, CVE-2026-28606, CVE-2026-28607, CVE-2026-28612, CVE-2026-28613, CVE-2026-28614, CVE-2026-28617, CVE-2026-28619, CVE-2026-28620, CVE-2026-28622, CVE-2026-28623, CVE-2026-28624, CVE-2026-28626, CVE-2026-28630, CVE-2026-28631, CVE-2026-28633, CVE-2026-28634, CVE-2026-28635, CVE-2026-28638, CVE-2026-28643, CVE-2026-28650, CVE-2026-28652, CVE-2026-28655, CVE-2026-28657, CVE-2026-28658, CVE-2026-28660, CVE-2026-28663, CVE-2026-28664, CVE-2026-28665, CVE-2026-28667, CVE-2026-28668, CVE-2026-28671, CVE-2026-45513, CVE-2026-45514, CVE-2026-45516, CVE-2026-45517, CVE-2026-45518, CVE-2026-45519, CVE-2026-45520, CVE-2026-45521, CVE-2026-45523, CVE-2026-45524, CVE-2026-45525, CVE-2026-45527, CVE-2026-45528, CVE-2026-45529, CVE-2026-49880
  • Unclassified: CVE-2026-28653

For detailed information on security preview releases, see our post about it.

view more: next ›