I’m having issues with frames being dropped. Before I ask for troubleshooting I want to make sure I get all the relevant logs so that I can get help. What log settings should I have turned on and which logs do I need to share to dig in properly?
Thanks
Hi,
Anyone else seeing this on boot ? It goes back to normal after a few seconds. Running latest ng nightly.
It does the same for me w/NG build 20250205. Video here.
Thanks, so setting HDR to “auto” on Android is supposed to fix this, right ? Is this fixed with Android 14 ? (Still waiting for the update…)
The “Dune HD Homatics Box R 4K Plus” has two USB ports: one USB 2.0 and one USB 3.0
I was connecting the external HDD with the MEDIAs/VIDEOs… to the USB 3.0 port.
And connecting the USB Flash Drive with the CoreELEC to the USB 2.0 port.
It didn’t work with any BOOT method.
Now I connected the USB Flash Drive with the CoreELEC to the USB 3.0 and it worked!
But there is a problem: the remote control of the “Dune HD Homatics Box R 4K Plus” did not work.
I’m stuck at the initial CoreELEC configuration screen.
Doh, i cannot even enter the Video & Audio settings Android; the app just crashes:
02-11 23:49:46.482 4461 4461 D AndroidRuntime: Shutting down VM
02-11 23:49:46.483 4461 4461 E AndroidRuntime: FATAL EXCEPTION: main
02-11 23:49:46.483 4461 4461 E AndroidRuntime: Process: com.android.tv.settings, PID: 4461
02-11 23:49:46.483 4461 4461 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.contains(java.lang.CharSequence)' on a null object reference
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.tv.settings.util.CustomizationUtil.searchNewUsbDevice(CustomizationUtil.java:470)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.tv.settings.device.displaysound.DisplaySoundFragment.configShowLedPref(DisplaySoundFragment.java:369)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.tv.settings.device.displaysound.DisplaySoundFragment.onCreatePreferences(DisplaySoundFragment.java:348)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.preference.PreferenceFragmentCompat.onCreate(PreferenceFragmentCompat.java:161)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.tv.settings.SettingsPreferenceFragment.onCreate(SettingsPreferenceFragment.java:91)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.Fragment.performCreate(Fragment.java:2939)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.create(FragmentStateManager.java:451)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:254)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2209)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2120)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:2022)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:527)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7839)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
02-11 23:49:46.483 4461 4461 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1006)
02-11 23:49:46.489 614 629 W ActivityTaskManager: Force finishing activity com.android.tv.settings/.MainSettings
Anyone knows what i should type to set HDR to auto from the command line ? I only found the following stuff which seems related:
$ adb shell
$ settings list global | grep hdr
nrdp_platform_capabilities={
"vp9Disabled": "false",
"hdrOutputType": "always",
"minVideoFramesForPlaybackStart":"11"
}
...
user_disabled_hdr_formats=
If anyone who managed to set the proper value could look at settings get global so that i can determine what to put, that’d be nice.
Thanks !
Use forum search!?
If connected to a TV, your TV remote can’t be used by CEC?
I was able to use a wireless keyboard with touchpad.
Although the keys don’t work correctly (sometimes I press a letter and another one appears), I managed to do the initial configuration of CoreELEC using the touchpad and the keyboard arrows (UP, DOWN, LEFT, RIGHT).
I was able to connect the bluetooth remote control of the “Dune HD Homatics Box R 4K Plus” by pairing it in the CoreELEC settings.
Some doubts:
The “USB Flash Drive” with the CoreELEC only worked on the USB 3.0 port.
The external USB 3.0 HDD with MEDIA/VIDEO files does not work very well connected to the other USB version 2.0 port.
On the last question, that may be flash drive dependent. The SEI s905x4 boxes can boot CE from the USB2 port. Maybe some flash drive models are only able to boot from the USB3 port?
I was only able to boot for the first time to install CoreELEC using the USB 3.0 port (maybe it’s not even because it’s USB 3.0, but because it’s port 1, for example).
With CoreELEC already installed on the “USB Flash Drive” I connected it to the USB 2.0 port and CoreELEC booted.
Maybe the first boot that needs to be on the port which, coincidentally, is a USB 3.0 port.
Maybe it has something to do with USB debugging on Android TV.
I got an update of my homatics box r 4k plus from Android 12 to Android 14, now it no longer boots the USB stick with corelecc, do I have to install a new corelecc version on it or does it no longer work because of Android 14, the USB debugging is activated under Android 14, I look forward to an answer Thanks
There was a CE-NG fix to boot with ATV14 in mid-january
It may have made it into CE-NG 21.2 stable, if not it’s in the nightlies now.
So I downloaded 21.2, put it back on the USB stick with Rufus, renamed the file and tried it as follows
PowerOFF the device and remove the DC power connector (or remove the power adapter from the wall socket )
Press and keep pressing the reset button ,then Power ON the device while keep pressing the reset button until the CoreELEC screen will appear .
Release the Reset Button
The problem is it doesn’t boot, new windows keep appearing which often change the resolution and then it says revocation mode USB hot mode etc… press rest again for revocvery etc
Do I have to boot it differently because of Android 14 or do I have to connect a keyboard to the box and then press something specific to get to a menu?
Try the latest ce-ng nightly,
Either boot to Android and issue adb shell reboot update or use the reset button as you described.
I try hit same problem with this option no coreelec icon black screen and usb hot mode…whatever that may mean
PowerOFF the device and remove the DC power connector (or remove the power adapter from the wall socket )
Press and keep pressing the reset button ,then Power ON the device while keep pressing the reset button until the CoreELEC screen will appear .
Release the Reset Button
Strangely, it worked without any problems under Android 12, well, I’m afraid I have to pass on the adb shell reboot update, I have no idea how to enter this command under Android, I’ve just tried the Reboot to CoreELEC 5.0 tool, unfortunately that doesn’t work either, it hangs on the Homatics initial logo… well, we’ll see, there is unfortunately no tutorial for Android 14 either, because I really suspect that I might have to connect a keyboard and then press something to get into the reboot mode and then possibly select something so that it then boots from the USB stick.
The adb command and/or the Reboot to CoreELEC 5.0 apk both working fine under ATV12 or 14. You just need correct install that. CE nighlies works and boot too, when you correctly write the image to the pendrive , and rename the correct dtb.
The installation same on any ATV version.
You can try the usb2 port.
I don’t know what mistake I made, I did it the same way as usual, tried omega 21.2 and the nightly, under Android 12 after 10/14 second i had the CoreELEC icon when I held down the reset button etc., now it doesn’t work, there’s a catch somewhere is Devices S905X2 4G (1GBit) must be correct or ?
About | FAQ | Terms of Service | Privacy Policy | Legal Notice