1 <html devsite> 2 <head> 3 <title>Migration Guide</title> 4 <meta name="project_path" value="/_project.yaml" /> 5 <meta name="book_path" value="/_book.yaml" /> 6 </head> 7 <body> 8 <!-- 9 Copyright 2017 The Android Open Source Project 10 11 Licensed under the Apache License, Version 2.0 (the "License"); 12 you may not use this file except in compliance with the License. 13 You may obtain a copy of the License at 14 15 http://www.apache.org/licenses/LICENSE-2.0 16 17 Unless required by applicable law or agreed to in writing, software 18 distributed under the License is distributed on an "AS IS" BASIS, 19 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 20 See the License for the specific language governing permissions and 21 limitations under the License. 22 --> 23 24 25 <p>This document contains a few helpful tips when migrating to new Android releases.</p> 26 <h2 id="migrating-to-android-gingerbread-23">Migrating to Android Gingerbread 2.3</h2> 27 <p>In Gingerbread, we added the concept of input device configuration files 28 (also referred to as input device calibration files in this release).</p> 29 <p>Make sure to provide an input device configuration file for all touch screens. 30 In particular, it is worth spending time providing a calibration reference for 31 touch size information.</p> 32 <h2 id="migrating-to-android-honeycomb-30">Migrating to Android Honeycomb 3.0</h2> 33 <p>In Honeycomb, we revised the key character map file format and started making 34 greater use of input device configuration files. We also added support for full 35 PC-style keyboards and introduced a new "Generic" key map, which 36 replaced the older emulator-specific "qwerty" key map (which was never 37 intended to be used as a general-purpose key map.)</p> 38 <p>Make sure to update all of your key character map files to use the new syntax.</p> 39 <p>If your peripherals relied on the old "qwerty" key map, then you 40 may need to provide new device-specific key maps to emulate the old behavior. 41 You should create a new key map for each device identified either by 42 USB product id / vendor id or by device name.</p> 43 <p>It is especially important to provide key character map files for all special 44 function input devices. These files should simple contain a line to set 45 the keyboard type to <code>SPECIAL_FUNCTION</code>.</p> 46 <p>A good way to ensure that all built-in input devices are appropriately configured 47 is to run <a 48 href="https://developer.android.com/studio/command-line/dumpsys.html">Dumpsys</a> 49 and look for devices that are inappropriately using <code>Generic.kcm</code>.</p> 50 <h2 id="migrating-to-android-honeycomb-32">Migrating to Android Honeycomb 3.2</h2> 51 <p>In Honeycomb 3.2, we added support for joysticks and extended the key layout file 52 format to enable joystick axis mapping.</p> 53 <h2 id="migrating-to-android-ice-cream-sandwich-40">Migrating to Android Ice Cream Sandwich 4.0</h2> 54 <p>In Ice Cream Sandwich 4.0, we changed the device driver requirements for touch screens 55 to follow the standard Linux multitouch input protocol and added support for 56 protocol "B". We also support digitizer tablets and stylus-based touch devices.</p> 57 <p>You will probably need to update your input device driver to implement the Linux 58 multitouch input protocol correctly according to the standard.</p> 59 <p>You will also need to update your input device configuration files because some 60 properties have been changed to be simpler and more systematic.</p> 61 <p>Refer to <a href="touch-devices.html">Touch Devices</a> for more details about 62 driver requirements.</p> 63 64 </body> 65 </html> 66
