Related
I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
I agree that the Cube looks pretty basic (that's why I won't put it on my phone, but I do have the TouchFLO).
But what I'm looking for is for the phone to do a very quick vibrate whenever the screen is touched.
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
worth a shot
vaxick said:
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
Click to expand...
Click to collapse
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
ryanshepherd said:
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
Click to expand...
Click to collapse
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
whiteblazer01 said:
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
Click to expand...
Click to collapse
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
steps said:
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
Click to expand...
Click to collapse
Voyager is hella gay
[email protected]$ said:
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
Click to expand...
Click to collapse
Great Idea [email protected]$, deffinately move forward with it, Ive been using the phonepadvibrate (essentially the same as what you posted) for well over 2 months now and love it. If you could do the same with the normal touch screen it would be amazing.
Yes its not full haptics, but in my opinion it really doesnt need to be. some sort of physical feedback (ie a slight vibration) would be great when working with the touch screen.
[email protected]$ said:
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
Click to expand...
Click to collapse
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
whiteblazer01 said:
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
Click to expand...
Click to collapse
It is very possible. I found other sources and they have some sort of program / prototype that can make this happen but it doesnt work on every tap of the screen.
What I want to do is make mine work on every tap of the screen but have the ability to turn it off and on to save power. Like turning the notification for the sound to play when you tap the screen on and off.
So far I have planned some steps to do it through the registry but since I am not an expert at programming like others are here it might take a while.
But any help is very welcome to complete this project and make it available for all.
As to changing the LED's on your phone. I think no2chem and some other guys found a way to customize your LED settings, but I'm not sure if it will be custom enough to indicate caps or shift. Maybe in the near future.
whiteblazer01 said:
I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
Click to expand...
Click to collapse
this is a oem out there i havent seen Cab for it
Dc_striker said:
this is a oem out there i havent seen Cab for it
Click to expand...
Click to collapse
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
[email protected]$ said:
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
Click to expand...
Click to collapse
i still havent tried the program out yet i really dont see the use for it
Let me know what you find out Carlos. I would agree with you that it may be better to have the phone vibrate maybe when any button is pushed instead of anytime the screen is tapped (or maybe have the option to choose?), and also have the option to turn it off. Lol, maybe we can call it "Taptics" instead of Haptics.
As for the LED's, I'll check with some of the other guys about what they can do. I do a lot of modding myself with other electronics (cars, motorcycles, game consoles, etc...), but I don't really get into programming all that much (although the logic makes sense to me).
-Paul
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
whiteblazer01 said:
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
Click to expand...
Click to collapse
I am not sure for all buttons but there is a CAB to make the phone vibrate when you press the screen. I tried it out and it works, but it's faulty and kills performance.
I'm still working on this project. I haven't had much time to work with it, but if any break through happens then I will post it up.
Hi,
I wish I had the knowledge to create such an application, but I don't so I'll try to explain this idea as clearly as I can see if someone finds it interesting enough.
As you know some phones already have the built-in feature to turn OFF the screen when a call is established. This prevents accidental actions with your cheek and ear on the touchscreen.
Some phones have fancy sensors like light sensor and proximity sensor.
But many other phones don't have, so this tiny app would be very useful to all of them:
How should it work?
Very simple:
1. Detect when a call is established
2. Call the "Turn OFF screen" command (same as pressing the power button)
That's it.
This would be exactly like pressing the power button after call is connected, so there wouldn't be incompatibilities with other apps. Plus the phone behavior when call is finished would be the same as always, since it only called the same command as power button.
This tiny app then could be cooked inside many ROM's.
Well, it's very easy explained like this, but as I said, I don't have the knowledge to do it myself
If you feel like programming the app I will gladly be your tester (or should I say guinea pig? )
+1
Having the problem with accidental touching the buttons and so fort pausing or hanging up a established Call.
+1
Add the functionality of turning the screen back on after the call is dis-connected and I'm sold
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
longice said:
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
Click to expand...
Click to collapse
Thank you!
Although I have an Elf, and it's got no G-sensor and no light sensor, so it won't work on my device
But it's pretty close to what I'm looking for! Thanks!
Is there really no way to disable the "Green" "Home" "Left arrow" and "Red" button when I'm in a call.
Ive tried to disable the buttons with AEB-plus, but it still doesn't work while Im in a Call.
Is it just me that have the problem with time and time Pausing or Hanging up established calls, "thanks" to the "Hardware" buttons.
PS
Using Touch HD
hi everyone one of the major problem is with xperia s i the capasitive keys arent very responsive sometimes have to press twice,and more.
is there actually a way to improve is it rom or kernel related can it be fixed by kernel tweaks. i know many of you say will get used to it its just pain in neck
Don't press, swipe!!!
Mano1982 said:
Don't press, swipe!!!
Click to expand...
Click to collapse
was xperia s design that way not pressing!
Mano1982 said:
Don't press, swipe!!!
Click to expand...
Click to collapse
Thank you very much. I couldn't have figured it out :-D
Sent from my LT26i using xda premium
what a nonsense! swipe well how do you get to recent apps by swiping! you meant to long press. my question was any solution as (kernel) not to workaround it. it was never designed to work swipe it was designed to work by press, and it does not!
I removed the screen protector and it did improve the touch sensitivity considerably.
defsix said:
I removed the screen protector and it did improve the touch sensitivity considerably.
Click to expand...
Click to collapse
does it really?
I think so, I did the same with my Arc and Tablet S . Improved response and not so much a dust magnet
cihanleanne said:
what a nonsense! swipe well how do you get to recent apps by swiping! you meant to long press. my question was any solution as (kernel) not to workaround it. it was never designed to work swipe it was designed to work by press, and it does not!
Click to expand...
Click to collapse
Swipe actually works fine for the recent apps. Just stop on the dot and wait.
Personally, I find the swipe motion easier then aiming for the silly dot. Never had issues since starting to swipe rather than press. But that's just me.
For me it works when pressing above the dots, not directly at the dots (about halfway from the dots to the display).
Also, I can press anywhere near the dots when using the whole thumb instead of only a fingertip.
so what you saying we cant increase sensivity with kernel
cihanleanne said:
so what you saying we cant increase sensivity with kernel
Click to expand...
Click to collapse
This is typically a hardware restriction. No software changes could possibly enhance the touch sensitivity. These dots weren't made like other Androids' capacitive buttons.
Correct me if I'm wrong though, but to me it doesn't seem possible
Hermantje said:
This is typically a hardware restriction. No software changes could possibly enhance the touch sensitivity. These dots weren't made like other Androids' capacitive buttons.
Correct me if I'm wrong though, but to me it doesn't seem possible
Click to expand...
Click to collapse
you right thanks
when you flip the screen the mouse will still act as if the screen was not flipped
so moving left and right is actually done by moving up and down
very confusing please fix this thanks
Yep, mouse movement processing "doesn't flip" with the screen Sure needs fixing
Sent from mobile
Vioner said:
Yep, mouse movement processing "doesn't flip" with the screen Sure needs fixing
Sent from mobile
Click to expand...
Click to collapse
Do you have an issue tracker we could use to report/monitor this issue (and others)?
I think this can't be fixed easily unless some sort of emulation occurs. I mean, our mouses were not made for flippable screen. So we need to change mouse movements according to our orientation.
@modaifallah all that needs to be done is "flipping" the input from mouse to PC respectively to the screen flip. This should be easy to do. I'll see what Jide team thinks about this.
@gcscaglia New feedback system is coming very soon!
UPDATE 12/21: Fixed, see thread: https://forum.xda-developers.com/ro...ide-asus-kunai-fixes-analog-drift-m1-t4023115
--------------------------------
Kunais definitely have an issue when moving both analogs simultaneously so I've tested EXTENSIVELY and have beaten my sticks to a pulp. If you move one at a time, no matter how hard you go at it, it won't get stuck, but as soon as you move both simultaneously (as anyone would do), that's when it starts going bonkers.
The sticks have no issues when used seperately.
So here is an interesting fact, when disconnecting the left Kunai, the right controller stops altogether. If removing the right side, the left Kunai still works. Also, the left has 3 rows of contact pins, the right has 2.
This tells me the left one should be the "master" of the two and yet, the USB-C is on the right.
Another fact, since these controllers clearly have no communication components (BT and/or Wi-Fi) the input data must travel through most likely a very thin copper wire that is embedded somewhere in the flexible back panel of the case... I'd assume there is one that goes from right to left and then another one from left to right, without looping.
Which brings me to what is definitely the scary part... The problem seems physical... If the data cable is too thin/too long and causing this issue, it will be a nearly impossible fix without damaging the case... Or, it is a software issue which seemingly bottlenecks input data and halts for a second but somehow, I doubt that because if that was the case, right side buttons as well as the right stick could get "stuck".
As it turns out, if you rotate the left stick and push buttons on the right side, a button can indeed get stuck.
Tl;dr - Does anybody have the center part to do some testing?
I feel like that piece is the key to understanding if it's a software conflict or hardware issue.
WhyKlwd said:
Kunais definitely have an issue when moving both analogs simultaneously so I've tested EXTENSIVELY and have beaten my sticks to a pulp. If you move one at a time, no matter how hard you go at it, it won't get stuck, but as soon as you move both simultaneously (as anyone would do), that's when it starts going bonkers.
The sticks have no issues when used seperately.
So here is an interesting fact, when disconnecting the left Kunai, the right controller stops altogether. If removing the right side, the left Kunai still works. Also, the left has 3 rows of contact pins, the right has 2.
This tells me the left one should be the "master" of the two and yet, the USB-C is on the right.
Another fact, since these controllers clearly have no communication components (BT and/or Wi-Fi) the input data must travel through most likely a very thin copper wire that is embedded somewhere in the flexible back panel of the case... I'd assume there is one that goes from right to left and then another one from left to right, without looping.
Which brings me to what is definitely the scary part... The problem seems physical... If the data cable is too thin/too long and causing this issue, it will be a nearly impossible fix without damaging the case... Or, it is a software issue which seemingly bottlenecks input data and halts for a second but somehow, I doubt that because if that was the case, right side buttons as well as the right stick could get "stuck".
As it turns out, if you rotate the left stick and push buttons on the right side, a button can indeed get stuck.
Tl;dr - Does anybody have the center part to do some testing?
I feel like that piece is the key to understanding if it's a software conflict or hardware issue.
Click to expand...
Click to collapse
You are correct, it only happens when using the two jousticks together connected to the phonr case. I have the controller dock and when using it via bluetooth, I am not getting the same issues, i can use both sticks at the same time no problem.
Can we raise this issue to asus? And hopefully it is a software issue which can be fixed via an update.
And just a tip, when you have it on bluetooth mode connected or even the left controller mounted to the phone case, you can also use other gamepads and with the touch control maping. I'm using it together with my xbox one controller this way.
Thanks for your reply @navydragon ! That confirms a thing at least. I would assume that the controller behaves the same while in handheld/controller mode. Not guaranteed mind you.
I am about 90% sure that the case to attach the Kunais run a thin cable, most likely a non-shielded copper one that is protected by the thin sheet of flexible rubber where the phone sits. It can be unglued from the case, which I have not done entirely everywhere but if we feel it slowly with our fingers, we can sort of feel there is a little, otherwise not noticeable, little bump running under that sheet.
That could also be what's causing the issue and quite frankly, I think it is really what is at play here. There is no situations where I couldn't reproduce the glitch BUT by bending the case while trying, it does seem to increase/decrease the frequency or time it takes to create it.
Thanks again for your inputs @navydragon!
Kunai Lag
Youtube video demonstration
[yt]/watch?v=dJfz0UetpuM
My kunai seems to be messed up
Regardless of the game I play, the right kunai controller seems to be broken or something
It's like it gets stuck with buttons being held down
Example, playing Free Fire, I shot my gun, let go of the trigger, yet it keeps firing the gun
I try to turn the camera, the camera keeps turning after I let go??
Call of duty, same issue, it's like the right analog stick is stuck down or something when it isn't
It also seems like half the time I try to aim and the right analog stick doesn't work?
What the hell is going on?
The "lag" seems fixed in the latest CN firmware, I haven't installed the WW firmware yet but I'd assume it fixed it as well. Essentially, the 1.3.9 firmware version for the gamepad will flash on the controller and it fixes the issue.
WhyKlwd said:
The "lag" seems fixed in the latest CN firmware, I haven't installed the WW firmware yet but I'd assume it fixed it as well. Essentially, the 1.3.9 firmware version for the gamepad will flash on the controller and it fixes the issue.
Click to expand...
Click to collapse
Hand/Foot cam of it in action
youtube/watch?v=Up9Qm9qUbgc
Edit: Just got the new firmware, testing now
WhyKlwd said:
Thanks for your reply @navydragon ! That confirms a thing at least. I would assume that the controller behaves the same while in handheld/controller mode. Not guaranteed mind you.
I am about 90% sure that the case to attach the Kunais run a thin cable, most likely a non-shielded copper one that is protected by the thin sheet of flexible rubber where the phone sits. It can be unglued from the case, which I have not done entirely everywhere but if we feel it slowly with our fingers, we can sort of feel there is a little, otherwise not noticeable, little bump running under that sheet.
That could also be what's causing the issue and quite frankly, I think it is really what is at play here. There is no situations where I couldn't reproduce the glitch BUT by bending the case while trying, it does seem to increase/decrease the frequency or time it takes to create it.
Thanks again for your inputs @navydragon!
Click to expand...
Click to collapse
having the same issue, check out my thread https://forum.xda-developers.com/showpost.php?p=81263745&postcount=3
It's honestly ruining my gaming experience
Asentrix said:
Hand/Foot cam of it in action
youtube/watch?v=Up9Qm9qUbgc
Edit: Just got the new firmware, testing now
Click to expand...
Click to collapse
Let us know if it is fixed in the new firmware and let me know what firmware so I can fix this issue too please.
Guide ASUS Kunai Fixes (Analog Drift + M1 as Start / M2 as Select) **ROOT only**
Hello everyone,
I made this thread to address two common issues that some may encounter with the Kunais. Unless there is ever an external updater released by ASUS, the known way to fix the "Right Kunai getting stuck" when in Handheld mode is to either update to CN .63 or WW .64 (it is to be assumed that later revisions should also fix that). When you first boot any of these 2, you'll be greeted with a firmware update for your accessory once connected.
The update should be 1.3.9, that will fix the right side having "stuck buttons" or the "analog drift" that occurs while using the Left side analog. From my personal testing, I was able to rollback to an older firmware with the problem no longer occuring, as long as the accessory was updated to 1.3.9 firmware.
As for the M1 and M2 buttons located behind the Kunais, when using the central unit, they can be used as extra buttons. When used in handheld mode, the hardware values leave you with two buttons that, yes can be mapped, but do not natively act as Select nor Start. That can be a problem in games/programs such as Stadia, Moonlight, or anything that do not let you remap in the software itself.
This can be fixed but will require root access. Assuming that you do:
-open up Root Explorer (quick Google search for "Root Explorer apk" if you don't have it and install that)
-once in Root Explorer, go to the root folder and click on "Mount R/W" it should change to "Mount R/O"
-Go to folder /system/usr/keylayout/
-Hold click on file "Vendor_0b05_Product_4500.kl" and make a Copy in the same folder
-It should create a copy, rename it to "Vendor_0b05_Product_7900.kl"
-Click on file you just renamed and pick "Text Editor"
-Add another blank line under "key 318..."
-Type "key 264 BUTTON_START"
-Enter another blank line
-Type "key 265 BUTTON_SELECT''
-Click on 3 dots top right and choose "Save and Exit"
From there, you can disconnect AND reconnect your Gamepad and your M1 and M2 buttons should now behave as START and SELECT respectively as would any BT gamepad.
If for any reason, that does not work, it is possible the your Kunais revision bears a different Vendor and Product ID. In such case, I would recommend getting any free Gamepad Tester program from Play Store and when testing, most if not all, should give you the name, vendor ID and product ID of your hardware being tested. If these numbers are different than the values in this guide, simply swap the values of the .kl file and that should work.
Cheers!
iBluesurge said:
Let us know if it is fixed in the new firmware and let me know what firmware so I can fix this issue too please.
Click to expand...
Click to collapse
Made a thread there, I can confirm that it is fixed, plus I covered how to fix M1 and M2 not behaving as Start/Select respectively. Cheers!
Your method works to reassign m1 and m2 into start and select, but unfortunately it makes left and right triggers into some key representing (|) for both. If there is a way to fix this then your method would be great. I tested it in a gamepad tester.
Left and right trigger register as key 313 in the gamepad tester.
iBluesurge said:
Your method works to reassign m1 and m2 into start and select, but unfortunately it makes left and right triggers into some key representing (|) for both. If there is a way to fix this then your method would be great. I tested it in a gamepad tester.
Left and right trigger register as key 313 in the gamepad tester.
Click to expand...
Click to collapse
That 313 trigger seems to come from "Keyboard" if anything, I'd assume whichever game you ran tests with probably has AirTrigger or a Gamepad Mapping still functional because that Keyboard trigger for 313 would most likely be something mimicking the touchscreen OR some BT device. But for reference, that is what my .kl looks like.
# Asus Gamepad
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 265 BUTTON_SELECT
key 264 BUTTON_START
key 158 BACK
key 172 HOME
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
WhyKlwd said:
That 313 trigger seems to come from "Keyboard" if anything, I'd assume whichever game you ran tests with probably has AirTrigger or a Gamepad Mapping still functional because that Keyboard trigger for 313 would most likely be something mimicking the touchscreen OR some BT device. But for reference, that is what my .kl looks like.
# Asus Gamepad
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 265 BUTTON_SELECT
key 264 BUTTON_START
key 158 BACK
key 172 HOME
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
Click to expand...
Click to collapse
Would you be willing to show me that left and right trigger still function for you on a gamepad tester? Also I copy and pasted what you have shown and it still shows a keyboard key for left and right trigger in the gamepad tester.
Is it possible to change the right analog sensitivity using this method?
iBluesurge said:
Would you be willing to show me that left and right trigger still function for you on a gamepad tester? Also I copy and pasted what you have shown and it still shows a keyboard key for left and right trigger in the gamepad tester.
Click to expand...
Click to collapse
Uh....That's interesting, it wasn't registering as button 312 and yet, now it does... Both L2 and R2 does it. I'll have to dig deeper and see what causes that but yeah, it seems you are right, there must be a trigger of some kind.
UPDATE: You are absolutely right, it breaks the mapping. I'm working on fixing it, if not in the next hour, it'll be updated in the next 12hours.
Hello, I've tested the WW .64 firmware, and I can confirm that it really fix the issue with the right controller. But im also encountering right now an issue with the right analog. When i gently press the right analog to the left and let it go, it seems like the input doesn't properly go back to the center. I've already tested with the holder directly connected to the phone and it doesn't occur. Can you please also test if it is also happening to your controller? Thanks
@xenken: I might be too tired to read this properly but at least when trying to recreate your conflict, I haven't had any issues as you seem to encounter, but I'll try again tomorrow.
Alright, I will make edits for the guide tomorrow cause right now, I'm exhausted and my bed is calling me. That being said, here is an edited .kl which is, so far, the best compromise I found. All keys work and have values that they should, L2 and R2 can now be mapped independently in ASUS's software but SELECT (M2) does not map any longer.
I get the feeling that some HEX path overlap between keys and is what causes the conflict, I tried many alternatives to no avail.
EDIT: This should be my last edit, I cleaned up what's in the quote. If you copy that precisely, all buttons will behave as expected AND all but "Select" will be mappable in Key Mapping software of ASUS. I've tested in native apps like Retroarch, Minecraft, Moonlight, Stadia App, Stadia through Chrome, PStreamer, etc... Enjoy!
# Copyright (C) 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Asus Gamepad
key 264 BUTTON_START
key 265 BUTTON_SELECT
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 312 BUTTON_L2
key 313 BUTTON_R2
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
Click to expand...
Click to collapse
WhyKlwd said:
@xenken: I might be too tired to read this properly but at least when trying to recreate your conflict, I haven't had any issues as you seem to encounter, but I'll try again tomorrow.
Alright, I will make edits for the guide tomorrow cause right now, I'm exhausted and my bed is calling me. That being said, here is an edited .kl which is, so far, the best compromise I found. All keys work and have values that they should, L2 and R2 can now be mapped independently in ASUS's software but SELECT (M2) does not map any longer.
I get the feeling that some HEX path overlap between keys and is what causes the conflict, I tried many alternatives to no avail.
Click to expand...
Click to collapse
Is this working for xcloud? if so i may have to root my phone or wait for ASUS to fix m1 m2 as start and select which idk if they would ever fix haha
Kunai and mobile desktop dock
Hello everyone! I've got both accessories and they're driving me crazy. I tried to make them work with cod mobile and and the perspective function seems dead. In the main menu when I use the kunai right analog the character moves but in game it's completely dead. When I use the mouse with the dock it goes completely crazy, it stops working every 2-3 seconds. I tried both accessories with pubg and had no issues it works perfectly. Tried to check the Asus forum but no success. If anyone knows the problem and can help me it'll be very nice. Thanks ?
Cod mobile doesn't support Asus Rog 2 kunai gamepad.. Actually COD mobile doesn't support any type of gamepad. That's y you r having this issue. Its not a problem with Asus rog 2.
Sent from my ASUS_I001DE using Tapatalk