Because i am sure most consumers would like the option to just have it on the detectornwhen they do not want to plug into their phone.I would not want my Auto lockouts built in to the detector. That would be so limiting compared to what I currently have and use.
Then if I'm using a GPS with JBV1, why use the one in the detector when the phone's GPS is programmatically closer?
Wait, if you are going to have JBV1 running anyway, why would you even need GPS or lockouts in the V1???
I'm not sure if you understand JBV1 users or how enjoyable it is to use JBV1 every time we drive.
I only post like once a year on social media personally. The problem for me is that my interests are too niche and specific for most people to care. I would literally only be posting about radar detector stuff, audio gear, classical piano, niche baseball stats, car racing, etc. And for those interests it doesn't make sense for me to post on social media when there are entire forums of like-minded people devoted specifically to each niche. Posting about that stuff on social media just feels like shouting into the wind to me...Maybe he just realized twitter is a massive waste of time.
I get what you are saying... Without using JBV1, you are coming from a point of view that isn't entirely accurate. These same misconceptions pop up over and over.Because i am sure most consumers would like the option to just have it on the detectornwhen they do not want to plug into their phone.
It could be a toggle.what if rhe lock outs were share between the detector and the app, when you are on the go and dont have time to sync the V1 alone could remember your lock outs .
Also JBV1 could use the gps built in on the V1 to save battery to aid on the phone's battery consumption.
In the end there are thousands of non enthusiasts that would like the option for the V1 to handle those things without plugging into a complicated app.
Sent from my SM-N950U using Tapatalk
The average consumer wants a quiet detector, and auto lockout has this .I get what you are saying... Without using JBV1, you are coming from a point of view that isn't entirely accurate. These same misconceptions pop up over and over.
Here are some facts from actual use:
When I get in the car, I have three choices.
There is no "synchronizing" procedure when starting the car. Just start the car.
- I can leave the phone in my pocket,
- I can place it on the magnetic dash mount,
- or I can additionally plug in the USB cord.
If I leave the phone in my pocket: (This is also true of V1 Driver by the way)
JBV1 connects automatically with the screen off. I can get voice announcements from JBV1 through the phone's speaker or over bluetooth to the car's audio. All features are available, I just can't see what would be displayed. Also, Waze is running with the screen off as well if I choose.
If I choose to see the screen, I can either do so without the USB cord or with. (That determines whether I want to use Android Auto or not for that drive)
When not plugged in; JBV1 starts automatically and then starts Waze for me on the phone screen. All alerts are overlayed on Waze.
When plugged in; the phone charges and JBV1 starts automatically and is displayed on the phone and Waze is sent to the car's Android Auto screen.
Your concept of a "complicated app" is probably a little out of place. These apps can be used to their potential, but they aren't inherently complicated any more than any other app.
Your suggestion of having lockouts on both the detector and the app sounds a lot more like a logistical nightmare than keeping it all on one device. An app that automatically connects in the background whether the phone is viewable or not provides the same lockout functionality and features in both scenarios.
The largest battery consumption of any phone is it's screen. GPS is already active by default. There's very little difference between GPS usage of the phone itself in normal operation and while using a GPS centric app in most cases.
In my observations, thousands of non-enthusiasts don't use auto-lockouts (or use them well) anyway. The general population doesn't want a highly configurable detector. They want a detector that they can install in an amateurish fashion and slow down when in beeps.
Fair enough. There's a balancing act between quiet and effective. FWIW, the V1 was never meant for those that want to ignore alerts. Everything about it is about being sure that it alerts whenever there's a possibility of a legitimate signal.The average consumer wants a quiet detector, and auto lockout has this .
I think the average consumer would like a detector that can take care of low speed muting and GPS lockouts without an app. while it leaves the option open for enthiusast that want to continue to use it as it would.
I don’t think that’s true. Ka Guard was put in place (and the responsiveness/range hit along with it) to minimize alerts. TMF/2 was put in place to minimize alerts. Savvy was released to minimize alerts. The only thing VR doesn’t equip the V1 to do is lockouts of stationary falses, and that’s only because they’d have pay royalties to Escort, and the “lockouts are bad” schtick.FWIW, the V1 was never meant for those that want to ignore alerts.