Power Wheels Gets Real With Real Wheels

We’re no stranger to Power Wheels modifications, from relatively simple restorations to complete rebuilds which retain little more than the original plastic body. These plastic vehicles have the benefit of nostalgia to keep the adults interested, and naturally kids will never get tired of their own little car or truck to tear around the neighborhood in. Many toys come and go, but we don’t expect Power Wheel projects to disappear from our tip line anytime soon.

Today’s project starts with a straightforward Power Wheels restoration story: [myromes] picked up a well-worn Jeep and decided that it needed a fresh coat of paint and some tweaks before handing the keys over to the next generation. But in an interesting spin, he decided to try mounting proper pneumatic tires on it in hopes they might imbue the pint-sized Jeep with some of the abilities of its full scale inspiration. But as it turned out, the project wasn’t quite the Sunday drive he was hoping for.

For one thing, the new wheels were much thicker than the old ones. This meant cutting away some of the plastic where they mounted so he could get the shafts to slide all the way through. At 5/16″, the original Power Wheels shafts were also thinner than what the axle the wheels were designed for. Luckily, [myromes] found that a small piece of 1/2″ PEX water pipe made a perfect bushing. Then it was just a matter of buying new push nuts to lock them in place.

That got the front wheels on, but that was the easy part. The rears had to interface with the Jeep’s motors somehow. To that end, he cut out circles of plywood and used an equal amount of Gorilla Glue and intense pressure to bond them to the new wheels. He then drilled four holes in them which lined up with the original motor mounts so he could bolt them on.

Things were going pretty well until he tried to replace the Jeep’s rear axle with a length of threaded rod from the hardware store. It wasn’t nearly strong enough, and sagged considerably after just a few test rides. He eventually had to place it with a correctly sized piece of cold rolled steel rod to keep the car from bottoming out.

While the new wheels certainly perform better than the original hard-plastic ones, there’s a bit of a downside to this particular modification. The slippy plastic wheels were something of a physical safety to keep the motors and gearboxes from getting beat up to bad; with wheels that have actual grip, the Jeep’s stock gears are probably not long for this world. But [myromes] says he’s got plans for future upgrades to the powertrain, so hopefully the issue will be resolved before the little ones need a tow back home.

For more tales from the Power Wheels garage, you might want to take a look at this fantastic rebuild complete with digital speedometer or just head straight to the big leagues with some seriously upgraded rides.

GoPro Factory Goes Nomad To Dodge Tariff Threat

Despite the fact that the United States and China are currently in the middle of a 90-day “cease fire” in their ongoing trade war, with new tariffs on hold until March 2019 while the two countries try to reach agreement, not everyone is waiting around to see who comes out on top. In a recent press release, action camera manufacturer GoPro has announced their intention to move some production out of China in the face of potential tariff expansions; which many analysts fear will be the result of the current stalemate. That’s right, only some of their production is moving.

“We’re proactively addressing tariff concerns by moving most of our US-bound camera production out of China,” says GoPro CFO Brian McGee. “We believe this diversified approach to production can benefit our business regardless of tariff implications.” Reading his words carefully, the key phrase here is “diversified approach”. GoPro doesn’t intend to move their entire production capability out of China, but only the production of the cameras which are designated for importation into the United States. GoPro models which are to be sold to other parts of the world will still be made in China.

This might seem an extravagant move just to avoid US tariffs, but with better than 40% of GoPro’s revenue for the third quarter of 2018 coming from the Americas, the company stands to be hit hard by the proposed 25% tax. Combined with the fact they shuttered their drone division last year citing “an extremely competitive aerial market”, and the proliferation of “GoPro clones” available for pennies on the dollar, it seems pretty clear that belt-tightening is the name of the game for the company that was once synonymous with action cameras.

Continue reading “GoPro Factory Goes Nomad To Dodge Tariff Threat”

Does Library Bloat Make Your Smartphone App Look Fat?

While earlier smartphones seemed to manage well enough with individual applications that only weighed in at a few megabytes, a perusal of the modern smartphone software store uncovers some positively monstrous file sizes. The fact that we’ve become accustomed to mobile applications requiring 100+ MB downloads on what’s often a metered Internet connection in only a few short years is pretty crazy if you stop to think about it.

Seeing reports that the Nest app for iOS tipped the scales at nearly 250 MB, [Alexandre Colucci] decided to investigate. On his blog he not only documents the process of taking the application apart piece by piece to find out just what’s eating up all that space, but lists some potential fixes which could shave a bit off the top. Even if you aren’t planning a spelunking expedition into your pocket supercomputer’s particular variant of the Netflix app, the methodology and tools he uses here are fascinating in their own right and might be something worth adding to your software bag of tricks.

By passing the application’s files through a disk usage visualizer called GrandPerspective, [Alexandre] immediately identified some rather large blocks of content. The bundled Apple Watch version of the app takes up 23 MB, video and audio used to walk the user through the device setup weigh in at 22 MB, and localization files for various languages consumes a surprising 33 MB. But the biggest single contributor to the application’s heft is the assorted libraries and frameworks which total up to an incredible 67 MB.

Of course the question is, how much of it is really necessary? It’s hard to be sure from an outsider’s perspective, but [Alexandre] notes that a few of the libraries used seem to be redundant or obsolete. In some cases this could be the result of old code still lurking in the project, but the four different libraries used for user tracking probably aren’t in there by accident. It also stands to reason that the instructional videos could be offloaded to something like YouTube, so that only users who need to view them have to expend their bandwidth on it.

Getting a little deeper into things, [Alexandre] notes that some of the localization images appear to be redundant. As a specific example, he points to the images of the Nest itself displaying Fahrenheit and Celsius temperatures. While logically this should only be two image files, there are actually eight copies of the Celsius image, each filed away as language-specific. These redundant localization images could easily be stripped out, but with gains measured in only a few hundred kilobytes, it probably wasn’t considered worth the effort during development.

In the end there’s really not as much bloat as we might like to believe. There were some redundant files, maybe a few questionable library inclusions, and the Apple Watch version of the app could surely be separated out. All together, it might get you a savings of 30 – 40%, but still not enough to bring it down under 100 MB.

All signs point to the fact that modern smartphone software development is just a lot more burdensome than us hackers might like. Save for projects looking to put control back into the hand’s of the users, it looks like mobile operating systems aren’t going to be slimming down anytime soon.

Arduino One Pixel Camera Sees All (Eventually)

Taking pictures in the 21st century is incredibly easy. So easy in fact that most people don’t even own a dedicated camera; from smartphones to door bells there are cameras built into nearly electronic device we own. So in this era of ubiquitous photography, you might think that a very slow and extremely low resolution camera wouldn’t be of interest. Under normal circumstances that’s probably true, but this single pixel camera built by [Tucker Shannon] is anything but normal.

Continue reading “Arduino One Pixel Camera Sees All (Eventually)”

Welcome To The Slow Death Of Satellite TV In America

During an earnings call on November 29th, CEO of AT&T Communications John Donovan effectively signed the death warrant for satellite television in the United States. Just three years after spending $67 billion purchasing the nations’s largest satellite TV provider, DirecTV, he made a comment which left little doubt about the telecom giant’s plan for the service’s roughly 20 million subscribers: “We’ve launched our last satellite.

The news might come as a surprise if you’re a DirecTV customer, but the writing has been on the wall for years. When the deal that brought DirectTV into the AT&T family was inked, they didn’t hide the fact that the actual satellite content delivery infrastructure was the least of their concerns. What they really wanted was the installed userbase of millions of subscribers, as well as the lucrative content deals that DirecTV had already made. The plan was always to ween DirecTV customers off of their satellite dishes, the only question was how long it would take and ultimately what technology they would end up using.

Now that John Donovan has made it clear their fleet of satellites won’t be getting refreshed going forward, the clock has officially started ticking. It won’t happen this year, or even the year after that. But eventually each one of the satellites currently beaming DirecTV’s content down to Earth will cease to function, and with each silent bird, satellite television (at least in the United States) will inch closer to becoming history.

Continue reading “Welcome To The Slow Death Of Satellite TV In America”

AI Bot Plays Castlevania So You Don’t Have To

We’re not allowed to have TV here in the Hackaday Wonder Bunker, but occasionally we’ll pool together the bandwidth credits they pay us in and gather ’round the old 3.5 inch TFT LCD to watch whatever Netflix assures us is 93% to our liking. That’s how we found out they’ve made a show based on, of all things, one of the Castlevania games for the NES. We wanted to play the game to understand the backstory, but since it hails from the era of gaming where primitive graphics had to be supplemented with soul-crushing difficulty, we didn’t get very far.

But thanks to a very impressive project developed by [Michael Birken] maybe we’ll have it all figured out by the time we’ve saved enough credits to watch Season 2 (no spoilers, please). The software, which he’s quick to point out is not an example of machine learning, is an attempt to condense his personal knowledge of how to play Castlevania into a plugin for the Nintaco NES emulator. The end result is CastlevaniaBot, which is capable of playing through the original Castlevania from start to finish without human intervention. You can even stop and start it at will, so it can play through the parts you don’t want to do yourself.

[Michael] started this project with a simple premise: if he could make a bot successfully navigate the many levels of Dracula’s castle, then getting it to kill a few monsters along the way should be easy enough. Accordingly, he spent a lot of time perfecting the path-finding for CastlevaniaBot, which included manually playing through the entire game in order to get an accurate map of the background images. These images were then analyzed to identify things like walls and stairs, so the bot would know where it could and couldn’t move protagonist Simon Belmont. No matter what the bot is doing during the game it always considers where it is and where it needs to be going, as there’s a time limit for each stage to contend with. Continue reading “AI Bot Plays Castlevania So You Don’t Have To”

Maze Generator Keeps Plotter (and Kids) Busy

We can tell that [Jon Howell] is our kind of guy. After updating his vintage 1985 Hewlett-Packard plotter with WiFi and the ability to load SVG files, he obviously needed to find a bunch of stuff to run off with it. Gotta justify those hacks somehow. So he doubled down and decided support a hack with another hack by writing a maze generator to keep his plotter well fed. He was kind enough to unleash his creation on an unsuspecting Internet as an open source project, and now we all can benefit from a couple of reams worth of mazes.

The generator itself is written in Java, and should work on whatever operating system your box happens to be running thanks to the *nix and Windows wrapper scripts [Jon] provides. To create a basic maze, one simply needs to provide the script with the desired dimensions and the paper size. You can define the type of paper with either standard sizes (such as --paper a4) or in the case of a plotter with explicit dimensions (--paper 36x48in).

If you aren’t a big fan of right angles, there’s support for changing the internal geometry of the maze to use a hexagonal or triangle grid. You can even pass the program a black and white PNG “mask” which it will use as the boundaries for the maze itself, allowing for personalized puzzles of whatever shape catches your fancy. [Jon] even ran the Wrencher though his software, leading to the creation of a maze which we can neither confirm nor deny will be making an appearance on our Christmas cards this year.

Whether you need to prove to your significant other that the hours you spent fiddling with your plotter are well spent, or an easy way to entertain the junior humans in your life, you can thank [Jon] for your solution.