[fritsch]

Can you send it back?

Hello sorry i don't understand your question
What shall I send back ? The log link is in my previous post 

From the log I have seen this firmware crashes when probing supported formats. If your project has a "headphone" plug. Plug something in there (change output in android settings to analog) and check if kodi starts. I am not kidding.

[regisl]

If you can't: plug in a headphone.

Hello if I plug the bluetooth headphones yes kodi 18.5 starts !
Is that possible to get a fix and not to use the headphones ?
Thanks !

[fritsch]

Ask your firmware vendor. He has to fix it.

[fritsch]

If you have adb access, give me adb logcat please from the crash - curios where exactly it happens.

[regisl]

I bought it in Nov 2019

[regisl]

If you have adb access, give me adb logcat please from the crash - curios where exactly it happens.

I actually already posted it in the thread, please find the link:
https://paste.kodi.tv/doyetohilu.kodi

[fritsch]

12-07 12:29:23.952  3972 14560 I AudioPolicyManager: getOutput() returns new direct output 8371
12-07 12:29:23.952  3972 14560 I power   : acquire_wake_lock lock=1 id='ApmOutput'
12-07 12:29:23.952  3972  4067 I power   : release_wake_lock id='ApmOutput'
12-07 12:29:23.952  3972  3728 I AudioFlinger: AudioFlinger's thread 0xf393d000 ready to run
12-07 12:29:23.952  3972  3728 D audio_hw_hdmi: out_standby(0xf3c3ea00),out 0xf3c3ea00
12-07 12:29:23.952  3972  3728 I audio_hw_hdmi: clear out pause status
12-07 12:29:23.953  3972  3728 E audio_hw_utils: unable to open file /sys/class/amhdmitx/amhdmitx0/aud_output_chs,err: No such file or directory
12-07 12:29:23.953  3695  3724 F libc    : Fatal signal 8 (SIGFPE), code -6, fault addr 0xe6f in tid 3724 (Thread-1619)
12-07 12:29:24.055  3970  3970 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-07 12:29:24.055  3970  3970 F DEBUG   : Build fingerprint: 'MI/anglee/anglee:8.1.0/OPM5.171019.017/891:user/release-keys'
12-07 12:29:24.055  3970  3970 F DEBUG   : Revision: '0'
12-07 12:29:24.055  3970  3970 F DEBUG   : ABI: 'arm'
12-07 12:29:24.055  3970  3970 F DEBUG   : pid: 3695, tid: 3724, name: Thread-1619  >>> org.xbmc.kodi <<<
12-07 12:29:24.055  3970  3970 F DEBUG   : signal 8 (SIGFPE), code -6 (SI_TKILL), fault addr 0xe6f
12-07 12:29:24.065  3970  3970 F DEBUG   :     r0 00000000  r1 00000e8c  r2 00000008  r3 dc17f978
12-07 12:29:24.066  3970  3970 F DEBUG   :     r4 dc17f980  r5 dc17f930  r6 00000000  r7 0000010c
12-07 12:29:24.066  3970  3970 F DEBUG   :     r8 ed489c80  r9 dba83000  sl ed489ee8  fp ed489ea8
12-07 12:29:24.066  3970  3970 F DEBUG   :     ip 00000008  sp dc17eb28  lr f73ce4a5  pc f73d08a0  cpsr 400f0010
12-07 12:29:24.068  3970  3970 F DEBUG   : 
12-07 12:29:24.068  3970  3970 F DEBUG   : backtrace:
12-07 12:29:24.068  3970  3970 F DEBUG   :     #00 pc 000428a0  /system/lib/libc.so (tgkill+12)
12-07 12:29:24.068  3970  3970 F DEBUG   :     #01 pc 000404a1  /system/lib/libc.so (pthread_kill+32)
12-07 12:29:24.069  3970  3970 F DEBUG   :     #02 pc 0001cb0f  /system/lib/libc.so (raise+10)
12-07 12:29:24.069  3970  3970 F DEBUG   :     #03 pc 0000c410  /system/lib/libcutils.so (__aeabi_ldiv0+8)
12-07 12:29:24.069  3970  3970 F DEBUG   :     #04 pc 0005e8a9  /system/lib/libmedia.so (_ZN7android10AudioTrack13createTrack_lEv+1428)
12-07 12:29:24.069  3970  3970 F DEBUG   :     #05 pc 0005df95  /system/lib/libmedia.so (_ZN7android10AudioTrack3setE19audio_stream_type_tj14audio_format_tjj20audio_output_flags_tPFviPvS4_ES4_jRKNS_2spINS_7IMemoryEEEbiNS0_13transfer_typeEPK20audio_offload_info_tiiPK18audio_attributes_tb+1064)
12-07 12:29:24.069  3970  3970 F DEBUG   :     #06 pc 000a0123  /system/lib/libandroid_runtime.so
12-07 12:29:24.069  3970  3970 F DEBUG   :     #07 pc 736f3365  /data/dalvik-cache/arm/system@[email protected] (offset 0x207b000)
12-07 12:29:24.410  4220  3733 I am_crash: [4220,0,org.xbmc.kodi,948485700,Native crash,Floating point exception,unknown,0]

You can manually build kodi from source and find out which enumeration fails and remove all formats your FW does not support. As you see it segfaults in your firmware libraries.

[regisl]

If you have adb access, give me adb logcat please from the crash - curios where exactly it happens.

I actually already posted it in the thread, please find the link:
https://paste.kodi.tv/doyetohilu.kodi

Ooking very quickly : There is a fatal signal caught with audio output missing in logcat file at line 2150

[regisl]

If you have adb access, give me adb logcat please from the crash - curios where exactly it happens.

I actually already posted it in the thread, please find the link:
https://paste.kodi.tv/doyetohilu.kodi

Ooking very quickly : There is a fatal signal caught with audio output missing in logcat file at line 2150

12-07 12:29:12.724 3972 3657 I audio_hw_hdmi: clear out pause status
12-07 12:29:12.724 3972 3657 E audio_hw_utils: unable to open file /sys/class/amhdmitx/amhdmitx0/aud_output_chs,err: No such file or directory
12-07 12:29:12.725 3572 3653 F libc : Fatal signal 8 (SIGFPE), code -6, fault addr 0xdf4 in tid 3653 (Thread-1615)
12-07 12:29:12.829 3970 3970 F DEBUG

[regisl]

[quote="fritsch" pid='2906489' dateline='1575836895']

You can manually build kodi from source and find out which enumeration fails and remove all formats your FW does not support. As you see it segfaults in your firmware libraries.

Ok will try that during week. Thanks.

[regisl]

BTW: There is no issue with kodi Leia 18 as long as release used is before July 12 2018. It's apparently a function which breaks compatibility it's the addition of the "VerifySinkConfiguration() it's been already reported in kodi github:
https://github.com/xbmc/xbmc/issues/16271

Is it true that amlogic support is abandoned ?

[fritsch]

BTW: There is no issue with kodi Leia 18 as long as release used is before July 12 2018. It's apparently a function which breaks compatibility it's the addition of the "VerifySinkConfiguration() it's been already reported in kodi github:
https://github.com/xbmc/xbmc/issues/16271

Is it true that amlogic support is abandoned ?

No. AMLogic support is not abondonned. Kodi will only support valid Android methods (Mediacodec, AudioTrack, etc.) - we don't care at all about the chip vendor. If the chip vendor creates Banana Software, which is fucked up, broken, just to make money with the poor customers and then requires kodi to have SW workarounds for their inabilities, we won't do that anymore.

FireTV Cube is an AMLogic Box - all fine here, including deinterlacing. Means: If your kodi experience sucks with your AMLogic based hardware, it's entirely those that sold it to you, that don't like to ship decent SW, cause they already made money with you.

[fritsch]

I can disable passthrough entirely for all AMLogic boxes and your Android Version ... if you want that.

[fritsch]

I checked the stuff a bit and the real fun begins here:

Code:

if (aml_present() && CJNIAudioManager::GetSDKVersion() < 23)

AML told us back at this time, whenever you get API 23 boxes, everything will be fine, we will support AC3 and DTS via standard APIs. Now if you look into your logfile, you see that you have API 23 - but still require the old AML hack. Firmware crashes right away, when we try to open offical Android AC3 sinks on startup ... I don't want to hack yet another hack for yet another broken AML box in there ... so I plan to disable AML passthrough entirely for AML and version 23.

[regisl]

Fyi: I tried your fix from github without success like servo386:
https://github.com/xbmc/xbmc/issues/16271