BUG: Functionless alarms and postponement (no sound, no reminders)

[Moostek]

With the new update 1.0.34 the alarms DO NOT WORK COMPLETELY: no sounds, nothing.

Is there anybody who care and read the reported issues and bugs? Nobody did react on my (and other) reports. As a result, the application is completely useless now.. I really do not understand this precedure "the new update -> nothing works".

p.s.: maybe it works on developer's phone, but i face these bugs, and with the new update, the reminders stopped to work completely. The previous version 1.0.33 suffers with the postponement bug of the events with no sound and visual reminder (occasionaly it works = not reliable).

[jspricke]

Yes we read the issues but we are all voluntary so please contribute if you have a problem. For me the app works on an Pixel 6 with CalyxOS 4.5.0. Also note due to the many different versions of Android there could be a lot of causes not related to Etar

[Gitsaibot]

I think there is a fundamental misunderstanding here. Etar is open source and not a commercial product. Open source is based on collaboration, but it seems that everyone here wants to be a beneficiary and not contribute anything.

When I have time I read the bug reports here. But what should I do with one like this? Apart from complaints, it doesn't contain any relevant info for me. No debug log. No information about the hardware used. Just nothing but complaints.

[Moostek]

Hello, i would like to contribute, but i am just an end user. I am not the developer. I know that open source apps is something completely diffrent from commercial support, of course. So I can contribute only with reporting the issues i face. I tested all issues with restarting etc. before to put it here. As stated, with the new 8.1.23 update reminders stopped to work on my Android 9 (LineageOS 16.0) completely. With previous version it worked, with some bugs (here and here), but it worked. For me it is crucial to have functional reminders, i just need them. So with your new update the Etar caused me a problem. I will have to switch probably to a different calendar. Well, i would like to know if there is some serious development and will to reflect bugs and deal with then (fix them) or if the development is just ocassional and sporadic, because developers do not have time etc. I need relieable product (like FairMail). I tried Etar, i like it (i have sympathy for this app) and i invested quite lot of time to report bugs (and maybe some ideas), but it seems that my effort can not be heard. Maybe i am wrong, i do not know. So, is there anybody who read it all here and try to fix these issues, or the development is really limited from whatever reason(s)? To know this will help me with my decision to keep Etar usage. Thank you.

I know the Android world is really fragmented. But if i face the bug, i report it - there is no way, so the bug can be fixed. I use several open source apps and if i report some problem, the author or dev teams take these issues seriously and try to fix it. They just care, because they want their product solid and widespread. To know that "it works on Pixel" is not relevant information for me, i.e. for my phone, I am sorry. I need the solution that it works on my phone too. Maybe there are some developers they fix the bugs just for their own phones and do not care about the rest. I do not know how about Etar in this matter. Anyway, instead of the debate "what is open source" i sort did expect technical questions leading into the solution of the issues, as it is usual on another open source threads of different cool apps.

Do not understand my words and reports as complaints. If you read them, you see i tried to describe the problem. And as i stated above, i am just an end user, i have no skills to help you technically (with codes etc.), and i guess that people who are not programmes have also "rights" to use apps and report bugs.

Lenovo S60 @ LineageOS 16.0 If there is needed some more info i will try to post it. For example, the Debug log? Where can i find it for Etar?

[jspricke]

the new 8.1.23 update

The latest version is 1.0.34.

Android 9 (LineageOS 16.0)

That is pretty old, maybe something in the Android support library changed. Maybe just use the old version for now.

[Moostek]

Yes, it stopped to work on my phone with the latest version 1.0.34. Right now i downgraded on version 1.0.33. Sound and visual reminders work again in version 1.0.33. So maybe it can be some clue.

I tested the postponement in both old versions (1.0.33 and 1.0.30 too) - the crucial trouble with those two versions for my phone is non-functional postponements, plus this issue with switching the lists.

Android 9 is sort of old, yes. But at the other side Android 9 is still far from the minimum requirements.

Yes, i can go back to the old version, but the reason i report thos bug here is to have the new version with fixed bug(s) ;) Well, yes, it seems that i will have to get back to 1.0.33 version for now, hopefully just for a while;)

[Gitsaibot]

If there is needed some more info i will try to post it. For example, the Debug log?

https://wiki.lineageos.org/how-to/logcat

So maybe it can be some clue.

Between version 1.0.33 and 1.0.34 there are only 4 changes and none has anything to do directly with the notification function. So I wonder why it works with v1.0.33 But who knows what lineageos uses internally for libraries. You can also test the individual debug.apk if you want to know from which commit the notifications no longer work. Under actions there is a matching debug.apk for each commit. e.g.:

https://github.com/Etar-Group/Etar-Calendar/actions/runs/3807595747

[jspricke]

I could imagine https://github.com/Etar-Group/Etar-Calendar/commit/9555bdba889a40df892fe47f51aac6b72aadeb0e

[Gitsaibot]

Yes but why? It corresponds exactly to the implementation recommended by google.

[jspricke]

Maybe some bug in the interaction of the Android support library with the old version. Could be even specific to the phone and probably hard to debug.

[Moostek]

I checked it all again. I have a second backup phone with the same OS (LOS 16.0). So it is confirmed that:

1) In version 1.0.33 reminders work, both acousticaly and visually. The only thing that does not work is the postponement of the reminders: when i postpone the advices, there is no sound, no visual reminder. The only way to postpone the events is to enter the setting of the event and change the time and save it, which is kind of cumbersome.

2) On another (backup) phone i have 1.0.34 version. The behaviour of this version is really strange. The initial reminder usually works, sometimes the postponement works too, but just with two or three postponements. Sometimes there is silence even for initial reminder, sometimes there is no diode reminder, sometimes there is no acoustic reminder (plus no visual reminder) until i click the power button to wake up the phone (the reminder starts right after the display is turned up, but again, only when i unlock the screen). As stated, it has really strange behaviour, it seems it has no logic. When i had 1.0.34 version installed on the first phone, there was really nothing, no reminder at all. The restart did not help (i had no time to install this version again, but i suppose it will be the same).

So, according to my tests, there are definitelly some bugs both in version 1.0.33 (the postponement bug) and 1.0.34 (strange chaotic not reliable reminders & the postponement bug). The version 1.033 is stable with reminders for my phone, but it contains the postponement bug.

[jspricke]

Thanks for trying to help but as said before the bugs are more likely in the old Android version then in Etar as notifications are handled by the Android system and Etar is only calling into it. There is probably a way to work around that but someone would need to find time to work on it.

[Cwpute]

I am using Android 11 (fairly newer than 9) on a Nokia TA-1157 with Etar updated to 1.0.33, and the notificatiwns were not showing either. I went looking for battery optimization settings and, there it was, Etar was "optimized" and thus couldn't check for events. When "unoptimized" i started receiving notifications as expected.

[Cwpute]

This bug has already been reported numerous times in recent weeks regarding either alarms or reminders:

• https://github.com/Etar-Group/Etar-Calendar/issues/1291
• https://github.com/Etar-Group/Etar-Calendar/issues/1179
• https://github.com/Etar-Group/Etar-Calendar/issues/1181
• older issue with recent comments: https://github.com/Etar-Group/Etar-Calendar/issues/1026

A similar bug has been reported for Simple Calendar, in a similar time-frame (around novemper 2022) which issues were promptly closed with instructions on how to work around that bug manually following help from https://dontkillmyapp.com/ (see for yourselves, that's how i fixed my issue here):

• https://github.com/SimpleMobileTools/Simple-Calendar/issues/1898 + https://github.com/SimpleMobileTools/Simple-Calendar/issues/1890 (same user, same bug)

Somewhat of a fix is being worked on i think: https://github.com/Etar-Group/Etar-Calendar/pull/1184

[Moostek]

Yes, maybe the Android 9 is older, but the issue is present also on much present Android. I guess there must be some join with this issue. Many people report some temporarily solution: it works for one reminder, but than it stops to work again. Many users report this issue across all Android versions and phone brands.

I am new in Etar thread, anyway Cwpute wrote nice overview!

I checked the battery optimazation on my phone and i do not have Etar optimized.

Let's hope that somebody will fnd the way and resolve this issue with Etar's affected code;) Permissions? ACTION_EVENT_REMINDER? Etar deserves the solution!

ACTUAL FINDNGS: The 1.0.33 version on my 1st phone the postponement does not work. On my 2nd phone of the same kind and OS (LineageOS 16.0/Android 9 @ Lenovo S60) the postponement works, but usually only two times. When the reminder is broken (silent) i can "restart" it with manual new time set up and then it works again, BUT sometimes there is only diode reminder without sound and when i enter the display with the power button, the sound appears (this is quite usual). Sometimes there is silence again..

I also tried 1.0.34 version on my 2nd phone. I updated this version and restarted phone. The prime advices work, but it happened once that the diode wwas flashing for a while and the sound reminder appeared some 15 seconds later or so.. The postponement have bugs, similar as staed above. When the postponement comes, the diode is flashing, but the sound appears only when i enter the display with the power button.. I will try to examine the 1st phone with 1.0.34 version again.

[Moostek]

Hello, any progress here in this BUG?? Or is the evolution & solution of the Etar dead? Again: this is crucial BUG, please.

[Cwpute]

No, no evolution, please be patient, the people maintaining this app are unpaid volunteers doing their best. While you wait for this to be sortel out i'd suggest you use another calendar app, so you don't sit with a software that doesn't work at intended and gets you nervous.

[Moostek]

Well, i understand. But this bug seems to be here around quite long period of time and it goes across the Android versions. So i the priority of this bug is pretty high. It is crucial for usage of the calendar.

[CelianGdfrd]

I think there is a fundamental misunderstanding here. Etar is open source and not a commercial product. Open source is based on collaboration, but it seems that everyone here wants to be a beneficiary and not contribute anything.

When I have time I read the bug reports here. But what should I do with one like this? Apart from complaints, it doesn't contain any relevant info for me. No debug log. No information about the hardware used. Just nothing but complaints.

I'm an end user. I've submitted, bumped and spammed about this particular issue, so much that maybe you hate my nickname by now.

The open source ecosystem really is something else from what we, users, know. We are used to products that come with warranty and support. So when something doesn't work, we complain to the shop. In open source, some of us try our best to shift our complaints to constructive feedback and demands for assistance, but we can only do so much : we are not developers, we are just consumers.

For instance, I asked several times if there were things I could do to help you, like logs or something. I never got any answer. And I completely get that you are swamped, are volunteers and do this on your free time. But please don't hate us for reporting a bug the best we can.

I just link again to my own bug report : https://github.com/Etar-Group/Etar-Calendar/issues/1179. The bug happened on my OnePlus 7T Pro, on OxygenOS, and now again on LineageOS. Please tell me if there's more I can provide you with.

Thank you so much for your time and efforts on Etar 🙏

[Moostek]

Hello, i can agree with Kalytis. But i also understand to all open source developers. They doing this in their sparetime, etc. But as Kalytis did note, I'am not also a developer. So from my point of view, my help is sort of limited. I can just try to describe and report the issue, that's all i can do now. I'am sorry for this, but this is like this.

I also asked for the manual here how to obtain the logs, but nobody did answer me to help me how to get them. For many GitHub users it is maybe daily rutine, but for end-users like me or Kalytis it is not automatic.

Every project is different, different people with different priorities, sparetime and capacities etc. But i found many open source projects, they really care about bugs, reports etc. like FairMail, and not only open source ones (like Total Commander or IrfanView for example).

Well, i like the Etar app. It has my sympathy, I would like to use this app as my default calendar app. But the problem is there are some crucial bugs. I reported also another issues here, but no answer. I am glad that in this thread is happening something, but we would like to see some activity to resolve the bugs;)

Thank you!

[jspricke]

Honestly I guess it will be cheaper to just get a phone with a new Android.

[CelianGdfrd]

Yeah that's definitely an option people can consider when encountering a bug with their calendar app

[jspricke]

Well, it is a bug in the old Android, after all. Alternatively just use the old version as noted above.

[CelianGdfrd]

I'm having it on Android 13.

[Moostek]

This solution "to buy a new phone" does not help to Etar. If there is a problem, the problem must be revealed and fixed. Only this attitude make a sence - I guess this is the mission of the community. Not to work for corporations with claims like "Yeah buddy, buy our new super phone, Uncle Sam needs you!"

And also, it is has the environmental aspects - to maximaze the lifetime of the gears (smartphones). I will not run to buy the new phone because i want the app working, even i have loads of money;) Better is to find the solution. And i do not want to install and setup 200 apps again...

By the way, several people reported same kind of issue on newer Android versions, on new smartphones, i.e. the issues are going across Android versions. So there is no garancy i will run Etar smoothly anywhere, until the issues are resolved;)

p.s.: it seems to me that the Etar is designed by the author for his own phone to work perfectly, and not care about the rest. Sorry, but this is my impression from all of this. Another open-source projects they do care, and they do not give such "advices" like " buy the new phone". It is ridiculous.

So let's hope that somebody constructive will appear here;D

[jspricke]

@Kalytis interesting, can you update #1179 with that information, also which version of Etar?

@Moostek I completely agree that it has an environmental aspect and I cry when I see that people by phones that contain closed source blobs and are not upgradable but that's how it is. Also, Etar is not "designed" for any specific phone, it is a fork of the original Android calendar by Google after all and we only try to keep it alive and follow what Google advices. We would be happy if someone "from the community" would come up with patches to improve the situation but till now no one showed up.

[CelianGdfrd]

Sure, will do. It happens to me since 1.0.33

I also filed a bug on Lineage, they made me join a logcat, maybe it could help you somehow : https://gitlab.com/LineageOS/issues/android/-/issues/5407

[Moostek]

Yeah, i really do not like disposable pattern of life. Typically with smartphones, PC or laptops. I understand there is the hw evolution like better camera, Bluetooth v2 to v5 etc. But not everybody need newest Bluetooth for example, i can live with v4 for years and i do not care about camera too (for photos i have Lumix, etc.). So i do not want to drop my old phone with LOS 16.0, 99% apps works fine with my phone, only Etar has some serious troubles. And as confirmed, the newer Androids bulds/phones face the problems too. I guess this is some rooty bug inside of the Etar.

Yes, it will be definitely nice to get some "community developer" to step on it and boost the Etar;D

p.s.: Btw, how can i to obtain the Etar logs?

[woheller69]

I could imagine 9555bdb

To me this also seem to be the only possible cause when looking at the changes made. What about creating an apk with and without this commit for testing?

[woheller69]

The developer guide says: If your app targets Android 13 (API level 33) or higher, you have the option to declare either the SCHEDULE_EXACT_ALARM or the USE_EXACT_ALARM permission.

Maybe there is a bug when both permissions are requested?

[jspricke]

@woheller69 I think #1179 is the better issue to discuss this, see my comment here: https://github.com/Etar-Group/Etar-Calendar/issues/1179#issuecomment-1401135378.

[Moostek]

Hello, i can verify that the Etar issue is NOT caused by my LineageOS 16.0. Why? I test the "Simple Calendar" app, and it works 100%, even the postponement!;) So maybe it is a hint - peep at "Simple Calendar" app.

[OldRoutard]

Hi folks, I just dropped by to report my experience as follows:

• Device: Fairphone FP4
• OS: FPOS always run the latest version, currently FP4.FP4I.A.175.20221207 (Android 11)
• Etar 1.0.33

Not long ago, after missing some appointments (annoying, naturally), I realised that Etar was no longer producing notifications of any sort. I don't know whether this started after the last OS update in December, or after some update of the app. Having spent some time checking settings, doing tests I wound up here and was (in a rather selfish way) relieved to discover that this was a known problem.

Thanks Cwpute for the hint to check battery optimisation.

I have changed the Battery optimisation setting from Optimise to Don't optimise.

I confess to having not taken any notice of the (i) icon displayed at the top (mentioned in another thread) and which of course has now gone.

Notifications are now working correctly (text and sound) including Snooze. I have not yet noticed any appreciable increase in battery use, but I only changed the setting this morning, will report back here if I do. I will update to 1.0.34 shortly, hoping that the notifications will keep on working ;-)

Regards - and thanks for a very useful app.

[Moostek]

Well, i did mention it somewhere here above (or in another thread): I do not have Optimalization turned on for Etar, but the problem persists. For my LineageOS deoptimalization has no effect.

And as i wrote in my previous message: it make really sence to focus on "Simple Calandar" app, because with this app works everything on 100% - event the postponement! This is the prove that the problem is inside of the Etar app.
Maybe it will be fine to check how it goes with "Simple Calendar" app, and find there some inspiration.

[jspricke]

And as i wrote in my previous message: it make really sence to focus on "Simple Calandar" app, because with this app works everything on 100% - event the postponement! This is the prove that the problem is inside of the Etar app. Maybe it will be fine to check how it goes with "Simple Calendar" app, and find there some inspiration.

Thanks for pointing that out though no one denied that a solution could be implemented in Etar. The two point where that something else then Etar changed breaking the function and that someone needs to find time to look into this.

[woheller69]

9555bdb

What about creating 2 apks and provide them here? One apk with and one without this commit as a simple way for testing?

[CelianGdfrd]

I confirm that turning off battery optimization didn't help either for me.

[Moostek]

Sure, i know that this issue is repareable. And yes, it is about that somebody will invest his/her time into it and find the solution. I did mention "Simple Calendar" app to get there some kind of inspiration - to check how it is there.

@woheller69: It make sence to me too.

[Gitsaibot]

@woheller69 I suggested this in the chat 3 weeks ago:

You can also test the individual debug.apk if you want to know from which commit the notifications no longer work. Under actions there is a matching debug.apk for each commit. e.g.: https://github.com/Etar-Group/Etar-Calendar/actions/runs/3807595747

[woheller69]

Then I would suggest:

try this APK: https://github.com/Etar-Group/Etar-Calendar/suites/10113941743/artifacts/493373469

and then this APK: https://github.com/Etar-Group/Etar-Calendar/suites/10206531662/artifacts/499838327

If notifications fail with the second APK, this commit https://github.com/Etar-Group/Etar-Calendar/commit/9555bdba889a40df892fe47f51aac6b72aadeb0e is the root cause

[CelianGdfrd]

After a quick test, I believe I encountered the bug again with the second APK. I didn't test the first one.

[bjlockie]

The first one works for me. I wonder if it has something to do with background battery use? It asked for that permission but I don't remember the buggy one asking.

[woheller69]

This commit https://github.com/Etar-Group/Etar-Calendar/commit/9555bdba889a40df892fe47f51aac6b72aadeb0e is the root cause and should be reverted.

[CelianGdfrd]

The first one works for me. I wonder if it has something to do with background battery use? It asked for that permission but I don't remember the buggy one asking.

Does it work more than once ? Sometimes it worked once after reinstalling and then stopped working again.

[bjlockie]

Works twice

[CelianGdfrd]

Well, are we finally about to fix this bug ? 👀

[bjlockie]

Well, are we finally about to fix this bug ? 👀

Try the apk and see if it works for you.

[CelianGdfrd]

The download isn't available anymore, I believe

[woheller69]

Here they are:

Then I would suggest:

try this APK: https://github.com/Etar-Group/Etar-Calendar/suites/10113941743/artifacts/493373469

and then this APK: https://github.com/Etar-Group/Etar-Calendar/suites/10206531662/artifacts/499838327

If notifications fail with the second APK, this commit 9555bdb is the root cause

[bjlockie]

Are you logged in to gitguh? I had the same problem until I logged in.

[CelianGdfrd]

Thanks @woheller69 @bjlockie !

After trying the first APK, the alerts seem to be working aswell