Obsolete
Status Update
No update yet.
Comments
sm...@google.com
Hi, Thank you for reporting this. Are you still seeing this issue?
Were you following the instructions at "https://source.android.com/devices/tech/admin/testing-setup.html "?
Could you share a bugreport/logs with android-bugreport@google.com and post the link here ?
Were you following the instructions at "
Could you share a bugreport/logs with android-bugreport@google.com and post the link here ?
ri...@gmail.com
I just tried to reproduce with the TestDPC app but it doesn't run on wear.
But yes, I did follow the steps according tohttps://source.android.com/devices/tech/admin/testing-setup.html just that I'm using a wear 2.0 compatible app. Also note that I'm using standalone mode and it seems that in this case it's already configured to be paired right from factory settings (which explains the message in the stacktrace).
I.e. on a freshly created emulator it already shows device-paired = true in device_policies.xml:
$ adb shell
1|generic_x86:/ $ su
generic_x86:/ # cat /data/system/device_policies.xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<policies setup-complete="true" device-paired="true" />
Happy to provide more info if necessary, just let me know (and in that case could you also point me to a wear 2.0 compatible app that I can use or alternatively let me know if it's ok to provide my own sample?).
But yes, I did follow the steps according to
I.e. on a freshly created emulator it already shows device-paired = true in device_policies.xml:
$ adb shell
1|generic_x86:/ $ su
generic_x86:/ # cat /data/system/device_policies.xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<policies setup-complete="true" device-paired="true" />
Happy to provide more info if necessary, just let me know (and in that case could you also point me to a wear 2.0 compatible app that I can use or alternatively let me know if it's ok to provide my own sample?).
sm...@google.com
Hi,
Yes, please provide your sample.
Thanks.
Yes, please provide your sample.
Thanks.
sm...@google.com
Hi, Thank you for reporting this. We will pass this along to the wear team.
sm...@google.com
sy...@google.com
is...@google.com
Mu...@postuf.com
any updates on this?
cc...@google.com
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the latest bug report here https://goo.gl/TbMiIO .
Description
* What device you are testing with: emulator
I'm trying to get a Wear 2.0 (stand-alone) app to run in kiosk mode, but when I try
adb shell dpm set-device-owner <myComponent>
I get:
java.lang.IllegalStateException: Not allowed to set the device owner because this device has already paired
at android.os.Parcel.readException(Parcel.java:1692)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:4707)
at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:148)
at com.android.commands.dpm.Dpm.onRun(Dpm.java:96)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.dpm.Dpm.main(Dpm.java:41)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)