By: Marshal Jim Raynor
In reply to <a href="https://www.osnews.com/story/139941/chrome-os-switching-to-the-android-linux-kernel-and-related-android-subsystems/#comment-10440639">colinstu</a>.
ChromeOS still run Android apps.
By: colinstu
ChromeOS used to be able to run Android apps until google ripped that out.
Now they're replacing the linux subsystem with their own AOSP crap... frightening.
Run far away from google and everything they poison.
By: iampivot
It makes sense for Google to move to make ChromeOS an OS that is more compatible with Android. Microsoft seems to screwing over their users with the directions windows 11 is taking, and it's opening up the market for other player to move in. Android on a laptop will probably be easier to sell to end users in the future than locked down ChromeOS on a laptop, when you want to replace windows, but still retain the option to install applications.
By: BluenoseJake
I hope that the Linux community stays as far away from this project as possible. It would be nice to have better bluetooth support, but at what cost? Watching how MV3 plays out will tell us all we need to know.
By: Alfman
In reply to <a href="https://www.osnews.com/story/139941/chrome-os-switching-to-the-android-linux-kernel-and-related-android-subsystems/#comment-10440607">kurkosdr</a>.
kurkosdr,
<blockquote>Generally, has anyone noticed that wireless technology tends to be a bit temperamental even today?
Bluetooth will sometimes mysteriously fail to pair or mysteriously drop connections....</blockquote>
I still use an ancient netgear 802.11g router, and it does that. I always figured this would be fixed in new products, but I couldn't be bothered to replace it given that I don't use wifi much. I know for a fact that my netgear router would frequently deplete it's connection tracking memory, which was not configurable. When this happens, all new connections get dropped until the old ones disconnect or expire.
Peer to peer software nearly always triggers this because P2P can rapidly contact hundreds.of UDP peers in a short time for each file. The router keeps track of each session for 2 hours and it just runs out of space. Dropping old/idle connections in favor of new active ones would probably be more useful, but most stacks do the opposite and drop the new packets.
TCP is supposed to be a bit more robust to this because the router knows that it can delete the mapping on FIN or RST, which indicates the end of a TCP connection. So while a computer may make hundreds of connections while browsing the web, the sessions are typically short lived. However, if a device is pwered down while TCP sessions are in progress, the TCP channels may start to accumulate in the tables even though they are dead. Many TCP stacks will keep idle TCP sessions around for hours. So on the WIFI router dead mappings can add up.
In my experience most cellular connections have the opposite problem: they are very quick to drop NAT session maps. IIRC on tmobile I would get udp disconnections at around 20-30s and tcp around 1minute. This was very infuriating when I was doing SSH from my phone, I'd constantly loose my connection!. A VPN with rapid keepalives could probably keep the connection up indefinitely but I generally try avoid using phones for any work, only rare emergencies. I'm using ATT now, but I haven't tested their session timeouts.
By: kurkosdr
Generally, has anyone noticed that wireless technology tends to be a bit temperamental even today?
Bluetooth will sometimes mysteriously fail to pair or mysteriously drop connections. Similarly, WiFi routers will mysteriously drop connections or connecting to the router will mysteriously stop working (even after repeated attempts) until you reboot the router (but Ethernet will keep functioning, which means the router is still alive). Things are slowly getting better over the years with every new batch of devices, but shouldn't this kind of stuff have already been figured out since day one?