While this may happen … one cannot rely on it to “fix an issue” as fundamental as this. You really want the issue registered like this Report an issue. It has not been reported as I write. See Post # 12 .
The route to contact the Murena helpdesk is quoted here:
In case any of you would care to add more useful evidence here on the forum, to help a speedy solution this is a copy of the
Bug report template
- /e/ version:
- Device model(s):
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
Summary
The problem
Steps to reproduce
- How one can reproduce the issue
What is the current behavior?
- What actually happens
What is the expected correct behavior?
- What you should see instead
Technical information
Relevant logs (adb logcat)
Relevant screenshots
Solutions
Workaround
Possible fixes