News
Downloads
Screenshots
Support
LiveMobileTools
Help Us
About KMobileTools
SubVersion howto
Links
Thanks- KMobileTools 0.5V0.4.3.3 Problem - Only downloadingbottlehall
- KMobileTools 0.5Problem compiling 0.5 beta 3 with P2K supportbottlehall
- KMobileTools 0.5Problem compiling 0.5 beta 3 when QT4 and QT3.x both installedbottlehall
- KMobileTools 0.5sms lg u880francescobat
- KMobileTools 0.5Samsung SGH-X530 fully supported in release 0.5.x?Chimichurri
Bluez 3.x pin-helper patch
Updated: fixed version string and usage informations.
Updated (v2): better memory allocation checks (and no more limits for path size)
Updated (v3): update for bluez 3.9
As some of you may know, bluez 3.x dropped old pin-helper.
Now you have to use a passkey agent which communicate with hcid over dbus. And of course, kdebluetooth pin helper can't.
Probably we'll fix it in the future, with kde4 using directly dbus should be easy. In the meantime, you can use this patch i did (or this one in case you're using bluez 3.9), which transforms the "passkey-agent" contained in bluez-utils/hcid into an agent that can EXEC files, in the old way. Just download the file, go in bluez-utils build directory, than do bzcat bluez-pin-exec-patch.diff.bz2 | patch -p1 Then start it with "passkey-agent --default <your-old-pin-helper>". It will automatically exec the old pin helper when it's needed.
Updated (v2): better memory allocation checks (and no more limits for path size)
Updated (v3): update for bluez 3.9
As some of you may know, bluez 3.x dropped old pin-helper.
Now you have to use a passkey agent which communicate with hcid over dbus. And of course, kdebluetooth pin helper can't.
Probably we'll fix it in the future, with kde4 using directly dbus should be easy. In the meantime, you can use this patch i did (or this one in case you're using bluez 3.9), which transforms the "passkey-agent" contained in bluez-utils/hcid into an agent that can EXEC files, in the old way. Just download the file, go in bluez-utils build directory, than do bzcat bluez-pin-exec-patch.diff.bz2 | patch -p1 Then start it with "passkey-agent --default <your-old-pin-helper>". It will automatically exec the old pin helper when it's needed.
»
- RockMan's blog
- Login or register to post comments
The binary is not built
The binary is not built together with bluez. You have to write "make passkey-agent" in the "daemon" directory, if i remember correctly. Then you will have "passkey-agent" executable in there. Just copy it in your PATH and use it.