elfs: (Default)
I have a serious peeve about my Macbook and bluetooth. Compared to every other device I own, the Macbook’s behavior around my headphones is rude to the point of being unacceptable. I can’t speak for Microsoft products, as I don’t own any (well, any software; I’m hacking this on my Surface Pro, which is currently running Linux Ubuntu 19.10).

I own a nice pair of bone-conducting headphones that “route around” a problem I have with my inner ear. Since they’re tiny and go around the back of the head, they’re practically invisible during conference calls, which is something of a necessity as we’re all working from home during the Coronavirus crisis. I wear them a lot, and I currently have them paired with two devices: the Macbook, which is my work laptop, and my Android phone.

When I wasn’t working from home, I paired the headphones with my personal laptop, which is running Linux PopOS 19.04.

You know how, when you turn on your headphones, it will pair with the last device it associated with, if that device is available? It’s a lovely feature but it can be inconvenient for headphones with multiple pairings. Both the Android and Linux devices however have a setting to handle that: if you manually disconnect (but not unpair) the headphones, the device will not automatically re-connect with the headphones the next time they start up. This is pretty nice; I can connect between my phone (for listening to music) and my laptop (for watching movies) without trouble.

But not with the Macbook. If I manually disconnect from the Macbook and then put the Macbook away, literally unplug it and put it into sleep mode, the next time I turn on the headphones the Macbook actually wakes up and grabs the headphones. I have to remember, when I shut the Macbook down for the day, to turn Bluetooth off.

There’s a word for this sort of behavior: rude. MacBooks assume you only every want to associate with a MacBook and ignores this idiomatic method of freeing up a multi-pair device like my headphones to connect with something else.

The MacBook is a pretty little fondleslab of aluminum, but it hides a possessive, abusive heart, and if work hadn’t required I take it home I wouldn’t have allowed it into my house.
elfs: (Default)
How to pair your Google Pixel 2 phone to your Subaru Outback.

The Google Pixel is a lovely phone, but it's notoriously bad at connecting with Subaru cars. It was the one feature I missed from my previous Samsung, which always connected reliably and automatically to the car every time I started the engine. Since I have "unlimited" 4G and a Spotify account, I found this breakdown highly annoying. It is possible to connect the phone to the car, but often it takes two or three minutes of sitting there with the car running, pressing the "connect" button on the phone's Bluetooth app over and over until, mysteriously, it would finally connect.

I have gotten it to work, and now when I sit down in my Outback, the music that was playing in my headphones in the office automatically starts right back up, reliably and automatically.

So here's why it fails:

Most people, when they want to create a Bluetooth Pairing between the phone and the car, go to the car radio, press the "Menu" button, and go through the Bluetooth pairing dialogs from the radio's LCD display. And that's where the problem lies— that dialog is for pairing with the radio and is therefore looking for an audio source, but the phone isn't programmed to prioritize being paired as an audio device, it prioritizes being paired as a phone. Every time thereafter, the protocol mismatch causes the automatic connection to fail. I'm not sure why manual connection sometimes works, but it should work reliably.

Here's the solution:

If you've already paired your phone and your car, go to the car's dialogue and delete the phone from the car's list of Bluetooth connections. Likewise, go to your phone and delete the car from the phone's list.

On the steering wheel, there's a button with a voice label. This is the HandsFree Talk Button. With the car parked and the parking brake on (this is important, as the car will not let you do this otherwise), but the key turned far enough to turn on the radio, press the Talk Button.

A female voice will say, "Welcome to the Subaru HandsFree Control. Press the Talk Button and choose from the following menu items: Setup. Go Back."

Press the button and say "Setup."

"Press the Talk Button and choose from the following menu items." One will be "Pair Phone". Do as the nice lady says and say "Pair Phone."

"Searching for phone. Searching. Searching. A device has been found. The passkey is 1234." Now go through the dialog on the phone and type in the stupid passkey.

"Phone paired. Press the talk button and say the name of the phone."

Press the button. "My Phone"

"Pairing Complete. Press the button and choose from one of the following menu items: Setup. Go Back."

"Go Back."

"[Beep]"

And now the car will use the connect to phone protocol whenever you start it, and your phone will respond accordingly. In short, the quicker and more obvious interface on the car's radio dial will activate the wrong protocol, and you'll get the bug. The only way to pair the phone to the car correctly is through a really stupid voice control menu tree.
elfs: (Default)
The laptop fan is doing that death-rattle thing again. Fortunately, replacement fans are cheap and the replacement process straightforward. But Jesus and Set, why can't I get a fan that just works?
elfs: (Default)
Keywords: palm, username, userid, restore, backup

I woke up half an hour late this morning. My Palm V, usually a reliable machine, had crashed hard. The LED was solid, the screen frozen, and I could not even get the box to warm reset. I had to do a cold reset, which means that I then had to go and restore from backup. Not too bad a problem: I make backups.

But the backup kept failing. Those programs that I had bought, rather than the GPLd ones, would not run. I tracked it down to the fact that the User-ID for the Palm had not been set-- and there is no way to set it from the Palm itself. You have to do it from a host computer.

The correct command to do this is install-user -p /dev/pilot -u "User Name". I'm just using this as yet another place to note that down.
elfs: (Default)
The power supply on my router has been dying for a while. The ball bearings on the fan have been making horrible buzzing noises and the time to replace it had come, so this afternoon I opened the case and prepared for surgery: transferring the hard drive and network cards into an older, slightly slower (it's still a P2 and it's fine for routing, nobody cares) PC.

When I opened the case on the old one while it was still running, I found a colony of vicious dust bunnies living within. I pulled out my trusty blower, but before I pulled the trigger I noticed something: the fan on top of the CPU wasn't spinning. A huge dust bunny had wedged itself into the works and was preventing the fan from spinning. A blast from the duster and it started right up. It's too bad I couldn't do that with the power supply, but it was dead.

A similar problem had hit my desktop a couple of weeks ago, and it had resulted in rapid overheat and shutdown. But this old P2 was still chugging along even though neither the power supply fan nor the CPU fan worked. I wasn't asking very much of it, true, but it was still impressive.

I swapped the cards and the disk drive, and the router happily accepted its new memory and CPU constraints. We got back on line in less than twenty minutes.
elfs: (Default)
Well, I bought a new hard drive to replace the one that died. It's hard to believe that the smallest hard drive commonly available is 100GB, and 200GB are only a little pricier. I did a pretty good re-install of GameOS and then overwrote the install with whatever was recoverable from the damaged drive.

I only lost a few things: An episode of MST3K, my Half-Life 2 saved games, and sob my BloodRayne saved games. Waaauugh!
elfs: (Default)
My left control button on my laptop wasn't working right, so I tried cleaning it out with a can of air. A small twig or something stuck out from underneath it, so I reached in with a pair of lab tweezers, the kind with a long thin point at the end, and pulled it out. Out with it came a cat hairball a half-centimeter on a side. I started working my way around the keyboard, and sure enough every key was gummed up underneath with a substantial and disgusting volume of cat hair.

It took a while to clean all of the keys but once I had it done I was happy with the results and the keyboard feels springy and responsive again.

I can't pop the keys off as at least one has broken when I tried to do that. Fortunately, it was only the Windows key; I chose it for the experiment because it was expendable. This keyboard is so old that the plastic undersprings have become fragile, and I don't dare stress them too hard.

Off to take the kids to the library and look up books on La Belle Epoque.

Profile

elfs: (Default)
Elf Sternberg

May 2025

S M T W T F S
    123
45678910
111213141516 17
18192021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated May. 28th, 2025 03:21 am
Powered by Dreamwidth Studios