Anybody know what this actually means?
https://www.androidauthority.com/android-15-qpr2-linux-terminal-3498872/
The article's author thinks you'd basically run an arm64 debian image in
a container, but admits they're just assuming that based on chromeos. It
seems a little more than just packaging the Google Terminal app from the
play store into the base OS image, but I dunno how MUCH more...
I note I've wanted a "posix container" in android for quite a while:
http://lists.landley.net/pipermail/toybox-landley.net/2016-July/024590.html
Earlier discussions on here talked about "each app has a single UID",
"the paths are weird", "where is reliably writeable space", "adb shell
has far more permissions than the terminal app and only one really gets
regression tested", etc...
Sucking in a GPLv3 systemd environment that shares no plumbing with the
host OS seems less than ideal, but "what image would you put in there to
build Android under Android" isn't a small question either. Container
support so Android _can_ nest seems generally good, and hopefully no bad
assumptions get baked in. I'm mostly just wondering if there's a good
place to follow for more information...
Rob
P.S. Don't get me started on https://www.samsung.com/us/apps/dex/ , you
think a USB 3 hub that can both charge the phone AND forward video
through a USB to HDMI adapter would be a little more straightfoward, but
you go into Target and grab a USB-C to HDMI adapter and NOWHERE does it
say whether this is displayport that won't go through a hub or UVC that
will? Assuming you're running a version with driver support
(https://en.wikipedia.org/wiki/USB_video_device_class#cite_note-3) and
whether that's capture support or output support and what you'd have to
do to enable it... Ahem.
_______________________________________________
Toybox mailing list
Toybox@lists.landley.net
http://lists.landley.net/listinfo.cgi/toybox-landley.net
