Difference between revisions of "Tested Phones"

Jump to navigation Jump to search
52 bytes added ,  03:41, 4 May 2023
→‎Samsung: update on a33 5g
(→‎vivo: 2 phones tested)
(→‎Samsung: update on a33 5g)
Line 498: Line 498:
| 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.0 || {{Partial}} || {{Yes}} || || || {{Yes}} || API 4.2 works fine on 4G, but has a -24 dBm RSCP bug on 3G. ARFCN seems to disappear in some towers on 2G. Also shows a lot of 5G NSA info.
| Samsung Galaxy A33 5G || SM-A336E/DSN || 13 || 5.6.0 || {{Partial}} || {{Yes}} || || || {{Yes}} || API 4.2 works fine on 4G, but has a -24 dBm RSCP bug on 3G. ARFCN seems to disappear in some towers on 2G. Also shows a lot of 5G NSA info. LTE_CA detection doesn't work even when on new API.
|-
|-
| 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 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 as of 5.5.3.
195

edits

Navigation menu