Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[Thingy101]

Where can i get sigpatches for atmosphere 20.0.1???

 

[impeeza]

Where can i get sigpatches for atmosphere 20.0.1???

On the OP!

 

[xXSoulGeoXx]

Where can i get sigpatches for atmosphere 20.0.1???

Hacking  Post in thread 'Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)'

Jul 15, 2025

*** Updated 2026 - 01 - 12 ***

Sigpatches updated for 21.2.0,

And Upgraded to Atmosphère 1.10.1 (no version for FW 21.2.0 yet)

SYS-Patch should work fine with this FW too.

• impeeza

• 
• 

 

[bombayjack]

On the OP!

I've added new code to the overlay for sys-patch to patch the looping issue with linked accounts of FW 21+, the best thing is that it only shows up on the menu if you are on fw21+ and if not already patched . Next thing to to do is add a reboot item to the menu. Then I'll probably be done with sys-patch and post the updated code.

 

[yeepsleep]

Just make another emunand so you have 2 emunads, one with the latest firmware and one 18.0.0, you can switch between them with hekate or using an overlay - https://github.com/Hartie95/fastCFWswitch
You can make small emunands so they don't take up much room, I used NxNandManager to shink mine down to about 3 gig, I have every firmware version emunand on my sdcard (for testing things) and still have loads of room. https://github.com/eliboa/NxNandManager

Sorry to bother you about this, but I just wanted to confirm something before I attempt this. Does setting up an additional emunand require deleting any data on the SD? My 500GB Switch SD has about 40GB left and ideally I would like to use that space for a second emunand just for MP4, but I don't want to affect anything on the existing emunand because I have everything set up perfectly and dont want to have to set any of that stuff up again. I'm seeing from the screenshots in the nxNandManager that the tools seem to indicate that "all data on target disk will be erased," and if thats the case i would probably not want to go through with it. Thanks in advance for your advice with this.

 

[Earthshine]

Which overlay shows the amount of memory for sys-modules and how much is being used?

 

[TomSwitch]

Which overlay shows the amount of memory for sys-modules and how much is being used?

Keep adding until system unstable, keep removing until it's good again, it's that simple. Or stay away from 21, the recommended choice.

PS: Games you run plays a part, what a pain right? Go minimalist if you don't want pain.

 

[Earthshine]

Keep adding until system unstable, keep removing until it's good again, it's that simple. Or stay away from 21, the recommended choice.

PS: Games you run plays a part, what a pain right? Go minimalist if you don't want pain.

First off, 21 doesn't have any less memory available than 20 did. Secondly, can you answer the actual question?

 

[TomSwitch]

First off, 21 doesn't have any less memory available than 20 did. Secondly, can you answer the actual question?

do you know how to read? https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.10.0-prerelease
hint: second "Please note:"

It’s best to check the segment map of the sysmodules. I know a few ways to do it, but I’m not writing a full tutorial. I believe someone already posted about it on GBAtemp.

You may be thinking of https://github.com/masagrator/Status-Monitor-Overlay but having it loaded takes up precious memory too. In the end looking at it does not prevent you from crashing, you just be knowing that you will crash sooner rather than later.

 

[Earthshine]

do you know how to read? https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.10.0-prerelease
hint: second "Please note:"

It’s best to check the segment map of the sysmodules. I know a few ways to do it, but I’m not writing a full tutorial. I believe someone already posted about it on GBAtemp.

You may be thinking of https://github.com/masagrator/Status-Monitor-Overlay but having it loaded takes up precious memory too. In the end looking at it does not prevent you from crashing, you just be knowing that you will crash sooner rather than later.

I know how to read perfectly fine, smart ass. You're the one that has issues. The release notes aren't saying that 21 has ANOTHER 10 MB gone. It's just the same 10 MB that was gone in 20. SciresM even commented on the entire "21 has only 4MB!!!" misinformation that's been going around here, reddit, and a bunch of other places and I've already corrected others on it a few times already. You're the one that's wrong here and has reading issues.

Also, who said anything about looking at an overlay would prevent me from crashing? That's just stupid to even say, as if I actually even thought that. My reason for wanting to know what the overlay is has nothign to do with me crashing or being worried about how much mem is left, or anything of the sort. It was because I have been accused of being full of shit about the amount of available memory on 21, despite the literal dev of Atmosphere clarifiying that it's not ANOTHER 10 MB gone. I wanted to know so I could tell others like yourself to go look for themselves on their own Switch instead of taking mine or SciresM's word for it. I mean, are you insinuating that SciresM is lying when they made this comment about it? And as you asked me.... do you know how to read?

Hacking  Post in thread 'Atmosphere-NX - Custom Firmware in development by SciresM'

Nov 19, 2025

3.86 for be exact

What? My testing showed 16 MB available for custom sysmodules at runtime.

• SciresM

• 
• 
• 

 

[impeeza]

Which overlay shows the amount of memory for sys-modules and how much is being used?

UltraHand overlay shiw you the available memory at the overlays menu

 

[Earthshine]

UltraHand overlay shiw you the available memory at the overlays menu

Thank you, impeeza. I already had ultrahand but didn't know how to get to that page. Figured it out. Have to press + at the overlays menu, then to the 'system' section. Now I can tell the others accusing me of lying how to find the info for themselves.

 

[bombayjack]

Can someone with a Mariko switch test the attached overlay to see if it detects Mariko properly?

It's just a payload launcher overlay so it goes into switch .overlays folder. I'm updating sys-patch and am writing the code for detecting switch versions and reboot code but I only have an Erista switch (the code works properly on that). I just need to test it detects Mariko and reboots as expected, then I'll add the code into the sys-patch overlay.

 

[adimah]

Are there sigpatches available for 21.0.1? Or have things changed now?

 

[AllOver]

First off, 21 doesn't have any less memory available than 20 did. Secondly, can you answer the actual question?

The code looks to say otherwise https://github.com/Atmosphere-NX/Atmosphere/commit/540d00e097357f36b65c8dc88d03bd8197aa7aff. This was later changed to reduce it by a further 1MB. So a reduction by 7MB from compared to firmware 20.

 

[Earthshine]

The code looks to say otherwise https://github.com/Atmosphere-NX/Atmosphere/commit/540d00e097357f36b65c8dc88d03bd8197aa7aff. This was later changed to reduce it by a further 1MB. So a reduction by 7MB from compared to firmware 20.

Release notes for Atmosphere 1.9.5 state "We can only steal a maximum of 14MB from the applet pool, down from 40MB"

His comment below was made later than when that code was committed by almost a week. If you want it settled you and @ him and ask for clarification. When I look in Ultrahand it says 11.88MB free with the overlay memory using 4MB. Imo, that falls in line with what he stated here:

Hacking  Post in thread 'Atmosphere-NX - Custom Firmware in development by SciresM'

Nov 19, 2025

3.86 for be exact

What? My testing showed 16 MB available for custom sysmodules at runtime.

• SciresM

• 
• 
• 

 

[impeeza]

Are there sigpatches available for 21.0.1? Or have things changed now?

they are now on the OP

Post automatically merged: Dec 6, 2025

*** Updated 2025 - 08 - 12 ***

Sigpatches updated for 21.1.0,

And Upgraded to Atmosphère 1.10.1

THEY ARE ON THE POST 5494

 

[AllOver]

His comment here, once again, says otherwise, and was made later than when that code was committed by almost a week. Argue with him about it if you feel he means something other than what he stated. If I'm wrong, I'm wrong. But you can @ him and ask if you want it settled.

Hacking  Post in thread 'Atmosphere-NX - Custom Firmware in development by SciresM'

Nov 19, 2025

3.86 for be exact

What? My testing showed 16 MB available for custom sysmodules at runtime.

• SciresM

• 
• 
• 

Firstly, drop the attitude. I am simply providing the code which does reduce the additional memory that ams provides. Did firmware 20 only provide 16mb in total? If so, then yes the author is saying the memory on firmware is unchanged. However in that exchange, I only see the author correcting another user saying that there was substantially less memory then there actually was.

As I understand, ams takes memory from the applet pool and gives it to the sysmod pool. Recently this broke web applet as N had it use more memory. It looks like in firmware 21, this is the case again, and a further 6mb was taken. Then in a later commit, another 1mb was taken for the eshop. The comment in that commit even says this:

"NOTE: On 20.0.0+ (and even more-so 21.0.0+) the browser requires much more memory in the applet pool in order to function."

If the code says it does X, then it does X. It's possible that I misunderstood the code, but I don't think I did.

 

[Earthshine]

Firstly, drop the attitude. I am simply providing the code which does reduce the additional memory that ams provides. Did firmware 20 only provide 16mb in total? If so, then yes the author is saying the memory on firmware is unchanged. However in that exchange, I only see the author correcting another user saying that there was substantially less memory then there actually was.

As I understand, ams takes memory from the applet pool and gives it to the sysmod pool. Recently this broke web applet as N had it use more memory. It looks like in firmware 21, this is the case again, and a further 6mb was taken. Then in a later commit, another 1mb was taken for the eshop. The comment in that commit even says this:

"NOTE: On 20.0.0+ (and even more-so 21.0.0+) the browser requires much more memory in the applet pool in order to function."

If the code says it does X, then it does X. It's possible that I misunderstood the code, but I don't think I did.

I was still in the process of editing my comment when you replied to it, so there are some changes from when you first read it. I think notes like this are confusing people. "As a result of changes made to nintendo's software in 21.0.0, there is again roughly 10MB less memory available for custom system modules." Imo people are misreading that to say there is an additional 10MB less than when 20.x had. I feel he is just saying that additional 10MB less is still there, not that it is an additional 10MB less. That's how people came up with 21.x having 4MB. And again, Ultrahand also says otherwise. You'll have to ask SciresM if you want a 100% answer. I'm not the dev, but I feel that I'm making correct observations. If I'm wrong I'm wrong. I don't mind being wrong if I am.

 

[garbagehuman123]

I was still in the process of editing my comment when you replied to it, so there are some changes from when you first read it. I think notes like this are confusing people. "As a result of changes made to nintendo's software in 21.0.0, there is again roughly 10MB less memory available for custom system modules." Imo people are misreading that to say there is an additional 10MB less than when 20.x had. I feel he is just saying that additional 10MB less is still there, not that it is an additional 10MB less. That's how people came up with 21.x having 4MB. And again, Ultrahand also says otherwise. You'll have to ask SciresM if you want a 100% answer. I'm not the dev, but I feel that I'm making correct observations. If I'm wrong I'm wrong. I don't mind being wrong if I am.

always you man