Database Info

Can we make a definitive reference for Bluetooth COM ports?!

Many people seem to be having problems using a Bluetooth GPS with nav software on a Pocket PC. I have had a few issues and trawled the net looking for answers and there seems to be a lack of reference information on this. This forum is probably the best hope of getting a definitive reference document compiled.
My XDA Pro (Universal) did not have the GPS Settings control panel installed in Settings/Connections until I edited the registry to make it visible. Why was it not enabled originally? Does it not work?
What does GPS Settings actually do? (My premise is that it virtualises the GPS Com port is that right?)
I have set up my BT GPS to be on COM8 by adding a new Outgoing Port. Using GPS Settings-
in the Programs Tab set "Program Port:" to be COM1:
in the Hardware tab set "Hardware portP" to be COM8: (why no 38400 baud rate setting??)
Is it safe to assume that any program that wants to use the GPS should connect to the virtual port COM1: or the actual port COM8:?
From a software perspective when trying to configure a program to connect to a GPS invariably the software will offer a list of COM ports to use e.g......
VisualGPSce (a free GPS monitoring tool from www.visualgps.net) offers a set of COM ports and SER01-SER32. If I connect this to SER08: it works fine but when I look at the settings again it has changed them to COM1: - Drivers\BuiltIn\Serial_dbg. (I assume this is the affect of using the GPS Settings above). Interestingly if I choose an invalid port then choose COM1: it fails to connect until I select SER08: again!!
Fugawi offers COM1: - COM8: but only works when I select COM8: Is this 'not playing the game' because it is talking to the real port and not the 'virtual one'?
A friend has Pocket Nav (Memory Map) which only offers a set of COM ports COM1,2,3,6,7,9 (all of which are named with the kind of device except 7) and none of them work. Is this software only offering COM ports that it believes to be active? It also seems to be not playing the virtual port game (If my premise above is correct). Why doesn't it see the GPS on COM8:?
Sorry for the long posts - lots of questions, a few suppositions and not many answers from me. I just hope the gurus who frequent this forum can provide some good technical answers which will benefit many frustrated (both by things not working but also through lack of techincal reference documentation) people.
Thanks
Clive

hi i'm experiencing the same problem, did you solve it ?
I can't find a useful COM port to connect to my java application using a Qtek 9000 with WM 5 and Creme JVM.
thank you.

I will surely spend a lot of time on this question in my forthcoming Bluetooth Bible (still don't know when to publish).

are you serious ..
or it was sarcastic ?
Yes, maybe i was not so clear writing my question, but i didn't want to write the same words clive_j wrote ...
I'm running a java application on a Qtek 9000 running Windows Mobile 5.1.1700 (build 14354.0.1.1) and using a Java Virtual Machine "Creme 4.12 for PocketPC".
While, via bluetooth manager, I'm able to connect my BTGPS (i.e. bluetooth GPS) only on COM0, or COM4, or COM8, my application can open only COM1, or COM2, or COM3, or COM6, or COM7, or COM9.
I configured GPS Settings on WM 5 just like clive_j did, and still i can't receive any data from the GPS, while VisualGPS can connect and receive data from SER08.
Did you have any idea ?

I found how to solve the problem.
don't know if menneisyys is interested.

Bluetooth DUN on CM 7.1.0

Hi all,
I spent a couple of days Googling around, trying to get Bluetooth DUN working on Cyanogenmod 7.1.0 on my Viewsonic GTablet.
After some hacking around with the source, I got it working. I can connect my GTablet to the internet through my Blackberry Torch on Rogers (in Ontario, Canada).
I've already posted my notes to the CM forums, but apparently since I'm a noob here I can't post the link to it, so here's my notes (direct copied from the CM forums):
Dial-up networking requires the chat binary, which is included in the standard Linux ppp package. For some reason, this binary was omitted from the Android ppp package, so I downloaded the Android 2.3.7 source, copied the chat source in to the Android ppp package and built it from scratch. The instructions for this were found at afewe DOT wordpress DOT com/android-arm-development/use-point-to-point-protocol-ppp-in-android/
Once the chat binary is installed in the proper location on the Android device (/system/bin/chat) it's just a matter of writing a pppd config and chatscript for your given provider. These configs can be found in the berry4all package at berry4all DOT com.
I copied the 'rogers' file from that package and put it in /etc/ppp/peers/rogers, then the rogers-chat file and put it in /etc/ppp/chatscripts/rogers-chat.
I modified the /etc/ppp/peers/rogers so that the last line, which calls the chat binary, reflected the proper locations of the binary and the chat script.
Finally, I removed the 'novj' option from the pppd config. Once the config was all up and ready to go, I went to the terminal and did:
$ su
# rfcomm bind /dev/rfcomm0 <BT MAC> <channel>
# pppd call rogers
And voila! A stable, bluetooth dial-up network connection through my phone.
I just wanted to throw out my notes first to make people aware that its possible and easy. If there's enough interest, I'll write a more detailed and specific step-by-step howto on getting it set up.

Hi,
I see that CM 7.1 includes "bluetooth tether" support now but it's not clear to me what this actually is. Does CM 7.1 include the DUN bluetooth profile? It sounds like you're using reverse tethering, i.e. you are using a Blackberry's data connection so you're using the DUN profile on the Blackberry and are using the CM device as a client?
I have a stock Desire S and am looking for DUN support so I can use the internet access in my car through the Desire's 3G connection. The car supports only DUN and PDANet doesn't work for some reason.
Thanks,
Tim

Looks like you're out of luck.... same story for my Benz with Comand Online Navcom system.
If you drive an MB like me, you'll have to wait for an update later this year (from MB that is)... or buy a BlackBerry.
Sent from my GT-P7500 using Tapatalk

Is it confirmed that mercedes benz are providing this update?
Sent from my GT-I9100 using Tapatalk

I very much doubt it (I'm also trying to get it working with Comand Online).
http://telematicsnews.info/2011/08/...connectivity-options-to-comand-online_ag2223/
Not great news.

tj80 said:
I very much doubt it (I'm also trying to get it working with Comand Online).
Click to expand...
Click to collapse
From the press release:
"An option for customers having phones without DUN support is the Mercedes-Benz “Bluetooth (SAP) telephone module - V4″, available early 2012. The new version (V4) offers UMTS capability, allowing fast data connection using customer SIM card or accessing SIM information from SAP (SIM Access Profile) enabled mobile phone."
and:
"... Furthermore Mercedes-Benz is in close talks with leading Android phone vendors to enable the DUN feature in their phones by default."
(I have Android 2.3 and Windows Phone 7.5 devices)

Yes, so we can pay £400 for a SAP module or buy a new phone if anyone actually launches an Android handset with DUN - remembering that Google appear to have zero interest so it will be manufacturer specific. Oh yes, I nearly forgot - Android doesn't have SAP profile support either!
I'd say the chances of Mercedes updating existing systems to work with phones which don't support DUN is virtually zero. Hardly ideal on a system which cost £2000...
Cheers,
Tim

I agree. It was a huge mistake of MB to go with this dead BT DUN protocol!

I thought Android phones do support SAP, isn't that why the car can dial a contact?

agupta80 said:
I thought Android phones do support SAP, isn't that why the car can dial a contact?
Click to expand...
Click to collapse
'fraid not, that uses PBAP (phone book access protocol).

[Q] Customizing NFC Field?

Hi,
I need to supply stable energy to a NFC-powered chip card that doesn't send any data of any kind over the NFC field.
The problem is that, when NFC enabled, the Nexus S only provides a pulsating NFC field : every 0.1 second (or even less), the NFC field is turned off for 0.1 second before it restarts.
So the goal would be to build an application that goes deep enough in the phone's settings to modify that pulsation and provide a stable field (or at least longer pulses).
Do you think this might be possible in a non-rooted phone?
In a rooted phone? Maybe using CyanogenMod as mentionned in an Internet article called "Uncovered: The hidden NFC potential of the Google Nexus S and the Nokia C7"?
Or do you think this won't be possible unless we have access to the Samsung firmware?
Thanks,
Gildas35

I get further in my researches and I am now sure that I can't modify the NFC field pulse in neither SDK or NDK.
So I am now browsing the Android source code (on that website: grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android-apps/4.0.3_r1/com/android/nfc/NfcService.java?av=f) to find where should I modify it.
But more and more I believe that it should be in the C part of the source code, not in the Java part. Especially in the libnfc layer?
Do anyone knows where I could find such a file?
Thanks,
Gildas

Help with dementia coffeemaker app.

Hi,
I am working on a coffeemaker that helps people diagnosed with dementia getting a bit of there independence back. It has to show the directions of the coffee making process. The coffeemaker has some sensors placed on it to register what steps have already been completed and has a arduino + bluetooth module for communication. I would like to build an app that makes it possible to show a particular page of the app>res>layout depending on what number it gets from the arduino. So basicly it should whent receives like a 4 from the arduino it should set the contentview to r.layout.4. I am a absolute noob at android programming and I have no clue where to start. I even cant get the Bluetooth connection to work. The arduino code is working so when I am using a android Bluetooth serial terminal I can communicate with the arduino.
So it has to fetch the data of the incoming bluetooth (serial) data and according to that data view a page on the app.
I am also able to create the layoutfiles with the desired text and pictures.
Do you guys have some tips and like a good tutorial for me or some help/advice?
I have looked at the android development pages but I simply cant get it to work.
Thank you in advance,
Marijnsp

How can I use my Android Phones to remember more than 200 Paired Bluetooth devices?

• Our In house app communicates with Bluetooth device (In house) via an Android Phone.
• We require a device (Android) to store pairing information for more than 200 devices (Bluetooth)
• Currently, we are losing the pairing information in our devices (Android) after more than 100 devices are paired.
* The paired device name is not lost, but it asks for re-pairing.
* If we cancel the pairing request, the Bluetooth device un–pairs with Android (device).
• We have conducted the same test with various Android devices and the same issue happens.
• We have googled various forums and observed that there is practically no limit for Bluetooth devices to be paired.
* We need your help to solve the issue so that our device can remember pairing information for more than 200 devices.
• If any custom app could be developed to persistently store pairing info locally, outside Android default file system and further to be read from there while connecting the device.
Please guide us on relevant APIs, permission sets required if any.

MOD ACTION:
Thread closed as duplicate. Follow the original HERE