Difference between revisions of "Tested Phones"

Tested Phones (view source)

Revision as of 13:25, 6 January 2024

81 bytes added , 6 January

→‎Samsung: some edits on a13, a23 and a33 (try 2)

Poggy205

195

edits

@@ Line 534: / Line 534: @@
 | Samsung Galaxy A13 5G (US) || SM-A136U || 13 || 5.5.4 || {{Yes}} || {{Yes}} || {{Yes}} || || {{Yes}} || Displays lots of NSA info NR SS, NR PCI, Band Name/Name and RFCN
 |-
-| Samsung Galaxy A13 || SM-A135F/DS || 13 || 5.6.0 || {{Yes}} || {{Yes}} || || || || API 4.2 working on 4G/2G. 3G not tested!
+| Samsung Galaxy A13 || SM-A135F || 13 || 5.6.0 || {{Yes}} || {{Yes}} || (Not tested) || || || API 4.2 seems to work fine on 4G/2G, but 3G is not tested. This phone may need more testing.
 |-
 | 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}} || {{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 :(
+| Samsung Galaxy A23 || SM-A235F || 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. The A23 doesn't support, nor read LTE_CA. Based on a Snapdragon 680 4G.
 |-
 | 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.
 |-
-| 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 A33 5G || SM-A336E || 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.