What Really Goes Wrong With Your Tablet

We’ve all seen our share of consumer electronic devices that need repair. It’s inevitable that, however well-cared-for it will be, there’s always the unforseen that brings its life to an end. Many of us will be using devices we’ve repaired ourselves, because often other people’s useless broken electronics can be our free stuff when we know how to fix them and they don’t. This is the arena the Restart Project operate in, as through their Restart Parties they provide repair services to save unnecessary landfill. Over nearly a decade in operation they’ve fixed a huge number of faulty items, and now they’re releasing some data and have analysed common fault modes and barriers to repair for some categories.

We’re restricted to tablets, printers, and batteries, and while many of the problems  are the wear-and-tear such as tablet screens, power supplies, charging connectors, and paper feeds that most of us would expect, it’s the barriers to repair which the Restart Project are keen to draw attention to. Products that are near-impossible to open without damage, parts such as batteries which are difficult to remove, and unavailability of spares. It’s to become part of their campaigning for legal repairability standards across Europe.

Aside from their own analysis, the full data is all available for download should you have any extra insights. We’ve made our position on this matter very clear indeed.

Oh Deere, Is That Right To Repair Resolution Troubling You?

Over the years a constant in stories covering the right to repair has come from an unexpected direction, the farming community. Their John Deer tractors, a stalwart of North American agriculture, have become difficult to repair due to their parts using DRM restricting their use to authorised Deere agents. We’ve covered farmers using dubious software tools to do the job themselves, we’ve seen more than one legal challenge, and it’s reported that the price of a used Deere has suffered as farmers abandon their allegiance to newer green and yellow machines. Now comes news of a new front in the battle, as a socially responsible investment company has the tractor giant scrambling to block their shareholder motion on the matter.

Deere have not been slow in their fight-back against the threat of right-to-repair legislation and their becoming its unwilling poster-child, with CTO Jahmy Hindman going on record stating that 98% of repairs to Deere machinery can be done by the farmer themself (PDF, page 5) without need for a Deere agent. The question posed by supporters of the shareholder action is that given the substantial risk to investors of attracting a right-to-repair backlash, why would they run such a risk for the only 2% of repairs that remain? We’d be interested to know how Deere arrived at that figure, because given the relatively trivial nature of some of the examples we’ve seen it sounds far-fetched.

It’s beyond a doubt that Deere makes high-quality agricultural machinery that many farmers, including at least one Hackaday scribe, have used to raise a whole heap of crops. The kind of generational brand loyalty they have among their customers simply can’t be bought by clever marketing, it’s been built up over a century and a half. As spectators to its willful unpicking through this misguided use of their repair operation we hope that something like this shareholder move has the desired effect of bringing it to a close. After all, it won’t simply be of benefit to those who wish to repair their tractor, it might just rescue their now-damaged brand before it’s too late.

Curious about previous coverage on this ongoing story? This article from last year will give context.

Header image: Nheyob / CC BY-SA 4.0

Vizio In Hot Water Over Smart TV GPL Violations

As most anyone in this community knows, there’s an excellent chance that any consumer product on the market that’s advertised as “smart” these days probably has some form of Linux running under the hood. We’re also keenly aware that getting companies to hold up their end of the bargain when it comes to using Linux and other GPL licensed software in their products, namely releasing their modified source, isn’t always as cut and dried as it should be.

Occasionally these non-compliant companies will get somebody so aggravated that they actually try to do something about it, which is where smart TV manufacturer Vizio currently finds itself. The Software Freedom Conservancy (SFC) recently announced they’re taking the Irvine, California based company to court over their repeated failures to meet the requirements of the GPL while developing their Linux-powered SmartCast TV firmware. In addition to the Linux kernel, the SFC also claims Vizio is using modified versions of various other GPL and LGPL protected works, such as U-Boot, bash, gawk, tar, glibc, and ffmpeg.

According to the SFC press release, the group isn’t looking for any monetary damages. They simply want Vizio to do what’s required of them as per the GPL and release the SmartCast source code, which they hope will allow for the development of an OpenWrt-like replacement firmware for older Vizio smart TVs. This is particularly important as older models will often stop receiving updates, and in many cases, will no longer be able to access all of the services they were advertised as being able to support. Clearly the SFC wants this case to be looked at as part of the larger Right to Repair debate, and given the terrible firmware we’ve seen some of these smart TVs ship with, we’re inclined to agree.

Now of course, we’ve seen cases like this pop up in the past. But what makes this one unique is that the SFC isn’t representing one of the developers who’s software has been found to be part of Vizio’s SmartCast, they’re actually the plaintiff. By taking the position of a consumer who has purchased a Vizio product that included GPL software, the SFC is considered a third-party beneficiary, and they are merely asking the court to be given what’s due to them under the terms of the license.

As firm believers in the open source movement, we have zero tolerance for license violators. Vizio isn’t some wide-eyed teen, randomly copying code they found from GitHub without understanding the implications. This is a multi-billion dollar company that absolutely should know better, and we’ll be happy to see them twist in the wind a bit before they’re ultimately forced to play by the rules.

Who Owns The Machine Anyway?

The story of the McDonalds’ frozen treat machine involves technology, trade secrets, inside business dealings, franchiser/franchisee friction, and an alleged NDA violation. In short: lots of money and lawyers. But it also involves something that matters to all of us hackers — what it means to own a machine.

Sad clown holding melted ice cream coneThe brief background is that McDonald’s requires its franchisees to buy a particular Taylor Soft Serve machine. The machine would enter pasteurizing mode and has opaque error codes that are triggered apparently without the owners or operators understanding, at which point Taylor service techs come in to fix them — and get paid for their service, naturally. A small hardware startup, Kytch, stepped into the mess with a device that man-in-the-middles the Taylor machine’s status codes, allowing the machine’s owners to diagnose and monitor it themselves. Heroes, right?

Taylor, naturally, wants to look at a Kytch device, but they’re locked up under NDAs that Kytch require users to sign in order to protect their trade secrets. So when Taylor gets their hands on one, Kytch takes them to court for, ironically, reverse engineering their device that they built to reverse Taylor’s protocols.

There are no good guys in this fight: it’s corporate secrecy fighting corporate secrets. None of which, by the way, is Hackaday particularly fond of. Why? Because these secrets rob the ostensible owners of the devices of their ability to inspect, fix, and operate their machines. This is akin to the “right to repair” idea, but it’s somehow even more fundamental — the right to know what your own devices are doing.

What this story needs is a Robin Hood. And as the devices we get sold become increasingly wrapped up in EULAs and NDAs, and full of secret sauce that’s out of our control, we’re going to need a lot more Robin Hoods. It’s McDonald’s frozen treat machines, but it’s also your smart thermostat and your inkjet printer and your — you name it. Have at it, Hackaday!

Robot Utopia

We see so many dystopian visions of automation, it’s time for us to do it right! The Redefine Robots round of the 2021 Hackaday Prize just started, and it’s your chance to build robots that respect the users. It doesn’t have to be the largest project in the world, but it does have to be automatic and helpful. Start your engines!

School Surplus Laptop BIOS Hacked To Remove Hardware Restrictions

Why did [Hales] end up hacking the BIOS on a 10 year old laptop left over from an Australian education program? When your BIOS starts telling you you’re not allowed to use a particular type of hardware, you don’t have much of a choice.

Originally [Hales] planned on purchasing a used Lenovo X260 to replace his dying laptop, but his plans were wrecked. A pandemic-induced surge in demand that even the used laptop market caused prices to bloat. The need for a small and affordable laptop with a built in Ethernet port led to the purchase of a Lenovo Thinkpad x131e. Although the laptop was older than he liked, [Hales] was determined to make it work. Little did he know the right-to-repair journey he was about to embark on.

Problems first arose when the Broadcom WiFi adapter stopped working reliably. He replaced it, but the coaxial antenna cable was found to be damaged. Even after replacing the damaged cabling, the WiFi adapter was still operating very poorly. Recalling past problems with fickle Broadcom WiFi adapters, it was decided that an Intel mPCIe WiFi adapter would take its place. When power was re-applied, [Hales] was shocked to find the following message:

Unauthorized network card is plugged in – Power off and remove the miniPCI network card

And this is where things got interesting. With off the shelf SOIC8 clips and a CH340 programmer, [Hales] dumped the BIOS from the laptop’s flash chip to another computer and started hacking away. After countless hours of researching, prodding, hacking, and reverse engineering, the laptop was useful once again with the new Intel WiFi adapter. His site documents in great detail how he was able to reverse engineer the BIOS over the course of several days.

But that’s not all! [Hales] was also able to modify the hardware so that his slightly more modern mPCIe WiFi adapter would come back on after the computer had been put in Hibernation. It’s an elegant hack, and be sure to check [Hales’] site to get the full details. And at the end, there’s a nice Easter egg for anybody who’s ever wanted to make their laptop boot up with their own logo.

We applaud [Hales] for his fine efforts to keep working equipment out of the landfill. We’ve covered many hacks that had similar goals in the past. Do you have a hack you’d like to share? Submit it via the Tips Line.

Sad clown holding melted ice cream cone

Freezing Out Ice Cream Machine Competition

We always knew that McDonald’s soft serve (you can’t really call it ice cream) machines are known to be finicky. There’s even a website that tracks where the machines are broken and, apparently, it is usually about 10% or more of them at any given time. But when we saw a news article about a judge issuing a restraining order, we knew there must be more to the story. Turns out, these $18,000 soft serve machines are in the heart of something we are very interested in: when do you own your own technology?

Cold Tech

There are apparently 13,000 or so of these machines and they are supposedly high-tech marvels, able to produce soft serve and milkshakes at the same time. However, they are also high maintenance. Cleaning the machine every two weeks (try not to think about that) involves a complete teardown. Worse, if anything breaks, you need a factory-authorized service person.

Continue reading “Freezing Out Ice Cream Machine Competition”

Should You Be Able To Repair It? We Think So.

You own it, you should be able to fix it. So much equipment on sale today has either been designed to be impossible to maintain, unnecessarily too complex to maintain, maintainable only with specialist tooling only available to authorised service agents, or with no repair parts availability. It’s a hot-button issue in an age when sustainability is a global concern, so legislators and regulators worldwide now finally have it in their sights after years of inaction and it’s become a buzzword. But what exactly is the right to repair, and what do we want it to be?

Is It Designed For Repair?

A Nestle Dolce Gusto machine
For some reason, pod coffee makers are especially resistant to repair. Andy1982, CC BY 3.0

The first question to consider is this: does it matter whether or not you have the right to repair something, if it’s designed specifically with lack of repairability in mind? Consider a typical domestic pod coffeemaker such as a Tassimo or similar: despite being physically quite a simple device, it is designed to be especially complex to dismantle and reassemble. You just can’t get into it when something goes wrong.

Should it be the preserve of regulators to require design for easy repair? We think so. There are other forces working on the designers of home appliances; design-for-manufacture considerations and exterior appearance concerns directly affect the firm’s bottom line, while the end users’ repair experience is often at the bottom of the list, even though the benefit at a national level is obvious. That’s what laws are for.
Continue reading “Should You Be Able To Repair It? We Think So.”