microg
Can't install latest versions after 0.2.27.223616
Describe the bug Can't get latest release 0.3.4.240913 to install - error "Zugriffsfehler!" (means "access error"). Latest on I was able to install was 0.2.27.223616.
To Reproduce Steps to reproduce the behavior: Just try to install on my OUYA console, Android 4.1.2
Expected behavior Install as previous version.
System Android Version: 4.1.2 Custom ROM: none
Additional context none
official microG has dropped support for old Android versions (< 4.4).
I have the intention of keeping the support for them in my fork but the new version isn't yet ready. Currently I have only the version 0.3.0 ready: https://github.com/micro5k/microg-unofficial-installer/blob/HEAD/zip-content/origin/priv-app/GmsCore-ale5000.apk https://github.com/micro5k/microg-unofficial-installer/blob/HEAD/zip-content/origin/priv-app/FakeStore-ale5000.apk
You can see the info here: https://github.com/micro5k/microg-unofficial-installer/blob/HEAD/zip-content/CONTENTS.rst
@ale5000-git I can't get the old 0.2.27 version of my OUYA. Titanium Backup deletes it, but after a restart it is there again. So I am not able to install your fork due to another signature.
Delete the microG files in the /system partition (if you have added them there).
Then uninstall the remains with:
adb uninstall com.android.vending
adb uninstall com.google.android.gms
Delete the microG files in the /system partition (if you have added them there).
Then uninstall the remains with:
adb uninstall com.android.vending adb uninstall com.google.android.gms
Thanks that did the job. Your fork is installed now... :)
Logging into my Google acc never worked with 0.2.27 - also doesn't with your fork. Error 400. Is this known or some misconfiguration on my side? Also several games have a rotating loading animation now... pressing B on the controller closes and loads the game.
There have been many improvements recently in the microG code, when I have time I will prepare the latest version and many things will work better.
Until the latest version is ready, it isn't worth spending time debugging these issues as they may have been already fixed in the latest code.