Hi everyone,
Thank you for voicing your concerns as of recent. We greatly appreciate the feedback, and I’d like to reiterate a few points that we have previously made.
Connecting an Android device to your Reloop Buddy for control and playback:
Please note, in order to make a proper connection between your devices, you must first connect a USB-B (printer style) to USB-C adapter - like the one linked here - to the Reloop Buddy, and then you may connect your Android device to the USB-C adapter, and finally plug the adapter into a power source thus providing power to the Reloop Buddy and your Android device.
Pre-cueing audio via a controller on an Android device:
As we have stated in other threads, such as this one, we know that some users have experienced issues where their Android devices do not pre-cue appropriately due to an issue with multi-channel audio out. This is not an issue with djay but rather an issue with Android’s audio processing on specific devices.
Please note that the Android market houses a large assortment of devices that are often made with hardware not consistent in every region of the world. As an example, certain Samsung devices use Snapdragon SOCs in European and North American markets, even though they also use Exynos SOCs in Asian/Eastern markets. Even though these two processors have the same exact job, at the end of the day, they are still two different pieces of hardware that require firmware and software tailoring from their manufacturers.
For this oversimplified reason, we are not able to specify what devices may or may not behave as intended with djay at this time. This is not to say that we aren’t actively compiling which devices work as intended with djay. However, there are thousands upon thousands of different Android devices in various shapes and sizes, running different operating systems, using different hardware, some out of date and some not, which makes it difficult to test and vocalize native support for.
We understand your frustrations, and because of that, our teams have been exhausting all of the resources at their disposal, such as notifying Google, reaching out to affected vendors, testing various devices extensively, and making the appropriate updates on our end to try and alleviate whatever issues we can.
In closing, we ask that you all please respect our community guidelines and review your posts before submitting them to the thread in order to promote our vision of keeping the community a “Civilized Place for Public Discussion.” We will continue to update you regarding Android and its pre-cueing abilities as we go on. Thank you for your patience and understanding.