CP notification beep / sound not always working

[Phil Humphreys]

This has been a problem for me for several months. During this time, I have used an iPhone 14 and more recently an iPhone 17 for MapRun. I have used several iterations of the MapRun app as they have been updated since last summer. The problem persists. A friend, who uses an android phone, has the same issue.
Whilst doing a MapRun event (although it seems more of a significant issue when I'm SiteChecking a course) my phone will usually register a CP as expected - vibration / beep (I use Chimes 3 tone) / CP changing pink to green... but occasionally, and for no obvious reason, there is no audible beep. Vibration / pink - green CP work registers correctly, but no sound. Then, later, maybe after a few more CPs, the sound will work - again, for no obvious reason. Whilst SiteChecking earlier in the week, the audible beep worked less than 50% of the time.
Any thoughts?

[Peter Effeney]

Sorry to hear of the issues. MapRun is regularly tested to ensure it works correctly on a range of phones.
There is a page on recommended phone settings here: https://maprunners.weebly.com/phone-settings.html

Following is information specifically targeting Sounds/Vibration on Punching. If you still have problems please email specific details to [e-mail].

The following instructions use examples for an iPhone, but there are similar settings on Android. Explore the specific settings for your Android Make and Model, as there are significant differences across the range of Android Devices (and so it is difficult to give precise general instructions).
MapRun is designed to work both in foreground and background modes, and in both modes, it should track the participant, detect controls, punch, beep/vibrate, keep time and score.
Foreground mode is when MapRun is visible on the screen of the phone. Background mode is when the focus has moved to another App or the screen is blank (either blanked by the user, or timed out as determined by settings).
MapRun needs location permissions for “While in Use”. It does not need “Always” as MapRun only tracks the participant during a run/event. (between “Go to Start” and punching Finish).


Options and Settings in MapRun

There is a range of settings that the organiser of the event and/or the user can set that affect sounds/vibrations:
o Setting: No sound or vibration upon punching (for “silent” punching)
o Setting: No sound of vibration upon punching EXCEPT Start and Finish (similar to above)
o Setting: Inhibit GPS-based punching at these controls: <list of controls>
o Setting: Alert Sound to select a “unique” sound, as this helps with issues such as mistaking an incoming text message for a punch, or mistaking the punch sound from another nearby participant.
If you are having problems, set this to “Beep 1 Simple” (the default value)
This is the “belts and braces” option, as upon punching:
    1. The App plays a beep sound - as a direct sound made by the App, AND
    2. Initiates a “Notification” that beeps and vibrates
(In some cases you may detect two beeps close together if the notification is delayed slightly by the phone)
For any other option/value, the App relies upon “Notification”s only.


iPhone Settings

The following settings can have a bearing on the sound/vibration when punching, as detailed in subsequent sections:
- Mute switch/button
- Volume control
- Permissions in Settings > General > Background App Refresh > MapRun
- Permissions in Settings > Notifications > Display As & Show Previews (Always) & Notification Style > MapRun > Alerts - Sounds (on) & Show Previews (Always)
- Focus modes
- Low Power Mode

Test Punch

MapRun now has a “Test Punch” button on the home screen. This can be hidden by a setting in “Options and Settings”.
- This is a good first step to make sure vibration and sound is working the way you want/expect upon punching (S1 in this case).
- If not, the quick things to check are:
   o Ring/Silent switch
   o Volume setting
   o Settings > Notifications > MapRun > check that everything you want is switched on including “Lock  Screen Appearance” at the bottom of the page, and make sure “Show Previews” is set to Always.
- Whatever this button does, should be replicated when you punch a control with the MapRun screen displaying on your phone.

Once the screen of the phone blanks or you open another App, so that MapRun is not in focus, some other factors come into play:
- Is MapRun allowed to run in the background?
   o Settings > General > Background App Refresh  
        Make sure, at the top, “Wi-Fi & Mobile Data” is selected
        Make sure MapRun is listed and the switch is on
   o The telltale sign of this NOT being enabled, is incomplete tracking with straight “track lines” between points where MapRun was in the foreground.

- Focus modes should be set to off (Do Not Disturb, Reduce Interruptions, Personal etc)

- If you have a watch that displays notifications from your iPhone you will probably see the notification on your watch instead of the locked phone (depending upon settings).

Comprehensive Testing of your Phone

MapRun is regularly tested to ensure it operates as designed. But to ensure it is working on your phone in the way you want, nothing beats testing your phone in an actual MapRun Event.

On site at an official event or a CheckSites event, you can walk to the Start (alternately with MapRun 1.in the foreground or 2. the screen blanked) to check that you get the outcome you expect.
You can simply then tap the “Home” button on the top left to exit from your test run, and repeat the process.

Another approach is to create a simple QuickStart event at your home location.
You just need a minimalist course of  say S1, 31, F1 (F1 can be at the location of S1, and 31 should be 50m away).
- Do some testing with MapRun visible on the screen and with the screen blanked
- Change Phone settings until you get the outcome you desire.