- Fix USB mode, Android permissions, MTP conflicts, and ignored-device settings.
- Use calibre detection logs to isolate USB and operating-system failures.
- Switch to the Content server when wireless delivery is more reliable.
- Confirm the Symptom With a Small Safe Test
- Check the calibre Settings Directly Related to Detection
- Check USB Mode, Permissions, and MTP Behavior
- Use Wireless and Folder-Based Alternatives When Appropriate
- Read calibre's Detection and Job Details
- Run a Clean Temporary Test Before Reinstalling
- Quick Fix Checklist
- Frequently Asked Questions
When a phone, tablet, or Kindle Fire charges over USB but does not appear in calibre, the cause is usually not a damaged calibre library. The failure is more often caused by the USB connection remaining in charging mode, an unanswered Android permission prompt, another application holding the MTP connection, an ignored device setting, or an operating system that cannot communicate with the device. Work through the checks below in order. After each change, look for the Device button in calibre and stop troubleshooting as soon as it appears.

Start with free Canva bundles
Browse the freebies page to claim ready-to-use Canva bundles, then get 25% off your first premium bundle after you sign up.
Free to claim. Canva-ready. Instant access.
1. Confirm the Symptom With a Small Safe Test
Begin by separating device detection from book-transfer problems. calibre cannot send a book through its normal device workflow until it recognizes the connected device. If a Device button does not appear on the main toolbar, troubleshoot the USB or wireless connection before changing metadata, conversion, or library settings.
1.1 Test With One Device and One Book
- Close any conversion, metadata download, or news download jobs in calibre.
- Disconnect other phones, tablets, cameras, e-readers, and removable storage devices.
- Unlock the Android device and keep its screen awake.
- Connect it directly to the computer with a known data-capable USB cable.
- Select File transfer or MTP on the device when prompted.
- Approve any prompt asking whether the computer may access device data.
- Start or restart calibre and wait briefly for the Device button.
Success means the Device button appears in calibre and opens a list of files found on the device. Select one small, non-DRM test book that you are legally entitled to transfer, then click Send to device. If the job completes and the book appears in the intended reading app or storage folder, stop changing settings.
1.2 Identify Which Layer Is Failing
- No USB notification appears: Suspect the cable, port, device connector, or operating system.
- The device only says charging: Change the USB mode to File transfer or MTP.
- The computer sees the device but calibre does not: Check competing MTP applications, ignored devices, plugins, and detection logs.
- calibre detects the device but cannot send a book: Check storage space, destination access, supported formats, and the individual job error.
- The book transfers but is absent from the reading app: Check the app's import behavior, supported formats, and watched folders.
This classification prevents unnecessary changes. A metadata source, conversion profile, or viewer preference cannot normally make the Device button disappear.
2. Check the calibre Settings Directly Related to Detection
2.1 Make Sure the Device Is Not Ignored
Open Preferences and look for the Ignored Devices section. If the connected Android device is listed, remove it from the ignored list, apply the change, disconnect the cable, and restart calibre. Reconnect only after unlocking the device and selecting File transfer.
Success means calibre adds a Device button to its toolbar. If that happens, do not reset unrelated preferences or reinstall calibre.
2.2 Check Device Plugins Without Randomly Disabling Them
calibre uses device plugins to identify supported hardware and choose appropriate transfer behavior. Open Preferences, select Plugins, and inspect the Device interface plugins category. A built-in plugin required for the device should not be disabled.
If you recently installed a third-party device plugin and detection stopped afterward, temporarily disable only that plugin and restart calibre. Avoid disabling multiple plugins at once because doing so makes it difficult to identify the cause. Re-enable the plugin if its removal makes no difference.
The User defined device plugin is intended for unusual devices that appear to the operating system as conventional disk storage. It is not a universal replacement for Android MTP support. In Windows, a user-defined disk device generally needs an assigned drive letter.
2.3 Distinguish Library Problems From Device Problems
A damaged or inaccessible library can stop calibre from opening books, editing metadata, or completing transfers, but it does not usually explain why an Android device is entirely absent. Confirm that you can open a known-good book in calibre's viewer and use Save to disk to place a copy in a temporary folder on the computer.
If Save to disk works, the library record and source file are probably usable. Continue with USB detection. If it fails, test another book before repairing the database or modifying the library folder.
2.4 Check the Format Before Sending
Detection and format compatibility are separate issues. Once the device is visible, verify that the destination reading application supports the selected book format. EPUB is widely supported by Android reading applications, while PDF support is common but offers limited text reflow. Kindle apps and Fire devices may have different import and library-display behavior depending on the file type and app.
Use Send specific format to when a calibre book record contains several formats. Convert a copy only when the reading application does not support the available format. Conversion will not fix a missing Device button.
2.5 Avoid Irrelevant Settings Changes
Metadata download sources, email accounts, news recipes, viewer preferences, and editor settings do not control basic USB recognition. Email sharing and the Content server can provide alternative delivery methods, but changing those settings will not repair MTP detection. Concentrate on the connection path that is actually failing.
3. Check USB Mode, Permissions, and MTP Behavior
3.1 Select File Transfer Instead of Charging
Many Android devices default to charging when connected. Unlock the device, swipe down to open notifications, and tap the USB notification. Its wording varies, but it commonly mentions charging through USB. Under the available USB uses, select File transfer, Transferring files, or MTP.
Keep the screen unlocked while the connection is established. Newer Android security controls can prevent a data connection from starting while the device is locked, even though charging continues normally.
After selecting File transfer, approve any request to permit access to device data. Restart calibre if it was already open when you changed the USB mode. Success means the Device button appears and the status area indicates that calibre is examining or communicating with the device.
3.2 Test the Cable and Port Correctly
A cable can provide power without carrying data. If no file-transfer option appears, replace the cable with one known to transfer files. Connect directly to the computer rather than through a monitor, keyboard, unpowered hub, or docking station during testing.
Try another USB port, then test the same phone and cable on another computer if possible. Conversely, test another data device on the original computer. These comparisons identify whether the failure follows the phone, cable, port, or computer.
3.3 Understand MTP on Windows
On Windows, confirm that the unlocked device appears in File Explorer after File transfer is selected. It may appear as a portable device rather than as a drive with a letter. Open it and confirm that internal storage can be viewed.
If Windows cannot browse the device, calibre is unlikely to detect it. Disconnect the device, restart both systems, reconnect, and watch for Windows hardware or driver errors. Windows Update or the device manufacturer's official support tools may provide an appropriate driver when Windows cannot establish MTP communication.
If File Explorer can browse the device but calibre cannot detect it, close windows displaying the device, restart calibre, check Ignored Devices, and run calibre's Debug device detection tool.
3.4 Understand MTP on macOS and Linux
Android devices normally expose files through MTP rather than behaving like ordinary mounted USB disks. On macOS and Linux, only one application may be able to control the Android MTP connection at a time. Close file managers, phone-integration utilities, media applications, Android transfer tools, and any other program currently browsing the device. Then disconnect the cable, restart calibre, reconnect the unlocked device, and approve the permission prompt.
On macOS, also review the system's Privacy and Security settings if calibre reports a permission error. Grant only the file or removable-volume access required for the workflow, then reopen calibre.
On Linux, confirm that the desktop or MTP subsystem can see the device. If a file manager automatically opens it, close the window and fully release or unmount the connection before asking calibre to connect. Do not run calibre as root as a routine workaround because that can create ownership problems in the library and configuration folders.
3.5 Handle Kindle Fire Data Mode
A Kindle Fire is Android-based, but its USB notification and storage behavior can differ from those of other tablets. When the cable is attached, tap the charging or USB icon and change the connection to data transfer or file transfer. Start or restart calibre after making that selection.
This article concerns Fire tablets, not dedicated Kindle e-ink readers. Kindle e-ink USB behavior, supported formats, and newer model restrictions require a separate troubleshooting path.
3.6 Account for Newer Android Restrictions
Newer Android devices may require the screen to be unlocked before the USB data session begins. Some phones also display a fresh approval prompt whenever an application attempts to access storage. Managed work profiles, organization policies, manufacturer security tools, and advanced USB protection can further restrict access.
If the device is managed by an employer or school, do not attempt to circumvent its policies. Ask the administrator whether USB file transfer is permitted, or use an approved wireless method.

4. Use Wireless and Folder-Based Alternatives When Appropriate
4.1 Use the Content Server on the Same Network
The calibre Content server is usually the cleanest wireless alternative when Android USB detection remains unreliable. It lets a phone, tablet, or Fire device browse the calibre library through a web browser and download an available book format.
- Connect the computer and Android device to the same trusted local network.
- In calibre, open Connect/share and choose Start Content server.
- If the operating system firewall asks whether calibre may accept connections, allow it on the appropriate private network.
- Open Connect/share again and note the displayed local IP address and port.
- Enter that address in the Android browser.
- Select a book and choose an available reading or download option.
Test the server on the calibre computer first by opening the local address shown in the server documentation or interface. If it works locally but not on Android, check whether both devices are on the same network, whether guest Wi-Fi blocks communication between devices, and whether a firewall or antivirus product is blocking calibre's server port.
Success means the calibre library opens in the Android browser and a test book can be downloaded. At that point, USB detection is optional unless you specifically need calibre's direct device-management features.
4.2 Use Connect to Folder Only When a Real Folder Is Available
Connect to folder allows calibre to treat a selected computer folder like a device. It is useful when the target storage is exposed as a normal writable folder or USB disk, or when another approved synchronization method carries files from that folder to the Android device.
It does not turn an inaccessible MTP device into a conventional disk. If the operating system does not expose a usable folder path, use the Content server, Save to disk, or another supported transfer workflow instead.
4.3 Avoid Cloud-Sync Conflicts
If you save books into a cloud-synchronized staging folder, wait until synchronization completes before opening them on the device. Do not place the live calibre library itself in a general-purpose sync folder while calibre is actively using it, because simultaneous changes can damage or conflict with library files.
For a safe test, use a separate temporary export folder. Save one book there, allow it to synchronize, and open the resulting copy on Android. If that succeeds, the wireless delivery path works independently of USB detection.
5. Read calibre's Detection and Job Details
5.1 Run Debug Device Detection
If the operating system can access the Android device in file-transfer mode but calibre still does not show a Device button, open Preferences, choose Miscellaneous, and click Debug device detection. Run the test with the device unlocked, connected, approved, and set to MTP or File transfer.
Save the output without editing it. For a useful comparison, repeat the test with the device disconnected. The connected output should show that calibre or the operating system discovered USB or MTP information that is absent from the disconnected output.
If the connected and disconnected results are effectively identical, the problem is probably below calibre, such as the cable, USB mode, permission, MTP service, or operating-system driver. If the device appears in the debug output but is ignored or rejected, review the listed reason, the ignored-device setting, and relevant device plugins.
5.2 Inspect the Failed Transfer Job
If detection works but Send to device fails, click Jobs in calibre and open the details for the failed operation. Read the final error lines first. Common categories include unavailable storage, a disconnected device, a read-only destination, an unsupported path, insufficient space, or a file that could not be converted.
Do not assume that every send failure is a detection failure. If the Device button remains visible and calibre can list device contents, focus on the transfer error rather than repeating cable tests.
5.3 Separate Conversion Debugging From Connection Debugging
When calibre reports that conversion failed before sending, retry the conversion without the device. Use a known-good source file and examine the conversion job details or conversion debug output. A malformed source book can fail even when USB communication is perfect.
If a converted copy saves successfully to the computer, send that specific format to the device. If conversion fails for only one title, stop changing global device settings and repair or replace the source file through a lawful source.
5.4 Report a Reproducible Detection Failure
If USB should work and every local check passes, prepare a concise report containing the operating system, Android or Fire device model, selected USB mode, whether the operating system can browse storage, and debug detection outputs captured with the device connected and disconnected. Remove personal file names or other sensitive details before sharing logs publicly.
6. Run a Clean Temporary Test Before Reinstalling
Reinstalling calibre rarely repairs a phone that is still in charging mode or blocked by another MTP application. A controlled test is faster and preserves your working library.
- Back up important data, but do not delete or move the existing calibre library.
- Close calibre and every application that may access the Android device.
- Restart the computer and Android device.
- Use one known data-capable cable and a direct USB port.
- Unlock the Android device before connecting it.
- Select File transfer or MTP and approve access.
- Open calibre with the normal library and check for the Device button.
- If detected, send one small supported book format.
- If direct USB still fails, start the Content server and test one wireless download.
If wireless delivery works, the library and book are usable, and the unresolved problem is limited to the USB or MTP path. If neither USB nor the Content server works, troubleshoot them separately because one depends on USB and the other depends on local networking.
A clean test is complete when one book reaches the device and opens in the intended reading application. Once that happens, stop changing settings and reintroduce other cables, hubs, plugins, or automation tools one at a time.
7. Quick Fix Checklist
- Unlock the Android or Fire device before connecting it.
- Use a USB cable known to carry data, not only power.
- Select File transfer, data transfer, or MTP from the USB notification.
- Approve the prompt allowing the computer to access device data.
- Connect directly to the computer and remove other portable devices.
- Close file managers and transfer utilities that may own the MTP connection.
- Restart calibre after changing the device's USB mode.
- Check Preferences for an entry under Ignored Devices.
- Confirm that the operating system can communicate with the device.
- Verify that the reading app supports the book's format.
- Use Debug device detection when USB should be working.
- Use the Content server when wireless delivery is more reliable.
- Use Connect to folder only with a real, writable folder or disk path.
- Test one small, lawful, non-DRM book before transferring a large collection.
8. Frequently Asked Questions
8.1 Why Does My Android Phone Charge but Not Appear in calibre?
The connection is probably in charging mode, the cable may not support data, or the device is waiting for permission. Unlock the phone, tap its USB notification, choose File transfer or MTP, approve access, and restart calibre. If no transfer option appears, test another cable and USB port.
8.2 Why Can Windows See My Phone While calibre Cannot?
First close File Explorer windows and other phone-management applications, then restart calibre. Check Preferences for ignored devices and disabled device plugins. If the Device button remains absent, run Debug device detection while the phone is unlocked and connected in File transfer mode.
8.3 Why Is Android Detection Different on macOS or Linux?
Android usually uses MTP instead of mounting as an ordinary disk. On macOS and Linux, another file manager or transfer program may already control that MTP session. Close competing applications, release the device connection, and let calibre connect first.
8.4 Can I Send Books Without Fixing USB Detection?
Yes. Start calibre's Content server and access it from the Android browser while both devices are on the same trusted network. You can browse the library and download a compatible format. Save to disk and a separate synchronization folder can also work when used carefully.
8.5 Why Did the Book Transfer but Not Appear in My Reading App?
The app may not support the file format, may not scan the destination folder automatically, or may require a manual import. Confirm the file exists on the device, verify the app's supported formats, and use its Open or Import command. This is no longer a device-detection problem if calibre completed the transfer successfully.
8.6 Should I Reinstall calibre or Delete My Library?
Not as an early step. Neither action fixes charging-only USB mode, a power-only cable, an unanswered Android permission prompt, or a competing MTP application. Run the controlled USB test and Debug device detection first. Never delete a library as a device-detection experiment.