On Mon, 17 Mar 2025 at 14:31, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > > Hi, > > On 17-Mar-25 13:38, Antheas Kapenekakis wrote: > > On Mon, 17 Mar 2025 at 13:27, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > >> > >> Hi Antheas, > >> > >> On 11-Mar-25 17:53, Antheas Kapenekakis wrote: > >>> OneXPlayer devices have a charge bypass > >> > >> The term "charge bypass" is typically used for the case where the > >> external charger gets directly connected to the battery cells, > >> bypassing the charge-IC inside the device, in making > >> the external charger directly responsible for battery/charge > >> management. > >> > >> Yet you name the feature inhibit charge, so I guess it simply > >> disables charging of the battery rather then doing an actual > >> chaerger-IC bypass ? > >> > >> Assuming I have this correct, please stop using the term > >> charge-bypass as that has a specific (different) meaning. > > > > Unfortunately, this is how the feature is called in Windows. On both > > OneXPlayer and Ayaneo. Manufacturers are centralizing around that > > term. > > Ok, so I just did a quick duckduckgo for this and it looks like > you are right. > > > Under the hood, it should be bypassing the charger circuitry, but it > > is not obvious during use. > > Ack reading up on this it seems the idea is not to connect the external > charger directly to the battery to allow fast-charging without > the charge-IC inside the device adding heat, which is the traditional > bypass mode. > > Instead the whole battery + charging-IC are cut out of the circuit > (so bypassed) and the charger is now directly powering the device > without the battery acting as a buffer if the power-draw superseeds > what the external charger can deliver. > > > The user behavior mirrors `inhibit-charge`, > > as the battery just stops charging, so the endpoint is appropriate. > > Hmm this new bypass mode indeed does seem to mirror inhibit charge > from a user pov, but it does more. It reminds me of the battery disconnect > option which some charge-ICs have which just puts the battery FET in > high impedance mode effectively disconnecting the battery. Now that > feature is intended for long term storage of devices with a builtin > battery and it typically also immediately powers off the device ... > > Still I wonder if it would make sense to add a new "disconnect" > charge_behaviour or charge_types enum value for this ? > The battery is not disconnected. It still provides backup. Unplugging the charger does not turn off the device. So it is more murky.
