#Devlog: Glove A Done!

Finally wrapped up Glove A!

I don’t think I’ve ever spent this much time continuously debugging a single part of a project before. Since yesterday, I’ve probably put in around 20 hours trying to get everything working properly.

Every time I fixed one issue, another one appeared.

It started with the flex sensors. Two of them suddenly became unresponsive and started giving completely unreliable readings. Since the whole glove depends on accurately detecting finger movements, that basically meant the gesture recognition stopped working. After a lot of testing and checking connections, I ended up replacing both sensors.

Then the DFPlayer decided to stop working.

Naturally, I assumed it was a code issue and spent way too long looking through my program trying to figure out what I had broken. Turns out the code wasn’t the problem at all. The SD card had somehow become corrupted, which meant none of the audio files could be read.

So after replacing and setting up the SD card again, the audio finally came back.

At that point I thought I was done.

I wasn’t.

The OLED display suddenly stopped working.

After even more troubleshooting, I found a wiring issue along with an address conflict that was preventing the display from communicating properly. A few rewires, some code changes, and a lot of patience later, the screen finally came back to life.

After all of that debugging, soldering, rewiring, replacing components, and questioning my life choices, I’m finally here.

Glove A is designed to help people with speech impairments communicate more easily. The glove recognizes hand gestures and converts them into pre-compiled speech.

For example, bending a specific finger can trigger a phrase like “Hello”, and the glove will immediately speak it through the onboard speaker. Different gesture combinations can be mapped to different words or sentences, allowing the user to communicate quickly without needing to type or press buttons.

I’ve attached a video showing the glove working in real time.

In the demonstration, the glove detects the gesture, processes the finger positions from the flex sensors, matches it with the corresponding phrase, and instantly plays the audio output.

This project might look simple from the outside, but getting all the sensors, audio modules, display, and processing logic to work together reliably was a much bigger challenge than I expected.

Seeing the glove finally recognize gestures and speak them out loud made all those hours of debugging worth it.

With Glove A now complete and Glove B already working, Now it’s time to focus on Visora and bring the final part of the system together.

#Devlog 3: We are DONE. 🎉

SlayOS is finally finished.

One of my favorites is the new ASCII Camera. It takes your normal webcam feed and converts it into live ASCII art using letters, numbers, and symbols like @, #, %, and more. It looks surprisingly cool and gives everything that old-school hacker terminal vibe.

I also added multiple display modes, so you can switch between different ASCII styles and effects depending on how cursed you want your camera feed to look.

Between the Apple-inspired UI, the Roulette app that can literally delete half your applications if you lose, and now a fully functional ASCII Camera, SlayyyOS has somehow become a real operating system!
Gonna Ship It Soon!

#Devlog 2: Slay-OS is getting dangerously close to being finished!

Been adding some of the final features and probably the most ridiculous one so far is the Roulette.

Here’s how it works:
You spin it, and if you lose… SlayOS randomly deletes half of its own applications. That’s it. No mercy.

If you win, absolutely nothing happens.

Is it useful? Nope.
Is it funny? Prolly.

I’ve attached some screenshots below so you can see how it looks in action.

At this point, most of the OS is done and I’m just polishing things up before release. It’s been really fun building this project from scratch and seeing it slowly turn into a real operating system.

Let me know what you think of the Roulette feature. Would you risk your apps?

Just Finished Up Building the website for you’re very-very own “TRASHPAD”

guys please tell me if this pcb will work ? the xiao is at the back side. (Im Lowkey New)

took me a while but yay!

add more tweakss ;)

i) changed the previous trash knob design
ii) made random cuts which i thought are coolll
iii) changed the fonts
iv) added the stardance logo

im gonna ship it soon!

This project started as a “quick build” and somehow turned into a full redesign loop I did not see coming.

I spent around 16 hours straight building it end to end. No breaks, just flow. Schematic → PCB → Fusion 360 enclosure. Everything was moving fast and honestly felt solid at the time.

⚡ Schematic phase

Mapped out the full switch matrix. Rows and columns looked clean on paper. Nothing felt off. This was the calm stage.

🧩 PCB design

Routed everything around the XIAO RP2040. Tight layout, all pins assigned, everything looked correct.

That’s the keyword: looked.

🖼️ Fusion 360 enclosure

Built the case, aligned the board, checked fitment. At this point I genuinely thought:
“yeah, this is a first-try success.”

It wasn’t.

💥 The moment it broke

During final checks, I realized something stupid but critical:

✔ Rows were connected
❌ Columns were NOT connected to the XIAO

At first I thought: “ok easy fix, PCB edit, done in 2 minutes.”

Then reality hit.

🚫 The real problem

No GPIO pins left on the XIAO.

Zero. Everything was already assigned.

So the “quick fix” wasn’t possible at all.

🔧 Forced redesign

Only option left was to free up pins.

That meant removing the potentiometer I had already designed into the system.

And that one change didn’t stay small:

~ PCB had to be updated again
~ Pin mapping had to be redone
~ Fusion enclosure had to be redesigned
~ Mechanical layout shifted again

What should’ve been a tiny wiring fix turned into a full system rollback.

I honestly can’t believe I’m writing this, but TrashPad is finally at the point where I can call it finished.

Today I wrapped up the OLED UI, which was one of the last things on my checklist. I spent some time cleaning up the screens, fixing spacing issues, and making everything feel consistent. It might seem like a small thing, but having a proper interface makes the whole project feel a lot more polished. It’s no longer just hardware connected together, it actually feels like a finished device.

The hardware side is now stable, the enclosure design is finished, and the PCB has reached that stage where I’m finally comfortable saying “I’m not changing this anymore.”

At this point there’s only one task left: getting everything organized. I need to clean up the code, prepare the repository, sort out the documentation, and make sure everything is ready for release.

After that, that’s it,
I’m Gonna Ship It

I honestly can’t believe I’m writing this, but TrashPad is finally at the point where I can call it finished.

Today I wrapped up the OLED UI, which was one of the last things on my checklist. I spent some time cleaning up the screens, fixing spacing issues, and making everything feel consistent. It might seem like a small thing, but having a proper interface makes the whole project feel a lot more polished. It’s no longer just hardware connected together, it actually feels like a finished device.

The hardware side is now stable, the enclosure design is finished, and the PCB has reached that stage where I’m finally comfortable saying “I’m not changing this anymore.”

At this point there’s only one task left: getting everything organized. I need to clean up the code, prepare the repository, sort out the documentation, and make sure everything is ready for release.

After that, that’s it,
I’m Gonna Ship It

This project started as a “quick build” and somehow turned into a full redesign loop I did not see coming.

I spent around 16 hours straight building it end to end. No breaks, just flow. Schematic → PCB → Fusion 360 enclosure. Everything was moving fast and honestly felt solid at the time.

⚡ Schematic phase

Mapped out the full switch matrix. Rows and columns looked clean on paper. Nothing felt off. This was the calm stage.

🧩 PCB design

Routed everything around the XIAO RP2040. Tight layout, all pins assigned, everything looked correct.

That’s the keyword: looked.

🖼️ Fusion 360 enclosure

Built the case, aligned the board, checked fitment. At this point I genuinely thought:
“yeah, this is a first-try success.”

It wasn’t.

💥 The moment it broke

During final checks, I realized something stupid but critical:

✔ Rows were connected
❌ Columns were NOT connected to the XIAO

At first I thought: “ok easy fix, PCB edit, done in 2 minutes.”

Then reality hit.

🚫 The real problem

No GPIO pins left on the XIAO.

Zero. Everything was already assigned.

So the “quick fix” wasn’t possible at all.

🔧 Forced redesign

Only option left was to free up pins.

That meant removing the potentiometer I had already designed into the system.

And that one change didn’t stay small:

~ PCB had to be updated again
~ Pin mapping had to be redone
~ Fusion enclosure had to be redesigned
~ Mechanical layout shifted again

What should’ve been a tiny wiring fix turned into a full system rollback.

Devlog: Glove B Completed

After weeks of development, testing, and debugging, I have finally completed Glove B of Gesture Link.

In the video, Glove B is working successfully and responding exactly as intended. You may notice a buzzing sound in the recording. That sound comes from the vibration motors activating to transmit Braille characters.

For this demonstration, the speech input “Hello, how are you?” was converted into Braille and sent directly to the glove. Each finger contains three vibration motors. Two fingers work together to form one Braille cell, while the other two fingers form a second Braille cell. By activating specific vibration patterns, the glove communicates Braille characters through touch, allowing information to be read without visual or audio output.

This marks a major milestone for the project, as the complete speech-to-Braille pipeline is now functioning on Glove B. The system can capture speech, process the text, convert it into Braille patterns, and deliver the output through haptic feedback in real time.

pulled an all nighter :D
worked on the VISORA code, it had some bugs took me a while to fix them. Also added a really nice UI to it.

#Devlog 1: yo gng, this is the OS that I have started developing. I have named it SlayyyOS, i tried to give it a apple inspired theme as u may see in the image.

drop ur thought about it in the comment section :)

#Devlog 1: yo gng, this is the OS that I have started developing. I have named it SlayyyOS, i tried to give it a apple inspired theme as u may see in the image.

drop ur thought about it in the comment section :)

add more tweakss ;)

i) changed the previous trash knob design
ii) made random cuts which i thought are coolll
iii) changed the fonts
iv) added the stardance logo

im gonna ship it soon!

took me a while but yay!

guys please tell me if this pcb will work ? the xiao is at the back side. (Im Lowkey New)