Spitz AX (GL-X3000) – Huge speed drop after modem firmware update – looking for advice / rollback info

Hi GL.iNet community,

I’m hoping someone here can help me diagnose a serious performance problem on my GL-X3000 “Spitz AX” router.


What happened

  • Before the update – The internal CAT19 LTE modem regularly delivered ~200 Mbps download (same SIM, carrier, location, and signal).
  • After updating the modem firmware – Download now maxes out at 70-100 Mbps (uploads dropped proportionally). The speed loss is consistent and reproducible across multiple test spots, including outdoors with very strong signal. Reboots, modem resets, and fresh APN settings make no difference.

Current setup

  • Router firmware: latest v4.x release
  • Mode: Router mode, cellular WAN only
  • Modem bands: LTE Bands 3/7/20 active; 5G NR bands n1/n28/n78 enabled (though I’m on LTE only)
  • No other config changes besides the modem-FW upgrade

Logs from the last 3-4 days

  • gl_modem killed by OOM: repeated “gl_modem invoked oom-killer” entries suggest a memory leak in the new firmware/drivers.
  • Timeouts talking to the modem: log lines like

arduino

KopiujEdytuj

modem.get_traffic_config fail: connect "127.0.0.1:80" fail: timeout

point to intermittent loss of contact with the modem’s internal API.

  • No such errors pre-update. Everything else on the router seems stable; only the modem side is misbehaving.

What I’ve tried

  • Full power-cycle, factory reset of router settings (kept modem FW)
  • Verified no new QoS / bandwidth caps in the GUI
  • Swapped SIM into a phone – phone still hits 200 Mbps, so the carrier signal is fine

Possible fix – roll back modem firmware?

The stock (factory) modem firmware never had these issues. Unfortunately I don’t know its version number and can’t locate it on the download page. Can anyone tell me if it’s possible to flash the factory modem firmware, or share guidance / files to do a rollback safely?

Modem serial (from AT logs): 016442004897324

Any advice, experiences with similar speed drops, or pointers from GL.iNet staff would be greatly appreciated!

Thanks in advance.

Ps.
Log:
root@GL-X3000:~# picocom /dev/ttyUSB2
picocom v3.1

port is : /dev/ttyUSB2
flowcontrol : none
baudrate is : 9600
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no

Type [C-a] [C-h] to see available commands
Terminal ready

+QENDC: 0

OK

+QNWCFG: "disable_lte_ca",0

OK

+QNWCFG: "disable_nr_ca",0

OK

+QNWPREFCFG: "lte_band",1:2:3:4:5:7:8:12:13:14:17:18:19:20:25:26:28:29:30:32:34:38:39:40:41:42:43:46:48:66:71

OK

+QNWPREFCFG: "nr5g_band",1:2:3:5:7:8:12:13:14:18:20:25:26:28:29:30:38:40:41:48:66:70:71:75:76:77:78:79

OK

+QNWPREFCFG: "nsa_nr5g_band",1:2:3:5:7:8:12:13:14:18:20:25:26:28:29:30:38:40:41:48:66:70:71:75:76:77:78:79

OK

+QNWCFG: "dis_4mimo_enable",1

OK

+QNWCFG: "nr5g_4mimo_enable",1

OK

+QNWCFG: "nr5g_ul_256qam",0,0

OK

+QNWCFG: "lte_cdrx",1,1

OK

+QNWCFG: "nr5g_cdrx",1

OK

+QNWPREFCFG: "rat_acq_order",NR5G:LTE:WCDMA

OK

ERROR

+QNWCFG: "nr5g_mimo",1,3

OK

+QNWCFG: "lte_ulMCS",0

OK

+QNWCFG: "dss_enable",1

OK

+QNWINFO: "FDD LTE","26003","LTE BAND 7",3025
+QNWINFO: "FDD NR5G","26003","NR5G BAND 1",423410

OK

+QCAINFO: "PCC",3025,75,"LTE BAND 7",1,444,-98,-14,-61,11
+QCAINFO: "SCC",423410,2,"NR5G BAND 1",444,-87,-11,1781

OK

+QENDC: 0

OK

+QTEMP:"modem-lte-sub6-pa1","44"
+QTEMP:"modem-sdr0-pa0","0"
+QTEMP:"modem-sdr0-pa1","0"
+QTEMP:"modem-sdr0-pa2","0"
+QTEMP:"modem-sdr1-pa0","0"
+QTEMP:"modem-sdr1-pa1","0"
+QTEMP:"modem-sdr1-pa2","0"
+QTEMP:"modem-mmw0","0"
+QTEMP:"aoss-0-usr","44"
+QTEMP:"cpuss-0-usr","44"
+QTEMP:"mdmq6-0-usr","44"
+QTEMP:"mdmss-0-usr","44"
+QTEMP:"mdmss-1-usr","43"
+QTEMP:"mdmss-2-usr","44"
+QTEMP:"mdmss-3-usr","44"
+QTEMP:"modem-lte-sub6-pa2","43"
+QTEMP:"modem-ambient-usr","44"

OK

+QCSQ: "LTE",-69,-99,17,-11

OK

+QSINR: 8,-32768,-32768,-32768,LTE
+QSINR: 18,19,20,19,NR5G

OK

+QRSRP: -99,-140,-140,-140,LTE
+QRSRP: -86,-86,-88,-87,NR5G

OK

+QNWPREFCFG: "mode_pref",AUTO

OK

+QCFG: "pcie/mode",0

OK

+QNWCFG: "nr5g_ulbw",1,1,2

OK

+QNWCFG: "nr5g_ulTBsize",0

OK

+QCFG: "lte/bandprior",03,07,20

OK

+QCFG: "rrc",5

OK

+QCFG: "hsdpacat",24

OK

+CGPIAF: 0,0,0,0

OK

+QNWCFG: "lapi",0

OK

+C5GREG: 0,0

OK

+CEREG: 0,1

OK

+QNWCFG: "ctrl_plane_dly",1,"LTE",0

OK

+QNWCFG: "nr5g_mimo_layers",1,2

OK

+QENG: "servingcell","NOCONN"
+QENG: "LTE","FDD",260,03,3AC721F,444,3025,7,4,4,D314,-103,-12,-72,13,12,210,-
+QENG: "NR5G-NSA",260,03,444,-85,23,-3,423410,1,2,0

OK

+QSCAN: "LTE",260,03,3025,444,-100,-10,24,118
+QSCAN: "LTE",260,03,6200,381,-83,-18,45,110
+QSCAN: "LTE",260,03,6350,381,-81,-10,47,9
+QSCAN: "LTE",260,02,6350,381,-81,-10,47,9
+QSCAN: "LTE",260,03,1749,444,-96,-11,32,116
+QSCAN: "LTE",260,03,1599,444,-97,-6,31,8
+QSCAN: "LTE",260,02,1599,444,-97,-6,31,8
+QSCAN: "LTE",260,06,1474,193,-93,-6,35,12
+QSCAN: "LTE",260,03,3175,444,-102,-10,23,8
+QSCAN: "LTE",260,02,3175,444,-102,-10,23,8
+QSCAN: "LTE",260,01,1300,77,-100,-14,28,115
+QSCAN: "LTE",260,03,75,444,-92,-15,37,114
+QSCAN: "LTE",260,03,225,444,-98,-11,31,6
+QSCAN: "LTE",260,02,225,444,-98,-11,31,6
+QSCAN: "LTE",260,06,525,193,-97,-7,31,11
+QSCAN: "LTE",260,01,2850,317,-108,-13,21,115
+QSCAN: "LTE",260,06,6275,193,-81,-10,45,7
+QSCAN: "LTE",260,03,3686,444,-83,-8,45,11
+QSCAN: "LTE",260,02,3686,444,-83,-8,45,11
+QSCAN: "LTE",260,01,3526,496,-75,-12,49,115
+QSCAN: "LTE",260,06,3350,287,-135,-24,-7,104

OK

+QNWCFG: "ssb_beam_id",1,2,2,-85,-11,444

OK

+QNWCFG: "event_a3_offset",1,5

OK

+QNWCFG: "3gpp_rel",R15,R15

OK

OK

+QNWLOCK: "common/4g",(0-10),,
+QNWLOCK: "common/5g",,,,
+QNWLOCK: "save_ctrl",(0,1),(0,1)
+QNWLOCK: "common/4g_ext",<num_of_cells>,<cell_list>

OK

OK

Quectel

OK

RM520N-GL

OK

+CPIN: READY

OK

In my experience, modem firmware is highly related to your carrier. Once you find a firmware that works, keep it until there is a known issue. Do not upgrade modem firmware just because it is available. I had to test about 7 different versions of modem firmware until I found one that was stable and works well. I will not upgrade it again unless there is a very good reason AND I can undo it and go back to what was working. Sorry this doesn't help where you are now, though.

1 Like

Please tell us your purchase time, I think we can probably guess the corresponding factory modem firmware version.

Update:

Please try this modem firmware version:

http://download.gl-inet.com.s3.amazonaws.com/download/RM520GL-modem_firmware/RM520NGLAAR01A07M4G_01.201.01.201.zip