Have you searched the community for related issues?
No similar issues found.
Description:
Why is Intel Legacy still on v19?
Reasons I believe v20 should be made available (for legacy):
Vulkan works (For all devices, I believe Vulkan IS supported, even if there is like Vulkan support is incomplete for <some_cpu_family_name> it’s still fine.)
FydeOS Notes → A Web App, Not native that demands hardware.
Help Center + Other stuff: Help Center is just your website. Other stuff came with the new chromium update. Chrome OS Flex works fine with all the features available. except the android subsystem.
I’ve enabled flags for Vulkan support. No issues so far.
Please correct me If I’m wrong.
Android Subsystem:
I’ve seen some news here that the Android subsystem is going under major revision for legacy branch, okay, why not stick with the old android version in v19 and ship? (Android v9 is still standard in many android emulators).
We are a small team, and we are currently maintaining three versions of Android: 9, 11, and 13. The maintenance cost is too high. We have decided to stop maintaining Android 9. If devices with Intel 5th generation or earlier cannot be upgraded to Android 11, we will have to stop supporting those devices. This is a product decision made for the development of the company.
I believe that they can be upgraded to Android 11.
In my opinion, we should make v20 available for Intel Legacy as I believe they can run it. Any computer that comes under Intel Legacy should be able to run Android no matter the version unless it requires some new CPU instruction set like something greater than SSE 4.2
Just checked, as long as cpu has sse4.2 or newer, it should be fine. Chatgpt says so.
ChatGPT may not always be correct. I can only tell you that, at present, we have not found any way to upgrade Intel 5th generation and earlier devices to Android 11. In fact, you won’t be able to find a ChromeOS image that upgrades Intel 5th gen or earlier devices to Android 11, either. The ideal is beautiful, but reality is harsh.
Isn’t the Android subsystem made by Fyde. Like the ArcHero project stuff? btw, I’m pretty sure that if Bliss OS works, then it would be possible. Is this the reason for the Android rework? Because no chrome OS image is found suitable?
I also wanna say that I tried the Google Play Games Beta on Windows 11. On the same intel legacy laptop. It ran poorly, only due to the ram requirement. But in my experience FydeOS does better. And consistently has been.
Can’t we make something? I’ve also used waydroid on arch Linux and it works pretty well.
I understand what you guys are trying to do here. And maybe this is out of your control.
Anyways, regardless of the image and all. I wanna try and comprehend this, why is FydeOS split into these branches? The Linux Kernel should have pretty much all the drivers right? Just a few tweaks to the Android setup process, like letting users choose a version would be better in my opinion. Just wanna know that’s all.
Also, is there a way that I can run the modern variant on a legacy one? Like I feel this is more of a driver issue. The screen goes black when I try. I think if the drivers in Intel legacy were put in Intel modern, I could test and see.
So far, Fyde has been the only thing stopping me from OS hoping. Which is why I wanna know what’s happening so bad.
There are some rather complex technical reasons behind this. I believe that for the same technical reasons, ChromeOS also does not provide Android 11 upgrades for devices with Intel 5th generation or earlier. BlissOS is pure Android, which is different from FydeOS and ChromeOS. If your device can run BlissOS, then you can use BlissOS.
The virtual machine version has poor support for the Android subsystem, so it’s not recommended for daily use.
We are just a small team, and there are some issues we simply cannot solve. This is the reality, and we have no choice but to accept it.
I kind of know the issue. Because Intel 5th Gen doesn’t have Vulkan support, and Android upgrade requires Vulkan support. That’s the simple explanation.
lol, then why would I be able to enable the flags as shown in the picture? (See first post)
Also, Vulkan support is there, just incomplete. Not entirely supported, BUT supported.
btw, I think what @Carrie_Gu said is the final answer now.
Thanks @Carrie_Gu for your patience and explanation. I’ll close this now.
btw, @Carrie_Gu , by poor android support in the vm version, do you mean it’s caused by no graphics support? Like if we can passthrough a gpu, it’ll work better?
This is my last question for this topic.
Because the Android subsystem in FydeOS is not a native application, but runs through containers and virtual machines, nesting containers and virtual machines within the virtual machine can lead to various issues.
Ask ChatGPT if you don’t know. For intel chips, only 6th and above support vulkan. You can enable flag does not mean it is supported. It’s a feature related with hardware not software.
@Mayday , I think you’re wrong in this case. I’ve seen on multiple Linux distributions and on my testing in their terminals, that vulkan is supported, on the legacy branch system I have. Vulkan has incomplete support, which doesn’t mean that there is NO support. For these systems.
btw, @Carrie_Gu , one last question before I close this,
What is the expected roadmap? From what I believe, v19 will go EOL soon. What should legacy users expect? If no solution is found within the EOL time period, will the legacy variant of FydeOS cease to exist? Or, will Android be stripped out and be given to those users. Or will they be told to switch to OpenFyde and make hay while the sun shines with that? Cause, I imagine in the following years, there won’t be a possible way to even run chromeOSFlex on these systems.
Incomplete support means not supported. Intel is the chip manufacturer, and officially, Intel does not support Vulkan on its 5th-generation processors. Any claims of support you’ve heard are the result of third parties forcing it through various workarounds — these implementations are highly unreliable and far from true compatibility. Official backing from Intel is the only true support.
So I’m guessing that at EOL the Intel legacy download option will be removed and users will be encouraged to switch to Intel slim. Is that it? I’m thinking Linux subsystem would still work though, right? If linux works, then legacy users should get more ram somehow and try arch with waydroid. Which would be a bumpy ride as it would become a nested vm. Since waydroid basically runs Android in a virtual container.
But some guys in the community have been able to get waydroid working, so I guess that’s the only option for now.
Thanks guys for your clarification.
Question Description
System & Device Information