Deep standby isn't working

[amadeus99]

After upgrade to build 150, doing a deep standby or a restart on the standby / restart menu don't work. It behaves like a restart gui.

Can anyone check this issue?

[birdman]

Deep Standby is working OK with 150 on my box

[dieselakita]

i had this problem and so did others but was on earlier image and was affecting vu solo2 the problem was when i updated the software putting me onto the updated image there was a bug so only way to fix it you had to do a couch flash or reflash

[MarsArtis]

This morning I experienced on my DUO:
first deep standby -> duo restarted
second deep standby -> Ok

[olly]

Deep standby works on my Gigablue ue,but no actual deep standby purple light,even tho its set in the lcd panel settings.

[JohnaJames]

After upgrade to build 150, doing a deep standby or a restart on the standby / restart menu don't work. It behaves like a restart gui.

Can anyone check this issue?

Having exactly the same problem with my Duo2 after updating to 150.

[amadeus99]

I think the online update isn't working because of the issue with deep standby and reboot.

I confirm the same issue with my Duo2.

[ndesorden]

Deep standby = reboot on 152, 150 and before on solo2...and image laggy...and nfs mounts issues and....more than 5 years with vix but...time to change

Anyway thanks for your job!

[JohnaJames]

After upgrade to build 150, doing a deep standby or a restart on the standby / restart menu don't work. It behaves like a restart gui.

Can anyone check this issue?

Problem still there after update to build 152 on my Duo2, selecting deep standby causes box to reboot.

[abu baniaz]

Is it going to be beneficial to upload crash or debug logs? If so, please do so.

[dude1]

Deep standby = reboot on 152, 150 and before on solo2...and image laggy...and nfs mounts issues and....more than 5 years with vix but...time to change

Anyway thanks for your job!


Problem still there after update to build 152 on my Duo2, selecting deep standby causes box to reboot.

I had this deep standby problem back on build 142 with a solo2 so did a couch flash with settings / plugins restore & that fixed it.

I've also just done the software update from build 147 to 152 & all seems to be working ok. Deep standby still ok, no lag from menus / epg / typing etc & image manager downloads now showing again which were blank on 147. Good work guys.

If you haven't done a couch / fresh flash I'd try that :)

[JohnaJames]

I had this deep standby problem back on build 142 with a solo2 so did a couch flash with settings / plugins restore & that fixed it.

I've also just done the software update from build 147 to 152 & all seems to be working ok. Deep standby still ok, no lag from menus / epg / typing etc & image manager downloads now showing again which were blank on 147. Good work guys.

If you haven't done a couch / fresh flash I'd try that :)


Can confirm that a fresh re-flash to build 152 followed by a settings/plugins restore has cured the deep standby problem I was having with recent builds on my Duo2.

[dude1]

Can confirm that a fresh re-flash to build 152 followed by a settings/plugins restore has cured the deep standby problem I was having with recent builds on my Duo2.

Good news that it fixed your duo2 as well :)

[edogg]

updated my solo2 to 153 and now i dont have deepstandby it just reboots

[JohnaJames]

updated my solo2 to 153 and now i dont have deepstandby it just reboots

Try doing a re-flash of 153 via couch or USB, then restore previous settings, worked for me.

[Lothar2]

yes, this way works. But why is the defect update not removed from feed? such updates are poor, poor, poor.

[Larry-G]

yes, this way works. But why is the defect update not removed from feed? such updates are poor, poor, poor.

Because thats not how GITHUB works, you can't just pull a file you have to either revert the commit or update it with a later version, and even then those changes won't be present in the image until a new build is completed.