![]() ![]() You may have other vendors in your environment so there may be others you need to add.įirst, we need a target group of devices. In our case we created one for the native (Google) Android dialer and one for the Samsung dialer. What we need to do is bring the dialer into the work profile to give it precedence and to do that we use the ‘ Android Enterprise system app‘ option to create instances of the native dialers in the environment. This would have happened if we introduced ANY application that was registered to handle tel: links, but Zoom was the only one for us. What is happening here is Zoom is now registered to handle tel: links and because it exists inside of the work profile it is taking precedence (the dialer is not really part of the work profile). Users can tap a telephone number in an email or web page to call that number with Zoom Phone. It was obvious that a change in 5.6.3 caused this: Support for tel: protocol links - Android We first looked into what changed within the app in the release notes. They suggested I setup a new kiosk and start that way, which mostly seems to work, but so does any other fix I use.We recently came across an issue where after a recent Zoom app update anytime a user clicked a tel: link from within the work profile the Zoom app was launched instead of the native dialer. I'm now up to 29 occurrences of this problem, with only 2 of the phones recurring. At first I kept factory reseting them and starting from scratch, but eventually found a workaround that I can get into the settings and restart the app properly. We had our first report on Sept 17th and by October 2nd I had 20 different phones come through my office with this problem. Unfortunately the phone will not work without kiosk mode running so this puts it into an endless loop. What happens is that when someone goes to use the phone it shows an error that "sonimkiosk keeps stopping" with only options being try again or close app. I've got a fleet of about 60 Sonim XP8s and I use sonim scout's kiosk mode. Phones are Sonim XP8s and are on Android 8.1.0 (unfortunately highest offered version for them) on the Sprint network.ĭid you get anywhere with this? I had a similiar problem which started in September. If anyone has any suggestions at all, please let me know! I've been at this for the past two days and have come up with nothing while no one can use their devices to make calls. ![]() I've contacted the phone manufacture as well as Microsoft Intune Support and neither have been able to give me any real assistance yet. We've tried factory resetting them, cleared data for the phone and call manager apps, tried enrolling as "Corporate-owned, fully managed user devices" to test, tried giving the phone app full permissions in an app config policy, tried adding "" as an "Android Enterprise System App" even though Intune's documentation says that one is automatically allowed full permissions. Unfortunately you still can't actually RECEIVE a call because when a call comes in, it also pops up with "Phone has stopped" and you get no opportunity to answer.Īs you can probably imagine, this happening to all 40 of the phones in our company is a huge issue. Here is the kicker, it actually places the call, but you have no way of ending the call or pressing any keys in the call. You can open it up, dial a phone number, then when you try to call it says "Phone has stopped working" and gives me the option to "Open app again", I click that and it comes up "Phone keeps stopping" and gives me that same option and "Close app" options. These phones were working properly until 8/28 and with no changes on our end, all of them are having an issue with the Phone app. We have 40 phones that are set up in Intune, enrolled as dedicated devices. I'm having an issue that is absolutely destroying my brain right now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |