Skip to main content

Android Bluetoothsocket

Bluetoothyhteyden muodostaminen koitui projektin haastavimmaksi osuudeksi. Eri Android-versiot ja puhelimet toimivat eri tavoin kun muodostetaan laiteyhteyttä. Lisäksi käytettävä Bluetoothrauta ja Android eivät tykkää toisistaan (http://stackoverflow.com/questions/9052460/with-just-one-particular-bluetooth-spp-module-createrfcommsockettoservicerecor).

Ratkaisuna ongelmaan ohjelmassa käyttäjä voi valita mitä yhdistystapaa käytetään. Jos laiteyhteyksiä ei saa muodostettua, käyttäjä voi vaihtaa yhdistystapaa. Keräsin kaikki löytämäni bluetoothyhdistystavat, joilla jokaiseen testipuhelimeen löytyi oikeat asetukset.
/**
  * Luo socketin laitteeseen. Huom! yhdistämisessä paljon eroja eri
  * laitteiden välillä. Katso API-levelit ja android versioiden vastaavuudet
  * Androidin nettisivuilta. 

  * 

  * Yhdistystapaa voi muuttaa asetuksista. Oletuksena on neljä erilaista tapaa. Kts. 
  * @param device
  * 
  * @throws IOException
  */

 private BluetoothSocket createBluetoothSocket(BluetoothDevice device)
   throws IOException {
  try {
   final Method m;
   BluetoothDevice hxm;
   Log.i(BT_TAG, "Connection "+ MainActivity.CONNECTION_METHOD);
   switch (MainActivity.CONNECTION_METHOD) {
   case RFCOMMSECURE:
    return device.createRfcommSocketToServiceRecord(REMOTE_UUID);    
   case REFLECTION_RFCOMM:
    m = device.getClass().getMethod(
      "createRfcommSocketToServiceRecord",
      new Class[] { UUID.class });
    Log.i(BT_TAG, "createInsecure");
    return (BluetoothSocket) m.invoke(device, REMOTE_UUID);
   case REFLECTION_NOUUID:
    hxm = BluetoothAdapter.getDefaultAdapter().getRemoteDevice(
      device.getAddress());

    m = hxm.getClass().getMethod("createRfcommSocket",
      new Class[] { int.class });
    return (BluetoothSocket) m.invoke(hxm, Integer.valueOf(1));
   case REFLECTION_INSECURE:
    hxm = BluetoothAdapter.getDefaultAdapter().getRemoteDevice(
      device.getAddress());
    m = hxm.getClass().getMethod("createInsecureRfcommSocket",
      new Class[] { int.class });
    return (BluetoothSocket) m.invoke(hxm, Integer.valueOf(1));
   }
  } catch (Exception e) {
   Log.e(BT_TAG, "Could not create Insecure RFComm Connection", e);
  }
  return device.createRfcommSocketToServiceRecord(REMOTE_UUID);
 }

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

Extracting object properties from an IFC file with IfcOpenShell

Besides the object geometry information, IFC files may contain properties for the IFC objects. The properties can be, for example, some predefined dimension information such as an object volume or a choice of material. Some of the properties are predefined in the IFC standards, but custom ones can be added. IFC files can be massive and resource-intensive to process, so in some cases, it helps to separate the object properties from the geometry data. IfcOpenShell  is a toolset for processing IFC files. It is written mostly in C++ but also provides a Python interface. To read an IFC file >>> ifc_file = ifcopenshell.open("model.ifc") Fetch all objects of type IfcSlab >>> slab = ifc_file.by_type("IfcSlab")[1] Get the list of properties >>> slab.IsDefinedBy (#145075=IfcRelDefinesByType('2_fok0__fAcBZmMlQcYwie',#1,$,$,(#27,#59),#145074), #145140=IfcRelDefinesByProperties('3U2LyORgXC2f_hWf6I16C1',#1,$,$,(#27,#59),#145141), #145142

Hubristic developer

Almost half of any Finnish generation goes through a shared experience: the conscript army. An integral part of that experience is learning military slang, a set way people in the army talk. The stories told with said jargon often spread outside of the barracks. It is not uncommon to hear strangers bonding together over beers reminiscing and feeling nostalgic about freezing cold nights spent in tents. There is a similar phenomenon detectable among us coders. To be part of the coder tribe, there is at least one type of story that one must master. That is - of course - ranting about legacy codebases. "Can you believe how much of a mess the previous coders left? Hear, hear!" There is no better way to onboard a new team member than to blame some previous B-team for all the murky parts of the system at hand. This can be seen as harmless, a subject for a good  meme . Rarely do we hold real grudges against "the legacy folk" and can be the best of friends in a social gather