Install process crash when install microg update

[DeepBlueBubble]

When install new version from Magisk, or manually install new version of GMS core App. All rhe install process, the Magisk, the package installation, will crash. This happened all my 3 devices (A12L-A13) with Microg installed, across three different microg revived installer versions (because.I am only using microg 3-4 versions ago).

[DeepBlueBubble]

But what curiosity is that, the version number of Gms core apperas to be update-to-date, after even the installation crashes. But this problem also result the real store sometimes can't be installed, but the fake one instead.

[nift4]

what installer version? this was supposed to be fixed a long time ago

[diamant711]

I've the same issue with the latest version

[nift4]

please provide logs

[DeepBlueBubble]

You mean the log in Magisk after install crash?

[nift4]

android logcat should be enough i think

[imol-ai]

The update crashed while in the "installing microg gms core". I included the necessary logs.

02-05 13:44:38.959 W/PackageManager( 1515): Package com.google.android.gms declares library com.google.android.gms that already exists; skipping 02-05 13:44:38.961 W/ServiceWatcher( 1515): [network] 10274/com.google.android.gms/org.microg.nlp.location.v3.LocationService@3 died 02-05 13:44:38.961 W/ServiceWatcher( 1515): [GeocoderProxy] 10274/com.google.android.gms/org.microg.nlp.geocode.v1.GeocodeService@2 died 02-05 13:44:39.063 W/ziparchive( 1515): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:39.986 W/ziparchive( 1515): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:40.011 W/dex2oat64( 3168): /apex/com.android.art/bin/dex2oat64 --zip-fd=8 --zip-location=base.apk --oat-fd=9 --oat-location=/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/oat/arm64/base.odex --input-vdex-fd=-1 --output-vdex-fd=10 --app-image-fd=13 --image-format=lz4 --profile-file-fd=12 --swap-fd=11 --classpath-dir=/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA== --class-loader-context=PCL[]{PCL[/system/framework/android.test.base.jar]#PCL[/system/framework/com.android.location.provider.jar]#PCL[/system/framework/org.apache.http.legacy.jar]} --compact-dex-level=none --instruction-set=arm64 --instruction-set-features=default --instruction-set-variant=kryo785 --compiler-filter=speed-profile --compilation-reason=install --max-image-block-size=524288 --resolve-startup-const-strings=true --generate-mini-debug-info --runtime-arg -Xtarget-sdk-version:29 --runtime-arg -Xhidden-api-policy:enabled --runtime-arg -Xms64m --runtime-arg -Xmx512m --inline-max-code-units=0 02-05 13:44:40.192 E/ActivityManager( 1515): Failure starting process com.google.android.gms 02-05 13:44:40.192 E/ActivityManager( 1515): java.lang.SecurityException: Package com.google.android.gms is currently frozen! 02-05 13:44:40.195 W/ServiceWatcher( 1515): [GeocoderProxy] 10274/com.google.android.gms/org.microg.nlp.geocode.v1.GeocodeService@2 died 02-05 13:44:40.195 W/ServiceWatcher( 1515): [network] 10274/com.google.android.gms/org.microg.nlp.location.v3.LocationService@3 died 02-05 13:44:40.214 W/ziparchive( 3170): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:40.214 W/ziparchive( 3170): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:40.199 W/ContentProviderHelper( 1515): Unable to launch app com.google.android.gms/10274 for provider com.google.android.gms.chimera: process is bad 02-05 13:44:40.504 E/ActivityManager( 1515): Failure starting process com.google.android.gms 02-05 13:44:40.504 E/ActivityManager( 1515): java.lang.SecurityException: Package com.google.android.gms is currently frozen! 02-05 13:44:40.510 W/ContentProviderHelper( 1515): Unable to launch app com.google.android.gms/10274 for provider com.google.android.gms.chimera: process is bad 02-05 13:44:40.565 W/ziparchive( 3321): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:40.565 W/ziparchive( 3321): Unable to open '/data/app/~~2Dwb4l3fuZWhruqDMwIAew==/com.google.android.gms-NNWfprr4iRlj4pUfo-bQQA==/base.dm': No such file or directory 02-05 13:44:41.287 W/ServiceWatcher( 1515): [GeocoderProxy] 10274/com.google.android.gms/org.microg.nlp.geocode.v1.GeocodeService@2 died 02-05 13:44:41.287 W/ServiceWatcher( 1515): [network] 10274/com.google.android.gms/org.microg.nlp.location.v3.LocationService@3 died 02-05 13:44:41.308 W/BroadcastQueue( 1515): Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package: flg=0x4000010 (has extras) } to com.google.android.gms/org.microg.gms.gcm.UnregisterReceiver 02-05 13:44:41.368 E/gle.android.gms(31960): Not starting debugger since process cannot load the jdwp agent. 02-05 13:44:41.483 E/.gms:persistent(31961): Not starting debugger since process cannot load the jdwp agent. 02-05 13:44:42.100 W/GmsGcmMcsSvc(31961): Unknown message: IqStanza{type=SET, id=, extension=Extension{id=12, data_=[size=0]}}

[nift4]

the logs don't contain any relevant information

[nift4]

What is the first version of the module where this can be observed? What device(s)? Where did you download the module?

[DeepBlueBubble]

This issue occurs to me since 2.6.3, download from Github&Magisk. I noticed that, when trying to install gms core, magisk simply crashes. And after reboot, it shows the module is up-to-date. All three devices running at unoffical AOSP-based system: Xperia 1, K50i, Samsung Tab A7

[nift4]

2.6.2 work fine?

[nift4]

are you using official Magisk app to install? or FoxMMM?

[DeepBlueBubble]

Yes, offcial Magisk 25. I didn't try the 2.6.2 so I really don't know.

I want to add another situation here. So, this happened on a Gapps build system, but degoogle afterward. At first, the Fake Gapps wasn't enable properly (like, I didn't reboot or sth.). Then, I tried to install this module (2.6.3 or after), and no surprise it failed because of signature issue. However, the Microg app somehow managed to install itself (and with no correct signature in self-check obviously). And, the second time, I properly enabled the Fake Gapps, and then tried install this module again (while the previous Microg installed). The Magisk crashed, and the module refused to install. So I have to uninstall the previous Microg app, and reboot, and install the module again to make it work.

[nift4]

@FadeDave77 @diamant711 was your ROM originally Gapps build? Is it AOSP or OEM ROM? what Android version? Did you use this module before/did you experience this issue before?

[imol-ai]

the logs don't contain any relevant information

Oh, I am very sorry then, thought the dex2oat or the missing base.dm were the troublemakers

What is the first version of the module where this can be observed? What device(s)? Where did you download the module?

Before the newest version I never had this problem. The device is Poco F3 (alioth), and I have both downloaded the module in FoxMMM and from your github, and installed in magisk.

@FadeDave77 @diamant711 was your ROM originally Gapps build? Is it AOSP or OEM ROM? what Android version? Did you use this module before/did you experience this issue before?

I am using CrDroid, vanilla by default. It is aosp, android 13. I have been using your module since android 11, like 2 years ago, never had this issue before.

2.6.2 work fine?

Now all versions I try to install, crash On the Installing GmsCore step. 3.1.0, and even 2.6.2.

[nift4]

2.6.1?

[imol-ai]

Also crashes.

[diamant711]

@FadeDave77 @diamant711 was your ROM originally Gapps build? Is it AOSP or OEM ROM? what Android version? Did you use this module before/did you experience this issue before?

Hi! I use Lineage OS 20.0. With no originally gapps. It is not the original OS (xiaomi redmi 5 is the smartphone). I've never faced this issue before!

[nift4]

last one i'm gonna ask - 2.1.0?

[imol-ai]

This should be all the available logs while installing latest - I didn't filter but redacted values i think are sensitive. 02-07 15:19:51.241 I/MediaProvider( 4022): Deleted 1 0 0 0 0 0 0 items on external_primary due to io.github.muntashirakon.AppManager 02-07 15:19:51.248 W/MediaProvider( 4022): isAppCloneUserPair failed. Users: 0 and 0 02-07 15:19:51.248 W/MediaProvider( 4022): isAppCloneUserPair for user 0: false 02-07 15:19:51.251 V/MediaProvider( 4022): Inserted id:1000003151 less than next row id backup:1000004000. 02-07 15:19:51.347 D/GmsGcmMcsSvc(10576): Sending login request... 02-07 15:19:51.348 D/CompatibilityChangeReporter( 1515): Compat change id reported: 171306433; UID 10274; state: DISABLED 02-07 15:19:51.348 D/GmsGcmMcsSvc(10576): Scheduling heartbeat in 958 seconds... 02-07 15:19:51.351 D/GmsGcmMcsSvc(10576): Connect initiated, reason: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) } 02-07 15:19:51.381 D/GmsGcmMcsOutput(10576): Outgoing message: LoginRequest{id=android-33, domain=mcs.android.com, user=REDACTED, resource=REDACTED, auth_token=REDACTED, device_id=android-REDACTED, setting=[Setting{name=new_vc, value_=1}], adaptive_heartbeat=false, use_rmq2=true, auth_service=ANDROID_ID, network_type=1} 02-07 15:19:51.381 D/GmsGcmMcsOutput(10576): Write MCS version code: 41 02-07 15:19:51.412 D/vendor.qti.vibrator.xiaomi_kona( 1074): Vibrator perform effect 21 02-07 15:19:51.413 D/vendor.qti.vibrator.xiaomi_kona( 1074): Vibrator perform effect 2 02-07 15:19:51.413 D/vendor.qti.vibrator.xiaomi_kona( 1074): Starting perform on another thread 02-07 15:19:51.433 D/vendor.qti.vibrator.xiaomi_kona( 1074): Notifying perform complete 02-07 15:19:51.434 D/vendor.qti.vibrator.xiaomi_kona( 1074): QTI Vibrator off 02-07 15:19:51.540 D/GmsGcmMcsInput(10576): Reading from MCS version: 41 02-07 15:19:51.542 D/GmsGcmMcsInput(10576): Incoming message: LoginResponse{id=android-33, jid=user@firebase.com/notifications, last_stream_id_received=1, server_timestamp=1675779591565} 02-07 15:19:51.550 D/GmsGcmMcsSvc(10576): Logged in 02-07 15:19:51.556 D/GmsGcmMcsInput(10576): Incoming message: IqStanza{type=SET, id=, extension=Extension{id=12, data_=[size=0]}} 02-07 15:19:51.556 W/GmsGcmMcsSvc(10576): Unknown message: IqStanza{type=SET, id=, extension=Extension{id=12, data_=[size=0]}} 02-07 15:19:51.692 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:51.791 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:51.835 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1 02-07 15:19:51.968 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:52.015 D/vendor.qti.vibrator.xiaomi_kona( 1074): Vibrator perform effect 0 02-07 15:19:52.015 D/vendor.qti.vibrator.xiaomi_kona( 1074): Starting perform on another thread 02-07 15:19:52.018 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:52.029 W/Choreographer( 3165): Frame time is 0.137447 ms in the future! Check that graphics HAL is generating vsync timestamps using the correct timebase. 02-07 15:19:52.035 D/vendor.qti.vibrator.xiaomi_kona( 1074): Notifying perform complete 02-07 15:19:52.036 D/vendor.qti.vibrator.xiaomi_kona( 1074): QTI Vibrator off 02-07 15:19:52.362 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:52.373 I/input_focus( 1515): [Focus leaving 7037e31 com.android.launcher3/com.android.launcher3.uioverrides.QuickstepLauncher (server),reason=Waiting for window because NOT_FOCUSABLE] 02-07 15:19:52.394 E/OpenGLRenderer( 9143): Unable to match the desired swap behavior. 02-07 15:19:52.398 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:52.447 I/input_focus( 1515): [Focus entering 7b6d2b io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.logcat.LogViewerActivity (server),reason=Window became focusable. Previous reason: NOT_VISIBLE] 02-07 15:19:52.478 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1 02-07 15:19:52.542 W/InputManager-JNI( 1515): Input channel object 'd1571a3 SnapshotStartingWindow for taskId=2504 (client)' was disposed without first being removed with the input manager! 02-07 15:19:52.835 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1 02-07 15:19:53.335 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1 02-07 15:19:53.388 I/SDM ( 1063): HWDeviceDRM::UpdateMixerAttributes: Mixer WxH 1080x2400-0 for Peripheral 02-07 15:19:53.388 I/SDM ( 1063): HWCDisplay::SubmitDisplayConfig: Active configuration changed to: 0 02-07 15:19:53.426 I/SDM ( 1063): HWDeviceDRM::UpdateMixerAttributes: Mixer WxH 1080x2400-0 for Peripheral 02-07 15:19:53.426 I/SDM ( 1063): HWCDisplay::SubmitDisplayConfig: Active configuration changed to: 1 02-07 15:19:53.836 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1 02-07 15:19:54.336 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1 02-07 15:19:54.730 I/input_interaction( 1515): Interaction with: 7b6d2b io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.logcat.LogViewerActivity (server), [Gesture Monitor] swipe-up (server), [Gesture Monitor] edge-swipe (server), PointerEventDispatcher0 (server), 02-07 15:19:54.733 W/libperfmgr( 5486): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 30, fd: -1

[imol-ai]

last one i'm gonna ask - 2.1.0?

That one - surprisingly - does not crash!

[nift4]

sigh.. please flash back to the lastest one. then reboot and try pm install /data/adb/modules/microg_installer/system/priv-app/GmsCore/GmsCore.apk inside root terminal emulator

[imol-ai]

Okay, that works. And also I thought that this was the reason apps couldn't register for fcm messaging - but I just had the device registration turned off. So all good now.

[nift4]

What's your "mount namespace" setting in Magisk settings?

[imol-ai]

Inherit

[nift4]

Okay, that works. And also I thought that this was the reason apps couldn't register for fcm messaging - but I just had the device registration turned off. So all good now.

Please try again with pm install -g --dont-kill /data/adb/modules/microg_installer/system/priv-app/GmsCore/GmsCore.apk

[imol-ai]

Please try again with pm install -g --dont-kill /data/adb/modules/microg_installer/system/priv-app/GmsCore/GmsCore.apk

That works as well.

[nift4]

Does flashing 3.2 work now?

[imol-ai]

After I ran that command?

[nift4]

yes

[imol-ai]

It still crashes.

[yennor]

Same problem here. Android 13 (Cr droid 9.1). Installed over actual magisk.

Last screen output before it crashes attached. Also logcat. But I can-t see anything interesting. maybe you do...` [logcat.txt](https://github.com/nift4/microg_installer_revived/files/10697396/logcat.txt)

[slock83]

Same here for me, android 13, crdroid 9.2

After digging around a bit, it seems that the issue is with the play store install part of the script. Namely, it appears that the folder /data/adb should not be used anymore, and installing manually raises an error, even when doing a manual cp.

It now asks to use the folder /data/local/tmp apparently. I don't know if that's the issue though...

[nift4]

Some other users reported /data/adb with Termux to be fine - hence why that was off my agenda. And microG is in /data/adb too - but whatever, I will make an test build with changed install logic soon

[slock83]

Just tested parching it myself, and that didn't do the trick alone, but commenting the pm install line for GMSCore stopped the crashing. Weird, because launching it manually doesn't seem to cause issues ...

[SageSystems]

I also have this issue, also on crdroid 9.3 on android 13. also after install microg fakestore constantly crashes making it unusable

[nift4]

Is there anyone experiencing this but not using crDroid? (I know someone said Lineage, but I had multiple people saying "Lineage" when they actually run crDroid).

[DeepBlueBubble]

I experienced this on Kaleidoscope and Cherish OS, EvoX

[nift4]

Eh this gives me a headache - I will experiment with session-based installers soon

[DeepBlueBubble]

🫡 Good luck

[imol-ai]

I switched to ArrowOS not so long ago, and I noticed that it worked fine on it. (still on alioth) Hope that may help.

[nift4]

ROM bugs caused by blind mass cherry-picking have always been a thing, so it might just be some faulty command - I think I'll flash a GSI sooner or later to reproduce this issue

[SageSystems]

I switched to ArrowOS not so long ago, and I noticed that it worked fine on it. (still on alioth) Hope that may help.

I am also on alioth and there's several crdroid specific bugs in the video API that break newpipe so it's not a big surprise

[nift4]

Hello guys, please test this version https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived.zip

[SageSystems]

Hello guys, please test this version https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived.zip

nope still crashing

[nift4]

What is the last message it prints?

[nift4]

https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived-t2.zip

how about this

[urgali]

Crashing at

Installing microg gmscore Success!

[urgali]

How can i get more useful logs? Is adb logcat enough?

[nift4]

please try https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived-t3.zip

yes, adb logcat is the best you can get