nolirium
commented
5 years ago Yes, I had the same frustration (with Tincore and similar) at one point. It took a lot of messing around before I managed to get it working.
It's been a while (a few CrOS versions) since I was looking into this, but assuming nothing's changed, IIRC to get uinput working in Android, you have to edit /opt/google/containers/android/config.json, adding uinput in as an allowed device with its major/minor numbers etc.
Previously I had added the details in manually (using the existing entries in config.json as a guide), but something like the following (courtesy of the Droidmote author) should also work:
patch_config_json() {
File="/opt/google/containers/android/config.json"
if ! grep -q uinput "$File"; then
cp $File /opt/google/containers/android/config.json.bak
awk '{print} /"devices": \[/ && !n {print "{\n\t\t\t\t\"path\": \"/dev/uinput\",\n\t\t\t\t\"type\": \"c\",\n\t\t\t\t\"major\": 10,\n\t\t\t\t\"minor\": 223,\n\t\t\t\t\"fileMode\": 438,\n\t\t\t\t\"uid\": 0,\n\t\t\t\t\"gid\": 0\n\t\t\t},\n\t"; n++}' /opt/google/containers/android/config.json.bak > /opt/google/containers/android/config.json
fi
}
netship02
I know this is not related but i am trying to get this working for days. I am trying to use tincore keymapper but it complains about "uinput" not supported by kernel. I can load (
modprobe uinput) from crOS shell but apps still complain. I check in crOs shell /dev/...uinputwas there but i if check within android subsytem no "uinput" was there. whole /dev/input folder was empty. Basically android subsytem also does not detect any keyboard or mice.