Skip to content

Develop - button remap uses automation actions, debugging long press options, standby bulk app configs, volume level in automations, are we there yet full screen alert and more - #823

Merged
sameerasw merged 8 commits into
mainfrom
develop
Aug 21, 2026

Conversation

@sameerasw

Copy link
Copy Markdown
Owner

This pull request introduces several improvements and new features related to action handling, settings migration, and notification behavior in the app. The biggest changes are the introduction of a robust serialization/deserialization system for actions, a central action registry, and enhancements to button remapping and notification customization. Additionally, new actions have been added and legacy ones removed, and a new setting for location-based full-screen alarms is now available.

Action Model and Registry Improvements:

  • Introduced ActionGsonAdapter, a shared Gson serializer/deserializer for the Action sealed interface, enabling robust storage and retrieval of action objects in preferences and repositories.
  • Added ActionRegistry, providing a central, categorized list of available actions for use in automation and button remapping, with support for Android-version-specific actions.

Button Remap and Settings Migration:

  • Updated SettingsRepository to migrate legacy string-based button remap actions to the new Action object format, and added methods for storing and retrieving these actions as JSON. This ensures backwards compatibility and future extensibility. [1] [2]
  • Refactored InputEventListenerService to use the new getRemapAction method, ensuring button remap logic now works with the new serialized action objects instead of plain strings. [1] [2]

Action Model Updates:

  • Added new actions: CycleSoundModes, ToggleMute, ToggleVibrate, and a configurable SetVolume action with support for different audio channels. Removed legacy notification actions (ShowNotification, RemoveNotification) to clean up the action set. [1] [2]

Settings and Notification Enhancements:

  • Added a new setting (KEY_LOCATION_REACHED_FULL_SCREEN_ALARM_ENABLED) and corresponding getter/setter to control whether location-reached notifications should trigger a full-screen alarm. The notification channel is now selected based on this setting in LocationReachedService. [1] [2] [3] [4]

Other:

  • Registered a new DebuggingSettingsActivity in the Android manifest, likely for internal or developer use.

@sameerasw sameerasw self-assigned this Aug 21, 2026
@sameerasw sameerasw added the enhancement New feature or request label Aug 21, 2026
@sameerasw
sameerasw merged commit e5db467 into main Aug 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant