hm... i added the phonebook last night. i exported it from outlook adressbook, renamed it and put it in mediaportal directory like you wrote it in your guide. so i don´t know what i´ve made wrong but every call on my cellphone kills mediaportal. after uncheck phonebook in setup the plugin works normally... :| other problem is the automatic reconnect. after standby i can see the pc in my phone, the phone to see on the bluetooth control panel too. the settings are all ok. but it doesn´t work. i have to reconnect the phone manually. but then DUN is set to another com port in bluetooth settings. so i have to change this in pluginconfigurations too. then it works fine until the next standby...
hi ya the phonebook method is not ideal yet but i'm still looking for a better solution, all phones and e-mail programs have different formats so not too sure what to do. one option that i'm looking at is using the my contacts plugin database which i think might be the best. if you want to use the phone book in the mean time you can use excel and but the name in colum a and the first number that relates to that name in b and the 2nd in c etc. then the next name in 2A etc. i'm also looking at the standby problem. does the phone change the com port it's using after it returns form standby?
ok thanks i have another version do you think you could try it out and if the bug is still there send the log. sorry i cant do it my htpc is connected to the tv so i cant read text in windows properly.
some phones don't support the at commands used. to test if that is the problem go to start > programs > accessories > communications hyper terminal and open a connection on that comport then type the command at+clip=1 or +clip=1 if it returns ok it will work. the next version will show incoming calls for unsuported phones but will not be able to show the number because they dont support this.
just made a quick change and put up the new version that supports phones that dont support caller id. just set it up in the settings. it should be on the download page soon after it is reviewed and should work with your samsung.
There's two reasons why this won't work on a Windows Mobile.
First Microsoft removed Bluetooth DUN from WM5 AKU3 and later.
Second, Windows Mobile doesn't support AT commands. Instead TAPI is used. If I read this correct, WM can also supply contact information from the phone book. This might be out of scope for boozelclark though