I learned something today: Google's Gemini "AI" on phones accesses your data from "Phones, Messages, WhatsApp" and other stuff whether you have Gemini turned on or not. It just keeps the data longer if you turn it on. Oh, and lets it be reviewed by humans (!) for Google's advantage in training "AI" etc.

But this only came to my attention because of an upcoming change: it's going to start keeping your data long-term even if you turn it "off": "#Gemini will soon be able to help you use Phone, #Messages, #WhatsApp, and Utilities on your phone, whether your Gemini Apps Activity is on or off."

This is, of course, a #privacy and #security #nightmare.

If this is baked into Android, and therefore not removable, I'd have to say I'd recommend against using Android at all starting July 7th.

https://www.extremetech.com/mobile/gemini-ai-will-soon-access-calls-and-messages-on-your-android-even-if-you

#spyware #AI #LLM #Google #spying #phone #Android #private #data

GrapheneOS: the private and secure mobile OS

GrapheneOS is a security and privacy focused mobile OS with Android app compatibility.

GrapheneOS
@dragonsidedd Not an option for an awful lot of phones; easiest to implement on Google's own phones; also a nightmare for people not tech-savvy. @cazabon
@ZenHeathen I'm curious which part is a nightmare. When I started using it, I was afraid it would be a big ordeal (as someone who just wants to use their phone, not tweak it), but I found it surprisingly straightforward. And it seems like if you go the less paranoid route and use sandboxed Google Play and still install from the Play Store, the user experience is mostly like using vanilla Android. But I am somewhat tech-savvy, and I was expecting it to be worse, so it's possible that I've just forgotten some of the bumps in the road.
@dragonsidedd @cazabon

@internic @ZenHeathen @cazabon Also honestly curious about what is nightmarish on Graphene.

I specifically suggested Graphene for general advice instead of PinePhone, which I prefer -- but I have been using Linux desktop for ~20 years and Windows flummoxes me

https://pine64.org/devices/pinephone_pro/

PinePhone Pro

Meet the PinePhone Pro, our flagship smartphone and the best way to experience mainline Linux on a mobile device. Features and Specifications System on Chip (SoC) Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz GPU ARM Mali T860 4x core GPU @ 500MHz RAM 4GB LPDDR4 @ 800MHz Storage 128GB eMMC flash storage Optional micro SD card (SDXC up-to 2TB) LCD panel 6β€³ 1440 x 720 in-cell IPS with Gorilla Glass 4β„’ Cameras 13MP Sony IMX258 main camera with Gorilla Glass 4β„’ protective layer 8MP OmniVision OV8858 front-facing camera Modem & GPS Quectel EG25-G – global GSM and CDMA bands GPS, GPS-A, GLONASS WiFi & Bluetooth AMPAK AP6255 WiFi 11ac + Bluetooth V4.1 I/O MicroSD slot Pogo-pins (compatible with the original PinePhone) USB-C power, data (USB 3.0) and DP alt-mode video out Sensors Accelerator Gyroscope Proximity Compass Ambient light Privacy hardware switches Cameras Microphone WiFi and Bluetooth LTE modem (including GPS) Headphones (to enable UART output) External buttons Volume up / down rocker Power ON/ OFF Audio Out Headset speaker Audio jack Loud Speaker Other Flash / Torch Vibration motor Status LED UART via audio jack Battery Samsung J7 form-factor 3000mAh Charging 5V 3A (15W) Quick Charge – USB Power Delivery specification Dimensions 160.8 x 76.6 x 11.1mm Weight Approx. 215g Stores Global Global: Accessories Global: Spare parts EU EU: Accessories Affiliates Documentation PinePhone Pro Datasheets, schematics and certifications What’s inside? We learned a lot from working on the original PinePhone. Over the past two years we painstakingly collected and analyzed your feedback and explored all avenues for hardware improvements. The PinePhone Pro is the end result of this journey. It is powered by a Rockchip hexa-core SoC operating at 1.5GHz, and ships paired with 4GB of dual-channel LPDDR4 RAM as well as 128GB of internal eMMC flash storage. It features a high-fidelity 13MP main camera sensor and a 5MP front-facing camera.

PINE64

@internic @ZenHeathen @dragonsidedd @cazabon My experience as a Danish citizen, is that a bunch of apps for interacting with government are at best challenging to make work, some (MitID) are impossible. For stupid reasons that I can do nothing about.

For now I use alternative but slightly more cumbersome workarounds, but it is definitely eroding the otherwise very positive experience I'm having with GrapheneOS.

I might cave in and buy an iPhone, eventually.

@m @internic @ZenHeathen @dragonsidedd @cazabon mitID only working with chrome is a freaking scandal.

@Ruth_Mottram @internic @ZenHeathen @dragonsidedd @cazabon The problem with MitID on GrapheneOS is the Google Play integrity check the app require, which will only work on Google authorized Androids logged in to Google, as far is I know.

Pretty nice racket Google have going there.

@m @Ruth_Mottram @internic @ZenHeathen @dragonsidedd @cazabon When "Security" forces you to use an insecure operating system.

Owellian Newspeak...

@m Yeah, based on your first post I figured it was a Play Integrity problem. I knew that this could be a problem theoretically, I just hadn't personally encountered it, aside from one case; my authenticator (Authy) stopped working one day due to them abruptly turning on Play Integrity checks, which was problematic. But in that case I could just switch to an alternative. With a government app, that's a much bigger problem. @Ruth_Mottram @ZenHeathen @dragonsidedd @cazabon

@m @internic @ZenHeathen @cazabon
> apps for interacting with government

That's the problem right there. Governments should produce *webpages* that are open standard and can be used on any device.

*Apps* on the other hand are tied to a vendor. I better not need to buy an Apple or Google phone to get government services.

@internic I didn't mean the user experience; I haven't had the experience, myself. I meant the process of trying to fight the OS you have and vendor lockouts and crap to get to a point where you can try to install it. @dragonsidedd @cazabon
@ZenHeathen Oh. The install was pretty trivial for me (another surprise), but I bought a Pixel new, directly from Google (so unlocked). I'm guessing you're referring to scenarios like using a preexisting phone that may have a locked bootloader, and, yes, I can believe that could be a nightmare. @dragonsidedd @cazabon
@internic Yes, a Pixel--that's the one where alternate OSs are quite simple to install, but you're buying Google's own phone, and so directly giving them more money. @dragonsidedd @cazabon