FydeOS v18 Legacy is broken and no V20 Legacy

Support & help
, ,
1

:pushpin:Question Description

Have you searched the community for related issues?

  • No similar issues found.

Please describe the problem you’ve encountered in detail:

  • Description:

I’ve tried to install FydeOS V20 (Slim) on my device (which i won’t mention the brand because it is like 8 years old). The thing is that it was working fine on V18 until i started to have issues:

Websites are telling me Chromium version isn’t supported anymore, i couldn’t fix my Android subsystem because FydeOS was asking me to update it before trying to “Install” (which was the install/fix option)

Also i am very tired of being on V18 when there is already an V20 release! Intel Slim version doesn’t work for me because i get the Red tinted screen error. I’ve waited for so much time for a fix but… No fixes…

ChromeOS Flex works fine on my device, no red screen issues and it is on the latest version, i don’t understand why FydeOS has the red screen error. Can someone help me? it is an old laptop but it still useful for basic usage which is what i mostly do.

:computer:System & Device Information

  • Hardware & System Configuration:

    • Processor:Intel(R) Celeron(R) CPU N3010 @ 1.04GHz (2 threads, 2.240 GHz)
    • Graphics Card(Please specify if there’s a discrete graphics card): i can’t find it ‘-’
    • RAM: 4GB
    • FydeOS Version: V20 Installer

  • Relevant System Logs:

    • Open the Chromium browser and enter /var/log/messages to retrieve logs.
    • Log Details: Nothing, i haven’t FydeOS installed because of the error guh

Note: If you’ve lost your FydeOS subscription, please refer to this FAQ for assistance.

2

Could you provide a photo of this? It looks rather strange.

3

Of what specifically? the red screen? :face_with_raised_eyebrow:

4

If there was any error message on the screen, then it would be helpful. But if there was nothing but a red screen, you might encounter graphics problems. Have you tried the v19 legacy variant?

Update: We’ve figured out the reason behind this problem and will fix it in the next major release.