Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,745,282
  • Replies Replies 9,314
  • Likes Likes 92
That sounds more like a worn battery, rather than the known drain issue. The latter happens on standby while a network is connected.
no yeah I'm just talking about standby. cuz like at 100% i'll play for 1hr it goes to 90% i put it sleep mode and come back it's at 15%
 
thanks but wouldn't it be easier to just attach the ini file? I have no idea if I am doing it right cuz what's already on there looks nothing like what you are telling me to add and then what I add is blue ink and what was there already is in green ink........

Looks like you used the unmodified ini file from the config_templates folder. Leave that one as is. They are just templates to go by and any changes do not have any effect in that folder. Everything is green because you notice the ";" next to that line indicating the setting is not active. Create a new system_settings.ini file and place it in the config folder. Not the config_templates folder. Then paste what was given to you into that new file. If one already exists in that location, then just add the lines to it. But there shouldn't be one there unless you already made one with changes prior to now.
Post automatically merged:

no yeah I'm just talking about standby. cuz like at 100% i'll play for 1hr it goes to 90% i put it sleep mode and come back it's at 15%

Instead of the ini file you have a couple of other choices. Put your switch in airplane mode before you put it in standby, or create an entirely new emuMMC from scratch after you have already linked an nnid. Perhaps linalho fixes it too, but I can't remember for sure.
Post automatically merged:

As far as I can see, seems like we kept the ~14Mb available from 20+ in the 21 FW.

I checked in the ultrahand overlay that can display how many ram is used by current loaded custom sysmodules and what remains free. When adding values it's about 14Mb

Which overlay is that? I'd like to use it.
 
Last edited by Earthshine,
  • Like
Reactions: laz305
what's the newest firmware we need to be on for full compatibility for most/all games?
21.01 works perfectly fine! There might be a few games you might have to reinstall as .nsp's because I had to redo about 3 to 4 games with I updated, it was odd.

They were mega XCI's, I had to go back and install the parts individually the correct way with the updates.
Meaning Game NSP first, Update second, and DLC last.

And now they work like normal again.
 
  • Like
Reactions: Willsito_GG
21.01 works perfectly fine! There might be a few games you might have to reinstall as .nsp's because I had to redo about 3 to 4 games with I updated, it was odd.

They were mega XCI's, I had to go back and install the parts individually the correct way with the updates.
Meaning Game NSP first, Update second, and DLC last.

And now they work like normal again.

21.01 is the newest firmware out? And is there any important homebrew that is broken?
 
might be along for pretty long one time it was around for a long time.
Hope not to Long wait for stable Atmosphere from SciresM.
Post automatically merged:

You wait until its finished and ready. the Dev has a normal life outside the dev of atmos and not getting paid for it so we wait and when a new release happens we say thank you!
Must paid for Download link on Discord server when have no Membership.This situation is no Good.
 
  • Wow
Reactions: impeeza
  • Like
Reactions: BigOnYa
How long musst Wait for Official atmosphere the 1.10.0 is Prerelease and very Bad.
Atmosphère has been prerelease for years now.
Post automatically merged:

Must paid for Download link on Discord server when have no Membership.This situation is no Good.
Are you telling us what michael is charging you for Atmosphère releases? that smell like a scam from other people.
 
  • Wow
Reactions: josete2k
posted on another thread, but will ask here as well.

what is the safe way to update atmoshepe (or do i nee to do smth else?) and how do i know that it is ready for m OFW

updated ofw accidentally while transfering data to switch2.
now on my old switch OFW and CFW are both loading with a warning that they cannot go into sleep and smth about fuses

i think i need to update atmospher. but decided to ask first.
 
posted on another thread, but will ask here as well.

what is the safe way to update atmoshepe (or do i nee to do smth else?) and how do i know that it is ready for m OFW

updated ofw accidentally while transfering data to switch2.
now on my old switch OFW and CFW are both loading with a warning that they cannot go into sleep and smth about fuses

i think i need to update atmospher. but decided to ask first.

Update Hekate, Atmosphere, and all homebrew that you use.
 
  • Like
Reactions: miola
posted on another thread, but will ask here as well.

what is the safe way to update atmoshepe (or do i nee to do smth else?) and how do i know that it is ready for m OFW

updated ofw accidentally while transfering data to switch2.
now on my old switch OFW and CFW are both loading with a warning that they cannot go into sleep and smth about fuses

i think i need to update atmospher. but decided to ask first.
 
  • Like
Reactions: miola
i've updated the atmosphere and hekate following this guide.
but still the same warning loading the CFW. do i need update firmware on cfw?
 
i've updated the atmosphere and hekate following this guide.
but still the same warning loading the CFW. do i need update firmware on cfw?
you need to have syspatch installed and for the warning yes you will probably need to update the fw in your emmunand
 
any hints where to get one is allowed.
you need to have syspatch installed and for the warning yes you will probably need to update the fw in your emmunand

i see the link to dumper. but i assume i need to dump the new system
Post automatically merged:

any hints where to get one is allowed.


i see the link to dumper. but i assume i need to dump the new system
i think i've managed to do it
Post automatically merged:

yes it worked. i was not going to update the FW. but looks like it was necessary. thank you guys again! you all are the best
 
Last edited by miola,
I accidentally updated the firmware to 21.0.1, and wanted to downgrade the Switch back to 20.5 using Dawnbreak. After wiping the switch via TegraExplorer's wipe script, I had a switch on 20.5, but with the appropriate fuse burnt. If you get the error message, update it again to 21.0.1 and it's appropriate version of Atmosphere, get the warmboot file, and then downgrade down again. As long as a legit warmboot file is installed, your sleep function will still work.
 
Last edited by ASwitchUser,

Site & Scene News

Popular threads in this forum