I read there was a chance that the PD controller would lock up and prevent charging, but we never got any percentage on the chances of that.
For sure you can lock it up if you write at [0x40000000 - 0x40003000], via fusee-gelee/shofel2 or through a relocated payload.
But I spent the most time in RCM and a little bit in hekate (when I actually run the test payload and I reboot into rcm again).
My battery is always 100% after a "normal" dev session.
E.g., yesterday I had a lot of free time and played Bayo 2 handheld. Then I started development at 6%.
The time I got to sleep, it was 100% (and it was 99% of the time in RCM).
Btw, I use intermezzo.bin v1, if I remember correctly.
EDIT:
I forgot the most important: I never triggered that bug before. So I can't bug test it.
Last edited by CTCaer,
So what you're saying is there is a chance that being in RCM for too long can throw off the battery? And even if it does fully drain with AutoRCM installed, there won't be a problem with syncing up battery levels because the Switch is at or near zero charge as long as it accepts a charge?
I'm not talking about battery calibration (I never run linux before, so no problem here. But it still seems strange to me).
I'm saying that RCM will eventually drain the battery "completely". This is not generally good for a battery. Because 2 things can happen.
1. After many less than threshold drains, the total capacity will be reduced to a certain small percent.
2. If anything bugs completely and the charger can't cutoff normally the battery after a certain threshold, and the battery reaches 2.7V, that's it. It's dead. The battery's controller threshold will kick in and disable the cell completely.
(This can happen with the internal battery resistance also. That's why you need to charge any lithium battery at 40-50% and then store it.)
*All thresholds above are specific voltages, defined in the battery's controller, charger ic default config and config that loads on boot.
Normally the cutoffs are
Battery IC: 2.6-2.7V,
Charger IC/Power controller: 3.2V-3.3V
Anyway, what I really want to say, is that all these are not official and shit can happen.
The most important thing for a developer or a user, is to take care of the device.
You finished with hekate? Don't reboot (if you have autoRCM), power off.
You pressed the power button or plugged it in dock when was switched off? Don't leave it in RCM. Load a payload and power off.
etc.
--------------------- MERGED ---------------------------
@Draxzelex
I'm currently reading the other threads that talk about the battery charging in RCM.
I'll reply there
I'm saying that RCM will eventually drain the battery "completely". This is not generally good for a battery. Because 2 things can happen.
1. After many less than threshold drains, the total capacity will be reduced to a certain small percent.
2. If anything bugs completely and the charger can't cutoff normally the battery after a certain threshold, and the battery reaches 2.7V, that's it. It's dead. The battery's controller threshold will kick in and disable the cell completely.
(This can happen with the internal battery resistance also. That's why you need to charge any lithium battery at 40-50% and then store it.)
*All thresholds above are specific voltages, defined in the battery's controller, charger ic default config and config that loads on boot.
Normally the cutoffs are
Battery IC: 2.6-2.7V,
Charger IC/Power controller: 3.2V-3.3V
Anyway, what I really want to say, is that all these are not official and shit can happen.
The most important thing for a developer or a user, is to take care of the device.
You finished with hekate? Don't reboot (if you have autoRCM), power off.
You pressed the power button or plugged it in dock when was switched off? Don't leave it in RCM. Load a payload and power off.
etc.
--------------------- MERGED ---------------------------
@Draxzelex
I'm currently reading the other threads that talk about the battery charging in RCM.
I'll reply there
Download the sd files from the first page and the latest version of hekate, thats all
As always this info exists in OP.
And if you use it you can see the exact filenames in the dump log.
Once hekate launched the CFW, can we remove the SD to add/remove files without the need to relaunch hekate via payload?
Or each time we remove the sd, we need to send the payload again?
Or each time we remove the sd, we need to send the payload again?
Only remove the SD card while the Switch is powered off. Otherwise...
you would need to resend the payload becuase the system turns itself off when removing its sd you could just use FTPD
As stated by others, you can't remove it, once you are inside Horizon OS.
It will reboot (and may corrupt some files, especially the ones written when you were in it).
Anyway, Horizon OS does not support unmounting, so reboot it is.
As again stated by others, yes.
Why you are asking though?
My joycons where getting low from using docked mode for too long and had to recharge them. I usually shut my switch off unless I'm using it.
Oh I see. They surely charge in sleep mode and in horizon.
Haven't checked if the rail is powered in RCM/hekate or autoRCM, though.
Similar threads
