VTech Toy Becomes PinkPad, The DIY Linux Laptop

Originally envisioned as a simple DIY laptop project, [kati]’s PinkPad V1 ended up being considerably more involved than expected. But the end result is a perfectly usable, stunningly pink, and remarkably sturdy portable laptop that looks nothing like a hack job.

Originally a VTech toy, the PinkPad is a perfectly functional DIY laptop.

The PinkPad V1 started as a toy laptop for toddlers, repurposed into a DIY laptop running Linux while keeping the original clamshell design and cute aesthetic. As [kati] herself points out, while it may not seem particularly difficult to yank out a toy’s insides and stuff it with a Raspberry Pi, most of the real challenges were related to actually getting all the necessary parts and connectors and wiring to actually fit in a useful way. As anyone with experience in building something knows, working around existing enclosures or hardware almost always brings unexpected challenges.

The original toy laptop? Produced by none other than VTech, whose products have been hacked to create things like a punch card-reading cyberdeck and Z80 hacking station. Our own [Tom Nardi] has also shared his fondness for these devices in several teardowns over the years.

In the end, [kati]’s PinkPad ended up sporting a mini keyboard (whose black keys were turned pink with a little nail polish) and a 5 inch touchscreen LCD. Combined with a rechargeable power supply, it provides all the comforts of an Arch Linux ARM mini laptop.

Thanks [alex] for the tip!

Build The CPU, Then Build The Calculator

It’s possible that among Hackaday readers are the largest community of people who have designed their own CPU in the world. We have featured many here, but it’s possible that not so many of them have gone on to power an everyday project. Step forward [Baltazar Studios] then, with a scientific calculator sporting a self-designed CPU on an FPGA.

The calculator itself is nice enough, with a smart 3D printed case, an OLED display which almost evokes a VFD, and very well made buttons. But it’s the CPU which is of most interest, because while it follows a conventional Harvard architecture with a 12-bit instruction set, it works with 4-bit nibbles. This choice follows one used by HP in their calculator designs, seemingly because it can be optimised for the binary coded decimal which the calculator uses.

With calculators being yet another app on our spartphones or comnputers, there seems to be less use of calculators outside of education in 2026. But if you are a calculator user there’s nothing like a calculator you made yourself, and with a CPU of your own design it has few equals. We like this project almost as much as we like the Flapulator!

The Truth About The Hindenburg

The Hindenburg disaster recently marked its 89th anniversary, and [The History Guy] marked the event with a video that dispels many of the myths surrounding the airship. Example: the disaster did not actually occur on the airship’s maiden voyage. That isn’t true. The ship was on its 63rd voyage. However, it was the first flight of the 1937 season.

The giant ship burned because of the hydrogen gas inside, but the cause of the fire remains debatable and was likely not solely due to hydrogen. In fact, from a technical standpoint, the ship didn’t explode. It only burned.

Some of the myths are just from sloppy reporting or the tendency of people to misunderstand things. Others are a blurring in the common consciousness of the Hindenburg and the Titanic.

It is easy to think of the necessity for safe engineering when you are building, say, a bomb or a spacecraft. But anything capable of wreaking havoc requires careful design and testing. However, ships like the Hindenburg had made many trips without incident. Sure, the Hindenburg was a spectacle, but even the fatality rate was fairly low. Many of those who died jumped to the ground — they might have survived if they had waited a minute.

There are many myths around [Herb Morrison]’s famous “Oh the humanity!” report. We’ve noted before that it was played back at the wrong speed for decades. Airships have a stranger history than you might imagine.

Continue reading “The Truth About The Hindenburg”

The Dark Side Of Unitree Robot Dogs

Arbitrary command execution with the Wi-Fi password. (Credit: Benn Jordan)
Arbitrary command execution with the Wi-Fi password. (Credit: Benn Jordan)

Continuing on his quest to expose the dark underbelly of modern technology, [Benn Jordan] recently did a deep-dive into the rise of so-called robot dogs. Although their most striking resemblance with biological dogs is that they also have four legs and generally follow commands, [Benn] found many issues with them that range from safety issues due to limited sensory capabilities, to basic security vulnerabilities, all the way to suspicious network traffic from Unitree’s robot dog firmware.

Although not the only seller of this type of quadruped robot, Unitree Robotics has made a name for itself by offering very capable and yet very cheap products. Their basic quadruped robot costs only a few thousand clams and features Lidar and heaps of processing power, all of which should make it a pretty useful device.

Despite this, [Benn] found that the original task that he’d envisioned for the robot, as in protecting his chickens from uninvited visitors, wouldn’t quite work as the robot is rather blind. The reason for this is the placement of the Lidar below the head, which obscures most of what’s behind and around the robot. Rather than risk trampled chickens and chicks, this plan was thus abandoned.

When digging further into the robot, he found an easy to exploit arbitrary command execution flaw via the Wi-Fi password entry field, a year-old CVE-2025-2894 exploit, as well as highly suspicious traffic to Chinese servers whenever the robot’s software figured that it was not being watched.

Although much of this can be circumvented with hacks, issues like the sensory limitations and general distrust of firmware updates makes using these robots a rather daunting and often ill-advised proposition.

Continue reading “The Dark Side Of Unitree Robot Dogs”

Trying To Fix A GoPro Hero 10 With A No Camera Input Issue

In the search for more exciting broken electronics to repair, [Hugh Jeffreys] bought a GoPro Hero 10 for US$100 with an apparently rather common issue of no camera input, along with a cracked display. This particular camera issue is rather obvious, with just darkness where the camera’s input should appear on the display. Since [Hugh] already needed a spare display, he figured that he might as well get an even more broken GoPro Hero 10 for parts.

Another US$40 later, [Hugh] found himself the proud owner of a second GoPro, this one being water damaged and no longer turning on. Getting to the internals requires removing the glued-in display, which is even trickier than with a smartphone. By inserting a thin blade, adding solvents and not prying, you can slowly work it loose.

With two disassembled GoPros it was now possible to swap modules. After a factory reset and firmware update had failed to fix the first GoPro, the camera module from the donor unit was inserted, but this made no difference. Amusingly, after cleaning the water-damaged unit’s PCBs, it was found to be in good working condition, so ultimately the second GoPro was repaired, leaving the ‘no camera input’ issue undiagnosed.

It’s possible that a board-level repair on the first unit can address the original issue, but without schematics this would likely entail a lot of blindly poking around, in the hope of finding a damaged MLCC or other obvious fault. There is also the possibility that this is a firmware issue, with some reporting luck mashing the record button, but others disagree.

Since [Hugh] did do the firmware reset and updating steps, and even inserted a whole new working camera module, it would seem to narrow the problem down to a board-level issue. Whatever the case may be, it’s a frustrating issue with a rather expensive device.

Continue reading “Trying To Fix A GoPro Hero 10 With A No Camera Input Issue”

CRTs Are Too Mainstream, So Game On A Mechanical TV Instead

Aside from nostalgia, people claim to like CRTs because they’re apprehendable– the technology just makes more sense than the arcane wibbly-wobbly solid-state madness going on inside the driver chip of your new OLED. CRTs weren’t the first technology used to display moving images though, and their mechanical forebears were even easier to understand. For that reason we suppose it was only a matter of time before one of The Youths– in this case a British YouTuber by the name of [smill]–tried gaming on a mechanical television display.

The game in question was Minecraft— because of course it was, that’s the new generation’s DOOM–and the mechanical TV in question is not a priceless 1920s antique but a commercial kit that reproduces [John Logie Baird]s 1925 televisor. If you’re not familiar, it uses a flat disk– called a Nipkow disk after its inventor– with a series of holes in a spiral to demodulate a single lamp’s brightness variations into monochrome image made of scan-lines. As you might imagine, the resolution depends both on the size of the disk and its speed, so with a tabletop example you’re not going to get much– in this case, 32 holes for 32 lines. At least they’re not interlaced this time.

Getting a video signal from the computer to the LED in the televisor kit was the hard part of the hack. Aside from actually playing on the diminutive monochrome display, that is. There is a “video2NBTV” tool that can do the job, as the Narrow Band TV signal used by amateur radio enthusiasts still has the compatible timing values and modulation as what the televisor kit uses. We suspect that’s because the Televisor people used the modern NBTV standard as a starting point for their electronics, since [Baird]’s device reportedly ran 30 lines at only 5 frames per second, compared to the 32 lines at 15 FPS here.

Some of you may turn your nose up at this as a mere YouTube stunt, which is fair enough. At the same time, we cannot wait for the eventual arms race. Imagine when someone decides to go for 4K cred? Staring through a supersonic Nipkow disk makes pointing a particle accelerator at your face downright mundane. The kit [smill] used was monochrome, but if you want to repeat his antics in glorious colour, you can 3D print your own TV.

Continue reading “CRTs Are Too Mainstream, So Game On A Mechanical TV Instead”

A Cyberdeck That Runs Linux…in An Altoids Tin

In the time Hackaday has been in existence we must have brought you plenty of projects housed in Altoids tins, as well as a sizeable number of cyberdecks. But until today with [Exercising Ingenuity]’s build, we’ve never brought you a project that combines the two. It’s a fully functional computer that runs Linux, and with its Altoids tin enclosure, looks for all the world like a miniature clamshell laptop.

Hardware wise it’s a Pi Zero with a UPS PHAT and an SPI display, but perhaps it’s arguably the home-made keyboard that really sets it apart. There’s a full-size USB port as well, and a selection of GPIOs are broken out to a header. It wasn’t all plain sailing though, the Altoids hinges needed modifying to make it close, and he driver for the SPI screen required an older version of Raspberry Pi OS. We will forgive it those foibles.

It’s fair to say we’ve not seen anything quite like this, in that there have been plenty of tiny laptops but never one as integrated as this. There’s a demo video with details of the build, that we’ve placed below.

Continue reading “A Cyberdeck That Runs Linux…in An Altoids Tin”