<krzk>
Viciouss: thanks, the fuel gauge behaved correctly?
<krzk>
Viciouss: mszyprow reported me that on Trats2 (Midas family device) there is a continuous interrupt on FG
<mszyprow>
krzk: i realized that this might be related to the fact that i don't have a real battery on my test setup, indead i connected a 4.6v power supply there
<krzk>
mszyprow: hmmm, so maybe the interrupt indeed is reported every time
<krzk>
also - isn't 4.6 too high?
<mszyprow>
krzk: I don't think so, i remember i've checked that
<krzk>
hm, ok, do you have an option to test it with regular Trats2 with battery?
<krzk>
or later figure out why FG complains with alerts - whether it is 0% SoC or maybe voltage out of range?
wwilly_ has joined #linux-exynos
<mszyprow>
krzk: currently i have no way to test it with real battery
wwilly_ has quit [Quit: This computer has gone to sleep]
tuxd3v has joined #linux-exynos
wwilly_ has joined #linux-exynos
tuxd3v has quit [Ping timeout: 256 seconds]
mszyprow has quit [Ping timeout: 256 seconds]
genii has joined #linux-exynos
mszyprow has joined #linux-exynos
tuxd3v has joined #linux-exynos
tuxd3v has quit [Remote host closed the connection]
tuxd3v has joined #linux-exynos
minicom has quit [Ping timeout: 264 seconds]
minicom has joined #linux-exynos
mszyprow has quit [Ping timeout: 272 seconds]
<Viciouss>
krzk: I continued working on Android with the patches applied and I didn't notice anything in logcat, the fuel gauge was working as expected