GrapheneOS version 2025110600 released


Both of the November 2025 patches have been provided in our regular non-security-preview releases for over a month, so we've already had the 2025-11-05 Android security patch level for over a month. Our patch level is set based on providing both the Android and Pixel security patches, so we're leaving it at 2025-11-01 until the Pixel stock OS release and Pixel Update Bulletin are published. The stock Pixel OS also included both November 2025 patches in early September. We expect they made a 2nd October release to ship the November carrier changes and will make a release in mid-November with patches from future Android Security Bulletins.

Tags:

  • 2025110600 (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, emulator, generic, other targets)

Changes since the 2025102800 release:

  • raise declared patch level to 2025-11-01 which has already been provided in GrapheneOS since our regular 2025090200 release (not a security preview) since the patches were included in the September security preview and were then pushed to AOSP despite not being listed in the bulletin
  • kernel (6.1): update to latest GKI LTS branch revision
  • kernel (6.1): keep POSIX_MQUEUE disabled to avoid increasing attack surface
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.114
  • kernel (6.12): update to latest GKI LTS branch revision
  • adevtool: switch to obtaining Android 16 QPR1 backports from the latest October releases for 7th/8th/9th gen Pixels (6th gen Pixels did not have an October release) for very minor radio carrier configuration changes (no code changes)
  • Settings: add 1 second delay for approving device admin activation to mitigate tapjacking (this matches the 1 second delay we add to both permission prompts and ADB authorization prompts which is currently not configurable)
  • Vanadium: update to version 142.0.7444.138.0

All of the Android 16 security patches from the December 2025, January 2026, February 2026 and March 2026 Android Security Bulletins are included in the 2025110601 security preview release. List of additional fixed CVEs:

  • Critical: CVE-2025-48631, CVE-2026-0006
  • High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2025-22420, CVE-2025-22432, CVE-2025-26447, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634, CVE-2026-0005, CVE-2026-0007, CVE-2026-0008

2025110601 provides at least the full 2025-12-01 Android security patch level (a Pixel Update Bulletin for November 2025 hasn't been released could have fixes we don't get early, although it's likely empty) but will remain marked as providing 2025-11-01.

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

Vanadium version 142.0.7444.138.0 released


Changes in version 142.0.7444.138.0:

  • update to Chromium 142.0.7444.138

A full list of changes from the previous release (version 142.0.7444.48.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

"Two headlines from yesterday (Nov. 6):

'Musk Could Become World’s First Trillionaire in New Tesla Pay Package'

'SNAP Recipients Go Without Food After Benefits Don’t Arrive'

And there is the moral rot of our capitalistic empire. A trillionaire shouldn’t exist, especially in a world where children are starving."

~ Brian Kaylor

#Musk #Tesla #trillionaire #SNAP #food #hunger #children #capitalism #shutdown #Republicans

publicwitness.wordandway.org/p…

Recently, a trained, active firefighter said that smoke alarms and CO2 alarms have different beeps. Smoke is three longer beeps, while CO2 is four shorter ones. I don't doubt he knows what he's talking about, but I've never heard a residential smoke alarm that doesn't alert using a continuous series of beeps with no pause at all. I'm not sure why there's a disconnect between firefighters' knowledge and what I've heard from real alarms my whole life.
in reply to Alex Hall

The current code 3, or temporal pattern, used pretty much everywhere these days, is somewhat recent. It was codified in 1996, and even for a while after that, fire alarms did all sorts of different things over the years. The most common in households in the late 80s to about late 90s was a continuous bunch of beeps with only very short pauses between them. The speed and pitch varied by brand. This came after the previous generation of alarms, which would give one loud, continuous beep, usually with an actual paper speaker. This was much lower in frequency, maybe 500 to 600 hz. We had some of these in my house when I was a very small person.
This entry was edited (5 days ago)
in reply to Borris

@BorrisInABox Borris: Excellent nugget of information.
Alex: In the like vein of this informationn, indicating that the alarms you're using could potentially be as old as 30 years, it is most certainly advisable to replace all of these older alarms ASAP. All alarms actually do indeed have an expiry date, beyond which some of the materials used internally in the detection process actually decay and become less effective, until in fact the device becomes ineffective at its job, as more time passes.

Dog owners should be subject to strict inspections and recurring training to ensure they have the necessary time, skills, and dedication to own such an animal. Dog attacks and bites are stupidly common, and they really shouldn't be. I can barely fart without a permit and three licenses, but any fucking idiot can get a dog, neglect it, and have it bite a toddler - and then the dog gets blamed and put down. Insanity.

This is most likely my most controversial take.

I'm very much getting tired of explaining to people why I'm still in high school at 41, especially to GenZ teachers. Yeah, it might only be in dreams, but it, along with the inevitability of a fire alarm going off somewhere (never a residential one, by the way), happens just about every night, or whatever passes for night.

Have you ever booted a zip archive? I was doing my regular computing shenanigans, and then it dawned on me that a floppy image can be a valid ZIP archive. That's because the boot sector and the FAT table are at the beginning of the file, and the ZIP file header is at the end of it. The trick was used in the past for something called "rarjpeg" (a JPEG image that is a valid RAR file).

I needed a test fast, so I took @nanochess's bootBASIC, and created a file that has the bootsector at the beginning, then 701709 bytes of padding, and then 25159 bytes of ZIP file with the bootBASIC sources.

It can be unzipped by your favourite archiver, or booted in your favourite emulator ( qemu-system-i386 -fda bootableBASIC.zip)

The file: drive.google.com/file/d/1JQgBS…

Peter Vágner reshared this.

Hello @Friendica Developers ..

It seems, my search doesn't work after installing new because of changed Linux Distro.

edit: not "installing new".. I imported the backup of the database, etc.. and copied my friendica folder to the server etc..

If I search this string: https://mastodon.online/@amicalucis/115406224193886465

I get a page not found error:

Exception thrown in /usr/share/nginx/boerdica/src/Module/HTTPException/PageNotFound.php:35
Stack trace:
\#0 /usr/share/nginx/boerdica/src/BaseModule.php(251): Friendica\Module\HTTPException\PageNotFound->content()
\#1 /usr/share/nginx/boerdica/src/Module/HTTPException/PageNotFound.php(53): Friendica\BaseModule->run()
\#2 /usr/share/nginx/boerdica/src/App.php(595): Friendica\Module\HTTPException\PageNotFound->run()
\#3 /usr/share/nginx/boerdica/src/App.php(190): Friendica\App->runFrontend()
\#4 /usr/share/nginx/boerdica/index.php(22): Friendica\App->processRequest()
\#5 {main}

The same when I search a user like @memo, a hashtag like #tree or a group like !friendica..

The friendica log shows nothing for this error.. Only the usual memory limit errors, all the time..

Does somebody have an idea?
Thanks

It's official: WhatsApp (non-beta) for Windows is going to be downdated to the web version on november 5th. I just got a pop-up when I opened the app. The text is as follows:

The next update starting 5 November

Some changes are coming to WhatsApp for Windows. Channels will be available and you’ll be able to do more with Status and Communities.
What will happen:
• You’ll be logged out
• You’ll need to open WhatsApp on your phone to log back in
• Up to 1 year of chat history will sync from your phone
<OK>

I've said it before, but it's disappointing when small things let down the #accessibility of an otherwise good interface.

For instance, I've told many people that the Tailscale web UI is actually quite good with a #screenReader. Unfortunately, the first thing an NVDA user hears after authenticating is a bunch of nonsense caused by an unlabelled SVG, and it doesn't create the best first impression:

"
banner landmark visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
"

This entry was edited (6 days ago)

По совету @abera80486 перешёл с пены для бритья на мыло для бритья. Взял мыло Proraso, лезвия Feather. Иии... сразу испортил себе впечатление порезами и раздражением. Но потом вернулся к копеечным лезвиям Спутник, и всё стало хорошо.

Теперь порезы случаются крайне редко, и кожа морды лица не раздражается. Да и баночки с мылом, кажется, хватит очень надолго - разровнял мыло ложкой перед первым использованием, чтобы легче было елозить помазком, с тех пор его как будто меньше не становится. На моей азиатской физиономии волосня какая-то редкая и короткая, но если не бриться пару дней, становлюсь похожим на алкаша. Борода не успела вырасти, так уже первые седые волосы пошли, лол.