Posts by jim1985

    My dad recently ordered an Xtrend ET9500 from WOS.


    I have to say that for the price I am massively impressed with it. If I was in the market for a new E2 dual tuner receiver I would definitely be throwing my money at one of these right now

    Best way to do this is to have OpenELEC running on the Raspberry Pi.



    Within OpenELEC you need to go to Settings -- Addons and look for PVR Clients. You need to find the one called VU+ / Enigma 2 Client. Install it and then configure it by pointing it to the IP address of your Wetek running PBNigma.
    I've not tried this personally myself with the Wetek but I used to run this exact set up when I used to have a Vu Duo so it should work just the same for the Wetek

    Server A, the one with the card should have a user account on it. AU should be enabled for this account. Also, AU should not be disabled for the physical reader.


    Server B, the one where your peers are set up should have a proxy reader set up via the newcamd protocol back to server A, AU should not be disabled for this proxy reader. Now at least one user account on this server should have AU enabled. This should then allow server B to push EMMs through to server A and your real card should then get it's entitlements updated periodically

    So I've recently got my hands on the new Wetek enigma2 remote control after my original Wetek remote control decided to give up on me.


    The first thing I discovered was that the enigma2 remote does not work in OpenELEC.
    I only use OpenELEC on my Wetek so this was a bit of a problem for me. I have managed to get it working though so I thought it best I share how to get it working with everyone on here just in case you decide to purchase the enigma2 remote and want to use it in OpenELEC as well.



    So, all you need to do is download the attached remote.conf file and copy it to your Wetek OpenELEC installation in the /storage/.config/ folder
    Now reboot your Wetek and the enigma2 remote should be working fine.




    One thing to point out is that the power button on the remote does NOT power the Wetek on when running OpenELEC.


    I have created this remote.conf file myself. There are a few buttons on the remote that I have not enabled simply because I couldn't decide what to have them do. The disabled buttons are as follows


    • Red
    • Green
    • Yellow
    • Blue
    • FAV (I couldn't figure out how to get this key to bring up the OpenELEC favourites list)
    • PVR (I couldn't figure out how to get this key to bring up the OpenELEC live TV recordings list)
    • Audio (I couldn't figure out how to get this key to bring up the OpenELEC media Audio settings)
    • DTV
    • Apps
    • The button below the Apps button



    Every other button should work as expected.



    Any problems please reply here and I'll try to get them resolved

    OpenELEC 6.0 Beta 3 Update File


    OpenELEC 6.0 Beta 3 NAND Install


    OpenELEC 6.0 Beta 3 SD Card Image


    Updated core Components (summary) since OpenELEC 5.95.2 (6.0 beta 2)


    • update to dvb-firmware-0.0.48
    • update to kodi-15.0-rc2-0aa930b
    • update to bcm2835-bootloader-47d51d6
    • update to bcm2835-driver-47d51d6
    • update to mesa-10.6.2
    • update to gettext-0.19.5
    • update to linux-4.1.2
    • update to nano-2.4.2
    • update to libevdev-1.4.3
    • update to libshairplay-0f41ade
    • update to libinput-0.19.0
    • update to xproto-7.0.28
    • update to openssh-6.9p1
    • update to xproto-7.0.28
    • update to openssh-6.9p1
    • update to libva-1.6.0
    • update to libva-intel-driver-1.6.0
    • update to platform-1.0.10
    • update to libdrm-2.4.62
    • update to gcc-4.9.3
    • update to curl-7.43.0
    • update to mpfr-3.1.3
    • update to xorg-server-1.17.2
    • update to xf86-video-nvidia-352.21
    • update to RTL8812AU-3f015f0
    • projects/RPi*/linux: enable CONFIG_BCM_VC_SM, needed to show HW Cursor
    • projects/RPi2/patches/linux: update RPi support patches
    • projects/RPi2/patches/kodi: update RPi support patches
    • projects/imx6/linux: enable CONFIG_SND_SOC_IMX_AC97_VT1613
    • Fix 16bpp patch which doesn't use stride consistently - see #4221
    • kodi: enhance english kb layout a bit.
    • linux: add patch for Hauppauge HVR-2205/2215/2255 support
    • linux: fix TechnoTrend S2-4600 DVB-S received
    • Configure RPi/RPi2 platform with optimal CPU and IO settings
    • projects/WeTek_Play/initramfs: Init framebuffer according to HDMI resolution from kernel command line
    • projects/WeTek_Play/patches/kodi: Make ugly IEC958 workaround less ulgy
    Quote

    Work starts this week to connect the first 20,000 Manchester homes and businesses to broadband speeds of 152Mb, which the operator says is at least twice as fast as the fastest speeds available from BT, TalkTalk and Sky


    I think Virgin Media needs to check their facts before making statements like that. Where I live BT offer 300Mb FTTP connectivity.
    Unless perhaps they are referring to the specific area in Manchester that they are starting work in?

    If you're running OpenELEC 6.0 Beta 1 or any of the dev builds released AFTER Beta 1 then yes the Update file will update an SD installation or a NAND installation. It is Universal now.



    BUT
    If you are currently running OpenELEC 5.0.8 or lower then yes you will need to go for a full reinstall

    The top one in the list mate.
    Updates are universal now, SD & NAND use the same update file.



    What version are you currently running though? If you're running 5.0.8 or lower then you need to do a fresh installation

    OpenELEC 6.0 Beta 2 Update File


    OpenELEC 6.0 Beta 2 NAND Install


    OpenELEC 6.0 Beta 2 SD Card Image


    Updated core Components (summary) since OpenELEC 5.95.1 (6.0 beta 1)


    • update to mesa-10.6.0
    • update to kmod-21
    • update to kodi-15.0-beta2-daedd5f
    • update to freetype-2.6
    • update to OpenELEC-settings-0.6.8
    • update to libressl-2.1.7
    • update to RTL8192DU-7498302, this fixes #4187
    • update to bcm2835-bootloader-37600d5
    • update to bcm2835-driver-37600d5
    • update to wireless-regdb-2015.06.05
    • update to fuse-2.9.4
    • update to libmicrohttpd-0.9.42
    • update to wireless-regdb-2015.05.15
    • update to wlan-firmware-0.0.29
    • update to misc-firmware-0.0.14
    • update to iwlwifi-firmware-0.0.2
    • update to linux-4.0.5
    • update to xf86-input-libinput-0.11.0
    • update to libinput-0.17.0
    • update to libpng-1.6.17
    • update to xf86-video-intel-7d30cce
    • update to libva-1.6.0.pre1
    • update to libva-intel-driver-1.6.0.pre1
    • update to xorg-server-1.17.1
    • update to cmake-3.2.3
    • update to u-boot-imx6-e817fa3
    • update to arm-mem-4418bb4
    • update to llvm-3.6.1
    • update to sqlite-autoconf-3081002
    • update to dbus-1.8.18
    • update to glib-2.44.1
    • update to udevil-0.4.4
    • update to firmware-imx-3.14.28-1.0.0
    • update to imx-vpu-5.4.28
    • update to libfslvpuwrap-1.0.58
    • update to RTL8188EU-3091828
    • update to e2fsprogs-1.42.13
    • update to ffmpeg-2.6.3
    • update to libXrandr-1.5.0
    • update to randrproto-1.5.0
    • update to dcadec-37d8e68
    • update to libssh-0.7.0
    • update to xf86-video-nvidia-346.72
    • update to libbdplus-0.1.2
    • update to libbluray-0.8.0, enable UDF support
    • update to libdrm-2.4.61
    • update to libcec-3.0.0
    • update to libhdhomerun-20150406
    • projects/RPi*/patches/kodi: update RPi support patches
    • linux: add and update some AMD and RTL firmwares
    • IMX: Update 352Mhz patch for newer kernel remove pr_info message
    • kodi: add PR7280
    • projects/*/linux: enable CONFIG_HID_SMARTJOYPLUS, this fixes #3973
    • Build SPI BCM_2708 and BCM_2835 as modules - in line with Raspbian
    • Add CuBox-i remote codes
    • projects/WeTek_Play/linux: Disable CONFIG_FB_AMLOGIC_UMP in kernel config
    • project imx6: add sgtl5000 analog output alsa config file
    • projects/RPi*|imx6/linux: enable CONFIG_W1, this fixes #3975
    • libc: install package 'arm-mem' on all RPi variants
    • arm-mem: install libarmmem-a7.so on cortex-a7
    • projects/WeTek_Play/patches/kodi: add patch to force IEC958 Audio and remove temporary patch to Allow audio passthrough
    • libressl: symlink cert.pem
    • libressl: fix certificate name

    If you want to run XBMC / Kodi then I'd strongly consider you look at getting a WeTek Play and install OpenELEC on it.


    The Prismcube Ruby is a little outdated now and was never very good even when it was first released in my opinion

    Which build have you been trying to install to NAND?
    I've been using this one for a while: http://www61.zippyshare.com/v/F27M50NE/file.html



    Works perfectly, extract the downloaded file, you should be presented with 4 files. Plonk them all on to the root of a FAT32 formatted SD Card. Power off the Wetek, insert SD Card, keep the 'Upgrade' button pressed on the bottom of the Wetek whilst reconnecting the power cable. Keep the button pressed until the Android robot appears on screen and the installation should then complete without a problem