I noticed that my Handy was struggling to reach full length and especially to push the sleeve down onto my anatomy. Purchasing the industrial lubricant mentioned here on EroScripts as the best for the Handy and applying it brought new life to my Handy. Longer strokes, deeper movement, and less heat. The last is of particular importance talking about FW3 versus FW4, since FW4 has an earlier cutoff for overheating.
I use lubricants too on a regular basis, and the differences are still there between the 2 FWs.
But i guess you raise a point there, though.
im liking fw4 so far, no more delay, just instant script.
can you link it or name it? I had to completely tear apart my handy to clean it up because it stopped working, but now it’s noisier and heats up faster
This is what was recommended in another thread on this forum. There were other options for other countries, so you may want to search.
1 Like
Am I the only one that has been experiencing odd errors between both FW3 and FW4 where my device seems to get in an unknowable state and I’ll have to reconnect using HandyOnboarding but when connecting, it says something along the lines of the device is on both and to choose either FW3 or FW4 to connect, and it gives an error about RPC (I think?) timeout? This happens a few times every couple of weeks.
I have not seen anything like that. My thought would be to do a factory reset and re-apply the latest firmware.
I’m on FW 4.0.18+cba495e6 and can’t seem to downgrade? Yellow led does not light up when powering the handy on with the action button held down even for prolonged time (up to 30 sec). Anyone came across this type of issue? I have tried reconfiguring the wifi settings and factory resetting the device but no luck so far.
Edit: Nevermind, here’s the direct link for folks with same issue in the future: Handyverse
I’ve been using ScriptPlayer 1.2.2 for quite some time now, and as the network settings and such are stable, I haven’t touched it. It started crashing simply when connecting to Handy, so I could only think of the firewall and tried to downgrade, but couldn’t. This is extremely troublesome.
I’m having the same problem after the last huge windows upgrade.
I don’t think anything changed on the side of the API.
It seems it can’t deserialize the response for setting the mode in the API. I fixed it locally by adding a class to deserialize into instead of just trying to deserialize it into a string. The ScriptPlayer doesn’t even really do anything with that response as far as I can see.
I open a pull request on github and it’s already merged. You can download the beta version with the bugfix here: Downloading Beta Builds · FredTungsten/ScriptPlayer Wiki · GitHub
1 Like
I included @HornyTomcat’s fix in pre-release 1.2.3:
2 Likes
Was it that Windows Update again!
Thank you for letting me know about the ScriptPlayer 1.2.3 debug version.
In case it stops working again: I’ve added a new version 1.2.3.464 which undoes yesterdays fix.
I think they changed the API or something …
1 Like
Yeah. It seems the /mode endpoint is deprecated and there is a new /mode2 endpoint. (Handy Rest API v3 - Swagger UI)
According to the docs the /mode endpoint should still be there for backwards compatibility reasons but it seems it now gives the same response as /mode2.
Before it was just “ok”.
@Liquid I opened a new PR for using the new endpoint. I think the new endpoint should keep working, while the old one got reverted to the response it was before. I assume the initial change in the API was an error because it should have been backwards compatible. But for now it seems to work. So your judgement if you want to update the pre-release.
Update:
Eh.. the build somehow fails, while it worked locally. I’ll have a look.
Our bad! We accedently pushed out a change on the response to the mode change. It is reverted back. If you want to use the new one you will have to use the second mode change endpoint.
4 Likes
Are you guys using Bluetooth on the latest firmware for The Handy? I’m having all kinds of issues with Wi-Fi. With some SLR videos, the script stops, and I have to pause and play to get it working again. Bluetooth seems to resolve the issue, but I thought Bluetooth had higher latency compared to Wi-Fi.
I assume its related to FW4. Running 4.0.18+cba495e6 atm, and have experienced the last month that faptap.net videos start off fine, but then an indefinite handy logo starts loading over the video, and the handy stops.
I also have the same issue that the script will stop moving sometimes when i use wifi mode. Don’t know what’s the problem. But the new Bluetooth mode is better now. The new Bluetooth mode (dark blue light on the handy) is not the legacy blue tooth mode (light blue light on the handy). It will not stutter when playing fast scripts. As I know, there is only one player support the new Bluetooth mode called syncopathy. You can find it on this community by search “syncopathy”.
im going back to 3, the bluetooth has some latency issue, very noticeable
Anyone else having issues upgrading to v4.1 on the Handy 2? Mine fails most of the times, and when I get it to update to 100%, after a restart it says it’s still locked on 4.0.16-13.local+ef44b67d. WTF
Update: managed to “downgrade” it to 4.0.15+d982fe53, and then retry. Still stuck throwing errors and behaving exactly as 4.0.16-13.local+ef44b67d - can’t upgrade.
4.0.18+cba495e6doesn’t work4.1.0+16bc633bdoesn’t work
The device sometimes reboots on its own right after displaying the 00 percentage when first starting to process the download, and other times, when it finally kicks in and downloads the firmware, it will reach 100%, flash the red LED, and turn itself off.
I also tried applying the update via safemode. It takes half the usual time to process the update, then flash yellow/green, but after booting normally it will display the old firmware instead of the new one.
What the hell am I doing wrong?