Latest Oscam-EMu for ARM7 Osmio4k request

There are 12 replies in this Thread which was already clicked 5,814 times. The last Post () by supwiddiss.

  • I just found a binary for OSCam 2.25.10-11888-803 here and have it working.
    Frankly, the color splash at the top is simply taking up too much screen area.
    Is there a version that closely resembles Mohamed's versions that is straight and to the point without all of the cake decoration?
    And also utilizes /etc/tuxbox/config/ for the confgs.
    Another thing. Why would I need icam? What is icam? Things look flooded with icam lately.


    Reason for updating from the previously used ver. 11846? Hoping for a touch more live log info for pv, bi**, etc.
    Also the other cardless emulator configs are rather sparse or nonexistent. The above mentioned schemes are usually fine.
    What others might be available that require no card or Internet connection for things like iks and the like that I can decode locally?


    I know you dev's work hard and it's greatly appreciated. Mohamed just always, usually, seemed to get it right. My b-day is in March so I can hold off on all of the icing at the top of the webif screen.

  • I shall read through the thread. Although I am nowhere near a programmer myself.

    In #1 I see an error that haunted me for a long time. And it's even highlighted.

    The Osmio4k is not aarch64 but in fact ARM7. I had downloaded and installed many binary-only oscam version only to find they did not work.
    A flippy-flop may have occurred last night. Either the Arm7 version that I placed in OpenVix softcam directory that I tried running in the Softcam Manager screen was in fact an aarch64 version. Or because it was a binary. And as I found from other full .ipk installs. The configs directory has a one-deeper directory.
    At any rate I put the current version in the /usr/softcams directory and started it. And yes, I did change permissions to 755.

    Becuase OpenVix is a fairly new install. I do not have the extra configs directory as was the case when previously installing other versions from .ipk .


    OSCam 2.25.10-11888-803 is what I'm using right now. The version is very hard to see. The web links in the top line are cool. But just hard to read w/o a mouse over to highlight. Mohamed where are you, buddy?

  • I'm not a programmer either, but I really recommend that thread. Now I compile my binaries for the basics, I think that's just what you want.

    To find out if a binary will work for your computer and where it will load the configuration files from the command line, type:

    #oscam -help

    That will tell you where to put your files

  • This is more what I was looking for. Easier to navigate and less screen real estate used.
    What happened to Mr. Mohamed?

    I would like to ask something. PV & B*SS is working but not listed. What's up with that?

    I think Tandberg might be working but have not checked. It used to with different emu versions. It's cardless.
    How many more cardless capabilities will oscam-emu work with? It would be nice to know to search how to get them working and how to make channels clear.
    Such as the section below highlighted in red.
    The server file includes an Internet source for keys. I added that to my existing file that also includes Mohamed's git link. Anyone know of a usa source link?
    Also. I see stream relay is enabled. I thought that stream relay was not needed due to the faster processors, etc. of newer receivers.
    So, what advantage is there to leaving it enabled? I never did understand stream relay since I never needed it.
    But it would be cool if someone could work a solution of an in-box transcoder that handled 4:2:2 content. Far fetched?
    Any input is appreciated.


    Unix Starttime: 1760164645

    Starttime: 11.10.2025 02:37:25

    Build Date: 06.10.2025 18:28:34

    Version: 2.25.10-11888-802@39998034

    Compiler: arm-vuplus4k-linux-gnueabihf-ssl-libusb-libdvbcsa-upx

    Compression: upx 4.2.4, level --best

    Box Type: osmio4k (generic)

    PID: 1246

    TempDir: /tmp/.oscam

    GBox tmp_dir: not defined using: /tmp/.oscam

    ConfigDir: /etc/tuxbox/config/

    WebifPort: 8888


    Signature: Valid - successfully verified using built-in Public Key

    Signer: OpenSSL 3.0.16 11 Feb 2025

    SHA256: 6584c28b82539d659d5b3845042ccc0e67e7e860765bec774e04c38352eefe70

    Certificate: Trusted CA Certificate

    Subject: CN=Private OSCam CA Certificate

    Issuer: CN=Private OSCam Root CA

    Version: 3

    Serial: 66a1a4f3725e4e91553295cefb95392de72774da

    Fingerprint: 5b026c41ffca5ee71a66ed957bd1f6ea91ccd2f6

    Valid from: 06.10.2025 12:20:20

    Valid to: 06.10.2026 12:20:20

    Status: Valid

    Type: 256 bit ECDSA Key


    Web interface support: yes

    LiveLog support: yes

    jQuery support intern: yes

    Compressed pages: yes

    SSL support: yes

    DVB API support: yes

    DVB API with extended CW API support: yes

    DVB API with Stream Relay support: yes

    DVB API with AZBOX support: no

    DVB API with MCA support: no

    DVB API with COOLAPI support: no

    DVB API with COOLAPI2 support: no

    DVB API with STAPI support: no

    DVB API with STAPI5 support: no

    DVB API with NEUTRINO support: no

    DVB API read-sdt charsets: yes

    Anti-cascading support: yes

    Debug mode: yes

    Monitor: yes

    Loadbalancing support: yes

    Cache exchange support: yes

    Cache exchange AIO support: yes

    CW Cycle Check support: yes

    LCD support: no

    LED support: no

    Clockfix with realtime clock: no

    IPv6 support: no

    ARM NEON (SIMD/MPE) support: no

    Binary signing support: yes

    Emulator support: yes

    Built-in SoftCam.Key: yes


    camd 3.3x: no

    camd 3.5 UDP: yes

    camd 3.5 TCP: yes

    newcamd: yes

    CCcam: yes

    CCcam share: yes

    gbox: yes

    radegast: no

    scam: no

    serial: no

    constant CW: yes

    Pandora: no

    ghttp: no

    Streamrelay: yes


    Reader support: yes


    Nagra: yes

    Nagra Merlin: yes

    Irdeto: yes

    Conax: yes

    Cryptoworks: yes

    Seca: yes

    Viaccess: yes

    NDS Videoguard: yes

    DRE Crypt: yes

    TONGFANG: yes

    Bulcrypt: yes

    Griffin: yes

    DGCrypt: yes


    cardreader_phoenix: yes

    cardreader_drecas: no

    cardreader_internal_azbox: no

    cardreader_internal_coolapi: no

    cardreader_internal_coolapi2: no

    cardreader_internal_sci: yes

    cardreader_sc8in1: no

    cardreader_mp35: no

    cardreader_smargo: yes

    cardreader_pcsc: no

    cardreader_smartreader: yes

    cardreader_db2com: no

    cardreader_stapi: no

    cardreader_stapi5: no

    cardreader_stinger: no

  • Shows which cards you can insert into the card reader


    Nothing has changed for the EMU for years
    https://github.com/oscam-emu/o…/Supported-crypto-systems

    Edited once, last by EnoSat ().

  • Eno buddy. Cards in the usa do not matter so I'm told. I'm sure you would know better. N***a went cardless in the receivers that used to use them.
    To me the emu part in oscam-emu means emulator. "Emulating" cards? Some commercial headend receivers use cards, other's don't. Or so I read.

    Another thing. Going back a few years. I asked how if oscam-emu was capable of finding keys, updating and adding new ones. Why logs (live, etc.) "could not" display them. Magically it seems one day with a newer version they started appearing.

    We have discussed this on another site. I use The Last Drakkar to log pv ecm, emm and then pvhe. And wait.

    I know that drakkar uses commands sent to dvbsnoop in the receiver. I've asked if there was another GUI (I suck at console commands) that attains the same goals or better.

    I'm asking this because some time ago you mentioned that an Enigma 2 receiver such as the OsMio series could not record a full .ts.

    Yet from what I gather, with the correct dvbsnoop command string. Perhaps it can. And what would be missing if it cannot that is needed to do the magic you come up with?

    The link you provided I've read through before. It seems written for "those in the know" and provides little for an in-depth tutorial. As is all too common with actually using any softcam, oscam. Right!.

    Going back. TVROSat.com lists the crypt schemes in the sat list. I know the 3 that work with no physical card. B**s is still crazy difficult to understand with exception of the likes of Fiji's keyfinder with cw lists. It's helped a few times. But not many to be honest.

    And somewhere here in the cobwebs there was a post on how to read live log to grab a b*ss key. My newer searches come up blank.


    So your question cards I can insert is vague. Since I do not use any. Although I do have dn and direc receivers from the roadside I've scavenged for the 2TB drives that still had cards in them. They fit n the receiver slot but could never work because it has no t8psk demod.

    On that subject. I've also asked why E2 receivers cannot display the actual satellite you're aimed at.

    Replies are 'no FTA receiver can'. Yet I have a Dreamlink T5 that will. If you tune it to lets say 125W and aim to the same transponder on another satellite, it in fact displays that satellites name. So I call b.s. on that statement. :unamused face:

    Edit:

    I see in the above oscam.version file that we have "TempDir: /tmp/.oscam".
    In the past when using this entry in oscam.server:

    [reader]

    label = mohamed

    enable = 0

    protocol = emu

    device = https://raw.githubusercontent.…/main/Enigma2/SoftCam.Key

    caid = 0500,0604,090F,0E00,1010,1801,2600,2602,2610,4AE1

    detect = cd

    ident = 0500:000000,007400,007800,021110,023800;0604:000000;090F:000000;0E00:000000;1010:000000;1801:000000,001101,002111,007301;2600:000000;2602:000000;2610:000000;4AE1:000011,000014,0000FE

    group = 5

    emmcache = 2,1,2,1

    emu_auproviders = 0604:010200;0E00:000000;1010:000000;2610:000000;4AE1:000011,000014,0000FE

    A SoftCam.keys file was created in the above quoted directory. Not now. The latest oscam-emu .ipk, when extracted shows a reader similar:

    [reader]

    label = linuxsat-support.com

    enable = 0

    protocol = emu

    device = https://raw.githubusercontent.com/smcam/s/main/SoftCam.Key

    disablecrccws_only_for = 0E00:000000

    caid = 0500,0604,090F,0E00,1010,8191,1801,2600,2602,2610,4AE1

    detect = cd

    ident = 0500:000000,007400,007800,021110,023800;0604:000000;090F:000000;0E00:000000;1010:000000;8191:000000;1801:000000,001101,002111,007301;2600:000000;2602:000000;2610:000000;4AE1:000011,000014,0000FE

    group = 1

    emmcache = 2,1,2,1

    emu_auproviders = 0604:010200;0E00:000000;1010:000000;8191:000000;2610:000000;4AE1:000011,000014,0000FE


    The whole intention (for me) using it was to grab the latest AFN keys. When adding keys to the file in the regular config directory. I need to restart oscam in the webif for them to work. I do not remember when I used Mohamed's git link if I needed to actually restart oscam.
    But now. Using and activating either or both readers does not show a SoftCam.keys file in the /tmp/.oscam directory
    .
    I can c/p the link(s) in a browser and see the keys. So, what gives?
    Are all of the entries in caid, ident, emu_auproviders needed? The most Eastern satellite I can receive is 30W....IF I'm really, really lucky. Else 34.5W is my limit.
    CAID I 'kind of get". Because I can look up a caid table of the different crypts. 0E00, 2600, 2602 is clear. Again, Streamboard just isn't that informative to me.
    Nor is all of that crap in emu_auproviders and ident. Jesus!



  • The red text shows which plastic cards (SmardCard) can be used in oscam, not that you must have them.

    Yes, providers are gradually switching to cardless systems.

    Currently, EMU can only be used for the old PowerVu (CAID-0E00 wihout new nano), old BISS (CAID-2600), and old Tandberg (CAID-1010) - EMU no longer exists for new versions.
    Oscam-EMU automatically updates PowerVU and Tandberg if you have the correct keys in SoftCam.Key.


    If there is also a thread with the correct data in the E2 in TS, you can see (Orb Pos) it in the menu (dependent on the team, whether they have incorporated this option into the image) or in the terminal.

    screenshot_20251012105008.jpg

    But we've already strayed from the topic.

    capture_010_12102025_112054.png

    1_0_19_66_65_12_5A0000_0_0_0_20251012105720.jpg

    If you have the correct EMM keys (UA) in SoftCam.Key, you don't have to wait for ECM keys (00/01) until someone uploads them to the internet/github, since it changes approximately every hour.
    10:57 - key 00 54...
    10:57 - key 01 EC...
    11:27 - key 00 81...

    Edited 3 times, last by EnoSat ().

  • Ahh. I got the Orb Pos on a couple of tp's. So looks a little pick and choose. More playing to come!

    Umm. Where did you get the data from the code above that starts with PID: 16 (0x0010) ?
    Curious. I see the live log with Writing key file: /var/keys/SoftCam.Key.

    What is doing that? Make sense? Is it the Internet reader (Device in readers with https:// link)?

    Who is responsible for that directory? In other words why not /tmp/.ocsam ? Because in the oscam.version file I see GBox tmp_dir: not defined using: /tmp/.oscam.
    That is where Mohamed's oscam and reader used to populate keys from the git link.

  • I do not use SoftCam.Key files from HTTP for EMU reader because they are mostly outdated and inaccurate.

    The default location of the SoftCam.Key file is /var/keys or /etc/tuxbox/config,

    Code
    2025/10/14 17:52:31 2B4D8EE5 r      (emu) Key file not found in: /etc/tuxbox/config/oscam-emu
    2025/10/14 17:52:31 2B4D8EE5 r      (emu) Reading key file: /var/keys/SoftCam.Key
    2025/10/14 17:52:31 2B4D8EE5 r      (emu) Total keys in memory: W:0 V:6 N:0 I:0 F:205 G:0 O:0 P:189 T:171 A:0

    or it can be specified by the -c parameter in the startup script.

  • Well. Ran across and posted that 11888 was giving me problems. Running ver. 11868 again.
    AFN keys here and other places did-not-work with 11888. To the point that I thought something had changed. And a boat load of pv, biss went black.

    Now with 11868 installed with .ipk. AFN is updating thru the 'net. PV and biss came back.

    Crazy stuff man. Crazyyyy stuff!

    Never knew oscam could be started and parameters set in terminal or script. Anytime I tried editing the startup script ended up in disaster.

Your resource for OSCam-EMU softcam

Find configs, downloads, tutorials, and support for emulation setup, IPTV decoding, and extended protocol support. Master emulation and extended decoding with OSCam-EMU. Access dedicated support, configs, tutorials, and downloads for enhanced IPTV and service access.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!