Google releases Glass kernel GPL source, lets developers have at it
While our own Tim Stevens is currently adapting to life through Google Glass, developers are going beyond scratching the surface to fiddle with what's inside. Hot on the heels of Jay Freeman rooting Glass …
Context & Ripple Effects
Google publishing the GPL-licensed kernel source lands two days after Jay Freeman confirmed he had rooted Glass, converting what was reverse-engineering into sanctioned access to the device's internals. The move follows a spring of developer experimentation on the Explorer Edition, including Duke University's March demo of a Glass app that recognizes people by what they wear.
The story traveled unusually wide for a kernel drop — CNET, Android Authority, Ubergizmo, Phone Arena and others all picked it up — reflecting how much attention the Explorer hardware is drawing while the official development tooling remains limited to the Mirror API.
First-order effects
- Developers working from Freeman's root now have the actual kernel code to inspect and modify, replacing guesswork about how Glass's Android base is put together.
- Google satisfies its GPL obligations for a shipping consumer device, putting Glass's low-level internals on the same footing as other Android-derived hardware.
Second-order effects
- Custom kernels and system-level mods become feasible before any official SDK covers them, letting the enthusiast community surface capabilities Google has not exposed through the Mirror API.
- Security researchers gain a legitimate baseline for auditing the device, raising the odds that vulnerabilities get found and disclosed publicly rather than traded privately.
Third-order effects
- If Google keeps releasing kernel sources for each hardware revision, Glass develops a parallel open-source track alongside its controlled app ecosystem — a governance split between what the kernel permits and what the SDK allows.
- The pattern sets an expectation for the wearable category: hardware shipped to early adopters arrives with inspectable internals, making community modification part of the platform's development cycle rather than an exception to it.
The trend: Wearable hardware is opening from the bottom up — kernel source and rooting communities filling the gap left by deliberately narrow official SDKs.