Bose product name
S1 Pro, Revolve PLus, Revolve II
Country
Australia
Firmware Version
S1 Pro -7.1.8, Revolve Plus 3.11
App Version
15.0
What devices were you using that were affected and what version are they on
(Samsung Galaxy S10 on Android 11, Galaxy A Series on Android 9, iPhone X on iOS14)
Detailed description of the issue and steps to reproduce
Hi,
We recently paired an older (2018) SoundLink Revolve Plus and new S1 Pro(7.1.8 FW) in Party mode via the Bose Connect App. Very easy to setup. Our aim was to use the two Mic input on the S1Pro and stream it over bluetooth to the SoundLink Revolve plus in a different room.
From the two articles this is possible i.e to pair up and S1 Pro to the SoundLink devices.
https://community.bose.com/t5/Portable-PA/Pairing-Bose-S1-Pro-to-other-bluetooth-speaker/td-p/575721
This worked perfectly and we could stream over bluetooth to the SoundLink Revolve Plus.
Unfortunately, we upgraded the SoundLink Revolve Plus to 3.11. This somehow affected the bluetooth. We cannot steam the Mic inputs of the S1 Pro over to the Revolve Plus. We can still stream over Blueooth using an android/IOS device to the S1 Pro and it will simultaneously stream to the Revolve Plus. For some reason the Mic inputs have been affected only which is what we require.
I have factory reseted both S1 Pro and Revolve Plus with no success. Tried pairing from different phones.
1.Since we cannot downgrade from 3.11 what can we try next ?
2. Will I be able to achieve this S1Pro pairing if we purchase a Revolve II or Micro speaker ? am worried even if it works, a FW upgrade in the future may kill it.
3. We had to resort to using the Aux input of the Revolve Plus using a 10 meter cable. If I were to purchase a Revolve II and put Revolve Plus and Revolve II in a party mode, would the Aux input of one stream wirelessly over to the 2nd unit (or is it only limited to a bluetooth source i.e android/IOS device)
Where do you run into the issue?
When did you start to experience the issue? Did it work correctly previously?
Any troubleshooting steps you took