Hi,
I'm trying to validate background phone-message handling in a Connect IQ watch-app on a real FR265.
Environment:
- Device: Forerunner 265
- CIQ SDK: 8.4.1
- App type: watch-app
- Permissions: Background + Communications
- App class is marked :background
- getServiceDelegate() returns a ServiceDelegate
- Android side uses the Garmin Mobile SDK and sendMessage(...) to the correct app id
- Foreground transport is confirmed working with the same app id and the same phone/watch setup
What I expect:
- App launches once and calls Background.registerForPhoneAppMessageEvent()
- App is no longer in foreground
- Android sends a message
- ServiceDelegate.onPhoneAppMessage() runs in background
- Background data is passed back via Background.exit(...) / onBackgroundData(...), or at least some persisted evidence is visible when reopening the app
What I actually see:
- Android sendMessage(...) returns SUCCESS
- Foreground-only builds receive the message correctly
- But a background-only build (no foreground phone-message registration at all) shows no evidence after reopening:
- msg=0
- src=waiting
- rx=0
- mem=-1
- The app still shows that the background phone message event is registered
Important control result:
- A foreground-only variant of the same app id receives messages fine on this same FR265, including 512-byte payloads.
- So the general phone -> Garmin Connect -> watch path is working.
- The missing piece is specifically the background ServiceDelegate path.
Question:
Is Background.registerForPhoneAppMessageEvent() expected to wake a watch-app background service on FR265 / CIQ 5.2 when the app is not in the foreground?
If yes:
- Is there any extra requirement beyond Background permission + :background + getServiceDelegate() + registerForPhoneAppMessageEvent()?
- Is there any known device/firmware limitation where delivery is deferred until the app is foreground again?
- Does anyone have a minimal real-device example of ServiceDelegate.onPhoneAppMessage() working in the background?
Thanks.