Database Users

Can align screen shortcut be disabled?

I'm curious if its possible to disable the align screen shortcut on the Wizard (Enter Button in center plus Messages Button) Its really annoying when playing Doom or an emulator in landscape and having that popup all the time. Does anyone know a fix for this?

Unfortunately i dont have an answer for you. but i do have aquestion that i hope youcan answer. I got myself a doom launcher. It works well, but the control setup is terrible on the wizard. If i play in portrait mode, the fire button is the left soft key. So i ahve to fire with the same finger that i use to move. That makes the game unplayable. What launcher are you using and where did you get it?

I haven't done any testing or trying yet, but here is my idea...
what if you rename the align screen app, just so it stops it from launching?

Unfortunately i dont have an answer for you. but i do have aquestion that i hope youcan answer. I got myself a doom launcher. It works well, but the control setup is terrible on the wizard. If i play in portrait mode, the fire button is the left soft key. So i ahve to fire with the same finger that i use to move. That makes the game unplayable. What launcher are you using and where did you get it?
Click to expand...
Click to collapse
Its called GF Doom (I'm sorry but I don't remember where I got it or whom made it. Although if the creator see's this I would love for him/her to PM me as I also have some questions.) Anyway the launcher shouldn't control the Key Mapping, usually thats done in some sort of config file. With the program that I have the keys are mapped in the skin file's txt document.
Try this, unzip all contents into your storage card and run the launcher you should get Doom, Doom II, and Plutonia (sometimes called Ultimate Doom) as well as a 3rd party mod called Evilution. Keep the default skin, with that the keys I have mapped are:
The directional Buttons for Movement, Messages button for Fire and strafe(I would like to change strafe to volume up/down or Internet but have not been able to if you can figure this out let me know), and the softkeys for Select and Start.
The screen defaults to protrait with your choosen skin. To play in full landscape start the game in the options change the resolution to "low" and it will switch, Hope this helps
I can't seem to get the attachment to work here is the link ftp://[email protected]/Uploads/
the file is pocket doom.zip

A Flock of Seagulls are in my Wizard
It would be awesome to find a way to disable this. Is there maybe an entry in the registry that corresponds to what key combination turns on the align screen program. Maybe it could be changed to some combination of keys that is very unlikely to be executed simultaneously.
Until then, I'll continue to drink foo-foo drinks to calm myself while trying to play any action games.

GF Doom
Dragonedge:
What version of GF Doom do you have? Maybe I have an old version. When I enter full screen mode, the soft keys are shoot and strafe, while the message/IE buttons are menu and escape. I have to use the same hand to shoot as I do to move.
Thanks for the tip about full screen, I would never have figured that out. Now I'm not dissapointed with the program anymore.

Lol, funny posts. Is this still a problem? Does it need investigating?
V

I still have the problem........ working on some things now.

What version of GF Doom do you have? Maybe I have an old version. When I enter full screen mode, the soft keys are shoot and strafe, while the message/IE buttons are menu and escape. I have to use the same hand to shoot as I do to move.
Thanks for the tip about full screen, I would never have figured that out. Now I'm not dissapointed with the program anymore.
Click to expand...
Click to collapse
Not sure what version it is. Check out the ftp I uploaded a zip file with everything I use. Also you can edit the skin files to remap the softkeys as well as the messaging and internet keys. All the information about remapping the buttons is in the skins folder in a txt file names Skin Specs.
Lol, funny posts. Is this still a problem? Does it need investigating?
Click to expand...
Click to collapse
The only problem I had was being able to map the message and internet buttons as different keys. Also I would like to use the volume slider as a left and righ strafe but could not seem to get that mapped either. Any help there would be great.

I've made an app to disable this - VJCalibrula for Universal and Hermes.
Wizard requires a slightly different hack, and I don't have one to test on.
dragonedge: what hardware/ROM are you using? I'll try to get you to alpha test if you want.
V

dragonedge: what hardware/ROM are you using? I'll try to get you to alpha test if you want.
Click to expand...
Click to collapse
I wouldn't mind at all . I have the T-mobile MDA/Wizard with the 2.26 ROM
An app to disable this would be handy another idea that would be nice is an app that would let you specify another button combination for system shortcuts would be awesome.

VJCalibrula - disable align screen settings (alpha)
Guys, please give this a go.
I don't think it supports AKU 3.2 for now. Soon...
http://forum.xda-developers.com/showthread.php?t=282152
V

[Q] accessing MENU via. Bluetooth Keyboard or mouse

Hi all,
I recently picked up the 2.0MHL to HDMI cable along with a Bluetooth mouse and Bluetooth (what appears to be Apples style) keyboard to use with my S4. So far I'm enjoying the experience in terms of uses and navigating relatively easily through the phone. Currently using NOVA as my launcher. Volume, home button, back buttons were easy to figure out. Accessing the multi-window, recent apps/task killer is not a problem. I can't however, for the life of me figure out how to access the MENU button via. the keyboard or mouse. I've done various searches and YouTube videos online and people mention how the right click doesn't access the menu but neglect to mention how to ACTUALLY access the menu. I did see 1 video where it mentioned Control P but when I had tried that, it was a shortcut to select either music player or Google play. Has anyone else had this problem? Any luck with finding the right short key? Thanks in advance for your time and consideration.

Moosterly said:
Hi all,
I recently picked up the 2.0MHL to HDMI cable along with a Bluetooth mouse and Bluetooth (what appears to be Apples style) keyboard to use with my S4. So far I'm enjoying the experience in terms of uses and navigating relatively easily through the phone. Currently using NOVA as my launcher. Volume, home button, back buttons were easy to figure out. Accessing the multi-window, recent apps/task killer is not a problem. I can't however, for the life of me figure out how to access the MENU button via. the keyboard or mouse. I've done various searches and YouTube videos online and people mention how the right click doesn't access the menu but neglect to mention how to ACTUALLY access the menu. I did see 1 video where it mentioned Control P but when I had tried that, it was a shortcut to select either music player or Google play. Has anyone else had this problem? Any luck with finding the right short key? Thanks in advance for your time and consideration.
Click to expand...
Click to collapse
I know this is a late reply to your question, but maybe I can help. I bought a mini bluetooth keyboard designed to use with windows, and for a while I had the same problem. I. could access everything on my S3 except the menu. I searched, found your post, then started randomly trying different buttons. I'm not sure if your board has this key, but it's between the right Alt and Ctrl keys, it looks like a square with an arrow pointing inside it. That`s the menu button on mine. Hope this help, and sorry for the long reply.

How to make headset button control music on the stock ROM

I'm not sure this is the right subforum for this, but I was coming here to ask how to do this before I figured it out for myself. So I figured I should post about it in case I forget what I did.
I just switched to a shiny new G2, and I'm using the one-button earphones that came with my Nexus S 4G. This is actually the third set of such headphones (I keep breaking and replacing them), so I refuse to have them not work on my rooted but otherwise stock G2.
When I first plugged them in to the G2, it was configured so that the button would control the phone function: one press would open my call history, a double press would redial, and a hold would start up voice dialer. On the Nexus S 4G, the buttons controlled my media player, so that's what I want them to do here.
I tried various button remapping tools like the JAYS Headset Control app, but none of them would take precedence over the default LG actions.
Instead, I modified this approach from the Nexus 4, and changed the key code for the button from the one that the voice dialer controls were intercepting (HEADSETHOOK) to something else (MEDIA_NEXT).
What I did:
1. Have root and install Busybox (for vi).
2. Get a root shell on the device.
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ #
3. Mount /system as read-write:
Code:
[email protected]:/ # mount -o rw,remount /system
4. Edit the default Android keyboard layout to swap the HEADSETHOOK and MEDIA_NEXT keys.
Code:
[email protected]:/ # vi /system/usr/keylayout/Generic.kl
Press "i" to enter insert mode. Move around with the arrow keys.
Change:
Code:
key 163 MEDIA_NEXT
to:
Code:
key 163 HEADSETHOOK
And also change:
Code:
key 226 HEADSETHOOK
to:
Code:
key 226 MEDIA_NEXT
Press Escape, and then press Shift + Z twice to save and quit.
5. Reboot your device for the changes to take effect.
6. Now the button on your single-button headset is the equivalent of the "down" or "next" button on a three-button headset. To configure it, install JAYS Headset Control or a similar application. Chose the three-button headset instead of the one-button headset, and configure the third button to do everything you want your button to do.
7. Enjoy your customizable button!

Sweet! Not having my headset button work for audio was my biggest issue with the G2.
I followed the instructions above, but instead of swapping "key 163 MEDIA_NEXT" I swapped "key 164 MEDIA_PLAY_PAUSE". This caused the default behavior to be "Play/Pause".
I tried using JAYS Headset Control and it works great. Thanks for the find!

Oh my gosh! I've been looking everywhere for this solution. Thank you so much!
My dilemma was that I want to be able to use the headset buttons because I listen to music and switch tracks frequently while walking around the university. Only the Android KitKat ROMs worked for me, but the problem with those ROMs is that GPS has locking problems and/or doesn't work at all.

Thanks for this, it was helpful for me also. Like Myzur I've also used MEDIA_PLAY_PAUSE instead of MEDIA_NEXT.
I had a quick go with the "Headset Button ControllerTrial" app for some extended functionality, but it kept switching from Rhapsody to LG's music app. This was before I saw the comment about configuring things as if it were a 3 button headset, so I'll play around with this some more (and will probably also try the JAYS app). But even as-is, just the ability to play/pause is a very nice improvement over stock behavior (honestly, who uses their phone more for making calls than listening to music.. ).

doesnt work
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?

pabel101 said:
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?
Click to expand...
Click to collapse
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.

doesnt work
ChoppedLiver said:
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.
Click to expand...
Click to collapse
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply

pabel101 said:
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply
Click to expand...
Click to collapse
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.

playpause
ChoppedLiver said:
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.
Click to expand...
Click to collapse
ok i did what you said and now my middle button Just skips to next track is that alright?

pabel101 said:
ok i did what you said and now my middle button Just skips to next track is that alright?
Click to expand...
Click to collapse
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.

headset
ChoppedLiver said:
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.
Click to expand...
Click to collapse
Just to be more specific these are the headphones im using http://www.amazon.com/Samsung-Repla...m-Headset/dp/B007C5S3AU/ref=pd_bxgy_cps_img_y

Help
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance

Ghost_Killer811 said:
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance
Click to expand...
Click to collapse
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.

ChoppedLiver said:
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.
Click to expand...
Click to collapse
Thanks for the help. I tried reading the instructions, but I got confused. When it says to make a root shell and then gives the code, do I put it somewhere specific in the file or just anywhere.

Shield Nvidia button Tweaks and Moga Pro HID tweaks

Having purchased the nvidia shield back at launch, one of the main things that bothered me about it's design was the lack of a few buttons, namely a menu button and select button, instead we got a button that opened nvidia's tegra zone, something easily accessible from a launcher and a volume button which again wasn't something I needed to constantly access.
So i ended up editing some of the .kl files and using an xposed tweak called gravity box to tune things a bit
I changed the nvidia button to act as a menu button with the .kl files, and the volume button to act as a select button
with gravity box i changed the menu button's long press function to call up the power menu to restore that function to how the shield comes, and set the back button when long pressed to call up the volume control
also keep in mind if you don't use xposed with gravity box to tweak the keys after they've been changed you will have difficulty shutting down the shield properly as the nvidia button of course acts as the power button when held down longer, it of course still powers up the device either way, and will hard power the device off if held for several seconds, still setting up gravity box feels like the best way
now for the moga controller, while you can make it function in a usable state with tincore or game keyboard, and in fact those both still come in very handy for touch emulation, I didn't want to always have those apps running when i wanted standard button presses, when the controller would go to sleep it would take time to get re detected so i wanted a little more convenience, I think this also should make it work with the built in console mode touch emulation, though I haven't tested that
the HID mode on it would have the select button as a back button, and the shoulder buttons didn't seem to work unless an app specifically supported the controller
So i added a few .kl files for that as well, not sure which of the 3 gets called as they're all duplicates in function, but presumably the device ID one should be the default, but i added the other 2 in case it doesn't for some reason
these .kl files should be put in /system/usr/keylayout
root is required and obviously backup the files that get replaced for the shield, the moga ones should not have existing files and match the permissions to the other files that're in the folder
I've tested these moga files on an LG phone on 4.2.2 and the shield on 4.3
I've included a backup of the original files for 4.3 for the shield in the zip, but no idea if they'd be different under Kitkat though I don't see why they would be

ciphray said:
Having purchased the nvidia shield back at launch, one of the main things that bothered me about it's design was the lack of a few buttons, namely a menu button and select button, instead we got a button that opened nvidia's tegra zone, something easily accessible from a launcher and a volume button which again wasn't something I needed to constantly access.
So i ended up editing some of the .kl files and using an xposed tweak called gravity box to tune things a bit
I changed the nvidia button to act as a menu button with the .kl files, and the volume button to act as a select button
with gravity box i changed the menu button's long press function to call up the power menu to restore that function to how the shield comes, and set the back button when long pressed to call up the volume control
also keep in mind if you don't use xposed with gravity box to tweak the keys after they've been changed you will have difficulty shutting down the shield properly as the nvidia button of course acts as the power button when held down longer, it of course still powers up the device either way, and will hard power the device off if held for several seconds, still setting up gravity box feels like the best way
now for the moga controller, while you can make it function in a usable state with tincore or game keyboard, and in fact those both still come in very handy for touch emulation, I didn't want to always have those apps running when i wanted standard button presses, when the controller would go to sleep it would take time to get re detected so i wanted a little more convenience, I think this also should make it work with the built in console mode touch emulation, though I haven't tested that
the HID mode on it would have the select button as a back button, and the shoulder buttons didn't seem to work unless an app specifically supported the controller
So i added a few .kl files for that as well, not sure which of the 3 gets called as they're all duplicates in function, but presumably the device ID one should be the default, but i added the other 2 in case it doesn't for some reason
these .kl files should be put in /system/usr/keylayout
root is required and obviously backup the files that get replaced for the shield, the moga ones should not have existing files and match the permissions to the other files that're in the folder
I've tested these moga files on an LG phone on 4.2.2 and the shield on 4.3
I've included a backup of the original files for 4.3 for the shield in the zip, but no idea if they'd be different under Kitkat though I don't see why they would be
Click to expand...
Click to collapse
I supposed that ir just a copy paste and remplace the files for the ones on the zip right ?, thanks for the info i agree with you, i hate the tegra zone button, nice idea man

what bothers me is that in some Gameloft Shooters like Nova 3 you aim and shoot with the bumpers instead triggers.
you think there is a way to change that without ****ing up other games?

psycho1200 said:
I supposed that ir just a copy paste and remplace the files for the ones on the zip right ?, thanks for the info i agree with you, i hate the tegra zone button, nice idea man
Click to expand...
Click to collapse
yes replace the existing files for the shield, the permissions should stay the same, just make sure they match the other files in that folder
what bothers me is that in some Gameloft Shooters like Nova 3 you aim and shoot with the bumpers instead triggers.
you think there is a way to change that without ****ing up other games?
Click to expand...
Click to collapse
if you swap them via this method it would change it for all games, something like tincore or gamekeyboard would let you switch for just 1 game, as they have profiles

Thanks!
Just wanted to say that I love having the select button useful in HID mode again, thank you so much as I had no idea how those layouts got set!

ciphray said:
yes replace the existing files for the shield, the permissions should stay the same, just make sure they match the other files in that folder
if you swap them via this method it would change it for all games, something like tincore or gamekeyboard would let you switch for just 1 game, as they have profiles
Click to expand...
Click to collapse
tried. Tincore doesn't do such thing and gamekeyboard does not detect the analog triggers.

nex86 said:
tried. Tincore doesn't do such thing and gamekeyboard does not detect the analog triggers.
Click to expand...
Click to collapse
if you're refering to the moga controller
if you use the .kl files from here that will make gamekeyboard detect the analog triggers, the reason game keyboard doesn't see them is they get assigned a random generic axis each time if they're undefined in one of the kl files
tincore is tricky to get used to how to setup, and a number of it's addons need to be purchased
it sets 2 different buttons to the triggers, both analog and digital, i think one set comes up as buttondead and as gas brake, make sure you set both of them, the profiles also need to be created while the game is loaded in the background if you want it to auto load with that game, otherwise it'll remove the profile when the game starts if you have auto profile switching enabled

No I was refering to the Shield Controller, not Moga.

nex86 said:
tried. Tincore doesn't do such thing and gamekeyboard does not detect the analog triggers.
Click to expand...
Click to collapse
I have the same exact issue - want to use triggers instead of bumpers. Can someone here either explain how to map the triggers or just upload a profile that already does?

delt31 said:
I have the same exact issue - want to use triggers instead of bumpers. Can someone here either explain how to map the triggers or just upload a profile that already does?
Click to expand...
Click to collapse
So I got it to work.
open tincore then minimize,
open NOVA or MC and then volume start volume and select open TKM editor
then scroll all the way down and under L1 and L2 select disable on the drop down
for R2 and L2 select click button joy 0
Then press check button then name the new profile and you're good. Make sure the profile is activated in order for it to work.
Only catch was that I had to pay in order for the new functionality to work. 2.75 well worth it now that I can use triggers for zoom and shoot!

Not recognizing the KL files after updating image
So I have a nexus 5 and was running the factory 4.4.2 image and these KL files worked great (the moga files). After updating to the new 4.4.3 image the device doesn't seem to load them. Anyone have any ideas? It's almost as though it doesn't know those files were put there, but I copied them over from a directory in the /sdcard with root explorer and updated the permissions just like I did originally.
Only oddities I can think of is that the OTA failed (I rooted but didn't flash the team win bootloader so OTA's could still work, update did work on my wifes rooted nexus 5) for me so I had to download the factory image and flashed the update without the -w flag so that it would keep my user partition.

tridium said:
So I have a nexus 5 and was running the factory 4.4.2 image and these KL files worked great (the moga files). After updating to the new 4.4.3 image the device doesn't seem to load them. Anyone have any ideas? It's almost as though it doesn't know those files were put there, but I copied them over from a directory in the /sdcard with root explorer and updated the permissions just like I did originally.
Only oddities I can think of is that the OTA failed (I rooted but didn't flash the team win bootloader so OTA's could still work, update did work on my wifes rooted nexus 5) for me so I had to download the factory image and flashed the update without the -w flag so that it would keep my user partition.
Click to expand...
Click to collapse
So after doing some more research it seems that the product code wasn't the same anymore. instead of 0dad it was 6271, so after renaming the vendor specific file to incorporate the correct product code, it worked again for me. I don't know enough about things to know why that would have changed, but before that rename it was just using the Generic.kl as it was before.
I got the code it wanted by adb shelling into the device and running a dumpsys input. One of the lines under the Moga had it's vendor and product code in it.

tridium said:
So after doing some more research it seems that the product code wasn't the same anymore. instead of 0dad it was 6271, so after renaming the vendor specific file to incorporate the correct product code, it worked again for me. I don't know enough about things to know why that would have changed, but before that rename it was just using the Generic.kl as it was before.
I got the code it wanted by adb shelling into the device and running a dumpsys input. One of the lines under the Moga had it's vendor and product code in it.
Click to expand...
Click to collapse
that's definitely interesting that the device portion would change, the triggers still work as analog? even windows gives the vendor id and device id as the 0dad one, only thing that comes to mind is maybe the newer version of android is seeing some other piece of hardware in the controller before the HID device and using that since the vendor portion isn't changing

ciphray said:
that's definitely interesting that the device portion would change, the triggers still work as analog? even windows gives the vendor id and device id as the 0dad one, only thing that comes to mind is maybe the newer version of android is seeing some other piece of hardware in the controller before the HID device and using that since the vendor portion isn't changing
Click to expand...
Click to collapse
Yeah, very weird. The only thing I can think of that I've done is that I have taken the controller apart. I was trying to see if there was any way i might make some adjustments to the d-pad. But other than taking the case apart and having the board being a bit on the free side for a bit, I didn't end up doing anything to the controller. It works fine as well, so I doubt anything I did could have changed that code.

Can the long press back button behavior be changed?
Would altering the kl files somehow make it possible to alter the long press behavior of the back button? When streaming Fallout 4, the Select button is the Back button on the controller. In the game you long press Select to bring up the workbench menu. As it is now, long pressing the button brings up the share menu on the tablet. The menu for taking screenshot and recording gameplay etc. I want to disable that somehow or change it from long pressing the back button.
Is that possible?

[Q] Key remapping issues

Hello,
So... I successfully remaped the left buttons to hardware Menu and Back buttons, but the top right is giving me headaches. It's set from 4 different places (Settings>Reader, NT Mod Manger, twl4030_keypad.kl file and from Cool Reader itself) to work as page back button, but it still turns the pages forward and I can't get what is forcing it to do so. I've tried to set it as a Menu button just from the twl4030_keypad file and it works as intended, but then again, when I set it to RIGHT_PREVPAGE it goes back to be a < button...
Any ideas how to fix this?

Anyone?
I've tried to bind PREVPAGE to the other buttons, but it doesn't seems to work at all. Am I doing something wrong or what?

Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.

nmyshkin said:
Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.
Click to expand...
Click to collapse
Thanks for the reply!
It turns out that Cool Reader f*cked up somewhere. I re-installed it before, but I didn't notice that my settings were saved, so I thought the problem was somewhere else. BTW, Cool Reader's button assignment options didn't work at all - something was overriding them. What crossed my mind now was to delete the .cr3 folder and that fixed my problem.
P.S. Aaaaaand the problem is back! And I didn't even touched the Key actions... Interesting.
P.P.S. Changing the tap zones is messing with my hardware buttons... oh well.
P.P.S. So, when I change the left middle tap zone from previous to next page it also changes my top right button. Mystery solved. Right middle is also bugged.