{"id":33040,"date":"2016-03-03T17:43:07","date_gmt":"2016-03-03T12:13:07","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=33040"},"modified":"2016-04-17T18:05:18","modified_gmt":"2016-04-17T12:35:18","slug":"android-permission-system","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/android-permission-system\/","title":{"rendered":"Android Permission System And Case Study"},"content":{"rendered":"

How to work with Android Permission System in Android M
\n<\/strong><\/p>\n

To protect the android system and the user’s privacy, Android system<\/a> runs each application in a limited access sandbox. If the application wants to use resources or information outside of its sandbox, the application has to explicitly request permission. Depending on the type of permission the application requests, the system may grant the permission automatically, or the system may ask the user to grant the permission. Android depends on two types of permission to decide to grant or request permission, \u00a0Normal and Dangerous Permissions.<\/p>\n

Declaring Permission:<\/strong><\/p>\n

You need to declare required permissions in Application manifest file.
\nDepending on the sensitiveness of the permission, the system might grant the permission automatically, or the device user might have to grant the request. For example, if your\u00a0application requests permission to turn on the device’s flashlight, the system grants that permission automatically. But if your\u00a0application needs to read the user’s contacts, the system asks the user to approve that permission. Depending on the platform version, the user grants the permission either when they install the\u00a0application (on Android 5.1 and lower) or while running the\u00a0application (on Android 6.0 and higher).<\/p>\n

Add Permissions to Manifest:<\/strong><\/p>\n

To declare that your\u00a0application needs a permission, put a\u00a0<uses-permission>\u00a0element in your\u00a0application manifest file, as a child of the top-level\u00a0<manifest>\u00a0element. For example, an\u00a0application that needs to send SMS messages would have this line in the manifest:<\/p>\n

[code]<\/p>\n

<manifest xmlns:android="http:\/\/schemas.android.com\/apk\/res\/android"
\n\u00a0 \u00a0 \u00a0 \u00a0 package="com.example.ttnd">
\n\u00a0 \u00a0 <uses-permission android:name="android.permission.SEND_SMS"\/>
\n\u00a0 \u00a0
\n\u00a0 \u00a0 <application …>
\n\u00a0 \u00a0 \u00a0 \u00a0 …
\n\u00a0 \u00a0 <\/application>
\n<\/manifest>
\n [\/code]<\/p>\n

Requesting Permissions at Runtime:<\/strong><\/p>\n

The Beginning in Android 6.0 (API level 23), users grant permissions to\u00a0applications while the\u00a0application is running, not when they install the application. This approach streamlines the\u00a0application install process, since the user does not need to grant permissions when they install or update the application. It also gives the user more control over the application’s functionality; for example, a user could choose to give a camera\u00a0application access to the camera but not to the device location. The user can revoke the permissions at any time, by going to the application’s Settings screen.<\/p>\n

Android System permissions are divided into two categories, Normal<\/strong>\u00a0and Dangerous<\/strong> permission:
\nThe Normal<\/strong> permissions do not directly risk the user’s privacy. If your\u00a0application lists a normal permission in its manifest, the system grants the permission automatically. The Dangerous<\/strong> permissions can give the\u00a0application access to the user’s confidential data. If you list a dangerous permission, the user has to explicitly give approval to your application.<\/p>\n