ale5000

> Thanks. So for L4M, we will pull the microG components from the github releases page, making decisions about when to pull new versions into our builds. I think the...

> Alright. As such, [@mid-kid](https://github.com/mid-kid) I'd like you to make a new repo that will have the contents of the [`TrickyStoreOSS/module` directory](https://github.com/beakthoven/TrickyStoreOSS/tree/main/module?rgh-link-date=2025-10-08T15%3A10%3A22.000Z) in it (so it follows the other modules'...

> > Why not just using an automated workflow that on a release of the main repo just copy the content of the sub-folder in the "copied Magisk repo"? >...

Hi, I think it should be fixed by #2746 but you should wait that the PR get merged and a new version of microG is released.

> Have you fixed it in your flashable zip version? No, I haven't yet had time to look at this issue.

I will make it more clear, the xml of the repository list the version 0.3.10, but the real apk file doesn't physically exist on the server. So it isn't impossible...

Upon closer inspection, the file does not exist in the main repository but does exist in the mirror repository (using Git LFS).

@mar-v-in Before the bandwidth of Git LFS is exhausted please look here: https://github.com/lineageos4microg/android_vendor_partner_gms/issues/53#issuecomment-3419616470

> Perhaps the easiest way to trim down the APK size is to split it by ABI. Split apk cannot be installed in the system partition, so this will never...

> Does this problem somehow only affect a subset of users? The file is not available in the main repo but is available in one mirror repo so after some...