Take a look at the security functions the Pixel platform hardware provides. It isn’t optional.

GrapheneOS is Android though.

I’ve also thought of that option, since it offers flexibility and allows better receiver placement.

Thanks for the suggestion, but I was thinking of continous, transparent position fix acquisition.

While I use Vanadium, it doesn’t support the basic Firefox plugins.

To hell. In a handbasket.

You still don’t?

Dunno, for now Ironfox and Vanadium as a fallback work for me on mobile. I’m open to alternative browsers when the upstream fails.

No use cases for this so far.

Mobile service quality is defined by the baseband, which is an immutable blob to the OS. I phone rarely and currently use my old LineageOS phone for it.

I’ve got a support case for my Pixel 7a open due to potential battery issue. If I return it I will buy a different, bigger (6.7") Pixel model. My new Pixel tablet is doing fine so far.

I use tablets to read things when lying down, so notebooks don’t fit.

Matrix (Element), Signal, Telegram. Other stuff probably requires Google services which I don’t use on the tablet. Phone has Google services, but I don’t really use it for messaging other than Signal.

I’m on GrapheneOS on tablet/phone for time being, but I’m fine going back to a dumphone and a Linux or BSD tablet or convertible.

The Keeling Curve and lately the isotopic composition is telling you everything you need to know. The only “good” news is that we’re at the extraction limit.

The Internet is a bunch of Autonomous Systems running open source protocols. It is doing fine.

Supports Linux apps poorly.

Their ChromeOS tablets suck as well. The only reason for me to buy Google hardware is to put GrapheneOS on it.

Yes, I’ve also gone back to Hacker’s Keyboard on GrapheneOS (been using it on LineageOS for years) after checking out some alternatives. Interestingly enough, my new Pixel Tablet’s screen has less contrast than my trusty old AMOLED on my Samsung Tablet.

Thanks! FYI, I went for Hacker’s Keyboard (apk downloaded from F-Droid since newer version than GitHub) after all. I hope this does not have a severe security impact on my setup.

I’ve made a support request and chose the payout version rather than a free walk-in repair for my 7a. I will be contacted by an agent within three weeks. Probably have to revert to Google stock if I have to send it in.

GitHub blurb mentions “WARNING: This is a rather ancient project that was originally developed back in 2011 based on the Android 2.3 (Gingerbread) AOSP keyboard. While it still works as-is for many users, it would need some major rewrites to work with newer APIs, and some features such as language switching or popup keys don’t work right on modern Android systems. I’m not currently planning on significant updates, and it’s possible that it will stop working on modern devices or will no longer be updateable via the Google Play store due to minimum API level requirements. Play Store requires targeting API level 29 (Android 10), while the code was written for API level 9 (Android 2.3) from 2011.” and I thought I saw that the F-Droid package is 7 years old.