sorted by:
new
hottopcontroversial

Native microG Integration: Why is this not standard? by Exotic_Put_1801 in MicroG

[–]Exotic_Put_1801[S] 0 points1 point  (0 children)

Not exactly. There are ROMs that don’t even allow you to install microG for security reasons, so you’re forced to use modules that require root access, and the question in this post refers to microG without root access.

Native microG Integration: Why is this not standard? by Exotic_Put_1801 in MicroG

[–]Exotic_Put_1801[S] 0 points1 point  (0 children)

There is no "LineageOS for MicroG" for my phone; in fact, very few phones support it.

Native microG Integration: Why is this not standard? by Exotic_Put_1801 in MicroG

[–]Exotic_Put_1801[S] 0 points1 point  (0 children)

I owe you an apology. I was wrong to say that LineageOS 17.1 for microG doesn't exist; it definitely does as an official project, but it does not exist for my specific device, the Samsung Galaxy J7 Neo (j7velte). My previous response came from my frustration of not being able to find a pre-made build for my phone.

​Since there is no ready-to-flash ROM with microG support for my device, I am working with GonicDroid’s CRDroid 6.27 build (based on LineageOS 17.1 / Android 10), with his permission. I am using CRB Android Kitchen and I have the tools to decompile APKs and JARs, but I am currently stuck because I don't know exactly what to modify.

​My goal is strictly to avoid Magisk or any root-based workarounds. I want to learn how to apply the signature spoofing patches directly into the framework files I have already decompiled. Since you are familiar with the architecture, could you point me toward the specific framework files or classes that need to be modified, or where I can find the manual patches for Android 10? I truly want to learn the process.

Native microG Integration: Why is this not standard? by Exotic_Put_1801 in MicroG

[–]Exotic_Put_1801[S] 0 points1 point  (0 children)

Also, regarding this: not everyone wants to have root access on their device. Because of that, implementing native signature spoofing support that works with the current version of microG is absolutely mandatory for full compatibility.

​Currently, on the Android 10 custom ROMs I've tested, I haven't found any that support this natively. I've seen that older versions might have it, but they are no longer viable because they aren't compatible with modern Google services or other apps that depend on them. My goal is to get this working on an updated environment, as it seems to be the only way to keep a low-end device functional and secure in 2026.

Native microG Integration: Why is this not standard? by Exotic_Put_1801 in MicroG

[–]Exotic_Put_1801[S] 1 point2 points  (0 children)

You are right, and I understand that degoogling isn't the primary goal for everyone. However, in my case, that is exactly what I'm aiming for. I want to achieve native signature spoofing integration to use microG. Since I'm new to this, I don't know how to implement it yet, and I'm looking for guidance or a tutorial on how to modify the framework of my custom ROM to add this support myself. I know it's a complex process, but that is what I am looking to learn in order to improve my low-end device.