Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for Search instead for Did you mean:02-12-2021 08:17 PM - edited 01-05-2022 05:16 PM
I recently switched my phone to a different phone. It tries to activate OMADM (error 6601) and keeps failing. The phone is a Samsung A20.
Is there something that is required on your end?
11-05-2023 07:52 PM
This is the post I found that really helped. It's a phone issue - I just had to keep blasting away and shutting down the OMADM. Eventually I broke my phone and made sure my new one was completely unlocked. Never had the issue again.
"Those suggestions provided a very temporary (about an hour) fix for me, but
I tried something different today that seems to be working (no messages in almost 8 hours).
Go to Settings > Apps. Click the three dots at the top, and select "Show system apps."
Under "Notification style" click "Silent and minimized."
I also have under OMADM "Change System Settings" = Not allowed. I don't know if that has an impact or not because that alone didn't work before I did the sequence I described above, but I'm not turning it back on just in case allowing it to change system settings means allowing it to undo what I did with the notifications.
There is also (on my phone) a "Sprint OMADM Phone Interface" but I don't know if it has any impact. I have it also set not to allow changes to system settings."