9.0.2 Discussion

alex · 19 May 2019 07:59

@anon88919003 I don’t use meson-ir
@Portisch If you have multiple remote*.config files, only last one (sorting by file name) is loaded.
Using unloaded remotes causes Wrong custom code is 0xXXXXXXXX in dmesg.
Command
remotecfg /storage/.config/remote.conf
just does a replacement.
Configuration files haven’t сhanged since Krypton.
9.0.1 doesn’t have this issue

kiarod · 19 May 2019 09:26

I have the same problem as Alex.
After install of 9.0.2 second remote not working.
My box is Beelink mini iii. Boxes remote works
but now the logitech remote will not work anymore.
Worked fine with previous install 9.0.1
This is using Amremote config files in root directory.

Portisch · 19 May 2019 17:56

I don’t understand this issue correct. As I know the script search for remote.conf and load it with remotecfg. But only this single file. Also when remotecfg is reading the file and transfer the settings to Amlogic remote driver all others get cleared before. So they will not work at the same time. Or do I missing here something?

Edit: @alex @kiarod I checked the script and it really loads all found remote*.conf.
But before loading the new file the old get cleared.

So how it was before at 9.0.1? Where both remote working at the same time without changing anything on the remote.conf files? Please give me your remote config files too!

alex · 20 May 2019 07:09

@Portisch
At 9.0.1 both remotes were working at the same time. I can’t remember anything specific for using them simultaneously when I prepared configs.
I see factory_infcode = 1 in my secondary conf file, but I think it’s useless.
remote.conf (2.2 KB)
remoteoriginal.conf (1.9 KB)

Edit
See this post: Krypton style IR remote configuration is back!

anon88919003 · 20 May 2019 07:56

@alex SSH to your device and type remoteinfo and paste the link, thanks.

Portisch · 20 May 2019 14:00

Try to add factory_infcode = 0 in your remote.conf. In remoteoriginal.conf it is factory_infcode = 1 - leave this as it is. I am not sure, but this parameter set the “remote number”. When it is the same in the config files the remote will be overwritten.

You can also combine the remote files to one remote.conf like this example:

github.com

CoreELEC/amremote/blob/master/remotes.conf

#*********************************************************************************************************
#this file is configuration for each factory remote device
# 	work_mode	  0 :software mode  1 :hardware mode
#	repeat_enable	  0 :disable repeat 1 :enable repeat
#
#	factory_code      each device has it's unique factory code.
#			  pattern:custom_code(16bit)+index_code(16bit)
#			  examble: 0xff000001 = 0xff00(custom cod)  0001 (index)
#
#	release_delay	  unit:ms.release will report from kernel to user layer after this period of time
#			  from press or repeat triggered.
#
#	debug_enable      0 :debug disable  1 :debug disable
#
# SW MODE:
#	bit_count	  how many bits in each frame
#	tw_leader_act	  time window for leader active
#	tw_bit0		  time window for bit0 time.
#	tw_bit1		  time window for bit1 time
#	tw_repeat_leader  time window for repeat leader

This file has been truncated. show original

Use the custom_begin/custom_end labels to seperate the different remotes.

alex · 20 May 2019 16:15

@Portisch
Adding factory_infcode didn’t help. But combining two remote files to one remote.conf is working.
I prefer separating the remote files, because I use the similar remotes on 2 devices and it’s more convenient to maintain one file and share it.

@anon88919003
http://ix.io/1JzS

anon88919003 · 20 May 2019 16:24

@alex by that log you only have 1 remote.conf?

Will try this out myself tonight and see if I can reproduce it

kiarod · 20 May 2019 16:34

Here are my remote configs. Both remotes workremote.conf (1.8 KB)
remotesecond.conf (2.6 KB)
I have gone back to 9.0.1 and this is what remote info gives me http://ix.io/1Jzq

alex · 20 May 2019 16:41

@anon88919003
No, two files - remote.conf and remoteoriginal.conf
remoteoriginal.conf was actually loaded

anon88919003 · 20 May 2019 20:30

@alex we found the cause of it, ashame nobody gives us feedback on the nightlies because the offending change has been in them for over 2 months, it would have prevented this issue and others.

GiJOr33 · 20 May 2019 23:10

Hi,

I upgraded from 9.0.1 to 9.0.2 just fine (installed on SD Card), however bluetooth no longer works and so my Harmony Hub Remote can no longer be used.

When i go to the CoreElec settings it says “No Bluetooth Adapter Found”. If I reboot off the internal eMMC to Android, the bluetooth is all working fine.

I have updated uboot.bin in the passed to support the H96 Pro+ power/hibernate function. Will I need to update uboot.bin again?

The normal IR remote that came with the device works fine.

Thanks

Portisch · 21 May 2019 06:24

@alex @kiarod Please have a try tomorrow with the next nightly. The amremote config was cleared before selecting the remote.

@GiJOr33 thx, I own the H96Pro+ and will check it.

GiJOr33 · 22 May 2019 08:03

@Portisch That would be great. Thanks.

utiltiy · 22 May 2019 12:51

No time sync after reboot or cold boot with 9.0.2. If i test with “Wait for network” are the same, no time sync.

Any solution?

kiarod · 22 May 2019 16:42

@Portisch Tested two remotes and working again. Thank you for your help.

alex · 23 May 2019 05:16

@Portisch Remotes are working as before. Thanks

rmm · 24 May 2019 17:09

I’m not sure if the following problem is already known, but I couldn’t find anything about it. I’ve installed CE 9.0.2 on my ODROID C2 a couple days ago. I have 2 Hauppauge WinTV-DualHD DVB sticks connected to it.

Generally everything works really reliable. I use tvheadend and TBS drivers (since the ones from media_build don’t work correctly, at least with those sticks).

While watching live TV (tested with mpeg2, h264 and h265), as soon as I enable any kind of an OSD overlay, eg. channel’s EPG (KEY_I), codec info (KEY_O) or channels’ list, a strange hiccup starts after a few seconds. The picture starts to blur and pauses sometimes, sound breaks quite often too.

I’ve tried different settings available in Kodi and it seems, that everything works OK only if the HW-support for amcodec is disabled.

Please note: the problem occurs only while watching the live TV on the C2 with visible overlays. After hiding them, it disappears.
Recordings or any other video files are played without any problem (with visible OSD overlays of course). I’m even able to watch the same channels from the C2’s tvheadend on my RPi 3 under the current xbian and Kodi 18.2 or stream them to a video player (VLC) on my PC w/o any problems. But as soon as the live TV is played on the C2 and the OSD overlays are visible, all of the clients (1 or more, it doesn’t matter), playing any channel from an arbitrary MUX, start to show a similar hiccup as the C2: picture and sound distortions, pauses and buffering can be seen, the streaming sometimes even stops completely.

I checked shortly the current nightly build (20190523) too and could reproduce there the symptoms described above as well. Is there anything I’m missing? My settings seem to be pretty default.

Meeuuh92 · 24 May 2019 22:03

Lasts nighty builds are fine on my c2. Everything is ok Thank you.

GiJOr33 · 26 May 2019 04:56

Any luck with your H96 Pro+ and Bluetooth remote? Thanks.