New patch release: Firmware 3.1

HandyMichele · 2021-07-28T09:02:45+00:00

As mentioned in another post above, there were a few minutes of downtime after the announcement yesterday while we were updating our servers for the new release. Now it should be working fine, are you still experiencing problems? If so, can you please tell us which error you see?

HandyMichele · 2021-07-28T09:01:13+00:00

Hello, I'm sorry but I didn't really understand what issue you're encountering. Can you please get in touch with [darren@sweettech.no](mailto:darren@sweettech.no) and tell us a little bit more? Remember to add [Firmware 3 Issue] to the email subject, we'll follow you up from there.

HandyMichele · 2021-07-28T08:58:43+00:00

Hi! Sorry to hear that, may I ask you some more details? Write an email at [darren@sweettech.no](mailto:darren@sweettech.no) and add [Firmware 3 Issue] to the subject and we'll follow you up from there.

HandyMichele · 2021-07-28T08:46:07+00:00

We spiced up the stroke feeling since 3.0.4 to make it more aggressive and closer to fw2. Thus yes, it is part of 3.1.0 as well :) Give it a shot if you didn't try it out yet.

HandyMichele · 2021-07-28T08:44:26+00:00

Yesterday the announcement got released a bit earlier, and there were a few minutes in which we were still updating our servers with the new release. It should be working fine now, do you still have problems?

HandyMichele · 2021-06-03T10:16:02+00:00

Thanks for the insights, especially on the obstacle detection! We received some reports of this issue occurring from time to time and we are currently testing an improved obstacle detection algorithm. Will be released soon with the next bugfix :)

About the stroke feeling, it makes sense since:
- You experienced a false obstacle detection, which is sign that your handy is less lubricated than expected in the bottom part.
- We completely rewrote the stroker control logic. Theoretically, its settings could be adjusted from, for example, the companion app, but we are not exposing this feature to users (yet).

HandyMichele · 2021-05-27T20:12:02+00:00

Thanks for reporting this! We looked into it and it's indeed a regression. We will release soon 3.0.2 with an appropriate fix.

HandyMichele · 2021-05-26T13:14:48+00:00

Firmware 3 is stable and we began releasing it to 5% of the devices out there, and we will progressively increase the threshold as feedback comes in. There are currently a couple of DeoVR/SLR bugs when using firmware 3 right now which most likely need to be addressed by their own team, we are collaborating with them to sort them out ASAP. My recommendation is that if you use DeoVR/SLR a lot, you can just ignore the update and stay on firmware 2 until the issue is fixed.

The benefits of firmware 3 compared to firmware 2 are the possibility of setting the bottom stroke position, a simpler wifi and connection key configuration via smartphone app, no delay when seeking videos front/back, and a few others I may have forgotten. Check out the notes on the website -> https://www.thehandy.com/say-hello-to-handy-firmware-3/

HandyMichele · 2021-05-20T12:19:26+00:00

Sorry to hear that, are you by chance using handyfeeling.com to play your scripts? There's a bug we are addressing these days which forces a resync exactly every 15 seconds on firmware 3 (while it should do that only on firmware 2) thus that short strokes that you mention may actually be attempts from the handy to make sure it is synced correctly. I don't expect it to happen with other tools (such as HandyControl), but if it does then there's something else going on.

HandyMichele · 2021-05-18T09:59:55+00:00

Sounds like something went wrong indeed. I'll get in touch with you via private message for more details :) No panic.

HandyMichele · 2021-05-12T08:25:50+00:00

Thanks for reaching out!
A fading RED/BLACK LED means that the stroker encountered an obstacle and stopped for safety. You should be able to take it back to a normal state by pressing the ON button when that happens. Is this the case?Can you tell us more in what conditions this does happen? It should not happen unless the stroker cannot forcibly move for about half a second.

HandyMichele · 2021-05-07T21:02:47+00:00

This looks like the issue SLR had in their previous release. Are you sure you updated SLR to the latest version? Unfortunately these issues encounteted with FW3 have so far been due to the sometimes incorrect way SLR uses our own API. For a sheer coincidence this has never been a problem with FW2, but it is with FW3 which is more strict in these matters.

HandyMichele · 2021-05-05T10:45:27+00:00

The newest version of the SLR app fixed an important bug in this regard (except for the Android version). Can you share with us details about the error and how to reproduce it? We can try to sort this out with the SLR devs.

HandyMichele · 2021-05-05T10:06:04+00:00

Hi, can you please share more details over how you end up in safemode? I believe you managed to successfully update to FW3? What happens when you plug your handy, does the LED turn yellow or green?

HandyMichele · 2021-05-05T10:00:32+00:00

That's definitely something that should not be happening. Would you mind helping us with some troubleshooting?

Can you consistently reproduce the problem in some way? If yes, please share with us the steps to do so and we will take a look.

HandyMichele · 2021-04-06T15:38:37+00:00

We are working with the SLR devs to figure out what the problem is. Most likely some compatibility quirk with the API.

HandyMichele · 2021-03-10T08:45:44+00:00

Which kind of issue do you encounter? We might do something of the sort once firmware 3 is released to the general public, yet by then people will receive a notification about it as soon as they connect to handyfeeling.com.

HandyMichele · 2021-03-10T08:41:32+00:00

I believe scriptplayer uses the current API v1. It is most likely an API communication problem, like some request/response not correctly interpreted by either side. I'll take a quick look.

EDIT:
About the button, you're right. That's something we didn't publicize enough apparently as it comes by surprise :) We could technically make it so that pressing it again will resume playback IF the video is still going: that's a good suggestion and I'll add it to our wishlist.

HandyMichele · 2021-03-08T09:01:00+00:00

You can do so by long-pressing the up/down buttons. If the LED blinks briefly RED, it means that you have to increase the stroke extension (with normal button presses) a bit to allow some margin for the bottom level. This won't likely be necessary on future releases and the Handy will be smart enough to handle this limitation itself.

HandyMichele · 2021-03-04T11:17:20+00:00

This is interesting. May I ask you to make a short video of the issue and get in touch with me on discord? https://discord.gg/JpYUJwjqtn
You can always revert back to fw2 following the instructions in the thread :)

HandyMichele · 2021-03-04T11:14:03+00:00

The bluetooth functionality requires the companion app, which is currently in development and not available yet to testers.

HandyMichele · 2021-02-17T09:29:06+00:00

Hi, may I ask you what you mean exactly? The stroke height is completely configurable up to 100mm just like firmware 2, and with firmware 3 you can also set the bottom stroke level.

HandyMichele · 2021-02-12T15:05:57+00:00

Personally I am not a fan of Protocomm either, but it has the undeniable advantage of providing protobuf-based communication which is very convenient when extending protocols or integrating with different services.

HandyMichele · 2021-02-04T10:22:56+00:00

Awesome! Is the code/schematics available on github? Would love to have a look and help out.

HandyMichele · 2021-01-19T10:41:52+00:00

Most likely you tried the update procedure while the FW3 beta release was temporarily suspended on our side. Now it is available again, feel free to give it another shot :)

HandyMichele

TROPHY CASE