Sheet 04 · All applications
Support
Questions, problems and suggestions all reach the person who wrote the code. There is no ticket system and no support tier.
Please say which application or extension you are using, and which Android, Windows or browser version. For KB525C Control, bug reports and pull requests are also welcome on GitHub.
TiltFlow — fault finding
Symptoms are listed with the checks in the order worth making.
F-01
Tilting does not scroll anything
- The accessibility service is enabled, and shows as connected inside TiltFlow.
- The application you are in has been ticked in the list.
- The Tilt scrolling switch at the top is on.
If the phone is lying flat, sideways tilt cannot be measured at all. Hold it more upright, as you would to read.
F-02
An application is missing from the list
Applications appear once you have opened them at least once with TiltFlow's service running. This is deliberate: it means TiltFlow does not need permission to see every application installed on your phone. Open the application, then return to TiltFlow and it will be there.
F-03
The page scrolls while I am just holding the phone
Raise Tilt needed to start scrolling in the Sensitivity section; it ships at 12.0°. Re-calibrating the neutral position while holding the phone the way you actually read is usually the better fix, because every angle is measured from that position.
F-04
My e-book reader turns too many pages at once
For readers that turn pages sideways, such as Kindle, enable both Turn pages sideways and One swipe per tilt for that application. One tilt then turns exactly one page, however long you hold it.
F-05
An application ignores TiltFlow completely
Some applications (certain games, and readers with copy protection) ignore simulated swipe gestures. These cannot be scrolled by TiltFlow, and there is no setting that will change that. A report naming the application is still useful.
F-06
How do I stop TiltFlow?
Leave the application: TiltFlow stops as soon as a non-ticked application is in front. You can also turn off the Tilt scrolling switch, or disable the service entirely in Android's Accessibility settings.
KB525C Control — fault finding
The two commands that answer most questions: kb525c status and
kb525c log 80. Tray menu → Log shows the same, live.
K-01
The tray icon is grey and a balloon says the command channel is busy
Dell Peripheral Manager's service, DPMService, is running and holds
the keyboard exclusively. The install script disables it; if it came back after a
Dell update, run Set-Service DPMService -StartupType Disabled; Stop-Service
DPMService as administrator, then tray menu → Reconnect.
K-02
"Keyboard not detected"
Plug the KB525C in directly if it hangs off a hub that was asleep, then Reconnect. A different Dell keyboard is reported with its product id and is not driven; only the KB525C is supported.
K-03
In a meeting, the Mic button mutes Windows but the meeting app does not follow
Shortcuts only reach the window in front. Bring the meeting window forward; the operating-system mute happens regardless, and the LED shows it. If the app's shortcut has changed, fix it on the Meeting apps settings page — no rebuild needed. Google Meet has no screen-share shortcut at all.
K-04
The buttons act as if a meeting were on, but there is none
A meeting is "something is using the microphone". A browser tab or a voice-typing
tool holding the microphone keeps the meeting layer active; kb525c status
says whether the microphone is in use. Close the offender, or switch the mode to
Always or MeetingsOnly if the detection does not fit your setup.
K-05
A command-line tool started from a button has no colours
A console program started directly gets a plain console host without Windows
Terminal's environment. Start it through the terminal instead: program
wt.exe, arguments -d . claude (or whatever the tool is).
K-06
Claude Code hooks do not blink
Hooks are read when a Claude Code session starts, so restart it after editing
settings.json. Test the signal on its own first:
kb525c signal bounce --sticky — if that says the app is not running,
start the tray app; if it says the pattern is unknown, define bounce
on the Signals settings page. Keep the || true at the end of
the hook command.
Reporting something
Compatibility reports are the most useful thing to send, especially for applications that ignore simulated swipes — that list can only be built from real phones. Feedback and suggestions are equally welcome, and so is a rating on the Google Play listing.
TiltFlow is independently developed, which means there is one person reading this address. Replies are not instant, but they are from someone who can actually change the code.