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