<urjaman>
There was a time when google shipped their CrOS android thing on the C201 CrOS firmwares (but you had to enable it with some magic flags) ...
<urjaman>
then they decided not to actually enable it for the C201 and removed the whole thing
<macc24>
android apps work fine on my c100pa, why wouldn't they on c201pa?
<urjaman>
... it ran fine enough, like for what the C201 is ... i played most of GTA Vice City on it
<macc24>
now to just make some instructions on anbox...
<urjaman>
hmmmmm let me check the CrOS device ... but i'm fairly certain they removed the whole android image from them
<macc24>
on my c100pa android apps work just fine
<macc24>
i am now running one
<urjaman>
hmm i forget where in the rootfs the image is/was, tho can't find it quickly ... but the C201 rootfs is 2.0G, has 949M of things in it ... i dont think that includes android
<urjaman>
i think it was pretty full with the android image shipped :P
<urjaman>
so just for curiosity, df -h the C100pa and tell me the rootfs line?
<macc24>
rootfs?
<macc24>
/dev/root?
<urjaman>
yes
<urjaman>
ChromeOS itself
<macc24>
2G, 1.4G used
<urjaman>
yeah the C201 is 2G, 949M used
<macc24>
i have some trash on my c100pa
<macc24>
wait, MyFiles are separate partition
<urjaman>
the rootfs is read-only fixed... unless you changed that ofc
<urjaman>
but even then it'd be kinda stupid to stuff things in there since it ... well back when updates happened, would be wiped on every update
<urjaman>
actually is the android support like actually enabled by default on the C100PA?
<macc24>
by the way, how's the situation with u-boot on veyron devices?
<macc24>
yeah it was
<urjaman>
I guess it's because of the touchscreen then
<urjaman>
like they thought it was useful enough with a "tablet-like" device, but decided to remove it from the entirely computer-like
<urjaman>
(well, laptop-like...)
<urjaman>
I haven't tried u-boot in half a year idk, but switftgeek and I did fix it once like 2020-05 ... so almost a year ago again
<macc24>
wait what
<macc24>
oh it's not 2020 anymore
<urjaman>
but yeah with the amount of testing it has gotten (one or two folks making it boot once a year or so :P) i still wouldnt expect it to be quite plug-and-play ... and theres still some things that dont work (eg. i think only one of the USB ports on the C201 works... but one is enough to do an USB boot so... lazy.)
<macc24>
on odroid go advance it's even worse xD
<macc24>
there is no display, no usb, nothing
<macc24>
just enough u-boot to run mainline linux from sd
<urjaman>
hmm now i'm like... wanna try putting a C100 rootfs on the C201
<urjaman>
I think i can get the rootfs from google just by making a C100 recovery USB ... how do i make it install nice tho (I expect it to go very "HEY! Wrong device!" by default :P)
<macc24>
i wish you luck
<macc24>
i don't use chromeos other than for android apps
<urjaman>
yeah i have my chromeos-running C201 just as a youtube player / ssh device / something with chrome on it... but yeah android used to be nice to have
<urjaman>
(it does only have 2GB of RAM tho... but that's also part of why it's not running generic linux... chromeos deals with low ram pretty ok by default)
<macc24>
when i ran linux on my c100pa it was fine
<macc24>
ssh on chromeos bad in vim or whatever
icecream95 has quit [*.net *.split]
icecream95 has joined ##panfrost-offtopic
icecream95 has quit [Ping timeout: 244 seconds]
<urjaman>
yeah i mean i ran linux for a while on the 2GB C201... I just prefer running it on the 4GB one :P
<urjaman>
also another sidenote: there are still 2 veyron devices getting chromeos updates, tiger and fievel (AOpen Chromebase Mini and AOpen Chromebox Mini)
<urjaman>
they arrived on the market in 2017 so they still have a year or so (Feb 2022) of updates... it's just f'ed up to me that like... you're supporting some veyrons, why not all veyrons...
<urjaman>
(and yeah i'm thinking it'll be more sane to just try and pull ARC and whatever is related/needed out of the minnie rootfs, and just RW the C201 rootfs and put them in, than changing the whole thing)
<hexdump0815>
macc24: btw. i think you played around with sleep on the duet a bit and had some problems - did you also experiment with suspend-to-idle (echo s2idle > /sys/power/mem_sleep) - it helped for me on armv7l chromebooks which had problems to resume from sleep
<hexdump0815>
macc24: does not save that much energy but devices usually survive about a day in that state
<macc24>
s2idle doesn't work too, my guess is that mediatek drm or panel driver don't have resuming implemented
<macc24>
well, with screen off and everything else running as normal, linux was talking about 24 hours of battery life on ssh
<hexdump0815>
thanks for the link about ccd ... i also once had a situation where the display appeared to be dead after sleep i think and in the end just the brightness level of the backlight was set to zero after sleep - very unlikely, but maybe worth a check
<macc24>
._,
<macc24>
the panel has backlight, but it's all black
<hexdump0815>
ah - ok - evel less likely the case then :(