Thanks to CommonsWare's comment, I quickly found the answer:
[...] The only way to start a service is if someone starts it, and the OS does not do it on its own.
I was so blinded that the OS was responsible for this, that I did not notice that it was done specifically as an undocumented function inherited from the previous version of the application.
There was a BroadcastReceiver, which listened to the action android.intent.action.BOOT_COMPLETED. This receiver, among other things, restarted the service at startup when the application was not properly disconnected.
Thank you CommonsWare for your help.
Update
After the BroadcastReceiver does not listen to the BOOT_COMPLETE action, I still experience the same behavior.
, BroadcastReceiver SIP, WIFI , . Wether , , , .
- : BroadcastReceiver android.net.conn.CONNECTIVITY_CHANGE , , , , .