Hi, I received my Mudi 7 yesterday. Unfortantly 5G on o2 Germany is not working.
Please fix this asap Thanks!
Regards, Heiko
1 Like
Hi!
I also have issues with a roaming SIM in the O2 network, as well as a Telekom SIM. The band 3 mask workaround works, but speeds are really tanking, because LTE band 3 is quite important in Germany.
@mux you might consider that thread: Mudi 7 - Telekom SIM card
As a workoround mask Band 3, which avoids connection on LTE band 3, which will deacrease speed but the connection will start to work.
1 Like
Dito, genau so vereinfacht gesagt,
4G geht, 5G geht gar nicht und führt zu einem Softwarefehler.
Welcher ein Neu starten des admin-tools notwendig macht und teilweise musste ich am Router zusätzlich einen Reset durchführen.
Same problem. I use Lycamobile in the German O2 network. 4G works, no chance with 5G. Solution would be nice, in the actual version it is only a beta version.
I´m using O2 as well on Mudi 7 in Germany. Not sure it is the same issue, but just as a remark:
If you activated 5G+ with O2 then O2 network will usually "force” your Mudi 7 into 5G SA bands and kind of disable 5G NSA.
And Mudi 7 also prefers to keep the connection exclusively into a 5G SA band if there is one. Mudi won´t start 5G NSA out of my experience even not if the speed is slow on 5G SA.
So in case you have a 5G+ contract and there is no 5G SA band available it might fail to connect.
It will connect if you select 4G only. (If you cannot even access the Admin Web UI to change the settings use a USB-C cable to connect to your notebook)
What you can try as well is to deactivate the 5G+ option in your contract (takes 48 hours!) via O2 hotline or chat. (You cannot do it online) and then try again. It helped me to enable 5G NSA on Mudi 7 in the Auto Network mode.
Keep in mind that many devices show “5G” in the display while in reality it is “5G NSA”. But many other devices are capable to switch from 5G SA to 5G NSA properly - which doesn´t seem the case with Mudi 7 right now in Auto network mode for O2. (I think it has to do with the ROW MBN file coming from Quectel/Qualcomm)
What you can also do as a first step: Check via Tower Scan what 5G SA band is shown in your location.(i.e. 5G SA N28) - then block it (SIM Card Settings => Advanced => Enable Band Masking) Mudi 7 should then fall into 5G NSA as well when reconnecting.
I am very confident that these issues should be resolved in a few weeks, or at least better guides will be available. GL will do an infield test by using the major 3 operators in Germany shortly.
1 Like
Topic moved to a separate post: Mudi 7 Upload Speed issue with O2 / Telefonica - #5 by Martixx72
My Mudi 7 has always slow upload speeds when using a O2 Telefonica SIM card.
I compared it today with 3 other routers plus my smartphone (same location and timing) to verify further. In total I did about 50 testcycles with 3 different provider SIMs, all on 5G NSA contracts (no 5G SA) - see screen shot below.
Anybody else experiencing the same? There is no issue when using Vodafone or Telekom SIM cards and download is fine as well.
I´m based in Germany. Not sure it is the same for other countries.
1 Like
Exactly like me.
ZTE U60 and ZTE MU5120 work fine in terms of throughput, Mudi 7 does not. On a T-Mobile MultiSIM within Germany.
I believe the MBN from Quectel for O2 Telefonica is not enabling dual upload carrier aggregation. But I would need other people to double-check to verify if I'm the only one experiencing this. In other words is it an issue only with my individual device or a generic one?
(I never had any issues with Telekom/TMobile on Mudi 7. A lot of the throughput depends on carrier aggregation and 5G SA vs 5G NSA from my experience. But this is why I put 3 contracts on 5G NSA now and tested with 5 devices in total. At least 2 of the devices with lower performance / older chipsets, one is the same and one I consider equal. It is obvious Mudi 7 upload on O2 has an issue. I experienced this from day one and it replicable.)
If I understood correctly, through AI matching. You should use the AT command to check which protocols from which providers are installed. With this query, I found on my FW805 that there is no access protocol at all for O2. As a result, a universal rudimentary one is used, which means that only 4G is supported. And that is also the cause of the CA problem. So all that remains is to wait until GLI integrates a protocol generated by O2. That should then also resolve O2 problems from 5G to CA with 4G. Ultimately, that also explains why other providers work in your case. Overall, I have top speeds with 4G, but connection problems. Since it is always checked first and, as a last resort, the simplified universal access is chosen, this leads to a delay when connecting.
MBN = Modem Board Network = Protocol = Modem Module Firmware
Wer are talking about the same thing.
There is no specific MBN for O2 Telefonica installed. Quectel only provides a generic one (ROW = Rest of World) for O2 Telefonica / Gl.iNet / the modem module used in Mudi 7.
But first I want to verify the upload issue.
Definitely, but you can't force CA by explicitly programming via AT; that seems to be blocked by GLI. I was too lazy to dig up the exact dialogue in the documentation. The fact is that for O2 there is only limited functionality.
1 Like
If this is a generic issue then it is up to Gl.iNet to request a MBN / firmware update from Quectel.
I would appreciate if other Mudi 7 users test it as well.
I did some further tests. Seems to be a CA issue. More details under separate post here:
1 Like