Usually its bad/fake replies from a card server.
Can be.
Usually its bad/fake replies from a card server.
Can be.
Yeah, I've read all the forums about it, but unfortunately I cannot tell where the problem lies :(
Anyway, thanks for your help :)
Looks okay to me as well, I don't know what's the problem..
2022-10-31 21:24:21.034 TS: Astra 19.2E/11992.5H/Sky Atlantic HD: AC3 @ #1284: Invalid start code 56:ee:9e
2022-10-31 21:24:30.418 TS: Astra 19.2E/11992.5H/Sky Atlantic HD: H264 @ #1279: Invalid start code 93:d0:2c
2022-10-31 21:24:30.762 TS: Astra 19.2E/11992.5H/Sky Atlantic HD: AC3 @ #1283: Invalid start code 0a:38:e0
Invalid start codes have something to do with odd/even errors. Not really sure.
Once the 2 patches are applied (tvh and libdvb) the vanilla OSCAM will open icam channels.
No need for stream relay or any of that stuff. It will work just like before they added icam.
Are you using dvbapi?
Yes, and oscam is up to date, as I build it as well from sources. I saw another post where it says to filter out teletext streams. Did that as well, but no change.
For corelec you have a complete build system:
coreelec:build_ce [CoreELEC Wiki]
You will have to find where are the config files for tvheadend and ajust them according to what is in the configure scripts here.
This script is for debian based standalone systems.
I've put together a build script, which should include everything from the posts.
Adjust the work dir accordingly, and also if you do not wish to install it to /usr/local/bin, then the =prefix as well.
Now here's my question:
I've succesfully built the patched tvheadend, but it's still dark on all channels. Is there anything else to do ? I read about this icam, I saw that some people use stream server, is it something like this necessary ?
I'm getting invalid start code errors in the tvheadend log, just like before, and of course the dvbapi shows that the key was received ok.
Hello,
I've recently purchased this receiver to mount it in the weekend house in a quite remote location.
As there was no internet, I've plugged in an Huaweii 3g stick.
As software, I've used Amiko HD8150 2.0.65 emu and recently I've updated to AMIKO HD8150 2.2.14 emu.
Suprisingly the 3g support was quite ok, it supports several huaweii and ZTE modems.
With the 2.0.65, I've also managed to get it autoconnect.
After updating to the latest 2.2.14, after bootup, or after plugging in the 3g stick, the stick is recognized (3g plug-in appears on the display), but it won't automatically connect.
After manually connecting from the menu, the 3g works ok.
I've tried flashing back the older 2.0.65 FW, but still the 3g won't connect. That is very strange. So if somebody has a clue what's preventing to autoconnect, I would greatly appreciate it.
Oh, btw, it also has newcamd/mgcamd and cccam client support.