Jump to content


Photo

Howto build unofficial pli for your unsupported receiver


  • This topic is locked This topic is locked
2740 replies to this topic

Re: Howto build unofficial pli for your unsupported receiver #621 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 18 April 2018 - 07:55

boot successfull.
but issue remains active as in persian prince  both builds.
exit or back button not working still.
hopefully prince will solve this issue soon.


First I thought the problem is remote xml file but now I guess the problem is non-standard rc which I have to patch enigma2 itself.

As far as I know WeTek won't respond to driver issues so the only choice is e2 patching ...

Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #622 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 18 April 2018 - 11:31

I did add a new patch regarding rc problem for wetek, compile an test again.

 

Good luck :)


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #623 fc_candido

  • Member
  • 7 posts

0
Neutral

Posted 18 April 2018 - 12:20

Thanks waiting for compilation 

No audio ac3 in wp2.


Edited by fc_candido, 18 April 2018 - 12:23.


Re: Howto build unofficial pli for your unsupported receiver #624 engineerkhan15

  • Senior Member
  • 145 posts

+18
Neutral

Posted 18 April 2018 - 12:50

Error while compiling for Wetek Play2:

WARNING: firmware-ap6210-1.0-r0 do_populate_lic: Could not copy license file /home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/LICENSE-CLOSE to /home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/license-destdir/firmware-ap6210/LICENSE-CLOSE: [Errno 2] No such file or directory: '/home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/LICENSE-CLOSE'
ERROR: firmware-ap6210-1.0-r0 do_populate_lic: QA Issue: firmware-ap6210: LIC_FILES_CHKSUM points to an invalid file: /home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/LICENSE-CLOSE [license-checksum]
WARNING: amremote-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '/home/tahir/openpli-oe-core/build/tmp/work/aarch64-oe-linux/amremote/1.0-r0/packages-split/amremote/usr/bin/remotecfg' [ldflags]
ERROR: firmware-ap6210-1.0-r0 do_package_write_ipk: The recipe firmware-ap6210 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
  /home/tahir/openpli-oe-core/build/tmp/deploy/ipk/all/firmware-ap6210_1.0-r0_all.ipk
    (matched in manifest-allarch-firmware-ap6210.package_write_ipk)
Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: firmware-ap6210-1.0-r0 do_package_write_ipk: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
ERROR: firmware-ap6210-1.0-r0 do_package_write_ipk: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/temp/log.do_package_write_ipk.31142
ERROR: Task (/home/tahir/openpli-oe-core/pli-extras/meta-amlogic/recipes-linux/linux-firmwares/firmware-ap6210.bb:do_package_write_ipk) failed with exit code '1'
ERROR: firmware-ap6210-1.0-r0 do_populate_sysroot: The recipe firmware-ap6210 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
  /home/tahir/openpli-oe-core/build/tmp/sysroots-components/all/firmware-ap6210/lib/firmware/brcm/ap6210-nvram.txt
    (matched in manifest-allarch-firmware-ap6210.populate_sysroot)
  /home/tahir/openpli-oe-core/build/tmp/sysroots-components/all/firmware-ap6210/lib/firmware/brcm/fw_bcm40181a2.bin
    (matched in manifest-allarch-firmware-ap6210.populate_sysroot)
  /home/tahir/openpli-oe-core/build/tmp/sysroots-components/all/firmware-ap6210/sysroot-providers/firmware-ap6210
    (matched in manifest-allarch-firmware-ap6210.populate_sysroot)
Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: firmware-ap6210-1.0-r0 do_populate_sysroot: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
ERROR: firmware-ap6210-1.0-r0 do_populate_sysroot: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /home/tahir/openpli-oe-core/build/tmp/work/all-oe-linux/firmware-ap6210/1.0-r0/temp/log.do_populate_sysroot.30311
ERROR: Task (/home/tahir/openpli-oe-core/pli-extras/meta-amlogic/recipes-linux/linux-firmwares/firmware-ap6210.bb:do_populate_sysroot) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5766 tasks of which 5585 didn't need to be rerun and 2 failed.

Summary: 2 tasks failed:
  /home/tahir/openpli-oe-core/pli-extras/meta-amlogic/recipes-linux/linux-firmwares/firmware-ap6210.bb:do_package_write_ipk
  /home/tahir/openpli-oe-core/pli-extras/meta-amlogic/recipes-linux/linux-firmwares/firmware-ap6210.bb:do_populate_sysroot
Summary: There were 6 WARNING messages shown.
Summary: There were 7 ERROR messages shown, returning a non-zero exit code.
Makefile:125: recipe for target 'image' failed
make: *** [image] Error 1



Re: Howto build unofficial pli for your unsupported receiver #625 frankviana

  • Senior Member
  • 474 posts

+4
Neutral

Posted 18 April 2018 - 13:12

It's possible for this too? https://www.aliexpre...1046658225.html

 

I have 1

 

 

Item specifics
  • Brand Name: ANEWISH
  • Model Number: DS-G2
Product Description
 

1.DVB S2  Android 4.0 TV Box hd satellite receiver
2.ARM Cortec A9
3.WIFI
4.1GB/4GB
5.HDMI 1080P

 

Features:
Android 4.0 operation system with higher performance. 
Amlogic-8726M3 Cortex A9 CPU Max.1.2GHz

Built-in WiFi: 802.11b/g/n.
Support Ethernet cable for Internet.
Support SD card up to 32GB. 
Easy one-click firmware upgrade from SD card. 
Support network 1080P HDMI videos.
Easy file sharing within the LAN. 
It is a perfect combination of HD media player, computer, digital photo frame, game console, and Internet set-top-box.

Support Http Live Streaming, such as PAK TV GLOBAL, etc.
Support Social Network, you can share information with friends on Facebook, Flicker, Twitter, or uploading files onto YouTube. 
It allows you to watch movies, listen to music, view picture albums, play games, read news, chat with friends easily.

 

 

Note: The flash plug-in of our TV box is well match with the CPU, please do not delete or replace it.

 

CPU Amlogic AML8726-M3 (Cortex A9)

GPU Mail-400

RAM 1GB DDR3

Storage(User Memory) 4GB NAND Flash

Android 4.0

Internet viewer FALSH11.1 & HTML5

TV system DVB-S2 Interface

Video CVBS/HDMI(1080P)

Audio Stereo L/R/HDMI/Optical

LAN RJ45(10/100Mbps)

CARD SD CARD

WIFI IEEE802.11 b/g/n

USB USB Host X 3

Power supply 12V/2A AC Adaptor RF RF INX1, RF OUTX1 IR IR X1 LED LED X1

 

Media format

 

Video MPEG1/MPEG2/MPEG4/H.263/H.264/VP8/AVS/VC-1/RV7/8/9

Audio M4A/AC3/AMR/MP3/OGG/WAV/WMA

Photo JPEG/BMP/PNG

 

                                                                                                                                   

 

Attached Files


Dreambox Two, GT-Media V8XS, GT-Media M7x, GT-Media v9 prime, Gt-Media Finder Meter 2, , TBS 6903-x v2, Octagon SF8008 single, Edision OS Mini 4k, Zgemma h9s SE, GT-Media V8UHD, Raspberry Pi 4, T95 Max + (CoreElec/Tvheadend), Freesky Triplo X, Zgemma h9 twin, Zgemma h9s, Amiko SHD 8900, Gt-Media GTC, Octagon SX88+, Octagon SX88, Vu Zero, Vu+ Zero 4K, Mecool K1/K2/K3, Azamerica s2010, Azamerica s810B, Nazabox Xgame, Koqit K1 mini, TBS 5520se, TBS 5925, TBS 6922se, Openbox X5, Openbox S9, AZBOX TITAN twin, AZBOX Premium+, AZBOX Elite , Rasp Pi, Rasp Pi 2/3, Orange Pi PC, Coolsat 5000, Dm528s, DM800se, Satlink 6933, Satlink 6960, Satlink 6932, GT-Media V8, Gt-Media V8 Meter,  PixelView PlayTV USB SBTVD ISDB-T (dib0700), Mygica S270 ISDB-T (Siano Rio). C-Band Motorized dish - 5,00m (20ºE - 116.8ºW), Ku-Band Motorized dish - 1,80m (3ºw - 116,8ºW)


Re: Howto build unofficial pli for your unsupported receiver #626 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 18 April 2018 - 13:28

 

 

Hey @WanWizard and @Persian Prince

 

I have the normal E4HD not the 4K version.

Here a Picture of it 

 

311kZfYc5pL.jpg

 

Here a screenshot with some informations:

Directlink:

https://abload.de/im..._1_c00kbpia.jpg

 

I hope you can help me :) i love OpenPLi on my Edision OS Mini, it's almost the same Hardware..

 

Thank you :)

It's "meta-ceryon" and I will add it next week: https://github.com/P...tas/meta-ceryon

 

e4hd
e4hdhybrid
e4hdcombo
twinboxlcd
twinboxlcdci5
odin2hybrid
odinplus
singleboxlcd
sf208
sf228
sf238
9910lx
9911lx
 
;)

 

Hey!

Thank you i will wait for it :)

 

Best Regards,

Jamal2367

 

Well I was super fast :D

 

meta-ceryon added:

 

  • 9910lx
  • 9911lx
  • e4hd
  • e4hdcombo
  • e4hdhybrid
  • odin2hybrid
  • odinplus
  • sf208
  • sf228
  • sf238
  • singleboxlcd
  • twinboxlcd
  • twinboxlcdci5

Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #627 WanWizard

  • PLi® Core member
  • 70,291 posts

+1,799
Excellent

Posted 18 April 2018 - 13:36

FYI, we've asked Axas to reconsider and rename the e4hd in their BSP, so collisions in machine name can be avoided. No response as of yet.


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: Howto build unofficial pli for your unsupported receiver #628 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 18 April 2018 - 14:16

FYI, we've asked Axas to reconsider and rename the e4hd in their BSP, so collisions in machine name can be avoided. No response as of yet.

They just need to merge this: https://github.com/A...-axasuhd/pull/1 :)


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #629 engineerkhan15

  • Senior Member
  • 145 posts

+18
Neutral

Posted 18 April 2018 - 15:52

Here is the latest build for Wetek Play 2:

https://www.mediafir...d -18042018.zip



Re: Howto build unofficial pli for your unsupported receiver #630 fc_candido

  • Member
  • 7 posts

0
Neutral

Posted 18 April 2018 - 17:24

Thanks .

rc key exit/back works.

ac3 no sound 



Re: Howto build unofficial pli for your unsupported receiver #631 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 18 April 2018 - 17:45

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

Edited by Persian Prince, 18 April 2018 - 17:46.

Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #632 algdu83

  • Senior Member
  • 36 posts

+1
Neutral

Posted 18 April 2018 - 20:24

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

 

I think you can help you with vitmod firmware for ki plus, kii pro
It's a multi boot that includes enigma, libreelec, android
To my memory he had solved the problems of image and audio

 

https://cloud.mail.r.../JYzE/nbjeQWc4X



Re: Howto build unofficial pli for your unsupported receiver #633 fc_candido

  • Member
  • 7 posts

0
Neutral

Posted 18 April 2018 - 20:53

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

OpenATV 5.3 and 6.0 ac3 works in wp2 



Re: Howto build unofficial pli for your unsupported receiver #634 jamal2367

  • Member
  • 17 posts

0
Neutral

Posted 18 April 2018 - 21:12

 

 

 

Hey @WanWizard and @Persian Prince

 

I have the normal E4HD not the 4K version.

Here a Picture of it 

 

311kZfYc5pL.jpg

 

Here a screenshot with some informations:

Directlink:

https://abload.de/im..._1_c00kbpia.jpg

 

I hope you can help me :) i love OpenPLi on my Edision OS Mini, it's almost the same Hardware..

 

Thank you :)

It's "meta-ceryon" and I will add it next week: https://github.com/P...tas/meta-ceryon

 

e4hd
e4hdhybrid
e4hdcombo
twinboxlcd
twinboxlcdci5
odin2hybrid
odinplus
singleboxlcd
sf208
sf228
sf238
9910lx
9911lx
 
;)

 

Hey!

Thank you i will wait for it :)

 

Best Regards,

Jamal2367

 

Well I was super fast :D

 

meta-ceryon added:

 

  • 9910lx
  • 9911lx
  • e4hd
  • e4hdcombo
  • e4hdhybrid
  • odin2hybrid
  • odinplus
  • sf208
  • sf228
  • sf238
  • singleboxlcd
  • twinboxlcd
  • twinboxlcdci5

 

Hey:)

Thank you :)

 

I will test it and give feedback :)

 

Best Regards,

Jamal2367



Re: Howto build unofficial pli for your unsupported receiver #635 starz

  • Senior Member
  • 59 posts

+1
Neutral

Posted 18 April 2018 - 22:40

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

Thanks for your great effort and support on unsupported devices:)

Edited by starz, 18 April 2018 - 22:41.


Re: Howto build unofficial pli for your unsupported receiver #636 taree

  • Senior Member
  • 48 posts

0
Neutral

Posted 19 April 2018 - 04:01

 

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

OpenATV 5.3 and 6.0 ac3 works in wp2 

 

we are very happy to see ur here fc_candido

ur efforts are really awsome .i follow u in ur forum.

but ac3 did  work with openatv5 and 6.0 ?

i dont think so


Edited by taree, 19 April 2018 - 04:03.


Re: Howto build unofficial pli for your unsupported receiver #637 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 19 April 2018 - 05:40

 

 

 

 

Hey @WanWizard and @Persian Prince

 

I have the normal E4HD not the 4K version.

Here a Picture of it 

 

311kZfYc5pL.jpg

 

Here a screenshot with some informations:

Directlink:

https://abload.de/im..._1_c00kbpia.jpg

 

I hope you can help me :) i love OpenPLi on my Edision OS Mini, it's almost the same Hardware..

 

Thank you :)

It's "meta-ceryon" and I will add it next week: https://github.com/P...tas/meta-ceryon

 

e4hd
e4hdhybrid
e4hdcombo
twinboxlcd
twinboxlcdci5
odin2hybrid
odinplus
singleboxlcd
sf208
sf228
sf238
9910lx
9911lx
 
;)

 

Hey!

Thank you i will wait for it :)

 

Best Regards,

Jamal2367

 

Well I was super fast :D

 

meta-ceryon added:

 

  • 9910lx
  • 9911lx
  • e4hd
  • e4hdcombo
  • e4hdhybrid
  • odin2hybrid
  • odinplus
  • sf208
  • sf228
  • sf238
  • singleboxlcd
  • twinboxlcd
  • twinboxlcdci5

 

Hey:)

Thank you :)

 

I will test it and give feedback :)

 

Best Regards,

Jamal2367

 

Don't forget to remove https://github.com/O...op/Makefile#L71 otherwise you will compile for the 4K version of e4hd, later with e4hdultra name we won't have this problem ;)


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #638 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 19 April 2018 - 05:59

 

 

Good to hear specially for me as I don't have any enigma2 STB, making people happy feels good :)

I think I can't help you with ac3.

OpenATV 5.3 and 6.0 ac3 works in wp2 

 

we are very happy to see ur here fc_candido

ur efforts are really awsome .i follow u in ur forum.

but ac3 did  work with openatv5 and 6.0 ?

i dont think so

 

Maybe we need to install "enigma2-plugin-systemplugins-servicemp3" by default ...


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #639 taree

  • Senior Member
  • 48 posts

0
Neutral

Posted 19 April 2018 - 08:01

thanks prince for idea :)

will try to install from system plugins openpli feed.



Re: Howto build unofficial pli for your unsupported receiver #640 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 19 April 2018 - 11:04

Well AXAS doesn't care about e4hdultra: https://github.com/A...-axasuhd/pull/1 so why should I?

Just remove meta-axasuhd from your Makefile as it's just one machine and why the hell I should care about one when I can support more? :D

Open Vision sources: https://github.com/OpenVisionE2



4 user(s) are reading this topic

0 members, 4 guests, 0 anonymous users