Use bundled microg if system microg is outdated #51

Closed
opened 7 months ago by vanitasvitae · 11 comments

Hey,
I've updated CCTG to version 1.9.1.5, but now the app conplains that my microg is too old (I have 0.2.13.something installed as part of my ROM, therefore I have to wait for the ROM maintainer to upgrade it).
Because of this, CCTG is no longer usable for me at the moment.

Wouldn't it be a good idea to fall back to the bundled microg if the installed system microg is too old?

Hey, I've updated CCTG to version 1.9.1.5, but now the app conplains that my microg is too old (I have 0.2.13.something installed as part of my ROM, therefore I have to wait for the ROM maintainer to upgrade it). Because of this, CCTG is no longer usable for me at the moment. Wouldn't it be a good idea to fall back to the bundled microg if the installed system microg is too old?
Owner

Wouldn't it be a good idea to fall back to the bundled microg if the installed system microg is too old?

It's not a great idea to do that automatically I think as this would split the exposure db across 2 places in case there's an update to the built-in microg.

What you can do to make it work is disable the built-in microg installation, this way it won't be used. The above still applies of course if you ever enable it again.

> Wouldn't it be a good idea to fall back to the bundled microg if the installed system microg is too old? It's not a great idea to do that automatically I think as this would split the exposure db across 2 places in case there's an update to the built-in microg. What you can do to make it work is disable the built-in microg installation, this way it won't be used. The above still applies of course if you ever enable it again.

I've got the same problem: I'm using /e/ OS (a Lineage fork, Android 9) with MicroG included. Unfortunately, for some reason I cannot update MicroG by installing the newest .apk. I think this is because MicroG is a system app or something like that (it is preinstalled). And since there was no system update yet providing the newest MicroG version which would include the required exposure notification, I had no option to use the original Corona Warn App – until CCTG was published. I'm using CCTG since its first day and everything worked very well – until today.

Today, I updated CCTG to the latest version but it just showed me a popup saying I'd need to update MicroG. But since I can't update MicroG myself, I'm unable to use any Corona contact tracing app.

Is there anything I could do myself in order to make CCTG work again on my device – without having to flash anything or root the device?

I've got the same problem: I'm using /e/ OS (a Lineage fork, Android 9) with MicroG included. Unfortunately, for some reason I cannot update MicroG by installing the newest .apk. I think this is because MicroG is a system app or something like that (it is preinstalled). And since there was no system update yet providing the newest MicroG version which would include the required exposure notification, I had no option to use the original Corona Warn App – until CCTG was published. I'm using CCTG since its first day and everything worked very well – until today. Today, I updated CCTG to the latest version but it just showed me a popup saying I'd need to update MicroG. But since I can't update MicroG myself, I'm unable to use any Corona contact tracing app. Is there anything I could do myself in order to make CCTG work again on my device – without having to flash anything or root the device?

Is there anything I could do myself in order to make CCTG work again on my device – without having to flash anything or root the device?

You could downgrade to 1.7.x and it should work again. I did the same (just from 1.9.1.2) and everything seems to be back to as it was before now.

@bubu Is downgrading save, though, don't want to unintentionally brake someone else's db or anything.

>Is there anything I could do myself in order to make CCTG work again on my device – without having to flash anything or root the device? You could [downgrade](https://www.xda-developers.com/downgrade-an-app-android-no-root/) to 1.7.x and it should work again. I did the same (just from 1.9.1.2) and everything seems to be back to as it was before now. @bubu Is downgrading save, though, don't want to unintentionally brake someone else's db or anything.
Poster

Downgrading is probably not an option as recent Android versions disallow downgrading installed apps without removing the prior version first (and thereby deleting the database).

Downgrading is probably not an option as recent Android versions disallow downgrading installed apps without removing the prior version first (and thereby deleting the database).
Owner

removing the prior version first (and thereby deleting the database)

If external microg is used, which is the case here, it would actually not be an issue (though the app would claim it had been active for 0 days again), as microg would still have the data and process it correctly independent of what the app thinks.

> removing the prior version first (and thereby deleting the database) If external microg is used, which is the case here, it would actually not be an issue (though the app would claim it had been active for 0 days again), as microg would still have the data and process it correctly independent of what the app thinks.
Poster

Ah that would be nice then :)

Ah that would be nice then :)

Just installing the older version (which I had previously installed) from fdroid wouldn't work, that's right.
I then installed it via adb as explained in the link from my previous post without removing the newer version first. In my case, the app didn't even loose track of how many days it had been active for.

EDIT:
My phone's running on CalyxOS 11 btw..

Just installing the older version (which I had previously installed) from fdroid wouldn't work, that's right. I then installed it via adb as explained in the link from my previous post **without** removing the newer version first. In my case, the app didn't even loose track of how many days it had been active for. EDIT: My phone's running on CalyxOS 11 btw..
Owner

Version 1.9.1.6 will ignore microG without ENF but normal microG < 0.2.15 will still not work with the new version.

If you depend on your ROM to update microG you are encouraged to stay on release 1.7.1 for the time being.

Version 1.9.1.6 will ignore microG without ENF but normal microG < 0.2.15 will still not work with the new version. If you depend on your ROM to update microG you are encouraged to stay on release 1.7.1 for the time being.
Poster

For the sake of completeness:
The method of downgrading applications using adb push ~/Downloads/de.corona.tracing_1070102.apk /sdcard/app.apk && adb shell pm install -r -d /sdcard/app.apk did not work for me. However, the flags -r (retain data) and -d (allow downgrade) are also available in adb, so I was able to downgrade the application using

adb install -r -d ~/Downloads/de.corona.tracing_1070102.apk

without any problems.

For the sake of completeness: The method of downgrading applications using `adb push ~/Downloads/de.corona.tracing_1070102.apk /sdcard/app.apk && adb shell pm install -r -d /sdcard/app.apk` did not work for me. However, the flags `-r` (retain data) and `-d` (allow downgrade) are also available in adb, so I was able to downgrade the application using ``` adb install -r -d ~/Downloads/de.corona.tracing_1070102.apk ``` without any problems.
Bubu added the
upstream-microg
label 7 months ago
Owner

I'll close this issue now.

The original suggestion "use bundled ENF if the system one is too old" would need to be implemented on the microG side. (Still unsure if it's a good idea to do that automatically, I'd tend to 'no' here.)

I'll close this issue now. The original suggestion "use bundled ENF if the system one is too old" would need to be implemented on the microG side. (Still unsure if it's a good idea to do that automatically, I'd tend to 'no' here.)
Bubu closed this issue 7 months ago
Owner

I just realized that this would need to be changed here as well (in the update checker) if microg end up implementing this (maybe with a setting or something)

I just realized that this would need to be changed here as well (in the update checker) if microg end up implementing this (maybe with a setting or something)
Sign in to join this conversation.
No Milestone
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.