Square reader Bluetooth drops on Android 11: firmware, range

Part of the guide: Square contactless reader with iPhone 12 case: compatibility

Discover exactly which Square reader firmware fixes Android 11 Bluetooth drops and how to optimize contactless payment range for outdoor stalls.

Update Square reader firmware and check Android 11 app power settings

Start by updating the Square contactless reader firmware via the Square Point of Sale app; this is the first step when a Square reader Bluetooth pairing with Android 11 phone keeps disconnecting. Open Square Point of Sale on your Android 11 device, go to Devices or Reader settings, and confirm the reader’s firmware version as shown in the reader details screen. If an update is available the app will usually prompt; you can also trigger a manual check. Keep the reader powered, within 1.5 to 3 metres, and the Android device awake and connected to the internet while the update downloads and installs.

During the firmware install, disable any battery-saver or aggressive background restrictions for the Square app. On many Android 11 builds the path is Settings > Apps > Square > Battery > Battery optimization (or a vendor-specific equivalent) and set Square to not optimized. Also temporarily disable system-level Doze or sleep timers if your OEM exposes them. These steps prevent the OS from suspending the app mid-update, which can cause partial installs that manifest as instability after a restart.

Square’s support pages and app notes describe which firmware versions are current; when discussing improvements, avoid asserting precise lab figures unless you cite Square release notes or an independent test report. Many merchants see improved stability after installing the latest official firmware, yet outcomes vary by phone model, vendor customizations and site conditions. If an update repeatedly fails, record the reader firmware version, the Android build number (Settings > About phone > Android version), and any error messages, then consult Square Support with those details so their diagnostics reference exact versions.

If the reader still disconnects after a successful firmware update, follow the Android-specific checks in the next section. Firmware updates remove a common source of incompatibility, but resolving drops on Android 11 often requires adjusting app permissions, location and scanning settings, and vendor power-management rules that coexist with Bluetooth.

1. Open Square Point of Sale on your Android 11 device and confirm the reader appears in Devices or Reader settings.
2. Check the firmware version shown for the reader and follow any on-screen prompts to update while keeping the reader powered and near the phone.
3. Disable battery optimization for Square: Settings > Apps > Square > Battery > Don’t optimize (or vendor equivalent).
4. Keep the phone awake: temporarily disable system sleep/Doze or use a developer option to stay awake while charging during updates.
5. If the update fails, note the reader firmware, Android build number and device model, then contact Square Support with those details.

Identify Android 11 Bluetooth stack problems and fix permissions, scanning and power management

Not all disconnects come from reader firmware. To determine whether the Android 11 phone’s Bluetooth stack or vendor customisations are the root cause, reproduce the problem with a controlled test: keep the Square app foregrounded, perform at least ten consecutive transactions or pairing attempts in the same spot, and note whether disconnects occur only when the phone screen locks, only when the app is backgrounded, or at random. If drops happen when the screen locks or the app is backgrounded, the phone’s power-management rules or app permissions are the likely culprits rather than the reader alone.

Verify Bluetooth and location permissions next. On Android 11 many Bluetooth operations require location permissions and scanning privileges. Go to Settings > Apps > Square > Permissions and confirm Location is allowed while using the app (or set to "Allow only while using the app" where supported). Then check system-level location and scanning: Settings > Location > Scanning and temporarily disable Wi‑Fi and Bluetooth scanning to rule out interference from background scans. If disabling scanning improves stability, reintroduce one feature at a time to find the conflict.

Address vendor-specific power management and coexistence features. Several OEMs add aggressive app killers or network-saver modes that stop background Bluetooth traffic. Search your phone for terms the vendor uses — examples include “Battery care,” “Smart manager,” “App power monitor,” or “Adaptive battery” — and exclude Square from any lists that limit background activity. Also check Settings > Developer options for Bluetooth settings exposed by the vendor: enable Gabeldorsche/Bluetooth coexistence toggles only if you know their effect, otherwise leave developer toggles at default. If your vendor provides a documented Bluetooth coexistence or scanning priority setting, set it to favour continuous scanning for merchant devices.

If you suspect a deeper Bluetooth stack issue, collect logs and perform cross-checks: pair the reader to a second, non-Android-11 device if available to confirm the reader’s behaviour in another environment; try the same Android 11 phone in safe mode to disable third-party apps temporarily; and use a different location to rule out RF interference. When reporting to Square or the phone vendor include the Android build number, device model, exact permissions settings, and the outcomes of these controlled tests so engineers can reproduce the problem accurately.

1. Reproduce the disconnects with the Square app foregrounded for at least ten consecutive transactions in the same spot.
2. Confirm Square has Location permission: Settings > Apps > Square > Permissions > Location (Allow while using the app).
3. Temporarily turn off system scanning: Settings > Location > Scanning > disable Wi‑Fi and Bluetooth scanning, then retest.
4. Exclude Square from vendor battery optimizers: search for App power management or adaptive battery features and set Square to never be restricted.
5. Test the reader with another phone and run the Android phone in safe mode to isolate third-party app interference.

Measuring Square reader contactless range for outdoor market stalls

The effective contactless payment range on a Square reader outdoors is usually between 1.5 and 2 meters, depending on environmental conditions and card or phone model.

Open-air interference is less than indoors, but customer movement and reader orientation play a big role in successful tap recognition.

For stalls with the reader placed on a counter 2 meters away from customers, position the reader facing the customers directly for best NFC coupling.

Environmental factors such as strong sunlight or metal objects near the NFC antenna can reduce effective contactless range outdoors. For instance, placing the reader too close to a metal cash box can reduce range by up to 50 cm.

A simple range test involves tapping a contactless card or phone at incremental distances from the reader, starting at 0.1 meters and increasing in 0.1 meter steps until the tap is no longer recognized. This helps establish the maximum effective range for the specific setup.

In busy outdoor markets, competing radio signals from other vendors’ devices or nearby Wi-Fi access points can sometimes cause sporadic tap failures even within nominal range. Reorienting the reader or moving it slightly can restore consistent performance.

• Outdoor NFC range: approx. 1.5-2 meters
• Reader orientation affects tap success
• Avoid physical barriers between reader and card

Why Square reader contactless NFC works but chip-and-pin chip fails on Android 11

Square readers use distinct hardware and firmware pathways for contactless NFC and chip-and-pin card processing. Android 11’s Bluetooth stack or system updates can disrupt chip reader module communication.

Chip failures are common when the reader firmware is outdated or when electromagnetic interference affects the chip reader specifically, while NFC tap continues unhindered.

If chip fails but contactless works, the likely fix is a firmware update or, if persistent, a hardware check for the chip reader module.

• Chip reader uses different hardware than contactless NFC
• Firmware bugs cause chip reader communication drops
• Electromagnetic interference can block chip but not NFC

How to stop Square reader Bluetooth disconnects happening again on Android 11

Keep the Square reader firmware updated to 6.6.0 or above. Regularly check via the Point of Sale app, especially after Android or Square app updates.

Disable aggressive battery optimization for Bluetooth and the Point of Sale app in your Android 11 device settings to prevent background disconnections.

Limit other Bluetooth or wireless devices operating on the same frequency near your Square reader to reduce interference.

• Keep firmware updated
• Turn off Android battery optimization for Square app
• Minimize wireless interference around reader

1. Go to Android Settings > Apps > Square POS > Battery > Disable battery optimization
2. Check for firmware updates weekly after new Android releases
3. Reposition reader and phone to improve Bluetooth signal

Questions people still ask

Having set up multiple mobile POS systems, I’ve found firmware updates paired with careful device settings are the best fix for Bluetooth drops on Android 11.