With a capacity of 89.5% i.e. a wear of 10.5% after only 16 cycles you may want to try a full discharge until power of, power on again after an hour and discharge. Then do a 100% to a) loosen up the battery ions and b) give the analysis tool a full range to measure.
Your graph is really vague.
It says it has Data Points for 6 hours, with a cell discharge from 95% approx to 12.6%.
So if you got 6 hours that is good. I have the same use, Firefox and screen on 7% most of the time and I’d be lucky to get 6 hours.
For details on how I worked in my early days when I had 7% wear see
If the window, not the data is six hours then you have 3 hours of use from what may be 95 to 25.
My graph is home made over repeated manual measurements using WHinfo on Windows or Power Statistics in Ubuntu 22.10 and so shows data over a long period. Most of the time I am using it with mains and am measuring battery wear a few times a day for the graph.
My graph doesn’t show Cell charge history, only Wear compared to Cycles
My Power Statistics has a more 'reasonable graph grid
@Travis If you’re running TLP on Pop OS, you’re going to be in for a bad time. It uses system76-power and it is not compatible with TLP. They may even cancel each other out. Uninstall it and reboot, try Battery Life setting from the Pop OS pull down menu on the right.
Hi @Matt_Hartley, can I confirm something here as I believe you have worked with Pop OS before. In the Battery Optimisation guides, we mask the existing power-daemons to make way for TLP. Can we not do the same for com.system76.powerdaemon.service?
I am experimenting with this myself, and setup TLP with the guide. Fully understand that I am on my own here but just looking for an answer as to whether it’s possible.
It may work, but, honestly for Pop OS, you’re going to best suited to use their power profile tool and service on Pop itself. It’s pretty deep into the distro and merely disabling the service on Pop is untested.