Toggle sidebar

Hardware CFW sleep mode drains battery 75% in 8 hours while OFW is normal

  • Thread starter Thread starter mosipd
  • Start date Start date
  • Views Views 18,002
  • Replies Replies 31
I just got done trying every firmware version from v11.0.1 down to v9.2.0 and I can't launch RetroArch in applet mode. Is there any way to disable applet mode pre-boot?
 
This is so frustrating, I'm getting ready to throw this switch out the fkn window.

That is all.
 
I'm not sure what you're stressing about, use the latest firmware and launch in application mode (not applet mode, don't use album icon) and get on with your day.

If you don't like holding R on a game to start hbmenu, then install a game you don't want to play, configure atmosphere to override that specific titleid rather than any application, and when a button is not pressed ("!R"), then selecting that game will open hbmenu. Bonus points for using sys-tweak to change the game's name and icon hbmenu.
 
I think my solution is using the Switch as a Linux tablet. I'm much more comfortable in Linux and this homebrew stuff is a bit too wonky and rigid for me. I just installed L4T and now I can run RetroArch and anything else compiled for ARM.

I am curious about one thing though, when you launch L4T how exactly does the boot process work? For example, does it require the original Nintendo OS to function? Could you theoretically install L4T to the system NAND and completely replace Nintendo's OS on the Switch?
 
Glad this thread is still open. its the only one i could find as I have a similar battery issue. In sleep mode my battery drains to 19% quickly and then sleep mode battery drain is pretty normal from 19% to 0%. Ive completely drained the battery a few times in hekate, fully charged up and booted to atmosphere. i had 1 - 2 occasions where after this process ive experienced normal sleep battery drain but more often than not im down to 19% after a few hours. the drain also happens in airplane mode.

fw: 14.1
latest atmosphere, fusee, sigpatches
also using an emunand


my last resort is to create an emunand from scratch but im reluctant as ive got a bunch of games backed up and would be tedious to re-install, reconfig everything.

anyone experience this before? is wiping and starting over my only option?
 
dirtyape705 said:
Glad this thread is still open. its the only one i could find as I have a similar battery issue. In sleep mode my battery drains to 19% quickly and then sleep mode battery drain is pretty normal from 19% to 0%. Ive completely drained the battery a few times in hekate, fully charged up and booted to atmosphere. i had 1 - 2 occasions where after this process ive experienced normal sleep battery drain but more often than not im down to 19% after a few hours. the drain also happens in airplane mode.

fw: 14.1
latest atmosphere, fusee, sigpatches
also using an emunand


my last resort is to create an emunand from scratch but im reluctant as ive got a bunch of games backed up and would be tedious to re-install, reconfig everything.

anyone experience this before? is wiping and starting over my only option?
Click to expand...
Dude same problem read in this thread that he hadn’t updated ofw just custom through daybreak. Is your ofw the same as your cfw? Mine is lower which I suspect may be the problem. Let me know if it helps I’m away for the next 8 days so have just been trying to find a solution for when I get back
 
Nekrobumping here because of exactly the same issue but slightly longer battery time.

Using atmosphere 1.9.1 and FW 20.1.1. Booting through a recent Hekate version.
I am using a partition based Emunand as my main system. Since I don't use the switch online my OFW is around 1X.X.X

I have this issue since ever and it is really annoying. I don't use the Switch often and when I want to play the battery is always drained to death meaning I have to wait for at least 30min to get atmosphere to boot so the console can be fast charged.

Using the original battery with original charger.
System can hold about 1.5hrs of playtime without charging which is really good for an 8 yr console.

Sleepmode holds about 10hrs until battery dies. Shutting the system down through horizon holds slightly longer around 2-3days. It is as if the switch is always on and can't power off.

Anything I can do? Or is it just the way the payload 'fusee gelee' works?

I would use the console more often if this issue wouldn't be that annoying.

EDIT: Missed a detail: AutoRCM is on so I don't have to trash the joycon rail pins.
 
GothicIII said:
Nekrobumping here because of exactly the same issue but slightly longer battery time.

Using atmosphere 1.9.1 and FW 20.1.1. Booting through a recent Hekate version.
I am using a partition based Emunand as my main system. Since I don't use the switch online my OFW is around 1X.X.X

I have this issue since ever and it is really annoying. I don't use the Switch often and when I want to play the battery is always drained to death meaning I have to wait for at least 30min to get atmosphere to boot so the console can be fast charged.

Using the original battery with original charger.
System can hold about 1.5hrs of playtime without charging which is really good for an 8 yr console.

Sleepmode holds about 10hrs until battery dies. Shutting the system down through horizon holds slightly longer around 2-3days. It is as if the switch is always on and can't power off.

Anything I can do? Or is it just the way the payload 'fusee gelee' works?

I would use the console more often if this issue wouldn't be that annoying.

EDIT: Missed a detail: AutoRCM is on so I don't have to trash the joycon rail pins.
Click to expand...
You're probably not going to like this answer, but the only surefire way to the battery drain is to recreate your Emunand. I did it recently and though it was a bit of a pain to have to restore the games, updates and saves, the problem was solved.

Other solutions were tried but they don't work consistently, like creating a new user, which would be less time-consuming but as I've said, it does not always work so I personally didn't even bother since it would also be time-consuming.

If you go down that route, I'd advise you to force USB3 to reinstall your games and updates, that should shave off quite a lot of time. You can then deactivate it as it apparently can mess with the controller connection.

The other alternative which I have not tested since I never needed it is this one, which requires you to modify atmosphere files but seems rather straightforward but it's hard to know about the side-effects: https://github.com/Atmosphere-NX/Atmosphere/issues/2528#issuecomment-3054401265
Post automatically merged:

hippy dave said:
Has nobody run a debugger or figured out the relevant changes in user files for this yet?

Edit: nm I thought this was about the issue after updating to fw 20
Click to expand...
As you can see with the working solution from Github, it's tied to the Switch notifications. It's trying to fetch a notification from Nintendo over and over again while being blocked and that completely prevents sleep mode. The console actually stays on and never disconnects from WiFi.

The problem actually started appearing with firmware 18. But once it's fixed (after recreating a new Emunand), it does not appear to return with subsequent firmware updates.
 
Last edited by XenoFredo,
  • Love
  • Like
Reactions: GothicIII and hippy dave
@XenoFredo

Thank you very much for this insight.
The atmosphere config you linked pretty much only disables wifi related stuff, which only would be needed if connected to Nin Servers, so I'd guess I'll give this a try.

But I don't think this is related to the other issue (battery drain when powered off), because horizon is not loaded so the wifi chip is probably in a sort of powered on but standby state until the firmware is loaded.

This issue is much more severe than the standby battery drain. I think it could be a problem with autorcm but am I really the only one who has battery drain with it? Turning off autorcm is not really an option since '+' and 'power' are pretty worn out and pushing both to register at the same time became hard.
 
  • Like
Reactions: XenoFredo
Yes, AutoRCM is known to cause that issue. Apparently your console is still on if the battery drains that much while it's supposed to be off. I didn't know those buttons could wear out with time. For me it's never been an issue to use the jig. I do so very rarely, when there is a Firmware update or I quickly want to check out the stock firmware.
 
  • Like
Reactions: GothicIII
XenoFredo said:
The other alternative which I have not tested since I never needed it is this one, which requires you to modify atmosphere files but seems rather straightforward but it's hard to know about the side-effects: https://github.com/Atmosphere-NX/Atmosphere/issues/2528#issuecomment-3054401265

As you can see with the working solution from Github, it's tied to the Switch notifications. It's trying to fetch a notification from Nintendo over and over again while being blocked and that completely prevents sleep mode. The console actually stays on and never disconnects from WiFi.

The problem actually started appearing with firmware 18. But once it's fixed (after recreating a new Emunand), it does not appear to return with subsequent firmware updates.
Click to expand...
Thank you for sharing this, looks like a great solution! I've been putting off updating to fw20+ because of this and sys-tweak, I hope someone fixes that soon too.
 
  • Like
Reactions: XenoFredo

Site & Scene News

Go to forum More news

Popular threads in this forum

Dekopon - (Mostly) Fullspeed 3DS Emulation on Nintendo Switch

Emulation Emulator  NetherSX2 - Switch Port

Emulation Emulator  Cemu - Wii U Emulator - Switch Port

Homebrew Homebrew game  Ultimate Switch Port Thread

Emulation Emulator  Dolphin - GC/Wii Emulator - Switch Port

Emulation Emulator  DrasticDS Emulator - Switch Port

Raikopon - a speedy, experimental 3DS emulator for Nintendo Switch (Dekopon Fork)

Homebrew Homebrew game  Plants vs Zombies Fusion - Switch Port