It only takes one line of text to add Kindle Fire to the list of devices that ADB knows about. The hard part is tracking down the text file to edit and getting ADB to restart after making the required changes. Things are more involved when using Windows than with Mac because you also have to configure the USB driver, so the two systems are shown here as separate steps.
The steps to be followed for adding a Kindle Fire to ADB for a Windows OS are as follows:
C:Usersyourusername.android
where the adv_usb.ini
file is located.adv_usb.ini
text file in a text editor. The file has no visible line breaks, so it is better to use WordPad than NotePad.0x1949
.9
at the end of 0x1949
.C:Program Files (x86)Androidandroid-sdkextrasgoogleusb_driver
where android_winusb.inf
is located.android_winusb.inf
file in NotePad.[Google.NTx86]
and [Google.NTamd64]
sections and save the file:;Kindle Fire %SingleAdbInterface% = USB_Install, USBVID_1949&PID_0006 %CompositeAdbInterface% = USB_Install, USBVID_1949&PID_0006&MI_01
googleusb_driver
folder, and then select it to be the new driver.cd C:Program Files (x86)Androidandroid-sdkplatform-tools
adb kill-server adb start-server adb devices
The steps to be followed for a Mac (MUCH simpler!) system are as follows:
adv_usb.ini
file is located. On Mac, in Finder, select the menu by navigating to Go | Go to Folder… and type ~/.android/
in.adv_usb.ini
file in a text editor.0x1949
.9
at the end of 0x1949
.adv_usb.ini
file.yourusername
with your actual username and also change the path if you've installed the Android SDK to some other location):export PATH=$PATH:/Users/yourusername/Documents/android-sdk-macosx/platform-tools
adb kill-server adb start-server adb devices
I suspect that you're going to have nightmares about all these steps! It took a lot of research on the Web to find out some of these obscure hacks. The general case with Android devices on Windows is that you have to modify the USB driver for the device to be handled using the Google USB driver, and you may have to modify the adb_usb.ini
file (on Mac too) for the device to be considered as an ADB compatible device.
If you carefully went through all these Android steps, especially on Windows, you will hopefully be amused by the brevity of this section! There is a catch though; you can't really test on an iOS device from LiveCode. We'll look at what you have to do instead in a moment, but first, we'll look at the steps required to test an app in the iOS simulator.