Valentine has released a Mid-October 2021 update for the Valentine 1 Gen2 (purchase the V1 Gen2 here) that updates the detector to firmware 4.1027.
This update brings a number of nice improvements to the V1, but it also introduced an annoying issue too. Here’s what you need to know about this latest update.
Firmware 4.1027 Changelog
First up, here’s the full changelog, straight from Valentine:
(This is what you’ll see on your phone when you go to update your V1.)
Improved Ka Sensitivity
The main improvement with this new firmware is that Valentine has improved the V1’s sensitivity to the Ka frequency ranges that officers generally use in the US: 33.8, 34.7, & 35.5.
So far in testing (test 1, test 2), people have been able to confirm that the V1 does indeed perform better now with this latest update. That’s especially impressive considering the V1 Gen2 was already an outstanding performer.
Reduced Ka Falses
This update also helps address an issue where some K band transmitters (such as certain vehicles with K band blind spot monitoring systems) could cause the V1 to incorrectly alert to Ka band instead of K band.
Increased Ka Falses
Annoyingly though, after this update, many people are now reporting increased weak Ka falses, much more than before the update. These falses don’t seem to be related to being near a K band emitter.
I don’t know what’s causing them, but this is an issue. Hopefully Valentine can work it out in a future update.
Apps Can Now Adjust V1 Volume
Apps now have the ability to not only remote mute the V1, but they’ll be able to remotely control the V1’s volume levels too. Apps will have to be updated to support this feature, but it gives them more control over the V1 now.
How to Update Your V1
Finally, if you’d like to update, simply launch the V1connection app for Android or iOS. It’ll let you know there’s an update. Follow the prompts and after about 10 min, you’ll be running the latest firmware.
Here’s a tutorial you can check out as well:
Be aware though that there is no ability to downgrade to a previous firmware in case you run into issues with the Ka falses. The app simply updates you to the current (latest) firmware available.
If you’d like to update, you can go ahead and download the update for free through the app.
For full discussion or if you have any issues, you can join the full discussion here.
If you don’t yet have a V1 Gen2, you can purchase one here.
This website contains affiliate links and I sometimes make commissions on purchases. All opinions are my own. I don’t do paid or sponsored reviews. Click here to read my affiliate disclosure. |
18 comments
Skip to comment form
You forgot to mention or repeat mention that the increased Ka sensitivity if InThe Box only.
I noticed that they haven’t fixed other issues that are important. The first is the slow transition of the direction arrows, and still occassinally showing multiple K bogies when only 1 is present.
Author
It’s displayed in the changelog at the top of the article. This article is intentionally kept brief and simply adds some additional info based on what people have reported in testing. If you notice more stuff though, please continue to share!
Great Update, 33.8 is the main frequency being used in my area & so far I’m experiencing zero false alerts.
Thanks Vortex
Author
Awesome! Glad to hear it. 🙂
Going over to Staten Island tomorrow I don’t normaly use the V1 in NY because of NO MRCD/CT detection. I use V1 Driver and it works very well. I’ll see if it sees the speed cam signal, I don’t think it will, I run it in small L mode. If I put it in A mode it will see it but that would make the V1 useless as it will be falsing every few minutes.
I’m in NY and and I also run mine in small L. Mine picks up the speed radars both stationary and portable that my town and other have. There are some tho that it doesn’t pick up that I have come across and I believe from checking that the signal from those if I remember correctly is horizontal rather than vertical or vice versa or something to that effect.
I was on Staten Island today and first off my V1G2 in small L mode is useless against the speed cams. It’s completely quite in the cam kill zone. Red light cams useless again You MUST use an app on your phone. So for me I use V1 Driver & Waze to cover myself. Also since the last update the V1 will drop my Bluetooth connection after about 45 minutes and you have to re booth your phone for it to connect again to V1 Driver..It never did this before the last update.
Author
Thanks for the feedback! Yeah that seems to match what I’ve heard others report in your area too. Does Waze do a good job against the stationary cams? I understand it offers limited help against mobile speed cams. Interesting to hear about the BT connectivity issues with the latest update too…
I don’t know if it’s just my phone or a new issue after the latest update to the V1.We will have to see if anyone else reports the same issue.
All things being equal, anytime you significantly increase sensitivity, you should expect to see more false alerts because the detector will “see” more signals. Conversely, increasing selectivity (discriminating against non-radar) will increase reliability.
So increasing sensitivity is nice, but absent an equal improvement in selectivity, all you get is more false alerts.
I will not update with this version because the V1 is already plenty sensitive. Increasing false alerts creates a risk I will not always respond accordingly. Hopefully, VR will increase the selectivity with future updates. When that happens I will certainly upgrade. Not till then.
Since updating with the latest October software I have experienced a multiple ka ramp up and falses, along with very slow arrow transition and alot more laser alert falses.. we need another update to address these issues…
I appreciate your recommendation for V1 for Road trips. Thank you 😊.
Today March 7, 2022 there is a new firmware upgrade to V4-1028. It doesn’t mention any fixes to what many are reporting. It may be an interim upgrade since it’s an even number.
Sooo what does the upgrade do???, been having arrow transition issues and laser falling, and bogie counter rampup issues
Author
Good question. I don’t know either so I reached out to Valentine and we’ll see what they say.
Author
Update, here ya go.
The “here ya go” link doesn’t work.
Author
Sorry you’re right. That thread I linked to has since merged with another thread. I updated the previous mention just now. Here’s the new link again for your convenience.