Jump to content


Photo

OpenPLi Release Candidate 7.2


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

Re: OpenPLi Release Candidate 7.2 #221 nor50

  • Senior Member
  • 423 posts

+1
Neutral

Posted 2 December 2019 - 21:10

That's often a sign of new version...


VU+ Ultimo 4K, 19.2, 13, 4.8 E via switch on input/tuner 1. 1W. Inverto Unicable II LNB IDLU-32UL40 on input/tuner 2. OpenPLi 8.3


Re: OpenPLi Release Candidate 7.2 #222 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 2 December 2019 - 21:21

Lol, not quite.

 

Our hoster has replaced an old and failing FreeNAS server by a NetApp NAS, so the data needed to be stored offline while the swap happened, and is currently restoring. As it is 1.2TB, it takes a while. ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #223 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,396 posts

+394
Excellent

Posted 2 December 2019 - 21:22

In this case it has to do with maintenance where a previous NAS, which is replaced just today, should be restored. And obviously that takes ‘a while’. So I’ve just been informed. 


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: OpenPLi Release Candidate 7.2 #224 FRAP

  • Senior Member
  • 329 posts

+23
Neutral

Posted 3 December 2019 - 14:21

Hello dear Erik!!! Thank you very Much for changing The lcd4linux plugin version (new release) I saw it here https://github.com/e.../commits/master THANK you THANK YOU thank YOU thank YOU!!!!!!!!!!!!!!


Alcohol for wimps. Strong people enjoy depression.


Re: OpenPLi Release Candidate 7.2 #225 fg54

  • Member
  • 13 posts

0
Neutral

Posted 4 December 2019 - 17:02

OpenPLi Enigma2 crash log

crashdate=Wed Dec  4 19:25:43 2019
compiledate=Dec  3 2019
skin=PLi-FullNightHD/skin.xml
sourcedate=2019-12-02
branch=rc
rev=e1f85da
component=Enigma2

stbmodel=et6000
stbmodel=dm800se
kernelcmdline= bmem=216M ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs console=null consoleblank=0
nimsockets=NIM Socket 0:
imageissue=openpli 7.2-rc %h


REMOVE Peer et6x00
REMOVE Peer et6x00


dmesg

<6>PCI2.3->SDRAM window: 512 MB
<6>bio: create slab <bio-0> at 0
<5>SCSI subsystem initialized
<7>libata version 3.00 loaded.
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Linux video capture interface: v2.00
<6>Advanced Linux Sound Architecture Driver Initialized.
<6>PCI host bridge to bus 0000:00
<6>pci_bus 0000:00: root bus resource [mem 0xd0000000-0xefffffff]
<6>pci_bus 0000:00: root bus resource [io  0x0400-0x83ff]
<6>pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
<7>pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
<6>PCI host bridge to bus 0000:01
<6>pci_bus 0000:01: root bus resource [mem 0x10510000-0x1051ffff]
<6>pci_bus 0000:01: root bus resource [io  0x8400-0x87ff]
<6>pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
<7>pci 0000:01:00.0: [14e4:8602] type 00 class 0x01010f
<6>PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
<7>pci 0000:01:00.0: reg 24: [mem 0x00000000-0x00000fff]
<7>pci 0000:01:00.0: reg 30: [mem 0x00000000-0x000007ff pref]
<7>pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
<6>pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
<6>pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
<6>Bluetooth: Core ver 2.16
<6>NET: Registered protocol family 31
<6>Bluetooth: HCI device and connection manager initialized
<6>Bluetooth: HCI socket layer initialized
<6>Bluetooth: L2CAP socket layer initialized
<6>Bluetooth: SCO socket layer initialized
<6>cfg80211: Calling CRDA to update world regulatory domain
<6>Switching to clocksource upg
<5>FS-Cache: Loaded
<6>NET: Registered protocol family 2
<6>TCP established hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>TCP: reno registered
<6>UDP hash table entries: 256 (order: 1, 8192 bytes)
<6>UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
<6>NET: Registered protocol family 1
<6>RPC: Registered named UNIX socket transport module.
<6>RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
<6>RPC: Registered tcp NFSv4.1 backchannel transport module.
<7>PCI: CLS 0 bytes, default 64
<5>NFS: Registering the id_resolver key type
<5>Key type id_resolver registered
<5>Key type id_legacy registered
<6>fuse init (API version 7.20)
<6>msgmni has been set to 567
<6>io scheduler noop registered
<6>io scheduler cfq registered (default)
<6>Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
<6>serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
<6>serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
<6>loop: module loaded
<7>sata_brcmstb 0000:01:00.0: version 4.0
<7>__clk_enable: sata [1]
<4>PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
<7>sata_brcmstb 0000:01:00.0: setting latency timer to 64
<6>scsi0 : sata_brcmstb
<6>scsi1 : sata_brcmstb
<6>ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
<6>ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
<6>Broadcom STB NAND controller (BrcmNand Controller)
<6>bcmemac: Broadcom STB 10/100 EMAC driver v3.0
<6>bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:16:b4:04:db:d1)
<6>bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
<6>usbcore: registered new interface driver zd1201
<6>ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<7>__clk_enable: usb [1]
<6>ehci-brcm ehci-brcm.0: Broadcom STB EHCI
<6>ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
<6>ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
<6>ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<6>ehci-brcm ehci-brcm.1: Broadcom STB EHCI
<6>ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
<6>ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
<6>ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 2 ports detected
<6>ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>ohci-brcm ohci-brcm.0: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
<6>ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>ohci-brcm ohci-brcm.1: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
<6>ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 2 ports detected
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>mousedev: PS/2 mouse device common for all mice
<6>i2c /dev entries driver
<6>usbcore: registered new interface driver btusb
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>TCP: cubic registered
<6>NET: Registered protocol family 17
<6>Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>Bluetooth: HIDP socket layer initialized
<5>Key type dns_resolver registered
<6>EBI CS1: setting up NAND flash (primary)
<6>mtd->oobsize=0, mtd->eccOobSize=0
<4>NAND_CS_NAND_XOR=00000000
<4>B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
<4>brcmnand_read_id: CS1: dev_id=ecf10095
<4>After: NandSelect=50000200, nandConfig=15142200
<4>Block size=00020000, erase shift=17
<6>NAND Config: Reg=15142200, chipSize=128 MB, blockSize=128K, erase_shift=11
<6>busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
<4>timing1 not adjusted: 5363444f
<4>timing2 not adjusted: 00000fc6
<4>eccLevel=15, 1Ksector=0, oob=16
<4>nbrBitsPerCell=2, cellinfo=0, chip->cellinfo=00000000
<4><--brcmnand_set_acccontrol: acc b4: d7ff1010, after: d7ff1010
<6>BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS1
<6>
<6>Found NAND on CS1: ACC=d7ff1010, cfg=15142200, flashId=ecf10095, tim1=5363444f, tim2=00000fc6
<6>BrcmNAND version = 0x0302 128MB @00000000
<4>B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
<4>brcmnand_read_id: CS1: dev_id=ecf10095
<4>After: NandSelect=50000200, nandConfig=15142200
<4>Found NAND flash on Chip Select 1, chipSize=128MB, usable size=128MB, base=0
<4>brcmnand_scan: B4 nand_select = 50000200
<4>brcmnand_scan: After nand_select = 50000200
<6>page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
<6>Brcm NAND controller version = 3.2 NAND flash size 128MB @18000000
<4>ECC layout=brcmnand_oob_bch4_4k
<6>brcmnand_scan:  mtd->oobsize=64
<6>brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
<6>brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
<4>-->brcmnand_default_bbt
<4>brcmnand_default_bbt: bbt_td = bbt_main_descr
<7>Bad block table Bbt0 found at page 0000ffc0, version 0x01 for chip on CS1
<7>Bad block table 1tbB found at page 0000ff80, version 0x01 for chip on CS1
<7>nand_read_bbt: Bad block at 0x03fe0000
<4>Adjust partition complete size from entire device to 7f00000 to avoid overlap with BBT reserved space
<4>Adjust partition rootfs size from entire device to 7900000 to avoid overlap with BBT reserved space
<5>Creating 3 MTD partitions on "brcmnand.0":
<5>0x000000000000-0x000007f00000 : "complete"
<5>0x000000000000-0x000000600000 : "kernel"
<5>0x000000600000-0x000007f00000 : "rootfs"
<6>PM: CP0 COUNT/COMPARE frequency depends on divisor
<5>UBI: attaching mtd2 to ubi0
<6>ata1: SATA link down (SStatus 4 SControl 300)
<6>usb 1-2: new high-speed USB device number 2 using ehci-brcm
<6>scsi2 : usb-storage 1-2:1.0
<6>usb 2-1: new high-speed USB device number 2 using ehci-brcm
<6>ata2: SATA link down (SStatus 4 SControl 300)
<6>hub 2-1:1.0: USB hub found
<6>hub 2-1:1.0: 4 ports detected
<6>usb 2-1.2: new full-speed USB device number 3 using ehci-brcm
<5>UBI: scanning is finished
<5>UBI: attached mtd2 (name "rootfs", size 121 MiB) to ubi0
<5>UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
<5>UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
<5>UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
<5>UBI: good PEBs: 967, bad PEBs: 1, corrupted PEBs: 0
<5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
<5>UBI: max/mean erase counter: 17/2, WL threshold: 4096, image sequence number: 1062708493
<5>UBI: available PEBs: 0, total reserved PEBs: 967, PEBs reserved for bad PEB handling: 19
<6>ALSA device list:
<6>  No soundcards found.
<4>Warning: unable to open an initial console.
<5>UBI: background thread "ubi_bgt0d" started, PID 51
<5>UBIFS: background thread "ubifs_bgt0_0" started, PID 52
<5>UBIFS: recovery needed
<5>scsi 2:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 0 CCS
<5>sd 2:0:0:0: Attached scsi generic sg0 type 0
<5>sd 2:0:0:0: [sda] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
<5>sd 2:0:0:0: [sda] Write Protect is off
<7>sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
<3>sd 2:0:0:0: [sda] No Caching mode page present
<3>sd 2:0:0:0: [sda] Assuming drive cache: write through
<3>sd 2:0:0:0: [sda] No Caching mode page present
<3>sd 2:0:0:0: [sda] Assuming drive cache: write through
<6> sda: sda1
<3>sd 2:0:0:0: [sda] No Caching mode page present
<3>sd 2:0:0:0: [sda] Assuming drive cache: write through
<5>sd 2:0:0:0: [sda] Attached SCSI removable disk
<5>UBIFS: recovery completed
<5>UBIFS: mounted UBI device 0, volume 0, name "rootfs"(null)
<5>UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
<5>UBIFS: FS size: 118468608 bytes (112 MiB, 933 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
<5>UBIFS: reserved for root: 0 bytes (0 KiB)
<5>UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3D20D2FD-9B04-4073-8592-966F6CAE8104, small LPT model
<6>VFS: Mounted root (ubifs filesystem) on device 0:10.
<6>devtmpfs: mounted
<6>Freeing unused kernel memory: 316k freed
<6>EXT4-fs (sda1): recovery complete
<6>EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
<6>usbcore: registered new interface driver tpm
<4>dvb: module_layout: kernel tainted.
<4>Disabling lock debugging due to kernel taint
<6>Console: switching to colour frame buffer device 160x45
<6>input: dreambox remote control (native) as /devices/virtual/input/input0
<6>input: dreambox advanced remote control (native) as /devices/virtual/input/input1
<6>DVB: registering new adapter (dvb0)
<6>platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
<6>input: front panel as /devices/virtual/input/input2
<6>Console: switching to colour dummy device 80x25
<6>NET: Registered protocol family 10
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: © 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>Installing knfsd (copyright © 1996 okir@monad.swb.de).



Re: OpenPLi Release Candidate 7.2 #226 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 4 December 2019 - 17:06

No crash information present.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #227 FRAP

  • Senior Member
  • 329 posts

+23
Neutral

Posted 4 December 2019 - 19:41

Hello

LCD4linux The plugin has been updated to the new version "V5.0-r6" No complaints! (No problem) Thanks for that to the whole OpenPLi team !!! I must inform you (Maybe this information is useful to you) I noticed on the path / var / lib / opkg / status An old plug-in entry remained in this file. From this a question symbol appears See photo
 
Package: enigma2-plugin-extensions-lcd4linux
Version: 5.0-r4-30+fa07d72-r0.0
Depends: png-util, pydpflib, python-codecs, python-ctypes, python-datetime, python-email, python-imaging, python-mutagen, python-pyusb, python-shell, python-simplejson, python-subprocess, python-textutils, python-zlib
Status: install ok installed
Architecture: mips32el
Conffiles:
 /etc/enigma2/lcd4config be6e66984b8794862e242c243d650970
Installed-Size: 3791649
Installed-Time: 1575473254

Attached Files


Alcohol for wimps. Strong people enjoy depression.


Re: OpenPLi Release Candidate 7.2 #228 ciciol

  • Senior Member
  • 157 posts

+10
Neutral

Posted 5 December 2019 - 19:51

For me, the plug still does not work properly and switching programs then takes longer and with the message that the tuning has failed.

Re: OpenPLi Release Candidate 7.2 #229 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 5 December 2019 - 20:58

Which is why we said that nothing substantial had changed, and therefore the update was rather pointless.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #230 FRAP

  • Senior Member
  • 329 posts

+23
Neutral

Posted 5 December 2019 - 23:07

Which is why we said that nothing substantial had changed, and therefore the update was rather pointless.

A small example from a pointless update.
Earlier in my display, when there was no Timer, incomprehensible characters were displayed (here is an example -?% ;? "" %% ") After updating the version, the Author appeared on my display the correct text" No Timer "I am not familiar with the Author of the plugin but I'm sure the fact that he does not crawl into the plugin code from the fact that he has nothing to do.
 
Here is the text of the change I found it with the UltraCompare program (this is one example)
 
Version = "V5.0-r4"
 
w,h = self.draw[draw].textsize(_("no Timer"), font=font)
ShadowText(draw,POSX+h+5,ConfigPos,_("no Timer"),font,ConfigColor,ConfigShadow)
 
 
Version = "V5.0-r6"
 
tx = Code_utf8(_("no Timer"))
w,h = self.draw[draw].textsize(tx, font=font)
ShadowText(draw,POSX+h+5,ConfigPos,tx,font,ConfigColor,ConfigShadow)
 
The ignoramus hooligans like me should write about a meaningless update! But not like you Dear WanWizard !!! :) :)

Alcohol for wimps. Strong people enjoy depression.


Re: OpenPLi Release Candidate 7.2 #231 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 6 December 2019 - 00:07

I didn't say there were no changes, I said there were no significant changes: https://github.com/e...71ff68ed9dbd9a3

 

Your example is what I call "a detail", not "a significant change".


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #232 daveraver

  • Senior Member
  • 412 posts

+5
Neutral

Posted 6 December 2019 - 00:48

Hi mates, I have installed 7.2rc on vu+ zero 4k, and I see kodi 17.6 available. It's vu+ near to launch kodi 18 stable on their 4k boxes?? Is there any confirmed info??

 

regards,



Re: OpenPLi Release Candidate 7.2 #233 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 6 December 2019 - 01:47

No.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #234 daveraver

  • Senior Member
  • 412 posts

+5
Neutral

Posted 6 December 2019 - 11:12

ok, thanks, I saw a youtube video showing openbh running kodi 18 and netflix addon yesterday. If it is real, we could wait some changes in next months, I hope so...
I am sorry for this offtopic.

regards,

Edited by daveraver, 6 December 2019 - 11:13.


Re: OpenPLi Release Candidate 7.2 #235 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 6 December 2019 - 13:16

Kodi is a pain to get compiled, especially for the 70+ different boxes we need to support. So someone needs to invest time in it, and afaik nobody of us uses Kodi.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #236 daveraver

  • Senior Member
  • 412 posts

+5
Neutral

Posted 6 December 2019 - 14:18

@wanwizard , I thought kodi came prebuilt by vu+ brand.. someday before I read this of some openpli teamcore member or I think so. So I thought it wasnt a problem... I am sorry that adapt kodi to openpli were too hard to achieve. I didnt know it, I thought that was the first case I've said... I have had working kodi 17.6 on openpli 6.2 with very good performance... and it will keep on this way, thanks to openpli team!

regards,

Edited by daveraver, 6 December 2019 - 14:22.


Re: OpenPLi Release Candidate 7.2 #237 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 6 December 2019 - 14:44

Nope, it's build from source. But as it wants to talk directly to the hardware, afaik it does need driver support.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: OpenPLi Release Candidate 7.2 #238 daveraver

  • Senior Member
  • 412 posts

+5
Neutral

Posted 6 December 2019 - 22:07

so it depends of vu+... thanks for the explanations @WanWizard , regards


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users