Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #16201

Re: Battery save app

Show all headers | View raw

On Fri, 1/10/2025 4:59 PM, Carlos E.R. wrote:
> On 2025-01-10 21:37, sticks wrote:
>> On 1/10/2025 2:03 PM, Ralph Fox wrote:
>>> On Fri, 10 Jan 2025 08:49:34 -0600, sticks wrote:
> 
> ...
> 
>>>> Any suggestions welcomed!
>>>
>>>
>>> My HP laptop (series G5) has the HP Battery Health Manager.
>>> It is a BIOS-level option. The settings are in the BIOS.
>>> I updated it a few years ago by flashing a new BIOS.
>>>
>>> My guess is the file sp78633.exe may be for flashing the BIOS on
>>> certain HP models only.  I don't know what it might do to your
>>> wife's HP laptop.
>>>
>>> See this HP support page.  Note the words "BIOS-level" and
>>> "found in most HP business notebooks."
>>>
>>> <https://support.hp.com/gb-en/document/ish_4449597-3519507-16>
>>>
>>>      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ QUOTE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>      HP Business Notebook PCs - HP Battery Health Manager
>>>      HP Battery Health Manager is a BIOS-level setting found in most
>>>      HP business notebooks. It is designed to optimize battery health
>>>      by minimizing the notebook battery exposure to key factors, such
>>>      as high state-of-charge, which can accelerate the natural
>>>      degradation and chemical aging of the battery over time.
>>>      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ QUOTE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> I was hoping when I updated the bios it would appear, but I think the others are right and this box can't do it.  Thanks
> 
> No, you never know.
> 
> Not the same case, but my Motorola mobile phone (means Lenovo) has developed a new feature after two years of use. Since the beginning it had some "clever" battery management. If left connected to the charger all night, it would charge to 80%, stay there, and go to 100% just in time for the alarm.
> 
> Now it has changed behaviour: it charges to 80% and stays. Once every few days, it charges to 100% to maintain calibration, it says.
> 
> Of course, the control hardware was there from the start, but what they did with it changed.
> 
> And another phone from the same brand, very similar but one year younger charges to 100%.
> 
> 
> My old and small Lenovo laptop (Yoga 30011IBR) can limit the charge to about 80% with a Windows application from the manufacturer. The tool does many things, and one of them is configure the charge limit. Interestingly, if I boot to Linux the limit holds, till one day randomly it goes to 100%.
> 
> My newer laptop, Lenovo ThinkPad L14 Gen 3, has never booted Windows, but it has a generic daemon that knows how to handle the power limit. There is a generic configuration file, and works perfectly (the limit applies even if the machine is not booted). I actually bought the thing with a larger battery to compensate. I mention this because generic applications to control charge must be possible also in Windows.
> 
> 

The scheme isn't all that mysterious.

There are two parts to charging. CC and CV.

The CC (Constant Current part), charges to somewhere around 80%.

The CV (Constant Voltage part), charges the rest of the way, and
as the constant voltage is applied, the current that flows into the
battery declines with time. When the current flow is down to 3-5% or
so of the CC value, the battery is considered "full". Because the cell is held
at the high voltage (4.2V maybe), this is hard on the cell, and the
choice of "fullness" is a compromise (since each 100% charge cycle
stresses the battery a tiny bit).

Charging and using just the first phase (CC), the "end voltage" is
the CV value. The cell is only at that voltage for a short time.
If no other charging occurs (the MOSFET disconnects from the pack), then
the voltage across the cell "relaxes" as normal and heads back to 3.7V .

The charger knows, via a state machine, it has completed CC and is
entering CV. If instead, the state machine heads back to "idle" state,
the pack is now charged to 80%.

This means, to a large extent, the charge controller already has
all the ingredients for the behavior, it just needs a controllable
state path to "idle", controlled by a "only charge to 80%" bit
in a register. If the bit is set, the charging stops after CC completes.

Using Constant Current, protects the charge controller. An infinite current
would flow, if the battery was really flat and the controller was
applying a relatively high voltage. By using a Constant Current circuit,
just the desired current flows, maybe a current high enough to support
"fast charging".

The charging behavior in BEVs shares some similarities, but the
values applied are modulated by the measured conditions at the
pack (like pack temperature). Some cars, like the IONIQ 5,
they're a bit closer to a laptop curve, while some of the
Teslas have a peak at maybe 30-40% or so, and the charging
level isn't all that constant. The laptop charger on the
other hand, is generally well behaved, so the electrical settings
don't really change during CC, and later during CV.

   Paul

Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Battery save app sticks <wolverine01@charter.net> - 2025-01-10 08:49 -0600
  Re: Battery save app Andy Burns <usenet@andyburns.uk> - 2025-01-10 15:06 +0000
    Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 09:48 -0600
      Re: Battery save app "Alan K." <alan@invalid.com> - 2025-01-10 10:56 -0500
        Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 14:18 -0600
          Re: Battery save app Frank Slootweg <this@ddress.is.invalid> - 2025-01-10 20:34 +0000
            Re: Battery save app "Carlos E.R." <robin_listas@es.invalid> - 2025-01-10 23:06 +0100
              Re: Battery save app Joerg Walther <joerg.walther@magenta.de> - 2025-01-11 13:35 +0100
                Re: Battery save app "Carlos E.R." <robin_listas@es.invalid> - 2025-01-11 15:40 +0100
          Re: Battery save app Daniel70 <daniel47@eternal-september.org> - 2025-01-26 19:52 +1100
      Re: Battery save app Paul <nospam@needed.invalid> - 2025-01-10 12:21 -0500
        Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 14:35 -0600
          Re: Battery save app Daniel70 <daniel47@eternal-september.org> - 2025-01-26 20:02 +1100
            Re: Battery save app Andy Burns <usenet@andyburns.uk> - 2025-01-26 10:01 +0000
            Re: Battery save app "Carlos E.R." <robin_listas@es.invalid> - 2025-01-26 13:58 +0100
  Re: Battery save app Frank Slootweg <this@ddress.is.invalid> - 2025-01-10 16:04 +0000
    Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 14:21 -0600
  Re: Battery save app Ralph Fox <-rf-nz-@-.invalid> - 2025-01-11 09:03 +1300
    Re: Battery save app Paul <nospam@needed.invalid> - 2025-01-10 15:20 -0500
      Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 14:39 -0600
    Re: Battery save app sticks <wolverine01@charter.net> - 2025-01-10 14:37 -0600
      Re: Battery save app "Carlos E.R." <robin_listas@es.invalid> - 2025-01-10 22:59 +0100
        Re: Battery save app Paul <nospam@needed.invalid> - 2025-01-10 18:46 -0500
        Re: Battery save app "Carlos E.R." <robin_listas@es.invalid> - 2025-01-11 15:50 +0100
  Re: Battery save app Jeff Barnett <jbb@notatt.com> - 2025-01-10 22:35 -0700
    Re: Battery save app dbnnet <dbnnet@invalid.com> - 2025-01-11 14:25 +0200
      Re: Battery save app Daniel70 <daniel47@eternal-september.org> - 2025-01-28 19:50 +1100
        Re: Battery save app Paul <nospam@needed.invalid> - 2025-01-28 06:04 -0500
          Re: Battery save app Daniel70 <daniel47@eternal-september.org> - 2025-01-29 20:54 +1100
            Re: Battery save app Paul <nospam@needed.invalid> - 2025-01-29 05:54 -0500

csiph-web