other8026 These things seem strange to me. I agree that there might be some upstream bug, but I am not sure how carrier config can affect wifi like this. I'd think that the best way to figure out what's really going on would be by seeing the full system logs.
Yeah, it's super weird, moreso since Bluetooth isn't affected, which I believe might tip the scales further towards something in software and not hardware. I'll try to upload a syslog.
other8026 as I alluded to, I'm not in a place where a reset is a practical possibility, if only because reauthorizing Signal and WhatsApp would be impossible. I've been there since my initial message.
Bandwith and outages-wise, re-downloading both a stock image and GrapheneOS would probably take half a day. I'll definitely do it once I'm back in a more normal location, at which point I will not be putting the SIM I am using here back into the phone.
The workaround described here works, hence my sneaking suspicion that it might come from something upstream.
So, one thing that works is activating airplane mode, rebooting with airplane mode activated, and THEN activating Wi-Fi or hotspot.
WiFi scans correctly and can connect, and the hotspot activates as well.
Best I can garner for now (I'm in a place where my home provider doesn't have a roaming agreement, and I'm not switching my home sim on here) is that there's some type of upstream bug that might be linked to cell providers who don't allow connection sharing / hotspots, and that, for some reason, is then also applied to activating WiFi.
Guardian piece here, Forbes piece there.
Anyone got a message ? Do we know if an affected GrapheneOS device passes attestation ?
Thanks a lot for the pointers!
The safe mode reboot got me connected, once, and now we're back to the old ways.
Hotspot won't start and just says "error"
Hi,
seems like my WiFi died completely (the scan stays stuck on searching for networks, no matter what)
I’ve tried resetting the internet settings, to no avail. Rebooted a few times as well.
Logs give me “failed to unregister death recipient! com.android.server.wifi.scanner.wifiscanningserviceimpl$internallistner@xxxxxxx”
Device is on 2024121200.
Would anyone know what’s going on and how to fix this ?
EDIT: Ah, spoke too soon. Sorry. Might be linked to the killswitch, but crash-a-delic with memory tagging on.
Xtreix I know from my experience that IVPN, ProtonVPN, Cloudflare WARP and Orbot all have bugs when Memory tagging is enabled
FWIW, ProtonVPN (5.6.38.0) seems to be working OK here, Hardened Malloc, Memory Tagging on, debugging, JIT, code loading disabled/restricted.
N1b People ask questions specific to their situation and we can give education for them to make informed decisions
OK, good, practical use case then: what are the community's recommendations for the thread model described at the end of the report right here ?
Please keep in mind that the usecase described implies plausible deniability for highly non-technical users, and that it must be assumed that the devices will be searched. The adversary's remote capabilities are described here.
matchboxbananasynergy People who realize that improvements can be made to the overall looks of some of the default AOSP apps which are dated, but would rather the team prioritize security and privacy features over spending time on that aspect of the experience.
Without going into the type of decision making that's associated with default apps, is there a way for the more graphically competent of those people to contribute, say, colour themes ?
de0u Thanks for the explanation - makes a lot more sense.
This is probably a bit of a dumb question, but I'm curious as to why, rather than reaching out to the individual banking app devs, one couldn't try to reach out to Google themselves and fix the issue at the root by getting GrapheneOS certified on that side ?
Hi,
I was wondering what the already in place / planned mitigations were for threat models in line with those described in ENEA's Location Tracking on the Battlefield report.
(and yeah, I've done the homework and get that the IMEI issue can pretty much only be done through something like a mobile router)