No Matches Found!
Try with a different search term
We have a number of Samsung Phones (A20e) that we are running in KIOSK mode, I am wanting to let the device use the phone app and have added an entry in the policy that I believe should allow the phone app to run:
launch://com.samsung.android.dialer
The phone app is there and you can enter a phone numbewr, but it will not allow it to dial and connect, this works on our other devices running as AndroidPlus devices
Is there another setting that needs entering somewhere?
It can b very different, on our samsung devices it should "com.android.phone" but i don't use kiosk mode, so i can't verify.
Similar issues related to kiosk mode arise all the time, not just with dialler, but any other apps defined in the kiosk mode.
You do NOT just need to verify whether the dialler app is com.samsung.android.dialer or com.android.phone (as Rafael suggested, but unlikely because you said you can already input the numbers).
You also need to check if the dialler call other app/service module(s) to process your call request. If so, you have to whitelist suh modules with kiosk/application-run-control policy if you have not yet done so. This was discussed in many discussion threads in this forum in the past. If any such transitionary module remain active in the foreground for long enough time, it might be quite easy to find its bundle ID's with MobiControl's "identity_activity" script command. Otherwise, one might need other tools or even programing skill/background to find such information.
