DigiCue Blue graph interpretation

I’ve been using the new app about a month and believe it’s extremely valuable in identifying cue delivery issues. One of my favorite gadgets, definitely for advanced players.

That said, I’ve also had some false shots from chalking and feel the graphical summary all on the same chart is confusing.

It took me a while to figure out the size of the inner circle corresponds to difficulty and maybe display the setting somewhere could enhance user experience.

Hope this helps, truly do appreciate having the inventor being so interactive.
 
Last edited:
Thanks for responding. How do you know the tip was moving up a tiny amount and not down? I assume that because straightness(STR) measures vertical tip movement, and my score was not a 10, that there was some up and down movement, but how can you tell the movement was up?

I strive for a pendulum stroke--where the tip moves up and down during the stroke--so I think the high score for STR means that I must have dropped my elbow.
Are you going to be selling these as a set once the DigiBall comes out?
There seem like too many bugs to iron out for now. When everything gets in sync and works properly is when I will become interested.
 
There seem like too many bugs to iron out for now. When everything gets in sync and works properly is when I will become interested.
Yep, people live in different areas of the consumer curve, and there is no problem with any area:
1733857338579.png


The major improvement has been that the new app I made has fixed a lot of connection issues with Android. Android and Bluetooth used to be a huge mess, now it is a bit better. It also uses a single code base so that Android and iOS apps behave the same way. But the interface can use some improvement.

There are a couple of minor bugs that have been identified and are now fixed, or being fixed. These are:

1. A weaker spring clip in the battery holder causes the battery to lose contact and cause a device reset. This is easily fixed by bending the spring clip outwards more to create more tension. I changed the battery holder vender and have also increased the power rail capacitance to allow for a short disconnect. I may also investigate a permanently soldered rechargeable lithium ion battery, but this could drive up cost a bit.

2. The steering calculation on the new app needs a small adjustment.

3. People have requested more information and a better display for the polar straightness plot.

4. People have requested a better way of viewing the history of shots.

5. People have mentioned some false triggers. I need to work a little more to make a good compromise between a robust trigger, and being able to detect softly hit shots.
 

Ive updated the app with your suggestions. Version 2.0.7. I also fixed some configuration errors I found. Give it a try.

After Christmas I’ll work on improving the shot history stuff.

Nate
 
j'ai la version 2.0.7 sur un samsung A15 5g l'application se ferme et j'ai un message d'erreur l'application se ferme car il y a un bug contacter le développeur.
j'adore l'application je suis desole quelle ne fonctionne plus sur mon nouveau téléphone pouvez vous me répondre sur mon email 8993@hot mail.ca
 
j'ai la version 2.0.7 sur un samsung A15 5g l'application se ferme et j'ai un message d'erreur l'application se ferme car il y a un bug contacter le développeur.
j'adore l'application je suis desole quelle ne fonctionne plus sur mon nouveau téléphone pouvez vous me répondre sur mon email 8993@hot mail.ca
Try uninstalling completely and reinstalling the app, instead of upgrading. I read that this fixes the issue a lot of the time on Android devices.
 
Ive updated the app with your suggestions. Version 2.0.7. I also fixed some configuration errors I found. Give it a try.

After Christmas I’ll work on improving the shot history stuff.

Nate

New graphs are pretty nice. I like the thin line in the bar chart to show the red/green threshold. Great update!

I get quite a few backstroke pause faults even if I make a lengthy pause on purpose. I’ve noticed that is less frequent with an extended long set before the backswing. Curious how it differentials between warm up strokes and delivery and if this can cause a backswing error. I have that currently set at medium difficulty.


Sent from my iPhone using Tapatalk
 
j'ai la version 2.0.7 sur un samsung A15 5g l'application se ferme et j'ai un message d'erreur l'application se ferme car il y a un bug contacter le développeur.
j'adore l'application je suis desole quelle ne fonctionne plus sur mon nouveau téléphone pouvez vous me répondre sur mon email 8993@hot mail.ca
TRANSLATED:
I have version 2.0.7 on a Samsung A15 5g the application closes and I have an error message the application closes because there is a bug contact the developer. I love the application I am sorry it no longer works on my new phone

My Comment
I, too, have problems with 2.0.7 that prevents it from logging shots.

Problem One:
When installing the app, a pop-up screen asks: Allow digicue_app to find, connect to, and determine the relative position of nearby devices? I allow it that access. The app will start but seconds later, closes. Same thing happens if I restart it.

Problem Two: By pressing the icon on the cell phone screen and without letting up off the screen, option "APP INFO" appears. Using that option, I can turn off the app's access to nearby devices. If I then start the app, it will start, and the START SHOOTING screen appears. Nothing happens, however, if I hit the ball with the cue stick.

The digicue blue appears OK. If I hit the digicue button, it vibrates. If I hit a ball, it vibrates.

If I try to do a SYNC CONFIGURATION on digicue blue, the power button never responds with four vibrations to my pressing the ON button

Under the app's bluetooth icon, it states DEVICES FOUND: 0 _________ SELECTED DIGICUE: DIGICUE:78. No shots are recorded in the data history.

It worked under 2.0.7

The cell phone does not list any device called digicue under bluetooth.
 
New graphs are pretty nice. I like the thin line in the bar chart to show the red/green threshold. Great update!

I get quite a few backstroke pause faults even if I make a lengthy pause on purpose. I’ve noticed that is less frequent with an extended long set before the backswing. Curious how it differentials between warm up strokes and delivery and if this can cause a backswing error. I have that currently set at medium difficulty.


Sent from my iPhone using Tapatalk
Yes, I believe this has to do with the settling of a running averages filter, where if you don't set for long enough (remain still), the filter retains a residual value from the warm up strokes. Its a tradeoff between time and precision.
 
TRANSLATED:
I have version 2.0.7 on a Samsung A15 5g the application closes and I have an error message the application closes because there is a bug contact the developer. I love the application I am sorry it no longer works on my new phone

My Comment
I, too, have problems with 2.0.7 that prevents it from logging shots.

Problem One:
When installing the app, a pop-up screen asks: Allow digicue_app to find, connect to, and determine the relative position of nearby devices? I allow it that access. The app will start but seconds later, closes. Same thing happens if I restart it.

Problem Two: By pressing the icon on the cell phone screen and without letting up off the screen, option "APP INFO" appears. Using that option, I can turn off the app's access to nearby devices. If I then start the app, it will start, and the START SHOOTING screen appears. Nothing happens, however, if I hit the ball with the cue stick.

The digicue blue appears OK. If I hit the digicue button, it vibrates. If I hit a ball, it vibrates.

If I try to do a SYNC CONFIGURATION on digicue blue, the power button never responds with four vibrations to my pressing the ON button

Under the app's bluetooth icon, it states DEVICES FOUND: 0 _________ SELECTED DIGICUE: DIGICUE:78. No shots are recorded in the data history.

It worked under 2.0.7

The cell phone does not list any device called digicue under bluetooth.
So are you saying that you can not get the app to work if you agree to "Allow digicue_app to find.... devices?" You definitely need that option enabled for Bluetooth to work.

Does it work if you revert to the previous version (if possible)??

Do you have a newer phone as well?

I am hoping Google didn't do something funky with their APKs which caused a breaking change.
 
Does it work if you revert to the previous version (if possible)??

Do you have a newer phone as well?
I don't know how to revert to previous version. I had uninstalled it.

My phone isn't new. Its Pixel 5, Android 14 version, Android Security update 11/5/2023; Google Play System update 11/1/2024
 
If I allow phone to access devices and start app, the START SHOOTING screen will appear. It will stay up until I start digicue blue by pressing on its on button. The app screen then disappears. If I try restarting app, the same quick and short appearance of START SHOOTING appears.
 
If I allow phone to access devices and start app, the START SHOOTING screen will appear. It will stay up until I start digicue blue by pressing on its on button. The app screen then disappears. If I try restarting app, the same quick and short appearance of START SHOOTING appears.
OK. I am trying something now. I am certain that Google's push from SDK 33 to SDK 34 broke something, as I am seeing a lot of problems online from other app developers.
 
Last edited:
Ok, now version 2.0.8. Please retry and let me know if it still crashes.
Version 2.0.8 still crashes. I cannot tell any difference between this version and the last. Still closes fast if I allow access to other devices versus, if I do allow it access to other devices, it shows the START SHOOTING screen and that is it --- no effect on screen from hitting balls with digicue blue.
 
Yep, now this is a big problem. The app is only 2 years old, and already the bug could be a compatibility problem with the new SDK. I am going to have to rewrite the whole app under a new project since Google won't let me convert back to the previous version. Until I finish, a lot of Android users won't have a working app. I'll try to do it quickly.

Thanks a lot Google.
 
Why the heck not?! What's their reasoning for that?
Security feature updates and other BS. I'm not a professional app developer and it takes me a lot longer to make an app then a full time company/firm. By the time I am done it is obsolete. Very hard for the small guy.

But I've written this thing in like 5 different ways now, so it shouldn't be too much work. I just wanted to relax this Christmas, but nope. Lol.
 
This will probably take a couple weeks. I’ll most likely get hit with some bad reviews on Amazon during the wait. If any of you could help me out and leave some positive feedback on Amazon to offset this hiccup I’d appreciate it. 🙏
 
Back
Top