Display More
Hello.one of my "old" mx2/8276's recently died and so I replaced it with a 905 device - MXQ PRO 4K.
I've tried a number of your libreelec builds with a few different dtb.img's, all work, but all of them seem to be missing the SPDIF option in the audio. my older receiver doesn't have HDMI, only spdif...so I get silence.The audio works fine over spdif with the native android/kodi installation...so I know the hardware itself is fine.
I checked the openelec/kodi my other mx2/8276 and for that device it lists SPDIF in the audio output option.
in the MXQ PRO 4K, depending on which dtb.img I use, I seem to get "bluetooth audio", ALSA-something-HDMI, or PCM...but no SPDIF options.
Is this something I can enable myself ? maybe a driver is missing or a config file ? - I have a little general linux knowledge, and I'm comfortable with SSH, but I'm not really sure where to start looking for this.
I guess my other option is a HDMI-->SPDIF break out box, I know I have one somewhere, but I would prefer to use the native spdif on the amlogic box, as I did with my MX2.
Sorry, it says 'kszaq wrote....' in my post..which is not true. not sure how that got there, I dont know what I'm doing with these forums.
[8.0.2e] LibreELEC 8.0 for S905/S905X
-
kszaq -
October 28, 2016 at 10:45 PM -
Closed -
Thread is Unresolved
-
-
Did you try ALSA, AML M8L AUDIO, HDMI? Audio should be output from SPDIF at the same time with HDMI.
-
I can't find the option to boost the central audio channel. Where is it?
-
I can't find the option to boost the central audio channel. Where is it?Removed in Krypton.
-
Hello everybody, I've got the TANIX TX95 (this one) box and I'm unable to boot into LibreElec on sdcard (and using a toothpick).I've got two other boxes (one S905 and one S905X) with which I don't face any problem.
For this one, not any dtb.img is working, I tried all the S905X ones, mainly this one: glx_p212_2G.dtb but none of them make the device boot (I'm stuck on the boot screen).
Is this related to the fact that it has 1G Lan so probably a dedicated chip?
Can I give you anything to create a working dtb.img?
Thank you in advance!
I'm quoting myself just in case some people are facing the same issue as I did.
I found a workaround to get my TX95 box booting into LibreElec (must have been something like a broken recovery into original rom): Just install a custom firmware like this one using USB_Burning_Tool, it will then give you the ability to boot into LibreElec using usual toothpick method.
-
Silly question, if I'm on 7.0.3.012g do i need to upgrade the device tree? I recall reading 8.0 still uses the old 7.0.3.012 device tree
-
I have a few bluetooth controllers. I pair in LibreElec, I go into Jokerzbox retroarch port and I can not even get the controller to register, Does anyone have any ideas on what I could be missing or doing wrong? I have no issues with connecting them on PC, Android, OSX etc. Any ideas would be great. Thank you all very much
[hr]
Same with Mini USB keyboards, plug usb in, mouse will work but keyboard will not. Thanks again for the awesome work. I should state I am using the latest Krypton 8.0.0c I think it was no sensors -
How is everyone's GUI smoothness in 8.0.0c? Better or no change than in previous builds?I believe to feel c is smoother in GUI than a. But I have not much practice to come to statistical thruth. But feeling also counts.
[hr]
Silly question, if I'm on 7.0.3.012g do i need to upgrade the device tree? I recall reading 8.0 still uses the old 7.0.3.012 device treeI successfully use old device 7.0.3 trees. In fact I am not sure there are newer ones (for my devices).
[hr]
Try replacing addons URL to something like this: options#L129 and use WP2.Thanks for the hint! I had not spotted this options ADDON_SERVER_URL key.
[hr]
[...]
I like 8.0.0 a lot, but there is one reason I stay with 7.0.3:
The deRedactie.be video TV streaming add-on, for some reason, works in 7.0.3 but not in 8.0.0
I'll contact developer of that add-on.
Thanks kszaq for keeping us all happy.
deRedactie.be developer provided workaround fix for his add-on (to be found in github).
I'll switch from 7.0.3 to 8.0.0 ! -
Yes, yes and yes. And yes.
If you're jumping from 7 to 8 I'd run a backup first, otherwise you can't easily revert - but that's your call.
I'd also switch to confluence - if you're not already using it - before updating.Thanks for the info, I already use Confluence and like it. When updating within the Update folder, is that for my SD card or internal NAND? I run LE from my SD card...
Thanks again
-
Try replacing addons URL to something like this: options#L129 and use WP2.
I may be missing something but if I defineCodeADDON_PATH="$ADDON_VERSION/WeTek_Play_2/$TARGET_ARCH" ADDON_URL="$ADDON_SERVER_URL/$ADDON_PATH"
I still end up in kszaq.libreelec.tv since
Unfortunately I do not find an alternative Addon server URL ...Code$ pwd kszaq/LibreELEC.tv $ find projects/ -type f | xargs grep ADDON_SERVER_URL projects/S905/options: ADDON_SERVER_URL="http://kszaq.libreelec.tv/addons" projects/S905/options: ADDON_URL="$ADDON_SERVER_URL/$ADDON_PATH" projects/S805/options: ADDON_SERVER_URL="http://kszaq.libreelec.tv/addons" projects/S805/options: ADDON_URL="$ADDON_SERVER_URL/$ADDON_PATH" projects/Virtual/options: ADDON_URL="$ADDON_SERVER_URL/$ADDON_PATH"
-
After upgrading from 7.03.012x to 8.0.0c * it just hung at the libreElec screen after the reboot
*This was running on an SD card and simply put the img.gz file in the update folder and reboot
No need to even include a device tree for this update.I suspected the problem was similar to when I updated my Linux system from 16.1 to 17 and employed the same fix as indicated here
[ubuntu] Kodi fails to startSo a heads-up for anyone who finds the same situation, follow instruction in that link above
(just ssh into box and delete that file - I actually use cyberduck which is an awesome utility with very simple 'explorer' type navigation - I highly recommend it) -
I just finished upgrading to Krypton and all my DTS files now show Dolby Digital on my TV and AVR, on Jarvis it would show DTS instead. Also the number of channels has to be set to 2.0 for it to show Dolby Digital, if i set it to 5.1 (which is what I have) i only get PCM 2.0 audio.
Yes passthrough is enabled and so are the formats my AVR supports.
EDIT: Turns out you can no longer have "Sync to Display" enabled for passthrough.
-
I just finished upgrading to Krypton and all my DTS files now show Dolby Digital on my TV and AVR, on Jarvis it would show DTS instead. Also the number of channels has to be set to 2.0 for it to show Dolby Digital, if i set it to 5.1 (which is what I have) i only get PCM 2.0 audio.Yes passthrough is enabled and so are the formats my AVR supports.
Sorry to say I have a different experience. Yes, 'Number of Channels' is always set to 2.0, this was it since Kodi running under Android and I didn't bother to change it.
I just pulled couple of disk drives and tested several videos with different audio format. For DTS, it shows DTS on my AVR; for DTS MA (or DTS HD), it shows DTS HD and for TrueHD, it shows DD (Dolby Digital) HD on my AVR. Therefore I believe there's no problem with audio passthrough.
BTW, I'm testing with M18 (S905, 2G/16G), Pioneer VSX-321 AVR using HDMI connection.
-
How is everyone's GUI smoothness in 8.0.0c? Better or no change than in previous builds?
I've seen no speedup, sorry. I use aeon nox anyway. Mx64 box. -
Update to 8.0.0c worked nicely as all updates before. Only thing is, the MAC of my ethernet controller changed!?
Thx for a great piece of software for that tiny little box
-
It changed and now should be a proper one.
-
How is everyone's GUI smoothness in 8.0.0c? Better or no change than in previous builds?
For me 8.0.0.c it's smoother then "a" or "b". Keep experimenting on this layer, pls. Still slower then GUI on Jarvis, but definitely an visible improvement on the last iteration.
On topic: is it only me or could be a known issue - the colours are a little bit darker compare to Jarvis (same box, same tv)? -
On my S905 (Minix Neo U1) no freezes so far, but it was a clean installation.Thanks for this info. Mine was an upgrade. I might try a fresh install
-