tag+: Hi rtcvb32. I assume yours is x86. How is ChromeOs x86 compared to ChromeOs arm (or Android arm)?
After having put Crouton on (ubuntu files basically) it became apparent it was indeed a x86_64 architecture. How many are ARM vs x86 i couldn't say, i only know it's basically a super cheap laptop compared to what you'd expect.
tag+: I mean, the trackers & the well known G crap aside.
Did you find apps not x86 available or different than arm? like abandoned, older versions, more bugs, etc
as example, I remember seen MXPlayer having a mess between x86 & arm. I don't have any experience with Android x86, but even with arm, I witnessed huge differences of codecs supported, performance, trimmed features (subtitles) between tegra, mali and adreno...
I ask because I have an old x86 laptop 32bits Centrino where the last windows possible is Vista and all the web browsers abandoned it already. I riffle the option to install ChromeOS there for the sake of web browsing usage (widevine streaming, youtube) as I resist to leave that good laptop to die yet... but I need to ponder the ChromeOs beast...
I haven't found anything specific i was looking for in differences. When i do get the sound to work it can sound glitchy, which may just be that the sound doesn't have a high enough priority, but it is good enough to play some stuff. For basic utilities and office apps, web browsing and programming it's just fine.
Getting emuation (
virtualbox/qemu) seems like a lost cause, the chips probably support it but there's no access to changing those settings from SeaBios.
On a second chromebook also finding some distros just won't boot, can't find the files (
Probably partition detection). This is likely old firmware that i can't update because i don't want to disassemble the thing to remove the firmware protection screw (
yes a literal screw on the motherboard somewhere) and i don't want to accidently damage the machine. Having a few lost features and the boot screen annoy you for 2 seconds is... fine.
tag+: Time ago, testing Slax I got some clock issues (Slax vs internal clock vs internet)
timedatectl set-local-rtc 1
or so fixed that. give it a try
Chromebooks unlike normal laptops don't have a CMOS battery to keep track of the time/date, and the time/date will
always be off, be it a few hours or days. Or when the battery is dead, years. Updating it automatically can do the job.
Currently got 2 distos installed, a heavy preference for Slax (
speed simplicity, wiping to clean slate, prep for a cluster setup, etc), as well as Mint.