Homebrew Discussion Turn off your Nintendo Switch!

[bundat]

That sounds like the autorcm issue that's been around for a while

But then this doesn't happen while in RCM:

You can see this because SX PRO Dongle will generate power if you plug it in

Otherwise, the capacitors in dongles running dry wouldn't be an issue with Switches with AutoRCM crashing while on the go (thus having no way to reboot if you don't have a way to revive the dongle, like a powerbank).

 

[Grmmish]

Oh wow. forget this stupid post... WHERE DO YOU GET AN N64 EMULATOR!? AND DOES IT RUN WELL???

 

[Deleted_444986]

(NOT CONFIRMED ON VANILLA CONSOLES AND NOT CONFIRMED TO HAVE HAPPENED BEFORE 6.0.0 UPDATE)

Ever since 6.0.0 all users that have installed modified software (It seems) now suffers from a problem that has to do with turning off your console. Perhaps this is Nintendo's 6.0.0 firmware problem? Or perhaps it's modified software but for now I will blame the SX OS/Other Payloads. (Even though I personally believe it's Nintendo's faulty firmware.)

When turning your Nintendo Switch off the system does not turn off. In CFW or not, it does not *ACTUALLY* turn off. You can see this because SX PRO Dongle will generate power if you plug it in and, more importantly, your Joy-Cons will be on. This seems to happen 100% of the time since 6.0.0 when turning off the system any other way but a hard reset. (Hold Power Button for 12 seconds.)

Holding the Power Button and pressing "Turn off" on the touch screen causes this to happen.
Pressing reset and it getting interrupted causes this to happen. (AutoRCM installed and pressing reset while the dongle is not in.)

Just wanted to say it wastes your Joy-Con batteries and your Nintendo Switch battery all because you did not know it failed to turn off... Every time.

same than me from leaked 6.0.0-4

 

[Grmmish]

I do not understand. O-o @Thomhack

 

[Techjunky90]

also keep in mind the retronx nsp I'm using is in no way associated with the official retronx, not trying to give retronx a bad name, developer is doing wonderful work

 

[Grmmish]

BUT DES IT RUN WELL?

 

[FierceDeityLinkMask]

Since nobody else is saying it I will, thanks for the PSA man.

 

[Grmmish]

Of course. Thanks for the appreciation. But this should also get everyone to realize not only NOW but in the future always ensure you Switch is off when you need it off just as a reminder things like this happen unexpectedly and goes to keeping a well maintained Nintendo Switch.

 

[PiracyForTheMasses]

I just pulled my SD card out, booted the switch up, powered it down, it's still not fully powering down.

 

[Grmmish]

EXACTLY^

 

[JHannibalSmith]

After reading the first post i turned my switch fully off but it would not come back on. I can boot into SX OS no problem but black screen when trying to boot into normal software. I can see that it is just auto Rcm causing this, BUT I have never turned auto Rcm on, I have never even gone into the options panel of SX OS before. I am running 6.0 firmware with SX OS pro 2.0. I have gone into settings now of SX OS and turned off auto RCM but it makes no difference, still black screen (stuck in auto RCM mode)when booting from normal start up??

 

[Grmmish]

Hmm. Not sure how to help you. I'd say wait until an update for the custom firmware that is more compatible with 2.0 SX OS.

 

[TurtlePowerrr]

(NOT CONFIRMED ON VANILLA CONSOLES AND NOT CONFIRMED TO HAVE HAPPENED BEFORE 6.0.0 UPDATE)

Ever since 6.0.0 all users that have installed modified software (It seems) now suffers from a problem that has to do with turning off your console. Perhaps this is Nintendo's 6.0.0 firmware problem? Or perhaps it's modified software but for now I will blame the SX OS/Other Payloads. (Even though I personally believe it's Nintendo's faulty firmware.)

When turning your Nintendo Switch off the system does not turn off. In CFW or not, it does not *ACTUALLY* turn off. You can see this because SX PRO Dongle will generate power if you plug it in and, more importantly, your Joy-Cons will be on. This seems to happen 100% of the time since 6.0.0 when turning off the system any other way but a hard reset. (Hold Power Button for 12 seconds.)

Holding the Power Button and pressing "Turn off" on the touch screen causes this to happen.
Pressing reset and it getting interrupted causes this to happen. (AutoRCM installed and pressing reset while the dongle is not in.)

Just wanted to say it wastes your Joy-Con batteries and your Nintendo Switch battery all because you did not know it failed to turn off... Every time.

This sounds like a user specific issue, you must be doing something wrong bud!

 

[nmkd]

Same^ XD But I've been making model and texture mods with Breath of the Wild so I absolutely need to turn it off often.. Which sucks because it's annoying.

Why turn it off? Just use FTP

 

[Grmmish]

Just use... Ftp? How would that help? I'd still need to reload the Switch to test new mods? Ftp is a very interesting idea...

EDIT: @TurtlePowerr

Maybe but I'm not the only one. And it does not explain the fact that without any CFW "CURRENTLY" installed this happens.

 

[Csmrcc]

Ok seeing all of this I think I'm not going to upgrade any soon...

 

[Grmmish]

Yeah. too many problems, for now please stay BELOW 6.0.0.

--------------------- MERGED ---------------------------

Now for the love of JABIS! PLEASE SOMEONE DIRECT ME TO THIS N64 EMULATOR THAT DOES NOT INVOLVE STREAMING A COMPUTER OPERATING SYSTEM OR ANY OF THAT! XD

 

[Shrike]

Can't you just kill it with 12 Seconds On/Off-Button Push ? Always worked for me, when i saw SXPRO was still on after turning the console off..

Btw.. I'm < 6.0.0

 

[mleeneg]

I am on FW 5.1.0 and this happens to me. I have to either hold power then press the turn off and hold power for 12 seconds or just hold power till the switch powers off.

Edit: also not using AutoRCM.

 

[Grmmish]

Good source Mleeneg. How often and when does it happen? On CFW? OFW as well?
I am especially focused on OFW. With CFW ANYTHING can happen. Game crashing. "Error has occurred" etc.

And YES you HAVE to hold it for 12 seconds. That's the problem. We don't want to do that. 6 seconds is long enough. Heck, 4 seconds is too damn long. The fact that it stealthily stays on does not help at all. :/