[ROM] [P880] [L 5.1.1] Euphoria OS [BETA]
5 stars based on
Usually you see only a short description of the permission e. The permissions technical name is rarely visible to the user. Unless he casts a glance at the Manifestwhere they are stated in plain-text. An mostly up-to-date but far from being complete overview can be found in the Developers Manual.
There's also a Community Wiki on this topic at Stack Exchange — where you can participate, and which also holds some more details. Another good overview with additional hints can be found at AndroidForums. First, permissions are organized in "permission groups".
When installing an app, you see those as captions to the permissions. An up-to-date listing again can be found in the API Reference. Below is an extract with some explanations added. But the relevant stuff to pay the real attention to is found with the permissions themselves.
Another classification is done with protection levels see Developers Reference on Permission Element and protectionLevel. Five levels regulate how permissions are dealt with the "tokens" are for reference in the real permission table below. The permission level assigned to a given permission may change over time, and e.
You can look this up e. In addition to the protection levels, there are additional flags used. A selection of most relevant flags:. For a full list, please refer to the reference on protectionLevel. Again a short extract of the relevant android 6 entwickleroptionen deaktivieren. In below table, "Lv" stands for the protection level"Risk" if filled for the possible risks involved android 6 entwickleroptionen deaktivieren the given permission:.
But the risk has to be seen in connection with the android 6 entwickleroptionen deaktivieren level: Source for the "risk classes" was the already mentioned artikle at AndroidForums. Commost protection levels android 6 entwickleroptionen deaktivieren be found in this Blog article. In short it describes how a permission reveals the requesting app as being dependent on Google services or the existence of the Google Apps on the device: Android DevelopersAndroidForums.
Permissions Usually you see only a short description of the permission e. Permission Groups First, permissions are organized in "permission groups".
This includes vibrator, flashlight, etc. Examples include such as listing running apps, or killing background processes. Includes Barcode Readers and more. These are not permissions that should appear in third-party applications; they protect APIs that are intended only to be used for development purposes. An example shows android 6 entwickleroptionen deaktivieren might android 6 entwickleroptionen deaktivieren access to features not explicitly requested by the app.
This includes audio, the camera, vibrator, etc. Note that phone calls also capture audio but are in a separate more visible permission group.
The main permission here is internet access, but this is also an appropriate group for accessing or modifying any network configuration or other related network operations. This includes both reading and writing of this data which should generally be expressed as two distinct permissions. Many of these are not permissions the user will be expected to understand, and such permissions should generally be marked as "normal" protection level so they don't get displayed.
Android 6 entwickleroptionen deaktivieren can also, however, be used for miscellaneous features that provide access to the operating system, such as writing the global system settings. Access to user dictionaries. Keyboard apps use this e.
Keyboard apps need this to add new terms. Protection Level Another classification is done with protection levels see Developers Reference on Permission Element and protectionLevel. Description normal android 6 entwickleroptionen deaktivieren Low risk or "Standard". These permissions are not android 6 entwickleroptionen deaktivieren to the user on app-install, but tacitly accepted.
These permissions have android 6 entwickleroptionen deaktivieren be explicitly approved by the user on app-install. In most cases, these apps already come pre-installed.
As such can only be installed with root powers, it's rather of low interest to "normal users". These permissions are only intended for developers, and seem to be meant as "developmentOrSignatureOrSystem". A selection of most relevant flags: Flag Description installer this permission can be automatically granted to android 6 entwickleroptionen deaktivieren apps that install packages.
Permissions Again a short extract of the relevant candidates. In below table, "Lv" stands for the protection level"Risk" if filled for the possible risks involved with the given permission: The protection level could be relaxed in the future to support third-party download managers.
This permission is usually used by applications that display location based ads by publishers like Admob Google. Network sy 0 Allows the app to access the download manager and to use it to download files.
Malicious apps can use this to disrupt downloads and access private information. Only accessible by system apps. Network sy 0 Allows the app to access the download manager's android 6 entwickleroptionen deaktivieren functions. This permission can android 6 entwickleroptionen deaktivieren used by applications that display location based ads by publishers like Admob Google. Android 6 entwickleroptionen deaktivieren is also used by applications that want your exact location.
Examples would be Navigation applications, "Check-In" apps like 4square. The documentation of Locus Map gives android 6 entwickleroptionen deaktivieren hint, though: Cases where this is needed in an app ready for endusers should be rare.
Requires "Allow mock locations" to be enabled in android 6 entwickleroptionen deaktivieren options. The application may check the state of your connection before trying to access the internet, and e.
Only in combination with other permissions e. This permission is reserved for system apps. It was introduced with Android 4.
This permission requested or not, no app automatically gets granted those "root powers"; but some "SuperUser apps" can be configured to ignore requests by all apps not having it. For all other apps, the user has to acknowledge their legitimity at least on the first request. Thus an app with this permission does not automatically have root permission — but only obtains them when the user explicitely approves that to the "SuperUser app".
So better be sure you trust its developer and your installation source that far. SurfaceFlinger is part of Android's media framework. It provides a compositor which takes care for rendering in frame buffers so this has to do with graphics.
For details, please see Android. The application may check the state of your connection before trying to access the internet. Only the system can get this permission. An account-manager is the service working behind the scenes and taking care everything works as expected.
According to the API reference, the app doesn't receive any coordinates this way, but rather the android 6 entwickleroptionen deaktivieren of the detected activity — e. Using this service will incur data usage. This is for applications that would authenticate you to their service. An app using this permission usually provides an interface to deal with a certain account type which is not known by the pre-installed Android systemsuch as Dropbox.
As shipped, Android does not know how to login to Dropbox and how to deal with a Dropbox account — so the Dropbox app provides the mechanism. Additionally, an "account authenticator" might restrict android 6 entwickleroptionen deaktivieren actions an app can perform with the account so it would e. More details can be found e. Packages that do not use android. This seems to be an old and possibly deprecated?
For some details, please take a look at this Stack Exchange article. Might be a permission specific to Samsung Touchwiz with "sec" referring to the "seclauncher" ; not sure whether other devices are affected by it. Battery widgets and other battery information tools use this permission. Must be required by an AccessibilityServiceto ensure that only the system can bind to it.
The normal user flow is that a user picks an AppWidget to go into a particular host, thereby giving that host application access to the private data from the AppWidget app. An application that has this permission should honor that contract. Very few applications should need to use this android 6 entwickleroptionen deaktivieren. Must be required by device administration receiver, to ensure that only the system can interact with it.
For further details, also see: What permissions are granted to an app with device administration privileges? Must be required by an InputMethodServiceto ensure android 6 entwickleroptionen deaktivieren only the system can bind to it. Must be required by a RemoteViewsServiceto ensure that only the system can bind to it.