198
edits
Difference between revisions of "Tested Phones"
Jump to navigation
Jump to search
→Samsung: update on a23 and a33
(→Xiaomi) |
(→Samsung: update on a23 and a33) |
||
| Line 538: | Line 538: | ||
| Samsung Galaxy A20s || SM-A207 || 10.0 || 5.5.3 || {{Yes}} || {{Yes}} || {{Yes}} || || || Full API 4.2 support for 4G/3G/2G w/o root. In some rare occasions, API 4.2 may report additional extra data and no band infomation on 2G/3G if enabled API 4.2. Does not require root but location services have to be enabled to read full band/frequency data. | | Samsung Galaxy A20s || SM-A207 || 10.0 || 5.5.3 || {{Yes}} || {{Yes}} || {{Yes}} || || || Full API 4.2 support for 4G/3G/2G w/o root. In some rare occasions, API 4.2 may report additional extra data and no band infomation on 2G/3G if enabled API 4.2. Does not require root but location services have to be enabled to read full band/frequency data. | ||
|- | |- | ||
| Samsung Galaxy A23 || SM-A235F/DS || 13 || 5.6.1 || {{Partial}} || {{Yes}} || || || || API 4.2 works fine on 4G, but has the same RSCP bug on 3G and ARFCN disappearance bug on 2G. Since this has a Snapdragon chipset, it reads LTE RSSI and TA just fine. Phone doesn't | | Samsung Galaxy A23 || SM-A235F/DS || 13 || 5.6.1 || {{Partial}} || {{Yes}} || {{No}} || || || API 4.2 works fine on 4G, but has the same RSCP bug on 3G and ARFCN disappearance bug on 2G. Since this has a Snapdragon chipset, it reads LTE RSSI and TA just fine. Phone unfortunately doesn't support LTE_CA :( | ||
|- | |- | ||
| rowspan="2" | Samsung Galaxy A30 || SM-A305GN || 10.0 || 5.5.3 || {{Partial}} || {{Yes}} || {{Yes}} || || || Reads only 4G band/freq data on both SIMs. API 4.2+ reads -51 dBm and additional extra data on 2G/3G if enabled API 4.2. API 4.2 bug as for all Exynos based models. Does not require root but location services have to be enabled to read full band/frequency data. | | rowspan="2" | Samsung Galaxy A30 || SM-A305GN || 10.0 || 5.5.3 || {{Partial}} || {{Yes}} || {{Yes}} || || || Reads only 4G band/freq data on both SIMs. API 4.2+ reads -51 dBm and additional extra data on 2G/3G if enabled API 4.2. API 4.2 bug as for all Exynos based models. Does not require root but location services have to be enabled to read full band/frequency data. | ||
| Line 544: | Line 544: | ||
| SM-A305G || 11.0 || 5.5.3 || {{Partial}} || {{Yes}} || {{Yes}} || || || Full API 4.2 support for 4G Only. 2g-3g old -51 dBm API bug as for all Exynos based models. | | SM-A305G || 11.0 || 5.5.3 || {{Partial}} || {{Yes}} || {{Yes}} || || || Full API 4.2 support for 4G Only. 2g-3g old -51 dBm API bug as for all Exynos based models. | ||
|- | |- | ||
| Samsung Galaxy A33 5G || SM-A336E/DSN || 13 || 5.6.1 || {{Partial}} || {{Yes}} || || || {{Yes}} || API 4.2 works fine on 4G, but has a -24 dBm RSCP bug on 3G, plus ARFCN seems to disappear on some 2G towers. Also shows a lot of 5G NSA info. Since One UI 5.1, 5G NSA connection becomes very intermittent. | | Samsung Galaxy A33 5G || SM-A336E/DSN || 13 || 5.6.1 || {{Partial}} || {{Yes}} || || || {{Yes}} || API 4.2 works fine on 4G, but has a -24 dBm RSCP bug on 3G, plus ARFCN seems to disappear on some 2G towers. Also shows a lot of 5G NSA info. Since One UI 5.1, 5G NSA connection becomes very intermittent. Phone supports LTE_CA, but doesn't seem to read it on Cellmapper? | ||
|- | |- | ||
| Samsung Galaxy A50 || SM-A505G || 11.0 || 5.5.3 || {{Partial}} || {{Yes}} ||{{Yes}} || || || Full API 4.2 support for 4G Only. 2g-3g old -51 dBm API bug as for all Exynos based models. LTE_CA (LTE-A) detection does not always work with dual sim as of 5.5.3. | | Samsung Galaxy A50 || SM-A505G || 11.0 || 5.5.3 || {{Partial}} || {{Yes}} ||{{Yes}} || || || Full API 4.2 support for 4G Only. 2g-3g old -51 dBm API bug as for all Exynos based models. LTE_CA (LTE-A) detection does not always work with dual sim as of 5.5.3. | ||