[Bug]:Version 2.8.0 fdroid crashes randomly on Android 11

[ccchdro]

Contact Details

ccchdro@gmail.com

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.8.0 fdroid

Affected Android version

Android 11

Affected phone model

Samsung

Affected node model

Heltec T190

Affected node firmware version

2.7.26.54e0d8d Beta

Steps to reproduce the bug

The application no longer communicates with the node and crashes randomly the only solution is to force close it after which it works normally again

Actual behavior

No response

Expected behavior

No response

Screenshots/Screen recordings

No response

Relevant log output

===== App Logcat =====
--------- beginning of main
07-28 16:59:12.615 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:14.616 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:16.617 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:18.618 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:20.620 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:22.623 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:24.624 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:26.625 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:28.627 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:30.628 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:32.631 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:34.632 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:36.634 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:38.635 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:40.636 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:42.639 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:44.640 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:46.641 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:48.643 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:50.645 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:52.647 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:54.649 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:56.651 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 16:59:57.916 I/geeksville.mes(11483): Background young concurrent copying GC freed 498660(17MB) AllocSpace objects, 0(0B) LOS objects, 35% free, 28MB/43MB, paused 640us total 310.028ms
07-28 16:59:58.653 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:00.656 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:02.658 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:04.661 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:06.663 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:08.666 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:10.668 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:12.671 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:14.673 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:16.675 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:18.678 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:20.680 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:22.682 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:24.685 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:26.687 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:28.688 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:30.690 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:32.692 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:34.695 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:36.697 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:38.700 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:40.702 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:42.704 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:44.707 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:46.709 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:48.711 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:50.713 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:52.715 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:54.717 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:56.719 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:00:58.720 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:00.722 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:02.725 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:04.727 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:06.730 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:08.732 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:10.161 I/        (11483): Starting MeshService (trigger=UserInterface, appInForeground=true)
07-28 17:01:10.218 W/Adreno-EGL(11483): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-28 17:01:10.350 I/        (11483): MeshService: selected device ready (...:05), staying foreground
07-28 17:01:10.620 I/geeksville.mes(11483): WaitForGcToComplete blocked Background on ProfileSaver for 18.280ms
07-28 17:01:10.733 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:10.800 I/geeksville.mes(11483): Background young concurrent copying GC freed 463264(16MB) AllocSpace objects, 9(196KB) LOS objects, 38% free, 26MB/43MB, paused 213us total 177.886ms
07-28 17:01:12.733 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:14.734 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:16.735 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:16.933 I/geeksville.mes(11483): Background young concurrent copying GC freed 246294(12MB) AllocSpace objects, 0(0B) LOS objects, 21% free, 34MB/43MB, paused 244us total 255.523ms
07-28 17:01:17.884 I/geeksville.mes(11483): Background concurrent copying GC freed 455837(29MB) AllocSpace objects, 3(208KB) LOS objects, 50% free, 19MB/39MB, paused 183us total 466.003ms
07-28 17:01:18.736 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:19.101 I/geeksville.mes(11483): Background young concurrent copying GC freed 325558(21MB) AllocSpace objects, 0(0B) LOS objects, 51% free, 19MB/39MB, paused 244us total 194.213ms
07-28 17:01:20.288 I/geeksville.mes(11483): Background young concurrent copying GC freed 307415(20MB) AllocSpace objects, 0(0B) LOS objects, 48% free, 20MB/39MB, paused 183us total 189.819ms
07-28 17:01:20.737 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:21.725 W/Adreno-EGL(11483): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-28 17:01:22.597 D/OpenGLRenderer(11483): endAllActiveAnimators on 0xa715c8d0 (UnprojectedRipple) with handle 0x7bb949d0
07-28 17:01:22.737 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:24.738 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:26.739 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:28.740 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:30.741 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:32.741 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:34.742 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:36.743 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:37.623 W/Choreographer(11483): Frame time is 0.225077 ms in the future!  Check that graphics HAL is generating vsync timestamps using the correct timebase.
07-28 17:01:38.744 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:40.745 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:42.747 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:44.748 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:46.749 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:48.750 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:50.642 I/geeksville.mes(11483): Background young concurrent copying GC freed 505086(18MB) AllocSpace objects, 13(308KB) LOS objects, 45% free, 21MB/39MB, paused 244us total 247.192ms
07-28 17:01:50.751 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:52.261 D/WM-DelayedWorkTracker(11483): Scheduling work ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4
07-28 17:01:52.262 D/WM-GreedyScheduler(11483): Starting work for ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4
07-28 17:01:52.283 D/WM-Processor(11483): Processor: processing WorkGenerationalId(workSpecId=ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4, generation=0)
07-28 17:01:52.342 D/WM-WorkerWrapper(11483): Starting work for org.meshtastic.core.service.worker.MeshLogCleanupWorker
07-28 17:01:52.348 I/meshlog_cleanup_worker(11483): Successfully cleaned old MeshLog entries
07-28 17:01:52.363 I/WM-WorkerWrapper(11483): Worker result SUCCESS for Work [ id=ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4, tags={ org.meshtastic.core.service.worker.MeshLogCleanupWorker } ]
07-28 17:01:52.409 D/WM-Processor(11483): Processor ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4 executed; reschedule = false
07-28 17:01:52.431 D/WM-GreedyScheduler(11483): Cancelling work ID ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4
07-28 17:01:52.477 D/WM-SystemJobScheduler(11483): Scheduling work ID ec3d0485-53ab-40f6-a8d1-7f3cd1ea65b4Job ID 8
07-28 17:01:52.753 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:54.754 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:56.755 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:01:58.756 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:00.758 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:02.760 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:04.762 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:06.765 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:08.766 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:10.769 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:12.772 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:14.774 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:16.775 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:18.777 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:20.779 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:22.780 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:24.783 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:26.785 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:28.786 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:30.787 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:32.789 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:34.791 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:35.434 I/        (11483): Starting MeshService (trigger=UserInterface, appInForeground=true)
07-28 17:02:35.658 W/Adreno-EGL(11483): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-28 17:02:35.863 I/        (11483): MeshService: selected device ready (...:05), staying foreground
07-28 17:02:35.869 I/        (11483): [FW_CHECK] Firmware version comparison - device: DeviceVersion(asString=2.7.26.54e0d8d) (raw: 2.7.26.54e0d8d), status: OK, absoluteMin: DeviceVersion(asString=2.3.15), min: DeviceVersion(asString=2.5.14)
07-28 17:02:35.869 I/        (11483): [FW_CHECK] Firmware version OK - device: DeviceVersion(asString=2.7.26.54e0d8d) meets requirements
07-28 17:02:36.228 I/geeksville.mes(11483): Background young concurrent copying GC freed 392435(14MB) AllocSpace objects, 13(512KB) LOS objects, 31% free, 27MB/39MB, paused 335us total 252.349ms
07-28 17:02:36.793 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:38.794 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:38.941 I/        (11483): Stopping location requests
07-28 17:02:38.941 I/        (11483): Stopping location requests
07-28 17:02:39.014 I/        (11483): Starting location updates with [gps, network] intervalMs=30000 and minDistanceM=0.0
07-28 17:02:40.794 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:42.795 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:44.796 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:46.796 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:48.797 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:50.798 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:52.798 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:54.800 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:55.918 I/geeksville.mes(11483): Background young concurrent copying GC freed 261533(10049KB) AllocSpace objects, 7(228KB) LOS objects, 26% free, 28MB/39MB, paused 1.251ms total 397.827ms
07-28 17:02:56.800 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:02:58.801 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused
07-28 17:03:00.801 E/geeksville.mes(11483): failed to connect to jdwp control socket: Connection refused

Additional information

No response

[kd2var]

@jamesarich

I may be experiencing the same issue described here. I wanted to add some additional testing information.

I am testing the current Meshtastic Android snapshot build (from main) and I am seeing a similar stale connection behavior:

The app UI remains responsive.
The node stops updating.
The app continues to show the node as connected.
Disconnecting from the node is not possible.
Force stopping and reopening the Meshtastic app clears the stale connection and restores normal operation.

My environment:

Android version: 16
Phone: Samsung Galaxy A15 5G
Node: Heltec V3
Firmware: 2.7.26
Android app: current snapshot build

I initially suspected this may have been related to my custom TCP/WiFi bridge, but I reproduced the same behavior using a direct Bluetooth connection.
I also previously mentioned this behavior while testing the Mesh-to-CoT enhancement (#6416), where the Mesh-to-CoT functionality itself was working correctly. The additional details are in my comments there.

Not sure if this is the same underlying issue, but I wanted to provide another data point.

[kd2var]

@jamesarich the connection went stale again with the same symptoms and fix required even running the snapshot build with the fix in it. This time it was running for over 24 hours without any issues before it happened which is longer than in the past so it may just be an isolated case. I will continue to test and let you know if it happens again.

[ccchdro]

@jamesarich the connection went stale again with the same symptoms and fix required even running the snapshot build with the fix in it. This time it was running for over 24 hours without any issues before it happened which is longer than in the past so it may just be an isolated case. I will continue to test and let you know if it happens again.

kd2var is not something isolated, sometimes it works fine without problems, other times it crashes every few hours, 2.7.14 works without any problems.

[kd2var]

@jamesarich the connection went stale again with the same symptoms and fix required even running the snapshot build with the fix in it. This time it was running for over 24 hours without any issues before it happened which is longer than in the past so it may just be an isolated case. I will continue to test and let you know if it happens again.

kd2var is not something isolated, sometimes it works fine without problems, other times it crashes every few hours, 2.7.14 works without any problems.

Yes, I know that 2.7.14 worked without problems and the issue appeared in 2.8.0 but there was a fix that was put into a snapshot debug build that I tested and it worked fine for 24 hours which is longer that it would previously but then the issue happened again. I was just letting the developer know that the issue is still present.

[kd2var]

@jamesarich Additional testing update after the stale connection fix was merged.

I am testing the latest snapshot build containing the fix from this issue. I was able to reproduce another stale connection condition, although this appears to be a different failure path than the original report.

This time the failure occurred much sooner. The connection appeared to be working normally. I opened the Connections tab and then the Node List tab and noticed the node database information was no longer available.

Observed behavior:
The Meshtastic UI remained responsive (the app itself was not frozen).
The entire node list became blank; all nodes disappeared from the list.
Reloading/refreshing the node list did not repopulate the nodes.
The connection state appeared to be stuck.
Force stopping and reopening Meshtastic was required to restore normal operation.

Additional details:
Latest snapshot build containing the previous stale connection fix.
Bluetooth connection.
TAK server was running during this test.
ATAK was not required to reproduce the issue.

The captured log shows repeated Room database errors while this was occurring:

meshtastic_logcat_20260808_043347 2.txt

android.database.SQLException: Error code: 5, message: Timed out attempting to acquire a reader connection

I do not know if this is related to the recent TAK/database changes, but I wanted to include that detail because the TAK server was active during this reproduction.

Full log attached.

[kd2var]

Some more testing info I noticed it in a frozen state when I checked it this morning but was unable to get log info. It happened just now again and I was able to get logs which are attached. When it happened this most recent time I shut Bluetooth off on the phone and the node disconnected however when I turned Bluetooth back on it got stuck in a reconnecting state and I had to force stop the app to get it to recover.

meshtastic_logcat_20260808_150604.txt

[kd2var]

@jamesarich I reproduced the same issue on my tablet with 2.8.1 debug snapshot. It appears to be the same errors in the log. The full log is attached.

meshtastic_logcat_20260809_163600.txt

[kd2var]

@jamesarich I noticed something while testing the snapshot debug build. Leak detection runs after every force stop/restart of the app. The reported leak count increases by exactly one each time (started at 1, currently at 22 after 22 restarts).
The report points to SystemJobService / ResourcesImpl.mAppContext through WorkManager. I do not know if this is related to the stale connection issue or just debug leak reporting, but it appears reproducible. Attached is a photo of the same result I get every time it runs

[kd2var]

@ccchdro Did you install the prerelease snapshot APK with the stale connection fix included? If so, are you still experiencing the stale connection issue?
I am still seeing the issue after the fix was included, so I’m trying to determine if we are seeing the same behavior or if there is another condition involved. One difference I’m investigating in my setup is the built-in TAK server, so I was curious if you are also using it.

[ccchdro]

@ccchdro Did you install the prerelease snapshot APK with the stale connection fix included? If so, are you still experiencing the stale connection issue? I am still seeing the issue after the fix was included, so I’m trying to determine if we are seeing the same behavior or if there is another condition involved. One difference I’m investigating in my setup is the built-in TAK server, so I was curious if you are also using it.

I'm currently using 2.8.1 (29321777) and it seems to be working fine for 2 days and hasn't crashed. It seems to have a lag at times where previous versions crashed but it gets over it and doesn't crash, i'll see in time.

[kd2var]

@ccchdro can you toggle the built in TAK server on in settings and see if the stale connection returns because I think that me be contributing to me still getting the stale connection issue.