Homebrew RELEASE Lakka.tv - turn your Switch into a RetroArch powered retrogaming console - includes PSX, N64 and PSP

Status
Not open for further replies.

WuskyDingo

Active Member
Newcomer
Joined
Jun 2, 2018
Messages
26
Trophies
0
Location
San Diego, CA
Website
www.youtube.com
XP
112
Country
United States
I might've found another way to recalibrate the battery. I left my switch plugged into a power source that does not give enough charge to keep it charging during a game, so I left a game running for a few hours until it finally died. Seems like battery calibration is back to normal now.
 

CatmanFan

Anxious and regretful
Member
Joined
Aug 14, 2016
Messages
1,954
Trophies
0
Website
www.youtube.com
XP
1,858
Country
Morocco
I might've found another way to recalibrate the battery. I left my switch plugged into a power source that does not give enough charge to keep it charging during a game, so I left a game running for a few hours until it finally died. Seems like battery calibration is back to normal now.
I don't think I have any sources that don't charge the Switch enough, though.
For me, the only solution on my hands might be the drain-cycle thingy. And this is coming from a guy who hasn't even booted Linux or Lakka yet...
 

Deathscreton

Well-Known Member
Member
Joined
Oct 1, 2009
Messages
826
Trophies
0
XP
1,082
Country
United States
Why does this not happen during normal switch use tho?
When you say "normal use", do you mean playing? Or just leaving the screen on?

When you're playing, screen burn in only happens when an image is left on the LCD for too long. If the image is moving, there's little to no chance of burn-in.
If you're talking about leaving the screen on with nothing moving, the Switch has an auto-sleep timer. Protects both the screen from prolonged still images that cause burn-in and reduce power consumption.
 
  • Like
Reactions: Centergaming

Phenj

Well-Known Member
Member
Joined
May 22, 2018
Messages
488
Trophies
0
XP
1,848
Country
Italy
I won't accept this fix until I see the source code.
@rajkosto reverse engineered the code
init_i2c_controller(0);
i2c_read_register((int)v2, 1u, 0, 0x6B, 0xA);
if ( v2[0] != 0x2F )
{
printk("ERROR: charger part number mismatch got: 0x%02x want: 0x%02x\n\n ", v2[0], 0x2F);
while ( 1 )
;
}
i2c_read_register((int)&v2[1], 1u, 0, 0x6B, 5);
v2[1] &= 0xCFu;
i2c_write_register(0, 0x6B, 5, &v2[1], 1);
i2c_read_register((int)&v2[2], 1u, 0, 0x6B, 7);
v2[2] |= 0x20u;
i2c_write_register(0, 107, 7, &v2[2], 1);
printk("\n\nBATFET is now disabled, disconnect the USB cable.\n\n");
 
  • Like
Reactions: Deathbot64

natinusala

Win32 error 31 is not an error
OP
Member
Joined
Dec 1, 2012
Messages
1,032
Trophies
0
Age
43
XP
2,904
Country
France
That's not a reason. Even if we know that it's not malicious, it's based on fusee primary, and giving the source code is required.
 
Status
Not open for further replies.
General chit-chat
Help Users
    SylverReZ @ SylverReZ: @Veho, How was your day, Veho? You high rn?