Porting Android 16 to my blind mother's keypad phone

A visually impaired mother’s failing Nokia 1280 was replaced with a $400 Kapsys SmartVision3, a keypad phone marketed with speech and accessibility features. But it proved slow, battery-hungry, unstable, and stuck on Android 11 with an outdated security patch. Telegram calls failed in the background, and a crashing Google app broke voice input. The writer decided to replace its software with Android 16, hoping to make the device usable without sacrificing the physical-key navigation and spoken feedback that mattered to his mother.

The attempt required discovering that Kapsys had built accessibility behavior into Android’s system library, as well as modifying the dialer, status bar, and settings - not merely adding an app. After failing to make a full backup, the writer unlocked the bootloader and flashed a generic LineageOS build. Repeated boots ended in recovery, prompting experiments with partitions, encryption, and different Android versions. Recovery logs and advice from AI models helped identify a problem: the phone rejected an unsigned boot-verification file, even with verification disabled. Signing it with Google’s test key changed the failure into a fastboot fallback, but did not make Android start. The writer then turned to MediaTek’s low-level tools to retrieve crash logs, encountering another technical obstacle. The project’s central tension is clear: modernizing the phone means reverse-engineering the very custom software that makes its keypad accessible, and the effort has not yet produced a working replacement.