News for 2017

    Wednesday, December 20, 2017

    What's new in this release?

    • Force Speaker audio option now works as intended: When enabled, sound plays to device speaker only. When disabled, sound plays to device speaker or BT audio connection (if any), but not both.
    • Force Speaker change no longer requires app restart to take effect.
    • Initial Device Volume default value changed from "100%" to "No change."
    • Fixed alerts could get stuck in Priority Alert Display.

    Master changelog for all releases.

    Tuesday, December 19, 2017

    What's new in this release?

    This update resolves the following issues:

    1. Marks system crashes the app when enabled and approaching a mark.
    2. Performance of the app degrades over the course of a few hours.

    Master changelog for all releases.

    Saturday, December 16, 2017

    What's new in this release?

    • App mute volume control for some auto mutes
    • Display option for peak signal strength
    • Current profile and sweeps now available in push dialog
    • K mute settings remain visible when K band is enabled

    Regarding the mute volume control:

    I was thinking about a master mute volume and also individual mute volume controls for all mutes (use master would be the default setting for individual mutes), including locked-out signals. That seemed unnecessarily complex to me from a user perspective, so I went with a single auto mute volume control for now. Lockouts, snoozes, user mutes, and Silent Ride still fully mute and are excluded from auto mute volume setting. If enough people really want it, I can make individual mute controls, even by band if there's enough interest in that, too.

    The mute volume controls the alert sounds only. Setting a >0 auto mute volume will not cause alerts immediately auto muted by direction, box, or K mute to be announced.

    Master changelog for all releases.

    Tuesday, December 12, 2017

    What's new in this release?

    • Audio settings reorganized by band
    • Audio option to play new bogey sound on new auto-muted bogeys
    • Alert sound bug fixes
    • Mute control bug fixes
    • Custom sweeps definition bug fixes
    • Overlay bug fixes
    • V1 "settings" directory renamed to "profiles"
    • New "settings" directory to be used for app settings export/import (coming soon)

    Master changelog for all releases.

    Saturday, December 09, 2017

    What's new in this release?

    • Custom sweep definition helpers (segments)
    • Bug fixes (auto dark, settings reload)

    I didn't quite finish the sweep definition helpers because I wanted to get some important fixes out. They work, but the segment a sweep may correspond to isn't on the button label when you return to the sweeps. Note that you don't have to use the seg buttons at all.


    Master changelog for all releases.

    Wednesday, December 06, 2017

    What's new in this release?

    • Settings button on V1 alert screen now shows menu: JBV1 Settings, V1 Profiles, Custom Sweeps, Alert Log, Exit.
    • Profiles/sweeps push dialog headers are now buttons for navigation to V1 Profiles and Custom Sweeps screens. Buttons inactive when speed >= 2 meters/sec.
    • Priority Alert Display mute memo now shows only alert-specific mutes (no more "Silent Rd" and "Sound Off" memos).
    • GPS tracking changes for Android 5.x.
    • Connection setting for length of time to scan for V1C-LE dongle.

    Master changelog for all releases.

    Sunday, December 03, 2017

    What's new in this release?

    • Auto Mute settings reorganized by band.
    • Time Mute settings optionally mute alerts after selected periods of time (off, 3 secs, 5 secs, 10 secs).
    • Mute flag added to alerts in alert list, shows most significant mute rule set on each alert: (L)ocked out, Snoo(Z)ed, (U)ser muted, (B)ox muted, (D)irection muted, (T)ime muted, (K) muted.
    • Alert audio fixes (?)

    Master changelog for all releases.

    Saturday, December 02, 2017

    What's new in this release?

    • Display option to show locked-out alerts in overlay
    • K muting bug fixes
    • GPS tracking improvements
    • New holiday-themed app icon (@InsipidMonkey)

    This should fix a bug where K-band alerts were being "K Muted" outside the rules defined in active V1 profile.

    Master changelog for all releases.

    Thursday, November 30, 2017

    What's new in this release?

    • Mute control enhancements and fixes
    • New setting for priority conflict resolution
    • New settings category, Auto Mute, includes settings for rear/side muting by band and strength
    • New audio settings for initial device volume and announce direction first
    • New display settings for overlay position
    • New app icon (looks less like a tree to me, lol)

    Master changelog for all releases.

    Wednesday, November 15, 2017

    What's new in this release?

    • Option to hide status bar
    • Option to change alert priority
    • New General settings category
    • Mute control enhancements and bug fixes
    • Alert list management bug fixes
    • White listed alert bug fixes (alert log, map)

    Mute control changes: d

    When there's no active alert, the speaker button functions normally as a sounds on/off toggle. Tap it when it's green and it turns gray and everything gets muted automatically. Tap it when it's gray and it turns green and only auto-muted alerts (lockout, snooze, silent ride, K muting, OTB/ITB) will be muted.

    When there's an active, un-muted alert, the green speaker icon will be much larger (for easier access while driving). Tapping the large speaker icon will mute V1, and then the speaker icon will shrink back to its original size, turn gray, and be disabled. The speaker icon will automatically turn green and be re-enabled when V1's mute expires (about 10 secs after no alerts, or when V1 wants to un-mute for a new bogey).

    The same thing will happen with active, auto-muted alerts, except that you don't have to tap a button. The speaker button will turn gray and be disabled until V1's mute expires.

    You also can mute an alert with a push of V1's volume knob, and that will also mute JBV1 and trigger the same changes to the speaker button. The button will turn green and be re-enabled automatically when V1's mute expires.

    Muted alerts appearing in the Priority Alert Display area will have a mute memo that indicates why the alert is muted:

    • "Mute" - Muted by the user with either the JBV1 speaker button or the V1 knob
    • "Silent Rd" - Muted because the current GPS speed is below the Silent Ride setting
    • "OTB Mute" - Muted because the frequency is outside of all defined boxes for that band, and mute OTB option is enabled for that band
    • "ITB Mute" - Muted because the frequency is inside of a box defined for that band, and mute ITB option is enabled for that box
    • "K Mute" - Muted because of K muting rules defined in the currently active profile
    • "Sound Off" - Muted because sound has been toggled off

    There are no mute memos for locked out or snoozed alerts because they will never appear in the Priority Alert Display.

    One other change worth explaining:

    Since alerts can be locked out and snoozed, other un-muted alerts can and will be promoted to the top of the alert list in JBV1 and will be the ones for which JBV1 audibly alerts. V1 has its own algorithm for deciding which alert is the priority alert, and that alert will be the one for which V1 audibly alerts. When V1's priority alert is locked out or snoozed, or when JBV1 and V1 otherwise disagree on the priority alert (V1 Priority option disabled), JBV1 will mute V1 and only JBV1 will audibly alert. This is important to know if you depend mostly on audible alerts.

    Alert priority changes:

    There's a new setting (General) to toggle V1 Priority:

    • Enabled - V1 tags an alert as a priority alert and is the one V1 audibly warns about. JBV1 respects this tag and will show this alert in the Priority Alert Display, unless that alert is snoozed or locked out. After the priority alert, JBV1 sorts by band (Laser > Ka > K > Ku > X) and strength for active alerts. Locked out alerts and snoozed alerts are pushed to the bottom of all active alerts.
    • Disabled - JBV1 sorts all alerts by band (Laser > Ka > K > Ku > X) and strength for active, un-muted alerts. Muted alerts will be below all un-muted alerts, followed by locked out and snoozed alerts, followed by inactive alerts. The alert at the top of this list is considered to be the priority alert if it isn't locked out, snoozed, or inactive.

    I plan to work signal orientation into my sorting soon, but for now, it isn't considered.

    As always, please report any issues you encounter, and feel free to ask questions.

    Master changelog for all releases.

    Wednesday, November 15, 2017

    What's new in this release?

    • Fixed bug where auto lockout learning was creating multiple lockouts for same signal location.
    • Fixed bug where removing a lockout only removed the best match instead of removing all applicable lockouts (thanks to @Stoopstroop for the report).
    • Fixed bug where laser audio alert began looping after creating a manual lockout.

    In 0.9.22 a new, cleaner-looking layouts (esp. portrait) for when Priority Alert Display is disabled in settings.

    Cleaner Look

    Master changelog for all releases.

    Friday, November 10, 2017

    What's new in this release?

    • New priority al1ert message area under the priority alert frequency shows band and reason muted (if muted by rule) (landscape layout also shows priority alert front/rear antenna bias)
    • Revised compass heading algorithm to be more accurate at slow speeds and not revert to N when stopped (stupid Android location services)
    • Revised some alert log headers to show speed and distance units instead of "Speed" and "Distance"
    • Alert log day maps will map an entire day's worth of alerts, with auto zoom to fit all markers
    • New map options to toggle alert markers and lockout markers
    • Map now loads additional lockouts as they come into view when scrolling around the map
    • Auto lockouts!
    • Bug fixes

    Be careful with auto lockouts, especially if you need whitelisting (not there yet). The current auto lockout settings, in addition to the tolerance/drift and radius options that also affect manual lockouts, are as follows:

    1. Enable/disable globally
    2. Enable/disable by band+laser
    3. Maximum signal strength
    4. Learn count (signal hits in same location before auto learn/lockout)
    5. Unlearn count (consecutive signal misses in same location before auto unlearn)
    6. Learn/unlearn interval (amount of time that must pass between hits and misses at a location before either is incremented/reset)

    I'm sure there will be more settings to come as the auto lockout algorithms evolve.

    Master changelog for all releases.

    Friday, November 03, 2017

    You may have to click this link from your device:

    Or you may be able to find it without the link (IDK).

    Here's a link to the play store listing if you want to see it from your computer:

    It defaults to working only with LE adapters. If you want to try it out on a non-LE adapter, wait for the LE connection attempt to timeout, then tap Options, then Settings, then Connection, then disable the LE option.

    I think most of the app is self-explanatory. There is a Help item on the Options menu for basic help. This is my first mobile app, so I expect some issues when rolled out to the masses. Please be patient as I try to correct issues that arise. I can only work on JBV1 in my spare time, and that will limit how responsive I can be.

    Known issues:

    • On rare occasions (for me anyway), the activity stack gets messed up after backgrounding the app. I'm working on that. If any Android dev experts want to help me with that, please send PM. I would be extremely grateful!

    One more thing:

    • Normally, you would use the Back button to completely exit JBV1. If you background it with the home button and start Waze or some other app, and you get the alert overlay, tap on the overlay to bring JBV1 back to the foreground. After doing that, the back button will not exit JBV1, but will go back to the previous app instead.

    Master changelog for all releases.

    Tuesday, October 31, 2017

    JBV1 is nearing an open beta test. This week, I'm trying to finish the V1 profile functionality (settings + custom sweeps) and fix a couple remaining bugs. I hope to announce the open beta this weekend. After I fix any issues arising from the open beta, I'll release to production and begin working on alternate screen layouts (who doesn't like options?) and auto lockouts.

    Also, since this is my first mobile app, I'm pricing it accordingly. JBV1 will be free and there will be no features reserved for a paid version.

    Tuesday, October 31, 2017

    I've been slowing down a bit on JBV1 development, but I haven't stopped. Here's a demo of what I have so far on alert logging:

    I've also tweaked the alert screen a bit. Here's the latest from a Demo run in an emulator:

    Alert Screen Demo

    Tuesday, September 26, 2017

    I'm also testing some frequency highlights to see if they help while driving.

    Wednesday, September 20, 2017

    It's been really great having a working demo mode. This allows me to test alert behavior in an emulator, which means my V1 can stay in my car.

    Recent changes:

    1. Alert tracking (history) optimized for efficiency.
    2. Active alerts now sorted by Laser, Priority Alert, Band (Ka, K, X), Strength.
    3. Alert logging.
    4. New bogey notification sounds:
      1. X band = Dee-Dee-Deet (standard V1 bogey lock signal)
      2. K band = Dee-Dee-Brap
      3. Ka band = Dee-Dee-Brap-Brap
      4. I really like these, but yes, there will be an option to turn them off.?

    Tuesday, September 12, 2017

    Here's where I am with JBV1:

    • New arrows distinguish frequencies that are in-the-box (ITB) versus not. For now, I have the boxes at +/- 100 MHz from base (24.150, 33.800, 34.700, 35.500), but eventually those will be settings. I'm not happy with how the side arrows turned out and will be redoing those.
    • Arrows now scale relative to signal strength.
    • Long-clicking the priority alert area (the big signal strength meter and arrow) will change the priority alert display mode from ENABLED to BOTH to DISABLED. ENABLED shows priority alert in the priority alert display only, so only other alerts will appear in the alert list. BOTH shows priority alert in the alert list also. DISABLED turns off the priority alert display and the priority alert will only appear in the list along with any other alerts. When they appear in the alert list, priority alerts are highlighted with a slightly different background color. Soon, the priority alert display won't light up at all when moving under a minimum speed, regardless of the display mode selected.
    • The text colors of frequencies in the alert list now match the colors of the respective strengths and arrows.
    • Clicking the digital speedometer will switch speed and altitude from English units to metric.

    The road map from here:

    1. Logging of alerts to a SQLite database.
    2. Manual lockouts
    3. Marking (for RLC or whatever)
    4. Auto lockouts

    Numbers 2 and 3 might get reversed.

    Let me know what you think.

    The screenshot here is from a shopping center parking lot. It show's K band disabled, which is obviously not the case, so I need to fix that.

    In the Box

    Thursday, September 07, 2017

    Sunday, September 03, 2017

    So I've been busy with my JBV1 app for Android. In the last few days, I added the following:

    1. Indicators for enabled bands and a few other settings. I eventually plan to have settings files for on-the-fly changes, but I like knowing what's on and what's not, without depending on a file name for clues (and not accidentally turning something on/off, or testing and forgetting to change back later).
    2. Character-based arrows replaced with better-looking images. These are easier to "read" and, well, just look nicer.
    3. Signal strength dot colors are now yellow for first 4 dots, orange for next 2 dots, and red for last 2 dots.
    4. V1 mute on/off.
    5. V1 display on/off/auto. Auto setting turns display on during alerts and off when no alerts.
    6. GPS speed and elevation. I eventually will use speed for auto muting and who knows what else. Elevation is just a personal preference, as I sometimes drive in and around the Smoky Mountains, and I like to know my elevation. Besides, since I need GPS for speed anyway, I might as well get elevation, too. I've changed my mind on GPS lockouts, but I need to do a lot of reading on how best to go about it.

    Let me know what you think!



    Split Screen

    Tuesday, August 29, 2017

    Saturday, I decided to download Android Studio and check it out. Below are some screenshots of my very first Android app! I'm calling it JBV1. It works with both V1Connection and V1Connection LE.

    Each alert has a signal strength meter for each of the antennas. For minimum CPU usage and small memory and storage footprints, I'm using characters for everything (no images).

    Before too long, I hope to have it announcing the frequency of the alert, showing enabled bands, auto connecting to last device, and auto stopping after a timeout period. Except for trying to figure out all the nuances of screen layouts and styling, this is fun stuff!

    Ka Band 1 Ka Band 2 Ka Band 3

    Bluetooth is a registered trademark of Bluetooth SIG, Inc.
    iPhone and iOS are registered trademarks of Apple Inc.
    Android, Google Play, and the Google Play logo are trademarks of Google LLC.
    TMG is a registered trademark of Chen, Kuan-Ming
    Valentine One, V1, V1connection, All-Bogeys, Logic, Advanced Logic, and Valentine One Generation 2
    are registered trademarks of Valentine Research Inc.