Hi @freisatz, sorry to hear this – we were aware this might happen with older devices.
In later Android versions they’ve changed how the ‘safe-area’ is calculated. We were using an old system in the past that was outdated and was causing issues on newer devices. We’ve now fixed this, but as a consequence older devices running Android 12 and below have now reached end of life support. As much as we’d like to continue support for all systems it’s difficult for us to support both – so we recommend using the Web App on older devices.
If anyone is running Android 13 and above and you’re encountering the same issue as Robin above please let us know asap.
We’ve had one report of this on a new version of Android 16, soo good news it may be a problem with our new implementation, so hopefully we can fix for older devices as well. On our test devices & simulators the keyboard and vertical alignments work perfectly but unfortunately that’s not representative of all Android devices.
If anyone is using Supernotes on Android please let us know the behaviour of the keyboard / vertical alignments below
Thanks everyone for sharing your device specs. We’re still unable to identify a pattern and why this is occurring, on our two physical Android test devices (Samsung Galaxy A53 & Google Pixel 5 both running Android 16) and simulators running Android 12, 15 & 16 we’re unable to reproduce the issue.
We think it might be related to a build issue with the live app in the Google Play Store, and will be pushing a new update to the store today. Hopefully that will fix things, please keep us updated here or via the in-app messenger – we’d like to fix this asap.
We’ve entirely re-written the code for the safe-area and keyboard on Android. We hope this has fixed the bug for all of you (@freisatz, @intonationcop, @dlthunder) – let us know asap if not! Thanks for your patience while we resolved the issue.