Customize Your Badge. Make it weird.
Step-by-step recipes for putting your name, photos and colours on the badge, reading its sensors, and shipping your own updates. Each hack is one Markdown file in the repository, checked against the code.
oreo setup writes GITHUB_USER, DISPLAY_NAME and DISPLAY_DESIGNATION to the badge; the Badge app shows your name, title and live GitHub card.
Add your photo to the Gallery
beginnerSend a photo or a short video with the Transfer app and oreo transfer send, or oreo add; it is converted to .rz565 / .rv565 and lands in the carousel.
Point the built-in Commits app at your GitHub user: the full year, streaks and your busiest week. The brick-breaker built on it is still yours to write.
Theme the OS in your colours
beginnerEdit the palette in oreoOS/theme.py and push it with oreo push: the background, accent, cards and text of every themed screen follow.
Beam a booth code with IR Quest
intermediateSend NEC codes from one badge and watch another pick them up in IR Quest, or loop a beacon with oreo run. Receiving still has an open bug (#48).
Tilt to scroll in your app
intermediateRead the MPU-6050 through oreoWare.imu in your app's update(dt) and turn a forward or backward tilt into scrolling, next to UP / DOWN.
Ship your first app
intermediateoreo new my_app, edit src/app.py, oreo app install ./my_app: a counter on the badge in minutes.
Self-host OTA updates
advancedPoint oreoOS/ota.py at your GitHub fork and publish stable/ or beta/ releases with tools/release.py; your badge updates from them.
Spin a PCB
advancedStart from the KiCad 10 schematics in circuit/elixpo/ and docs/HARDWARE.md. The schematics are drawn; the board layout is not, yet.
Got an idea for a hack?
Propose it, then write it up as one Markdown file in docs/hacks/ and send a pull request. Once it is merged, it gets its own page here.