20.26 beta to final Varia Radar STILL NOT WORKING PROPERLY

Experienced this today as well in the production version of the software. 

The radar gauge (green, yellow and red on the right side) appears only randomly with no rhyme or reason. Mostly, just a half bubble at the top saying vehicle approaching and then a beep when it thinks everything is all clear. You may reach me via email. Located 35miles east of HQ in Olathe in Lawrence, KS. When the gauge does appear, it has the number of vehicles BUT quickly disappears most of the time. As for vibration, I have the 965 mounted on the handlebars out front (btw, another sore spot that Garmin no longer has the quick release, triathlon kit). So don't know if vibration or not. BUT I do HEAR notifications in my ear buds that a vehicle is approaching just no visuals anymore that are consistent. Really a pain and not safe.

Thanks for the feedback on the firmware error.
1. Vibration signals always work on approaching objects from behind (two, three vibro depending on the speed of the object from behind and one vibro at a clear horizon from behind), radar indicator and the track on the right of the visualisation disappears one, two minutes after the start of driving. May randomly show visualisation for one two minutes in the middle of the route.
2. Yes.
3. Russian Federation

Hi, the most interesting should be, why Garmin released 20.26 to Publicwith that known regression ?

Post and Bug Report during beta phase ? this could be a good list of people to contact again, and retreive complementary information ?

• https://forums.garmin.com/beta-program/forerunner-965/f/community-discussion/380945/varia-510-radar-still-not-working-w-965
• https://forums.garmin.com/beta-program/forerunner-965/f/community-discussion/380698/v20-21-rearview-radar-indicator-missing/1815273#1815273
• https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-20-xx/varia-radar-loose-connection
• https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-20-xx/varia-radar-notification-screen-not-working
• https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-20-xx/fr-965-and-varia-515-randomly-not-displaing-incoming-vehicles
• https://forums.garmin.com/beta-program/forerunner-955-series/public-beta-bug-reports/i/public-beta-version-20-xx/radar-missing-gauge-most-of-the-time-bike
• https://forums.garmin.com/beta-program/forerunner-955-series/public-beta-bug-reports/i/public-beta-version-20-xx/20-23-radar-alert-green-threat-level-all-clear

The radar gauge disappears after the first vehicle has passed. At that time also the radar connect symbol disappears. There are still vibrations and a message: vehicle approaching. This is in the top portion of the screen where all messages are shown. Receiving a WhatsApp message sometime fixes the situation until one vehicle has passed. Then the radar symbol disappears 

I m also running the my bike radar connect iq app. In that app I can see distance and speed. However the number of vehicles displayed is not increasing. So remains zero. 
The uploaded rides however have all of the details 

there is no difference in behavior between using the 965 on my wrist of in my out front mount. 
i m located in the Netherlands 

feel free to approach me by email 

Can confirm I am also experiencing this BUG.  Garmin-Sierra pointed me here from the thread I just created.

I confirm. I have the same problem. The column display on the right of the clock, after the update, works for about 2 minutes and then disappears. When the vehicle arrives, only a notification appears at the top of the display but you do not see the column on the right with the vehicle approaching.

If you enter the radar sensor settings during the activity and then exit, the column on the right reappears for about 2 minutes and then disappears again.

Can't describe how frustrating this is to have something broken that was previously working flawlessly, especially the fact it was reported repeatedly during beta testing.

I have this issue, also. Would be interested in rolling back to v19 firmware until this is fixed.