It needs to be solved in the community build you are using.
So, I opened a new thread for this topic as per kszaq 's and your request.
It needs to be solved in the community build you are using.
So, I opened a new thread for this topic as per kszaq 's and your request.
This is related to this thread and I opened this thread on @kszaq 's request. Other than in the aforementioned post, I believe the trouble is with the Sundtek driver and not with TvHeadend, since VDR can also not tune to a channel when using the (high quality and expensive) Sundtek stick, while both TvHeadend and VDR work just fine with the (cheap and ok quality) XBOX ONE Digital tuner.
I would like to mention that I have been using these Sundtek Sticks for almost 8 years now. They have been in heavy use during that time (often attached to a 24/7 headless VDR on a Dockstar and now a cubietruck). So, I would really love to be able to use them with the new toy - the china boxes.
To make this (somewhat) reproducible, here is what I did (on November 29th 2017 on a S905X 1GB/8GB EgoIggo
I then disabled VDR (backend and client) and also TvHeadend server in order to be able to copy over the respective configurations so as to be able to use them right away. Of course, I enabled debug logging in Kodi.
Then, I checked whether the Sundtek sticks were found (locally and over the network):
Android-TV:~ # mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Pro (USB 2.0)] DVB-C, DVB-T, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
[INFO]:
STATUS: STANDBY
[BUS]:
ID: 1-1
[SERIAL]:
ID: 0110126045427
[DVB-C,DVB-T]:
FRONTEND: /dev/dvb/adapter0/frontend0
DVR: /dev/dvb/adapter0/dvr0
DMX: /dev/dvb/adapter0/demux0
[ANALOG-TV]:
VIDEO0: /dev/video11
VBI0: /dev/vbi0
[FM-RADIO]:
RADIO0: /dev/radio0
RDS: /dev/rds0
[REMOTECONTROL]:
INPUT0: /dev/mediainput0
[OSS]:
OSS0: /dev/dsp0
Android-TV:~ # mediaclient --scan-network
Scanning network for IPTV media servers
------------------------------------------------------------------------------
IP address | ID | devicename | Users | Capabilities | Serial
------------------------------------------------------------------------------
xxx.xxx.xxx.xxx | 0 | MediaTV Digital Home III (EU) | 0 | DVB-T, DVB-T2, DVB-C | U150522194056
xxx.xxx.xxx.xxx | 1 | Sundtek MediaTV Digital Home (USB 2.0) | 0 | DVB-T, DVB-C | 0101230184035
xxx.xxx.xxx.xxx | 2 | Sundtek MediaTV Digital Home (USB 2.0) | 0 | DVB-T, DVB-C | U110726102636
xxx.xxx.xxx.xxx | 0 | Sundtek MediaTV Pro (USB 2.0) | 0 | DVB-T, DVB-C | 0110126045451
- 4 IPTV server found -------------------------------------------------------
Android-TV:~ #
Display More
So, the sticks were visible the way they should be.
After copying over the configuration, I re-enabled TvHeadend server, headed over to the Web-If and attached the DVB-adapter to the DVB-C network and enabled it. Here, it can already be seen, that something is not quite right, because TvHeadend only sees the DVB-C part of the tuner, not the DVB-T part (on the left you can see the situation on the Wetek Play (as it should be) and to the left the situation on an AML S905X):
Then, I turned the box off, power-cycled and turned it back on. Then, I went to TV and tried to watch the first channel (not encrypted). This gave me a message form the TvHeadend HTSP Client saying "No free adapter available". I then stopped TvHeadend server via the command line.
This lead to the following logs: dmesg | paste and Kodi log: log-2017-11-29-12.22.24.zip
Then, in for TvHeadend server, I activated TRACE Debug setting Debug Value #1 to "all" first and to "dvb" second and tried watching the channel again. This gave the following two debug.txt files: tvheadend_debug.zip
I would like to mention, that
As GDPR-1 mentioned in the related thread I linked above, all this must be due to the 64bit kernel mixed with the 32bit user space.
Anything else I can do like provide similar info for devices where the Sundtek sticks work (Rpi3, Wetek Play) or test something specific on the china box, please let me know.
As kszaq mentioned elsewhere, it is back up again. I tried it as well - works
Hi,
the one for the ANTSIR Box is actually already available in this post over at kodinerds. That is where I got it from (copy & paste) in the first place, but meanwhile I also have the original from my box. It is in the attachment. Also, there is a file remote_gen.xml, which will allow you to use the button with the browser symbol down left for play/pause and the delete button down right for stop (which you otherwise have to do via OK and choosing the corresponding option).
You do realize that remote.conf needs to go to /flash or, if you want to put it on the SD card/USB-Stick directly, on the LIBRELEC partition along with the device tree and such (I believe, you can also put it in /etc instead). The file remote_gen.xml has been generated using the Keymap Editor addon and needs to go in /storage/.kodi/userdata/keymaps.
Hope this will help!
I also bought a WeChip V7 and have the same problem. Original remote.conf doesn't work at all.
What does the remote look like? I have two different ones, one for an EgoIggo and one for an ANTSIR box, which also worked for an ABOX MAX (you can already tell from the pictures that they are the same).
So, if yours looks like one of those, I'll be happy to provide the file.
Thank you very much, kszaq !
Now, the reason I was anxious to test was the problem with Sundtek-Sticks described here. Are you aware of this? Because I have the exact same issue with my Sundtek Media TV Home/Pro Sticks, which is quite annoying. Fortunately, the cheap XBOX ONE tuner works with your build, so I can test with that, but it has nowhere near the quality of the Sundteks. And, since those are "sunk cost", I would very much like to be able to use them with the China-Boxes ...
If you want, we can take this up further in the linked thread and I would be happy to provide any information you might want.
Please wait a bit, addon site is being moved to a different hosting.
Is there an ETA?
Also here, anxious to try something out, but waiting for the repo to come back up ...
kszaq , ok, thanks and the other one which works says mmcblk0: emmc:0001 NCard 7.21 GiB Then, how do I find out what chip this actually is? Is there, maybe, some udevadm command like for the Wifi chip?
I found the NAND chip. The 2 boxes with problems have a different chip.
OK: Samsung KLM8G1WEPD-B031
NOT OK: EUDAR EMB1CTTCL1F008
ryv , is there a way to find out the chip without opening up the box?
By the way: the link in your thread on reporting bugs to the HowTo: Provide Logfiles is broken. The link just before is the correct one.
Here we go: Output of dmesg | paste
Looks like it is running into timeouts resulting in a read partition error for the EMMC
And, for comparison, the Output of dmesg | paste of the EgoIggo S95X I got today, booted with the exact same card used on the ANTSIR-device yesterday. Here, /dev/system does exist
Hi kszaq,
thanks for the build, but no dice: same as before, no /dev/system
It needs to be solved in the community build you are using.
Ok, I understand that. I am using kszaq 's build and you said somewhere above that the two of you try to keep in sync in this respect ...
Hi guys,
any news on this front? I seem to have such a box (which is fine with SD card, though), but seems to have such a EUDAR NAND as well ...
Using device tree with _nand suffix does not help.
Cheers,
chessplayer
Thanks for the quick reply. I guess that means that the S905W box which exhibits the problem will really have to go back (a pity, since at 28€ for a 2/16 box, there was so much hope ...). Or should I keep it just for the heck of it ... anyway, that is for me to decide. Looking forward to all your great upcoming releases
I'm glad that my builds are working on S905W but I don't support running my builds on S905W.
Thanks for getting back to me on this. It does seem, however, that in some cases we must wait to be able to force RGB output again, as discussed here. Do you know whether that is going to be the case again any time soon?
Cheers,
chessplayer