Skip to main content

Tutkin diplomityössäni älypuhelinten hyödyntämistä maatalouskäytössä. Tutkimukseen liittyy GPS träkkäysohjelma, jota olen ollut kehittämässä jo lähes vuoden. Ohjelman tarkoitus on automatisoida maatalouteen liittyvän tyokirjanpidon muodostamista

Ohjelman on pystyttävä seuraavaan maanviljelijän liikkeitä koko vuorokauden. Ohjelman virrankulutus on pidettävä sellaisena, ettei se kuluta koko akkua loppuun ainakaan kymmeneen tuntiin. GPS palvelu on siis pystyttävä katkaisemaan väliajoin eikä muu puhelimen käyttö saa katkaista träkkäystä.

Android-implementaatiossani GPS kuuntelusta vastaa oma Androidin Service. Servicet sinänsä eivät ole erityisen soveltuvia tähän käyttöön, koska ne ajetaan samassa säikeessä muun ohjelman (käyttöliittymä) kanssa ja myös Servicen säie lopetetaan, jos laite menee näppäinlukkoon tai on käyttämättä jonkin aikaa. Ongelma ei poistu, vaikka Servicessä luotaisiin uusia säikeitä.

Ratkaisuna käytin WakeLockia, joka mahdollistaa näytön sammumisen ja näppäinlukon, mutta ei pysäytä prosessoria ja säikeet pysyvät päällä. Periaatteessa tämä on aika huono ominaisuus kännykkäohjelmalla, mutta paras löytämäni tapa pitää träkkäys hengissä. Jos GPS pollausintervalli pidetään yli minuutin mittaisena eli GPS on vähintään minuutin pois päältä ja taas minuutin päällä, virrankulutus pysyy melko inhimillisenä. Ohjelma lisää virrankulutusta noin 15mA.
private void startListening() {
  new Thread(new Runnable() {
   @Override
   public void run() {
    PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
    PowerManager.WakeLock wl = pm.newWakeLock(
      PowerManager.PARTIAL_WAKE_LOCK, "AlkioGPS");
    wl.acquire();
    Looper.prepare();
    while (!die) {
     mloc.requestLocationUpdates(LocationManager.GPS_PROVIDER,
       1000, 0, listener);
     try {
      Thread.sleep((gpsinterval / 2));
     } catch (InterruptedException e) {
      e.printStackTrace();
     }
     mloc.removeUpdates(listener);
     try {
      Thread.sleep(gpsinterval / 2);
     } catch (InterruptedException e) {
      e.printStackTrace();
     }
    }
    gpstimer.cancel();
    try {
     unregisterReceiver(rec);
    } catch (Exception e) {

    }
    wl.release();
   }
  }).start();
 }

Comments

Post a Comment

Popular posts from this blog

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...
Post a Comment
Read more

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

How my work has changed in the past few years

When I started at my current job 3ish years ago, we had nothing but a few PowerPoint slides and a Figma prototype. I recall talking with one of the founders, whom I had worked with some 10 years ago, and pointing out that the very next step after PowerPoint and Figma was still the same as it had always been: translating those slides and mockups into CRUDs, forms, and other basic building blocks. Sure, all the new fancy tools and frameworks (we had jQuery then) help, but I still had to tinker with very basic primitives like tables and forms. I could not just say, "here is a table, here is a form." Well, yes, technically I could, but I still needed to write a lot of code to make a working form or table. This was around the time of GPT-3, Copilot beta, and very early Cursor. I did attempt to use them, but they could only perform very basic tasks and were pretty much useless for frontend work. We, being one of the first-wave "ChatGPT wrapper" startups has naturally pus...
Post a Comment
Read more