[bluez/bluez] 078a04: device: Fix the return type of device_irk_cmp()

[RSmirnov512 <noreply@github.com>]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 078a047f6a40b0acf67861d01f1f2cb7bb50d024
      https://github.com/bluez/bluez/commit/078a047f6a40b0acf67861d01f1f2cb7bb50d024
  Author: Andrey Smirnov <andrew.smirnov@gmail.com>
  Date:   2025-11-17 (Mon, 17 Nov 2025)

  Changed paths:
    M src/device.c

  Log Message:
  -----------
  device: Fix the return type of device_irk_cmp()

The return value from device_irk_cmp() is returned directly from
device_addr_type_cmp() which implements a memcmp()-like interface, so
we need to return an int() and a zero for equality. Returning bool
will cause false positives since false is 0 and true is 1.

Fixes: f1fb4f95f49e ("core: Fix not resolving addresses")


  Commit: f5043771c27b5d9c19b1415e4e4c1eb5f7d470f8
      https://github.com/bluez/bluez/commit/f5043771c27b5d9c19b1415e4e4c1eb5f7d470f8
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-11-17 (Mon, 17 Nov 2025)

  Changed paths:
    M tools/mgmt-tester.c

  Log Message:
  -----------
  mgmt-tester: add tests for discoverable timeout

Test that the discoverable timeout can be set successfully and that the
timeout actually triggers:

Set discoverable on timeout - Success 1
Set discoverable on timeout - Success 2 (Timeout)


  Commit: c5d4a041483c52f16f9f47adae41225d8ad90595
      https://github.com/bluez/bluez/commit/c5d4a041483c52f16f9f47adae41225d8ad90595
  Author: Roman Smirnov <r.smirnov@omp.ru>
  Date:   2025-11-17 (Mon, 17 Nov 2025)

  Changed paths:
    M Makefile.am
    M src/battery.c
    A src/shared/battery.c
    A src/shared/battery.h

  Log Message:
  -----------
  shared/battery: improve the display of the charge level

The battery charge level may fluctuate due to uncalibrated
sensors. Commit smooths out such fluctuations.

The algorithm for determining uncalibrated sensors consists of
finding the number of changes in charge direction (i.e., "spikes").
If the number of spikes is zero, the device is charging or discharging.
If there is one spike, it may mean that the device has started charging
or has been disconnected from charging. If there are two or more spikes,
this is a clear indication of an uncalibrated sensor.

Check that the battery charge is fluctuating. If the battery charge
is fluctuating, use the average charge value, otherwise use the current
value.

Fixes: https://github.com/bluez/bluez/issues/1612


  Commit: c1493c32d7da270329d0ac2ca02117b905c04362
      https://github.com/bluez/bluez/commit/c1493c32d7da270329d0ac2ca02117b905c04362
  Author: Roman Smirnov <r.smirnov@omp.ru>
  Date:   2025-11-17 (Mon, 17 Nov 2025)

  Changed paths:
    M .gitignore
    M Makefile.am
    M doc/test-coverage.txt
    A unit/test-battery.c

  Log Message:
  -----------
  unit: Add basic unit tests for battery charge handling


Compare: https://github.com/bluez/bluez/compare/4bf47f880d06...c1493c32d7da

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications