@DanHulme I still couldn't get it right, putting -d 'tel:*#06#' or -d "tel:*#06#" still returned * only on Nexus 5, Android 6.0.1, stock Phone app. Perhaps something-dependent related?
It's data for Intent, I guess it's considered as URI
However.... it didn't work just like I expected... dialing/calling *#06# using ADB will return UNKNOWN APPLICATION. It seems the phone app only listening to the input (using input text *#06# worked, but I have to get the focus of the dial input first).
In any case, I don't have simple solution for that question...
There must be a component actively listening to whatever is getting typed into default dialer and whenever the number matches, it shows up that IMEI fragment.
@AndrewT. I don't know. This is something that SE has to do for us, so maybe try and attract the attention of our community manager. It seems to be an oversight that it wasn't updated when the site design was.
one of the easiest way of doing that (put the code in onCreate):
EDIT: addied wikipedia free opensearch (if https://en.wikipedia.org doesn't work try http://en.wikipedia.org)
AutoCompleteTextView actv = new AutoCompleteTextView(this);
actv.setThreshold(1);
String[] from = { "name", ...
Let's say I'm planning to buy a new Android device. I have a certain list of criteria for the device. I want to know which devices fit most or all of my criteria, and possibly get feedback from users who have already tried the devices in question.
Would this be on or off topic here?
If it's off...
It kind of worked, it displayed *#06# on the dialpad, but nothing happened afterward (no IMEI popup). It's on Nexus 5, stock Android 6.0.1 though, so it might be dependent to something.
hmm, I need a better process for recording GPS tracks, editing them (to trim the start and end), and showing them on a map
I've been using GPSLogger to record, and it can automatically send the tracks to Google Drive (or other cloud storage). But the editing them afterwards is cumbersome.