Skip to content

[Bug][T-LoraPager]: There is no difference between buzzer and vibration #8908

@polarikus

Description

@polarikus

Category

Other

Hardware

Other

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

  • Meshtastic UI aka MUI colorTFT
  • InkHUD ePaper
  • OLED slide UI on any display

Firmware Version

2.7.16.a597230

Description

Currently, in T-loraPager, it is not possible to control vibration and audible notifications separately.

Steps to reproduce:

  1. Go to System Actions -> Notifications -> Buzzer Actions
  2. Set to None

Expected result:

All audible notifications (Speaker) are turned off.

Actual result:

All tactile notifications (Vibration motor) are turned off.

Second case:

  1. Go to External Notification in the mobile app.
  2. Disable vibro and buzzer.

Expected result:

All audible notifications (Speaker) are turned off.
All tactile notifications (Vibration motor) are turned off.

Actual result:

The settings do not affect notifications; sound is only turned off if External notification is completely disabled.

Disscution

  1. Clearly separate the Notification Module (Vibra) and Notification Module (Buzzer).
  2. Create a setting: System Actions → Notifications → Vibra Actions.
  3. The setting System Actions → Notifications → Vibra Actions should now affect vibration feedback from button clicks, while the Notification Module (Buzzer) setting should not affect vibration feedback from the keyboard.

If you agree with the concept, I'm ready to implement it for the T-LoraPager and check which other devices need similar rework.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions