Posts by userfame

Quote from Iridium

This is a moderated forum.

Like all this other forums I'm on - no difference despite here goes everything thru censorship upfront which this topic is about. So I'm asking here why are things like that? Is the server location china or the content mafia threatening this forum? Why are these radical measurements needed here?

Quote from Iridium

What YOU think is acceptable may not be acceptable to others.

And here comes the funny thing. I thought all of my posts are acceptable - and oh wonder - they are! All past the censorship team - despite this one*, chewitt wasn't accepting this thread here and trashed the first version of it. But then comes Iridium and is fine with it - I guess like everybody else. Why not? Are we talking about secrets here? Only chewitt knows - maybe he will tell us and enlighten us?

Quote from Iridium

BTW: As you have brought yourself to the attention of LE moderators, any additional posts will get a lot more attention than other posters.

What does this mean exactly? Now it will takes 2 days that my posts are get published?

---

This signature will remain inaccessible for others until approved by the great Chinese firewall.

*and one more actually Iridium didn't like. Why? I don't know because it complied with the rules...

And now my signature get's shown everywhere even when disabled... Weird times here

I know, sometimes critic can hurt - sorry for that...

---

This signature will remain inaccessible for others until approved by the great Chinese firewall.

Quote from HiassofT

It might be best to check with a fresh install on a spare SD card. Could well be that you carried over some outdated config/scripts (autostart.sh, .config/udev.rules.d, .config/lircd.conf etc) that's now interfering.

Good point! The install was already an upgrade from a LE8 or something like that. I will give it a shot with a fresh install.

Quote from HiassofT

The only thing you need to change on a fresh install is adding the "dtoverlay=gpio-ir" line to config.txt - then Microsoft MCE (and Xbox 360) remotes should just work.

Very nice. That's what I'm used to. Good to hear that it's like this on LE9 and there is no regressions here

Quote from HiassofT

The Xbox 360 remote uses the rc6/mce protocol as well but uses different scancodes so it needs a separate keymap (to map scancodes to keycodes) - see http://LibreELEC.tv/xbox_360 at libreelec-9.2 · LibreELEC/LibreELEC.tv · GitHub

That's interesting. Thank's a lot for this link.

What I really don't understand is that it worked one time now without any additional configs (see pulse/spaces in my last post) and also the mapping was right out of the box (didn't tried all keys but successfully navigate thru kodi). Now, one day and a reboot later it doesn't work at all anymore

I'm still on 9.2.0 and will do the update to 9.2.1 to see if something happens - don't have much hope but it's worth a try.

Captain, we good pulse! And even space

kodi:~ # ir-ctl -r
pulse 2607
space 930
pulse 439
space 449
pulse 426
space 455
pulse 432
space 895
pulse 435
space 892

Quote from Skeeve

<key id="61662">shutdown</key>

How does this configuration end up here:

Quote from Skeeve

A button connecting pins 5 & 6 will now shut down your libreelec.

Why it's gpio 5 & 6? How could I set my own gpio pins?

This is a real question despite chewitt just delete my old thread:

Is this normal in this forum? I never experience something like that and really need to say that it annoys me a lot.

Does this just happens to some users or to all? What is the propose of this? Why can't it work like anywhere else where you can just post and it's accesible for other users to read?

Kindly approved by Iridium (who just delete/disapproved another critical post he didn't like )

---

This signature will remain inaccessible for others until approved by the great Chinese firewall.

Quote from kefir

Hi.

Help please.

How enable TV out in Orange Pi PC Plus?

It's described on the first page under Limitations:

Quote

- no support for TV out

---

This signature will remain inaccessible for others until approved by the great Chinese firewall.

Quote from userfame

So I will need to check wiring and come back here...

I checked. Ground to Ground, 3.3V to 3.3V and the signal pin to GPIO 18 (should be default, at least it was in the past). With this wiring I had my remote running without problems the last years, after upgrade to libreelec9 the thing broke.

My config.txt has this:

# enable the gpio-ir modules -> GPIO18
dtoverlay=gpio-ir

Quote from HiassofT

The wiki page contains a very detailed step-by-step troubleshooting section Infrared Remotes [LibreELEC.wiki].

Found /sys/class/rc/rc0/ (/dev/input/event1) with:
Name: gpio_ir_recv
Driver: gpio_ir_recv, table: rc-rc6-mce
lirc device: /dev/lirc0
Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
Enabled protocols: lirc nec rc-6
bus: 25, vendor/product: 0001:0001, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms

Looks good. My ir remote is a mce remote (listed here: List of MCE remote controls - Official Kodi Wiki) so maybe this mce_kbd thing could be useful.

kodi:~ # ir-ctl -r

But libreelec doesn't receive any commands. So I will need to check wiring and come back here...

Quote from Da Flex

The essential sentence for LE 9.x.x is this:

Have you done this?

Not that I'm aware of. But isn't that the "fallback" mechanism and a ir remote like mine (which worked already out of the box in the past versions) should work without this modifications? Should the file be empty then?

I have the feeing LE 9 made a big step backwards regarding ir remotes.

Thank's Klojum for approving my thread. That's so nice from you!

I'm not sure if it's related but I was trying to do capture keypresses from the remote with

rctest

if this is right? I don't no. It's not mentioned in the documentation. My output looks like this:

rctest[564]: Waiting for connection on channel 10 ...

and nothing happens if I push buttons on my remote....

I wanted to ask how the performance (mainly interesting is the menu navigation and loading times) for Allwinner H3 (for example Orange Pi PC) and H5 (e.g. Orange Pi PC 2) devices is compared to a Raspberry Pi 2 or Raspberry Pi 3.

From the specs they look a like and all have 4 cores and 1 gig of ram. But can someone who has both or more devices give a statement?

I know this images here are not ready yet and will just ship with LE 10. But if you look the prices for this oranges they are almost half the price as the raspberries and also have some extras (ir receiver, a button - useful? I don't know!)...

---

This signature will remain inaccessible for others until approved by the great Chinese firewall.

Hello,

newly created threads will remain inaccessible for others until approved by a moderator. Sorry for that!

and now - the content: I know there is a lot's (really a lot!) of outdated information, documentation and threads about the use of ir remotes.

Let's just start where I came of... back the old days before libreelec... the openelec days:

In this times (was it v6?) my remote (a xbox 360 universial model or something like this it's called) looking like this:

Source: Microsoft XBox 360 Universal Remote Control - Official Kodi Wiki

...and this remote didn't worked out of the box but required a (more or less) correct keymap file. After adding the file it worked: Great!

Migration to libreelec (I think we are talking about v.7 now - but not sure) and it continued like that: Providing the right file in the right place -> Profit.

Next version was a real bummer. I think it was libreelec v.8 and it just worked right out of the box! Without any configuration! Surprise!

Now I made the upgrade to libreelec v.9 and lost my remote and don't get it running anymore.

I found (after reading half on the remote related threads here) this link: Infrared Remotes [LibreELEC.wiki] which even mention the changes in librelec v9.

And I did what was written:

Quote from https://wiki.libreelec.tv/infrared_remotes#rpi_specific_changes

RPi specific changes

Change dtoverlay=lirc-rpi to dtoverlay=gpio-ir in /flash/config.txt to switch to the newer gpio-rc-recv driver which replaces lirc-rpi.

But my remote doesn't work. I (since always) used the default pins for the (tsop?) receiver on my raspberry. And no hardware changes.

I'm more confused now after reading the wiki because It talks about a lot's of confusing things but doesn't tells me how I could use my remote which already worked out of the box in the past

Good old days? Maybe

Quote from chewitt

It just means the wifi chip will not work. The chip copies (is ripped off from) a Realtek design but with enough differences that you can't simply add the chip IDs to the existing Realtek driver, and the existing driver source for Linux 3.14 "works" but is garbage code. We had a stab at forward porting to Linux 4.20? (it was some time ago) but with no documentation and badly written code to start from it wasn't a fruitful expedition and we gave up. I also had one of the Rockchip staff (native Mandarin speaker) do some phoning around and he confirmed SSV went bust in 2016 so there's never going to be newer official sources. The latest kernel the current driver will run on is Linux 4.4. After 4.4 you run into significant crypto API changes (needs a major rewrite) and this stops the driver from working.

Very valuable information about this (dead) wifi chipset. Thank's a lot!

I then *just* need to a attach a usb wifi dongle with a (mainline) supported chipset that I have flying around anyways

Quote from chewitt

Mainline kernel doesn't have same hard-coded 1GB/2GB device-tree silliness as older kernels. Wireless chip is the SSV6051P .. the same crap cihp that's in the Tanix box. There's no support for that chip under mainline kernel (and unlikely to change).

Nice to know. But no mainline support for the wifi doesn:t mean no support for libreelec, right?

Here it's written libreelec supports the SSV6051P:

ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<) - Page 42 - TV boxes - Armbian forum

Is this still true?

Quote from chewitt

I've a Tanix TX3 mini which is the same spec (1GB/8GB and also S905W) purchaded off eBay for $18 a year or so back. The TX3 device-tree will probably work on is as most of these ultra-cheap S905W boxes are carbon copies of the Amlogic reference board. It likely only differs in choice of wireless chipset.

Nice to hear. I ordered the 2GB/16GB now for $18 shipped. Does the TX3 device-tree also offer a 2/16 Version?

And what would be the most convinient way to check with wifi chipset is used (once I have my device...)?

I actually found a photo from the inside from this m8s plus w (1GB/8GB) here

Quote from buzzmarshall

Sounds like a deal... But... there is always a but ...

[...]

Kodi has already moved to 18 and in the near future will be going to 19 and unless you want to just settle to keep it going on 17 and python 2 or maybe if your lucky enough to find a version with Kodi 18 your choices will keep getting smaller.

But if that is all you expect out of the device then it may serve your purposes...

For sure I want the latest kodi running on my device. I don't now why it shouldn't run?

If there is no recent *elec available for it I just have to bite the bitter apple and install kodi on the box (prerooted android 7.1)...

Borygo77 what image/version you are running on your a905w box?