<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Android on Sylvia Mirecki</title>
    <link>http://elijah.mirecki.com/categories/android/</link>
    <description>Recent content in Android on Sylvia Mirecki</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Dec 2014 16:45:59 +0000</lastBuildDate>
    <atom:link href="http://elijah.mirecki.com/categories/android/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Git Dependencies in Gradle</title>
      <link>http://elijah.mirecki.com/blog/git-dependencies-in-gradle-android/</link>
      <pubDate>Wed, 24 Dec 2014 16:45:59 +0000</pubDate>
      <guid>http://elijah.mirecki.com/blog/git-dependencies-in-gradle-android/</guid>
      <description>I found it a pain to get git dependencies working in Gradle, so I decided to write this ugly blog post for my future self and possibly some other desperately-searching Android developers.&#xA;The problem:&#xA;Including git project dependencies (e.g. a common library among your apps).&#xA;The solution:&#xA;Add this to your root build.gradle:&#xA;import org.ajoberstar.grgit.* buildscript { // ... dependencies { // ... classpath &amp;#39;org.ajoberstar:gradle-git:0.13.+&amp;#39; // ... } // ... } // .</description>
    </item>
    <item>
      <title>Coloured output for ADB logcat</title>
      <link>http://elijah.mirecki.com/blog/coloured-output-for-adb-logcat/</link>
      <pubDate>Wed, 02 Apr 2014 13:08:12 +0000</pubDate>
      <guid>http://elijah.mirecki.com/blog/coloured-output-for-adb-logcat/</guid>
      <description>I always love nice colour coded debug messages, but all of the adb wrappers that currently exist seem to be far more complex than they really need to be.&#xA;So I rigged up this little bash script to neatly colour logcat.&#xA;#!/bin/bash # Argument 1 is the optional log tag name. # Always should ERRORS from the android runtime because that is where the # exception message are generated from. [ $1 ] &amp;amp;&amp;amp; args+=&amp;#34;$1:* AndroidRuntime:E *:S&amp;#34; adb logcat $args | perl -pe &amp;#39; s/^I.</description>
    </item>
    <item>
      <title>Simulate Android D-pad through ADB</title>
      <link>http://elijah.mirecki.com/blog/simulate-android-d-pad-through-adb/</link>
      <pubDate>Fri, 21 Mar 2014 16:53:38 +0000</pubDate>
      <guid>http://elijah.mirecki.com/blog/simulate-android-d-pad-through-adb/</guid>
      <description>Recently, I had to deal with testing D-pad functionality in my app. Unfortunately, my device doesn&amp;rsquo;t have a D-pad.&#xA;So I rigged up this little script to simulate a dpad from the console of my desktop.&#xA;#!/bin/sh # Key codes may be found at: https://groups.google.com/forum/#!topic/tasker/LJhmfxT2mj8%5B1-25-false%5D SHELL_COMMAND=&amp;#34;adb shell&amp;#34; function send_keyevent { $SHELL_COMMAND input keyevent $1 &amp;amp; } function read_and_send_text_input { echo -n &amp;#34;Line: &amp;#34; read line $SHELL_COMMAND input text `echo $line | sed -e &amp;#39;s/ /%s/g&amp;#39;` &amp;amp; } while read -sN1 key; do # Catch multi-char special key sequences read -sN1 -t 0.</description>
    </item>
  </channel>
</rss>
