Nightly builds (NEW)

Hi, how to set custom resolution properly?
tried to change paarameter config.ini 1680x1050p60hz and modeline= (copy from xrandr info), I’d activate vesa mode setting coreElec, but still no luck.

I installed to emmc the Generic version of the new NG build on my old S905X box and everything work fine except performing a hard or soft reset to clean the CE storage :slight_smile: When trying to reset, the box just reboot without removing anything from storage.

After digging a little bit I guess the issue is related to get_target() function from /usr/lib/coreelec/factory-reset file failing to find the target device parsing /proc/cmdline
The get_target() function expect disk= in command line to start with either LABEL=, UUID= or / but in the failing case it is starting with FOLDER= (full disk for failing case is disk=FOLDER=/dev/CE_STORAGE)

I tried both 9.2.4.2 build as well as 20201011 nightly build and both show same failing result when trying to reset.

Full /proc/cmdline used for 9.2.4.2 is here http://ix.io/2AEn and for nightly build here http://ix.io/2AEq

JakeTri, thanks for this complete analysis. You are right, the script doesn’t cover installation to eMMC. I have solution ready but first attempt failed with wiped Android :frowning: I have to recover it and test again to confirm that solution is correct.

Thank you for looking into this…
Sorry for being lazy and provide only the analysis but I not have time right now to work on a potential patch / solution as well…

1 Like

@vpeter

I am unable to replicate this on a NexBox A95X-B7N (S905X) 1/8 running CE-ng 9.2.4.2 stable from eMMC

Betatester: Do you have dual boot with Android? I think the issue happens only in this case.
Can you check /proc/cmdline if you have disk=FOLDER=/dev/CE_STORAGE.

@vpeter

Yes, dual boot.

Created full system and Kodi backup to external USB with CE backup tool.

Performed soft reset. System restarted and went through its soft reset cycle. System restarted again and I was greeted with the red Welcome to CoreELEC screen. My media were untouched.

Restored from backup, rebooted and found my previous configuration restored.

Performed hard reset. System restarted and went through its hard reset cycle. System restarted again and I was greeted with the red Welcome to CoreELEC screen. My media were gone.

Restored from backup, rebooted and found my previous configuration and media restored.

System: NexBox A95X-B7N 1/8 running CoreELEC-ng 9.2.4.2 stable in dual boot with Android 7.1 (Nougat) from eMMC.

Unable to replicate following error during 5 consecutive attempts:

Conclusion: CoreELEC-ng 9.2.4.2 Stable works as intended on a NexBox A95X-B7N (S905X) 1/8 when performing a hard and/or soft reset via the CoreELEC configuration addon.

@Betatester

I’m using single boot configuration and installed CE-ng via ceemmc -x on top of Android 7.1 rom on A95X 2/16 box.
The /proc/cmdline generated for booting from eMMC used disk=FOLDER=/dev/CE_STORAGE vs the one for booting from USB / SD disk=LABEL=STORAGE ( there is special case in the cfgload script for this )
The script that perform soft/hard reset does not handle the FOLDER case so it is just restarting the box without performing the reset operation as it does not find the reset target.

Check with file explorer if you have CE_STORAGE mounted. If yes, unmount. See if that makes a difference.

Anyway, the fix is send: https://github.com/CoreELEC/CoreELEC/pull/263

Tested on Beelink GT King Pro.

1 Like

@vpeter, just tested a local build with your fix on my A95X box and confirm fixing the issue.

Thank you!

1 Like

@vpeter

I presume this issue only affects some boxes then?

From what i know about dual boot installation it is done in same way on all boxes. That’s why I can’t understand why it would work on some boxes and not on others.
When folder is used for storage it is subfolder from Android data partition. In this case partition can’t be recreated but files must be manually removed. And this case was not covered in factory reset. This is for hard reset: soft reset was not affected.

That’s what I am trying to figure out myself. Right now I am leaning towards file permissions.

Then try this:

mkdir mount_storage1
mkdir mount_storage2
mount /dev/CE_STORAGE mount_storage1
mount /dev/data mount_storage2

You should see same content inside like

drwx------    2 root     root          4096 May 25 17:13 adb
drwxrwxr-x    2 1000     1000          4096 May 26 12:06 anr
drwxrwx--x    6 1000     1000          4096 May 26 12:06 app
drwx------    2 root     root          4096 May 25 17:13 app-asec
drwxrwx--x    2 1000     1000          4096 May 25 17:13 app-ephemeral
drwxrwx--x    2 1000     1000          4096 May 25 17:13 app-lib
drwxrwx--x    2 1000     1000          4096 May 25 17:13 app-private
drwx------    6 1000     1000          4096 Oct  3 15:40 backup
drwxr-xr-x    2 2000     2000          4096 May 25 17:13 bootchart
drwxrwx---    5 1000     2001          4096 May 25 17:13 cache
drwxr-xr-x   19 root     root          4096 Oct 18 16:16 coreelec_storage
drwxrwx--x    3 root     root          4096 May 25 17:13 dalvik-cache
drwxrwx--x   87 1000     1000          4096 May 25 17:14 data
drwxrwx---    3 1019     1019          4096 May 25 17:13 drm
drwxrwx--x    2 1000     1000          4096 May 25 17:13 droidota
drwxr-x--x    4 root     root          4096 May 25 17:14 local
drwxrwx--x    3 1007     1007          4096 May 25 17:13 log
drwxrwx---    2 root     root         16384 May 25 17:13 lost+found
drwxrwx---    4 1023     1023          4096 May 25 17:13 media
drwxrwx---    2 1031     1031          4096 May 25 17:13 mediadrm
drwxrwx--t   42 1000     9998          4096 May 25 17:13 misc
drwxrwx--t    3 1000     9998          4096 May 25 17:13 misc_ce
drwxrwx--t    3 1000     9998          4096 May 25 17:13 misc_de
drwxrwx---    3 1027     1027          4096 May 25 17:13 nfc
drwxrwx--x    2 root     root          4096 May 25 17:13 ota
drwxrwx---    2 1000     2001          4096 May 25 17:13 ota_package
drwx------    2 root     root          4096 Oct  3 15:40 property
drwxrwx--x    2 1000     1000          4096 May 25 17:13 resource-cache
drwx------    2 1000     1000          4096 May 25 17:13 ss
drwxrwxr-x   19 1000     1000          4096 Oct  3 15:40 system
drwxrwx---    3 1000     1000          4096 May 25 17:13 system_ce
drwxrwx---    3 1000     1000          4096 May 25 17:13 system_de
drwxrwx--x    2 1000     1000          4096 May 25 17:13 tombstones
drwx--x--x    2 1000     1000          4096 May 25 17:13 user
drwx--x--x    3 1000     1000          4096 May 25 17:13 user_de
drwxrwx--x    6 root     root          4096 May 25 17:13 vendor
drwxrwx--x    3 root     root          4096 May 25 17:13 vendor_ce
drwxrwx--x    3 root     root          4096 May 25 17:13 vendor_de

and the most important is folder coreelec_storage which is mounted to /storage.

I try this from where? Android Terminal, Secure Shell? Can you please elaborate? Thank you.

Model: Mecool M8S Plus DVB
CoreELEC-Amlogic-ng.arm-9.2-nightly_20201019
GXL p231

Is running with black screen and with this error in dmesg:
failed to allocate memory for node linux,meson-fb, size:8 MB

dmesg.txt (71.9 KB)

I keep having network related problems with playback, particularly easy to reproduce using the music player’s Party mode. Enable party mode and skip to the next song until the player goes all wonky and refuses to play anything. It just keeps scrolling through the list until I use the X key to stop it.

This is what repeats in the log in that situation:

2020-10-23 20:43:20.330 T:3918496640 WARNING: PAPlayer::QueueNextFileEx - Failed to create the decoder
2020-10-23 20:43:20.376 T:3578037120 ERROR: Open - Unhandled exception
2020-10-23 20:43:20.376 T:3578037120 ERROR: Open - Error opening nfs://192.168.0.75/volume2/Music/Faith No More/The Real Thing/06 The Real Thing.ogg
2020-10-23 20:43:20.376 T:3578037120 ERROR: Init: Error opening file musicdb://songs/11973.ogg
2020-10-23 20:43:20.376 T:3578037120 ERROR: CAudioDecoder: Unable to Init Codec while loading file nfs://192.168.0.75/volume2/Music/Faith No More/The Real Thing/06 The Real Thing.ogg

The NAS is online and no problems accessing it. I switched to NFS shares today to test, but it’s as bad as SMB.

Is there anything I could do to make it work better? I have a big library and it would be nice to be able to skip songs as needed. The same issues are probably causing problems with playback of videos over the network, I’ve reported those in this thread a few times I think.

Known dtb issue. S902 dtb’s are faulty.

I got a debug log here, couldn’t use pastebin as the file is too big.
https://drive.google.com/file/d/1HNPX0Xc_2VRMBDi7Kplmf_TKtoM3sRfV/view?usp=sharing