Oscam 11537 emu 797 STAPI

oscam-1.20_svn11537-797

[dvbapi] Reworked "ca_pmt_cmd_id" skipping logic According to the spec (https://www.dvb.org/resources/public/standards/En50221.V1.pdf), the "ca_pmt_cmd_id" value shall be present inside the ES info loop. Unfortunately, each dvbapi client does each own thing. The only reliable way to detect when this info is present in the CA PMT is to actually check its value, like it was done in the old code. Most boxes always send the typical value of 0x01 (ok_descrambling) and the above check works fine because there is no descriptor_tag 0x01 to get confused with. On the contrary, for enigma2, values like 0x03 (query), 0x04 (not_selected) are possible (not yet, but soon). Skipping these higher values the same way will not work, because descriptors with such tags can exist, so a different check is implemented for enigma2. In practice, this commit fixes the VDR dvbapi plugin, as well as the enigma2 boxes with wrong dvbapi boxtype setting ("none" instead on the correct "dreambox" - the setting is irrelevant now, but will make a difference in the future, so make sure you set it correctly). /trunk/module-dvbapi.c

Android 7 box
config path: /mnt/plugin/oscam
stapi 
stapi & upx

config path : /mnt/plugin/config
stapi
stapi & upx

config path : /var/tuxbox/config
Here

Android 6 box
config path : /var/tuxbox/config
Here

Oscam 11535 emu 797 STAPI

updates
         "[dvbapi] Tryfix for various boxes not working after 11533

It seems there are more retarded boxes out there that set the ca_pmt_cmd_id to 0 instead of a proper value.

/trunk/module-dvbapi.c"

oscam emu for stapi based android 7 box
HERE OR HERE

---------------------------------------------------------------------------------------------