Datalogic Falcon X60 / X65 troubleshooting guide: errors, faults and fixes

Short answer: The good read feedback options are set separately in Datalogic Settings > Scanner & Decoder > Good Read: Enable good read, Enable Green Spot, Enable good read LED and Enable vibrator. The beep volume is set on the Notification page (Good read audio volume).

Likely cause

According to Datalogic, the Falcon X60/65 confirms a good read with the Green Spot (green dot projected onto the barcode), a light, a sound and a vibration, each of which can be enabled separately on the Good Read page. The sound goes through the audio channel chosen in Good read audio channel (Scanner, Music, Voice-call, Alarm or Ring) and its volume is set in Good read audio volume.

What to do

1. Open Datalogic Settings > Scanner & Decoder > Good Read.
2. Enable Enable good read, then the feedback you want: Enable Green Spot, Enable good read LED and Enable vibrator.
3. Open Scanner & Decoder > Notification: check Good read audio mode (tone or audio file) and Good read audio channel, then turn up Good read audio volume.
4. If the Green Spot disappears too quickly, set Good read duration or Good read timeout: the latter sets how long the light and the Green Spot stay on after decoding, unless the trigger is released first.
5. If the mobile computer does not respond to the trigger at all, see the scanner no longer scans entry.

According to the Datalogic data sheet, the Green Spot is available on all Falcon X60/65 scan engines; it remains visible up to 10 m with the extra-long-range (XLR) engine.

Sources: Good Read | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Notification | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60/65: Handheld Mobile Computers – Datalogic (opens in a new window) – Datalogic Falcon X60/65 product page (official documentation).

Short answer: Open Datalogic Settings > Scanner & Decoder: check that the scanner is enabled (Enable Scanner) and that the scan source is the scan engine (Scan engine). Then check that the triggers are not disabled in the physical keypad settings. If only one barcode type is not read, reset the symbologies configuration.

Likely cause

According to the Datalogic Settings documentation, several settings stop scanning: the internal scanner disabled (Enable Scanner), the scan source switched to the rear camera (Input type set to Camera rear), the physical triggers disabled (Triggers, active by default) or symbologies disabled.

What to do

1. Open Datalogic Settings > Scanner & Decoder > Scanner Options and enable Enable Scanner.
2. In Scanner & Decoder > Input Selection, check that Input type is set to Scan engine (default value) and not to Camera rear.
3. In Keyboard & Touch > Physical keyboard, check that Triggers is enabled: this setting enables or disables the triggers.
4. Still in Scanner Options, check Enable Illumination (illumination helps decoding) and Enable Aim (laser aiming).
5. If only one barcode type is not read, open Scanner & Decoder > Symbologies Configuration and tap Reset symbologies configuration to return to the default configuration, or Enable all symbologies to run a test.
6. If scanning does not come back, tap Reset configuration at the bottom of the Scanner Options screen to return this page to its default values (see resetting the settings).

Datalogic specifies that the Datalogic Settings options may vary depending on the device, the region and the software version.

Sources: Scanner Options | Technical Documentation (opens in a new window) · Input Selection | Technical Documentation (opens in a new window) · Physical keyboard | Technical Documentation (opens in a new window) · Symbologies Configuration | Technical Documentation (opens in a new window) · Datalogic Settings | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: The range depends on the scan engine: Datalogic offers the Falcon X60/65 in a standard, long-range or extra-long-range (XLR) version. Use the two-stage TrueAim trigger (Half Trigger mode) and enable Enhance DoF, which extends the maximum scanning distance.

Likely cause

Datalogic offers the Falcon X60/65 with three 2D engines: standard range (DE2121-DL), long range (DE2121-ER) and extra-long-range XLR (DE2172). The product page states reading up to 20 m and a Green Spot visible up to 10 m; the data sheet specifies that these 10 m apply to the XLR engine. Target mode (Enable Target Mode) projects an aiming pattern before scanning, and its Half Trigger option enables the two-stage TrueAim trigger, designed according to Datalogic for faster and more accurate long-distance scanning.

Caution: According to the Datalogic data sheet, the Falcon X60/65 aimer uses a Class 2 laser diode (IEC/EN 60825-1).

What to do

1. Identify the scan engine: Datalogic Settings > Device > Device Information shows the engine (scan engine) in the detailed hardware information.
2. Open Datalogic Settings > Scanner & Decoder > Scanner Options, enable Enable Target Mode and choose Half Trigger: according to Datalogic, this mode enables the two-stage TrueAim trigger.
3. Enable Enhance DoF, which extends the maximum scanning distance.
4. Check that Enable Aim (laser aiming) and Enable Illumination (illumination) are enabled.
5. If scanning stops before it succeeds, increase Decode Timeout, the maximum decoding time.

Sources: Falcon X60/65: Handheld Mobile Computers – Datalogic (opens in a new window) – Datalogic Falcon X60/65 product page · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60/65: BUILT FOR HARD WORK, HEAVY INPUT & THE HIGHEST SHELVES - Datalogic (opens in a new window) – Datalogic press release of 18 June 2026 · Scanner Options | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Device Information | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) (official documentation).

Short answer: Enable the anti-reflection display mode: Datalogic Settings > Scanner & Decoder > Scanner Options > Display Mode. According to Datalogic, this setting optimises the reading of barcodes displayed on a screen.

Likely cause

The Datalogic knowledge base describes this setting for Datalogic Android mobile computers with a 2D scanner that need to read barcodes displayed on a PC screen or a monitor. The Datalogic Settings documentation calls it Display Mode (Antireflex).

What to do

1. Open Datalogic Settings.
2. Tap Scanner & Decoder, then Scanner Options.
3. Tap Display Mode and slide the switch to the enabled position.
4. Scan the barcode displayed on the screen again.

The Datalogic knowledge base article is common to Datalogic Android mobile computers with a 2D scanner; it does not mention the Falcon X60/65 by name.

Sources: Android Devices with 2D Scanner Reading Barcodes from Monitors (opens in a new window) – Datalogic knowledge base (Customer Self-Service), article KA-01715 · Scanner Options | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Enable Enable Picklist in Datalogic Settings > Scanner & Decoder > Scanner Options. According to Datalogic, the mobile computer then decodes only the targeted barcode when several barcodes are close together.

Likely cause

Datalogic provides the Enable Picklist setting for barcodes that are close together: it restricts decoding to the barcode you are aiming at. Multiple scan mode (Enable Multi Scan), on the other hand, captures several barcodes in succession.

What to do

1. Open Datalogic Settings > Scanner & Decoder > Scanner Options.
2. Enable Enable Picklist.
3. Check that Enable Aim is enabled so that you can see the aimer, and place it on the barcode you want.
4. If Enable Multi Scan is enabled although you only scan one barcode at a time, disable it, or check Number of Labels, the number of labels to be read for confirmation.

Source: Scanner Options | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Three settings trigger scanning without the trigger: the Always On scan mode, motion triggering (Motion Trigger Enable) and presentation mode (Presentation Mode). Set Scan Mode back to Single and disable any automatic triggering you do not need.

Likely cause

According to the Datalogic Settings documentation, Always On mode scans continuously without the trigger being pressed, Motion Trigger Enable starts scanning when the mobile computer moves quickly and Presentation Mode starts scanning when motion is detected.

What to do

1. Open Datalogic Settings > Scanner & Decoder > Scanner Options and set Scan Mode to Single: scanning stops as soon as a barcode is read, the trigger is released or the decoding timeout expires.
2. On the same page, under Partial Results, disable Presentation Mode if you do not use it.
3. Open Keyboard & Touch > Physical keyboard > Triggers and disable Motion Trigger Enable, or lower Motion Trigger Sensitivity (Sensitive, Intermediate or Dull).
4. Datalogic states that these settings can also be set by the SDK, OEMConfig or Scan2Deploy Studio: on a mobile computer managed by your IT department, check with the fleet administrator.

Sources: Scanner Options | Technical Documentation (opens in a new window) · Physical keyboard | Technical Documentation (opens in a new window) · Keyboard Wedge | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: The barcode is read but not sent to the application. In Datalogic Settings > Scanner & Decoder > Wedge, check that Enable keyboard wedge is enabled; if Keyboard wedge only on focus is enabled, tap the input field first. If your application receives barcodes by intent, it is the Intent Wedge settings that need checking.

Likely cause

According to Datalogic, the Keyboard Wedge sends the scanned data to the foreground application as keystrokes; if it is disabled, nothing is entered. With Keyboard wedge only on focus, the data only goes to the active text field. An application that listens to the scanner by intent depends on the Intent Wedge settings (action, category, data keys).

What to do

1. Open Datalogic Settings > Scanner & Decoder > Wedge.
2. Enable Enable keyboard wedge (enabled by default according to Datalogic).
3. If Keyboard wedge only on focus is enabled, place the cursor in the input field before scanning, or disable this setting to send the data to the foreground application.
4. If your application receives barcodes by intent, check the expected values with its publisher: Enable intent wedge, Intent action (by default com.datalogic.decodewedge.decode_action) and Intent category (by default com.datalogic.decodewedge.decode_category).
5. If the mobile computer does not beep either, the problem lies with scanning: see the scanner no longer scans entry.

Sources: Wedge | Technical Documentation (opens in a new window) · Keyboard Wedge | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Change the Keyboard Wedge input mode in Datalogic Settings > Scanner & Decoder > Wedge > Keyboard wedge input mode: Text Injection, Key Pressure or Commit Text. Also check on the Formatting page that no prefix or symbology identifier is added.

Likely cause

Datalogic offers three input modes: Text Injection (the barcode is injected into the field; default mode), Key Pressure (the barcode is converted into keystrokes) and Commit Text (text injected for printable characters, simulated keystrokes for the others). The formatting settings also change the data sent: prefix, suffix, code identifier (Send code ID), replacement of the GS separator or removal of non-printable characters.

What to do

1. Open Datalogic Settings > Scanner & Decoder > Wedge and try each of the Keyboard wedge input mode modes in turn.
2. In Text Injection or Commit Text mode, if non-printable characters (tab, carriage return) are lost, increase Non-printable key event delay, the delay applied before and after each of these characters.
3. Open Scanner & Decoder > Formatting and check Label prefix, Label suffix and Send code ID (set it to None if the application does not expect an identifier).
4. For GS1 barcodes, check Group Separator replacement and Remove non-printable characters, which change or remove the GS separator.
5. If the characters typed on the physical keypad are also wrong, see the physical keypad entry.

Sources: Wedge | Technical Documentation (opens in a new window) · Keyboard Wedge | Technical Documentation (opens in a new window) · Formatting | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Add a suffix: Datalogic Settings > Scanner & Decoder > Formatting > Label suffix, then Add special, and choose the character the application expects (CR, LF or TAB). The Keyboard Wedge's IME action after sending data setting can also send a confirmation action.

Likely cause

According to Datalogic, the suffix (Label suffix) is the text sent after the last character of the barcode; it can contain non-printable characters added with Add special (CR, LF, TAB…). The IME action after sending data setting also sends an action to the virtual keyboard after the data (GO, SEARCH, SEND, NEXT, DONE…).

What to do

1. Open Datalogic Settings > Scanner & Decoder > Formatting.
2. Tap Label suffix, then Add special, and select the expected character: CR (carriage return), LF (line feed) or TAB (tab).
3. If the application responds to keyboard actions rather than to a character, open Scanner & Decoder > Wedge and set IME action after sending data, for example to IME_ACTION_DONE or IME_ACTION_NEXT.
4. Scan a test barcode in the application to check the result.

Sources: Formatting | Technical Documentation (opens in a new window) · Wedge | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Datalogic recommends testing the roaming profiles (Wi-Fi Roaming > Roaming Profile: Slow, Legacy or Aggressive), restricting the mobile computer to the bands used by your access points (Wi-Fi Module > Band Selection) and checking that the firmware is up to date.

Likely cause

According to the Datalogic knowledge base, Datalogic Android mobile computers may switch slowly from one access point to another or lose the connection intermittently; roaming depends on the access point configuration, the signal level, the channel plan and the wireless infrastructure.

What to do

1. Open Settings > DL Settings > Wi-Fi > Wi-Fi Roaming > Roaming Profile and compare the profiles: Slow (less aggressive), Legacy (older networks) and Aggressive (switches faster to a stronger access point).
2. The Custom profile lets you set RSSI Threshold (signal level at which the mobile computer looks for another access point) and RSSI Difference (signal difference needed to change access point).
3. In Wi-Fi Module > Band selection, keep only the bands used by your access points: 2.4 GHz, 5 GHz or 6 GHz. Datalogic specifies that the 6 GHz band is only available on Wi-Fi 6E and Wi-Fi 7 mobile computers; the Falcon X60/65 has Wi-Fi 6E.
4. If the dropouts affect a latency-sensitive application, test with Power save disabled: according to Datalogic, this mode saves battery but can reduce throughput and increase latency.
5. Note the build number of each affected mobile computer (Datalogic Settings > Device > Device Information) and install the latest firmware, which may contain Wi-Fi fixes (see firmware update).
6. For a diagnosis by your network team, Verbose logging (Wi-Fi Module) increases the level of detail of the Wi-Fi logs.

The Datalogic knowledge base article is common to Datalogic Android mobile computers; it mentions the Memor 11 for the roaming profiles.

Sources: Improving Wi-Fi Roaming Performance on Android Devices (opens in a new window) – Datalogic knowledge base (Customer Self-Service), article KA-01770 · Wi-Fi Roaming | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Wi-Fi Module | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Device Information | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet (official documentation).

Short answer: The Falcon X60 is a Wi-Fi 6E mobile computer with no mobile network: only the Falcon X65 version has built-in 5G. On an X65, 5G and LTE are for data only according to the data sheet, and the SIM card is selected in Datalogic Settings > Dual SIM.

Likely cause

According to Datalogic, the Falcon X60 has Wi-Fi 6E and the Falcon X65 has Wi-Fi 6E + 5G. The data sheet specifies “data only” for the 5G NR FR1 and LTE on the X65, which also adds GPS and a barometer.

What to do

1. Check the model: Falcon X60 part numbers start with 946600, Falcon X65 part numbers with 946650. The part number is shown in Datalogic Settings > Device > Device Information.
2. On a Falcon X60, use Wi-Fi: the model has no mobile modem.
3. On a Falcon X65, open Datalogic Settings > Dual SIM to choose the SIM card and set the SIMs used by default.

The Datalogic pages consulted do not describe how to install the SIM card in the Falcon X65.

Sources: Falcon X60/65: Handheld Mobile Computers – Datalogic (opens in a new window) – Datalogic Falcon X60/65 product page · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) · Dual SIM | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Device Information | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: The mobile computer must be in file transfer mode (File Transfer (MTP)). Change the mode from the notification panel while connected, or set USB function to MTP in Datalogic Settings > USB, with USB client data enabled.

Likely cause

According to Datalogic, the behaviour of an Android mobile computer connected by USB (charging only, file transfer, tethering…) depends on the USB mode chosen. Datalogic Settings offers USB function (None, MTP, PTP, RNDIS, MIDI) and USB client data, which enables or disables USB communication when the mobile computer is connected to a computer.

What to do

1. Connect the mobile computer to the computer, open the notification panel and choose the file transfer mode.
2. If the setting does not stick, open Datalogic Settings > USB: enable USB client data and set USB function to MTP.
3. To change the default mode: enable the developer options (Settings > About phone, tap Build number seven times), then open Settings > System > Developer options, Networking section, Default USB configuration, and choose File Transfer (MTP).
4. On a managed mobile computer, the developer options may be blocked by the fleet management policy: check with the administrator.

The Datalogic knowledge base article is common to Datalogic Android mobile computers and specifies that the steps may vary depending on the Android version.

Sources: Changing the Default USB Connection Setting on Android Devices (opens in a new window) – Datalogic knowledge base (Customer Self-Service), article KA-01610 · Overview | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), USB section (official documentation).

Short answer: First check the battery health in the Battery Manager application. Then reduce the sleep timeouts (Datalogic Settings > Power & sources) and, on a managed fleet, use Enterprise Battery Saver, which Datalogic states is compatible with the Falcon X60 running Android 15.

Likely cause

The Falcon X60/65 battery is rated at 7,000 mAh (25.445 Wh) in the data sheet. Datalogic provides several levers: the sleep timeout on battery, the Wi-Fi power-saving mode and the Enterprise Battery Saver profiles, which can limit the CPU and GPU frequency and the brightness, and switch off certain radios according to triggers (battery level, time slot, power source, connection…).

What to do

1. Open Battery Manager and look at Battery Info: Health reports potential errors and State of Health gives the level of health (see battery health).
2. In Settings > Datalogic Settings > Power & sources, reduce Internal battery, the inactivity timeout before sleep on battery (in seconds); also set Settings > Display > Screen timeout.
3. If your applications allow it, enable Power save in Wi-Fi Module: Datalogic states that it saves battery at the cost of lower throughput and higher latency.
4. On a fleet, create an Enterprise Battery Saver profile (Battery Manager from v2.17.0, Battery Management menu in Datalogic Settings, Scan2Deploy Studio or OEMConfig): CPU frequency limit and GPU frequency limit limits (None, Intermediate or Aggressive), Use power-save governor, disabling radios, with a trigger such as Battery level or Time interval.
5. For long days, have a spare battery (94ACC0440): according to the data sheet, the Falcon X60/65 battery can be hot-swapped with application data protection.

The Datalogic Enterprise Battery Saver and Smart Charge pages mention the Falcon X60 (Android 15, all versions); the Falcon X65 is not named there.

Sources: Battery Manager | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Battery Info | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Suspend Timeout | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Wi-Fi Module | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Enterprise Battery Saver | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) (official documentation).

Short answer: Open the Battery Manager application, then Battery Info: the Lifetime section shows Health (with warnings in case of a potential error) and State of Health. If the health has deteriorated, replace the battery with the Datalogic 94ACC0440 battery.

Likely cause

Datalogic provides Battery Manager, pre-installed on compatible mobile computers, to monitor the battery: real-time status (Status, Source, Temperature, Voltage, Current) and history (Health, State of Health, Total Discharge, extreme temperatures and voltages reached).

Caution: According to the Datalogic data sheet, the Falcon X60/65 operates between -20 and 50 °C. The pages consulted do not give the charging temperature range: refer to the Datalogic user manual for the Falcon X60/65.

What to do

1. Tap All Apps, then the Battery Manager icon.
2. Open the menu (icon at the top left, or swipe right) and choose Battery Info.
3. In the Lifetime section, read Health and State of Health, as well as the maximum and minimum temperatures reached by the battery.
4. In the Manufacturer section, note the serial number and the date of manufacture of the battery if you need to report it.
5. Replace a deteriorated battery with the Datalogic 94ACC0440 battery. The 94ACC0274 4-slot charger (with the 91ACC0048 power supply) recharges spare batteries outside the mobile computer.

Sources: Battery Manager | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Battery Info | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet (official documentation).

Short answer: Check whether Smart Charge or a battery-lifetime charging profile is active. According to Datalogic, Smart Charge avoids keeping the battery at 100% for too long and times the full charge to the work schedule; the charging profile is set in Battery Management > Charging Policies.

Likely cause

Datalogic explains that keeping a battery at 100% for long periods exposes it to high voltage and heat, which shorten its life. Smart Charge (Battery Manager v2.17.0 and later, compatible with the Falcon X60 running Android 15) therefore sets the work schedule and the discharge time so that the battery only reaches full charge when a shift needs it. The Battery Charging Profile setting offers six profiles, some of which favour battery life.

What to do

1. Open Datalogic Settings > Battery Management > Charging Policies.
2. Look at Battery Charging Profile: Charging Speed, Maximum Capacity, Maximum Capacity + Charging Speed, Battery Lifetime, Battery Lifetime + Charging Speed or Battery Lifetime + Maximum Capacity. Choose a “Maximum Capacity” profile if you need the full capacity.
3. Check Battery Charging Profile Policy: the profile is saved either in the mobile computer (Persistence set by device) or in the battery (Persistence set by battery).
4. If Smart Charge is used, check the configured work schedule with the administrator: Datalogic states that it is set through Scan2Deploy Studio or OEMConfig.
5. If the mobile computer does not charge at all, see the charging in the cradle entry.

Sources: Charging Policies | Technical Documentation (opens in a new window) · Smart Charge | Technical Documentation (opens in a new window) · Battery Manager | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).

Short answer: Check that the cradle is powered by the specified power supply (94ACC0380 for the 4-slot cradles, 91ACC0048 for the single cradle) with the mains cord for your country. Then open the Dock Manager application: Dock Status should show Ready and not Error.

Likely cause

According to the Datalogic accessories list, each Falcon X60/65 cradle requires a power supply and a mains cord sold separately. Dock Manager, compatible with the Falcon X60/65 running Android 15, shows the cradle status (Ready or Error), the fast charging status (Fast Charge Status, enabled by default and disabled when cradles are daisy-chained) and the last occurrence of each fault per slot.

What to do

1. Check the power supply: 94ACC0380 for the 4-slot charge-only cradle (94A150143) and for the 4-slot charge and Ethernet data cradle (94A150144); 91ACC0048 for the single cradle with contacts (94A150151). Each cradle also requires a mains cord suited to the country.
2. On a 4-slot cradle, if the mobile computer does not have a protective cover (rubber boot), use the adapters supplied with the cradle.
3. Place the mobile computer in the cradle and open Dock Manager: check Dock Status (Ready or Error) and Fast Charge Status. Datalogic states that fast charging is disabled when cradles are daisy-chained.
4. In the Dock Manager menu, Get Slot Failure shows the last occurrence of each type of fault for the slot.
5. If Datalogic publishes a cradle update, install it from Dock Manager: place the file in the mobile computer's Download folder, open the menu at the top right > Firmware Update, choose the package in Downloads, then tap UPDATE (or UPDATE ALL).
6. For a switched-off mobile computer placed on charge, the Off-Mode Charge setting (Battery Management > Charging Policies) determines whether it switches back on automatically and at what threshold.

When to call a technician: Dock Manager still shows Error with a compliant power supply: the Datalogic product page refers you to Datalogic technical support and repair service.

According to the data sheet, the Falcon X60/65 is also compatible with Qi EPP wireless charging (10 W); the pages consulted do not give details of its use.

Sources: Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) · Dock Manager | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Get Slot Failure | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Firmware Update | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Dock Manager · Charging Policies | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60/65: Handheld Mobile Computers – Datalogic (opens in a new window) – Datalogic Falcon X60/65 product page (official documentation).

Short answer: Tap the failed step to display the reason, then view the log with Previous Log. Have the profile recreated with Scan2Deploy Studio 2.7.0 or later, the version that added the Falcon X60/X65, and scan all the barcodes of the same profile without mixing two profiles.

Likely cause

According to Datalogic, the Scan2Deploy agent shows a Pass, Fail, Warning or Progress status for each step. Fail means that the step did not complete and that applying the profile stopped at that step; Warning indicates a step completed with non-blocking problems. If a barcode from another profile is read during the sequence, the initial profile is abandoned without being applied. Scan2Deploy Studio has supported the Falcon X60/X65 since version 2.7.0 (12 June 2026).

What to do

1. On the mobile computer, tap the step marked Fail to display the details and the reason for the failure.
2. Tap Previous Log to review the log of the last session. The files /sdcard/Download/S2DStatus.log (status of the last session) and /sdcard/Download/S2DLog.txt (recent history, with the content of the barcodes read) can be sent to your administrator.
3. If the profile has several barcodes, scan them all without reading a barcode from another profile: each barcode read turns green and the profile is applied once all the barcodes have been read.
4. Have the profile recreated with Scan2Deploy Studio 2.7.0 or later, which supports the Falcon X60/X65 and its keypad layouts.
5. For an update profile, check that the OTA file matches the model and the Android version chosen in Scan2Deploy Studio.

According to Datalogic, the Scan2Deploy agent is present on recent Datalogic Android mobile computers (Android 9 and later) and Scan2Deploy Studio requires version 1.11 or later of the agent.

Sources: Scan2Deploy Agent | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Blog | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), release notes (Scan2Deploy Studio 2.7.0) · Scan2Deploy Studio | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Firmware Update Page | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Scan2Deploy Studio · Frequently Asked Questions | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Scan2Deploy Studio (official documentation).

Short answer: Open Datalogic Settings and tap Reset device configuration, at the bottom of the main screen: according to Datalogic, all Datalogic settings return to their factory values. To reset just one page (scanner, Wi-Fi…), tap Reset configuration at the bottom of that page.

Likely cause

Datalogic Settings groups together the settings specific to the mobile computer: scanner and decoding, keypad and touch, power, battery, cradle, Wi-Fi, USB. Datalogic provides two levels of reset: the whole device (Reset device configuration) or a single screen (Reset configuration). Targeted resets also exist for symbologies, remapped keys and the custom keyboard.

Caution: This reset applies to the Datalogic settings. For a full reset of the mobile computer (return to factory defaults), follow the Datalogic user manual for the Falcon X60/65, published on the Datalogic developer portal, and back up your data before you start.

Step by step

1. Note down the custom settings you will need afterwards (wedge, suffix, Wi-Fi profile…).
2. For one page only: open the page concerned in Datalogic Settings (for example Scanner & Decoder > Scanner Options) and tap Reset configuration at the bottom of the screen.
3. For symbologies: Scanner & Decoder > Symbologies Configuration > Reset symbologies configuration.
4. For keys: Keyboard & Touch > Key Remapping > Key Mapping Reset; for a custom keyboard: Physical keyboard > Custom Keyboard > Reset Configuration.
5. For the whole device: scroll to the bottom of the Datalogic Settings main screen and tap Reset device configuration.
6. Datalogic states that these settings can also be imposed by the SDK, OEMConfig or Scan2Deploy Studio: on a managed mobile computer, check with the fleet administrator before resetting.

In a Scan2Deploy Studio update profile, the Reset Type field is set to None by default.

Sources: Datalogic Settings | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Symbologies Configuration | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Key Remapping | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Physical keyboard | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Keyboard Wedge | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Frequently Asked Questions | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Scan2Deploy Studio · Falcon X60/65 - Android - Technical-docs - Products - Datalogic Developer Portal (opens in a new window) – Datalogic developer portal (official documentation).

Short answer: According to Datalogic, the firmware for Android mobile computers is downloaded from the Datalogic developer portal, after logging in, by entering the mobile computer's serial number; downloading is restricted to mobile computers covered by an active Datalogic Shield contract. Back up the mobile computer and keep it charged or on mains power during the update.

Likely cause

The Datalogic knowledge base states that firmware downloads are restricted to mobile computers with an active Datalogic Shield service contract. For the Falcon X60/65, the developer portal publishes Android 15 versions (v3.25.014 of 13/10/2026, v3.25.011, v3.25.009), as full or incremental packages, with or without Google services (GMS and non-GMS), as well as the Espresso Extension v3.25.001.

Caution: According to Datalogic, a firmware update may reset the mobile computer's settings depending on the method used: back up before you start.

What to do

1. Note the serial number and build number of the mobile computer: Datalogic Settings > Device > Device Information.
2. On a PC, open the Datalogic developer portal (Mobile Computers section), create an account or log in, then choose Products > Falcon X60/65 > Firmware.
3. Choose the package that matches the mobile computer: GMS or non-GMS, full or incremental from your current version. Read the release notes (fixes, security patches, new features).
4. Enter the serial number when prompted: if the Shield contract is active, the download starts.
5. Back up the mobile computer, then install the package following the instructions supplied with the firmware; Datalogic mentions DXU, Recovery mode or ADB. For a fleet, Scan2Deploy Studio also creates update profiles (System Update) from the OTA file.
6. Keep the mobile computer charged or plugged in throughout the update.
7. If an application (SureFox or SureLock, for example) requires it, install the Espresso Extension, developed by Datalogic and certified by Google.

When to call a technician: the portal refuses the download because there is no active Datalogic Shield contract: Datalogic states that a Shield licence may then be required.

Datalogic announces monthly Android security updates and up to 10 years of operating system support for the Falcon X60/65; the data sheet states a platform upgradable to Android 19.

Sources: How to Download and Install New Firmware on a Datalogic Android Device (opens in a new window) – Datalogic knowledge base (Customer Self-Service), article KA-01096 · Firmware Update Process for Android Mobile Computers (opens in a new window) – Datalogic knowledge base (Customer Self-Service), article KA-01558 · Falcon X60/65 - Android - Firmware - Products - Datalogic Developer Portal (opens in a new window) – Datalogic developer portal · Device Information | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Frequently Asked Questions | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Scan2Deploy Studio · Firmware Update Page | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), Scan2Deploy Studio · Falcon X60/65: BUILT FOR HARD WORK, HEAVY INPUT & THE HIGHEST SHELVES - Datalogic (opens in a new window) – Datalogic press release of 18 June 2026 · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet (official documentation).

Short answer: Open Datalogic Settings > Keyboard & Touch > Physical keyboard. Check the keyboard layout (Layout policy and Layout, for example fr-FR) and that Lock Keyboard Input is not enabled. If keys have been remapped, Key Mapping Reset restores the original keys.

Likely cause

According to Datalogic, the physical keypad layout depends on Layout policy: Default (layout chosen by the system), Automatic (based on the language or region) or Custom (layout defined in Layout, which accepts a language code such as fr or fr-FR). Lock Keyboard Input blocks keypad input. Key remapping (Key Remapping) or an installed custom keyboard also changes what a key produces.

What to do

1. Open Datalogic Settings > Keyboard & Touch > Physical keyboard.
2. If the keys do not respond, disable Lock Keyboard Input.
3. If the characters do not match the keys, set Layout policy to Automatic, or to Custom with Layout = fr-FR.
4. If a key produces something other than expected, open Keyboard & Touch > Key Remapping: View All Remapped Keys lists the remappings and Key Mapping Reset removes them all.
5. If a custom keyboard has been installed, Custom Keyboard > Reset Configuration restores the default keyboard.
6. If the keypad overlay is worn, Datalogic sells replacement keypad overlays for each version: 94ACC0459 (31 keys), 94ACC0460 (41 keys) and 94ACC0458 (53 keys).

The Falcon X60/65 is available with three backlit keypads: 31-key numeric, 41-key numeric with functions and 53-key alphanumeric (Datalogic data sheet). Scan2Deploy Studio 2.7.0 added the Falcon X60/X65 keypad layouts.

Sources: Physical keyboard | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Key Remapping | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · Falcon X60-X65 (opens in a new window) – Datalogic list of models and accessories (Models & Accessories) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Blog | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io), release notes (Scan2Deploy Studio 2.7.0) (official documentation).

Short answer: Adjust the screen sensitivity: Datalogic Settings > Keyboard & Touch > Touch > Touch mode > Screen sensitivity. According to Datalogic, this setting adapts the screen to a bare finger, a gloved finger, a stylus or a wet screen.

Likely cause

According to the Datalogic data sheet, the Falcon X60/65's 4.3-inch capacitive touch screen (Corning Gorilla Glass Victus) accepts gloves and a stylus. The sensitivity mode is chosen in Datalogic Settings according to use.

What to do

1. Open Datalogic Settings > Keyboard & Touch > Touch.
2. Tap Touch mode > Screen sensitivity and choose the mode that matches your use: bare finger, gloved finger, stylus or wet screen.
3. For frequent input with gloves, use the physical keypad: Datalogic states that its keys (up to 53) can be used with gloves.

Sources: Touch | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) · FALCON X60-X65 – Technical Specifications (DS-FALCONX60-X65-EN Rev A) – Datalogic Falcon X60-X65 data sheet · Falcon X60/65: Handheld Mobile Computers – Datalogic (opens in a new window) – Datalogic Falcon X60/65 product page (official documentation).

Short answer: Open Datalogic Settings > Power & Sources > Wake-Up Policies and check the wake-up sources (Wake-up sources). According to Datalogic, by default, the side triggers, the pistol trigger, the front trigger and the PTT key wake up the mobile computer.

Likely cause

A wake-up source disabled in Wake-up sources no longer wakes the mobile computer from sleep. The Physical Trigger active in suspend setting of the physical keypad also defines which triggers remain active during sleep.

What to do

1. Open Datalogic Settings > Power & Sources > Wake-Up Policies.
2. Tap Wake-up sources and re-enable the trigger concerned (side, pistol, front) or the PTT key.
3. Open Keyboard & Touch > Physical keyboard > Triggers and check Physical Trigger active in suspend.
4. If the mobile computer goes to sleep too quickly, increase the Power & sources timeouts: Internal battery (on battery) and External power (on mains, USB or cradle), in seconds.

Sources: Wake-Up Policies | Technical Documentation (opens in a new window) · Physical keyboard | Technical Documentation (opens in a new window) · Suspend Timeout | Technical Documentation (opens in a new window) – Datalogic technical documentation (datalogic.github.io) (official documentation).