What happens to a bound service during config changes and multiple clients?

This tests bound service reference counting and client lifecycle coupling. When a config change destroys an Activity, its binding is torn down; if that was the sole binding and the service was not started, the service is destroyed and recreated only when the new Activity rebinds. With multiple bound clients, the service stays alive until the final unbind because the system tracks active connections. A red flag is claiming the service survives config changes automatically or that one unbind kills it regardless of other clients.