This perhaps could be of interest to You @AmpBenzScientist .
A mobile phone or perhaps a smartphone with a li-ion battery lasting up to 1 month.
https://blog.flipperzero.one/1-month-battery-life-with-firmware-update/
@PawelK Infinitime had the same problem with the PineTime and its Nordic chip.
A cell phone would be very different. What Mr. Lee is working on could actually get closer to it if the Pinephone had a low power screen and a larger battery. There is likely a problem with that hardware revision too. It has enough control to where it charged at 5V 3A without issue for me. Two microcontrollers control charging of the device.
@PawelK Pinephone uses the same battery as a Samsung J5 I believe. It's not a complicated connector.
If I remember correctly J5's batteries used to hołd charge rather nicely.
Do samsungs also use two microcontrols for charging?
After normalising USB-C, I would insist on somewhat normalising batteries and their connectors and general stuff around power consumption.
Emphasis: impossible to remove or replace a battery on that mobile? Trashed!
@PawelK The Pinephone battery is removable. The whole phone is held together with 6 screws that are the same size. The back of the phone pops off for battery and switch access.
They are doing great job here then, and could be viewed as a gold standard perhaps.
@PawelK The whole design is based off existing products and easily sourced smartphone parts. There are a lot of cool stories from those directly involved in the development of the phone. Cameras had to be reversed to get working with open source code and the A64 was the most powerful SoC with the Mali400. It was as open source as possible.
Two micro-controllers? WTF?
On low power side from my ie SW perspective, i just suspect (AS yet), java, JavaScript, and unwanted and unneeded animations on web (including via elements of CSS and SVG) suck dong, just as user-tracking and web-ads and app-ads.
Also on datalimiting, so both bandwidth and CPU, vector + text formats for many images + tinysvg-esque projects will kick ass.
@PawelK Allwinner SoCs like the A64 are paired with an X Powers AXP 803 which controls charging and power use. There's also another PMU on the Pinephone. I think the other is used for faster charging and more advanced features.
Cool, its clear now. Thank You for that.
@PawelK Using wget for the HTML and loading in the parts desired would be easy on resources.
Scrolling doesnt help here, but i would think of paged HTML view, and DLing per page more or less. Chunking division and serving effort moves to server, and displaying would mean rendering a single PDF page more or less.
Just additional q from a noob:
Is much power lost in idle-running and/or unneedily high clocking of CPUs and/or specialized subcores like 3D-GPU and/or various radios?
@PawelK That's a significant amount of power being used for each of those.
I would attempt on decoupling their clock controls, and/or adding more granularity per core visavis clocking selection and power level.
Also static display screens wouldnt need 1M refreshes per second.
@AmpBenzScientist
Propose to pinephone kind of common interface for battery, maybe? Idk, a wild guess.
About screens, 90% of what i need, can treat it roughly as Pareto, amoleds or even nobacklight passive ones would suit me perfectly.