Skip to main content

Comparing bluetooth carkits

Bluetooth carkits come in three main categories: those with bluetooth HSP, those with bluetooth HFP, and ones that do bluetooth SAP. Some implement multiple of these profiles and allow you to choose.

  • HSP (head set profile) is the simplest profile: your carkit is basically a speaker-microphone combo, and will play the received audio and send your voice to the telephone. The telephone connects to the cellular network and handles the call. HSP is commonly used in bluetooth earpieces.
  • HFP (hands free profile) is the most common protocol in carkits with a display: your phone still handles the call, and the carkit provides the two-way audio function just like HSP. But the carkit also has basic control over the phone: it can access the received/dialled/missed call lists. It can also instruct the phone to dial a number, to accept or to reject an incoming call. Most carkits also access the phonebook.
  • SAP (SIM access profile, also known as rSAP or SIM) is the most complex of the three: this carkit contains a cell phone ! The mobile phone will disconnect from the network, and lend its SIM card to the carkit phone. Calling is now done by the carkit phone. The carkit will typically also sync the phonebook of the phone via another bluetooth profile.
this is my list of pros and cons for all:

  • HSP pro: your phone can do everything it wants, and you speak to the carkit the way you'd speak into your phone. You still have 3G, and if your phone does smart tricks like voice commands, that probably still works over the carkit. You can seamlessly disconnect the bluetooth kit during a call and continue the call on your phone.
  • HSP con: your phone is the only place to control calls, see caller ID, etc. Also, your phone emits radiation inside your car.

  • HFP pro: you can still use your phone to control calls, but also the carkit display and buttons. On your phone, you'll still have 3G. In my experience, things like voice commands for your phone won't work anymore, but maybe your carkit has similar functionality. As with HSP, you can seamlessly disconnect/connect the carkit during a call.
  • HFP con: your phone emits radiation inside your car, although with a suitable cradle, your mobile phone may benefit from an external antenna. Depending on phone and carkit, you may not hear your personal ringtone anymore.

  • SAP pro: no more phone radiation inside your car! The carkit has an external antenna, which means better reception. Battery usage on your mobile phone is minimal.
  • SAP con: you can't seamlessly switch from carkit to mobile phone. Getting in your car during a call means ending the call and redialing from your carkit phone. Your phone can't do 3G anymore while connected to the carkit. Not all phones support this profile (most notably the iPhone doesn't). You don't hear your fancy personal ringtone anymore, because it's now you carkit phone that's ringing.

Comments

jmeydam said…
Hi Bert

Totally unrelated, but since I have no other way to contact you:

Please check your email at

bert+cv@debruijn.be

You can get in touch with me via email:

jmeydam at gmail dot com
jmeydam said…
This comment has been removed by the author.

Popular posts from this blog

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition). But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now: the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth the phone connects to "Touch Adapter" device, also via bluetooth The device doesn't allow step 2 if step 1 didn'

Reset lost root password on vSphere ESXi 6.7

VMware's solution to a lost or forgotten root password for ESXi is simple: go to  https://kb.vmware.com/s/article/1317898?lang=en_US  and you'll find that "Reinstalling the ESXi host is the only supported way to reset a password on ESXi". If your host is still connected to vCenter, you may be able to use Host Profiles to reset the root password, or alternatively you can join ESXi in Active Directory via vCenter, and log in with a user in the "ESX Admins" AD group. If your host is no longer connected to vCenter, those options are closed. Can you avoid reinstallation? Fortunately, you can. You will need to reset and reboot your ESXi though. If you're ready for an unsupported deep dive into the bowels of ESXi, follow these steps: Create a bootable Linux USB-drive (or something else you can boot your server with). I used a CentOS 7 installation USB-drive that I could use to boot into rescue mode. Reset your ESXi and boot from the Linux medium. Ident

GEM WS2 MIDI System Exclusive structure and checksums

MIDI is the standard for communication between electronic music instruments like keyboards and synthesizers. And computers! While tinkering with an old floppy-less GEM WS2 keyboard, I wanted to figure out the structure of their System Exclusive memory dumps. SysEx is the vendor-specific (and non-standard) part of MIDI. Vendors can use it for real-time instructions (changing a sound parameter in real-time) and for non-real-time instructions (sending or loading a configuration, sample set, etc.). In the GEM WS2, there's two ways of saving the memory (voices, globals, styles and songs): in .ALL files on floppy, and via MIDI SysEx. The .ALL files are binary files, 60415 bytes long. The only recognizable parts are the ASCII encoded voice and global names. The SysEx dumps are 73691 bytes long. As always in MIDI, only command start (and end) bytes have MSB 1, and all data bytes have MSB 0. The data is spread out over 576 SysEx packets, preceded by one SysEx packet with header informat