All, >Hello, >Brad Midgley schrieb: >> Artem, >> >> It may not be the best way, but I modified simple-agent from tests >> with a hardcoded pin, then I run it in the background at startup. >> Replace 5555 with your pin. >Thanks for your reply. >I have tired this. It works only with the 1st bluetooth device in the >system. It does not work with my 2nd bluetooth device. So it is not >useable for me. >Are there any other passkey-agents available? >Thanks, Artem I also have a similar issue, only mine involves Linux embedded on a device. I have no agent running on the device at this time and therefore pairing isn't working (which makes it hard for anything else to work). At this point, I can either put Python on the device and use the simple-agent python script to start the agent (which may be a job in itself), or I can try and fix the test/agent.c program to suit my needs. My question is, how hard would it be to fix the agent.c code myself? It seems that it is self contained and therefore not impossible to fix myself. But, could it be that since I am new to dbus and agents, I am not seeing the entire picture? Could someone lend me some assistance and then I could submit my work back to the group? My background is EE/Computer Eng. and I have been programming in C/C++/Java for almost 20 years now. Naturally, the problem for me is that I have a deadline looming (beginning of June) so I need to have something working sooner rather than later. Any and all comments are welcome. Thank you, Scott Wilson -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
