Custom Drawn Interface/Using the Android SDK, Emulator and Phones: what changed
Revision 2 to 3. Removed lines have a minus sign; added lines have a plus sign.
| Old | New | Line | |
|---|---|---|---|
| 1 | - | ||
| 1 | + | [](</File:Android_robot.svg>) | |
| 2 | 2 | ||
| 3 | + | This article applies to [Android](</Category:Android> "Category:Android") only. | |
| 4 | + | ||
| 5 | + | See also: [[Multiplatform Programming Guide]] | |
| 6 | + | ||
| 7 | + | │ **English (en)** │ **[[Custom Drawn Interface/Using the Android SDK, Emulator and Phones/ru|русский (ru)]]** │ | |
| 8 | + | **** | |
| 9 | + | ||
| 3 | 10 | Go back to [[Custom Drawn Interface/Android]] | |
| 4 | 11 | ||
| 12 | + | ## Contents | |
| 13 | + | ||
| 14 | + | * 1 Using the Android SDK | |
| 15 | + | * 1.1 How to configure Ant | |
| 16 | + | * 1.1.1 Configuring Ant in Mandriva Linux | |
| 17 | + | * 1.1.2 Generic Ant errors | |
| 18 | + | * 1.2 Recognition of devices under Linux | |
| 19 | + | * 2 Using the Emulator | |
| 20 | + | * 2.1 Installing the Emulator | |
| 21 | + | * 2.2 Building an emulator image with sdcard support | |
| 22 | + | * 2.3 Running an emulator image | |
| 23 | + | * 2.4 Copying files to the emulator | |
| 24 | + | * 2.5 Installing applications in the emulator | |
| 25 | + | * 3 Using the phones | |
| 26 | + | * 3.1 Installing a File Manager | |
| 27 | + | * 3.2 Samsung Galaxy S | |
| 28 | + | ||
| 5 | 29 | ## Using the Android SDK | |
| 6 | 30 | ||
| 7 | 31 | Downloading and installing the Android SDK is easy. One just needs to following this link: <http://developer.android.com/sdk/index.html> | |
| 8 | 32 | ||
| 9 | 33 | ### How to configure Ant | |
| 10 | 34 | ||
| 11 | - | ||
| 35 | + | When issuing 'ant debug' to build and Android project one might receive a lot of errors about missing dependencies. In Linux those can be solved by installing packages which have these dependencies, and that will change from distribution to distribution. | |
| 12 | 36 | ||
| 13 | 37 | #### Configuring Ant in Mandriva Linux | |
| 14 | 38 | ||
| 15 | - | ||
| 16 | - | ||
| 17 | - | ||
| 39 | + | These errors: | |
| 40 | + | ``` | |
| 18 | 41 | /usr/bin/build-classpath: error: Could not find jaxp_parser_impl Java extension for this JVM | |
| 19 | - | ||
| 42 | + | /usr/bin/build-classpath: error: Could not find xml-commons-apis Java extension for this JVM | |
| 20 | 43 | ``` | |
| 21 | 44 | ||
| 22 | - | ||
| 23 | - | ||
| 24 | - | ||
| 45 | + | Can be fixed, respectively, with: | |
| 46 | + | ``` | |
| 25 | 47 | urpmi xerces-j2 | |
| 26 | - | ||
| 48 | + | urpmi xml-commons-jaxp | |
| 27 | 49 | ``` | |
| 28 | 50 | ||
| 29 | 51 | #### Generic Ant errors | |
| 30 | 52 | ||
| 31 | - | ||
| 32 | - | ||
| 33 | - | ||
| 53 | + | This error: | |
| 54 | + | ``` | |
| 34 | 55 | /home/felipe/Programas/lazarus-ccr/examples/androidlcl/android/build.xml:46: taskdef class com.android.ant.SetupTask cannot be found | |
| 35 | 56 | ``` | |
| 36 | 57 | ||
| 37 | - | ||
| 58 | + | Means that you need to update the Paths in your project files to correctly point to the SDK. | |
| 38 | 59 | ||
| 39 | 60 | ### Recognition of devices under Linux | |
| 40 | 61 | ||
| 41 | - | ||
| 42 | - | ||
| 43 | - | ||
| 62 | + | Unlike in Windows, where one needs to install a new set of drivers for nearly every phone, in Linux the Android devices are recognized as generic Android devices (regardless of being a phone, a tablet or a notebook) and they are ready to be used without installing additional drivers. One issue, however, that often appears is that devices are not fully recognized automatically and one receives the error message "?????? no permissions". In this case the command adb devices will look like this: | |
| 63 | + | ``` | |
| 44 | 64 | [felipe@localhost ~]$ cd Programas/android-sdk-linux_x86/tools/ | |
| 45 | - | ||
| 46 | - | ||
| 47 | - | ||
| 65 | + | [felipe@localhost tools]$ ./adb devices | |
| 66 | + | List of devices attached | |
| 67 | + | ???????????? no permissions | |
| 48 | 68 | ``` | |
| 49 | 69 | ||
| 50 | - | ||
| 51 | - | ||
| 52 | - | ||
| 70 | + | To solve this issue one can proceed with the following steps: | |
| 53 | 71 | ||
| 54 | - | ||
| 72 | + | **Step 1** \- First read the tag of the device using lsusb run as root (or sudo): | |
| 73 | + | ``` | |
| 55 | 74 | [root@localhost Programas]# lsusb | |
| 56 | - | ||
| 57 | - | ||
| 58 | - | ||
| 59 | - | ||
| 60 | - | ||
| 61 | - | ||
| 62 | - | ||
| 63 | - | ||
| 64 | - | ||
| 75 | + | Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub | |
| 76 | + | Bus 001 Device 003: ID 04e8:681c Samsung Electronics Co., Ltd | |
| 77 | + | Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 78 | + | Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub | |
| 79 | + | Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 80 | + | Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 81 | + | Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 82 | + | Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 83 | + | Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | |
| 65 | 84 | ``` | |
| 66 | 85 | ||
| 67 | 86 | The tag in this case is **04e8** | |
| 68 | 87 | ||
| 69 | - | ||
| 70 | - | ||
| 71 | - | ||
| 72 | - | ||
| 73 | - | ||
| 88 | + | **Step 2** \- Now, still as root, edit the file /etc/udev/rules.d/51-android.rules | |
| 74 | 89 | ||
| 75 | - | ||
| 90 | + | If the file doesn't exist yet, then create it. Add the following line to the file: | |
| 91 | + | ``` | |
| 92 | + | SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="04e8", SYMLINK+="android_adb", MODE="0666" | |
| 93 | + | ``` | |
| 76 | 94 | ||
| 77 | - | ||
| 95 | + | Change the ID to correspond to the id of your device. | |
| 78 | 96 | ||
| 79 | - | ||
| 97 | + | **Step 3** \- Restart the linux usb service (udev) | |
| 80 | 98 | ||
| 81 | - | ||
| 99 | + | In Ubuntu this can be done with: sudo services udev restart | |
| 82 | 100 | ||
| 83 | - | ||
| 101 | + | In Mandriva udev doesn't appear as a service, so the only way to get things working for me was restarting the computer. | |
| 84 | 102 | ||
| 85 | - | ||
| 103 | + | After doing this, the device should be fully recognized and "adb devices" as well as "adb logcat" should work. | |
| 104 | + | ``` | |
| 86 | 105 | [felipe@localhost tools]$ ./adb devices | |
| 87 | - | ||
| 88 | - | ||
| 89 | - | ||
| 90 | - | ||
| 106 | + | * daemon not running. starting it now on port 5037 * | |
| 107 | + | * daemon started successfully * | |
| 108 | + | List of devices attached | |
| 109 | + | 1000c31696b6 device | |
| 91 | 110 | ``` | |
| 92 | 111 | ||
| 93 | 112 | ## Using the Emulator | |
| 94 | 113 | ||
| 95 | 114 | ### Installing the Emulator | |
| 96 | 115 | ||
| 97 | 116 | ### Building an emulator image with sdcard support | |
| 98 | 117 | ||
| 99 | - | ||
| 118 | + | Step 1: Run the application C:\Program Files\android-sdk-windows\tools\android.bat | |
| 100 | 119 | ||
| 101 | - | ||
| 120 | + | Step 2: Create a new image, by clicking the New button as in the image below. | |
| 102 | 121 | ||
| 103 | - | ||
| 122 | + | [](</File:Android_new_image.PNG>) | |
| 104 | 123 | ||
| 105 | - | ||
| 124 | + | Step 3: Set the name and properties of the image, the size of the SDCard and add hardware support for the sdcard, as seen on the image below. | |
| 106 | 125 | ||
| 107 | - | ||
| 126 | + | [](</File:Android_new_image_dialog.PNG>) | |
| 108 | 127 | ||
| 109 | 128 | ### Running an emulator image | |
| 110 | 129 | ||
| 111 | - | ||
| 130 | + | Step 1: Run the application C:\Program Files\android-sdk-windows\tools\android.bat | |
| 112 | 131 | ||
| 113 | - | ||
| 132 | + | Step 2: Select the image | |
| 114 | 133 | ||
| 115 | - | ||
| 134 | + | Step 3: Click on the "start" button, as seen below. | |
| 116 | 135 | ||
| 117 | - | ||
| 136 | + | [](</File:Android_run_image.PNG>) | |
| 118 | 137 | ||
| 119 | 138 | ### Copying files to the emulator | |
| 120 | 139 | ||
| 121 | - | ||
| 122 | - | ||
| 123 | - | ||
| 140 | + | You can use a script similar to this one to copy files from your hard-drive to the emulator. Notice that the image must be running and that it must have sdcard support built inside itself. | |
| 141 | + | ``` | |
| 124 | 142 | c: | |
| 125 | - | ||
| 126 | - | ||
| 127 | - | ||
| 128 | - | ||
| 129 | - | ||
| 143 | + | cd "Program Files" | |
| 144 | + | cd android-sdk-windows | |
| 145 | + | cd tools | |
| 146 | + | adb push C:\Mypath\Somefile.extension /sdcard | |
| 147 | + | pause | |
| 130 | 148 | ``` | |
| 131 | 149 | ||
| 132 | 150 | ### Installing applications in the emulator | |
| 133 | 151 | ||
| 134 | - | ||
| 135 | - | ||
| 136 | - | ||
| 152 | + | Android apps should be packaged in the Android .apk file format. For more information about how to create an .apk file that you can install on an emulator/device instance, see Android Asset Packaging Tool (aapt). After packing a file, it can be installed in the emulator by using the following adb call: | |
| 153 | + | ``` | |
| 137 | 154 | c: | |
| 138 | - | ||
| 139 | - | ||
| 140 | - | ||
| 141 | - | ||
| 142 | - | ||
| 155 | + | cd "Program Files" | |
| 156 | + | cd android-sdk-windows | |
| 157 | + | cd tools | |
| 158 | + | adb install C:\Mypath\MyApp.apk | |
| 159 | + | pause | |
| 143 | 160 | ``` | |
| 144 | 161 | ||
| 145 | 162 | ## Using the phones | |
| 146 | 163 | ||
| 147 | - | ||
| 164 | + | Installing the drivers and getting a reliable way to transfer executables and debug software with all the different Android phone can be a challenge in itself. | |
| 148 | 165 | ||
| 149 | 166 | ### Installing a File Manager | |
| 150 | 167 | ||
| 151 | - | ||
| 168 | + | Astonishingly, Android phones don't come with a file manager o.O One can however simply download one from the Android Market. I suggest the following instructions: | |
| 152 | 169 | ||
| 153 | - | ||
| 170 | + | 1\. Connect the phone to a WiFi or Mobile network | |
| 154 | 171 | ||
| 155 | - | ||
| 172 | + | 2\. Click in the "Market" icon in one of the Android desktops. It will be necessary to log into a Google Account to access it. | |
| 156 | 173 | ||
| 157 | - | ||
| 174 | + | 3\. Click the search button and type "oi" | |
| 158 | 175 | ||
| 159 | - | ||
| 176 | + | 4\. Locate and install the "OI File Manager" which is Free | |
| 160 | 177 | ||
| 161 | 178 | ### Samsung Galaxy S | |
| 162 | 179 | ||
| 163 | - | ||
| 180 | + | The first thing to do when using Samsung Galaxy S is not believing the Samsung instructions. They will say that one should install Kies, their horribly crappy PC suite which is 130MB large and fails to install because the first thing that it does is failing to connect to a server in Korea to download even more files. Instead of doing this, following these instructions: | |
| 164 | 181 | ||
| 165 | - | ||
| 182 | + | 1\. Go in the phone menu Settings -> About Phone -> USB settings. Change from "KIES" to "Mass storage" | |
| 166 | 183 | ||
| 167 | - | ||
| 184 | + | 2\. Download and install 19 MB of Samsung USB drivers from: [http://drivers.softpedia.com/dyn-postdownload.php?p=96692&t=4&i=1](<http://drivers.softpedia.com/dyn-postdownload.php?p=96692&t=4&i=1>) | |
| 168 | 185 | ||
| 169 | - | ||
| 186 | + | 3\. Connect the cable of the phone | |
| 170 | 187 | ||
| 171 | 188 | 4\. Drag the top menu of the phone down and mount the sdcard | |
| 172 | 189 | ||
| 173 | 190 | --- | |
| 174 | - | ||
| 175 | - | ||
| 176 | - | ||
| 191 | + | *From the Free Pascal wiki, page "Custom Drawn Interface/Using the Android SDK, Emulator and Phones", as the Internet Archive kept it on 2023-01-28. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).* |