JBV1 0.9.X Releases

    Saturday, March 31, 2018

    What's new in this release?

    • Google Drive Backup & Restore
    • New CSA options for minimum speed and map distance
    • Always On overlay now shows V1 mode letter / bogey counter
    • Margin settings for overlay
    • Optional over speed warning
    • New indicators for APO (Auto Profile Override) and GEO / PSL (reverse GEOcoding / Posted Speed Limit)
    • Bogey counter added to alternate portrait layout
    • Bug fixes

    Related Releases:

    Monday, March 12, 2018

    What's new in this release?

    • Resolves a CSA issue introduced in 0.9.70.

    Please update promptly if you use this feature.


    Related Releases:

    Sunday, March 11, 2018

    What's new in this release?

    • New overlay option: Always On
    • Long press overlay while alerting mutes all non-muted alerts
    • MANY multi-window mode fixes and adjustments

    I spent over an hour fixing (finally) and tuning multi-window mode. Work continues on Google Drive backup/restore, as time permits.


    Related Releases:

    Friday, March 09, 2018

    What's new in this release?

    • Added thumbs-up counter to CSA alerts on alert screen
    • Added style options for CSA alert map night mode
    • Changed when night mode style is applied to alert map to increase likelihood that the style is applied properly
    • NPE crash fix

    Known issue: When CSA alerts begin while app is backgrounded, the map isn't visible when app is brought to foreground. I hope to have this fixed soon.

    The new styles for night mode:

    Dark Dark Map Theme

    Aubergine Aubergine Map Theme


    Related Releases:

    Wednesday, March 07, 2018

    What's new in this release?

    • CSA alerts now include age on alert screen and in announcement
    • CSA alerts (simplified) now appear in overlay
    • CSA inset map widened, centered, and moved to bottom of alert screen
    • CSA maps show current location toward bottom of map
    • CSA maps now show variable 3D perspective with auto zoom
    • Weather radar alerting alpha now applied to position/bearing indicator
    • Signal graph now shows all raw signal strength data by antenna (used to show combined & sampled data)
    • Signal graph now auto scales to signal peaks, with intent to show relative strength over time instead of absolute strength
    • New option to show signal graph for each threat in alert list
    • New option for full-screen CSA map
    • New options for alert screen orientation lock and overlay background dim
    • Fixes NPE crash when device orientation changes, or multi-window mode engages, before current profile displayed

    Related Releases:

    Monday, March 05, 2018

    What's new in this release?

    0.9.65 fixes another problem with multi-window mode. Sorry for forgetting about this mode, and thanks to someone for crash reports while trying to use it. :)

    I also forgot about other changes:

    • New options for Alert Screen Flasher
    • Option to hide weather radar map location marker

    You can now control the flasher by band and initial signal strength. For example, I have mine set to flash on Laser and Ka band initial 4+, and nothing else.

    I haven't seen any CSA map feedback. Is anyone using that feature? I'm changing it up a little in the next release, adding some 3D perspective and a full screen option. Your location on the map is moved way down near the bottom of the map like below. I'm also removing the option for orientation to north, because that works best with a square-ish map and there just isn't room unless it's really (too) small.

    CSA Map Full Screen CSA Map Small


    Related Releases:

    Sunday, March 04, 2018

    What's new in this release?

    • CSA maps with auto zooming and auto day/night modes, option for orientation to current heading or north
    • Fixed multi-window mode crashes

    Map Fullscreen Map Small


    Related Releases:

    Wednesday, February 28, 2018

    What's new in this release?

    • Option to disable speed restriction on settings
    • Option to announce "out of the box" for OTB signals
    • Option to show weather radar image on alert screen background
    • Bug fixes

    Weather radar images require an API key from Weather Underground. If interested, create an account on WU, and then find the menu option to create an API key, using a project name unique to you, please.


    Related Releases:

    Wednesday, February 28, 2018

    What's new in this release?

    • Settings icon menu optimized for driving
    • Option to display alert screen distances in miles/kilometers instead of feet/meters
    • Alert list restyled a bit
    • Road names added to CSA alert display
    • Option to reverse geocode an alert location for easier same road match. This isn't fully tested, so be careful if you try it out.
    • Fixed title-less dialogs having empty space where a title would be if there was one (Android 5.x)
    • Other miscellaneous bug fixes

    Related Releases:

    Thursday, February 22, 2018

    What's new in this release?

    • New: Auto Profile Overrides (general)
    • New: Silent Ride Tracks PSL option (experimental)
    • New: Announce Bogey Count option (audio)
    • New: Long press large mute button mutes all non-muted alerts
    • New: Speed Limit Sign color option (white/orange)
    • Changed: Settings icon no longer hidden at speed
    • Fixed: V1 mode apply on profile push not working properly
    • Fixed: Profile push dialog, tapping OK without selection disables pushing until app restart

    Auto profile overrides:

    This feature is intended to be used for exceptions to the rule. If you often drive from A to B and need some profile changes along the way, create overrides in those areas and assign the appropriate profile to each area. You should leave your home area with no override, I would think, but you can do it however you like. Although it would probably be ok to create polygons for every state in the USA, it wasn't really designed for that, and I have not tested that use case for performance.

    When searching for a city, county, or state in the USA, search for "city, st" or "x county, st" or "state" for best results. For example:

    1. City:​
      • "baton rouge, la" (Geaux Tigers!)​
      • "atlanta, ga"​
    2. County:​
      • "east baton rouge parish, la"​
      • "fulton county, ga"​
    3. State:​
      • "louisiana"​
      • "georgia"​

    If you click on a search result, and you don't get either shaded polygon(s) or a box, you can't use that area for an override. Some very small towns you may not be able to use for an override. Sometimes you might get a large polygon with no shading. I get that for Texas. I think it's a Google Maps bug, because the code indicates its a closed polygon (required) and it shows up shaded after the polygon is simplified and saved in the database.

    After you've created one or more override areas, don't forget to enable this feature in General settings. Also, the crowd-sourced alerts settings are in the Experimental settings section. Let me know how it works for you in your area.

    And one more thing to remember: The auto profile overrides only require internet when you're searching for areas to use or when you want to see a saved area on a map. Operationally, the feature itself requires only GPS and uses zero data.


    Related Releases:

    Friday, February 16, 2018

    What's new in this release?

    • New: option to announce "in the box"
    • New: mute codes written to alert log
    • Fixed: alert screen dimmer activates when disabled
    • Fixed: alert screen activity could have multiple instances
    • Fixed: connections to non-LE dongle not closing completely
    • Fixed: audio volume reduced after phone call
    • Fixed: alert sounds play during phone call
    • Changed: force speaker option affects announcements only
    • Changed: when force speaker disabled, announcements play to car audio when streaming music, to device speaker otherwise
    • Changed: alert sounds and bogey lock tones always play on device speaker (sorry, had to do this to get better handling of announcements and phone calls)

    Related Releases:

    Friday, February 09, 2018

    What's new in this release?

    • New connection option: auto start delay (3-second default)
    • Master switch for alert screen dimmer
    • New dimmer options: exclude speedo and speed limit from alert screen dimmer, stay dimmed on muted alerts
    • New screen flasher option: use band or orientation for flash color coding
    • New marks option: "Other" mark text customization
    • New box options: OTB mute punch-through, OTB mute alpha
    • Old option "No Priority for ITB/OTB Muted Alerts" changed to "No Priority for Muted Alerts," and it works now
    • Bug fixes (app shutdown, overlay)

    Related Releases:

    Monday, January 29, 2018

    What's new in this release?

    • Improved V1C-LE connectivity
    • Improved auto start for Android 8.x
    • Improved multi-window support (7.0+)
    • Mostly static white text changed to orange for less wear on OLED screens and better night vision (speed is still green/white)
    • Alert screen dimmer option
    • Alert screen flash option
    • Hide navigation bar option
    • Toast messages restyled and color coded by category (green = info, orange = warning/attention, red = error)
    • Bug fixes

    I made a lot of changes to LE connectivity, hopefully for the better. I tested it exhaustively on three different brands of hardware (Google/LG, Alcatel, Samsung) running four different versions of Android (8.1, 7.1.2, 7.0, 6.0.1), and it's working pretty well. I was able to trip it up a little when pulling the plug on dongle power at the worst times, but it always recovered and reconnected. I wasn't able to test on 5.x, but I don't expect it to have any problems. I'll continue to work on making it smoother for brown-out starts.

    Hope no one minds the change to orange for mostly static text that stays in one spot on the screen for a long time. After only a few minutes, I started liking it even more. It's way better at night. I got the idea to change it after researching which colors are worst for wearing out AMOLED screens ("burn in"). Worst are blues and whites. Best are reds, yellows, oranges, and greens.

    I LOVE the alert screen dimmer, personally. I use it (60%) in combo with the alert screen flash for new, non-muted alerts. The flashes are color coded to the band, of course. :) I'm sure there will be tweaks in future releases. If you depend on the speedometer or speed limits, you may not want to use the dimmer. I could add an option to raise those items above the dimmer, if there's interest in that.


    Related Releases:

    Wednesday, January 24, 2018

    What's new in this release?

    • Addresses issues connecting to V1C dongles
    • New audio options for alert volume ramping by signal strength
    • Status bar icons revised

    Related Releases:

    Sunday, January 21, 2018

    What's new in this release?

    • Reverse geocoding (Internet required)
    • Speed limit display (requires reverse geocoding)
    • New status bar icons
    • Sweep sections fetched from V1 after each connection to ensure correct values are cached for display in Custom Sweeps definition screen
    • Elevation display removed
    • Fixed bug where enabling Always Mute V1 option would disable app bogey lock tone and announcement
    • Other minor bug fixes

    The reverse geocoding option is intended to be used for auto profile/sweeps pushing and speed-limit-based muting options to appear in a future release. The speed limit display option was added mainly because I was already getting the data in the reverse geocoding, so why not show it (disabled by default). Reverse geocoding (primary) and speed limits come from OSM (OpenStreetMap). When (not if) you find roads in your area with the wrong speed limit, or none at all, you can correct them in OSM. Just go to OSM web site, create a free account, and add or edit them wherever they're missing or incorrect. If you don't care about any of this, or you're using a dedicated device with no data, or you just don't want to use more of your data, you'll want to leave these options disabled. In the future, and if there's enough interest, I plan to try some no–data-required options for detecting state boundaries.

    The sweep sections for your V1 are what define the boundaries for your custom sweeps. For v3.8952 V1s, there's one sweep section: 33.360 - 36.051. For older V1s, there are two sections: 33.xxx - 34.770, 34.774 - 36.xxx (I don't have an older V1 and I don't remember what the xxx's are). No sweep may span a section boundary.

    Alert Screen


    Related Releases:

    Sunday, January 14, 2018

    What's new in this release?

    • On Android 6.0+, all required permissions are checked on app launch, and the user is prompted to grant any that are missing.
    • Fixes for notifications on Android 8.0+.

    If after launching you get the "draw over apps" permission screen, please enable for JBV1 and then hit your back button.


    Related Releases:

    Saturday, January 13, 2018

    What's new in this release?

    • Fixed issue where app could try to create an overlay when overlay permission has not been granted, resulting in a crash
    • Fixed issue where app could exit when dialog windows remain open, resulting in a crash on exit
    • Fixed issue where locking out an alert from the alert log might not lock out the entire alert trail if the trail was longer than the configured lockout radius
    • Long press on settings/profile/sweeps region of alert screen will display current sweeps

    Related Releases:

    Thursday, January 11, 2018

    What's new in this release?

    • Option to launch Daze* after connection to V1 (*Substitute W for D)
    • Alert log map fixes and enhancements
    • Fixed issue where lockouts with > 10 MHz tolerance could miss an alert frequency > 10 MHz from lockout frequency but within specified tolerance
    • Auto lockouts will now be deleted from database after unlearn count is reached (they used to hang around in case of future relearning)

    Alert log map enhancements:

    More info has been added to lockout markers, including created date, last seen date, and last visited date. There's a new menu item to toggle visibility of lockout circles. Long pressing an alert marker title will isolate that alert and any associated lockout for better visibility. This means that all other markers not related to the alert whose title you long pressed, or its lockout (if any), will be hidden on the map. Example (in thread)

    Alert Map Locked Out Alert Map Details


    Related Releases:

    Wednesday, January 10, 2018

    What's new in this release?

    • Auto start for V1Connection Android (SPP/non-LE)
    • Auto start improved for V1Connection LE
    • Auto start wake lock option now applies only to V1Connection Android
    • Option to not show disconnected icon on status bar when auto start enabled and JBV1 not running
    • Option for 125-meter lockout radius
    • Bug fixes

    If you're using auto start now, updating will kill the auto start service. After updating, you'll need to manually run the app once, or restart your device, before the service is restarted.


    Related Releases:

    Saturday, January 06, 2018

    What's new in this release?

    • Improved signal graph visibility
    • Application auto start (V1C-LE only)

    New connection options, some of which (Auto Start, Use Wake Lock) are for V1C-LE only at this time.

    If you're going to use Auto Start, be sure to first disable any automation app launching of JBV1. How much battery is used by the Use Wake Lock option varies greatly by device. On my Alcatel 5044R, it only uses about 3% overnight. On my old Galaxy S5 Active (original battery, very old), it uses a bit more. With Use Wake Lock disabled, no extra battery is used if nothing else is keeping the system from sleeping, but auto start generally won't happen until some other event occurs (power connected, button pressed, BT connection to car). I don't see this as a bad thing for dedicated devices. I'll look into auto start for the non-LE dongle when I have more time.

    If you're not using any lock screen security, Wake Display will also dismiss the key guard.

    Wake Display

    The Darth Vader voice (optional) is me, with some enhancements. :) I know it's a little cheesy, but I couldn't resist.


    Related Releases:

    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.

    Related 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.

    Related 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.


    Related 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)

    Related 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.

    Sweeps


    Related 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.

    Related 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 (?)

    Related Releases:

    Sunday, December 02, 2018

    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.


    Related 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)

    Related 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.


    Related 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


    Related 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.


    Related Releases:

    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.