@Manoj it would be pretty helpful if some in-depth-info about murena MDM would be made available in the documentation or howto or faq like it is provided for say Advanced Privacy…
I disabled MDM using ADB root, but there should be user level control over it. Forcing it enabled for all installations is bad form. Though it’s not such a big deal for me that it would dissuade me from using /e/os.
Which is actually a good idea. I doubt a “corporation” would use /e/os in the first place so why force it on all the normal users. If a corpo wants a phone they can administrate then Murena could do a “special” build for them. But I’ll just disable it as it stands, no harm no foul.
I totally agree with you and had a similar idea. Why not creating a business build for each device ? A build with murena MDM setuped for companies or whatever.
Having this installed by default without announcement or explaination is definitly not correct for average users. I already said it and i’ll say it again : i opted for murena to be in charge of my data, and this is not the case due to this software. I understand that behind /e/ stands murena who tries to create a cloud option and a safe work environment ; however, this should not interfere with the first goal of /e/OS : providing a safe android environment.
Right now, i can’t neither install shelter nor activate parental control AND i’m not the owner of my own phone. That was the whole goal of installing /e/ and this is currently not fullfilled.
You can use an app called App Inspector to get the package name. You can list packages with “adb shell pm list packages” but the list can be long and unruly. Better to use the app.
I actually use a tool called ADB AppControl. It greatly simplifies the whole process.
It’s a Murena thing, I suppose they’re trying to be more corporate friendly by including admin tools, but the ironic thing is that most of use /e/os to get big tech corpos out of our life. In any case Google and Apple include those tools so I guess Murena thinks they should too.
Thanks ! But you have the package name as you already did the process, don’t you ? Can you tell me what its name is please ? I’m not skilled when it comes to use adb…
Edit: looks like you can find it at the bottom of the app details in the settings. You just select an app and scroll down. For MDM it is “foundation.e.mdm”.
They can’t even properly support the consumer market. They should get that nailed down before they start looking for corporate or government contracts. In the mean time they should not be locking down that MDM app.
Also organizations are not going to be interested in last year’s models. They don’t spend money on older tech. Then there’s support. Having worked in the tech industry for a time, I can tell you that reliable vendor support is utmost priority.
