[DeadObjectException] Transaction failed on small parcel.

[Markoise]

Since version 4.3.13.1-glplay I get the following error message:

Contacts (Nextcloud (Lokal) 0A)
Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffer space

This error occurs 1 to 2 times a day. Apparently it refers to the synchronization of contacts.

OS: Android 14
Device: Pixel 7
Nextcloud: 28.0.2

Everything else works fine.

The error is annoying, so I hope to find a solution here.
I have already set up the connection again.

[rfc2822]

I have sometimes seen that already, but could never reproduce it. Does it go away when you restart the device?

[rfc2822]

Can you try restarting the device?

[Markoise]

Sure, of course. I'll get in touch again tomorrow.

[Markoise]

This also happens after a restart.

[rfc2822]

I have already seen it myself, but never managed to reproduce it.

Any hints on how to reproduce it? Otherwise there's no chance of fixing it.

[Markoise]

The error no longer appears now. No idea why.

[Lurikbolding]

Hello

I have the same issue : "Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffer space"

OS: Android 14
Device: samsung A15
carddav on Synology NAS

[rfc2822]

Can you kill the app and the tasks app and try again or reboot the phone?

[pascalxricher]

Same error here, one or twice a day
Android 14
Synology NAS carddav

[rfc2822]

I have already seen it myself, but never managed to reproduce it.

Any hints on how to reproduce it? Otherwise there's no chance of fixing it.

[rfc2822]

May be relevant:

• expo-location background location task quietly crashes app until android shuts it down. expo/expo#23853
• https://community.verizon.com/t5/Samsung/After-OS-upgrade-on-my-Galaxy-S23-many-apps-including-Samsungs/td-p/1724533
• https://medium.com/@jiang7748533/how-aidl-slices-and-transfers-large-lists-of-parcelable-data-a0e4126e44e6

[rfc2822]

See also https://github.com/bitfireAT/davx5/issues/459

[danepowell]

Same issue, started occurring around the same time. Restarting doesn't stop it from appearing again in a few hours.

Pixel 8, Android 14, March security updates, version 4.3.15-ose

[rfc2822]

Any hints how to reproduce it?

[ZeroOne010101]

I have recently started to get what seems to be the same error.
I have attached the davx5-debug.zip (some information redacted), hope it helps.
The error has appeared twice so far, with a couple of days to a week time in-between.
I think i updated to the newest f-droid version shortly before, but I'm not certain.
I dont think i have any further hints, sadly.

[musichemist]

Same issue
Pixel 8 pro
Up-to-date Android and F-droid DavX5 version
CardDav with fastmail.com
"Allow regular sync" was not selected, but now it is. I'll check back if this changes anything
No idea how to reproduce
Can figure out how to send a log if it would be helpful

[fabienli]

Also happening here since yesterday (Samsumg S22 Android 14, DAVx5 4.3.15-ose, Nextcloud 27.1.8).
-> a restart doesn't solve it
-> I've just tried to clean all data from OpenTasks, first sync was then ok ... pending if the error happens again later on

[jeffxt]

Guess I'm not alone

Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffer space

Pixel 8, Android 14
Baikal via Docker on Synology NAS

I've tried:

• Clearing cache on Dav5 on my phone
• Clearing data on Davx5 (i.e., completely reset the app from scratch and reset up everything)
• Restarting my phone
• Restarting Baikal on Docker
• Restarting my NAS

I'm not able to reproduce it. It happens randomly, sometimes late at night, sometimes in the evening. It can be days or a week between issues.

However, I did notice this started to happen after a recent update somewhere in February (not exactly sure what version I was on, I have auto-update enabled in Google Play Store). But I'm fairly confident it's on the app-side, because I have not changed anything with my setup in the months prior to observing this issue.

[domiEf]

Same error here, is there a solution I didn't stumble upon yet?

Pixel 6
CalyxOS Android 14
syncing with posteo.de

[rfc2822]

It seems to (only/mostly) affect Android 14. I wish I could even reproduce the problem...

[kartoffelheinz]

Here also with a Pixel 4a (no 5G) on Android 13 and latest Nextcloud.
Happening multiple times a day and even seems to get worse, about 20 times today so far.

[rfc2822]

Any ideas how we could reproduce the problem so that we can get even a slightest idea of what is going on?

Maybe adb logs?

Does it still happen with 4.3.16 (was just released)?

[arnowelzel]

I have 4.3.16 installed here and will let you know, if it happens again. Hopefully I can the provide a bit more details if possible.

[bene64]

Just had it again on 4.3.16.1-ose (from F-Droid) on Android 14 (Lineage21 for microG).

[kartoffelheinz]

Wait, thats weird. I also just (past minute) had it occur on my Pixel 4a Android 13. Coincidence?

[rfc2822]

I wonder whether the problem could maybe be related to this change in Android 14:

https://developer.android.com/about/versions/14/behavior-changes-all#pending-broadcasts-queued

On Android 14, the system can place context-registered broadcasts in a queue while the app is in the cached state. This is similar to the queuing behavior that Android 12 (API level 31) introduced for async binder transactions. Manifest-declared broadcasts aren't queued, and apps are removed from the cached state for broadcast delivery.

When the app leaves the cached state, such as returning to the foreground, the system delivers any queued broadcasts. Multiple instances of certain broadcasts might be merged into one broadcast. Depending on other factors, such as system health, apps might be removed from the cached state, and any previously queued broadcasts are delivered.

[MattRGX]

Same issue here. Happen randomly for me or maybe there is a pattern but i'm not able to figure it out.

Pixel 7
Android 14
CalyxOS 5.6.0

If you want any logs, i can share if you want.

[devvv4ever]

adb logs from the device while this occurs may help us finding something out. section "Android debugging" here: https://www.davx5.com/faq/how-to-debug, thank you!

[reaganch]

Been seeing the same issue as well for the last few weeks. Been occurring rather randomly a few times every day. If there's anything (logs, etc.) I can share to help troubleshoot this, please let me know.

Xiaomi Poco F5
Android 14
crDroid 10.2

[devvv4ever]

adb logs from the device while this occurs may help us finding something out. section "Android debugging" here: https://www.davx5.com/faq/how-to-debug, thank you!

[ZeroOne010101]

It happened again half an hour ago.
I had Verbose Logging turned on in anticipation of this.
You can find the (redacted) logs attached.
I know next to nothing about this, but the line right before the error says something about storage being inaccessible?

I hope this helps.

davx5-debug_detailed.zip

[arnowelzel]

JFTR: so far it works for me now for at least a week with 4.3.16.1-gplay running in Android 14 on a Google Pixel 6a. Before I had the error at least once or twice a week.

[arnowelzel]

I just happend here again as well with 4.3.61.6-gplay. Since the debug info also contains personal information I'd rather don't want to share this public, thanks.

[exstntlmsnthrp]

For what it's worth, I had the same things happen once today and once yesterday and both at similar times of day. Using version 4.3.16.1-ose from GitHub on Pixel 7 Pro with Android 14.

I tried to duplicate it but was unable to do so. After I remove personally sensitive information, I'll post logs.

[Wurzelmann]

Same problem here on Pixel 7 with Android 14 (LineageOS), Version 4.3.16.1-ose. Cannot reproduce it manually, it just happens a few times per day.

[rfc2822]

Anyone willing to test an APK (I can only sign with our = github/gplay key)?

I have an idea of a workaround but I don't know whether it will actually work, and because I can't reproduce the problem myself, I'd need someone to test it.

[rfc2822]

Ok, new version. This one should hopefully work:

https://cloud.bitfire.at/s/6TAejrJNFiwHPSm

Can someone try?

[Wurzelmann]

Thank you very much, installing right now!

[arnowelzel]

Ok, new version. This one should hopefully work:

https://cloud.bitfire.at/s/6TAejrJNFiwHPSm

Can someone try?

Just done.

[exstntlmsnthrp]

Okay, touch wood; but, since installing version 4.3.17-alpha.3, I have not seen the error any longer. It seems like whatever you did, likely fixed the problem.

Cheers.

[arnowelzel]

Works fine here so far as well. Thanks for your support!

[rfc2822]

Hopefully fixed with 857309c, which is contained in 4.3.17-alpha.4 and newer.

[reaganch]

@rfc2822 - Could you please advise where I can download 4.3.17-alpha.4 from? The link above (https://cloud.bitfire.at/s/6TAejrJNFiwHPSm) only provides the download to 4.3.17-alpha.3. Thanks!

[rfc2822]

@rfc2822 - Could you please advise where I can download 4.3.17-alpha.4 from? The link above (https://cloud.bitfire.at/s/6TAejrJNFiwHPSm) only provides the download to 4.3.17-alpha.3. Thanks!

You can use the link above. Its 4.3.17-alpha.3 plus the DeadObject fix.

[reaganch]

Great! Thanks...

[devvv4ever]

A first beta of DAVx⁵ 4.4 will be available soon via Google Play beta programme, it will also contain the workaround for this Android caching bug.

[devvv4ever]

4.4 is now live!