User Profile
Andeo
Level 1.5: Cupcake
Joined 2 years ago
User Widgets
Contributions
Re: Keyguard automatically disabled when kioskCustomLauncherEnabled is enabled
Hey Moombas Thanks for the answer. When the kioskCustomLauncherEnabled flag is set to true then the DevicePolicy on the phone automatically sets the Home-Launcher to "Device Policy" (it's the home-launcher that is automatically provided by the Device-Policy, if kioskCustomLauncherEnabled is set to true). I can't really test this on a non-managed device, because this home-launcher activity is set by the Device Policy. Do you know if I can test this on a non-managed device? This is how the home-launcher looks like and it's automatically set by the Device Policy: The standard-app is actually set to "Device Policy" Is there maybe another input that you could give me? Kind regards Kol706Views0likes0CommentsRe: Keyguard automatically disabled when kioskCustomLauncherEnabled is enabled
can a supporter please give us an update to this post? it doesn't make any sense that the user has to unlock the phone with a pin only once, and doesn't get asked again until the phone is restarted because of the keyguard that is disabled741Views0likes0CommentsRe: Bluetooth bonding behaviour, when kioskCustomization.deviceSettings is set to SETTINGS_ACCESS_BLOCKED in android management policy
Can someone please give me an update on this? This behaviour is very confusing, either it works or it doesn't but there shouldn't be an inbetween state, where one way it works and another way it doesn't593Views0likes0CommentsKeyguard automatically disabled when kioskCustomLauncherEnabled is enabled
Hey guys The title says it all. I want my customers to be able to see their device name on the lock screen, when using the kiosk custom launcher. Our customers can only see the device name when they restart the phone. If they lock the phone normally, it doesn't activate the keyguard. Is there a possibility to have this fixed? Regards841Views0likes3CommentsBluetooth bonding behaviour, when kioskCustomization.deviceSettings is set to SETTINGS_ACCESS_BLOCKED in android management policy
Hey guys I have developed an app which can turn on and turn off bluetooth as well as change some sound settings of the device. Toggling the bluetooth setting to on / off works fine, as does the different sound settings. The weird behaviour shows up when I try to bond a device. As I described in the title, my policy has the kioskCustomization.deviceSettings flag set to SETTINGS_ACCESS_BLOCKED. With this policy enforced, the bonding process doesnt work with my custom app and also does not work with the official android bluetooth settings (accessed over an intent) I think this is a bug, because the phone can still bond to other devices if other devices advertise themselves to this phone. Can you please help me with this? Regards759Views0likes2Comments