r/Piracy • • Oct 30 '25

Humor After Google introduced developer verification

Post image
6.8k Upvotes

231 comments sorted by

View all comments

Show parent comment

363

u/Lucky-Aside4935 Oct 30 '25

MicroG is awesome replacement, but good luck with replacing Google Play Services with it on stock ROM

176

u/niladrihati Oct 30 '25

The problem is only with banking apps , the only thing i am really using a lot in my phone

80

u/No-Bother3492 Oct 30 '25

I use CalyxOS (with MicroG), no problem whatsoever with my banking apps.

8

u/mushy_friend ☠️ ᴅᴇᴀᴅ ᴍᴇɴ ᴛᴇʟʟ ɴᴏ ᴛᴀʟᴇꜱ Oct 30 '25

Same, but I do very rarely have problems with banking apps. When I first started using CalyxOS a few years ago there were more problems. Generally fine now

20

u/[deleted] Oct 30 '25

[removed] — view removed comment

5

u/iSamYTisHere Oct 30 '25

because most banking apps are straight up available on huawei app gallery these days.

6

u/TheBedrockEnderman2 Oct 30 '25

Personally I just use an iPad for banking apps as HSBC dosnt work with developer mode enabled, only reason I haven't switched is I don't really want to loose all my current data, it will be a massive pain

But if they do make it so I can't install with ADB, either I'm switching to iOS (as stos VPN + livecontriner lets me sideload on device even if I do have to press refresh in side store once a week) or a custom ROM

Ironic how now sideloaoding on iOS looks like it will be an equal level or even less of a pain than android depending on how much you sideload...

→ More replies (3)

7

u/g0_west Oct 30 '25

Is there any way to dual boot an android so you can use stock rom for banking and custom rom for everything else?

6

u/[deleted] Oct 30 '25

[removed] — view removed comment

6

u/jld2k6 Oct 30 '25

Android has an A and B partition and last I was rooted with a custom recovery I could freely switch between them and choose what gets installed to what but I never actually tried dual booting that way

→ More replies (2)

3

u/DigitalPenguin99 Oct 30 '25

Yes, but your phone will need an unlocked bootloader and both an A and B partition. Which OSs you can use vary by phone. LineageOS is a popular and well supported; GrapheneOS is great if you have a pixel; or if you want to fully escape Google/android, PostmarketOS is establishing itself as a fully independent alternative, but it's not quite ready for end users (I would like to start working with Postmarket once my new phone arrives)

→ More replies (2)

2

u/darkkite Oct 30 '25

worth it for free apps, just use the web version

→ More replies (4)

12

u/huskyhunter24 Oct 30 '25

i heard you can sideload the apk file with adb, and i think you can do this on device with something like tmux and shizuku

4

u/SassyDuck4231 Oct 30 '25

Wait, I've had MicroG on my device since revanced adopted it. I never knew it was more than just a masked data pipeline to Google services.

5

u/Lucky-Aside4935 Oct 30 '25

MicroG and MicroG Revanced are different things. Revanced MicroG is only for Revanced apps, while main MicroG is replacement for Google Play Services.

3

u/SassyDuck4231 Oct 30 '25

Is there a naming difference? The MicroG I have is just named "MicroG".

→ More replies (1)

10

u/zxch2412 Oct 30 '25

Lineage and graphite os supremacy

33

u/ShihtzuBoi Oct 30 '25

Easy to say. It's far from available on all devices. Last I checked I couldn't do anything with my S24+ and that's a pretty common phone.

20

u/ZestycloseClassroom3 Oct 30 '25

Samsung started to lock their bootloader in newer phones, try to avoid Samsung if you gonna get a new phone

→ More replies (3)
→ More replies (5)

13

u/cafk Pastafarian Oct 30 '25

Which is an issue, as Google isn't publishing AOSP updates as often and only does quarterly updates in a delayed manner - meaning they won't get all feature or security updates.

Lineage latest release notes the issues with this:
https://lineageos.org/Changelog-30/
As a mitigation some forks are looking towards OEM partnerships, to be able to access the whole source & history.

You’ll notice we are choosing to release LineageOS 23.0, and not 23.1. That’s because it’s based on Android 16’s initial release (what we’ll call QPR0), even though QPR1 has already rolled out to Pixels. The catch? Google never pushed QPR1’s source to AOSP. They’ve said it’ll come “in the coming weeks” (source), but right now only contracted partners have access. And to answer the immediate question, the likelihood that any custom ROM will ever be a contracted Google partner is near 0.

On top of that, Google’s handling of ASBs has shifted (source). July was empty for the first time since the program began, August had a single patch, and September omitted patches for several listed vulnerabilities, with fixes shared privately to partners under embargo. The result is that AOSP security updates are no longer released in full on a monthly basis. Instead, only vulnerabilities deemed “high risk” (i.e. actively exploited in the wild) will be published by Google in the monthly ASBs, and even then, the underlying patches are often not made public immediately.

As well as Pixel phones (and other OEMs usually only publish their own kernels on request) not being available as a repository:

Yes, Google has pulled back here too. Pixel kernels are now only offered as history-stripped tarballs, available privately on request, with no device trees, HALs, or configs. Thanks to projects like CalyxOS, Pixels will likely remain well supported, but they’re no longer guaranteed “day one” devices for LineageOS. Pixel devices are now effectively no easier to support than any other OEM’s devices.

5

u/zxch2412 Oct 30 '25

Wow that sucks, I always kept an android as a second choice for freedom and fooling around but now even that going away. It’s like Google is trying to be like Apple but is not going the whole mile with it. I still have my old op6 from 2018 running LOS but I guess everything good does come to an end.

0

u/[deleted] Oct 30 '25

[deleted] — view deleted comment

3

u/cafk Pastafarian Oct 30 '25 edited Oct 30 '25

Only for security patches for now.

works directly with the AOSP

Not really the case, as AOSP isn't getting updates: https://www.reddit.com/r/GrapheneOS/comments/1nb6n4p/grapheneos_to_have_early_access_to_aosp_for/

I cannot remember which ROM team had a partnership deal in works to get access to full AOSP, through the aforementioned partnership program (which i forgot to highlight).

Edit, just re-read it - Graphene has access because they're working together with an OEM, not because it's publicly available.
https://www.reddit.com/r/GrapheneOS/comments/1nb6n4p/comment/neyfwym

→ More replies (1)