cm0002

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.

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.

Marina Dunbar in Forest Hills Mon 27 Oct 2025 06.00 EDT

For Mitch, the key issues facing NYC right now are “safety, the trains being safe, and affordability”, adding that while he’s skeptical about whether Mamdani can deliver on all his promises, he’s open-minded. “I don’t know who’s going to pay for all this stuff he wants done … but I’m going in open-minded, and just hoping somebody is offering some alternatives.”

Brooklyn, 30, also from Astoria, said their top priorities were protecting LGBTQ rights and tackling the city’s affordability crisis. “I think Mamdani is doing a great job of addressing everything I’m concerned about,” they said.

Nicole, 30, echoed that sentiment, praising Mamdani’s authenticity: “I feel like Mamdani is very genuine in his responses in a way that isn’t typically seen in most politicians. He’s a little less lip service-y than usual.”

I'm in the market for a new phone, and I'd like it to be Linux. As I've been building a table of options, I thought I'd share it. It's a wide table; sorry about that.

Phone	Display "/nits	Size mm/g	Cameras	CPU GHz	Mem GB	Battery	USBC	Lnx	US	Avail	Price
Mecha Comet								✅	🚫	🚫	£649
FairPhone 5	6.46 OLED 1224x2700	161x76x9.6 212	50/50	QCM 6490 1.9	8/256 SD	4500r	3.0	✅	🚫	✅	€499
Furi FLX1s	6.7 LCD 720 x1600	170x76x8 201	20/13	Cortex 2.4	8/128	5000	2.0	✅	✅	🚫	$550
FairPhone 6 (Murena)	6.31 OLED 1116x2484	156x73x9.6 191	50/32	Snap 7sG3 1.8	8/256	4415	2.0	🚫	✅	✅	€599
Murena HIROH	6.67 AMOLED 1220x2712		108/32	Cortex 3.35	16/512	5000	??	?	✅	🚫	$900
PinePhone64	5.95 720 x1440	??	5/2	ARM 1.152	2/3	3000	??	✅	✅	??	??
Purism Librem 5	5.7 IPS 720 x1440	153x75x15.5 263	13/8	ARM 1.5	3/32 SD	4500	3.0	✅	✅	✅	$799
Purism Liberty Phone	5.7 IPS 720 ×1440	5.7	13/8	ARM 1.5GHz	4/128	4500 r	3.0 (v)	✅	✅	🚫	$1,999
Jolla	4.5 IPS 540 x960	131x68x9.9 141	8/2	Qualcomm 1.4	1/16 SD	2100 r	2.0	⭕	🚫	🚫	N/A
Volla								✅	🚫	✅	Varies
Liberux NEXX								✅	🚫	🚫	~€1000
F(x)tec PRO¹ X								?	🚫	🚫	£649
Murena CMF Phone 1	6.67 SAMOLED 1080x2400	194x77x8 197	50/16	Cortex 2.5	8/128	5000	?	?	✅	✅	$419
Murena Teracube 2s	6.1 IPS 720x1560	155x73x10 190	20/8	MediaTek 2.35	4/64 SD	4000r	2 (¬PD)	🚫	✅	✅	$340
Xiaomi Poco X3	6.67 1080x2400		13/64	Qualcomm 2.3	6/64	5160		✅	✅	🚫	$320

It's very "me" oriented: it's biased toward US markets ('cause that's where I am); it summarizes several features such as the CPU, display, and camera (all of which get spec'd out ad nauseum in marketing) which I'm too lazy to standardize; and it's biased toward device availability. Since there isn't a huge selection of options, the minute details hold less relevance.

I welcome updates, clarifications, and corrections; I expect to keep this table up to date until at least such time as I acquire a Linux phone -- even if I am forced into using a de-Googled Android in the meantime. Given Google's shenanigans of late, I am going to factor "Linux-ability" of the de-Googled phones, in the hopes that after Google screws over the forks, we'll still have the option of installing some future more compatible mobile Linux distribution.

I've also considered making a public Cryptopad spreadsheet, but I kind of hate working with SPAs.

Minutia

• There are many more potential specs for Display, but not all vendors include all specs: nits, refresh rate, touch sample rates, colors, contrast, and protective glass. This can all be useful information, but not all vendors provide all specs, and it would blow up the table. Therefore, I include the most common information: diagonal size, technology (if provided), and dimensions.

• CPU specifics are restricted to the basics. Most specs list # of performance vs efficiency cores, multiple speed specs, and just a ton of information that wouldn't fit easily into a table; and not all vendors provide the same amount of data in anything like a standard format. So, I include the family and the fastest clock speed, because I'm not sure that even with all the other variables you could calculate an expected standby run time by knowing the slower clock speeds.

• Cameras are in megapixels, and are back/front resolutions. I do not care about video capture frame rates, modes or anything else about the camera. I have a real camera for photography.

• Mem is RAM/storage, and whether the phone takes SD cards

• Battery is in mAh, and an r suffix means replacable

• USBC is the supported version of USB-C on the device; (v) means I confirmed it supports 3.0's video-over-USB; 2.0 never does, but sometimes 3.0 doesn't, either.

• Lnx in this context doesn't mean "you can boot it," but "you can make calls" -- IE, what most people would consider daily driving. A smart phone is considered functional if

  • Calls can be placed and received
  • The screen works
  • The WiFi works
  • The speakers work
  • The USB connection works (you can charge the phone)

  In particular, VoLTE is becoming mandatory on many networks in the US, and several EU phones apparently don't support it on US networks (if at all?). Wireless charging appears to require chip support which nobody has implemented Linux drivers for. None of these phones have wireless charging, and if they did, the impression I got was that it wouldn't work under Linux anyway. Regardless, while some people might have that as a minimum requirement, I do not consider it in the "daily driver" category.

  Murena phones come with /e/OS; some are available with Ubuntu Touch.

• US is whether or not it works on US networks, AFAICT

• Avail is whether you can get your hands on one right now. Several of these are pre-order.

• I did not convert Price to dollars, despite this being a US-centric table, because exchange rates are highly variable. A couple of phones I may not flesh out; the Pine64 has embarassing hardware, and I'm fairly certain by now the the Jolla doesn't work in the US; since my goal is to get a phone for me, I'm not spending time filling in data for a phone which can't work.

Therefore, while I'm not including all de- Googled phones, I'm including some -- especially if Linux support seems to be coming along. I'm also considering only contemporary technology, because even if the battery is replaceable, I'd really not buy myself into having to upgrade soon. Murena, in particular, sells several Pixels (5, 7, 8) with /e/OS.

Phone notes

• FairPhone 5
  The one phone Murena skipped importing into the US was the FairPhone 5, despite a promising post in 2023 claiming it was coming. It's the one most interesting, and would probably be at the top of my list. The 6 doesn't bring a lot to the table and is both larger and more expensive.

• The Jolla Phone
  Jolla no longer makes this phone, and the specs are quite old.

  Jolla phones ran Sailfish, which is neither Android nor Linux, but which apparently was pretty nice. I have no knowledge of whether it was what privacy wonks would consider "secure", but it isn't open source and you can not trust anything that isn't open source.

• Volla phones
  None of the Volla phones have ever been imported into the US, and I've seen commentary that they both work on US networks, and don't. Volla phones are quite nice, specs-wise, and it's a shame we can't get them in the states.

  The Ubuntu Touch website lists the Quintus and 22 as fully functional.

• F(x)tec PRO¹ X
  Another phone with a physical keyboard which looks both fantastic and also perpetually in development with no clear indication of when, or if, it'll ever be released. The name is absurd and makes me skeptical of the entire project.

• Murena Teracube 2s
  The bootloader on the Teracube is locked, which precludes installing Linux.

• Xiaomi Poco X3
  Something of a dark horse, and a phone dating back to 2020, the Xiaomi shows as having every feature functioning under Ubuntu Touch. Unfortunately, the phone does not support VoLTE under Ubuntu Touch, which hinders its use in the US. The phone hardware itself does.

  Nobody has this phone in stock, though, so "Availability" is negative, although I suppose it could be found on eBay or something. The non-replacable battery makes buying it used a sketchy proposition.

OC by @Sxan@piefed.zip