Sukrara manual QA
Esta página aún no está disponible en tu idioma.
What automated checks can’t see: how each surface looks and behaves. tools/check/run.sh prints the sections a change
touches (map: tools/check/qa.json); go through them before saying a change works, and attach the before/after
pictures to the report. Cheapest way first in every section.
Data rules for every picture: synthetic or emulator data only. Never commit the user’s real glucose, crop phone screenshots so no other apps’ notifications show, and keep phone checks read-only (NEXT.md §5).
Automated already (don’t repeat by hand): tools/check/run.sh (repo rules, --layout for the cross-surface card
tests), Android unit tests (cd apps/android && ./gradlew check: alert scenarios, graph fixtures, strings parity,
Roborazzi goldens: verified on CI only, re-recorded by gh workflow run goldens.yml --ref <branch>), Mac tests (cd apps/macos && swift test). CI runs all of them (.github/workflows/checks.yml).
- Emulator:
medium_phone(wearer, debug build = synthetic glucose) andsmall_phone(follower); at most two at once. DebugReceiver:adb shell am broadcast -n app.mauri.sukrara/.debug.DebugReceiver -a app.mauri.sukrara.debug.<NAME> …, written below as<NAME> …. The only commands:SYNTHETIC --ez on true|false [--ez frozen true] [--ei cycle M] [--ei endsInMin N] [--ei warmupMin W](the synthetic sensor: a 3-hour curve from 45 to 215 mg/dL;cycle 135= its lowest point now,cycle 45its highest,cycle 0130 and rising; a sensor that ends in N min; a new one warming up for W min),ALERTS [--es kinds low,falling_fast] [--el gapMs 0] [--ez reminder true](made-up alerts through the real notifier, outside the alert rules),PEN_READ …,PEN_TAGS --ez blocked true|falseandPEN_JUGGLUCO --ez installed true|false(docs/FEATURES.md “Sensor reminders and countdowns”, “Insulin pens”),RELAYS --es urls ws://10.0.2.2:7447|public|off(where the debug build’s relays go; nothing chosen = no relay: Q22),UPDATES --es server http://10.0.2.2:8765/|off [--es cert <sha256>](the updater reads a local test release and trusts the debug key: Q25),GARMIN_SIM --ez on true|false(Sukrara Aura’s push goes to the Connect IQ simulator instead of Garmin Connect: Q27),LIBRELINKUP --es server http://127.0.0.1:8766|off(LibreLinkUp, the LibreView sign-in and the LibreView upload go to the local faketools/librelinkup-probe/fake.py: Q30). No other commands or extras (tools/checkruledebug-docs). Treatments are added in the app; a stage, sensor family or pen model is reached through the app’s own flows. These fake commands exist only in the emulator’s debug build: the release app never shows a glucose value, an alert, a treatment or a sensor state that isn’t real (a release build has no DebugReceiver). - Phone (
62240DLCH0005W): only aftertools/install.sh phone; read-only adb,adb exec-out screencap -pwhile unlocked. No fake commands (a release build has none); root/LSPosed checks that need a value use the real one.
Q1 App home and screens
Section titled “Q1 App home and screens”- Emulator, light and dark: home shows value + arrow + card + graph; scroll; open every screen touched.
- Spanish: switch the per-app language (Settings → Apps → Sukrara → Language) and repeat for the changed screens; no clipped or English-only text outside the settings pages.
- Rotation / small window (
small_phone) keeps the layout usable. - Read glucose aloud (#159; emulator with synthetic glucose, sound on): long-press the Sukrara icon → Read glucose aloud says the value, trend, range and age (Spanish per-app language: in Spanish) and nothing opens; again while it speaks stops it; drag it to the home screen and tap it there; with TalkBack, the icon’s Actions menu offers it. Without a voice for the language (emulator without the Spanish voice): the toast says where to add one.
- Screen transitions (a change to
ScreenHost/ScreenMotion.kt/screenMotion, a page’s scaffold or a vendored SPA widget; FEATURES.md “Screen motion”): set Animator duration scale to 5×,screenrecordhome ↔ settings, a settings page push / pop, setup opening over home (fade through, no slide), and a predictive back swipe held, cancelled and released (the page shrinks to 90 % with rounded corners over the scrimmed page under it, follows the finger up / down, springs back; released, it leaves to the end), and step the frames: no page drawn from scratch at the start or end of a move (empty chart, rows in another layout for one frame). Then Remove animations on: every screen change is instant and the back gesture shows no preview. Compare with the PoC (poc/spikes/showcase-android) on the same emulator when in doubt.ScreenHostTest/ScreenMovesTest(:core:designsystem) andScreenMotionTest(:app) check the same in JVM tests.
Q2 Graph and value card
Section titled “Q2 Graph and value card”- JVM gallery before/after: marks, mute lines, badge, slots, bands; light and dark; small and large sizes.
- Mac
sukrara-snap card <dir>before/after shows the same decisions (same labels, same badge text, same slot order). - Units mg/dL and mmol/L both read right (setting in the app).
- Scrolling (app panel, Mac dropdown):
screenrecorda slow drag, a fling, a fling against now (stretch) and a tap on Now; step the frames: the % column, distribution, y range (eased, no jump), hour labels and treatment marks follow the window; the plot doesn’t jump when a treatment scrolls in or out; the pill fades in and out. Mac: the same with two-finger swipes (momentum after lifting) and a mouse wheel;sukrara-snap shell <dir>writespanel-chart-scrolled-*.png. - Zoom (app panel pinch, Mac pinch / ⌘-scroll): the moment under the fingers / cursor stays put; 2 h to the whole
history; the line steps and labels change (hours → dates); the line turns into columns far out without a jump;
Now returns to now and the place’s time shown. JVM gallery
zoom; Mac by hand (ChartScrollTestscover the rules). - Sensor life (JVM gallery
sensorLife, Macsukrara-snap card→*-ended-*,*-warmup-*; emulator:SYNTHETIC --ei endsInMin <min>,--ei warmupMin <min>): badge13d/20h(no ring with an 8 h window) /5hwith the countdown ring over the main ring, legible over every band colour, light and dark; warm-up42m+ filling ring; endedSensor ended+Replace sensorpill on every widget size (3×1 and 2×1 too, also while the last value is fresh; pill/tap opens the Sensor screen on the wearer’s phone), checkered flag in the status bar (notification icon, root slots, hook) and the Mac menubar + no-data alert quiet. Follower and Mac show the same from the live events. Evidence 2026-10-18:poc/spikes/showcase-android/evidence/sensor-life-emulator-{13d,20h,5h}.png(emulator app panel),sensor-life-gallery-*.png,poc/spikes/widgets-macos/evidence/mac-sensor-*.png.
Q3 Android widgets
Section titled “Q3 Android widgets”- Emulator: add value, graph and combined widgets (2x1, 4x2, larger); light and dark wallpapers.
- They update on a new reading (synthetic source) within a minute and after
adb shell am force-stop+ reopen. - Release build (R8) once per round: widgets still render (proguard rules).
- Share-with-your-clinic banner (emulator, wearer, nothing uploading): home and Settings show Share your data with your clinic with LibreView and Tidepool pills (real icons); each opens its page; setting either up hides it on both; close hides it for good. Spanish wording fits.
- Add-the-widget banner (emulator, Pixel Launcher): with no graph widget, home shows the card under the glucose panel; Add widget opens the launcher’s dialog with the preview; Add to home screen places it and the card is gone on return; remove the widget → the card is back; close → gone after a force-stop too (Settings › Show closed tips brings it back). Spanish wording fits.
Q4 Lock screen widget
Section titled “Q4 Lock screen widget”The widget around the fingerprint icon needs a phone with root, LSPosed and the Sukrara module for System UI (System UI restarted after the install): the emulators have no LSPosed. Synthetic data or cropped captures only.
- Settings › Lock screen: Lock screen widget on (the default), Frosted glass, Automatic; lock the phone with the screen on: the value and its arrow left of the fingerprint icon, the slots right of it, the chart below; the fingerprint icon, the shortcuts, the indication text and the notifications draw over it; the rings are round (nothing stretched).
- A finger on the sensor unlocks and never opens the dialog (also resting on it, and beside it); swipe up to unlock, pull down the shade, long press to customise and the shortcuts work over it.
- Pull the shade down, open the bouncer, unlock: it fades with them and is back on the lock screen; screen off (always-on display): not shown; screen on: shown with the newest reading.
- Tap the value: Add treatment over the lock screen, still locked (the countdown on Cancel); Cancel is back on the lock screen. Without a value (no reading for 20 min, or none yet): the tap asks to unlock, then opens the app.
- Screen on and locked: a new reading shows within a minute; at 5 min struck, at 20 min No reading since ….
- Many notifications: the shelf (the pill with the overflow icons) stays above the fingerprint icon, never over the value.
- Each Background (none, shadow, dim, card, frosted glass) on a busy wallpaper and each Appearance; switch the system’s dark theme while locked: the tint and the picture follow at once.
- Turn the widget off: gone from the lock screen at once; on again: back. Disable the module in LSPosed + restart System UI: gone, the switch says On. Shows once the Sukrara LSPosed module runs in System UI.
- After an update that changes System UI’s code: Settings › Lock screen shows Restart System UI (the widget keeps showing meanwhile); Restart → the card goes.
- TalkBack on the lock screen: the widget reads the card’s sentence and Add treatment.
- Settings › Lock screen in Spanish at 360 dp (the footer, the dialogs’ lines); a phone or emulator without LSPosed: the switch says what it waits for, no card, nothing on the lock screen.
- A device whose lock screen hosts widgets (tablet hub): the home widgets are offered there (not the lock-screen widget); a tap opens the treatment dialog over the lock screen; the value updates while locked.
- Lock-screen countdown (emulator:
adb shell locksettings set-pin 1234, keyevent 26 then 224, open the quick dialog from the glucose notification on the lock screen): the ring with the seconds on Cancel counts from 20; typing doesn’t add time; one tick at 5 s with input; at 0 it closes and toasts Treatment not saved (only with input); screen off closes it at once; Unlock → PIN → the same dialog with amounts, note, 16 min ago and the keyboard, Open Sukrara back, no ring; cancelling the bouncer resumes with ≥ 5 s; the When? picker’s Cancel shows the ring; Spanish at 360 dp wraps Desbloquear above Cancel / Save. TalkBack on: ≥ 60 s, Cancel says Closes in N seconds, one announcement at 10 s. Remove animations: the ring steps per second. - No other app’s notifications in the screenshots.
Q5 Status bar & notification
Section titled “Q5 Status bar & notification”- Emulator: pull down the shade; collapsed (value + slots) and expanded (card) in light and dark.
- Lock screen version (public/redacted) shows what the settings say.
- Glucose on the lock screen (#94; real phone): on, the value and arrow show locked with the phone’s Hide silent notifications on and off and with Sensitive notifications off, and on the always-on display; off, only Sukrara · Monitoring shows locked, also on the Live Update chip, and the value is back after unlocking.
- A sensor past its end that keeps sending (#3; emulator, synthetic sensor ended a few minutes ago): the value with Sensor ended · Replace sensor under it; once the readings stop, Sensor ended with Replace sensor.
- Live Update chip / status bar value if the change touched them (phone).
- One notification (docs/36; Android 16 and 17 emulators,
SYNTHETIC --ei cycle 170then--ei cycle 116, chip and graph, light and dark): exactly one Sukrara notification while a low rings (dumpsys notification --noredact: id 1 onalert.lowwithoutONLY_ALERT_ONCE,category=alarm,PROMOTED_ONGOINGwith the chip; 10 s later onglucose.livewith the alert still on it); buttons Treatment · Remind less · Mute, none with “…”; in the Live Update Mute opens the length dialog over the lock screen (Mute lows: For 15 min … For 2 h, Custom; radio rows TalkBack reads); on the card the chips 15m 30m 1h 2h; muted: Lows muted with Time left (17) / · 29m left (the card), only Treatment and Unmute; the value’s label is the trend in words, never Now; no “glucose” in any title (Very low, Low · eat carbs); swipe it during a ring: it comes straight back onglucose.livewithout the alert and doesn’t ring again; an alarm-level kind (very low) locked, screen off, on Android 16 and 17: full screen on the first ring (its own notification onalert_alarm.very_low, ids 1000+, gone 10 s later with the glucose notification carrying the alert); a very low and falling fast on one reading: Very low glucose in front on its channel, Also: Falling fast; the glucose channel turned off in Android’s settings during an alert: the alert shows as a notification of its own. Graph: the value smaller than the rings, two rings expanded and collapsed, no Low word beside a level alert’s title, Coloured background keeps every pill legible (white / black on red). - Settings › Status bar & notification (docs/36 §11, §14; its overview icon the status bar with the shade pulled down): the picture follows the choice (fade, cut with reduced motion; TalkBack reads it as one sentence); Chip, Notification icon, Status bar text (a Root label at its end that TalkBack reads with the row), Nothing are one radio group of equal rows; under it only the chosen one’s rows (chip: Allow Live Updates while refused; icon and text: What the icon shows with the newest value drawn as each icon, None only with the text; text: root’s card, Placement, Colour by range, Glucose notification), then Notification with Alerts in the notification (flipping it flips Alerts › Separate alert notifications). Light theme: the picture’s notification is clearly outlined. Searching “chip”, “status bar text” or “value and trend” finds the row and flashes it. Spanish.
- Each icon (emulator, synthetic sensor): Value and trend, Value, Trend, Sukrara icon each show in the status bar as their picture on the page; with the text and the module (phone) None hides it while the value shows; without the module None says so and the icon stays the value.
- Nothing (Android 16 and 17): Turn off the glucose notification opens Android’s Glucose switch; off and back →
the row is gone, nothing of Sukrara’s in the bar or the shade, the footer says alerts stand alone; monitoring keeps
running (Quick Settings › Active apps lists Sukrara; readings keep arriving in the app and widgets); a low rings as
a notification of its own (
dumpsys notification: analert.lowrecord, ids 1000+, no id 1); reboot → monitoring starts, still no glucose notification, an alert still rings. Then Chip → Turn on the glucose notification until Android’s switch is back on. The same with Status bar text and its Glucose notification row (phone with root). - Live Update value (phone, Android 17.1+, three metrics, steady arrow
→, mg/dL and mmol/L): the value shows whole with its arrow, never 138 …; a decimal that can’t fit a third drops a ring instead. - Settings › Alerts › Separate alert notifications (its icon a bell with a plus): on → a separate alert beside the glucose notification (ids 1000+), which carries no alert; its summary suggests it with a watch app installed. Real watch (when one is paired): the separate alert buzzes the watch.
Q5b Root status bar in a full row
Section titled “Q5b Root status bar in a full row”Phone with root + the LSPosed module (System UI restarted after the install), Status bar text chosen with a system-icon placement. Read-only checks; screenshots stay off the repo (health data).
- Root for Sukrara (#178), fresh install, another choice: nothing asks for root until Status bar text is chosen (Settings › Status bar & notification) or setup’s Yes, it’s rooted. Chosen with Sukrara not allowed in KernelSU: Allow root for Sukrara (Magisk: its prompt; Deny → Root refused). Allow it in the root manager’s Superuser list and come back: the card goes by itself, the value shows, a confirm haptic. TalkBack reads the card.
-
adb logcat -s LSPosedFramework Sukraraafter the System UI start:icon fit hooks: 1, noicon fit … failed. - Before the mobile signal (the default on a fresh install): glucose right of vibrate / VPN / speakerphone, right before the mobile signal, never between mobile and Wi-Fi; Wi-Fi only (mobile hidden): still left of Wi-Fi. Lock screen: the same order.
- Without the module (module off in LSPosed, or emulator with root only): Placement reads “Before the mobile signal needs the LSPosed module. For now, it shows first among the system icons.”; the icons show leftmost; in the dialog the system-icon placements are selectable with that line, the clock ones are disabled; choosing With the system icons clears the note. Spanish too.
- Fill the row (vibrate, Do Not Disturb, hotspot, alarm, Bluetooth on): other icons fold into the overflow dot from the left; number and arrow stay, at their placement.
- Keep filling until even the pair can’t fit (larger font / display size): number and arrow become the one dot together, never the arrow alone; removing icons brings both back.
- No readings (> 20 min) / sensor ended: the single icon keeps the same priority.
- Range colour (#118): out of range with Colour on, the number is in the range colour while Wi-Fi, battery,
mobile and every other icon keep the bar’s tint; still so after the value goes back in range (number in the
bar’s tint), after a light / dark bar change (an app with a light status bar, the shade) and on the lock screen.
logcat -s LSPosedFramework Sukrara:icon tint hook: ok (platform filter)(or(Compose's own)), noicon tint failed. - Placement After the Bluetooth icon with Bluetooth off: the value sits where Bluetooth would be (not far left); turning Bluetooth on puts it right after the icon.
- Restart System UI (home’s Restart System UI card, or the Settings action): number then arrow from the first
frame, no swap and no blink a few seconds later;
adb logcat -s Sukrara.slots:orders our icons itself (module): no re-add. Same with the plain With the system icons placement. - A row that is just full (an icon in the dot): if that icon would fit with the pair 8 px closer, it shows instead of the dot; the row never runs into the clock / cut-out and number + arrow still go into the dot together when there’s no room.
- Number and arrow about 3 dp apart (as on the app’s card), closer than the other icons; the gap to the icons
beside them unchanged (6 dp); still close after a reading, after a no-readings / ended spell and with the row
full.
logcat:icon fit hooks: 1, gap hooks: 1. - Without the module (or
settings put global sukrara_hook_disabled 1+ System UI restart): leftmost, SystemUI’s own fit (the arrow alone can show in a full row; documented). - TalkBack in the person’s language (#159), phone in English, then Sukrara in Spanish (Settings › System › Languages › App languages): explore the status bar. The number says Sukrara: 120 milligrams per decilitre, rising, high (Sukrara: 120 miligramos por decilitro, subiendo, alta), the arrow Sukrara, rising (subiendo); struck: …, old reading, … and Sukrara, old reading; no readings: Sukrara. Glucose: no reading since 9:50; ended: Sukrara. Sensor ended. Replace sensor. The module still orders, colours and fits the pair in Spanish (same checks as above), and an out-of-range number keeps its colour.
- The module’s text (a clock placement, or a
slot:one in mmol/L): TalkBack says Sukrara: 6,2 milimoles por litro, bajando, en rango; force-stop Sukrara (adb shell am force-stop app.mauri.sukrarais not read-only: only on a test phone) and wait 6 min, then 21 min: TalkBack follows the struck value and Sukrara. Glucosa: sin lecturas desde … in Spanish, never the earlier words.
Q6 Mac menubar panel
Section titled “Q6 Mac menubar panel”- Test build at another path (never over the installed
/Applications/Sukrara.app): menubar number + colour; click → panel (card in its module, Return opens Add Treatment: Tab rapid → long → carbs → note,4.5ukeeps4.5, quiet line, limits line at 600g, time chip popover, Return saves all, Escape cancels; Escape / click outside closes the panel); right-click menu; Treatments… (7 days, delete with ⌫ / context menu, ⌘W; a pen treatment from the phone: total as title, From the pen · 1.5u primed, the triangle opens the doses with primed on air shots, tooltip Read from the pen on …’s phone (no serial); Add Treatment with rapid within 45 min of a pen treatment → Already logged by the pen?, Cancel keeps the insulin typed and saves carbs / note, Log Anyway saves; VoiceOver reads the row as one sentence and each dose as 12:37, 1 unit, primed; a correction on the phone shows here within seconds; chart mark = the total; synthetic:sukrara-snap windows <dir>→treatments-*.png,treatment-add-*.png); Glucose Report (report only, period, Export CSV…); Settings (each pane; ⌘, ⌘W, paste in the invite field); light and dark, over a bright and a dark window/wallpaper, Increase Contrast and Reduce Transparency (System Settings → Accessibility → Display). - Add Treatment placement and inputs (#181), in the running test build: from the panel (row, Return, a pill) it
opens centred under the status item, whole, its top 6 pt under the menu bar; a click on the desktop widget and
the Treatments window’s + open it centred on the pointer, whole on that screen (try the widget near the top edge
and on a second display). No placeholder in any field of the app (Add / Edit Treatment, the When? popover, the
panel’s Mute all Custom…, How You Appear, Juggluco, the invite link, Custom numbers). Amounts, minutes ago and
Custom numbers: field + stepper + unit, ↑ ↓ step (rapid 0.5u, long 1u, carbs 5g, minutes 5); Cancel and Save at
the regular height, Escape / Return; the alert sheets’ Done closes with Escape; a click outside the When? popover
keeps a changed time, unchanged keeps Now. Synthetic:
sukrara-snap windows→treatment-*.png. - How the readings come (2026-11-15), following on a test build: the end of the Mute All Alerts row (and of Mute
all’s Unmute / Change Time) says Internet with the globe; with the wearer’s phone in Bluetooth range
Nearby with the Bluetooth mark within a minute; Wi-Fi off and the phone out of range: Offline in red; back:
Internet. The tooltip and VoiceOver say it in words; a click opens Settings › Source. Synthetic:
sukrara-snap shell→panel-nearby-*.png,panel-offline-*.png,panel-muted-all-nearby-*.png. - Card overflow (#181):
sukrara-snap shell→panel-flowers-*.png: the flowers and laurel at the card’s right and top edges and the value’s first digit at its left edge are whole, drawn over the panel’s margin (compare docs/img/mac-ux/panel-overflow-*.png); the same on the real panel with a ring at 95 % or more. - Synthetic renders (the only snapshot path; offline, scratch data, debug builds):
cd apps/macos && swift build && .build/debug/sukrara-snap shell|windows|card <dir>(shell-es/windows-esfor Spanish): the menu bar title + panel in each state, every window state (light, dark, large text) and every card surface. Never into the repo. - The running app offline:
FIXTURE=1 Bundle/smoke.sh .build/debug/Sukrara(a made-up wearer, fresh data, no socket); by handSUKRARA_DEV=1 SUKRARA_FIXTURE=1 SUKRARA_DEV_HOME=<scratch dir> .build/debug/Sukrara. A dev build refuses to start withoutSUKRARA_DEV=1and takes no arguments (LaunchPlan,LaunchModeTests). - Settings (round f28):
sukrara-snap windows <dir>renders the panes with synthetic data (settings-*.png: General with Custom and the login states, Alerts own and mirrored, Graph and Metrics own and from the wearer, Following); check the toolbar (five panes, title = pane), Settings from in General (Their settings / This Mac’s own, In use line; This Mac’s own: Copy the Wearer’s Settings… disabled until an event arrived, Reset to Defaults… asks first), Their settings shows the read-only summary and Change… opens General; every number: presets + Custom…, the field takes a value in range on Return / leaving it, out-of-range text turns the range note red and changes nothing, the stepper and Shift-click stay in range; a custom value (7 h, 45 days, 183 mg/dL) survives a relaunch and shows in the panel / widgets; the per-place windows; ring order: drag a range onto another (insertion line), Control-click Move Up / Down, VoiceOver actions; Details… of an alert in Custom vs Wearer; Send Test Alert. Snapshots:sukrara-snap windows→settings-*.png. - Settings window and About (#181), in the running test build and in
settings-*.png/about-*.png: the pane buttons sit in the title bar with the traffic lights (one bar, no tab view, no frame inside the window), the active one highlighted, minimize and zoom dimmed, the title = the pane; switching panes resizes the window from its top edge (animated; instant with Reduce Motion) and each form starts at its top; section footers align left; ⌘, opens it on the last pane, ⌘W closes it; Tab reaches the pane buttons with full keyboard access and VoiceOver reads them by name. About Sukrara from the app menu, the right-click menu and Settings › General: icon, name, Version x.y.z (build) (selectable), GitHub version / App Store version, the medical reminder, the links open the browser, ⌘W closes it; light, dark, large text, Spanish. - Read Glucose Aloud (#159): ⌃⇧⌘G in another app says the menu bar value’s sentence in the Mac’s language (also in Spanish); again while it speaks stops it; with VoiceOver on, VoiceOver says it in its own voice; the status item’s right-click menu has Read Glucose Aloud ⌃⇧⌘G first; VoiceOver on the value → VO-Command-Space → Read Glucose Aloud. Settings › General › Read glucose aloud with ⌃⇧⌘G off: the keys do nothing (and reach other apps), the menu item stays without the keys; on again: they work at once.
- Provisioning profile (#19, #34; installed with
tools/install.sh mac): the first launch after a build without the profile moves the follower key into the data-protection keychain (at most one Keychain prompt for the old item, Always Allow); it keeps following after a relaunch, and Keychain Access no longer listsapp.mauri.sukrarain the login keychain. Stop following → relaunch → still not following. The web invite link clicked in Safari, Mail or Messages (once the site serves/.well-known/apple-app-site-association) opens the Follow step with Follow / Cancel, never following by itself; while launching, it waits for the launch. - QR scanner (#172; only a build installed with
tools/install.sh macmay open the camera, a dev run shows the made-up feed): the Follow step’s Scan QR Code… and Settings › Source › Scan QR Code…. First time → Allow Camera → macOS asks (in Spanish with the Mac in Spanish) → the live picture, mirrored; the phone’s Share › Invite QR → green check and a tap, then who is inviting (Cancel sends nothing); a menu / Wi-Fi QR → the orange That QR code isn’t a Sukrara invite, scanning goes on, the warning leaves once the code does; an iPhone near the Mac (Continuity Camera) is in the camera picker and takes over when placed on a mount; Cancel, Escape, closing the window and Skip turn the camera light off at once, minimizing or covering the window too (on again when it shows); Privacy & Security › Camera off → Camera access is off… → Open System Settings… → turn it on → back in Sukrara it scans; with no camera (lid closed, no iPhone) No camera found…, then it starts when one connects; VoiceOver reads Camera view for the QR code and the announcements. Synthetic:sukrara-snap windows→follow-scan-*.png,settings-following-none-*.png. - App Store version (#186): offline,
Bundle/bundle.sh --app-store && Bundle/smoke.sh(sandboxed, offline, sandboxed in its last line);tools/release/verify-app.sh build/Sukrara.app --app-store. Online only from TestFlight (docs/20-publishing.md › Mac App Store: signing): Settings › General › Version says … · App Store version without Check for Updates… or the update switches, About Sukrara says App Store version, the right-click menu has no Check for Updates…; following over the relays, the phone nearby, Juggluco on this network, an alert with its sound and through a Focus, the widgets, open at login, Export CSV… to a folder you pick, the QR scanner, a web invite link; both versions show the medical reminder and Privacy Policy in About. Thentools/install.sh macback to the GitHub version. - Development and release builds: after
tools/install.sh mac, About Sukrara shows Version x.y.z (build) and Development build · x.y.z + n commits ·· (selectable), Settings › General › Version the same line, and Check for Updates… doesn’t offer x.y.z itself; the notarized dmg of the release says GitHub version / x.y.z · GitHub version there instead. - Updates (Sparkle, #91), after a release that added an item to
website/public/appcast.xml: on a Mac with the previous GitHub version installed from its dmg or the cask (not a dev build), right-click › Check for Updates… → Sparkle’s window with the new version and its notes → Install Update → the download → Install and Relaunch → Sukrara quits and comes back as the new version (About), still following, alerts and the widgets as before, no Keychain prompt. Check for Updates… again → You’re up to date!. Settings › General › Software Update: Last checked … moved; turn Check for updates automatically off → the download switch dims; on again. A scheduled find while you work shows the panel row (Sukrara x.y.z is available, Later / Install…), not a window over your app. Offline Check for Updates… → Sparkle’s error → OK, nothing installed. VoiceOver reads the windows, the row and its hint. Never test on the owner’s/Applications/Sukrara.app: the local end-to-end check is in docs/20-publishing.md › Sparkle: the update feed. - Relaunch the user’s copy afterwards.
Q7 Mac widgets
Section titled “Q7 Mac widgets”-
sukrara-snap card <dir>before/after:widget-*for every family and state, light, dark and-dimmed(the dimmed desktop’s greyscale,DimmedDesktop). - Dimmed (#189): dark appearance, a bright wallpaper, then a dark one; click another window so the desktop widgets
dim (System Settings › Desktop & Dock › Dim widgets on desktop Automatically): on both, the widget is a dark
card like Apple’s Calendar next to it, the value, arrow and ring numbers light and clearly the strongest, the grid
and band faint. Same in light appearance (a light card, dark inks).
screencapture -l <window id>of the widget’s window (NotificationCenter) shows it without the wallpaper; compare with-dimmedfromsukrara-snap. - Real widgets only via
tools/install.sh mac(restarts the widget extension); they update within a minute.
Q8 Alerts on a device
Section titled “Q8 Alerts on a device”- New/changed rule: a scenario in
contracts/alerts/scenarioscovers it (the checks enforce this). - Quiet while heading back into range (#193): emulator
SYNTHETIC --ei cycle 135(the trough now): Very low glucose rings; about 10 min later, rising, its repeat doesn’t come and Active now / the home sheet say Low alerts muted while rising back into range with Alert me anyway (es … mientras sube hacia el rango);SYNTHETIC --ez frozen true: within 2.5 min of the last reading the low that came due rings at once. Settings › Alerts: Quiet highs falling back into range and Quiet lows rising back into range side by side, each with Back in range within; off → the repeats come every 5 min. Mac Settings › Alerts › Quiet times shows the same pair. - Emulator:
SYNTHETIC --ei cycle 135(45 mg/dL now) and--ei cycle 45(215 mg/dL): real alerts through the rules; notification text, channel, sound, repeat. - Grouping (Android 16 / 17 emulators, chip on and off):
SYNTHETIC --ez on true --ei warmupMin 10+ALERTS --es kinds high, then the warm-up’s end (Sensor ready with the first reading), thenALERTS --es kinds rising_fast.dumpsys notification --noredact: alerts only ing:app.mauri.sukrara.ALERTS(summary id 1000; the alerts 1001 and up, one per group: 1001 level, 1002 rate, 1003 no data;NotificationIdsinmonitor/notify/Channels.kt), Sensor ready and both countdowns (the warm-up one, thenSYNTHETIC --ei endsInMin 300for the end countdown, chip on and off) ing:app.mauri.sukrara.INFO(summary 1100), the glucose card the one ungrouped notification, nothing ing:Aggregate_…(#156); an alert is the one that sounded (mSoundNotificationKey= an alert’s id, 1001 or up; never Sensor ready’s). In the shade High glucose never inside a bundle with Sensor ready; a real alert (SYNTHETIC --ei cycle 135) is removed with its group’s summary once the curve is back in range (--ei cycle 0). - What stays on screen (#195, emulator,
SYNTHETIC --ei cycle 135, a slow low): the alert’s value follows the card without sound with every change of the value (dumpsys notification --noredact: the level alert’sandroid.textmatches the glucose notification’s value, no newmSoundNotificationKey); stop the readings (SYNTHETIC --ez on false): at 90 s its time follows, at 5 min the value is struck through. Swipe it: it stays away until its 5-min repeat rings. Back in range then low again within 5 min: shown at once, silent. A watch paired (or a notification-forwarding app) gets the alert (note whether it buzzes on the silent updates too); the glucose notification stays its own (never merged). Mac following the emulator: the same value updates, no second banner, a dismissed alert stays away until its repeat. - Mac: no fake-reading hook yet; follow the emulator wearer (or
swift test --filter AlertsTests: the scenarios) and compare the headline and timing with Android. - Android Do Not Disturb (#184, emulator, fresh install): setup’s Do Not Disturb shows a moon, Sukrara doesn’t
alert in Do Not Disturb and Let Sukrara through, no tick, no Allow, no red; home has no banner for it. Turn on
Bedtime / a mode without alarms: home says Do Not Disturb is on: alerts make no sound with Change; Send a
test alert stays in the shade without sound or vibration. Let Sukrara through → Android’s Do Not Disturb access
list → Sukrara on → back: Sukrara alerts in Do Not Disturb (TalkBack hears it),
dumpsys notification: everyalert_alarm.*mBypassDnd=true(an edited one moved to.2with its choices); the test alert now shows and vibrates through the mode (silent while it mutes alarms). Don’t let Sukrara through → at once Sukrara doesn’t alert…, everyalert_alarm.*mBypassDnd=false. Mode off: the home line goes. Spanish too. - Android sound while unlocked (#183, emulator, phone unlocked, ringer normal): Sound while the phone is unlocked
→ Test the sound: the test alert rings once (
logcat -b events -s notification_alert: one beep) and I heard it / It only vibrated appear; with Do Not Disturb on or the ringer on vibrate the button is off and says why.adb shell settings put system notification_cooldown_vibrate_unlocked 1(emulator only), test again: it only vibrates (beep=0), Sukrara plays nothing during the test; It only vibrated → Open Android’s setting shows; a real alert (ALERTS --es kinds low) then rings exactly once (Sukrara’s player, beep=0 from Android). Back to 0, test, I heard it: a real alert rings exactly once (Android’s). On the phone (owner): with the switch on and off, an alert sounds exactly once while unlocked. - Mac Focus (#184, a build with the provisioning profile:
bundle.shprints profile “…”): Settings › Alerts and setup’s notification step say Sukrara doesn’t alert during a Focus with Let Sukrara Through; turn on Do Not Disturb, Send Test Alert on an alert set Like an alarm is held back. Let Sukrara Through → Sukrara alerts during a Focus; the same test alert shows and plays. System Settings › Notifications › Sukrara › Time Sensitive Notifications off → Time Sensitive notifications are off… with Open Notification Settings (it opens Sukrara’s page) and Don’t Let Sukrara Through. A build without the profile (--no-profile): This build of Sukrara can’t send Time Sensitive alerts… with Open Focus Settings. The panel says nothing about a Focus. VoiceOver reads statement, meaning, button. In Spanish too. - Never on the user’s phone with real alarms unless the user asked.
Before the first unlock (emulator; docs/30, #160)
Section titled “Before the first unlock (emulator; docs/30, #160)”An emulator of your own with file-based encryption (adb shell getprop ro.crypto.type = file), never the phone.
Before the unlock run-as can’t reach the app (its data dir is locked): adb root reads /data/user_de/0/….
- Debug build,
SYNTHETIC --ei cycle 108(wearer monitoring; a low about 5 min later).adb shell run-as app.mauri.sukrara ls -R /data/user_de/0/app.mauri.sukrara:datastore/alerts.preferences_pb,files/recent-readings.json,files/state/{role,role-backup,monitor-record,alert_state,sensor_end}.json,files/locked-boot.json,shared_prefs/debug-fakes.xml; nothing else of the app’s. -
adb shell locksettings set-pin 1234,adb reboot, wait forsys.boot_completed;dumpsys usersaysRUNNING_LOCKED. Within a minutelogcat:Sukrara.monitor: start (LockedBoot): Started; lock screen: the glucose notification with the value and Monitoring before unlock (public, silent;dumpsys notification --noredact: id 3 onstatus); a new reading every minute; noFATAL. - Still locked, when the curve reaches 69: Low glucose rings (
alert.low,RingtonePlayerplayscontent://app.mauri.sukrara.alertsound/low); its buttons and the swipe work on the lock screen. -
adb root:/data/user_de/0/app.mauri.sukrara/files/locked-readings.csvgrows a line a minute. - Unlock (
input keyevent 82, swipe up,input text 1234, Enter): id 3 goes at once, the same process and service go on (dumpsys activity services: the service’screateTimefrom before the unlock),locked-readings.csvis gone,start (Boot): Startedafter the boot broadcast. Pulldatabases/sukrara.db(adb root): one reading a minute across the restart and the locked minutes, no gap, nothing twice. - A follower’s phone (or
source.sourceJuggluco): the old path. Lock screen: Unlock to resume monitoring;dumpsys alarm:lockedboot.RINGat the last reading + No data’s minutes. Ring it now:adb root,adb shell am broadcast -n app.mauri.sukrara/.monitor.lockedboot.LockedBootReceiver -a app.mauri.sukrara.lockedboot.RING: id 3 moves toalert_alarm.no_dataand plays; unlocking clears it and monitoring starts. - Phone (the owner): after a restart without unlocking (an OS update at night, or restart by hand and leave it locked), the lock screen shows the value and Monitoring before unlock, a Libre 3 reading arrives each minute, alerts ring; after unlocking the history has those minutes and followers catch up. The Bluetooth link to a Libre 3 before the first unlock is verified only on a real phone.
Q9 Translations
Section titled “Q9 Translations”- Every new key in
values/strings.xmlandvalues-es/strings.xml(the checks and StringsParityTest enforce the keys; a person checks the wording: Spain Spanish, hidratos, insulina rápida / lenta). - Spanish UI on the emulator for each changed screen; long Spanish strings don’t clip in widgets or the card.
Q10 Release build
Section titled “Q10 Release build”Release smoke (emulator)
Section titled “Release smoke (emulator)”tools/release/android-smoke.sh (--final for the release gate: every WARN becomes a FAIL) does the cheap part on
its own AVD release_smoke (API 37, port 5600; it refuses anything that isn’t an emulator): signed release build →
verify-apk.sh → fresh install → the app launches, renders,
survives an activity recreation (saved state) → 3 min watch + a 3 h clock jump with no alert (no sensor) → a walk
of every screen up to two taps from home (tools/release/ui-walk.py: taps each labelled control, the app must
survive it; the app’s data is cleared before each path, so every path starts from the same fresh home) → the app’s logcat has no crash and no R8 / JNA / UniFFI / serialization / Room error. Output in
$TMPDIR/sukrara-smoke.* (the walk’s screenshots in walk/).
- The smoke exits 0 (
--finalbefore a release). Look at its screenshots, the walk’s too. -
verify-apk.shFAILs on the debug APK (signer, debuggable, debug receiver, no R8 marker): the checks bite. - A release build without Juggluco (
-Psukrara.juggluco=/nonexistent) or without the key (SUKRARA_KEYSTORE=/nonexistent) stops inverifyJuggluco/verifyReleaseSigning. - By hand on the emulator release build: the screens deeper than the walk’s two taps that the change touched (a settings page’s own pages, setup’s later steps, a sensor’s pairing) — R8 breaks screens nothing opens.
- Not checkable on an emulator (phone, by the owner): the Live Update chip on the status bar with a real sensor,
the NFC tag chooser and the
https://sukrara.mauri.app/joinApp Link. - The version in
VERSIONmatches what the release notes say. - The release notes list every pre-release library
android-release.shprinted (tools/check/allow.jsonprerelease_ok), each with its reason.
Google Play build (emulator)
Section titled “Google Play build (emulator)”tools/release/play-bundle.sh builds and checks the bundle (docs/20-publishing.md › Flavors). Then, on an emulator
(never the owner’s phone: the Play build would replace the GitHub one), install bundletool’s universal APK
(bundletool build-apks --mode=universal, or apps/android/app/build/outputs/apk/play/release/app-play-release.apk)
over nothing:
-
play-bundle.shexits 0 with bundletool ($BUNDLETOOL), andverify-apk.sh --playFAILs on the full flavor’s APK (the updater’s classes, receiver andREQUEST_INSTALL_PACKAGES): the Play check bites. - Settings › About: 0.16.0 · Google Play version (the version from
VERSION), About the versions (opens sukrara.mauri.app/android/#versions, the Versions section), Sukrara for Mac, Report a problem, Source code, Privacy policy (opens sukrara.mauri.app/privacy); no update rows, no Updates switches, no disabled row, nothing that says to install another version. Searching “check again” or “install updates” finds nothing; “versions” finds About the versions. Android’s Settings › Apps › Sukrara › Notifications has no App updates channel, and Install unknown apps doesn’t list Sukrara. - The same app as the GitHub build otherwise: Settings › Status bar & notification has Status bar text (searching “root” finds its
rows) and setup has the Root step; a fresh install’s alert checklist has no Alarms and reminders item (
USE_EXACT_ALARMis granted at install). - The GitHub build’s About says 0.16.0 · GitHub version with the same About the versions link and its update rows.
- TalkBack reads the About rows with their summaries.
- Development and release builds (docs/FEATURES.md › Development and release builds): after
tools/install.sh phone, About says Development build ·+ (the commit install.sh printed), in Spanish Versión de desarrollo · …; the update check offers no release with the same version (Up to date). The GitHub release’s APK and the Google Play build saycommits · · · GitHub version / · Google Play version.
Q11 Sensor reminders and countdowns
Section titled “Q11 Sensor reminders and countdowns”- Emulator (wearer):
SYNTHETIC --ez on true --ei endsInMin 300→ the end countdown in the shade (bar, timer); with Settings › Status bar & notification › Notification icon chosen the status bar chip shows the timer. A reminder set in Settings › Sensor end for a minute ahead → it shows then (“Sensor ends today at …”).--ei endsInMin 1→ “Sensor ended” a minute later. -
SYNTHETIC --ez on true --ei warmupMin 20→ the warm-up countdown (bar filling, chip timer); at its end the first reading → “Sensor ready”. - Swipe the countdown away: it doesn’t come back for that sensor (also after the app restarts).
- Settings → Sensor end: add / edit / remove a reminder (dialog: days radio, time picker), countdown hours, both switches; the card’s countdown ring follows the hours. Spanish texts.
- Follower role: none of these notifications.
Q12 Sensor scan
Section titled “Q12 Sensor scan”- Unit tests first:
Libre3NfcTest(commands, answers, receiver ID,chipGate),PatchStateTest. - Unit tests:
NewSensorFlowTest(steps after the tap, home button). Every stage:SensorGallery(JVM, light and dark, font 1× and 2×, some in Spanish; no debug command forces a stage). Emulator: home’s button filled afterSYNTHETIC --ei endsInMin 0, tonal with--ei endsInMin 600, gone otherwise. - Settings → Glucose source (one page): header with the sensor (family, red Untested tag when unverified, serial, dates, status) and Pair new sensor; Read glucose from: This phone (named family) / Juggluco (from Juggluco to This phone asks first, then the New sensor screen); Sensor: open on scan, Forget this sensor. Settings search finds Pair new sensor, This phone, Juggluco, Forget this sensor.
- Phone, the user does the tap, home → Pair new sensor (or Settings → Glucose source → Pair new
sensor): the circle sits on the phone’s real NFC spot; the tap vibrates, then Pairing ticks its steps and
ends in the warm-up countdown (new) or Sensor ready (taken over). With Sukrara closed, a tap opens the New
sensor screen and uses that tap. Libre 3 / 3 Plus: starts or takes over;
adb logcat -s Sukrara.nfc Sukrara.directshows the patch info and the pairing. A Libre 1 / 2 / 2 Plus (or any other NfcV tag) shows Libre 2 sensors aren’t supported / Not supported, and logcat showsLibre 1/2 chip: not supported, nothing sentwith no command lines. - A new Libre 3 without a known LibreView receiver ID: Sign in to LibreView, nothing sent; after the
sign-in the next tap starts it (logcat
patch info … state=1, then the pairing). - Issue #177, one LibreView account (emulator, a throwaway LibreView account, never the owner’s): sign in once
in setup’s sensor step; Settings › Sensor shows Signed in as with the email and opens the same screen; Share
with apps › LibreView shows the email under Account, turning the upload on asks nothing and the status moves
on by itself (or says another device uploads: Take over / Cancel). Sign out on the account screen asks
first, then Settings › Sensor says Sign in to LibreView, the upload says Sign in to LibreView first, and the
next new sensor asks to sign in.
adb logcat | grep -i <the password>finds nothing. - Libre 3 unchanged by the brand step (investigation 23): the screen opens on Which sensor are you
starting? with FreeStyle Libre 3 / 3 Plus selected; tapping the sensor right there starts the scan (no
Continue needed); Continue → the same NFC flow as before; no Untested tag, no confirmation, no banner on
home. After the install,
adb logcat -s Sukrara.direct Sukrara.scanshows the usual Libre 3 connection by address and noSukrara.scanline at all; readings keep arriving every minute. - Untested families (emulator, no sensor needed; no debug command forces a stage: home → Pair new sensor →
Which sensor are you starting?): every brand but the Libre 3 has the Untested tag (a red label, no icon;
TalkBack “untested with real sensors”); Continue with an untested family goes to the flow’s next page,
Untested with real sensors (red,
NewSensorStep.ConfirmUntested), whose Continue anyway (10) … (1) counts down with the button disabled, then Continue anyway → the family’s setup; Cancel and back go back to the brand step; opening the page again restarts the count; the Libre 3 never asks. Pair is disabled until a typed id is valid. Light and dark, English and Spanish. Unit tests:NewSensorMachineTest(the untested page and its wait), the driver tests (G7DriverTest,G6DriverTest,SmartGuideDriverTest,AidexXDriverTest,CrcTest). - Untested banner (after pairing an untested family through the New sensor flow above, no sensor needed; no
debug command fakes a family) → home shows Dexcom G7 / ONE+
support is untested. Tell us how it works. directly under the graph, no close button, not red; Send feedback
opens github.com/…/issues/new with the sensor-feedback form pre-filled with the sensor, the Sukrara and Android
versions and the phone model only (
SensorFeedbackTest); back on a Libre 3 → gone; a follower never shows it. - Untested family, outputs: with that sensor, Settings → Share with apps → Apps on this phone
starts with Paused: Dexcom G7 / ONE+ support is untested and
adb logcat -s Sukrara.broadcaststays silent for readings tagged with an untested family; a Libre 3 → the line is gone and the allowed apps get readings again. Unit tests:BroadcastPayloadsTest(no broadcast without a verified label),SensorOutputsTest(Health Connect, Tidepool, Nightscout, phone APIs, CSV),LibreViewUploaderTest.
Q13 Sensor end in calendar
Section titled “Q13 Sensor end in calendar”- Phone with a real sensor (the synthetic sensor has no serial, so it gets no event;
SensorCalendarPlanTestcovers the plan): Settings → Sensor end → “Sensor end in calendar” on: the permission dialog; Allow → “On · Sukrara (this phone only)”; Don’t allow → stays off with the reason. -
adb shell content query --uri content://com.android.calendar/events --projection title:dtstartlists one “Sensor ends” event at the sensor’s end; a new sensor moves the future event to it (the old future one is removed); restart the app → still one event per sensor. - A calendar app on the device shows the “Sukrara” calendar in the brand colour (if the image has one).
- Off → the Sukrara calendar is gone (
content query --uri content://com.android.calendar/calendars). - Picking a Google calendar (needs a signed-in account): the event appears on another device after sync and goes away again when the setting is turned off.
Q14 Apps on this phone and Health Connect
Section titled “Q14 Apps on this phone and Health Connect”- Emulator (wearer, debug = synthetic glucose) with GlucoDataHandler installed: Settings → Share with apps lists
it under Apps on this phone with its own icon, switch off;
adb logcat -s Sukrara.broadcaststays silent. - Switch on → each minute
→ de.michelinside.glucodatahandler 3; GDH (logcat | grep GDH) logsXDripBroadcastReceiver … SourceInfo => Libre3andGlucodata received from XDRIP, and shows the value. - A new real sensor (phone; the synthetic one has no serial): the next minute sends 4 (SENSOR_ACTIVATE), GDH
setSensorStartTime. - Source → Juggluco: the app switches are greyed with “Only while Sukrara reads the sensor itself”; nothing sent.
- Follower role: the page has neither group.
- Health Connect on → Health Connect’s own sheet; Don’t allow → stays off with “needs access in Health Connect”;
Allow →
Sukrara.health backfill N, Health Connect → Blood glucose lists Sukrara entries, one per minute. - Off → On again: the
wrote …ids repeat the first run’s ids; still one entry per minute in Health Connect. - Spanish: the two groups and summaries are translated.
- Icons: open Settings → Apps → All apps beside Share with apps. GlucoDataHandler (adaptive), xDrip+ (legacy) and Health Connect have the same size, shape and shadow in both; LibreView, Nightscout (switch and upload row) and Juggluco (Glucose source, with Juggluco not installed) show their logos at that size; Tidepool shows the cloud symbol. Same in dark theme.
- Garmin Connect (or a stub app with package
com.garmin.android.apps.connectmobile) installed: it appears under Apps on this phone with “Reads your glucose through the xDrip+ server”; its switch turns the xDrip+ server on/off, and the server row says “read by Garmin Connect”. Without any receiver or Garmin app the group says “… Garmin watches read the xDrip+ server below.”
Q15 Data export
Section titled “Q15 Data export”- Emulator (wearer, debug = synthetic glucose): Settings → Export data; the count updates when the period changes;
This sensor shows only when the current sensor is known (
Exporter.currentSensor). - Save file: the system picker suggests
sukrara-glucose-<from>-to-<to>.csv; saving shows “File saved”;adb shell catthe file (or open it in Files): line 1Glucose Data,…, 5-minute rows, treatments withEntered By; a pen treatment has its priming inPrimed Insulin (units)(1.5,0.0without), typed treatments leave it empty. - Share: the share sheet shows the CSV (a preview line with the file name, no person’s name); sending it to an app (Drive, Gmail, Files) attaches the file.
- Follower (
small_phone): the same page reads “already on this phone” and exports what it received. - Mac: Glucose Report › Report › Export CSV…: the save panel suggests the same name for the report’s period; the file opens in Numbers.
- Import check (optional):
poc/spikes/export-fixtures/tidepool-checkruns Tidepool Uploader’s LibreView driver on a file and prints the records it would upload. - Damaged database (emulator wearer, debug build; never a phone;
DatabaseSchemaTestcovers the same on the JVM): with some history,adb shell am force-stop app.mauri.sukrara, thenadb shell run-as app.mauri.sukrara sh -c 'head -c 8192 /dev/urandom > databases/sukrara.db; rm -f databases/sukrara.db-wal databases/sukrara.db-shm'. Open the app: no crash, an empty history thatSYNTHETICreadings fill again, home’s Some saved data was damaged banner → Damaged data lists the database, andadb shell run-as app.mauri.sukrara ls databases/shows the keptsukrara.db.corrupt-<time>beside the new file.
Q16 Tidepool upload
Section titled “Q16 Tidepool upload”Use a test Tidepool account (or a real one only with synthetic emulator data you delete afterwards: Tidepool web → the data set’s device → delete, or the end-to-end test below). Never switch it on on the user’s phone for a test.
- No device first:
TIDEPOOL_E2E_EMAIL=… TIDEPOOL_E2E_PASSWORD_FILE=<gitignored file> TIDEPOOL_E2E_LEDGER=<gitignored file> ./gradlew :app:testFullDebugUnitTest --tests '*TidepoolLiveTest*'passes: it uploads a synthetic night across a DST change into its own data set, checks dedupe / edit / delete / notes, deletes everything and checks that nothing is left ([tidepool-e2e] left: data=0 … e2e data sets=0 notes=0in the test’s output). Each run leaves one empty deleted upload record (Tidepool’s tombstone; the API can’t remove it), so run it only when needed. - Emulator (wearer, debug = synthetic glucose): Settings → Share with apps → Tidepool: account Not signed in, main switch greyed. Wrong password → “Tidepool didn’t accept this email and password”, dialog stays.
- Sign in → the account row shows the email; nothing uploads until Upload to Tidepool is on. On →
adb logcat -s Sukrara.tidepoolshowsuploaded N readings …; status “Up to date · last upload …”; Tidepool web shows the readings (one per 5 minutes) under a Sukrara device. - Add carbs and rapid insulin in the app, then edit and delete one in the app: Tidepool web follows within a cycle (one food / insulin each, the deleted one gone); a note on its own shows as a Tidepool note.
- Airplane mode for 15 min → status “Will retry · …”; back online → the gap is filled (no missing 5-minute slots).
- Follower (
small_phone): the page has Upload the person you follow, off; status “Waiting for your choice below” and no upload in the log until it’s on. - Sign out → account Not signed in, main switch off; the data stays on Tidepool.
- Spanish: every row, summary, dialog and status is translated.
Q17 Nightscout upload
Section titled “Q17 Nightscout upload”Only a local, throwaway Nightscout with synthetic data (poc/spikes/nightscout-upload/verify/nightscout.sh up; down
afterwards). Never a hosted site, never the user’s phone.
- No device first: with the site up,
NS_E2E_URL=http://localhost:1337 NS_E2E_SECRET=… NS_E2E_TOKEN=… NS_E2E_READ_TOKEN=… ./gradlew :app:testFullDebugUnitTest --tests '*NightscoutLiveTest*'passes (30 days in, a late gap filled, 0 gaps / 0 duplicates, treatments, both sensor events, battery, v3 edit + move + delete), thenpoc/spikes/nightscout-uploadcli check(24/24) andfollowers/run.shpass against the same site. - Emulator (wearer, debug = synthetic glucose;
adb reverse tcp:1337 tcp:1337): Settings → Share with apps → Nightscout → Nightscout upload: Not set up, main switch greyed. A follower has no such row. - Site dialog:
http://my.ns.exampleandhttp://192.168.1.20:1337(https only, the home network too) → “Use https:// … Let’s Encrypt and Tailscale give one free”, Save disabled; a self-signed site on the Mac (openssl req -x509 -newkey rsa:2048 -nodes -subj /CN=localhost -days 1 -keyout k.pem -out c.pem,openssl s_server -accept 8443 -cert c.pem -key k.pem -www,adb reverse tcp:8443 tcp:8443) →https://localhost:8443Test → “Couldn’t connect. The site’s certificate isn’t trusted: … Let’s Encrypt, Tailscale … reverse proxy …” (Spanish too);http://localhost:1337+ the access token → Test shows “Connected · Nightscout 15.0.8”; a wrong token → “The site refused the token or secret”. Save. - Main switch on →
adb logcat -s Sukrara.nightscoutshowssent N; status “Up to date · last upload …”; the site shows the last 30 days, the treatments, SAGE and the phone battery. A new reading is on the site within seconds. - Add carbs, edit the amount, move it, delete it: the site follows (1 → 1 → 0 documents). Long-acting 14u: the site’s IOB doesn’t change.
- Stop the container for a few minutes → “Will retry · …”; start it → the gap fills, no duplicates.
- Post an entry from another device (see
verify/roles-and-conflict.sh) → status “Paused: another app (…) is uploading to this site” with Upload anyway; tap it → uploads resume. - Wrong token saved → “The site refused the token or secret: change it”, nothing more is sent until it is changed.
-
adb logcatwhile uploading: no token, secret or JWT in clear. Spanish: every row, dialog and status translated.
Q26 Trend arrow
Section titled “Q26 Trend arrow”- Android (emulator, debug synthetic source): Settings › Readings › Trend arrow: the preview shows the newest value and an arrow that matches the home card’s; pick each choice: the preview’s arrow turns with a short spring (none with Remove animations on), each row’s own arrow says what it would show, the Ranges row’s summary follows. With the synthetic source rising and falling, the home card’s arrow turns smoothly between readings (not in 45° steps), the glucose notification’s title arrow, the alert text and the status bar agree with it.
- From the sensor: every arrow goes back to the sensor’s own rate at once; Balanced again: back.
- A follower mirroring the wearer: the page is read-only with the Settings from note; the wearer’s change reaches it.
- TalkBack / VoiceOver: the preview reads as one sentence (value, trend word, where it came from); the choices as radio buttons with their lines.
- Mac: Settings › General › Trend arrow: the same choices and preview; the menu bar arrow follows the choice.
Q18 Settings: numbers, Settings from, metrics
Section titled “Q18 Settings: numbers, Settings from, metrics”Emulator (medium_phone wearer, small_phone follower; debug = synthetic glucose) and a Mac test build with
throwaway data. Schema: contracts/settings/settings.json; tools/check/run.sh covers the rest.
- Settings search (Android, #181), light and dark, English and Spanish: the pill opens the full-screen search with the recent searches; night lists Night alerts once (Alerts), opening it shows Alerts › Night alerts and Back walks up through Alerts to Settings; battery, vary, garmin open Alert reliability, Alerts, Share with apps scrolled to the row, which flashes; each result has its section’s icon and where it is in the accent colour.
- Settings sections (#205, docs/35 §7), light and dark, English and Spanish, wearer and follower: the overview reads [Alerts · Alert reliability] [Settings from · Readings (drop) · Graph · Metrics] [Status bar & notification · Lock screen] [Sensor · Sensor end (chequered flag) · Insulin pens] [Sharing · Share with apps · Backup · Import and export] [Advanced · About]; each page’s title is its row’s. Search ranges, mmol, rings, gmi, export, settings file, margin: each finds the page the row moved to and flashes the row. Alerts › Fine-tuning holds the waits and the notification buttons (Reset fine-tuning asks first). Falling fast’s Trend arrow row and Readings › Trend arrow show the same choice and change each other. Change Bedtime in Sensor end: Night alerts › Starts shows it (and back). Sensor end’s Sensor time left rows and Graph’s change each other. Every See also row opens its page and Back returns: Alerts ↔ Alert reliability, Alerts ↔ Readings, Metrics › Time-in-range rings → Readings, Graph’s Ranges → Readings, Sensor ↔ Sensor end, Night alerts → Sensor end (wearer), and Sharing / Share with apps / Backup / Import and export link the other three (no Backup on a follower). TalkBack reads every link row.
- A switch with its own options (owner 2026-11-14), light and dark, English and Spanish, wearer and follower: no row anywhere appears or disappears under a switch. Alerts › Quiet times: four two-target rows (switch + summary For 1 h / Back in range within 20 min / Off); the switch toggles without opening, the row opens the rule’s page (Use this quiet time, its length greyed while off, what it does); search how long / back in range within opens the rule’s page with the row flashed, Back walks up through Alerts. Sharing › Over Bluetooth nearby: the same row (a warning row while Bluetooth is off or the permission is missing); its page has Share over Bluetooth nearby, the fix row, Pair nearby (greyed while off, an open pairing keeps its switch) and the devices nearby (a device opens its follower). Share with apps › Nightscout API: Share with apps on this phone is the main switch; Also on this Wi-Fi stays visible, greyed with Turn on … first while it is off. Mac Alerts › Quiet times: each rule is a row with its summary, Details… and its switch; the sheet has the switch, the length (greyed while off) and what it does; Done and Esc close it; VoiceOver reads … details on the button. TalkBack reads the row and its switch as two nodes.
- Metrics (docs/39; once Rings), light and dark, English and Spanish, font size 1× and 2×, wearer and follower, TalkBack / VoiceOver. Android: Settings › Metrics lists Main metric, Second metric, Third metric, then Last treatment and No recent treatment, each a switch beside a row that opens its page, then Time-in-range rings. Turn the second metric off: the live card drops it at once, the row says Off, its page greys Shows, Period and Dimmed under the switch. Choose GMI on a 1-day metric: its period becomes 14 days and Period offers 7 / 14 / 30 days. Turn the last treatment off: No recent treatment greys with Needs the last treatment on; on again: back where it was (At the right end kept). Time-in-range rings: Very good changes every ring’s number, Rewards off drops the laurel, the colour order drags and resets. Reset metrics asks first. A follower in Wearer: every switch shows the wearer’s value and can’t be flipped. A widget’s own Metrics: None shows the value alone (no last treatment), Up to 1 the main metric. Mac: the Metrics pane does the same with switches and Details… sheets (Done and Esc close them); outside Custom it is a read-only summary.
- A setting the app sets, that a place can change (#209, docs/38), light and dark, English and Spanish, font size 1× and 2×, wearer and follower, TalkBack / VoiceOver. Android: Graph › Time shown says 12 h; its page has the live card, the App radios and Notification and widgets (both Same as the app). Notification → 3 h (the dialog starts with Same as the app (12 h)): the row says 12 h · 3 h in the notification on one line and the notification’s chart shows 3 h. Widgets → 6 h: three lines, 12 h in the app / 3 h in the notification / 6 h on widgets, never a break inside one. Widgets → 3 h too: 3 h in the notification and on widgets. At font size 2× one differing place takes the per-line form. Change the app’s value: places on Same as the app follow. Sensor end / Graph › Sensor time left: the switch turns the app’s off; its page’s Widgets → Off: the row says Off on widgets and the widgets lose the badge. A follower in Wearer sees the app’s value read-only and still edits the places. Search notification: the page opens with the row flashed. A home widget’s Widget settings rows say Same as in Settings. Mac Graph: each setting is one row (value + chevron; 6 h on widgets under the title only when widgets differ); it opens its page inside the pane, the back button, ⌘[ and Esc return; the Widgets pop-up is grey and borderless while it follows, a normal pop-up with its own value; its menu starts with Same as the menu bar (12 h). VoiceOver reads Widgets, 12 hours, same as the menu bar.
- Mac panes (#205): the toolbar shows General, Following, Alerts, Readings (drop), Graph, Metrics (gauge) in that order, each tooltip names what it holds and the window resizes per pane (no animation with Reduce Motion). Readings: change a range → Graph’s Ranges row and the menu bar colour follow; Alert Levels… opens Alerts; in Wearer / Default the ranges and the trend are read-only with their source, the unit stays editable. Graph Edit in Readings…, Metrics Ranges…, Alerts Ranges… land on Readings; the panel’s Juggluco no-data button lands on Following with the Juggluco rows under the follow link. Falling fast Details… › Trend from and Readings › Trend arrow change each other; Fine-tuning… opens the sheet, Done and Esc close it, VoiceOver reads every row.
- Every number row (Readings: the six ranges; Graph: time shown and the widgets’ own, lines, vertical lines; Metrics: each metric’s
period (a GMI from 7 days); Alerts: thresholds, remind, quiet times, Mute all custom; Fine-tuning: Mute…, Relax, the margin; Sensor countdown; Nostr / LibreView intervals) opens the
number dialog: specials + presets, Custom with the unit as suffix and “From … to …” under it;
0, a value above the range and (rates)1.55are refused with that text in red; a valid typed value saves with OK and with the keyboard’s Done (the dialog closes, the row shows it); a custom value shows as Custom + value. - The six ranges and every level alert’s threshold (day and night, the threshold review / setup step’s number dialog; Mac Settings › Readings › Ranges, an alert’s Details…, its night rule), mg/dL and mmol/L, English and Spanish: under the number a line says the values it covers (Low: 56–69 mg/dL, In range: 70–179 mg/dL under low and high, Very low: up to 55, Extremely high: from 300); typing a custom value (Android dialog, Mac field or stepper) changes it as you type; turning very high off makes high’s line reach extremely high (180–299).
- Glucose unit mmol/L (Android Settings › Readings › Glucose unit; Mac Settings › Readings › Unit), in English and
Spanish: the card, the chart’s range labels, the average slot, the glucose notification’s title and Live Update,
an alert (Send a test alert and a real low), widgets, the System UI text, the Quick Settings tile, the report,
TalkBack / VoiceOver and the Mac menu bar all write mmol/L with one decimal (
3,9in Spanish); every glucose number dialog offers mmol/L presets (3.9, 10.0 …) and 0.1 steps, typing3,9stores 70; switching back shows the same thresholds as before in mg/dL; LO / HI say below 2.2 / above 22.2 mmol/L. - Ring order (Android): touch-down on a handle and drag: the row lifts and the others slide live; scrolling the page by swiping over the rows still scrolls; long press a row then drag also works; dragging to the screen edge scrolls the page; the drop settles with a spring and a haptic tick per slot. TalkBack offers Move up / down / to top / to bottom. Mac: drag a row: the image is the row, a gap opens and the others slide; Escape returns it unchanged; Control-click → Move Up / Move Down. No position numbers on either.
- Follower: overview Settings from = Wearer; Graph’s mirrored rows are read-only and the places on its Time shown / Sensor time left pages stay editable; Alerts rows say “Set by the wearer’s app” and quiet times are hidden. Change a range on the wearer’s emulator: the follower’s graph follows within a minute. Custom → the rows appear; Copy their settings asks first, then copies.
- Mac: the same choices per number (pop-up + Custom… field and stepper), Settings from in General, drag to reorder the rings. Spanish on Android: every new row and dialog translated.
Q19 Complete flows (states and exits)
Section titled “Q19 Complete flows (states and exits)”Every app change (CLAUDE.md Complete flows; user, 2026-10-21: “There’s no way to unmute! On any platform”). The
states check only sees that FEATURES.md has the paragraph; this is the walk-through behind it.
-
List the states the change lets a user enter (muted, slowed, scrolled, dismissed, disabled, paired, custom…). Each one is in the feature’s States and exits paragraph in
docs/FEATURES.md. -
Each state is visible where the user looks for it, on every platform and surface that shows the feature (Android app / widget / notification / lock screen, Mac panel / widget / notification / Settings).
-
Each state has a way to change it and to leave it (undo, cancel, turn off, unmute, go back), without needing a notification, and with TalkBack / VoiceOver (a button or an accessibility action).
-
Leaving it updates everything that showed it at once (history, badge, widgets, ring, notification).
-
What’s left behind (docs/44 Appendix G §8: earlier reviews compared screens and never asked what a hidden state keeps doing). For a state that ends or is replaced, check what it leaves running or stored, not only what shows: open sockets (Mac
lsof -nP -i -a -p $(pgrep -x Sukrara); Android the relay’s log oradb shell cat /proc/net/tcp6by the app’s uid), stored accounts and keys, the settings in use, the alert role, the treatment log entries go to, and what the other side (the wearer’s list) believes. Leaving a Sukrara link: Q30’s table. -
Status bar text placement without the LSPosed module: the rows say the placement needs the module and what shows meanwhile; the dialog lets you leave a clock placement (system-icon placements selectable).
-
Alerts: emulator
SYNTHETIC --ei cycle 135(a low) → Mute 30 min → the muted notification’s Unmute brings Low glucose back at once; Mute… → the pill opens the sheet → Change to 15 min; Remind less → the chip → Remind as usual; home Mute alerts → 1 h → the muted pill on the card and widgets → the line counts down → Unmute; Until you turn it off stays after a restart; the muted notification’s header counts down; a high muted, then a low: the low alerts; muted low back at ≥ 80 for 10 min → the muted notification goes; durations everywhere read 1 h / 2 h; log carbs → Alert me anyway in Settings → Alerts › Active now. Mac (sukrara-snap shell:panel-low-muted-*,panel-muted-all-*): the rows under the card and the pill’s menu. -
Log carbs (#194): emulator wearer,
SYNTHETIC --ei cycle 125(a very low): the alert’s buttons read Log carbs, Mute…, Remind less (dumpsys notification:actions=3) → Log carbs opens the quick dialog over the app with Carbs focused and, once typed, Lows quiet for 15 min → Save → the alert goes, the card says Low alerts muted after carbs; again with Cancel: nothing saved, the alert stays and repeats.ALERTS --es kinds high: no Log carbs. Mute a low → the muted notification has Log carbs, Unmute, Change time. Lock the phone (a PIN): Log carbs asks for the unlock, then the dialog; Mute… still works locked. A follower without Can add treatments: no Log carbs; with it: the treatment reaches the wearer and the wearer’s clear removes the follower’s low (its very low keeps repeating, #2). TalkBack reads Log carbs. Spanish: Registrar hidratos. Mac following with Can add treatments: a low’s Options list Log Carbs… first → Add Treatment on Carbs, the low comes back silently; without it (or Juggluco) no Log Carbs…. -
First-run setup (emulator, fresh install, #175): on every step a rotation, home → back from recents and a process death (home, then
adb shell run-as app.mauri.sukrara kill -9 <pid>, reopen) return to the same step, also on a step reached with Back. Back on Let alerts reach you (the step after the role) goes home with Finish setup · Next: Let alerts reach you; Continue resumes the walk there. Set up sensor and Export CSV first → their Back → the step that opened them. After the walk, the banner’s skipped steps come one by one, also after a rotation (Later → the next, Back → home, still on the card). Settings › Sharing › Set up sharing → Back → Settings › Sharing. Once a role exists nothing of setup opens by itself, except Bring your history back at launch when it is the only step left. Mac (swift test --filter SetupFlowTests): close the setup window half-way, Finish Setup… reopens the same step. -
Setup in two parts (#181, emulator,
pm clear): Step N of 5 over the essentials only; after the thresholds The essentials are done lists the optional steps (with Later on Permissions / Sensor: Some essentials are left for later and what is still to do). Later → home (no banner for the optional steps) → Settings’ first row Finish setup with their titles (and no updates suggestion beside it) → Optional step 1 of N; Later on Your followers keeps it on the row, Not now / Start empty don’t.PEN_TAGS --ez blocked false(made-up NFC): Insulin pens → Read my pens turns Settings › Insulin pens’ reading On; I don’t use a smart pen leaves Ask. Dark mode and Spanish (Paso opcional 1 de 3, Termina la configuración); TalkBack reads each step’s counter. -
Setup’s Root and Status bar & notification (docs/36 §11; GitHub build): Root asks Is this phone rooted?; Yes, it’s rooted asks for root at once (Magisk’s prompt; KernelSU not allowed → Allow root for Sukrara with Check again); allowed and back → the walk goes on by itself to Status bar & notification with Status bar text picked and a confirm haptic; It isn’t rooted → the chip stays picked. On a rooted phone with LSPosed the question is skipped and the check runs by itself. Google Play build: no Root step, two choices. Spanish, TalkBack.
-
Add treatment (#181, emulator): the note is empty while empty (no example), no pen reminder under the fields; When? › Minutes ago is the length wheel (flick: a tick per length, minutes then hours in one scroll, it snaps), the chips 5m 15m 30m 1h scroll it there; TalkBack: Minutes ago, 5 minutes, swipe up / down steps one length, the chips read 5 minutes; Spanish 5 min / 1 h. Home’s quiet sheet Change to and the report’s 1d … 30d use the same short lengths. The sheet with the keyboard: opening, both come up together; drag the sheet down slowly: the keyboard follows under the finger and leaves with it, a short drag springs back with the keyboard; again with Remove animations on.
screenrecordthe two and step the frames.
Q21 Insulin pens
Section titled “Q21 Insulin pens”Emulator only (debug build, synthetic data: PEN_READ …, docs/FEATURES.md “Insulin pens”); a real pen
only on the user’s phone, by the user. The full checklist is poc/spikes/novopen-android/PRODUCT.md §9 (59 rows).
- Fresh install (Ask): the first tap shows Log this pen in Sukrara?; nothing logged; Turn on → New pen added · … · 412 earlier doses left out with Log 8.5u + Set up (opens the pen’s page: Name, Insulin, Log it; no separate setup screen); No → later taps do nothing, Settings off.
-
1, 0.5, 8, 0.5→ card 8.5u logged · Rapid · 13:12 · 1.5u primed, Add treatment + Undo, no scrim, closes by itself; the low-importance notification has the same text; home row8.5u rapid · from the pen. - Undo → Undone; a merged typed treatment is back with its note; Doses read Not logged → Log this injection.
- Rescan → Nothing new; top-up → Now 8.5u · 0.5u added;
1, 1.540 min ago → Priming or injected? card + home card + notification, Log 1.5u clears all three. - Pen treatment sheet: flip a dose → header updates, Save → snackbar Treatment changed · Undo; all priming → Remove from log; TalkBack reads one node per dose with Mark as injected / priming.
- Type 8u rapid within 45 min of a pen treatment → Already logged by your pen?; carbs in the same save are saved. Rotate with the question open: it is asked again. Over the lock screen the countdown ring stands still while it is open; Cancel → the form, the ring runs again.
- Light and dark (
adb shell cmd uimode night yes|no, #181): the read card over home and over another app (Android’s Settings), Already logged by your pen? and Add treatment follow the phone’s theme; the navigation bar handle under the card stays legible; switching the theme while the card is up redraws it in the new theme. - On Android 17 a pen tap from another app opens the card (no
does not have DISPATCH_NFC_MESSAGE permissionin logcatNfcDispatcher); a Libre tap with Sukrara closed opens the New sensor screen (0.11.47). - Taps blocked (the debug
PEN_TAGS --ez blocked truecommand on the emulator, with Open Sukrara when you scan a sensor on for the sensor part; on a phone, Android’s own tag-intent screen): home banner names what’s blocked (pen / sensor / both) with Turn off and Allow; the pens and Glucose source pages show the card on top (the sensor page also turns its Open Sukrara when you scan a sensor row into a warning row); Allow opens Android’s screen; back allowed → everything gone. Ask state: no home banner, pens page card only. Light and dark. - Big read (
PEN_READ --ez first true --el firstAgo 7200 --es doses "-6000:6,-3000:5,-30:4"): the card says 3 injections logged · Since with Review first and Undo; the doses are on the graph. Review → Review read with 3 injections logged on, only that read’s rows; a row opens its sheet. Undo this read → dialog → Undo read → snackbar Read undone, the rows stay as Not logged, the graph loses them. Again with a row’s treatment deleted first (sheet Delete) → Couldn’t undo: some of these treatments changed since…, nothing else changes. The pen page shows Review the last read until undone. An everyday read ( -30:4alone) has no Review. With Notification after each read on, the notification has Review and Undo. Spanish. - Pens page intro: the phone’s back with the circle on this phone’s NFC antenna (the same spot as the new-sensor
scan) and Touch the back of the phone with the end of your pen…; TalkBack reads the drawing’s description and
the sentence.
PEN_JUGGLUCO --ez installed truewith reading On → footer A pen tapped while Juggluco is open on screen… (text only);false+ resume → gone. Main switch: fresh install Off · asks when you tap a pen; on → the settings and pens show; off → only Your pens (if any) and the footers; no row icon twice on the page. - A bank / transit card or a passport held to the phone (reading on): nothing at all (no card, no vibration, no notification); only a pen tap shows the card (the filter is IsoDep + NfcA since 0.11.46).
- Failed read → red card, REJECT haptic, nothing logged; a second one within 2 min adds the tips. The card springs up; while reading the wavy ring fills with a tick per segment; a logged dose pops a check and counts up (8.5u logged); a failure shakes once. Remove animations on: none of it, a still ring, final numbers.
- Home question card (
PEN_READwith1, 1.540 min ago, and a typed 8u near an 8.5u read twice for Same injection?): under the glucose card, never above it; Log 1.5u / All priming answer it and the next one fades in; several typed treatments → Choose → the sheet (radio rows, None of these, Save disabled until a choice); the same sheet from Doses read; TalkBack reads amounts as units. Light, dark, largest font. - Add treatment with a pen (a real pen, on the phone, by the user): Injected? Hold your pen to the phone. under the fields; holding the pen → Reading your pen…, the dose counts into Rapid (Long-acting for a long pen) and When moves to its time, Logged from your pen · 1.5u primed + Undo; type carbs, Save → only the carbs are new; change the dose by hand → Already logged by your pen?. A read card’s Add treatment → the dialog at the injection’s time with the other insulin focused. Rapid typed by hand with a pen known → toast … · Next time, just tap your pen (once a day, 3 times). A day without a read → Pen read 1d ago on the treatments’ title opens the pen. Carbs typed alone → Injected? Hold your pen to the phone. under the treatments for an hour.
- Uploads (LibreView / Nightscout / Tidepool on): a pen dose goes up only 10 min after its last dose; a top-up within those 10 min goes up as one treatment.
- Notification after each read off (default): a read posts no Pen reads notification (Pen doses to check
still posts). On: the read’s notification, silent, no heads-up;
dumpsys notification --noredactshows it in Sukrara’s info group (g:app.mauri.sukrara.INFO), never ing:Aggregate_…with the glucose card or an alert (ALERTS --es kinds high), chip on and off. Switching it off removes the shown one. Notifications blocked: the row says Blocked in Android settings and opens the channel page. - Treatment dialog with pen reading on: no pen icon in the title row; a pen with nothing new → Nothing new under the fields for 3 s; a failed read → red Couldn’t read the pen for 3 s.
- Untested NovoPen 6 (a new pen whose doses are all whole units:
PEN_READ --es serial NP6000001 --es doses "-30:4") → Untested pen added; Set up → the pen’s page: red 10 s confirmation → display check; It doesn’t → Sukrara doesn’t log this pen. - Your pens: one row per pen (pen icon, not a pencil), · Revisa sus ajustes until its page was opened; no extra setup row.
- Which pens work = the page’s footer (always, also with reading off and no pen; no rows, no red tag): Sukrara reads NovoPen Echo Plus and NovoPen 6 (untested). Other NFC pens, and Bluetooth pens or caps like Tempo, InPen or Mallya, aren’t supported. / Sukrara lee NovoPen Echo Plus y NovoPen 6 (sin probar). …; TalkBack reads it as one paragraph. Settings search NovoPen 6, novopen, pen, Spanish pluma → Insulin pens. Light and dark, largest font.
- Automatic detection (pens page row Priming under 2u · one injection within 10 min, reading Ask / On; its own
page): intro (applies from now on), groups Priming (priming size, priming ahead of time), Injections (one
injection, small doses on their own, last injection on a new pen), Doses you type (time apart, amount apart,
amount apart, big doses), a footer under each group; each row shows its value, no row icons but Reset’s;
each opens the one number input; Reset to defaults disabled at the defaults, else a dialog (Cancel keeps the
values, Reset restores them). Changing One injection to 15 min and reading
4then412 min later logs one 8u treatment; treatments already logged keep their split. Search finds every row. - A new pen whose last injection matches a hand-typed treatment: the pen page’s card says Matches your 8u treatment at … and the button Replace your treatment (Reemplazar tu tratamiento); tapping it replaces the typed treatment (pen time and amount) and the card goes; the read card’s pill Replace with 8.5u; Doses read → the session’s sheet Replace your treatment. Without a match: Log it / Log 8.5u / Log this injection as before.
- Follower: no Insulin pens row; pen treatments open read-only.
- LibreView / Nightscout / Tidepool / CSV / graph / insulin mute:
aonly; CSV column 23 Primed Insulin. - Spanish: pluma, purgado, amounts
8.5u.
Q22 Follower over a local relay
Section titled “Q22 Follower over a local relay”Two emulators with fresh debug installs (medium_phone wearer, small_phone follower; never a physical device) and
the local test relay; no public relay is involved (docs/DEVELOPMENT.md “Relays in debug builds”).
python3 tools/relay/relay.py --port 7447on the computer (its log shows every connection, REQ and EVENT).- Before pointing anywhere: wearer
SYNTHETIC --ez on true, open the app, Settings › Sharing › Set up sharing → Start fresh. The app’s uid has no socket in/proc/net/tcp/tcp6(a debug build reaches no relay). RELAYS --es urls ws://10.0.2.2:7447on both emulators (the app process ends; open it again). The wearer’s log lines appear in the relay (REQ inbox, kind 30078 / 21078 events) and its uid’s only socket is…0202000A:1D17(10.0.2.2:7447).RELAYS --es urls http://xis refused in logcat (SukraraDebug) and changes nothing.- Wearer: Share with someone → Create invite. Follower:
adb shell am start -a android.intent.action.VIEW -d '<link>' -p app.mauri.sukrara→ Someone else’s → Their Sukrara → Join: the relay logs the invite lookup (REQ q-…, 1 stored) and the request (kind 1059); the follower shows Waiting forto allow you with Ifasks for a code: NNNN as one quiet line. - Wearer (left on the share screen with the QR): within seconds the screen turns into
asked to follow you and the approve dialog shows over it, with the whole label under Your invite for and no code (an ordinary link) → Allow. Without touching either phone: the share screen saysfollows you now (Done → Settings › Sharing lists them) and the follower’s card turns into You follow(#174), then home shows the wearer’s value and graph; the next minute’s reading arrives on both. Both uids still have only the 10.0.2.2 socket. - Optional on the same pair: Deny instead of Allow (wearer: You didn’t allow
; follower: didn’t allow you… by itself), a third emulator opening the same link first or second (the second shows Another device used this invite… by itself; the wearer’s dialog asks to type the code the first one’s screen shows), an invite left unused until it expires (This invite expired), a writer’s treatment, Mute mirroring, Remove follower. Allow / Deny after Android stopped the app (#167): a new request showing, end the wearer’s process (adb shell run-as app.mauri.sukrara kill <pid>; the notification stays), then the notification’s Allow: the follower is let in within seconds, the notification leaves, and the wearer keeps sharing (Settings › Sharing still Sharing, the relay keeps logging its events, the follower’s next minute’s reading arrives). - Can add treatments and Nearby devices (docs/40): on the wearer, before step 4, revoke Nearby devices
(
adb shell pm revoke app.mauri.sukrara android.permission.BLUETOOTH_ADVERTISE) and turn Let them add treatments on in Share with someone. The approve dialog shows Letadd treatments already on; Allow asks Nearby devices right then (deny it). Home shows Bluetooth sharing is blocked (Allow / Turn off), Settings › Sharing says it in red, and the follower’s row carries the Can add treatments mark; its sheet has the switch on. Allow → the banner leaves. On the follower, setup’s permission step lists Nearby devices; revoked while following, home shows Bluetooth is blocked with its close. - Who is nearby (2026-11-15; needs real Bluetooth: two physical test phones or a phone and a test Mac, never the owner’s): the wearer’s header reads 1 follower until the follower’s device connects nearby, then 1 follower · ᛒ 1 (TalkBack: 1 follower, 1 nearby over Bluetooth); Settings › Sharing marks that follower with the Bluetooth-connected mark, and Over Bluetooth nearby › Nearby devices lists it Connected. Out of range (Bluetooth off on the follower): the header loses the mark, the follower’s mark turns plain and dimmed, Nearby devices still lists it Disconnected (also after a restart of both apps) until Remove. The follower’s header shows the Bluetooth mark, then the globe, and with airplane mode the crossed globe in red. At the largest font and in Spanish the header line stays whole on one line (the people icon replaces the words where they don’t fit).
- Optional, Replace this identity (#161): wearer Settings › Sharing › Backup › Replace this identity › Start
fresh, confirmed. Telling your followers… fills (1 of 1 told) and ends on Started fresh; the relay logs the
kind 1059 notice before the new identity’s events. Follower:
stopped sharing with you (notification and home), no No data alarm afterwards. Again with the relay stopped: Telling your followers… waits 15 s with Cancel; Cancel says Cancelled. Nothing changed… and the follower keeps following once the relay is back. - Leave (PROTOCOL-v2 “Leave”): follower Stop following (the leave questions say
’s phone is told. ). The relay logs one kind 1059 eventp-tagged to the wearer’s identity, on the follower’s own connection that closes within a second of it (+ … connected,EVENT kind 1059 … ok,- … gone; with the follower’s Bluetooth off, so the relay alone tells): the leave counts as told and sent. The same event again every minute or so (… duplicate: already have this event) means the relay’s answers aren’t counted (PROTOCOL-v2 “Relay answers”). The wearer showsstopped following you within seconds, Settings › Sharing counts one follower less, and Past followers lists them with Left. Again with the wearer’s emulator off: start it a few minutes later and the same happens (the date is still when they left). Again with the follower offline (airplane mode) at Stop following: after about 20 s the follower shows hasn’t been told yet . Back online, it goes within seconds (or with the app closed, from the WorkManager job) and the notification leaves. A Mac follower: Not following anyone sayshasn’t been told yet… while offline. The wearer’s escalation line (Lately) with no follower left reads no follower to tell.
Q23 Import history
Section titled “Q23 Import history”Synthetic data only: a throwaway Tidepool account and files written from the emulator, never the owner’s.
- Fresh install (emulator, wearer): setup’s last step Bring your history back; Start empty goes home and the step never comes back; reinstall, Bring it back opens Settings › Import and export › Import history and Back lands on home.
- An update that bumps the database version over an install with history (debug build): the history is empty, no crash, and the next launch opens Bring your history back on its own; Back counts as Start empty.
- Choose a file with an export from Export data › Everything on this phone (and one from the earlier app’s Export data › All time): the card shows progress and the counts; the graph and the report have the history; choosing the same file again adds 0 (“… were already here”).
- A LibreView-layout file in mmol/L with day-first dates (
integrations/src/test/resources/history/): the values read in mg/dL as expected; a random CSV says “This isn’t a glucose file…”. - Issue #176:
libreview-us-12h.csvandlibreview-es-12h.csv(one-digit 12-hour times,p. m.) import with the right times; the same file with one date changed tonoonsays “Sukrara can’t read the dates in this file (the first one it couldn’t read: …)” with Choose another file, Report the problem (the issue form shows only00-00-0000 noon-style layouts, no values) and OK; the owner’s own LibreView download imports on their phone. - With a LibreView account signed in, the LibreView steps dialog says “sign in as
”. - Tidepool (a test account with data): Sign in to Tidepool first opens the Tidepool page; signed in, the row imports the last 90 days with the progress bar moving week by week; Stop half way keeps what was added and a second run completes it with no duplicates; the Tidepool upload (if on) never sends the imported data back.
- The sensor’s own backfill after an import (emulator
SYNTHETICover imported readings): no two points within 2 minutes on the graph. - TalkBack: the progress card reads the added counts as they change; Stop and OK are buttons. Largest font, dark theme, Spanish.
Q24 Backup to a password manager
Section titled “Q24 Backup to a password manager”Emulator wearer with a throwaway identity (setup’s Start fresh); KeePassDX (F-Droid / its GitHub release) as the test password manager: create a vault, turn its Educational hints off, lock it once so the save flow unlocks it (a vault just created refuses user verification), and set a screen-lock PIN. Never the owner’s identity.
- No password manager (a Google APIs image without an account answers no create options): Settings › Sharing ›
Backup › Save to password manager → the red card No password manager can save it with Open settings and
Make a recovery code instead;
run-as app.mauri.sukrara cat files/diag/diag.loghaspassword manager: none takes passwords (TYPE_NO_CREATE_OPTIONS). - Open settings opens Passwords & passkeys; Back without changes asks again (same card); turn KeePassDX on, Back → the system’s sheet Save password to sign in to Sukrara? opens by itself.
- Close the sheet → Not saved: you closed the password manager.; tap the row again → Continue → unlock the
vault → add the entry → Saved to your password manager…, the row reads Save to password manager again ·
Saved
, the intro says it’s saved, home’s Not backed up is gone. - Save to password manager again (pick the existing entry or a new one) → saved again, no error. Turn the phone while the sheet is open and close it → the card still says Not saved….
- Make a recovery code instead from a card → the recovery dialog → Copy and close → Recovery code copied. Paste it now….
- The restore side finds it: Backup › Replace this identity › Restore another identity (needs a live reading from this phone’s own sensor) › Restore from password manager → the sheet lists Sukrara · npub1… → That code is for the identity this phone already shares as. Nothing changed. On a second emulator with the same password manager vault, setup’s Restore from password manager takes it.
- Owner’s phone (TEST identity, after
tools/install.sh phone): the same with the real password manager; if it fails, Settings › Advanced › Log shows thepassword manager:line with the error’s type and number. - TalkBack reads the row as a button (SPA’s stock double-tap to activate), each card when it appears, its title as a heading; largest font and Spanish wrap the full-width buttons.
Q25 Updates (Android, GitHub version)
Section titled “Q25 Updates (Android, GitHub version)”docs/FEATURES.md › Updates (Android, GitHub version), #188. On an emulator only (never the owner’s phone), a debug
build of the GitHub version (:app:assembleFullDebug) as the running version and a newer one (the same code with a
higher VERSION, never committed) as the “release”, both signed with the debug key; a third copy re-signed with
another key (apksigner sign --ks other.jks) for the refusal:
python3 tools/updates/serve.py new.apk --port 8765 # [--digest <64 hex>] lists another SHA-256adb -s emulator-5584 shell pm grant app.mauri.sukrara android.permission.ACCESS_LOCAL_NETWORK # 10.0.2.2 is localadb -s emulator-5584 shell am broadcast -n app.mauri.sukrara/.debug.DebugReceiver \ -a app.mauri.sukrara.debug.UPDATES --es server http://10.0.2.2:8765/The command ends the app; open it again: with a test server it checks once at start (otherwise an hour after start,
then daily), but only once Check for updates automatically is on (opt-in: off as installed). SYNTHETIC --ez on true
for monitoring; --ei cycle 135 brings a low (an alert), --ei cycle 0 ends it.
-
Opt-in, on a fresh install (
pm clear): setup shows Keep Sukrara up to date right after the alert checklist (Step 4 of 8 for a wearer), its two buttons equal in size and style; Not now → the sensor step, About’s switch off, and home never shows the banner (Settings › Show closed tips shows it again, then Turn on there). Again with Turn on → About’s switch on. Back from the sensor step shows Keep it on / Turn off. -
An install from before (setup finished, the switch never stored; or
pm clear+ finish setup with the step answered, then clear only thesettingsDataStore’supdateChecksand thehome-bannersfile): no setup walk for it; home shows Keep Sukrara up to date after any Finish setup banner, Turn on → the snackbar Sukrara checks for updates once a day…, the banner leaves and About’s switch is on; turning it off in About doesn’t bring the banner back. Not now → Tip closed with Undo (brings it back). The Settings overview shows the same card at its top, before the clinic’s. -
The Google Play build (
:app:assemblePlayDebug): no updates step (Step N of 7), no banner on home or Settings. -
Sukrara 0.x is available arrives once, silent, under Silent in the shade, never in the Glucose alerts group; Update and Release notes (opens the test page); tapping it opens Settings › About. A second check of the same version posts nothing.
-
Update while a low alert is showing: Downloading… with progress, then … is ready to install · It installs once no alert is showing (Cancel); nothing installs. Once the alert is gone, within the next retry (5 min, then longer) Android asks (Install unknown apps for Sukrara the first time, then Update this app?) → Update.
-
The new version is running (About’s version) and the glucose notification is back within a minute without opening the app (
adb shell dumpsys activity services app.mauri.sukrara: MonitoringService in the foreground). -
The re-signed APK (serve it instead): The update to 0.x didn’t install · It isn’t signed by Sukrara… keeps running; nothing changed.; the running version is unchanged; nothing left in
files/no_backup/updateonce refused.--digestwith another hash: the same with The file isn’t the release’s. -
Android’s own Cancel in its prompt: Android didn’t install it… keeps running with Try again.
-
Settings › About shows each state with its way out (Q19), Release notes, Check again; the Updates group’s two switches (the second dimmed with Needs the automatic check while the first is off); search finds both.
-
Install updates automatically on (Wi-Fi): after the check the update installs without a tap once allowed (or says Android asks you to confirm this update and offers Install); the new version posts Sukrara updated to 0.x with Release notes.
-
TalkBack reads every update row, the setup step’s lines and both buttons, the banner and its two pills, and the notification’s buttons; Spanish strings fit (the step and the banner at the largest font too).
-
The release (not emulator): after publishing, the GitHub version on the owner’s phone shows the update within a day, the asset is
Sukrara-<version>.apkwith GitHub’s digest, and it installs and comes back monitoring.
Q27 Garmin link (phone → Sukrara Aura) and the xDrip+ server page
Section titled “Q27 Garmin link (phone → Sukrara Aura) and the xDrip+ server page”Cheapest first: the simulator, then the owner’s phone and watch (only after tools/install.sh phone and the face on the
watch; the watch shows the real value: check it against the phone, never photograph it).
- Simulator (debug build on
medium_phone,SYNTHETIC --ez on true,GARMIN_SIM --ez on true, open the app):adb forward tcp:7381 tcp:7381andadb forward tcp:17582 tcp:17582; run the face in the Connect IQ simulator (descentmk343mm), adb Connection › Start (and Settings › Use Device HTTPS Requirements off for the fetch; put it back after). Within a minute the face shows the emulator’s value and trend; Simulation › Background Events › Temporal makes it fetch (Share with apps › Garmin: Sukrara Aura “Watch face · in use, asked this phone at”). Stop the emulator’s app: the face’s value goes late, struck, then No reading since, counting from the reading’s time. - Phone + watch: Share with apps › Garmin says “
has the - Walk away with the phone (or Bluetooth off on the phone): the row says “
isn’t connected”; the face goes late → struck → No reading since and Garmin’s No phone; the page’s line “Not connected · has the - Watch restart, phone restart, Garmin Connect swiped away: the face shows the last reading aging right away, and is current again by itself (push on reconnect, or its 5-minute fetch).
- The main switch off: the row says “Off”, the page’s note “Your watch gets no readings from this phone”, nothing more reaches the face (it ages out); on again: current within a minute. Send now (an action button, a haptic) sends at once. Open Garmin Connect opens it. Pick another face on the watch: within 11 minutes Sukrara Aura says “not in use”; back, “in use” after its next fetch.
- Other watch faces and data fields › xDrip+ server opens the xDrip+ server page (also from Share with apps › Apps on this phone): Use xDrip+ server on shows “Listening on 127.0.0.1:17580 · not asked yet”, Apps that read it lists Garmin Connect with its icon and no switch; a face made for xDrip+ asking it updates “last asked at”; off again from either way in. Light, dark, largest font, Spanish: the action buttons’ labels readable, nothing clipped.
- A low with the pill, a mute, a treatment: the face’s pill and treatment field change within seconds of the phone’s card.
- TalkBack: the row and every page row read their text; each action button reads as a button with its label; the main switch reads as a switch with its note.
Q28 Garmin watch face (Sukrara Aura)
Section titled “Q28 Garmin watch face (Sukrara Aura)”-
uv run --with pillow --with pyobjc-framework-Quartz apps/garmin/tools/garmin_test.py run <dir> [<core refs>](simulator, ~8 min): numbers for every case, 0 differences; open the worstdiff-core/images: every red pixel is a glyph’s edge (fonts rasterise differently) or a dial’s anti-aliasing / its 16-bit colour, never a moved, missing or wrong-coloured element.core_refs.mjsmakes the dial-less references. - The
dial-*matrix andhalo-*insim/besidedocs/img/aura/ref/: each dial gathers at the bead’s height, spreads with how far out of range, grey and dashed when old; no dial line touches a digit (never a strike-through) with the halo on outline or box. - Look at
sim/for the safety states side by side withdocs/img/aura/ref/: old (struck, grey, hollow bead, no arrow), no reading since (no figure anywhere), LO / HI (no number, a ring), very low (white on red), warm-up, sensor ended, nothing paired. The time is readable in every one, always-on and night included. - The run’s “always-on” lines: every
aod-*case under 10 % luminance (very low and LO the brightest). Simulator › Settings › Display Mode › Always On on the very low and LO cases: no luminance warning. - On the watch, a new reading while awake: the bead, trail and arrow glide (0.9 s); the sweep steps once a second.
- On the watch, always-on on: a notification while the screen is dim, left untouched until the watch goes back to
the face; then a menu left the same way. The face stays (#223: no new Sukrara Aura entry in
GARMIN/Apps/LOGS/CIQ_LOG.YML/.BAKover USB). - The sides (
sides-*,sensor-rail-*insim/beside the references): the glucose rail mirrored on the left (up still higher, the dial’s focus on its side), the battery and sensor labels right-aligned on the right, both marks only with both labels, the warm-up bar,--without dates; the run’s “combinations” line 0 overlapping. On the watch: Customize › Left side / Right side change the face at once; with a sensor rail in the sensor’s countdown the bottom field stays the person’s own (the rail is amber), and the sensor rail’s days match the phone’s sensor page. - On the watch (
tools/install.sh watch, then the owner selects the face): it draws, Customize opens and every setting changes the face; Private hides the value and touch and hold shows it for 5 s; Spanish with the watch in Spanish. - On the watch, raise the wrist a few times with Do Not Disturb off: the full face at the panel’s brightness,
never the always-on look. After the next fetch,
adb logcat -s Sukrara.Aurashows eachX@<t>followed byDw@<t>within a second (docs/43 “The screen”).
Q20 The person and the feel
Section titled “Q20 The person and the feel”Every app change (CLAUDE.md Design from the person’s life first, Make it juicy; user, 2026-10-23).
- The feature’s spec (PRODUCT.md or the round’s notes) answers: why the person wants it, the contexts they’ll use it in, what it takes off their mind, what triggers the action and whether that can be detected or prompted, how it’s discovered, what people say online and what other apps do (judged).
- Nothing blocks the person unless a confirmation already existed there or safety demands it.
- Every action answers within ~100 ms: a visible change, and a haptic where the platform uses one (confirm / reject); motion shows where things came from and went; numbers that change animate; no jank on a mid-range phone.
- With reduced motion / remove animations on, and with TalkBack / VoiceOver, everything still works and reads well.
Q30 Source: whose glucose and where it comes from
Section titled “Q30 Source: whose glucose and where it comes from”docs/44 Person × Source; FEATURES.md Source. Emulator / a dev Mac with synthetic data only.
-
Fresh install: setup’s Whose glucose shows two illustrated cards (light and dark), nothing preselected; a pick lifts its card, the ring breathes once, a tick; with Remove animations it snaps. TalkBack reads “radio button”.
-
Yours → Source shows the sensor (Recommended line), Juggluco and Sukrara on your other phone; Someone else’s → Juggluco and Their Sukrara. Back from Source returns to the cards, nothing stored.
-
Settings › Source: Whose glucose and Where it comes from open the steps alone (no Step N of M); Whose glucose → Continue → the source, Back → the cards again (the pick kept), Back → Settings › Source unchanged; a change says what changes (Switch to …?; from their Sukrara to Juggluco nothing about a sensor), a change of person with history asks Delete the earlier history? (Export CSV first, Cancel). Last reading reads Just now / 2 minutes ago / None yet. Juggluco not installed: Connect Juggluco says so. Press a person card: the ripple stays inside its rounded corners.
-
Their Sukrara: the follow rows and Settings from are on Settings › Source; Settings › Sharing says sharing is for your own glucose and leads there. Stop following → setup.
-
An install updated from a version before #213 (wearer, Juggluco, follower): monitoring and alerts keep running; setup opens on Whose glucose preselected; answering the same deletes nothing; Back → home’s Finish setup. A wearer with history but no pairing (emulator:
run-as app.mauri.sukrara rm files/state/source*.jsonunder/data/user_de/0/app.mauri.sukraraafterSYNTHETIC): Yours preselected, Someone else’s asks Delete the earlier history? (never keeps your readings as theirs). -
Mac: setup’s Whose glucose (two cards side by side, someone else’s in purple) and Source (radio rows), neither with Skip; Settings › Source pane; Juggluco on the network chosen while following someone shows Juggluco only; back to Their Sukrara shows the wearer at once; Changing the source keeps the person… only while following; an unanswered Mac’s banner has Answer… (setup’s two steps).
-
Nightscout (FEATURES.md Nightscout as a source): against a local fake site with synthetic data (
adb reversetohttp://127.0.0.1:<port>on the emulator; never a real site). Source → Nightscout (Online group) → Connect: a wrong token says so under its field, plainhttp://to another host says Use https://, a pasted…/?token=…connects without typing; connected → Reading received; Later → home’s Finish setup. -
Stop the fake site: home (once the value hides) and Settings › Source say No answer from … with Try again; airplane mode: No internet; a refused token: Sign in again opens Connect with the address filled in.
-
Treatments both ways: an entry logged in Sukrara appears on the site; one added on the site appears read-only (from Nightscout, change it there, no edit or swipe); deleted on either side, it goes on the other. A read-only token says so on Settings › Source. Upload to the same site says Your source…; Tidepool shows its Glucose and treatments from Nightscout switch off.
-
Sensor life: a Sensor Start on the site 30 min ago → warming up; 16 days ago → Sensor ended, no no-data alarm.
-
Sensor start and length (decision 10): a site without a Sensor Start → Settings › Sensor says Start not known with Set start; the dialog refuses a time later than now and a start whose length is over; Save → warming up / running, the reminders follow; a Sensor Start posted on the site later replaces it; Remove → not known again; switching the source and back → gone. LibreLinkUp: Lasts 14 → the card’s time left and the end move a day at once; Mac: the same in Settings › Source › Sensor. Sensor ended notification’s Replace sensor with an online source opens Settings › Sensor.
-
Mac: Do you have Sukrara on your phone? → No · Read it online → Nightscout → Connect; the panel’s states; Add Treatment works on this Mac’s log, the site’s entries are read-only.
-
LibreLinkUp (FEATURES.md LibreLinkUp as a source), on the emulator against the fake only (never a real account:
tools/librelinkup-probe/fake.py+ theLIBRELINKUPdebug command, docs/DEVELOPMENT.md): Source → LibreLinkUp → Connect: with a LibreView account signed in, Sign in as … in one tap (refused,wrongas the LibreView password: the form with the email filled in, the refusal under the password); Use another account → the form; a wrong password says so under the field;login=terms,login=ratelimit,login=redirect,login=version(signs in, every call names 4.18.0); several people → Whose glucose?; no one → the invite instructions and Try again; connected → Reading received. History step: Your last 12 hours came with LibreLinkUp → Import history; a LibreView file over the same hours adds only the older readings (run-as … sqlite3: no two readings of two sources within 2 min). -
LibreLinkUp’s states (the fake’s
_fakeswitches):stopped=1→ home Late (the age), after 15 min No readings from LibreLinkUp with the Libre app as the place to look;stopped=0→ back by itself, the gap filled with the graph’s points;calls=expired→ one new login, no state shown;calls=version→ the next call names the version asked for, no Stopped;calls=terms/ratelimit/retired/down→ their words and exit on home and Settings › Source;people=none→ Pick again; the fake stopped with the network off → No internet;sensor=new→ a new sensor on the card (warm-up while it has no readings); Settings › Source and Connect say Sensor warming up · ready at … (not Nothing new), and Connect’s Continue goes on (Mac: no Reading received for the old sensor’s reading). -
LibreView maintenance (docs/45; signed in after
login=redirect, so the account’s region iseu):maintenance=1→ Settings › Source LibreView maintenance until … (clock mark, no error colour, no Try again); after 20 min home’s reason LibreView maintenance until … with Change source (and Read the sensor in Sukrara only for your glucose withpt=4and no loop or pump app installed), the card and widgets LibreView maintenance / until …, the glucose notification’s line, the no-data alert on time with No data · LibreView maintenance;until=none→ the same without a time;maintenance=0→ back by itself within 5 min.ahead=600→ Settings › Source Next maintenance · … today, …, home’s quiet line under the card (tap → Settings › Source);ahead=50→ one silent notification (LibreView maintenance at …), not again after a restart. A sign-in during it → the neutral LibreView is down for maintenance… notice. TalkBack reads the card’s maintenance. -
Settings › Source › LibreLinkUp: account, whose glucose, sensor, status with its exit (Sign in again, Try again, Pick again); Sign out is confirmed. Tidepool shows Glucose from LibreLinkUp (on).
-
LibreView beside the Libre app (FEATURES.md LibreView upload “Beside the Libre app”, docs/45), emulator and the fake only (it serves LibreView’s app API under
/lv/too and acts as LibreView does: one session per app identity, a sign-in on the Libre app’s identity stops its readings and prints!!!): the LibreView account and Share with apps › LibreView on → Beside the Libre app says FreeStyle LibreLink and log in one app only, Glucose says the Libre app sends it; log a dose → the fake printsLibreView upload as librelink: 1 entries, 0 glucoseand never alibre3sign-in (/_fakelists the sign-ins);dtid=40067→ uploads aslibre3, neverlibrelink;dtid=40069→ Paused: LibreLinkUp doesn’t say which Libre app…, nothing sent, home’s rows Waiting for LibreView…;lvother=1+lvexpire=1→ Another device sends as FreeStyle LibreLink → Take over (the dialog says the Libre app isn’t affected). Watchdog:lvmerge=1+lvexpire=1, log a dose (a new sign-in stops the fake’s readings) → after 10 min the status Stopped since … and home’s The Libre app stopped uploading (Fix → the page);stopped=0, the status row → Send again → the next dose goes up. -
The move (the owner’s phone, with the Libre app holding a running Libre 3 and LibreLinkUp as the source): Read the sensor in Sukrara → Take the sensor from the Libre app (what the Libre app loses, Open the Libre app’s info) → force-stop the Libre app → Take over → tap: the source becomes Sukrara reads your sensor by itself, the graph keeps one line through the switch (no doubles), the sensor’s start is unchanged, LibreView offers Take over. Way back: Where it comes from → LibreLinkUp, scan the sensor with the Libre app.
-
Mac with LibreLinkUp (a debug build against a fake LibreLinkUp, or
sukrara-snap windows|shellwithSUKRARA_SNAP_ONLY=setup-connect-librelinkup,settings-source-librelinkup,panel-librelinkup; never a real account on a test run): No · Read it online → whose glucose → LibreLinkUp → Sign in to LibreLinkUp: Return signs in, AutoFill offers a saved sign-in, a wrong password says so under the field (reject tap), too many attempts / no answer / no internet / stopped as a notice; several people → Whose glucose? → Choose; no one → the invite instructions, Try Again, Change Account; connected → Signed in as …, Reading Ana Example’s glucose., Reading received (tap, VoiceOver hears it) → Continue. Settings › Source › LibreLinkUp: status with its exit, Account + Change Account… (Keep This Account back), Whose glucose menu (another person with readings here asks first), Sensor, Sign Out of LibreLinkUp… confirmed. The panel: LibreLinkUp path badge; a refused password → LibreLinkUp refused the password + Sign In Again…; not signed in → Sign In…. Add Treatment writes this Mac’s own log (nothing uploaded); Spanish and VoiceOver on every step. -
One person, one link (docs/44 Appendix G,
contracts/sources/link.json; FEATURES.md Source): two emulators (wearer + follower) over the local relay, and a Mac dev run; fakes only (the local relay, the fake LibreLinkUp, a Nightscout stub). On a linked device every other source is still in the picker; picking one asks Keep following? naming the picked source (LibreLinkUp, Nightscout, Juggluco, your sensor: each reads right); Keep Following (Return / the default) changes nothing. Stop following asks only whatlink.jsonsays (settings only with Their settings that differ from the defaults; history only when something was received; Android’s person change asks the deletion with Export CSV first); Cancel changes nothing. After each transition, what’s left behind:| Transition | Sockets / Bluetooth | Stored accounts | Settings in use | Alert role | Treatment log | Wearer's list ||---|---|---|---|---|---|---|| Linked → other source → *Keep Following* | relay (and Bluetooth) open, as before | as before | as before | mirror or own, as before | the wearer's | following || Linked → other source → *Stop Following* (keep settings, keep history) | no relay socket, no Bluetooth to the phone | the new source's; the follow key gone | the wearer's values, now this device's own; *Settings from* not shown, panes editable | own engine on the new source | the new source's own log; the kept wearer entries read-only, never uploaded | told (`leave`): the device leaves the list || Linked → *Stop following* (Sukrara's defaults, delete history) | none | none for the link | the mirrored rows at their defaults | none until a source is picked | empty | told || Linked with *This device's own* → leave | none | the follow key gone | this device's own, unchanged (no settings question) | own engine | the new source's | told || Follow ended (the wearer removed the device) → other source | none (already closed) | the follow key gone after the leave questions; no *Keep following?* | as answered | own engine | the new source's | (already removed) || Android: someone else's glucose (link) → yours | none | the follow key gone | as answered | wearer (your glucose) | your log, the earlier history deleted (asked) | told || Online source → *Their Sukrara* (join) | relay (and Bluetooth) open | the online account kept, listed under *Also on this device* with *Sign out* / *Forget* | *Their settings* (default) | mirror | the wearer's | following || Updated with a live follow kept behind another source → *Keep following* | relay (and Bluetooth) open | the other source's account kept (*Also saved on this …*) | *Their settings* | mirror | the wearer's | following || Updated with a live follow kept behind another source → *Stop following* | none | the follow key gone | unchanged (the source's own) | own engine | the source's own | told || Updated with an ended follow kept behind another source | none after the start | the follow key gone, no question | unchanged (the source's own) | own engine | the source's own | (already ended) |Offline (the wearer's phone or the relay unreachable) at *Stop following*: where the person lands (Android setup'ssource step and Settings › Source; Mac under *Not following anyone* and at the top of Settings › Source) says*<name> hasn't been told yet* until the leave is delivered, then it goes by itself (bring the relay back).Also: the name, picture, path badge and blocked-feature warning of the link appear nowhere on a non-link source(card, alerts, notification, widgets, Settings); the no-data reason is the source's; rings and reports count overthe shown person's history (Mac: the kept history continues with the next source after *Keep it*); a hidden ringsays why in Settings › Metrics. TalkBack / VoiceOver read both questions and their choices; Spanish.
Q29 Website
Section titled “Q29 Website”sukrara.mauri.app (website/, website/README.md). Automated already: npm run check
(links, anchors, the apps’ URLs, App Links, the feed). Locally: cd website && npm run build && npx astro preview.
- Home, features, Android, Mac, privacy, join (
/join/#+ 32 letters, and without), sounds, developers, one report and a wrong URL (the 404), each in light and dark, at desktop width and at ~400 px: nothing scrolls sideways, every app picture matches the theme, the hero’s card and Mac panel don’t hide each other. - Spanish: the same pages under
/es/; the language menu switches both ways; with the browser in Spanish an English page shows the hint, which keeps the#sectionand whose × hides it for good. - The download buttons show the newest release’s version, size and date (a build that reached GitHub); What’s new opens it; on a phone the APK downloads and installs. The badges under it (Google Play, F-Droid / Mac App Store, Obtainium / Homebrew, GitHub) are one row of the same height and open their place; Get Obtainium / Get Homebrew sit under theirs. Homebrew’s copies the command and shows it with “Copied. Paste it into Terminal…”; pasted into Terminal, it installs Sukrara.
- Pictures arrive as JPEG XL in Chrome 155+, Firefox 158+ and Safari (DevTools › Network › Type
jxl), as AVIF in a browser without it, never WebP; no card, crown or widget is cut at its edge. - Features: every tile visible, four across on a wide window, icon beside the words at ~400 px; a tile with the picture mark opens its picture centred (Escape, × or a click outside closes it, focus back on the tile); each home section’s See all lands on its group; every tile still matches the README’s “What it does”.
- The sharing drawing: side by side on a wide window, top to bottom at ~400 px, every word inside its box; a dot leaves the phone on each route at once and the Bluetooth one arrives first.
- Sounds: a number plays with its progress ring, a second click stops it, Play a random high… plays one per pack.
- Keyboard and screen reader: the skip link, the header links, search (⌘K / Ctrl+K), every sound button says its pack, alert and number; with reduced motion the hero, the live dot and the sharing diagram stand still.
- After a deploy:
/.well-known/assetlinks.jsonand/.well-known/apple-app-site-associationanswer 200 with the files,/appcast.xmlis the feed, an invite link opens the app on a phone with Sukrara, and a page’s link pasted in a chat app shows its own preview.