Android x86 (7 x64) throws +3 hours under VirtualBox, what should I do? (see details plz)?

Question

linux

details:
- I set the VM clock both UTC and back (by the way, the very first time I even tried to set it on a real ssd, and load both on real hardware and on the VM - there was no problem (or did not have time to appear), everything else was pleasantly stable)
- sinned on KDE Connect (not confirmed)
- time on the network and yes and no - does not help, after some time (from half an hour?) It still throws +3
- suspicion of applications (for the first time such garbage was not observed) but what ??? (thrown the hell out, although not yet launched everything) started with "17TRACK" - not confirmed .. the rest seem to be all RF-oriented, from those that have already launched
any ideas? (((

Answer 1

it was noticed that the only correlation of the time failure is the screen off timeout (30 minutes was set, and in 6-ke there was an item "never", but in 7.1 it is not unfortunately) and it seems like logically, the OS should have trying to "sleep"... it quickly became clear that there is a wagon and a trolley of applications on the topic " stay alive ", so, at the time of writing, this version is being checked))
ps bingo! .. although .. who would have thought? where exactly is the dog buried... but there remains a sediment - when saving the machine, and then restarting, the time is not synchronized with the network (or it is not known when it deigns to synchronize; ((... and an honest reboot, android, despite the fact that everything happens on a decent, average PC, and the virtual disk is located on quite a ssd (and not even on the system one), it's still a very long
pps and everything is just ridiculous - at the request of time sync we find a car of offers in the store))