NEED HELP: Freezes in game after SXOS migration to Atmosphere ...

Zerstoren

New Member
OP
Newbie
Joined
Dec 2, 2021
Messages
4
Trophies
0
Age
42
XP
21
Country
France
Hello,

I recently migrated my switch from SXOS to atmosphere on the sysnand by following this guide: rentry.org/mys8q
Everything went well, the console starts up correctly, the homebrews ditto, the XCI games installed with the latest version of Awoo-Installer also with one detail.
Indeed it happens that the console freezes in play when switching from the game to the home menu and vice versa.
By freeze I mean that the image freezes and that I have almost no control with the buttons. if I keep pressing "home" I can put it on standby, but when I return to standby it's still frozen. If I press the power button to turn it off, it pretends to turn off but the screen remains backlit, I have to keep pressing the power button for a long time to turn it off ....

Basically, my Samsung 512gb card (new) was formatted as ex-fat. Thinking that the problem might come from the format, I formatted the card in Fat32 and redid a clean installation of ATM etc ... Results the freezes are still in the game.

This morning I manually performed the new console and atm update (AIO Updater having managed to download the atmosphere update but not install it) .... the problem persists.

Tonight, I spent "a little" time doing "a few" tests, and I am now able to reproduce the crash at will:
+ once the console has started if I play game A, I can go back and forth between the game and the home menu as much as I want, no problem ...
+ if then I quit this game to start a B game (or even relaunch game A), this time, if I try to switch from the game to the home menu and then from the home menu to the game, there, every time it's freezing!

What is "interesting" is that I may have also found a way to more or less work around the problem: if after quitting game A, I put the console to sleep, then when I woke up the console, I can launch game B (or even restart game A) and go back and forth between the game and the home menu as much as I want!
In fact it would seem that it is enough to put the console on standby and take it out between each game to avoid freezes ...
it will help out while waiting for a "real" solution ....

No matter how much I searched the internet, I couldn't find any way to solve my problem.
Thank you in advance for your help!

PS: the only homebrews installed are Awoo-Installer, Tinfoil self installer, JKSV, Checkpoint, Daybreack, AIO Switch updater
 

jimkage

Well-Known Member
Newcomer
Joined
Oct 19, 2017
Messages
81
Trophies
0
Age
19
XP
728
Country
Brazil
Same thing started happening to me as soon as I updated to 13.xx about a month ago, however, I found out if I insert the left joy con the console gets unstuck and I can start playing it again.
Never used SXOS.
 

cashboxz01

Well-Known Member
Member
Joined
Sep 28, 2008
Messages
142
Trophies
0
XP
915
Country
United States
You need a clean SysNAND dump for Atmosphere to work properly, despite what any guide tells you. I had those issues, but my SysNAND was clean AF (only used to activate exFAT before SX Core mod on a new console). I had my SX Core EmuNAND which I migrated using the option in hekate...Atmosphere was buggy AF, and all my game installs were gone. It would randomly crash on random titles installed using Tinfoil (yes, sigpatches were installed). I eventually gave up on Atmosphere for the time being.

SXOS > Atmosphere for all practical use (the reason why 99% of people use atmosphere anyway.)
SXOS is basically a pirated version of an OS people already use to pirate, but with several enhancements and everything you need built-in (cheats, installer, etc.)

So then I decided to do a clean install of Atmosphere on a new microSD card (not that my old one was cheap or low quality by any means). Worked like a charm, but I still prefer SXOS due to its ease of use.

tl;dr: if you've used SXOS and have ever updated it (99% of SX users have), then SXOS EmuNAND to Atmosphere "migration" won't work, and you'll have to start from a clean SysNAND dump.
 

Zerstoren

New Member
OP
Newbie
Joined
Dec 2, 2021
Messages
4
Trophies
0
Age
42
XP
21
Country
France
Hi,
Factory reset performed on Friday evening.
Yesterday I spent my time reinstalling everything (homebrews, games, backups ...) and testing ... It seems that the problem is solved :)
Thank you again for the help provided!
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • phalk @ phalk:
    I only do anything in my life to allow me to be lazier
    +1
    Gift
  • mr_switch @ mr_switch:
    same
    Gift
  • Veho @ Veho:
    TRJ, I learned all those in school/college.
    Gift
  • Veho @ Veho:
    As part of some course or other.
    Gift
  • Veho @ Veho:
    I forgot to list Assembler, Pascal and Matlab scripting.
    Gift
  • phalk @ phalk:
    I know some pascal, c, php
    Gift
  • phalk @ phalk:
    and I'm a History teacher
    Gift
  • Veho @ Veho:
    Went over the basics in all of them, never took it anywhere.
    Gift
  • Veho @ Veho:
    I do use bash for my job though. It's useful.
    Gift
  • phalk @ phalk:
    Assembler is something I always wanted to learn
    Gift
  • phalk @ phalk:
    but.... nah
    Gift
  • Veho @ Veho:
    No point really.
    Gift
  • Veho @ Veho:
    Even the simplest device these days runs some sort of high level language.
    Gift
  • The Real Jdbye @ The Real Jdbye:
    @Veho all the IT stuff i've learned in school has been extremely basic... i knew most of it already
    Gift
  • The Real Jdbye @ The Real Jdbye:
    it's better to learn on your own, it goes much faster than the snail pace they teach you at in school
    Gift
  • Coto @ Coto:
    assembly is actually great, gets you to run everything about 80% faster than C massaged code
    Gift
  • Coto @ Coto:
    assembler syntax is dead easy, but "how to put pieces together" logic requires to have in mind the original idea, and the CPU layout, and that's like double the work of C stuff. It's best to write C first, add some unit tests, then go assembly, then run the unit tests
    Gift
  • The Real Jdbye @ The Real Jdbye:
    it can run faster than compiled code, but modern compilers are really good at optimization and you need to be even better at assembly to do a better job
    Gift
  • Coto @ Coto:
    with that all your assembler base will actually work
    Gift
  • Coto @ Coto:
    even on embedded systems, without a damned debugger
    Gift
  • The Real Jdbye @ The Real Jdbye:
    syntax is easy but the code is hard to read, you can't look at a piece of code and expect to understand it without looking at all the code around it to see how it all works together so it takes much longer to read the code, it takes longer to write it too because what might be 1 line of code in C might be 20 lines of assembly
    Gift
  • The Real Jdbye @ The Real Jdbye:
    the language is very simple to understand (because it's barely a language at all) understanding how all the instructions work together to form a whole is another matter, in general it's such a pain to work with that i would never recommend it unless you have a need for it. don't listen to this guy and learn assembly just because you want to make your code run faster, you are wasting your time, but if you run into a situation where your code isn't fast enough even after you enabled -Ofast and you NEED it to be faster, then you can consider assembly
    Gift
  • The Real Jdbye @ The Real Jdbye:
    @Coto have you tried -Ofast btw? ;)
    Gift
  • Gift
  • Psionic Roshambo @ Psionic Roshambo:
    I have o fast before but I suspect we are talking different Os lol
    Gift
    Psionic Roshambo @ Psionic Roshambo: I have o fast before but I suspect we are talking different Os lol