* Which Android Beta build are you using? See Settings > About phone > Build number (for example PPP5.180610.010).

QPP1.190205.018.B4

* Is this a regression from P to Q?

Not applicable, new API to Android Q

* What device are you using? (for example, Pixel XL)

Pixel

* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)

Step #1: UnZIP the attached RoleNonReversal-20190324.zip file, import it into your favorite IDE, and run it on an Android Q device.

Step #2: Notice that the really big button is enabled. It is enabled if roleManager.isRoleHeld(RoleManager.ROLE_MUSIC) returns false. Since this app was just installed, it does not hold any role, so roleManager.isRoleHeld(RoleManager.ROLE_MUSIC) returns false, and the really big button is enabled.

Step #3: Click the really big button.

Step #4: When Android Q asks if you want to make this app be your music player, click OK.

Step #5: Notice that the really big button is now disabled, as RoleManager is reporting that the app holds ROLE_MUSIC.

Step #6: Go to Settings > Apps & notifications > RoleNonReversal > Permissions > Music, and toggle that "permission" to Deny.

Step #7: Terminate the process for the RoleNonReversal app (should already be terminated by Android Q, but make sure it's gone).

Step #8: Run the RoleNonReversal app again.

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc

Framework

* What was the expected result?

The really big button should be enabled, because roleManager.isRoleHeld(RoleManager.ROLE_MUSIC) should return false, since the role is no longer held.

* Can you provide the API document where this expected behavior is explained?

See the RoleManager JavaDocs.

* What was the actual result?

The really big button is still disabled, as roleManager.isRoleHeld(RoleManager.ROLE_MUSIC) is returning true.