Posts by Forage

Quote from johnberg

Thank you Forage.

Sorry for my slow understanding.

I could try Kodi 17.3 but that is still Jarvis or just be patience and wait for Leia in the future

No need to wait for that [8.0.2c] LibreELEC 8.0 builds for KIII Pro (S912)

Quote from johnberg

I begin to think that you can't simply install Jarvis on LibreElec 8.2 , am I right?

I mean just as you can with Windows or Android.

The easiest way is just install a complete build.

That's basically almost literally what I just said and you are just beginning to think it? What does it take to convince you?

It's a confirmed bug as kszaq has already explained to you. There's not much more to test.

Try the 8.0 build, that one should have Kodi 17.3. That's the earliest I could find.

Quote from johnberg

Is there a tutorial to do this.

Need Putty for up/downgrade Kodi or can you make it right from LibreElec?

Why would you want this? What is the problem you're trying to solve? It doesn't really make sense to do this. You are better off installing an older LE build if you really need an older version of Kodi or wait for a new build if you really need a newer version. LE is not like a random Linux distribution where you can just install or remove packages. You'd need to recompile the whole platform for one package (version) change.

Check the wiki for instructions if you really insist on going down this road and discuss issues in a separate forum thread if you get stuck.

Quote from afl1

LibreELEC 9 beta version for KIII Pro based on GDPR-2 LE 1.0.4.1

LibreELEC-S912.arm-8.90.1-K.img.gz

LibreELEC-S912.arm-8.90.1-K.tar

You can use it for other S912 devices. You need only replace dbt.img and add /storage/.config/remote.conf.

Which dbt.img from where?

Quote from the_bo

Hi prpaul

I'm using the aeon mq7 mod also. Heres how to to add reboot to internal button.

1. Winscp into your box.

2. Navigate to aeon mq 7 folder .kodi/addons/http://aeonmq7.mod/1080i/

3. Double click the DialogButtonMenu.xml to open file.

4. Search for the words reboot you should see code similiar to following

Code

<item>
  <!-- Reboot -->
  <label>Reboot</label>
  <onclick>XBMC.Reboot()</onclick>
</item>

5. Under that paste the following to add the button.

Code

<item>
   <!-- Reboot to Internal -->
   <label>Reboot to Internal</label>
   <onclick>System.ExecWait("/usr/sbin/rebootfromnand")</onclick>
</item>

6. Save changes and reboot box (or switch to another skin and switch back to mq7). Press letter S on your keyboard to bring up the power menu. Hopefully Reboot to internal option should be listed. It may take a few seconds after you click it for the box to reboot into android.

Hope this works for you

Display More

Can we please move all this off-topic stuff to either a new thread or even better: the Kodi forum?

It has nothing to do with the S912, nor LE for that matter.

Quote from ChimeyJimmey

But... "Powerkey definition = shutdown" in Android, so it REALLY does shutdown and pass through the whole booting process everytime.

And the remote works! In Android.

In LE - nope!

If it really would have shutdown your box completely it would not be able to act on your remote signal. No matter what you call the button.

Quote from ChimeyJimmey

Well,

it seems that Android ROM/bootloader has it, since it's working there.

How to make it work in LE is the question...

LE really shuts down your box completely. Your default OS does not. That's why waking it up with the remote works in one and not it the other.

Quote from hillz

Guys is it possible to install chromium on LibreELEC ? I have Tanix TX3 mini with S905W running the LibreELEC build in this thread

You're running a S912 build on an S905 device? Well done! ;-P

Quote from skyhigh69

Now if any1 has a tip how to get the blue light on?

That's a feature, not a bug

Quote from chewitt

Tethering requires a wireless driver that supports AP modes. Not all drivers support it and it is not possible to reliably pre-detect whether a driver supports it so the option shows in the GUI even if the driver doesn't. If it doesn't work, 99.99% the driver doesn't support it.

I'm sorry to hear the state of support is that low.

Is there at least a reliable way to detect that the lack of AP modes support was the cause of tethering failing when trying to activate it? Or is the lack of LE telling when trying to do so already my answer?

I'm just now starting to use WiFi on this device, having used just a wired connection until now.

The experience I had so far would be best labelled "unstable" I suppose.

All in the LE settings section:

1. The available connections seem to randomly disappear under "Connections". While they randomly come back sometimes, the only 'reliable' method I found was to toggle WiFi off and on again under "Network". When one of the two connections is actually connected it will remain in the list.
2. Only one of the two connections can actually connect at a given time. Not that you really need two, but it does feel a bit awkward.
3. When enabling "Tethered" under "Network", both connections disappear under "Connections" and there is no new wireless LE network to be found by other WiFi devices.
4. Enable "Tethered" under "Network", followed by disabling the "Active" option to disable wireless networks, followed by activating the same setting again and you will have all settings under "Network" listed twice.
5. Being connected to a wireless network seems to prevent the screensaver from kicking in. It will dim, followed by undimming a few seconds, up to a minute, later again automatically

What has been your experience?

I'm especially interested in tethering, if it would allow me to pass the wired internet connection through, to increase my WiFi coverage in the house. Did any of you got this to work?

I'm on the latest s912 8.1.9 build, but I figured most issues could be related to just the KIII.

Quote from boot2k3

Does preferred audio language setting work in LibreElec for LiveTV?

If I change audio track to 2nd available track, than it uses 2nd audio track(if available) on all tv channel too. But it's not preferred audio language track.

If I change it back to 1st track, than it uses 1st track on all tv channels again

Sounds like a general Kodi issue. You're better off discussing that in the Kodi forum.

Quote from marck120

You know, I know the topic you mentioned to me, mine was just a short question.

Which you can ask in the dedicated thread over there if you bothered to read it first and still didn't get your answer. This thread is about S912.

Quote from marck120

@Tim_Taylor

I did not understand exactly what problems with LibreELEC with the s912 ?

It is clearly stated in the first post. Does it really need to be repeated on every thread page?

Using libhybris remains a necessity, which means maintaining a hack, which means suboptimal performance and the occasional crash/hang.

Quote from kszaq

After a few nights of pulling my haіr out (fortunately I have some of it left) I can now confirm that vsync is going to work in a next build.

Great news and many thanks! How did you manage this?!

Quote from Jeffers

Why would you want to switch it off?

Some of the S912 (if not all?) boxes can get quite hot. I feel much more comfortable turning mine off when I don't use it since it stays at a constant 78°C when not using it.

Quote from wrxtasy

Booting to Android Recovery or TWRP Recovery sometime may be enough to stop LibreELEC from Autobooting again when you power on or reboot from Android.

In that case simply hold in the Reset button again, or whatever method you first used - when connecting power to restart autobooting into LibreELEC.

I performed the reboot process a couple of times going from LE to Android and back again and it will keep going back to LE automatically now indeed. I'm 100% sure that I had to perform the reset button method again in the past to get back to LE, so there must have been some instability in LE builds and/or Android booting at the time.

Quote from bubblegum57

I don't know about your box, but I agree with Pelican.

So you are saying that if I boot from LE (on SD) to Android using the "boot to internal" option from the menu, leave the SD card in and reboot again from Android, it will go back to LE automagically without doing anything?