Atmosphere v1.12.0 released, adds support for Switch firmware 23.0.0

atty.png

It's that time again. Prepare your Switch updates! Or prepare to forgive your sister's nephew's dog for updating your Switch a few weeks ago. Atmosphere v1.12.0 has just released, with the headline feature of course being the initial support for Switch firmware 23.0.0.

You can find the full release notes below:

Release Notes said:
1.12.0 is Atmosphère's ninety-third official release.

Please be sure to update fusee when upgrading to 1.12.0. fusee-primary no longer exists, and will not work any more.

With thanks to the @switchbrew team, Atmosphère 1.12.0 is bundled with hbl 2.4.5, and hbmenu 3.6.1.

The following was changed since the last release:
  • Support was added for 23.0.0.
  • Special thanks to @alula for handling the implementation of several kernel changes.
    • The console should boot and atmosphère should be fully functional.
    • Please note: As a result of changes made to nintendo's software in 23.0.0, there is even less memory available for custom system modules.
      • The amount of memory we can steal from the applet pool has been reduced beyond 7MB and we can no longer launch browser applets (e.g.: eshop) without crashing.
      • To compensate for this, a set of patches for the browser applets has been introduced.
        • Thanks to the redesign of the browser applets in 22.0.0 there are only 3 applets we need to worry about: systemWeb, openWeb and LibAppletOff.
        • With the added burden of maintaining patches for these applets, we can reclaim around 9MB of reserved memory by patching out their allocations.
        • This memory is provably unused and stealing it should not affect the browser applets in any way as the applets themselves tag it as reserved and never access it.
        • As a result, the memory available for custom system modules has been experimentally increased to 16MB.
        • Preliminary testing has seemingly shown no downsides to the overall functioning of the OS and the browser applets in particular.
        • Nonetheless, please report any issues you may face to ensure no edge cases have been missed and to determine if the memory amount needs to be adjusted.
        • These patches may be deprecated at any point in the future if a better solution is devised.
    • exosphère was updated to reflect the latest official secure monitor behavior.
      • A new ConfigItem was added to the secure monitor for the first time since firmware 5.0.0.
    • mesosphère was updated to reflect the latest official kernel behavior.
      • The kernel now supports a 42bit wide address space.
      • A new memory region dubbed ShadowStack has been introduced.
      • Kernel RNG was changed to CTR-DRBG.
    • boot was updated to reflect the latest official behavior and to implement a previously missing change.
      • The way battery i2c shutdown was being enabled changed in firmware 18.0.0 and we missed it.
      • It is possible this might have been related to a known battery draining issue reported to have started around firmware 18.0.0. Further testing will be needed to confirm.
    • loader was updated to reflect the latest official behavior.
    • erpt was updated to reflect the latest official behavior.
    • pgl was updated to reflect the latest official behavior.
    • ro was updated to reflect the latest official behavior.
      • NROs can now be lz4 frame compressed.
  • ZBIC compresison/decompression has been properly implemented. Applications using it should now launch and work properly.
  • A dockerfile has been added to atmosphère (thanks @alula).
  • R_DISCARD macro has been adopted across the entire codebase where applicable. This finishes the work started in version 1.10.0 and eliminates the nodiscard warnings during compilation.
  • General system stability improvements to enhance the user's experience.
For information on the featureset supported by 1.12, please see the official release notes.

As always you can find the GitHub releases page linked below.

:arrow: Atmosphere Download
 
Why doesn't Atmosphere just reverse that memory change? Seems like a lot less headache.
I don't know the technical details, but I assume it would break whatever function Nintendo are using that memory for.

However it does look like they are at least partially doing this now, for memory that is provably unused even by Nintendo. It doesn't reclaim a ton of memory, originally we had 40MB and now we have 16MB, but its enough for normal use.
 
Last edited by Sir Tortoise,
How can you tell how much memory you're currently using for your system modules? I don't use a lot of them for example, but I do got ultrahand, emuiibo and breeze running on my system for example.
 
I always tell myself that but have to update in the end sooner or later


I never updated my 3DS so I still have the flashing green & blue icons telling me that Miiversere had a special guest ^.^,still really miss the great eshop theme's that used to play every time you opened the shop though
 
I never updated my 3DS so I still have the flashing green & blue icons telling me that Miiversere had a special guest ^.^,still really miss the great eshop theme's that used to play every time you opened the shop though
Good old 3ds didn't had such a deluge of useless updates
 
  • Haha
Reactions: ChibiMofo
I got a System Update prompt when I wanted to update Mario Kart 8 Deluxe via Match local version using another Switch. So this is welcoming to me.

It's because DNS.MITM doesnt work.

supposedly dns.mitm isn't functional in 23.0.0 with atmosphere 1.12.0;
doesn't impact people who are banned from nintendos domains, or people who use third-party DNS servers / have prodinfo-blankers (such as the exosphere option).
 
It's because DNS.MITM doesnt work.

supposedly dns.mitm isn't functional in 23.0.0 with atmosphere 1.12.0;
doesn't impact people who are banned from nintendos domains, or people who use third-party DNS servers / have prodinfo-blankers (such as the exosphere option).
Strange, everything is blocked, but I think it asks for it since the Mario Kart Update came out fairly recently and the Mario Kart Update or any game update that is fairly new might be programmed to check if your system version is high enough on atleast the firmware the update came out with.

I'm on 22.1.
I'm not sure if the Mario Kart Update came out when there was still no 23.0.0 out yet, so it could work on 22.5.

I haven't updated yet.
Reading that the DNS. MITM doesn't work, I might hold off, though I have triple protection actually. Blanked out serial number with zeros, setting up wifi with DNS to block Ninty servers.

So I might aswell go ahead, but actually there is no hurry.
 
Last edited by thekarter104,
I don't know the technical details, but I assume it would break whatever function Nintendo are using that memory for.

However it does look like they are at least partially doing this now, for memory that is provably unused even by Nintendo. It doesn't reclaim a ton of memory, originally we had 40MB and now we have 16MB, but its enough for normal use.
They further crippled an already crippled function, and it's literally just to thwart homebrew apps from loading in Applet mode.
 
  • Like
Reactions: BigOnYa

Site & Scene News