Android key layout issue
I have an issue where Android is only using the generic.kl for the key layout file even though I have a correct Vendor_xxxx_Product_xxxx.kl file created.
This is for a handheld remote with a USB receiver.
I used 'cat /proc/bus/input/devices' in a shell to determine the correct vendor/product info. I have also removed all the other device specific layout files as to eliminate a duplicate. The system is definitely using the generic.kl because I can make a slight change to it and it is reflected in the remote. The remote does work with the generic.kl, it's just there are some extra buttons I need to make work.
Any help would be appreciated. Thanks
android
add a comment |
I have an issue where Android is only using the generic.kl for the key layout file even though I have a correct Vendor_xxxx_Product_xxxx.kl file created.
This is for a handheld remote with a USB receiver.
I used 'cat /proc/bus/input/devices' in a shell to determine the correct vendor/product info. I have also removed all the other device specific layout files as to eliminate a duplicate. The system is definitely using the generic.kl because I can make a slight change to it and it is reflected in the remote. The remote does work with the generic.kl, it's just there are some extra buttons I need to make work.
Any help would be appreciated. Thanks
android
add a comment |
I have an issue where Android is only using the generic.kl for the key layout file even though I have a correct Vendor_xxxx_Product_xxxx.kl file created.
This is for a handheld remote with a USB receiver.
I used 'cat /proc/bus/input/devices' in a shell to determine the correct vendor/product info. I have also removed all the other device specific layout files as to eliminate a duplicate. The system is definitely using the generic.kl because I can make a slight change to it and it is reflected in the remote. The remote does work with the generic.kl, it's just there are some extra buttons I need to make work.
Any help would be appreciated. Thanks
android
I have an issue where Android is only using the generic.kl for the key layout file even though I have a correct Vendor_xxxx_Product_xxxx.kl file created.
This is for a handheld remote with a USB receiver.
I used 'cat /proc/bus/input/devices' in a shell to determine the correct vendor/product info. I have also removed all the other device specific layout files as to eliminate a duplicate. The system is definitely using the generic.kl because I can make a slight change to it and it is reflected in the remote. The remote does work with the generic.kl, it's just there are some extra buttons I need to make work.
Any help would be appreciated. Thanks
android
android
asked Nov 25 '18 at 22:24
dcoldcol
64
64
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53472620%2fandroid-key-layout-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53472620%2fandroid-key-layout-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown