Nemo Outdoor 8.1.1 Release Note

er’s Manual
Technical Bulletin
and Release Notes
Keysight
Nemo
Insert the
Outdoor
Title in this8.1.1
Release
Space
1 | Keysight | Nemo Outdoor 8.1.1 Release Notes
Table of Contents
Introduction ...................................................................................................................................................................... 3
Copyright ................................................................................................................................................................. 3
New Features ................................................................................................................................................................... 4
Key features ................................................................................................................................................................. 5
Nemo Media Router ......................................................................................................................................................... 5
New features ................................................................................................................................................................ 5
New devices ............................................................................................................................................................ 5
Error corrections .......................................................................................................................................................... 6
Nemo Media Router licensing options ........................................................................................................................ 6
Compatibility and update process .............................................................................................................................. 7
Supported handsets with Nemo Media Router .......................................................................................................... 9
Error Corrections............................................................................................................................................................ 17
Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards ..................................................................... 18
New Devices ................................................................................................................................................................... 18
Generic Test UE Software Handler Updates ................................................................................................................. 19
Qualcomm Software Handler Updates .......................................................................................................................... 20
Samsung Shannon Software Handler Updates ............................................................................................................. 21
Neul Software Handler Updates .................................................................................................................................... 22
Generic Scanner Handler Updates ................................................................................................................................ 23
Keysight spectrum analyzers and scanning receivers.............................................................................................. 23
PCTel scanner handler updates ................................................................................................................................ 23
Rohde & Schwarz scanner handler updates ............................................................................................................. 23
User Interface Updates .................................................................................................................................................. 24
Nemo File Format ........................................................................................................................................................... 25
Computer Hardware and Software Requirements ........................................................................................................ 26
Device Configuration and Workspace Files .................................................................................................................. 27
Nemo Outdoor accessories and verified configurations .......................................................................................... 27
Installation...................................................................................................................................................................... 27
First-time installation ................................................................................................................................................ 27
Update/Upgrade ........................................................................................................................................................ 27
Uninstallation ............................................................................................................................................................. 28
Dongle runtime drivers .............................................................................................................................................. 28
Limitations and Issues with Windows 7 Operating System .......................................................................................... 28
Known Issues ................................................................................................................................................................. 29
General and user interface ........................................................................................................................................ 29

Nemo Analyze ............................................................................................................................................................ 30
Nemo Cloud ............................................................................................................................................................... 30
Nemo Media Router ................................................................................................................................................... 31
Nemo Media Router for Android ........................................................................................................................... 31
Nemo Media Router for iOS .................................................................................................................................. 32
Nemo Backpack (former Nemo Walker II)/ Nemo Carrying Case (former Nemo Multi Lite) ................................... 32
Applications and protocols........................................................................................................................................ 33
Troubleshooting Device Connectivity Issues ................................................................................................................ 36
Troubleshooting Data Transfer Issues ........................................................................................................................... 36
PS connection works but no data ............................................................................................................................. 36
Antivirus filtering ....................................................................................................................................................... 37
Low data throughputs................................................................................................................................................ 37
All Windows versions ............................................................................................................................................ 39
Windows 7 ............................................................................................................................................................. 40
Issues with HTTP browsing testing ........................................................................................................................... 42
Low data throughput with Nemo Media Router application .................................................................................... 42
Introduction
This document contains the release notes of Nemo Outdoor version 8.1.1, released December 2017. The
document describes new functionalities and features.
Copyright
The information contained in this document is confidential and no part of it may be copied or reproduced in
any form without the written consent of Keysight Technologies, Inc. Additionally, this document is not to be
passed to or discussed with third parties without the prior written permission of Keysight.
Keysight’s products are subject to continual development and specifications may change. Users of Keysight’s
products and documentation should exercise their own independent judgement to evaluate the suitability of
Keysight’s products and documentation for their particular use. Keysight does not accept any liability arising
from the application or use of the product or this documentation.
All reasonable care has been made to ensure that this document is accurate. If you have any comments on
this document, or would like details of any Keysight products, services or equipment, please contact us
through the Keysight Website.
December 2017
New Features
Nemo Outdoor 8.1.1 release includes the following new main features:
• Sequence-based end to end call synchronization between field unit and Nemo Server
• Mute call and missing audio detection with VoLTE calls
• Enhanced Voice Services (EVS) codec support with Samsung Shannon based devices
• Speech path delay (SPD) with VoLTE
• Enhanced 4x4 MIMO information elements
• New test devices:
o Essential Phone PH-1 including support for E-UTRA band 42
• Nemo File Format version 2.33
Sequence-based end to end call synchronization

The new sequenced-based end-to-end call synchronization method between a field unit and Nemo Server
provides perfect call statistics at both ends, field unit and Nemo Server, regardless of call connection success
and even in the most difficult cellular environments, such as out of coverage. By utilizing timing and pre-
determined test sequences, a data connection is not required during the measurements. The new feature has
been developed for Nemo Handy, Nemo Outdoor/Invex and Nemo Server platforms and it is independent of
the current script-based implementation. Requires Nemo Server version 5.x or higher.
Key features
• Only a one-time data connection at the start of the measurement is needed
• No data connection during the measurement is required, but a data connection may provide optional
time synchronization to compensate clock drifts and to abort test sequence if needed
• Perfect call attempt statistics at both ends (field unit and fixed unit) regardless of call connection
success or abnormal issues in the cellular network. Test devices are reserved only for voice testing
• Each channel (field test terminal/landline couple) generates one file on A-side and one file on B-side.
A and B files have the same name with the « B_ » distinction
• A unique call ID is written to each call session at both sides
• When the measurements are aborted from the field side and then restarted, a new B-file is opened
and the previous one is closed properly
• Measurement file event timestamps are written based on time zone-corrected time base
• Flexible test call patterns, such as 1:1 2:1 1:3 (MOC / MTC)
• Possibility to define independent groups of test devices for call sequencing
• User can create and modify generic call sequence patterns, including the following:
o Originated call count
o Terminated call count
o Repeat count
o Call duration
o Wait duration
Nemo Media Router

New features
New devices
The following new devices are verified and approved by Keysight Technologies:
o Essential Phone PH-1

Error corrections
Support Ticket Title
Fixed issue related IP Capturing with full logging -option.

Improved Huawei U-vMOS. Handling initial buffering changed. As a result of this change, the
loading score will remain more constant, and thus enhance the overall MOS.
Fixed the issues with PEVQ-S video resolution. Earlier the video resolution information was taken
from YouTube API instead from the PEVQ-S library. This fixes inconsistency between video quality
downlink event (VQDL) event bitrate, video MOS values taken from PEVQ-S library and the DSS
event video resolution value.
67713 Fixed issue with Facebook scripting hanging
Fixed crash issue with YouTube streaming that occurred approx. after a few hundred videos
Fixed issue with HTTP browsing scripting hanging
Fixed problem of disconnecting a just answered phone call
Nemo Media Router licensing options
Licenses can be easily upgraded over the air (OTA) by launching the Nemo Media Router application after
installing the application to the handset or via Nemo Outdoor user interface with NMR version 7.90 onwards.
The following license options are available with Nemo Media Router version 8.00 for Android:
Product Code Description
NTA50054A Nemo Media Router basic Includes voice call and VoLTE support. Requires also Nemo
Outdoor or Nemo Invex PESQ & POLQA licenses for voice
quality testing (optional license)
NTA50055A Nemo Media Router data and Includes basic data and social media applications (FTP, Ping,
application software testing option HTTP/ HTTPS, YouTube video streaming, and HTML browsing
protocols)
NTA50056A Nemo Media Router WLAN software Enables WLAN measurements
option NOTE! Not available with HIM modules /2 slot wide HIM.
Required with VoWiFi and ViWiFi measurements
NTA50057A Nemo Media Router PEVQ-S Enables PEVQ-S video streaming analysis option. (YouTube).
software testing option One license per test handset
NTA50058A Nemo Media Router IMS audio and Enables IMS audio and video call quality testing. One license
video call quality software option per test handset
NTA50097A Nemo Media Router Pro Includes Nemo Media Router basic, Nemo Media Router data
and application software testing option, Nemo Media Router
WLAN software option
NTA50120A Nemo Media Router U-vMOS U-vMOS is Huawei’s objective criteria for measuring video
software testing option experiences based on the actual user experience. Algorithmn
is running on- device and own license option is needed per
test handset. Please see the release documentation for
compatible devices
Table 1. NMR 8.10 license options.

Compatibility and update process

Application Version Information
Nemo Media Router 8.11.286 (for Android)

1.10.14 (for iOS 11)
Nemo Browser nemobrowser-53.0.1.android-arm-final2.apk
Netflix 4.16.1 build 15145
Nemo Outdoor 8.1.1.16
TeamViewer (PC) 11.0.53254
NOTE! To be used only with Android- 10.0.43174
based handsets 10.0.47484
TeamViewer QuickSupport (Android- teamviewer_quicksupport_11.0.4203.apk
based test handset)
NOTE! To be used only with Android-
based handsets
TeamViewer QuickSupport Add-on for teamviewer_quicksupport_addon_samsung_10.0.3086.apk
Samsung
TeamViewer QuickSupport Add-on for teamviewer_quicksupport_addon_htc_10.0.3086.apk
HTC
Table 2. Compatible versions.
Nemo Media Router version 8.11 is compatible with Nemo Outdoor 8.1.1 NOTE! NMR Android versions 1.0 or
1.1 are not supported with Nemo Outdoor version 7.3.0.6 or higher. Customers using Nemo Media Router
Android versions 1.0 or 1.1 should not update Nemo Outdoor to the latest version before updating the Nemo
Media Router application on the test handsets. Nemo Media Router application updates can be done using
the over the air update via NMR user interface from version 2.30.099 onwards or using the local NMR
application software update via Nemo Outdoor user interface from version 7.9.0 onwards.
To check for OTA software updates, make sure that Wi-Fi or mobile data is enabled, tab the button at the
bottom of the NMR main view and select Check for updates. Notice! Nemo browser is a separate installation
package that needs to be installed to the NMR test handset after NMR has been updated to the latest version.
If Nemo Browser is not installed, you need to manually download the Nemo browser APK file to your Nemo
Media Router handset from https://www.keysight.com/ssoauth/login.jsp. Alternatively, you can use the below
QR code to load the latest Nemo Browser version or using this URL from your Android browser:
http://handy.nemo.fi/Browser/Nemobrowser.apk
Figure 1. QR code
NOTICE: Do not launch the Nemo Browser directly. Nemo Handy and Nemo Walker Air will automatically
Please follow the steps below.
Nemo Outdoor/ Nemo Invex II NMR test handsets
1. In case your test device is Samsung Galaxy S8 SM-G950F, updating the firmware is required.
Please contact nemo.support@keysight.com for further information
2. Update Nemo Media Router to the latest version using OTA update or local update method.
3. Use local update to install the Nemo browser (nemobrowser-53.0.1.android-arm-final2.apk) to
your Nemo Media Router handset.
4. Install the file and follow the instructions.
5. Update Nemo Outdoor to version 8.1.1.
6. Re-start the Nemo Media Router application.
Do not launch Nemo browser directly. Nemo Media Router will automatically launch the
browser and at the same time activate the API in the browser. In case you open the
browser manually please shut down the application before conducting HTML testing
with Nemo Outdoor.
When updating NMR from version 2.20.xx or older, please see the Nemo Outdoor user manual chapter
Installing Nemo Media Router.
Nemo Media Router for iOS is available from the App Store.
Supported handsets with Nemo Media Router
The handsets shown in the table below are supported with the Nemo Media Router application.
Product Code Handset Firmware/ NMR/ Nemo PEVQ-S video Screen VQMon, u-vMOS
Nemo ID Teamviewer Outdoor streaming Casting Audio/ Video
versions version analysis quality
(with monitoring1
(with initial initial
release) release)
NA Essential 2.0.c4-M1.3.1 8.11.286 8.1.1.16 Yes No No Yes
Phone PH-1 (8998.gen Nov 1
2017 22:44:47)
Nemo ID: 22759/2
NTT20078A Samsung "MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes Yes No No

Galaxy S8 00006-
SM-G950U 8998_GEN_PACK-
(AT&T) 1.90474.8.97734.8
(8998.gen Jul 14
2017
14:01:05)","22194"
,"1","samsung/drea
mqltesq/dreamqlte
sq:7.0/NRD90M/G
950USQU1AQGA:u
ser/release-keys"
NTT20084A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 No No No No

Galaxy S8 00167-
(Sprint) 1.107921.1
(8998.gen Jul 29
2017
11:40:10),"22255",
"1","samsung/drea
mqltesq/dreamqlte
sq:7.0/NRD90M/G
950USQU1AQGL:us
er/release-keys"
NTT20079A Samsung "MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes Yes No No

Galaxy S8 00006-
(T-Mobile) 1.90474.8.97734.8
(8998.gen Jul 14
2017
14:01:05)","22194"
,"1","samsung/drea
mqltesq/dreamqlte
sq:7.0/NRD90M/G
950USQU1AQGA:u
ser/release-keys"
NTT20083A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 No No No No

Galaxy S8 00167-
(Verizon) 1.107921.1
(8998.gen Jul 29
2017
11:40:10),"22255",
"1","samsung/drea
mqltesq/dreamqlte
sq:7.0/NRD90M/G
950USQU1AQGL:us
er/release-keys"
NTT20069A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes No No No

Galaxy S8 00152-
SM-G950W 8998_GEN_PACK-
(Canada 1T (8998.gen Aug
variant) 3 2017
10:43:43)","22179"
,"1","samsung/drea
mqltevl/dreamqltec
an:7.0/NRD90M/G
950WVLS1AQH1:u
ser/release-keys
NA Samsung MPSS.AT.2.0.c2- 8.10.273 8.1.0.12 Yes Yes No Yes

Galaxy S8 00593-
SM-G9500 8998_GEN_PACK-
1.108464.1
(8998.gen Aug 16
2017
19:26:46)","22404"
,"1","samsung/drea
mqltezc/dreamqlte
chn:7.0/NRD90M/
G9500ZCU1AQH6:
user/release-keys
NA Samsung N950FXXU1AQHB, 8.10.273 8.1.0.12 Yes No No No

Galaxy Note ICDver 5.18,
8 SM- chipset
N950F 0x355,"22440","1",
"samsung/greatltex
x/greatlte:7.1.1/N
MF26X/N950FXXU
1AQI1:user/release
-keys"
NTT20065A HTC U11 MPSS.AT.2.0.c4- 8.02.245 8.02.22 No No No No

(2PZC30000 00242.1-
) 8998_GEN_PACK-
1.99509.3.100016.
1 (8998.gen May
23 2017 18:47:46)
NTT20064A Sony Xperia "MPSS.AT.2.0.c4.3- 8.02.245 8.02.22 Yes Yes No Yes

XZ Premium 00006-
G8142 8998_GEN_PACK-
single 1.94857.13
(8998.gen May 25
2017
18:33:40)","21859"
,"1","Sony/G8142/
G8142:7.1.1/45.0.
A.5.1/475998232:u
ser/release-keys"
NTT20063A Sony Xperia "MPSS.AT.2.0.c4.3- 8.02.245 8.02.22 No No No No

XZ Premium 00006-
G8141 multi 8998_GEN_PACK-
1.94857.11
(8998.gen May 1
2017
17:14:51)","21722"
,"1","Sony/G8141/
G8141:7.1.1/45.0.
A.1.229/42111011
82:user/release-
keys"
NTT20075A Samsung G950FXXU1AQDG, POLQA & PESQ 8.0.0.15 Yes (Requires No No Yes
Galaxy S8 ICDver 5.17, supported from version 8.01)
SM-G950F chipset 0x355 8.02.245 onwards
8.00.233
NTT20076A Samsung G955FXXU1AQC9, 8.00.233 8.0.0.15 Yes No No Yes

Galaxy S8+ ICDver 5.17, (Requires
SM-G955F chipset 0x355 version 8.01)
NTT40081A Samsung MPSS.TH.2.0.c2- 8.01.244 8.0.1.20 No Yes No No

Galaxy S7 00178-
SM-G930R7 M8996FAAAANAZ
(CSpire) M-1 (8996.gen Apr
13 2017
19:39:35)","21808"
,"1","samsung/hero
qlteacg/heroqlteac
g:7.0/NRD90M/G9
30R7WWU4BQD3:
user/release-keys
NA Samsung MPSS.TH.2.0.c2- 8.01.244 8.0.1.20 No No No No

Galaxy S7 00171-
SM-G930V M8996FAAAANAZ
(Verizon) M-1.81356.3
(8996.gen Mar 13
2017
16:13:31)","21521"
,"4","Verizon/heroq
ltevzw/heroqltevzw
:7.0/NRD90M/G93
0VVRU4BQA4:user
/release-keys
NTT20052A Samsung MPSS.TH.2.0.c2.1- 8.00.233 8.0.0.15 Yes No No

Galaxy S7 00018-
SM-G930P M8996FAAAANAZ
M-
1.78569.1.78978.1
(8996.gen Dec 21
2016
14:28:49)","21317"
,"1","samsung/hero
qltespr/heroqltespr
:6.0.1/MMB29M/G
930PVPE4APL6:en
g/test-keys
Not available Sonim MPSS.DI.2.0.1.c1- NMR 8.00.233 8.0.0.15 No Yes No

via Keysight XP7700 00017-
(DAAAANAZ Apr 28
2016 15:57:11)
MPSS.DI.2.0.1.c1.1
8-VOLTE-
(DAAAANAZ Dec 2
2016 15:53:04)
Not available Apple 1.33.00_DEBUG NMR 1.10.14 (iOS) 7.9.1.16 No No No

via Keysight Iphone 7 (MPSS. TH. Nov 6
(A1160) 2016 18:23:16)
NTT20050A Google Pixel MPSS.TH.2.0.2.c1- NMR 7.9.1.220 7.9.1.16 Yes Yes No

G-2PW4100 00005-
M8996FAAAANAZ
M-
1.78021.1.78053.1
(8996.gen Nov 19
2016
02:02:25)","20887"
,"1","google/sailfis
h/sailfish:7.1.1/NM
F26Q/3537182:use
r/release-keys
NTT40041A Huawei P9 21.201.00.00.031 NMR 7.90.210 7.9.0.9 No Yes No

EVA – L09
NTT40043A Sony Xperia 39.0.A.1.250 R7B NMR 7.90.210 7.9.0.9 No No No

XZ F8331 NO (1305-1010)
NTT40039A HTC 10M MPSS.TH.2.0.c1.8- NMR 2.52.177 7.8.2.18 Yes (7.90 Yes
(Orange & 00004- teamviewer onwards)
Taiwan M8996FaaaaNAZM 10.0.47484
variants) -
1.47560.3.48552.3 teamviewer_
(8996.gen Mar 31 quicksupport_11.0.
2016 22:18:46) 4203 and
(Orange variant) teamviewer_quicks
upport_addon_sam
sung_10.0.3086
MPSS.TH.2.0.c1.8. and QS Add-On:
00004.M8996FAAA HTC
ANAZM-
1.50355.1.51912.1
(8996.gen Apr 25
2016 15:13:02)
Taiwan variant
NTT40036A Sony Xperia MPSS.TA.2.0.c14- NMR 2.52.177 7.8.2.18 Not supported Yes
X F5121 00002-
8976_GEN_PACK-1
(8976.gen May 5
2016 03:38:55)
NTT40037A Sony Xperia MPSS.TH.2.0.c1.11 NMR 2.52.177 7.8.2.18 Yes (7.90 Yes
Performance -00006- onwards)
X F8131 M8996FAAAANAZ
M-1 (8996.gen Aug
10 2016 03:41:02)
NTT40038A Sony Xperia MPSS.TH.2.0.c1.11 NMR 2.52.177 7.8.2.18 Yes with NMR Yes
Performance -00006- 8.01 onwards
X F8132 M8996FAAAANAZ
M-1 (8996.gen Jun
2 2016 20:11:33)
NA Samsung N920GUBU2BPE4, 2.52.177 7.8.2.18 Yes NA

Galaxy Note ICDver 5.00, teamviewer_quicks
5 SM- chipset SS333 upport_
N920G
11.0.4203.apk
teamviewer_quicks
upport_addon_sam
sung_10.0.3086.ap
k
NTT40047A Samsung G935FXXE1APD1 2.51.164 7.8.1.14 Yes Yes Yes

Galaxy S7 Device requires an
edge (SM- engineering
935F, firmware for NMR
Optus) use
NTT40045A Samsung G928W8VLU2BPC5 2.51.164 7.8.1.14 Yes

Galaxy S6 , ICDver 5.00,
edge+ (SM- chipset SS333
G928W8)
NTT40040A Samsung MPSS.TH.2.0.c2- 2.51.164 7.8.1.14 NMR 7.91.220

Galaxy S 7 00060- onwards
(SM-G9300) M8996FAAAANAZ VoWiFi audio
M-
1.42191.6.43195.1 ViWiFI video
5 (8996.gen Mar 17
2016 16:28:28)
Not available Apple 1.56.00_DEBUG NMR for iOS 7.8.0.8

via Keysight iPhone 6S (MPSS.BO. Jan 13 v1.00.9
Network (A1688) 2016 18:02:43)
Testing
NTT40044A Samsung G928KKKU1AOH4 2.50.156 7.8.0.8 Yes

Galaxy 6 ICDver 4.90,
edge+ chipset SS333
(SM-G928K)
NTT40034A Samsung MPSS.BO.2.0.1.c3. 2.41.137 7.7.1.14 Yes Yes

Galaxy Note 5-00137- teamviewer_quicks
5 SM- M9635TAARANAZ upport_
N9200 M-1 (TAARANAZ
Nov 24 2015 11.0.4203.apk
20:51:00) teamviewer_quicks
upport_addon_sam
sung_10.0.3086.ap
k
NTT40004A Sony Xperia 32.0.A.6.170_R16B 2.41.137 7.7.1.14

Z5 E6653 (1298-3443 Telstra teamviewer_quicks
AU) upport_
11.0.4203.apk
NTT40001A Motorola MPSS.BO.2.5.c8- 2.41.137 7.7.1.14 Yes

Moto X Pure 00010- teamviewer_quicks
Edition M8994FAAAANAZ upport_
XT1575 M-1 (FAAAANAZ
Jul 23 2015 11.0.4203.apk
14:27:30)
NTT40031A Samsung G928FXXU1AOH3, 2.40.125 7.7.0.9 Yes

Galaxy S6 ICDver 4.90, teamviewer_quicks
edge+ SM- chipset SS333 upport_11.0.4203
G928F teamviewer_quicks
upport_addon_sam
sung_10.0.3086
NTT40032A Samsung N920IDVU1AOH3, 2.40.125 7.7.0.9 Yes

Galaxy Note ICDver 4.90, teamviewer_quicks
5 SM-N920I chipset SS333 upport_11.0.4203
teamviewer_quicks
upport_addon_sam
sung_10.0.3086
NTT40023A Samsung G920FXXU1AOCWI 2.31.108 7.6.1.12 Yes

Galaxy S6 CDver 4.80
SM-G920F
NTT40046A Samsung G920W8VLU1AOE1 2.31.108 7.6.1.12

Galaxy S6 , ICDver 4.61
SM-
G920W8
(Bell)
NTT40030A Samsung G920IDVU1BOF6, 2.31.108 7.6.1.12 Yes

Galaxy S6 ICDver 4.90,
SM-G920I chipset SS333
(APAC)
NTT40022A Samsung S6 MPSS.BO.2.0.1.c3. 2.31.108 7.6.1.12 Yes

SM-G920P 5-00023-
(Sprint) M9635TAARANAZ
M-
1.15020.1.15643.1
(TAARANAZ May 5
2015 01:51:10)
NTT40021A Samsung MPSS.BO.2.0.1.c3. 2.31.108 7.6.1.12 Yes

Galaxy S6 5-00051-
SM-G9208 M9635TAARANAZ
(Taiwan) M-
1.17099.2.17432.1
(TAARANAZ Apr 23
2015 10:06:47)
NTT40028A Samsung G920TUVU2COF8, 2.31.108 7.6.1.12 Yes From NMR

Galaxy S6 ICDver 4.61, 7.90 onwards
SM-G920T chipset SS333 ViLTE video
(T-Mobile) VoWiFi audio
ViWiFi
audio/video
NTT40035A Samsung MPSS.DI.3.0.c5- 2.30.099 7.6.0.7 Yes

Note 4 Note 00300-
SM-N910T M9625TAARANAZ
(TMOB) M-1.7386.2
(TAARANAZ Nov 11
2014 19:36:24)
NTT40003A Sony Xperia MPSS.DI.3.0.c9.1- 2.30.099 7.6.0.7 Yes

Z3 D6653 00022-
M8974AAAAANAZ
M-1 (AAAAANAZ
Nov 26 2014
03:27:54)
NTT40020A Samsung MPSS.DI.2.0.1.c2.2 2.20.078 7.5.0.5

Galaxy S5 -00006-
SM-G900M M8974AAAAANRZ
M-1 (AAAAANRZ
May 9 2014
21:44:23)
NTT40015A Samsung MPSS.BO.1.0.r10- 2.11.060 7.4.1.13 Yes Yes

Galaxy Note 00108-
4 M9635TAARANAZ
SM-N910F M-1.5514.1
(TAARANAZ Sep 16
2014 20:04:39)
NTT40016A Samsung MPSS.BO.1.1.r10- 2.11.060 7.4.1.13

Galaxy Note 00108-
4 M9635TAARANAZ
SM-N910G M-1.5514.1
(TAARANAZ Oct 4
2014 16:47:00)
NA Samsung MPSS.DI.2.0.1.c2- 2.11.060 7.4.1.13

Galaxy S5 00055-
SM-G900T1 M8974AAAAANRZ
M-1 (AAAAANRZ
(Metro PCS) May 23 2014
19:27:09)

Galaxy S5 -00006-
SM-G900R4 M8974AAAAANRZ
M-1 (AAAAANRZ
(US Mar 31 2014
Cellular) 01:04:01)
NA Samsung MPSS.BO.1.0.c1- 2.10.054 7.4.0.9

Galaxy S5 00091- (Data
4G+ SM- M9635TAARANAZ only, not
G901F M-1 (TAARANAZ voice
Aug 11 2014 quality)
11:59:20)

Galaxy S5 -00006-
SM-G900I M8974AAAAANRZ
M-1 (AAAAANRZ
Mar 29 2014
15:46:27). Android
4.2
NTT40007A Samsung MPSS.DI.2.0.1.c2.2 2.01.041 7.3.1.9 Yes

Galaxy S5 -00006-
SM-G900F M8974AAAAANRZ
M-1 (AAAAANRZ
Mar 29 2014
15:46:27). Android
4.2
NTT40009A Samsung M9615ACEHWMAZ 2.01.041 7.3.1.9 Yes

Galaxy S5 D1795
SM-G900T (ACEFWMAZ Aug
(T-Mobile) 17 2012 20:29:27)
NTT40010A Samsung M8930B- 2.01.041 7.3.1.9

Galaxy S5 AAAATAZM-
SM-G900P 5.0.060165
(Sprint) (BBAAATAZ Jan 30
2014 14:45:25)
NTT40011A Samsung M8930B- 2.01.041 7.3.1.9

Galaxy S5 AAAATAZM-
SM- 5.0.060165
G900W8 (BBAAATAZ Jan 30
(Bell) 2014 14:45:25)
NA Samsung M9615ACEHWMAZ 1.0.011 7.1.0.6

Galaxy S III D1795 2.00.034 7.3.0.6
(I9305) (ACEFWMAZ Aug
17 2012 20:29:27)
NA Samsung M9615A- 2.00.034 7.3.0.6 Yes

Galaxy S4 CEFWTAZM-
(GT-i9505) 4.0.17062
(ACEFWTAZ Apr 12
2013 18:16:13)
NA Samsung M8930B- 1.10.015 7.2.0.6

Galaxy S4 AAAATAZM- 2.00.034 7.3.0.6
Mini (GT- 3.2.27040
i9195) (BBAAATAZ Jul 15
2013 11:32:02)
NA Samsung M8974A- 2.00.034 7.3.0.6

Galaxy S4+ AAAANAZM-
(GT-i9506) 1.0.180095
(AAAAANAZ Dec 12
2013 16:26:28)
Android 4.3
NA Samsung SET_BY_CM 2.00.034 7.3.0.6

Galaxy Note (AAAAANAZ Sep 13
3 (SM- 2013 18:20:25)
N900T)
NA Samsung M8930B- 2.00.034 7.3.0.6

Galaxy S4 AAAATBZM-
Mini (SPH- 6.0.01049
L520 Sprint) (BBAAATBZ Nov 4
2013 20:22:08)
Table. Supported handsets with Nemo Media Router application.
Table 3. Supported handsets with Nemo Media Router application.
1 VQMon, Video quality monitoring description explanations:

• ViLTE video: video quality metrics available with ViLTE calls
• ViLTE audio: audio quality metrics available with ViLTE calls
• VoLTE audio: audio quality metrics available with ViLTE calls

• ViWiFi video: video quality metrics available with ViWiFi calls
Huawei u-vMOS
• U-vMOS captures information from video player. Indicates handsets what Keysight Network Testing has been
verified
If the technology is not suitable for audio or video quality monitoring with the listed device, particular
technology is not mentioned.
For a complete list of supported devices, please see the separate document Nemo Outdoor 8.1.1 Compatible
Devices.pdf.
Do not upgrade, root, or reflash your measurement terminal firmware. Doing so will
cause the terminal to permanently lose its measurement capability!
Error Corrections
The following issues has been fixed:
Support Ticket Description
Scanner configuration via Nemo Cloud. Fixes to frequency and pilot scanning mode. Spectrum
scanning not implemented at the moment.
Fixed issue downloading the measurement files from Nemo Invex UIC- modules. Earlier if transfer
failed it occasionally caused measurement files to be are lost or corrupted.
Fixed issue with extra call attempt and call disconnect events when the measurement is started by
incoming call.
Fixed issue with exporting measurement files to Dropbox.
Fixed issue uploading files to Nemo Xynergy in remote (Nemo Cloud) mode.
Fixed issue with missing project ID information with Nemo Cloud.
Fixed issue with automatic remote session. Session failed to continue when its execution was
interrupted either by user or application crash.
64367 Fixed issue with high jitter logging due to corrupted RTP header from Shannon diagnostics.
Fixed issue not showing measurement name on status bar
Table 4. Nemo Outdoor error corrections.
For detailed information about bug fixes and error corrections please see the readme.html file located at
C:\Program Files (x86)\Keysight\Nemo Outdoor\readme.html. If you have Nemo Outdoor application installed
to your PC just click the link below
file:///C:/Program%20Files%20(x86)/Keysight/Nemo%20Outdoor/readme.html
Qualcomm-based WCDMA and CDMA2000 Terminals and

Data Cards
Nemo Outdoor is compatible with all devices labeled as “CDMA by Qualcomm” or “QUALCOMM 3G CDMA”
using the Qualcomm chipsets. However, Keysight Network Testing cannot guarantee full functionality when a
test terminal is used with a Qualcomm-compatible handler. Video calls, for example, might not work. Please
see the separate document Nemo Outdoor 8.1.0 Compatible Devices.pdf. for a list of verified Qualcomm-
based CDMA and WCDMA terminals.
CDMA terminals with or without RUIM card purchased from Keysight Network Testing must be registered with
a local CDMA operator. Keysight Network Testing does not take any responsibility if a local operator restricts
the registration of test terminal(s) supplied by Keysight Network Testing.
New Devices
Product Code Device Firmware/ Handler SW UEs/ Technology Driver
Nemo ID CPU
NA Essential 2.0.c4-M1.3.1 Qualcomm 1 LTE band 1(2100), 2(1900), 3(1800), Qualcomm

Phone PH-1 (8998.gen Nov LTE-A Cat. 9 4(1700/2100), 5(850), 7(2600), 8(900), USB host
(Qualcomm 1 2017 3CC 11(1500), 12(700), 13(700), 17(700), 20(800), driver
MSM8998 22:44:47) 21(1500), 25(1900), 26(850), 28(700), 29(700), 1.00.37
Snapdragon Nemo ID: 30(2300), 38(2600), 39(1900), 40(2300),
835) 22759/2 41(2500), 42(3500), 43(3700), 66(1700/2100)
HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100
& TD-SCDMA
CDMA 800 / 1900
HSPA 42.2/5.76 Mbps, LTE-A (4CA) Cat12 DL
EV-DO Rev.A 3.1 Mbps
Quad band GSM
Table 5. New test devices.

Generic Test UE Software Handler Updates

• Mute call and missing audio detection with VoLTE calls
o Based on RTP packet information. Present the max. number consecutive lost RTP packets
o RTP burst error length information is written to the RTPJITTER event and logged also with ViLTE
calls
o Enables detecting mute calls and calls with missing audio without the need to have a dedicated
voice quality call testing activated. For example, if there are 20 or more consecutive RTP packets
lost, the call will be considered as a mute call.
o Missing audio detection. For example, when there are 10 or less consecutive RTP packets lost in
sequence, only then the call will be considered as missing audio call.
o User must enable RTP messages logging from measurement options per device
o Mute call and missing audio call detection is supported in Nemo Analyze version 8.01 where user
can define the threshold values according to which the classification of mute call or call with
missing audio is made.
• Enhanced 4x4 MIMO information
o Renamed old PDSCH MIMO usage ratio to PDSCH rank 2 usage ratio
o Added PDSCH rank 3 usage ratio
o Added PDSCH rank 4 usage ratio
Qualcomm Software Handler Updates

Added support the following new bands:
• E-UTRA band 48 support

• E-UTRA band 71 support
Samsung Shannon Software Handler Updates

Added support the following new KPIs:
• PDCP downlink / uplink throughput

• PDCP downlink / uplink block rate
• Radio bearer ID
• PDCP downlink / uplink throughput per RB
• PDCP downlink / uplink block rate per RB
• Handover U-plane interruption time
o Defines the time from the last RTP packet in the old cell to the first RTP packet in the new cell.
• RTP message logging and decoding providing the following new KPIs:
o Speech codec mode and rate information
▪ Shannon VoLTE AMR codec estimation has been replaced by the decoding RTP signaling
messages
▪ Provides channel modes with bit rate information for all speech codecs with VoLTE calls
including NB, WB and SWB with Enhanced Voice Services (EVS) information
o User must enable RTP messages logging from measurement options per device. If RTP messages
are not enabled, speech codec estimation is used.
• Speech path delay (SPD) with VoLTE
o Together with RTP packet loss and jitter, speech path delay determines good or poor voice
quality. Good 0-150ms, acceptable 150-400ms, poor >400ms
o Time between two devices sending and receiving the same RTP packet
o Raw data logged with Nemo Outdoor and user must enable RTP messages logging from
measurement options per device
o Both MO and MT devices must be connected to the same PC
o SPD calculation and statistics with data analytics tools. Requires Nemo Analyze version 8.01 or
higher
Neul Software Handler Updates

• Added support to accept also devices reporting manufacturer as “U-Blox” and “Lierda” instead of
Neul. This change enables the use of a wider range of NB-IoT devices with Neul NB-IoT handler
software.
• Some Lierda USB devices are using Exar USB UART chipset instead of one from FTDI. These devices
are now supported.
Generic Scanner Handler Updates

No changes.
Keysight spectrum analyzers and scanning receivers
No changes.
PCTel scanner handler updates
No changes.
Rohde & Schwarz scanner handler updates
No changes.
User Interface Updates

• Nemo Navigation Assistant connection status
o Added color coded status bar for Nemo Navigation Assistant
o Green = Connected, Red = Disconnected
Nemo File Format

Nemo Outdoor version 8.1.1 supports the Nemo file format version 2.33. Existing Nemo analytics tools can be
used to post-process files made with Nemo Outdoor 8.1.0 but the new parameters are not parsed. Nemo file
format 2.33 is supported in Nemo Analyze version 8.01, Nemo Xynergy version 18.1 and Nemo WindCatcher
version 3.6.5.0.
• Added support for Nemo Server hardware and software information. (#SERVER, #SERVERHW)
• Added support test script sync group id logging. (SCRIPT)
• Added support for WhatsApp testing. (CAA, CAF, CAC, CAD, DAA, DAF, DAC, DAD, DREC, DCOMP)
• Added support for RTP burst error length parameter. (RTPJITTER)
• Added support for LTE uplink MIMO. (PLAIU)
• Added support for LTE uplink and downlink transport block size. (PLAID, PLAIU)
• Added support for LTE uplink and downlink repetitions. (PLAID, PLAIU)
• Added support for LTE RACH CE-level and repetitions. (RACHI)
• Added support for NB-IoT subcarrier allocation. (PLAIU)
• Added support for NB-IoT subframe allocation. (PLAID)
• Added support for NB-IoT downlink control information. (DCI)
• Increased video frame rate from 50 to 120. (VQDL)
Computer Hardware and Software Requirements

• PC (Lenovo or Dell recommended) with Windows 7 ®, Windows 8 ® or Windows 10 ® Professional (32/64
bit)
• Processor Intel® Core™ i7 2.66GHz or higher
• SSD drive recommended
• 500 MB of free hard disk space for installation and use; 4 GB recommended
• One USB port for copy protection module
• Ethernet port RJ45
• Display resolution 1400 x 900 recommended

• Memory 4GB RAM minimum, 8GB recommended
• One USB port for copy protection module
• One USB port per mobile

• Depending on the scanner used, one USB port or serial port or RJ45 or FireWire port per scanner
• One USB port for an external GPS receiver
• Internal 3G/ 4G modem or WiFi hotspot is recommended when using end to end call communication with
Nemo Server and with Nemo Cloud
Device Configuration and Workspace Files

Device configuration and workspace files made by Nemo Outdoor version 8.1.0 are fully compatible with
Nemo Outdoor version 8.1.1.
Nemo Outdoor accessories and verified configurations
The following multi device configurations has been verified by Keysight Wireless Network Testing.
Device Nemo Backpack Nemo Carrying Case

(# of devices) (# of devices)
Samsung Galaxy S7 SM-G9300 9 8
Samsung Galaxy S8 SM-G950F 9 8
Sony Xperia XZ Premium G8141 9 8
Sony Xperia XZ Premium G8142 9 8
Installation
Supported operating systems are Windows 7 ® (32/ 64-bit), Windows 8 ® (32/ 64-bit) and Windows 10.
First-time installation
Note that the installation must be run under Administrator account or other user
account with administrative privileges. Nemo Outdoor setup 7.5.1.8.exe or higher
includes also the IP packet capturing monitoring. NOTE! Microsoft Network Monitoring
3.4 must be installed to enable the packet capturing.
Start Windows® and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D). Copy the files
to your PC. Select Start | Run in the Windows® Status bar. Type D:\Nemo Outdoor 7.x\Nemo Outdoor x.xx.x in
the Open field (xx refers to the version number). Run the setup.exe and click the OK button. After the
installation program starts, follow the instructions on your screen. NOTE! When the Nemo Outdoor software
installation is complete, you will need to restart the computer.
Update/Upgrade
Note that installation must be run under Administrator account or other user account
with administrative privileges. Note that if the existing Nemo Outdoor version is 6.2.1.x
or older it must be uninstalled via add or remove programs before the Nemo Outdoor
7.6.x installation can be run.
Nemo Outdoor setup 7.5.1.8.exe or higher includes also the IP packet capturing
monitoring.
Start Windows® and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D). Copy the files
to your PC. Select Start | Run in the Windows® Status bar. Type D:\Nemo Outdoor7\Nemo Outdoor x.xx.xx in
the Open field (xx refers to the version number). Run the setup.exe and click the OK button. After the
Installation program starts, follow the instructions on your screen. NOTE! With Nemo Outdoor 6.21 or earlier
version the copy protection key must be attached to USB port during the installation and uninstallation when
asked. When the Nemo Outdoor software installation is complete, you will need to restart the computer.
Uninstallation
Note that the uninstallation must be run under Administrator account or other user
account with administrative privileges.
Nemo Outdoor application must be uninstalled via Add or Remove Programs. NOTE! With Nemo Outdoor
versions 5.80- 6.21 the copy protection key must be attached to USB port during the uninstallation. With
Nemo Outdoor 6.3.x onwards a copy protection module is not needed during uninstallation. When the Nemo
Outdoor software uninstallation is complete, you will need to restart the computer.
Dongle runtime drivers
In case software license (Nemo GLS) is used with Nemo Outdoor application the runtime driver must be
chosen at the time of installing Nemo Outdoor application.
Limitations and Issues with Windows 7 Operating System

The following limitations with Windows 7 operating system have been noticed and verified by Keysight Finland
or informed by the vendors:
- Debug logging needs administrative privileges if User Account Control Settings (UAC) is enabled. It is
recommended to change the UAC settings to Never notify. This can be done via User Account Control
Settings.
- If UAC is set to always notify it might cause issues with data testing. PS connection can be established but
data transfer cannot be done. It is recommended to change the UAC settings to Never notify. This can be
done via User Account Control Settings.
Figure 2. UAC settings.

Known Issues
Test device related known issues for UEs, scanners, and other devices are listed in a separate document:
(Nemo_Outdoor Test_Device_Technical_Notes).
General and user interface
Note that if there is a system that measures acceleration in the laptop and that causes
the hard disk to stop when jolted, it should be turned off. Otherwise there may be
breaks in the measurement files. With voice quality testing this can be seen with
missing MOS scores, and with other test devices with gaps in the measurement results.
Figure 3. Lenovo active protection system properties.
- Map:
- User is not prompted to save BTS file after modifications. Will be fixed to 8.2.0
- Saving Mapinfo MapX geoset file is not supported
- Google map issues:

- Map layers flash too often
- Using "Points of interest" interferes with the layer drawing
- Auto center is disabled when map is moved by user
- Measurement list: Nemo Outdoor crashes while running measurement list with iPhone
- Script editor: When using invalid value for timeout, duration, or file size (depending which protocol is
used) parameter, editor changes values without any notification
- When there is no PDF reader in PC, opening the help causes error code 31
- Occasionally when opening device configuration, UI shows false locks to some devices even if the lock is
not saved to configuration
- “Server busy. This action cannot completed….” error message is shown when opening the packet grid for
packet capturing files (.pcap). Workaround is to click the Retry button several times to close the message
window
- Running Nemo Outdoor setup directly from the USB flash memory will not work. Workaround is to copy
the files to PC prior running the setup
- Download stops responding. Applies to Windows Vista and Windows 7 operating systems. When you try
to download a file, the download stops responding and times out. The problem occurs when you use a
USB modem that has a data transfer speed that is faster than or equal to 240 kilobits per second (Kbps).
The problem occurs because of a limitation in the current USB modem driver (Usbser.sys). The hotfix
download is available from http://support.microsoft.com/kb/925681
Please select View and request hot fix downloads and follow the instructions to download the appropriate
file. Files can be found also from the DVD supplied by Keysight (Nemo Outdoor 6.0\Setup\Microsoft hot
fix). Please note that for each operating system there is a separate file available:
- Windows 7, Windows6.1-KB925681-x86.msu
- Windows Vista, Windows6.0-KB925681-x86.msu
- It is highly recommended not to use the User Parameters functionality during multi-device testing as the
decoding of L3/ RRC messages will cause a high CPU load. If performance problems are found, it is
recommended to remove all user parameters from the user interface.
- If the message “Server Busy” is displayed on the screen, it is recommended that the packetmon.exe is
killed using the task manager. Packetmon.exe is used by the Microsoft Network Monitor. Microsoft
Network Monitor is needed only with the video streaming quality or IP packet capturing functionalities. If
IP packet capturing or video streaming quality measurements are not required, it is recommended to not
install Microsoft Network Monitor.
- Line graph zooming with mouse wheel does not work occasionally
Nemo Analyze
- Nemo Analyze initialization fails if Nemo Analyze is already open and the user clicks the Analyze button in
the Nemo Outdoor UI to open the files.
- Export to Nemo Analyze. When an open workbook or open report is selected, the loaded measurement file
is shown twice in the Analyze Measurements database, i.e., there are two number 1 devices in the
measurements database.
Nemo Cloud
- Scanner configuration
- GSM TOP-N scanning configuration is not working with Nemo Cloud

- Spectrum scanning cannot be configured via Nemo Cloud
- In a manual session it is possible to run a Measurement list, but the file names are not taken from Cloud
configuration, and therefore files done via the Measurement list are not uploaded to Nemo Cloud.
- Measurement list should be disabled in manual sessions, or if measurement files are done via
Measurement list they should be handled as manual session measurement files, file name should be taken
from Cloud autoconfiguration file and files uploaded to Nemo Cloud.
- Devices without IMEI information cannot be configured and used via Nemo Cloud.
Nemo Media Router

Nemo Media Router for Android
- VoLTE voice quality testing: During SRVCC handing over LTE to 3G audio quality MOS results should be
ignored as received audio sample include audio from mic line
- A data cable must be connected to the computer and to the test handset before switching on power to
the handset. In case the handset power is turned on before connecting the data cable, Nemo Media
Router does not always detect the data cable and connection to Nemo Outdoor fails. In such a case, exit
the NMR application and it will automatically restart.
- Access Point Name (APN) must be defined in the test handset. APN used in the script file is ignored by
NMR application.
- Team Viewer version 11 should be used with the Samsung Galaxy S6 and Note 5 handsets.
- GPS fix source type (Glonass/GPS) cannot be identified when using NMR for GPS data.
- Packet capturing, full logging should be used only for troubleshooting purposes as the file size of the
packet capturing file is limited by the memory of the test handset. Error message is shown in the Nemo
Outdoor user interface when the memory is full.
- Remote TeamViewer UI control and monitoring:
- If the user has already started a PC client connection to the device before NMR is asked to start
accepting connections, it may take over 30s for the connection to succeed.
- Screen power saver should be disabled, because TeamViewer will not work if the screen is not
visible. Occasionally TeamViewer connection to the handset fails. Try again.
- Samsung Galaxy S4 mini (GT-I9197) and Samsung Galaxy S7 edge SM-G935F (Optus) do not
support remote control.
- DNS query is not supported
- HTTP/HTTPS browsing
- As redirection is allowed with NMR version 2.40 onwards with certain web pages, the browser
may prompt to use the mobile versions of websites instead of the full versions and also ask to add
local weather information, etc. If the user does not select any option, the web page is not loaded.
Therefore, it is important to pretest the web page using the internet browser of the phone before
measurements, including browsing. An alternative method is to change the user agent settings
via the Android browser. In case the handset is inside the Nemo Invex HI module, use a
Teamviewer remote connection to change the settings:
1. In the address bar, type: about:debug and hit return
2. Go to the settings menu and look for the UAString

3. Open up UAString and select desktop
4. Return to your browser. Browser will be seen as a desktop browser when you visit
sites.
- iPERF UDP DL testing cannot be done with test handsets running Nemo Media Router application. Non-
NMR test handsets are required.
- Ping testing using delay from reply to request does not work using NMR. Workaround is to use delay
between requests. Repeat until stopped is not supported at the moment and repeat X times should be
used.
- WLAN measurements via Nemo Media Router

- WLAN quality is not available
- WLAN measurement is not supported with Nemo Invex HI modules
- Huawei u-vMOS measurements
- Video codec is not available
- PEVQ-S measurements via Nemo Media Router
- Video codec is not available
- YouTube measurements via Nemo Media Router
- PER event is not available
- Data stream playback position, data transfer content type, data transfer video codec and data
transfer audio codec and file size are not available
Nemo Media Router for iOS

- Access Point Name (APN) must be defined in test handset. APN used in the script file is ignored by NMR
application.
Nemo Backpack (former Nemo Walker II)/ Nemo Carrying Case (former Nemo
Multi Lite)
Nemo Carrying Case (Nemo Multi Lite)
- Samsung Galaxy Note 4 SM-N910G/ F/ T handsets must be removed from the holders before closing the
lid. Otherwise closing the lid will damage the handsets. The suitcase has not been designed for bigger
handsets, such as Note 4.
- When using max. six Samsung smartphones (e.g. Note 4 handsets), the system cannot charge all
handsets, and therefore the batteries of the test handsets will run out. It is recommended to start testing
with fully loaded batteries. For example, with YouTube testing, measurement duration is limited to ~four
hours.
Nemo Backpack (Nemo Walker 2.0)
- “Number of USB devices exceeded” error messages might appear with certain laptops when more than
five test UEs are connected to USB hubs. Issue is seen especially with Lenovo Yoga laptops. It is advised
to connect max. four UEs per USB hub. With computers having both USB 2.0 and USB 3.0 ports, it is
advised to connect the first USB data cable to USB 2.0 port and the second USB data cable to USB 3.0
port. Disabling USB 3.0 from the BIOS is also an alternative with laptops running Windows 8.x OS.
Laptops with Windows 7 OS, uninstalling the Intel® USB 3.0 eXtensible Host Controller Driver via add/
remove program can be done. The recommended laptop with up to eight test handsets is Lenovo T430S.
- Samsung Galaxy Note 4 SM-N910G/ F or similar size of handsets cannot be used with the Nemo
Backpack 2.0 chassis. Chassis has not been designed for big handsets, such as, Note 4.
Applications and protocols
Trace route testing
- Traceroute protocol does not generate DTRACE events on hop. Only last hop generates DTRACE event.
Fix will be available in version 8.1.1
Email (POP3) testing
- Email testing with POP3 protocol is not currently working. Fix will be available in version 8.1.1
Dropbox testing
- File size is not written to the DREQ event, and because of that, the device status does not show a progress
bar for DL or UL transfers.
- With uplink data transfers the UL data throughput goes up and down. This is normal behavior as the
uploaded files are split to 4MB fragments and uploaded to server with separate upload commands.
- With multi-data transfers, e.g. benchmarking Dropbox testing, different local file names must be used for
each test device. In multi-script it means that you can download the same file with all devices, but you
must write it with different names to the local disk.
PEVQ-S streaming analysis (PC-based using Flash player)
- Only one active PEVQ-S connection is supported per PC. Only one active PS connection is allowed while
executing PEVQ streaming. When multiple test handsets are connected to the same PC, a PS connection
with only the test handset executing PEVQ-S testing is allowed.
- If a test handset has Nemo Media Router application installed, it prevents PEVQ-S testing as NMR test
handsets are always online. In such case, to run multiple PEVQ-S connections simultaneously, a dedicated
PC is required with only one NMR test handset connected to the PC.
Facebook testing
- Facebook limits the number of status updates and image postings
- If you see an error message, it means the Facebook limit has been reached. It is not a permanent
error, so the feed will continue to work, and once the limit is reset on Facebook’s end (daily), new
posts will be posted again automatically
- Currently each app is given an allotment of 200 API calls per user in any given 60-minute window.
Please note that Facebook can change this limit. Please see more details from:
https://developers.facebook.com/docs/graph-api/advanced/rate-limiting
- Custom Facebook test applications offer more flexibilities to test Facebook with drive test tools as
some of the limits seen with normal Facebook apps do not apply, such as number of allowed
postings per hour. Please see the following link for further information:
https://developers.facebook.com/docs/apps
- To create your own Facebook test application, please login to

https://developers.facebook.com/docs/apps/register
- If Facebook benchmarking is done using a commercial laptop, the same user account settings must be
used with all test devices
Instagram testing
- Due to changes in the application permission policy and in the application protocol interface (API)
provided by Instagram the following Instagram operations cannot be supported:
- Load user feed
- Load popular feed
- Search media with a tag

- Customers can continue to test accessibility to Instagram service using the Load self- feed operation only.
Old script files can be used but operations that are not supported are ignored.
VoLTE IR.92 voice/ SMS and IR9.4 calls/ VoWiFi/ ViWiFi
- Call type in the call attempt event (CAA) is written as a voice call, not VoLTE or WLAN IMS voice call when
a call is generated via Nemo Outdoor user interface. This is because the call type is unknown at the time
of the call attempt. Call type in the call connection event (CAC) should be observed.
- SIP UL/ DL messages are missing occasionally.

- With networks using encryption, it is required to perform radio off/ radio on for the VoLTE/ VoWifi/ ViWifi
and wait ~40 seconds. During this time, SIP server registering is shown in the user interface even if the UE
is already registered. After this, measurements can proceed normally.
- With IMS SMS testing it is not recommended to use more than 160 characters.
- During recording, the user cannot enable WLAN measurements. WLAN measurement needs to be
enabled before starting measurement. In this case, the user needs to enable WLAN from the device UI
manually.
- When enabling WLAN measurement from Nemo Outdoor, a notification Turning on Wi-Fi will turn off USB
Tethering. Continue? is shown in device UI. WLAN will not be activated before the user responds to the
dialog. This dialog will not affect the functionality, the connection between NMR and Nemo Outdoor stays
active.
- If the device is in Airplane Mode and WLAN is activated, device handler starting may fail.
- ”SIP server registration type” is not updated until the next SIPREGA/SIPREGC events are written.
Information is also not updated with WLAN IMS voice -> LTE IMS voice and LTE IMS voice -> WLAN IMS
voice events.
- If WLAN is disconnected/disabled, WLAN IMS SIP server registered status stays visible in Nemo Outdoor
UI.
VLC media player:
- Retrieving proper error messages (streaming cause codes) is missing. VLC player version 2.1.0 required
with Nemo Outdoor version 7.3.0.6 or higher
USSD testing:
- USSD testing is not supported with Huawei UEs
FTP UL data transfers:

- Occasionally FTP UL data throughput values can exceed the maximum value supported by the network.
This is seen at the beginning of data transfers. The root cause is that the operating system can buffer the
data.
CDMA SMS end-to-end testing
- To be able to calculate end-to-end delivery time, SMS testing must be done using the same operator
between two terminals. This is due to the fact that SMS message ID changes from operator to operator.
MMS testing
- In case of high MMS sending/receiving failures, it is recommended to increase the default time out time
from 30 seconds to for example 60 seconds.
- With Nemo Outdoor 6.3 onwards the required Microsoft Network Monitor version is 3.4.
- If IP packet capturing is not required it is highly recommended to uninstall it, as it affects the CPU
performance.
- If data throughput problems are experienced with Windows 7 operating systems and you are using auto-
tuning TCP receive window, please see article http://blogs.msdn.com/wndp/archive/2007/07/05/receive-
window-auto-tuning-on-vista.aspx or try to set the auto-tuning level to highlyrestriced." Auto tuning can
be restricted by running “netsh interface tcp set global autotuninglevel=restricted” from the command
prompt. We have found that the restricted mode will often allow some of the benefits of auto tuning with a
number of problematic devices. Current auto tuning level can be shown with the command “netsh
interface tcp show global”.
- With MMS testing the data transfer status can occasionally show more than 100%.
Troubleshooting Device Connectivity Issues

In general, all power saving options should be disabled and high performance power settings should be used.
Battery stretch should not be used and USB port power saving option should be deselected.
Figure 4. Generic USB hub properties
Troubleshooting Data Transfer Issues

PS connection works but no data
If UAC is set to always notify it might cause issues with data testing. PS connection can be established but
data transfer cannot be done. It is recommended to change the UAC settings to Never notify. This can be done
via User Account Control Settings. If the UAC settings cannot be changed it is highly recommended to start
Nemo Outdoor application with administration rights by right-clicking Nemo Outdoor icon and by selecting
Run as administrator.
Figure 5. UAC settings.
Antivirus filtering
Disable antivirus application and Windows firewall. If data transfer still does not work, please do the following:
- Activate PS connection (activate PDP context)
- Go to Network settings and choose appropriate connection assigned for the device. Go to Connection
properties and check that antivirus NDIS filtering is unchecked.
Figure 6. Network connections.
Figure 7. Antivirus NDIS Filter.
Low data throughputs
In case lower data throughputs are received with Nemo Outdoor compared to third-party applications, read
this document for troubleshooting throughput problems with various TCP-based protocols. Please note that
the following applies to PC-based data transfers, not to data transfers made by Nemo Media Router
application running on Android-based smartphone. If you experience low data throughput with Nemo Media
Router application, please see the chapter Low data throughput with Nemo Media Router application.
In case low throughput values are monitored with Nemo Outdoor and also with third-party applications, the
issue can most likely be seen by observing link adaptation parameters.
For example, low average CQI and high MAC-HS 3rd retransmission rate indicate an area of bad coverage or
high interference. Low HS-SCCH usage rate (= high HSDPA DTX percentage ratio) points to capacity, server,
or transmission problems.
In LTE networks, observe physical resource block allocation (PRB) and signal to noise ratio (SNR). PRB affects
throughput directly. Values less than maximum may indicate other users in the cell, a bottleneck in the
transmission network, or not enough data to be sent (application does not need all the available bandwidth). If
data throughputs in LTE are lower than expected, it is recommended to adjust the buffer size via Nemo
Outdoor user interface, for example, to value 1024. It should be noted that buffer size must be adjusted
separately for each protocol (e.g. for FTP and HTTP).
When requested throughput is much higher than the actual measured throughput, it may indicate that there
are other users sharing the radio resources of the cell or some other bottleneck in the network that prevents
the mobile from getting the maximum achievable throughput.
High PUSCH TX power values indicate a lack of uplink coverage.
When operating in the dynamic range of link adaptation, average BLER (PDSCH BLER) should be higher than
0, typically 10-20%, in order to achieve the gain of HARQ retransmission scheme.
Residual BLER after all HARQ retransmissions should be 0%. Higher values indicate that the radio link is about
to drop. Observe the MAC downlink/uplink residual BLER (%) values.
Other things that could help troubleshooting:
- Disable any firewall and/or antivirus software that could reduce the throughput. Some HSPA USB
interfaces may also install their own software which may affect to window size settings in registry.
- Disable IP packet monitoring from the Advanced properties.
Figure 8. IP packet capture settings.
- Try another FTP server for comparison.

- Command prompt FTP throughput. This comparison is recommended because command prompt FTP
does not use any multithreading or other non-standard methods. For better results, keep Nemo Outdoor
at the background measuring the mobile network while making the transfers. Also try different servers.
- For Nemo Outdoor 5.60 and older versions: Run a script with simultaneous FTP transfers to see if the
throughput increases. Does not work manually, script is always needed.
- For Nemo Outdoor 5.70 and later versions: Use the multithread feature of the FTP protocol to test
simultaneous transfers. Works also manually
- For Nemo Outdoor 6.30 and later versions: Transmit/receive buffer size should not be mixed with the TCP
receive window size which is the global setting. TCP receive window size affects the TCP/ IP layer whereas
transfer buffer size affects the application layer. Transfer buffer size can be adjusted per socket. This
means that the transfer buffer size can be adjusted for each test UE separately. Transfer buffer size can be
adjusted with the FTP, SFTP, HTTP, POP3, SMTP, and IMAP protocols
- When buffer size is not checked from user interface, Nemo Outdoor checks if auto-tuning is on with
Windows 7. If auto-tuning is on, no values are set. Otherwise the static value 64k is used.
- Normally default buffer values are acceptable. But if low data throughputs are still experienced, increasing
the receive/transmit buffer size may increase data throughput.
- In uplink direction, transfer buffer size that is too high can be seen as high data throughput peak at the
beginning of the data session. For example, it is possible that measured data throughput peak is higher
than what the cellular system supports. In this case, decreasing the transfer buffer size in uplink direction
will eliminate high data throughput peaks.
Figure 9. Data transfer settings.
- Make a comparison test between Nemo Outdoor and the connection manager used with the device. When
configuring a device with Nemo Outdoor, only the trace port should be defined. The modem port and dial-
up connection must be left blank. As ports are left blank it is not possible to perform a manual PDP
context activation or data transfer via Nemo Outdoor. However, a script file with data connection
commands can be used. Script files should include only data transfer commands, not Attach/detach or
PDP context activation or deactivation commands. Start a data transfer and observe the application data
throughput value. Do the same test again but this time make a connection using Nemo Outdoor.
All Windows versions
How to check the TCP window size from packet logs:
Using Wireshark:
1. Check the .pcap file and look at the (non FTP-DATA) TCP traffic in the middle of the transfer.
Window size value tells the current TCP window size used.
Using Nemo Outdoor:
1. Open a packet grid window in Nemo Outdoor.

2. Look at the TCP traffic in the middle of an FTP transfer with PayloadLen=0:
3. Double-click the frame to get detailed frame info. Look at the Tcp tree. Window shows the
current value.
Using debug logs (for developers, help desk, etc.):
1. Look for the GetWindowSizeFromRegistry() function.
- TCP Window size set to n = Value found from registry.
- TCP Window size set to default: n = Value not found from registry. Set to default.
- TCP Auto-Tuning detected. Window size not set. = Windows Vista/7 is using auto-tuning TCP window.
- A measurement file (.nmf) does not save window size info. Packet log and/or debug log is always needed.
Windows 7
Windows 7 does not use static window sizes from the registry. They rely on dynamic window size which is
handled by TCP auto tuning feature. However, if the same registry value that Windows uses is set, Nemo
Outdoor reads it and adjusts the manual window size based on this value. In most cases, the registry has been
edited by a third-party software or a USB mobile interface driver/software. This registry entry can be removed.
If the TCP auto-tuning is disabled Nemo Outdoor will use its default window size 64 KB. Nemo Outdoor 5.40
and newer checks the auto-tuning state and does not change any window sizes if auto-tuning is enabled.
How to check TCP auto-tuning state:
1. Open command prompt by typing “CMD” to ”Search programs and files” field.
2. Type ”netsh interface tcp show global”. Receive Window Auto-Tuning Level shows the
current state.
Please note that administrator rights are required to change auto-tuning settings.
3. Open command prompt by typing “CMD” to ”Search programs and files” field. Right-click and select
Run as administrator.
Figure 10. Run as administrator.
4. To disable auto-tuning type “netsh interface tcp set global autotuning=disabled”. This limits the TCP
window size to 64KB. However, Nemo Outdoor sets its own default 256KB when auto-tuning is
disabled.
5. To increase the maximum TCP window size that auto-tuning uses, type “netsh interface tcp set global
autotuning=highlyrestricted”.
6. Below are all the values of auto-tuning level with explanations:
- disabled: Uses a fixed value for the TCP receive window. Limits to 64 KB (65535).
- highlyrestricted: Recommended. Allows the receive window to grow beyond its default value, very
conservatively.
- restricted: Recommended. Somewhat restricted growth of the TCP receive window beyond its default
value.
- normal: Default value. Allows the receive window to grow to accommodate most conditions.
- experimental: Allows the receive window to grow to accommodate extreme scenarios (not recommended,
it can degrade performance in common scenarios, only intended for research purposes). It enables receive
window values of over 16 MB.
Issues with HTTP browsing testing
Selecting Automatic configuration or Proxy settings can cause problems with HTTP browsing testing, such as,
increase the page downloading time. In such a case, automatic/ proxy settings should be disabled. From
Nemo Outdoor 7.7.0 onwards, proxy settings can be enabled.
Figure 11. LAN settings.
Low data throughput with Nemo Media Router application
New Android-based smartphones with Android version 6.0 have battery optimization enabled by default. It will
stop some CPU and network activity operating in the background for Android apps, thus saving battery.
Battery optimization is activated when handset is left idle for a period of time, while unplugged and with the
screen off. Battery saving mode interrupt background activity for Android applications such as Nemo Media
Router. E.g. with data transfers this is seen with limited data throughput values. Battery saving option is
disabled by default for the handsets delivered by Keysight Network Testing. However, in case of low data
throughput is experienced the following settings should be checked and battery optimization should be
disabled for all applications. Please note that settings menu varies depending on handset vendor and model.
Step by step instructions per handset can be found from the device configuration guide.
1. Select phone's settings.

2. Select battery from the device list and select battery optimization from the menu icon at the top-right
of the screen.
3. Select all apps from the drop-down menu in the center of the display. Now you'll see all the apps that
are Doze-enabled.
Figure 12. Battery optimization settings.
4. Select Don’t optimize for all apps and then tap Done.
5. Now you're set up.

Nemo Outdoor 8.1.1 Release Note

Uploaded by

Document Information

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

Nemo Outdoor 8.1.1 Release Note

Uploaded by

Copyright:

Available Formats

er’s Manual

General and user interface ........................................................................................................................................ 29

Sequence-based end to end call synchronization

Nemo Media Router

o Essential Phone PH-1

Fixed issue related IP Capturing with full logging -option.

Nemo Media Router licensing options

Product Code Description

Table 1. NMR 8.10 license options.

Compatibility and update process

Nemo Media Router 8.11.286 (for Android)

Table 2. Compatible versions.

Nemo Outdoor/ Nemo Invex II NMR test handsets

Supported handsets with Nemo Media Router

NTT20078A Samsung "MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes Yes No No

NTT20084A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 No No No No

NTT20079A Samsung "MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes Yes No No

NTT20083A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 No No No No

NTT20069A Samsung MPSS.AT.2.0.c2.2- 8.10.273 8.1.0.12 Yes No No No

NA Samsung MPSS.AT.2.0.c2- 8.10.273 8.1.0.12 Yes Yes No Yes

NA Samsung N950FXXU1AQHB, 8.10.273 8.1.0.12 Yes No No No

NTT20065A HTC U11 MPSS.AT.2.0.c4- 8.02.245 8.02.22 No No No No

NTT20064A Sony Xperia "MPSS.AT.2.0.c4.3- 8.02.245 8.02.22 Yes Yes No Yes

NTT20063A Sony Xperia "MPSS.AT.2.0.c4.3- 8.02.245 8.02.22 No No No No

NTT20076A Samsung G955FXXU1AQC9, 8.00.233 8.0.0.15 Yes No No Yes

NTT40081A Samsung MPSS.TH.2.0.c2- 8.01.244 8.0.1.20 No Yes No No

NA Samsung MPSS.TH.2.0.c2- 8.01.244 8.0.1.20 No No No No

NTT20052A Samsung MPSS.TH.2.0.c2.1- 8.00.233 8.0.0.15 Yes No No

Not available Sonim MPSS.DI.2.0.1.c1- NMR 8.00.233 8.0.0.15 No Yes No

Not available Apple 1.33.00_DEBUG NMR 1.10.14 (iOS) 7.9.1.16 No No No

NTT20050A Google Pixel MPSS.TH.2.0.2.c1- NMR 7.9.1.220 7.9.1.16 Yes Yes No

NTT40041A Huawei P9 21.201.00.00.031 NMR 7.90.210 7.9.0.9 No Yes No

NTT40043A Sony Xperia 39.0.A.1.250 R7B NMR 7.90.210 7.9.0.9 No No No

NA Samsung N920GUBU2BPE4, 2.52.177 7.8.2.18 Yes NA

NTT40047A Samsung G935FXXE1APD1 2.51.164 7.8.1.14 Yes Yes Yes

NTT40045A Samsung G928W8VLU2BPC5 2.51.164 7.8.1.14 Yes

NTT40040A Samsung MPSS.TH.2.0.c2- 2.51.164 7.8.1.14 NMR 7.91.220

Not available Apple 1.56.00_DEBUG NMR for iOS 7.8.0.8

NTT40044A Samsung G928KKKU1AOH4 2.50.156 7.8.0.8 Yes

NTT40034A Samsung MPSS.BO.2.0.1.c3. 2.41.137 7.7.1.14 Yes Yes

NTT40004A Sony Xperia 32.0.A.6.170_R16B 2.41.137 7.7.1.14

NTT40001A Motorola MPSS.BO.2.5.c8- 2.41.137 7.7.1.14 Yes

NTT40031A Samsung G928FXXU1AOH3, 2.40.125 7.7.0.9 Yes

NTT40032A Samsung N920IDVU1AOH3, 2.40.125 7.7.0.9 Yes

NTT40023A Samsung G920FXXU1AOCWI 2.31.108 7.6.1.12 Yes

NTT40046A Samsung G920W8VLU1AOE1 2.31.108 7.6.1.12

NTT40030A Samsung G920IDVU1BOF6, 2.31.108 7.6.1.12 Yes

NTT40022A Samsung S6 MPSS.BO.2.0.1.c3. 2.31.108 7.6.1.12 Yes

NTT40021A Samsung MPSS.BO.2.0.1.c3. 2.31.108 7.6.1.12 Yes

NTT40028A Samsung G920TUVU2COF8, 2.31.108 7.6.1.12 Yes From NMR

NTT40035A Samsung MPSS.DI.3.0.c5- 2.30.099 7.6.0.7 Yes

NTT40003A Sony Xperia MPSS.DI.3.0.c9.1- 2.30.099 7.6.0.7 Yes

NTT40020A Samsung MPSS.DI.2.0.1.c2.2 2.20.078 7.5.0.5

NTT40015A Samsung MPSS.BO.1.0.r10- 2.11.060 7.4.1.13 Yes Yes

NTT40016A Samsung MPSS.BO.1.1.r10- 2.11.060 7.4.1.13

NA Samsung MPSS.DI.2.0.1.c2- 2.11.060 7.4.1.13

NTT40017A Samsung MPSS.DI.2.0.1.c2.2 2.11.060 7.4.1.13

NA Samsung MPSS.BO.1.0.c1- 2.10.054 7.4.0.9

NTT40008A Samsung MPSS.DI.2.0.1.c2.2 2.01.042 7.3.1.9

NTT40007A Samsung MPSS.DI.2.0.1.c2.2 2.01.041 7.3.1.9 Yes

NTT40009A Samsung M9615ACEHWMAZ 2.01.041 7.3.1.9 Yes

NTT40010A Samsung M8930B- 2.01.041 7.3.1.9

NTT40011A Samsung M8930B- 2.01.041 7.3.1.9

NA Samsung M9615ACEHWMAZ 1.0.011 7.1.0.6