>Motorola’s use of a single QFUSE that must be blown to unlock the device, permanently voiding the warranty.
If this isn't illegal (the warranty part), it should be.
If this isn't illegal (the warranty part), it should be.
Hardware warranty shouldn't be generally affected, unless it's about parts that can fail because of software malfunction - e.g. when failsafes are defined in user-overridable software. It is fair that a hardware vendor shouldn't be responsible for user e.g. overclocking something.
Software warranty should be voided. Although I can't remember when it was the last time I saw a warranty for software, explicit or implied. Rather, I believe there's an explicit dismissal of any warranties in every single licensing agreement out there.
As an aside, LineageOS seems to have been getting gradually more buggy on my Nexus 5X. 15.1 has the two issues above, plus Bluetooth music streaming is broken and crashes the music player. I reverted to an old 14.1 ROM and everything works perfectly.
I have none of those problems with 15.1 on my nexus 5x, but I also make it a point to install the latest weekly updates and the latest vendor partition blob.
- Get latest nightly build from lineageos.org
- Get matching factory image from Google and extract vendor and radio images from it
- Install TWRP
- Do a full wipe of the phone
- Install LineageOS, vendor image and radio image
Then when an OTA update came out, I'd install it and update the vendor image manually if it complained.
What'd I miss?
Yea it's incredible how long the battery lasts on this device, compared to previous nexus devices (though I never owned a nexus 5..) I've only ever run lineageos on this thing and regularly get multiple days on a charge with light/moderate usage. I once took it on a 8 day backpacking trip where it was powered on but in airplane mode (to serve as camera and backup map), got out of the wilderness with something like 40% battery left. IMHO that really shows how much negative impact on performance google's shit has on a mobile device when it can last that long without it.
Come on. If you modify the device to work in a way it wasn’t intended (eg overclocked) you have clearly voided the warranty. This is what this is there to detect.
There were car makers voiding warranties when users replaced a tire. They gave the same arguments: Users modifying the car might do anything, so better give them no chance, as nobody could ever walk safely on the streets again.
Wiser heads prevailed, and e.g. the USA created the Magnuson-Moss Warranty Act. It is today legal to replace tires on your car. It is nevertheless illegal to make it non-street-worthy. If you stupidly damage your car while replacing a tire, you do in fact void your wararanty. If reality isn't clear enough, a judge decides. While streets might not be that safe, it is extremely rare that modified vehicles are part of the problem. The system works.
Why do we have to rediscuss all of this again? Exactly the same idea is applicable to software.
The important point is that the second of your changes is the one that voided the warranty: Replacing the tire to run in an unsafe way will void your warranty too. Modifying the ECU, on itself, doesn't do anything to the warranty.
And it is up to the manufacturer to prove your specific modification is unsafe. Claiming that some parts are inherently so complex that any change voids your warranty is legal bullshit for cars.
If I understand your argument well, it is that for cell phones the OS is so complex that any person on this planet should be declared unfit to make changes to it, except the manufacturer.
* First of all, the very audience of this site disproves this statement. Note the 'hacker' in hacker news.
* Second, I invite you to take a look to the garbage you find in most software powering our hardware. Someone going trough the effort to examine a device and create a modification is almost guaranteed to create better quality. There is something Darwinian going on here: Software mods, when they are supported for some time, give by their very existence away something of the persistent and qualified nature of their creator (otherwise they would not have been published).
* Third, the nature of software is that it is hard to create and easy to copy. Only 1 person has to create the firmware modification. The rest of us can copy it. This is exactly the reverse of the tire example and makes firmware mods a lot more easy.
UPDATE: After rereading, this post sees a bit harsh and a personal attack. So let me add that I have respect for your 2 posts. You provide a valid viewpoint in a reasonably toned, adult post. I also respond to more than can be found in your posts alone. I disagree with people downvoting you. I do however respectfully believe your viewpoint is incorrect and dangerous.
You are moving the goalposts, because we were talking about "changing the ROM", not about "changing the ROM and then doing something that will fuck the hardware up"
By the way, if you fuck up the CPU by overclocking it I guarantee they won't notice it because they will just throw the entire motherboard away. The subcontracted company that fixes your mobile (it's almost never the manufacturer) won't spend their time doing some CSI on it.
This is a lie sold to you to convince you to give up control to the manufacturers, to make a warranty a flimsy and easily discarded thing. Their products are getting lower in long term quality and reliability each year, but they don't want to take responsibility for them.
If you modify your cars engine increasing the pressure in the cylinders beyond what they are designed to handle you have voided the warranty, and wouldn’t be covered when the seals fail etc.
Your warranty covers the intended use cases. It does not cover you t do what ever you want...