Hi,
I updated my e/OS/ version to the official v3.2 version on my Samsung Galaxy S7.
The bug reported here is still there (The topic was automatically closed)… even if (thanks @Manoj) it should have been removed in version 3.1 ( Why I stop recommending /e && why you might wanna know - #25 ).
Can we hope that this bug will be fixed one day?
Thanks
this is not a new S7 install, you could just never get rid of the org admin since?
I’d go for a reset if the fix takes longer to come through.
The gitlab issue is still open atm at
murena moved to a stub installer for the mdm in later releases, so I’d be surprised if the issue crops up again on new installs
As of today the latest official version is still 3.1.4 from what I see here (was it available for a short period and withdrawn?)
(no milestone set in the gitalb issue anymore (was set to 3.2 for a while but removed), but from a functional perspective, I can live with that issue in my current S7-install as it only interferes with functions I do not activate anyways - like parental control (different story when you want to use it). In general “the organization” has no means to “own” the device since the MDM-part was removed in 3.0 … apart from that: workarounds and fixes were described in the thread you linked to)
(edit: now, ~12h later, 3.2 is shown in the above linked page)