Thread by @buttplugio

Finally giving up on my hopes of doing a max 2 unboxing video in order to figure out the lovense firmware issues in buttplug. :|

Ok. Max 2 firmware upgraded, at v213, and... it works fine in Chrome Buttplug Playground?

Ok, well, if someone that's been having problems with Lovense toys and Buttplug is around, please feel free to DM or hmu on the Discord server (discord.buttplug.io). Things seem to work fine for me.

I fucking miss the old days of being able to just go "Hey does anyone in my local geographic region have [insert sex toy here] if so let's meet up so I can debug my sex toy control code" like a fucking normal person instead of this remote COVID shit.

Ok to everyone who's like "why not just buy the toy yourself"

LISTEN

Do you know how many sex toys I have and how many sex toy usable areas on the human body there are?

My ratio is already WAY out of whack and I don't need it to continue in that direction.

You might think it's fun to buy YET ANOTHER $100 buttplug because "oh they changed the firmware loading mechanism", but no.

It is not.

Does anyone in the San Francisco Bay Area have a new-ish Lovense sex toy (Either purchased in the past month or with recently loaded firmware) they could come hold against my car window while I do some quick bluetooth traces?

Just tell the passers-by that its exactly what it looks like.

Two normal people doing normal sex toy reverse engineering on a normal monday night in a COVID-19 safe way.

Yes you can just duct-tape the sex toy to my car window and go back in your house.

I'm super ADD tho so I may drive off with it taped to my car but I will totally come back with it if I do that.

They're pretty aerodynamic so hopefully it won't fall off while I'm driving.

If it does fall off I'll totally dust it off before giving it back though.

Least I can do.

Listen I'm seeing a lot of likes and retweets and not nearly enough "Here is my home address, so you can drive over and I can walk out and tape a bluetooth buttplug to your car window" DMs.

To tell the truth, it's more than a little frustrating.

You realize there are people out there that would spend good money for this opportunity?

For anyone that's curious about the ongoing saga of buttplug debugging:

What I think we're seeing is github.com/buttplugio/but… again.

I've tried a new Hush and a Max 2 on desktop, they're fine. They also work ok on WebBLE on iOS (Yes, iOS has a polyfilled WebBluetooth impl! apps.apple.com/us/app/webble/…).

But on Android, Lovense devices just don't show up when using the web based Buttplug in the Chrome browser.

Non-lovense toys still work, so what I'm guessing is that our wildcard search for Lovense names may be causing problems.

Most toys have static names (i.e. Fleshlight Launch is just "Launch", ALL vibratissimo toys are just "Vibratissimo", etc).

Lovense is different.

Lovense is "LVS-[ToyName][FirmwareVersion]" for newer toys.

Older toys used [ToyIdentifier] (not name), see stpihkal.docs.buttplug.io/hardware/loven… for more info.

Since we don't want to change our configs for all firmware version, we just use "LVS-*" in our WebBluetooth filter.

That's the only major difference in toy connections between Lovense and everything else, but I'll still need to do some chrome remote debugging and see what's up.

More info as I figure this shit out.

It's an Android Chrome bug! As of Chrome 81, there is a bug in picking up the namePrefix block of WebBluetooth requestDevice() calls! Here's the relevant bug report for those that are interested:

bugs.chromium.org/p/chromium/iss…

There are few things as fun as sending teams completely serious bug reports filled with tons of bluetooth sex toy names.

Every so often I do miss being a browser dev (for those not aware, I'm an ex-Mozilla Firefox platform dev), kinda sorta a little bit.

Though the fact I can just report this and don't have to touch JNI/Java myself is definitely a plus.

https://twitter.com/reillyeon/status/1298337188724084737

Anyways, to finish this out: The fix for now will probably be to agent detect Android in buttplug-js, and use acceptAllDevices while still passing Lovense UUIDs to optionalServices.

This means the user doesn't get a name filter, but it'll do until a fix lands in Chrome Stable.

I'm testing this on @glitch now, and will release buttplug-js v0.13.2 later this week if that works out.

Note that any app that doesn't update will be broken until the Chrome fix, which should just make everything work again, but may be weeks/months out due to release trains.

@glitch And thus ends this thread, with buttplug-js 0.13.2 released.

We now return you to your regularly scheduled buttplugs.

https://twitter.com/buttplugio/status/1298471458658689025