Very interesting... almost makes me want to proxy it
Though the real problem imho, is the fact that I do not believe it is possible to initiate a RemoteCare session without an Oticon Pro Account (since the app uses Oticon's cloud services to perform RemoteCare)
It is certainly interesting...
Note: I have heard of some remote fitting types requiring a home programmer (rly dumb imo) but personally I'll be focussing on mobile-powered remote fitting
Specifically Phonak's protocol but it should be interchangeable
My theory is that remote fitting uses the same protocol, or a limited...
Note that this is a bitmask, and since this code is decompiled, it shows as decimal, the RAW bitmask itself, however, would be:
1010000010
Or in hex:
0x282
Edit: my mistake, not a bitmask, but rather, the manufacturer ID must be 0x282
They are filtered through manufacturer data:
,%20byte[])']https://developer.android.com/reference/android/bluetooth/le/ScanFilter.Builder#setManufacturerData(int, byte[], byte[])
new ScanFilter.Builder().setManufacturerData(642, new byte[0]).build()
Regarding HA BLE Scanning
Sonova HAs are scanned in "scan mode 2" (aka: SCAN_MODE_LOW_LATENCY) - https://developer.android.com/reference/android/bluetooth/le/ScanSettings.Builder#setScanMode(int)
new ScanSettings.Builder().setScanMode(2).build();
Ugh, yet another BTC BTLE implementation...
Like many other companies, Sonova has opted to use a packet-response architecture despite using BTLE, which kind of defeats the purpose of BTLE in my opinion...
still better than BT-Classic tho lol
This is a lot of spaghetti....
The app is very... compartmentalised... many subsections which I'll need to look through lol
I do know that com.sonova.mobilesdk seems to handle scanning for HAs