The Android documentation contains the following description of the adb grant and adb revoke commands.  

    grant &lt;PACKAGE_PERMISSION&gt;

Grant permissions to applications. Only optional permissions the application has declared can be granted.

    revoke &lt;PACKAGE_PERMISSION&gt;

Revoke permissions to applications. Only optional permissions the application has declared can be revoked.

**Can anybody please give an example of the correct syntax to use them?**

I assume that &lt;PACKAGE_PERMISSION&gt; would be a permission like `android.permission.WRITE_EXTERNAL_STORAGE`, or perhaps just `WRITE_EXTERNAL_STORAGE`.  Well I tried those, and several others and I cannot get it to work.

I also tried (to no avail) several combinations of package and permission, which makes more sense to me (this sounds like a command that would modify a permission on one package, not all) 


How do I use adb grant or adb revoke?

I&#39;m updating our app to use the new M runtime permissions system.
It&#39;s all working except for onRequestPermissionsResult(). I need to check a permission on a button press, and if it&#39;s successful, send a text message. When I grant permission to do it, the dialog closes, but it doesn&#39;t trigger the Send Text until I press the button again.

I&#39;ve debugged and set breakpoints in the onRequestPermissionsResult() method but it never goes into it.

This method gets called first:

        private void askForPermission() {
        String[] permissions = new String[]{Manifest.permission.SEND_SMS};
        ActivityCompat.requestPermissions(getActivity(), permissions, PERMISSIONS_CODE);
    }

And then my callback looks like this:

        @Override
    public void onRequestPermissionsResult(int requestCode, String[] permissions, int[] grantResults) {
        super.onRequestPermissionsResult(requestCode, permissions, grantResults);

        if (requestCode == PERMISSIONS_CODE) {
            for (int i = 0; i &lt; permissions.length; i++) {
                String permission = permissions[i];
                int grantResult = grantResults[i];

                if (permission.equals(Manifest.permission.SEND_SMS)) {
                    if (grantResult == PackageManager.PERMISSION_GRANTED) {
                        onPPSButtonPress();
                    } else {
                        requestPermissions(new String[]{Manifest.permission.SEND_SMS}, PERMISSIONS_CODE);
                    }
                }
            }
        }
    }

Has anybody run into a similar issue?
Appreciate any help with this.
Thanks

Android M Permissions: onRequestPermissionsResult() not being called

User is reporting my app crashes with this error trace

    java.lang.SecurityException: com.android.phone from uid 10134 not allowed to perform OP_READ_PHONE_STATE
    at android.os.Parcel.readException(Parcel.java:1620)
    at android.os.Parcel.readException(Parcel.java:1573)
    at com.android.internal.telephony.IPhoneSubInfo$Stub$Proxy.getVoiceMailNumberForSubscriber(IPhoneSubInfo.java:858)
    at android.telephony.TelephonyManager.getVoiceMailNumber(TelephonyManager.java:2383)
    at android.telephony.TelephonyManager.getVoiceMailNumber(TelephonyManager.java:2366)

So far only one user has reported this problem.  Several thousand other users are running this version of the app with no apparent problems.

The exception is thrown when we call  `TelephonyManager.getVoiceMailNumber()`.  This operation is documented as required the `READ_PHONE_STATE` permission, which has absolutely, positively been granted.

I tracked down the `OP_READ_PHONE_STATE` permission to the `android.apps.AppOpsManager` class but can not figure out exactly what it is unhappy about.

Can anyone explain just what is happening and what needs to be done to fix things.

Thanks,
-Ken

SecurityException: not allowed to perform OP_READ_PHONE_STATE

I need to check programmatically if the auto start permission for my app in MIUI phone is on or off. Facebook and whatsapp have this permission already enabled by default , how can I do so?

How to check MIUI autostart permission programmatically?

In **Android M (Preview)** the user can choose a specific app and retreive specific permission.
 
So I am asking *How to check Grants Permissions at Run-Time*?


How to check Grants Permissions at Run-Time?

&lt;br /&gt;
I am maintaining one existing (very-huge, very-sensitive) Android Application. &lt;br /&gt;
The other day, I have received an email from my client that, the Application might be declaring the Permissions that are not actively being used.

For example, they wants me to remove &quot;WRITE_EXTERNAL_STORAGE&quot; permission.&lt;br /&gt;
I have removed it and compiled it and run the App. There is NO error at all. &lt;br /&gt;
But, just because of that, I don&#39;t think I can assume that permission is not actively being used at all.

My question is **&quot;Is there anyway I can easily and simply check the permission if it is actively being used ?&quot;**

Frankly, I don&#39;t want to go through every little detail aspect of that application just to fine out the permission is required or not.&lt;br /&gt;
I just don&#39;t have time.

My goal is check if the permission is actively being used. If not, remove the permission.&lt;br /&gt;
Hope there is an less-time consuming way for that.

Regards



How to check if Android Permission is actually being used?

Lately we have suddenly been seeing a few of the following stack traces. Why could that be? This is from when the app tries to move an audio commentary service into the foreground with a media notification and everything.


    java.lang.SecurityException: Permission Denial: startForeground from pid=1824, uid=10479 requires android.permission.FOREGROUND_SERVICE
        at android.os.Parcel.createException(Parcel.java:1942)
        at android.os.Parcel.readException(Parcel.java:1910)
        at android.os.Parcel.readException(Parcel.java:1860)
        at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:5198)
        at android.app.Service.startForeground(Service.java:695)
        at com.example.app.services.AudioService.setUpMediaNotification(AudioService.java:372)
        at com.example.app.services.AudioService.setUpAndStartAudioFeed(AudioService.java:328)
        at com.example.app.services.AudioService.onStartCommand(AudioService.java:228)
        at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3667)
        at android.app.ActivityThread.access$1600(ActivityThread.java:199)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1681)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:193)
        at android.app.ActivityThread.main(ActivityThread.java:6669)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
     Caused by: android.os.RemoteException: Remote stack trace:
        at com.android.server.am.ActivityManagerService.enforcePermission(ActivityManagerService.java:9186)
        at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked(ActiveServices.java:1189)
        at com.android.server.am.ActiveServices.setServiceForegroundLocked(ActiveServices.java:870)
        at com.android.server.am.ActivityManagerService.setServiceForeground(ActivityManagerService.java:20434)
        at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:976)



Permission Denial: startForeground requires android.permission.FOREGROUND_SERVICE

I am currently working on an application that requires several &quot;dangerous&quot; permissions. So I tried adding &quot;ask for permission&quot; as required in Android Marshmallow(API Level 23), but couldn&#39;t find how to do it. 

How can I ask for permission using new permission model in my app?



Android marshmallow request permission?

I&#39;m trying to write code to send an SMS from an Android app, but when I try to send the SMS it sends me back the error:

&lt;!-- language: lang-none --&gt;

    09-17 18:37:29.974  12847-12847/**.**.****E/AndroidRuntime﹕ FATAL EXCEPTION: main
    Process: **.**.****, PID: 12847
    java.lang.SecurityException: Sending SMS message: uid 10092 does not have android.permission.SEND_SMS.
            at android.os.Parcel.readException(Parcel.java:1599)
            at android.os.Parcel.readException(Parcel.java:1552)
            at com.android.internal.telephony.ISms$Stub$Proxy.sendTextForSubscriber(ISms.java:768)
            at android.telephony.SmsManager.sendTextMessageInternal(SmsManager.java:310)
            at android.telephony.SmsManager.sendTextMessage(SmsManager.java:293)
            at **.**.****.MainActivity$3.onClick(MainActivity.java:70)
            at android.view.View.performClick(View.java:5198)
            at android.view.View$PerformClick.run(View.java:21147)
            at android.os.Handler.handleCallback(Handler.java:739)
            at android.os.Handler.dispatchMessage(Handler.java:95)
            at android.os.Looper.loop(Looper.java:148)
            at android.app.ActivityThread.main(ActivityThread.java:5417)
            at java.lang.reflect.Method.invoke(Native Method)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

I checked but I have the permissions in the manifest, as follows:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;manifest xmlns: Android=&quot;http://schemas.android.com/apk/res/Android&quot;
    package=&quot;**.**.****&quot;&gt;

    &lt;uses-permission android:name=&quot;android.permission.SEND_SMS&quot;/&gt;
    &lt;uses-feature android:name=&quot;android.hardware.telephony&quot;
        android:required=&quot;true&quot;/&gt;

    &lt;application
        android:exported=&quot;true&quot;
        android:allowBackup=&quot;true&quot;
        android:icon=&quot;@mipmap/ic_launcher&quot;
        android:label=&quot;@string/app_name&quot;
        android:theme=&quot;@style/AppTheme&quot;&gt;
        &lt;activity
            android:name=&quot;.MainActivity&quot;
            android:label=&quot;@string/app_name&quot;
            android:screenOrientation=&quot;portrait&quot;&gt;
            &lt;intent-filter&gt;
                &lt;action android:name=&quot;android.intent.action.MAIN&quot; /&gt;

                &lt;category android:name=&quot;android.intent.category.LAUNCHER&quot; /&gt;
            &lt;/intent-filter&gt;
        &lt;/activity&gt;
    &lt;/application&gt;


&lt;/manifest&gt;

I searched the internet but all the errors were about the `&lt;uses-permission/&gt;` syntax, could you help me please?


Android permission doesn&#39;t work even if I have declared it

I know that Android 6.0 has new permissions and I know I can call them with something like this 

    if (ContextCompat.checkSelfPermission(this, Manifest.permission.WRITE_EXTERNAL_STORAGE) !=
        PackageManager.PERMISSION_GRANTED) {
        ActivityCompat.requestPermissions(this,
            new String[] { 
                Manifest.permission.WRITE_EXTERNAL_STORAGE
            }, PERMISSION_WRITE_STORAGE);
    }

Today I saw a Google app which needs 3 permissions: contacts, sms and camera. It&#39;s making a page 1-3 and calls them all together at the same time to activate.

Can anybody tell me how I can call 4 permissions to activate at the same time like sms, camera, contacts and storage?


Example (forgot the name of the google app :( )   
The app needs sms,contacts and camera 

the app asked me (and made a dialog page1-3) activate sms, activate contacts and then camera. 
So this google app was calling all 3 required permissions together and my question is how can i achive the same ?





Android 6.0 multiple permissions

I&#39;m trying to make an app like, when a call comes to the phone I want to detect the number. Below is what I tried, but it&#39;s not detecting incoming calls. 

I want to run my `MainActivity` in background, how can I do that?

I had given the permission in `manifest` file.
  
    &lt;uses-permission android:name=&quot;android.permission.READ_PHONE_STATE&quot;/&gt;

Is there anything else should I provide in the manifest?

    public class MainActivity extends Activity {
        @Override
        protected void onCreate(Bundle savedInstanceState) {
            super.onCreate(savedInstanceState);
            setContentView(R.layout.test_layout);
       }

       public class myPhoneStateChangeListener extends PhoneStateListener {
           @Override
           public void onCallStateChanged(int state, String incomingNumber) {
               super.onCallStateChanged(state, incomingNumber);
               if (state == TelephonyManager.CALL_STATE_RINGING) {
                   String phoneNumber =   incomingNumber;
               }
           }
       }
    }

How to detect incoming calls, in an Android device?

I get the following Exception running my app:

    java.net.SocketException: Permission denied (maybe missing INTERNET permission)

How do I solve the missing permission problem?


What permission do I need to access Internet from an Android application?

I want to check a permission inside a fragment. 



my code:

            // Here, thisActivity is the current activity
            if (ContextCompat.checkSelfPermission(getActivity(),
                    Manifest.permission.ACCESS_FINE_LOCATION)
                    != PackageManager.PERMISSION_GRANTED) {


                // Should we show an explanation?
                if (ActivityCompat.shouldShowRequestPermissionRationale(getActivity(),
                        android.Manifest.permission.ACCESS_FINE_LOCATION)) {

                    // Show an explanation to the user *asynchronously* -- don&#39;t block
                    // this thread waiting for the user&#39;s response! After the user
                    // sees the explanation, try again to request the permission.

                } else {

                    // No explanation needed, we can request the permission.

                    ActivityCompat.requestPermissions(getActivity(),
                            new String[]{android.Manifest.permission.ACCESS_FINE_LOCATION},
                            1);



                    // MY_PERMISSIONS_REQUEST_READ_CONTACTS is an
                    // app-defined int constant. The callback method gets the
                    // result of the request.
                }
            }

but `onRequestPermissionsResult` not called after allow or deny.



    @Override
    public void onRequestPermissionsResult(int requestCode,
                                           String permissions[], int[] grantResults) {
        switch (requestCode) {
            case 1: {
                Log.e(&quot;test&quot;,&quot;0&quot;);
                // If request is cancelled, the result arrays are empty.
                if (grantResults.length &gt; 0
                        &amp;&amp; grantResults[0] == PackageManager.PERMISSION_GRANTED) {

                    // permission was granted, yay! Do the
                    // contacts-related task you need to do.
                    //yes

                    Log.e(&quot;test&quot;,&quot;1&quot;);

                    Intent intent = new Intent(getActivity(), MapsActivity.class);
                    intent.putExtra(&quot;latitude&quot;, 35.694828);
                    intent.putExtra(&quot;longitude&quot;, 51.378129);
                    startActivity(intent);

                } else {
                    utilityFunctions.showSweetAlertWarning(getActivity(),r.getString(R.string.str_warning_title_empty),
                            r.getString(R.string.str_you_must_allow_this_permission_toast),
                            r.getString(R.string.str_warning_btn_login));

                    Log.e(&quot;test&quot;,&quot;2&quot;);
                }
                return;
            }

            // other &#39;case&#39; lines to check for other
            // permissions this app might request
        }
    }

How to check permission in fragment

In Android Marshmallow, permissions should be requested at runtime when they are needed, instead of all at once when an app is installed. However, I can only seem to request permissions from an Activity, which is a problem since my app contains only Services. (Why is that, you might ask? The app has an Android Wear watch face bundled inside, and all the phone does is look up photos nearby to send to the watch - no Activity needed. But it does require location permissions.)

So, is there any way to request permissions from a Service? Or somehow force the permissions to be granted at install time as in the past?

How to request permissions from a Service in Android Marshmallow

I have a GPS app that already requests `ACCESS_FINE_LOCATION` permission in the manifest, now I want to add a library (MoPub)  that requires `ACCESS_COARSE_LOCATION`.

Am I correct in assuming that `ACCESS_FINE_LOCATION` is enough, and I can leave out `ACCESS_COARSE_LOCATION` from my manifest?

If I have ACCESS_FINE_LOCATION already, can I omit ACCESS_COARSE_LOCATION?

Facebook, Evernote, Pocket - all apps get this permission on Android 6.0 automatically, even though they are targeting 23 (`targetSdkVersion=23`).

There has been a lot of documentation regarding the new Marshmallow permission model. One of them is `SYSTEM_ALERT_WINDOW` been &#39;promoted&#39; to &#39;above dangerous&#39;  permission class thus requiring a special user intervention in order for apps to be granted with those. If the app has `targetSdkVersion` 22 or lower, app gets this permission automatically (if requested in the manifest). 

However, I&#39;ve noticed some apps that get this permission, without needing to send the user to the setting special page of `Draw over other apps` permission. I saw Facebook, Evernote, Pocket - and perhaps there are more.

Anyone knows how an app can be granted this permission without the user go through `Settings -&gt; Apps -&gt; Draw over other apps`?

Thanks

SYSTEM_ALERT_WINDOW - How to get this permission automatically on Android 6.0 and targetSdkVersion 23

Which permissions need for requesting permissions at run time of API 23?

List of Android permissions normal permissions and dangerous permissions in API 23?

I am building an Android app that will track the user&#39;s geolocation and draw their route on a map.

I am using the Google Play Services location API, as described [here][1].

It is intuitive that my application requires the `ACCESS_FINE_LOCATION` permission, which I put in the manifest:

    &lt;uses-permission android:name=&quot;android.permission.ACCESS_FINE_LOCATION&quot;/&gt;

Do I also need the `ACCESS_COARSE_LOCATION` permission?
What&#39;s the use case where I need the coarse location?


  [1]: http://developer.android.com/training/location/index.html

When should I use ACCESS_COARSE_LOCATION permission?

There is a lint warning in AS with regards to `android.permission.WRITE_EXTERNAL_STORAGE`. The warning says that the permission will no longer provide write access when targeting Android 10 and above. Removal of the said permission can still write in internal storage folder `Pictures/MY_APP_NAME` to save images, but it only works on Android 10 (SDK 29) and/or above (haven&#39;t tested yet on Android R). When I tested it again on lower version such as Android M (SDK 23), saving images stop working so I decided to return the `android.permission.WRITE_EXTERNAL_STORAGE` thus the warning shows up again. Is it possible that the lint is just false positive that incorrectly diagnosed the problem on different cases? Because currently my support SDK starts with 21 up to the latest which is 30 but the lint only point out that it is no longer needed when targeting Android 10 (SDK 29) and did not consider looking back at the project&#39;s minimum SDK support.

WRITE_EXTERNAL_STORAGE when targeting Android 10

I have some receivers declared in my AndroidManifest :

    &lt;!-- no warning --&gt;
    &lt;receiver
        android:name=&quot;.receivers.TriggerMonitoringBootReceiver&quot;
        android:enabled=&quot;false&quot;&gt;
        &lt;intent-filter&gt;
            &lt;action android:name=&quot;android.intent.action.BOOT_COMPLETED&quot; /&gt;
        &lt;/intent-filter&gt;
    &lt;/receiver&gt;
    
    &lt;!-- no warning --&gt;
    &lt;receiver
        android:name=&quot;.receivers.ScanResultsReceiver&quot;
        android:enabled=&quot;false&quot;&gt;
        &lt;intent-filter&gt;
            &lt;action android:name=&quot;android.net.wifi.SCAN_RESULTS&quot; /&gt;
        &lt;/intent-filter&gt;
    &lt;/receiver&gt;
    
    &lt;!-- warning : Exported receiver does not require permission--&gt;
    &lt;receiver
        android:name=&quot;.receivers.BatteryMonitoringReceiver&quot;
        android:enabled=&quot;false&quot;&gt;
        &lt;intent-filter&gt;
            &lt;action android:name=&quot;@string/intent_action_setup_alarm&quot; /&gt;
            &lt;action android:name=&quot;@string/intent_action_cancel_alarm&quot; /&gt;
            &lt;action android:name=&quot;@string/intent_action_monitor&quot; /&gt;
        &lt;/intent-filter&gt;
    &lt;/receiver&gt;



The first one is meant to receive a `BOOT_COMPLETED` action. The second is meant to receive `android.net.wifi.SCAN_RESULTS`. The third one is meant to receive some actions I broadcast (intent_action_monitor) and some actions broadcasted by the `AlarmManager` (intent_action_setup_alarm etc).

Two questions:

 - Why don&#39;t I get the warning on all receivers? 
 - What permissions do I need to set *for receivers meant to receive from system services to correct the warning* (I understand what it is about and I don&#39;t want anyone to use my receivers anyway) ? _**Will**_ `exported=&quot;false&quot;` _**do** for boot receivers, wifi receivers, alarm receivers etc_?  
I thought of using a custom permission with `android:protectionLevel=&quot;signatureOrSystem&quot;` but the docs advise against both this [protection level][1] and [custom permissions][2]. So how I should handle this warning ?

Links to the docs and/or some code will be much appreciated.


  [1]: http://developer.android.com/guide/topics/manifest/permission-element.html#plevel
  [2]: http://developer.android.com/training/articles/security-tips.html#Permissions

android - &quot;Exported receiver does not require permission&quot; on receivers meant to receive from system services

I have a question regarding the new Android 6.0 (Marshmallow) release:

Is it achievable to display the *permission screen* for a specific app via an Intent or something similar?

[![Android M Permission Screen][1]][1]

It&#39;s possible to display the app settings with the following code - is there an analog solution for directly opening the permission screen?

    startActivity(new Intent(android.provider.Settings.ACTION_APPLICATION_DETAILS_SETTINGS,
    Uri.fromParts(&quot;package&quot;, getPackageName(), null)));

I already did some research on this, but I wasn&#39;t able to find a proper solution.

  [1]: http://i.stack.imgur.com/H4GxJ.png



How can I programmatically open the permission screen for a specific app on Android 6.0 (Marshmallow)?

I am getting

&gt; open failed: `EACCES (Permission denied)`

on the line `OutputStream myOutput = new FileOutputStream(outFileName);`

I checked the root, and I tried `android.permission.WRITE_EXTERNAL_STORAGE`.

How can I fix this problem?

    try {
        InputStream myInput;

        myInput = getAssets().open(&quot;XXX.db&quot;);

        // Path to the just created empty db
        String outFileName = &quot;/data/data/XX/databases/&quot;
                + &quot;XXX.db&quot;;

        // Open the empty db as the output stream
        OutputStream myOutput = new FileOutputStream(outFileName);

        // Transfer bytes from the inputfile to the outputfile
        byte[] buffer = new byte[1024];
        int length;
        while ((length = myInput.read(buffer)) &gt; 0) {
            myOutput.write(buffer, 0, length);
        }

        // Close the streams
        myOutput.flush();
        myOutput.close();
        myInput.close();
        buffer = null;
        outFileName = null;
    }
    catch (IOException e1) {
        // TODO Auto-generated catch block
        e1.printStackTrace();
    }


Exception &#39;open failed: EACCES (Permission denied)&#39; on Android

I&#39;m trying to get my app ready for the new Android M permissions changes and found some weird behaviour. My app uses the Camera intent mechanism to allow the user to get a picture form the camera. But in another activity needs to make use of the camera itself with Camera permission (because of a library dependency card.io that requires this).

However with M in the activity that only needs a camera intent when I try to launch the Camera intent I see the following crash (this does not happen if I remove the Camera permission from the Manifest),

    &gt; 09-25 21:57:55.260 774-8053/? I/ActivityManager: START u0
    &gt; {act=android.media.action.IMAGE_CAPTURE flg=0x3000003
    &gt; pkg=com.google.android.GoogleCamera
    &gt; cmp=com.google.android.GoogleCamera/com.android.camera.CaptureActivity
    &gt; (has clip) (has extras)} from uid 10098 on display 0 09-25
    &gt; 21:57:55.261 774-8053/? W/ActivityManager: Permission Denial: starting
    &gt; Intent { act=android.media.action.IMAGE_CAPTURE flg=0x3000003
    &gt; pkg=com.google.android.GoogleCamera
    &gt; cmp=com.google.android.GoogleCamera/com.android.camera.CaptureActivity
    &gt; (has clip) (has extras) } from null (pid=-1, uid=10098) with revoked
    &gt; permission android.permission.CAMERA 09-25 21:57:55.263 32657-32657/?
    &gt; E/ResolverActivity: Unable to launch as uid 10098 package
    &gt; com.example.me.mycamerselectapp, while running in android:ui 09-25
    &gt; 21:57:55.263 32657-32657/? E/ResolverActivity:
    &gt; java.lang.SecurityException: Permission Denial: starting Intent {
    &gt; act=android.media.action.IMAGE_CAPTURE flg=0x3000003
    &gt; pkg=com.google.android.GoogleCamera
    &gt; cmp=com.google.android.GoogleCamera/com.android.camera.CaptureActivity
    &gt; (has clip) (has extras) } from null (pid=-1, uid=10098) with revoked
    &gt; permission android.permission.CAMERA 09-25 21:57:55.263 32657-32657/?
    &gt; E/ResolverActivity:     at
    &gt; android.os.Parcel.readException(Parcel.java:1599) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.os.Parcel.readException(Parcel.java:1552) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.app.ActivityManagerProxy.startActivityAsCaller(ActivityManagerNative.java:2730)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; android.app.Instrumentation.execStartActivityAsCaller(Instrumentation.java:1725)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; android.app.Activity.startActivityAsCaller(Activity.java:4047) 09-25
    &gt; 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ResolverActivity$DisplayResolveInfo.startAsCaller(ResolverActivity.java:983)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ResolverActivity.safelyStartActivity(ResolverActivity.java:772)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ResolverActivity.onTargetSelected(ResolverActivity.java:754)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ChooserActivity.onTargetSelected(ChooserActivity.java:305)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ResolverActivity.startSelected(ResolverActivity.java:603)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ChooserActivity.startSelected(ChooserActivity.java:310)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.app.ChooserActivity$ChooserRowAdapter$2.onClick(ChooserActivity.java:990)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; android.view.View.performClick(View.java:5198) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.view.View$PerformClick.run(View.java:21147) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.os.Handler.handleCallback(Handler.java:739) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.os.Handler.dispatchMessage(Handler.java:95) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.os.Looper.loop(Looper.java:148) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; android.app.ActivityThread.main(ActivityThread.java:5417) 09-25
    &gt; 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; java.lang.reflect.Method.invoke(Native Method) 09-25 21:57:55.263
    &gt; 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
    &gt; 09-25 21:57:55.263 32657-32657/? E/ResolverActivity:     at
    &gt; com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) 09-25
    &gt; 21:57:55.286 1159-1159/? I/Keyboard.Facilitator: onFinishInput() 09-25
    &gt; 21:57:55.297 32657-32676/? E/Surface: getSlotFromBufferLocked: unknown
    &gt; buffer: 0xaec352e0 09-25 21:57:55.344 325-349/? V/RenderScript:
    &gt; 0xb3693000 Launching thread(s), CPUs 4 09-25 21:57:57.290 325-349/?
    &gt; E/Surface: getSlotFromBufferLocked: unknown buffer: 0xb3f88240

Is this a known problem with Android M? And more importantly how do I work around this?

&lt;edit&gt;
in the manifest I have the following,

    &lt;uses-permission android:name=&quot;android.permission.CAMERA&quot; /&gt;

and this is the code I use to let the user click a pic with the Camera and/or select an image

    public static Intent openImageIntent(Context context, Uri cameraOutputFile) {
    
        // Camera.
        final List&lt;Intent&gt; cameraIntents = new ArrayList&lt;Intent&gt;();
        final Intent captureIntent = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
        final PackageManager packageManager = context.getPackageManager();
        final List&lt;ResolveInfo&gt; listCam = packageManager.queryIntentActivities(captureIntent, 0);
        for(ResolveInfo res : listCam) {
            final String packageName = res.activityInfo.packageName;
            final Intent intent = new Intent(captureIntent);
            intent.setComponent(new ComponentName(res.activityInfo.packageName, res.activityInfo.name));
            intent.setPackage(packageName);
            intent.putExtra(MediaStore.EXTRA_OUTPUT, cameraOutputFile);
            cameraIntents.add(intent);
        }
    
        // Filesystem.
        final Intent galleryIntent = new Intent();
        galleryIntent.setType(&quot;image/*&quot;);
        galleryIntent.setAction(Intent.ACTION_GET_CONTENT);
    
        // Chooser of filesystem options.
        final Intent chooserIntent = Intent.createChooser(galleryIntent, &quot;Take or select pic&quot;);
    
        // Add the camera options.
        chooserIntent.putExtra(Intent.EXTRA_INITIAL_INTENTS, cameraIntents.toArray(new Parcelable[]{}));
        return chooserIntent;
    }

I call the `openImageIntent()` on a button click in my activity. When I do not have the CAMERA permission in my app it works fine, but with that added I get the exception posted above.

        @Override
        public void onClick(View v) {
            Intent picCaptureIntenet = openImageIntent(MainActivity.this, getTempImageFileUri(MainActivity.this));
            try {
                startActivityForResult(picCaptureIntenet, 100);
            } catch(Exception e) {
                Toast.makeText(MainActivity.this, e.getMessage(), Toast.LENGTH_SHORT).show();
            }
        }

&lt;/edit&gt;



Android M Camera Intent + permission bug?

Using adb, how can I find out the which permissions an Android application requires?

Because I want to display the permissions of multiple applications on different devices, viewing them in `Google Play` or `Settings` &gt; `Applications manager` requires too much manual work.

Listing permissions of Android application via adb

I&#39;ve been trying to encrypt files and write those files back on to the same place. But I got the error message saying `&quot;java.io.FileNotFoundException: /storage/emulated/0/New file.txt: open failed: EACCES (Permission denied)&quot;.`

My `Manifest` file is this 

    &lt;manifest xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
    package=&quot;com.example.tdk.mytestapplication2&quot;&gt;

    &lt;uses-permission android:name=&quot;android.permission.READ_EXTERNAL_STORAGE&quot; /&gt;
    &lt;uses-permission android:name=&quot;android.permission.WRITE_EXTERNAL_STORAGE&quot;/&gt;


    &lt;application
        android:allowBackup=&quot;true&quot;

I think I have provided correct permission there. And the code I am using to encrypt files is this. 

    public static void encrypt(SecretKey secretKey, String filePath){
        try {
            // Here you read the cleartext.
            FileInputStream fis = new FileInputStream(filePath);
            // This stream write the encrypted text. This stream will be wrapped by another stream.
            FileOutputStream fos = new FileOutputStream(filePath);

            // Create cipher
            Cipher cipher = Cipher.getInstance(&quot;AES&quot;);
            cipher.init(Cipher.ENCRYPT_MODE, secretKey);
            // Wrap the output stream
            CipherOutputStream cos = new CipherOutputStream(fos, cipher);

            // Write bytes
            int b;
            byte[] d = new byte[8];
            while ((b = fis.read(d)) != -1) {
                cos.write(d, 0, b);
            }

            // Flush and close streams.
            cos.flush();
            cos.close();
            fis.close();

        }catch(IOException e){
            e.printStackTrace();
        }catch (NoSuchAlgorithmException e){
            e.printStackTrace();
        }catch(NoSuchPaddingException e){
            e.printStackTrace();
        }catch(InvalidKeyException e){
            e.printStackTrace();
        }
    }

 And I used this method inside a button 

    Button btnEncrypt = (Button) findViewById(R.id.btnEnc);
        btnEncrypt.setOnClickListener(new OnClickListener() {
            @Override
            public void onClick(View v) {
                aesKey = EncAndDec.generateKey();
                String filePath = editText.getText().toString();
                //Generating the file hash
                String md5Hash = MD5Hash.getMD5(filePath);

                System.out.println(aesKey.toString());
                System.out.println(filePath);
                System.out.println(md5Hash);

                //Encrypting the file
                for(int i=1; i&lt;100; i++) {
                    EncAndDec.encrypt(aesKey, filePath);
                }
            }
        });

Still I couldn&#39;t configure this error. Please someone help! 

java.io.FileNotFoundException: /storage/emulated/0/New file.txt: open failed: EACCES (Permission denied)

According to this: http://developer.android.com/preview/features/runtime-permissions.html#coding an app can check for runtime permissions and request permissions if it hasn&#39;t been granted already. The following dialog will be displayed then:

![enter image description here][1]

In case the user declines an important permission, imo an app should display an explanation why the permission is needed and what impact declining has. That dialog has two options:

1. re-try again (permission is requested again)
2. deny (app will work without that permission).

If the user checks `Never ask again` however, the second dialog with the explanation shouldn&#39;t be shown, especially if the user already declined once before.
Now the question is: how does my app know whether the user has checked the `Never ask again`? IMO the `onRequestPermissionsResult(int requestCode, String[] permissions, int[] grantResults)` doesn&#39;t give me that information.

A second question would be: does Google have plans to incorporate a custom message in the permission dialog that would explain why the app needs the permission? That way there would never be a second dialog which would certainly make for a better ux.



  [1]: http://i.stack.imgur.com/JiZCa.png

Android M - check runtime permission - how to determine if the user checked &quot;Never ask again&quot;?

When it comes to the M Developer Preview runtime permissions, according to [Google][1]:

1. If you have never asked for a certain permission before, just ask for it

2. If you asked before, and the user said &quot;no&quot;, and the user then tries doing something that needs the rejected permission, you should prompt the user to explain why you need the permission, before you go on to request the permission again

3. If you asked a couple of times before, and the user has said &quot;no, and stop asking&quot; (via the checkbox on the runtime permission dialog), you should just stop bothering (e.g., disable the UI that requires the permission)

However, we only have one method, `shouldShowRequestPermissionRationale()`, returning a `boolean`, and we have three states. We need a way to distinguish the never-asked state from the stop-asking state, as we get `false` from `shouldShowRequestPermissionRationale()` for both.

For permissions being requested on first run of the app, this is not a big problem. There are plenty of recipes for determining that this is probably the first run of your app (e.g., `boolean` value in `SharedPreferences`), and so you assume that if it&#39;s the first run of your app, you&#39;re in the never-asked state.

However, part of the vision of runtime permissions is that you might not ask for all of them up front. Permissions tied to fringe features you might only ask for later on, when the user taps on something that requires that permission. Here, the app may have been run many times, for months, before we all of a sudden need to request another permission.

In those cases, are we supposed to track whether or not we asked for the permission ourselves? Or is there something in the Android M API that I am missing that tells us whether we asked before or not?


  [1]: https://plus.google.com/+AndroidDevelopers/posts/8aaudh5n1zM?linkId=16190516

How Do We Distinguish Never-Asked From Stop-Asking in Android M&#39;s Runtime Permissions?

In Permissions tab of Android Manifest, in the drop down there are options called `android.permission.ACCESS_NETWORK_STATE` and `android.permission.ACCESS_WIFI_STATE`. What is the difference between them? Is `ACCESS_NETWORK_STATE` more generalized than `ACCESS_WIFI_STATE`?



What&#39;s the difference between access network state (ACCESS_NETWORK_STATE) and WIFI state (ACCESS_WIFI_STATE) permissions?

I have read that it is necessary to ask the user for some permissions at runtime for API 23 and up. For example: `android.permission.ACCESS_FINE_LOCATION`.
Is it necessary (or even possible) to ask for a runtime permission for using GCM/push notifications at runtime if API is 23 or higher?

I have tried using the `requestPermissions` method at runtime, but it doesn&#39;t seem to work (nothing happens) when I use it with any GCM/push notification related permissions.

I have the following permissions in my Manifest for this purpose:

    &lt;uses-permission android:name=&quot;android.permission.INTERNET&quot;/&gt;
    &lt;uses-permission android:name=&quot;com.google.android.c2dm.permission.RECEIVE&quot;/&gt;
    &lt;permission
        android:name=&quot;${applicationId}.permission.C2D_MESSAGE&quot;
        android:protectionLevel=&quot;signature&quot;/&gt;

The only permission that the user knows of, is the `ACCESS_FINE_LOCATION` when downloading the app from Play Store. Shouldn&#39;t the user be able to choose whether or not they would allow push notifications?


All Android Permissions Solutions on Gang of Coders

Total of 29 Android Permissions Solutions