PLEASE TRY A FACTORY RESET AND FIRMWARE REFLASH BEFORE REPORTING ANY NEW ISSUES, THANK YOU
So there's a mess of threads here, making it hard to keep track of some issues, and just making a general mess of the section. With permission from Andrew21 I'm starting the "official" thread if you will, which I will be updating constantly.
If anyone has any suggestions on how to make it better, let me know, but I prefer to keep it as similar as possible from the first time I post through to the end of Uniden's updates, hopefully multiple years down the road, and then somewhat beyond if new issues come up.
Known issues:
#1 K POP On alerts outside of K narrow range even with KN on: Choose Life pointed out that K POP on with K Narrow will alert to K-band frequencies outside of the range of K Narrow, at least above 24.200 (the K Narrow cutoff) but possibly not below 24.080. Not a huge issue but it is performance related.
#2 Mounts: Myself and many other users find that the sticky cup-style mount is useless as it comes from the factory on steeply swept-back windshields. At the lowest possible angle, they still aim up 5-15º which is not ideal for radar detection. The stalk on the part of the mount that sticks to your windshield can be filed where the retainer ring is hitting it, as well as the ring itself. This allows several more degrees of adjustment, but is done at your own risk as you could damage your mount if you're not careful. Another fix for this that some users have done is to obtain a Garmin GPS mount with a ball and socket style arm, so far it's been reported all known Garmin mounts with the proper ball and socket style arm work.
Many users also do not like the fact that the mount point on the detector is part of the lens. This will cause scratches on the lens over time, although they will not affect detection of radar, and shouldn't affect laser detection unless you scratch the laser detection area (the small round bulb) directly. This can be fixed by putting something like clear packing tape or electrical tape around the mounting slot and carefully cutting a slit in it for the mount to go in.
#3 RLC repeated alerts/incorrect muting: When stopped at a stoplight near an RLC area, the GPS might jump around a few feet and cause repeated RLC alerts. Vortex mentioned this to Uniden so they are aware of it. It's unknown whether this will be fixed in the future. Thankfully it's quite a minor and infrequent issue. In addition to this, when you try to mute a radar source while you're near a RLC alert, the R3 will ask to delete the RLC point rather than mute the radar source.
#4 X-band falses: Some users report a high number of X falses, but this is likely due to the extreme sensitivity. It's picking up falses that other detectors didn't have the sensitivity to detect.
#5 High operating temperature: BRD has stated DSP detectors tend to run hot, and that the R1/R3 need to be mounted on the windshield with the bottom vent holes exposed for best cooling. Highly unlikely to be a true issue at this point in time. See post #3 below for analysis and temperature readings, as well as post #13.
#3 GPS speed and lock performance: Obviously this could only be an issue with the R3, since the R1 doesn't have GPS. Some users report very long delays after turning on their RD before a GPS signal is acquired, difficulty acquiring a lock in certain places, and GPS speed reading up to 3mph high compared to other sources. Odds are this is NOT a device issue and there are naturally variations in satellite signal strength day-to-day and hour-to-hour depending on satellite position and weather.
Issues that have been resolved:
#1 Constant 35.5 false: Some users were reporting a constant or near constant 35.5GHz false alert on their Rx detectors, firmware 1.26 has resolved this.
#2 Polarized sunglasses: There are a couple reports that suggest some of the vertically polarized preproduction units made it out into the wild, causing issues with polarized sunglasses. The reports are very limited currently. Please contact Uniden if you have this issue, they'll replace your unit's screen for you.
#3 Frequency ghosting across K and Ka frequencies: Pre-1.30 firmware, the Uniden R1 and R3 would sometimes display a strong K signal as Ka with Ka wide enabled, and vice versa. Also, sometimes when you turned off Ka, a Ka source would show up as K. This is now fixed!
#4 Lockout frequency range too wide: The lockout frequency tolerance used to be very wide at 50MHz which locked out most of K band when you locked out a centered frequency. This is now reduced to +/- 30MHz.
#5 Quiet alerts: Some users were reporting tones were too quiet, make sure you have automute disabled, and try scrolling through the alert tones to find one you like. If you're POSITIVE the tones are super quiet even on high volume with automute off and know you have good hearing, try contacting BRD/Uniden.
And of course let me know if I missed anything.
So there's a mess of threads here, making it hard to keep track of some issues, and just making a general mess of the section. With permission from Andrew21 I'm starting the "official" thread if you will, which I will be updating constantly.
If anyone has any suggestions on how to make it better, let me know, but I prefer to keep it as similar as possible from the first time I post through to the end of Uniden's updates, hopefully multiple years down the road, and then somewhat beyond if new issues come up.
Known issues:
#1 K POP On alerts outside of K narrow range even with KN on: Choose Life pointed out that K POP on with K Narrow will alert to K-band frequencies outside of the range of K Narrow, at least above 24.200 (the K Narrow cutoff) but possibly not below 24.080. Not a huge issue but it is performance related.
#2 Mounts: Myself and many other users find that the sticky cup-style mount is useless as it comes from the factory on steeply swept-back windshields. At the lowest possible angle, they still aim up 5-15º which is not ideal for radar detection. The stalk on the part of the mount that sticks to your windshield can be filed where the retainer ring is hitting it, as well as the ring itself. This allows several more degrees of adjustment, but is done at your own risk as you could damage your mount if you're not careful. Another fix for this that some users have done is to obtain a Garmin GPS mount with a ball and socket style arm, so far it's been reported all known Garmin mounts with the proper ball and socket style arm work.
Many users also do not like the fact that the mount point on the detector is part of the lens. This will cause scratches on the lens over time, although they will not affect detection of radar, and shouldn't affect laser detection unless you scratch the laser detection area (the small round bulb) directly. This can be fixed by putting something like clear packing tape or electrical tape around the mounting slot and carefully cutting a slit in it for the mount to go in.
#3 RLC repeated alerts/incorrect muting: When stopped at a stoplight near an RLC area, the GPS might jump around a few feet and cause repeated RLC alerts. Vortex mentioned this to Uniden so they are aware of it. It's unknown whether this will be fixed in the future. Thankfully it's quite a minor and infrequent issue. In addition to this, when you try to mute a radar source while you're near a RLC alert, the R3 will ask to delete the RLC point rather than mute the radar source.
#4 X-band falses: Some users report a high number of X falses, but this is likely due to the extreme sensitivity. It's picking up falses that other detectors didn't have the sensitivity to detect.
#5 High operating temperature: BRD has stated DSP detectors tend to run hot, and that the R1/R3 need to be mounted on the windshield with the bottom vent holes exposed for best cooling. Highly unlikely to be a true issue at this point in time. See post #3 below for analysis and temperature readings, as well as post #13.
#3 GPS speed and lock performance: Obviously this could only be an issue with the R3, since the R1 doesn't have GPS. Some users report very long delays after turning on their RD before a GPS signal is acquired, difficulty acquiring a lock in certain places, and GPS speed reading up to 3mph high compared to other sources. Odds are this is NOT a device issue and there are naturally variations in satellite signal strength day-to-day and hour-to-hour depending on satellite position and weather.
Issues that have been resolved:
#1 Constant 35.5 false: Some users were reporting a constant or near constant 35.5GHz false alert on their Rx detectors, firmware 1.26 has resolved this.
#2 Polarized sunglasses: There are a couple reports that suggest some of the vertically polarized preproduction units made it out into the wild, causing issues with polarized sunglasses. The reports are very limited currently. Please contact Uniden if you have this issue, they'll replace your unit's screen for you.
#3 Frequency ghosting across K and Ka frequencies: Pre-1.30 firmware, the Uniden R1 and R3 would sometimes display a strong K signal as Ka with Ka wide enabled, and vice versa. Also, sometimes when you turned off Ka, a Ka source would show up as K. This is now fixed!
#4 Lockout frequency range too wide: The lockout frequency tolerance used to be very wide at 50MHz which locked out most of K band when you locked out a centered frequency. This is now reduced to +/- 30MHz.
#5 Quiet alerts: Some users were reporting tones were too quiet, make sure you have automute disabled, and try scrolling through the alert tones to find one you like. If you're POSITIVE the tones are super quiet even on high volume with automute off and know you have good hearing, try contacting BRD/Uniden.
And of course let me know if I missed anything.
Last edited:
(unless of course, Uniden can solve every issue from every member, including the conflicting ones) 
