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…
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 😱
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.
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:
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 💪
I got my daughter a FItbit Ace 2 from Best Buy for her birthday in 2021. You can get the older model Ace 2 there frequently on sale for less than $50. I honestly didn’t think she’s wear it, but I quickly learned she loved completing the challenges that it offered. She’s the type of kid that never sits still, so it seemed like a good fit.
She stopped wearing it later in the year. I thought getting her a new band for Christmas would get her excited about wearing it again, but my wife thought it was a lost cause. After Christmas came and went I asked her why she didn’t wear it, and it was because she didn’t like the band! 💡So I decided to revisit a new band for her birthday.
There are several big band stores out there like StrapsCo and Axios that sell several different styles of Fitbit bands. I really thought she’d like this rainbow one (which cost as much as I spent on the watch) 😅
Inspire 2 / Ace 2 bands – interchangeable?
So I ordered it because it claimed the Inspire 2 bands also work on the the Ace 2… sort of…
When I got the band, there was one problem. There’s an extra ridge on the band that must work on the Inspire but the Ace doesn’t accommodate it.
That ridge won’t let you insert the band to snap it into place on the Ace 2. So I got to work with my trusty Dremel rotary tool using a 409 cut-off wheel. Here’s what it looks like in-progress:
Once that ridge is gone, it’s now actually compatible with the Ace 2. My daughter loves it and it’s given her renewed interest in wearing it again!
I saved $300 on a portal-axle G500 crawler!
Or did I?
I was at Hub Hobby, my local hobby shop, getting some body posts for the LaTrax Prerunner after they busted out on the ice.
I wandered into the RC section and noticed they had a few of the new PandaHobby Tetra 1/24 scale portal-axle rigs. I asked the sales guy if they had blue. He said they did in the back and went to go get it.
I didn’t expect to buy anything besides LaTrax parts, but I guess I’m doing this! I already knew of some of the 1/24 Tetra’s shortcomings – having subscribed to a Tetra Facebook group a while ago.
Continue reading →
All seemed great, until it wasn’t. I did a ride with a friend in April and it inexplicably dropped GPS signal after 5 miles.
Elapsed Time
Moving Time
Distance
Average Speed
Max Speed
Elevation Gain
Calories Burned
02:53:01
hours
00:29:05
hours
4.90
mi.
10.10
mph
21.03
mph
73.16
ft.
1,304
kcal
My Fitbit stopped recording for some reason (said it lost GPS signal 😖). Actually went 16 miles, see https://www.strava.com/activities/5186103344
We went down Chicago to 38th. Continued south on Chicago then east on 46th to Sift. Then took the creek trail back to the river, then back the way we came.
Then it happened again, and again, and again. I found myself having to use my phone to record the remainder of the ride. That is, if I even noticed that my fitbit had conked out.
I could be riding outside in perfectly clear weather and then BAM, I’d get the dreaded “Cannot establish a GPS Connection. Turning GPS off” message 😡 WTF? No option to retry or anything. My fitbit would say “we’re done here” and give up. Very frustrating.
I opened a support chat with Fitbit to see what’s up. They had me go through the usual paces of making sure it had a full charge, disabling/removing unnecessary apps, make sure the firmware was updated, double-checking the GPS settings. Then they put a “watch” on my account to see what the tracker was logging.
Charge 4 RMA
They saw the same problems I was having, and then they told me to send my unit in for a replacement. Curiously they didn’t tell me what they were doing – presumably they knew what the problem was and they had a newer hardware version of the Charge 4 that would remedy the problem. But I can’t tell what has changed since there’s no indication of hardware version without opening it up to look at the circuit board.
I did some testing and noticed a new behavior when doing activities that use GPS. When you go into a building, or tunnel, or someplace where GPS signal is lost, it doesn’t turn the GPS off, it starts looking for a signal – indicated by a dim arrow icon in the upper left.
To confirm that it’s truly fixed, I went to my piano lesson (which is in a basement) and left the GPS running the whole time – 30 minutes indoors. It never turned the GPS off and I was able to record my full ride home.
Elapsed Time
Moving Time
Distance
Average Speed
Max Speed
Elevation Gain
Calories Burned
01:27:29
hours
00:59:04
hours
8.98
mi.
9.12
mph
20.36
mph
208.66
ft.
514
kcal
More Fitbit Charge 4 GPS testing
I wouldn’t recommend doing this normally – searching for GPS signal is likely a very power hungry operation. If you’re stopping somewhere, best to hit the pause button and then resume when you leave.
Get it replaced
I’m not the only one having this issue, as indicated by this thread in the Fitbit community forum. If you have one of these, you should contact support to get it replaced. With the issue fixed, it’s great and I no longer worry about losing my riding log.
