[Help Needed] Request for compiling latest Oscam-Emu Stapi for legacy Android 5.1

There are 23 replies in this Thread which was already clicked 2,683 times. The last Post () by tracefm.

  • Hello dear developers and experts,


    I am facing a compatibility issue and urgently need your help.

    I am trying to run the LATEST version of Oscam-Emu Stapi on an older device, but all recent binaries fail to install/run due to API mismatch.


    Device Info:

    - Model: Next 10000 UHD

    - CPU: Amlogic S905 (ARM Cortex-A53)

    - OS: Android 5.1.1 (API Level 22)


    The Problem:

    Standard binaries are compiled with newer NDKs targeting API 24+, which causes "Parse Error" or execution failure on my Android 5.1 system.


    My Request:

    Could someone please do me a favor and cross-compile the latest SVN using a legacy toolchain (like NDK r10e/r11c) that supports API 21/22?


    I lack the environment to do this myself and would be very grateful for a working binary.


    Thank you very much for your time and support!

  • master G

    Approved the thread.
  • oscam-2.25.11-11906-802@a93e1a0c-armv7a-unknown-linux-android22-stapi-ssl-libcurl-libusb-libdvbcsa-upx


    oscam-2.25.11-11906-802@a93e1a0c-armv7a-unknown-linux-android22-ssl-libcurl-libusb-libdvbcsa-upx



    config direct: /data/plugin/etc

  • Hi again dear Shahrooz, and thank you so much for your support.


    I have tested the binary you provided, but unfortunately, I encountered some issues:


    1. When I replaced the binary inside my original receiver app (cam.apk), Oscam started, and I could connect to the WebIF. However, the receiver became very laggy/unstable (freezing), and although Cccam connected to the server, the channels did not open (black screen).


    2. I also tried to install the APK file you provided, but it failed to install on my device with an "App not installed" error (I suspect this is due to the signature scheme not being compatible with Android 5.1).


    **Could you please provide the UNSIGNED version of your APK?**

    This way, I can try to sign it manually with "ZipSigner" (using testkey) on my device to see if it installs and works better than the manual binary replacement.


    I am also attaching my original working APK (the old version that works on my device). Could you please kindly check it and, if possible, optimize/compile the new binary based on this specific architecture/lib structure?


    Here is my original cam.apk:

    CAM-ME001_IKS-20180319-1647_v2.1.2.01.cfc6fdd.apk


    Thank you very much for your time and help.

  • Dear Shahrooz,


    I wanted to give you an update. The version you provided is working perfectly!

    Thank you so much for your time and effort. It had been a long time since we received any updates for this device, and we were losing access to channels via SoftCam day by day. You really saved us!


    However, I would like to share some important tips for other users who want to use this file on Next 10000 UHD:


    1. **Warning about WebIF:** Do NOT use the Web Interface extensively. If you log in, stick to the main status page only. Do not try to navigate to other tabs or modify configuration/settings via WebIF, as this causes the receiver to lag severely and freeze, forcing a hard reboot.


    2. **Adding CCCam:** It is highly recommended to add your subscription by importing a `cam.cfg` file (NOT `cccam.cfg`) directly through the app menu on the receiver itself, rather than using the Web Interface.


    3. **Display Issue:** Please note that after importing the file, the cccam will be active and working, but it might NOT show up visibly in the app's panel. You can only verify that it is connected by checking the WebIF status page (again, without navigating further).


    I have attached a sample `cam.cfg` file below for anyone who needs it.


    Thanks again for your great work!


    cam.cfg

  • ‎‏‎ ...

    Hello, if I have the chance, I will compile a new version of OSCAM with a light webif and the ability to read the cam.cfg file.

  • Hi dear Shahrooz,


    I noticed something that I think prevents the receiver's original Oscam from causing freezes and allows the WebIF page to load smoothly. It seems I only have access to the following three pages, and the rest do not open at all:

    - Status

    - Live Log

    - Readers


    I have also taken screenshots of the "Status" and "Readers" pages from both the receiver's original Oscam and your Oscam for comparison.


    What is noteworthy in your new Oscam is:

    - CCCam does not connect (it stays in OFF state).

    - In the "Clients" section, under the "LB Value/Readers" column, CCCam is not recognized.

    - Also, in the "Readers" tab, no CCCam exists at all. Even when I add it manually, it still remains OFFLINE.


    Thanks again.

  • What is the config directory for cam.cfg and other files?

  • On my receiver the Oscam configs are not stored in a normal filesystem folder like /data/plugin/etc.


    In my case all config files (cam.cfg, oscam.conf, oscam.server, etc.) are inside the APK itself under:


    cam.apk -> assets/cfg/


    So the internal config directory for Oscam on this Next 10000 app is: assets/cfg

  • ‎‏‎ ...

    replace it

    you cam config cccam from cam.cfg by this format


    [server]
    C: host port user pass


    or oscam.server by this format


    [reader]

    label = server1

    protocol = cccam

    device = host,port

    user = user

    password = pass

    group = 1

    disablecrccws = 1

    cccversion = 2.3.2

    ccckeepalive = 1

    cccreshare = 2


    try it and send me feedback

  • here is my feedback after testing the new file:


    There is no more freezing or lag at all, everything runs very smoothly now.


    CCCam can be added with both methods you mentioned:

    - Method 1 (cam.cfg): CCCam connects, but the reader is not shown/recognized in the “Readers” section.

    - Method 2 (oscam.server): CCCam connects AND the reader appears in the “Readers” tab with ONLINE status. (Previously this was not possible.)


    The only remaining issue is that it still cannot decrypt/open the TV channels. I will post the log so it might help to find the cause.

  • Also, in the “Clients and Cccam” section the column **SRVID:CAID@PROVID** show `0000:0000@000000` and no channels are detected at all.


    If needed, I can also provide the TV application (APK) that works together with this cam so you can check it.

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!