PUMP UNREACHABLE - Pod fails to connect after successful activation in middle of active session

Reporting bugs

• The iasue ia happening on following setups
• my setup - Samsung galaxy z fold 5, android 16, AAPS 3.4.0.0, BYODA, Omnipod Dash
• my daughter - Google pixel 9a, android 16, AAPS 3.4.0.0, BYODA, Omnipod Dash.
• After successful activation of the pod, in middle of the active session, we get alert on phone saying "Pump Unreachable" and pod starts giving the "continueous beep sound". Sometimes I have observed "COMMUNICATION_ERROR" in Pod status. The only way out from here is to deactivate the pod / descard the pod. I have tried all the solutions provided by other users in AAPS Users fb group and in issue #4464

AAPS 3.4.0.0
Build: 796d36ef0d-2026.01.06
Remote: https://github.com/nightscout/AndroidAPS
Flavor: fullrelease
Nightscout version: 15.0.2

AndroidAPS_LOG_1769709211581.log.zip

• Obtain the app's log files, which can be found on the phone in
  /storage/emulated/0/Android/data/info.nightscout.androidaps/
  See https://wiki.aaps.app/en/latest/GettingHelp/AccessingLogFiles.html
• Open an issue at https://github.com/nightscout/AndroidAPS/issues/new

Start by reviewing the attached AndroidAPS log and the related discussion in issue #4464, focusing on the transition from successful pod activation to the "Pump Unreachable" or "COMMUNICATION_ERROR" alert. Compare the Samsung Galaxy Z Fold 5 and Google Pixel 9a reports; done means identifying a supported reproduction or likely cause and verifying a fix against the reported pod-session failure.