Now it’s fine, thanks.
Bonjour,
I can not find the covers/infos of my new movies, do you know why? I did not change any settings (TMDB) …
Vim3
i did not yet try that but i am wondering what you want to say. coreelec/odroid is not able to handle CEC correctly? because the raspberry did not have any problems with my setup (which is - i guess - a very common one)
edit: just tested it. the behaviour is as i expected.
when the tv has its input on hdmi1 and the odroid is connected to hdmi1, it works. but as soon as the default hdmi input is e.g. hdmi2 on the tv/avr, the odroid simply ignores that. when i explicit select hdmi1 on the tv as input source (even tho its greyed out because its not recognized), the odroid wakes up, otherwise never. so its exactly the same behaviour with the avr - i have to select explicit the channel, otherwise the signal seems to be ignored.
the raspberry woke up no matter which hdmi input was the default one in my tv or in the AVR.
as this happens on both sides (avr and tv), i assume thats not an error in the avr/tv but in coreelec or in the odroid.
1 Like
I also have CEC issues. Waking up when turning on the TV works fine for me, but sometimes the remote is not forwarded to the N2 afterwards. I then have to switch to another HDMI input, wait 1-2 secs, then switch back to the N2 to make the remote work. The N2 is directly connected to my TV and other HDMI devices (e.g. PS4) work without issues and always have the remote working properly.
2 Likes
I am changing this (CE 9.2.0) with notepad ++, no automatic update. And disable the blue led but none of the 2 things works. Any help / suggestion? Thank you
Did you remove # character ?
# enable_system_power=0 -> no effect
enable_system_power=0 -> effect
1 Like
surely that is, I forget to remove them. thanks i will try now
now yes, i forget this 
thanks team, petitboot and coreelec best things in N2 
1 Like
Does that then mean we cannot have any other device linked to our TV while using a N2? Seems a bit of a harsh workarround no?
For me I got my Set-top box connected and a N2 to my TV directly on different HDMI ports.
When I go from my settop box to my N2 it sometimes picks up on it but most of the time it shows the N2 but the command is actually still going to my settop box. Switching sources a couple more times or disable/enable CEC on my TV itself wakes up the N2
No, it doesn’t mean that.
Disconnect other devices help you to narrow down your problem.
If you are troubleshooting better to eliminate all other possible trouble sources.
For example, most of the older amlogic boxes have a bug in their uboot which blocks the CEC functions completely even if they turned off.
CEC implementation on different manufacturer’s different devices are all differs so hard to tell how it will work together in different combination of devices.
Hi,
First of all let me thank you for spending hours into the support of this device and make many people happy 
I’ve just spun up my new N2 with the latest ce nightly and everything is working pretty well except hyperion. I’ve seen there were a lot of discussions some months ago but it’s pretty quiet since then. Is there any known issues with the addon? I can’t get it running for HW accelerated videos (H265, PVR), but it works smooth on H264 (like netflix.inputstream). Anyone facing the same?
I’m using the hyperion not hyperion-ng addon. The ng-build seems not to support my udp device 
Hyperion.ng work fine for me in my N2 with all content
i have some problems with the latest updates (nightlies). is there anything known that the installation of those files does not start? i have to reboot (removing the power cable) of my n2 two times so it boots without installing the .tar.gz - otherwise i just see the coreelec welcome screen, then it “freezes”, but the heartbeat led is still blinking as regular, but no lan, no text on the TV that it updates anything etc.
Read this and it’ll explain.
thanks, that fixed it!
I tried to update the hyperion.ng to the latest version, but I came across this error:
"[hyperiond MAIN] Set user data path to '/storage/.hyperion’
QSqlDatabase: QSQLITE driver not loaded "
Any idea how to fix it? Current version have many issues with multiple instances
hi @ all
today i tried to use my Minix Neo A2 Lite for shutdown/wakeup my odroid n2
shutdown works great but wakeup does not work:
i was collecting the code like this:
CoreELEC:~ # ir-keytable -u
Protocols changed to irmp
Waiting for IRMP decode event. Please, press CTRL-C to abort.
Received IRMP code: remotewakeup=‘0xe718fe01’, decode_type=‘0x0’, remotewakeupmask=‘0xffffffff’
this is my config.ini:
#------------------------------------------------------------------------------------------------------ # # IR setup Setup a custom keycode to wake the N2 from suspend or poweroff You can stop kodi and eventlircd # and use "ir-keytable -u" to obtain a compatible u-boot IR keycode # remotewakeup='0xe718fe01' # # decode_type can be one of the following: NEC='0x0', DUOKAN='0x1', TOSHIBA='0x2', RCA='0x3', RC5='0x4', # RC6A='0x5', NEC_TOSHIBA_2IN1='0x6', NEC_RCA_2IN1='0x7', RCMM='0x8', NEC_RC5_2IN1='0x9', # NEC_RC5_2IN1='0xa', RC6='0xb' # decode_type='0x0' # NEC # # remote power key mask: Some IR protocols implement a toggle bit, this can be ignored by the "and" mask: # RC5='0x37ff', RC6='0x1effff', RC6A='0xffff7fff' # remotewakeupmask='0xffffffff' # #------------------------------------------------------------------------------------------------------
I am not sure now, try decode_type='0' in config.ini
thank you for your quick reply but still no bootup.
You try to wake up N2 or the Minix?