shipped / October 9, 2026

An AI agent on a Nokia 110: the calculator app is now a chatbot that can phone people

score RAM: 48MB

Anup Ray bought a Nokia 110 4G to cut his screen time. Then he reverse-engineered its firmware, turned the Calculator app into a chat window, and wired it to an agent that answers questions over SIM data, checks the battery, flips the torch, starts calls and sets alarms. In 48MB of RAM, with Codex helping.

Built by Anup Ray with OpenAI Codex.

cfirmwarereverse engineeringnokiafeature phoneembeddedcodexdeepseektool callsagenthardware

What it is

A Nokia 110 4G with an AI agent in it. You open what used to be the Calculator, type on the number pad, and the agent answers over the phone's SIM data. Ask it to and it will check the battery percentage, turn the torch on or off, start a phone call or set an alarm. The demo video is 48MB of phone doing things 48MB of phone was not supposed to do.

The origin story is the best part. In his Show HN: "I was using this mobile to reduce my screentime. Recently got the idea to put ai agent in it."

How it was built

Anup Ray first tried the obvious thing. "Started with installing android, but failed as it has only 48MB RAM." So he reverse-engineered the firmware instead, "for few days." It is written in C, he told the thread, unlike the Java of earlier Nokias, so custom changes are possible. They just get erased on restart.

His README lays it out in five phases. Phase 1 was a workaround: an AI search option bolted onto Opera Mini. Phase 2 was getting his own code running at all. With no supported way to install anything, he loads custom code into RAM through the Calculator's entry point. The first proof was a tiny C app that printed "PDP" on keypresses. Phase 3 was a real answer over SIM data, which meant tracing firmware callbacks until a response reached the app with the USB cable unplugged. Phase 4 made the chat usable, swapping the calculator layout for a text input; a colour change kept rebooting the phone until he found he was writing the wrong style field. Phase 5 turned chat into actions. "As the phone memory is only 48MB, normal agent code wont fit," so he wrote a minimal custom agent, shrank the builds, compressed the payloads and reused buffers.

The loop itself is plain: "It sends your message to DeepSeek chat API and use tool calls accordingly." And the coding help: "I used OpenAI Codex to help build it and tested the app on the handset."

Status, in his words: "It's a working prototype loaded into RAM from a computer." Once loaded it runs unplugged on mobile data. Power it off and it needs loading again. "Permanent installation is still unresolved." The source is not published yet, because "sensitive data is scattered across the project."

Why we picked it

Because he bought the one phone that cannot run an app and then taught it to run an agent. The screen-time plan did not survive contact with the idea, and we respect that.

And because the constraint is the whole story. No install path, no room for a normal agent, every feature tested one at a time on the handset. As one commenter put it, finding a Nokia 110 is the hard part.


Shipped is Accept All's daily pick of things people build with AI, written by MK. We are not affiliated with Anup Ray; the work and the credit are theirs, so go tell them it's good. Newer: bigarrow: a macOS CLI that lets your agent draw a big arrow at the button you need to click. Older: City 2026: a low-poly SimCity 2000 clone, decompiled and rebuilt by Opus 5.5 in a browser tab.