Following on the heels of the Nintendo Switch firmware update for version 20.4.0 is a new update for Atmosphere CFW. SciresM has just released version 1.9.4, which adds support for the latest OFW, and even fixes a few minor bugs on top of that. As always, you can grab the latest version of Atmosphere from its official GitHub page, linked below.

The following was changed since the last release:

• Basic support was added for 20.4.0.
  • An issue was fixed in exosphère's register accessilibity tables (thanks @CTCaer).
    • I believe this had no impact on official code, though it would have prevented some homebrew from interacting correctly with the MC0/MC1 registers.
• An issue was fixed that could cause a deadlock when building multiple romfs images simultaneously (thanks @Ereza).
  • This fixes support for certain mods, e.g. system language translations overriding content for both overlayDisp and qlaunch.
• General system stability improvements to enhance the user's experience.

Source

 

[meow81]

My atmosphere version is 20.3.0 and I have no idea how to update, can you update on the switch itself, or do I need to use a PC?

Your switch firmware version is 20.3.0 !!

 

[EmmaQF]

what sys-patch logs tell you about the patching state

where can I find this again ? There are a lot of folders so I get bit lost haha

 

[impeeza]

where can I find this again ? There are a lot of folders so I get bit lost haha

On the SYS-Patch overlay.

 

[Bigdrago]

Havent updated in ages but now all four switches is updated to newest cfw and works perfectly.
But what the h***, what is this virtual card nonsense? I have the same users on all stock firmware but I cant have fortnite installed on all 4. Do I have to make 4 users for my children to make them play fortnite?

 

[EmmaQF]

On the SYS-Patch overlay.

 

[Blythe93]

Do I have to make 4 users for my children to make them play fortnite?

I think so, yeah. Each separate user needs a separate account in order to play. Profiles without accounts can only borrow the virtual cards, I guess. Haven't really played much with it to be honest.

 

[Psd99]

Nintendo has already aligned its tool chain with Switch 2, and I wouldn’t be surprised if every developer eventually follows suit. So I expect most updates and new games will require at lease 20.

If not for Switch 2 I doubt this getting a new update every month would be happening.

20.1.1 seems to be the base requirement for most people.

Actually,,, I am on 18.0.1 is it worth me upgrading to the latest firmware? If so, can someone please kindly remind me of the process and in which order to do things, although I have been a member here for while my knowledge of these things has subsided somewhat.

 

[Blythe93]

Actually,,, I am on 18.0.1 is it worth me upgrading to the latest firmware?

It depends on how you're using your Switch. If you're using a lot of sys-modules and mods for certain games, 18.1.0 is probably the best, 19.0.1 being the second, primarily based on the amount of memory available for those modules. 18.1.0 has 40MB, 19.x.x 24MB and 20.x.x 14MB.

I'd stay on 18.1.0 unless there's a game you'd like to play that requires higher firmware revision. Latest 20.4.0 works fine on my end. I still have 18.1.0 on my secondary Switch for now.

As for how to update, check this guide. In short, uninstall any custom theme you might have before updating your console, grab the latest firmware files off the Internet, latest Atmosphere, Hekate, sys-patch and whichever module or homebrew you're actively using (like MissionControl, DBI, sphaira, Ultrahand, etc. in my case), update via Daybreak and reboot. Remember to remove the firmware files once you're done updating in order to reduce the clutter on your SD card.

EDIT: There has been a battery draining issue introduced in 20.x.x where user was required to connect to the Nintendo servers in order to accept the new EULA. Otherwise, the console would repeatedly try to connect to the Nintendo servers while they were blocked all along, resulting in a significant battery drain to say the least. Not sure about the fix, though. I personally never run into it as I never had a real NNID linked to any of my accounts. Staying in airplane mode when not using the Internet is one of the workarounds, the other was updating the sysMMC if clean to the latest, accepting the EULA and recreating a new emuNAND. Not sure what was the final fix, it's been a while since I saw anyone complaining about it. Not sure if they've fixed it yet.

 

[Psd99]

It depends on how you're using your Switch. If you're using a lot of sys-modules and mods for certain games, 18.1.0 is probably the best, 19.0.1 being the second, primarily based on the amount of memory available for those modules. 18.1.0 has 40MB, 19.x.x 24MB and 20.x.x 14MB.

I'd stay on 18.1.0 unless there's a game you'd like to play that requires higher firmware revision. Latest 20.4.0 works fine on my end. I still have 18.1.0 on my secondary Switch for now.

As for how to update, check this guide. In short, uninstall any custom theme you might have before updating your console, grab the latest firmware files off the Internet, latest Atmosphere, Hekate, sys-patch and whichever module or homebrew you're actively using (like MissionControl, DBI, sphaira, Ultrahand, etc. in my case), update via Daybreak and reboot. Remember to remove the firmware files once you're done updating in order to reduce the clutter on your SD card.

EDIT: There has been a battery draining issue introduced in 20.x.x where user was required to connect to the Nintendo servers in order to accept the new EULA. Otherwise, the console would repeatedly try to connect to the Nintendo servers while they were blocked all along, resulting in a significant battery drain to say the least. Not sure about the fix, though. I personally never run into it as I never had a real NNID linked to any of my accounts. Staying in airplane mode when not using the Internet is one of the workarounds, the other was updating the sysMMC if clean to the latest, accepting the EULA and recreating a new emuNAND. Not sure what was the final fix, it's been a while since I saw anyone complaining about it. Not sure if they've fixed it yet.

woah thanks and that sounds like more hassle then its worth and yes I am using modifications,cheats etc for example on mario kart and zelda.

perhaps 18.1.0 might be the last upgrade I ever have on this switch on the emucc side of things.

I mean are there any games that I would be missing out on in your experience? and btw can I safely update my stock firmware??

 

[Blythe93]

I mean are there any games that I would be missing out on in your experience?

It depends. Here's the list of the games I'm interested in playing at some point on higher firmwares:

• 19.0.1:
  • Broken Sword - Shadow of the Templars Reforged (available on other platforms)
  • Cabernet (available on other platforms)
  • Mighty Morphin Power Rangers - Rita's Rewind (available on other platforms)
  • Slay the Princess - The Pristine Cut (available on other platforms, performance on Switch is pretty choppy)
  • Tales of the Shire - A The Lord of The Rings Game (available on other platforms)
  • Xenoblade Chronicles X Definitive Edition
• 20.x.x:
  • Call of the Sea (available on other platforms)
  • Fate/hollow ataraxia REMASTERED (available on other platforms, probably censored)
  • Gex Trilogy (available on other platforms)
  • Hollow Knight - Silksong (available on other platforms)
  • NINJA GAIDEN - Ragebound (available on other platforms)
  • SHINOBI꞉ Art of Vengeance (available on other platforms)

The only thing that you might be missing out on is the Xenoblade Chronicles X Definitive Edition, but all you have to do is update up to 19.0.1 for it to work (even with the latest update). 19.0.1 isn't too bad and you can safely downgrade from 19.0.1 to 18.1.0 if necessary. Downgrading from 20.x.x to anything lower is a bit tricky, though. You can even try installing the game with DBI to see if it's firmware requirements will be lowered and maybe the game will run properly. The only other thing you'll be locked out from is the newer updates for certain games but they aren't necessarily... well, necessary. All of those games worked just fine up to 19.0.1 anyway.

and btw can I safely update my stock firmware??

Can't really say anything about that, my hacked Switches are still on 15.x.x and 16.x.x and I don't use sysNAND on them at all (at least, not willingly). I do have a few other Switches I use for the games I own and play online from time to time.

 

[Psd99]

It depends. Here's the list of the games I'm interested in playing at some point across various firmware:

• 19.0.1:
  • Broken Sword - Shadow of the Templars Reforged (available on other platforms)
  • Cabernet (available on other platforms)
  • Mighty Morphin Power Rangers - Rita's Rewind (available on other platforms)
  • Slay the Princess - The Pristine Cut (available on other platforms, performance on Switch is pretty choppy)
  • Tales of the Shire - A The Lord of The Rings Game (available on other platforms)
  • Xenoblade Chronicles X Definitive Edition
• 20.x.x:
  • Call of the Sea (available on other platforms)
  • Fate/hollow ataraxia REMASTERED (available on other platforms, probably censored)
  • Gex Trilogy (available on other platforms)
  • Hollow Knight - Silksong (available on other platforms)
  • NINJA GAIDEN - Ragebound (available on other platforms)
  • SHINOBI꞉ Art of Vengeance (available on other platforms)

The only thing that you might be missing out on is the Xenoblade Chronicles X Definitive Edition, but all you have to do is update up to 19.0.1 for it to work (even with the latest update). 19.0.1 isn't too bad and you can safely downgrade from 19.0.1 to 18.1.0 if necessary. Downgrading from 20.x.x to anything lower is a bit tricky, though. You can even try installing the game with DBI to see if it's firmware requirements will be lowered and maybe the game will run properly. The only other thing you'll be locked out from is the newer updates for certain games but they aren't necessarily... well, necessary. All of those games worked just fine up to 19.0.1 anyway.


Can't really say anything about that, my hacked Switches are still on 15.x.x and 16.x.x and I don't use sysNAND on them at all (at least, not willingly). I do have a few other Switches I use for the games I own and play online from time to time.

thanks for that and take no offence but it looks quite clear that most if not all of them games are pretty meaningless to me to want to play... lol but yes with one exception xenoblade and that's the one u highlighted

Whats the process to get to 19.0.1 - just contemplatng.

 

[Blythe93]

thanks for that and take no offence but it looks quite clear that most if not all of them games are pretty meaningless to me to want to play... lol but yes with one exception xenoblade and that's the one u highlighted

Whats the process to get to 19.0.1 - just contemplatng.

None taken. ^^ The process to get to 19.0.1 is the same as to get to 18.1.0 - nothing special, just follow the usual guide. The only downside is going from 40MB to 24MB which isn't too bad.

EDIT: I don't play Pokemon games so I'm not sure if they require a higher firmware or something. And there are a lot of games that I don't plan on playing so I can't really say whether you're missing out on anything else, but still I'm pretty sure the only significant one should be the Xenoblade Chronicles X.

EDIT #2: worm28 mentioned that Xenoblade Chronicles X Remastered works on 18.1.0 here. So, yeah, there's no need to go up to 19.0.1 unless really necessary.

 

[TomSwitch]

woah thanks and that sounds like more hassle then its worth and yes I am using modifications,cheats etc for example on mario kart and zelda.

perhaps 18.1.0 might be the last upgrade I ever have on this switch on the emucc side of things.

I mean are there any games that I would be missing out on in your experience? and btw can I safely update my stock firmware??

Just buy a extra sd card.

 

[Psd99]

Just buy a extra sd card.

ok remind me.. I got one spare what does that allow me to do? have a diff version of firmware for each memory card?

 

[Blythe93]

ok remind me.. I got one spare what does that allow me to do? have a diff version of firmware for each memory card?

Yep. You can stay on a lower firmware on one, while being on the lastest on another one. Maybe it's even possible to have dual Atmosphere setup with different firmware versions?

 

[Hayato213]

It depends on how you're using your Switch. If you're using a lot of sys-modules and mods for certain games, 18.1.0 is probably the best, 19.0.1 being the second, primarily based on the amount of memory available for those modules. 18.1.0 has 40MB, 19.x.x 24MB and 20.x.x 14MB.

I'd stay on 18.1.0 unless there's a game you'd like to play that requires higher firmware revision. Latest 20.4.0 works fine on my end. I still have 18.1.0 on my secondary Switch for now.

As for how to update, check this guide. In short, uninstall any custom theme you might have before updating your console, grab the latest firmware files off the Internet, latest Atmosphere, Hekate, sys-patch and whichever module or homebrew you're actively using (like MissionControl, DBI, sphaira, Ultrahand, etc. in my case), update via Daybreak and reboot. Remember to remove the firmware files once you're done updating in order to reduce the clutter on your SD card.

EDIT: There has been a battery draining issue introduced in 20.x.x where user was required to connect to the Nintendo servers in order to accept the new EULA. Otherwise, the console would repeatedly try to connect to the Nintendo servers while they were blocked all along, resulting in a significant battery drain to say the least. Not sure about the fix, though. I personally never run into it as I never had a real NNID linked to any of my accounts. Staying in airplane mode when not using the Internet is one of the workarounds, the other was updating the sysMMC if clean to the latest, accepting the EULA and recreating a new emuNAND. Not sure what was the final fix, it's been a while since I saw anyone complaining about it. Not sure if they've fixed it yet.

https://github.com/hanai3Bi/Switch-OC-Suite/blob/master/system_settings.md

This will help with the battery draining problem in sleep mode.

ok remind me.. I got one spare what does that allow me to do? have a diff version of firmware for each memory card?

Well I would watch out for that SD card flex from constant SD card swap.

 

[impeeza]

It depends on how you're using your Switch. If you're using a lot of sys-modules and mods for certain games, 18.1.0 is probably the best, 19.0.1 being the second, primarily based on the amount of memory available for those modules. 18.1.0 has 40MB, 19.x.x 24MB and 20.x.x 14MB.

I'd stay on 18.1.0 unless there's a game you'd like to play that requires higher firmware revision. Latest 20.4.0 works fine on my end. I still have 18.1.0 on my secondary Switch for now.

As for how to update, check this guide. In short, uninstall any custom theme you might have before updating your console, grab the latest firmware files off the Internet, latest Atmosphere, Hekate, sys-patch and whichever module or homebrew you're actively using (like MissionControl, DBI, sphaira, Ultrahand, etc. in my case), update via Daybreak and reboot. Remember to remove the firmware files once you're done updating in order to reduce the clutter on your SD card.

EDIT: There has been a battery draining issue introduced in 20.x.x where user was required to connect to the Nintendo servers in order to accept the new EULA. Otherwise, the console would repeatedly try to connect to the Nintendo servers while they were blocked all along, resulting in a significant battery drain to say the least. Not sure about the fix, though. I personally never run into it as I never had a real NNID linked to any of my accounts. Staying in airplane mode when not using the Internet is one of the workarounds, the other was updating the sysMMC if clean to the latest, accepting the EULA and recreating a new emuNAND. Not sure what was the final fix, it's been a while since I saw anyone complaining about it. Not sure if they've fixed it yet.

https://github.com/hanai3Bi/Switch-OC-Suite/blob/master/system_settings.md

This will help with the battery draining problem in sleep mode.



Well I would watch out for that SD card flex from constant SD card swap.

More information on
https://github.com/Atmosphere-NX/Atmosphere/issues/2528#issuecomment-3054401265

you need to add

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF

at the end of the "/atmosphere/config/system_settings.ini" file.

at least worked for me.

 

[Hayato213]

More information on
https://github.com/Atmosphere-NX/Atmosphere/issues/2528#issuecomment-3054401265

you need to add

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF

at the end of the "/atmosphere/config/system_settings.ini" file.

at least worked for me.

Doesn't work for me on OLED without the other lines

 

[impeeza]

Doesn't work for me on OLED without the other lines

I got lost, which ones where a solution for you and which ones did not work?

 

[Hayato213]

I got lost, which ones where a solution for you and which ones did not work?

[bgtc]
enable_halfawake = u32!0x0
minimum_interval_normal = u32!0x7FFFFFFF
minimum_interval_save = u32!0x7FFFFFFF
battery_threshold_save = u32!0x64
battery_threshold_stop = u32!0x64

[npns]
background_processing = u8!0x0
sleep_periodic_interval = u32!0x7FFFFFFF
sleep_processing_timeout = u32!0x0
sleep_max_try_count = u32!0x0

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF

[account]
na_required_for_network_service = u8!0x0
na_license_verification_enabled = u8!0x0

[account.daemon]
background_awaking_periodicity = u32!0x7FFFFFFF
initial_schedule_delay = u32!0x7FFFFFFF
profile_sync_interval = u32!0x7FFFFFFF
na_info_refresh_interval = u32!0x7FFFFFFF

[capsrv]
enable_album_screenshot_filedata_verification = u8!0x0
enable_album_movie_filehash_verification = u8!0x0
enable_album_movie_filesign_verification = u8!0x0

[friends]
background_processing = u8!0x0

[notification.presenter]
snooze_interval_in_seconds = u32!0x7FFFFFFF
connection_retry_count = u32!0x0
alarm_pattern_total_repeat_count = u32!0x0
alarm_pattern_with_vibration_repeat_count = u32!0x0

[prepo]
;background_processing = u8!0x0 (shutdown directly when entering sleep mode)
transmission_interval_min = u32!0x7FFFFFFF
transmission_retry_interval_min = u32!0x7FFFFFFF
transmission_retry_interval_max = u32!0x7FFFFFFF
transmission_interval_in_sleep = u32!0x7FFFFFFF
statistics_save_interval_min = u32!0x7FFFFFFF
statistics_post_interval = u32!0x7FFFFFFF
save_system_report = u8!0x0

[olsc]
default_auto_upload_global_setting = u8!0x0
default_auto_download_global_setting = u8!0x0
autonomy_registration_interval_seconds = u32!0x7FFFFFFF
network_service_license_info_cache_expiration_seconds = u32!0x7FFFFFFF
postponed_transfer_task_processing_interval_seconds = u32!0x7FFFFFFF
retry_offset_seconds = u32!0x7FFFFFFF
network_trouble_detection_span_seconds = u32!0x7FFFFFFF
network_connection_polling_interval_seconds = u32!0x7FFFFFFF
is_save_data_backup_policy_check_required = u8!0x0
is_global_transfer_task_autonomy_registration_enabled = u8!0x0
is_on_event_transfer_task_registration_enabled = u8!0x0
is_periodic_transfer_task_registration_enabled = u8!0x0

[ntc]
is_autonomic_correction_enabled = u8!0x0
autonomic_correction_interval_seconds = u32!0x7FFFFFFF
autonomic_correction_failed_retry_interval_seconds = u32!0x7FFFFFFF
autonomic_correction_immediate_try_count_max = u32!0x0
autonomic_correction_immediate_try_interval_milliseconds = u32!0x7FFFFFFF

[systemupdate]
bgnup_retry_seconds = u32!0x7FFFFFFF

[ns.rights]
skip_account_validation_on_rights_check = u8!0x1
next_available_time_of_unexpected_error = u32!0x7FFFFFFF

[pctl]
intermittent_task_interval_seconds = u32!0x7FFFFFFF

[sprofile]
adjust_polling_interval_by_profile = u8!0x0
polling_interval_sec_max = u32!0x7FFFFFFF
polling_interval_sec_min = u32!0x7FFFFFFF

I been using all of these lines, including the one you listed