Short Answer
There any many factors to consider when choosing an Android device that will work with GoChip including Bluetooth read speed and distance, Wi-Fi and cellular bands, Android version and skinning, battery life and price. Beyond the spec sheet, each device has it’s own characteristics that can only be discovered during testing. Zone4’s testing methodology is listed below, and this article will be updated with newer devices over time.
Best Devices
These are the best devices available as tested by Zone4.
2025
- Motorola Moto E15 (2025, XT2523-6): tested spring 2025, has not been used in volume by Zone4
- Motorola Moto G (2025, XT2513-1): tested spring 2025, has not been used in volume by Zone4
2024
- Motorola Moto G85 (2024, XT2427-2): tested spring 2025, has not been used in volume by Zone4
- Motorola Moto G (2024, XT2417-1): tested spring 2025, has not been used in volume by Zone4
- Motorola Moto G Play (2024, XT2413-3): tested spring 2025, has not been used in volume by Zone4
- Motorola Moto G Stylus 5G (2024, XT2419-2): tested spring 2025, mediocre Bluetooth read speed
2023
- Motorola Moto G13 (2023, XT2331-1): tested spring 2024, has not been used in volume by Zone4
- Motorola Moto G14 (2023, XT2341-2): tested spring 2024, has not been used in volume by Zone4
2022
- Google Pixel 6a (2022, GX7AS): re-tested spring 2025, has not been used in volume by Zone4
- Motorola Moto G 5G (2022, XT2213-2): tested spring 2024, has not been used in volume by Zone4
- Motorola Moto G53 (2022, XT2335-3): tested summer 2023, used in volume by Zone4
- OnePlus Nord N300 (2022, CPH2389): tested spring 2024, has not been used in volume by Zone4
2020
- OnePlus Nord N10 5G (2020, BE2028): tested summer 2023, has not been used in volume by Zone4
Minor Issues
These devices have minor issues and may not be as well tested as the Best Devices.
2022
- Motorola Moto G Stylus 5G (2022, XT2215DL): tested summer 2023, regular (~30s) brief (~3s) BLE pauses in low latency scan mode
- OnePlus Nord N20 5G (2022, GN2200): tested spring 2024, regular (~30s) brief (~3s) BLE pauses in low latency scan mode
2021
- Motorola Moto G50 (2021, XT2137-1): tested summer 2023, regular (~30s) brief (~3s) BLE pauses in low latency scan mode
- OnePlus Nord N200 5G (2021, DE2118): tested summer 2023, regular (~30s) brief (~3s) BLE pauses in low latency scan mode
Major Issues
These devices have been tested by Zone4, major issues have been found and should not be used with GoChip. However, devices that experienced throttling during original testing may now be usable with Zone4 Go version 17 (spring 2025) or newer due to the addition of throttle detection. However they are unlikely to be re-tested due to age and lack of availability.
2025
- Motorola Moto G05 (2025, XT2523-3): tested spring 2025, poor Bluetooth read speed
- Motorola Moto G15 (2025, XT2521-2): tested spring 2025, poor Bluetooth read speed
2024
- Motorola Moto G04 (2024, XT2421-2): tested spring 2024, frequent (~1s) micro (~1s) BLE pauses in low latency scan mode
- Motorola Moto G24 (2024, XT2423-1): tested spring 2024, BLE rate is severely throttled (20p/s) in both balanced and low latency scan modes within an hour
- Motorola Moto G55 (2024), XT2435-2: tested spring 2025, poor Bluetooth read speed
- Motorola Moto G Power (2024, XT2415-3): tested spring 2025, poor Bluetooth read speed
2023
- Motorola Moto G54 (2023, XT2343-1): tested spring 2024, BLE rate is severely throttled (20p/s) within an hour in low latency scan mode, frequent (~1s) brief (~3s) BLE pauses in balanced scan mode
- Motorola Moto G Play (2023, XT2271-5): tested spring 2024, BLE rate is severely throttled (20p/s) in both balanced and low latency scan modes within an hour
- Samsung Galaxy A15 5G (2023, SM-A156M/DSN): tested spring 2024, BLE rate is severely throttled (1p/s) within an hour in low latency scan mode
2022
- OnePlus Nord CE 2 Lite 5G (2022, CPH2409): tested spring 2024, BLE rate is severely throttled (20p/s) in both balanced and low latency scan modes within an hour
- OnePlus Nord N20 SE (2022, CPH2469): tested spring 2024, BLE rate is severely throttled (20p/s) in both balanced and low latency scan modes within an hour
2021
- Motorola Moto G Power (2021, XT2117-4): tested summer 2023, frequent BLE failures
- Motorola Moto G Pure (2021, XT2163-4): frequent (~4s) micro (~1s) BLE pauses in low latency scan mode
2020
- Motorola Moto G Fast (2020, XT2045-3): tested summer 2023, frequent BLE failures
Pending Testing (August 2025)
These devices have been acquired by and are pending testing by Zone4.
Candidate Devices (August 2025)
These devices have been researched and may be acquired for testing by Zone4 if a supplier can be found.
- Motorola Moto G Power (2025): looks very similar to Motorola Moto G (2025) which was classified as a Best Device
- Motorola Moto G Stylus 5G (2025)
- Motorola Moto G56 (2025): expensive, see if it drops in price
- Motorola Moto G86 (2025): expensive, see if it drops in price
- Motorola Moto G86 Power (2025): probably expensive
- Motorola Moto G96 (2025)
Legacy Devices
These devices have previously been Zone4’s workhorse devices but have been superseded by newer devices with better availability.
- OnePlus Nord N100 (2020, BE2011/BE2012): in large use by Zone4 since 2020 but a major issue with delayed delivery of BLE packets in noisy BLE environments has since been discovered requiring a less aggressive scan mode resulting in a lower packet rate
- Xiaomi Mi A2 Lite (2018, M1805D1SG)
- Motorola Moto E4 Plus (2017, XT1775)
- Xiaomi Mi A1 (2017, MDG2)
- HTC One m7 (2013)
- LG Nexus 5 (2013, LG-D820)
Minimum Requirements
- Android 5.1 or newer
- Bluetooth 4.0 or newer with Bluetooth Low Energy (BLE) support
- 5GHz (or 6GHz) Wi-Fi (also called: dual-band, triple-band, Wi-Fi 5, Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7, 802.11ac, 802.11ax, 802.11be)
- cellular band compatibility in your region
Internet Connectivity
If the device is only used on Wi-Fi networks then cellular connectivity is not need. Conversely, if the device is only used on cellular networks, then Wi-Fi is not needed. Although 2.4GHz only Wi-Fi will technically work, this shares the same frequency with the GoChips resulting in degraded network performance so 5GHz Wi-Fi is considered essential.
How to Test a Device
To test if an Android device is capable of reading GoChips, Zone4 has developed a set of requirements and/or tests for the important specifications and operations of Android devices. These tests are based around measuring performance and handling typical race conditions.
Bluetooth Read Speed
Bluetooth read speed is the number of Bluetooth packets a device can process in a period of time and the consistency of this processing rate. The read speed must be high enough that the device can process packets from a large group of quickly passing GoChips. The read speed is impacted by the devices Bluetooth radio, processor, drivers and software limitations. It can only be determined by testing.
There is a tool built into the Zone4 Go app that benchmarks the number of packets read, the read rate and population of GoChips read. Quantifying the read speed of a given device cannot be expressed as an absolute value (packets/second), only as relative to a baseline device. This is because the quantity, distance and behaviour of nearby GoChips impacts this read rate significantly.
The consistency of read rates should also be considered. Some devices tested read packets in blocks and then go idle for a period of time before reading another block. This creates the potential to miss GoChips during the idle time.
Device’s will be classified based on their Bluetooth read speed in the Zone4 office:
- Best Devices: 175 packets/second or higher
- Minor Issues: 125-175 packets/second
- Major Issues: 125 packets/second or lower
Bluetooth Read Distance
Bluetooth read distance is how far away a GoChip can be read by a device. This should be tested by keeping the device and GoChips at the same height and orientation; 4 feet from the ground, 10 GoChips label side facing the back of the device. Open the Bluetooth Read Speed tool in the Zone4 Go app and find the furthest distance between the device and GoChips that consistent reads can be attained.
Unexpected BLE Behaviour
Bluetooth Stopping
During testing of some devices, BLE packet reading would unexpectedly get stopped in such a way that the Zone4 Go app would not be able to restart reading without user intervention. Typically this would happen when switching away from the Zone4 Go app to the homescreen or another app.
Delayed BLE Packets
During testing of some devices in noisy BLE environments, BLE packets would not immediately be delivered to the Zone4 Go app. This delay would generally increase over time as the phone got further and further backlogged. This backlog can be reset by rebooting the phone or turning Bluetooth off and back on again. To test for this issue:
- perform the testing in a noisy a BLE environment which can be created by having thousands of GoChips nearby
- clear any potential backlog on the device under testing by rebooting it
- after rebooting, open the Zone4 Go app
- run a GoChip over a running Activator and the new time should appear in the Zone4 Go app within a couple of seconds
- continue to run the GoChip over the Activator every 5 minutes and ensure the new time appears in the Zone4 Go app within a couple seconds
- if it takes longer and longer for times to appear in the Zone4 Go app, the device likely has a major issue with delayed BLE packets
Other Considerations
Battery Life
It is important that the device’s battery lasts for the duration of a normal race. If a device does not last for the duration of the race, attach a USB battery pack to extend the battery life of the device. Zone4 has used Anker battery packs with great success.
Testing Battery Life
Testing the battery life of a device requires several variables be kept constant. The device should be in proximity to 100 GoChips, screen on at full brightness and have the Zone4 Go app running in the foreground. Run the device from full charge to empty battery and the run time is considered the battery life.
Choosing a device with a long battery life
Battery life of a device is impacted by a handful of factors; hardware speed and optimizations, screen resolution and brightness, battery size and software optimizations.
Newer hardware technology is physically smaller which results in lower power consumption. This resultant reduction is power consumption is offset by increasing the performance of the hardware so it consumes as much power as the previous generation but has higher performance. Lower priced value targeted hardware typically has lower power consumption than higher priced performance hardware.
The device’s screen is the biggest power consuming component in a device. Newer screen technologies such as OLED when displaying specifically designed interfaces may change this. A device with a lower resolution display, turning off the screen or adjusting brightness will have a significant impact on battery life.
Battery size is a very simple way to increase battery life. A bigger battery will make the device larger and heavier which is of little concern to a GoChip specific device. Phoes are increasing becoming available in a ‘plus’ version with a bigger screen and battery.
Software optimization will also increase battery life. However, some optimizations will have a negative performance impact on the Zone4 Go app reducing the ability to read GoChips or transmit data to Zone4’s servers. The Zone4 Go app does what it can work around these optimizations but to ensure the best performance, keep the app open and the screen on.
Physical Aspects
Screen
Android devices range in size from small phones to large tablets. Screen size becomes important when considering using the device as a keypad. Due to the limited options available in tablet sized devices, no devices that meet Zone4’s requirements have been found at a reasonable price. Using a device with a 5″ screen or larger has generally performed well for prolonged keypad use, although the bigger the screen the better.
Screen brightness should also be considered as this impacts readability in outdoor race conditions. Higher resolutions screens will reduced battery life and provide little benefit for GoChip applications. Similarly, screens with better colour quality provide few benefits.
Ruggedness
Devices at events get treated rougher and are put through conditions that personal devices don’t experience. Manufacturing material and construction has an impact on the amount of abuse a device can take. Construction of the device has a bigger impact than material used (plastic vs metal), however glass backed devices (for wireless charging) should be avoided.
There are an increasing number of devices available with some degree of water and/or dust resistance or proofing. This is certainly an advantage but devices without this feature can be protected with a simple plastic bag.
Connecting to the Internet
The most popular and simplest way to connect to the internet is through cellular networks. When buying a new device, ensure it supports the cellular frequencies used by local carriers. Wilson Amplifiers provides an excellent North American guide to this:
https://www.wilsonamplifiers.com/frequencies-by-provider
If using Wi-Fi instead of cellular data to connect to the internet, it is important to make sure to use 5GHz (or 6GHz) Wi-Fi and not the more common 2.4GHz Wi-Fi. GoChip technology uses Bluetooth for communication which shares the same frequencies with the near universally supported 2.4GHz Wi-Fi. Having GoChips in close proximity to 2.4GHz Wi-Fi networks will provide network degradation, increasing with the number of GoChips present. 5GHz (or 6GHz) Wi-Fi avoids this congestion by using an entirely different frequency.
Devices that support 5GHz (or 6GHz) Wi-Fi are almost ubiquitous with new devices but this can be confirmed by checking the device’s Wi-Fi specification for one or more of the following terms: dual-band, triple-band, Wi-Fi 5, Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7, 802.11ac, 802.11ax, 802.11be. This isn’t the only requirements that is needed, an available 5GHz Wi-Fi network is also required. Again these are becoming increasingly common in home and public networks but haven’t reached ubiquity. When designing a permanent network installation, ensure a 5GHz Wi-Fi network is included.
Android Version, Skinning and Modifications
The Android operating system has a large amount of fragmentation resulting from a massive variety of devices, variety of update schedules, manufacturer/carrier skins, modifications and restrictions. This fragmentation makes it difficult to predict the behaviour of a similar hardware configuration from different manufacturers.
Newer versions of Android have focused on increasing battery life by adding restrictions that reduce the performance of apps when in the background. The Zone4 Go app performs best when in the foreground but takes advantage of workarounds provided by the Android framework to maintain performance when in the background. There is no recommended Android version other than being Android 5.1 or newer.
Manufacturer skinning can vary from small tweaks that add functionality to complete re-designs of the interface that are barely recognizable. Skins shouldn’t have an impact on the performance of the Zone4 Go app but makes it difficult to support other other skins when the interface is re-arranged, renamed or operates differently. Sticking to a device with a relatively ‘stock’ version of Android is preferred.
Issues resulting from software modification made by the manufacturer (or carrier in locked devices) can be the most difficult to detect and diagnose. These modifications usually target increasing battery performance but don’t conform to Android specifications and cannot be worked around. Additionally, devices that come locked from a carrier typically have a further modified version of Android with restrictions on features that impact their service. Carriers also act as an additional delay and/or risk of the device receiving updates. Devices that are factory unlocked and run a minimally modified version are least likely to experience unexpected behaviour.
Apple iOS Devices (iPhones and iPads)
Zone4 has done some experimenting with iOS apps but found some show-stopping limitations in the architecture. The development of an iOS app has not been completely ruled out but it will likely be focused on providing a keypad and less so on GoChip.