fl42v

I think ppl just got pissed with the fanboys unironically asking to RIIR everything. The language itself is comfy AF, tho

A bit of an update here: I decided to do it. Basically, 1st you need to desolder the flex cable, starting with 2 positive wires and not shorting them to other stuff (I haven't tried doing it myself, but it doesn't seem like a good idea)

Then solder everything but positive, isolate, solder positives, isolate. I used hot glue since I'm in the middle of nowhere and too impatient to wait for some more appropriate stuff to be delivered.

Then install the contraption into the case which doesn't fully close now, but it's unnoticeable when plugged in into the laptop.

App pinning has an explicit warning that "personal data may be accessible" and "pinned apps may open other apps". I mean, it's better than nothing, but I'd prefer not to rely on it anyways.

Funny enough, I wasn't entirely sarcastic. I've seen some trump memes that day and suspected smth happened to him, but they were the 1st to explicitly tell it as far as I remember 😅

They've explicitly told in there FAQ 0 bytes of info was disclosed. And I suspect whatever they've shared with Germans alone wasn't 7 bits long.

Well, at least children running away on instinct is a benefit. No pets is a bit of a bummer, but hey, no pests either

Wait, haven't they already? Sry, not much into real world news

Fck, literally me. And I don't even smoke pot

Soo, how exactly CC solves the issue? I suspect it wouldn't stop those who ignored a much more lax GPL, tbh

It's not like they exactly didn't before: https://www.androidpolice.com/telegram-germany-user-data-surrendered/

Also, nothing said about whether they're going to start making transparency reports, not that I've expected anything else from this crapshow of a messenger...

I didn't build it, although I've been entertaining the idea for quite a while. I just happened to have 2 dead batteries, one 72wh with a locked controller (2 parallel cells simply fell off due to bad spot welding) that I later bricked while trying to unlock, and a 22wh with one of the packs dead. So, after fixing the welding (tbh I've just soldered those cells since I didn't have a spot welder myself at the time) I just swapped out the working controller with the locked one. T480 doesn't seem to mind, so whatever. Although I eventually decided to set the charge threshold at ~90% since it seemed to me the BMS overcharges the batteries

As for building, there's this beauty (also there's a hackaday article about it; includes a link to the blog post outlining how it was done) for t420 which seems to include a PoC-ish smbus implementation for an attiny, as we'll as a prototype based on bq3060. Verification may be a problem, tho, if the board runs on EC firmware from lenovo (also, I've been looking at coreboot docs for x230 today, and yap, they sometimes do keep blobs with EC firmware, although there were tutorials on patching it to remove the verification). Also, if you happen to have a battery based on bq8030 ic, this blogpost has a disassembler for its firmware, which makes it possible to more or less see how the battery side of verification is done and implement it some other way. Dumping the firmware is also quite simple using theese scripts (tested on the second battery mentioned in the post)

I guess so, but you should check which controller is used on your bms. This guide targets bq8030, as mentioned in the readme

Edit: also, my bad: it looks like the guide doesn't show how to change the battery capacity, so recalibration is also necessary (alternatively, you can look for the values reported by /sys/class/power_supply/BAT*/energy_full{,design} in the dumped firmware and change them. However, the script is useful if your bms locked itself (in this case replacing/shorting the fuse might also be necessary, as some bms-es try to blow it when locking)