Well... back to DebugViewer and send me that logfile.
Okay, I messed around with the phonebook reading a little more and I still can't get it to work. I'm 99.9% sure that I made all the changes that we did last time. When I look through the logs the new version outputs:Originally Posted by zorro
----------------------------------------------------------------------------
3/11/2005 9:46:19 AM COM: <
+CPBR: (1-201),80,30
OK
----------------------------------------------------------------------------
3/11/2005 9:46:19 AM COM: <
OK
----------------------------------------------------------------------------
when I click on refresh phonebook. Previously, it would output that and then it would start receiving the phonebook entries which would be listed in the second portion of what I pasted. Now it doesn't list anything and just says okay. Any ideas?
Well... back to DebugViewer and send me that logfile.
Skinning to go... VisualDesigner2!
So what is the fix for the ResString error? I have a Nokia 6230 on a Win2k machine. I downloaded the new Test app above and, when it starts, it asks if I have a Motorola phone, then when I test the winachsf0 line gives me:
ERRORAT+CSCS=?;+CRC=?;+CLIP=?;+CNMI=?;+CMER=?<cr>< lf>
<lf>
ERROR<lf>
ERROR
But all of the other lines give me the ResString error. I've installed widcomm4 and my Nokia Suite works fine with the pc. I have port 7 selected in the config.
Epia-M II M10000 Nehemiah WinXP sp2 Travla C134 case Carnetix 1260 power Xenarc 700TS XM Direct Toslink Extigy USB 5.1 Garmin GPS18 Linksys 802.11g wireless Nokia 6230 Bluetooth Memphis Amps Focal Speakers Frontend: RoadRunner
There is an updated version of PhoneTest for download.
ResString error means: There is no respose on opening the port.
If it works with the Suite, why don't you try COM7?
Skinning to go... VisualDesigner2!
Z picked this up after finally buying a mic for my install:
When making/recieving a call the headset profile is initiated - but when the call is cut off by either party the headset profile is still active which is a pain as it means i have to lose the bt connection in order to use my phone again - also if i try to make another call after hanging up no sound or vioce can be heard either over the BT connection or thru the phone
is phoco Deinitialising the headset profile properly as this is all i can think of
Thanks - Nick
PhoCo isn't dealing with the Headset Profile at all.
Skinning to go... VisualDesigner2!
audio gateway?
Thats strange as the headset profile is showing on the phone - could XP be doing that? i hear that windows "chime" when phone ringing
Widcomm is doing this. The chime you hear might be an "Audio Notification" you have configured in the Headet properties.
Skinning to go... VisualDesigner2!
So can phoco not kill the connection at the end of a call?
Originally Posted by OriginalNick2
anyone else having this prob?
Bookmarks