FW16 USB PD Battery Issues

Community Support
,
59

Hi together,
I’ve got the same powerbank (Anker 737 powerbank PowerCore 24K) and the same problem as described in the first post. I’ve investigated this topic a little bit and would like to share my findings with you.

The problem is related to the specific powerbank + specific types of cables.

I’ve tested multiple variants:

  1. Anker powerbank (USB PD 3.1; 140 W) + PD 3.0 cable (E-Marker saying 20V, 5A max; <=100 W)
  2. Anker powerbank (USB PD 3.1; 140 W) + PD 3.1 cable (E-Marker saying 50V, 5A max; > 100 W)
  3. Anker charger (USB PD 3.0; 100 W) + PD 3.0 cable (E-Marker saying 20V, 5A max; <=100 W)
  4. Anker charger (USB PD 3.0; 100 W) + PD 3.1 cable (E-Marker saying 50V, 5A max; > 100 W)

My conclusion so far: Using a USB PD 3.1 compatible cable with the Anker powerbank (#2 from above) will show the problematic behaviour. All other combinations will work without problems.
This problematic behaviour can be described as following:

  1. The laptop tries to charge. After a few seconds the charging will be stopped and retried.
  2. This behaviour continues until the cable will be removed. After that, any charger + cable combination will now only supply the system with energy but the battery will not charge any more.

During #1 the following log messages will be printed:

ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
workqueue: acpi_ec_event_processor hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
workqueue: acpi_ec_event_processor hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
workqueue: ucsi_handle_connector_change [typec_ucsi] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)

The broken battery charging can only be fixed by fully shutting down the system and waiting roughly 60 seconds. After that the battery will charge again (given you’ll use a charger + cable combination that works).

I will try some further scenarios next week with PD 3.1 enabled chargers. I would like to find out whether this is only related to this specific powerbank or any 140W charger based on PD 3.1

I’ve also contacted support to get some help from Framework, too.

Edit:
It seems Like Framework already came to the same conclusion in their BIOS 3.04 Release notes

Known issues:
Charger support for certain portable EPR power banks.

1 Like