time_monotonic_ms values did wrap every ~24 days, leading to problems
in code that did not cope with that. Instead of fixing all places where
relative comparisons with time_monotonic_ms() are made, just use a
bigger datatype. Convert all users to the new type.
The start point of the monotonic clock is undefined, but in practice
it is often zero. There is lots of code that does not assume that a
timestamp can be that low and then fails in subtle ways.
Add a 7 day offset to the clock value to work around that.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@1271 e54a6e83-5905-42d5-8d5c-058d10e6a962
