• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle



  • If there was an option that was presented to users once the device got below 80% battery health to slow down the system to make daily batter life longer

    This isn’t why they did it. Degraded Li-ion batteries cannot sustain their rated voltage at high currents due to increased internal resistance. Sufficiently undervolted CPUs/memory cells produce errors (specifically bit flips), which can rather quickly lead to memory corruption and a crash.

    Reducing the CPU frequency (thereby reducing the peak current draw) is practically necessary in the face of a degraded battery. Various laptops were infamous for not doing this, because it resulted in a ~20-30 minute battery life, as the voltage drop became too great once the battery charge drops below 80-90%. Within the context of a smartphone, neglecting to use the remaining 80-90% would make it basically useless.

    What Apple (and the rest of the smartphone industry, at this point) really needs to do is make their batteries replaceable.









  • Of course the Lemmy devs aren’t liable for GDPR violations; the admins are. That doesn’t eliminate the problem, though: if the Lemmy devs wish to see their software used as it is now in the long term, they need to introduce GDPR compliance tools. We should consider it gravely concerning that bad actors (e.g., a Reddit employee) can set up Lemmy admins for a massive GDPR suit at any moment.

    Edit:

    if the people complaining are so concerned, why do they not contribute the code to fix their perceived issues?

    I know it’s a stereotype around here, but not everybody on Lemmy is a programmer with free time.