You might want to go through that code again. Since only change needed is auto scan and pair.
Just check this logic with existing scan and pair logic in android
Also please make sure that BWD01 and BWD02 connect logic are same. If this is currently the case then scan , pair and connect might have some prob
My guess is the prob might exist between pair and connect methods.Compare this with android version
Regards,
Ajith
On Thu, Feb 10, 2011 at 12:44 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:
Hi,
OK I was not realy clear.
We have made a first android application which is just an adaptation of our application for non-android, and non-touch mobile. This first application is the one I call old software version (Let's call it BWD01). The application I'm developping do almost the same things but is specialy made for android mobile (Let's call it BWD02). With BWD01, the user have to touch the screen in order to launch a bluetooth scan and connect his android mobile to our product. In BWD02 the goal is to do this automaticaly : when the user launch the application, a scan is automaticaly started and normaly the connection is done auromaticaly (with the pariring if needed). And with this 'automaticaly' version, the android application has the bug I explain you.
Our product (the BlueWatchDog) has not change, it's the same for the two android application version (BWD01 and BWD02) (the product itself and also the firmware)
I hope it's more clear now. If you need more information please let me know !
Thank you for your help
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
Mobile : +4179 4509 566
Skype : laurent.lugon.moulin
On Thu, Feb 10, 2011 at 07:30, Ajith Kamath <sjce.ajith@gmail.com> wrote:
HiWhat are these old software versions. Which device was upgraded and what?Code doesnt seems to be having any prob and my guess is you have upgraded the device's(not phone) software.Do let me knowRegards,Ajith
On Wed, Feb 9, 2011 at 6:38 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:
Hi,
We have a LED on the device which is turned on when the bluetooth chip say that a connection is seting up. With the old software version it works perfectly, the LED is turned on and then the 'connected screen' is loaded on the mobile phone. But yet, the LED stil turned off and in fact, I can't use my device when the 'connected screen' is loaded on my mobile phone.
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
Mobile : +4179 4509 566
Skype : laurent.lugon.moulin
On Wed, Feb 9, 2011 at 12:27, Ajith Kamath <sjce.ajith@gmail.com> wrote:
HiOk, I understood the application. By looking into the code thats given, I dont think there is any probSince its probing in while loop regularly.When the device is connected to your mobile, it should be working fine. i think connection is completed .The device which you are using, Is it able to detect the connection setup complete?Regards,AjithOn Wed, Feb 9, 2011 at 3:59 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:
Hi,
I've try to add delay before, after, before and after but the result still unchanger...
It's not a headset it's a device used to protect your valuables, it checks the bluetooth connection and when it to far from the mobile phone (=> loose the bluetooth connection) an alarm is started.
Any more idea ?
Thank you
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
Mobile : +4179 4509 566
Skype : laurent.lugon.moulin
On Wed, Feb 9, 2011 at 05:02, Ajith Kamath <sjce.ajith@gmail.com> wrote:
HiChecked the logs. Everything seems to be fine.I'm not sure what the prob is. Try adding some delay before bluetooth socket connect takes place.this might be needed if you are connecting to some headsets/handsfree.If Still it doesn solve the problem.. Add logs upto jni level and send the logs.The logs which you have added so far does not point out any problems .Also tell what kind of device are you trying to connect to you mobile.?Regards,AjithOn Tue, Feb 8, 2011 at 7:40 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:
Hi Ajith,
I've add logs in the connectThread and connectedThread.
See the result in attached files.
Thank you for your help !
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
On Tue, Feb 8, 2011 at 06:10, Ajith Kamath <sjce.ajith@gmail.com> wrote:
HiSorry I rechecked logs again. BEGIN mConnectedThread seems to be called.my bad.Still please add logs before and after connect and sendRegards,AjithOn Tue, Feb 8, 2011 at 10:39 AM, Ajith Kamath <sjce.ajith@gmail.com> wrote:
HiFrom the attached logs, its unclear what is the error.Discovery seems to be stopped in an odd manner, but that should not generate any problemYou need to rig the code , add more logs.Since the connect thread was called, add more logs in Connect threadIt seems that "BEGIN mConnectedThread" is never displayed.I think there exists problem in connect thread. Please check this.Also what I meant by my previous question is that, What kind of h/w are you trying to connect to your mobile(Ex: headset, handsfree, carkit etc etc)Regards,Ajith
On Mon, Feb 7, 2011 at 6:16 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:
Hi Ajith,
You will find the logs attached.
I use our own hardware device. It's the product we develop : http://www.secu4.com/en/product.html
It's works realy good with the actual software so it's not a hardware issue. I'm developing the new version of the software related to our product and we change different things on the bluetooth connection procedure.
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
Mobile : +4179 4509 566
Skype : laurent.lugon.moulin
On Mon, Feb 7, 2011 at 12:01, Ajith Kamath <sjce.ajith@gmail.com> wrote:
please paste the logs. And what bluetooth h/w are you trying to connect to your mobile deviceRegards,AjithOn Mon, Feb 7, 2011 at 4:21 PM, Laurent Lugon <laurent.lugon@secu4.com> wrote:Hi all,
I use a hardware bluetooth device and I need to connect it to my mobile phone. I've follow the instruction on developer.android.com to set up a bluetooth connection but I still have a problem. When I'm connecting to the Bluetooth Socket with bluetoothSocket.connect() I don't catch any exception so according to the docs, that mean I'm connected to my device. The problem is I'm not... Here is my code :
private class AcceptThread extends Thread {
// The local server socket
private final BluetoothServerSocket mmServerSocket;
public AcceptThread() {
BluetoothServerSocket tmp = null;
// Create a new listening server socket
try {
tmp = mAdapter
.listenUsingRfcommWithServiceRecord(NAME, MY_UUID);
} catch (IOException e) {
Log.e(TAG, "listen() failed", e);
}
mmServerSocket = tmp;
}
public void run() {
if (D)
Log.d(TAG, "BEGIN mAcceptThread" + this);
setName("AcceptThread");
BluetoothSocket socket = null;
// Listen to the server socket if we're not connected
while (mState != STATE_CONNECTED) {
try {
// This is a blocking call and will only return on a
// successful connection or an exception
socket = mmServerSocket.accept();
} catch (IOException e) {
Log.e(TAG, "accept() failed", e);
break;
}
// If a connection was accepted
if (socket != null) {
synchronized (BluetoothConnectionService.this) {
switch (mState) {
case STATE_LISTEN:
case STATE_CONNECTING:
// Situation normal. Start the connected thread.
connected(socket, socket.getRemoteDevice());
break;
case STATE_NONE:
case STATE_CONNECTED:
// Either not ready or already connected. Terminate
// new socket.
try {
socket.close();
} catch (IOException e) {
Log.e(TAG, "Could not close unwanted socket", e);
}
break;
}
}
}
}
if (D)
Log.i(TAG, "END mAcceptThread");
}
public void cancel() {
if (D)
Log.d(TAG, "cancel " + this);
try {
if (mmServerSocket != null)
mmServerSocket.close();
} catch (Exception e) {
Log.e(TAG, "close() of server failed", e);
}
}
}
/**
* This thread runs while attempting to make an outgoing connection with a
* device. It runs straight through; the connection either succeeds or
* fails.
*/
private class ConnectThread extends Thread {
private final BluetoothSocket mmSocket;
private final BluetoothDevice mmDevice;
public ConnectThread(BluetoothDevice device) {
mmDevice = device;
BluetoothSocket connection = null;
// Get a BluetoothSocket for a connection with the
// given BluetoothDevice
try {
// device.createRfcommSocketToServiceRecord(MY_UUID);
Method m = device.getClass().getMethod("createRfcommSocket",
new Class[] { int.class });
connection = (BluetoothSocket) m.invoke(device, 1);
Utils.pause(100);
} catch (Exception e) {
Log.e(TAG, "create() failed", e);
}
mmSocket = connection;
}
public void run() {
Log.i(TAG, "BEGIN mConnectThread");
setName("ConnectThread");
if (mmSocket != null) {
// Always cancel discovery because it will slow down a
// connection
mAdapter.cancelDiscovery();
// Make a connection to the BluetoothSocket
try {
// This is a blocking call and will only return on a
// successful connection or an exception
mmSocket.connect();
} catch (Exception e1) {
Log.e(TAG, "connect failed", e1);
connectionFailed();
// Close the socket
try {
mmSocket.close();
} catch (IOException e2) {
Log.e(TAG,
"unable to close() socket during connection failure",
e2);
}
// Start the service over to restart listening mode
BluetoothConnectionService.this.start();
return;
}
// Reset the ConnectThread because we're done
synchronized (BluetoothConnectionService.this) {
mConnectThread = null;
}
// Start the connected thread
connected(mmSocket, mmDevice);
} else {
connectionFailed();
BluetoothConnectionService.this.start();
}
}
public void cancel() {
try {
if (mmSocket != null) {
mmSocket.close();
}
} catch (IOException e) {
Log.e(TAG, "close() of connect socket failed", e);
}
}
}
/**
* This thread runs during a connection with a remote device. It handles all
* incoming and outgoing transmissions.
*/
private class ConnectedThread extends Thread {
private final BluetoothSocket mmSocket;
private final DataInputStream mmInStream;
private final OutputStream mmOutStream;
public ConnectedThread(BluetoothSocket socket) {
Log.d(TAG, "create ConnectedThread");
mmSocket = socket;
InputStream tmpIn = null;
OutputStream tmpOut = null;
// Get the BluetoothSocket input and output streams
try {
tmpIn = socket.getInputStream();
tmpOut = socket.getOutputStream();
isConnected = true;
} catch (IOException e) {
Log.e(TAG, "temp sockets not created", e);
isConnected = false;
}
mmInStream = new DataInputStream(tmpIn);
mmOutStream = tmpOut;
}
public void run() {
Log.i(TAG, "BEGIN mConnectedThread");
while (isConnected) {
Utils.pause(5);
isConnected = checkConnection();
}
}
/**
* Check if the connection is still alive
*
* @return true or false
*/
private boolean checkConnection() {
synchronized (mmInStream) {
try {
int len = mmInStream.available();
if (len > 0) {// Checks the available amount
byte b[] = new byte[len];
mmInStream.readFully(b, 0, len);
mHandler.obtainMessage(MESSAGE_READ, len, -1, b)
.sendToTarget();
}
return true;
} catch (IOException ioe) {
Log.e(TAG, "disconnected", ioe);
connectionLost();
return false; // Connection is lost.
}
}
}
Thank you for your help !
Best regards
SECU4 SA
Laurent Lugon MoulinTechnical & Development Assistant
Technopôle 5
3960 Sierre – SwitzerlandOffice : +4127 4567 931
Fax : +4127 4567 935
Skype : laurent.lugon.moulin
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment