Skip to main content

Finally! A bluetooth headset that works with both phones!

After what seems like ages, I finally have a headset that works with both my cordless and my cell phone! I've got an AT&T EP5632 and a Motorola Krzr K1 (T-mobile), and all I want to do is have a single headset that I can use with both phones simultaneously. I have that now with the BlueAnt Z9i.

The EP5632 has been hit-and-miss concerning with what it will connect/pair. Unfortunately, the only compatibility list is on AT&T's site, and it's severely lacking. To add to the mess, I can't find enough documentation to figure out specifically what it's not compatible with. The best info I've found simply says it can handle Bluetooth 2.0 with both headset and hands-free profiles; In practice, that's not enough info.

Here's what I've gone through:
  1. Plantronics Voyager 510 - YES. Multipoint. Works with both, but not simultaneous (if on one call, cannot switch to other phone to answer). It was was starting to fail on me about the time of the purchase of the AT&T, so I don't recall much of my experience with it.
  2. Plantronics Voyager 520 - NO. Multipoint also, but will not connect with the EP5632. I like the ear-loop and ear-bud/gel.
  3. Plantronics Discovery 655 - YES/NO. Not Multipoint, but will connect to either phone just fine. (It was a gift, and wasn't known that multipoint was critical to me) Beyond that, the ear-gels' connecton is flimsy/cheap, and the ear-loop is held in place by the ear-gel (Everything almost always comes apart when in my pocket.). It never fits well in my ear, so I don't like to use it. Points for the raised volume buttons, though.
  4. BlueAnt Z9i - YES. Multipoint and it can switch between active calls on each phone. So far, the ear-loop and ear-bud make it feel secure. Unfortunately, there's only 3 buttons on the thing, so there's an overwhelming amount of unintuitive, difficult button combinations to activate the various features.
That reminds me: Is there some secret/unwritten rule somewhere that says a bluetooth headset cannot have more than 3 buttons, but the best is 1? I would have loved to try the Motorola H780 if only because it has a dedicated power switch. More buttons means less unintuitive sequences to remember when operating the headset.

Comments

Popular posts from this blog

SqlBulkCopy and the "colid" error

I thought there was a page explaining this somewhere out there on the Internet, but I can't find it anymore. So here's what I re-discovered. When you try to insert the rows from a DataTable and the data in one of the columns of one of the rows is too big to fit into the destination column in the database, you get a SqlException with this error message: "Received an invalid column length from the bcp client for colid N." (Where "N" is a number.) It doesn't tell you which row, and it's a pain to figure out what column to look at. To determine what column it is referring to, you first need to get a listing of all columns in the table, listed in the order as they have been defined in the database. Next, you remove any columns in the list that are not represented in SqlBulkCopy.ColumnMappings (the order of the column mappings is irrelevant). The list that remains is what "colid" is referring to, with the first column corresponding to colid &

Live Migration between domains

For those of you like me who aren't experts at all things Active Directory (AD) and Hyper-V Live Migration (LM) permissions, it can be enough of a pain to LM a Virtual Machine (VM) between domains that you simply decide to take the VMs offline to affect the move. See, I only tolerate AD because it's required for LM'ing VMs; there isn't a choice. (It's also required for Windows Clusters, but that's a different topic.) But I figured it out. My back-story is that we setup a cluster using Windows 2012 r1 as the AD Domain Controller (DC) and Hyper-V Server 2012 r1 for the VM hosts. Then we decided we wanted to use r2 for the AD DC and Hyper-V hosts. Upgrading Hyper-V was easy. But I found that there's some unresolved Microsoft bug with Windows Clustering when upgrading the AD DC from Windows 2012 r1 to Windows 2012 r2--- clustering simply doesn't work correctly anymore . So we gave up and created a from-scratch Windows 2012 r2 AD DC then made a new cluster

Hyper-V and reserving RAM for the host/root/parent partition

After a long process, I finally have a real-world calculation for determining how much RAM to reserve for a Hyper-V host. The question/answer about it is here. But the summary is that Hyper-V loses RAM to the Nonpaged pool (and all of it is "untagged") in addition to the "standard" stuff that Microsoft has documented. Be aware that I write MB/GB here, when I actually mean MiB/GiB. I feel it will be more intuitive to see the notation that Windows (incorrectly) uses. Host Overhead 300 MB for the Hypervisor services 512 MB for the Host OS (This is a recommended amount; you have some wiggle-room with this.) [The amount of physical RAM available to the host OS] multiplied by 0.0425 (result in GB ) for the Nonpaged pool (Which means multiply that by 1024 to convert to "MB") Per-VM Overhead 24 MB for the VM 8 MB for each 1 GB of RAM allocated to the VM. Examples 12 GB RAM, 1 VM @2 GB, 1 VM @4 GB Host: 812 + (0.0425 * 12 * 1024) = 1,334.24 MB