Open data · checked 5 November 2026
Alarm answers and fixes, free to reuse
Every answer, fix and known bug from Will my alarm go off? in one JSON file and two CSV files, for iPhone, Samsung and other Android phones.
JSON, 120 KB
- Fixes, as CSV · 22 KB
- Answers, as CSV · 23 KB
- The JSON Schema · 17 KB
Free to reuse under CC BY 4.0, with credit. Every answer and fix links the pages it rests on.
What's in it
For each phone, what eight settings do to an alarm tonight, from Do Not Disturb to a phone that's switched off: the same answers, fixes and bugs the checker and the fix pages show, in a form your code can read.
-
3 phones
iPhone, Samsung and other Android phones. Other Android uses a Pixel's answers and menus.
-
8 settings
Each answered for the phone's own Clock app and for other alarm apps.
-
42 fixes
Each with the menus to tap and the problems it helps with.
-
7 known bugs
With the versions they hit, whether they're fixed and what to do.
Who it's for
Apps that ring alarms
Medication reminders, prayer times, habit trackers and alarm clocks. When a setting might keep your alarm quiet, show your user the menus to change on their phone, with the answers written for apps like yours.
Researchers and writers
What phone makers' help and Android's code say about alarms, and where we found nothing from the maker, what the tech press and owners report. Every answer links its sources and is dated, with what no source settles marked Not confirmed.
How to use it
Fetch the JSON from your app or website, or download it and ship it with your app. The files can be read from any website, and may be cached for an hour.
const res = await fetch('https://bedquitter.app/data/alarm-checker.json');
const data = await res.json();
// What Do Not Disturb does to your own app's alarms on a Samsung phone
const samsung = data.phones.find((phone) => phone.id === 'samsung');
const dnd = samsung.answers.find((answer) => answer.setting === 'dnd').app;
console.log(dnd.tag, dnd.line, dnd.pathText); The main fields
phones[] | One per phone: id, name, how and when it was checked (checked, checkedOn), and its fix page. |
phones[].answers[] | One per setting: setting, the phone's own name for it, and an answer for the Clock app (clock) and for other alarm apps (app). |
kind, tag, line | The verdict (ok, catch, depends, unsure, no), its short label, and what happens. sameAsClock says when other apps get the Clock app's answer. |
path, pathText | The screens to tap, as steps (menu, yours, search) and as one line. |
notConfirmed | True when no source we read settles it, on answers and fixes. |
phones[].otherAlarmApps | An extra row for other alarm apps on phones where battery limits hold them back, or null. |
phones[].fixes[] | id (stable), title, why, path, symptoms (ring, vib, quiet, late), clockOnly, appOnly, notConfirmed, sources and url. |
phones[].knownBugs[] | id, title, what, versions, status (open, unknown, fixed, design), fix, todo, the fixes that cover it, sources and checkedOn. |
sources[] | name and url of each page an answer, fix or bug rests on. |
Every field, with what it holds, is in the JSON Schema.
In the CSV files
One row for each fix on each phone, or for each phone, setting and alarm, with the same ids as the JSON. A path is written on one line, like Settings > Apps > [your alarm app], and several sources are split by “|”. The files are UTF-8, comma separated, with a header row and quotes only where a field needs them, as RFC 4180 sets out.
Versions
This is version 1.0.0. Within version 1, fields are only ever added, so ignore any you don't know. If one has to be renamed or removed, the version number changes and the changelog below says so. A fix keeps its id while its title stays the same.
How it's checked
The answers say what the phone's own Clock app does. They rest on the makers' help pages and user guides first, then Android's own documentation and code. Where we found nothing from the maker, they rest on the tech press, carriers or owners' reports, each named and linked. Other alarm apps get their own answer where they behave differently.
Not confirmed means no source we read settles it, so a test alarm on a real phone is the answer. These are checks against published pages, not tests on every phone, and updates can change things.
Each phone carries the day it was last checked, now 5 November 2026. When we check again, the files change, the dates move, and the changelog says what's new.
iPhone
Checked against Apple's guides for iOS 26 and iOS 27 on 4 and 5 November 2026.
Samsung
Checked against Samsung's guides for One UI 8.5 on 4 and 5 November 2026.
Other Android
Checked against Google's Pixel and Clock help, and Android's own code, for Android 16 and 17 on 4 and 5 November 2026. Answers and menu paths are a Pixel's. Other Android phones can differ, in menus and in how alarms behave.
Licence and credit
Use it, share it and change it, in free or paid work, under the Creative Commons Attribution 4.0 International licence (CC BY 4.0). Credit it with a link to this page, and say if you changed it. Show this line, with its links, where your app or article uses the data:
Source: Bed Quitter alarm fixes, bedquitter.app/data/, CC BY 4.0
The licence covers our own wording and the way the data is put together. Menu and setting names are the phone makers' own words, quoted so you can find them, and product names are their owners' trademarks: the licence doesn't cover those. Source links lead to other people's pages.
The data comes as is, with no promise that any alarm will ring. Test on a real phone before you rely on it.
Changelog
Version 1.0.0 ·
First version: iPhone, Samsung and other Android phones (a Pixel's answers and menus), each with its answers, fixes and known bugs.
Questions people ask
Can I use it in a paid app?
Yes. CC BY 4.0 lets you use, share and change it, in free or paid apps, as long as you credit it with a link and say if you changed it.
Do I need a key or an account?
No. They're plain files: download them, or fetch them from your app or website.
How do I show the answer for my user's phone?
Find the phone by its id (iphone, samsung or android), then the setting, then app: that's the answer for alarm apps other than the phone's own Clock. Show its line, and its path when it has one. Where Not confirmed is true, suggest they set a test alarm a couple of minutes ahead.
Why does Other Android show a Pixel?
Its answers come mostly from Google's help for Pixel phones and from Android's own code. Samsung has answers of its own. Other phones can differ in their menus and in how alarms behave, so a test alarm is the surest check.