3.4.1.0 Omnipod Dash Bluetooth Problem

[thees]

My Honor 400 Smart (LGN-NX1) did an auto update of their Android Verison and therefore I cannot connect to Dash Pods via bluetooth any longer.

While I am not sure which Android Version it was before, it is now Android 16 in their "Magic OS 10" build number 10.0.0.135 .

I tried an Upgrade to the newest AAPS 3.4.1.0 (23f7) without any success. (Before I had 3.4.0.0 working very well.)

I checked all the know BLE Problems at https://androidaps.readthedocs.io/en/latest/GettingHelp/BluetoothTroubleshooting.html and there is no battery save option or nearby device option set, besides for APPS, "Google" and "Android System Intelligence" active (which I think is still needed, right?)

Bond BT is off.

I have attached a log where I tried to activate a new pod.

a16_honor_BLE_problem.txt

[xitation]

As per that guide, you have allowed all the correct permissions and turned off Battery Optimisation on all the things listed there?

As this section of the setup guide was updated recently and sometime is overlooked - https://androidaps.readthedocs.io/en/latest/SettingUpAaps/SetupWizard.html#setup-wizard-bluetooth-battery-optimisation

[thees]

@xitation yes battery optimization is disabled. There is no battery optimization sceen for bluetooth. However, I checked with adb and set the bluetooth applications manually by:

adb shell "dumpsys deviceidle whitelist +com.hihonor.bluetooth"
adb shell "dumpsys deviceidle whitelist +com.android.bluetooth"

This was not set before.

Need to check now about it. I'll let you know if this works.

[xitation]

Worth also, removing all "Nearby Device" permissions, except for AAPS until you can verify if that helps or not. I know a recent issue someone had left Alexa there which caused their issues. Noting I see you have Google added unsure if you can remove that for a test? The "Nearby Device" thing has been one of the bigger causes of BLE issues for OmniPod, so worth removing everything to see if just AAPS resolves your issue.

[thees]

@xitation unfortunately no luck with all your tips.
I removed all apps from nearby devices permissions but aaps.
And the adb settings did not help either.

[xitation]

Sorry to hear mate, in that case you have exceeded all of our community knowledge on connection issues that is documented.

I don't see your phone in this list - https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true

I guess there is always a nuclear option of factory re-set phone/os and see if anything improves after that. No guarantee that helps... But if you did go that route, install as little as possible to get into a working position then setup AAPS and see if things improve.