B/D.

Lesson Nº4

Lazarus 360.

Could I bring a dead camera back? Samsung stopped caring about it years ago, and mine still worked fine.

AI loop, no sound · 12s

  • Door: Can it even be done?
  • Reverse engineering and direction of the build
  • Kotlin + Wear OS, 100% on-device
  • 2026
  • In development

The camera

I have a Samsung Gear 360 from 2016, and it never broke. Samsung removed the framework its app depended on, so modern phones just won't talk to it, and it ended up in the drawer where I keep the things I value. What got to me was the pain of an object being obsolete while still intact. Nobody was paying me to fix that. It came in through the same door as CCWEAROS, I just wanted to know if it could be done. Then I found out the camera speaks an open protocol called OSC over Wi-Fi, and after reading that spec I couldn't leave it alone.

The studio wall

scroll sideways →

  • The real Kotlin file mapping the camera's fixed IP and its three OSC endpoints

    the dead camera's address, from the source

  • Ink style sketch of a small spherical 360 camera on an orange heartbeat line that just came back to life, made with AI

    AI keyframe of the camera coming back

  • The real GLSL shader code that turns two fisheye images into one sphere

    the stitch, in GLSL, on the phone's GPU

Honest weaknesses

The crit

  1. It's for people who own one discontinued camera, and there aren't many of us.

  2. The tests are green and I've closed the holes I found, but I haven't finished checking it on the actual camera, so until the hardware agrees with the tests it stays in development.

  3. No app is going to fix the optics. The sensor is what it is, and some shots will look old no matter how good the stitch gets.

Shipped & taught

  • In development, 2026
  • Kotlin + Wear OS
  • 100% on-device, no cloud, no Samsung account

What this taught me

With the other projects, when something didn't fit I could change the plan. With this camera I couldn't, it's an old piece of hardware and it does what it does, so I ended up writing more tests here than on anything else I've built, mostly because there's no arguing with it.