1.9.8 released

Bloovy One

Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
4,015
Reaction score
7,850
Location
Western NC
Hopefully some of this will help. :)

JBV1 is pushing to the V1 but the V1 "pushes back". :p
 

johnboy00

Geaux Tigers!
Advanced User
Lifetime Premium Member
Software Developer
Joined
Sep 6, 2016
Messages
4,146
Reaction score
8,288
Location
Raleigh, NC
I delete the unknown profile each time it occurs. This is such an infrequent event I didn't think much of it.

I thought pushing sweeps on startup meant that JBV1 was pushing to the V1, not the other way around. Does having location overrides force a sweep to be pushed each startup?
When APO is disabled, nothing is pushed on startup. It reads the current V1 settings, matches them to an existing profile, and displays the matching profile name. If no match is found, a new Unknown profile is created, or an existing Unknown profile is overwritten. If in custom sweeps mode, it then does the exact same thing for sweeps.

When APO is enabled, it still does the profile and sweeps matching, but then when the GPS starts sending location updates, it checks to see if it's in an override area. If it is in an override area, it will push the override profile if it isn't the current profile (the one matched at startup), and if the override profile specifies sweeps, it will push those sweeps if they aren't the current sweeps.
 

theclutch

Learning to Drive
General User
Joined
Dec 21, 2019
Messages
11
Reaction score
4
Sorry, I don't think you are understanding me.
I do have a "little experience" with JBV1 (wink-wink) and I also frequently travel between 4-7 states with occasional trips to another 8 or 9.

Of all the people here, I might have the most JBV1 customization for various counties and states.

Give me a bit and I'll try to explain better what I'm saying. :)
Post automatically merged:

One thing that will help us is to know specifically which version of V1 you have. If it's v3.894 or v3.8945 you will have to split up the 34.7 sweep.
If it's v3.8952 you don't have to.

Do you know which version V1 you have?
Post automatically merged:

I'm going to create a new thread for the ideas I'm about to present. I'll link to it here when I have that worked out. :)
I'm running 3.8952 = the latest.

Also, I noticed that even though I press the sunlight in the upper right hand corner to completely darkout my V1, it reverts back to "Auto". I haven't nailed down as to why yet. But I assume it has something to do with me switching back and forth between the JBV1 screen and the Waze screen. Ditto with the graph vs time that still pops up even though I set it to not do so.

Lastly, it's super annoying that I have to stop the car to change settings! C'mon...was this thing built by a lawyer? Sometimes, my wife changes things for me - same with the Nav, radio, CD, AC, etc. on the car. She also access the glove box for me for napkins, snacks or whatever else I keep in there. So should we lock the glovebox while the car is moving? We're all adults... If I choose not to wear a seatbelt (but I do all the time), so be it.

Overall, this JBV1 thing is a must... I'm glad I didn't get the Uniden R7!!!
 

InsipidMonkey

Premium Monkey
Advanced User
Premium Member
Joined
Mar 22, 2017
Messages
6,264
Reaction score
13,365
Location
New England
Lastly, it's super annoying that I have to stop the car to change settings! C'mon...was this thing built by a lawyer? Sometimes, my wife changes things for me - same with the Nav, radio, CD, AC, etc. on the car. She also access the glove box for me for napkins, snacks or whatever else I keep in there. So should we lock the glovebox while the car is moving? We're all adults... If I choose not to wear a seatbelt (but I do all the time), so be it.
You can change this.
Settings -> General -> Settings Disabled at Speed
 

Bloovy One

Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
4,015
Reaction score
7,850
Location
Western NC
If it helps, every issue you've mentioned can be addressed in settings. Johnboy00 is one of the good guys and he's on our side. You shouldn't be losing settings when viewing VVaze. It sounds like a continuation of a Profile issue.

Once you have JBV1 setup, settings never change unless you want them to. It works really seamlessly. :)

Did you see the new topic I created in response to your earlier concerns? If not, it's at: https://www.rdforum.org/index.php?threads/95151/


I made a little meme that seems appropriate here. :p

one-does-not-simply-run-JBV1.jpg
 

theclutch

Learning to Drive
General User
Joined
Dec 21, 2019
Messages
11
Reaction score
4
You can change this.
Settings -> General -> Settings Disabled at Speed
Wow thanks! I can't believe I missed that!

Did you see the new topic I created in response to your earlier concerns? If not, it's at: https://www.rdforum.org/index.php?threads/95151/
Another wow! That great info you posted. Thanks for taking the time to write it up!

On another note... I have certain areas "locked out" already along with some frequencies belonging to Hondas, etc. But for some reason, my V1 still beeps at these and then mutes off. How can I just stop if from beeping at all?
 

johnboy00

Geaux Tigers!
Advanced User
Lifetime Premium Member
Software Developer
Joined
Sep 6, 2016
Messages
4,146
Reaction score
8,288
Location
Raleigh, NC
I have certain areas "locked out" already along with some frequencies belonging to Hondas, etc. But for some reason, my V1 still beeps at these and then mutes off. How can I just stop if from beeping at all?
You must enable V1's native K muting. Try the minimum of 3 seconds.
 

DMartinUA

Δ
General User
Premium Member
Joined
Mar 2, 2016
Messages
40
Reaction score
25
Location
Bama
You must enable V1's native K muting. Try the minimum of 3 seconds.
I have been trying to find some time to screenshot my settings and load them up to ask about this, but I also regularly receive brief (1-3 seconds?) audible K alerts before JBV1 mutes. I have the native V1 K muting set at 30 seconds. It happens for signals that are below my native breakthrough strength setting of 5 and also while I'm under the JBV1 silent ride speed setting.
 

johnboy00

Geaux Tigers!
Advanced User
Lifetime Premium Member
Software Developer
Joined
Sep 6, 2016
Messages
4,146
Reaction score
8,288
Location
Raleigh, NC
I have been trying to find some time to screenshot my settings and load them up to ask about this, but I also regularly receive brief (1-3 seconds?) audible K alerts before JBV1 mutes. I have the native V1 K muting set at 30 seconds. It happens for signals that are below my native breakthrough strength setting of 5 and also while I'm under the JBV1 silent ride speed setting.
A screenshot of the alert screen while connected will show the native K mute settings. Can you post one?
 

InsipidMonkey

Premium Monkey
Advanced User
Premium Member
Joined
Mar 22, 2017
Messages
6,264
Reaction score
13,365
Location
New England
I have been trying to find some time to screenshot my settings and load them up to ask about this, but I also regularly receive brief (1-3 seconds?) audible K alerts before JBV1 mutes. I have the native V1 K muting set at 30 seconds. It happens for signals that are below my native breakthrough strength setting of 5 and also while I'm under the JBV1 silent ride speed setting.
Your settings are to unmute for initial alerts at 4 dots or if the signal exceeds 6 dots, with a 30 second K mute in other situations.

As johnboy00 suggested above, you can use a hard 3 second K band mute to bridge the ~300ms gap between the initial alert and when JBV1 can respond with a mute command. Change the K band mute timer to 3 seconds, and disable unmute for initial 4+ and unmute at 6+. (Note: You change these settings under "Profiles" as they are stored on the V1, not in the app settings like you showed above. Once you make this change, I would recommend removing your time mute and rear mute settings in JBV1.) This will mute all K band alerts initially for 3 seconds and keep the detector quiet according to your JBV1 settings. Obviously you would not want a hard 3 second K mute if you encounter K band I/O, but luckily this is fairly rare in most of the country. You can configure the display options so that you still get a visual alert for these K band encounters (on the detector itself and/or on your phone), so you are aware there is a K band signal but without the noise.

I've been running a hard 3 second K mute with the detector dark during muted alerts but displaying the alert on my phone, and it works incredibly well. Good luck!
 
Last edited:

DMartinUA

Δ
General User
Premium Member
Joined
Mar 2, 2016
Messages
40
Reaction score
25
Location
Bama
Your settings are to unmute for initial alerts at 4 dots or if the signal exceeds 6 dots, with a 30 second K mute in other situations.

As johnboy00 suggested above, you can use a hard 3 second K band mute to bridge the ~300ms gap between the initial alert and when JBV1 can respond with a mute command. Change the K band mute timer to 3 seconds, and disable unmute for initial 4+ and unmute at 6+. (Note: You change these settings under "Profiles" as they are stored on the V1, not in the app settings like you showed above. Once you make this change, I would recommend removing your time mute and rear mute settings in JBV1.) This will mute all K band alerts initially for 3 seconds and keep the detector quiet according to your JBV1 settings. Obviously you would not want a hard 3 second K mute if you encounter K band I/O, but luckily this is fairly rare in most of the country. You can configure the display options so that you still get a visual alert for these K band encounters (on the detector itself and/or on your phone), so you are aware there is a K band signal but without the noise.

I've been running a hard 3 second K mute with the detector dark during muted alerts but displaying the alert on my phone, and it works incredibly well. Good luck!
Thanks for the advice. Your settings definitely make more sense to mesh the native V1 and JBV1 mute settings.

I was still getting audible alerts from the V1 for locked out stationary K band sources at very low signal strength (initial 1-2 dots). Or maybe that's not even possible, and I just don't see the initial 4 dots and it drops to 1-2 by the time I look up. But based on the programmed ramp up of the audible alerts with signal strength, I'm still fairly certain the initial strength of these instances is not 4+.

Since this didn't start occurring until I changed my JBV1 settings a few weeks ago, I suspect it has something to do with the 3 second JBV1 mute or the rear mute being active. Was there a reason you recommended disabling the JBV1 time mute and rear mute? I like to be made aware of K band due to a small town on my commute, but once it's alerted I'd rather it auto-mute itself so I don't have to push the button.
 

InsipidMonkey

Premium Monkey
Advanced User
Premium Member
Joined
Mar 22, 2017
Messages
6,264
Reaction score
13,365
Location
New England
Thanks for the advice. Your settings definitely make more sense to mesh the native V1 and JBV1 mute settings.

I was still getting audible alerts from the V1 for locked out stationary K band sources at very low signal strength (initial 1-2 dots). Or maybe that's not even possible, and I just don't see the initial 4 dots and it drops to 1-2 by the time I look up. But based on the programmed ramp up of the audible alerts with signal strength, I'm still fairly certain the initial strength of these instances is not 4+.

Since this didn't start occurring until I changed my JBV1 settings a few weeks ago, I suspect it has something to do with the 3 second JBV1 mute or the rear mute being active. Was there a reason you recommended disabling the JBV1 time mute and rear mute? I like to be made aware of K band due to a small town on my commute, but once it's alerted I'd rather it auto-mute itself so I don't have to push the button.
Can you post the JBV1 logs of the alerts that didn't seem to be properly muted? May give some clues as to where the issue lies.

I recommended you remove the JBV1 settings as they become redundant to what it sounded like you were trying to accomplish. I believe any app mute settings are additive with the native V1 muting, eg if you have the V1 set to mute for 3 seconds and JBV1 time mute set to 3 seconds, the JBV1 timer doesn't start until the V1 timer expires giving you a total muting time of ~6 seconds.

If you want to get an initial alert upon a K band signal then have it auto mute, what was wrong with your settings previously?
 

DMartinUA

Δ
General User
Premium Member
Joined
Mar 2, 2016
Messages
40
Reaction score
25
Location
Bama
Can you post the JBV1 logs of the alerts that didn't seem to be properly muted? May give some clues as to where the issue lies.
I thought about this, but I never thought to make a mental time stamp so that I could look at the appropriate logs. I hit a lot of locked out K sources every day.
I recommended you remove the JBV1 settings as they become redundant to what it sounded like you were trying to accomplish. I believe any app mute settings are additive with the native V1 muting, eg if you have the V1 set to mute for 3 seconds and JBV1 time mute set to 3 seconds, the JBV1 timer doesn't start until the V1 timer expires giving you a total muting time of ~6 seconds.
I thought the JBV1 timed mute would allow a signal to alert for the selected time value and then mute that signal indefinitely rather than adding the selected time value to the native V1 K mute. For example, assuming a LEO K band hit, native V1 would mute for 3 seconds, then alert to K band for 3 seconds, then JBV1 would mute that specific signal for the rest of its duration.
If you want to get an initial alert upon a K band signal then have it auto mute, what was wrong with your settings previously?
I am happy with my previous settings and they behaved nearly exactly as I wanted. I am only trying to solve why some locked out K sources alert initially when they should be natively muted.

Thanks for your help in figuring this out. I may leave my current settings active and see if I can get logs of a low strength locked out signal that gives an audible alert. I guess I could go ahead and exchange JBV1's rear muting for the V1 native K band rear muting.
 

Discord Server

Latest threads

Forum statistics

Threads
80,883
Messages
1,229,576
Members
20,496
Latest member
robasap
Top