Wired Xbox 360 controller won't work with my Tab 2 10.1

By Elliot B.
in Android Support

 Share

Recommended Posts

Grand Master

Elliot B.

Posted
Posted

I am trying to connect a wired Xbox 360 controller to my Samsung Galaxy Tab 2 10.1 tablet (running Samsung's stock Android 4.1.1 ROM) via. an OTG adapter.

When I connect it, the following two messages appear:

"High-power USB device connected."

"Can not access to this device. "Connected device needs power supply."

Due to this, USB/BT Joystick Centre can't detect the controller.

Due to the poor English in the second message, I am presuming it's a Samsung ROM issue, rather than an Android/a tablet hardware issue.

Any ideas?

Grand Master

Elliot B.

Posted
  • Author
Posted

Seems like the error message gives the problem quite clearly to me...

Hardly. Loads of other Android phone/tablets users have no issues with the controller and their OTG adapter.

And are you saying you think the controller needs to be plugged into the mains? ;) Think.

Experienced

bmdixon

Posted
Posted

Not sure if it's the same for your tablet but it don't think my Galaxy Tab 10.1 (the first one) supported the XBox controller until i installed a custom rom that included the necessary kernel modules.

Having said that... both my Nexus 7 and Galaxy Nexus support it without doing anything special. I also haven't needed to use "USB/BT Joystick Center" at all, it just works when detected by Android.

Grand Master

Elliot B.

Posted
  • Author
Posted

Not sure if it's the same for your tablet but it don't think my Galaxy Tab 10.1 (the first one) supported the XBox controller until i installed a custom rom that included the necessary kernel modules.

Having said that... both my Nexus 7 and Galaxy Nexus support it without doing anything special. I also haven't needed to use "USB/BT Joystick Center" at all, it just works when detected by Android.

Yeah, I had a feeling it was related to the stock Samsung ROM :/

Grand Master

HawkMan

Posted
Posted

your USB port by default does not support high power output. so it cannot support a high power USB device, aka in this case the xbox controller. just like it wouldn't support most printers who require high power, many external HDD's. and so on.

a custom ROM "MIGHT" be able to change this by sending over spec power to the USB port, at the risk of burning it out.

Grand Master

Elliot B.

Posted
  • Author
Posted

your USB port by default does not support high power output. so it cannot support a high power USB device, aka in this case the xbox controller. just like it wouldn't support most printers who require high power, many external HDD's. and so on.

a custom ROM "MIGHT" be able to change this by sending over spec power to the USB port, at the risk of burning it out.

I'm surprised the controller is classed as a "high power" device. Sure, the vibration function is what it could be regarding, but I wouldn't if that's disabled.

I'm also annoyed that this tablet apparently can't do it, but many Samsung Galaxy phones support the Xbox 360 controller. Confusing!

Grand Master

_neutrino Veteran

Posted
  • Veteran
Posted

Apparently it is a common issue with people attempting to do this however, the USB port is not providing enough power to support using the Xbox 360 controller, I would suggest using Bluetooth and a PS3 controller. (that is what I use on my Tablet and phone.)

)

Grand Master

Elliot B.

Posted
  • Author
Posted

Apparently it is a common issue with people attempting to do this however, the USB port is not providing enough power to support using the Xbox 360 controller, I would suggest using Bluetooth and a PS3 controller. (that is what I use on my Tablet and phone.)

)

I can't really afford a PlayStation 3 controller.

Thank you for your help, guys :)

Grand Master

Eric Veteran

Posted
  • Veteran
Posted

Hardly. Loads of other Android phone/tablets users have no issues with the controller and their OTG adapter.

And are you saying you think the controller needs to be plugged into the mains? ;) Think.

It should work if you use a powered USB hub. 360 controllers (even the wireless dongle for Windows) use a ridiculous amount of USB power.

Grand Master

HawkMan

Posted
Posted

It should work if you use a powered USB hub. 360 controllers (even the wireless dongle for Windows) use a ridiculous amount of USB power.

The wireless dongle use it so it can charge up the blow the fuse capacitor :p

Grand Master

HawkMan

Posted
Posted

part of it is probably the really tiny antenna inside combined with the relatively good range. and as I said, they have to get the power to constantly blow that fuse after a couple of months from somewhere.

Grand Master

Elliot B.

Posted
  • Author
Posted

Got it half working thanks to this guy.

All we need to do is plug the controller into the OTG cable before you plug it into the tablet. Simple as that!

Now USB/BT Joystick Center detects the hardware, and all keypresses. However, no other apps seem to detect any keypresses (e.g. Mupen64Plus, XBMC 12.0 BETA 2 etc.)

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component

      By hellowalkman · Posted

      Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The quantum search for Time's origin had an equally mind-boggling conclusion

      By cleverclogs · Posted

      The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20

      By Copernic · Posted

      VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed

      By +Nik Louch · Posted

      They will
    • Politically funny images of the World

      By +Nik Louch · Posted

      Too soon, I'm still not over this death!

  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!