cstimer
cstimer copied to clipboard
356i sync issues
Once I'm able to get my 356i to sync with the app (often takes several reloads of the page for some reason) I'm then able to get a single scramble and solve to work.
After the first solve though, the virtual cube stops responding to my cube. If there's some sort of reset button I need to push or some such I haven't been able to find one that works.
Thanks a ton for getting this programmed in so fast though! I'd much rather use your excellent app than the native one that Gan put out. (I'm a Roux solver so....)
Is there any bug reported in the console (Opened by pressing F12)?
Sorry haven't done any phone dev, though I am a software engineer and will be happy to help if I'm able. I've been trying to figure out how to get a keyboard to show up while viewing your page on my phone, or some other way to open the debug console. I did finally get the keyboard up, by clicking on a time recorded in a session and clicking the comment text box, but when I then hit the F12 key nothing seems to happen.
Sorry haven't done any phone dev, though I am a software engineer and will be happy to help if I'm able. I've been trying to figure out how to get a keyboard to show up while viewing your page on my phone, or some other way to open the debug console. I did finally get the keyboard up, by clicking on a time recorded in a session and clicking the comment text box, but when I then hit the F12 key nothing seems to happen.
Well, I have never use a smartphone to connect with gan356i. Are you able to use a laptop with bluetooth to connect with gan356i and reproduce the bug?
Unfortunately I don't have access to a laptop with bluetooth. I only use it on a Samsung S8+ Android phone. If I can be of any assistance getting it to work properly on such devices though, I'll be happy to help.
I have the same issue, chinese Gan 356i.
I have the same issue, chinese Gan 356i.
Try https://cstimer.net/src/?debug=1
Is there any log starts with [gancube]?
Same here. Really often in the solves the cube is no longer responding. See attached image with debug infos.