1045143 - [B2G][Flame][Keyboard] The process name of built-in keyboard is not displayed in adb tool

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect)

Description

[Rachel Pribble [:rpribble]]

Attachment: KeyboardProcess.jpg

Description:
The process number of the built-in keyboard does not display when communicating with the device using an adb tool. When the built-in keyboard is disabled and a third party keyboard is used, the third-party keyboard's process number displays correctly.

Repro Steps:
1) Update a Flame to BuildID: 20140723000201
2) Connect device to pc
3) Use adb tool to communicate with device, type: adb shell b2g-info

Actual:
Built-in keyboard process number does not display correctly.

Expected:
Build-in keyboard process number displays when prompted.

v2.0 Environmental Variables:
Device: Flame v2.0 MOZ ril (319MB)
BuildID: 20140728000238
Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko: 2da96d621030
Version: 32.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Notes:

Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/11367/
See attached: Screenshot, logcat

---------------------------------------------

This issue occurs on the Flame v2.1 , Buri v2.1, Flame v2.0, Buri v2.0, Flame v1.4, and Buri v1.4.

Environmental Variables:
Device: Flame Master (319MB)
Build ID: 20140728040209
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: a4dcfbebcb58
Version: 34.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Buri Master
Build ID: 20140728073003
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: d77f6a96ff96
Version: 34.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0 MOZ ril (512MB)
Build ID: 20140728000238
Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko: 2da96d621030
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Buri 2.0 MOZ ril
Build ID: 20140721000201
Gaia: 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97
Gecko: 4bd4b0ae7bbe
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Flame 1.4 MOZ ril (319MB)
Build ID: 20140728063001
Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko: aae9112f1fc6
Version: 30.0 (1.4) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Environmental Variables:
Device: Buri 1.4 MOZ ril
Build ID: 20140728063001
Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko: aae9112f1fc6
Version: 30.0 (1.4)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Built-in keyboard process number does not display correctly.

Comment 1

[Rachel Pribble [:rpribble]]

Attachment: Logcat.txt

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

I don't see how this would affect an end user so not nominating as a blocker.

Comment 3

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

With Bug 1036577, we would run built-in keyboard as in-proc for device < 512 MB.
So, this is expected behavior since this bug is reported on a device with 319 MB.
Note that that patch was applied to v2.0 and master (v2.1).

For v1.4, the built-in would always be run in-proc.

--
Thanks for filing this and please help re-open if there is any other concern.

Comment 4

[John Thomas [:Johnt]]

This test case IS valid for devices under 512mb and needs to be updated to specifically mention the memory prerequisites.

Comment 5

[KTucker [:KTucker][Inactive 3/4/2016]]

This should only work on devices equal to or greater than 512mb. Please ignore comment 4. 

Test case has been updated in moztrap here:

https://moztrap.mozilla.org/manage/case/11367/