The permissions of Android Apps have changed. Previously, they were acquired during installation, but now they are requested during runtime. It is a little unclear here.

  android, question

When a writer declares permissions, he configures them in manifest.

In actual use, such as the use of MEIZU and hammer, it is to use specific permissions, such as requesting location permissions when positioning is needed, and requesting Bluetooth when Bluetooth control is used. Isn’t this a runtime request?

The new version of the system runtime request is What Do You Mean?

And Google’s engineers said that most of the previous requests were for all permissions during installation, while the new version was requested at runtime. If the old app continued to use the old request method, that is, requesting all permissions during installation, there might be problems.

This one is very confusing to me. What I know about declaring permissions is that it is configured in manifest. Is there any other method? Or will Android M be followed? If not, what do you mean by the old permission application method and the new method? There is no difference in writing code for developers. Why are there compatibility problems?

Just like your map application, it definitely involves network connection and location functions. Previously, all the required permissions were agreed upon at the time of installation. Now, it is divided into many runtime requests. As for the hammers and MEIZU you mentioned, they have not been used. Maybe they have changed them themselves