Comment My solution... (Score 5, Funny) 119
#SaveWaterWithGoatse
Did someone get to claim the $5,000 bounty on that one?
Wish he'd do the same for boardview file formats. I've already reverse-engineered a few like xzz and teboview but for some reason he's now somewhat oblivious to it ( I suppose since he doesn't repair any more he's not "in the game" as such ).
That's because the schematics are basically under heavy NDA. Designing a motherboard is basically impossible without heavy help from Intel or AMD and that is provided under NDA only.
That's why boardviews are so nice - they don't reveal *anything* about the actual PCB fabrication other than position of the parts and the logical connections between the parts (ie, which pins are on the same net); they are not *design* files, likewise schematics aren't truly revealing a lot either, certainly not enough that you could implement a clone for exactly the reasons you cite, there's simply too many other things such as firmware, routing and actual timing/impedence-control of the signals that go well beyond what can be deduced from the schematic and/or boardview alone.
If you look at common boardview files for things like Macbooks, all they contain is a long list of the following data tuple
{ position, side, part#, pin#, network name }
I had hoped that Framework would be a real change in the market but we're still locked out from really repairing those boards because there's no boardview access.
Sure, you can fix some things without the schematic and/or boardview ( they're two separate things btw ), but if you really want to be able to service machines that have been damaged you do need both in this day & age.
I've approached Framework a few times and it keeps ending up with a dead end when it comes to the boardview ( even through the conduit of Louis Rossmann to assist ). Basically, the whole repairability marketing tilt is little more than skin deep; they don't even have the rights to the designs to distribute the boardviews, of which I will point out are NOT the same as design files.
@CAIMLAS very much my own sentiment. After years of replacing HTC, Samsung phones due to performance loss, breakage, or just not being supported by updates, got my hands on an iPhone ( I repair them ) to try out and was basically a convert over night. That was a bit painful in many ways as I was primarily android/*nix person, shunning microsoft/apple any way I could, yet the improvement from the change was so great I was able to overcome that mindset, at least with Apple
These days I am fine to use iPhones that are 4~5 years old and there really isn't any problem. iPhone 11's are by far the most popular currently.
Provably false in general terms. iPhone SE, 6, 6S still run just fine.
Apple's "fail" with the slow-down was their marketing side; should simply have said "If your battery is lacklustre iOS will dial back the performance to avoid instability caused by the battery not being able to comply with instaneous power demands". Makes me wonder if that feature was slipped in as a "Lets extend the life of an iPhone" by some engineers trying to be nice which probably goes against the MO of the Apple shareholders/board which would deeply frown on that as their pitch would be "Upgrade to a new iPhone".
The feature serves to extend the working life of a device, that's not cool on the quarterly profits.
Meanwhile, I moved to iPhones because places like Samsung can't help but render flagship phones to laggy crap only after 2 years with their updates. Might be better now but at the time of the change over my Samsung Note went from being a great phone to a source of frustration (I'm sure if I loaded in a different Android build that stripped out the crap that Samsung wouldn't it'd have restored performance... alas, normal people don't do that ).
I repair Apple devices, at the microscopic electronics level; I am anticipating some sort of trap in this "change of heart" out of Apple.
I like their gear but their progressive obsession with pairing everything is becoming quite problematic; it effectively nerfs a large portion of what could be done.
Thankfully at least while they can go about pairing a lot of things, there's still a good number of repairs that don't involve the paired parts.
What I'd like to see is the ability to purchase brand-specific variants of the components that are used for things like USB-C PD, or battery management, which frequently are existing products from TI/Linear/etc but with small tweaks but you cannot buy them from sources such as Farnell/Mouser/Digi.
"An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup." - H.L. Mencken