Skip to main content

Android ja Bluetooth


Android-ohjelma, jota teen töissä toimii kaukosäätimenä erilaisille moottorinohjaimille. Kaukosäädin toimii bluetoothilla. Androidin SDK:n mukana tulee hyvä esimerkkiprojekti bluetoothin käyttämisestä, jonka pohjalta on helppo aloittaa. Androidiin bluetooth muistuttaa mitä tahansa verkkosockettia jolla on sisääntulo ja ulostulostreamit, joihin voi kirjoittaa samanaikaisesti. Bluetooth toimikin testipuhelimellani (2.1) suhteellisen pienen työn jälkeen moitteettomasti.

Viime viikolla testasin laitteilla, joissa oli Androidin versiot 2.3 ja 4.0.1 ja näissä ei ollut toivoakaan saada yhteyttä testilankkuun. Ongelmat johtuivat vielä eri syistä molemmissa laitteissa. Pahinta oli että toimimattomuus oli satunnaista, joten en ollut täysin varma onko vika testilankussa vai puhelimessa.

Löysin muutaman Androidin ratkaisemattoman bugiraportin, joissa viitattiin käsittelemiini ongelmiin. Ratkaisuksi annettiin muutamia väliaikaisia korjauskikkoja, mutta nämäkään eivät auttaneet tapauksessani.

Ongelmien lähteenä on sokettiyhteyden muodostus, joka toimii blokkaavasti 2.1 versiossa, mutta ei muissa testaamissani laitteissa.
Log.i(BT_TAG, "Connecting");
btSocket.connect();
Log.i(BT_TAG, "Connected");
2.1-versiossa suoritus pysähtyy connect()-kutsuun kunnes yhteys on luotu, mutta muissa versioissa yhteys luodaan, vaikka sitä todellisuudessa ei ole. Yhteys katkeaa vasta kun sokettiin yritetään kirjoittaa jotain.

Ratkaisuna tein ylimääräisen kättelyn varmistamaan, onko yhteys todella luotu. Heti kun input ja output streamit on luotu lähetän outputtiin kättelykomennon ja jos vastaus saadaan, siirrytään vasta silloin yhdistetyyn tilaan. Jos vastausta ei saada, onneksi Android osaa itse heittää poikkeuksen ja sulkea soketin.

Tässä ei sinänsä ole mitään erikoista, mutta tuntuu turhalta, koska käyttöjärjestelmän pitäisi hoitaa Bluetooth-protokollan mukaisen yhteyden luomisen. Varsin ikävää on, etteivät eri Android-versiot toimi luvatulla tavalla.
private class ConnectedThread extends Thread {
private BluetoothSocket mmSocket;
private InputStream mmInStream;
private OutputStream mmOutStream;
private boolean isAvailable = false;

public ConnectedThread(BluetoothSocket socket) {
Log.d(BT_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();
} catch (IOException e) {
Log.e(BT_TAG, "temp sockets not created", e);
}
mmInStream = tmpIn;
mmOutStream = tmpOut;
//Handshake
write(HANDSHAKE);
// sendSuccessfulConnectionBroadCast();
}

public void run() {
Log.i(BT_TAG, "BEGIN mConnectedThread");
byte[] buffer = new byte[Protocol.RESPONSE_LENGTH];
int i = 0;
// Keep listening to the InputStream while connected
while (true) {
try {
// Read from the InputStream
// bytes = mmInStream.read(buffer);
int readByte = mmInStream.read();
Log.i(BT_TAG, "Read: " + readByte);
buffer[i] = (byte) readByte;
i++;
//Listen for the handshake confirmation
if (i == Protocol.RESPONSE_LENGTH) {
if (!isAvailable) {
isAvailable = true;
listenState = false;
sendSuccessfulConnectionBroadCast();
i = 0;
continue;
} 
GlobalHandler
.getHandler()
.obtainMessage(
GlobalHandler.MESSAGE_RESPONSE,
buffer).sendToTarget();
Log.i(BT_TAG, "Read: " + buffer[0] + " "
+ buffer[1] + " " + buffer[2] + " "
+ buffer[3] + " " + buffer[4]);
i = 0;
listenState = false;

}
} catch (IOException e) {
Log.e(BT_TAG, "Disconnected", e);
break;
}
}
}

Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

Canyon Precede:ON 7

I bought or technically leased a Canyon Precede:ON 7 (2022) electric bike last fall. This post is about my experiences with it after riding for about 2000 km this winter. The season was a bit colder than usual, and we had more snow than in years, so I properly put the bike through its paces. I've been cycling for almost 20 years. I've never owned a car nor used public transport regularly. I pedal all distances below 30km in all seasons. Besides commuting, I've mountain biked and raced BMX, and I still actively ride my road bike during the spring and summer months. I've owned a handful of bikes and kept them until their frames failed. Buying new bikes or gear has not been a major part of my hobby, and frankly, I'm quite sceptical about the benefits of updating bikes or gear frequently. I've never owned an E-bike before, but I've rented one a couple of times. The bike arrived in a hilariously large box. I suppose there's no need to worry about damage durin...

Emit structured Postgres data change events with wal2json

A common thing I see in an enterprise system is that when an end-user does some action, say add a user, the underlying web of subsystems adds the user to multiple databases in separate transactions. Each of these transactions may happen in varying order and, even worse, can fail, leaving the system in an inconsistent state. A better way could be to write the user data to some main database and then other subsystems like search indexes, pull/push the data to other interested parties, thus eliminating the need for multiple end-user originating boundary transactions. That's the theory part; how about a technical solution. The idea of this post came from the koodia pinnan alla podcast about event-driven systems and CDC . One of the discussion topics in the show is emitting events from Postgres transaction logs.  I built an utterly simple change emitter and reader using Postgres with the wal2json transaction decoding plugin and a custom go event parser. I'll stick to the boring ...