- It looks like fast pair/shared Matter devices now re-use the commissioning activity if it is still open in the background. Set the launch mode to single top to be able to use onNewIntent and get data for new devices.
- Prevent unnecessary changes to the selected entity when changing servers, if an entity exists on both servers. It already didn't clear everything like title/icon, just the selected entity!
- Still calling selectEntityId in case the icon is different
- When checking if an expanded zone geofence should be created include the server ID in the comparison as that is what is used everywhere else. Otherwise expanded zones are never added, and as a result high accuracy mode won't work as expected.
Fix dialog for high accuracy zone constraint entity id
- Zone entity ids can contain underscores, only split on underscores once to keep those that belong to the entity id (string is serverid_entityid). The data was being stored correctly.
* Bump com.android.tools.build:gradle from 7.4.2 to 8.0.0
Bumps com.android.tools.build:gradle from 7.4.2 to 8.0.0.
---
updated-dependencies:
- dependency-name: com.android.tools.build:gradle
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
* Bump Gradle version
* Build default values changes
- Remove items that match new defaults
- Add item to keep old default to allow for those changes to happen in another PR
* Align target Kotlin version with target Java version
* Use JDK 17
* Remove one more item that now matches default
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Joris Pelgröm <joris.pelgrom@gmail.com>
* Add ComplicationType.LONG_TEXT support, friendly state
- Makes it possible for watch faces to request a long text complication
- Use the friendly state to support translated states and dates
* Add show title option
- Allows hiding the title of a complication in case it doesn't look right
* Implement/fix reading state from database
- When a entity ID is provided in the configuration request, load data for that complication from the database to allow easy reconfiguration
- Provide more appropriate error messages when complication isn't configured / the entity doesn't exist
* ktlint
* Fix "Always show first view" option with HA > 2023.04
* Revert "Fix "Always show first view" option with HA > 2023.04"
This reverts commit bb1421e3f7.
* Much easier fix for "Always show first view" option with HA >2023.04
- The zone ID sent to the server included the server ID, which could break automations listening for the zone ID (server ID isn't intended to be exposed)
- Exchange server information between the Wear app and phone app, and create a temporary server on the phone that holds the Wear server information, to ensure that the same server is used on both devices
- Expand the automatic Thread dataset sync on Matter commissioning to also send the device-preferred Thread dataset if it's different from core (it will either receive something new or update)
* Creation of Automotive Module and Fix OnboardingActivity parent Activity.
* Adding Manifest Dependencies.
* Fixing ktlint
* Remove unused import.
* Copy Google Services to android automotive
Github actions for PR require this to be set up in order for the build to pass.
* Missing two entries to copy the google-services.json file
* Fixing Build Process.
* Version code +2
We add 2 because the app, wear (+1) and automotive versions need to have different version codes.
* Update +3 per recomendation.
* Code to support transition from Full app to Car App Library.
* Fixing linter.
* More ktlin
/home/runner/work/android/android/app/src/main/java/io/homeassistant/companion/android/BaseActivity.kt:19:1 Needless blank line(s)
/home/runner/work/android/android/app/src/main/java/io/homeassistant/companion/android/BaseActivity.kt:31:95 Unnecessary semicolon
/home/runner/work/android/android/app/src/main/java/io/homeassistant/companion/android/BaseActivity.kt:39:1 Unexpected blank line(s) before "}"
/home/runner/work/android/android/app/src/main/java/io/homeassistant/companion/android/BaseActivity.kt:44:1 First line in a method block should not be empty
* Changes to allow navigate back from / native and feedback from PR.
* Indentation fixes.
* Get and cache user information
- Add function to get information about the current user
- Cache user information alongside server in database
* Replace/prevent admin only calls
* Prevent crash when pausing if server is deleted
* Handle race when deleting
- Handle a race condition where we delete and finish the activity at the same time during which it might not yet have been fully removed
- Handle a race condition where a back-up may be restored and a server is deleted on startup, which causes the authentication repository to become unavailable with a minor delay
* Update play store listing for wear OS
* Update description and add screenshots for tiles
* Update phone screenshots to be consistent and showcase some widgets
* Fix small size
* Use single screenshot to show widgets and meet requirements
* Update home screen images
* Show all widgets
* Update camera widget image, oops
* Fix screenshots
* Make background transparent, remove resizing and set minimum size to 1x1 grid for camera widget
* Use transparent background with rounded corners
* Remove background
* Change image view scale type
* Restore transparent background
* Set target cell size to maintain 2x2 grid by default
---------
Co-authored-by: Justin Bassett <bassett.justint@gmail.com>
* Bump org.jlleitschuh.gradle.ktlint from 11.1.0 to 11.2.0
Bumps org.jlleitschuh.gradle.ktlint from 11.1.0 to 11.2.0.
---
updated-dependencies:
- dependency-name: org.jlleitschuh.gradle.ktlint
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
* gradlew ktlintFormat
* Rename packages with underscores
> Task :app:ktlintMainSourceSetFormat FAILED
home-assistant-android\app\src\main\java\io\homeassistant\companion\android\widgets\media_player_controls\MediaPlayerControlsWidget.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
home-assistant-android\app\src\main\java\io\homeassistant\companion\android\widgets\media_player_controls\MediaPlayerControlsWidgetConfigureActivity.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
Rename: media_player_controls to mediaplayer
> Task :wear:ktlintMainSourceSetFormat FAILED
home-assistant-android\wear\src\main\java\io\homeassistant\companion\android\onboarding\manual_setup\ManualSetupActivity.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
home-assistant-android\wear\src\main\java\io\homeassistant\companion\android\onboarding\manual_setup\ManualSetupModule.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
home-assistant-android\wear\src\main\java\io\homeassistant\companion\android\onboarding\manual_setup\ManualSetupPresenter.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
home-assistant-android\wear\src\main\java\io\homeassistant\companion\android\onboarding\manual_setup\ManualSetupPresenterImpl.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
home-assistant-android\wear\src\main\java\io\homeassistant\companion\android\onboarding\manual_setup\ManualSetupView.kt:1:1 Package name must not contain underscore (cannot be auto-corrected)
Rename: manual_setup to manual
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Joris Pelgröm <joris.pelgrom@gmail.com>
* WebView check app lock on server change
* Settings check app lock on server details
- If the currently active server has a lock, show it
- If the currently visible server has a lock, also show it
* Sync sensors with individual servers
- Update sensors once, and allow syncing enabled/state with individual servers instead of doing the same for every server
- Default to the default sensor enabled state for new servers instead of copying another server
* Make last update sensor server-specific
* UI
* New servers: enable if enabled on any server
* Handle per-server enabled state in location tracking
* Fix icons in dark mode
* Server gestures and chooser
- Add gestures to quickly switch between multiple servers
- Add a chooser to select a server, and add a gesture for it
* Fix history (new page is added _after_ loading finishes)
* Sync Thread datasets when starting Matter commissioning
- When starting Matter commissioning from the frontend, check if there are Thread datasets on the device or in core but not the other, and if so try to sync them
* Also sync Thread datasets in shared device flow
- Datasets may not be used by the system but it is useful for future devices
- Make methods in ThreadManager a bit more general
* Multiserver foundation
- A foundation to build multiserver support on. Not ready for general use.
* Update new vehicle support
* Rebase fixes
* Multiserver settings
- Show settings for the correct server when editing server settings from the settings
* Bind session to device/install
- Save an install id with the app install to make sure that it isn't re-used on another device causing issues
* Add migration
- Migrate server info from shared preferences to the database after database migration and clean up
- Remove unused url shared preferences
- Read/save server version from/to database
* Fix auth error when session is refreshed
* Show server name instead of URL
- Read the server name when getting the config, and save it to the database
- Allow the user to override the server name in the app's settings
* Multiserver notifications
- Make notifications aware of which server sent the notification
- Show server name in notification if more than 1 server is added to the app
- Use the server-specific repositories when calling webhooks/authenticating/etc
* Handle multiserver in websocket worker
- Copy the settings database row to the new server ID to allow for server-level settings (websocket) while keeping the original for app-level settings (sensor update frequency), and handle this in onboarding
- Make the websocket worker check in on all servers and open/close connections where required
- Add the webhook_id to websocket notifications to link them to servers
- Update ServerManager servers to defaultServers because I'm using the same filter everywhere
* Migrate shared preferences
- Move server-specific device name to Server and secret key to ServerConnectionInfo
- Add a server ID key to the remaining shared preferences and migrate existing values
* Add option to delete server from settings
- Allow deleting servers directly from the app's settings, because you might not be able to do so from the frontend.
* WebView switching and active server management
- Allow switching which server is considered 'active' and used for the webview when loading
- On auth errors remove the server instead of removing the URLs (?)
- When getting external auth consider that the server might just have been removed (possible race condition from frontend which frequently causes 1 unauthorized connection when logging out)
- Fetch config after adding a new server to fill in name and version before first use
* Sync registrations and blocking load
- When starting the app, sync all registrations
- Remove Wear state with server but new registration required
- When receiving a new push token, update all registrations
- Do a blocking load for getting the servers because otherwise the app might think it's not registered when running in the background
* Use StateFlow for the server list
- Don't manually refresh but use a StateFlow to get updates pushed when the list of servers changes
- Make settings use unique server keys to prevent constant remove/re-add
* Sensor updates and sync with multiple servers
- Send sensor updates to all servers and sync changes to the app. Sensors are shared across all servers the app is connected to so changing enabled state on one server will update it for all servers.
- Don't update sensor enabled state for location tracking directly from onboarding, this should be done in the result.
- Remove unused SensorWithSettings class
* Send NFC tag scans to all servers
* QS tiles server selection
- Listen to updates for a specific server
- Allow selecting server if there is more than one
* Shortcuts server selection
- Allow selecting server if there is more than one
- Extract OutlinedButton with DropdownMenu for server selection to a standalone Composable
- Update QS tiles to not automatically reset server ID when server no longer exists, align with shortcuts
* Fix revoked sessions + crashing app
- When a session is revoked update the session object to reflect it
- Fix app crashes on revoked sessions because of race conditions with the AlertDialog causing window active/inactive at the same time as finishing it
* Extra server onboarding tweaks
- Skip welcome and location
- Save/fix notification preference for minimal version
* Fix sensor state type conversion errors for new servers
- If the state is removed but the type isn't, this can result in unwanted conversions throwing errors so remove the state type as well when copying a sensor
* Matter multiserver
- Request specific server ID in Matter functions
- Add server selection to shared Matter device flow
* Android Auto multiserver
- Allow switching server in Android Auto. Defaults to active server, note that it doesn't change the default but only changes it in AA.
* Widgets server selection
- Add server selection to all widgets and update handling to use the selected server
* Clean up TODOs out of scope
* Device controls multiserver
- Subscribe to updates for each server that controls are added for
- Allow managing lock screen enabled controls for each server
* Don't try to register sensors when finishing
- Don't try to do a sensor update when finishing, as this may cause unintended use of resources we're trying to clean up (when deleting a server)
* Server-level zones and location tracking
- Keep track of which server a zone belongs to for location tracking, and send updates only to that server
- Add server name to zone selection setting
* Merge fix
* Show 'Activate Server' any time there are multiple servers
- If the user is looking for the option to go to their server why hide it if it is already used, making them go back twice?
* More consistent strings
* Improve add server feedback in settings
- Preserve the activate server before adding a new one to prevent unexpected active server changes
- Show a Snackbar when another server is added indicating success with a button to activate it, or failure
* Remove unused ServerManager
* Fix tag import
- Update images to align with Matter branding guidelines
- Remove "shared" from screens as this flow is also used for fast pair where it makes no sense
* Move server settings to a server settings screen
- Move server-specific settings to a new screen to be accessed from the main settings only containing server specific settings in preparation for multiserver
- Sensors is currently not server-specific even though one setting is stored by server ID, to be fixed later
* Store app preferences in another shared preferences file
- Store app preferences not in the integration shared preferences file, but in the shared preferences file for general prefs (it is named themes but there are already other app-level prefs in it)
- Move Wear specific preferences to it's own repository + shared preferences file
* Improve server row with local data
- While we don't have a server name or user name, show the registration name when available to improve the server row layout
* Simplify location permission request code
- Remove the flexible permission requests as it isn't used in the current settings structure, only expect location permissions
- Switch from the deprecated functions to the new flow using activity result contracts
* Remove unused string
* Initial commit of wear OS notifications
* Update to allow message and title
* Move constants to object to reduce imports
* Split up logic to match phone app
* Update readme and set websocket to false for wear OS
* Bump firebase BOM
* Initial work on Android Auto support.
* Get some toggling working, add a main view that is useful.
* Make sure we can test this on every commit.
* Migrate to full flavor.
- Add option to quick settings tile to only allow interacting with it when the device is unlocked, similar to device controls on Android 13 (but phrased differently to match the system default behavior)
- Add a lot more quick settings tile services
- Enable QS tile services only for tiles up to the highest tile # in use + 4, with a minimum of 12, to prevent long lists and make it work 'automagically'
* Update instead of cancel notification on reply
- When a notification is replied to, update it instead of cancelling it to allow the other to continue manipulating it
* Support multiple replies
- Keep a history of replies in the bundle to match system behavior
* Only keep replies that are actually shown
* Update Matter dependency
* Improve shared device commissioning
- Show device name if available
- Show error codes if returned
* Show toast for commissioning request errors
- When an error occurs for commissioning requests/before the Play Services UI is shown, show a toast informing the user that Matter is currently unavailable. Most user-facing errors will be shown in the Play Services UI (during commissioning).
* Add setting to start the app always on the first dashboard view
* Run linting
* Do not close SettingsActivity
* Only show first view if not in HA Config + Fix flash of dashboard when navigating to app settings
* Scroll to top when calling first view of dashboard
If we are on a another view a we are scrolled to the bottom, the first view will be also at the bottom
* Use default dashboard as starting dashboard
* Allow HA config dashboard to call the first view of dashboard
- Also disallow /hassio (Home Assistant addons) to call the first view
* Enhance show first view setting description
* Fix class name spelling LifecycleHandler
* Fix calling first view of dashboard on config/areas and config/automation
Co-authored-by: Justin Bassett <bassett.justint@gmail.com>
* Add new option to vibrate when quick settings tile is clicked
* Use vibration effects if the device supports it
* Review comments
* Remove question mark
* Set switch color when unchecked
* Matter commissioning: MVP
- Implement a basic framework for the app to support Matter commissioning
- Add hooks for the `matter/commission` message that will be sent by the frontend to trigger Matter commissioning
* [WIP] HA as Matter share target
* [WIP] Updated commissioning flow
- Add websocket Matter API support
- Update architecture to better ensure a working minimal build
- Remove external bus responses for Matter commissioning message
* Rename MatterRepository
* Handle shared Matter devices
- Adds UI to handle shared Matter devices instead of copying the pairing code to the clipboard
- Updates the on network pairing pin/code to be a String, which may be received for shared devices
* Cleanup test button
* Pairing code type and service error handling
- Update pairing/pin code type to Long for server
- Send Play Services error if commissioning returned an error
* Increase timeout for Matter commissioning requests
* Use normal commissioning for shared devices
- Use the normal matter/commission command for devices shared with the app
- Shared device UI polishing
* Fix minimal and remove old name
* Update frontend commissioning status enum
* Update quick setting tiles with state updates
* Keep track of appropriate job to cancel when needed, use variable for toggle with lock
* Switch to Job from CoroutineScope
Catch ActivityNotFoundException for downloads
- When trying to forward a download intent to the system catch the exception that is thrown if the system can't handle it to prevent a crash
* Manage app language using AndroidX, integrate with Android 13
- Manage the app language using AndroidX to fix the setting not being applied and to be able to easily integrate with Android 13's system setting
* Move locales_config.xml to common
* Generate locales_config.xml when downloading translations
* Fix multiple variants for languages being collapsed into one
* Fix language codes with region variants
* Don't split languages when using app bundles
* Rename
* Add daily floors sensor for Wear OS3 devices
* Do a compatibility check for sensor availability in health services
* Print more logs and attempt to send latest data, update more getAvailableSensor methods
* Process review comments
* Process more review comments, use actual time in millis
* Clear out available sensors when updating with new list
* Log the capabilities in case we need to troubleshoot later
* Review comment
* Missed one additional review comment
* Return immediately instead of storing a list
- If no Wear app is installed on a device, checking for nodes will throw an exception that the API is unavailable. This is an expected error, don't log it to not confuse users.
* Update change log for week of 10/21
* Add data roaming breaking change fix
* Update per recent merges
* Mention breaking change for command_bluetooth on android 13+ devices
* Support zone name only location tracking
* Update strings to match iOS
* Only add Sent location setting on supported versions
* String updates
* Simplify code as the setting is always on
* Save cloud URL separately and add pref
- Save the cloud / remote UI url that is received during registration separately, and add a preference to use the cloud url instead of the external url
- Save the cloud / remote UI url and cloudhook url received during webhook config updates, to be able to support using cloud after the app was set up
- Clean up cloudhook url when logging out
* Add UI for "Use Home Assistant Cloud" url
* Cleanup
* Fix function order
- Update onBackPressed functions which have been deprecated to use the new OnBackPressedDispatcher and OnBackPressedCallback
- Indicate support for the predictive back gesture
* Use compressed entity changes for device controls
- Add support for the subscribe_entities websocket subscription which delivers initial state + changes in a compressed format to reduce data usage
- Use the new subscribe_entities format in device controls on supported Home Assistant versions
* Less duplicate code
* Add notify command for app-lock
* Add null check for optional parameters
* Only allow enabling app_lock by notify command if previously enabled by user
* Use constants for app lock command parameters
* Add BiometricManager check before turning on app_lock
* Remove 'hasLockEverBeenEnabled' in favor of only biometricmanager check.
* Improved value checking for app lock command.
Made setAppLock function suspending i.s.o. sepearate runBlocking calls.
* Show notification if no parameters were updated.
* improved parameter value checking
* Don't make changes when invalid data is provided
* Early check on argument validity for app lock commands
* Cleanup app lock command parameter validation
* Request notification permission during onboarding
- When using Android 13 or the minimal version, add a screen to onboarding to request to enable notifications on the device. This screen is based on iOS onboarding. When tapping Continue, on Android 13 this requests the system permission and/or on the minimal version this changes the websocket setting.
- Compile with and target SDK 33 (targeting required to be able to request notification system permission on demand)
* Add notification settings link in settings when off
- Show a new setting in settings for the user to enable notifications for the Home Assistant app, either because the permission was denied (Android 13) or the user manually turned off all notifications (Android 8-12).
- This new setting replaces the notification channels setting when everything is off; in this case there is no point managing individual channels. If at least one channel is on, the existing notification channels setting is shown instead.
* Compose tweaks
- Remove redundant content description for icon
- Change to a simpler scroll modifier
* Fix skipping notifications on minimal version
- Ensure that the value is actually saved to the database
* Post Bluetooth on/off commands as if invalid
- When using Android 13, post notification commands to control Bluetooth on/off as a normal notification as if they were invalid, as the function has been deprecated for the app
* Remove type that can be inferred
- Update Gradle to latest version (7.5.1)
- Update Android Gradle plugin to latest version (7.3.0)
- Move package property out of manifest into gradle build files namespace as recommended
* Merge Follow Home Assistant/Follow System Settings theme
- As these two themes behave the same now, don't present two options but instead just one. The default setting has been renamed back to "Follow System Settings" to best match expectations. Internally the "android" setting still works, settings will show "Not set".
* Remove useless webview force dark
- The WebView force dark settings are no longer required (and will no longer be supported when targeting Android 13), as the latest appcompat/webview/HA frontend already respect the app's theme setting and allow overriding it
* Add support for showing custom icons in device controls
* Clean up and set color based on state
* Set icon size and adjust colors based on domain
* Move color values to resources and add more color options from source
* Review comments
* Only set the icon if it exists in the library
* Add commands to control screen brightness and a sensor to get the value
* Minor file clean up
* Review comments
* Rename Device Settings to Display Sensors
* Add support for intent scheme URI in clickAction and actionable notifications
* Add a new prefix for app links in actions
* Rename app link to deep link to be more precise
* Use correct intent prefix
* Take user to the play store if the app is not installed
* Fix taking user to the market if app is missing, remove ability for deep links since we can't get the package name
* Only open the play store if we have an actual package to open to
* Add support for using BSSIDs for internal connection
- Add support for entering BSSIDs to use for detecting when the internal connection URL should be used. These are saved like any regular SSID, but contain the prefix "BSSID:".
* Add link to documentation
* Fix full screen mode for all devices
* Hide system UI when we regain focus and a video is still full screen
* Revert theme changes
* Remove unneeded line break
- Set the thumbnail template for the camera control to active as long as the camera isn't unavailable and the app was able to download an image, to show the camera image more often and better match the frontend.
- Instead of receiving all state changes when the device controls are open, only receive state changes for entities that were added as controls. This potentially reduces the amount of data used while controls are open.
* Improve adding quick settings tiles
- Use the new option available on Android 13 to prompt the user to add a tile to the quick settings panel, if a tile wasn't already added
- Switch Toast to Snackbar
- Move some logic from the manage tiles view to viewmodel
* Only show subtitle field when supported
- Setting a tile subtitle is only supported on Android Q+, so don't show the field on versions before that!
* Deeplink into app for tiles that aren't setup
- Instead of disabling a tile if it isn't setup, if the user is logged in set it up as inactive with the default icon/label and deeplink into the app settings with a notice that it needs to be setup first. This provides a better first use experience, as the user can simply tap it to setup instead of requiring them to manually go to the settings.
* Always do Wear onboarding on phone
- Switch the Wear onboarding to always use the sign in flow on the paired phone, instead of offering the option to sign in completely on the watch.
- When opening the companion app using the Wear app, immediately link the user to the list of instances or sign in screen.
- Use standard OAuth flow for devices without companion app installed.
- Fix type casting of location preference in Wear onboarding result.
* Fix ListenableFuture await import
* Add BLE Beacon Monitoring Sensor
* Fix on/off toggle
* Add on/off commands
* Fix commands
* Add all beacons to attributtes
* Add Kalman Filter
* Improve performance
* More settings
* cleanup
* Fix linter errors
* Update description
* Show monitoring state in sensor
* Add missing permissions
* Fix permissions
* Fix Bluetooth state of Android 12
* Use instance instead of singelton
* Use runBlocking for updateLastSendState
* Use own scope for beacon manager
* Use new notification commands
* fix rebase
* use null instead of empty string
* return if sensor is disabled
Implement subscribe_trigger and use it in widgets
- Implement support for subscribing using subscribe_trigger, currently used to get state changes only for specific entities
- Change the entity state and media player widgets to use this new subscription instead of subscribing to all state changes, based on the template widget
- Removed some placeholder code from media player widget
* Add setting to bypass app lock on home network
* Debug loging to check logic
* Fix logic. Cleanup logging.
* Disable home lock bypass when no home networks are configured.
* Only check for WiFi SSID, not internal URL when evaluating isLockEnabled.
* Fix build error
- Adding a media player widget from settings didn't work because the list used to check that entities have been selected isn't updated immediately, but only on load or in a callback after pinning the widget. To work around this, manually check it before pinning the widget.
* Add some more attributes to geocoded sensor and check that device supports it
* Remove language attribute as it does not supply the expected data
* Combine latitude and longitude into the location attribute again
* Update WebSocketRepository for multiple subscriptions of same type
- Change the structure of how the websocket repository tracks individual subscriptions to allow subscribing multiple times with the same type, but different data
* Update TemplateWidget to use template subscriptions
- Instead of depending on entity state changes and refreshing any time there is a change, use the render_template subscription for the template widget to limit the amount of data and power used. To make this possible without too much abstractions, the TemplateWidget no longer implements BaseWidgetProvider.
- Fix hardcoded "Loading" string
* Handle potential null subscription ID
- Implements #2795 for changes to tracked subscription ID
* Handle failed subscribing similar to other failures (null)
- When subscribing fails, return null and don't store an active subscription instead of continuing and returning a flow (which would never emit messages)
* Update manifest
* Handle foreground service restrictions for persistent connection
- When trying to start the WebsocketManager as a foreground service, catch exceptions due to restrictions and show the user a notification to fix it
* Update logging in WebsocketManager
- Change to the OkHttpClient used elsewhere by the app to download notification videos to resolve problems related to cookies and mTLS authentication. As a result, storing and deleting the file is now handled by the app instead of by the system.
* Modify Notification GIF Framerate
Modoify VIDEO_INCREMENT_MICROSECONDS to have notification GIFs generate a frame every 0.5 seconds for a video instead of the current every 2 seconds. This should result in smoother notification animations thus improving the UX
* Increase processingFrames.size
Increase processingFrames.size as increasing the framerate results in the animation ending too soon
* Scale video to a max width of 480 while maintaining video ratio
Notification video width scaled to 480. (1920 / 4) Height will scale accordingly while maintaining video aspect ratio. e.g. 1920x2560 will be scaled to 480x640
Frames are set to every 1 seconds with 5 frames resulting in a 5 second GIF
* Update MessagingManager.kt
Based on research and rapid prototyping under another fork, I've decided that scaling the image to a fixed width and a ratioed height is not going to work. There are issues that need to be resolved which result in the image being cut off and stretched in the notification.
End result is the only overall change is changing the frame generation from once every 2 seconds to once every 1 second. This has improved the fluidity of notifications but I understand is my own subjective opinion.
This means there is still a potential case where 4K cameras will exceed the size limits of notifications.
* Typo fix
* Re-Implement Scaling to a Constant Width
* Update MessagingManager.kt
* Add logic to not scale videos smaller than specified width and Increase GIF speed (ViewFlipper)
* Tune processing times
Tune processing time to have one frame generated every 0.75s, then frames are played back at 3x speed. This results in 9 seconds of activity being played in 3 seconds.
* Implement Dynamic Frame Count
Dynamic number of frames up to a specified size limit (currently 2.5MB)
* Review Before Merge
