Q. Plot not getting generated?

I took the liberty to process the files. The first time I processed, I see only 1 position in a city nearby. No
other GPS values were showing.

I reprocessed the data again with the unchecking “Use TEMS Track file”. See below:

After import, I made a composite dataset and loaded the MS4 GPS position. I see the following:
This is identical to what you see in the “other tool”. Can you please try with the way I tried and see what
you see ?
TEMS Track Files are useful for Indoor data collection. I typically leave that out if it is outdoor file.
TD Version used: TD 24.2.2
Q.: Overlapping legends with drive test plot
Ans: Please uncheck inside map legend option.

Q: Drive test plot looking clumsy (not getting clear picture of drive plots).
Ans: please increase the zoom lavel.

Option 1:
Option:2

3. not able get the throughput when we are running the DL and UL script in iperf for some of the
sessions

I can see the gap in the iperf throughput due to iperf failure in this trp file: PC1_ITERATION 1_DAY
1_PRE_CLUSTER ID_02E_03152023_0315110645_1.trp

As you see in the screenshot of TI below, 2 out of 3 Network Bandwidth actions failed for EQ4 and there
is no throughput for iperf.
However, the UL throughput is available and there is no gap during the last iperf test that was
successful.

As far as I can tell from these 3 trp files, as long as the test is successful, the throughput is available with
no gaps during iperf tests.
So the gaps in your plot could be either because of iperf failure or the time between two consecutive
Network Bandwidth tests.
4. One thing to clarify. Iperf3 watcher is installed on the server and a port range is given in the TEMS
script. It should switch the port in case of an error or failure from an iperf port – correct?

When the server gets a connection request, the watcher will open up an iperf instance for that port.
The connection will happen and whether it passes or fails, it will close that port once it's complete and
open a new port for the new connection request.
It will assign the new port from unallocated (available) ports in the range that is specified in the script.

5. During a meeting few months ago, the following question came up:
Do we need TEMS IperfWatcher 1.0 to run the successful Iperf DL/UL ?

My Answer was YES.

Without running the biPerfWatcher.exe running, how can the .exe work to manage the iperf sessions?

Open a Command Prompt window in the server with “Run as Administrator”. Change the folder to the
directory location where the exe exists. Then execute the exe. The iPerfwatcher will start monitoring the
ports for incoming requests, create and teardown the sessions as needed.

Lastly, Make sure the Firewall rule is set to allow the exe (iPerfwatcher and iPerf3).

iPerfwatcher is in the server. Not in a laptop.

Find the person who administers the server and ash him/her to start the watcher program.

6. We are having frequent disconnect in TEMS, as couple of S21 (SM-G991UZAAXAG) devices are keep
getting disconnected in TEMS 24.2.1.

I checked both laptops. For both of them you have this license:

This license covers these options:

Meanwhile you are using S21 SM-G991U which require Qualcomm O option:

The problem in this case is a missing license.

7. After the remote session, I found the issue with usb mode .

When we dialing the number *#0808# its going on mtp enable. but we need to select
DM+Modem+ADB. and its not showing in phone.

These 2 phone behavior not like a normal phone. because we checked one other phone
and it connecting with and upgraded the ODM successfully
and also getting the normal USB mode.

Could you please check Samsung about these 2 phone. while i will also check
internally.

Have you tried to enable USB debugging under developer options?

8. The S21’s that have android 13 are failing to connect in TEMS, the android 12 models are not having
the same issue. Could you please reach out to Tushal who is on this email and troubleshoot this issue.
If these are commercial devices and they have upgraded to A13, it is best if you factory reset these
devices.

***Make sure there are no accounts signed into the device, like Google/Samsung/other app account
before doing this***

You can check this in Android settings -> Accounts & Backup

Power off the phone and put the device into recovery mode.

Resetting the device via recovery mode:

1. Turn off your phone and wait a few seconds.

2. Press and hold the Volume Down and Power buttons until you see the Android logo.
3. Wait a few seconds.
4. Navigate with the volume buttons to 'Wipe data/factory reset' and confirm with the Power
button
5. Navigate to Yes and confirm with the Power button.
6. Your device will now be reset

After the phone comes back up:

1) Enable developer options and turn on USB debugging

2) Disable Play Protect in the Google Play Store App
3) Turn off any kind of android battery save settings and putting apps to sleep.
4) Open the dial pad and select *#0808# and select DM + MODEM + ADB for USB mode. If this is a
Verizon or a smaller CDMA based carrier, you may need to select ##DMMODE# and enable this.

Make sure you are running the latest TI 24 version and make sure that you have downloaded the latest
ODMs from true update on the splash screen.

Connect one phone at a time to TI and install the odms. You will get prompted to reboot the phone and
then it should detect properly.

You can also go into developer options and shut off automatic updates, its one of the first few options

I have spent as much time as I could since 2:25PM ET. To be quite frank here, there are quite a lot of set
up problems with this kit and phones, and I do not see how this drive tester was supposed to succeed.

The issue for which this case was raised for with the USB mode not showing all the options was showing
up regardless of A12 or A13 versions. The behavior I saw when I remoted into the PC is that the USB
ports would be continuously connecting/disconnecting from the PC. This explained the inconsistency
with the USB debugging and missing USB modes.

We had the device plugged directly to the PC to rule out any other kinds of Hardware issues which could
cause this.

FINALLY after seeing what was installed on the PC, it looked like the only possible culprit of this was
MacAfee Live Protect Anti-Virus. I uninstalled this from the first PC and then rebooted it.

After that we re-connected the device and now it was stable in the device manager. We were able to do
USB debugging and select DM+MODEM+ADB as we should. This is by the book stuff that is normally
simple and it took awhile to figure out this anti-virus.

Now the next problem was the inconsistency of FW on the phones. Some are on A12, other on A13... I
am not sure if it matters so much which firmware is loaded but I wanted to bring this to your attention.
It seems like no one had an idea of what FW should be used.

The next problematic part is that there are some other 3rd party testing applications like XCAL, multiple
google accounts, even old TEMS apps which must have been in stalled from previous testing
adventures. If there was just one or two we manually removed it, but if there was a lot we just played it
safe and factory reset.

During the session I explained and tried to teach how to set up the phones from scratch after this,
settings needed on the phone, which I outlined in the previous email when it comes to disabling play
protect, removing google accounts, putting unused apps to sleep, etc.

We got through 5 of the 10 phones this way and I am hoping that this should be good enough help so
that the team can do the remaining 5, and then confirm that they can connect these to the other PC.

It is always important to try and get the PC and Phones setup before getting to the field. Trying to do
this stuff over a poor remote connection is difficult.

If the phones are being used with other tools, please factory reset the phones before using them again
with TEMS as some times these will interfere with our tool and we have no idea how these other apps
work or behave like taking over diagnostic of the phone.