Battery Info - Vendor is unknown 31615

Support and Help
, ,
1

25.10
LxQT

The “BatteryInfo” LxQT shows the Vendor is unknown 31615.
Is there a database of vendors?

2

Hi and welcome :wave:

To understand this better, we’ll need a bit more information, because LXQt’s BatteryInfo simply reads what the system firmware reports—it doesn’t maintain its own vendor database.

Could you please clarify the following:

  • What exactly are you trying to find out?
    Are you concerned about battery health, correctness of the vendor name, or just curiosity?

  • Hardware details

    • Laptop/Device brand and model
    • Is the battery original or a replacement?

  • System details

    • Output of:

      upower -i $(upower -e | grep BAT)

      or alternatively:

      cat /sys/class/power_supply/BAT*/manufacturer

In many cases, seeing something like “Vendor: unknown 31615” simply means the battery firmware does not expose a proper manufacturer string, or it uses a numeric/ACPI ID instead of a human-readable name. LXQt is just displaying that raw value.

Once we know your hardware model and can see the upower output, it will be clearer whether this is:

  • a firmware limitation,
  • a third-party battery reporting incomplete data,
  • or just cosmetic and nothing to worry about.

Looking forward to the details :+1:

1 Like
3

Acer Aspire A515
Original battery.

$ upower -i $(upower -e | grep BAT)
  native-path:          BAT1
  vendor:               PANASONIC
  model:                AP19B5L
  serial:               31615
  power supply:         yes
  updated:              Sun 28 Dec 2025 09:36:33 PM (15 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    warning-level:       none
    energy:              35.9744 Wh
    energy-empty:        0 Wh
    energy-full:         35.9744 Wh
    energy-full-design:  52.976 Wh
    energy-rate:         0 W
    voltage:             16.412 V
    charge-cycles:       N/A
    percentage:          100%
    capacity:            67.907%
    technology:          lithium-ion
    icon-name:          'battery-full-charged-symbolic'
  History (charge):
    1766975758  100.000 charging
    1766975757  98.000  charging
    1766975756  100.000 discharging
    1766975752  98.000  discharging
    1766975737  100.000 charging
    1766975735  98.000  discharging
  History (rate):
    1766975752  0.000   discharging
    1766975752  6.021   discharging
4

battery
battery338×390 18.8 KB

5

“Unknown” is hard-coded in the LXQt sources. It displays the literal string “Unknown” followed by the battery serial number. Although the battery information comes from the UPower, the vendor property is not used and is not available when the battery information is shown.

6

What is the output of

find /sys/class/power_supply/BAT0

There may be a fire we can echo into and change things

7 
$ find /sys/class/power_supply/BAT0
find: ‘/sys/class/power_supply/BAT0’: No such file or directory

I tried BAT1 and that works.
This laptop has 1 battery.

8

Based on the outputs you shared, everything on the system side looks correct and healthy.

  • upower correctly reports the vendor as PANASONIC and the model AP19B5L.
  • The value 31615 is clearly the battery serial number, not the vendor.
  • Battery data (capacity, energy, state) is being read properly, which confirms there is no hardware or firmware issue.

As @avb66 explained, this behavior is a limitation in LXQt itself:

  • LXQt’s BatteryInfo does not use the vendor field from UPower.
  • Instead, it displays a hard-coded "Unknown" string and appends the battery serial number.
  • So "Unknown 31615" is expected behavior and purely cosmetic.

In short:

  • :heavy_check_mark: Battery is detected correctly
  • :heavy_check_mark: Vendor information is available at the system level
  • :x: LXQt BatteryInfo just doesn’t show it

If you want accurate vendor details, upower (or /sys/class/power_supply/BAT1) is the correct source.

3 Likes
9

I thought it might be a bug in:

1 Like
10

Yes, your assumption is correct :+1:

Based on what we’ve seen, this looks like a UI limitation/bug in LXQt BatteryInfo, not an issue with your battery or your system.

Because the vendor information is correctly available via upower, this is something that would need to be fixed on the LXQt side. If you’d like, you can report this upstream to the LXQt team as a small UI improvement.

Also, don’t forget to mark the reply that answered your question as the solution—it will help others who run into the same behavior in the future.

Cheers :beers:

2 Likes
11

Could try

sudo ln -s /sys/class/power_supply/BAT1 /sys/class/power_supply/BAT0

See if it expects BAT0 only

12

Good idea but sudo and a root shell don’t work:

# ln -s /sys/class/power_supply/BAT1 /sys/class/power_supply/BAT0
ln: Permission denied
13

I’m guessing you ran that as root instead…

1 Like
14

I just used AI, seems you can make a udev rule:

The standard Linux way to handle device naming is through udev. You can create a rule that tells the system how to identify the battery.

Create a new udev rule file:
sudo vi /etc/udev/rules.d/99-battery-name.rules

Add the below line:
SUBSYSTEM=="power_supply", KERNEL=="BAT1", NAME="BAT0"

Save and exit vi, then reboot and test

If this doesn’t help then simply run:
sudo rm -f /etc/udev/rules.d/99-battery-name.rules
Then re-reboot to roll back

15

That didn’t work.

Oh well.