Cheers for the new test build Ray.
I’ve sorted the issue I was having with the Hyperion and the 4k vp9 file so everything working as it should be so far 
Thought about trying this last night then fell a kip but the posts today reminded me!!
vp9 afaik is basically Google’s version of h265 so I set double_write to 3 for vp9 also and it fixed up the issue 
Whats the sysfs path? I have add it for hevc in the upcoming hyperion.ng service addon. I will add it for vp9 too
And yeah VP9 and hevc share the hw decoder IP.
Cheers dude wasn’t 100% but give it go haha
The path is: /sys/module/amvdec_vp9/parameters/double_write_mode
Guessing when the addon is updated I’l be able to take it out of autostart.sh?
Nahh it doesn’t matter. The idea is to only set it for hyperion addon users out of the box.
Hi, I’m testing night builds for several weeks and I’m having issues with samba. I have three USB3 drives connected directly to N2 and I’m using default samba configuration. It works, write speed is ok, about 80-100MB/s, but read is just 20-30MB/s. Samba client is Win7 or Win10 PC connected via 1GB ethernet. I tried official Ubuntu 18.0.4 image from hardkernel and samba works there like a charm, r/w 80-100MB/s both. Do you have any idea what could be the issue with CoreElec samba settings? Or maybe USB3 drivers? Thank you!
In this build multichannel Dolby transcoding option is missing.
Not sure what that means.
Do I have to update u-boot manually or does it come with coreelec? I saw that hardkernel solved some performance issues.
Hi Ray. Just a minor for me on the new kernel test build. I have some personal video shot in my phone that uses aac mono. I get no sound. This was the case as well until one of the nightlies fixed it. Files play with sound on S905 CoreElec.
It will update with every tar update. We have the new uboot too but we need to do more testing.
@Ray I’ve just got my N2 and use it with my LG 55B7D. I think you mentioned somewhere in this thread that you have the same tv. Whenever I switch the input to the N2, the remote (regular Magic Remote that comes with the TV) is not forwarding the button presses to the N2 for a couple of seconds (sometimes only 2-3 seconds, sometimes up to 20-30 seconds). Do you have the same issue on your model? Is there anything I can do to improve this, maybe send some kind of ‘keep-alive’ from the N2 every second or so? After the delay, the remote works flawlessly until I switch back and to the N2 again, then the issue repeats.
Yeah I have the same TV and no issues.
So that I get this right. The N2 is booted and doesn’t go to suspend and you switch input to say Netflix then some time later back to the HDMI and it doesn’t work right away?
Yes. But the same happens on a regular boot or when waking from standby. Seems like the TV takes a bit to recognize that there is a CEC capable device? On the other hand, it wakes it from suspend just fine.
Try to disconnect any other HDMI device. Then reboot. Just for testing. Normally it takes a few seconds on boot until CEC works. But not on input switching.
Thanks, I’ll try this in a few minutes. Do you use the regular LG remote or another one? How does it behave for you when turning on the TV and thus waking the N2 from suspend? For me, first the TV turns on and after a short delay it wakes the N2 and then after another few seconds the remote starts to work. All in all it takes like 10-20s until Kodi can be used, which also seems quite long.
It is instantly for me. I turn it on kodi is already up when TV outputs an image. CEC works right away.
Multichannel PCM doesn’t work, same as earlier. But, at the same time, the workaround of Dolby transcoding is missing. That option is completely missing. The option appears below dolby passthrough usually, but I can’t find it in this build.
I am experiencing very frequent full freezes on my N2, is there anything I can do? When navigating through some network directories (or bringing up the search menu) the UI freezes for up to 30s but not always, about 75% of the time.
This happens both with NFS and SMB, using a remote controller also does not work (USB or wifi like kore) – the odroid is wired and the remote storage is working perfectly for other users (including my odroid c2)
What can I do to debug or fix this?
I also see this with my older LG TV.
I don’t even have to switch inputs though.
I can navigate around the menus, put the remote down, pick it up again in a minute or so later and if I press a navigation button a few times, I have to wait for 5-10 seconds then the inputs are all sent at once. Often it double sends.
E.g
Start watching TV show. I want to pause midway.
I press ok button once to bring up osd.
Nothing happens.
5 seconds later and the show will pause and the osd comes up. (Double input brought up the osd then pressed ok again on the play pause button)
After that navigation will work normally again for a while.
When it first connects it also behaves like this where it takes a while to accept inputs, sends all at once, then double inputs for another 5-10 seconds, then behaves normally
I now retried with only the N2 connected and rebooted both the TV and the N2 multiple times, but nothing changed.
When switching from ‘Live TV’ input to the N2, the remote takes about 5 seconds each time to be usable in kodi. During these 5 seconds, the TV displays the new input on the top left ‘N2 | HDMI4’. When this disappeared, then the remote works.
When turning on the TV, it shows a blank screen for 6 seconds, then displays the input on the top left, then 5 seconds later kodi shows up and then 15-20 seconds later, the remote starts to work. I repeated this 5 times now and it always behaves like this. All in all this takes roughly 30 seconds.
However, if I turn on the N2 through Wake-On-LAN, it takes about 5 seconds (seems to be the time it takes for it to wake up), then the TV turns on (through CEC), which again takes 6 seconds. Then kodi is already visible and the remote can be used 5 seconds later (after the input on the top left has been hidden) - just retried and the remote took 25s to respond, so this seems to be hit-and-miss.
Can you describe how exactly you turn the TV on (which remote e.g.)? Do you have ‘Quick Start+’ turned on in your TV settings? Mine is off, because otherwise my AVR did not turn on through CEC in the past.
EDIT: tested again with my fire tv stick. The input switching behaves the same here, it takes 5 seconds for the remote to work. But after waking it from standby, the remote works ~3 seconds after the fire tv stick showed its UI. So I guess the input switching is the TV’s fault (and I don’t care too much about this), but the 20s lag on startup is annoying.
EDIT: what also happened a few times now is that the TV turns on and immediately turns off again (probably because the N2 sends a power-down event somehow).
About | FAQ | Terms of Service | Privacy Policy | Legal Notice