GC3, Foresight App and Android phone

[Flyer Lie]

I'm having a difficult time getting numbers to populate to the Foresight App. The Bluetooth connection is good, the app recognizes the numbers of shots taken with a particular club in the "Shot Library". However, the data, doesn't populate to the "Ball Launch Parameters" (Blue tiles), Club Parameters (Green tiles) and Flight Parameters (Yellow tiles). GC3 Club data turned on, all Ball and Club data is detected by GC3. Blinking Green light on GC3 is in sync with blinking green light on Foresight App.

Has anyone every had this issues before? I'd really appreciate any comments. I use this outside mostly and I'd really like to see the numbers on the phone. I'm in contact with Foresight tech support, they are "working on the issue".

[Hannaford]

I haven't had an issue connecting with WiFi on my android phone and tablet. Have you tried the WiFi connection? Also make sure your unit has phones home in the last 45 days if you haven't already.

[Flyer Lie]

Thanks, from what I understand the phone and GC3 communicate via Bluetooth. I verified the WiFi, Bluetooth and Cloud icons all appear on the GC3 and the phone app is connected via Bluetooth to the GC3.

[jammer13]

I had the exact same issue. Yesterday (4/16/24), Foresight released ver 1.3.3 which intended to fix the "no data" issue. Seems to work at home, but I have yet to test out at the range.

My biggest problem is that the sessions from the Foresight app do no populate into FSX Live, which I'm working with Foresight Tech Support to resolve.

[jammer13]

Update - I went to the range this morning with ver 1.3.3 and had the zero data problem recur several times. However, I think it may have to do with the phone being asleep (in my pocket) during the swings. When I kept the phone awake and display on, the data was received as expected. I have a BLP which I don't think makes a difference in this case.

Secondly, it might be worth mentioning that the Foresight Android App is very resource intensive when connected to the BLP/GC3 and the phone gets very hot. It eventually became hot enough after 20-30 minutes that the phone (Pixel 6A) throttled itself and the Foresight App became very unresponsive.

Anyway, keeping the phone awake and monitoring the phone temperature might be reasonable workarounds to at least save some data from your range sessions. Hopefully, Foresight continues to improve the app so it's a little more seamless to use it on the range.