microg
microG Services v0.3.10 isn't available in the F-Droid repo (except 1 mirror)
@mar-v-in
The latest microG Services (v0.3.10) isn't available in the F-Droid repo.
This: https://microg.org/fdroid/repo/com.google.android.gms-250932020.apk
Maybe it got blocked because it is over 100MB?
NOTE: Git (on GitHub) reject files over 100 MB and Git Lfs is pretty limited if you don't pay.
This is also a good time to start talking about stripping down libraries and optimizing; microG is really too big now.
Huh, I got the update from F-Droid with the correct version, 0.3.8 and 0.3.9 was not recommended by F-Droid but 0.3.10 was automatically updated. Maybe it's the version number F-Droid is the issue and people need to update that the app, I use the MicroG Repo as source. LOS+MicorG doesn't update MicroG when you flash the OTA.
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 to download it.
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
This is also a good time to start talking about stripping down libraries and optimizing; microG is really too big now.
The APK blew up not too long ago from ~43MB to 99MB with v0.3.6, which added face detection features based on openCV. OpenCV is - by far - the largest compiled library inside the APK. That's not an issue per se, but because the APK is universal, shipping four ABIs (openCV is largest for x86_x64).
Perhaps the easiest way to trim down the APK size is to split it by ABI.
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 be a solution.
I can see version 0.3.10 in the F-Droid repo just fine, and also successfully installed it. (However, I had to manually do that; the version is listed but it is not "suggested".) Does this problem somehow only affect a subset of users?
EDIT:
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 to download it.
Did you mean "it is impossible to download"? Otherwise the two sentences don't seem to add up.
Upon closer inspection, the file does not exist in the main repository but does exist in the mirror repository (using Git LFS).
So I guess I got lucky and downloaded the file before the bandwidth is exhausted for the day, or so?
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 attempts F-Droid may be able to get it.
So I guess I got lucky and downloaded the file before the bandwidth is exhausted for the day, or so?
The bandwidth is per-month, so after it is exhausted, it won't be available until the month is passed.
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 be a solution.
@ale5000-git Didnt he mean split as in seperate apk downloads for armv8, x86, armabi and so on instead of one split apks? Or did I get it wrong? Or would that not be possible either?
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 be a solution.
@ale5000-git Didnt he mean split as in seperate apk downloads for armv8, x86, armabi and so on instead of one split apks? Or did I get it wrong? Or would that not be possible either?
Maybe yes, but that would be another additional complication for both installers and ROMs that bundle officially signed microG.