You must have installed Linux or Lakka then. It doesn't.Wrong. it is a known issue with AutoRCM as if you see my last few posts i had this issue from installing and just running Hekate payloads and only like 2 or 3 times.
You must have installed Linux or Lakka then. It doesn't.Wrong. it is a known issue with AutoRCM as if you see my last few posts i had this issue from installing and just running Hekate payloads and only like 2 or 3 times.
I never installed linux or used anything else, literally all i did was install AutoRCM and restart the switch a few times to test it and the next time i turned it on it wouldn't work.You must have installed Linux or Lakka then. It doesn't.
It's not a real issue if you're alone. You have probably leave your switch for some hours in RCM mode.Wrong. it is a known issue with AutoRCM as if you see my last few posts i had this issue from installing and just running Hekate payloads and only like 2 or 3 times.
But that would imply it was a battery drain issue, it took quite a while for the battery de-sync to fix itself after that even after uninstalling AutoRCM it still struggled to turn on.It's not a real issue if you're alone. You have probably leave your switch for some hours in RCM mode.
You said its a known issue. That is false. No one here speaks of getting a battery sync issue using AutoRCM.But that would imply it was a battery drain issue, it took quite a while for the battery de-sync to fix itself after that even after uninstalling AutoRCM it still struggled to turn on.
Well to be fair i'm not the only one who has commented in this thread with this problem.You said its a known issue. That is false. No one here speaks of getting a battery sync issue using AutoRCM.
Battery desync has only been happening to users who tried Lakka or Linux as others have said. You probably left your switch in RCM too long because you didn't power it off properly using the hetake boot menu.
Tinker can do it and it's $6 and can be powered with small little power supply was thinking an old wiimote rechargable bat .Raspberry Pie or teensy board maybe be. This is worth looking into for sure.
You said its a known issue. That is false. No one here speaks of getting a battery sync issue using AutoRCM.
Battery desync has only been happening to users who tried Lakka or Linux as others have said. You probably left your switch in RCM too long because you didn't power it off properly using the hetake boot menu.
The battery de-sync with AutoRCM HAS happened before. The below is one example.Well to be fair i'm not the only one who has commented in this thread with this problem.
edit: Also i have triple checked my switch has been turned off properly so i have never left it in RCM mode.
I've done the following:
I can't think of any explanation for this other than the Switch charging in RCM. The OS not lowering the battery percentage doesn't explain it being at 100%.
- Install AutoRCM and boot into Horizon, disconnecting the Switch from the computer.
- Let the Switch battery get to 50% in Horizon.
- Completely power off the system.
- Plug in the Switch to a power source, which causes it to enter RCM.
- Let it sit plugged in and in RCM all day.
- Unplug the Switch from the power source and quickly load Horizon.
- The battery is at 100%.
As you can see, if you leave the Switch charging in RCM with a corrupt BCT, the OS will think its accepting charge but the actual charge rate is diminished due to the corrupt BCT. The following is the differences in charges rates with and without AutoRCM during RCM.You're probably right. I performed this test a day or two ago. I powered on my Switch today, and it's dead or nearly dead. It definitely was not left in RCM.
So to achieve the battery de-sync, you would have to have AutoRCM installed AND have the Switch in RCM AND be actively charging it.So, Switch charges and does not charges in RCM. xD
The results (battery was 89%):
The switch can charge normally the battery, if the BCT is intact!
In RCM AND in hekate menu.
*BCT is the boot configuration table that autoRCM corrupts.
Tests showed that it was charging with the same current, as in Horison OS.
The current it was drawing with 89% battery, was 800mA - 1000mA, using Switch wall adapter. On PC, it was the max the hub could give.
------------------------------------
The switch cannot charge normally with a corrupt BCT (AutoRCM).
In hekate, it shows similar behavior (read below).
Extra emphasis on the "normally".
With autoRCM, basically a corrupt BCT, the switch behaves differently.
There are 2 behaviors that I saw when connecting to the switch wall charger:
- Common - It was draining 140-250mA.
- Common (in hekate) - 200mA - 400mA
- Rare (normally if you connect charger after powering off from HOS) - Drain of alternating 250mA and 1000mA, with surges of 2.5A.
------------------------------------
Summary - facts:
I don't know for behavior .3 what really happens and what Switch does. This can be easily examined, by connecting a current multimeter between battery and switch and check the readings.
- Switch can charge completely normally in RCM or Hekate with a BCT intact
- The percent % in Horizon OS, after a RCM charge, is not fake.
- Switch does not charge normally with AutoRCM, a.k.a corrupt BCT.
- Either it charges very slowly or sometimes with a broken slow/fast/slow/fast charge pattern:
- Or this behavior is current taken from the USB controller or the BPMP (Nvidia's Boot and Power management processor)
- In AutoRCM, the Charge IC probably can't update the battery calibration file and could make the percent fake.
So to achieve the battery de-sync, you would have to have AutoRCM installed AND have the Switch in RCM AND be actively charging it.
Do you have AutoRCM?I've done exactly this on multiple occasions and I know for sure my battery is calibrated properly still. Odd.
And you left the Switch charging in RCM for copious amounts of time or was it simply idling in RCM without accepting a charge?
I wasn't aware of how to turn off the switch fully for a while when I got AutoRCM, and would just put it into sleep or turn off via horizon (not hetake boot menu) and then would plug it in to charge, and it would do so very slowly. Never had any battery desync issue to this day.And you left the Switch charging in RCM for copious amounts of time or was it simply idling in RCM without accepting a charge?
It will accept charge with a corrupt BCT, albeit very, very slowly. I'm assuming after you left it charging (which is being done in RCM) that you hooked it up via USB, sent the Hekate payload, and booted into Horizon/CFW? Not hold power for 10+ seconds to manually power down the Switch to exit RCM?I wasn't aware of how to turn off the switch fully for a while when I got AutoRCM, and would just put it into sleep or turn off via horizon (not hetake boot menu) and then would plug it in to charge, and it would do so very slowly. Never had any battery desync issue to this day.
Yep that's correct that's what I did do. Now I always inject the payload from my phone to hit power off in the hetake menu.It will accept charge with a corrupt BCT, albeit very, very slowly. I'm assuming after you left it charging (which is being done in RCM) that you hooked it up via USB, sent the Hekate payload, and booted into Horizon/CFW? Not hold power for 10+ seconds to manually power down the Switch to exit RCM?
This is the last thing I can think of. Say you left your Switch at X battery percentage then you let it charge in RCM up to a Y percentage that you see once you immediately send Hekate. Now you use the Switch for some time and it goes down. Do you charge the Switch at all while it is on or do you do all of your charging in RCM?Yep that's correct that's what I did do. Now I always inject the payload from my phone to hit power off in the hetake menu.
Pressing the power button on your Switch with this will make it automatically go into RCM. In RCM, you cannot do anything outside of manually turning the Switch off or sending a payload. So it will stay in RCM if no payload is no found and not boot normally. It will only boot normally without AutoRCM installed.So this boots normally if no payload is found?