Hi, I installed the mr chromebox firmware on a samsung galaxy chromebook board name SASUKE and it works perfectly, the only issue being when I connect the battery and plug in the charger the light starts blinking green, blue, red then back to blue, the screen backlight turns on for half a second and then it shuts down and the loop restarts. Before installing the firmware I never had battery problems on this laptop.
Is there a way to fix this?
Thanks
This is something which is rather advanced. I can’t help you much for this reason, but I can give you a few tips. First of all I’d like to know which OS are you running right now
I installed Arch Linux
OK so unfortunately I’m not an experienced Linux user. You must search ways which you can use to update and optimize the battery charger mechanism in your laptop to prevent these kernel panics. If you don’t find any either you invent a driver or unfortunately you will need to wait for further driver announcement.
I don’t think it’s a Linux issue since it started having this problem even before installing Arch and when it bootloops I don’t even get to the UEFI screen, the display powers on for a second and then restarts.
your posts sound like the output of a LLM – completely lacking understanding of the actual question being asked. OP is having an issue with the device powering on when the battery is connected. The OS is irrelevant, since they aren’t booting to it. There are no drivers at play, no kernel panics.
1 Like
why was the battery disconnected in the first place? As per the supported device list, SASUKE doesn’t use the battery for WP. Samsung’s battery connectors often use very fine pitch pins which can be mis-connected. It’s possible you shorted something momentarily.
1 Like
OH my bad I’m not a native English speaker I thought they meant the charger
I misunderstood the process initially, I saw CP50 listed in WP methods and when I clicked on it the only section that said CP50 was “Disconnecting the battery” so I thought that’s what I had to do, then when it didn’t work I realized I had to bridge the pins and that worked. So I might have killed the battery? Can I check it somehow?
sure, you can restore the stock firmware and see if the issue persists. If so, the issue is either with the battery itself or the mainboard
I’ll try restoring in a couple of days but if I discover it’s a firmware problem I’ll let you know. Thanks for the help anyways!
1 Like