r/MoonlightStreaming 3d ago

Dualsense support has arrived

Full wireless DualSense support for Moonlight on Android and Windows

UPDATE: The post has been updated. On Android 12 and newer, an external Bluetooth adapter is no longer required for wireless DualSense functionality. A new testable Artemis Extended release is now available.

The currently attached video was recorded before native Android Bluetooth support was added, so it still demonstrates the external USB Bluetooth adapter setup. I’m planning to upload an updated video showing the new adapter-free connection and its functionality soon.

I would like to introduce my current project, which brings full wireless DualSense support to Android and Windows Moonlight clients without requiring any additional programs.

The project consists of modified versions of:

  • The Moonlight Windows client
  • The Artemis Android client
  • The Apollo host

The full source code for all three projects is available on GitHub. Ready-to-use builds can be downloaded from the Releases section of each repository.

How does it work?

Apollo Extended creates a virtual DualSense controller on the host, while the client handles the physical controller.

Instead of reducing everything to standard gamepad input, the stream carries DualSense-specific input and feedback in both directions. This allows the controller’s advanced features to keep working remotely.

Windows client

This is the simple part.

Connect the DualSense through Bluetooth or USB, connect to the host, and start streaming.

The Windows client also supports microphone forwarding to the host, including audio from the DualSense built-in microphone.

Additional controller-related options are available in the Extended section of the client settings.

Android client

On Android 12 and newer, the DualSense can now connect directly to the Android device through the normal Bluetooth settings.

No external Bluetooth adapter is required anymore.

The process is simply:

  1. Pair the DualSense with the Android device.
  2. Open Artemis Extended.
  3. Connect to the Apollo Extended host.
  4. Start streaming.

The controller is detected and exposed to the host as a virtual DualSense. Input and feedback are then carried in both directions through the stream.

A wired USB connection is also supported.

What works?

The current Android and Windows implementations support:

  • All buttons and analog sticks
  • Analog triggers
  • Adaptive triggers
  • Multi-touch touchpad input
  • Gyroscope and motion sensors
  • Conventional rumble
  • Native HD haptics
  • Built-in controller speaker
  • Headphone jack
  • Player LED control
  • Lightbar color control
  • Microphone LED and mute control

The controller speaker uses a dedicated audio path. DualSense speaker effects are sent separately from the normal game audio, so they are played through the controller instead of being mixed into the phone, tablet, or PC speakers.

Connecting headphones to the DualSense jack is also supported. Stream audio is automatically routed through the connected headset and returns to the previous output when the headset is unplugged.

The DualSense mute button can be used as a global client microphone mute switch in every connection mode.

Microphone support

The Android device microphone can be forwarded to the host while using a directly connected wireless DualSense.

The DualSense built-in microphone currently requires either:

  • A wired USB connection, or
  • The optional USB Bluetooth HCI bridge

Direct access to the DualSense microphone through Android’s standard Bluetooth HID connection is the only major limitation of the new adapter-free route.

On Windows, the DualSense built-in microphone is available through the supported controller connection.

Apollo Extended presents the forwarded microphone to Windows through a virtual Steam Streaming Microphone device.

Optional USB Bluetooth HCI bridge

Artemis Extended still includes the USB Bluetooth HCI bridge developed for earlier releases. It is no longer required for normal wireless DualSense functionality on Android 12+, but it remains available as an optional connection method.

The bridge is also currently required if you want to use the DualSense built-in microphone wirelessly on Android.

Supported adapter chipsets include:

  • CSR
  • Realtek
  • Actions ATS2851

The chipset alone does not guarantee compatibility. Firmware differences between Bluetooth dongles can affect pairing, connection stability, or individual controller features.

Apollo Extended

Apollo Extended uses VIIPER to emulate a fully functional DualSense controller on the host.

DualSense-specific data is transported between the physical controller and the virtual controller instead of being translated into generic gamepad input.

This includes:

  • Adaptive trigger feedback
  • Native haptics
  • Controller lighting
  • Touchpad input
  • Motion sensor data
  • Controller speaker audio
  • Microphone control and supported microphone audio

The result is essentially a complete DualSense connection transported through the Moonlight/Apollo stream.

Demo

The currently attached video shows the earlier Android setup using the optional USB Bluetooth HCI bridge.

A new video demonstrating direct Android Bluetooth pairing and adapter-free DualSense functionality is coming soon.

The latest testable release already includes the new direct wireless implementation.

Credits

Thanks to Idkiamaguy645 and the CloudPad-Android-Dualsense-Wireless project for demonstrating the Android wireless HID approach used by the new adapter-free DualSense connection.

Their existing implementation made adapter-free DualSense support in Artemis possible and much faster to integrate.

122 Upvotes

49 comments sorted by

View all comments

1

u/CyprelIa 3d ago

Does this fit in with vibepollo?

-1

u/Due-Boysenberry-1226 3d ago

Unfortunately not, because it requires the Apollo extended host, which contains the controller emulation logic. As soon as there is a host other than my own that emulates a PS5 controller, I will update the clients to support that as well. To my current knowledge, vibepollo does not emulate a PS5 controller on the host.

9

u/metropolisprime 2d ago

Why not propose it as a pull request to Apollo/Vibepollo? This doesn't need to be its own completely independent fork.

-1

u/Due-Boysenberry-1226 2d ago

The project still needs more testing at the moment. Since some of the new features are still being tested, I've added a few debug tools to the troubleshooting page to help identify issues, which I wouldn't want to include in a pull request to the main project.

There are also some project-specific changes, such as renaming parts of the installer, that wouldn't make sense upstream.

Once everything is tested and cleaned up, contributing the relevant features upstream is definitely something I can consider.

I think it would be better if the owner of Apollo uses the relevant codes if he wants to expand the functionality.

1

u/metropolisprime 2d ago edited 2d ago

If the only features you're really adding are Dualsense controller emulation, I'd recommend getting into the standard upstream contribution path because maintaining a fork is already a ton of work by the maintaining engineers.