Same problem here with a Odroid N2 with 19.4 RTM and also latest nightly (20220315). I too have an LG TV!
No logs for now.
@Compent please update with this “dirty” build:
After update try again if suspend is working.
Or you use 19.4 release and run in SSH:
echo "0" > /sys/devices/platform/aml_pm/time_out
Then try suspend
I updated this on top of the clean install.
I have never used the suspend feature before but I ran it and it seemed to suspend for about 20 seconds before waking up but giving me a black screen, although I can see that the TV is seeing the box. I can ssh into it and reboot from there. I also tried the power off funtion again and it rebooted.
Latest dump http://ix.io/3SnL
It’s somehow related to your Android image. And your device use some gpio different to standard. So if it goes down it check this gpio and resume as it think like power button pushed.
Helpful will be you open your box and attach real UART line so bootloader messages are recorded as well. It will tell us the reason for wakeup.
It’s not had Android installed for a long time now, so I think that can be ruled out.
But yes, I agree that UART will be required to solve it.
Thanks for your help.
Here’s todays logfile of the problem with activated libcec component logging: ix.io/3Sy0
System was booted, a movie was watched and afterwards CEC connection was lost (tried to stop the movie manually when the credits began).
Please just test this devel build if something change, what I do not think. But just please have a try: 229.77 MB file on MEGA
I gave it a try and it had the same results as before.
Thank you.
I’ll look into getting a UART bridge board.
1 Like
My last post about successfully solving the random CEC wake-up issue in 19.4_rc3 by uninstalling some plugins was incorrect. The issue goes on also in 19.4 final release. Now I am testing the 19.5-Matrix_nightly_20220315 build from a SD card and I have not noticed any CEC wakeups within the last 30 hours (or so) yet. However, it has other issues, as expected 
Moving from 19.3 on the N2 there are combing artifacts over faces and things that are moving watching interlaced broadcast TV.
The effect looks identical to when /sys/module/di/parameters/bypass_all is set 0 in 19.3.
Setting bypass_all to 1 no longer seems to have the same an effect in 19.4.
Anyone know of a different way to move it back?
I’m having some issues with my Odroid n2+ when booting via NFS on 19.4 (on 19.3 it boots fine). I’m just getting a black screen then it reboots so I’m not able to see what’s going wrong, something to do with the NFS upgrades done in 19.4 ?
Any suggestions on how to debug this ?
I have also had problems with my n2 not always powering on and off correctly from Harmony remote. I followed your instructions but on sp1 the screen froze. After changing back to eMMC boot everything working well so far. Is that the correct procedure to follow?
I started a thread in the SBC N2 section some time back regarding playback issues after listening to multichannel audio. Lots of views, but no answers, unfortunately.
I’m on the 19.4 nightlies updated on my eMMC and and after I play a 5.1 or 5.0 FLAC audio track (I have a number of multichannel albums ripped from my SACD/DVD-A collection at 88.2kHz or 96kHz), then I can’t play back a regular 2.0 FLAC audio (ripped from CD at 44.1kHz), nor can I hear the GUI navigation sounds. I can play any number of 5.0 or 5.1 tracks successfully but I don’t hear GUI navigation between selecting albums.
In order to restore navigation sounds (and 2.0 CD format playback), I have to play a 2.0 track at 48kHz or above. Anything which is not at 44.1kHz will do - internet radio MP stream at 48kHz (BBC radio), high definition stereo audio at 88.2/96/176kHz will restore navigation sounds and normal stereo FLAC playback.
I burned an SD card with a clean 19.4 nightly and also 19.4 stable and I have the same issue. The legacy 9.2.8 works perfectly but this is EOL, so no point 
I’m using an N2+, so it’s the recommended hardware platform. I’ve been using this box successfully with prior builds. I can’t say for definite when the problem started, but it’s in the 19.4 stable.
The 19.4 log - http://ix.io/3RIU
The 9.2.8 log - http://ix.io/3Sz1
I see lot of USB issues which probably cause some issue in kernel later.
Can you upload 2 samples (5.1 and 2.0) and also tell us which audio output you have selected in Kodi.
And next time please reboot the device to get started from clean state.
N2+ running CE 19.4 stable
- Play multichannel flac (Testfile 24Bit 96KHz 6 Channel)
- Play any regular flac (CD rip)
- Play again multichannel
- Play again regualar flac
- Play DTS audio file
- Play .dsf file
.
.
.
The USB issues are caused by the fact that my N2+ has a “fried” USB3 controller since new. I don’t use the USB3 ports on the box. I just the USB2 OTG port on the front for the RF remote. I use the 7.1 Mch PCM HDMI output in Kodi as always. I have been using the same FLAC files for years, first in LE and now since CE got multichannel PCM working on the N2. The files work perfectly in 9.2.8, so I think it’s something to do with the audio driver or configuration as it seems to enumerate the ALSA devices three times ar startup in 19.4. Both logs are from clean boots.
Thanks for confirming that you can play 24 bit 96kHz 6 channel file followed by regular CD rip on 19.4 stable. There must be some issue on my setup between my N2+ and my Sony DN1060 AVR which is different between 19.4 build and 9.2.8. It’s very strange. On the 19.4 build I can see the AVR reporting “2.0 44.1kHz” format messages every time I press the BACK key on my remote. It’s as if there is some audio format change happening all the time. I have no issues at all with the 9.2.8 EOL build.
I don´t know about Sony AVR.
My setup is N2+ connected to my Denon AVR-X3300 via HDMI cable
1 Like
Can I ask if I can suppress checking of the USB3 controller? It’s definitely not working as it was one of the earlier N2+ boxes which blew up the controller due to USB power issues.
Also, why do I see a Bluetooth device (Pulseaudio) detected at startup? There is no Bluetooth or WiFi on the N2, unless you use a USB dongle.
Enumerated PULSE devices:
2022-03-08 19:02:21.091 T:5359 INFO : Device 1
2022-03-08 19:02:21.091 T:5359 INFO : m_deviceName : Default
2022-03-08 19:02:21.091 T:5359 INFO : m_displayName : Default
2022-03-08 19:02:21.091 T:5359 INFO : m_displayNameExtra: Bluetooth Audio (PULSEAUDIO)
2022-03-08 19:02:21.091 T:5359 INFO : m_deviceType : AE_DEVTYPE_PCM
2022-03-08 19:02:21.091 T:5359 INFO : m_channels : FL, FR
2022-03-08 19:02:21.091 T:5359 INFO : m_sampleRates : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
2022-03-08 19:02:21.091 T:5359 INFO : m_dataFormats : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT