Android Telephony API Issues

Last update: April 2017

 

Phones with Android 5+ that still do not implement fully API 17 telephony functions

There are phones with Android 5 or Android 6, i.e. API 21+, that still do not fully implement API 17 telephony functions (they implement API 1 telephony functions!), which limits drastically our app's features for those phones. This has as consequence, for example, not showing any LTE neighbors, and not showing PCI (since no such info is provided). These are manufacturers' issues and not ours.

 

Android 7+ phones, showing erroneously Band 1

There have been recorded (from users' feedback) Android 7+ phones, e.g. cases of Samsung S8+ (SM-G955U), Samsung S7 Edge (SM-G935V), Samsung S7 (SM-G930T, SM-G930F), Samsung S6 (SM-G920F) devices, showing erroneously EARFCN = 0 which translates to Band 1. This is Samsung firmware issue, not ours. Since EARFCN = 0 (which translates to Band 1) is a valid number, we cannot filter it out. Please report this issue, to the device manufacturer.

 

Android 7+ phones, showing No Band

Officially Android supports band information from Android 7 (N, Nougat). The device however has to implement the API17 telephony functions, and also to fully and correctly implement them, for the app to show the Band. If the device does not implement at all the API17 functions, or if the Android API provides e.g. xARFCN = 2147483647, i.e. meaningless number - out of range, then no Band info is available in the Android API to show. These are device firmware issues. Please report this issue, to the device manufacturer.

 

LTE+ (4G+) for Android 6+ devices BETA support

Indication of LTE+ (4G+) connection type (not carrier aggregation bands), is currently in BETA development, meaning development is undergoing, and it may not work as expected. In addition, current Android does not fully support LTE+ (and no info on Carrier aggregation bands is given). Currently, from users' feedback, only two (2) phones have been shown to give LTE+ indication in Android API. From users' feedback, these devices are: Lenovo Vibe P2 (P2a42) with Android 6.0.1, and OnePlus 3T (A3003) with Android 7.0. Devices may be LTE+ ready, but the LTE+ connection maybe currently rare, and if the devices do not indicate that capability to the Android API, we have no data to show anything.

 

Phones not showing any neighbor cells

There are phones not showing any neighbor cells under a certain wireless technology, and there are phones not showing at all signal strength. These are manufacturers' issues and not ours.

 

The following issues with android phones have been identified through users' feedback (who we thank very much for the debugging information):

 

Phones not showing any signal strength

From users' feedback, a number of phones (listed below) seem not to reveal the signal strength to the Android Telephony Interface, therefore they show no signal in our app (this is manufacturers' issue): 

- BullittGroupLimited B15Q, Hardware: Mt6582, Android: 4.4.2 (API 19)

- Energy Sistem Energy Phone Max, Hardware: Mt6582, Android: 4.4.2 (API 19)

- LG G2 Lite (LGE LG-D295), Hardware: L70pds, Android: 4.4.2 (API 19)

- LG G Flex (LGE LG-LS995), Android: 4.4.2 (API 19), Android image: KOT49I.LS995ZVB

- LG Optimus F3 (LGE LG-P655H), Android: 4.1.2 (API 16), Android image: JZO54K

- LG Optimus L5 E612 (LGE LG-E612f), Android: 4.1.2 (API 16), Android image: JZO54K

- Samsung GT-I9100, Hardware: Smdk4210, Android: 4.1.2 (API 16)

- Samsung GT-I8190, Hardware: Samsunggolden, Android: 4.1.2 (API 16)

- Samsung I9300, Hardware: Qcom, Android: 4.3 (API 18)

- Samsung SCH-R530M, Hardware: Qcom, Android: 4.3 (API 18)

- Samsung SAMSUNG-SM-G530AZ, Hardware: Qcom, Android: 4.4.4 (API 19)

- Sharp Aquos Crystal (SHARP 306SH), Android: 4.4.2 (API 19), Android image: KVT49L

- ZTE Rapido (ZTE Z932L), Android: 4.1.2 (API 16), Android image: Z932LV8.0

(!) If your device doesn't show any signal with our app, you may send us the system info (from the app's settings) to check it.

 

>> Samsung Developers Forum

Topic: "TelephonyManager GetAllCellInfo() does not work on Samsung Android devices" (read on 4-Nov-2015)

 

>> Samsung Galaxy A3 (dual SIM)

This phone with Android 5.0.2 API 21 (LRX22G.A300...) has been recorded to return constantly PCI = 0 for LTE, and no LTE neighbour cell information. Also in 3G/UMTS it returns constantly PSC = -1 (shown as "n/a") for the serving cell. This is a Samsung bug/issue.

 

>> Samsung Galaxy Note 3 (SM-N9005)

This phone has recorded issue in the Android project, e.g. Issue #69578

Additionally the phone with Android 5.0 API 21 (LRX21V) was shown to return null in API 17's function getAllCellInfo(), which has as consequence that no LTE neighbor information is available in this phone.

 

>> Samsung S6 (SM-G920F)

This phone with Android 5.1.1 API 22 (Xtre.... v.2.3) has been recorded to return constantly (for more than 50") maximum signal strength value (RSSI = -51dBm, ASU = 31) for neighbours under UMTS/HSDPA (hence these neighbors' values are not reliable). This is a Samsung bug/issue.

 

>> Samsung S6 edge+ (SM-G928F)

This phone with Android 5.1.1 API 22 (LMY47X) has been recorded to return constantly maximum signal strength value (RSSI = -51dBm, ASU = 31) for neighbors under UMTS/HSDPA (hence these neighbors' values are not reliable). This is a Samsung bug/issue.

Additionally this phone has been recorded to return non-meaningful values UCID (=0,1,2,...) for UMTS neighbors. This is a Samsung bug/issue.

 

>> Samsung S5 mini (SM-G800F)

The phone in LTE mode has been recorded to return non-valid raw RSRP values (2147483647).

 

>> Samsung Galaxy S3 mini (GT-I8190N)

This phone with Android 4.1.2 (API 16) has been recorded to return ASU = 99 (i.e. non-valid signal strength) for 3G (and no neighbors). 

 

>> Cubot H1 (dual SIM, MT6735P Quad-Core 1.0GHz)

This phone with Android 5.1 API 22 (Image: R12) has been recorded to return, under UMTS, same UCID for serving and neighbor cell, and same PSC for serving and neighbor cell.