I was using the app "Fossify Calendar "(formely “Simple Calendar”) since long time. So when I install /e/os, I install it, but then I receive double notification from Etar and Fossify.
So I went to the settings of Etar and uncheck “synchronize calendar” and “show calendar” for each of my calemdars and remove the notifications.
But after some minutes, etar re-add the calendar in addition to the deleted ones, so now i have the double number of calendars that I should have and I don’t know how to get rid of this problem, it is really anoying when you want to add an event to a calendar and the list of calendar is double size without knowing the onea which are synchronized and the one which are not.
An easy solution would be to delete this etar app, but I didn’t find a way to do it. I feel a bit forced to use an app that I don’t want to use. Does anybody have an idea how I could solve this ?
The superfluous calendar are superfluous only in etar, not in DAVx5 and not Fossify.
In etar i don’t understand how i can disable them, they re-appear just after in double :
I did it but it doesn’t change anything, i don’t know exacly how it works, but it seems that calendar are - kind of - managed by android and that the parameters and data of the app are more about presentation of the calendar, not the subscription…
Hmm… OK… Sounds like a question for support then. In the unofficial ROM I’m using, it’s not a problem.
One thing you might try is to use Android Debug Bridge (ADB) to disable the app for the current user (i.e. you). It’s easy to do, and doesn’t require root. I can help you with the commands, if you want to try. No guarantee it will work for Etar, but it’s a useful skill to have.
I would be happy to try. I never did it but I’d like to.
I am under linux, if you want to explain, it would be nice from you, but i think i can also find documentation how to do. (Anyway, i have no computer to try this until tomorrow).
What are the advantages to use the unofficial ROM ? And can you get the updates with it ?
An unofficial ROM is generally used when an official one is not available. (And I’m currently on iodéOS, not /e/OS.) Over-the-air (OTA) updates aren’t available to unofficial ROMs, so every system update requires manual flashing (without losing personal data and installed apps, if the update is for the same Android version).
So, the basic steps are:
Enable Developer Options by tapping 7 times on the “Build,” found at Settings > About phone > Build.
In Settings > System > Developer Options, enable “USB Debugging.”
Install ADB on your computer (either from your repository or with the command sudo apt install adb).
Connect a data cable to your computer and your phone.
Open the Terminal on your computer.
Type the command adb devices to confirm that your phone is seen. (Allow debugging in the pop-up that appears on your phone, too.)
Type adb shell to enter the file system of the phone.
Type pm list packages -e | grep etar, to list enabled packages containing the name “etar” or, if not found, grep calendar, grep agenda, etc.
If still not found, pm list packages -e to see all enabled packages; then look for the app name.
Then pm disable com.android.xxxx, (or similar) where “xxxx” is the package name you want to disable.
To see a list of disabled packages, the command is pm list packages -d.
To explore the file system: ls
Then cd at will, as you would on a Linux system.
Other commands that may be of interest can be found with adb --help.
255|heroltexx:/ $ pm disable foundation.e.calendar
Exception occurred while executing 'disable':
java.lang.SecurityException: Shell cannot change component state for foundation.e.calendar/null to 2
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:24283)
at com.android.server.pm.PackageManagerService.setApplicationEnabledSetting(PackageManagerService.java:24079)
at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:2194)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:240)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:24948)
at android.os.Binder.shellCommand(Binder.java:950)
at android.os.Binder.onTransact(Binder.java:834)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4818)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:8937)
at android.os.Binder.execTransactInternal(Binder.java:1184)
at android.os.Binder.execTransact(Binder.java:1143)
maybe this app is considered as an important one and cannot be disabled.
But, I solved the problem ! I delete the DAVx account and re-add it then the multiple agenda problem disapear !
Then I remove all authorizations (especially access to the agenda) of the app foundation.e.calendar, then I hope I will not receive more notification in double.
So at the end the problem is solved, but I still have the feeling that it is not easy to use an alternative app to the one chosen by /e/OS because it is not possible to remove it.
