Bluetooth serial port communication between e72 and a bluetooth module
-
The QuteMessenger works on PC as well. You just have to take a look at how to make QBluetoothZero work on Windows. The code of QuteMessenger works without change. So that could be of use for you.
-
Im pretty if not almost sure that no qutemessenger is needed on windows to make it possible to send text from mobile to windows terminal software that makes a use of serial port communication.
I'm also sure that it will work like you said, but that solution will not help me on the diy BT module side since its pure hardware based communication.
If i knew better the coding of s60, there whould not be any problems.
I usually code everything in one main() function and this QT is a little object based i have only been coding c++. So its a bit confusing.But ok. I will continue my investigation.
-
i wish i knew what i did to get it work. Anyways now the communication works.
Well one thing was, that i brought back the comparison of the SPP service.
I named the rfcomservice name as SPP.
I gave the BT module service name SPP.Then the comparison worked.
I also reverted by uninstalling SDK 1.1.4 and the installing 1.1.2 while trying to get TRK agent working on E72. But i didn't get it working...
Now i just need to strip off the unnecessary applications and i'm talking business. NOT but my hobby is on.
Thank you again for the help you gave.
So once again. I reverted the qutemessenger back to original with the difference that i commented out the fileexchange. So only chat selection possible. Otherwise the same as original. Well of course i changed the
rfcommServerServiceName = QString("SSP");
QString exprectedServiceName("SSP");So if you guys wondering the same thing as i did.
Change the service name of your bt module to the same as in the qutemessenger.cpp file and its good!
Also spend one week banging your head on the table or floor! -
Actually now i think i know what the problem was of course in addition of the expectedSrvice tag.
So i had detected my diy BT module from the mobilephone with the old code stating some other if non servicename. I detected it again deleting it first from the phone (known devices) and detected it again. I think it has to do something with the DIY BT module UUID (Universal unique ID) that maybe is changing each time the diy module is reconfigured. So i had the weird problem yesterday also, didn't work at all but then i tried to recognize the BT module again and the suddenly it started working... So i think that was the issue in many of non-working cases!