stringrazor
Inspired
I'm having an issue with getting my Samsung S5/Android device to reliably connect to my Axe/FX II. I've been discussing this with Alex via email but I thought I'd post it here too to see if anyone else has any insight. The issue seems to me to be an issue with Android & the Axe/FX not necessarily with Fracpad but since that's what usually uses the connection, it's what shows up the issue, which is:
Often (not always and I can't seem to nail down the pattern) when the S5 is connected to the Axe via USB/OTG, Android fails to recognize and present the axefx MIDI port so neither Fracpad nor any other app will list it or be able to access it. Fracpad just sits there waiting for the axefx MIDI device to become available and nothing I do with the S5 seems to make it connect. What will allow a connection is if I unplug the S5 and connect a different device, for example my Samsung Tab2 running Cyanogenmod. Once the Tab2 shows the axefx driver and Fracpad can connect on that device, if I reconnect the S5, the axefx MIDI device "magically" appears and all is well however nothing I have tried using ONLY the S5 seems to be able to correct the situation when the afefx MIDI drive is initially not found.
I have tried rebooting one or both the S5 and the Axe/FX and just about anything that can be done from the S5 including uninstalling/reinstalling Fracpad, force stopping running apps, changing USB parms in Developer Options. I've also tried different USB cables and OTG adapters without observing any change in behavior.
The S5 is the perfect size to be mounted on my FCB1010 at gigs. When connected successfully to the Axe/Fx and running Fracpad, it works flawlessly and I use it to display the patch names called up by the FCB so I don't have to remember what FBC patch #3 is or run over to the backline and look at the Axe/Fx's LCD. With the setup stress at gigs though, I need to be able to RELIABLY and easily connect the S5 so that Fracpad works every time. There will be no time for onstage debugging (I also have a keyboard rig to connect!).
Has anyone seen a similar situation and found a quick and easy workaround?
Often (not always and I can't seem to nail down the pattern) when the S5 is connected to the Axe via USB/OTG, Android fails to recognize and present the axefx MIDI port so neither Fracpad nor any other app will list it or be able to access it. Fracpad just sits there waiting for the axefx MIDI device to become available and nothing I do with the S5 seems to make it connect. What will allow a connection is if I unplug the S5 and connect a different device, for example my Samsung Tab2 running Cyanogenmod. Once the Tab2 shows the axefx driver and Fracpad can connect on that device, if I reconnect the S5, the axefx MIDI device "magically" appears and all is well however nothing I have tried using ONLY the S5 seems to be able to correct the situation when the afefx MIDI drive is initially not found.
I have tried rebooting one or both the S5 and the Axe/FX and just about anything that can be done from the S5 including uninstalling/reinstalling Fracpad, force stopping running apps, changing USB parms in Developer Options. I've also tried different USB cables and OTG adapters without observing any change in behavior.
The S5 is the perfect size to be mounted on my FCB1010 at gigs. When connected successfully to the Axe/Fx and running Fracpad, it works flawlessly and I use it to display the patch names called up by the FCB so I don't have to remember what FBC patch #3 is or run over to the backline and look at the Axe/Fx's LCD. With the setup stress at gigs though, I need to be able to RELIABLY and easily connect the S5 so that Fracpad works every time. There will be no time for onstage debugging (I also have a keyboard rig to connect!).
Has anyone seen a similar situation and found a quick and easy workaround?
Last edited: