TEMS™ Pocket 26

Release Note

www.infovista.com | 1
1 About This Document
This document contains the release notes for all TEMS Pocket 26.x releases.

© Infovista Sweden AB 2024. All rights reserved.

TEMS™ is a trademark of Infovista. All other trademarks are the property of their respective holders.

2 Installation and Upgrading

To install TEMS Pocket 26.x on a device, please follow the instructions in the TEMS Pocket 26.x Installation
Guide and TEMS Pocket 26.x Installation Guide for supported devices with commercial firmware

Note: Always reboot your device after installing or upgrading TEMS Pocket.

www.infovista.com | 2
3 TEMS Pocket 26.0

3.1 Decoding updates

This release contains vendor specific decoding updates of messages for devices based on the Qualcomm
chipset.

3.2 New TEMS Devices

• Google Pixel 8 and 8 PRO

• Samsung S24 Series based on the Qualcomm chipset
• Samsung S24 Ultra (Commercial)
• Samsung TAB S9 SM-x716 as controller tablet

Please note that there might be regional differences in band support, please refer to https://www.devicespecifications.com,
https://www.gsmarena.com or https://phonedb.net for details

3.3 New Features

3.3.1 SA/NSA Mode and Band Lock Control Functions

The 5G NR control function in TEMS Pocket has been expanded to locking on one or more bands in both SA
(Stand Alone) and NSA (Non Stand Alone) modes on devices with firmwares that supports the selected options.
This greatly expands the testing capabilities for the end user and allows for complex network scenarios to be
tested either scripted or via manual control functions.

3.3.2 Hardware based PDSCH/PUSCH Throughput measurement

Hardware Based Throughput measurement (HBTM) offers an alternative source for NR Physical throughput
values for Qualcomm chipset based devices calculated directly by the modem. This is an experimental feature
that updates certain NR information elements when recording Refined data into the logfile.

www.infovista.com | 3
3.3.3 CA Control, EPS Fallback and Attach type, now available as scriptable actions
The list of scriptable control functions in TEMS Pocket 26 has been expanded with additional options previously
only accessible via manual testing. This makes for a more automated and convenient testing process.

3.3.4 New Control Function: UE Usage Voice/Data centric

TEMS Pocket now allows for control over the UE usage preference, Voice centric or Data centric as defined in
3GPP TS 23.221. This can be especially useful for testing private networks where no CS core is available.

3.3.5 New TEMS Pocket installer

TEMS Pocket 26.0 is the first release that enables customers to install using our TEMS Module installer
application.

This simplifies installation on both devices with TEMS firmware and commercial phones, making it possible to
perform OTA (Over The Air) installations and upgrades of both TEMS Pocket core and service components
without the need to connect the phone to a PC.

Note: For installation on commercial devices a DCU unit is required.

3.3.6 Android 14 support

TEMS Pocket 26.x is now compatible with Android 14 running on supported mobile phones.

www.infovista.com | 4
3.3.1 E-sim and SIM slot availability
TEMS Pocket now supports the use of an e-SIM or the use of a physical SIM card in any slot on compatible
Qualcomm chipset based devices with no restrictions compared to devices with only physical SIM slots.

Any single physical SIM slot or e-SIM can be used with full functionality of diagnostics, service testing and control
functions.

3.3.2 Updated Line chart

The Line chart view in TEMS Pocket has been enhanced with improved granularity for increased precision both
during recording and logfile replay.

3.4 Corrected Bugs

• 00525013 Problem with LTE UL CA information elements

• 00524830 Wifi RSSI Not Shown on Indoor Map

• 00514152 API NR Bandwidth decimal values - MHz10

• 00522743 No Speech Playout Events is Speech Sentence Statistics

• 00525196 MR-DC DRB PDCP UL Throughput Total Mbps/Kbps Reported Abnormal Values

• 00526720 Single Echo Request must be checked

• 00527203 FTP sessions failed with Unknown Error after TP25.2 upgrade

• 00527892 Call Indexing issue

• 00530994 Wrong Call Initiation Event for VoNR Calls

• 00529137 5G Blind Scan issue with TP 25.2

3.5 Deprecated Functions

These functions are deprecated, which means that they are still in the product, but will be removed in an
upcoming release. Until then, no updates or corrections for these functions will be made available.

• With the removal of the old legacy internal decoder, the cached cell ID function which relied on the internal
decoder is now obsolete and will be removed in an upcoming release.

3.6 Removed features

• Social media testing activities have been removed. These have been replaced with the new OTT testing
procedure using Python scripts for a more flexible and versatile testing keeping up to date with the evolving
nature of social media apps.

• Support for the the TEMS Pocket Internal decoder has been removed.

• Support for Android 10 and 11. Only Android 12 or higher is supported.

www.infovista.com | 5
4 Device support

Please refer to the TEMS Connectable Device List for details about supported devices.

Supported Android versions1: 12, 13, 14

1
TEMS Pocket can be installed on all supported devices with TEMS firmware based on one of these Android versions.

www.infovista.com | 6
5 Known Bugs and Limitations

5.1 TEMS Pocket Application Related

• If the ImagePositioning tool isn't loading correctly, please toggle Wi-Fi on/off before restarting the application.

• The control function for carrier aggregation on 5G NR currently does not work if you try to disable existing
carrier aggregation. This will be corrected in an upcoming release of TEMS Pocket.

• Iperf is not currently supported on Samsung S24 devices.

• Python scripting is currently not supported on Samsung S24 devices

• Loaded cell files are not persistent after reboot on certain phone models and must be reloaded after reboot.
This will be fixed in an upcoming release.

• On some devices the location in the Outdoor map is not updated initially until the device has moved.

• Ping error event is missing the detailed error cause.

• Replaying a logfile in TEMS Pocket with data from another SIM slot than the currently active will not update
any views. You must switch active SIM slot to match the one in the recorded logfile.

• Some events are not working when using them with Custom event triggers.

• YouTube PEVQ-S testing is not possible on devices with Android 14

• Values in the WiFi views are not cleared when WiFi is turned off.

• On the Xiaomi 13 TEMS Pocket UI does not return to focus when doing hangup.

• On the Xiaomi 13 RTP messages are not logged.

• SMS events and statistics may be incorrectly calculated and presented locally or on Director Fleet.

• If the Controller Hub with an external GPS is rebooted while agents are connected, the external GPS location
is lost and will default to the internal GPS for each agent. Agents must physically be disconnected and
reconnected to the Controller Hub to activate the external GPS.

• Cell list values are not updating properly on Controller.

• OTT Media Service YouTube recommends YouTube version 18.4.35.

YouTube action requires older 17.x version.

• Due to recent changes from Google the YouTube app will be updated even though the auto update for the
app is disabled in Play Store. This will cause problems with streaming testing and to avoid this disable
Google Play Store from within phone settings.

• When running TEMS Pocket on a device with Android 13, these value elements may not be updated on a
Samsung device for NR: PDSCH BLER and Modulation.

• To make sure that the Controller tablet keeps the display on during drivetest it is recommended to have a
charger or powerbank connected to the Controller tablet.

• The Iperf action can be killed by Android after +30 minutes of runtime.

• Commercial devices may experience issues running TEMS Pocket due to Battery saving features.

• Downlink SIP signalling messages are missing on some specific S22 Exynos chipset devices, this causes
issues with call handling leading to TEMS Pocket being unable to answer calls.

www.infovista.com | 7
• LTE PCI Lock is currently not working on Samsung S22 Exynos chipset-based phones not running the latest
firmware.

• In a Controller/Agent setup using Bluetooth as bearer, GPS location sharing is only active when script is
being executed.

• In a Controller/Agent setup only one agent can have a scanner connected, and only one agent can have a
scanner license.

• All old scripts with Internal HTTP Internal action need to be updated manually to use either OnDevice
Browser or OnDevice File.

• On the Samsung Galaxy Fold TEMS Pocket should be started when device is folded to get correct view
configuration when unfolded. Also lock the device in portrait mode.

• When scanning on NB-IoT no other scan mode is allowed.

• When NR scanning is performed a dedicated device needs to be used without using simultaneous Data
actions.

• All Pocket devices must be connected to an internet connection at first restart after the Pocket installation,
and then at least once a week to receive updates and allow license synchronization.

• When performing automatic pinpointing in a Controller/Agent setup, it is not possible to pan the map and set
manual pinpoints. To recover if the location is lost, cover the camera to trigger the correction pinpoint.

• Android Location must be enabled on devices to be able to use the SeeGull Connect App.

• Events are not updated correctly when running YouTube PEVQ-S testing.

• When the device is on GSM, the application layer throughput displayed during HTTP and FTP sessions might
dip periodically. The average throughput, however, is not affected and is calculated correctly.

• When executing several HTTP Get actions in a row, the timestamp of the first data report of one action may
sometimes actually be identical with the timestamp of the last data report from the previous action. This can
occur for FTP as well.

• The Wi-Fi function in TEMS Pocket does not distinguish between 20 MHz and 40 MHz bandwidth
measurements. All channels will be displayed as 20 MHz channels.

• 5 GHz Wi-Fi cells are not shown in the Spectrum view.

• In a controller/agent setup, all agents must have the same TEMS Pocket version as the controller. If they do
not, the controller will not connect them.

• During logfile replay, when rewinding, or fast-forwarding more than 60 seconds, the event markers in line
charts and maps will be incorrect or missing. To get accurate event markers, replay the logfile from beginning
to end.

• When replaying a Refined only logfile in TEMS Investigation no logfile progress update will be displayed

• When stopping a script with control functions on a device with the Samsung Exynos chipset, all control
functions are set to default and need to be enabled manually again.

• If the TEMS Pocket UI is restarted during pinpointing, the pin-pointing session must be restarted.

• When making a voice call with TEMS Pocket, a dialog to select dialing service may appear. You must select
“Phone” and “Always” to ensure correct functionality in TEMS Pocket.

• It is recommended to avoid extremely large map sets while performing indoor measurements since it may
sometimes result in log files that cannot be read in post-processing tools.

www.infovista.com | 8
• TEMS Pocket presently does not support IPsec encryption algorithm des-ede3-cbc on devices using the
Samsung Exynos chipset.

• The time display while replaying a logfile, can sometimes show the wrong value. Drag the control back to
start of the playback to resolve the time display issue.

• Using the Remote-Control feature in TEMS Director while running tests in TEMS Pocket will impact logfile
size because the IP traffic generated by the live stream will be recorded to the logfile.

• The maximum Response Timeout setting for ODM SynchPoint is 60 seconds. If a value above that is set, it
will be handled as 60 seconds.

• In a multi-device configuration, if you switch off Bluetooth on the Controller when several Agents are
connected, the Controller application may restart

• In a multi-device configuration, for pinpointing:

• Set the Map Set Floor Sync option in the Controller Settings to Enabled

• In this mode the Controller will only sync the selected floor plan in the Map Set with the selected Agent

• The largest Map Set floor plan that you can load is 2MB

• It is not possible to perform Facebook Post photo operation.

• NR Layer 3 messages will not be decoded or displayed in the L3 Message view.

• If the devices go into No Service when synchronizing to TEMS Director Fleet, any active measurements will
be paused and restarted when the device gets into service again.

• It is not possible to perform a call action in a commercial device if the Raspberry Pi is disconnected.

• PEVQ-S is not supported on 64-bit-only devices.

5.2 Third-party Data Related

N/A

5.3 Device Hardware Related

• Devices running intense data testing in high throughput environments may experience CPU thermal
Throttling. To reduce the risk of this happening add wait actions between data actions in scripts (We
recommend a maximum of 10 seconds data transfer, then 20 seconds wait until next action. This may vary
depending on device model, network performance, and ambient temperature). We also recommend using the
Performance mode option in these scenarios.

• PCTEL scanners may lose USB connection when in idle mode, therefore it is recommended to disconnect
and reconnect the USB cable just before starting tests with TEMS Pocket.

• In a multi-device (controller:agent) configuration, the Agent Configuration view displays the Agent ID
incorrectly, e.g. 02:00:00:00:00:00. The Agent Name is displayed correctly.

• GPS signaling can cease during testing on OnePlus devices. If it happens, please restart the device.

• To apply an LTE EARFCN lock from TEMS Director Fleet, use the CellLockLTE activity.

www.infovista.com | 9
6 Important Information
If you get a 404 error when you try to access the online User's Manual or Release Note from TEMS Pocket, you
need to clear the application cache:

1. Launch the device's Settings app

2. Tap Apps (or Applications) > TEMS Pocket UI > Storage

3. Tap the Clear Cache button

4. Close the Settings app

5. Restart TEMS Pocket

www.infovista.com | 10
7 Contact Information
Please visit www.infovista.com for customer support contact information.

www.infovista.com | 11