IssueTracker

Hi,
Can you provide the below requested information to better understand the issue which is applicable:

can you share sample source code to reproduce the issue.

Android build
Which Android build are you using? (e.g. KVT49L)

Device used
Which device did you use to reproduce this issue?

Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Expected output
What do you expect to occur?

Current output
What do you see instead?

logcat output
See http://developer.android.com/tools/help/logcat.html. Copy and paste relevant sections of the logcat output into this issue.

Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

The real issue here is that the system UI for granting SYSTEM_ALERT_WINDOW is missing/inaccessible on Android Wear 6.0 (API 23).


> can you share sample source code to reproduce the issue.
Uploaded to Google Drive: https://drive.google.com/open?id=0B5ry4aCYVaqodWU0SUh4aUFhWVk

Run OverlayTest.apk, and it should just show two buttons.

REQUEST PERMISSION: sends the intent to open the Settings UI to grant SYSTEM_ALERT_WINDOW for the app (the underlying issue here).

SHOW OVERLAY: adds a View to the WindowManager of TYPE_SYSTEM_ALERT. This will succeed if the app has been granted SYSTEM_ALERT_WINDOW, or crash on a BadTokenException if it hasn't.

On the phone app, both work fine. On the Wear app, both crash.

Tested on an LG Urbane LTE, build MFB16N, and an API 23 emulator, build MEB44B


>Steps to reproduce
> What steps do others need to take in order to reproduce the issue themselves?

To invoke the system settings UI:

    startActivity(new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION));


>Frequency
>How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
100%


>Expected output
>What do you expect to occur?

A system Settings activity should appear, with a toggle to "Permit drawing over other apps". [Such a UI actually exists in Android Wear 5.x (screenshot in Drive), though it's not accessible via the ACTION_MANAGE_OVERLAY_PERMISSION intent, which wasn't added until 6.0.]


> Current output
> What do you see instead?

android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.action.MANAGE_OVERLAY_PERMISSION }


>logcat output

01-27 10:22:58.247 12979-12979/com.udellent.overlaytest E/AndroidRuntime: FATAL EXCEPTION: main
  Process: com.udellent.overlaytest, PID: 12979
  android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.action.MANAGE_OVERLAY_PERMISSION dat=package:com.udellent.overlaytest }
      at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1798)
      at android.app.Instrumentation.execStartActivity(Instrumentation.java:1512)
      at android.app.Activity.startActivityForResult(Activity.java:3930)
      at android.app.Activity.startActivityForResult(Activity.java:3890)
      at android.app.Activity.startActivity(Activity.java:4213)
      at android.app.Activity.startActivity(Activity.java:4181)
      at com.udellent.overlaytest.MainActivity.onClick(MainActivity.java:50)
      at android.view.View.performClick(View.java:5204)
      at android.view.View$PerformClick.run(View.java:21153)
      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:5422)
      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)


> Android bug report:

This option doesn't seem to be available on Android Wear. Holding down the power button opens the launcher, rather than displaying the usual menu. If there's an alternate way to get this on Wear, please provide instructions and I'll be happy to do so.

This is an intentional change in behavior.  These are not runtime permissions, they have a separate dedicated access control in settings.

Yes, we all understand that this isn't a runtime permission. Please re-read the report: "The real issue here is that the system UI for granting SYSTEM_ALERT_WINDOW is missing/inaccessible on Android Wear 6.0 (API 23)."

It's not about runtime permissions. The problem is that the "separate dedicated access control in settings" (to use your own words) is missing, and the documented Intent to open it fails (with ActivityNotFoundException).

Please reopen this issue. Thank you.

+1 indeed pleas reopen this issue, we need an access to this settings

I agree with "The real issue here is that the system UI for granting SYSTEM_ALERT_WINDOW is missing/inaccessible on Android Wear 6.0 (API 23)." App throw android.content.ActivityNotFoundException. RE-OPEN THIS ISSUE PLEASE.

Hi,
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks

＋1

FYI, it happens in some of 6.0.1 devices as well, but not on all.

I am seeing this on the Zuk Z1 device on Android 6 consistently

Fatal Exception: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.action.MANAGE_OVERLAY_PERMISSION dat=package:com.vsco.cam flg=0x10000000 }
       at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1812)
       at android.app.Instrumentation.execStartActivity(Instrumentation.java:1516)
       at android.app.ContextImpl.startActivity(ContextImpl.java:694)
       at android.app.ContextImpl.startActivity(ContextImpl.java:676)
       at android.content.ContextWrapper.startActivity(ContextWrapper.java:339)

is observed when running the below code:

if (android.os.Build.VERSION.SDK_INT >= 23
                && !Settings.canDrawOverlays(newBannerView.getContext())) {
            Intent intent =
                    new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION, Uri.parse("package:"
                            + getPackageName()));
            intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            (newBannerView.getContext()).startActivity(intent);
            return;
        }

btw, this same problem exists on Android TV (Nexus Player running Marshmallow). Should a separate issue be created?

Same also happens with latest Android N emulator!

This issue has been fixed in the latest Wear 2.0 developer preview 2, and will be in the final release.

This problem exists on Android TV as well

[Comment deleted]

indeed, it does! please make some noise in bug 36949180

I have the SAME issue. How can i do??

logcat:
{code}
05-06 15:31:36.189  1419  2385 I ActivityManager: START u0 {act=android.settings.action.MANAGE_WRITE_SETTINGS dat=package:com.autonavi.minimap} from uid 10098 on display 0
05-06 15:31:36.192  6155  6155 W System.err: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.action.MANAGE_WRITE_SETTINGS dat=package:com.autonavi.minimap }
05-06 15:31:36.194  6155  6155 W System.err:    at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1816)
05-06 15:31:36.194  6155  6155 W System.err:    at android.app.Instrumentation.execStartActivity(Instrumentation.java:1525)
05-06 15:31:36.194  6155  6155 W System.err:    at android.app.Activity.startActivityForResult(Activity.java:4265)
05-06 15:31:36.195  6155  6155 W System.err:    at android.app.Activity.startActivityForResult(Activity.java:4224)
05-06 15:31:36.195  6155  6155 W System.err:    at com.autonavi.common.utils.PermissionUtil.CheckWritingPermission(PermissionUtil.java:333)
05-06 15:31:36.195  6155  6155 W System.err:    at com.autonavi.map.activity.SplashActivity$8.run(SplashActivity.java:478)
05-06 15:31:36.195  6155  6155 W System.err:    at com.autonavi.map.activity.SplashActivity$11.onClick(SplashActivity.java:563)
05-06 15:31:36.195  6155  6155 W System.err:    at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:186)
05-06 15:31:36.196  6155  6155 W System.err:    at android.os.Handler.dispatchMessage(Handler.java:102)
05-06 15:31:36.196  6155  6155 W System.err:    at android.os.Looper.loop(Looper.java:154)
05-06 15:31:36.196  6155  6155 W System.err:    at android.app.ActivityThread.main(ActivityThread.java:6153)
05-06 15:31:36.196  6155  6155 W System.err:    at java.lang.reflect.Method.invoke(Native Method)
05-06 15:31:36.196  6155  6155 W System.err:    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
05-06 15:31:36.197  6155  6155 W System.err:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758)
{code}

I have this issue only on Zuk devices:
ZUK Z2121
ZUK Z2
ZUK Z2131

Is there any workaround for this?

Any news???

I have this issue for Zuk and some emus

I still have this issue only on Zuk devices
ZUK Z2 .  so i have try catch this problem.
how to solve the problem? help me~plz

Me too.. i am also facing same issue on ZUK devices. its running perfectly on Samsung 6.0.1 and 5.0.1, Mi 6.0.1 and nexus also.
When it will be solved by Google????????

Google, you should talk with ZUK and any OEM that doesn't follow the basic rules for handling API, and provide us developers a proper way to use the API, that will work on all devices.
It's not up to us to figure out how to work with each OEM. For this, we have the standard docs of Android.

I am having the same issue with Android TV on Sony Bravia, my project depends on this.

apparently the bugid in #17 somehow got messed up. for android tv, please make some noise in bug 37121932

same issue with Lenovo Z2 Plus

The issue was fixed.
If this issue currently still exists, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.

android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.app.action.CONFIRM_DEVICE_CREDENTIAL flg=0x8080000 pkg=com.android.settings (has extras) }
        at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1805)
        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1514)
        at android.app.Activity.startActivityForResult(Activity.java:3978)
        at zzzi.startActivityForResult(PG:50)
        at qr.f(PG:170)
        at qq.b(PG:32)
        at qn.c(PG:2)
        at az.startActivityForResult(PG:27)
        at rx.e(PG:87)
        at apfw.e(PG:245)
        at apfw.c(PG:2)
        at akkt.m(PG:25)
        at adkv.aY(PG:61)
        at adkv.s(PG:25)
        at amvo.mg(PG:48)
        at com.google.android.finsky.uicomponentsmvc.buttongroup.view.ButtonGroupView.f(PG:9)
        at amta.onClick(PG:77)
        at android.view.View.performClick(View.java:5207)
        at com.google.android.material.button.MaterialButton.performClick(PG:16)
        at android.view.View$PerformClick.run(View.java:21177)
        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:5441)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)

Thanks for the information. As requested in comment #28,  please file a new issue in the AOSP issue tracker and reference this issue ID for context.