Difference between revisions of "Tested Phones"
Jump to navigation
Jump to search
(→vivo) |
(some edits to a13, a23 and a33) Tags: Mobile edit Mobile web edit Advanced mobile edit |
||
Line 1: | Line 1: | ||
=== Samsung === | === Samsung === | ||
* For Snapdragon chipset devices, you can easily unlock all bands supported by the hardware instead of being limited to only the ones your carrier allows. For more information [https://forum.xda-developers.com/t/how-to-enable-all-bands-through-service-menu-on-us-ca-s22-series-including-sub-6-and-mmwave.4488435/ see this XDA post]. | * For Snapdragon chipset devices, you can easily unlock all bands supported by the hardware instead of being limited to only the ones your carrier allows. For more information [https://forum.xda-developers.com/t/how-to-enable-all-bands-through-service-menu-on-us-ca-s22-series-including-sub-6-and-mmwave.4488435/ see this XDA post]. | ||
Line 534: | Line 77: | ||
| 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 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 | | Samsung Galaxy A13 || SM-A135F || 13 || 5.6.0 || {{Yes}} || {{Yes}} || (Not tested) || || || API 4.2 seems to be working 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 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 | | 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. Reads LTE RSSI and TA ok. 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. | | 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 87: | ||
| 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 | | 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. | | 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. | ||
Line 564: | Line 107: | ||
|} | |} | ||
</div> | </div> | ||
Revision as of 13:13, 6 January 2024
Samsung
- For Snapdragon chipset devices, you can easily unlock all bands supported by the hardware instead of being limited to only the ones your carrier allows. For more information see this XDA post.
- You can lock bands on most newer Samsung phones in ServiceMode (not tested on MediaTek chipset devices) by dialing *#2263# in the stock dialer app.
- For US devices, 5G NSA band detection is dependent on CSC.
- Most Samsung Phones do not support Cell ID API 4.2 before Android 8. If you use a stock or custom Samsung Experience ROM (TouchWiz/OneUI) based on Android 8.0 "Oreo" or later, please use the Android 4.2+ CellID API. Note: This may not work on custom Samsung Experience ROMs ported from other devices than your own, or based on newer versions of Android than is officially available in stock Samsung Experience updates for your device. If you use a custom Samsung Experience ROM, please make sure it is based upon an official Samsung Experience stock ROM from your device model. Custom ROMs not based upon stock, such as LineageOS or ResurrectionRemix may not work for the 4.2+ CellID API.
- In some devices Cell ID API 4.2 may show extra data compared to the old API, but most important parameters are invalid or missing. Do not use Cell ID API 4.2 for cellmapping, if the chart below displays your device incompatible. Failing to do so may cause invalid data being displayed on the map.
- To force 2G/3G/4G LTE only mode on samsung phones, The easy way is an app called Advanced Signal Status however on certain samsung phones with 4.4.4 KitKat or newer, including Lollipop 5.x, it is also possible by dialing *#*#4636#*#*, then Device Information, and "Set preferred network type". This may require root on certain carriers. Tested and does not require root on AT&T (310-410).
- To force an LTE Band on Samsung phones running 4.4.4, It is possible by dialing *#0011# > Back > INPUT type Q > INPUT 0000 wait for 15 seconds then you into Band Mode.
- Most Samsung phones can be rooted with CF-Auto-Root 2G/3G/4G bands can be locked using Network Signal Guru but only with most qualcomm chipset. Remember to set "Read qualcomm LTE data (root) under cellmapper app settings, exit and reload cellmapper and allow permissions for cellmapper.
- (Warning: feature deprecated since 5.1.4) Most Samsung phones support reading bands and frequency when Service Mode (*#0011#) is active. Using this feature you need to run Cellmapper in the background and have Service Mode in the foreground. That feature working with root and without. Please check manual here.
Phone Name | Model Number | Android Version | Cellmapper version | API 4.2 Support | Support read Bands / Freq | Support read LTE_CA | B66/71 Bug | 5G | More info |
---|---|---|---|---|---|---|---|---|---|
Samsung Galaxy K Zoom | SM-C115 | 4.4.2 | 4.1.1 | No | May report incorrect TAC on LTE | ||||
Samsung Galaxy Ace Style LTE | SM-G357FZ | 4.4.4 | 4.1.4 | No | |||||
Samsung Galaxy Ace 4 LTE | SM-G357FZ | 4.4.4 | 4.1.1 | No | Root and service mode running foreground needed | In some occasions rooted device may report some invalid data if the API 4.2 is enabled. | |||
Samsung Galaxy Note 4 | SM-N910F | 6.0.1 | 4.1.4 | No | |||||
Samsung Galaxy S3 Mini | GT-I8190N | 4.3 | 4.0.8 | No | No | Report bad data on Stock Rom | |||
Samsung Galaxy S3 4G | GT-I9305 | 4.4.4 | 4.1.1 | No | Yes | Cellmapper Field Test Reader and with root working | |||
Samsung Galaxy S4 | GT-I9506 | 5.0.1 | 4.1.1 | No | Not tested | ||||
GT-I9505 | No | Not tested | |||||||
Samsung Galaxy S5 | SM-G900A | 5.1.1 | 4.1.2 beta | Partial | Root and service mode running foreground needed | ||||
SM-G900I | Partial | ||||||||
SM-G9006V | 6.0.1 | 5.4.5 | Partial | Partial | Root and service mode running in foreground needed for UMTS & LTE bands only. Doesn't read 2G bands regardless of root or not. | ||||
Samsung Galaxy S5 Neo | SM-G903F | 6.X | 4.1.6 | Yes | Yes | ||||
Samsung Galaxy S6 | SM-G920F | 6.0.1 | 4.1.6 | Partial | Yes | Yes | Only Enable API 4.2 for 4G only. 2G-3G reads errors if enabled API 4.2 - also old api 2g-3g problem - service mode running foreground needed | ||
Samsung Galaxy S6 Edge+ | SM-G928F | 6.0.1 | 4.1.6 | Partial | Yes | Yes | Only Enable API 4.2 for 4G only. 2G-3G reads errors if enabled API 4.2 - also old api 2g-3g problem - service mode running foreground needed | ||
Samsung Galaxy S7 | SM-G930F | 8.0.0 | 5.1.7 | Yes | Yes | Yes | Full API 4.2 support as of Android Oreo update. Older Android has only partial API 4.2 support. 2g-3g update cell info very infrequently and most of the times reports -51 dBm and no band info regardless of Android version. | ||
Samsung Galaxy S8 | 7.0 | 5.0.9 | Partial | Yes | Yes | Only Enable API 4.2 for 4G only. 2G-3G reads errors if enabled API 4.2 - also old api 2g-3g problem | |||
Samsung Galaxy S8+ | SM-G955FD | 8.0.0 | 5.2.4 | Partial | Yes | Yes | Full API 4.2 support for 4G Only as of Android Oreo update. 2g-3g old -51 dBm API bug as for all Exynos based models. | ||
Samsung Galaxy S9 | SM-G960F | 10 | 5.5.3 | Yes | Yes | Enable use Android 7.0+ Cell ID API and Record neighbor cells this maps 4G fine. Records 5G DCNR Status fine. Not tried 2G/3G. | |||
Samsung Galaxy S10 5G | SM-977B | 10.0 | 5.3.1 | Partial | Yes | Yes | Yes | Only Exynos version supported record 5G tiles: See | |
Samsung Galaxy S21 5G (US) | SM-G991U | 13.0 | 5.6.0 | Yes | Yes | Yes | Works perfectly, LTE TA shown, and everything maps without any obvious problems. | ||
Samsung Galaxy S21 Ultra 5G | SM-S998U1 | 13.0 | 5 beta | Not tested | Not tested | Not tested | Not tested | ||
Samsung Galaxy S22 Ultra | SM-S908U | 13.0 | 5.6.0 beta | Yes | Yes | Yes | 2G/3G seems to work okay. LTE TA not reported by device. NR SA works. | ||
SM-S908B/DS | 13.0 | 5.6.0 | Partial | Yes | Yes | Yes | Samsung Exynos 2200. Working perfect in 5G/4G w/o root. 5G/4G on one sim, only 4G on the other. Not tested for 3G/2G. LTE TA not reported by device, though this may need more testing. | ||
Samsung Galaxy S23 | SM-S911B | 13.0 | 5.6.0 | Yes | Yes | Yes | LTE TA and CQI not reported by device. | ||
Samsung Galaxy Xcover 3 | SM-G388F | 5.1.1 | 4.1.1 | No | Not tested | ||||
Samsung Galaxy Core Prime | SM-G360F (EU) | 5.0.2 | 5.4.1 | Yes | Yes | Root needed i used CF-Auto-Root 4G/3G/2G bands can be locked using Network Signal Guru (Tested with version 2.11.2) once rooted, However without rooting it can still be used with basic information. 4G LTE bands supported 1(2100)/3(1800)/7(2600)/8(900)/20(800), LTE Cat4 Device. | |||
SM-G360FY (India) | 4.4.4 | 4.1.2 | No | ||||||
Samsung Galaxy A5 2015 | SM-A500FU | 6.0.1 | 5.0.7 | Partial | No | Didn't tried with root. Without root, 4G looks like ok, but 3G shows wrong dBm. | |||
Samsung Galaxy A5 2017 (EU) | SM-A520F | 6.0.1 | 5.X | Partial | No | ||||
Samsung Galaxy A5 (2017) | SM-A520F | 8.0.0 | 5.X | Partial | Yes | Yes | Full API 4.2 support for 4G Only as of Android Oreo update. 2g-3g old -51 dBm API bug as for all Exynos based models. | ||
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 | 13 | 5.6.0 | Yes | Yes | (Not tested) | API 4.2 seems to be working 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 | 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. Reads LTE RSSI and TA ok. The A23 doesn't support, nor read LTE_CA. Based on a Snapdragon 680 4G. | ||
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. | ||
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 | 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 Tab A (2018, 10.5) | SM-T595 | 8.1.0 | 5.2.4 | Yes | Yes | Yes | Working perfect in 2G/3G/4G w/o root | ||
Samsung Rugby LTE | SGH-I547C | 4.1.2 | 4.1.4 | No | Yes | Root and service mode running foreground needed. Bands can be forced with *#BAND# | |||
Samsung Galaxy Alpha | SM-G850F | 5.0.2 | 5.0.7 | Partial | Yes | Only Enable API 4.2 for 4G only. 2G-3G reads errors if enabled API 4.2 - also old api 2g-3g problem - service mode running foreground needed | |||
Samsung Galaxy J3 | SM-J320FN | 5.1.1 | 5.3.0 | Yes | Yes | Working perfectly in 2G/3G w/o root. Not tested yet for 4G | |||
SM-J320G | Yes | Yes | Working perfectly in 2G/3G/4G w/o root. | ||||||
Samsung Galaxy J4 | SM-J400M | 8.0.0 | 5.2.7 | Yes | Yes | Working perfectly in 2G/3G w/o root. Not tested yet for 4G | |||
Samsung Galaxy J8 | SM-J810Y/DS | 9.0 | 5.5.3 | Yes | Yes | Yes | Full API 4.2 support for 4G/3G/2G on both SIMs w/o root. Based on Qualcomm Snapdragon 450 chipset. |