Posts by Poida

Quote from PatrickJB

Can't see autostart.sh via samba and still not sure how to create it, sorry for being thick. I thought the latest build used interactive according to the changelog: LibreELEC

I might just revert to 7.0.1.3 and see if it's any better as I don't think you changed much in 7.0.1.4.

You won't see autostart.sh unless you have created it.
It's simply a text file list of commands, like most script files and needs to be created in / moved to /storage/.config via SSH
or alternatively the configfiles samba share.

Quote from kszaq

To make "V3_1 Android way" work on these boards I would have to do 2 things: enable WAKELOCK in kernel config and write code to make Kodi aware of "suspend" with wakelock. Unfortunately enabling WAKELOCK breaks kernel for some other boards so this is a no-go.

Thanks for taking the time to enlighten me on this. Do you know if the same problem exists with the S905 boards?

kszaq Why is it that the Android builds of the v3_1 boxes can wake using the power button, but the LE builds cannot?

I know that you have mentioned it is a u-boot.bin bug, so are the Android builds not using u-boot.bin? or is it really complex and not easily explained to the layman?

Quote from PatrickJB

I don't have an S905 at the mo so may wait and see which box runs well, is popular and, dare I say it, cheap!

Wise words mate!

Quote from PatrickJB

[hr]

Not a fan of zero cacheing just wondering if cache can be specified?

You seem to be ignoring the information you have quoted

Quote from kszaq

Does the LED switch at all for you with the most recent build?

It actually does work correctly. The LED is blue when on and dim red in standby / off.
The problem is that, since I cannot put the box into standby or off due to being unable to wake via remote from either condition, effectively, the blue light is permenantly showing.

I can work around the fresh start I prefer by causing a Reboot in place of the On function.
The only slight irritation is that the bright blue LED is always on.
I was kinda hoping to discover there is a way to manually manipulate the LED, or have it permenantly show very dim red in place of the bright blue before resorting to phsically covering it.

Quote from PatrickJB

kszaq

BUG: I've noticed that local vid files are being buffered which I'm sure never used to happen and I thought this might have helped minimise frame drops although the verdict is out on that.

I've experienced that even with the earlier builds.

Quote from and later

. . . The problem is that after a pause when starting playback the first 10 to 15 seconds of the vid are skipped.

I'm sure there's a kodi 'jump-back' addon that allows you to set how many seconds you skip backwards on resume play.
If all else fails, maybe that might be of use?

+1 for any possible patches to get the blue light to go out

Working fine here

kszaq Being the eternal optimist, I eagerly await your next brilliant new idea for a workaround 

Quote from kszaq

Can you test if this build reads a correct MAC for you

Yep, reads the correct MAC address but still not able to wake up the box with the remote after poweroff / suspend.

One down, one to go Thanks for rushing this through kszaq

The not waking is easier to work around until you get time to take a closer look.

Quote from Bruur

Hi, try this . . .

kudos to you man - it works!

Man, you're all over this kszaq - I'll just stop trying to figure it out and leave up to the maestro, I think LOL

@Bruur I'll take a look at that, while I wait for the Guru to work his Magic

kszaq thanks, this will be a great step forward for many, and I'm sure will avoid issues down the track.

It just seems strange that, posts here suggest this is ONLY an issue for 3_1 boards yet, from what I read elsewhere, it is normal practice to look at efuse for the MAC address, at least with Amlogic boards. I wonder why the other revision boards are not affected?

I have looked at patches used with other builds, but I'm sadly nowhere near competent enough to tackle this sort of stuff myself.

Keep up the impressive work & thanks again for looking into this issue

kszaq - Sure is

Many thanks kszaq, for your efforts with this

@kszaq Is there any way I can patch the box (using update.zip or SSH) with a pre-defined MAC - different to the existing generic one ?

If so, would the MAC address be overwritten with future updates ? Shouldn't really matter, if it is possible, as the patch could always be reapplied

I am currently using 6.0.1.1 on one of the boxes and static IPs, but it looks dreadful each boot / reboot with text output spilling all over the boot screen which kinda feels like I've gone backwards here LOL

The real nuisance being that, most of the time, you've no idea what the board revision will be until you actually receive the box.

Quote from PatrickJB

Both the same as in my signature.

OK so we have a date, 25/08/2015, but what motherboard version is that? V1.0? v2.0? v3_1? . . .

. . . It looks like they have v2.0 motherboard which would explain why you are not seeing the v3_1 issues.
Good news, I guess, as that seems to support the theory that this problem is confined to the v3_1 boxes