App crashes or stutters when running on Google Pixel 9a

[Hubertilus]

Checklist

• [x] I can reproduce the bug with the latest version given here.
• [x] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• [x] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• [x] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [x] This issue contains only one bug.
• [x] I have read and understood the contribution guidelines.

Affected app version

1.8.1

Affected Android/Custom ROM version

Android 16

Affected device model

Google Pixel 9a

How did you install the app?

Google Play Store

Which calendar service or provider do you use, if any?

local Nextcloud

Which sync adapter app do you use for calendar synchronization, if any?

DAVx5

Steps to reproduce the bug

There are three ways to see issues with the app:

1. Just open the app by taping the app icon
2. Flicking up and down repeatedly, while viewing a weekly calendar
3. Flicking left and right repeatedly, while viewing a weekly calendar

Expected behavior

1. App starts fast (normal)
2. Rolling the weekly content up and down is smooth without stuttering.
3. Switching between different wicks goes smoothly without stuttering

Actual behavior

1. When opening the app It takes several seconds until I can see the content. Frequently, if the app wasn't used for a time (say 1 hour), it often crashes the first time before I can see a more than a white screen.
2. When flicking up and down and the content scrolles through the hours, if frequently stutters. Sometimes the app crashes
3. When flicking left or right between weeks, it frequently stutters/hangs for a moment. Sometimes the app crashes.

Screenshots/Screen recordings

No response

Additional information

Before I was using a Samsung Galaxy A71 phone. There the Fossify Calendar was running fine. But when moving to a Google Pixel 9a, I immidiately was facing crashes and stuttering/hanging. So I was wondering, if the app is not prepared for such kind of new phones. So I came up with the idea to try compiling the source code for Pixel 9a with API 35+ using Android Studio. Everithing was quite easy. And after installing the fresh compiled app on my Pixel 9a, it runs as smooth like on my old phone. So recompiling for API 35+ is a solution for me, but maybe there is a way to find the root cause and fix it in your official builds?

[naveensingh]

So recompiling for API 35+ is a solution for me, but maybe there is a way to find the root cause and fix it in your official builds?

The latest version does target API 36. You likely didn't see the issue because your build didn't have many events.

On average, how many events do you have per page on the weekly view? Just a few or many?

[Hubertilus]

Hi, I did crosscheck. Yes you're right with the building. I recompiled a release version, without changing any source file. So the API version was taken from the Android.Manifest. But anyhow, recompiling fixed my issue on the Pixel 9a. Im Synchronizing the calendars of 6 different persons. I crosschecked, that the setup on the Goolge Playstore App version and the new compiled one are the same. So for this week there are 10 event, the next week with 16 and the week afterwards 20 appointments. Running the Google Play store version flicking stutters and the app frequently crashes. Using the recompiled one I'm not having the issue. I just did a git clone https://github.com/FossifyOrg/Calendar.git Open the canedor directory in Android Studio, Chosse my USB connected Pixel 9a as runing device, added a signature/keystore and pressed the run app button. Nothing else.

[naveensingh]

Ok, could you please do an adb logcat and share the stacktrace here? That would really help find out what's causing the crash.

[Hubertilus]

Yes, I did an adb logcat. File is attached. I stopped the log directly after the crash.

Besides that I did take a video when flicking in the settings menu. Even there you can see a stuttering. I just did a singe flick with a finger.

https://github.com/user-attachments/assets/3e96a4f8-ade7-4a33-aba3-b8920c4f6df5

adb_logcat.txt

[Hubertilus]

Maybe the following log is more helpfull for ouy. I started the app, used adb shell pidof org.fossify.calendar for getting the pid of the running app. But before running logcat, the app already crashed. But still adb logcat --pid=1531 gave me the attached second log

adb_logcat2.txt

I also tried it a second time, and the app crashed while doing the logcat. And the error still looks similar:

--------- beginning of crash
11-19 23:26:51.069  4816  5831 E AndroidRuntime: FATAL EXCEPTION: Thread-385
11-19 23:26:51.069  4816  5831 E AndroidRuntime: Process: org.fossify.calendar, PID: 4816
11-19 23:26:51.069  4816  5831 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 16 byte allocation with 165056 free bytes and 161KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
11-19 23:26:51.069  4816  5831 E AndroidRuntime:        at s5.t.a(Unknown Source:4)
11-19 23:26:51.069  4816  5831 E AndroidRuntime:        at I0.v.run(Unknown Source:37)
11-19 23:26:51.069  4816  5831 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:1119)
11-19 23:26:51.082  4816  5831 I Process : Sending signal. PID: 4816 SIG: 9

[naveensingh]

Yes, both logs point to an OutOfMemory error.

[j-px]

version 1.8.0 doesn't OOM/hang after downgrading

don't forget backups or you'll lose your events like me!!

[j-px]

nevermind, the app still hangs, and seems to not finish synchronizing CalDAV calendars

[naveensingh]

@j-px, are you saying this problem also exists on v1.8.0?

[j-px]

yes

[528-491]

Hi, similar setup and issue here. Pixel 9 Pro XL with GrapheneOS (Android 16) Calendars synced via DAVx5

Getting crashes and hangups du to failed or slow memory allocation, can provide logs if needed.

What I noticed: My DAVx5 app was recently updated:

Version 4.5.6-ose

at.bitfire.davdroid
versionCode 405060004

targetSdk 36
minSdk 24

Installed: 30.03.2025; 23:11
Updated: 24.11.2025; 18:10

while Fossify Calendar wasn't updated for a few weeks:

Version 1.8.1

org.fossify.calendar
versionCode 15

targetSdk 36
minSdk 26

Installed: 29.03.2025; 20:38
Updated: 09.11.2025; 21:16

But the problems appeared only recently, lika a few days ago, so maybe it's due to the davx5 update?

[naveensingh]

But the problems appeared only recently, lika a few days ago, so maybe it's due to the davx5 update?

It could be. Only one way to find out 😉

[528-491]

I checked on another phone, Pixel 8, same setup BUT with davx 4.5.5-ose. Same issue there, unfortunately.

[daxcore]

We are facing the same issue on a pixel 7a with GrapheneOS and davX. Interessting that it does not happen on a pixel 7 with nearly exact same setup.