Test Device Technical Notes Nemo Outdoor 9.70 February 2024

Test Deviceer’s Manual
Technical Notes
a
Keysight
Nemo
Insert the
Outdoor 9.70
Title in this
Release
Space
1 | Keysight | Nemo Outdoor 9.70 Test Device Technical Notes
Table of Contents
General Information ........................................................................................................................................ 3
EOL Announcements........................................................................................................................................ 3
Discontinued Chipsets & Test Device Handler Software Options................................................................ 3
UEs ................................................................................................................................................................... 4
Removals from the document ..................................................................................................................... 4
Airbus Devices .............................................................................................................................................. 5
Generic Notes .......................................................................................................................................... 5
THR880/ THR9i ......................................................................................................................................... 5
TMR880 .................................................................................................................................................... 5
Hisilicon Kirin 990/9000-based handsets..................................................................................................... 5
Huawei Mate40 Pro 5G NOH-NX9 ........................................................................................................... 5
Huawei P40 5G, ANA-NX9, Huawei P40 Pro 5G ELS-NX9......................................................................... 5
Huawei Mate30 Pro ELS-N29 ................................................................................................................... 6
Qualcomm (MDM92xx/96xx, MSM89xx, Snapdragon)-based UEs ............................................................. 6
Generic notes ........................................................................................................................................... 6
Asus Handsets .......................................................................................................................................... 7
Bittium Handsets...................................................................................................................................... 7
Essential Handsets ................................................................................................................................... 7
Google Handsets ...................................................................................................................................... 8
HMD Handsets ......................................................................................................................................... 8
Knowyou NB-IoT/LTE-M devices .............................................................................................................. 8
Generic Notes .......................................................................................................................................... 8
OnePlus Handsets .................................................................................................................................... 9
Motorola Handsets ................................................................................................................................ 10
Samsung handsets ................................................................................................................................. 11
Sierra Wireless/ Netgear LTE modems .................................................................................................. 16
Sonim Handsets ..................................................................................................................................... 18
Sony Handsets ........................................................................................................................................ 18
Xiaomi handsets ..................................................................................................................................... 19
Other handsets and devices................................................................................................................... 20
Samsung Shannon (5100/5123/5123A,5123B, 5133, 5300, 5308) – based devices ................................. 20
Generic notes ......................................................................................................................................... 20
Samsung (Shannon modem) handsets .................................................................................................. 21
Google Pixel handsets (Tensor, Tensor2, Tensor3)................................................................................ 23
Mediatek chipset -based devices ............................................................................................................... 24

Generic notes ......................................................................................................................................... 24
Qualcomm 3GPP2-based UEs .................................................................................................................... 24
Generic notes ......................................................................................................................................... 24
Scanning Receivers..................................................................................................................................... 24
Nemo FSR1 scanner ............................................................................................................................... 24
PCTEL scanners....................................................................................................................................... 25
Rohde & Schwarz scanners .................................................................................................................... 25
Other Devices ................................................................................................................................................. 28
GPS receivers ............................................................................................................................................. 28
General Information
The test devices tested and sold by Keysight Nemo Wireless Network Solutions are intended for testing
purposes only. Software changes in devices may limit their normal use. Keysight Nemo Wireless Network
Solutions does its best to provide test devices without any limitations but it is not always possible. Keysight
Nemo Wireless Network Solutions assumes no liability if any commercial application or feature is blocked or
limited due to software or other device-related modifications. If the test device is moved to another country or
used in the network of another operator than initially ordered, it is possible that the device does not support all
network features. Keysight Nemo Wireless Network Solutions assumes no liability in any cases.
EOL Announcements
-
Discontinued Chipsets & Test Device Handler Software Options
Product Code Handler Software Option Chipset/ Vendor Notes

UEs
Removals from the document
Known issues for the following UEs can be found from earlier Nemo Outdoor release documents:
• Bandrich Bandluxe C320 (Nemo Outdoor 7.2 Release Notes)

• Beceem BCS200 / BCSM 250/3300 WiMAX devices (Nemo Outdoor 7.2 Release Notes)
• Blackberry Torch 9810 (RDM71UW) (Nemo Outdoor 7.2 Release Notes)
• Datang/Leadcore handsets (Nemo Outdoor 6.31 Release Notes)
• HTC One XL (PJ83120) (Nemo Outdoor 7.2 Release Notes)
• Huawei: E270, E220, E1820, E169, E180, E367 and E372 modems (Nemo Outdoor 7.2 Release Notes)
• LG: KF700 and P500 (Nemo Outdoor 6.31 Release Notes)
• Motorola V9 (Nemo Outdoor 6.31 Release Notes)
• Motorola iDEN i886
• Nokia: 21M-02 and Lumia 920 (RM-821) (Nemo Outdoor 7.2 Release Notes), 6720, 612x, N95, N80,
N85, N96 and N97 (Nemo Outdoor 6.31 Release Notes)
• Novatel: Ovation MC545 (Nemo Outdoor 7.2 Release Notes), MC996D, MC998D, 930D and 990D (Nemo
Outdoor 6.31 Release Notes)
• Option USB modems (Nemo Outdoor 6.31 Release Notes)
• Pantech UML290 USB modem (Nemo Outdoor 7.2 Release Notes)
• Samsung: Galaxy Ace, Omnia 7, Focus and Rugby II SGH-A847, Galaxy S II Skyrocket (SGH-I727), Galaxy
S II LTE (GT-I9210), Galaxy S II Note (GT-N7105) (Nemo Outdoor 7.2 Release Notes)
• Sierra Wireless: 312U, 319U, 320U (Nemo Outdoor 7.2 Release Notes), Aircard 885, 306, 307, 308, 309,
310U, Siptune 215 (Nemo Outdoor 6.31 Release Notes)
• Sony Ericsson Xperia Arc S (LT-18i) (Nemo Outdoor 7.2 Release Notes)
• ZTE: MF668A and MF683 USB modems (Nemo Outdoor 7.2 Release Notes)
• Altair ALT3100-based devices (Nemo Outdoor 8.0.0 Release Notes)
• LG G3 D801, LG P930 (Nemo Outdoor 8.0.0 Release Notes)
• Broadcom devices (Nemo Outdoor 8.0.0 Release Notes)
• Nokia 500, E-7, C-7, Nokia C5 series (Nemo Outdoor 8.0.0 Release Notes)
• IPhone 5, iPhone 6S (Nemo Outdoor 8.0.0 Release Notes)
• Terratec DMX 6 Fire and Maya44 USB Sound cards (Nemo Outdoor 8.0.0 Release Notes)
• Samsung Galaxy S6, S6edge (Nemo Outdoor 8.0.0 Release Notes)
• Hisilicon Balong 710/720 based devices (Nemo Outdoor 8.2.0 Release Notes)
• Oneplus 6, 6T (Nemo Outdoor 8.9.0 Release Notes)
• Oneplus 6T (Nemo Outdoor 8.9.0 Release Notes)
• Samsung: Galaxy S6 edge+, Galaxy S7 SM-G930F, Galaxy S7 SM-G930FD, Galaxy S7 edge SM-G935FD
(Nemo Outdoor 8.9.0 Release Notes)
• Sony Xperia: Z5 E6653, Z53 D6603, Z3 D6653, XZ F8331, XZ F8332(Nemo Outdoor 8.9.0 Release Note)
• Huawei Hisilicon Kirin 95x/960 handset Huawei P9 (Nemo Outdoor 8.9.0 Release Notes)
• PCTel EX, EX Wimax, EX GSM/TD-SCDMA, CX, LX (Nemo Outdoor 8.9.0 Release Notes)
• R&S TSML-C, TSML-G, TSML-W, TSMQ (Nemo Outdoor 8.9.0 Release Notes)
• Motorola Moto X Pure Edition (2015) XT1575 (Nemo Outdoor 8.9.0 Release Notes), Google Pixel 4
G020M (global) and G020I (US), Google Pixel G-2PW2100 (Nemo Outdoor 8.9.0 Release Notes)
• Iphone7 (A1660), iPhone 8 (A1863), iPhone X (A1865) (Nemo Outdoor 8.9.0 Release Notes)
• HTC U12+ HTC U11, HTC One M8x OP6B110 (Nemo Outdoor 8.9.0 Release Notes)
• OnePlus 7 Pro GM1913, OnePlus 7 Pro 5G GM1920 (Nemo Outdoor 9.1 Release Notes)
• Sony Xperia XZ3, XZ2, XZ1, XZ Premium, Xperia 1, Xperia 1 II (Nemo Outdoor 9.1 Release Notes)
• Samsung Galaxy S8+ SM-G955F, S8 SM-G950F, Galaxy Note 8 SM-N950F (Nemo Outdoor 9.2 Release
Notes)
Airbus Devices
Generic Notes
• Measurement profiles cannot be used with Tetra calls

• MER value is not reported by the terminal
• The terminal does not answer all incoming calls when call modes are semi-duplex or duplex. Auto-
answer can be enabled in the following ways with THR880i and THR880.
THR880/ THR9i
• Plug in a headset (Nokia Headset Type HDC-9)

• Settings / Enhancement Settings / Headset / Automatic Answer --> On
• Settings / Profiles / Headset / Personalize / Incoming Call Alert: this must not be "Off".
• Settings / Profiles / Headset / Activate
• Reboot the phone.
• THR880i: Before the terminal can be used with Nemo Outdoor, the field test mode of the terminal must
be activated by the Cassidian TETRA Prorgramming Tool. Tool is available only from Cassidian.
• For THR880 the procedure is identical, except that there is a slightly different menu structure for the
steps. Instead of Settings | Profiles | Headset, the correct path is Profiles | Headset.
• THR880i reports the PTT State incorrectly with some phone firmware versions. This can cause the
device to hang during group call and semi-duplex call testing, and device restart is needed to recover
TMR880
• Device is supported only with Win XP OS. Using Win7 OS running the device is causing instability
issues. Development has been discontinued and there is no fix available
Hisilicon Kirin 990/9000-based handsets

Huawei Mate40 Pro 5G NOH-NX9
• Device requires Nemo Active Testing Application for better connectivity with Nemo Outdoor
• Following data protocols are verified
o ICMP ping, FTP(s), HTTP(s), Iperf, Iperf3, Browsing, Youtube
• Packet capture, PEVQ-S, Digital Voice Quality is not supported
• Data and OTT testing that requires Android apps is not supported
• Volte calling ok, SIP signaling ok, detailed Volte KPI (jitter etc) not available
• When testing with Nemo Outdoor or Nemo Invex, internet access is required when adding device. This
is required once a week.
• With Nemo Invex, data connection is required in UIC during connecting device in Invex setup. For
example, WIFI modem can be used. This is required once a week
• Forcing features: NR band forcing is not supported
• Nemo Outdoor 9.20 required with EMUI12 and Harmony versions
• Nemo Outdoor 9.30 is required in some networks for forcing features on all LTE bands
Huawei P40 5G, ANA-NX9, Huawei P40 Pro 5G ELS-NX9
• Following data protocols are supported
o ICMP ping, FTP(s), HTTP(s), Iperf, Iperf3, Browsing, Mscore, Youtube
• With Invex, data connection is required in UIC during connecting device in Invex setup. For example,
WIFI modem can be used. This is required once a week
• Nemo Outdoor 9.20 required with EMUI12 and Harmony versions
Huawei Mate30 Pro ELS-N29
• Following data protocols are supported
o ICMP ping, FTP(s), HTTP(s), Iperf, Iperf3, Browsing, Mscore, Youtube
• Minimum version to use is Nemo Outdoor 9.01 (due to Huawei license server change)
• Nemo Outdoor 9.20 required with EMUI12 versions
Qualcomm (MDM92xx/96xx, MSM89xx, Snapdragon)-based UEs

Generic notes
• LTE-A: Number of secondary serving cells is > 0 when secondary channel is configured but not active.
The activation state is shown in “Cell state” parameter.
• Listed cells are not reported in idle mode
• RRC CONNECTION REQUEST message is missing occasionally
• Attach/detach commands should be avoided with LTE terminals. Using these commands causes
instabilities in the UEs. UEs can also reset itself. Issue is fixed to Nemo Outdoor version 6.4.1.8 but if the
issue is still experienced, the following instructions should be followed. It is recommended to choose
from User Interface Properties -> Measurement -> Force detach when going to idle mode -> No. This
will prevent the UE from detaching. If attach/ detach commands are needed frequently, for example,
with script files, it is recommended that ‘Radio Off’ / ‘Radio On’ commands are used instead of
attach/detach.
Figure 1. User Interface properties.

• MultiRAB testing. When a voice call is terminated, the PS data connection might be released with UEs
using the “Trace interface” call method to make voice calls. In such a case it is recommended to use
“Trace interface 2” call method.
• Android 13: With some non-root phones, notification permission rights need to be given manually from
phone. Settings – Apps – NATA – upper corner *** -> allow restricted permissions. After this
notifications can be enabled. This step is not required with Nemo Firmware phones.
Asus Handsets
Asus Smartphone for Snapdragon insiders (ASUS I007D)
• These forcing features are not supported: GSM channel lock, UMTS scr code lock
• Netflix and Instagram not supported
• When using Nemo Outdoor 9.30 with NATA, following ADB files from Nemo Outdoor 9.20 installation
folder need to be used for replacing files in version 9.30 installation folder (adb.exe, AdbWinApi.dll,
AdbWinUsbApi.dll). With Nemo Outdoor 9.50 autodetect recognized adb-compatibility with default
adb-version and adb connection can be selected from list in offline mode. With Nemo Outdoor 9.60
autodetect device – after error popup go offline – in device connection menu, select ADB serial from list
– go online.
• For NR Standalone usage, disabling FR2 bands could be required
•
Bittium Handsets
Bittium Tough Mobile
• When doing MT voice call testing, the call answer delay must be set to 1 (the default setting of 0 will
cause the phone to not recognize the call properly, even though it is correctly handled in Outdoor)
Essential Handsets
Essential Phone PH-1
• Limited forcing features:

o GSM channel lock not supported, UMTS SCR code lock not supported. UMTS channel lock is
preferred
• Voice quality testing is supported, but there are occasions with slight clipping on the samples, which
has minimal effect on MOS scores
• Screencast opens a connection, but cannot control the phone
• Video call, ViLTE, VoWiFi and ViWiFi not verified
• MMS testing not verified
• PEVQ-S verified without Netflix
• AMR codec mode forcing not verified
Google Handsets
Google Pixel 4 G020M (global) and G020I (US)
• Voice Quality is not supported

• UMTS scr. lock is not available
• GSM Channel lock is not available
HMD Handsets
Nokia 8.30 5G (TA-1243)
• Forcing features: UMTS scr code and GSM channel code lock not supported
• Voice Quality, Packet capture, PEVQ-S not supported
Nokia XR20 (TA-1362 Global, TA-1371 US)
• Forcing features: Method2 setting to be used for LTE Channel lock (without PCI)
• Non-root requires specific build, full features supported with Nemo Firmware
• Voice Quality not supported
• IP Capture, PEVQ-S need Nemo Firmware
Nokia X30 (TA-1450)
• Forcing features: NR Channel forcing works with NR SA, Channel+PCI required with SA
• Forcing features: Method2 setting to be used for LTE Channel lock (without PCI)
• Non-root requires specific build, full features supported with Nemo Firmware
• Voice Quality not supported
• IP Capture, PEVQ-S need Nemo Firmware
Knowyou NB-IoT/LTE-M devices
Generic Notes
• With IoT devices it is recommended to use following setting to prevent Windows traffic via IoT
interface. Outdoor Settings – User Interface Properties – Measurement – Routing table modification for
devices -> Disable default gateway
Knowyou KDC-5737 Rel13
• Connection to device is lost when device enters PSM mode, connection is retrieved after PSM state
• PCI lock not supported. Other forcing features not verified
Knowyou KDC-6336 Rel14
• Connection to device is lost when device enters PSM mode, connection is retrieved after PSM state
• PCI lock not supported.

• UDP testing, Packet capture is not supported (Outdoor 9.10)
• Setting eDRX Cycle works. When set eDRX PTW value, dongle goes to endless sleep mode
• LTE-M / NB-IoT mode change can be done using at-commands
• Nemo Outdoor 9.70 recommended for forcing
OnePlus Handsets
OnePlus8 IN2013
• Netflix, Instagram and Twitter are not supported
• Network setting feature Smart 5G, should be disabled during 5G testing
• Android 11: NATA tethering mode not supported, NATA ADB Forwarding mode needs to be used
OnePlus8 IN2015 (US)
OnePlus 8 Pro IN2023
OnePlus 8T KB2003
OnePlus 9 LE2113 / Oneplus 9 Pro LE2123 / Oneplus 9 Pro LE2125
• Android 12 support requires Nemo Outdoor 9.20
• Android 12 forcing features: lock released with airplane mode on/off with NATA forcing method
• USB-Multi testing not supported
OnePlus 10 Pro NE2213
• These forcing features are not supported: GSM channel lock, UMTS channel lock, UMTS scr code lock
• Forcing: UMTS system lock could get released over time
• Forcing: Separate LTE channel and PCI locks supported with forcing Method2
• OTT app testing not verified
• NBM and Invex support not verified with version 9.4.x
• USB Autostart and Smartcharging not available
OnePlus 10T CPH2413 / CPH 2415 / CPH2417
• NBM and Invex support not verified (version 9.50)
• USB Autostart and Smartcharging not available
OnePlus 11 CPH2449
• NBM and Invex support not verified (version 9.50)
Motorola Handsets
Motorola Edge 40 Pro 5G XT2301-4, Motorola Edge+ (2023) XT2301-1
• Forcing features: System forcing ok, other forcing features under testing (Outdoor 9.60 status)
•
Motorola Edge 30 Pro 5G XT2201-1
• OTT apps: Only Whatsapp is verified
• Forcing features: not verified with Nemo Outdoor 9.21
• Forcing features: Airplane mode releases forcing
• Forcing features: CA mode change requires manual device restart
Motorola Edge 20 Pro 5G XT2153-1
• PEVQ-S: with Outdoor 9.11 only test test003b vide can be used
• Forcing: CA mode change requires manual device restart
• AMR codec mode change not verified
• Android 11 and newer: NATA tethering mode not supported, NATA ADB Forwarding mode needs to be
used
Motorola Edge Plus 5G XT2061-3 (EU)
• Only System lock tested with version 9.0
• Android 11 and newer: NATA tethering mode not supported, NATA ADB Forwarding mode needs to be
used
Samsung handsets
General
• Android 11: NATA tethering mode is not supported with Android 11 NATA devices, ADB Forwarding
mode can be enabled from NATA settings. Nemo Outdoor 9.20 has this selection automatic.
• There can be lost synchronization in WCDMA and in GSM Voice Quality tests
with Samsung Galaxy S21 SM-G991U variant
• Voice Quality testing requires Nemo Firmware or NIDI
• IMS/SIP signaling support could require Nemo Firmware in encrypted networks.
• With many models NATA and Handy cannot be installed at the same time
• Non-root phones: Nemo Assistant installation happens when device is connected with Outdoor first
time, this is not mandatory but is recommended step.
Samsung Galaxy S24 Ultra SM-S928B (Global)
• Forcing functions: Scr. Code lock and GSM and UMTS channel lock not supported
• Only non-root version is tested by release date of this document (Nemo Outdoor 9.70)
• Non-rooted: ip-capture, PEVQ-S not supported
Samsung Galaxy S24+ SM-S926U/U1 (US)
Samsung Galaxy S24+ SM-S9260 (CHN/TWN)
Samsung Galaxy Z Flip5 SM-F731B (Global)
• Forcing functions: method2 to be selected as band forcing method for LTE channel and LTE PCI lock
• Forcing: Nemo Firmware required for NR Channel/PCI forcing and NSA/SA mode change
Samsung Galaxy S23 SM-S911B, S23+ SM-S916B, S23 Ultra SM-S918B (Global)
Samsung Galaxy S23 SM-S911C (Rakuten), S23 SC-51D (Docomo), S23 Ultra SM-S918Q (Japan Sim-Free)
• UMTS is not supported

• Forcing: NR forcing features are not verified in live network
• Depending on Nemo Firmware version, continuous Airplane toggle could stop NATA connection.
Samsung Galaxy S23+ SM-S916U, S23+ SM-S916U1 – US Operator and unlocked
• Forcing: Browsing could fail with non-root devices when run together with other data tests
• Verizon variant: Forcing not supported with non-root
• Forcing: T-Mobile variant: NSA system/band lock sets device to SA mode (Nemo Outdoor 9.50)
• Forcing: Verizon and AT&T: LTE Channel/PCI lock set device to wrong band/channel (Nemo Outdoor
9.50)
• Forcing: U1 unlocked variant: LTE Channel/PCI lock set device to wrong band/channel, NSA
system/band lock sets device to SA mode (Nemo Outdoor 9.50)
• GSM and UMTS not verified with AT&T and Verizon variants
Samsung Galaxy S23+ SM-S9160 – TWN,China
Samsung Galaxy S23+ SM-S916W - Canada
• Non-rooted: forcing features not verified
Samsung Galaxy S22+ SM-S916U (US variants)
• Not all features are tested in 2G and 3G environment (not available in live network)
• Nemo Outdoor 9.40: testing partially ongoing with release version; VQ, OTT apps not verified yet
• Nemo Outdoor 9.40: Nemo Firmware support under testing during release data
Samsung Galaxy S22 SM-S901E, S22+ SM-S906E, S22 Ultra SM-S908E (Global variants)
• Forcing functions: Scr. Code lock and GSM channel lock not supported
• Forcing functions: method2 to be selected as band forcing method for LTE/UMTS channel and LTE PCI
lock
• Forcing functions: Nemo Firmware required for forcing features
• Nemo Outdoor 9.20: fix patch required for NR MAC and NR PDSCH throughput correct results, ok with
Nemo Outdoor 9.21
Samsung Galaxy S22+ SM-S9060 (China, TWN)
• Forcing functions: LTE channel forcing: method2 required as band forcing method
• Forcing functions: UMTS channel forcing not supported
• Outdoor 9.20: fix patch required for NR MAC and NR PDSCH throughput correct results
Samsung Galaxy S22 SCG13 (Japan KDDI/Au), S22 SC-51C (Japan Docomo)
• Forcing functions: LTE channel forcing: method2 required as band forcing method
• UMTS not supported
• Non-rooted version not verified
• Outdoor 9.20: fix patch required for NR MAC and NR PDSCH throughput correct results
• Long airplane mode causes mis-behaviour for USB/NATA connection
Samsung Galaxy S22+ SM-S906U (AT&T)
• Forcing functions: UMTS forcing features not verified
• Forcing functions: LTE system and band lock released in device reboot
• Forcing functions: LTE PCI locking to weak cell not possible
Samsung Galaxy S22+ SM-S906U (T-Mobile)
• Forcing functions: UMTS forcing features not verified
Samsung Galaxy S22+ SM-S906U1 (Operator unlocked)
• Forcing functions: UMTS band locking not supported
• Forcing functions: LTE channel and PCI forcing don’t work, device stays in original
Samsung Galaxy Z Flip 4 SM-F721B (Global)
• Forcing functions: UMTS Channel and Scr. Code lock and GSM channel lock not supported
• Forcing functions: UMTS channel forcing drops network
• Forcing functions: LTE PCI and LTE channel forcing requires usage of forcing NATA method2 in
Outdoor device options, LTE PCI + LTE channel forcing works with default NATA method
• Non-rooted version not verified
Samsung Galaxy Z Fold 3 SM-F926B (Global)
• Only non-rooted version tested with Outdoor 9.01
Samsung Galaxy Z Flip 3 5G SM-F711B (Global)
• Forcing functions: UMTS channel forcing drops network (Outdoor 9.01)
• Only non-rooted version tested with Outdoor 9.01, Nemo FW version under testing (9.10)
• All app testing features are not verified with Outdoor 9.10
Samsung Galaxy A52 5G SM-A526B (Global)
• Forcing functions: CA mode change requires manual reboot
• Non-rooted: ip-capture, PEVQ-S, digital VQ not supported
Samsung Galaxy S21 5G SM-G991U (AT&T), S21+ 5G SM-G996U (AT&T)
Samsung Galaxy S21 5G SM-G991U (Verizon)
• Forcing functions: not supported with non-rooted

• IMS voice call does not work with Samsung Galaxy S21 G991U Verizon variant
Samsung Galaxy S21 5G SM-G991U (T-Mobile)
• Forcing functions: NR SA Band forcing does not work, leads to no service state
Samsung Galaxy S21 5G SM-G991U1 unlocked, S21+ 5G SM-G996U1 unlocked
Samsung Galaxy S21 5G SM-G991W (Canada)
• Forcing functions: Non-rooted: NR SA/NSA forcing not verified
• Non-rooted: If UARFCN is given manually to forcing dialog device remains offline
• All forcing functions not verified with Outdoor 9.0
Samsung Galaxy S21 5G SM-G9910 (China/TWN), S21+ 5G SM-G9960 (China/TWN)

• Full forcing functions require Nemo Firmware update and Nemo Outdoor 9.0 version
Samsung Galaxy S20+ 5G SM-G986U (AT&T)
• Volte testing (SIP signaling) requires Nemo firmware

• SMS, MMS, IP Capture not tested
• PEVQ-S not supported with 8.80
• Forcing functions: AMR type lock and CA enable/disable not tested
Samsung Galaxy S20+ 5G SM-G986U (Sprint)

• LTE Band lock not supported with 8.70 (device does not get attach after locking)
• PEVQ-S supported with 8.81
Samsung Galaxy S20+ 5G SM-G986U (Verizon)

• Forcing functions: with non-rooted terminal forcing does not work, firmware required.
Samsung Galaxy S20+ 5G SM-G986U (T-Mobile)

Samsung Galaxy S20+ 5G SM-G986U1(unlocked)

Samsung Galaxy S20+ 5G SM-G9860

• Forcing functions require Nemo Firmware update and Nemo Outdoor 9.0 version
Samsung Galaxy A90 SM-A908B

• Mobile to Mobile Voice Quality testing is supported, but there are issues with testing against fixed line
(Nemo Server)
• WhatsApp calls are not working in the receiving end
Samsung Galaxy S10 SM-G973U T-Mobile

• With Autodetect connection Modem port set to "Not used".
• LTE channel lock and PCI lock doesn't work. Issue 26023.
• Device network adapter physical address unvalid. Probably new FW required.
• VQ MOS scores are pretty poor in all systems and also lost synchronizations observed. NMR issue 26040.
• Forcing functions: LTE channel lock does not work
• Forcing functions: PCI lock does not wotk
• Forcing functions: Scr. Code lock and GSM channel lock are not supported
Samsung Galaxy S10 SM-G973U Sprint

• Samsung Galaxy S10 SM-G973U Sprint variant: In Volte calls lot of gaps in MOS results and missing
synchronizations. NMR issue 26024.
• LTE channel lock and PCI lock doesn't work. Issue 26022.
• Device network adapter physical address unvalid. Probably new FW required.
• In Volte calls lot of gaps in MOS results and missing synchronizations. NMR issue 26024.
• With Autodetect modem port set to "Not used".
• Forcing functions: LTE channel lock does not work
• Forcing functions: PCI lock does not work
• Forcing functions: Channel lock does not work
• Forcing functions: Scr.code lock, GSM, and CDMA/ECDO locking are not supported
Samsung Galaxy S10 SM-G973U AT&T variant
• all the forcing functions take a long time before device get back connected to network. Example system
lock can take 2-3 minutes before it attach again to network. Also SIP server doesn't registration after
lock has run. Need to do manual terminal radio on/off. Issue 26211.
Sierra Wireless/ Netgear LTE modems
Netgear Nighthawk M1 Mobile Router (MR1100)
• Basic data testing supported

• PEVQ-S not verified
• Forcing features not verified
Netgear Aircard 810S
• SMS and MMS testing is not supported

• The device does not support GSM technology
• Device has a SIM lock (to Telstra AUS network), and cannot be unlocked.
• SMS and MMS testing is not supported
• Forcing functions do not work
• "Force Idle after measurement" setting must be disabled from the device. Otherwise the next attach
attempt will fail.
• This device is supported with restrictions. Full documentation not available.

• Device autodetection is not supported. Add device manually to Nemo Outdoor.
• USB tethering must be “ON” on the device.
• Occasionally the device may disconnect the packet data connection by itself. In such a case, user needs
to activate the packet data connection via device connection manager.
• "Force Idle after measurement" setting must be disabled from the device. Otherwise the next attach
attempt will fail.
• Packet data connection activation fails occasionally
Netgear AirCard 340U
• It has been observed that with some laptops (problem seen with Lenovo T410, but may be valid with
others as well) data connection attempts may occasionally start failing. Device needs to be rebooted to
correct the situation
Sierra Wireless 330U USB modem
• In GSM UE is unstable
• PDP context activations and deactivations cause instability problems. Avoiding these commands when
using script files is recommended
• MMS message testing not supported
Sierra Wireless 313U/ 320U/ 330U
• With LTE max. DL data throughput is limited to ~50Mbps with 320U

• Occasionally the network adapter interface (NDIS) disappears and device cannot perform PS data
connection. Workaround is to use the modem with microSD card or by disabling microSD card from
the device. By default Sierra Wireless modems do not include microSD cards. The microSD can be
permanently disabled with either AT commands or via a command line utility. The command line
utility ItmTk.exe can be downloaded from KSM. For AT commands use e.g. Hyperterminal.
o AT!ENTERCND=”A710”
o AT!CUSTOM=”USBMSENABLE”,x 0=disable 1=enable
• The Watcher application must normally be running simultaneously with Nemo Outdoor in the
background if default settings of the application are used. However it is recommended to change the
default settings of the Watcher application to avoid any issues during measurements. If the user wants
to close the Watcher application but still wants to be able to conduct measurements with Nemo
Outdoor, the following settings from the Watcher application must be selected. NOTE! The option
names seen in the Watcher application depend on the application version. If multiple modems are used
simultaneously on the same computer, these settings must always be changed!
Figure 2. Watcher application.
• Watcher autolaunch must be disabled. Select “No”

• On exit, select “Do nothing”
• USB interfaces: Dialup networking “Disabled”
• USB interfaces: MicroSD “Disabled”
• Check for updates, select “Never”
Sonim Handsets
Sonim XP7700
• Limited support available:

o Calls: CS calls and VoLTE supported
o SMS testing supported
o FTP data testing supported
• System and band locks requires reboot
• Voice quality testing not supported
Sonim XP8800
• Limited support available:

o Calls: CS calls and VoLTE supported
o With SMS testing, sending message is not supported
• Limited forcing features supported. Requires reboot.
• Voice quality testing not supported
• Screen casting is not supported
Sony Handsets
Generic
• In the phone settings, screen lock method must be set to “none” for Browsing and video streaming
testing to work (YouTube, PEVQ-S, Netflix)
• Android 11 and 12: NATA tethering mode is not supported with Android 11 and 12 NATA devices, ADB
Forwarding mode can be enabled from NATA settings
• NATA and Handy cannot be installed at the same time. Force stopping Handy could function when
using NATA
Sony Xperia 1 V XQ-DQ54 (Europe), XQ-DQ72 (Asia/TWN)

• Forcing features for GSM/UMTS channel and 3G channel and scrambling code are not supported
• All OTT applications not verified with Outdoor 9.60
• Forcing features: Device restart required for LTE CA mode enable/disable
• Forcing features: Forcing Method2 usage required for separate LTE Channel and PCI locks
Sony Xperia 1 IV XQ-CT54 (Europe), XQ-CT72 (Asia/TWN), XQ-CT44 Japan

• Forcing features for GSM channel and 3G channel and scrambling code are not supported
• Forcing features: Device restart required for CA mode enable/disable
• Digital Voice Quality requires Nemo Outdoor 9.41 or newer
Sony Xperia 10 IV XQ-CC54 (Europe), XQ-CC72 (Asia/TWN)

• Forcing features for GSM channel and 3G channel and scrambling code are not supported
• Digital Voice Quality requires Nemo Outdoor 9.41 or newer
Sony Xperia 1 III XQ-BC52 (Europe), XQ-BC62 (US), XQ-BC72 (Asia/Russia), XQ-BC42 (Japan)
• Forcing features for GSM channel and 3G scrambling code are not supported
• Netflix, Twitter and Instagram not supported
• Video call is not supported
Sony Xperia 5 II XQ-AS52

• Netflix and Viber not supported
• Lock to unavailable PCI does not stay on
• UMTS channel lock does not stay on unavailable channel
• Forcing features: Full support requires Firmware update and Nemo Outdoor 9.0
Xiaomi handsets
Xiaomi 13 / 13 Pro
• Forcing features: GSM channel and 3G scrambling code are not supported
device options, LTE PCI + LTE channel forcing works with default NATA method
• NATA autostart needs to be enabled manually from Android settings
• System rights need to be added manually in Android settings – apps – NATA settings
• Non-root version not fully verified. Non-root could require MIUI account to be added in phone and USB
Debugging (Security) option to be enabled in developer options
Xiaomi 12 / 12 Pro
device options, LTE PCI + LTE channel forcing works with default NATA method
• Non-root version not fully verified. Non-root could require MIUI account to be added in phone and USB
Debugging (Security) option to be enabled in developer options
Xiaomi 11T Pro
mode can be enabled from NATA settings
• Forcing features: LTE Channel and PCI forcing to unavailable, connects to strongest available
• PEVQ-S fails with longer tests (under study with 9.20)
Xiaomi Mi 11
Xiaomi Mi10T / Xiaomi Mi10 / Xiaomi Mi10 Pro
Other handsets and devices

RoHS NB-IoT
Super Design v3.0
• Connection to device is lost when device enters PSM mode
Samsung Shannon (5100/5123/5123A,5123B, 5133, 5300, 5308) – based

devices
Generic notes
• Samsung Shannon based devices are not recommended to be used for MIMO 4x4 testing due to the
following reasons listed below. Keysight does not take any responsibility to replace the devices free of
charge after initial delivery
o LTE RSSI/ RSRP/ RSRQ are not available for eNB TX-antenna ports 2-3
o Reported LTE PDSCH Rank indicator (RI) is not valid when MIMO configuration is higher than
2x2
• LTE PDSCH throughput per codeword is not available
• LTE PDSCH throughput per PRB is not available

• The following parameters are reported as a single value per reporting period. Not per TTI
o Control format indicator (CFI)
o PDSCH / PUSCH PRB allocation
o PDSCH/ PUSCH modulation and MCS
o LTE precoding matrix indicator (PMI)
• Samsung Galaxy S8, S9, S10: Voice Quality testing is recommended to be done with “Voice only” scripts.
It has been observed that data connections in the script may have effect on Voice Quality results
• Check latest Nemo Outdoor Shannon data sheet for details on reported parameters. For example, UMTS
Cell ID and GSM WB AMR codec are not reported.
• MMS testing is not supported (Samsung S8, S9, S10)
• System locking (GSM/WCDMA/LTE) and Band locking (WCDMA/LTE) are supported, when NATA is
used with the device
o With LTE band locking does not work for TD-LTE bands. They are always enabled, if the device
supports TD-LTE.
• Multiple bands/RATs locking is not supported with all devices
• With most Shannon chipset-based devices modem port is not responsive and needs to be set to “not”
used with Outdoor. Autodetect does this automatically. There are no major drawbacks to set the
modem port to “Not used” in Nemo Outdoor, when Nemo Active Testing Application is used with the
device.
o When the device is to be used with Invex, the modem port setting must be set to “Not used”
• If the device does not have SIM card inserted, opening the modem port will always fail.
• Nemo Active Testing Application is highly recommended. Without NATA some features may not work
correctly.
• Samsung USB drivers need to be updated for the latest version. With Samsung S22 and S23 devices use
version 1.7.5 or newer
mode can be enabled from NATA settings. Outdoor/NATA 9.20 does this automatically.
• If Nemo Firmware Manager has been used with PC, Samsung ports could appear as libusb-win32
device. Driver needs to be updated manually per USB port (browse my PC – Let me pick from list.. –
select Samsung Mobile USB CDC Composite device). With newer NFM versions, driver uninstall can be
done from tool.
• Android 13/14: With some non-root devices, notification permission rights need to be given manually
from phone. Settings – Apps – NATA – upper corner *** -> allow restricted permissions. After this
notifications can be enabled.
Samsung (Shannon modem) handsets
Samsung S24 SM-S921B, S24+ SM-S926B
• Volte testing (SIP signaling) requires Nemo firmware in encrypted networks

• NATA not starting if Handy is installed (force stop or uninstallation of Handy needed)
• Forcing features: AMR codec mode forcing not supported
• Forcing features: NR System and Band forcing not supported with non-root
• Only non-root version is tested during Nemo Outdoor 9.70 release
Samsung A53 5G SM-A536B, SM-A536E

• Forcing features: NR System and Band forcing not supported with non-root device
• Forcing features: not all forcing features are verified with Nemo Outdoor 9.40
Samsung Galaxy S22 SM-S901B, S22+ SM-S906B and S22 Ultra SM-S908B (Europe/CIS)

• Voice Quality: with EVS networks, POLQA 2.4 could give lower results than POLQA 3.0
• Forcing features: LTE PCI forcing not supported with non-root device and Nemo Firmware device
• Forcing features: NR System and Band forcing not supported with non-root device
• Device could lose NR capability after 2G/3G/4G forcing and device restart, “release locking”
resolves this. With non-root device factory reset is required
• Netflix testing is not supported
Samsung Galaxy S21 5G SM-G991B, S21+ 5G SM-G996B and S21 Ultra 5G SM-G998B

• LTE related forcing features are not supported with non-rooted device in Outdoor 8.90
• Forcing features: full forcing features require firmware update and Nemo Outdoor 9.0
• Forcing features: NR system/band forcing not supported with non-root device
• Forcing features: NR Band forcing supported with bands 1, 3, 5, 7, 8, 38, 40, 41, 77, 78. FW update and
Outdoor 9.20 or newer required for NR band 28 lock.
• Device could lose NR capability after 2G/3G/4G forcing and device restart, “release locking” resolves
this. With non-root device factory reset is required
Samsung Galaxy Note 20 5G SM-N981B and Note20 Ultra 5G SM-N986B

• LTE Band locking not supported with Outdoor 8.61-8.91
• Forcing features: full forcing features require firmware update and Nemo Outdoor 9.0
• Forcing features: NR Band forcing supported with bands 1, 3, 5, 7, 8, 38, 40, 41, 77, 78
• Device could lose NR capability after 2G/3G/4G forcing and device restart, Nemo Outdoor 9.0 and
“release locking” resolves this.
• Nemo Outdoor version 9.20 required for Android 12
Samsung Galaxy S20 5G SM-G981B, S20+ 5G SM-G986B and S20 Ultra 5G SM-G988B

• Forcing features: LTE Band locking not supported with Outdoor 8.61-8.91
• Forcing features: full forcing features require latest firmware update and Nemo Outdoor 9.0 or newer
• Forcing features: NR SA band forcing not supported
• Device could lose NR capability after 2G/3G/4G forcing and device restart, Nemo Outdoor 9.0 and
“release locking” resolves this.
Samsung Galaxy S10 SM-G973F (applies also to S10+ SM-G975F and SM-G970F)
• NATA not starting if Handy is installed (force stop Handy needed).
Samsung Galaxy 9+ SM-G965F
• Tested with basic CS voice call and data

• Ending calls do not work. Workaround is to end the call manually via device UI
• YouTube PEVQ-S and Netflix not verified
• VoLTE/ ViLTE/ VoWiFi and ViWiFi not verified
• 23531: TeamViewer remote connection not supported

• CS video call not supported
• SMS/ MMS testing not supported
• LTE channel and PCI locks require reboot
• UMTS scr lock: Channel lock doesn't hold while scrambling code lock. Scr. lock holds. Shannon specific
restriction.
• LTE PCI lock: PCI lock holds, but channel lock is not activated. Shannon specific restriction.
• While serving system is GSM audio MOS values are not valid
• Headset/ headphones must not be connected to device. This will cause audio synchronization failure
Samsung Galaxy 9 SM-G960F
• In phone settings the screen lock must be changed to 'None'. Other-wise video streaming testing cannot
be done (YouTube PEVQ-S and Netflix)
• ViLTE/ VoWiFi and ViWiFi not verified
• 23531: TeamViewer remote connection not supported
• CS video call not supported
• LTE channel and PCI locks require reboot
• UMTS scr lock: Channel lock doesn't hold while scrambling code lock. Scr. lock holds. Shannon specific
restriction.
• LTE PCI lock: PCI lock holds, but channel lock is not activated. Shannon specific restriction.
• If using Android 8 and while serving system is GSM audio MOS values are not valid. This is not an issue
with Android 9.
• 24093: Headset/ headphones must not be connected to device. This will cause audio synchronization
failure
Google Pixel handsets (Tensor, Tensor2, Tensor3)
Google Pixel 6 GB7N6, Pixel 6 Pro G8VOU
• Voice Quality supported only with NIDI
• Android 13: PEVQ-S, Youtube and Browsing not supported in GSM and UMTS with Outdoor 9.30
• Forcing features: LTE Channel and PCI locks require manual device restart
• Forcing features: NR System and Band forcing not supported
• Forcing features: UMTS Channel forcing not supported
Google Pixel 7, Pixel 7 Pro
• Nemo Outdoor 9.40 and NATA 9.40 required for testing (64bit only device)
• Forcing: NR related forcing not supported
• Forcing: Not all forcing features verified
Google Pixel 8 GPJ41/G9BQD/ GZPFO, Pixel 8 Pro GC3VE/ G1MNW/GE9DP
• Voice Quality supported only with NIDI, OTT App Voice Quality is not supported.
• Forcing: GSM Band lock: Lock to single Band fails, lock to two bands is ok.
• Forcing features: LTE Channel and PCI locks require manual device restart
• Forcing features: NR System and Band forcing not supported
• Forcing features: UMTS Channel forcing not supported
Mediatek chipset -based devices

Generic notes
• Nemo Outdoor 9.60 or newer recommended

• 2G/3G KPI’s are not supported. See 4G/5G KPI’s in Nemo Outdor Mediatek datasheet
• With some phones it is recommended to connect device in airplane mode.
• Airplane mode is required once before starting measurements
• Forcing is not supported (Nemo Outdoor 9.70)
• Packet capturing, PEVQ-S, OTT apps not supported
• Call answering: one second delay is required in Outdoor device settings with some devices
• Voice Quality requires NIDI
• Xiaomi and Redmi phones: MIUI 14.01 or newer recommended. MI account and USB Debugging
(Security) should be enabled in developer options.
• NDM version 1.80 recommended for Xiaomi/Redmi, Oneplus and Motorola devices.
Qualcomm 3GPP2-based UEs

Generic notes
• If auto detection is used to add device to Nemo Outdoor the CS dial up connection should be manually
changed to “not used”. This can be done via device properties window.
• Currently MMS send functionality is supported with CDMA terminals. Received MMS messages are not
detected.
• FER F-SCH (supplemental channel) is not working correctly
Scanning Receivers
Nemo FSR1 scanner
• The following TD-SCDMA parameters are not supported:

o Carrier RSSI (frequency scanning mode)
o Cell index
o Neighbor cell parameters ID/ channel number
o SIR (PCCPCH)/ SIR (SYNC DL)
• When narrow band (NB) and tunable down converters are installed to a base unit simultaneously,
channel style (BW) more than 5 MHz cannot be used if the selected channel is supported by both down
converters. A workaround is to remove the narrow band down converter to be able to select the
channel style up to 20MHz. This also limits the SIB1 decoding having NB and tunable down converters
simultaneously in use.
• GPS antenna should always be connected to the scanner receiver
• GPS fix must be acquired before starting CDMA/EVDO scanning
• GPS fix must be acquired once before BSIC can be decoded. After fix is acquired GPS connection / fix is
not needed anymore with GSM measurements
• Please read the separate Nemo FSR1 Release Note for further information
PCTEL scanners
PCTEL HBflex
• HBflex support implemented to Nemo Outdoor version 8.3.1. Scanner requires firmware updates to
support RSSI power measurements and 5G NR decoding.
• Please contact Keysight NWS sales for further information.
PCTEL IBflex Lite
• CDMA / EVDO: Not verified

• LTE
o P-SCH CINR is not supported
o Detected TX antenna ports not supported
• UMTS: Aggregate data processing method is not supported
PCTEL IBflex (8900-E)
• BW Autodetect is not supported in Band scan by the new IBflex scanner

• The 10MHz-6GHz range is not supported in band scan by the new IBflex scanner
PCTEL MXflex
• The scanner must not be added to Nemo Outdoor before the scanner LED turns green. During the
scanner start-up process the LED is amber. If the scanner is added to Nemo Outdoor in the middle of
the start-up process, it can cause Nemo Outdoor to crash.
• Missing neighbor difference to strongest pilot reports value 0.0dBm
• P-SCH CINR is not available
PCTEL MX
• The scanner must not be added to Nemo Outdoor before the scanner LED turns green. During the
scanner start-up process the LED is amber. If the scanner is added to Nemo Outdoor in the middle of
the start-up process, it can cause Nemo Outdoor to crash.
• When MX scanner receiver is used with a Nemo Invex UIC module, other devices must not be connected
to the same UIC module.
• The power switch must remain in the Drive Test position at all times. The Indoor Test Mode is not
available at this time.
• The GPS antenna needs to be connected before power up.
• Occasionally scanner device does not accept scanning configuration sent by Nemo Outdoor application
even though status is “scanning”. Device is not reporting any scanning results. In such situations it is
advised to open device measurement properties again and press ok. Issue have been reported to the
vendor.
• Detecting and connecting the PCTel MX scanning receiver for the first time takes a much longer time.
Time depends on the number of available COM ports installed in the computer. With Win XP computers
the required time is longer than with Win7 operating system. The required time is ~2min- 10 min. It is
recommend to save the hardware configuration file with Nemo Outdoor after the first connection to the
scanner receiver. Starting device with an existing hardware configuration file is much faster.
Rohde & Schwarz scanners

Generic notes
• Legacy scanner details in Outdoor 8.90 test device technical notes.

• After starting the measurement it can take up to 10- 20 seconds before the scanner receiver starts
reporting the scanning results
• Problems with some Dell Notebooks.
o Possible problems are caused by some of the drivers installed on Dell systems by default. The
problems can be solved out by removing the original system and re-installing the operating
system only with the components necessary to operate with the scanners.
o It has been recognized that the systems which only provide 1024 bytes Host rec. buffer size
(instead of 2048 bytes) can cause issues with the scanning receivers. This can be checked from
the Rohde & Schwarz TSMx Device driver properties tab. Dell Vostro 1014 model has been
found to be incompatible with the R&S TSML-GW scanner. GSM scanning cannot be performed.
Figure 3. TSMQ driver properties.
Rohde & Schwarz TSME6
• Nemo Outdoor 8.3.1/ ViCom 16.25

o Occasional gaps with scanning results are possible
• TSME6 scanning receiver requires the LAN adapter to be configured for 9k jumbo frame packets. 9k
jumbo frame must be supported with the network adapter card of the laptop controlling the scanning
receiver. For example, Dell M4700, Dell Latitude E63 and E65 support 9k jumbo frames. If the laptop
does not support 9k jumbo frame, it is recommended to use ExpressCards that provide a
supplementary Ethernet connection, like this Startech EC2000S:
http://www.startech.com/Networking-IO/Adapter-Cards/Dual-Port-ExpressCard-Gigabit-Ethernet-
NIC~EC2000S
o Please check the supported jumbo frames from the network connection properties of your
laptop before connecting the scanning receiver
• To be able to measure LTE Time Offset, a GPS antenna must be connected to the receiver
Rohde & Schwarz TSME

• LTE time offset measurement is not supported due to issue with integrated GPS receiver
• TSME scanning receiver requires the LAN adapter to be configured for 9k jumbo frame packets. 9k
jumbo frame must be supported with the network adapter card of the laptop controlling the scanning
receiver. For example, Dell M4700, Dell Latitude E63 and E65 support 9k jumbo frames. If the laptop
does not support 9k jumbo frame, it is recommended to use ExpressCards that provide a
supplementary Ethernet connection, like this Startech EC2000S:
http://www.startech.com/Networking-IO/Adapter-Cards/Dual-Port-ExpressCard-Gigabit-Ethernet-
NIC~EC2000S
o Please check the supported jumbo frames from the network connection properties of your
laptop before connecting the scanner receiver
• To be able to measure LTE Time Offset, a GPS antenna must be connected to the receiver
Rohde & Schwarz TSMW
• Nemo Outdoor 8.4.0/ ViCom 16.25

o LTE time offset measurement is not supported due to issue with integrated GPS receiver
• In case of abnormal behavior e.g. scanning results are freezing, it is recommended to restart Nemo
Outdoor. It is also recommended to power cycle the scanning receiver. Please check network card
jumbo packet and flow control settings
Figure 4. Network connection properties.

Other Devices
GPS receivers
• In case GPS fix is lost frequently during driver test, it is advisable to turn off the car radio to see if it is
generating spurious emissions that are interfering with the GPS receiver

Test Device Technical Notes Nemo Outdoor 9.70 February 2024

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Device Technical Notes Nemo Outdoor 9.70 February 2024

Uploaded by

Copyright:

Available Formats

Test Deviceer’s Manual

Mediatek chipset -based devices ............................................................................................................... 24

Discontinued Chipsets & Test Device Handler Software Options

Product Code Handler Software Option Chipset/ Vendor Notes

• Bandrich Bandluxe C320 (Nemo Outdoor 7.2 Release Notes)

• Measurement profiles cannot be used with Tetra calls

• Plug in a headset (Nokia Headset Type HDC-9)

Hisilicon Kirin 990/9000-based handsets

Huawei P40 5G, ANA-NX9, Huawei P40 Pro 5G ELS-NX9

Huawei Mate30 Pro ELS-N29

Qualcomm (MDM92xx/96xx, MSM89xx, Snapdragon)-based UEs

Figure 1. User Interface properties.

Asus Smartphone for Snapdragon insiders (ASUS I007D)

Bittium Tough Mobile

Essential Phone PH-1

• Limited forcing features:

Google Pixel 4 G020M (global) and G020I (US)

• Voice Quality is not supported

Nokia 8.30 5G (TA-1243)

Nokia XR20 (TA-1362 Global, TA-1371 US)

Nokia X30 (TA-1450)

Knowyou NB-IoT/LTE-M devices

Knowyou KDC-5737 Rel13

Knowyou KDC-6336 Rel14

• PCI lock not supported.

OnePlus8 IN2015 (US)

OnePlus 8 Pro IN2023

OnePlus 9 LE2113 / Oneplus 9 Pro LE2123 / Oneplus 9 Pro LE2125

OnePlus 10 Pro NE2213

• USB Autostart and Smartcharging not available

OnePlus 10T CPH2413 / CPH 2415 / CPH2417

Motorola Edge 40 Pro 5G XT2301-4, Motorola Edge+ (2023) XT2301-1

Motorola Edge 30 Pro 5G XT2201-1

Motorola Edge 20 Pro 5G XT2153-1

Motorola Edge Plus 5G XT2061-3 (EU)

Samsung Galaxy S24 Ultra SM-S928B (Global)

Samsung Galaxy S24+ SM-S926U/U1 (US)

Samsung Galaxy S24+ SM-S9260 (CHN/TWN)

Samsung Galaxy Z Flip5 SM-F731B (Global)

• UMTS is not supported

Samsung Galaxy S23+ SM-S916U, S23+ SM-S916U1 – US Operator and unlocked

Samsung Galaxy S23+ SM-S9160 – TWN,China

Samsung Galaxy S23+ SM-S916W - Canada

Samsung Galaxy S22+ SM-S916U (US variants)

Samsung Galaxy S22+ SM-S9060 (China, TWN)

Samsung Galaxy S22+ SM-S906U (AT&T)

Samsung Galaxy S22+ SM-S906U (T-Mobile)

Samsung Galaxy S22+ SM-S906U1 (Operator unlocked)

Samsung Galaxy Z Flip 4 SM-F721B (Global)

Samsung Galaxy Z Fold 3 SM-F926B (Global)

Samsung Galaxy Z Flip 3 5G SM-F711B (Global)

Samsung Galaxy A52 5G SM-A526B (Global)

Samsung Galaxy S21 5G SM-G991U (AT&T), S21+ 5G SM-G996U (AT&T)

Samsung Galaxy S21 5G SM-G991U (Verizon)

• Forcing functions: not supported with non-rooted

Samsung Galaxy S21 5G SM-G991U (T-Mobile)

Samsung Galaxy S21 5G SM-G991U1 unlocked, S21+ 5G SM-G996U1 unlocked

Samsung Galaxy S21 5G SM-G991W (Canada)

Samsung Galaxy S21 5G SM-G9910 (China/TWN), S21+ 5G SM-G9960 (China/TWN)

Samsung Galaxy S20+ 5G SM-G986U (AT&T)

• Volte testing (SIP signaling) requires Nemo firmware

Samsung Galaxy S20+ 5G SM-G986U (Sprint)

• Volte testing (SIP signaling) requires Nemo firmware