Odroid N2 test builds

Take another look, maybe you change your mind :wink:

The easiest way I’ve found is just you connect via SSH.
Touch the autostart file so it creates it.
Then you can edit it in notepad++ and it will save it back with the correct format

For me the easiest way is:

Open an SSH terminal
nano autostart.sh
(edit the file in nano)
Ctrl-X
Y
Enter

And you’re done.

2 Likes

Hello,

in my opinion @Ray is right.

Editors like Notepad++ or Notepadqq are often mixing up “spaces” and “tabs” for example. This and other formatting issues can cause serious Problems.

For me “nano” or “vi” is the best way, too…

Cheers
Mark :hugs:

2 Likes

Attaboy…

Never had such problems with any editor. If user press tab then it is tab not space :slight_smile:
For quick editing I’m using Metapad.

interesting fact, microsoft FINALLY fixed notepad, so in future releases you can now choose the line ending type:- https://devblogs.microsoft.com/commandline/extended-eol-in-notepad/

on another note, i remember back in the day when i was running openelec that they included the excellent dos2unix utility, not sure if its part of coreelec or not, but it was very easy to use and worked a treat for converting when things get screwed.

Great that you have the same 2017 LG OLED model line. I appreciate the offer to help with my non-functioning CEC. My logs are below:

Dmesg
http://ix.io/1J7y

Kodi log
http://ix.io/1J7z

Some editor has a setting for change tab to spaces on the fly. But they don’t mix anything with the correct setup. I use several windows editor without any problem and they can handle unix style line end too.

Yes, I have disconnected the C2 and replaced it with the N2 and CEC was still non-functional. I’ve not tried a complete unplug of the TV to hard reset it as I’ve heard CEC issues can be persistent.

Unless you have any other ideas I will try that tonight. Others have reported LG OLED models CEC working just fine so its something on my end it would appear.

CEC has been wonky for me with an lg on the n2.
Can’t remember if it’s a 16 or 17 model but it’s not an oled.
When the avr turns on and activated hdmi arc.
CEC stops working for about 20 seconds.
When it starts again all of the inputs pressed whilst it wasn’t working get sent at once.
It’s then slow to respond and double presses for about 20 seconds more then begins working normally.
If you don’t press a key for about a minute it seems like CEC goes to sleep.
When I press a key it then takes about 10 seconds before CEC starts working again.
Sometimes when turning on the tv, CEC will not work at all, have to switch input and switch back or sometimes have to power cycle the tv.
Never had these problems with the c2.

I have a B7 OLED too. All good here.

When I ssh into the box to create autostart.sh and then disconnect. When I smb into the box, the file is saved as : autostart.sh.save.

Is this normal? Did I mess a step up?


Ssh and use following commands:

echo "echo 0 > /sys/module/di/parameters/nr2_en" > /storage/.config/autostart.sh

Simple enough! Will try this later! Sounds like that would work.

To confirm (because it was told differently before).

The zero itself . Is it 0 or ‘0’ ?

Thanks

To append the file (if you already have something in it), you can use >> instead of >.

use the exact command I posted (copy/paste)

Kodi log should be a debug log with the CEC component log enabled. These logs don’t help.

More important is kernel log:

echo 0 > /sys/class/aocec/dbg_en
systemctl restart kodi
dmesg|paste

Also make sure to use a direct connection to the TV and disconnect all other HDMI devices.

Thanks for the trick. It seem to be ok.:grinning: