Watching a video or downloading an app (or latest eOS update) is such a mess.
Wifi is always deconnecting, then connecting again, sometimes working properly for a few minutes, then deconnecting again. For downloaching eOS update, I have to manually reconnect to the Wifi at least 20 times. And it does NOT come from my box. I had ORANGE box and same problem. Then I switched to BOUYGUES box, and problem remains.
I start doubting about Murena Two…as Wifi issues come on top of camera issue, SMS that cannot be sent, no protection case… and many little other things that make it complicate to use.
Is there any news on this issue? I have similar issues with my device. It keeps logging out quite often and has issues connecting again. In most cases it complains that the access point is “full” - which cannot be the case as most times I have more devices logged in without any issues on those devices.
If this really is connected to the WPA mode than it seems more like a driver than a hardware issue and could hopefully be fixed in software.
Any comment from Murena? It’s like pswiatki stated in some other threads: No feedback on the forum and no feedback on the support ticket. Not having a reliable WLAN connection is an important issue. I don’t understand why Murena does not care about this.
I got feedback from the helpdesk now. Completely resetting the network settings helped for now. I really hope that this is a persistent solution.
At least the good news is that this doesn’t seem to be a hardware issue.
These are the steps provided by helpdesk. Up to now the issue is solved for at least most of the time - I still get some strange errors sometimes.
Ensure your Murena Two is updated to the latest version of /e/OS. You can check for updates by going to Settings > System > System updates.
Try resetting the network settings by navigating to Settings > System > Advanced > Reset options > Reset Wi-Fi, mobile & Bluetooth. This will not delete your personal data but will reset all network settings to their default state.
I tried, but it didn’t make any difference. I have other smartphones with /e/os installed. Only the Murena 2 (android 13 version 2.2) has this problem with wifi. I didn’t have the problem with version 2.1. To be continued.
Fortunately (for me) these steps helped on my device. I got the following additional step from helpdesk back then. Maybe this helps you. If not I suggest contacting the helpdesk again.
If the issue persists, consider performing a network test by entering ##4636## on the phone dialer, selecting ‘Wi-Fi information’ > ‘Wi-Fi status’ > ‘Refresh stats’, and running a ping test to check for any anomalies.
Hi, I have several smartphones with v2.2 or v2.3 installed (samsung s10e, Teracube 2e). The problem only appear with the Murena 2 (v2.2 & v2.3).
I tried to reset the network parameters completely, but to no avail. I tested the ping from the menu obtained with ##4636##, everything is fine until the phone disconnects, then reconnects, etc…
When there’s a disconnection, I often get the message “Registered/Access point temporarily full”. It’s the same on 2.4 and 5 Ghz. My router is a Livebox 7.
Just a thought … I am wondering if your router sees the updated device in some way in conflict with the same device “pre-update”. I associate that message with the Router being full. It may be limited to a certain number of devices. I also got the issue with multiple Linux OS on USB sticks and SD cards in use at one time for testing. The router either gives two IP to one device and / or mistakes a device for one which already has a lease, with the result that the new version is denied access.
Worst case you could try to reset the router, but usually you can access Admin and have a clean out.
Same issue and error message here. With the steps provided by the helpdesk the issue does not happen as often as before but still it happens way too often.
Also here Murena Two is the only device with this issue, all other devices (including a refurbished device with the same OS) work as expected.
Regarding the pre-update conflict idea: I’d expect that this would happen to all updated devices, especially the other /e device. Also it should never work in this scenario.
MAC address randomization is turned off so this can not be the root course.
