I have used Nexus ne on Vontar X4 and it worked. Tested on DTS-HD MA 5.1 THX Deep Note Genesis from https://kodi.wiki/view/Samples .
After upgrade to Omega, no more sound and video plays as a slideshow. But it plays ok, when switching audio to DD. I have tried clean install on SD on Hako Pro (generic s905y4) with the same result.
I haven’t seen any complains about DTS-HD MA, maybe I have configured something wrong? On my Vontar I downgraded to Nexus and it seems to work again.
You should check your Audio settings by going to the KODI settings page (hit the gearwheel icon middle of three top left icons) and under System check the audio settings to see whether or not Passthrough is enabled. Most modern TVs and AVRs accept the passthrough digital audio stream and decode it giving top quality sound (well from an AVR as TV speaker sound is never top quality).
So I think you probably have passthrough enabled but DTS-HD MA is not a recognised mode by your TV or AVR, especially likely if they are fairly old. So try disabling passthrough and if that now works try with passthrough enabled again by disable DTS-HD MA as other passthrough digital audio modes may well work with your TV/AVR.
If you are only using audio from your TV speakers then I see little point in having passthrough audio enabled. So just disable it and let your streaming box send the decoded analogue audio to your TV as it will make little difference to to audio quality from TV speakers.
So has this BT pairing fix been incorporated into the latest nightly builds yet ?? If so I will test it out.
Yes would be nice to not have to re-pair the BT remote after coming back form crap Android. Maybe a simple little addon to invoke the pairing routine would be useful without having to go to the CoreELEC BT settings which is daunting for those not techie.
You don’t need to go into CE settings to pair again after comming from Android: just press whatever button combination is needed on your remote control and remote will be paired again and working.
Thanks again vpeter, one never stops learning new tricks. I never knew that and when I tried before your fix that would not work for me, not tried it since as rarely go into Andorid. Is that with this fix we applied through ssh or even true before this fix. Is it yet included in the latest nightlies ?? If not yet so please kindly let me know when it is so I can help test it out without reverting to ssh command lines ??
Correct permisions when coming from Android is included already in few nightlies. SO you only need to press pairing buttons on remote when CE starts. And remote should start working.
Sorry to report that no it does not work. After coming back from Android I cannot re-pair without going into the CE BT screen and manually pairing and then it no longer auto pairs after a reboot anymore needing a fresh pairing via the BT config screen after every CE reboot . This is with a fresh install of todays nightly build of 21 -ne on an Sandisk Extreme 64GB SD card. With the new install it does reboot fine into BT pairing until I first run Android then it is the same as before needs manually pairing on each boot into CE.
I did again then run the ssh command “find /storage -maxdepth 1 -type d ! -user root -exec chown -R root:root {} ;” and as before that fixed it and now auto pairs on each CE reboot again unless I boot into Android and back when it need the ssh command running again. So it seems this command does not auto run with booting into the latest CE nightly dated 5th May. So sorry to say that something is not working as you intended it seems.
Also a new problem with the latest nightlies is that with the Simple Client from the EPG screen trying to run a catchup program now just causes a freeze and reboot ?? So seems a bug reported here. But hey that is what the nightlies are for of course.
Let me know if you need any log files vpeter as any help I can give I will do to help with these problems
This is the commit vpeter added, but it’s slightly different to your command.
It just fixes for dir owner user “1023”, and sets back to root, while your command sets any user “not root” back to root.
Maybe you can check the dir owner in your usecase, to confirm it is different than root or 1023.
That’s why I hesitated to include this fix because I can’t test it. My android devices doesn’t change this folder.
From what I know 1023 is Android user for networking access. Maybe there are also some other cases and should test for root user. But again I don’t know if this can break some other user config.
This service file can be copied to /storage/.config/system.d/ and change command there. After reboot it will be used.
Understand. Well the ssh command and logged in to root did fix it as I confirmed and it still does.
Do you think this could be the cause of the catchup not working now on the Simpler Client EPG ?? Sounds unlikely and probably another unrelated issue with Simple Client???
So do I just make a file with that ssh command line and pop it in in that storage/.config folder/system.d folder?? If so what do I name that file? Sorry but I am not familiar with that and no expert on KODI commands or python but know a little bit about it and happy to learn more. Anyway let me know if you have a fixed nightly build ready so if you want I can easily test it for you before release.
BTW what Android device do you use ?? I rather like the uGoos X4Q Pro or Extra box and they are at a reasonable price.
Ahh rho-bot I missed this post before replying to vpeter. Sorry but how do I do that?? As I said I run that command line in ssh logged in as root not user which I thought was correct???
I did make a change in Kodi to get catchup at least for me one one other user working. But maybe that broke someething else? What issue exactly you have?
When I try to play any TV program that has already finished (ie catchup) it tries to load it with the circling wheel and then that wheel stop s and the box freezes before soft rebooting. This never happened before I installed this latest nightly but the last nightly I was using was back about a week ago sometime at the end of April as I had forgotten to change the update setting to auto from manual.
I do have a bespoke KODI addon for IPTV written by a friend of mine some 2 years ago and that works fine for live and catchup TV but does not use Simple Client although it does initially set SC up when first installed. It has always worked flawlessly after some initial debugging the code, and for Simple Client too though SC catchup only goes back 24 hours whereas the addon goes back for 5 to 7 days depending on the service you are using…
Interesting but I did notice earlier today before I found the problem with IPTV Simple Client catchup an auto update for the InputStream Adaptive addon. I just checked and the latest version form the CoreELEC repo is now 21.4.6.1 Not sure if this is relevant but it is mentioned in your commit.
Sorry not sure what you mean by ls -l /storage?? I thought ls was a list command ?? I know where the .config folder is with File Manager and can easily pop a file in any folder there without using ssh, Just want to know what file name and what content to put in the service file ???
Just run that ls ssh command and this is the result. So does this look like maybe 1024 not 1023 is the user ???
CoreELEC:~ # ls -l /storage
total 23
drwxr-xr-x 2 root root 1024 May 5 18:50 backup
drwxr-xr-x 2 root root 1024 May 5 18:50 downloads
drwxr-xr-x 2 root root 1024 May 5 18:50 emulators
drwxr-xr-x 2 root root 1024 May 5 18:50 logfiles
drwx------ 2 root root 12288 May 5 06:17 lost+found
drwxr-xr-x 2 root root 1024 May 5 18:50 music
drwxr-xr-x 4 root root 1024 May 5 18:50 picons
drwxr-xr-x 2 root root 1024 May 5 18:50 pictures
drwxr-xr-x 2 root root 1024 May 5 18:50 recordings
drwxr-xr-x 2 root root 1024 May 5 18:50 screenshots
drwxr-xr-x 2 root root 1024 May 5 18:50 tvshows
drwxr-xr-x 2 root root 1024 May 5 18:50 videos
CoreELEC:~ #
Thanks for your answer. I have checked all again, pass-through is working for me on Nexus. I have updated Vontar X4 again and this time is working on Omega too. No idea what went wrong previous time.
Ahh yes should have realised that as 1KB normal minimum file allocation size, duh. Okay will try that command later today and let you know the results.
Okay vpeter here is the result after booting in Android and back into CE. Of course the BT remote did not auto pair now as usual if I put it into pairing mode from the CE home screen. However if I using the IR part of the remote go into the CE BT config screen whilst leaving the remote in pairing mode it does automatically pop up the remote device and auto pair it. But a reboot still needs another manual pairing in the same way. If it auto paired from the CE home screen as you say it should it would be fine and of course. Hope this helps.
BTW I do have a Rii i8 handheld wireless keyboard permanently attached via its dedicated USB dongle. But do not think that would have any affect on the default BT remote.
Impressive dedication you guys have to CoreELEC, so very much appreciated.
CoreELEC:~ # ls -al /storage
total 31
drwxrwxrwx 20 1023 1023 1024 May 5 19:24 .
drwxr-xr-x 13 root root 245 May 5 06:16 ..
-rw------- 1 1023 1023 201 May 5 23:43 .bash_history
drwxr-xr-x 16 1023 1023 1024 May 5 18:54 .cache
drwxr-xr-x 18 root root 1024 May 6 18:47 .config
drwxr-xr-x 10 1023 1023 1024 May 5 18:54 .kodi
drwxr-xr-x 2 1023 1023 1024 May 5 18:54 .restore
drwx------ 2 root root 1024 May 5 18:50 .ssh
drwxr-xr-x 2 root root 1024 May 5 18:50 .update
drwxr-xr-x 2 root root 1024 May 5 18:50 backup
drwxr-xr-x 2 root root 1024 May 5 18:50 downloads
drwxr-xr-x 2 root root 1024 May 5 18:50 emulators
drwxr-xr-x 2 root root 1024 May 5 18:50 logfiles
drwx------ 2 1023 1023 12288 May 5 06:17 lost+found
drwxr-xr-x 2 root root 1024 May 5 18:50 music
drwxr-xr-x 4 1023 1023 1024 May 5 18:50 picons
drwxr-xr-x 2 root root 1024 May 5 18:50 pictures
drwxr-xr-x 2 root root 1024 May 5 18:50 recordings
drwxr-xr-x 2 root root 1024 May 5 18:50 screenshots
drwxr-xr-x 2 root root 1024 May 5 18:50 tvshows
drwxr-xr-x 2 root root 1024 May 5 18:50 videos
CoreELEC:~ #