Paul Eggert <egg...@cs.ucla.edu> writes: > On 2023-08-09 19:14, Po Lu wrote: >> This uses the uptime counter (which also results in an SELinux denial >> for me, but different Android distributions have SELinux policies of >> varying strictness), which cannot establish the precise time the system >> started > > Emacs doesn't need a precise boot time. All it really needs is an > integer that uniquely identifies the current OS boot. > >> since time elapses between the read from the uptime counter and >> the read from the RTC. > > Emacs allows for up to one second of slop in computing the boot > time. (In other words, it assumes that reboots are at least one second > apart.) So if there are minor errors in computing the boot time it > should be OK. If the errors are greater than one second, though, > lock-file may assume that locks are stale when they're not.
OK, but the SELinux problem still stands in the way. There's an uptime counter in the Settings app though -- I'll try to establish how that works.
