Hey,
Anyone with a fix using game controllers not working when the game does not support native mode?
The issue has been brought by A11 with some Accessibility issues but should have been fixed in A12 by Google. I still have this issue on 21.12.30. The controller is working just fine in native mode but if the game does not support native, I can not get any luck mapping the buttons.
I tried some stuff to turn off in Accessibility settings as it was advised with A11 but nothing works.
I'm using Gamesir X2 - USB-C / wired.
Anyone with a solution?
So it is not the ROM but Gamesir's own app I was using for the mapping.
Mantis Gamepad Pro Beta - Apps on Google Play
Play Games with ANY Gamepad. No-Ban. Google Play Login. On-Device Activation.
play.google.com
If you got any issue on a11/a12 mapping touch controls while native works just fine, this is the app for you. If wired won't connect, don't worry just follow instructions and do wifi.
Buy the Pro, thank me later.
The app and mapping also works on 22.1.19 Beta
Not working and I find why
There 3 versions of X2 : 2020, 2021 and LT (doesn't know what LT meaning)
2021 is working fine
2020 not
This is the same hardware but 2020 is blinking and 2021 is working fine
But doesn't know how to solve it
Related
Hi All,
I have a PS4 controller that I've been using between my Nexus 6 and Shield tablet using the Sixaxis Controller app. When my N6 got Marshmallow, Sixaxis stopped working and instead showed these errors when starting up
Code:
Could not load bluetooth library...
Error: Failed to configure bluetooth...
Could not load HCI library...
Some posts online said it might be because the app needed to request new permissions for api 23. I've tried decompiling, adding the permission, and recompiling with APK Studio. I also installed it as a system app. No change, still broken.
With no word from the Sixaxis dev months after 6.0's release, my question is: what would it take to write a Marshmallow-compatible Sixaxis alternative? I have some experience writing apps, but haven't touched JNI/NDK. Also, I've been doing some research on the history of Bluez vs. Bluedroid and it looks like there aren't really any equivalents to hcitool and hcidump for Bluedroid.
To clarify, the goal is only to get the controller to connect to the system. I'm not interested in the touch mapping, mouse emulation, or other extra features.
I'm interested in it too, don't know why no one ever replied. We can try to make an open sourced app.
Is there any document about the protocol used by PS3 controller? Seems like PS3 controller use some incompatible bluetooth protocol, I used Sixaxis app before, when I connected PS3 controller using BT, all other BT devices were dropped.
I am also getting this issue. No responses?
I have the same problem. any solution?
Yes please,not that I can help,but it'd be greatly appreciated.
Bump
Still nothing? It wouldn't be as bad but the native DS4 pairing mode sucks so bad on Android (Massive input delay after 30 seconds)
EDIT: Their website 404's... http://dancingpixelstudios.com/sixaxiscontroller/about.html
they are alredy working on it http://dancingpixelstudios.com/2016/02/05/migration-to-wordpress/
Love this app. I'm glad he still rocking. Google should just buy him out and implement this into their future OS... Give this man a job!
I am also having the same problem on HTC one m8 with gpe 6.0 rom.
Any news?
So far I have seen no update, but on his site he says he is working on it.
looks like there is no update for this
Is there any alternative available for this?
It' been months and still no update. Does someone know any alternative solution or app?
Hello,
Yesterday i've bought a wireless xbox 360 controller with wireless USB adapter. I tried it on my PC and it worked flawlessly - all games are responsive and auto-detect my controller. But it's a different story with my phone, i saw people connecting x360 controllers to their android devices too so i decided to do the same.
I own a Galaxy Note 5 (rooted, note7/S7edge port ROM & custom kernel). Before i've been using a cheap (~7$) controller, but most of the games did not recognize it, even if they did, the key mapping was really bad and not all of the buttons work.
When i connect the receiver through OTG cable to my Note5 and pair it with the x360 wireless controller, it keeps flashing (it is paired), but the phone does not recognize it - i cannot interact with the screen using the controller buttons (although with mouse/keyboard/cheap-controller it works).
I found out that i only had a USB wired xbox360 controller .kl and .kcm files in /system/usr/keylayout and keychar folders, so i found some guides -> i copied these files (changed the product number to Wireless X360 controller's) using "Terminal Emulator for android" with super user access and gave them specific permissions (chmod 644). I also checked if the permissions were granted ("ls -l" command) and restarted my phone. According to all of the guides, it should work after these steps but i still can't use the controller - it keeps flashing and is not recognized. Are there other steps/guides or maybe something i should know about Galaxy Note5 and Xbox 360 wireless controller connection?
I'm really desperate after 0% of success. Any help would be greatly appreciated!
EDIT: I just checked this setup with my old HTC One M7 and it worked from the first time. I really would like to hear that it is also possible with my newer Note 5 :/
I solved it!
!!! I SOLVED THE PROBLEM AND MADE MY GALAXY NOTE 5 NATIVELY SUPPORT XBOX360 WIRELESS CONTROLLER !!!
(S6 & S6 EDGE & S6 EDGE PLUS INCLUDED & AND BY NATIVE I MEAN WITHOUT ANY KEYMAPPING APPS LIKE USB/BT)
And now to everyone who has a Samsung Galaxy Note 5 and have problems connecting Xbox 360 USB or Wireless controller, i would like to share my solution, just to save time for some people with a similar problem.
If you have an older device, it's easy and there are many tutorials out there, but for people like me that have a newer Samsung's smartphone like Note 5, S6/edge/active etc. there is one thing you need to know - these devices no longer have native support for wireless xbox360 controller. After hours of searching, testing keymapping applications, editing system's key input files, creating and exploring them, i tried to install xbox360 driver module by myself, but my system (through Terminal Emulator) would not let me do that. After all that "trying" to make it work and some more googling i found out that the problem actually is not here. The real problem is the Kernel. The Kernel is the thing that controls everything on your device. So, i spent a couple of minutes searching for a Kernel that has full xbox 360 support and i came up with arter97's Kernel (I will post links in the end). A fact worth mentioning is that i have a Note7 Port ROM installed on my Note5 and that was where i made a mistake, i soft bricked my Note7. Before i've been using Minotaurus V10 custom ROM and Infinity v1.0 Kernel. Important info: I updated only my Kernel and left ROM, my data and apps untouched. At the first try i downloaded arte97's Kernel for the Note5 (n920cig) and soft-bricked the phone, i let it boot up, but that took ~35mins and was still loading, i couldn't turn off my phone (solution: there was samsung logo on the screen flashing and power button didn't work > i was able to enter download mode > select "No" which leads to reboot my phone > from there enter recovery and restore backup i've created before using TWRP recovery - that's how you un-soft-brick your phone). After this accident i found that the arte97 has a specific Kernel edition for galaxy Note5 that has Note7 Port rom installed, which was my case, so i gave it another shot, downloaded the Kernel (-N7/Grace UI Port'ed edition for N5) and the first boot-up took around 2-3minutes. The device works just like before switching Kernels, fast and smooth. Time to test the xbox360 controller - BOOM! it connects instantly allowing me to interact with the screen (using microsoft xbox360 wireless controller & official microsoft xbox360 USB receiver). I open up the game (Riptide GP2) and everything works without any adjustments, i checked the controls, the game automatically shows the image of a x360 controller. I also had "Dead Trigger 2" installed - same story, i can assign any button to do any action in the game. I've finally achieved what i was trying to do!
Here are the links i've been using:
My OS: https://forum.xda-developers.com/note5/development/rom-minotaurusrom-v1-note7-port-t3461731
Arter97's Kernel with native xbox360 controller support (I upgraded my Note5 to the v22.0 version):
XDA-Developers page: https://forum.xda-developers.com/note5/development/arter97-kernel-galaxy-note-5-t3189907
Official page (there is a link to this page in the xda page): arter97's Android studio
I have also have had these files installed on my phone before changing kernels (Vendor_045e_Product_0291 = wired x360 controller, Product_0719 = wireless, so i've created a .kl file with number 0719 and i downloaded a key character mapping file for x360 wireless, which ends with .kcm):
https://forum.xda-developers.com/showthread.php?p=29232978#post29232978
Before changing Kernels i made it work using USB/BT app. All the buttons were working using an older version of USB/BT, but the problem was that it was not comfortable enough for me (having to change keyboard every time & stick directions are registered as buttons, so in first person shooting games you can't aim slowly, it always goes at the same fast speed). If you are like me and want to use xbox360 wireless controller like "plug and play", you gotta check this thing with Kernels (^^), if you don't want to risk and think the emulator will be OK, i will leave a link to a USB/BT Joystick center tutorial bellow. (The guy in the video is using Galaxy S6 active, but my Note 5 also worked, so any other S6 will work)
https://youtu.be/I9fvLZMd9bE
Hope this helps!
Also tested Minecraft, Game of Thrones & The Walking Dead by Telltale and GTA: San Andreas - all games work with the wireless xbox 360 controller from the 1st try without any adjusting and the controls are 1:1 just like using my xbox360 console.
I know this is quite a while ago and I'm trying to get my Xbox remote to work on my android. So far Arter's kernel is the only one I see with support for the Xbox controller. Unfortunately I'm on nougat rom and the arter kernel only supports marshmallow. So now I'm stuck. You didn't by any chance see a kernel for the note 5 nougat?
Seems like arter's kernel has stopped being updated
WarSquirrel said:
I know this is quite a while ago and I'm trying to get my Xbox remote to work on my android. So far Arter's kernel is the only one I see with support for the Xbox controller. Unfortunately I'm on nougat rom and the arter kernel only supports marshmallow. So now I'm stuck. You didn't by any chance see a kernel for the note 5 nougat?
Click to expand...
Click to collapse
Luckily Android Central informs me about my posts via e-mail. I am sorry, i haven't seen a nougat kernel with x360 module installed. I'm still rocking a 6.0.1 marshmallow with arter's kernel + minotaurus V10 rom and they together work flawlessly - minotaurus rom has so much customization abilities that i didn't even think about upgrading to a newer OS as there are none that provide such huge amount of variety.
You can try searching not only for a kernel with x360 drivers already installed, but you can look for specific ROMs that come with their own kernel (which would have xbox360 drivers on it). That's the only recommendation i can give you right now.
ThomasKKKK said:
Luckily Android Central informs me about my posts via e-mail. I am sorry, i haven't seen a nougat kernel with x360 module installed. I'm still rocking a 6.0.1 marshmallow with arter's kernel + minotaurus V10 rom and they together work flawlessly - minotaurus rom has so much customization abilities that i didn't even think about upgrading to a newer OS as there are none that provide such huge amount of variety.
You can try searching not only for a kernel with x360 drivers already installed, but you can look for specific ROMs that come with their own kernel (which would have xbox360 drivers on it). That's the only recommendation i can give you right now.
Click to expand...
Click to collapse
True. I also used the minotaurus before and it was an awesome rom. But I was having tons of restarts and issues with magisk so I went up to nougat to sort it all out. Eventually, as you learn, you understand what was the issues and all. I actually still have the minotaurus rom on my pc. I should consider swapping back to mm maybe. Using a controller for games would make a massive difference. Well thanks for reply and info! Appreciate it. I did ask some of the other kernel creators if they would include a module for the controller. Let's hope they do!
Hi guys,
I have the international samsung note 9 (root with magisk) which I am trying to get AA Mirror to work.
I have tried 5-6 different walkthroughs and troubleshooted myself.
I have a 2016 Merc cla 45 Amg.
I treid;
AA Mirror
AA Mirror plus
Aa Unlock
Aauto app enabler
AA phenotype patches
SQlite installer for rooted devices
Second screen to reduce phone dpi
I can get car stream to work just fine. But the phone screen sharing (aa mirror) seems not to workproperly.
The app shows up on the andriod auto screen, and when I use aa mirror plus i can launch apps from my car and hear music through the entertainment system. Just the video wont display from the phone to the car.
Note I'm using the latest andriod auto, google play and google services as of May 2019.
Any thoughts of what I can try?
That's a nice phone dude
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Can you upload those aps somewhere for us?
Sent from my K10 using Tapatalk
GalaxyNote9Mark said:
Hi guys,
I have the international samsung note 9 (root with magisk) which I am trying to get AA Mirror to work.
I have tried 5-6 different walkthroughs and troubleshooted myself.
I have a 2016 Merc cla 45 Amg.
I treid;
AA Mirror
AA Mirror plus
Aa Unlock
Aauto app enabler
AA phenotype patches
SQlite installer for rooted devices
Second screen to reduce phone dpi
I can get car stream to work just fine. But the phone screen sharing (aa mirror) seems not to workproperly.
The app shows up on the andriod auto screen, and when I use aa mirror plus i can launch apps from my car and hear music through the entertainment system. Just the video wont display from the phone to the car.
Note I'm using the latest andriod auto, google play and google services as of May 2019.
Any thoughts of what I can try?
Click to expand...
Click to collapse
Same problem here with s8+. Having a VW Golf as a car. Anyone any ideas?
This problem ist caussed by the App himself. I can't watch PrimeVideo, Netflix. But I can watch YouTube so the problem ist caused by the App.
Hi Guys,
I have problem with my pocophone native cast app, it does not detect my android tv which i just bought online few days ago. Im pretty sure the problem is not in the tv since i tested it to connect with my other phone and cast connected just fine. I also tested some other tv on the electronic store, my pocophone also did not detect several other brand on the store while the rest tv like samsung and lg connected just fine.
I googled this issue and found the alternative of using app called activity launcher then launch the android native casting app (wireless display) and it detect my tv but its quite laggy and i cannot turn off the screen while casting like i did in miui casting app.
I wonder if any of you face the same issue and anyone can figure it out? Im running the latest miui 11 global stable anyway.
Thanks before.
SMGhufron said:
Hi Guys,
I have problem with my pocophone native cast app, it does not detect my android tv which i just bought online few days ago. Im pretty sure the problem is not in the tv since i tested it to connect with my other phone and cast connected just fine. I also tested some other tv on the electronic store, my pocophone also did not detect several other brand on the store while the rest tv like samsung and lg connected just fine.
I googled this issue and found the alternative of using app called activity launcher then launch the android native casting app (wireless display) and it detect my tv but its quite laggy and i cannot turn off the screen while casting like i did in miui casting app.
I wonder if any of you face the same issue and anyone can figure it out? Im running the latest miui 11 global stable anyway.
Thanks before.
Click to expand...
Click to collapse
I have the same issue. I guess its a long known issue according to various telegram sources and it seems Xiaomi is working on it
Pratik Shirodkar said:
I have the same issue. I guess its a long known issue according to various telegram sources and it seems Xiaomi is working on it
Click to expand...
Click to collapse
So it is a miui bug? Did they officially said that they will fix it?
Glad to know this before i do a factory reset for vain anyway.
For whom is this module?
This is for SHIELD TV users who can or do not want to use the original SHIELD TV controller for GeForce NOW gaming and miss haptic feedback with 3rd-party controllers (e.g., DualSense).
What do you need?
A 3rd-party controller that is compatible
An up-to-date (to-be) unlocked SHIELD TV with Android TV 9-11
For remote support, a USB Bluetooth dongle such as 8bitdo Wireless Adapter (until Android TV 12 is available)
I'm in - how to get it?
To check controller compatibility, install the attached APK, open it and test your controller setup whether it supports rumble with the Android Vibrator API
If it works, continue unlocking the device and installing Magisk root support (if not done already)
Install the latest version of LSPosed with Magisk
Enable this module in the LSPosed module manager, select the GeForce Games app as target (just as recommended by default) and reboot
Enjoy
I recommend using a launcher app for non-leanback apps to access Magisk and LSposed. Moreover, either a hardware mouse or a smartphone-based Android TV Remote with a virtual mouse (e.g. this app) will be helpful for navigating the apps.
How does it work?
NVidia don't use the native Vibrator API for haptic feedback. Instead, they have integrated their own API for their own accessory and their own accessory only. The inputs from other devices are accepted natively but they do not enable the haptic feedback, so the servers don't even send haptic packages unless the SHIELD TV controller (2017) is connected. This module hooks into the enabling method and sends the message to the server that haptic support is provided. This allows hooking to the haptic-package-receiving methods and redirecting their content to the InputManager devices.
What are the limitations?
Beginning with Android 12, there will be a native VibrationManager API and a HapticFeedback sound-based generator available that add native Bluetooth drivers and support for 3rd-party controllers. This will make the requirement for USB dongles redundant and even add extended haptic feedback support. The haptic packages from NVidia servers include low and high-frequency motor amplitudes. However, the Android 9-11 Vibrator API only accepts a single amplitude. This means that the haptic experience will be limited to a single amplitude because both amplitudes have to be merged. Due to the lack of native Bluetooth drivers and API support in Android 9-11, I see no way of getting Bluetooth compatibility without USB dongles or USB connection. NVidia might update its apps in the future, which might require module updates as well. In parts, the hooks depend on obfuscated/minimized method and class identifiers, which is weakly coupled and susceptible to changes. But overall, the Xposed module support allows Google Play updates to continue fluently. After an update, the only interaction that will be necessary is a system reboot and the hooks will be redeployed. If it should stop working, simply disable the module in LSPosed and reboot. The module will only affect the GeForce Games app and not the system or any other apps. Multi-controller setups aren't tested thoroughly. The Nvidia controllers probably receive separate rumble feedback but it's possible that the 3rd-party controllers, if connected, rumble at the same time. When 3rd-party controllers are used for input, Nvidia controllers shouldn't rumble, connected or not. Please let me know how it works for you. Full multi-controller support might be an option if I can map the id or index from the haptic packages to the native controller ids.
md5: B01301D858C7F24335C0CD50B430E6C9
sha1: F2309B55D9BB00E35E92BB1C59313E1F6D50AA3D
Spoiler: Changelog
Update 2022-03-12 - 1.4.0:
removed debug logging
fixed compatibility with version 5.46.31061641
increased idle timeout
Update 2022-05-03 - 1.4.1:
fixed compatibility with version 5.48.x
Update 2022-06-11 - 1.4.2:
fixed compatibility with version 5.49.x
Update 2022-06-11 - 1.4.3:
fixed compatibility with version 5.50.x
no update is necessary for version 5.51.x
Update 2022-10-14 - 1.5.0:
fixed compatibility with version 5.52.x
Update 2022-10-31 - 1.5.1:
fixed compatibility with version 5.53.x
Due to NVidia's refactoring and stronger obfuscation from version 6.x onwards, I can't provide any further compatibility updates.
I would just try to stick to the old 5.x version, if possible.