Posts by DANNYPS4

    uploading my OSCAM confi files, the TVHeadend is a bit heavy and is taking a while to complete.


    once done I will also posted.

    This is another one, is working and DVBAPI also is found....


    this is the list of commands I use to compile for android OSCAM but does not work for my box:


    fegol can you share your method?? so we wont bother you in the future... Thanks

    2 years ago I bought the original Wetek Play as the idea to combine Android and E2 really attracted me. I ended up abandoning the box as it was too slow and too buggy compared to my e2 boxes. It seems the new gen combo boxes are now very interesting. I was looking this afternoon at the A5 combo as well as the Gemma H9S. The H9S seems to support multistream (interesting for me as I use it to watch French tv channels on 5W sat). On the other hand i read marvels about the A5 combo, that almost gives you an e2 experience on the android. Anyone compared the two boxes?

    Dinobot 4k plus is the one I would suggest, because of the 2gb of DDR4, make it faster than any of the competitors


    answering this question:


    – TVHeadend Server # 1 (ver 3.2 custom) and if I access it thru the web interface there is no option to enable or disable extended_cw_api like with the other tvheadend which is 4.1, but this one doesn´t manage the tuners.


    ok, this oscam bin doesn´t work, is not like the first one you shared, my box doesn´t recognize it and it wont start...


    this box has an apk built by the manufature, is called eON tv, this app connects to the TVheadend #1, and yes I do have VLC installed but for my other videos and stuff...

    if path to oscam is located at /system the you can try to locate tvheadend at


    • #ls -la /system

    Hope you can find the configs.

    answering this question, here is the tvheadend...



    root@u5pvr-debian:~# ls -la /system

    total 100

    drwxr-xr-x 20 root root 4096 Jan 1 1970 .

    drwxr-xr-x 24 root root 4096 Aug 23 2017 ..

    drwxr-xr-x 61 root root 4096 Jul 13 2017 app

    drwxr-xr-x 2 root root 4096 Jan 1 1970 backuprestore

    drwxr-xr-x 4 root aid_shell 4096 Aug 24 00:53 bin

    -rw-r--r-- 1 root root 4240 Aug 1 2008 build.prop

    drwxr-xr-x 11 root aid_shell 4096 Aug 24 00:53 etc

    drwxr-xr-x 2 root root 4096 Jan 1 1970 fonts

    drwxr-xr-x 2 root root 4096 Jan 1 1970 framework

    drwxr-xr-x 8 root root 12288 Jul 28 2017 lib

    drwx------ 2 root root 4096 Jan 1 1970 lost+found

    drwxr-xr-x 4 root root 4096 Jan 1 1970 media

    drwxr-xr-x 2 root root 4096 Jan 1 1970 oscam <----- oscam is here

    drwxr-xr-x 42 root root 4096 Jan 1 1970 priv-app

    drwxr-xr-x 3 root root 4096 Jan 1 1970 samba

    drwxr-xr-x 3 root root 4096 Jan 1 1970 tts

    drwxr-xr-x 2 root root 4096 Jan 1 1970 ttx

    drwxr-xr-x 5 root root 4096 Jan 1 1970 tvheadend <------tvheaded is here

    drwxr-xr-x 7 root root 4096 Jan 1 1970 usr

    drwxr-xr-x 3 root root 4096 Jan 1 1970 vendor

    drwxr-xr-x 2 root aid_shell 8192 Aug 24 00:53 xbin

    answering one question at the time, this OSCAM build is what we need, however doesn´t have the EMU reader for powervu...


    OSCAM log:

    • 2018/08/24 22:29:44 37A861D6 c (client) plain dvbapi-client granted (anonymous, au=off)
    • 2018/08/24 22:29:44 37A861D6 c (dvbapi) dvbapi channelcache loaded from /storage/sdcard/OSEbuild/OSCam/conf/oscam.ccache
    • 2018/08/24 22:29:44 37A861D6 c (dvbapi) Detected Hisilicon{1}. <-- this is a good sign




    pasteboard.co

    bear with me a bit,


    answering your questions:


    - From post (#23):

    • Need to know if my build ( any progam I make in simulation) do work inside your REAL box. ---> yes it did worked
    • Need to know if your old oscam was removed and not creating any problem. ----> yes I replaced that bin with yours.
    • Need to know if you choose an appropriate area to work our linux kernel program running under Android. I sugested /sdcard/user ---> yes, no problem with it, I like more this folder, just personal preference: OSEbuild/installation
    • Need to know if my "NOT FINISHED static oscam build" execute and finds its configs. See we do not need dbapi. I do not care about that at the moment. ----> yes 100%.



    What I need then(post (#24):

    Your oscam config folder and its location. ----> /data/oscam

    Your tvheadend location and a copy of your config. Go to webif by: ---> pending I will answer once I get home.

    what everybody I know with this box needs is the hability to be capable to build our own OSCAM bin without depending from the manufacturer, because they have turn the wheel to another direction, they moved from Android to Enigma2 now...


    so, the current OSCAM, the one we are using, they that comes with the box is old, it does have PowerVU support and other things, but for example, power is getting patch every once in a while, we have not been able to keep the same rythim as everybody with other boxes, currently OSCAM is getting patch for nagra CAK7, we are not going to be able to get that patch, because as of today, there is no way possible to create our own OSCAM.


    so, you build, the box was capable to see, but if I tune a channel, your OSCAM bin won't do anything, because there is no comunication with your bin and the tuner, the DVBAPI is the link, is the bridge between both, the tuner and the software portion which is the bin.


    so if I get DVBAPI not dectected the bin wont work at all, there is no log, there is nothing more, that's is the log, the DVBAPI i not connecting.

    yes I was able to make the box initiate the OSCAM however I get this:


    (dvbapi) dvbapi channelcache loaded from /storage/sdcard/OSEbuild/OSCam/conf/oscam.ccache

    (dvbapi) ERROR: Could not detect DVBAPI version.


    as you may know already, without DVBAPI the oscam is usesless

    probably I miss typed something, I just tried again and I´m getting this:


    root@gbquad:~# busybox --help

    BusyBox v1.27.2 (2018-05-01 10:05:01 CEST) multi-call binary.

    BusyBox is copyrighted by many authors between 1998-2015.

    Licensed under GPLv2. See source distribution for detailed

    copyright notices.


    Usage: busybox [function [arguments]...]

    or: busybox --list

    or: function [arguments]...


    BusyBox is a multi-call binary that combines many common Unix

    utilities into a single executable. Most people will create a

    link to busybox for each function they wish to use and BusyBox

    will act like whatever it was invoked as.


    Currently defined functions:

    [, [[, addgroup, adduser, ar, arp, arping, ash, awk, base64, basename, blkid, bunzip2, bzcat, cat, chattr, chgrp, chmod,

    chown, chroot, chrt, clear, cmp, cp, cttyhack, cut, date, dc, dd, delgroup, deluser, devmem, df, diff, dirname, dmesg,

    dnsdomainname, dos2unix, du, echo, egrep, eject, env, ether-wake, expr, factor, fatattr, fbset, fgrep, find, fsck,

    fstrim, fuser, getopt, getty, grep, groups, gunzip, gzip, hdparm, head, hostname, i2cdetect, i2cdump, i2cget, i2cset,

    id, ifconfig, ifdown, ifplugd, ifup, inetd, inotifyd, ionice, ip, ipneigh, kill, killall, killall5, klogd, less, link,

    ln, loadkmap, logger, logname, logread, losetup, ls, lsattr, lsof, lspci, lsusb, lzcat, md5sum, mdev, mkdir, mkfifo,

    mknod, mkswap, mktemp, more, mount, mpstat, mv, nc, netstat, nice, nl, nohup, nproc, nslookup, ntpd, od, partprobe,

    paste, patch, printf, pwd, rdev, readlink, readprofile, realpath, renice, reset, resize, rfkill, rm, rmdir, route,

    run-parts, sed, seq, setconsole, setlogcons, setserial, setsid, sh, sha1sum, sha256sum, sha3sum, sha512sum, shred, shuf,

    sleep, sort, start-stop-daemon, stat, strings, stty, sulogin, swapoff, swapon, switch_root, sync, sysctl, syslogd, tail,

    tar, taskset, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top, touch, tr, truncate, tty, tunctl, udhcpc,

    uevent, umount, uname, uniq, unix2dos, unlink, unxz, unzip, uptime, users, usleep, vi, volname, w, watch, wc, which,

    who, whoami, whois, xargs, xxd, xzcat, yes, zcat

    I get this:


    root@gbquad:~# whereis busybox

    busybox: /bin/busybox.suid /bin/busybox.nosuid /bin/busybox

    to give more tips about this box, under the hood of it you have running at the same time debian linux, tvheadend#1 for your normal tv decoding and TVheadend #2 which is usesless, it doesn do anything, and if you reboot the box and have an sdcard with E2 in it, you will be able to boot into E2, but if I wanted to use E2, I would have kept my Gigablue or any Dreambox