@oausi @iFixit I took most of the old adhesive off. There's a light tackiness that is still holding the cover on, but it's not a very solid hold. I have it in a case so it's not a huge deal, but the batteries came with little strips of double sided tape that I'll try once I've done more battery tests to make sure it's good. I'd like the cover to be easy to remove in the future so I don't want to use too strong of glue.

@isola @cayeric I have #postmarketOS installed on my Nexus 5, it does work but it's pretty limited on what all it can do. The GPU isn't fully supported, there is no audio, no camera. It lags pretty bad. Firefox crashes. Unfortunately, the MSM8974 chip it uses it pretty old these days and while it has a fair amount of support, it is by no means complete. If you want to get started, go ahead and install, but otherwise I recommend picking up a OnePlus 6/6T for the best experience.

@davidoclubb @iFixit I just got it on eBay.

Success! I've installed a new battery in my #OnePlus 6 running #postmarketOS. Old battery capacity reported around 0.5Ah, new battery out of the box reports 2.96Ah and was around 50% charged, so letting it charge up now. Used a hair dryer to weaken the adhesive and @iFixit suction cup and picks to get the back off. After removing the back, swapping the battery is quite simple.

@crft I believe there are known issues with replacement touchscreens but I can't find it on the pmos wiki.

@crft Does your OnePlus 6 have an aftermarket replacement screen? I have both the 6 and 6T and both have working touchscreen.

(technically) it's making HTTP calls to a little tiny python shim service which is in turn making OpenRGB calls, but:

This way it's platform agnostic :P :P

Wrote a tiny little patch for #VoidCrew tonight that lets it make #OpenRGB calls after a fashion.

Now the ship lighting is integrated with case lighting! Need to implement effects, but it's something.

https://neon.cybre.stream/w/6nbFgdjjUkigHNBLhEmKjr

@cas After watching it pretty closely through several discharge/recharge cycles, I don't think overcharging is a concern (it caps out at 4.40V and I think you would experience issues in daily use) but overdischarging may be an issue. It seems that the battery will continue to power the phone below 0% if you let it, and the voltage reading will happily drop below 3.20V (below 3.10V even) before the hardware cuts off power. I don't think I saw it drop below 3.00V at least but this seems too low.

OP6T hit 0% after 59 minutes of the same test, also pulling around 5W continuously.

OP6 hit 0% after 42 minutes running stress-ng --cpu 8. It did not shut off, but I went ahead and plugged it back in. It was pulling ~5W for the duration of the run.

Does anyone familiar with sdm845 Linux know why the smb2_get_iio_chan() function in drivers/power/supply/qcom_pmi8998_charger.c checks if mode is not CHARGING and returns zero? I think it would be nice to see energy usage (voltage, current, calculating power) from the USB port even if the battery is at 100%. I've noticed as soon as the battery stops charging then these values stop being shown in Powersupply.

#postmarketOS #sdm845

After 3 discharge/recharge cycles, the OP6T is at 1.26Ah estimated full capacity and the OP6 is at 0.83Ah.

To make it easier to do complete discharge cycles for battery calibration, you can disable auto-shutdown when the battery capacity drops to zero by editing /etc/UPower/UPower.conf. At the very bottom, edit "CriticalPowerAction=Ignore" and then above that line add "AllowRiskyCriticalPowerAction=true". This is supposed to completely ignore it, but the phone still shows a notification saying it will hibernate, but it never does. Not sure if this Ignore is actually working or if just an ARM bug.

Also, at this point I'm just curious how the battery calibration works and if multiple charge/full discharge cycles will make it more accurate. I'm pretty confident the batteries on both phones are well below 50% of their original capacity and I have new batteries on the way.

For some reason on the 6T (left) it reaches 100% capacity but 1W is still going into the battery (power out of the battery is negative, power into the battery is positive). Full charge capacity dropped from ~1.4Ah down to 1.2 but it is now slowly creeping up. It says Discharging but it's still putting power into the battery. Meanwhile, the 6 (right) fully shut off and I am now recharging it.

I've submitted a merge request for the Powersupply changes shown here, though I want to do some cleanup before it's ready to merge.

https://gitlab.com/MartijnBraam/powersupply/-/merge_requests/10

Trying to calibrate my OnePlus 6 and 6T batteries on #postmarketOS. I noticed my OP6T has had worse and worse battery life lately and my "new" OP6 has even worse. Added charge monitoring display to the Powersupply app and have been doing charge/discharge cycles. The phones go from 100 down to 0 and pmOS shuts down, but if I power back on a few times the power tracking resets to 100% and continues running a while longer. Doing compile jobs pulls ~6W which makes for a decent discharge load.

We are looking into moving our Mastodon account to another instance within the next week or so.

@MagillaGorilla4Sale USB role switching isn't working yet on 6/6T so probably not. There is a dtb modification you can do to force it to always use host mode rather than device mode which might work. Dongles usually contain a USB DAC so they work like any other USB device. The dongle that comes with it may be a passive dongle though and not require host mode.