[8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

Thanks for the information. Obviously I did not test with the latest build by you, since I had the problem also with your image. Good to hear that this is fixed.

I didn't say it's fixed. I simply suggested that there is a patch that might help.

Is a new version alpha or stable version in the works?
Or are there nightlies of this project or something?

I know it’s off topic but apology in advance, I want to purchase ” HP t610 Thin Client AMD G-Series “ for watching movies (x264 x265 10 bit 720 to UHD and Netflix) I want to listen suggestion only for all guy form this great forum, hp thin client is better or andriod tv box ( I have nexbox 2g 16g S905X) is better for that purchase which I mention above. Sorry for bad English.

rajawaqas

The AMD APU doesn't support x265 hardware decoding, it doesn't support UHD.

Quote from rajawaqas

I know it’s off topic but apology in advance, I want to purchase ” HP t610 Thin Client AMD G-Series “ for watching movies (x264 x265 10 bit 720 to UHD and Netflix) I want to listen suggestion only for all guy form this great forum, hp thin client is better or andriod tv box ( I have nexbox 2g 16g S905X) is better for that purchase which I mention above. Sorry for bad English.

I have the t620 and linux driver support is crap. If you're going to run kodi on windows it might be better but I would stick with the s9xx boxes for kodi

This is a testing version and you should expect some hiccups. If your not good with alpha releases and willing to suffer a little then don't use with this version. That being said it is a very stable testing version. Thanks to all who contribute. If it doesn't work for you don't complain just use another version that works or at least be an adult when you make a comment or request. These guys don't get paid for this work they do it because they love it.

Thanks GDPR-2
There is a tuner ve channel list,but there is an idle adapter warning

Quote from adamg

DTB will require updating or your box will not boot however this should be done automatically as part of the upgrade process.

For me, it seems the upgrade did not update the DTB automatically, because my S905W device no longer boots (not complaining, this is a test box, no worries here!).

The Coolest - you helped prepare a DTB for my Abox A1 Max's LCD panel - can you help to create a new DTB using the new format required by this update? Or point me to the directions on what needs to be updated in the DTB file, and I can try myself using dtc?

It also looks like the releases/dtb folder linked in post #1 is currently available. I'm not sure if this is intentional or not.

dapharsyde

Hi,

The source for the A1 Max DTB is still not in the repo yet, so it has to be built manually for now.

You'll need a few tools and a linux machine to do it, or you can send me the DTB image that is on the box now, and I'll update it for you.

Attached the DTB from the new devel.

I would REALLY appreciate some help with a PCM sound problem I'm having. In fact, I will be happy to PayPal anyone who provides a solution or a patch with a $25 donation via PayPal for their trouble (please let me know if this is against the rules). I am at my wits end.

My entire library is encoded with Opus audio at 48khz. Playing any movie with Opus outputs as PCM, as you'd expect. According to Kodi and the log file, it is reading the stream at 48khz. The receiver is only getting 32khz, and is producing noisy (clipped) audio as a result.

Kodi's CodecInfo showing 48khz: http://imgur.com/hBp9NWI

Yamaha Receiver showing 32khz: http://imgur.com/jZ8dFNP

I'm attaching a full debug log from playing a video with 5.1 Opus audio, but here is an excerpt showing that the audio stream created is 48khz:

02:41:52.909 T:3743523664  NOTICE: Creating audio stream (codec id: 86077, channels: 6, sample rate: 48000, no pass-through)
02:41:53.381 T:4081054544   DEBUG: CAESinkALSA::SelectALSAChannelMap - Selected ALSA map "FL FR LFE FC RL RR NA NA"
02:41:53.419 T:4081054544   DEBUG: CAESinkALSA::GetChannelLayout - Input Channel Count: 6 Output Channel Count: 8
02:41:53.419 T:4081054544   DEBUG: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR, FC, LFE, BL, BR
02:41:53.419 T:4081054544   DEBUG: CAESinkALSA::GetChannelLayout - Got Layout: FL, FR, LFE, FC, BL, BR, UNKNOWN1, UNKNOWN1 (ALSA: FL FR LFE FC RL RR NA NA)
02:41:53.419 T:4081054544   DEBUG:   Channel Count : 8
02:41:53.419 T:4081054544   DEBUG:   Channel Layout: FL, FR, LFE, FC, BL, BR, UNKNOWN1, UNKNOWN1

Interestingly, the problem happens with audio set to "Fixed" as well.

• With audio set to Best Match and input file of 48khz, I get 32khz at the receiver
• With audio set to Fixed @ 48khz and input file of 48khz, I get 32khz at the receiver
• With audio set to Fixed @ 96khz and input file of 48khz, I get 64khz at the receiver (with stuttering audio)
• With audio set to Fixed @ 192hz and input file of 48khz, I get 128khz at the receiver

So there is clearly something not lining up between what Kodi is requesting and what the Minix is outputting.

I don't know what else to look at. Again, I will send a $25 donation to anyone who can provide me a fix or a patch to resolve the issue. My next step is to try to save up for an NVIDIA Shield, but I know that has it's own issues. I'd rather not have to do that!

Thank you,

-KJack

You should share a sample file. No problem here even with 192 kHz audio, but I don't have any opus audio (not even know what it is).

Quote from The Coolest

dapharsyde

Hi,

The source for the A1 Max DTB is still not in the repo yet, so it has to be built manually for now.

You'll need a few tools and a linux machine to do it, or you can send me the DTB image that is on the box now, and I'll update it for you.

Attached the DTB from the new devel.

Thanks for the DTB file - after updating with this file, the device boots up again.

In order to get my LCD working again, it looks like I'll need your help to recompile your updates to the aml_fd628 module against the new kernel. Attempts to insmod the file you provided me earlier result in an unknown symbol error.

dapharsyde

Does the built in driver work? (ie. Clock works?)

Perhaps we should take it back to PM.

This is probably a stupid question so apologies in advance. I have a KI Pro and its website says it has "eMMC" does that mean it doesn't have NAND and will work with the new build installed to internal?