# PixelBoard: Pixel-style Gboard features on non-Pixel Android phones > PixelBoard is a rebuilt Gboard for arm64 Android devices that carries the Gemini Rambler voice dictation, the in-line AI writing assistant and modern spell checker chips usually limited to Pixel hardware. It installs as its own package beside the stock keyboard, and the features are patched into Gboard at the bytecode level. **Akshayykadam/PixelBoard** — Unlock Google 11's Gemini "Rambler" Natural Voice Dictation & AI Writing Tools on ANY Android phone. No root required. - Repository: https://github.com/Akshayykadam/PixelBoard - Stars: 1,455 · Forks: 64 - Language: Java - License: GPL-3.0 - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/akshayykadam-pixelboard ## What PixelBoard is and what it is not PixelBoard is a modified build of the Google keyboard, released as an installable APK rather than as a source tree you compile. Its purpose is to move keyboard features that Google restricts to Pixel hardware, in particular the Gemini Rambler natural voice dictation and the Writing Tools V2 suite, onto any supported Android phone. The project presents itself as a productivity-focused enhancement that removes bloat, and its feature list mixes the new AI features with more ordinary items such as a Material 3 rounded key theme, an emoji palette, a scan text camera mode and clipboard history sync on Samsung and Vivo devices. Two design choices matter more than the feature list. The package carries its own application id, com.akshaykadam.pixelboard, so it installs beside the factory keyboard rather than replacing it, and the whole thing runs without root. ## Three ways to get it onto a phone Each release ships two assets and points at a third. The ready-to-install option is a signed APK, about 127 MB, published on the release page and installed directly, which is the path the README recommends for a first-time user. The second asset is a Morphe patch bundle, a file with the .mpp extension that is handed to Morphe Manager to patch a base APK you already have. That route needs the third piece, an unmodified official Gboard v18.4.1 downloaded from APKMirror, which the release notes list as required only when patching manually. So the choice is between convenience and provenance: the signed APK is already patched, while the bundle lets you apply the patches to a base application you fetched yourself. The latest release pair at the time of writing is v18.4.1-Stable-V7 with patch bundle v1.2.0, and the two assets are fetched from the release page: ```bash https://github.com/Akshayykadam/PixelBoard/releases/download/v18.4.1-Stable-V7/PixelBoard-18.4.1-V7.apk https://github.com/Akshayykadam/PixelBoard/releases/download/v18.4.1-Stable-V7/patches-1.2.0.mpp ``` The first link is the signed installable build, the second is the patch bundle for Morphe Manager. ## How the Rambler dictation is hooked into Gboard Voice typing is where the engineering detail sits. Traditional dictation transcribes hesitation literally, so the patch enables a server-side model that filters filler words such as um, ah and you know, repairs self-corrections, applies punctuation and capitalisation from context, and mixes languages inside one sentence. Getting that model active outside Pixel hardware is the hard part, and the README describes how it is done: the feature is hooked into the obfuscated VoiceSettingsFragment selector of Gboard 18.4.1, and a preference is initialised directly, with enable_jetson set to true, so the feature works on the standalone package without waiting for the Play Services phenotype flag sync. The project also fixes two lifecycle problems, releasing the GoogleAsrService speech recognition binding as soon as the keyboard is hidden to stop screen-off battery drain, and storing its state in Device-Protected Storage so voice typing is ready after a reboot without a manual keyboard restart. ## The AI writing assistant and the spell checker patches The writing assistant appears above the keys in any application and offers a one-tap proofread, a rephrase with a tone switch between Professional, Casual, Concise and Emotive, and a context aware quick edit. The patch work here is defensive rather than additive, because Gboard's suggestion-span handling changed on Android 16, so the patch adds null-safety handling around that expansion. The spell checker work is the opposite kind of job. Rather than adding a feature, the patch performs a bytecode level transformation on Gboard's spell checker utility class, hooking the obfuscated methods rcq.m and rcq.o, to force the modern inline suggestion chips and the add-to-dictionary interface on every device running Android 12 or later, since the stock behaviour depends on hardware gating. The grammar and suggestion strip is initialised automatically rather than left to the user. ## The rest of the feature surface Around the AI features sits a long tail of smaller changes that the README lists explicitly: a scan text camera OCR mode, floating suggestions on screenshots, Material 3 Expressive rounded keys, an emoji palette v2, a super insert quick hub, a restored emoji size slider, and clipboard history sync on Samsung and Vivo devices. The activation story is the last item and the one worth understanding. Rather than requiring the user to restart the keyboard after an update, the build advertises automatic zero-restart instant activation, which is a distribution convenience as much as a technical one. None of this is unique to the AI features, and for a user who does not want them it is the reason to keep the stock keyboard, since the stock Gboard is one install away and updates through Google rather than through a patch bundle. ## Where a bytecode patch becomes fragile The approach has a structural weakness that no amount of polish removes. The patch targets obfuscated class and method names inside the Google application, and those names change whenever Google ships a new build, so each patch is valid only for the exact base version it was written against, here Gboard 18.4.1. When Google pushes an update, the mod has to be rebuilt and re-released, which is visible in the release history, where three tags landed on 2026-10-15, 2026-10-17 and 2026-10-18 and the patch counter moved from v1.0.9 to v1.1.0 to v1.2.0 in the same week. The device matrix is narrow as well, arm64 only, Android 10 through 16, and the APK is large. A feature that depends on a server-side model also still depends on Google deciding to serve that model to your device, and the Phenotype workaround in the patch is an engineering answer to a policy that can change. ## PixelBoard next to the stock keyboard The alternatives split into two groups. The first is keeping the official Gboard and waiting, which means accepting that the newest voice and writing features arrive when Google decides to release them to your hardware, and on a non-Pixel device that may be never for some of them. The second is switching to a different keyboard application that ships its own AI features through its own account, which avoids the patching and the version lock but changes the keyboard wholesale, including the suggestion model, the privacy position and the theme. PixelBoard occupies the narrow space in between: the stock Google keyboard, with the Pixel-only features, on a device Google did not intend to grant them. The trade is maintenance. The upstream project can release quickly, but you take on the side effect that a Google update can leave you on an older patch until a new one appears. ## Build tooling, release notes and the licence The repository is more than a binary dump, although the release artefacts are its main output. A build.sh script sits at the root next to the README and the release notes, and the tree carries options.json, patches-list.json and patches-bundle.json as the configuration that describes the patch set, with the patch sources under patches/ and pixelboard-patches/ and helper scripts under tools/. Documentation and screenshots live in docs/, and a .github/ directory holds the workflow definitions. The project is released under the GPL-3.0, with a LICENSE file in the root, and the release tag names pair an application version with a patch version, which is how a user can tell that the v18.4.1-Stable-V7 build carries patch v1.2.0 rather than an earlier fix. The last push was on 2026-10-18, the same day as the newest release. ## Conclusion PixelBoard fits an owner of a non-Pixel arm64 Android phone on Android 10 to 16 who wants the Pixel keyboard features and is willing to replace the stock app with a patched build that is version locked to Gboard 18.4.1. It does not fit a device that receives Gboard updates through a Play Store channel you care about, or anyone who needs a supported keyboard with a vendor behind it. Before installing, check that the patched APK corresponds to the Gboard version on your device, read RELEASE_NOTES.md for the patch level you are getting, and confirm the licensing position of the Google base application separately from the GPL-3.0 terms of this repository. ## FAQ ### Does PixelBoard require root access on Android? No. The signed APK installs as its own package, com.akshaykadam.pixelboard, beside the factory Gboard, and the project states that root is not required. ### Which devices and Android versions does PixelBoard support? The badges and the release notes give Android 10 to 16 with arm64-v8a architecture, and the build is based on Gboard v18.4.1. ### What is the Morphe patch bundle in the release assets? It is a standalone .mpp patch file for Morphe Manager that lets you patch your own base APK. Patching manually also requires an unmodified official Gboard v18.4.1, which is not bundled. ### What does the Gemini Rambler voice typing add to dictation? It filters filler words and stutters in real time, repairs self-corrections, adds context aware punctuation and capitalisation, and allows languages to be mixed inside a sentence. ### Which licence is PixelBoard released under? The GPL-3.0, with a LICENSE file at the repository root. The terms covering the Google base application it is built from are a separate matter from this licence. ### How often does PixelBoard publish updates? Very often at the moment. Three release tags landed on 2026-10-15, 2026-10-17 and 2026-10-18, with the patch counter moving from v1.0.9 to v1.1.0 to v1.2.0, and RELEASE_NOTES.md records the changes. ## Sources - [Akshayykadam/PixelBoard on GitHub](https://github.com/Akshayykadam/PixelBoard) - [Issues](https://github.com/Akshayykadam/PixelBoard/issues) - [License: GPL-3.0](https://github.com/Akshayykadam/PixelBoard/blob/main/LICENSE) - [README](https://github.com/Akshayykadam/PixelBoard/blob/main/README.md) - [Releases](https://github.com/Akshayykadam/PixelBoard/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/akshayykadam-pixelboard