Future of Intel Legacy

Linux works.

Glad to know.
Thanks for the insight folks! :slight_smile:

Hey folks, I have another thing that’s very very important to me.
I wonder what are the possible solutions for this,
I have a external ssd that I use on 3 seperate computers, all of those are Intel Legacy, However, when I set up FydeOS on one computer, and turn it on the next day on another one, I see that everything resets and it’s like a fresh install, I’m required to sign back in through my google account and even the android subsystem is required to be re-activated. I haven’t tested chromeOSFlex, as I cannot trust it with any system’s internal drive. Is there any way to disable this sort of reset when FydeOS detects it’s on different hardware?

Never mind, I saw in another post that this is not possible.
lol, works on FydeOS v20

@Carrie_Gu @Mayday
I have very important news!
I tested FydeOS Slim today on the intel legacy laptop, (I’m certain the laptop cannot boot intel modern)
I WAS ABLE TO GET ANDROID APPS WORKING!
But there is one caveat, the android settings app doesn’t launch.

Installing apps from FydeOS Store worked!

I tried all this on LIVE USB. Using the “Try it first” option in the installer

Screenshot as proof!

You can see the blue colored android settings app

Hmm, tried on another system. The Live USB should reset right? like, act like a fresh install on new hardware? It didn’t, but the android does not work on Intel Xeon Graphics, It’s 2nd/3rd gen, so I guess it’s too old. But v19 android works. It’s an iGPU era one for Xeon.
The live usb android that worked for the system had Intel HD Graphics 5500 I believe.

@Carrie_Gu @Mayday
This is about the system that worked with android
Output from chrome://gpu
about-gpu-2025-06-13T02-34-30-920Z.txt (40.7 KB)

Screen Recording:
Note: The Android subsystem crashed while screen recording. But games work fine …
A restart often resolves the problems I had with Android. Like “loading (name of app) → eg: Google Play Store which gets stuck and comes back up like nothing happened after a few minutes”

EDIT: The game works fine, I just had to wait a minute. Guess I was impatient during the recording and that caused it to hang up and crash the subsystem.
So, yeah, if you’re lucky I guess, the only caveat is that the whole android system crashes when a single android app crashes. But wait 1 to 5 minutes and you’re back like everything’s fine.

Here’s an updated screen recording that showcases the gameplay experience.
It’s a game that’s available on Google Play Games Beta on windows and has been optimized for keyboard by the developer, so I haven’t used game dashboard as there are no touch controls shown.
The screen recording doesn’t do justice, but the game runs pretty smooth once the recording was stopped.

I’m able to get 20 to 30fps consistently, which is playable for me on my hardware.

@Carrie_Gu
@Mayday
I think maybe OpenGL is the problem? Like maybe a specific version number is required? I think you guys can do some testing on your end,
Let me know what you think.

EDIT: I’ve posted a chrome://gpu output as a .txt file in the previous comments, please have a look at that, I think you might find something that is useful, I hope so.

I think this has nothing to do with OpenGL; it’s just that the hardware doesn’t meet the required standards. Even if a slim machine is 6th generation or newer, its CPU performance might not be as good as a 5th generation Core, but it still meets the standards for new devices.

I see. So I’m just a “lucky candidate” who had “modern-enough hardware” to be able to run Android 11.

@Mayday @Carrie_Gu
One game gave me this


The name is “Extreme Car Driving Simulator”
Hill Climb Racing 2 barely works, sometimes really well, sometimes not playable, fps is too low.
But Garena Free Fire MAX works Splendid! + I don’t have a reset when I plug in to other computers so win win!
:blush: So happy I switched to FydeOS Slim. I needed Free Fire. + Portability with chrome but no google, Fyde has helped me acheive this! Thanks dev team!

@Carrie_Gu @Mayday
Isn’t FydeOS supposed to reset itself, like powerwash and treat like a new install on booting in a completely new system?
I didn’t have that happening with FydeOS v20 Slim. Is this expected, or abnormal behaviour because, well as @Mayday said in this post,

FydeOS is designed not to act like this.
So, what’s happening? Is something going wrong?
Or did we acheive this “portablility factor” in v20?