2 ms·
I had exactly the same experience. Android's Bluetooth stack is shockingly bad. They even changed implementation once (from the standard Linux Bluez stack to so
by IshKebab 7y ago
I had exactly the same experience. Android's Bluetooth stack is shockingly bad. They even changed implementation once (from the standard Linux Bluez stack to some other one). Just as bad, if not worse.
One example: Until very recently the default connection timeout was 20 seconds. There was no way to change it. 20 seconds! Such a shockingly bad user experience. The default on iOS is something like 0.7 seconds.
Several years after reporting this issue they "fixed" it - by changing the hard-coded timeout to 5 seconds. Like, yeah that's better I guess, but I think you're missing the point.
Just in general Android's bluetooth stack was way buggier and less reliable than iOS's. There were entire classes of products (mostly proximity-based stuff) that we tried to make that worked perfectly on iOS but were effectively impossible on Android because it was so janky.