Forum Discussion
Master ownership of Android devices
I am also concerned about this, I've been looking for details everywhere. We loan out phones all the time and FRP is a big problem for us when users change the pin.
Thanks for the response Genero, please let me know if you find out anything useful. I guess what it comes down to is that there is no "User" role on androids, the user is the Admin, which didn't used to be a problem until FRP came along.
Exactly, which is a big problem when your business model is based on being able to Factory Reset phones, to undo all the mess users make on them. We have lost the ability to loan out phones without an MDM solution.
Actually that's the crux of it, the introduction of FRP has made Android Enterprise mandatory where it wasn't before, as well as all the other MDM bits or whatever to make it impossible to remove accounts.
No, you haven't, you could force users to unlock and wipe those devices first if you don'T want to use an MDM but this would require that they always stay in front of you in person and not send them via package or similar.
And you have this behavior not only on Android devices, you have the same on Apple devices as well. And if devices got "connected" to an account (Google account/ Apple ID) also, they need to be removed from that as well.
If handing out "free to use" devices to employees, you always need to take care of that or need to manage them to ensure entire access and ability to reset it.
Let's not compare to Apple eh? We have higher standards than that. I wouldn't call anything made by Apple a "business device". Also "force users to stand in front of you", what world are you living in?
Thats not correct, if you have a fully managed device, there is an admin role (already described above) and user role. The only thing is you need to set it up correctly or force users to wipe the device when taking back the device (i know that this is most often very complicated).
And FRP i would only use on fully managed devices, not on work profile or BYOD or anything else otherwise you need to send such devices to repair (as jasonbayton mentioned before as well) to get them back working again for which you may got charged, depending on your error description.
