#12873 HIGH Not Tri: Keyboard mapping in Ceibal Andoid Image

[Zarro Boogs per Child]

#12873: Keyboard mapping in Ceibal Andoid Image
--------------------------------+-------------------------------
            Reporter:  ebordon  |          Owner:  Quozl
                Type:  defect   |         Status:  new
            Priority:  high     |      Milestone:  Not Triaged
           Component:  android  |        Version:  not specified
          Resolution:           |       Keywords:
          Blocked By:           |       Blocking:
Deployments affected:           |  Action Needed:  diagnose
            Verified:  0        |
--------------------------------+-------------------------------

Comment (by Quozl):

 Received 41072ca4.zd, thanks.  The file /system/input-manager-state.xml
 was not present in the build, as expected.

 The build tested fine on SKU322.  After research, SKU321 and SKU322 are
 equivalent in hardware components.  Therefore SKU322 is sufficient for
 replicating.

 Changed keyboard mapping and copied the file input-manager-state.xml.  The
 device descriptor hash was no different.  Reinstalled the build, but then
 booted Linux, restored the .xml file, and rebooted to Android.  The system
 hung during boot, the boot animation continued to pulse, camera indicator
 flashed every 39 seconds, and serial console showed cycles of:

 {{{
 [ 9999.837469] init: untracked pid 9391 exited
 [ 9999.879109] init: untracked pid 9787 exited
 [ 9999.895855] alarm_release: clear alarm, pending 0
 [ 9999.895855] alarm_release: clear alarm, pending 0
 [ 9999.905377] init: untracked pid 9768 exited
 [ 9999.937074] init: untracked pid 9390 exited
 [ 9999.949398] binder: release 9761:9761 transaction 1221548 out, still
 active
 [ 9999.956542] init: untracked pid 9761 exited
 [ 9999.975897] init: untracked pid 9794 exited
 [ 9999.977452] init: untracked pid 9733 exited
 [ 9999.993836] binder: release 9733:9733 transaction 1221547 out, still
 active
 [10000.035453] binder: release 9794:9794 transaction 1221543 out, still
 active
 [10000.055285] init: untracked pid 9820 exited
 [10000.066974] binder: release 9787:9787 transaction 1221544 out, still
 active
 [10000.105710] binder: release 9768:9768 transaction 1221545 out, still
 active
 [10000.105710] binder: release 9606:9606 transaction 1221544 in, still
 active
 [10000.175107] binder: send failed reply for transaction 1221544, target
 dead
 [10000.175128] binder: release 9606:9616 transaction 1221545 in, still
 active
 [10000.235142] binder: send failed reply for transaction 1221545, target
 dead
 [10000.235160] binder: release 9606:9819 transaction 1221543 in, still
 active
 [10000.295151] binder: send failed reply for transaction 1221543, target
 dead
 [10000.316060] binder: send failed reply for transaction 1221547, target
 dead
 [10000.316060] binder: send failed reply for transaction 1221548, target
 dead
 [10000.955093] siv121c 0-0033: reset...
 }}}

 Rebooted into Linux, deleted the .xml file, and rebooted into Android.
 The hang happened once more.

 Rebooted into Linux, changed the powerhal.conf file for the new camera
 sensor address, and rebooted into Android.  The hang happened once more.

 The results imply either the .xml file won't be accepted during first
 boot, or that another file also needs to be changed.

 The investigation is continuing.

--
Ticket URL: <http://dev.laptop.org/ticket/12873#comment:4>
One Laptop per Child <http://one.laptop.org/>
One Laptop per Child bug tracking system