U9-H with 008FW -> Waking up with no video signal [SOLVED]

M

minix4ever

Active member
Hello Guys,

I'm having a no VIDEO signal issue from the U9-H when put in sleep mode and waking up after a while. I say after a while because I don't have the issue when I put the box to sleep and wake it up within few minutes.

I tried turning on the TV before and after waking up the box without coherent results. I didn't recall experiencing this problem when the U9H was connected to my computer display via a KVM.

I never experience this issue from OFF to ON. Just from SLEEP to ON.

Is there a setting option or a tweak I can do to "force" or "reset" the video output signal when waking up?

Thanks.
 
In case of a language barrier, by Sleep I mean Standby mode. Problem only occures from Standby to ON. Not from complete OFF to ON.

And BTW this is not the first time I experience this kind of problems with an Android box [insert a competitor's name here] Which was resolved by later FW updates.
 
minix4ever said:
In case of a language barrier, by Sleep I mean Standby mode. Problem only occures from Standby to ON. Not from complete OFF to ON.

And BTW this is not the first time I experience this kind of problems with an Android box [insert a competitor's name here] Which was resolved by later FW updates.
Click to expand...

Try update MCU Firmware to the latest version
 

Attachments

  • MCU Firmware.png
    MCU Firmware.png
    48.3 KB · Views: 95
Solved BUT - Sometimes the box does not recover from Standby and just freeze with the blue light ON. Remote or Power button no longer respond. Need to pull the power cord to reboot.
 
minix4ever said:
Solved BUT - Sometimes the box does not recover from Standby and just freeze with the blue light ON. Remote or Power button no longer respond. Need to pull the power cord to reboot.
Click to expand...
Just wondering did you get to the bottom of the freeze problem. I have had no luck previously with standby mode and have had to resort to a complete shutdown which works well but I would dearly like to have standby working reliably.
 
Hi all,
Just a stub here, but this has been an issue with multi-core (specifically TV-boxes) since big.LITTLE and other similar multi-core implementations have existed. Android super-bug. Just power the thing down properly and be done with it. :p 30 Seconds boot is not going to change your lives :)

Don't quote me on this, but a senior android developer noted that screen-touch was often needed to "wake" the cores up (initiating the variable-core usage, as the user was now interacting). Since we're not touching our 58" 4K screens interactively (yet), that (theoretical bug) is here to stay.

So, for clarity, big.LITTLE means 4 "big, powerful, power-hungry" cores and 4 "little,power-efficient, weak" cores. From my conversations with the Dev-guy, again, don't quote me, there are about 2 LITTLE cores running when the phone is on standby (screen lock).. TWO! these are for messaging notification etc.. the screen swipe and the further interactions are designed to wake up the big cores and then load-balancing activates.

"Standby on Android-box'es seems to be the same process"

Wake-up activities without the touch-component, often do not "wake" the 4 bigger cores , or the other 2 LITTLE cores, hence the system running on two LITTLE cores until reboot.
 
Last edited:
You must log in or register to reply here.
Back
Top