When you plug a Device into your Delphi development environment you hope Delphi identifies it as a “Target”. What do you do if it does not?
Assuming you are convinced the device is supported, connected and there are no USB driver issues flagged in Windows I suggest you look at Android Debug Bridge to debug the issue.
Adb.exe sits in the Android “platform-tools” folder.
The Command “adb devices” gives a list of Adb devices and their status.
I now have a batch file in that folder with a desktop shortcut
Rem Get Devices adb devices Pause
List of devices attached 4d001a9fccc6b000 device 4200b247ac6a3300 unauthorized
List of devices attached * daemon not running; starting now at tcp:5037 * daemon started successfully 4d001a9fccc6b000 device 4200b247ac6a3300 unauthorized
The fact that the phone is reported as unauthorized and the note on the Android Debug Bridge web page explains why Delphi did not “Target” the device and suggests looking at the phone debug security features.
Note on web page:
When you connect a device running Android 4.2.2 or higher, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you’re able to unlock the device and acknowledge the dialog.