And again after someone's update the receiver doesn't turn on guys what updates are you doing there and who is doing this probably the third time I've asked this question in three months... Maybe after this How did you do the update check them yourself and only then run them, somehow it looks very strange lately with OpenPli
after update not turn on my receiver
Re: after update not turn on my receiver #2
Posted Yesterday, 22:21
As always, you provide absolely zero information.
What receiver? What OpenPLi version? What exactly did you do? What exactly was updated? What exactly is the result? Any messages?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: after update not turn on my receiver #3
Re: after update not turn on my receiver #4
Posted Yesterday, 22:46
A development image is just that, it is always in state of flux. If you don't know how to recover from issues with it, then a development image maybe isn't for you.
Development image builds run automatically, in a continuous loop, using whatever code base is available when it starts, and that codebase can be in the middle of development, untested (as we build development images only for developers), or both.
Because of that, they are inherently unstable.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: after update not turn on my receiver #6
Posted Yesterday, 22:53
Yes, and? Who said those updates are tested? Who said those updates are stable?
You install a test image for developers, of which we EXPLICITLY state is not suitable for end-users. You ignore that, you run into issues, and then you have the balls to come here and complain?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: after update not turn on my receiver #7
Re: after update not turn on my receiver #8
Posted Yesterday, 22:59
Yes. And the answer is that that is your own fault.
All you can do now is wait until the next build is finished, hope your issue is fixed, and do an update from the commandline. Or better, flash a release image, which is tested and stable, and meant for end-users such as yourself.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: after update not turn on my receiver #9
Re: after update not turn on my receiver #10
Re: after update not turn on my receiver #11
Re: after update not turn on my receiver #12
Posted Yesterday, 23:08
You can follow the build progress and estimated finish time on your homepage, in the sidebar on the right.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: after update not turn on my receiver #13
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users