This seems to be the standard behaviour on these boxes. Tried to use my Vim2 as an access point but it never worked.
I2S sound still broken in 0105.
The channel switching issue came back after upgrading to 0501 then reverting to 3112. Its not an issue with the PVR client as I tried them all and its the same behaviour.
I notice that refresh rate switching ALWAYS is gone and I always had this set previously.
There’s a certain randomness to this problem but its been coming and going for me for weeks now, I can only think its a settings carry over.
Update : found reproducible behaviour. If you do your first channel selection before all start up processes have finished then channel/video switchingo locks up. If you wait for them to finish then no lock ups.
Should be fixed in tomorrow’s nightly @Shoog there was changes in the dtb for kvim2 for dual tuner support that afl1 had been working on.
0106 working well and I2S problem gone. Cheers.
Update: Sorry spoke to soon, the AVL tuner isn’t working on either S or T. The tuner’s appear on the TVH web interface but time out on tuning.
I have found 3112 to be dependable if allowed to boot full before using TVH so I am again reverting back to that until this get resolved, i will try any fixes once released.
Update : 0801 still broken, checked 8.95.7 and that is working.
Is there any kind of development for S905X2 going on in nightlies?
In short: No (EDIT: …not yet!)
I much prefer “no, not yet” … it provides a little hope for the future
I’ve edited my post.
AVL-tuner card still broken on the latest nightly.
The same here!
Aynı olan ne sevgili Erbaş?
What is same?
This post was flagged by the community and is temporarily hidden.
No log, no answer. This is the development thread for testing new features. Attach kernel and kodi log is obvious for reporting issue.
Reproduced on a clean install, so will work up some logs to show what is going on.
AVL6862 is timeng out on scans.
dmesg is showing:
[ 822.032044@7] i2c i2c-2: Load avl6862 firmware patch for DVB-T/T2 size=70044
[ 822.440535@5] i2c i2c-2: avl6862 patch ver 2.0 build 24098
[ 832.465316@5] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44108
[ 832.790555@6] i2c i2c-2: avl6862 patch ver 2.0 build 21316
[ 961.053232@5] vidioc_qbuf skip: index:31912:31911
[ 1421.813048@7] vidioc_qbuf skip: index:54946:54945
[ 1569.259506@0] i2c i2c-2: Load avl6862 firmware patch for DVB-T/T2 size=70044
[ 1569.668011@4] i2c i2c-2: avl6862 patch ver 2.0 build 24098
[ 1723.053161@7] vidioc_qbuf skip: index:70008:70007
@Shoog pls read carefully “How to report an issue you’re having with CoreELEC”. From your log I can deduce issue only with using my crystal ball.
I will have to do this in a quiet down time which may take a day or two. I did state that I would post logs when I could generate them.
Update: I saw that there were quite a few updates the the dvb support in 0115’s nightly so I upgraded my test build but still no joy with the AVL.
A few comments about the log, the channels which showed up were from the working SAT > IP tuner. I couldn’t see much referring to the AVL tuner. Do I need to select some different logging options. I tried all three dvb-modules all with the same outcome. Will not scan any dvb-T channels and always poops out with no service and times out. The AVL tuner turns up in the TVH servers tuner list. This is fairly much exactly the behaviour I was experiencing a year ago when this cards driver was misconfigured and would not scan.
So what more can I do to help track this down ?
@Shoog, sorry, but how can fix issue in kernel driver from kodi.log? Have you ever read guide for repoting CoreELEC issues? My driver update are tested on my equipment. For internal dvb driver only issue was DVB-T driver for Wetek Play2 as I have for testing WP2 with DVB-S only. In the latest updates I fixed WP2 dvb-t I also improved dvb scanning. In my testing, Kvim2 with 2x VTV board scanning complete Astra 19E2 (114 transponders, 1771 services) took < 8 min without any FAIL.
The tuner works on 8.95.7 without issue, it also works on 1231 nighley without issues. Everything after that isn’t working for me. I am now not using the DVB-S within the AVL tuner having relegated it to just DVB-T service. As i said you never specified what level of logging you required so I simply followed the guide linked to which only describes Kodi.log so that is why I came back to ask what specific logging you wanted. When I get a quiet moment I will enable kernel logging and post again.
0117 still not working on dvb-T.