[Offtopic] My new #AndroidDev missile :-)

Finally changed the hard drive to an SSD Crucial MX200. Am very happy with the boot time:

[Ubuntu 14.04]

22 secs from power button tap to usable desktop
15 secs from first “HP” splash to usable desktop

[Ubuntu 14.04 + Android Studio]

9 seconds to first window (gradle has to load project)
19 seconds from desktop to code that is already writable (gradle config… everything done)

[Android] Setting a quick instrumentation test environment with Espresso + JUnit + Mockito

1.- Gradle dependencies – global build.gradle

buildscript {
    repositories {
    dependencies {
        classpath 'com.android.tools.build:gradle:2.1.0'
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.4'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files

allprojects {
    repositories {
        maven { url "https://jitpack.io" }

2.- Gradle dependencies – app/build.gradle

defaultConfig {
    applicationId "..."
    minSdkVersion 15
    testInstrumentationRunner 'android.support.test.runner.AndroidJUnitRunner'

dependencies { 
    // ... testCompile 'junit:junit:4.12' 
    androidTestCompile 'com.google.dexmaker:dexmaker:1.2' 
    androidTestCompile('com.google.dexmaker:dexmaker-mockito:1.2') { 
        exclude group: 'org.hamcrest', module: 'hamcrest-core' 
    androidTestCompile 'com.android.support.test:runner:0.4.1' 
    androidTestCompile 'com.android.support.test:rules:0.4.1'
    androidTestCompile 'org.mockito:mockito-core:1.10.19' 
        exclude group: 'javax.inject', module: 'javax.inject'
        exclude group: 'com.squareup', module: 'javawriter' 
        exclude module: 'support-annotations' 
        exclude module: 'recyclerview-v7' exclude module: 'support-v4' 
    testCompile "org.mockito:mockito-core:1.9.5" 
    testCompile 'org.mockito:mockito-all:1.9.5' 

configurations.all { 
    resolutionStrategy.force 'com.android.support:support-annotations:23.0.1' 

3.- Sample test (androidTest/com/package/name folder)

@RunWith(AndroidJUnit4.class) @LargeTest
public class IssuesActivityTest {
    public IntentsTestRule<IssuesActivity> activityRule =
            new IntentsTestRule<>(IssuesActivity.class, true, false);

    public void shouldDisplayToolbarOnStart() {


    private IssuesActivity startActivity() {
        return activityRule.launchActivity(null);

And that’s all folks

[Android] Configuring checkstyle for your Android project

1.- app/build.gradle

apply plugin: 'com.android.application'
apply plugin: 'checkstyle' // <-- add this line

android {
    // ...
task checkstyle(type: Checkstyle) {
    configFile = rootProject.file('config/checkstyle.xml')

    source 'src'
    include '**/*.java'
    exclude '**/gen/**'

    classpath = files()

dependencies {
    //  ...

2.- Create a file and name it checkstyle.xml inside project_root/config

You can find the contents of this file here

3.- You can now execute the checkstyle from your terminal

./gradlew checkstyle

[Android] Adding Dagger2 to your project in 4 quick steps

1.- Gradle dependencies

[global build.gradle]

classpath ‘com.android.tools.build:gradle:2.1.0’
classpath ‘com.neenbedankt.gradle.plugins:android-apt:1.4’

repositories {
maven { url “https://jitpack.io&#8221; }


apply plugin: ‘com.android.application’
apply plugin: ‘com.neenbedankt.android-apt’

compile ‘com.google.dagger:dagger:2.0.2’
apt ‘com.google.dagger:dagger-compiler:2.0.2’
provided ‘javax.annotation:jsr250-api:1.0’

2.- Root Component

@Component(modules = MainModule.class)
public interface RootComponent {

void inject(BaseActivity activity);
void inject(App application);

// …. more injections here

3.- Main Module

public class MainModule {
App application;
LoggedUserFacade facade;

public MainModule(App application) {
this.application = application;
facade = new LoggedUserFacade(application);
// … More dependencies here

Context provideApplicationContext() {
return application.getApplicationContext();

// … rest of the @Provides-annotated methods

4.- Application class

public class App extends Application {
MainModule mainModule;
RootComponent component;

public void onCreate() {


private void initializeDependencyInjection() {
mainModule = new MainModule(this);
component = DaggerRootComponent.builder()

public RootComponent getComponent() {
return component;

@VisibleForTesting public void setComponent(RootComponent component) {
this.component = component;

[Android] Uploading a new version of a Library (e.g. PdfViewPager)

Just a quick reminder of how to deploy a new version of the lib.

First, update all the version numbers in module library/build.gradle:

ext {
    bintrayRepo = 'maven'
    bintrayName = 'pdfviewpager'

    publishedGroupId = 'es.voghdev.pdfviewpager'
    libraryName = 'PdfViewPager'
    artifact = 'library'

    libraryDescription = 'Android widget to display PDF documents in your Views, Activities or Fragments.'

    siteUrl = 'https://github.com/voghDev/PdfViewPager'
    gitUrl = 'https://github.com/voghDev/PdfViewPager.git'

    libraryVersion = '0.3.0'

    developerId = 'voghDev'

    licenseName = 'The Apache Software License, Version 2.0'
    licenseUrl = 'http://www.apache.org/licenses/LICENSE-2.0.txt'
    allLicenses = ["Apache-2.0"]

After changing version numbers and commiting all the changes, execute:

./gradlew bintrayUpload

Then you can go to bintray website (I suggest you to log in using Github, that’s what I do), and see your recently uploaded package inside the list.


Important note: It will take around one week to have your version available via gradle dependency. One of my uploads took 13 days, so don’t desperate.

On the top-right corner you will find an useful link for the uploaded folder in maven central repositories. Mine is:


There you can see if the library is available yet, or not.

Hope it helps somebody on his/her deploys 🙂

[Android] Sugar ORM is not creating tables on DB creation/migration

I was having this issue in two scenarios:

– Database creation from zero (app just installed)
– Database migration (for example from v2 to v3)

there were two tables that weren’t being created.

I discovered that they both had only one constructor, with parameters.
After adding an empty constructor, both tables were created.

public NotificationDBEntry() {

public ProjectDBEntry() {

So there are two choices to make it work:
– In classes with no constructor, it will work because the default one is the empty constructor
– In classes with a non-empty constructor, it is mandatory to add an empty constructor.

Hope this saves you time!