Ah, I had a hunch. Almost guessed so. I would stop riding that puck immediately, you’ve got a loose potentiometer and need to fix it. If you continue riding, you run the risk of it breaking mid ride, worse case leading to a full throttle runaway.
It’s a common failure mode for the Hoyt puck, especially if you haven’t reinforced it and/or it’s taken some good smacks with the ground. The solder joints that attach the potentiometer to the PCB get stressed over time, until a lead comes loose and breaks off. Lots of related threads on the forum, ex this one
nbd to repair if you’ve done PCB soldering before, I’ve replaced a bunch of them on my remotes. That said, getting the replacement part is tricky…Hoyt just went out of business. Looks like the website is still up, but I’m not sure they’re still fulfilling orders…rumor is that Hoyt’s stock is going to show up on mboards at some indeterminate point in the future, so maybe you could wait for that.
Alternatively, not saying I recommend this, but you could try re-flowing the joints and reinforcing the pot. Looks like a loose solder joint, not a worn out potentiometer, so that could work. maybe.
Yes, I thought the same thing. Many people around me who use Puck have already reinforced the inside with hot glue or resin. I’ve only used the remote for about 6 months and have only used it about 700km, so I thought it would be okay, but I’ll have to check the condition. As far as I know, it’s vulnerable to dust. Thank you for the information : )
I am out of ideas why the app freezes for you. Do you have a desktop computer / laptop? Can you connect your android phone with a USB cable and collect debug logs? It’s explained very well in this video how to do it:
Once you have your phone connected and adb logs streaming over USB cable, trigger the app freeze and send us the logs.
Following the earlier thread, I also experienced intermittent (unrecoverable) Voyage Connect crashes when tapping [Account] or [Settings]. I’m on a Pixel 7 Pro running Android 15 build BP1A.250305.019.
Next time I use Voyage Connect (still prefer Metr for announcements, etc) and it crashes, I’ll collect debug logs & send them to you.
@rpasichnyk hey guys - today i rode 67km, but only 2/3 of the ride were uploaded. Missing the third one. It did failed to connect to wifi couple times…i received a bunch of Mongo db errors as well. But now, it says it synced it all, but big part of the ride are missing.
So I’m able to see my own logs on the cloud site, but I can’t see anybody else’s logs. Is there a way for me to make my logs viewable by others? So they can see for example where I skated during my skatepacking trip?
That’s not really practical for me, I have multiple days of logs that cumulatively make up the trip I want to share, can I just make them public so others can click on them on the cloud site just as I can click on my own? That way I don’t need to share individual logs.
In the Cloud, the merged ride logs can now be split. This restores the state before merging. A useful feature if you make a mistake. Also, in (the extremely rare ) case there’s a bug in the merge and the merged log is rubbish, you can report it to us and the logs can be re-merged once the bug is fixed.
Thanks for all the improvements you’ve been putting into the new Voyage platform, Jan!!
Perhaps related… The “Parts” menu disappeared from my Metr app a few days ago. What happened to it?
I’m on the Android Metr app v4.29.15 updated on May 22.
I’m about to swap my bald tires & was counting on that menu for lifespan tracking. I rode a bunch of miles since then & am nervous about attempting an old backup in case I mess up my board odometer.
Also - the Voyage app doesn’t meet my needs yet because it’s not currently at feature parity with Metr. I use the “Announce” feature with my helmetcom on every ride to alert me of high speed.
Tagging @poastoast 'cause he feels the pain of missing Parts, too.
Yes, please. I also have an idea how to “partially” restore backups, for example someone might want to just restore “part list” from a given backup, but leave everything else unmodified.
) case there’s a bug in the merge and the merged log is rubbish, you can report it to us and the logs can be re-merged once the bug is fixed.
