alvaroag

Hi. I'm preparing two identical Xiaomi Redmi 9A for usage with on premise ESET Protect. Both (now) have MIUI Global 12.0.18.0 (QCDMIXM), and have Endpoint Security for Android in Device Owner mode.. From the ESET Protect console, I'm applying policy to fully restrict incomming & outgoing calls & SMS. Therefore, the app requires call logs & SMS permissions, both which are not included in the app manifest. Therefore, Android won't give me any option to grant those permissions to the app. When I received both phones brand-new, I started with one of them. Despite the OS offering upgrade, I decided to configure everything and then upgrade. And, in that version, I was able to grand "unrequested" permissions. Not knowing that option was not available on the latest software, for the second phone, I decided to upgrade first and then configure everything. Thus. I now have one of both with no warnings, and the other with two "security risk" alerts for the missing Phone & SMS permissions. I tried granting the permissions via ADB, with "pm grant", but shell user doesn't have permissions for that. I can't root the phones, both for warranty and compliance reasons. Any idea? From my point of view, this could be also be a bug on the app, because, as any android app, it should request required permissions, either on manifest or at runtime.

Hi. The situation is the following. We have a ESMC set up for many months working fine with only a dozen PCs. Recently we have had the need to apply some security policies on Android devices, so decided to use the licenses we aleady have(a package with Windows+Android). Decided to use Dwvice Owner mode, as those are company's phones. First configured policies and groups. Then tried with a brand new phone. Device Owner enrollment went apparently fine, was able to read the QR and install. But then nothing else worked with that phone. Product was never activated, tasks were never executed, and no info could be seen on the Overview for that phone in Computers; only last connected time changed each time I rebooted the phone. Tried doing factory reset, deleting from ESMC, and enrolling again, having to delete the contents of "Device" table in MDC database. Same result all times. So tried updating ESMC & Server to latest version, as well as packages from the OS(already had a warning on that). After the update completed, I tried then enrolling again. Add New -> Mobile devices -> Device Owner. Set name, select license(Have 5 of 5 available), check "In case you are enrolling Android devices...", and click Next... And then get an error: Cant seem to find a solution for this. Software versions: ESMC Server Version: 7.2.2236.0 ESMC Web Console Version: 7.2.230.0 ESET Management Agent Version: 7.2.2233.0 MDMCore version: 7.2.5216.0 OS: CentOS 7 with latest updates (7.8.2003) DB Version: MySQL 8.0.21 Installed Components: Update module: 1076 (20200313) Translation support module: 1819.1 (20201009) SysInspector module: 1278 (20200609) SSL module: 1048 (20200608) Push Notification Service module: 1076 (20201006) Configuration module: 1889.4 (20200813) Any help will be appreciated.