Delay in updating charge status in Ubuntu 22.04 LTS

[lvek4096]

I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally.

When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status.

Normally, the change in power status should be instantaneous.
In short, there is a delay in the OS in showing the current charge status.

Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status.
This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status.

However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
There, the power status behaves normally with no delays whatsoever.

Please look into this issue and fix this bug as soon as possible.
One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly.

upower version:
UPower client version 0.99.17
UPower daemon version 0.99.17

OS:
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Kernel: Linux 5.15.0-47-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: upower 0.99.17-1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 20:41:16 2022
InstallationDate: Installed on 2022-09-12 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

[lvek4096 (lvek4096)]

This bug does not seem to be present in Ubuntu 22.10, on the same hardware.