2025-11-29.log

- switchy (QUIT: Ping timeout: 240 seconds) (~switchy@mechboards/switchy)00:00
+ paperManu (~paperManu@107.159.15.124)00:01
+ switchy (~switchy@mechboards/switchy)00:03
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@107.159.15.124)00:47
+ paperManu (~paperManu@142.169.16.211)01:09
- leony (QUIT: Quit: leony) (~leony@2a02:8109:f083:bb00::5ef2)01:11
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)01:18
- synnfynn (QUIT: Quit: WeeChat 4.5.2) (~synnfynn@user/synnfynn)01:19
- chomwitt (QUIT: Ping timeout: 246 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)02:10
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@142.169.16.211)02:26
- paperManu_ (QUIT: Ping timeout: 246 seconds) (~paperManu@107.159.15.124)03:52
- nsc (QUIT: Ping timeout: 256 seconds) (~nicolas@i5C74DDAA.versanet.de)03:55
+ nsc (~nicolas@i5C74DE46.versanet.de)03:56
+ pomel0 (~pomel0@user/pomel0)05:43
- cow321 (QUIT: Ping timeout: 260 seconds) (~deflated8@user/meow/deflated8837)06:56
+ cow321 (~deflated8@user/meow/deflated8837)07:07
joguminute: Oh sorry, I don't have a pocket. Was talking about what kxtells was mentioning they were seeing on the pocket last week07:17
+ leony (~leony@ip5f5bd792.dynamic.kabel-deutschland.de)08:20
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)09:20
- Svp (QUIT: Ping timeout: 240 seconds) (~svp@host-79-7-240-189.business.telecomitalia.it)09:48
+ Svp (~svp@2002:4f07:f0bd:0:95e7:dc62:c203:a24)09:51
+ gustav25 (~gustav@c-78-82-53-204.bbcust.telenor.se)10:02
+ XYZ_ (~XYZ@89-24-56-199.nat.epc.tmcz.cz)10:26
grimmwareminute: wrt my battery issues, I find it pretty suspect that they'll both sit at 3.7V but when I plug the pocket in one of the cells will go to like 3.8 and the other jumps straight to 4.0/4.111:00
grimmwareAll of this suggests to me either unequal drain or unequal charging11:00
grimmwareI've also been thinking about what's so different with my pocket versus someone else's and it does stand out that I've got the accelerometers installed, although I don't see any reason why these would cause uneven drain11:01
grimmwareI think (along with using firefox) explain why I was hitting the brownout condition more regularly than anyone else11:02
grimmwarebut I think the imbalanced batteries was likely a factor in that too given that one cell was more likely to undervoltage because the other cell would reach capacity sooner and prevent further charging11:02
- leony (QUIT: Quit: leony) (~leony@ip5f5bd792.dynamic.kabel-deutschland.de)11:03
grimmwarewhat's the balancing rate on the v2 charger?11:03
grimmware(again, as recap this is with the v2 charger and brand new 7000maH cells that have been through a couple of charge/discharge cycles)11:04
grimmwarehmm, I wonder if the cells both being at 3.7 is just because of the balance between them pulling both to the center...11:05
- XYZ_ (QUIT: Remote host closed the connection) (~XYZ@89-24-56-199.nat.epc.tmcz.cz)11:05
+ XYZ_ (~XYZ@89-24-56-199.nat.epc.tmcz.cz)11:06
grimmwareyeah christ currently running at 3.4V on the top cell without it being plugged in and that jumps to 4.1 when plugged in. That doesn't seem right to me :/11:21
grimmwareI don't have the stuff with me to externally balance but I bet if I do it'll be alright for another cycle and then have issues again11:21
grimmwareI'm gonna let it drain completely and then see if it can come back from 0% like people in the forum has said it does11:30
- XYZ_ (QUIT: Remote host closed the connection) (~XYZ@89-24-56-199.nat.epc.tmcz.cz)11:47
+ XYZ_ (~XYZ@89-24-56-199.nat.epc.tmcz.cz)11:48
- XYZ_ (QUIT: Remote host closed the connection) (~XYZ@89-24-56-199.nat.epc.tmcz.cz)12:01
+ XYZ_ (~XYZ@89-24-56-199.nat.epc.tmcz.cz)12:02
- lidstah (QUIT: Ping timeout: 272 seconds) (~lidstah@gateway/tor-sasl/lidstah)12:17
- jordi__ (QUIT: Ping timeout: 264 seconds) (~jordi@79.117.156.55)12:21
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)12:28
- lanodan (QUIT: Ping timeout: 256 seconds) (~lanodan@2a01:e0a:d6:9930::35)13:01
+ lanodan (~lanodan@2a01:e0a:d6:9930::35)13:03
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)13:03
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)13:13
grimmwareokay so completely drained, if I give it enough juice to turn the sysctl on and then unplug it says both cells are at 3.1V, but when I plug it in it's 3.4 and 3.6. Now it's at 1% and the top cell is 3.9 and the bottom is 3.513:31
grimmwarethat really doesn't seem right13:31
grimmwareyeah there we go, at 3% suddenly a little whine from the charger board and both cells at 3.4, no longer charging13:35
grimmwareso complete discharge made it worse13:35
grimmwareSo I guess another question I'd have here is why the sysctl doesn't request a higher charging rate when it's clearly plugged into the charger but both cells are at like, 3.4v. That's clearly not full.14:08
+ paperManu (~paperManu@107.159.15.124)14:17
grimmwarelol, yeah it can't stay on if I unplug it now, it claims to be at 4% but one of the cells drops to 3.0V once unplugged14:30
grimmwareI don't understand how/why that would be pulling up to 4.2V but the other cell not when it's actualy got more juice in it14:31
- UsrBinAnnika (QUIT: Ping timeout: 264 seconds) (~UsrBinAnn@109.255.154.246)15:06
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)15:15
+ UsrBinAnnika (~UsrBinAnn@109.255.154.246)15:20
- lanodan (QUIT: Quit: WeeChat 4.5.2) (~lanodan@2a01:e0a:d6:9930::35)15:53
+ lanodan (~lanodan@2a01:e0a:d6:9930::35)15:53
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)16:16
lidstahhomelab upgraded to proxmox 9.1: [x] done :) (and hello everyone!)16:17
lidstahtime to test this new OCI support in proxmox :)16:18
chgrimmware: when the batts are completely empty on startup, the sysctl enters an emergency charge mode. there it does not attempt PD. its meant to get to enough power so at a later point it could try PD, but this part is not implemented16:50
+ leony (~leony@ip5f5bf6c9.dynamic.kabel-deutschland.de)16:53
+ erle (~erle@user/erle)16:54
amospallagrimmware: did you mention you are using a remapper? If it is the case you use kanata, mleds has ability to set colors based on the kanata active layer.17:44
- cow321 (QUIT: Ping timeout: 264 seconds) (~deflated8@user/meow/deflated8837)18:32
+ cow321 (~deflated8@user/meow/deflated8837)19:13
+ paperManu_ (~paperManu@107.159.15.124)19:27
+ colinsane (~colinunin@97-113-95-185.tukw.qwest.net)19:56
- leony (QUIT: Quit: leony) (~leony@ip5f5bf6c9.dynamic.kabel-deutschland.de)20:01
+ leony (~leony@ip5f5bf6c9.dynamic.kabel-deutschland.de)22:06
- gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-53-204.bbcust.telenor.se)22:15
- leony (QUIT: Quit: leony) (~leony@ip5f5bf6c9.dynamic.kabel-deutschland.de)22:21
- plomlompom (QUIT: Remote host closed the connection) (~plom@139.59.138.73)23:13
+ plomlompom (~plom@139.59.138.73)23:13

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!