My experience with battery life has literally been the opposite with regards to airplay vs bt. Granted my BT is generally switched off on my phone, but when i use it I notice the battery life much more😎

Btw with the bs2 sound issues, do you have them on both BT and AP?

tlk wrote:

Out of curiosity, did you experience a difference in power consumption between wifi and bluetooth or was your statement based on theory?

Measured. It’s also quite noticeable for me since I typically only charge my phone once every two days on my iPhone 11 Pro, and I’m home a lot. I can easily listen to music for more than 12 hours a day since I consider music quite crucial to my sanity. I ran the tests back when I first got the speakers out of curiosity since Bluetooth’s design goal has always been lower power consumption.

Mikipidia wrote:

Btw with the bs2 sound issues, do you have them on both BT and AP?

For my sound issues the BS1 did eventually behave normally again after switching in between various wall positions and so on (out of nowhere my bass finally came back even though I eventually set everything back to default (not using a factory reset though)). Really weird. I tried the same thing with my BS2 but for now what I’ve done is set it to “Free” instead of “Wall” and move the bass sliders a few notches up on the equaliser.

It’s definitely much more tolerable now though.

Having said that I really wouldn’t be surprised if B&O has been adjusting the bass on the BS2 over time though.

And I say this because when I first got the speaker there really was too much bass (I used to use it on the “Corner” setting despite it not being in a corner, but after my last update (back in December I think) I noticed the bass was lowered so I settled down on the “Wall” placement).

After that update though I hadn’t gotten around to updating the speakers since my most recent update so it was quite a big jump in version numbers. Based on the information provided by other forum users I think I skipped around 4-5 new releases, so if they’ve been doing incremental changes to the sound signature then it’ll be a lot more obvious to me.

Stan wrote:

If you're using newer products, and you experience drop-outs while playing, then I'd look more toward environmental interference with the bluetooth signal.  I say this because, in my experience, BT is quite reliable with the newer products, and most of the issues revolve around pairing (especially with multiple devices as mentioned above).  I haven't experience drop-outs while playing except when there's interference or I'm walking around and get out of range. 

Then again, if you implement your reboot idea and the problem goes away, then it is most likely a software problem.

Hmm. Now that you mention it: I do recall my dealer mentioning that one of the reasons we were having pairing issues is due to the sheer number of Bluetooth devices they have in the showroom. It’s a plausible explanation I guess but I never dug into it further.

I say this though because in my current apartment things are really congested in terms of the sheer number of wireless access points everyone is running (neighbours and all), and while Bluetooth is designed to handle interference I’m not sure to what degree. I also recall USB 3.x being a culprit but I don’t have any permanently attached USB 3.x devices on any of my systems, so I doubt that’s the case.

While Bluetooth dropping out and crashing does happen, it’s doesn’t happen too often (about once a month I’d guess). My biggest issue is Bluetooth simply refusing to pair when I want to connect to the speaker.

What I’ll do for now is once I’m back home I’ll analyse the communications between the app and the speaker and just implement a reboot scheduler once I’ve picked up on the reboot command sent from the app, I still strongly suspect that there’s some sort of memory leak occurring that’s causing the Bluetooth stack to crash after the speakers have been up for some time, though it could be a combination of factors whereby interference is exasperating the problem further which results in more frequent issues.

I generally configure reboot scheduling on almost everything I own since it does prevent very obscure memory management issues from building up over time and eventually causing a degradation in performance, so we’ll see how that goes!

Thank you for this message though, it does give me something else to meaningfully look into in more detail. Cheers Stan!

BeoAnna wrote:

It’s also quite noticeable for me since I typically only charge my phone once every two days

Okay. I assumed that most people have their phone connected to their local wifi already, and so turning bluetooth on would be an additional drain on the battery.

BeoAnna wrote:

in my current apartment things are really congested in terms of the sheer number of wireless access points everyone is running (neighbours and all), and while Bluetooth is designed to handle interference I’m not sure to what degree.

Exactly. I doubt that a daily reboot will solve interference issues. 5Ghz wifi to the rescue.

BeoAnna wrote:

suspect that there’s some sort of memory leak occurring that’s causing the Bluetooth stack to crash after the speakers have been up for some time

Could be the case. I would not be surprised if B&O do not test their devices in modern city apartments surrounded by microwave ovens, loads of weird wifi access points and dozens of potentially broken bluetooth devices.

Bluetooth’s drain on the battery merely by being on with no active connection is pretty much negligible, and even with an active connection it’s as good as negligible; don’t forget Bluetooth was designed for small portable devices with microscopic batteries compared to what we get in phones. So it’s definitely not something I’d worry about. I used to have Bluetooth turned off all the time as well until I educated myself against all the FUD.

While a daily reboot won’t solve interference issues for sure, it could still help especially if there’s something funky going on in the Bluetooth stack (and again I suspect it could be exasperated by the conditions of my apartment, an environment which as you said B&O might not have accounted for).

I remember following Mikipidia’s whole Beolab 50 shenanigans, and if I remember correctly they suspected something similar?

As in the possible reason he had the weird clicks was because the speakers weren’t tested in a congested network environment and hence his issues.

As for 5GHz wireless; while yes I can turn 2.4GHz off it doesn’t change the fact that my neighbours all have their access points operating on both hands, and I actually have my speakers connected to my 2.4GHz network as they are not within reliable range of my 5GHz network due to a number of solid walls I have between the speakers and my wireless access point.

I guess I could add another WAP on the opposite side of my house to test this out though. 

[Didn't Miki go wired and still had problems?  Anyway,...]

You can have all neighbors with their access points operating both on 5GHz and 2.4GHz, and still the 5GHz will work better just because there are many more available channels.  Also most access points, by the time they were built with 5GHz, had channel-scanning built in so they would pick a free channel unless explicitly configured not to do that.  You can usually find an unused channel for a fixed-channel assignment, if your own WAP isn't smart enough to hunt every time it reboots.  Not to mention with only channels 1, 6, and 11 being the only non-overlapping choices in the 2.4GHz range, morons who pick channel 9 (for example) ruin it for everybody nearby-enough on *both* 6 & 11.  Plus if the neighbors are close enough, there's absolutely nothing to be done about 2.4GHz getting smothered every time a microwave oven is used.  Ugh.

BUT having a free channel doesn't fix your *range* issues with 5GHz vs. 2.4GHz, alas!  Putting a second wireless access point somewhere nearby is a good solution, even if you cannot hardwire it to the main router.  Why?  You can position that WAP wherever necessary for its own good signal reception: shelf, floor, ceiling, sideways, external antenna, tinfoil cone, whatever it takes.  But then your speaker merely must be nearby the new WAP, positioned as artfully as you like.

For foolproof daily reboot, I have a one-word solution for you: Intermatic!

Haha, mercifully all of my neighbors are too blissfully unaware of networking basics to be mucking around with their wireless network channels; literally *everyone* is on channel 1 (with me being the only one on 11, and 6 is also free (and no-one is on any of the overlapping channels either)) on the 2.4GHz band. I run a comprehensive wireless network scan every six months or so whenever I vet through the configuration of my gateway and wireless access point just to make sure everything is kosher and I didn’t miss out on any firmware updates requiring my attention.

And nope, the crappy routers given out by most of our ISP’s don’t bother with channel scanning.

Anyway wireless is never an issue for me, it’s Bluetooth deciding to take a vacation whenever it feels like it on all of my B&O speakers. Not sure how much moving the speakers to a 5GHz network will help given the hundred or so 2.4GHz networks around my vicinity, but I’ll give it a shot. Again there’s two issues here: one being pairing randomly failing after several days of uptime, and another being Bluetooth crashing in the middle of playback.

Anyway I have a pretty big upgrade on my home network due once some of my new kit has arrived, so I’ll get all of that tested out eventually. My new access point will be mounted in an open area bang in the middle of my home so I’ll finally ditch 2.4GHz once that happens.

As for Miki’s Beolab 50, yeah it was all really bizarre. I think the speakers were still scanning for wireless networks even when wired, I really cannot remember the details, but I do vaguely recall a mention on how his location was pretty congested with tons of wireless networks which greatly amplified the problem and hence why the speaker from his dealer which ordinarily worked fine also began ticking when they moved it over to his home.

Anyway I’ve always joked that this is such a first-world B&O problem to assume everyone’s living in a huge mansion in the middle of nowhere haha.

For my own speakers though I kinda suspect that in addition to some memory leak in the Bluetooth stack it’s somehow being amplified in a congested network environment, which may be why B&O didn’t catch it during testing. In the interim I’ll proceed to intercept the reboot command from the app and just setup a cron job on my server to take care of that every morning.

And finally; yeah I did originally consider an electrical timer of sorts but due to the way I have things wired at the moment I’m not really in the mood to implement such a solution though I do agree it’s definitely the most fool-proof method. I’ll probably just end up writing a script to probe for the speaker first before sending the reboot command and then making sure it actually reboots. That way I can just log all the data I need to make sure everything’s happening the way I want it to be happening so that I have all the data to fine-tune the process if needed.

I’m quite confident that this will improve things since I have noticed that it usually takes a few days worth of uptime before Bluetooth decides to act all naughty and uncooperative with me.

I’ve been meaning to look into this forever but work, laziness, and a healthy dose of procrastination got in the way!~

Thank you to everyone for contributing to this thread though, it’s given me a few extra things to look out for so let’s see how this all works out.

What my problems actually were in the end they never told me, they blamed it on the wifi. First that it wasn’t ubiquiti and then that it wasn’t hardwired but neither solves the issue in the end so I suspect a different fault somewhere else in the end but we’ll never know. I now live in an even more congested building and all is well with both network and BT(and new speakers)🤷🏼‍♂️

That’s why i don’t get it. Maybe a silly question but have you looked at how the BT is set in the devices? Because there are a few setting you can change, maybe it helps, just an idea.

Yeah there isn’t much in terms of Bluetooth settings in the speaker’s web interface unfortunately and I have tried fiddling around to no avail. Admittedly I do use Bluetooth *a lot* so maybe that’s why I’m more susceptible to problems; I generally average 4-6 hours of music listening a day on them and full day sessions aren’t that common since I do always like to have background music playing, and of course I switch between speakers a lot too.

I’ll see how things pan out with having the speakers freshly auto-rebooted every morning, hopefully there’s at least some improvement.