09-05-2008 10:10 AM
Hello, I need to develop an application that communicates with other Blackbery devices over bluetooth. I did this previously on other mobile phones over JSR82 and now need to get the app blackberry specific. Questions are:
Thanks for assistance.
Solved! Go to Solution.
09-05-2008 02:55 PM
2. Do you mean in the BlackBerry Simulator? This can be done with a Casira board. Otherwise you can debug your application on a real BlackBerry by connecting it to your PC and select Debug, Attach To, Handheld, your PIN in the BlackBerry JDE.
3. Yes, OBEX is supported in BlackBerry handheld software version 4.2.1 and higher. The link below explains this further.
What Is - Bluetooth support on BlackBerry devices
10-16-2008 11:37 PM
I am using a handheld blackberry to debug my application, but i think even to debug the application it needs to be signed in.
Am getting an exception in the debugger and when i stop debugging , it displays messeage in BB, that the api is secure.
is there any workaround to just run the application in debug mode without signing, i just need to verify the bluetooth PC application
with a sample application in BB. kindly suggest.
Thanks and regards
10-17-2008 12:23 AM
I dont think you can do this without signing. Signing is inexpensive process. Once you order signing keys ($20) and receive that usually happens in 2-3 days you can sign then unlimited number of BB applications (actually 2147483648 times).
10-17-2008 01:45 AM
01-06-2009 10:13 AM
i am playing with javax.bluetooth/javax.obex apis
and i am experiencing lockup when i use a while loop
to wait for service discovery to finish. this will freeze
the curve (4.2.2.xxx). and when i take out the battery
and try to run my program again, the curve does not
run it. so my question is, does the OS blacklist
programs that crash it?
There is OBEX Object Push and OBEX File Transfer.
Does the blackberry support the latter for file browse?
01-08-2009 02:45 PM
01-08-2009 03:25 PM
The following statement worries me
"a while loop to wait for service discovery to finish".
I suspect the while loop is running on the Main Event Thread, and this is why you are seeing the device 'lockup'. I suspect the best approach would to have some sort of event that is driven when the discovery completes, rather than have a while loop that waits for it.