SQ4You can't see mixer

Forums Forums SQ Forums SQ troubleshooting SQ4You can't see mixer

This topic contains 6 replies, has 5 voices, and was last updated by Profile photo of JLange JLange 1 month, 3 weeks ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • #109249
    Profile photo of Ben

    Hi all,

    First time posting here, just got my mixer all set up at our church. All of our users have been able to connect to the mixer using SQ4You or Mixpad, and they haven’t had any issues seeing the board’s name on the main screen…. Except for one guy!

    He is properly connected to our Wi-Fi (and has reconnected repeatedly). He has re-installed the app. He has refreshed the list 50 times. He can manually connect using the mixer’s IP address. His phone is a Pixel 6. What gives? Any ideas why the board won’t show up for him?


    Ben Hush
    Church in the Oaks

    Profile photo of Brian

    Does the app not save the IP address for future connection? Most apps you can put the address in once and then connect in the future without having to enter it again.

    Profile photo of Søren Steinmetz
    Søren Steinmetz

    Could be his phone has some sort of “secure browse” enabled, and thus forgetting the IP…

    Profile photo of Tom

    Did he try to disable the mobile data connection?
    Some phones don’t work well in wifi networks without internet access.

    Profile photo of Ben

    No the app doesn’t save the IP address (no option for that). It is not ideal to connect this way as I am the one who understands how to get the IP and connect, not him.

    And his phone is not operating in any kind of secure mode that I can see. Disabling the mobile data doesn’t make a difference.

    Profile photo of Ben

    I received a response from Keith I thought I would share here:

    “We’ve just started investigating this and believe it’s related to security changes with the latest android builds (which go out to Pixel’s first) that are preventing the discovery mechanism from automatically finding devices on the network.
    It may require a rebuild of the app against the latest SDK and libraries, which would then mean a complete test cycle to ensure everything else is still functioning correctly.
    This is something unexpected that we’d need to schedule in, so I’m afraid it probably won’t be a change to one line of code and it’s sorted in a few days.

    As it’s just the auto discovery feature that’s affected however, direct/manual connection will work correctly and will be required until we have solution – rebuild or otherwise.”

    Profile photo of JLange

    Now I know why our Android users started having issues. They will need to enter the IP address for now. Hopefully it won’t be too hard of a fix. Keith and team, thank you for looking into it please keep us posted.
    Thank you,

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.