What features will be missing in GOS' Android 15 version?

missing-root The audio input and output for the analog audio jack was always very low quality due to never having a high end DAC. There's still wired headphone support via USB-C. Even the basic Apple and Google USB-C DAC provide far high quality audio.

USB-C headphones are fully compatible with our USB-C port control feature with the default Charging-only while locked node. It allows the existing connection to continue while locked but disables new USB connections immediately and then fully disables USB when the headphones are disconnected. It does reduce security compared to not using it through keeping USB data partially active after locking while it's in use, but only while in use and data is fully disabled immediately as soon as it's unplugged. New connections are also blocked immediately after locking including at a hardware level, not just a software level. The USB-C controller in Pixels supports blocking the new connections at a hardware level while keeping existing connections working and has disabling data completely as a separate thing we can do once the existing connections end. It also has the option to fully disable it for even charging, which is quite useful since USB-PD isn't simple.

Analog audio jacks going away is simply something you're going to have to accept as part of devices becoming more modern in the same way that laptops rarely have an Ethernet port anymore despite that being more secure than exposing Wi-Fi attack surface. Phones also don't have Ethernet ports but you can still use Ethernet if you really want to via USB-C in the same way you can still use wired headphones. Dedicated charging ports on laptops are also going away and being replaced by USB-C charging. USB-C technically supports up to 240W power being supplied... Dedicated display outputs are also being replaced with USB-C via DisplayPort alternate mode. This is simply how things are going. Eventually there will probably be no ports on devices... By then, hopefully all the firmware and driver code is in a memory safe language combined with far better exploit mitigations and fuzzing, etc.

ignition VPNs are per-profile and it's no different with Private Space. Private Space is essentially a replacement for managing a work profile with a local device management app. It can be used alongside it and has better integration for local usage.

Sirut OTA as normal. You will receive a normal System Update Notification and can get your beautiful hands on a shiny GOS with Android 15.

Phead

I agree a lot, the 5a was the last one with that. It didnt require pressing the power button (or keeping touch always enabled), worked way faster had less false negatives, thus allowed to register more fingers in practice.

@GrapheneOS do you know if the newer sensors since the 6 had any security benefit, i.e. less false positives? I think to have heard that the new sensors in the 9 (?) have security benefits

Has there been an announcement on when GOS with Android 15 will release?
Private space could potentially remove my need for profiles :)

Thanks

epileptic055 Has there been an announcement on when GOS with Android 15 will release?

GrapheneOS based on Android 15 will be released shortly after Android 15 has been officially released to Google Pixel phones. The porting work is already done, but the GrapheneOS team has said they won't make a release based on a beta.

The last rumors I heard was that Google will release it for Pixels on 15th October. But I do not know if this has been confirmed officially.

ryrona Few days then hopefully :)

GrapheneOS

I forgot about face unlock, I only mean fingerprint. It is way faster on my 4a than on my 6a, where I need to register every finger twice, and also had occasions where after some time I needed to re-register (which for whatever reason requires all apps like KeepassDX to re-setup).

I was only asking if the switch from back to under-screen had any security benefit, i.e. less false positives. As UX wise it was just such a degradation, really sad.

TrustExecutor Do you mean it will be possible to run sandboxed Play inside a private space, confined along with apps that need Play services, as a more convenient option than different profiles for users with lower threat models?

Could someone confirm this is the case? @GrapheneOS?

This would be an excellent thing. It would make the proposed app communication/visibility scopes for non-system components feature a bit less pressing. I've been hoping for it to become a high-priority feature since always!

Will notification cooldown make it to GOS? Either with stable release or QPR1 later on?

ryrona using a regular headphone jack would have meant less or no DRM protection for the music u listen to. Music is more easily copied when it's analog already.. that's my guess

nullable Nah, the USB-C DAC is just a converter to an analog headphone jack, so that should be no different from the DAC being built into the device. And copying DRM protected music does not exactly sound very legal.

ryrona we got too used to being told we don't own the $hit we bought. DRMing CDs and DVDs was the start. Then we let big tech get away with fraud. Consumers, lawmakers, the FTC, the police, etc think it's OK that you click "buy" on a kindle ebook you're actually renting. And that's how we ended up owning nothing and some of us actually being happy about it.

Hb1hf THIS is true ..... but good to remember from time to time

ryrona But yeah, this discussion is political

Political organizations take ownership to all topics.
The people should not accept to leave any topic only to them.

I prefer also to buy DRM free content, but it's not always well advertised. And my music tastes don't match the general music offers of the big companies.

The user can't take it's own decisions when the OS and hardware restrict artificially the devices possibilities. This is where open source, open protocols are important to give the power back to the owner of the device.