I was previously using a Sony HWS-BTA2W bluetooth adapter from 2007 to get sound wirelessly from my computer or phone to a set of non-bluetooth speakers. It had a problem that only happened with my linux computer. I was annoyed with this device because as the workload would increase/decrease on my computer, the audio would speed up and slow down. You could hear the pitch rise and fall if you were listening to music. This is probably by design – as part of the base level Bluetooth SBC codec that everything supports. It makes sense that if you’re talking on the phone you’d want to hear everything someone said, even if it had to be sped up or slowed down for continuity.

The pitch bend happened on all of my linux laptops: 2008 Dell Studio 17 and my 2014 ThinkPad T440s, and my 2019 Developer Edition XPS 13. I wasn’t sure about the problem being in the linux bluetooth stack or the Sony device itself. I knew there was a better solution available – and it happened to be a combination of hardware and software.

After reading all about Bluetooth codecs and wanting another way to tap into my audio interface, I decided to try another, more modern, bluetooth interface. I went with a 1Mii B06S Bluetooth 5.2 Receiver. It supports several aptX profiles, which provide higher fidelity than the base BT codecs.

Interestingly, aptX originated as a PhD thesis, then later became incarnate in a DSP chip. Then the tech changed hands though several companies (including Solid State Logic which makes my audio interface). Before finally becoming part of Qualcomm. AptX was first used in the Bluetooth stack with some Sennheiser headphones from 2009. My 2007 Sony hardware was definitely not using this tech.

AptX on Ubuntu 22.04

To make sure my computer supported these extra codecs, I had to install some extras. Partly because aptX has some patent issues (although it’s been reverse engineered), and partly because I upgraded my system to use pipewire. The best source I found was this gist:

Enable PipeWire on Ubuntu 22.04

This guide is only for original Ubuntu out-of-the-box packages. If you have added a custom PPA like pipewire-debian, you might get into conflicts.

Ubuntu 22.04 has PipeWire partially installed and enabled as it’s used by browsers (WebRTC) for recoding the screeen under Wayland. We can enable remaining parts and use PipeWire for audio and Bluetooth instead of PulseAudio.

Starting from WirePlumber version 0.4.8 automatic Bluetooth profile switching (e.g. switching from A2DP to HSP/HFP when an application needs microphone access) is supported. Jammy (22.04) repos provide exactly version 0.4.8. So, we’re good.

Based on Debian Wiki, but simplified for Ubuntu 22.04.

Install

Install WirePlumber as the session manager:

$ sudo apt install pipewire-media-session- wireplumber

Notice ‘-‘ at the end of ‘pipewire-media-session’. This is to remove it in the same command, because ‘wireplumber’ will be used instead.

Start WirePlumber for your user:

$ systemctl --user --now enable wireplumber.service

Configure

ALSA

Install the ALSA plug-in:

$ sudo apt install pipewire-audio-client-libraries

And copy the config file from PipeWire docs (provided by the plug-in) into the ALSA configuration directory:

$ sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/

Check if you have other (like Pulse) configs in the /etc/alsa/conf.d/ installed by something else. You might want to remove them.

PulseAudio

Everything was done automatically by pipewire-pulse package, which should have been installed by wireplumber package as recommended. If not, install it yourself.

Bluetooth

Install the codecs and remove Bluetooth from PulseAudio, so it would be handled directly by PipeWire:

$ sudo apt install libldacbt-{abr,enc}2 libspa-0.2-bluetooth pulseaudio-module-bluetooth-

The supported codecs are SBC and LDAC.

Unfortunately, aptX and AAC are not supported because of patents and other technical reasons. aptX is available starting from 22.10 via libfreeaptx0 installed by default there (22.10 uses PipeWire by default as well). If you really need these codecs in 22.04 you may use this PPA from @aglasgall which is based on universe, but rebuilds pipewire with additional packages for aptX and AAC from multiverse. Read the discussion here.

Done

Reboot and check if it works by running:

$ LANG=C pactl info | grep '^Server Name'

view raw pipewire.md hosted with ❤ by GitHub

The important part in there is actually the link to the pipewire-extra-bt-codecs PPA for Ubuntu 22.04. I installed/removed the packages as expected and when I connected to the 1Mii B06S I can choose from all of the supported codecs in my sound settings:

I’m going to keep it on aptX HD for now and see how it sounds, but so far I’ve experienced zero pitch changes while listening to music.

Coming soon..

Next I’ll go through how I have everything hooked up in my home audio studio.

← Summary Only

If you have a pair of tried-and-true Sony MDR-V6 headphones (or V600, 7506, etc.) and you find yourself needing a new jack/plug, this is the one you want:

https://www.bhphotovideo.com/c/product/857699-REG/Remote_Audio_SONY18TRSMV2_Sony_Type_1_8_inch.html

It is made by Sony and fits the threaded 1/8″ to 1/4″ TRS adapter.

Continue reading →

This is just my experience, YMMV as they say…

In April of 2022 my VOIP home phone stopped receiving incoming calls. I could still dial out, but nobody could call the house. I received warning emails from Skyetel every 3 hours that my SIP endpoint was unreachable by their servers.

Since nothing had changed on my end, I suspected that something changed with my provider: Comcast/xfinity. Similar to my experience with British Airways, I found that xfinity has now automated everything.

I understand that automation helps if someone just needs to reboot their router, or forgot their wifi password. But for those who need genuine help getting shit done, it presents a huge barrier. It took me 9 calls and 3 trips to the xfinity store to get this resolved…

Continue reading →

Approach 1 (trying to fix the problem directly)

I phoned tech support to explain that port 5060 (for SIP service) was being blocked on my connection.

The first guy I talked to said they won’t open up that port unless I subscribe to xfinity’s VOIP service. Honestly, I didn’t want to talk to this guy anymore. He was obviously from India. No offense, but he sounded more like a scammer than a helper. I wanted to talk to someone who actually works for xfinity in the US, that actually knows how their network is set up. Before I hung up I got the phone number for Advanced Technical Support. It’s 888-780-8571. You’re welcome.

I called that number and magically wound up speaking with an actual technical rep based in these United States. BTW, this won’t happen every time – I’ve yet to figure out what automation magic I did to skip past the overseas nonsense.

When I mentioned my issue he referenced this page https://www.xfinity.com/support/articles/list-of-blocked-ports which I had also been looking at, noting that port 5060 isn’t in the list. He said I might need to do some configuration in my modem’s settings to forward that port.

But the Netgear CM1000 isn’t a combo modem/router. It doesn’t have a firewall or port forwards or anything. It just passes all connections on to my OpenWRT router which has firewall/forwarding/wifi/etc.

So the tech guy suggested I try an xfinity-supplied cable modem (at a rental fee of $15/mo) to see if that solves the problem. I wasn’t thrilled with the extra cost, but he said it’s pro-rated and might be worth seeing if it fixes the problem.

Approach 2 (playing the game)

So I went into my nearest xfinity store, went home with a new cable modem, and set it up. Then, to my dismay, when I went into the port forwarding settings on the modem, I consistently got this error:

I called technical support back and they said:

You need to go back to the xfinity store and get a different modem that is supported by the xfinity app. I’ve made a note on your account so they’ll give you the correct one this time.

WTF. OK, so I went back and returned my modem for another one. The new one worked with the app. I did have to do some weird things like disable IPv6 on my router so that it would show up in the xfinity app as an available device and port-forward destination because xfinity only supports port forwards via IPv4.

What’s really going on?

After configuring the router and updating my IP at Skyetel, it seemed to work 💪 Our home phone now rings after dialing. I called xfinity tech support again to re-activate my Netgear CM1000 to see if it will continue to work. Hey – it worked… But why?

My hunch is that by selecting a port forward in the app, something else is getting configured in their network to allow incoming connections – something upstream from your rental router. We’ll see how long the setting lasts before I have to go (temporarily) rent one again 🤞 Also – I was able to reactivate IPv6 in my router without issue.

The next day, the phone rang and it was music to my ears! ☎️ It was my daughter’s friend and they made plans to get together. Then the day after that, I received my first spam call 😱

← Summary Only

Holy 💩 y’all – I just spent two weeks not being able to share my screen on Ubuntu. It started with a regular system update that I think updated Wayland. I noticed that my fonts in certain applications looked sharper – likely meaning that the 4k scaling was working better. Then I noticed that zoom wouldn’t share the whole screen, it would just share a portion. 😩

To be clear about my setup, I was running Ubuntu 20.04 LTS with a dual monitor setup. I had been using Wayland because my XPS built-in screen is 4k and my external is standard HD (1080p).

As luck would have it, Ubuntu 22.04 LTS was recently in my update queue, and I figured it couldn’t get much worse. So I upgraded, but (womp womp) it didn’t help.

Continue reading →

Now zoom wouldn’t show a normal screen sharing option, but it had a new “System Capture” selection.

The system capture selection would bring up another new prompt:

But after I clicked “Share” nothing would happen. People on the other end would just see a black screen.

PipeWire Debugging

After some research it seems that the new sharing subsystem for Wayland is called PipeWire. In my quest to debug it end-to-end I found this handy guide for debugging screen sharing in Wayland, the “It doesn’t work” Troubleshooting Checklist.

One of the steps is to check the pipewire service itself:

systemctl --user status pipewire

And mine was up-and-running but was returning this warning in yellow:

no modules loaded

That led me to this post: https://www.linuxquestions.org/questions/slackware-14/using-pipewire-instead-of-pulseaudio-in-slackware-15-a-4175693980/page9.html

Yes it was for a different distro (Slackware) but one of the pieces of advice seemed sound:

Long story short, remove every little file from /etc/pipewire if exists and reboot the system.

I’m not sure why the folder was there with an old config file in it. Likely from when I was on 20.04 and tried upgrading PipeWire to try to fix zoom (which didn’t work).

I deleted that folder (actually moved it to a temporary place first), rebooted and it did the trick. Screen sharing is back on! Good thing because my job depends on it 💪

← Summary Only

I recently took a trip to Scotland. I didn’t plan ahead to add international calling because I thought I could disconnect for a week. Sometimes the world has other plans.

After landing in Glasgow I turned on airplane mode and left wi-fi enabled. Not surprisingly, I received a couple iMessage texts from some of the Minnesota Brass staff.

What did surprise me is that I was able to send and receive regular text messages as well. I wondered if it was because I had enabled Wi-Fi calling. My suspicion was confirmed after I enabled it on my wife’s phone and text messages came pouring in 😩

Continue reading →

Wi-Fi calling to the rescue

It came in extremely handy when British Airways automatically canceled our flight home. An aside about British Airways:

BA is an excellent example of a company that has automated too many things. Our flight from Glasgow to London got moved by 20 minutes. We received an email stating that it had moved and if everything was OK, no action was required. Behind the scenes the automated systems at British Airways determined that the time to make the connecting flight was no longer sufficient and automatically canceled our return trip (without notification).
We tried to remedy this by walking over to talk to the BA baggage and ticketing agents directly at the Glasgow airport. But they’re just contracted workers that can check in luggage, they can’t do anything when it comes to reservations. The only option was to call.
We spent 4-hours on the phone calling and re-calling British Airways to remedy the situation. Calls of course were routed to their call center in India where it was extremely difficult to get through (usually a 20-30 minute hold time) and once we got through they were very eager to get us off the phone, stating that “the team is working on it.”
The fastest way I got through was to call American Airlines once they were open (who was the US partner for London -> Chicago). Then I gave them my ticket number and they transferred me to the BA support line, and somehow I was magically at the front of the BA support queue.
Ultimately half of our party got home on the original flight, and the other half had to stay an extra day.

Enabling WiFi calling on iOS

For iPhone, WiFi calling is available on every major carrier. Turn it on under phone settings:

Once it’s enabled you’ll see a “<Carrier> Wi-Fi” message at the top when you’ve got a good wifi connection.

You’ll need to verify your home address for emergency calls. Keep in mind that if you’re on wifi with the cellular network disabled, the address reported to emergency services will be the address you entered (likely your home address). So if I dialed 911 in Scotland they’d think I’m calling from Minnesota – be careful!

When making calls over wifi with your cellular service off, it will be like you’re dialing from home. No need to dial any extra country code stuff. Just mind the timezone differences 😎

← Summary Only

Justin Foell

Technology, Bicycling, Hobbies, Kids, Life.

Category Archives: Business

Ubuntu 22.04 & aptX Bluetooth codec

AptX on Ubuntu 22.04

Enable PipeWire on Ubuntu 22.04

Install

Configure

ALSA

PulseAudio

Bluetooth

Done

Coming soon..

Sony MDR-V6 Headphone Jack Repair

Disassembly & Prep

Soldering

Test & Final Assembly

Unblock Port 5060 on Comcast / xfinity

Approach 1 (trying to fix the problem directly)

Approach 2 (playing the game)

What’s really going on?

Remove /etc/pipewire

PipeWire Debugging

Don’t have an international plan? Try WiFi calling

Wi-Fi calling to the rescue

Enabling WiFi calling on iOS