Posts by Poida

Quote from kszaq

Which builds do you use on these boards? Is it m201d for V3_1 and HD18Q for 2.0?

I use the MXQ builds for all of them

Quote from kszaq

can you temporarily flash 7.0.2.2 m201d to your 2.0 board and see if playback issues are gone?

I'll give the other builds a try, but the MXQ build is the only build that controls the LED properly

EDIT: Same issue with m201d and HD18Q builds but I did just notice that the HD18Q build is incorrectly switching the video playback to 24Hz. I'll just see if thats happening with all of the builds

EDIT2: That's it! If I remove 24Hz from available refresh rates, playback is fine.

Quote from kszaq

Is this specific to 2.0 board? Do the same files play OK on V3_1?

Yes and yes

Quote from kszaq

Can you also confirm that downgrading to 7.0.1.4 (you can simply put 7.0.1.4 tar in Update folder and reboot) makes the issues go away?

yes

Quote from kszaq

try this test build for fixing playback issues

Still have the same issue which, for me, is not limited to any particular resolution.
All movies, local or streaming. (on the v2.0 board)
[hr]

Quote from PatrickJB

not sure about how to set up a static IP address

You set that up in the LE settings addon

Quote from kszaq

S905 build goes public

Great news indeed !

There's still an issue with the S805 builds after 7.0.1.4 on the v2.0 boards (at least the one I have available)
Video playback is very jerky and glitchy. The audio seems to playback normally while the video jumps around.
The issue does not exist in builds prior to 7.0.2.1

Quote from CGarces

I'm using the SD version. It's posible to acess to the NAND and fetch the remote.conf from Android system directly with SSH without boot Android?

Yup, I think this is what you want

forum.libreelec.tv/core/attachment/163/

Actually that isn't from Android but from the HD18Q LibreElec build - see how you go

Quote from mikepap1

So I want to ask you if it is possible to add in the S805.MXQ firmware the remote control of the HD18Q, this way my device will work 100% !!! or if there is an easy way for me to upload the file of the HD18Q to the MXQ image!

copy remote.conf that works into /storage/.config via SSH or, alternatively, the configfiles samba share.

Quote from kszaq

This is the last try

Nailed it. Both types of boards are displaying the correct MAC address

Quote from kszaq

Can you please post a log from v2.0 board with latest test build

Attached Files
  log-2016-07-05-12.09.33.zip (Size: 50.59 KB / Downloads: 1)

Quote from kszaq

Please try another build

I feel your pain man, back to random MAC on v2.0. All good on v3_1

Quote from kszaq

yet another messed up u-boot.

Doesn't surprise me, these boxes were all silly prices.
I'm around for a good few hours yet if you need to chuck anything over for testing

I'm probably stating the obvious here, or something that is not possible but I'll mention anyway that, my observations so far have been that if there is a valid MAC at one location, there seems to be 00:00:00:00:00 at the other. I'm probably only observing this after all the action takes place. Just thought I'd mention it, in case it has been overlooked

Quote from kszaq

Please check this build for correct MAC address setting:

Works fine with the v3_1 boards, but then so did the 7.0.2.1.build.
For the v2.0 board it now sets the same MAC address each time (00:15:18:01:81:31) which is not the actual MAC for that board.

Quote from kszaq

Can you please post a log for this issue? It has to be collected right after a cold boot.

log-2016-07-05-00.48.32.zip

Quote from kszaq

Can you please post a log for this issue? It has to be collected right after a cold boot.

Prolly be tomorrow now, but will do

Quote from kszaq

When you enable wake_lock, LED will not turn turn red on "suspend".

Yes, I did not enable wake_lock on the v2.0 board as it already turns off / suspends as expected and the LED displays appropriately.

I only mention the LEDs since my MXQs seem to be able to run any build, but the v2.0 LEDs only work correctly with the S805.MXQ.arm builds

With the 7.0.2.1 release, without enabling wake_lock the v2.0 board behaves as before - except the MAC address is different after each boot
Like I said earlier, kszaq, if nobody else has an issue don't even worry about it (I can just use the script to correct the MAC address)

Quote from kszaq

I have re-built entire 7.0.2.1 release

Then the same issue exists, I have tried all builds on the v2.0 board and each one gives me a random MAC address each boot

As expected, the 'wrong' builds are also unable to switch the LED. ALL builds produce a random MAC address each reboot

I'll check again with the update builds

If it just turns out to be me, don't worry about it, as the script posted earlier does correct this problem

kszaq Which images have been re-built. I see no difference (result wise, they are different sizes) in any re-downloaded from the update folder. I'll try the SD method

Quote from kszaq

Please check the download site in 2-3 hours and re-download.

Will do

Sounds good !
Just waiting for the upload to complete, so I can get at the new toys

EDIT:
Excellent work again kszaq! Thank you

Quote from kszaq

you should note that with wake_lock enabled, your device is working all the time - e.g. pressing a keyboard button results in key press in Kodi that you cannot see!

That is the case with attached keyboards but, at least with my v3_1 boards, RC Key presses made while the screen is blank, seem to be ignored (which is good news if, as in my case, the boxes are predominantly controlled with remotes)

On the downside, at least using the update method, these new builds cause my v2.0 box to adopt a new random MAC address each boot. I'll check if the full install makes any difference . . . same

Quote from PatrickJB

Do you know if this is the correct syntax

Sorry, I'm a complete noob at the "Linuxy" stuff, so couldn't really say for sure