Background execution - Foreground service type

[guymoreillon]

Since Android 10 a foreground service needs to have a type, see https://developer.android.com/about/versions/14/changes/fgs-types-required#short-service.

We've been using FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE in our app, but Google is now suddenly rejecting our app because "Use of FGS is not perceptible to the user when performing Connected Device - Connected Device Other functionality."

I'm not quite sure how Google thinks we can let the user know that our app is using a flic button when the phone's screen is off, but anyway, in your example https://github.com/50ButtonsEach/flic2lib-android?tab=readme-ov-file#background-execution, you don't specify a foreground service type. What would you recommend to use then?

Or do we need to use something like https://developer.android.com/reference/android/companion/CompanionDeviceService#onDeviceAppeared(java.lang.String) to keep our app awake while the flic button is in range?

Any pointer would be much appreciated, thanks

[Emill]

Hmm... Maybe you can write something in the notification of the foreground service that it's listening for button events from your device or similar. I've not seen Google complaining about this before.

And yes the example code should be updated.

You could try to add use of the companion device api but I don't see why Google would require that.

[guymoreillon]

Thanks for the quick reply.

Hmm... Maybe you can write something in the notification of the foreground service that it's listening for button events from your device or similar. I've not seen Google complaining about this before.

I guess they are starting to tighten a few bolts. They certainly have new requirements, such as requesting an actual video showing how the bluetooth device operates with the app (and so does Apple btw).

You could try to add use of the companion device api but I don't see why Google would require that.

As long as I can get the button clicks while the app is in background, I don't care if it means bending left of right, but I was wondering if that would be compatible with the flic lib, or if you foresee any trouble?

[Emill]

After you have paired the Flic button in the normal way, you can add it as a Companion Device to your app by calling the associate method in the Companion Device API with the following AssociationRequest:

new AssociationRequest.Builder()
    .addDeviceFilter(
        new BluetoothDeviceFilter.Builder().setAddress( /* bluetooth device address of flic button as string */ ).build()
    )
    .setSingleDevice(true)
    .build()

The user will then get a popup asking if it's ok to pair this button with the app. No over-the-air data is happening - the Companion Device manager just adds this button to the list it manages for the app of associated companion devices. Having at least such association permits the app to e.g. turn on the screen from the background to start an activity.

[guymoreillon]

Great, thanks for the pointer!

[Emill]

@guymoreillon did you succeed getting past Google Play Store review?

[guymoreillon]

yes, it is happily published

[Emill]

What did you have to change?