Android Mobile SDK to easily integrate communication features (WebRTC, messaging, presence, voice, video, screensharing) based on RestComm into native Mobile Applications
When we receive messages while the app is in the background, we are starting the service in foreground. When service's onStartCommand is called, we need to call startForeground with notification. Notification data is:
Title:
Restcomm Connect
Message:
Background initialization...
When we are connected to Restcomm, we are replacing an existing notification with the "Message" notification or "Call" notification.
For the messages, while phone is locked, when we receive push we get something like:
message:
Background initialization...
Hey Oggie test
message:
Background initialization...
Hey Oggie test 2
...
The idea is to not starting the service if message counter is > 0
When we receive messages while the app is in the background, we are starting the service in foreground. When service's onStartCommand is called, we need to call startForeground with notification. Notification data is: Title: Restcomm Connect Message: Background initialization...
When we are connected to Restcomm, we are replacing an existing notification with the "Message" notification or "Call" notification.
For the messages, while phone is locked, when we receive push we get something like:
... The idea is to not starting the service if message counter is > 0