Same situation in Orange Poland. B1 and B3 masking is a workaround, but this takes away most valuable LTE band in this network. Please fix it as soon as possible, as I'm considering sending the router back and I think I won't be the only one who will do so…
2 Likes
Update:
As the method of masking bands has limited applicability, and to ensure a better user experience, we are recommending the R15 temporary solution for handling related issues. The band masking approach will be removed accordingly.
If you have tried Option 1 before, please unblock Band 1/3 first and try the Option 2.
Option 2: Switch UE capability to R15
- Log in to the device admin panel > INTERNET > Cellular > Modem AT Command
- Enter and execute the AT command below one by one to set 3GPP release to R15:
AT+QNWCFG="3gpp_rel",r15,r15
AT+QEFSSYNC=1
AT+CFUN=1,1
Note: You can switch back to R17 anytime using the same AT command:
AT+QNWCFG="3gpp_rel",r17,r17
AT+QEFSSYNC=1
AT+CFUN=1,1
If you have any questions, please contact our support team: support@gl-inet.com
Sincerely,
GL.iNet Support Team
Hello，
We sincerely apologize, but due to limitations in certain tower capabilities, the SIM registration of Mudi7 probably been affected.
Please share your Mudi7 with us via GoodCloud, we will remote check this issue and debug the modem.
Please PM me or email support@gl-inet.com with your router MAC address and the Admin Panel password.
Still not a proper workaround (Germany, Telekom). The AT commands leads to 4G only.
5G is possible via blocking R3, but of course with very limited speed.
Please support us with a proper hotfix, thanks a lot.
3 Likes
With R15 and deutsche Telekom I’m Able to use 5g. I don‘t have this Problem.
Today i testet with ookla Speedtest near Stuttgart i got 857 down and 78 up.
For me this is a good Solution Till we have the fix.
Neither for me … not really happy.
Anyone in the UK had any success with eSIM working reliably on mudi7? I’ve tried 2 or 3, all register ok and work for a very brief period, then stop and get the interface connected but no internet message.
I’ve tried locking to supported carriers and band masking etc, but no luck
Getting a bit frustrated with it now, as the eSIM functionality was the main buying point. I’ve been onto support and shared via good cloud, but still it doesn’t work.
Just interested to hear about other uk users?
Thank you for trying to solve the problem. For me, with ORANGE PL (Poland), it was very frustrating. Hope it will works
Interesting! Have tried R15 twice, same result, only 4G. Maybe a different kind of cell?
So still waiting for a proper solution.
1 Like
Hello,
We sincerely apologize, but due to the limitations of our cellular environment that we cannot fully verify if the solution work situation, and we would like to remote your Mudi7 (in the local cellular environment) for debugging and troubleshooting.
Please share your Mudi7 with us through GoodCloud.
During debugging, the following situations may occur:
-
The modem will be offline due to debugging or upgrading firmware, so the Mudi7 repeater needs to be connected to a stable WiFi/AP (home WiFi or mobile hotspot), or connected to a wired network (switch the Mudi7 network port to WAN mode).
-
The modem may get stuck due to debugging. Occasionally, we maybe need you in local assistance to restore Mudi7 to factory settings and reconnect to GoodCloud so that we can continue remote debugging.
Thank you for any help!
If there are other users who are willing to provide help, you can also contact us. Please PM me on the forum, or communicate via email at support@gl-inet.com.
This does not sound good. I thought there is a solution in place being implemented into the new firmware.
But here it sounds you are still „debugging“.
I am really sad about this - but please tell me how i can return the Mudi (Early Bird Buyer). NB: I do not have the packaging anymore.
We have identified potential solutions and have already compiled new firmware.
But we lack the necessary test environment to verify this fixed issue firmware stability.
We are looking for a way to reproduce the issue so we can validate the fix. During the validation process, we intend to add some debugging instrumentation to ensure we don't miss any critical information.
Truly sorry, if you’d like to contact us about return it, please email cs@gl-inet.com and cite your forum post.
Update:
After consulting with our R&D team, we have developed a new solution to address the registration issue.
We intend to enable the UE (Mudi7-EU) to report R17 capabilities instead of the previous R15. To better align with the requirements of specific European towers, we have developed a customized reporting mechanism. This is designed to ensure successful registration while leveraging R17 capabilities to enhance network performance.
If you have experienced similar issues, please provide GoodCloud remote access so we can verify if this new firmware resolves this issue.
MANY THANKS!
1 Like
Happy to install the beta firmware and do my own testing. Until then, my Mudi 7 device is officially retired. Spent another evening yesterday with all described options. I ended up with 4G, with a slow 5G or with no cellular coverage at all.
Setup: T-Mobile hardware SIM, Munich/Bavaria downtown area with high 5G coverage.
1 Like
Maybe we should meet and check? I live close to Munich and have not experienced issues with a T-Mobile SIM card in Mudi 7. However I´m using a prepaid card which doesn´t have 5G+ enabled. So it always uses 5G NSA (means always a 4G band is the primary band).
I have had a similar issue on O2 SIM card which was 5G+ enabled. Mudi 7 as well as O2 seem to force the device to remain in 5G SA band only. Which results in low speeds if only N28 as 5G SA band is available. And once no 5G SA band is available I could imagine no connection at all.
Once N78 5G SA is available in downtown areas the speed is obviously great, but Mudi 7 doesn´t do carrier aggreation with 4G at all in network auto mode which is a pitty as it reduces speed unnecessary during load.
I´m a bit lost if this is due to O2 or Mudi 7 or MBN files in Mudi 7. Or if it is a combination of all. I will simply wait for the firmware update for now and in the meantime I cancelled 5G+ from O2 contract. I can live with 5G NSA for now.
What I recommend: Try with different provider SIM cards and check the behavior. I have on top another router (ZTE U60 with X72 chip as well) that behaves totally different i.e. always sets up 2x P Cells, one in 4G one in 5G resulting usually in great speeds. (But the ZTE U60 is not my preferred device at all. Temperature and battery management sucks and it is by far not as versatile as Mudi 7)
Well, I need to use my T-Mobile SIM cards since I am a “heavy user” and I got flat rates on the contract. Not willing to pay for another full flat rate subscription.
I am now back on my ZTE MU5120 and I ordered a Telekom discounted ZTE U60 now as well.
It is a pity, since I bought the Mudi 7 after a very positive experience with the GL iNet Spitz AX. I use that for longer stays and I was always impressed about local WiFi coverage and cellular internet speed and reliability. The Mudi 7 was supposed to be a more mobile alternative for shorter trips.
I really don’t understand why this is such a challenge and hasn’t been fixed yet.
I have been using a Puli AX from day 1 of launch with an EE and Vodaphone UK SIMS with zero issues, both sims supported with 5G connection out of the box.
I bought 3 x Mudi 7 for myself and colleagues as the Puli AX that we have are an excellent solution, but without a removable battery option it cannot be checked in to aircraft checked luggage and is too big for hand luggage, so the MUDI seemed an excellent travel option.
Transfer sims from Puli to Mudi, Vodaphone is flawless, EE refuses to connect. using the same firmware (v4.8.3)
I have tried all the options above, blocking band 1 and 3, AT commands and connectivity for a maximum of 2 minutes before the dreaded “Not Registered” message.
Out of desperation and wanting to check i had not caused an issues with trying literally everything I reset the router and then re-upgraded to firmware 4.8.3. Reading the comments i then tried switching to 5G only - no dice, switching to 4g only and suddenly I have a stable connection.
For anyone else out there using a UK EE sim, try switching the ‘Simcard settings → Network Type’ to 4g only, it may give you a temporary solution, it works for me.
Is the slower connection workable, yes but obviously connection is impacted.
Hopefully GL-Inet will sort this soon or I will need to return the 3 units I have, as the EE sim is personal and the Vodaphone is work. Hoping for a quick resolution.
Alot of complaints, but why don’t everyone with the issue just let the staff login in your Mudi7 to test the fix they have so the fix can be released to the public.
3 Likes
Hello,
May I know if you have already configured modem to R15?
If yes, did you experience any issues with NSA network registration before changing the settings to R15?
I sincerely apologize for any inconvenience this may have caused.
I would like to clarify that the Puli AX modem supports R16, while the Mudi7 modem supports R17. In some regions of Europe, there are cell towers that do not fully support R17, which is causing SIM registration issues when the Mudi7 reports its R17 capability.
We are currently working on an optimization to improve compatibility with these towers while maintaining R17 functionality.
Would it be possible for you to share the device with us? We would like to verify our proposed solution—specifically, optimizing the reporting mechanism while keeping R17 enabled—to ensure it works seamlessly with these towers. Once verified, we will release a new firmware update as soon as possible.
1 Like
I never had registration issues so far with any provider in Germany. So I also did not have to switch to R15.
1 Like