Notices

should rtcom-eventlogger-async have been pulled in automatically (incorrect dependancy list in control file)? not sure what to check but librtcom-eventlogger0 and librtcom-eventlogger1 are installed along with corresponding librtcom-eventlogger-ui files and librtcom-eventlogger1-async. surely they should depend if they provide access.

edit: apparently librtcom-eventlogger1-async does't list it as dependancy.

might have to dig out the n95 and try pairing that just to check out results.

it may also be worth noting for other users that there are at least 2 different manufacturers for blue+me that i know of. first shipped with early 500s, punto etc which needed a seperate adaptor to work with iphone. it only had 32mb RAM iirc and sturggled cards over a few gig and when combined with ecodrive (not that you use that on an abarth ;p ). frequently hear of people having to disconnect battery to reset it after it screwed up, myself included after it took out steering wheel controls.

the second i know of is made by a different manufacturer and replaces more parts of the MS Auto 4 (yuck) system with there own. it doubles the RAM and seems to be far more stable. doesn't need iphone adaptor and features aux in as well. due to continued faults i now have one of these, minus the aux plug. Firmware is incompatible between the two.

i alsol noticed another dbus error in the syslog regarding mce, haven't a clue with that one, will have to check elsewhere.

I don't have good news for you. It seems that TomTom GO 950 use only AT commands which aren't supported by N900. It's on my TODO list but don't hold your breath. It hasn't so high priority

Sure. It's my mistake. I didn't want to force the installation of rtcom-eventlogger-async but I forgot it isn't installed at all then

Yes. Please try that and share the result.

Have you been successfull with Petrovich? Did you get another result with Petrovich tool?

Can you provide more details? What dbus error are you talking about?

Different but difficult (for me) question: how can i find out which profile a headunit is using, IrMC or PBAP? And if IrMC, which level?

You can see it only in obexd debug output and I don't know what you mean with IrMC level.

If you miss call history in CSSU-T let's install rtcom-eventlogger-async:
If you want to know what is supported you have to take a look into the obexd source code (plugins/irmc.c).

the mce error in question is:
been doing some digging regarding name ordering, i think the blue+me is to blame. seen reports of latest update doing the same for iphone, blackbery.

http://www.traud.de/gsm/IrMC.htm

I have a new syslog with obexd.
I was able to, you had to restart the N900 and just try to connect to the bluetooth and make an attempt to send a file on the N900.

IrMC level implemented in obexd is IEL: 2 (from source code).

I see boot there correct obexd initialization and that's all. I don't know if you even have paired the computer with N900.
Let's try to remove pairing from computer and also from N900 (Settings -> Bluetooth -> Device(s)). For sure you can also:
1) kill obexd
2) stop bluetoothd
3) remove content of /var/lib/bluetooth
4) enable bluetooth debug (in /etc/event.d/bluetoothd change "exec /usr/sbin/bluetoothd -n" to "exec /usr/sbin/bluetoothd -n -d"
5) shutdown the phone
6) start the phone
7) pair phone with the computer
8) try the file transfer