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.


jmeydam said…
Hi Bert

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

Please check your email at

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 bluetoothThe device doesn't allow step 2 if step 1 didn't s…

How to solve "user locked out due to failed logins" in vSphere vMA

In vSphere 6, if the vi-admin account get locked because of too many failed logins, and you don't have the root password of the appliance, you can reset the account(s) using these steps:

reboot the vMAfrom GRUB, "e"dit the entry"a"ppend init=/bin/bash"b"oot# pam_tally2 --user=vi-admin --reset# passwd vi-admin # Optional. Only if you want to change the password for vi-admin.# exitreset the vMAlog in with vi-admin These steps can be repeated for root or any other account that gets locked out.

If you do have root or vi-admin access, "sudo pam_tally2 --user=mylockeduser --reset" would do it, no reboot required.

Multiple VLANs on a Synology NAS

Synology, like other SOHO/SMB NAS vendors, touts VLAN functionality with their current DSM 4.1 software. However, the web interface just lets you specify one VLAN tag to use over each eth interface (or bond interface).
Manual approachIn the busybox environment that you can ssh into as root (after enabling ssh through the webinterface), there's all the tools you need to use multiple VLANs over one link (eth or bond), however:
First you insert the 802.1q module into the Linux kernel:
 /sbin/lsmod | /bin/grep -q 8021q || /sbin/insmod /lib/modules/8021q.koThen you add each VLAN you need to every interface (bond0 in this example)
 /sbin/vconfig add bond0 4And finally you can configure IP addresses on every interface.vlan combination (bond0.4 in this example)
 /sbin/ifconfig bond0.4 broadcast netmask same type of script would work on a QNAP NAS too, by the way. They offer 8021q.ko and vconfig in their commandline environment as well.
Packets from…