Same issue on android 12 for me.
Connected and not connected in the same time.
Reconnecting by bluetooth does not help.
Temporary fixes by powercycling orba2, but happens again in several minutes.
firmware 1.0.11, app 1.0.146
If you are running Android 13, know we are working with Google on a fix. Several tech companies that use MIDI over BLE (including us) are experiencing these issues. I know this is frustrating. It is to us as well but we are working on solutions as quickly as possible.
Hello! Is there any updates on this issue? Samsung Galaxy S22 Ultra also.
Thank you!
@Britt: I'm hoping the fix will be quick because it's 5 months since I first reported this issue.
I wouldn't see this fixed having Android 14 on my phone...
We're seeing some positive results with the latest Android Beta. If you have a newer Pixel phone, you can see if you have an update waiting for the Android 13 OS.
Colin, in the meantime you can connect to Android devices via USB.
And it still doesn't work on android 14.
Maybe its time to provide an super flexy long usb cable with the orba free of charge.
>>Maybe its time to provide an super flexy long usb cable with the orba free of charge.
gold
@Britt: 8 months ago you wrote "We're seeing some positive results with the latest Android Beta". And...?
Giuseppe Cervino
I had BT connection problems with my Galaxy S22 Ultra with Android 13 from the start: it gave continuous errors and now, after the last upgrade (Firmware 1.0.10, App 1.0.104), my Orba 2 at first seems to connect but eventually not (screenshots attached).
I allowed all the permissions the app asked for, Location services included.
The USB connection with the smartphone seems to work fine so it should definitely be a BT/Android (or Galaxy?) problem.
Any suggestions or same troubles?
THX
Giuseppe
2 people like this idea