Latest OneUI update for S20+ has broken the BUTTON_MODE input on controllers. It now incorrectly calls on Android's HOME command.
Controller .kl files are correct, it's a system level issue. Worked correctly before OneUI update.
For example: before OneUI update, pressing the PS button on the DualShock4 controller while using PlayStation Remote Play app would pass the BUTTON_MODE input to the remote play app and open my PlayStation dashboard in the app (intended behavior). After the last OneUI update, if I press that button on my controller it will now yank me entirely out of the app to phone's home screen.
Again, I checked the controller's .kl file in the root system directory and it still correctly shows BUTTON_MODE for button 316.
Happens with other controllers as well, like the Razer Kishi which is directly connected via USB-C. Never had this issue before last OneUI update.
Please roll this back to the previous functionality. When using a controller we want the controller to pass the inputs to whatever we are using at the time, we do not need or want it to perform phone system functions. All buttons are required to pass the input when using Playstation, Xbox, or Stadia remote play services. I don't want ANY buttons to control my phone functions. At least give us a section in the settings to toggle these things if you aren't going to remove it.
Also - please don't reply to me with a bunch of generic "solutions" from a script. I am an IT professional and dabble in coding as well. The issue persists on multiple controllers, as I've stated, and I checked the .kl files for each in the system folders. Yes, I have restarted my phone. Yes, I have restarted the controllers. Yes, I have unpaired and repaired any bluetooth controllers. Yes, the firmware on all my controllers is up to date. Yes, my phone is up to date with latest updates. The issue is with system coding and only began after the last OneUI update. It worked exactly as intended directly before the update and stopped working as intended immediately after the update. Just forward this to your dev team please.
Solved! Go to Solution.
The Razer Kishi is working as intended for me now in Android 11 / OneUI 3 (aside from Accessibility Services blocking input - workaround for that here: https://www.reddit.com/r/AndroidGaming/comments/kb8mzw/accessibility_services_block_controllers_andr...).
I haven't tried any other controller as I sold my PS4 lol so right now the handheld Kishi controller is all I have
I am on the Note 20 Ultra 5G and I am also experiencing this problem with my Razer Kishi. One thing to note, when I connect my Xbox one controller, the home button works as intended.
Is this the best forum to share this information to Samsung, or is there another option I could use as well?
Before finding this thread, I've spent the last 2+ months working with Razer to determine why this was happening with the Kishi. Razer initially thought it was a hardware defect, and it took a long time to get another working unit sent to me ... Only to realize the original issue persists, because of this change caused in the OneUI update.
In the meantime while we wait for this to be fixed I recommend using the app's on-screen menus/controls just for the home button. That's what I'm doing for now with Xbox GamePass. Tapping on the screen to bring up the overlay and then using the Xbox button from there.
Shame this is a thing, it used to work perfectly before the update. Really wish they would stop "fixing" things that aren't broken.
Any hope for a fix coming soon? Just picked it up for my S20 and found this post. This along with the terrible audio lag on the Buds Live and no ability to use wired headphones makes it likely ill just return it.