Frequency Files · Beta

Tester Guide

Everything you need to install the beta and send a bug report that we can actually act on. Two minutes, once — then you are set for the whole test.

Showing steps for

First

Keep this guide on your phone

Add this page to your Home Screen so it is one tap away while you test — you will want it open the moment something goes wrong.

iPhone: tap Share at the bottom of Safari, scroll down, tap Add to Home Screen, then Add.

Android: tap the menu at the top right of Chrome, then Add to Home screen. Chrome may offer to install it for you — either way works.

It is a guide, not the app, and it holds nothing about you. When testing wraps, press and hold its icon and delete it — that removes it completely.

iPhone · TestFlight

Install the beta

Get TestFlight, then the app

  1. Install TestFlight from the App Store. It is free and made by Apple — it is how every iPhone beta is handed out.
  2. Open the Frequency Files invite link below, tap Accept, then Install.
  3. The app lands on your Home Screen with a small orange dot beside its name. The dot means beta — that is correct.

Note your build number

Open TestFlight Frequency Files. The version and build sit at the top, reading something like 1.0.0 (15).

Include it in every report. A bug in one build is often already fixed in the next, and without the number we cannot tell which you hit.

iPhone · Reporting

Send a bug, the right way

Screenshot, then Share Beta Feedback

The moment something looks or sounds wrong — while you are still in the app:

  1. Take a screenshot: press the side button and volume up together.
  2. Tap the small preview in the bottom-left corner before it fades. Circle or arrow the problem if you want.
  3. Tap Share at the top right, then Share Beta Feedback.
  4. Write a sentence or two about what happened, then tap Submit.

Why this beats a text message

Apple attaches your exact iPhone model, iOS version, the app build, battery level, free storage, connection type and screen size to that screenshot, and drops it straight into our console. A screenshot sent by text arrives with none of that, which usually means the bug cannot be reproduced — and a bug we cannot reproduce is a bug we cannot fix.

No screenshot? Report it anyway

Open TestFlight Frequency Files Send Beta Feedback. Same destination, same attached details. You can add screenshots from your camera roll there too.

If the app quits on you

Open it again. TestFlight will ask whether to send the crash details — tap Send, and add one line about what you were doing when it happened. That single line is what turns a crash log into a fix.

Android · Google Play

Install the beta

Join the test, then install

  1. Open the tester link below in Chrome.
  2. Tap Become a tester, then Download it on Google Play.
  3. Install it like any other app.

Two things that trip people up

Firefox and some security add-ons block the opt-in page — use Chrome. And you must be signed in to Play with the exact Google address that was added as a tester. If Play says the app is unavailable, wait a few minutes and pull down to refresh; access takes a moment to reach your account.

Note your build number

Phone Settings Apps Frequency Files → scroll to the bottom. The version reads something like 1.0.0 (15).

Include it in every report. A bug in one build is often already fixed in the next, and without the number we cannot tell which you hit.

Android · Reporting

Send a bug, the right way

Android is different from iPhone

Google Play’s tester feedback box takes text and a star rating only — it will not accept a screenshot. So on Android the screenshot goes by email, using the button further down this page. It arrives with your device details already filled in.

Take the screenshot

Press power and volume down together. Crop it to the problem if you like — a wide shot of the whole screen is fine too.

If it is something that only shows in motion, record the screen instead: swipe down twice from the top and tap Screen record.

Email it with the details attached

Use Start a bug report below. It opens your mail app with the address, the subject and the questions already written, and your device details filled in at the bottom. Answer the questions, attach the screenshot, send.

It goes to niko@savagestud.io — straight to the person fixing it, not into a group thread.

Optional: leave private feedback in Play too

Text only, but it lands beside your install in the developer console, which is useful for the small stuff:

  1. Open the Play Store and tap your profile icon at the top right.
  2. Tap Manage apps & devices Beta.
  3. Tap Frequency Files, and under Private feedback to developer tap Write feedback.
  4. Write it, then tap Post.

It stays private — it never appears as a public review on the store.

Every platform

What makes a report fixable

  • One bug per report. Three problems in one message becomes one problem that gets solved and two that get lost.
  • The build number. From step 2 above.
  • What you did, what happened, what you expected— in that order, plainly. “Tapped play on Deep Rest, sound started then cut out after about ten seconds, expected it to keep going.”
  • Roughly when it happened. A time and date lets us match it to the server logs.
  • Whether it happens every time or only happened once. Both are worth knowing.
  • If it is audio — the track name, which of the four channels Tonalities, Nature, Music, Voice, and roughly how far in. Audio bugs are almost impossible to find without that.
  • Steps to make it happen again, if you can work them out. This fixes more bugs than everything else on this list combined.

Please do not text screenshots

Screenshots sent by text or DM arrive stripped of every detail above and get buried in the thread. If you have already sent some that way, no problem — just re-send them through the route on this page.

The shortcut

Start a report right now

This is the Android route. On iPhone, TestFlight is still the better path — but if you cannot get it to work, this always does. It opens your own mail app with everything pre-filled. Nothing is sent from this page.

Your device, as we see it

Read from this browser and used to fill in your report. It stays on your phone until you send it.

Device
Operating system
Browser
Screen
Window
Home Screen install
Connection
Language
Time zone
Captured
Start a bug report

Also worth testing

The web version

Frequency Files also runs in any phone or desktop browser — same account, no install. If you find a bug there, report it by email with the button above; the device details will already be correct.

When testing wraps

Deleting everything

iPhone:press and hold this guide’s icon on your Home Screen → Remove App Delete App. Do the same with the beta app when we ask, and with TestFlight if you are not testing anything else.

Android:press and hold this guide’s icon on your Home Screen → Uninstall. Do the same with the beta app when we ask.

Neither leaves anything behind on your phone. Thank you for testing — the specific, unglamorous reports are the ones that make the release good.