I tried out this version for a little bit, but I’m sorry to say that it didn’t work well for me. It wasn’t a ton of testing as faster movements felt really sluggish to me. I can’t quite put my finger on what was wrong, but after about a minute of it, I decided to downgrade the firmware back. Sorry.
Personally, I think the benefits of 4 still outweigh the new movement and occasional stops and lag timing issues, so I’m very vested in getting 4 to a good point. Happy to test any other staging build!
1 Like
I had a similar issue. When testing an early FW4 version, the slider on my handy was constantly hitting the edges and I think it got loose. Now it makes a pretty loud noise which it didn’t make before FW4. I’d like to know if it’s possible to tighten up the slider in order to fix this issue and make it quiet again.
1 Like
@rubbersexdoll and @colorincho
I HIGHLY recommend you guys to set your handy’s range to anywhere between 2-98 and 5-95, you barely notice the difference but it greatly reduces the risk of your handy breaking itself, I’ve had many many issues with my old devices that i had to get replaced (for free, with no hiccups thanks to warranty, luckily).
I’m trying to get myself in the habit of making 5% the bottom peak of all of my Scripts (I sadly forget it a lot still) just to make sure my scripts don’t break people’s devices.
It happens whenever a stroke is above ~350-400 units/s and hits either the bottom or top with a full range.
Also do not forget to grease the inner screw from time to time
3 Likes
Number 4 is bad luck in chinese culture right? Lets skip to fw5 
Immediately downgraded as soon as it felt off and my scripts weren’t as good anymore.
Yeah, removing features on your firmware that scripts are dependent on like smoothing is a HUGE mistake, especially with all these other stroker toys on the rise. All this does is make past collections of scripts seem worst than intended and add more tedious work to scripting.
Recently my old primordial handy broke and I got a new one and I’m already starting to feel the future regret since It seems like we might be railroaded into this.
As mentioned before you should probably just add the ability to enable and disable it as needed.
1 Like
Needed to downgrade to FW3 yesterday evening, FW4 suddenly stopped working with Faptap and Stash. Connection is made, but not doing any actions 90% of time.
With Faptap, some videos worked, but actions was random (not following videos) for 10 seconds, and then stop.
No issue at all after downgrading for a full hour session.
1 Like
I have to say that its a bad habit to do in scripts. Scripts should be designed without those limitations, because you dont know which device will play them.
If your handy struggles with 0-100, you can always scale it afterward. Those who dont face those issues can still get the max. If you limit it here, then its for everyone and it means that on a lot of devices you are going to miss out up to 10% of the range it can perform.
Especialy with things like the OSR, which has a far bigger move range, setting limitations is mandatory in the first place (going to just 50% is quite normal). Removing the 10% on the script would then mean adjustments are required for these settings to get the full experience, which in this case isnt what you normaly want to do, as this brings the risk of having a misconfiguration on loading the next script, and then potentialy causing damage.
The only reason to use 5-95 as baseline is because it does allow just that little bit of extra flexability when you want to nuance the tip or bottom (like a 0-20 or 80-100 section). 0 and 100 normaly shouldnt be common in a script (unless its a PMV or manualy made script that only uses 11 positions for convenience).
But 0 and 100 must be deemed safe in the script regardless of speed. Its not your task to protect devices, thats up to the user (OSR etc), or device manufacturer (handy/launch etc).
2 Likes
Interesting. I noticed my Handy stopped working yesterday. I thought it was the occasional server instability.
It is an eventually, FW3 & FW4 certainly not using same servers structure.
But for my yesterday session, tried to reconfigure Wifi, made a new connection key, but did not work. Finally decided to downgrade.
1 Like
Absolutely this. FW4 seemingly having a different slider range limit is a baffling issue, particularly when one considers that it’s on established hardware and may have the potential to cause damage.
The problem on that is that tests are still limited. Your test device might only be slightly different, and therefor appear as if it works. Wear over time can also affect a lot of things. And even something like room temperature can matter. There are a lot of factors, and if you want to make the device behave less restricted, you are going to reach limits faster, and in this case, went over it.
Testing isnt free either, a test where you need to run a device for 300h still costs money to do, and especialy when you need several (lets say 20) costs add up rapidly. As note, a test device needs occasional replacement. You cant realy expect them to test all, hence FW4 was released as beta to find issues early.
This is why public tests are often performed, and its then to the users to identify issues. Sadly they didnt provide a standardized test though that can at least ensure you can listen for issues before they happen. (a slow ramp up in speed from 0-100 with some half sections and some vibration sections in between could identify a few basic problems quickly).
A 5min testscript that people can run isnt that strange to have. And potentialy with logging, if any issues show, could be used to figure out where it went wrong. Standardized tests are good because any anomaly can be seen in its logging.
If a device cannot do that, it indicates they did cheap out somewhere. Memory chips arent that expensive that they will add a huge cost to the device. Its not like the device will go from €200 to €300. Its a case of only a few € at best. And with niche devices, margins never are truly small, so those few € generaly shouldnt even be noticed on the total cost.
But hey, its as far as i know their first real mistake, and to be honest, these things can happen even by those who are well prepared. Its murphys law taking place. Even with such test capabilities, im sure some devices would still have broken down.
Does anyone know how I can go to the previous version? Also, my TheHandy is in purple and blue, in handyverse (not on the new page) it tells me that I have version FW 4.0.12-1 and when I update it and it stays loading…, the videos do not they reproduce me
I couldn’t at first, but I was able to put TheHandy with the Handy oneboarding and now it stays purple. With this I can go to firmware 3?