>Google collects usage data for the Android CLI, such as commands, sub-commands,...

gowld · 2026-04-16T21:33:42 1776375222

Android CLI can write a tool that wraps android-cli and automatically passes the flag based on an env variable.

How would Google have enough data about a brand new product without collecting that data?

tredre3 · 2026-04-16T23:03:33 1776380613

> How would Google have enough data about a brand new product without collecting that data?

They wouldn't. But on the other hand, they probably have a large amount of in-house Android app developers on whom they can conduct such metrics collection. I wouldn't expect outsiders to have vastly different workflows, because when you get out of the happy path with Android all you get is pain.

Onavo · 2026-04-17T14:00:08 1776434408

Outsiders probably do have vastly different workflows. Google internally love to stick Bazel on everything and that's quite different (and overly complicated) compared to the usual Gradle route.

panzi · 2026-04-17T00:59:12 1776387552

`alias android-cli='android-cli --no-metrics'`

SJMG · 2026-04-17T02:11:20 1776391880

Uh do aliases load in non-interactive shells?

figmert · 2026-04-17T04:47:47 1776401267

Create a wrapping binary instead

    mkdir -p ~/.local/bin
    printf '#!/usr/bin/env sh\nexec android-cli --no-metrics "$@"' > ~/.local/bin/android-cli
    echo 'PATH="$HOME/.local/bin:$PATH"' >> ~/.zshenv

yorwba · 2026-04-17T07:18:17 1776410297

I'm pretty sure this will just call itself in a loop. You need to use the absolute path to the wrapped binary to distinguish it from the wrapper.

figmert · 2026-04-17T13:35:51 1776432951

Aah! Yes absolutely right! Using `exec command android-cli` would work I believe

oblio · 2026-04-17T08:55:59 1776416159

Also it's not a binary :-)

panzi · 2026-04-17T17:33:03 1776447183

Nope. I have this alias (a default on my distribution) and it's no loop:

    alias ls='ls --color=auto'

yorwba · 2026-04-17T18:35:09 1776450909

Creating an alias is not the same as putting an executable in your $PATH.

EdwardDiego · 2026-04-17T04:27:16 1776400036

You could export BASH_ENV to have Bash processes source a given file at startup.

Zsh has .zshenv, and Fish just has config.fish for everything with the ability to guard certain things within it to login only or non-interactive only.