Closed formula-spectre closed 11 months ago
Are there any errors in info.log?
I grepped for errors but I did not find any; here is the log, with the entry sed /d out for.. reasons
https://termbin.com/c3nc
The only surprising element from your log is the file fingerprint that keeps changing. What really changes is the relative modification time component (the first four bytes). It first jumps two hours backward, goes back to its previous state and then jumps one hour forward.
might be related to https://github.com/koreader/koreader/issues/10996
Could you:
auto-power-off
to 0.02
in Settings.toml;RTC Wake Alarm: RtcWkalrm {
enabled: 1,
pending: 0,
time: RtcTime {
tm_sec: 1,
tm_min: 0,
tm_hour: 0,
tm_mday: 1,
tm_mon: 0,
tm_year: 70,
tm_wday: 4,
tm_yday: 1,
tm_isdst: 0,
},
there's also this:
Plato is running on a Kobo Touch C.
The framebuffer resolution is 600 by 800.
Went to sleep on October 19, 2023 at 09:30:43.
Woke up on October 19, 2023 at 09:59:30.
the rest is updated fingerprint/add new entry, but if you want the full log I can attach it!
Thanks, could you:
RTC Wake Alarm: RtcWkalrm {
enabled: 1,
pending: 0,
time: RtcTime {
tm_sec: 1,
tm_min: 0,
tm_hour: 0,
tm_mday: 1,
tm_mon: 0,
tm_year: 70,
tm_wday: 4,
tm_yday: 1,
tm_isdst: 0,
},
}
note: when I wake up the device instead it powers off completely; is this the new binary's doing?
When I wake up the device instead it powers off completely; is this the new binary's doing?
Yes : it's caused by a wrong assumption regarding the alarm.
uh okay, so is the problem the RTC? is there any way it can be fixed?
FWIW, I'm mildly curious what the read looks like just after the set, and not just after the alarm fired (in case it just happens to reset to Epoch only after firing), but given that I'm pretty sure we've seen sane reads no matter what on the same device, it's mostly a theoretical at this point ;p. My best guess is it's a (low) voltage related quirk, but the voltage read ioctl is even more unreliable (even on sane devices).
@NiLuJe
I'm mildly curious what the read looks like just after the set,
wym? do you want me to attach something?
Nah, that was some more contextual musings ;).
oh okay :)
I'm mildly curious what the read looks like just after the set
It looks like this.
(in case it just happens to reset to Epoch only after firing)
That's what I was hoping for.
Yeah, that would track with what I vaguely remembered after posting that from the original report we got of this ;).
@formula-spectre Please try the attached binary and see if it solves the issue.
yep, this last one works, my kobo turned off after 30 minutes!
so the next update is gonna work fine or am I gonna require a "special" binary?
So the next update is gonna work fine?
Yes.
might be related to https://github.com/koreader/koreader/issues/10996 this is my setting; Settings.toml.txt i have the line
the suspension after 15 minutes works fine, it's the autopoweroff that does not work