Vero 4k+ hangs up after some days in power save mode

Hello, starting from the new release (Kodi 19.0) my vero 4+ has a strange behavior.

After some days in power save mode (the red led is on) my unit hangs up: no more connectivity and does not respond to remote control but the led continue to be red. At this point I can only unplug the power cord to recover it…

Some one have the same troubles? Is there any logs I can activate?

thank you, D

Including no SSH?


That function currently has a problem. Don’t preconfigure and just configure after installation via MyOSMC → Network.

Sorry I’m not sure to understand, which function?

When the unit hang up I can’t login with ssh because the unit is not reachable through the network: the unit don’t reply to pings.

Sorry, somehow I replied to the wrong post.
Ignore my post.
In regards to your problem try to upload logs after the restart maybe the kodi.old.log tells something. Otherwise need to enable persistent logging in the hope the kernel logs give an indication.

Kodi log tell nothing. Today I found my Vero blocked, see below.

How can I enable persistent kernel log? In my /var/log/ directory I can’t find the usual kernel.log or syslog

2021-09-22 16:57:49.281 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.ar_sa v9.0.16 installed
2021-09-22 16:57:50.546 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.da_dk v9.0.38 installed
2021-09-22 16:57:51.769 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.de_de v9.0.39 installed
2021-09-22 16:57:52.800 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.es_mx v9.0.23 installed
2021-09-22 16:57:53.950 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.et_ee v9.0.26 installed
2021-09-22 16:57:54.892 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.fi_fi v9.0.40 installed
2021-09-22 16:57:56.362 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.he_il v9.0.22 installed
2021-09-22 16:57:57.325 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.it_it v9.0.33 installed
2021-09-22 16:57:58.441 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.ko_kr v9.0.28 installed
2021-09-22 16:57:59.504 T:17349    INFO <general>: CAddonMgr::FindAddon: resource.language.zh_cn v9.0.30 installed
2021-09-22 17:07:59.472 T:2712     INFO <general>: Activating standby mode
2021-09-22 17:07:59.472 T:2712     INFO <general>: Ignoring standby request: we are already in standby

That is kodi.log or kodi.old.log?

Unfortunately we need kernel messages from previous boots which are disabled by default with OSMC. To activate and provide such information, please, follow the steps below:

sudo mkdir /var/log/journal


Ok, I have created the /var/log/journal directory. Now we can wait some days…

To extract the logs I think I have to use: journalctl --since "1 hour ago" according to the hangs up… right?

Unfortunately we need kernel messages from previous boots which are disabled by default with OSMC. To activate and provide such information, please, follow the steps below:

  1. login via SSH to the OSMC device, user osmc, password osmc
  2. cd /var/log
  3. sudo mkdir journal
  4. (from now, kernel messages are written to new directories for every boot)
  5. sudo shutdown -r now
  6. now wait for the issue/event which is the problem of this topic
  7. once it happens again and you are forced to reboot the OSMC device or it rebooted automatically, you’ve to identify the right kernel message log:
    7.a) login via SSH and invoke
    sudo journalctl --list-boots --no-pager
    7.b) the lines start with an index id like 0, -1, -2, etc. and contain the date and time when log was started
  8. upload the appropriate kernel log using
    sudo journalctl -k -b <identified index> --no-pager|paste-log
    (replace <identified index> with the real index id, see above)
  9. also, upload the appropriate full log using
    sudo journalctl -b <identified index> --no-pager|paste-log
    (replace <identified index> with the real index id, see above)
  10. provide the returned URLs here
  11. don’t forget to remove the created journal directory otherwise your system’s root file system gets filled
    11.a) login via SSH
    11.b )cd /var/log
    11.c) sudo rm -R -f journal && sudo reboot (repeat this line if you get a ‘cannot remove’ error until it works and your ssh connection gets lost by the reboot)

Thx for your time. We hope to help you, soon.

I’m also seeing the vero 4K+ freeze when coming out of the suspend mode, only started happening after the 19 upgrade

Having the Same behaviour here.

5 posts were split to a new topic: Crash during movie play

My Vero 4K seems to be hanging as well. Every time I go to use it, it seems to have crashed, sometimes it’s a distorted UI, sometimes the screen is just red.
I now I have pull the power cord out and replace it every time I go to use it.

hello, last night my Vero crashed again during the standby.

journalctl --list-boots --no-pager
-1 c48ab06631d24f51ab33a93f421f951c Thu 2019-02-14 11:11:58 CET—Sat 2021-10-02 21:02:01 CEST
 0 0b0bc95d479d4ef480c9cf724b6596cb Sun 2021-10-03 10:53:25 CEST—Sun 2021-10-03 10:54:38 CEST

journalctl -k -b -1 --no-pager |paste-log

journalctl  -b -1 --no-pager |paste-log

grab-logs -A |paste-log

Unfortunately the logs don’t show anything of interest and nothing looks out of the ordinary.

Do you experience this version on an older version of OSMC?


Nope. Only with v19.
On my experience with Linux… when the system hang up it’s to late to write something on the logs…

Yesterday it happened again…

journalctl -b -1 --no-pager |paste-log

journalctl -k -b -1 --no-pager |paste-log

grab-logs -A |paste-log