Android 17 Could Finally Fix One Of Mobile Gaming’s Biggest Problems: Native Controller Remapping Is Coming

For years, Android gamers have been stuck in an awkward middle ground. Most games rely entirely on touch, a handful support controllers, and almost none let you customise the button layout at the system level. If the default mappings feel wrong, your only options have been third-party hacks or hoping the game itself offers remapping.

But things are changing quickly: Google recently confirmed in their Android Canary build that they will introduce system-wide controller remapping into Android 17. Although a relatively subtle change, this feature could transform how millions of people play games across phones, tablets, TVs and new wave of Android PCs.

Here’s the thing — this is the first time Android has shown signs of taking controller support seriously.

Why Controller Support Matters More Than Ever

Android has become more than just a platform for mobile games. Through services such as Xbox Cloud Gaming, GeForce Now and PlayStation Remote Play users are streaming console titles with precise controls requiring custom controllers. Add Android handhelds, smart TVs and gaming-focused tablets into the mix and controller customisation becomes essential.

ALSO READ: 

Google Is Bringing An iPhone-Style Contact Sharing Feature To Android

Right now, Android treats every gamepad the same way:

- It identifies the controller

- Reads its input events

- Maps them using built-in configuration files

If your controller isn’t officially supported — or if you simply prefer another layout — you’re stuck. That’s where Android 17 steps in.

The First Big Hint: A New Permission for Remapping

Google has added a new system-level permission: android.permission.CONTROLLER_REMAPPING

It’s restricted to apps signed with the platform key, which signals one thing — controller remapping will be handled by Android itself, not third-party apps. The permission is tied to a feature flag inside the input subsystem, confirming this isn’t experimental code that slipped in. It’s a roadmap item.

A New Controller Menu Is on the Way

Buried inside the Settings app is an unfinished “Game Controllers” section. It doesn’t do anything yet, but the Activity definition makes its purpose obvious:

- List connected controllers

- Let users configure layouts

- Provide a home for future controller tools

Once filled out, this will finally give Android a central hub for all gamepad management.

Google Is Also Working on Virtual Gamepads

Here’s what really changes the game: references to a virtual gamepad inside the input framework.

What this suggests is clever:

- Android receives a real controller input

- The virtual gamepad intercepts it

- Android outputs a remapped version to the game

From the game’s perspective, it’s receiving input from a standard controller it already recognises.

The virtual controller can handle:

- Face buttons (A/B/X/Y)

- Menu buttons (Start, Select, Mode)

- Joysticks, including L3/R3

- D-pad

- Trigger axes and bumpers

- All standard controller event codes

This is the missing piece that enables true button remapping without hacks.

Touchscreen-to-Controller Mapping Might Be Next

Within the code, you can see traces of a deeper goal — mapping touch inputs to controller inputs. If Google pursues this fully, Android would allow users to play touch-only games with physical controllers.

That would be a massive deal for:

- Android gaming handhelds

- Smart TVs

- Android PCs

- Emulation-style experiences

- Cloud gaming setups

Chrome OS already uses similar mapping systems. Google Play Games on PC does too. So Android adopting this approach makes perfect sense.

Why This Matters for Gamers

If Google actually ships the full feature set, here’s what users gain:

- Custom layouts for every connected controller

- Accessible configurations for players with disabilities

- Platform-consistent remapping across all games

- Support for games that never added controller options

- Better ergonomics and lower hand fatigue

- A more console-like experience on Android devices

For the growing audience playing via cloud gaming, this also fixes a huge pain point: inconsistent button layouts across services.

ALSO READ: Anthropic’s Claim Of An AI-Driven Cyberattack Sparks Industry Backlash: Meta’s Yann LeCun Calls It ‘Regulatory Theater’

When Will This Arrive?

We’re still early. Android 17 is at least six months away and Google could trim features before launch. But the pieces are in place:

- The permission exists

- The feature flag exists

- The virtual gamepad framework exists

- The Settings menu stub exists

At the very least, Android 17 should deliver system-level button remapping. If we’re lucky, we’ll also get touchscreen mapping and deeper controller tools.

Final Thoughts

Android has long lagged behind iOS, Windows, and even game consoles when it comes to controller customisation. With Android 17, Google seems ready to treat controllers as first-class input devices — not an afterthought.

If everything teased here ships, mobile and cloud gaming on Android won’t just get better — it’ll feel more unified, more flexible, and far more accessible.