OW Bluetooth connection broken on Android 8.0.0 ('Oreo').
-
tl;dr: Android 8.0.0 ('Oreo') breaks connectivity with Onewheel+ (and presumably Onewheel as well).
Details: I work at Google and installed Oreo on my Nexus 5X as part of an internal effort to find critical issues before general public release. AFAICT, Android's Bluetooth code was updated to be more compliant w.r.t. the specification, but causes it to ignore some BT devices that send a too-long data advertisement packet (zero-padded). Apparently this is common enough that a fix has been patched into AOSP (https://goo.gl/q2dQsL) to be more tolerant of such malformed packets, but it's not part of the initial release and will take time to get into an OTA update. Those with a Nexus or Pixel phone -- which get updates directly from Google -- are the most likely to be affected. Future Motion would need to push a firmware update to fix this, so a quick fix from them is also unlikely.
-
(I already emailed support to let them know about the issue.)
-
Looks like people were way ahead of me.
-
Thanks for heads up.
My Pixel has not updated yet, so I'll wait for the fix.
-
@SeeTheInvisible . . .
-
So the first Oreo developer preview released in March with updates in May, June, and July. How is it possible FutureMotion pushed the Andromeda firmware update in mid-August without testing the Bluetooth connectivity on this build?
Is this the reason FM released the iOS version first and then only subsequently released the Android version immediately after with the customer outrage as the catalyst?
-
@heyitsme Android has always been an afterthought for FM. As you say, they had an eternity to test, and I wouldn't be surprised if it never even occurred to them.
-
Bumping this thread, because this is important, and I think the updates are starting to roll out to the general public.
-
Oops, I discovered this thread after updating and finding it not working...
-
@alexyoung I did the same, oops! I guess now we wait? Does anyone know if FM is working on an update??
-
They say it's Google:
”Hi Alex,
Thanks so much for your note. We checked in with our app engineers and were able to confirm this is something on Google's side that they are looking into fixing. In the mean time, I would recommend using another device if possible.
My sincere apologies for the inconvenience.
All the best,
OW Team "
-
I got same reply from onewheel support as @alexyoung above.
I dont have another device to connect with though :/
-
if the OW is putting out malformed packets, how is it Google's problem? this makes no sense... this is really problematic.
-
@denverrider27 said in OW Bluetooth connection broken on Android 8.0.0 ('Oreo').:
I got same reply from onewheel support as @alexyoung above.
I dont have another device to connect with though :/
If you search the Facebook group people have posted up the smallest devices that can independently run the OW app for Android. There is a small phone like device and someone even found a watch size device. I can look later if you don't find them.
-
So yesterday I went on my board, and when trying to connect, it gave me a warning about Android Oreo having difficultly connecting, but gave me the option to try and connect anyway. Low and behold...it connected! I'm running a Google Nexus 5X. I am coming from the same issue everyone else had. Dunno if someone did a fix, but it seems to work for me now.
