I don’t have the Quick option. I cannot explain this behavior. I only have a N2 connected without any AVR. Maybe the cable?
AC3 transcode only appears as an option when channel count is set 2.0
Thanks. Yes, there is a glitch somewhere. It doesn’t appear right away if it is previously set to 5.1. It appeared after I reset the sound settings.
This must be a Kodi bug then.
While the LG OSD is on the screen, the remote controls the TV. Once the OSD disappears, you can then control the N2. This has nothing to do with N2 or CEC, this is just how LG TVs work.
Not sure if it’s the same on newer versions, on mine you simply press up and that dismisses the tv osd
Good point.
On my B7 I can’t seem to dismiss it. When I click up, it selects the HDMI input, and I still have to wait for the OSD to disappear.
You have to use the pointer to click inside the screen to dismiss osd. Then click up for instance to make the pointer disappear.
Thanks, by clicking into the screen with the pointer indeed the remote gets assigned to the N2 immediately. So I guess this works the same on your TV and you also have to either do this or wait for the OSD to disappear right?
Then I only have the issue left that on bootup the remote sometimes takes up to 30s to respond. Are you sure that your N2 is actually in suspend when you turn on your TV? When my TV turns on and the N2 has not been in suspend, then indeed kodi is visible right away when the TV is on and the remote works kinda fast, but when the N2 has been in suspend, then the TV shows a blank screen for ~5s until the N2 woke up.
If I wakeup my TV from suspend by turning the TV on there is a slight delay until I can use the cec remote. Maybe 2 sec. I see the Kodi GUI this time and I click down and it takes 2s until it moves down.
Hmm weird I’m a bit confused why the N2 seems to be already awake for you when the TV finshed booting, while for me it seems like the TV sends the CEC signal only after itself actually booted and that’s why I see the black screen for 5s. The same delay occurs when I manually put the N2 to sleep and wake it through Wake-On-Lan, so this is the time the N2 takes to wake up.
This all is really brand/type of TV dependent! I own a LG, type unknown (webos 2), ~5years old. I need to select the HDMI port where the N2 is connected. Otherwise without any action it will not wake up the N2. Then it takes ~10-20s until the CEC is functional.
I don’t see this. Do you have uart. Maybe something is blocking. But weird since we have the same TV. For me it is really perfect experience.
I can put it to suspend manually too and wol it will be there right away.
No I have nothing connected to the N2 except power, ethernet, a microSD card, and the HDMI cable. So you say your N2 wakes up instantly and does not take 5 seconds? Do you use eMMC or microSD? But waking up should not tax the file system much anyway. Do you have any clue how I can debug why the wakeup takes rather long?
I use emmc. That’s why I asked about uart. If you have it uart log would be interesting
Is there a link somewhere that explains how to grab the UART log? I can probably find a matching cable at work.
Thanks, I’ll grab a UART->USB cable from work next week, maybe there will be some output.
Is the N2 waking up instantly for all of you guys or is it just me who has this weird 5s delay?
If you are using a uart cable other then the hardkernel one make sure you don’t connect the vcc/power pin on the odroid uart connector. Also make sure that the uart is using 3.3V LVTTL and not 5v TTL. 5v applied to the uart will damage the board.
1 Like