Dinobot 4k +
Re: Dinobot 4k + #2
Re: Dinobot 4k + #3
Posted 23 October 2018 - 10:40
You could try my old builds: http://www.mediafire...q4d9/pli-extras
Also you could compile a new image: https://github.com/P...etas/pli-extras
But you need to ask the manufacturer to contact PLi if you want real and proper support
Open Vision sources: https://github.com/OpenVisionE2
Re: Dinobot 4k + #4
Re: Dinobot 4k + #5
Posted 23 October 2018 - 12:28
Unless you are Dinobot, you can't. We only make images on the request of the manufacturer.
And we had that request, but Dinobot never managed to create a working BSP or provide any developer support, so it didn't lead to anything.
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: Dinobot 4k + #6
Re: Dinobot 4k + #7
Re: Dinobot 4k + #8
Posted 23 October 2018 - 12:58
but on other images there is support. Almost all
There aren't that many "other" images. Most either use OE-Alliance or OpenPLi as their source.
OE-Alliance doesn't have manufacturer support, they get the drivers mailed, and maintain their own BSP's. We don't work that way, we need active support from the manufacturers developers, both in maintaining the BSP and in fixing issues. Without that, we can't support our images to our users. Even with support it is difficult enough sometimes. The fact that something builds doesn't mean it is usable, and doesn't mean it is stable.
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: Dinobot 4k + #9
Re: Dinobot 4k + #10
Posted 23 October 2018 - 14:40
Openatv,pure2,opespa,openNFR,opendroid,all supported. what's missing?
You seem to fail to understand the definition of "support".
Support is not "compile an image, and if the logo comes up, ship it", support is "I have a problem and I want it fixed". And we can't provide our users with that kind of support if we don't have a direct link with the driver developers. We also refuse to hack our way with all sorts of workaround for driver issues, which other images do because they can't get driver issues fixed.
If you don't need support, fine, use one of the OE-A derived images. It is as simple as that.
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: Dinobot 4k + #11
Re: Dinobot 4k + #12
Posted 23 October 2018 - 15:02
I understood. But the box is already sold with openatv. so I think that image is supported by the producer. it's correct?
You misunderstand me.
To be able to create an Enigma based image, the manufacturer needs to create Linux DVB compliant drivers. They have done that, emailed them to OE-A, with the subtext "have fun". Then OE-A starts reverse engineering, creates a BSP layer with those drivers for the box, sees if it compiles, and if it does, tada, image.
You see that image, you flash it, and then it doesn't work, or has a problem? And then what?
Then you are reliant on someone to do more reverse engineering, trying to figure out what the problem is, and if found hack a workaround into Enigma in case it is a driver issue. As the root cause, fix the drivers, can often not be addressed.
We refuse to do that, we have better things to do that to work around driver problems. If it is a driver issue, the manufacturer needs to fix that in the drivers. To be able to get that done, you need a direct channel to the developers of those drivers so you can have a technical conversion with them about this issue, so it can be fixed.
Dinobot didn't want to do that appearently. Instead, they tossed some drivers over the fence, with a "good luck with them", probably to maximize their profit (support is expensive).
We don't believe people should buy hardware from a manufacturer with that attitude, an OpenPLi image means positive purchasing advice to a lot of people, we don't want to play a part in increasing their profit while we have to shovel all the support shit. This is the same reason as for example us stopping building Dream Multimedia and Wetek images...
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: Dinobot 4k + #13
Re: Dinobot 4k + #14
Re: Dinobot 4k + #15
Posted 23 October 2018 - 16:55
In that case if you're so happy with the OE-A support, I'd say, keep using that, I see no point in using an OpenPLi image then?
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: Dinobot 4k + #16
Re: Dinobot 4k + #17
Posted 23 October 2018 - 17:53
There is a reason for the stability as well...
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: Dinobot 4k + #18
Posted 3 November 2018 - 10:07
what isthe coder of the pli asking to support the image?t startup it remains black screen.You could try my old builds: http://www.mediafire...q4d9/pli-extras
Also you could compile a new image: https://github.com/P...etas/pli-extras
But you need to ask the manufacturer to contact PLi if you want real and proper support
Re: Dinobot 4k + #19
Posted 3 November 2018 - 13:43
We require direct manufacturer support and access to the driver development team in onder to support a box.
We had an initial request from Dinobot which was never followed up, so I guess they are not interested.
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: Dinobot 4k + #20
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users