Bose Soundlink Revolve won’t charge – and fix

It’s been a while since I used my Soundlink Revolve, it’s a good sounding little speaker, but I noticed that it won’t charge anymore – what good is a bluetooth speaker that I can’t run wirelessly? so I started looking for fix: Charge with cable, with base, different charger, no go. Googled for fix, and found Bose’s official suggestion of resetting, didn’t work either. Plugged into laptop and went to btu.bose.com for firmware upgrade (latest is 3.0.4 as of this writing), didn’t help. I’m almost starting to think this is hardware issue and getting my screwdrivers ready before I found this gem in Bose’s own forum.

User “joelirwin” laid out this routine that fixed his/her same issue. In case it’s lost by Bose, here it is: (highlight by me)

1. Turn off by holding down the**multifunction key**.

2. Plug in and tap power button until it comes on.

3. Unplug

4. Power on and initialize by holding down the **top power key **for at least 10 seconds.  If won’t work try with plugging in first.

5. Power off and power on to get english language prompt.  Do not process at this point, yet…

6. Power off and plug in to charge.

This is a little different than what Bose is listing in their official support… Specifically, I don’t see any mention of using the power key to reset in Bose’s support. They did mention using the multifunction key to reset, but I tried that and it didn’t work. And joelirwin’s routine worked for me. I share the same speculation that Bose messed up the firmware of the speaker and shut off charging function somehow…not sure what triggered it, but this routine fixed it.

The “Plex Dance”, I thought it’s 2019 already?

After experimenting with multiple ways of setting up my home media server/NAS/data-scraper-to-be/another box wasting electricicty, I finally stumbled upon “The Perfect Media Server” from linuxserver.io. I don’t know how I missed it last many times since it’s been around since 2016, but finally MergerFS + SnapRAID has shined their lights upon me. Also, I finally come into modern times and started actually using docker. (Rockstor does use it, but not me directly), and first thing I install is, obviously, plex.

So I put in some MP3s, fire up plex, and they show up. Artists and track names and pictures and all. Simple. Or you’d think. They showed up [Unknown Artist] and such. Bummer. Just update their tags and have Plex rescan it and all will be fine, right? RIGHT?

Apparently not. Enter the “Plex Dance”, something even their forum mods recognizes and recommends. So plex ignores the obvious file content change due to metadata, and instead rely on its own metadata to say, “doesn’t look like there’s change to me”. The solution? move the files to force plex to update its own metadata, then move them back to force plex to (again) update its own metadata, at which time it will read the tags.

I mean, tag updates cause file to change, that alone should be enough to trigger a rescan, no? It shouldn’t take the entire file to disappear before plex panics and update metadata…this is 2019 already, if you really are scanning library location periodically, you’d think they know enough about the file changes and update accordingly.