obsidian cobalt
Galaxy Watch Ultra
Build: BP2A.250325.020.L705FXXU1BYH6
Running WearOS 6
Issue Description:
When Bedtime mode is enabled (either automatically or during deep sleep / phone inactivity), template updates from Home Assistant do not appear. Instead, I observe side effects such as a stuck Home Assistant notification (“update sensor”) in the notification history.
Observed Behavior:
• Background activity is enabled for the Galaxy Wearable app.
• Home Assistant app is running in the background on the watch.
• As soon as I wake the screen, updates/actions resume immediately.
• It looks like shortcut actions are queued until the screen turns on.
• Issue only occurs when the watch is connected via Bluetooth (not on Wi-Fi).
Troubleshooting so far:
• Verified background activity is allowed.
• Confirmed issue doesn’t happen when connected to Wi-Fi.
• Ran dumpstate on the watch to collect logs (since running adb logcat over Bluetooth is not possible).
Hypothesis:
• Something in Bluetooth mode + Bedtime/Doze/deep sleep is delaying or blocking background updates/notifications until the screen wakes.
09-07 14:26:24.747 1000 808 1636 W ActivityManager: Background started FGS: Disallowed [callingPackage: io.homeassistant.companion.android; callingUid: 10198; uidState: TRNB; uidBFSL: n/a; intent: Intent { act=ACTION_START_FOREGROUND xflg=0x4 cmp=io.homeassistant.companion.android/androidx.work.impl.foreground.SystemForegroundService (has extras) }; code:DENIED; tempAllowListReason:<null>; allowWiu:-1; targetSdkVersion:34; callerTargetSdkVersion:34; startForegroundCount:0; bindFromPackage:null: isBindService:false]
09-07 14:46:12.284 1000 808 808 D AppOps : startOperationUnchecked: allowing code 40 uid 10198 package io.homeassistant.companion.android restricted: false flags: s
09-07 14:46:12.285 1000 808 1609 D AppOps : noteOperationUnchecked: reject #3 for code 24 (24) uid 10198 package io.homeassistant.companion.android flags: s
09-07 14:46:12.286 1000 808 1609 W ActivityManager: Background started FGS: Disallowed [callingPackage: io.homeassistant.companion.android; callingUid: 10198; uidState: TRNB; uidBFSL: n/a; intent: Intent { act=ACTION_START_FOREGROUND xflg=0x4 cmp=io.homeassistant.companion.android/androidx.work.impl.foreground.SystemForegroundService (has extras) }; code:DENIED; tempAllowListReason:<null>; allowWiu:-1; targetSdkVersion:34; callerTargetSdkVersion:34; startForegroundCount:0; bindFromPackage:null: isBindService:false]
09-07 15:05:13.518 1000 808 808 D AppOps : startOperationUnchecked: allowing code 40 uid 10198 package io.homeassistant.companion.android restricted: false flags: s
09-07 15:05:13.519 1000 808 1455 D AppOps : noteOperationUnchecked: reject #3 for code 24 (24) uid 10198 package io.homeassistant.companion.android flags: s
09-07 15:05:13.521 1000 808 1455 W ActivityManager: Background started FGS: Disallowed [callingPackage: io.homeassistant.companion.android; callingUid: 10198; uidState: TRNB; uidBFSL: n/a; intent: Intent { act=ACTION_START_FOREGROUND xflg=0x4 cmp=io.homeassistant.companion.android/androidx.work.impl.foreground.SystemForegroundService (has extras) }; code:DENIED; tempAllowListReason:<null>; allowWiu:-1; targetSdkVersion:34; callerTargetSdkVersion:34; startForegroundCount:0; bindFromPackage:null: isBindService:false]
09-07 15:05:13.521 1000 808 1455 W ActivityManager: startForegroundService() not allowed due to mAllowStartForeground false: service io.homeassistant.companion.android/androidx.work.impl.foreground.SystemForegroundService
Unable to trigger shortcuts / update template on Galaxy Watch
That sound like The async task (FutureTask) is stuck at pending background restrictions prevent HA from executing the update before the timeout hits.
Though I have allow background activity enabled for home assistant from wear app. not sure what should be done to lift off that background restriction
@fading rose @lilac ledge FYI
sorry for bothering during weekend
lilac ledge
theres already a known issue with bedtime mode and sensor updates, the watch enters a state where we cant do anything about background restrictions. Samsung has a setting in their companion app but pixel watch does not. https://github.com/home-assistant/android/issues/3976
obsidian cobalt
theres already a known issue with bedtime mode and sensor updates, the watch ent...
Thanks for your prompt response. got it for the bedtime what about when the phone enter deep sleep. at this stage is it still something samsung doing to block home assistant ?
cause I get this same behaviour even if bedtime is not enabled
lilac ledge
so you have a samsung watch, on your phone open teh companion app for their watch and there is a setting to give teh HA watch app unrestricted backgorund access
obsidian cobalt
PS I don't have power saver enabled
lilac ledge
kinda a hidden setting
i may also have some of that terminology incorect but the setting does exist in their companion app
lilac ledge
its possible teh app may have been killed in teh background....there is a known issue with the homescreen crashing. https://github.com/home-assistant/android/issues/3325 the only fix at the moment is to set favorite entities on the watch and to enable the "show only favorites" option in the app settings on the watch
