If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

[NOT WORKING] Carwhisperer

In BT4 because of the new bluetooth stack (bluez 4 instead of bluez 3.x) the tool carwhisperer doesn't work anymore.

It is possible to start it, it will connect to the headset (if default PIN was set correctly), but it doesn't record anything (it fills up the output file with zeros).

Maybe I screwed up something with the settings (however this is highly unlikely), but you know too that bluez 4 has no documentation at all, so figuring out how to change settings is really difficult.
I would highly recommend (if the newer kernel still makes this possible) to return to bluez 3.x.

Could you post the commands you used and their output to include error messages?
Maybe we can either help or get it fixed.
Thanks.

Well, it is pretty easy: setting up the default passkey is not possible (hcid.conf is missing), this could be fixed by using some Python script I found on the net. After that, it is able to connect to the BT headset (no more Access denied message), but recording doesn't work, all we got is noise (after SOX postprocessing).
I will look into the source code sometime, but maybe you can find out why this happens.

This might help, I will test it ASAP, if yes then please include the simple-agent and a short README file in the next Backtrack please.

EDIT3-final:
Well, I checked some stuff, and now I am able to connect to the headset, but all we got as replies are zeros, hcidump shows nicely how all the incoming packets contain only zeros, not valid data.
I tried to send out a test file, and see it it gets played back on the headset, but no luck with that either. It seems that somehow between the stack and the actual hardware some stuff simply disappears or gets cut out or I don't know.

To be short and simple: this part of the carwhisperer code fails with bluez-4 but it does work with bluez-3 (tested):

Re: [NOT WORKING] Carwhisperer

You didn't provide all of what Amael asked for, we see no output to commands. Try complying with a request so that we can help you.

Without any assistance from you, that big chunk of select code is useless to us. I can't say if it's a service= issue or a service issue, or whether or not the software is even associating correctly or just bailing down to saving blanks.

Again, help us to help you.

Still not underestimating the power...

There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

You didn't provide all of what Amael asked for, we see no output to commands. Try complying with a request so that we can help you.

Without any assistance from you, that big chunk of select code is useless to us. I can't say if it's a service= issue or a service issue, or whether or not the software is even associating correctly or just bailing down to saving blanks.

Under bt3 and bluez3 it did work perfectly. All I had to do is change some settings in the hcid.conf and restart the hci daemon. The changes I made were: auto authentication (or security mode or whatever it's called), pin 0000, lm mode MASTER, ACCEPT, class 0x050204 (phone).
I am currently trying to change the class and the LM mode with hcitool, so far no success.

mod: Finally changed the class and the lm mode, same result: only zeros in the output file.

Thanks for your help,
appreciate it a lot,
DOMy

I looked into things with hcidump and it seems that the headset is sending only zeroes, I don't know why, maybe it is a low level problem directly related to the BT stack.
Will continue researching the issue, but need some other people too, so please help me