😂

Big fan of trip-hop & liquid DnB.

Trip: https://www.youtube.com/watch?v=gEbU9EZsETY

Liquid: https://www.youtube.com/watch?v=jlTAnxX_R9Q

Bonus: https://www.youtube.com/watch?v=SltSONdHf5k

I really wish there was a way to run microG with graphene. I don’t want google binaries on my pixel at all if I can avoid it.

Till then, Calyxos with microG is privacy respecting but likely won’t resist feds trying to get at your data. If you’re just looking for strongly improved privacy and some moderately improved security, Calyx is pretty nice.

That’s wack as hell.

In my case, Medtronic does a lot to prevent inspection of how their apks work at all, encrypting and obfuscating the code to make open-source emulation extremely difficult.

Luckily, hackers don’t quit.

Imagine one of my medical apps refusing to run because of adb…

No, some 1200cc motorcycles use them.

How do they have so much time and creativity to devote here?

https://www.youtube.com/watch?v=EC1C0lH1SqM for the werewolf version

Err… That component appears to be built from source per Calyx’s Gradle rules? The source is pulled from here: https://android.googlesource.com/platform/frameworks/base/+/refs/heads/main/telephony/java/android/telephony/euicc

My hardware is too old to support MTE. I’m running a pixel 3 because I’m more worried about damaging our earthly environment with this constant hardware churn.

I’m sorry you’re unhappy that I’m happy. I’m still able to run Android 14 in a reasonably secure manner, I’m able to exchange information with other people easily, without Google getting much information from me, and that’s satisfactory. My actual security relevant machinations happen on my much better protected laptop.

Thanks for your input, have a nice day.

Dude I’m looking at the source code, there’s only a binary downloaded for enabling Safety net. Why are you making false statements?

Very nice. Can I use the much smaller codebase of microG instead of Google’s? Even you do not know how Play Services actually works, and that’s a problem.

Further, a memory exploit that leads to compromise would need a chain of privilege escalation. There’s a lot in the way of making that trivial even on stock Android. And you know what helps reduce risk of exploit? Smaller codebases.

Just about all of your identifying data is stripped out by the framework before interacting with Google at all: https://github.com/microg/GmsCore/wiki/Google-Network-Connections

That alone makes it an important tool. I’m not too worried about memory exploits as I don’t really install apps, but it’s an important feature in graphene’s toolkit.

For most people who want an Android alternative that’s open source but don’t have time to fiddle with it, calyxOS seems like a good solution. It just works out of the box.

I like calyx, might try graphene some day. But I absolutely won’t run Google’s play services ala graphene. It’s sandboxed, supposedly, but why run it at all?

Calyx uses microG, a much smaller, fully open source emulator of Google’s services.

Shhhh THEY’LL HEAR YOU

I wouldn’t have said it was a replacement just yet to non -open source centric folks, personally.

More attention isn’t a bad thing though, sometimes devs need more input to decide what to focus on next.

Your point?

I haven’t run graphene, so I can’t speak for it. But on any other android variant, microG is a system-app, so that it can spoof Google’s services properly. That means patching the system.

Functional apps is the important bit, use of microG allows apps to provide push messaging etc without knowing Google services aren’t installed. There’s still some communication with Google as a result, but it’s fully sanitized.

I invite you to try installing common apps like Strava or Pokemon go without any Google services at all.

It’ll at least give you good directions, car/bicycle/walking-optimized based on what you select.

It’ll get there, just needs time.

There’s also CalyxOS if you don’t want to run anything Google on your phone at all, but still have functional apps and such.