The question is stupid :)

For example, I wrote an application that will be turned off by my BroadcastReceiver when the device boots. Thousands of users will stay with bricks. Will Google Play block the app? How will he know about it?

  • 2
    why do you need it? - Mikhail Vaysman
  • one
    @MikhailVaysman something that just because of women will not do! - 0andriy

2 answers 2

First, the application does not have the ability to turn off the non-rooted device by software.

Secondly, it is not a brick, a qualified user will cope with this situation.

Secondly, Google will find out about it quite quickly: there is a Report button on Google Play. Most likely the developer account will be blocked.

    You can programmatically reboot a device only when at least one of two conditions is fulfilled:

    • The device is rooted and your application is provided with a root-parva;
    • Your application is a device administrator .

    In my opinion, users with rooted devices should, a priori, be aware of the consequences of granting root-rights to an application (therefore, sszb). To all this, you can give root-rights to the application only once . In this case, after a couple of reboots, the user simply will not give root-rights and will remove the application.

    The situation is similar to adding an application to the device administrators category.

    As for Google Play, I can only assume that after repeated calls to support users, the application will be blocked (and maybe even the entire account). And then no one will even listen to tales about the fact that this is the erroneous behavior of your application.

    Regarding the brick: the brick is a state of no return, and in the situation you cited, the problem is solved by rolling back to the previous backup, or by a full wipe.