mpv --start=30 --force-seekable=yes https://edge.audioxi.com/NT
This works for me in Termux on Android. It produces 20-30s of silence, then starts playing the stream. There’s no way around those 20-30s probably, as the server limits the download speed for the stream.
It won’t give you the same level of exploit protection as GrapheneOS on proper hardware does, but it’s ten times better than running any other OS on the very same hardware.
UPD: Just read through it, due to GSI, they’ve stripped almost all strongest protections from GrapheneOS. It probably still be more secure and private than any other OS given the same hardware (and obviously, assuming the code hasn’t been tampered with malicious intent).
DRM, game launchers and generally 3/4 of modern software overall are a security threat anyway.
That said, the best solution for all this problems is to never buy, pirate or play any DRMed crap. Let them choke on their greedy tech.
Very nice job!
A question: what are those wires? Single core? Which diameter are they?
It’s extremely clear to anyone who is not absolutely dumb that these installation restrictions have never been about addressing scams and malware but exclusively about enforcing control and ensuring their monopoly.
You won’t need to even do it in the first place if you upgrade your phone to GrapheneOS (or other non-gplay-forced-down-your-throat OS).
What are you guys getting from there? What kind of books/materials? Not to judge or spy on you (what a spy would say), but just genuinely curious.
Fuck Microslop and fuck Google.
It’s typical corporate marketing bullshit to cover up their real authoritarian censorship mechanism: https://keepandroidopen.org/
So, basically, nothing useful.
I think this is exactly the win-win situation from this possible partnership: Motorola makes secure hardware and firmware patches, GrapheneOS takes care of the whole software security and timely updates (they already do).
Fuck google.
GrapheneOS pretty much solved the closed device trees issue you’re referring to. They don’t need them anymore and use their own toolchain to workaround the issues.
The problem with Pixel 10 was different: it was released with Android 16 QPR1 out-of-the-box, but this very QPR1 hasn’t been pushed to AOSP until a couple of weeks ago. This is why the GrapheneOS build for Pixel 10 was not possible: they could not/didn’t want to port the older Android 16 OS to Pixel 10’s hardware, and they didn’t have the source code of the QPR1 to build GrapheneOS on top of it.
Now the QPR1 (and currently even the QPR2) has been pushed to AOSP, so GrapheneOS has released Android 16 QPR1-based GrapheneOS both for older phones and for Pixel 10.
Here: