# Help testing upcoming Delta Chat 2.34.\* release! **URL:** \ **Category:** User Testing\ **Created:** [December 8, 2025, 5:17pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427 "2025-12-08T17:17:52Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![Alex](https://forum.delta.chat/user_avatar/forum.delta.chat/alex/32/2697_2.png) [@Alex](https://forum.delta.chat/u/Alex)\ **Post date:** [December 13, 2025, 5:14pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/22 "2025-12-13T17:14:00Z")
Thank you, I was able to add one of the classic email accounts. ---
**Author:** ![Alex](https://forum.delta.chat/user_avatar/forum.delta.chat/alex/32/2697_2.png) [@Alex](https://forum.delta.chat/u/Alex)\ **Post date:** [December 15, 2025, 5:50pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/23 "2025-12-15T17:50:33Z")
Hello! Where did version 2.33.1 from F-Droid go? It’s now only 2.25.0. ---
**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\ **Post date:** [December 15, 2025, 6:31pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/24 "2025-12-15T18:31:37Z")
> [@Alex](#): > > Hello! Where did version 2.33.1 from F-Droid go? It’s now only 2.25.0. It is withdrawn because of this issue that resulted in the app not starting on some phones after upgrade: > > > \> visually, what happens looks like this: > \> > \> - i tap the delta icon > \> - screen …shows "black with delta logo" for maybe 15s > \> - i get dropped back to the android "main screen/desktop" > > Part of the log captured with \`adb logcat | grep -e b44t\`: > \`\`\` > 12-12 11:16:13.317 2100 2156 D WindowManagerShell: onActivityRestartAttempt: topActivity=ComponentInfo{com.b44t.messenger/org.thoughtcrime.securesms.ConversationListActivity}, wasVisible=false > 12-12 11:16:13.333 1290 1539 V WindowManager: Sent Transition (#3678) createdAt=12-12 11:16:13.273 via request=TransitionRequestInfo { type = OPEN, triggerTask = TaskInfo{userId=0 taskId=18597 effectiveUid=10163 displayId=0 isRunning=true baseIntent=Intent { act=android.intent.action.MAIN cat=\[android.intent.category.LAUNCHER\] flg=0x10200000 cmp=com.b44t.messenger/org.thoughtcrime.securesms.RoutingActivity } baseActivity=ComponentInfo{com.b44t.messenger/org.thoughtcrime.securesms.ConversationListActivity} topActivity=ComponentInfo{com.b44t.messenger/org.thoughtcrime.securesms.ConversationListActivity} origActivity=ComponentInfo{com.b44t.messenger/org.thoughtcrime.securesms.RoutingActivity} realActivity=ComponentInfo{com.b44t.messenger/org.thoughtcrime.securesms.ConversationListActivity} numActivities=1 lastActiveTime=544733346 supportsMultiWindow=true resizeMode=1 isResizeable=true minWidth=-1 minHeight=-1 defaultMinSize=220 token=WCT{RemoteToken{36b7236 Task{4016a12 #18597 type=standard A=10163:com.b44t.messenger}}} topActivityType=1 pictureInPictureParams=null shouldDockBigOverlays=false launchIntoPipHostTaskId=-1 lastParentTaskIdBeforePip=-1 displayCutoutSafeInsets=Rect(0, 0 - 0, 0) topActivityInfo=ActivityInfo{fce6aa4 org.thoughtcrime.securesms.RoutingActivity} launchCookies=\[android.os.BinderProxy@4fc9582\] positionInParent=Point(0, 0) parentTaskId=-1 isFocused=false isVisible=false isVisibleRequested=false isTopActivityNoDisplay=false isSleeping=false locusId=null displayAreaFeatureId=1 isTopActivityTransparent=false isActivityStackTransparent=false lastNonFullscreenBounds=Rect(252, 545 - 828, 1625) capturedLink=null capturedLinkTimestamp=0 requestedVisibleTypes=-9 topActivityRequestOpenInBrowserEducationTimestamp=0 appCompatTaskInfo=AppCompatTaskInfo { topActivityInSizeCompat=false eligibleForLetterboxEducation= false isLetterboxEducationEnabled= false isLetterboxDoubleTapEnabled= false eligibleForUserAspectRatioButton= false topActivityBoundsLetterboxed= false isFromLetterboxDoubleTap= false topActivityLetterboxVerticalPosition= -1 topActivityLetterboxHorizontalPosition= -1 topActivityLetterboxWidth=-1 topActivityLetterboxHeight=-1 topActivityLetterboxAppWidth=-1 topActivityLetterboxAppHeight=-1 isUserFullscreenOverrideEnabled=false isSystemFullscreenOverrideEnabled=false hasMinAspectRatioOverride=false topActivityLetterboxBounds=null cameraCompatTaskInfo=CameraCompatTaskInfo { freeformCameraCompatMode=inactive}} topActivityMainWindowFrame=null}, pipChange = null, remoteTransition = RemoteTransition { remoteTransition = android.window.IRemoteTransition$Stub$Proxy@9a57493, appThread = android.app.IApplicationThread$Stub$Proxy@1a99cd0, debugName = QuickstepLaunch }, displayChange = null, flags = 0, debugId = 3678 } > 12-12 11:16:13.334 1290 1539 V WindowManager: {WCT{RemoteToken{36b7236 Task{4016a12 #18597 type=standard A=10163:com.b44t.messenger}}} m=TO\_FRONT f=MOVE\_TO\_TOP leash=Surface(name=Task=18597)/@0xc381e5b sb=Rect(0, 0 - 1080, 2160) eb=Rect(0, 0 - 1080, 2160) epz=Point(1080, 2160) d=0 taskParent=-1}, > 12-12 11:16:13.366 1290 1954 E JobScheduler.JobStatus: App com.b44t.messenger became active but still in NEVER bucket > 12-12 11:16:14.185 1290 1539 V WindowManager: {WCT{RemoteToken{36b7236 Task{4016a12 #18597 type=standard A=10163:com.b44t.messenger}}} m=TO\_BACK f=NONE leash=Surface(name=Task=18597)/@0xc381e5b sb=Rect(0, 0 - 1080, 2160) eb=Rect(0, 0 - 1080, 2160) epz=Point(1080, 2160) d=0 taskParent=-1}, > 12-12 11:16:15.268 1290 27432 D CoreBackPreview: Window{7d641cc u0 Splash Screen com.b44t.messenger}: Setting back callback null > 12-12 11:18:54.794 1290 1554 I ActivityManager: Extending process start timeout by 371ms for ProcessRecord{72b1b1e 13836:com.b44t.messenger/u0a163} > 12-12 11:18:55.460 1290 13897 E ActivityManager: ANR in com.b44t.messenger > 12-12 11:18:55.460 1290 13897 E ActivityManager: Reason: Process ProcessRecord{72b1b1e 13836:com.b44t.messenger/u0a163} failed to complete startup > 12-12 11:18:55.463 1290 13897 I ActivityManager: Killing 13836:com.b44t.messenger/u0a163 (adj 0): bg anr > 12-12 11:18:55.466 1290 13897 D ActivityManager: Completed ANR of com.b44t.messenger in 290ms, latency 1ms > 12-12 11:18:55.560 1290 2241 W ActivityTaskManager: ProcessRecord{72b1b1e 13836:com.b44t.messenger/u0a163} is removed with pending start ActivityRecord{6751645 u0 com.b44t.messenger/org.thoughtcrime.securesms.RoutingActivity t18597} > \`\`\` > > Log grepped by process ID: > \`\`\` > 12-12 12:02:43.913 876 876 D Zygote : Forked child process 15391 > 12-12 12:02:43.914 1290 1555 I ActivityManager: Start proc 15391:com.b44t.messenger/u0a163 for next-top-activity {com.b44t.messenger/org.thoughtcrime.securesms.RoutingActivity} > 12-12 12:02:43.938 15391 15391 I .b44t.messenger: Using CollectorTypeCC GC. > 12-12 12:02:43.953 15391 15391 E .b44t.messenger: Not starting debugger since process cannot load the jdwp agent. > 12-12 12:02:43.960 15391 15391 D nativeloader: Load libframework-connectivity-tiramisu-jni.so using APEX ns com\_android\_tethering for caller /apex/com.android.tethering/javalib/framework-connectivity-t.jar: ok > 12-12 12:02:42.448 0 0 I binder : 15391:15391 ioctl 40046210 7ffee4f504 returned -22 > 12-12 12:02:43.985 15391 15391 D ApplicationLoaders: Returning zygote-cached class loader: /system\_ext/framework/androidx.window.extensions.jar > 12-12 12:02:43.985 15391 15391 D ApplicationLoaders: Returning zygote-cached class loader: /system\_ext/framework/androidx.window.sidecar.jar > 12-12 12:02:43.994 15391 15391 D nativeloader: Configuring clns-7 for other apk /data/app/ ~~zbPD9xXThHrGnmhg3O9FKw==/com.b44t.messenger-05CrmHXF9V3QoVu16qmxOA==/base.apk. target\_sdk\_version=36, uses\_libraries=, library\_path=/data/app/~~ zbPD9xXThHrGnmhg3O9FKw==/com.b44t.messenger-05CrmHXF9V3QoVu16qmxOA==/lib/arm64:/data/app/~~zbPD9xXThHrGnmhg3O9FKw==/com.b44t.messenger-05CrmHXF9V3QoVu16qmxOA==/base.apk!/lib/arm64-v8a, permitted\_path=/data:/mnt/expand:/data/user/0/com.b44t.messenger > 12-12 12:02:43.998 15391 15391 I .b44t.messenger: AssetManager2(0x73bc640eb8) locale list changing from \[\] to \[en-US\] > 12-12 12:02:44.005 15391 15391 V GraphicsEnvironment: Currently set values for: > 12-12 12:02:44.005 15391 15391 V GraphicsEnvironment: angle\_gl\_driver\_selection\_pkgs=\[\] > 12-12 12:02:44.005 15391 15391 V GraphicsEnvironment: angle\_gl\_driver\_selection\_values=\[\] > 12-12 12:02:44.005 15391 15391 V GraphicsEnvironment: com.b44t.messenger is not listed in per-application setting > 12-12 12:02:44.005 15391 15391 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported. > 12-12 12:02:44.010 15391 15391 I MultiDex: VM with version 2.1.0 has multidex support > 12-12 12:02:44.010 15391 15391 I MultiDex: Installing application > 12-12 12:02:44.010 15391 15391 I MultiDex: VM has multidex support, MultiDex support library is disabled. > 12-12 12:02:44.014 15391 15391 D WM-WrkMgrInitializer: Initializing WorkManager with default configuration. > 12-12 12:02:44.018 15391 15391 D WM-PackageManagerHelper: Skipping component enablement for androidx.work.impl.background.systemjob.SystemJobService > 12-12 12:02:44.018 15391 15391 D WM-Schedulers: Created SystemJobScheduler and enabled SystemJobService > 12-12 12:02:44.023 15391 15391 I DeltaChat: ++++++++++++++++++ ApplicationContext.onCreate() ++++++++++++++++++ > 12-12 12:02:44.093 15391 15391 D nativeloader: Load /data/app/~~zbPD9xXThHrGnmhg3O9FKw==/com.b44t.messenger-05CrmHXF9V3QoVu16qmxOA==/lib/arm64/libnative-utils.so using class loader ns clns-7 (caller=/data/app/~~zbPD9xXThHrGnmhg3O9FKw==/com.b44t.messenger-05CrmHXF9V3QoVu16qmxOA==/base.apk): ok > 12-12 12:02:58.977 1290 1554 I ActivityManager: Extending process start timeout by 26ms for ProcessRecord{ebe91a4 15391:com.b44t.messenger/u0a163} > 12-12 12:02:59.005 1290 15423 I ActivityManager: Collecting stacks for pid 15391 into temporary file temp\_anr\_7411366637760610173.txt > 12-12 12:02:59.006 1290 15423 E android.os.Debug: Failed to get binder state info for pid: 15391 status: -13: Permission denied > 12-12 12:02:59.007 1290 15423 I system\_server: libdebuggerd\_client: started dumping process 15391 > 12-12 12:02:59.008 620 620 I tombstoned: registered intercept for pid 15391 and type kDebuggerdJavaBacktrace > 12-12 12:02:59.009 15391 15393 I .b44t.messenger: Thread\[2,tid=15393,WaitingInMainSignalCatcherLoop,Thread\*=0x73dc636380,peer=0x20407a0,"Signal Catcher"\]: reacting to signal 3 > 12-12 12:02:59.009 15391 15393 I .b44t.messenger: > 12-12 12:02:59.177 620 620 I tombstoned: received crash request for pid 15391 > 12-12 12:02:59.177 620 620 I tombstoned: found intercept fd 512 for pid 15391 and type kDebuggerdJavaBacktrace > 12-12 12:02:59.178 15391 15393 I .b44t.messenger: Wrote stack traces to tombstoned > 12-12 12:02:59.179 1290 15423 I system\_server: libdebuggerd\_client: done dumping process 15391 > 12-12 12:02:59.198 1290 15424 E ActivityManager: PID: 15391 > 12-12 12:02:59.198 1290 15424 E ActivityManager: Reason: Process ProcessRecord{ebe91a4 15391:com.b44t.messenger/u0a163} failed to complete startup > 12-12 12:02:59.200 1290 15424 I ActivityManager: Killing 15391:com.b44t.messenger/u0a163 (adj 0): bg anr > 12-12 12:02:59.282 1290 1614 I libprocessgroup: Removed cgroup /sys/fs/cgroup/uid\_10163/pid\_15391 > 12-12 12:02:59.282 1290 7884 W ActivityTaskManager: ProcessRecord{ebe91a4 15391:com.b44t.messenger/u0a163} is removed with pending start ActivityRecord{15896056 u0 com.b44t.messenger/org.thoughtcrime.securesms.RoutingActivity t18602} > 12-12 12:02:59.282 876 876 I Zygote : Process 15391 exited due to signal 9 (Killed) > \`\`\` > > So this actually does get to \`ApplicationContext.onCreate\`, but fails with ANR later. > > Android version is LineageOS 22.2 (corresponds to Android 15). > > gplay version from https://download.delta.chat/android/beta/ starts, allows to create a new profile and restarts after kill on the same phone. There are no google services installed. Since then workaround was found, but it requires users to go into “developer options” of Android. A proper fix is pending at [do accounts migration in background by adbenitez · Pull Request #4129 · deltachat/deltachat-android · GitHub](https://github.com/deltachat/deltachat-android/pull/4129) ---
**Author:** ![deltahat](https://forum.delta.chat/user_avatar/forum.delta.chat/deltahat/32/2984_2.png) [@deltahat](https://forum.delta.chat/u/deltahat)\ **Post date:** [December 16, 2025, 10:28am UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/25 "2025-12-16T10:28:10Z")
> [@noob6](#): > > There is no option to add new relays by “paste from clipboard” or “load QR Code as image” if DC has no camera permission ON. For the record it’s the same when you add a contact. If camera permission is OFF it fails and won’t allow the option to “paste from clipboard” an invitation link or “load QR Code as image”. The same QR scan logic must be used in both places. ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [December 16, 2025, 5:17pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/26 "2025-12-16T17:17:31Z")
there is a new 2.34.0 release: - 🍋 [https://download.delta.chat/android/beta/deltachat-gplay-release-2.34.0.apk](https://download.delta.chat/android/beta/deltachat-gplay-release-2.34.0.apk) (google play candidate, overwrites existing installs, should keep data) - 🍉 [https://download.delta.chat/android/beta/deltachat-foss-debug-2.34.0.apk](https://download.delta.chat/android/beta/deltachat-foss-debug-2.34.0.apk) (f-droid candidate, can be installed beside google play) this is already on its way to f-droid and google play ---
**Author:** ![outofcreativity](https://forum.delta.chat/letter_avatar_proxy/v4/letter/o/5daacb/32.png) [@outofcreativity](https://forum.delta.chat/u/outofcreativity)\ **Post date:** [January 1, 2026, 11:38am UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/27 "2026-01-01T11:38:17Z")
Over the last few weeks after upgrading to 2.34 I’ve noticed some weird behavior regarding relays. When switching to a different relay, the next couple of messages are not synced to my other devices. Sometimes they, sometimes not all, arrive after some hours with a different timestamp. The other thing is, in the profile selector under “Connectivity”, the status of the wrong relay is displayed. At this point in time, “[nine.testrun.org](http://nine.testrun.org)” should display 800 MiB with more space used. Sometimes details of “chatmail.bsd.cafe” is displayed. On the screenshot you can see the details of “[arcanechat.me](http://arcanechat.me)” relay, which is mostly shown. To test things I’ve switched to the other 2 relays for a brief time in the past, although switched back to “[nine.test.run.org](http://nine.test.run.org)” I’ve experienced the behaviour on Android as well a on Linux desktop. This screenshot shows ArcaneChat from F-Droid. On Github I saw, some recently closed, issues that may relate to the behaviour. Can provide logs if it helps. Thank you! ![zq0mjxcpj1a43i5r](https://support.delta.chat/uploads/default/original/2X/9/9357c418c44eae332d090e56ed0c2e35e41ee801.jpeg) ---
**Author:** ![Simon](https://forum.delta.chat/user_avatar/forum.delta.chat/simon/32/287_2.png) [@Simon](https://forum.delta.chat/u/Simon)\ **Post date:** [January 1, 2026, 1:17pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/28 "2026-01-01T13:17:51Z")
> [@outofcreativity](#): > > The other thing is, in the profile selector under “Connectivity”, the status of the wrong relay is displayed. There is already a pr merged to display quota for all transports, will be in one of the next releases (in 2.36.x, which is not tagged yet) [feat: connectivity view: quota for all transports by Simon-Laux · Pull Request #7630 · chatmail/core · GitHub](https://github.com/chatmail/core/pull/7630). So the connectivity view part of your report is already solved. ---
**Author:** ![Alex](https://forum.delta.chat/user_avatar/forum.delta.chat/alex/32/2697_2.png) [@Alex](https://forum.delta.chat/u/Alex)\ **Post date:** [January 2, 2026, 12:15pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/29 "2026-01-02T12:15:45Z")
Hello! DC 2.34.0 Android, classic email server: 1. After changing the relay on my contacts’ side, the “Verified: Personal” checkbox disappeared from the properties of these contacts. 2. All other things being equal (the same number of chats with daily message self-destruction enabled), the size of the daily profile backup is constantly increasing. ---
**Author:** ![irvan-putra](https://forum.delta.chat/user_avatar/forum.delta.chat/irvan-putra/32/2473_2.png) [@irvan-putra](https://forum.delta.chat/u/irvan-putra)\ **Post date:** [January 20, 2026, 11:00am UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/30 "2026-01-20T11:00:22Z")
Because I don’t understand it properly, I have enabled “Multi-Device Mode” and this make me keep filling up relays when changing. I wish there are ways to clear non-main relays. ![Screenshot_20260120_164906_Delta Chat](https://support.delta.chat/uploads/default/original/2X/2/21459dffc877378d164e1522830785b066e5bee4.jpeg) ![Screenshot_20260120_165311_Delta Chat](https://support.delta.chat/uploads/default/original/2X/e/e0420380fbeff4c7af6ec8378efb58497e36f909.jpeg) Edit: seems like this is being tackled, thanks! [add api to clear all relay storage · Issue #7730 · chatmail/core · GitHub](https://github.com/chatmail/core/issues/7730) ---
**Author:** ![Alex](https://forum.delta.chat/user_avatar/forum.delta.chat/alex/32/2697_2.png) [@Alex](https://forum.delta.chat/u/Alex)\ **Post date:** [January 28, 2026, 6:49am UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/31 "2026-01-28T06:49:34Z")
Hello! In version 2.35.0, the ability to follow links for www-bots has been broken again. ---
**Author:** ![DELTA\_MAFIA](https://forum.delta.chat/user_avatar/forum.delta.chat/delta_mafia/32/2624_2.png) [@DELTA\_MAFIA](https://forum.delta.chat/u/DELTA_MAFIA)\ **Post date:** [February 9, 2026, 6:56pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/32 "2026-02-09T18:56:37Z")
Who has already discovered that from version 2.40 on Android, if you send a message or file to version 2.35 Desktop, an empty message is sent before the message? 🙃 ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [February 9, 2026, 8:35pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/33 "2026-02-09T20:35:22Z")
when sending an image/file/voice-message/etc. from 2.40, some - as well end-to-end-encrypted - information is sent before the real message. this so called “pre message” can contain message type, text, thumbnail, and allows to target a lot of long standing issues: 1. more reliable notification: a large download does no longer block tiny time window - the big message is downloaded automatically if there is time (already in 2.40) 2. reliable “download on demand” - currently it may happen that the not-downloaded message is assigned to the wrong chat (already in 2.40) 3. offering a download button, while already displaying a thumbnail (not yet in 2.40) unfortunately, this message is visible to 2.35, however, does not cause harm otherwise. we plan to roll out 2.40 even more coordinated, so that one has a chance to update quickly and get rid of the little annoyance. ---
**Author:** ![DELTA\_MAFIA](https://forum.delta.chat/user_avatar/forum.delta.chat/delta_mafia/32/2624_2.png) [@DELTA\_MAFIA](https://forum.delta.chat/u/DELTA_MAFIA)\ **Post date:** [February 13, 2026, 2:03am UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/34 "2026-02-13T02:03:58Z")
Version 2.42. When you open any video, it takes you to the chat desktop, and you can no longer watch videos. Google Pixel 9 ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [October 6, 2026, 9:09pm UTC](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427/35 "2026-10-06T21:09:19Z")
[Previous page](https://forum.delta.chat/t/help-testing-upcoming-delta-chat-2-34-release/4427.md?page=1)