arrow_back Back to Home
QUICK GUIDE

How to Debug GMVoice Fast

By Peter Fridrich · Published August 31, 2026 · 3 min read

A command did not work. Writing me an email about it does not help much, because I cannot hear what your phone heard. So do not describe it. Record it.

Five steps, five screenshots. That is the whole guide.


1. Tap the GMVoice logo

Top-left corner of the main screen. That opens the debug options.

GMVoice main screen with the GMVoice logo in the top-left corner highlighted and a label saying to tap the logo for debug options.
The logo is the debug menu. Nothing else on that row matters here.

2. Tap "Field Debug: Start recording"

From that moment the session is being captured. Close the panel, tap START, and train exactly as you normally would. Do not go easy on it. I need the real problem, in the real conditions where it happens.

The GMVoice debug panel with the 'Field Debug: Start recording' row highlighted, above Export Field Debug and Send Field Debug.
One tap. A red REC pill on the main screen means it is running.

3. Tap REC every time a command misses

During the workout the red REC pill sits above the command list. Every time a command is ignored, misheard or does the wrong thing, tap it. It drops a marker at that exact second and keeps the audio and the pipeline details around it, so I go straight to the problem instead of listening through the whole workout.

Tap it as often as you need, there is no limit. A capture with markers is worth far more than one without.

GMVoice listening for commands during a Free Lift workout, with the red REC pill highlighted as the button to tap whenever a command does not work, and the STOP button marked.
Command missed? Tap REC right away. The marker is a timestamp, so tapping it later points me at the wrong part of the audio.

4. Finish, stop, send

When the workout is done, in this order:

  1. STOP stops voice commands.
  2. GMVoice logo opens the debug menu again.
  3. Field Debug: Stop recording.
  4. Send Field Debug.
The GMVoice debug panel with numbered arrows pointing at the GMVoice logo, 'Field Debug: Stop recording' and 'Send Field Debug'.
Stop first, then send. If you would rather not send it over the internet, use Export Field Debug and pull the zip off your phone yourself.

5. Your email and one line about the session

Two fields. The email is so I can reply to you about this exact session. The message is so I know what you were trying to do.

One or two sentences is enough. For example: "Free Lift with AirPods, said turn on about ten times, three did nothing." Then tap Send.

The GMVoice 'Send to developer' dialog with an email field and a message field describing the session, and Cancel and Send buttons.
Short is fine. Just say what you were testing and what went wrong.

What actually gets sent

Nothing is recorded until you start a session yourself, and nothing leaves your phone until you tap Send. The capture is used only to diagnose the problem you reported. Details in the privacy policy.

Three things that break a capture

That is it. If you want the long version (Voice Guard setup, markers, notes, what I look at first), read How to record a Field Debug session. Otherwise just email me at contact@gmvoice.tech.


Related guides

Planning your next session? GM Manager builds Speediance workouts in your browser.

Buy me a coffee