是否有可能有一个"个人拥有者QUOT;应用在Android中棒棒堂,是不是共同present [英] Is it possible to have a "Profile Owner" app in Android Lollipop that is not co-present

查看:303
本文介绍了是否有可能有一个"个人拥有者QUOT;应用在Android中棒棒堂,是不是共同present的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

新的棒棒糖API提供了2个新的功能业主的个人资料和设备所有者(的 http://developer.android.com/about/versions/android-5.0.html#Enterprise )。他们之间,他们只提供我需要一个应用程序,父母可以用它来控制孩子的设备活动的功能。每个设置流程是:

The new Lollipop API provides 2 new features "Profile Owner" and "Device Owner" (http://developer.android.com/about/versions/android-5.0.html#Enterprise). Between them, they offer just the features I need for an app that parents can use to control their children's device activity. The setup flow for each is:

在设备的设置,使用NFC,你可以告诉的Andr​​oid您希望您的应用程序是一个设备所有者。 Android的下载,然后从URL应用程序,设备加密,并供应了应用程序的设备所有者。因此,有人从安装谷歌播放我的应用程序,我需要的应用程序,以促使他们为出厂重置设备,然后在另一个设备上安装其他应用程序,然后NFC撞在一起。由于设置流走,这是很不理想。但是,一旦安装,设备所有者API提供了非常丰富的功能,对于这种使用情况设置。

During device setup, using NFC, you can tell Android that you want your app to be a Device Owner. Android then downloads the app from a URL, and the device is encrypted and is provisioned with the app as a Device Owner. So for someone installing my app from Google Play, I would need the app to prompt them to factory reset their device, then install another app on another device, and then NFC bump them together. As setup flows go, this is far from from ideal. But once setup, the Device Owner APIs provide a very rich feature set for this use case.

此安装程序是一个小更直截了当:利用从安装谷歌播放应用程序,然后就可以提示给应用程序配置文件所有者权限。如果用户同意,该设备由Android加密,并在重新启动后该设备具有使用相同的启动器(主屏幕)2共present配置文件。设置也许更多向前伸直,但最终的结果是不是真的是我需要的,因为应用程序只有在管理配置文件下的应用程序的控制。

The setup for this is a little more straight forward: the use install the app from Google Play, and can then be prompted to give the app Profile Owner privileges. If the user agrees, the device is encrypted by Android, and after a reboot the device has 2 "co-present" profiles that use the same launcher (home screen). The setup maybe more straight forward, but the end result is not really what I need, as the app only has control over the apps under the managed profile.

所以我想其实我有2个问题:是否有可能使控制整个用户配置文件,即不是共同present管理配置文件的配置文件所有者的应用程序?或者是有可能使设备所有者的应用程序与不需要恢复出厂设置和NFC凸起一个简单的设置流程(生根不是一个选项)?这两种方法之间的一些中间地带将是理想的。

So I guess I actually have 2 questions: Is it possible to make a Profile Owner app that controls the entire user profile i.e. not a co-present managed profile? Or is it possible to make a Device Owner app with a simpler setup flow that does not require a factory reset and NFC bump (rooting is not an option)? Some middle ground between the two approaches would be ideal.

推荐答案

答(1):管理配置文件可以作为单独的人物,都在配置文件中的应用程序是不同的(它们是不同的独立应用程序实例),它类似于新用户。
档案所有者管理配置文件的所有者的应用程序,因此它并没有太多的能力和功能比较设备所有者因此无法控制整个用户配置文件。

Answer (1): Managed profile works as separate persona, all the apps under profile are distinct(they are different independent application instance),it is similar to new user. Profile owner is owner app of managed profile hence it doesn't have much power and functionality compare to device owner thus it cannot control the entire user profile.

答(2):用于创建设备所有者一个人与NFC的方法去,因为一旦你的设备是安装它得到供应,在那之后你不能让你的应用程序作为设备所有者(除非你用生根方法去) 。
您可以按照制作设备所有者

Answer (2): For creating the device owner one has to go with the NFC method because once your device is setup it gets provisioned, after that you cannot make your app as device owner(unless you go with the rooting method). You can follow the given links for making device owner

1)<一href=\"http://stackoverflow.com/questions/26906210/device-owner-on-android-5-0-and-others-whitout-rooted-devices-device-provisio/27009164#27009164\">Create与NFC 设备所有者

2)<一href=\"http://stackoverflow.com/questions/21183328/how-to-make-my-app-a-device-owner/26839548#26839548\">With生根

这篇关于是否有可能有一个&QUOT;个人拥有者QUOT;应用在Android中棒棒堂,是不是共同present的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆