Known Issues

Although I'm trying my best to make DSRC as perfect and bug free as possible, it's getting quite a complex 'beast', and every now and again, I screw up, Google changes the rules, or I just can't get the app to do what I want it to...

This page is to let users know of any restrictions, or bugs that have been found, and hopefully where possible some form of 'workaround' to keep it up and running until I can get it sorted.

Thank you for your patience...

Known issues:

  • V3.0 - Medium - Race/Results - HTML viewer not working (file access denied). Cause - Google change with Android 11. Fixed with V3.11


  • V2.6 - Minor - Race - Edit previous race may not contain the correct reference to the races results file (.pdf or .html). Fixed with V2.7.


  • V2.5 - Medium - Crash Recovery - Race number is not being saved, so post recovery, it would be at 1. Fixed with V2.6

  • V2.5 - Minor - Results - Series PDF results SHARE - External Share - Send, does not use the correct filename for title, but actual file shared is correct. Fixed with V2.6


  • N/A - External Devices - Non-ESP firmware e.g. Arduino - The current Network_All_xxx version of the DSRC firmware was developed around ESP8266 architecture, and works fine. But it was recently come to light that there are differences in the base variable Integer between this and some Arduino boards. Namely the size allocated to an Integer being only 2 bytes, whereas the ESP8266 allocates 4 bytes.

This basically means that the longer duration periods for Abort/Postpone, etc. are 'curtailed', and seen as negative. This screws up the flashing functions i.e. they stop flashing immediately (instead of flashing for an extended period i.e. until cleared by DSRC, or the period expires).

I have not published a revised Arduino specific version to cover this, as I'm not sure anyone is using Arduino (plus some wifi module) as yet.

But I do have a solution:

  1. Reformat the stored period timers to seconds (normally milliseconds) to make them within the Arduino Integer range (e.g. 1500000 becomes 1500)

  2. At usage points (which are type Long calculations), rescale to milliseconds, by multiplying period by 1000 ( e.g. 1500 becomes 1500000)

If anyone requires help on this, please contact via email, and I can provide a copy of my development Arduino code :o)

  • V2.1 - Race Screen - AutoMute button not displaying correct state post Start Abort, if it was ON at that point i.e. Still RED, when it should be GREEN. Fix ed with V2.2


  • V2.0 - Final positions for single and mixed fleet containing a class fleet can be incorrect (i.e. show a tie) if finish times between competitors are identical, but the number of laps if different - Example boat A completes 5 laps, whereas boat B completes 4 laps, but the last timings are the same (i.e. they crossed the finish line together). (Solved in V2.1)


  • V2.0 - WiFi light control only - Single start automatic cancel post General Recall not correct, but manual cancel is. (Solved in V2.1)


  • V2.0 - BT connection status icon is not visible on Race Screen. (Solved in V2.1)


  • V1.99 - Android 10 storage functions not working correctly. (Solved in Bug Fix release V1.991)


  • V1.97 - If Pursuit race has negative starts greater than -0:30 (example -1:30), the the 20 seconds announcement before those starts will be slightly wrong, in that a double "Minus" will occur (example - "Minus minus one minute thirty start in twenty seconds").(Solved in V1.98)


  • V1.79 - If race data is present (race run, but reset not yet performed), then exiting the Race Screen, and then selecting Competitors 'crashes' the app. (Solved in V1.8)


  • V1.79 - Although a user may select app 'Exit', Android may not actually 'kill' it off... This can lead to the same series file being used, when a new one was expected. (Solved in V1.8 by the app ensuring the series file name is cleared when Exit is selected)


  • All versions running under Android 8.1 Go and Android 9 - WiFi relay status fails. (Solved in V1.9. DSRC now checks the IP instead of SSID)

Apparently Google has changed the required permissions to needing FINE_LOCATION before WiFi status can be requested successfully.

And as DSRC doesn't current request this additional permission, it thinks contact with the WiFi relay module has failed (as it checks for connection the SSID of 'DSRC_WiFi_Relay').

As I currently do not have access to any devices running either 8.1 or 9, I am currently unable to develop and test a fix.

WORKAROUND - Set the WiFi SSID (via Settings Screen) to '<unknown ssid>'.

WARNING - Although this should allow the WiFi relay to operate, it's connection status will always be considered as 'good', regardless of the links actual state i.e. the Wifi Status icon will always be 'green'.


  • V1.6 Pursuit race - First post 'go' does not announce 30 seconds to go, or sound beeps/speech at 10, 5, 4, 3, 2, 1, but start is sounded. (Solved in V1.7)


  • V1.4 Sailwave series - If post race edits are made, and saved, then multiple entries will be made for the same race in the Sailwave Series file (Solved in V1.5)


  • V1.4 On some test devices, the Google Text To Speech initialisation can take 6-8 seconds from entering Race Screen. Note - I have only seen this on the Asus Nexus 7 (old version), so on most devices the delay will be short. I would advise doing a test of pressing Start soon after entering the Race Screen to see what delay there might be...


  • V1.2c - Landscape PDF output - As I’ve increased the column 1 width to accommodate long helm names ‘better’, the SC logo (if present) has increased in size also (as it’s also mapped to column 1)

Bugs:

  • V1.4 - RC Countdown - (now solved in V1.41, but I'll leave it here just in case someone did download V1.4 only)

On first startup, the app should check if there is an existing sound file (/files/DSRC_Countdown_sounds.txt), and if not found, create one using a example countdown.

Symptoms - app crashes on Race start if RC Countdown is active

The example should look like this:

1:05 race countdown starting in 5 seconds

1:00 60 seconds to the start

0:55 55

0:50 50

0:45 45

0:40 40

0:35 35

0:30 30

0:25 25

0:20 20

0:15 15

0:12 starting on the horn in

0:10 10

0:09 9

0:08 8

0:07 7

0:06 6

0:05 5

0:04 4

0:03 3

0:02 2

0:01 1

0:00

This doesn't seem to be working currently, so the workaround is to create one manually by:

  • From Main Screen - select Settings

  • Scroll down until you find 'Debug additional Info', and select it (extra edit options should then appear immediately below)

  • Select Edit RC Countdown info, to display internal editor (which in this case will display blank text)

  • Enter countdown text (cut & paste from above if you like), and press 'SAVE'

  • Remember to deselect Edit RC Countdown info (so you don't get lots of debug info displayed)

And that should be it. You can of course download your own existing (or created externally) file, but it has to be named DSRC_Countdown_sounds.txt, and be in the apps /files area