P

pixel9

I'm in the same boat. I was planning on using a secondary profile as my main profile most of the time. But I normally like to keep both wifi and mobile data switched off and turn them on as needed (to save battery [it seems to prolong it a lot] but also because I have very limited data, so I only turn data on when needed).

So it seems like I may have to abandon my secondary profile and just use the Owner profile. It's weird how toggling wifi is OK but data toggle is forbidden, even if you enable phone/sms in the secondary profile.

if you disable the 4g the apps on the secondary profile will not work anyway

There are a lot of apps that work without Internet access. (I like these kinds of apps. I like apps that don't rely on the Cloud.) An example is Organic Maps: You can download the map data ahead of time and then the app will work without any kind of network access (for example, if you are driving through an area with spotty service).

Android 15 QPR2 is moving 6th/7th/8th generation Pixels to the Linux kernel's 6.1 LTS branch already used for 9th generation Pixels. This will reduce the kernel branches we need to support down to 6.1 and 6.6. There will likely need to be a yearly migration for all the devices.

Linux kernel increased official support time for the Long Term Support (LTS) branches from 2 years to 6 years, mainly for Android devices using Generic Kernel Image (GKI) releases. However, it was recently reduced back to 2 years. Pixels will need to start migrating every year.

It will likely take around 6 months for a new branch to be considered stable enough with most regressions resolved and another 6 months to successfully integrate and ship it. Therefore, 2 years of support implies yearly migrations to keep up rather than doing it every 2 years.

Upstream LTS releases are closely connected to Android. Moving to 6 years of support was likely closely connected to the Pixel 6 moving to 5 years of support. GKI made the drivers far more standalone and easy to migrate, and Linux moving back to 2 year support is likely related.

Google has been testing newer kernels with the Pixel 6 and later for years. They have 6.6 and newer mainline kernels working fine already, it just takes a long time until the kernels are stable enough to consider shipping them. It's great that it's finally going to be happening.

Newer kernels bring many new features and increasingly complexity which means they bring lots of new security bugs. Older kernels get an increasingly small subset of bug fixes including security fixes backported in the LTS releases. Newer kernels also bring new security features.

Using a year old kernel for around a year and then upgrading to a new year old kernel is likely the best balance that's available. With 2 year support time, they can focus on backporting more patches and providing more testing/stability since there will be far fewer LTS branches.

It's not commonly understood that Android itself only has a single LTS branch, which is current Android 15. It receives monthly and quarterly updates. It moves to a new LTS with a yearly update after it has gone through many months of public testing via Developer Preview / Beta.

Many people including journalists covering it in tech news media wrongly believe Android's monthly security patch releases are the monthly releases. No, the monthly security patches are backports of a subset of the privacy/security patches to older releases. They're incomplete.

Android's monthly releases have many changes beyond privacy/security patches even when it's not a quarterly or yearly release. They also have a lot more privacy/security patches than the Android Security Bulletin backports. They backport High/Critical severity patches, not all.

These updates are a major factor in why Pixels are the only Android devices with competitive security with iPhones. Pixels also have a lot of hardware security features not implemented on other Android devices. They also have higher quality of implementation across the board.

Google will likely require other OEMs start upgrading kernel branches. However, standards for other OEMs are always far lower than the standards met by Pixels. For example, many important hardware security features are recommended in the CDD, not mandatory, or not even listed.

We aren't aware of any OEM trying to keep up with the monthly releases, only OEMs skipping all the monthly/quarterly releases but trying to ship the yearly release around the official launch. Only Samsung tries to keep up with the new security features, but lags quite behind.

Other Android OEMs do the bare minimum required by Google unless their SoC vendor (generally Qualcomm) hands the feature to them on a silver platter with no additional cost. They largely ship the monthly security backports now, but with significant delays or skipping some months.

The reduction of support time for Linux kernel LTS releases from 6 years to 2 years is likely going to become a major problem for non-Pixel Android devices. Google will likely require them to upgrade but probably at a very delayed schedule where they fall out of support first.

Our official hardware requirements are listed here:

https://grapheneos.org/faq#future-devices

You can see support for Linux 6.1 or 6.6 is already a requirement for new devices. We'll be adding a requirement to upgrade the kernel branch because it will be essential with 2 year Linux LTS support.

Social media threads:

X: https://x.com/GrapheneOS/status/1860365266921603389
Bluesky: https://bsky.app/profile/grapheneos.org/post/3lbmyp4jfi22b
Mastodon: https://grapheneos.social/@GrapheneOS/113533415116755738

Although not a traditionally formatted roadmap, one can view all open issues on the project's GitHub to understand where the work is currently going.

You could assess your own roadmap by looking at the open issues tagged as "priority-high" or "priority-max" here:
https://github.com/GrapheneOS/os-issue-tracker/labels/priority-high

Not a stupid question at all. Follow these steps:

1. Open your contacts app (stick with the AOSP contacts app that comes with GrapheneOS for this)
2. Tap on the menu button on the top left of the app.
3. Tap "Create Label"
4. Name your label
5. You'll be taken to your new label. Tap "Add contacts"
6. Press and hold the contacts you want to add to the label, then tap "add" on the top right once done
7. Go to the app where you want to give access to this label, in the contact scopes menu
8. Tap label
9. Select the label you just created
10. tap "Add to the list of scopes

All done!

One of the way how to delete all contacts:
Go to apps, in upper right corner confirm showing system apps and use search box to find Contacts storage. Clear cache and storage of the app and you will get rid of all contacts.

gpad1 following on from DeletedUser115 if say Startpage.com was your preferred option, the only way to get that particular search engine added to the list would be to go to the site settings, change HTTP Request method from POST to GET then do a search, add the engine and then change it back from GET to POST.

Try searching in your preferred search engine (make sure it's not in incognito tab) then open Vanadium settings / Search Engine and you should see an option to set your search engine as default.

You can't add extensions to Vanadium, you can use network-based ad blockers

FU6QydnIELkx You actually can add Startpage as a search engine in Vanadium. Before you search (also make sure it's not in incognito mode) you have to go into the settings of Startpage & change the HTTP request method from "POST" to "GET." Then do a search on Startpage & you should see it show up in the list of search engines.