marmistrz

Sounds plausible. I left the phone overnight at 63% and plugged in (but not really charging) and it remained precisely at 63%

I'm on the Nov 15 update right now, I'm connected to my display using a USB-C hub and an HDMI cable and it works much more reliably than before. I used to get random disconnections and now it works like charm.

Oh my goodness, I didn't realize I had the ACC daemon running! 😄🤦‍♂️ (the app had reported an error while finalizing installation so I thought it wasn't)

I can charge in the LOS recovery, so it's limited to chaging in LOS.

Right now I have a more serious problem: the device stops charging several minutes after a reboot. The only related thing in the logcat is: 08-29 11:49:16.367 1386 1454 I DreamManagerService: Gently waking up from dream. 08-29 11:49:16.367 1386 1419 I DreamManagerService: Performing gentle wake from dream. 08-29 11:49:15.708 0 0 W healthd : battery l=75 v=4135 t=30.0 h=2 st=3 c=429198 fc=2878000 cc=4 chg= 08-29 11:49:15.748 0 0 E i2c-msm-v2 c17a000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d

/sys/class/power_supply # cat battery/status Not charging

it's definitely done in software as it depends on the app used

I switched to the AOSP keyboard, turned off the autocapitalization. the software keyboard doesn't autocapitalize, the hardware one does (tested by writing an e-mail in k9 mail)

Thanks. My point is that while I want sticky modifiers, i don't want autocapitalization 🙂 so switching back to full doesn't do the trick

There is but it doesn't provide any autocapitalization setting

I'm using anysoftkeyboard as my virtual kbd and have autocapitalization turned off there. sentences are not autocapitalized when using the virtual kbd but the are while using the hw kbd

For me, the biggest annoyance of the Pro1 keyboard is that it's impossible to turn off autocapitalization. Some time ago I took a quick look at the sources but I didn't find the root cause. This seems to be done by the Android userspace. Did anyone find a root cause or a workaround?

I agree, PLA is completely unsuitable for printing the case. My PLA case broke after a month of usage without taking any large hits.

I can no longer notice this issue after the latest update, however, I have never let my battery discharge below 42%.

Since recently I have a problem with charging: the device doesn't charge until rebooted. More precisely, when I plug the device to a wall charger, the current used stays around 0A, as reported by BatteryBot Pro. When I reboot, I properly get 1.5A-3A of current from the charger, depending on the actual charger used (I tested using the official charger and an Anker charger)