I've been using the newly-arrived PBP, usually plugged in. In some sessions, the charge indicator drops below 100%, but still says it's charging. If that's true, it suggests that the wall-wart is unable to charge the machine at the rate it uses power. (Modest use, nothing dramatic.)
Is this a software problem, a failing unit, or is it an indication that a more puissant charger might be a good idea?
This is a known issue, and it's not the wall wart's fault. The charge controller in the PBP is apparently inadequate for what the PBP can do under full load. Without modifying the hardware, the best solution is to throttle the CPUs and/or dim the display. There are threads here with more details.
Also note that the development team enabled over-clocking of the CPUs. This of course gives better performance. But, it appears that the external power circuit was not designed for the extra power load. So the extra power comes from the batteries when higher loading of the CPUs is used.
--
Arwen Evenstar
Princess of Rivendale
(09-27-2020, 06:38 PM)Der Geist der Maschine Wrote: (09-27-2020, 04:47 PM)Arwen Wrote: Also note that the development team enabled over-clocking of the CPUs. This of course gives better performance. But, it appears that the external power circuit was not designed for the extra power load. So the extra power comes from the batteries when higher loading of the CPUs is used.
The small cores are not overclocked. The big ones are overclocked by 0.2GHz. I doubt that matters. That's just one of the many imperfections of the Pinebook Pro.
I don't know that I want to, so no big deal... but is there a way to un-overclock the CPUs? Is there are writeups concerning this issue? I can search here but .... it gets a little hard to find things.
I think that a lot of these issues would be good to port over to the wiki, a sub-wiki, or a different 'power users' 'extras' or similar section of the wiki... theres many things that could use extra discussion and information.

Especially for us newbies.
-----
pAULIE42o
. . . . . . . .
/s