Sometimes when charging my reform, it will - seemingly at random - decide that actually, 22% is a fine number to stop charging at, and the amperage flow will drop from -1.5A to about -0.4 (if in use) to -0.1A (and despite this, it will not actually charge). The batteries are maxed out at 3.5 and 3.4V right now, and will go no higher.
Often this is fixed, oddly enough, by flipping the USB-C upside down, or cycling the system’s power using the hardware switch, which makes me think this is either a firmware or hardware issue, but right now it’s not being fixed by either of those methods, which has me a bit concerned.
Still looking for advice on this, the issue has persisted through multiple discharge cycles. I’m under the impression that the issue may be with the battery board - should I order a new one and, if so, how?
@zeha might know a thing or two about charging the pocket reform.
Remember also that (independent of whether or not somebody here can provide help) you always have the option of writing to support@mntre.com when you have issues.
the wall plug resetting the USB-PD connection after some time, maybe now that its happening also declining the initial PDO selection
the charging IC detecting some kind of error.
Both should theoretically be visible in the sysctl debug logs on /dev/ttyACM0. Try running minicom and pointing it to that “serial port” to see what the sysctl firmware has to say.
Running minicom doesn’t seem to flag up any errors between charging working as intended or not, aside from the fact that the voltage repeatedly shows up as exactly “19.900000” once the charging has stopped, where it tends to be more sporadic before then.
I haven’t been able to try a different wall plug as yet, nothing I have outputs the necessary wattage - I’ll run down to microcenter or somesuch and see if I can’t test that.
(Update): Using a different charger yielded the same results, charging stopped abruptly after a few moments. Any tips on debugging the charging IC?
Hi there, I expirienced something similar with my new pocket. The first time it loaded to 80% and stopped and i unplugged it. at 20% i had a hard shutdown going to reboot. i put it back on power and had a hard shutdown going to reboot at around 80%. Those Numbers looked to me like a battery-saver function going crazy.
Now… i’m not sure, as some days have gone by and i fiddled around - i think Upower was there by default…
Anyway - i found a post from josh mentioning editing /etc/UPower/UPower.conf and changing following options to remove safety belts, which he described very nicely:
For me it did the trick. since then, there were no unexpected reboots.
What I also expirienced after that: the battery or sensor-values seemed somewhat uncalibrated. i powered it up to 100% and let it run dry - the last 1% did last very long. now it seems the battery values are ok and the runtime is now around 3 - 4 h, with a full-load voltage of around 4.1 V.
I’m running the rk3588 with preinstalled debian and sway btw. and i don’t need powersaving functions at the moment.