Android 

– ADB
 ADB stands for Android Debug Bridge.
  It is used to control Smartphone functionality using control command.
 ADB work as a client-server model in which ADB server is in mobile phone and ADB
client is installed in the PC where can control it.

ADB commands and its uses

 Checking Connected Device>>adb devices -- returns the list of the device that are
connected to PC. it can be used for basic connection check.
 Get the Device Serial Number>>adb get-serialno – it will give serial number of
devices. When you have multiple devices connected to a single PC, you can send the
command to a specific device.
 get Android OS Version>> adb shell getprop ro.build.version.release – it gives
android version.
 Get ADB Status >> adb get-state – it gives current status of the phone that is
connected to PC.
 Sending ADB command to a specific device >>adb -s <serial number> get-state – it
gives current status of the phone with a specific serial number that is connected to
PC.
 Copying a file from the device to your PC >> adb pull (file name and its path on the
device) -- it is use to copy a file from the device to your control PC.

 Check Airplane mode status - Checking whether the Airplane mode is On or Off>>
adb shell settings get global airplane_mode_on --- Query the status of Airplane Mode
of the device.
      If the device returns '1', it means Airplane Mode is ON
       If the device returns '0', it means Airplane Mode is OFF
 Check WiFi status - Checking whether the WiFi is On or Off >> adb shell dumpsys
wifi | find "Wi-Fi" ---- it will show the wifiis enable or not.if wifi enable and connected
then it will give wifi information.
 Making a voice call >> adb shell am start -a android.intent.action.CALL
tel:<PhoneNumber> --- to make MO call.
[WT][FT][PVT][RIL PROTOCOL][RJIO][Always][India][Mumbai] DUT observe network
reset while merge VOWIFI conference call for RJIO operator.
SW version: V1.040_A01(SW_T19545AA1_V042_M10_NF_NOKIA_Iris_USRD_TEST)

Product: Iris

Description:
[Hardware Information]
IMEI1: 355107510000296/304
[Test Precondition]:
1. Flash the device with latest software.
2. Insert RJIO operator sim card in SIM slot 1.
3. Data enabled default on SIM1.

[Test Procedure]:
1. Power ON device with valid RJIO Sim Cards.
2. Wait till the device register on VOLTE network.
3. Now enable Wifi and connect to Valid AP and enable Wifi calling, Wait for the device to latch
onto VoWifi.
4. Once registered to VoWifi calling, Initiate a MO WIFI call from DUT to UE1(RJIO) and
accept the call at MT end.
5. Now initiate another MO VoWiFi call to UE2(AIRTEL).
6. Try to merge both calls >> call gets disconnected automatically and sometimes we see
“Unable to merge calls” po-pup on DUT.
7. Observe that DUT observe network reset while merge VOWIFI conference call for RJIO
operator.

Expected Behaviour: DUT shouldn’t observe network reset while merge VOWIFI conference
call for RJIO operator.
Actual Behaviour: DUT observe network reset while merge VOWIFI conference call for RJIO
operator.

[Remarks]:
Issue time: 20:28 to 20:40
City: Mumbai
Operators: RJIO
HW version: PVT
Severity: Major
Reference Error (Nokia C3) Severity Definition: Not Reproducible

Additional Info:
1) We have captured logs and Screenshot for DUT and REF devices.

Issue probability: Always

Log Name: DUT observe network reset while merge VOWIFI conference call for RJIO
operator.rar
[WT][FT][PVT][RIL Protocol][RJIO][Always][India][Mumbai] DUT fails to merge VOWIFI conference call
for RJIO operator.
SW version: V1.040_A01(SW_T19545AA1_V042_M10_NF_NOKIA_Iris_USRD_TEST)

Product: Iris

Description:
[Hardware Information]
IMEI1: 355107510000296/304
[Test Precondition]:
1. Flash the device with latest software.
2. Insert RJIO operator sim card in SIM slot 1.
3. Data enabled default on SIM1.

[Test Procedure]:
1. Power ON device with valid RJIO Sim Cards.
2. Wait till the device register on VOLTE network.
3. Now enable Wifi and connect to Valid AP and enable Wifi calling, Wait for the device to latch onto
VoWifi.
4. Once registered to VoWifi calling, Initiate a MO WIFI call from DUT to UE1 and accept the call at MT
end.
5. Now initiate another MO VoWiFi call to UE2.
6. Try to merge both calls >> call gets disconnected automatically and sometimes we see “Unable to
merge calls” po-pup on DUT.
7. Observe that DUT fails to merge VOWIFI conference call for RJIO operator.

Expected Behaviour: DUT should successfully merge VOWIFI conference call for RJIO operator.
Actual Behaviour: DUT fails to merge VOWIFI conference call for RJIO operator.

[Remarks]:
Issue time: 20:28 to 20:40
City: Mumbai
Operators: RJIO
HW version: PVT
Severity: Major
Reference Error (Nokia C3) Severity Definition: Reproducible

Additional Info:
1) We have captured logs and Screenshot for DUT and REF devices.
2) We have provided Video for Wasp device.
3) Once unable to merge call on DUT, call will automatically be disconnected but UE1 and UE2 shows
calls are still connected.
4) Dialler version: DUT,UE1,UE2-65.0.370544174-go, REF C3-65.0.370544174 and Wasp-
63.0.364655934.
Issue probability: 10/10.
Log Name: DUT fails to merge VOWIFI conference call for RJIO operator.rar

SW Version : V0.120

HW version : EVT

Issue type:- New

Pre- Condition : WiFi Calling Enabled

Steps to reproduce:

1) Insert JIO SIM & Turn ON device. Wait till device register on VoLTE

2) Now Connect DUT to a WiFi AP > Now wait for some time & Observe  that DUT fails to
register on VoWiFi.

Expected Result : DUT should register on JIO VoWiFi when enabled & connected to a WiFi AP.

Actual Result : DUT sometimes Fails to register on JIO VoWiFi.

Additional Info : NA

Traces - Logs has been uploaded for ROG SW v0.110 & Nokia 2.4 

Reproducibility – 3/5

Reported by:

Akhil Ravindranath
 

28th,Dec: the call preference of the UE is set to LTE. Therefore, only when the LTE signal is
relatively weak (usually reaching a certain threshold value), it can be switched to VoWiFi So pls
TAM to check CC and retest also again in poor signal area.