dlew

public static Action1<Throwable> crashOnError() {
    final Throwable checkpoint = new Throwable();
    return throwable -> {
        StackTraceElement[] stackTrace = checkpoint.getStackTrace();
        StackTraceElement element = stackTrace[1]; // First element after `crashOnError()`
        String msg = String.format("onError() crash from subscribe() in %s.%s(%s:%s)",
            element.getClassName(),
            element.getMethodName(),
            element.getFileName(),
            element.getLineNumber());

JakeWharton

/**
 * Show the activity over the lockscreen and wake up the device. If you launched the app manually
 * both of these conditions are already true. If you deployed from the IDE, however, this will
 * save you from hundreds of power button presses and pattern swiping per day!
 */
public static void riseAndShine(Activity activity) {
  activity.getWindow().addFlags(FLAG_SHOW_WHEN_LOCKED);

  PowerManager power = (PowerManager) activity.getSystemService(POWER_SERVICE);
  PowerManager.WakeLock lock =

CDRussell

Maven + Google Play Services

The recently released version of Google Play Services presents itself as a library project with string and attribute resources coupled with a .jar in the libs/ folder that has been compiled against internal APIs.

While this is convenient for users of IDEs or Ant, it presents a problem for those using proper build systems (e.g., Maven, Gradle) with dependency management. Inside the .jar there are a lot of classes which reference static attributes on the com.google.android.gsm.R class. This means that