Home › Behind the scenes › Known issues & performance being fixed
Known issues & performance being fixed
In the interest of transparency: what I know is not yet perfect, what I have verified and what I have not. Updated 24 October 2026.
Known points
| Topic | What I observe | Status |
|---|---|---|
| Touch response | On Oppo A77 and Oppo Reno, playing one note with one finger feels slower than playing two notes with two fingers. This is a subjective hands-on observation, not measured with instruments. The native-engine test did not change the feeling, which points to a phone-level effect (touch / CPU power saving) rather than the app. | Investigating |
| Android audio latency | On the phones tested, the system does not grant the exclusive low-latency audio mode (Exclusive/MMAP): the latency floor is set by Android, not by the app. Details and numbers on the test page. | Measured |
| Other devices | I have only measured two phones (Oppo A77 and Oppo Reno). Other models may behave differently, better or worse. | To verify |
What I am doing about it
I measured before changing anything: a native audio engine (Oboe) was tried side by side with the current one. It gave no perceptible advantage on the phones tested, so I am not adopting it blindly. I keep working on touch responsiveness and engine optimisation, and I update this page as I go.
Reports and measurements from other phones are welcome: they help show where the limit really is.