Kobo Clara BW: More Capability, Less System Change
An account-free Kobo Clara BW, expanded with an app platform and alternative readers, while retaining its stock operating system. The work combined compatibility research, verified installation, recovery-minded integration, and a measured fix for landscape touch.
Project type: owner-led embedded-device customization and integration
Platform: Kobo Clara BW, physical N365B label; electronic N365 / code 391
Baseline: existing stock firmware 4.45.23655
Scope: application installation, access, launcher integration, touch-transform correction, and documented verification
Read the full engineering account · Explore all case studies
The challenge
The brief was straightforward: make the reader more useful without losing the reliable reading experience it already provided. That meant account-free setup, Cobalt applications, KOReader and Plato, selected convenience controls, and administrative access that remained usable when the touchscreen could not be trusted.
The constraints made it an engineering problem rather than a package-installation exercise. Similar Kobo product names did not establish identical hardware behavior. Published compatibility matrices described reference combinations, not every possible working installation. USB-visible storage was not a complete firmware backup. And enabling stock landscape exposed a real regression: the display rotated, but touch coordinates no longer matched it.
Success required extending the device at the smallest useful layer and checking the transitions between those layers—not replacing the system simply because replacement was possible.
Our approach
Establish the baseline before choosing a change
We identified the BW independently of the earlier Clara Colour investigation, preserved its USB-exported files on two storage devices, and checked the genuine device information against the selected Cobalt installer. The existing firmware passed the relevant checks and subsequent runtime qualification. No version spoofing, firmware migration, or custom boot image was needed.
The baseline and later snapshots gave us evidence for before-and-after comparisons. They were not presented as proof of complete eMMC recovery; boot-chain changes stayed outside this implementation.
Integrate existing projects rather than build replacements
We retained stock Kobo/Nickel and added Cobalt 0.3.31, NickelMenu 0.6.0, KOReader 2026.07.1, and Plato 0.9.45. Release verification and file readback were separate from physical launch and return checks. Account-free sideloaded mode remained enabled, and application directories were excluded from stock library scanning.
A dedicated SSH key and a reader-specific password fallback provided an independent administrative path. Access settings were checked after changes; credentials were not included in project publications.
Diagnose the landscape failure at the transform boundary
The landscape problem was addressed with the existing NickelTouchFix project, not a replacement input driver. Its targeted userspace hook corrects the touch transform in configured landscape orientations while leaving rendering and unselected orientations alone.
We qualified the released binary against the installed libraries, confirmed the live hook, and used fixed-pose corner taps followed by menu-selection and manual-return checks. Bounded non-touch recovery was available during the trials. Accidental-tap traces were preserved but excluded from clean acceptance.
Both landscape directions passed the measured checks. Native portrait and upside-down portrait also passed without additional portrait correction. The everyday menu was then reduced to just Portrait and Landscape (USB right): the tested capability remained documented without making the interface unnecessarily busy.
Treat handback and display state as part of integration
The dark-mode investigation separated a stock book-page setting from a display driver's global inversion state. The NickelMenu action was relabelled to explain its book-page-only scope. A narrowly scoped reset was installed before Plato restarts stock Kobo, following the cleanup behavior used by KOReader on this display platform.
The reset's file and protocol checks passed. The dedicated visual regression test was deferred when the owner accepted the behavior for now. That distinction remains explicit in the results.
Results and supporting evidence
| Outcome and evidence | Scope of the result |
|---|---|
| More capability with the stock OS intact. Cobalt core launch, touch, stock return, restart persistence, and repeat launch/return checks passed | Not exhaustive testing of every Cobalt app |
| Alternative readers available from the shared menu. KOReader launch/normal exit and Plato initial GUI operation with subsequent stock return observed | Not every book format or exit condition qualified |
| Account-free stock access. Owner reached the stock Books interface without registration | Optional online services may still require accounts |
| Usable selected landscape. Prescribed four-corner checks and operator menu/manual-return checks passed in both landscape directions | Direction and usability checks, not pixel calibration or swipe endurance |
| Controlled scope of system change. Vendor kernel, boot chain, and stock firmware retained | Complete boot-layer rescue was not demonstrated |
| A useful upstream contribution. Compatibility report published with selected debug lines, device/firmware context, and limits | Single-unit report, not a universal device guarantee |
The result was an account-free reader with multiple software environments, verified access, and a small set of practical controls. The project delivered that capability without turning an application-integration task into an operating-system replacement.
What this demonstrates
The value of constrained-device engineering is often in the boundaries: installer versus runtime, rendering versus input, application preferences versus driver state, and a successful launch versus a successful return.
Our contribution was to connect those boundaries, measure the behavior that mattered, preserve an independent recovery route, and distinguish completed checks from unfinished work. Credit for the application platforms and touch-fix implementation belongs to their upstream maintainers.
Long-duration battery behavior, suspend/resume, post-install USB handoff, alternate-reader launches from forced stock landscape, and complete retained-hook removal remain separate qualification work. No performance improvement, zero-brick guarantee, or broad hardware certification is claimed.
Explore the work
- Technical detail: Making a Kobo Clara BW Our Own—Without Replacing Its OS, including the firmware decision, host-installation complication, touch measurements, and dark-mode analysis.
- Another engineering case: Cog Wars website, SEO and AI visibility, a different application of measured delivery and explicit verification.
- Further reading: Engineering articles and project documentation. These are broader resources, not a claim that every documented tool was used in this Kobo project.
- Project context: All case studies.
Working on an integration where compatibility and reliable handback matter? Discuss the project with AlienMachine.