How to pre-cue in Djay for Android.

[hasaka0706]

• Device model : Redmi Pad SE 8.7 4G
• Version of operating system : Xiaomi HyperOS 1.0.5.0UHYMIXM (Android 14 UP1A.231005.007)
• Version of djay : 5.3.1
• Hardware/controllers used : AlphaTheta DDJ-FLX2

I’m unable to pre-cue in the environment described above and have to rely solely on judging by the waveform.
Could you please provide any solutions or workarounds?

[Slak_Jaw]

Hi @hasaka0706, welcome to the Community! Sorry to hear you’re experiencing this issue.
Can you please provide more details about the issue? Perhaps you can share a short video and/or some screenshots to show how everything is connected to your Android device and what your Audio Devices settings look like? Thanks!

[hasaka0706]

Thank you for your message.
The connection status of the equipment is as shown in the photo.

1.DDJ-FLX6: USB-C
Redmi Pad SE 8.6: USB-C
2.Headphones output terminal

With this connection, even when I press the cue button on the right deck, no sound is output to the headphones.

The pre-cueing settings on my device are as shown in the following photo.

[Slak_Jaw]

Thanks for the information @hasaka0706.

1. Please also a screenshot of your djay Settings>MIDI Devices.
2. I would start by trying a different USB cable.
3. There have also been reports of issues with using Xiaomi devices with djay. Do you have another device that you could test to confirm if it is an issue with the DJ controller or your Android device?

[hasaka0706]

Thank you for your reply.

1. This is the MIDI device settings screen.
   

   

2. Trying a different USB cable didn’t fix the pre-cueing issue.

3.I tried it on my other device (Unihertz Jelly Star: Android 13), but I couldn’t pre-cue.

[Slak_Jaw]

Hi @hasaka0706, based on this information, it sounds like it’s an issue with your DJ controller.

[hasaka0706]

Hi @Slak_Jaw ! Thanks for pointing that out. I’ll look into the DJ controller issue.

[Slak_Jaw]

You’re welcome @hasaka0706

[megamema]

@hasaka0706 @Slak_Jaw

Test Results with Djay 5.3.1, MIXON 4 & Pixel 9a

I am currently testing the Reloop MIXON 4 with the latest Pixel 9a (running Android 15, with lossless USB audio support) and Djay 5.3.1. The Pixel 9a comes with the latest Android 15 and supports lossless USB audio. I believe it’s an optimal Android reference device. Both RELOOP and Algoriddim officially state that the MIXON 4 has full compatibility with the Android version of Djay. I conducted this test to see how well this combination actually performs. My reasoning is, if it doesn’t work well on this reference device, I question what Android device would work properly.

Here are my findings after trying the latest Djay 5.3.1 for Android (full paid version):

• MIXON 4 Control: The MIXON 4 generally works well for controlling Djay . Not only do basic controls (play, stop, faders, knobs, etc.) function, but PAD features and various effect functions also work mostly without issue, operating very smoothly and comfortably.
• Master Output: The master audio output appears to be in stereo. However, when comparing the same audio source, the sound quality is noticeably inferior to that on iOS devices or Windows PCs.
• Cue Monitoring: This is where I encountered the biggest concern. I couldn’t get the MIXON 4’s independent CUE monitoring function to work at all. No sound comes out from the headphone output.
• Split Output Mode: When I enable the “Split” feature in the Djay app, the CUE monitor audio (what I want to hear in headphones) is simultaneously output through the master out (the main audio sent to speakers, etc.). I understand this is how it’s designed to work in this mode, but it results in the master output becoming mono.
• Audio Routing Limitations: Within the Djay app for Android, there were simply no settings options available to individually route audio outputs (e.g., master and cue) to specific audio devices.
• Custom MIDI Mapping: I also couldn’t find any way to customize MIDI settings to freely assign functions to the controller’s buttons and knobs within Djay Pro at all.

---

My Conclusion and Question

Based on these test results, the complete lack of functioning independent CUE monitoring is a significant issue. I suspect this is not a problem with the MIXON 4 controller itself, but rather a fundamental limitation stemming from the current Djay (Android version) and the Android OS audio specifications. Therefore, it’s not ideal for a professional DJ setup in its current state. I believe the only workaround is to force mono monitoring using an old-school split cable, but I’m unsure how exactly to route the cables in this scenario.

Is this also because of the controller?

[Slak_Jaw]

Thanks for the detailed information @megamema. I’ve passed this onto our hardware team to see if they experience the same results.

[Slak_Jaw]

Hi again @megamema, I spoke with engineering.

We are aware of this issue with the Google Pixel 9 series devices. Android devices not supporting independent cue output is, unfortunately, a common phenomenon. We were able to confirm this is an issue with the phone model and have reported it.

In the meantime, some newer Pioneer/AlphaTheta controllers such as the GRV6 and FLX4 have a “mono” switch to circumvent these issues, and can be recommended as a safer option.

[megamema]

@Slak_Jaw
Therefore, as a user, I am unclear on which devices the expected operation will be possible.

I would like to know what hardware and Android devices can be used without resorting to brute force mono output. It may be difficult to give a specific answer, but I would appreciate it if you could tell me informally.

[Slak_Jaw]

Hi @megamema, unfortunately, this is not an easy question to answer when it comes to Android devices. Please refer to our FAQ for more info: https://help.algoriddim.com/hc/en-us/articles/11294368324636-Why-aren-t-some-features-of-djay-for-Android-working-on-my-device