Tag: android

  • Utility Meter Reader: nice idea, flawed implementation

    Utility Meter Reader is a great idea for an app. Using the camera on your smartphone, snap a picture of your utility meter’s analogue dials, and through the power of some clever image processing, the app will return your meter reading. five-dial analogue kWh meter fasciaTraditional meters are a bit hard to read, as the dials rotate in alternate directions. You won’t realize why this is unless you get a chance to peek behind the fascia:

    the fiddly gear-train inside a five-dial analogue kWh meterThere’s an incredibly fiddly set of 10:1 reduction gears in there, so each dial registers a tenth of the one next to it. Because it’s a drive-train, adjacent shafts rotate in opposite directions. This serves to keep the cost of the meter down at the expense of having to think a bit about how to read the thing.

    We only have one dial meter on the house. It’s a 58 year old gas meter (same age as the house) and it’s certainly been around a bit:

    gas meter (but not Scarlett O'Gasmeter)

    Here it’s reading 969700 ft³, ignoring the lower dials; the units are hundreds of cubic feet. Let’s see how Utility Meter Reader made out with that:

    meter read failed

    Not very well, it seems. How about if I carefully process the image, sharpening it up, straightening it, and making it very high-contrast greyscale:

    not quite right: gas meter

    Hmm, the big figure’s completely wrong, but it got the rest.

    Okay, so let’s feed it a nice canned example, like this one (courtesy of Greeneville Light & Power System‘s “How to Read Your Electric Meter” page). Even I can see that this reads 46372:

    glps.net-sm46372According to Utility Meter Reader, though:

    2013-10-21_16.28.15

    The big figure’s off by one again. Very strange, especially since it picked up 4.23 for the first dial. In desperation, I clipped a small part of the GE meter image from my screen, and sent it to the app:

    2013-10-21_18.41.11

    2558 is the right answer. Phew! But the app only seemed to work on a well-lit, clean meter fascia with no glass in the way and an image taken by a rather nice DSLR. One out of three ain’t quite good enough.

    One concern I have about the app is that — while it allows you to e-mail a reading to your utility — it quietly BCCs a copy of that reading (which includes your meter details) to imeterreader [at] the-next-future.com. I didn’t see much of a privacy contract when I downloaded the app onto my Android phone, so I don’t know what they are going to do with my readings or personal data. So if it ever gets to working properly, I won’t use that feature.

    The app’s a good idea, but the implementation’s pretty far off where it needs to be. Of course, one could quickly whip up an implementation in OpenCV to identify dial circles and read the pointers. But do all this on your smartphone, however, and you’d fall foul of their US patent application.

  • The problem with Nook apps

    Compare and contrast:

    B&N Nook App Store

     

    Apple App Store

    Same game, 404% more expensive on the Nook. No free demo versions from B&N, either, but they do want to sell you books. Maybe before completely spinning off the Nook brand, they should let us run Android properly on our capable little tablets. Hey, sure beats dying of dysentery …

  • rootery nook

    OooOOooh! teh pritty! I’ve temporarily rooted my Nook Color to run the latest version of Android from microSD using the following instructions: [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards. – xda-developers. It’s a bit slow.

    Perhaps the hardest part was getting this screenshot. I got it using the Android SDK ddms tool, which took some hitting with a virtual Stillson wrench to get going. If, on OS X, the command adb devices returns a blank list, you will need to add the Nook’s USB vendor ID to the ~/.android/adb_usb.ini config file. Stop the server (adb kill-server), then enter the following command:

    echo 0x2080 >> ~/.android/adb_usb.ini

    then restart the adb server (adb start-server). adb devices should return something like:

    List of devices attached 
    2010830023232004    device

    and now all tethered Android joy can be yours.