Closed Bug 1168730 Opened 9 years ago Closed 9 years ago

we need to add a new keyword 'led' for KeyLayoutMap

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.2+, firefox41 fixed, b2g-v2.2 fixed, b2g-master fixed)

RESOLVED FIXED
2.2 S14 (12june)
blocking-b2g 2.2+
Tracking Status
firefox41 --- fixed
b2g-v2.2 --- fixed
b2g-master --- fixed

People

(Reporter: viralwang, Assigned: viralwang)

References

Details

Attachments

(1 file, 1 obsolete file)

we expect we can use Generic.kl for keycode mapping but we can load it since there's a new keyword 'led'
we will get the error log as below

E/KeyLayoutMap(16416): /system/usr/keylayout/Generic.kl:431: Expected keyword, got 'led'.
Hi Michael,

I only update partial code for the new keyword 'led', then we can use the Generic.kl file directly.
Attachment #8611075 - Flags: review?(mwu)
Assignee: nobody → vwang
Is there a git commit on the Android side which this corresponds to? Or a set of commits?
Hi Michael,

Most of changes come from this commit: https://android.googlesource.com/platform/frameworks/native/+/74bdd2e7ceabd3c9e74ccf7c2e6bd3dae27ca497
Android move it to KeycodeLabels.h in following commit but I think we only need few things to make it work.
https://android.googlesource.com/platform/frameworks/native/+/872db4f11e407accccba9d37c335ef7e3597eba4

Thank you :)
Comment on attachment 8611075 [details] [diff] [review]
add 'led' for KeyLayoutMap scan code

Review of attachment 8611075 [details] [diff] [review]:
-----------------------------------------------------------------

Ok. Please put the information about where you got this in the commit message.

We should probably just drop in a new copy of Android input code at some point and pickup all the updates.
Attachment #8611075 - Flags: review?(mwu) → review+
update commit message for landing
Attachment #8611075 - Attachment is obsolete: true
https://hg.mozilla.org/mozilla-central/rev/bdc2ca02b080
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S14 (12june)
blocking-b2g: --- → 2.2?
Hi Josh,

I think we need this fix for v2.2 since we can't use power key to wake up flame-l with v2.2 now.
With this gecko fix, we can use correct key mapping for flame-l.
Thank you :)
Flags: needinfo?(jocheng)
blocking-b2g: 2.2? → 2.2+
Flags: needinfo?(jocheng)
Please request b2g37 approval on this patch when you get a chance.
Flags: needinfo?(vwang)
Comment on attachment 8614504 [details] [diff] [review]
add 'led' for KeyLayoutMap scan code (v2)

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): NA
User impact if declined: we need this fix for v2.2 since we can't use power key to wake up flame-l with v2.2 now. With this gecko fix, we can use correct key mapping for flame-l.
Testing completed: local test is fine.
Risk to taking this patch (and alternatives if risky): Low. 
String or UUID changes made by this patch: NA
Flags: needinfo?(viralwang)
Attachment #8614504 - Flags: approval-mozilla-b2g37?
Attachment #8614504 - Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: