V1Driver Beta CJR trying it out

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#1
I have been using YaV1 for a long time now and didn't have much need to change but figured i would give V1Driver a go. So far its seems pretty cool, lots of features but no custom weep options or K band muting options?

I am super happy it has the overlay now, but the other important features was to be able to push different custom sweeps and different V1 muting with band settings which V1Driver doesn't seem to have?

I have to get some time with how it mutes and locks out since to manually mute and other mute setting are different than YaV1.
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#2
It has not been show that changing Custom Sweeps makes all that much difference performance wise. Is this to address Ka falses or something or do you think you get more extreme range by tweaking it?
I've yet to see any evidence of that posted. I personally use the same values of YaV1 default sweeps. If frequent twiddling of Custom Sweeps is requirement for you, then V1Driver isn't for you. No problem.

What does make sense to change is X band on or Off as needed and I may add that.

The more you turn K-Mute settings up to be more aggressive the less V1Driver can do on the other end (V1Driver has less control when K-Mute is "active"). So I recommend minimal K-Mute and leave it there.
Let V1Driver take care of it with it's AutoSnooze, which is safer and more effective IMHO.

I discourage using manual lockouts (they are risky). Let V1Driver learn it.

Thanks for trying it out.
 

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#3
It has not been show that changing Custom Sweeps makes all that much difference performance wise. Is this to address Ka falses or something or do you think you get more extreme range by tweaking it?
I've yet to see any evidence of that posted. I personally use the same values of YaV1 default sweeps. If frequent twiddling of Custom Sweeps is requirement for you, then V1Driver isn't for you. No problem.

What does make sense to change is X band on or Off as needed and I may add that.

The more you turn K-Mute settings up to be more aggressive the less V1Driver can do on the other end (V1Driver has less control when K-Mute is "active"). So I recommend minimal K-Mute and leave it there.
Let V1Driver take care of it with it's AutoSnooze, which is safer and more effective IMHO.

I discourage using manual lockouts (they are risky). Let V1Driver learn it.

Thanks for trying it out.
Thanks!

I have 3 custom sweeps depending on where I am since i drive far distances. Some focus on having a balance of 35.5 and 34.7, while others focus more on 34.7. Yes the advantage is negligible, but they do help. But no biggie.

The big one was Band filtering. I have one set with X off but when i drive in NJ i need X on with a different setting. I also have 3 seconds K muting and rear K muting, sometimes in areas where K is used i need to switch to no K muting on the fly. This happens often. But ill need more time with V1Driver K/X band filtering/snooze to see the real difference.

So if i program my V1 with YaV1 both the sweeps and K/X band settings like rear arrow muting stays?

It seems my focus will be on how V1Driver mutes/locks/learns with the many different pres/swipes.
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#4
Yes, anything programmed to V1 by any app should stick.

Doing something about X band is on the to do list.
 

thanks

for all the fish
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Acceptus
Newly Registered
Sep 16, 2016
4,813
18
#5
What does make sense to change is X band on or Off as needed and I may add that.
Turning K on/off (C to c) is easy. Being close to a state where X is used, simplifying that toggle would be great!
Having used V1Driver on iOS, the GPS based automuting is great and as I always say V1Driver just set it and forget it. If I want to hear the Ka frequency, I have it speak it (not always, but only when driving solo). For me, I prefer to rely on the V1CD in my instrument cluster for immediate SA, so I didnt need an app for that.
 

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#6
So i need to clarify the muting features, ones in bold below specifically.

What i have is this:

Tap Mute = mute band (I guess this means regular mute and bogie lock tone will still alert)

Tap Twice = Snoose (mutes even new alerts? No bogie lock tone?)
Snooze mode i tap it again and it no longer mutes?


Long press/tap = Save recording

Swipe right with 2 fingers = Lock out (manual lock out?)

Swipe left = lock out cancel (is this manual unlock?)

Swipe down = hide nav bar (what?)

Swipe up = Show recorder

I will want to manually nuke a lock out area thats complex and has no LEO's runnin K.
 
Last edited:

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#7
I need to update those tips.

Tap should say = Mute Frequency. (it used to be mute the band). It will auto mute on it's own if you let it.
Snooze will mute the current frequency and engages snooze. It will auto snooze on it's own if you enable it and let it.
AutoSnooze is AutoSnooze, check out the Video [continue reading below the big fat Video insert]
Swipe Right is manual lock out. It's 2 fingers on iOS (to prevent accidental lock) it's 1 finger on Android because Android doesn't standardly support it, 2 fingers should work too ;).
Yes, swipe left "cancels" the manual "locking". It is not retroactive. It will just stop adding more manual lockouts. It's on until it goes quiet.
Hide Nav bar isn't implemented yet on Android. That hides the Steering wheel, Compass, and Cogwheel at the bottom on iOS.

Bogey lock tones are independent and totally under V1 control and will work as they always do. As you probably know I'm not a big fan of the bogey lock tone, I keep my lever at 0 and bogey on Lever.
But V1Driver shouldn't interfere with them or has any control over them. No App does.

Note also manual locks go to userLockpend first. So you can review them. in 24 hours they will migrate to userLock.
In hindsight I wouldn't have bother with this two stage lockout. I didn't even have Auto Lockout when I first added this 2 stage concept. But it works. Needs to much explaining.
 

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#8
Interesting, Snooze sounds like its a cool feature. I have mine set to after 10 seconds (think that's enough for a real encounter). And 35 seconds since i don't want it to mute too long incase a LEO may be using the same frequency (unlikely).

So all i really need to remember is tap to mute, and swipe right to manually nuke an area, and left to stop the destruction. lol

I can also cancel snooze by taping it like mute when its in snooze mode?
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#9
Correct.

Sometimes 10 seconds feels long. Keep in mind that delay is ADDED to your K-mute delay, because V1 might keep it completely muted for 3 seconds. When you tell V1Driver 10 seconds that means 10 seconds of you hearing it.
And V1Driver doesn't try to guess if K-mute canceled in the V1 or not. It's too tricky when it's busy. So I assume it could have been muted the whole k-mute delay. I always error on the side that the user gets alerted.

I'm not sure what you mean by the 35 seconds? Once V1Driver mutes (unless something else comes along out of the current lock out frequency ranges active - also now displayed in real time) it's not gonna unmute by time (like K-mute does). This is similar to your other favorite brand detector with auto GPS lockout style automute. With the Auto Snooze twist.

And again V1Driver doesn't start it's thing until V1 is "done". V1Driver only takes advantage that it was "pre muted" by K-Mute when it knows it should be muted (savvy or gps) and those encounters can stay completely silent (if it stays below K-mute threshold for it's entire delay). That is partly why I like to keep K-Mute delay short. I prefer peace ASAP, once I know the possibility exists I don't need to be reminded.
 
Last edited:

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#11
I dont think I ever manual locked out in V1Driver. I have a V1 safe n sound mute button (Valentine Flat Mute Plug - "Be Safe with Safe-N-Sound1.com") on my wiper stalk which works great for muting when needed.
Keep in mind though, that will mute all frequencies and all bands until V1 is idle (plus it's hold time, which is fairly long). I never mute the V1 and I rarely hit mute on V1Driver. I let it do it. If I want more piece and quiet then I just lower the automute delay. I often set it to 5 seconds, but I set the default to a conservative 10 seconds. I'm often reseting to factory to test stuff. Also because I have V1Driver routed through the Radio. I can have the V1 volume set fairly low.

Because I do so much testing. I'm actually pretty numb to anything alerting :( I hear the V1 in my sleep I here it in tunes, I hear it in TV shows when anything gets close to that pitch.
 
Last edited:

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#12
Correct.

Sometimes 10 seconds feels long. Keep in mind that delay is ADDED to your K-mute delay, because V1 might keep it completely muted for 3 seconds. When you tell V1Driver 10 seconds that means 10 seconds of you hearing it.
And V1Driver doesn't try to guess if K-mute canceled in the V1 or not. It's too tricky when it's busy. So I assume it could have been muted the whole k-mute delay. I always error on the side that the user gets alerted.

I'm not sure what you mean by the 35 seconds? Once V1Driver mutes (unless something else comes along out of the current lock out frequency ranges active - also now displayed in real time) it's not gonna unmute by time (like K-mute does). This is similar to your other favorite brand detector with auto GPS lockout style automute. With the Auto Snooze twist.

And again V1Driver doesn't start it's thing until V1 is "done". V1Driver only takes advantage that it was "pre muted" by K-Mute when it knows it should be muted (savvy or gps) and those encounters can stay completely silent (if it stays below K-mute threshold for it's entire delay). That is partly why I like to keep K-Mute delay short. I prefer peace ASAP, once I know the possibility exists I don't need to be reminded.
By 35 seconds i mean "Snooze Mute For" option that i think defaults for 2min.

Yes, ill be leaving the 3 second mute at any strength and rear arrow mute. If it messes things up i can disable it, but i really need that 3 second delay. And since V1Driver overly still shows even if an alert is muted it should be fine like YaV1.

I dont think I ever manual locked out in V1Driver. I have a V1 safe n sound mute button (Valentine Flat Mute Plug - "Be Safe with Safe-N-Sound1.com") on my wiper stalk which works great for muting when needed.
Yes, i have the same mute button close by. Works great!
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#13
By 35 seconds i mean "Snooze Mute For" option that i think defaults for 2min.

Yes, ill be leaving the 3 second mute at any strength and rear arrow mute. If it messes things up i can disable it, but i really need that 3 second delay. And since V1Driver overly still shows even if an alert is muted it should be fine like YaV1.

Yes, i have the same mute button close by. Works great!
Ahh, I see, that sounds good. V1Driver won't pop up the overlay if it's gpsMuted. It will for savvy or automute. I debated having an always pop option and actually had in there and took it out.
It seemed to contradict having the App at all if it pops an alert on everything !!
 

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#14
Ahh, I see, that sounds good. V1Driver won't pop up the overlay if it's gpsMuted. It will for savvy or automute. I debated having an always pop option and actually had in there and took it out.
It seemed to contradict having the App at all if it pops an alert on everything !!
For muting and savvy as well as snooze its important, but for lock outs seeing the V1 light up is fine.
 

NVR2FST

PSL +15
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Aug 1, 2011
1,064
8
#15
Running the "Demo" crashes my phone every time. See phone type below.

Posted from my Studio XL 2 using the RDF Mobile App
 
Last edited:

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#16
Running the "Demo" crashes my phone every time. See phone type below.

Posted from my Studio XL 2 using the RDF Mobile App!
Don't run Demo then. :p

Also, i even titled the thread "V1Driver Beta CJR trying it out" i didn't title it" tell me whats wrong with your V1Driver app". lol

jk
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#17
Running the "Demo" crashes my phone every time. See phone type below.

Posted from my Studio XL 2 using the RDF Mobile App!
Thanks for the report (albeit not it the best thread, feel free to create a new one on something like this).
I think I have it fixed (hard to reproduce). I definitely want the Demo to be solid. It definitely sets a bad first impression if the Demo crashes.
If after the next update (Version 1.0.0.80) please send me a log if it crashes for any reason. But please include forum name and briefly what happened.

Thanks.
 

NVR2FST

PSL +15
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Aug 1, 2011
1,064
8
#18
Thanks for the report (albeit not it the best thread, feel free to create a new one on something like this).
I think I have it fixed (hard to reproduce). I definitely want the Demo to be solid. It definitely sets a bad first impression if the Demo crashes.
If after the next update (Version 1.0.0.80) please send me a log if it crashes for any reason. But please include forum name and briefly what happened.

Thanks.
I was thinking of asking you that. I wasn't even sure that the logging function worked with the demo. Kinda assumed that logging was only for running the app when it was running in a real world environment. Thanks!

Sent from my Studio XL 2 using Tapatalk
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,293
0
MA
#19
I was thinking of asking you that. I wasn't even sure that the logging function worked with the demo. Kinda assumed that logging was only for running the app when it was running in a real world environment. Thanks!

Sent from my Studio XL 2 using Tapatalk
That's a good thought, but the log covers anything. I use the Demo for a lot of testing because it's easier than driving around and setting up a Ka combined with a K situation while moving with Savvy etc.
The Demo can even drop new pins etc. because it's playing back the same data as real data and 95% of the code doesn't know it's running a Demo (a recording), it thinks it's real.
The bug was actually in the stupid dialog box that pops up (or tries to pop up).
 

CJR238

-CMS Article Admin-
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 30, 2010
26,219
28
CT. MZDA 3. ALP, V1/RedLine/Waze
#20
Omg, thease start up loop popups are driving me crazy. Make them stop. Lol

Sent from my XT1585 using Tapatalk