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

Post a Comment

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...
Post a Comment
Read more

"You are a friendly breadwinner"

A recent blog post by Pete Koomen about how we still lack truly "AI-native" software got me thinking about the kinds of applications I’d like to see. As the blog post says, AI should handle the boring stuff and leave the interesting parts for me. I listed down a few tasks I've dealt with recently and wrote some system prompts for potential agentic AIs: Check that the GDPR subprocessor list is up to date. Also, ensure we have a signed data processing agreement in place with the necessary vendors. Write a summary of what you did and highlight any oddities or potentially outdated vendors. Review our product’s public-facing API. Ensure the domain objects are named consistently. Here's a link to our documentation describing the domain. Conduct a SOC 2 audit of our system and write a report with your findings. Send the report to Slack. Once you get approval, start implementing the necessary changes. These could include HR-related updates, changes to cloud infras...
Post a Comment
Read more

RocksDB data recovery

I recently needed to do some maintenance on a RocksDB key-value store. The task was simple enough, just delete some keys as the db served as a cache and did not contain any permanent data. I used the RocksDB cli administration tool ldb to erase the keys. After running a key scan with it, I got this error Failed: Corruption: Snappy not supported or corrupted Snappy compressed block contents So a damaged database. Fortunately, there's a tool to fix it, and after running it, I had access to the db via the admin tool. All the data was lost though. Adding and removing keys worked fine but all the old keys were gone. It turned out that the corrupted data was all the data there was. The recovery tool made a backup folder, and I recovered the data by taking the files from the backup folder and manually changing the CURRENT file to point to the old MANIFEST file which is apparently how RocksDB knows which sst (table) files to use. I could not access the data with the admin tool, ...
Post a Comment
Read more