FydeOS 21 and 22 white screen with dots after fydeos logo

Support & help
,
1

:pushpin:Question Description

Have you searched the community for related issues?

  • [Yes ] No similar issues found.

Please describe the problem you’ve encountered in detail:

  • Description:
    I had fydeos before in my notebook, and i tried to use the new version fydeos 22, but after the fydeos logo, appears a white image with black dots and the mouse pointer, so i cant go any further. i was asure that my PC configuration is compatible with fydeos cuz i had it before. so i downloaded the fyde os img 22 and 21 again, and happened the same thing, but when i downloaded the fydeos 20, works perfectly, just to mention it i am writing this from the fydeos 20 of the very same notebook. so my question is: what happened with 21 and 22 version that doest work for amd processors if the fydeos team didnt mentioned anything about changes in amd variants. if the 20 version works should all of then work right? second question it will be fixed? or cant be fixed or it suppose to finish for me at 20 os version.

:computer:System & Device Information

  • Hardware & System Configuration:

    • Processor:AMD Quad-Core A10-9600P (2.4 GHz atĂ© 3.3 GHz, 2MB Cache).
    • Graphics CardAMD Radeon R5 Graphics (integrada ao processador).
    • RAM: 32gb
    • FydeOS Version: FydeOS 20 FydeOS for PC (AMD Graphics), v20.0-SP1, Non-commercial Edition
      Platform 16093.91.20.23
      Chromium 132.0.6834.228

  • Relevant System Logs:

    • Open the Chromium browser and enter /var/log/messages to retrieve logs.
    • Log Details:Message=Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:38:42.804746Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(247)] Requested to install unsupported DLC=nc-ap-dlc
      2026-05-06T01:38:42.804770Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(237)] [CoreServicesAlert] Failed to install DLC=nc-ap-dlc
      2026-05-06T01:38:42.805048Z INFO dlcservice[1701]: INFO dlcservice: [metrics.cc(81)] InstallResult metric sent:5
      2026-05-06T01:38:42.805749Z INFO cras_server[1685]: failed to install nc-ap-dlc: D-Bus failure: Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:38:42.805872Z INFO cras_server[1685]: retrying DLC installation in 120s, order [CrasDlcNcAp]
      2026-05-06T01:39:21.429861Z WARNING cryptohomed[1189]: PinWeaverIsSupported: command failed: 0x9a TPM_RC_INSUFFICIENT
      2026-05-06T01:39:21.435221Z WARNING cryptohomed[1189]: PinWeaverIsSupported: command failed: 0x9a TPM_RC_INSUFFICIENT
      2026-05-06T01:39:38.203727Z NOTICE temp_logger[12936]: acpitz:54C
      2026-05-06T01:40:38.231455Z NOTICE temp_logger[13211]: acpitz:55C
      2026-05-06T01:40:42.808749Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(433)] GetDlc(…): Domain=dbus, Code=org.chromium.DlcServiceInterface.INVALID_DLC, Message=Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:40:42.808778Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(247)] Requested to install unsupported DLC=nc-ap-dlc
      2026-05-06T01:40:42.808798Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(237)] [CoreServicesAlert] Failed to install DLC=nc-ap-dlc
      2026-05-06T01:40:42.808968Z INFO dlcservice[1701]: INFO dlcservice: [metrics.cc(81)] InstallResult metric sent:5
      2026-05-06T01:40:42.809623Z INFO cras_server[1685]: failed to install nc-ap-dlc: D-Bus failure: Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:40:42.810116Z INFO cras_server[1685]: retrying DLC installation in 120s, order [CrasDlcNcAp]
      2026-05-06T01:41:38.254706Z NOTICE temp_logger[13444]: acpitz:54C
      2026-05-06T01:42:38.281167Z NOTICE temp_logger[13613]: acpitz:48C
      2026-05-06T01:42:42.812406Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(433)] GetDlc(…): Domain=dbus, Code=org.chromium.DlcServiceInterface.INVALID_DLC, Message=Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:42:42.812426Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(247)] Requested to install unsupported DLC=nc-ap-dlc
      2026-05-06T01:42:42.812439Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(237)] [CoreServicesAlert] Failed to install DLC=nc-ap-dlc
      2026-05-06T01:42:42.812586Z INFO dlcservice[1701]: INFO dlcservice: [metrics.cc(81)] InstallResult metric sent:5
      2026-05-06T01:42:42.812952Z INFO cras_server[1685]: failed to install nc-ap-dlc: D-Bus failure: Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:42:42.813040Z INFO cras_server[1685]: retrying DLC installation in 120s, order [CrasDlcNcAp]
      2026-05-06T01:43:38.312179Z NOTICE temp_logger[13809]: acpitz:54C
      2026-05-06T01:44:32.297193Z INFO rsyslogd[582]: – MARK –
      2026-05-06T01:44:38.342138Z NOTICE temp_logger[13985]: acpitz:49C
      2026-05-06T01:44:42.816431Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(433)] GetDlc(…): Domain=dbus, Code=org.chromium.DlcServiceInterface.INVALID_DLC, Message=Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:44:42.816464Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(247)] Requested to install unsupported DLC=nc-ap-dlc
      2026-05-06T01:44:42.816482Z ERR dlcservice[1701]: ERROR dlcservice: [dlc_service.cc(237)] [CoreServicesAlert] Failed to install DLC=nc-ap-dlc
      2026-05-06T01:44:42.816678Z INFO dlcservice[1701]: INFO dlcservice: [metrics.cc(81)] InstallResult metric sent:5
      2026-05-06T01:44:42.817155Z INFO cras_server[1685]: failed to install nc-ap-dlc: D-Bus failure: Passed unsupported DLC=nc-ap-dlc
      2026-05-06T01:44:42.817275Z INFO cras_server[1685]: retrying DLC installation in 120s, order [CrasDlcNcAp]

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

2

This cpu is too old actually. Even though v20 can run, the android subsystem cannot be enabled. V21 and v22 has newer version of Linux kernel which support worse on old CPUs. I think you should give it up.

3

I see your point but doenst make sense throught facts.

1: the android system on fydeos 20 was enabled without any problem.

  1. The fydeos website on amd download page informs that supports processors starting 2011+ mine is a 2016 mid year 7th generation

  2. I had linux on my machine as well. Even the newest kernel was compatible with it in 100%.

Can you feel me ? :sweat_smile:

4

Read the AMD part.

  • Furthermore, for devices equipped with AMD processors or APUs, it must be the Ryzen series or a newer architecture to enable the Android subsystem; AMD processors older than the Ryzen architecture cannot use this feature.
5

i see your point but it says the “android subsystem must be a ryzen or newer” , and thats is not my problem, my problem begin even after the fydeos logo and the android subsystem is activate only after the system installation, and on 20 it is actually running without any problem the playstore, gapps, android subsystem and everything else, how can the processor be the problem in that case? i think is more easy to say that is a hardware limitation, over a system compatibility problem.

6

“Regardless of processor brand (Intel or AMD), the CPU must support the SSE4.2 instruction set to utilize FydeOS’s Android and Linux subsystems.”

t says before the thing that you quote.

Information about the processor below with that feature.

Yes, the AMD A10-9600P APU (Bristol Ridge, 7th Gen) supports SSE4.2 instructions. [1, 2]

Based on the Excavator architecture used in this chip, it also supports other modern instruction sets, including:

SSE4a

AES

AVX / AVX2

FMA3

PopCnt

This CPU is a mid-range, 4-core mobile processor released around 2016.

7

Because android subsystem upgraded to 11 in v21, so it has a higher requirement now.

8

Again android subsystem is not the point in here. And on 20 its already 11 and i am using it without any problem. Like i said the problem is something else… if the problem appears after the installation and after activates android subs, you will have won with your arguies, but i cannot even install it. Due to that white screen after fyde os logo. So it seems to be a video driver compatibility over anything else. In my mind the problem is on fydeos new img.

9

I’m not trying to win this argument. I’m just trying to tell you that even if your device can boot v22, Android still may not work, because many users with similar CPUs are able to boot v22 but cannot use Android. I simply wanted to give you a friendly reminder: if you’re spending time researching this mainly for Android support, you may end up wasting your time. If that’s not your goal, then feel free to ignore what I said and continue your own research.

10

Oh thank you hacker for your answers, i am sorry i am no trying to be rude, if seems so, sorry for that. I see your point now. Thanks.