F-Droid Version 1.0.35 Will Not Install

[landry314]

F-Droid Version 1.0.35 Will Not Install

[rababerladuseladim]

And for LineageOS (no need to uninstall Etar):

1. adb shell pm uninstall --user 0 org.lineageos.etar
2. adb shell pm install-existing org.lineageos.etar
3. update Etar

[criztovyl]

I have reported a bug on LinageOS side: https://gitlab.com/LineageOS/issues/android/-/issues/6224

[criztovyl]

Cannot update either, but for me it says "error -112", not "unknown error".

[luk1337]

This change addresses the issue, but only for new installations or upgrades from builds that didn't have this issue. I have pretty much no interest in tracking down why package manager doesn't free no longer used permission. Good luck~

[Iey4iej3]

or the issue isn't solved just by uninstalling/re-installing Etar.

In my experience, you need to uninstall both the Etar that you installed and the Etar in Lineage OS. I used AppManager (root required) to uninstall the later (and again, disabling is insufficient — you have to uninstall it), but according to https://android.stackexchange.com/questions/179575/ you can also uninstall it without root, cf. https://android.stackexchange.com/questions/215313/

I suspect that the key point is to clean some permission in /data partition, and it is enough to remove both apps.

I guess that if you do not need the Lineage OS Etar, upgrading Lineage OS is not necessary.

[jspricke]

For me this worked on CalyxOS 15.0.1:

• uninstall Etar
• adb shell pm uninstall --user 0 org.calyxos.etar
• adb shell pm install-existing org.calyxos.etar
• install Etar

[jspricke]

@pjmkrpg I don't know, please ask the e Foundation, it is their bug.

[vitor895]

I tried to upgrade to 1.0.35 from F-Droid but It not worked, then I downgraded to 1.0.34

[criztovyl]

Ok, this seems to related to the core-ctx update which seems to be adding an ${applicationId}.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION to all manifests now (https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:core/core/src/main/AndroidManifest.xml;l=19;drc=cb9edef10187fe5e0fc55a49db6b84bbecf4ebf2), but as discussed at #1297 (comment) this seems to be an issue with the linage-os embedded Etar not changing all IDs.

[fvkras]

думаю что эта ошибка возникает на lineage OS из-за стокового пакета org.lineageos.etar

[je-vv]

To me it's that 112 error as well, not the unknown one.

[ezfox]

I get the same error -112 on CalyxOS.

[erebion]

I get the same error -112 on CalyxOS.

Same here, seems to affect many people and not just a few.

[Gitsaibot]

As far as I can see we can't fix the problem on our side. Please contact the CalyxOS and LineageOS teams. And please use the rating function.

[hummingbaer]

Same Problem at my device on lineageos 20.
Same deinstallation/reinstallation results.
Even tried to uncheck all permissions for lineage's standard calendar - doesn't help either.

[landry314]

i will send this thread to someone in los team

[criztovyl]

I have been in touch with LOS team, this seems to be an issue with an aapt flag (this one); I volunteered to have a look at it. I still have to update the LOS bug in regards to that.

[magicvince]

Same error with LOS microG (20-20230910-lake)
uninstall etar, but impossible to install 1.0.35

I had downgraded to 1.0.34 to still have a calendar

[Iey4iej3]

I succeeded to install v1.0.36. I don't know what precisely I did to do that, but here is a possibility:

1. Upgrade to the latest Lineage OS;
2. Uninstall org.lineageos.etar — This does not seem to be possible in Android via UI, but I use https://f-droid.org/en/packages/io.github.muntashirakon.AppManager/ to uninstall it — disabling is not enough;
3. Uninstall Etar and re-install v1.0.36.

[landry314]

I just started using the built in etar calendar which is being updated by LOS and works fine.

[je-vv]

I received a new update from LOS for MicroG (I don't use plain LOS), and unfortunately whether the recently released update for my moto didn't come new enough, or the issue isn't solved just by uninstalling/re-installing Etar. I read from some other issue, perhaps a LOS one, that the patch provided as a solution was only meant to work on totally new LOS installations, from scratch, no on LOS upgrades. See comment https://gitlab.com/LineageOS/issues/android/-/issues/6224#note_1587585809. So, I'm not sure if the comment is misleading, or if it's right and the patch applied on LOS won't really address the issue, of if it's just a matter of time to get the right LOS upgrade through LOS for MicroG on my case:

Seems a fix was merged in lineage build 20.0-20230927 however as stated by luk1337 (author of the fix) it does not resolve the issue for devices that already ran into this issue, only new installs. Apparently package manager does not remove unused permission.

I tested by removing cache and data of both etar and the inactivated calendar app before updating to 20.0-20230927 and as suspected the issue remains.

And yes, perhaps using the LOS provided calendar gets rid of the issue, if you don't care about using the LOS version of Etar... I don't know when LOS decided to move to Etar as its default calendar app, but I believe it's not up to date with the F-Droid provided Etar, and issues on the LOS version may be already fixed on the F-Droic version...

[landry314]

1.0.36 was merged in late september into LOS... weekly sept 29 build has it.

https://review.lineageos.org/366904

[anaktivix]

Hi, yes I do get that error , the “"Failed to install due to an unknown error."
Reading the other comments, what should I/we do? Uninstall it? I am wary of installing a previous version.

[landry314]

read above for explanations of installation

[criztovyl]

but according to https://android.stackexchange.com/questions/179575/ you can also uninstall it without root, cf. https://android.stackexchange.com/questions/215313/

I can confirm this, it worked for me.

[landry314]

well, the LOS version does not allow me to change the time zone and the fdroid version does... what is that about? had to switch to fdroid version.

[landry314]

The LOS Calendar which is a version of Etar was fixed to allow time zone changes and time zone updateed code was pushed to the Etar version in general, fyi. This has drifted from the original point of the thread but the update might interest people here and encourage them to use the built in Etar which wouldnt have these install issues.

https://review.lineageos.org/c/LineageOS/android_packages_apps_Etar/+/370189

[pjmkrpg]

I get the following message while trying to install Etar on e-foundation OS 1.15 :
$ adb install /tmp/ws.xsoh.etar_36.apk
Performing Streamed Install adb: failed to install /tmp/ws.xsoh.etar_36.apk: Failure [INSTALL_FAILED_CONFLICTING_PROVIDER: Scanning Failed.: Can't install because provider name ws.xsoh.etar.provider (in package ws.xsoh.etar) is already used by foundation.e.calendar]
But neither foundation.e.calendar nor org.lineageos.etar is installed on the phone.

[jspricke]

@pjmkrpg same procedure as above just for e:

1. adb shell pm uninstall --user 0 foundation.e.calendar
2. adb shell pm install-existing foundation.e.calendar
3. update Etar

[pjmkrpg]

@jspricke thanks but it does not work: 1. fails (not installed), 2. succeeds, 3. same error as before. Should I clear something before reinstalling?

[pjmkrpg]

@jspricke Ok, it seems that now Etar is built inside the OS with another name. So I should probably not try to install the genuine Etar from F-droid or apk file.

[magicvince]

Ok, I understand Etar is the new lineageOS (microG) default calendar and there's a conflict with the "f-droid Etar version".
I uninstall Etar from f-droid and use the lineageOS calendar.

It's seems to be ok, but I have no information for the etar version in "information about", only a copyright "Le projet Etar parties (c) The Android Open Source Project"