I also still have a hd ready 720p in the house. How to solve the issue: buy a new TV.
The time for hd ready was S805 and before.
1 Like
Sure, that is the option, or I can rollback to previous version and wait for microLed technology to be availableâŚ
Hi, I have a problem with the pvr and some channels at 8-14h, the image starts to go in slow motion and to solve it, I need to restart the tvbox.
I tried to restart tvheadend, restart kodi with systemctl stop and start kodi, but only resolves the issue rebooting.
It is a problem that has been dragging all the versions of coreelec that I have tried.
Any ideas?
The tvbox that i tried with same problems was mecool ki pro, ki plus, and kiii pro
thanks
Hello, tanix tx3 mini wonât display wireless networks , any solution ? Thanks
@paulopais Tanix TX3 mini has a cloned Realtek WiFi chip and there is no driver available so it will never work, plenty of posts regarding this already.
i bought a new one, my older tanix tx3 mini wifi works, the chip has changed?
These TX3 Miniâs came out with 2 Chips.
9082xs Chip will never work
SSV6051 Chip will work
1 Like
Hi there,
i have a curios question,maybe someone can reproduce it. I have a couple of movies (4k - x265 - 4096x2160) and if I look them on 9.2.1 after a couple of minutes my eyes hurts, tears a little bit and it seems that the picture has a high pitched flicker (donât know how to descripe this). Movies 1080 or 3840x2160 in 4k doesnât have this effect. But on 9.2.0. the 4096 4k movies plays fine and normal. so I went back to 9.2.0. Any ideas?! Its all played on Odroid N2 and a Sony 4K HDR 65"
Have a read over here
1 Like
AhâŚokâŚso my display is only for 3840x2160 ⌠and it cannot handle 4096! if I now go back to 9.2.1. and limit the resolution in the whitelist to max. 3840 it should be displayed correct?! Correct?! 
BTW: Thanks for the link, I ve searched everywhere but this (to me) old website from a long time ago I was making SVCDs, doesnât pop up in my mind ;))
Hello guys
Installed the latest version to Tronsmart Vega S95 and booted from SD. Configured it and it seemed to work. Unfortunately when I left it half day without touch (it repeated 3times what means everytimeâŚedit:now after 2hrs problem introduced again, grrr) and later tried to open IPTV, box is completely without the connection. Using WiFi (Ubnt Unifi AC router) connection which shows âfailure/failedâ state (all other WiFi clients have no issues so not a router problem). Wifi reconnection doesnât work, Kodi restart the same failure behaviour. Only box reboot fixed the issue.
How can I create log without no option to ssh into the box, no possibility to create debug log via CoreElec Menu which will fail during the upload and url creation (logically), dmesg is cleared after fresh restart, etcâŚ
Can anyone help? Does anyone have similar behaviour? Are there any option how to create logs locally so after reboot I can manually upload here?
Thank you!
I presume you have an S905 chip ?? Please disclose your hardware instead of these mish mash Chinese model descriptions. Donât feel like Googling these names to find your chip 
Disclose the DTB.IMG you used to match your hardware.
Hello. Yes sorry, it is S905 chip with 2/8GB, wifi module: Broadcom AP6330 (Vega S95 Meta).
HW specs:
DTB.IMG:
Tronsmart Vega S95 S905 2G gxbb_p200_2G_1Gbit
Thank you
Once youâre connected via WiFI
SSH into the box and run command
udevadm info /sys/bus/sdio/devices/sdio*
You mean anytime or after reproducing the problem (after restart)? As it seams output will be same during working state or clean restart, posting it now (it is weird I canât reproduce it now but had not much time to test it more deeply):
CoreELEC:~ # udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4330
E: MODALIAS=sdio:c00v02D0d4330
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=9004283
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
L: 0
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4330
E: MODALIAS=sdio:c00v02D0d4330
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=9005408
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
CoreELEC:~ #Thank you!
Reproduced it after I re-enabled bluetooth so it seems bluetooth âbackground refreshes?â lead to wifi failure after a while.
When wifi connection is in failed state it is still possible to do ârefreshesâ for surrounding wifi and bluetooth devices so hw seems not totally dead but canât be reconnected again until box reboot.
As device is with no connection, it is not possible to create report and I suppose reboot clears dmesg so no possibility to create offline log available after reboot?
Thank you
When I was using Libreelec with Minix NEO U9-H I could get BT2020. Is there anything I need to do to enable BT2020 with Coreelec
Hello, back again, reproduced it again, with bluetooth disabled so it wasnât root causeâŚ
@kostaman @coreelecteam
When Wifi status got failed with no option to reconnect, I shared WiFi via mobile hotspot and was able to connect to it. Internet worked in tvbox but it is not possible to generate âKodi logsâ unfortunately (1st option).
I was able to create âKodi crashâ link and also link without logs (3rd option), but first option always failed (Failed to paste log files, try again), until reboot.
Linking logs in order:
- kodi crash log (reconnected to other wifi-mobile hotspot): http://ix.io/27hF
- without logs: http://ix.io/27hG
- kodi logs : canât create link-failed to paste files
- reboot at 06:20 - it fixes wifi problem, box is reconnected (to wifi which was failed before reboot) and link creation for âKodi logâ works (1st option)
- kodi log (unfortunately log timestamp starts after reboot, logically): http://ix.io/27hH
- kodi crash log: http://ix.io/27hI
Do you see anything in logs or there is other option how I can get Kodi (non-crash) log? I am not sure the differences between Kodi log vs. Kodi crash log but I suppose they are different and if Kodi didnât crashed when wifi failed, such log will be useless?
Thank you!
Can you try latest nightly.
I canât keep up with all the chip driver updates but i think there was un update for yours.
Nothing to lose by trying on SD Card.
@kostaman
Thanks for info. Updated to the ânightly_20200112â but same error.
I found out that traversing LOGFILES SMB folder generates logs locally (zipped) so I created media source in KODI directing to it via LOCALHOST and it worked to generate logs without network!.
Please let me know which log you need from ZIP file.
Pasting here relevant part from â02_System.logâ:
[12112.484106@1] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND
[12112.484148@1] link down if wlan0 may call cfg80211_disconnected. event : 6, reason=6 from ec:41:18:bb:ac:21
[12112.485865@1] wl_iw_event: Link Down with BSSID=ec:41:18:bb:ac:21
[12112.485965@1] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
[12112.488070@0] cfg80211: Calling CRDA for country: CN
[12112.490736@1] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[12112.497347@2] Connecting with ec:41:18:bb:ac:21 ssid âMyUnifiWifiâ, len (13) channel=6
[12112.497347@2]
[12112.839679@1] wl_iw_event: Link UP with BSSID=ec:41:18:bb:ac:21
[12112.839722@1] wl_bss_connect_done succeeded with ec:41:18:bb:ac:21
[12112.934849@0] wl_bss_connect_done succeeded with ec:41:18:bb:ac:21
[20276.105012@3] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND
[20276.105055@3] link down if wlan0 may call cfg80211_disconnected. event : 6, reason=6 from ec:41:18:bb:ac:21
[20276.106859@3] wl_iw_event: Link Down with BSSID=ec:41:18:bb:ac:21
[20276.106966@3] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
[20276.109574@3] cfg80211: Calling CRDA to update world regulatory domain
[20276.116578@0] Connecting with ec:41:18:bb:ac:21 ssid âMyUnifiWifiâ, len (13) channel=6
[20276.116578@0]
[20276.458700@3] wl_iw_event: Link UP with BSSID=ec:41:18:bb:ac:21
[20276.458744@3] wl_bss_connect_done succeeded with ec:41:18:bb:ac:21
[20276.563563@3] wl_bss_connect_done succeeded with ec:41:18:bb:ac:21
[20421.237107@3] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND
[20421.237133@3] link down if wlan0 may call cfg80211_disconnected. event : 6, reason=6 from ec:41:18:bb:ac:21
[20421.238802@3] wl_iw_event: Link Down with BSSID=ec:41:18:bb:ac:21
[20421.238844@3] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
[20421.240221@0] cfg80211: Calling CRDA to update world regulatory domain
[20421.245797@0] Connecting with ec:41:18:bb:ac:21 ssid âMyUnifiWifiâ, len (13) channel=6
[20421.245797@0]
[20422.227357@3] connect failed event=0 e->status 3 e->reason 0
[20422.236156@3] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection
I found lot of exactly same problems via google search, like:
https://devtalk.nvidia.com/default/topic/1036987/r28-2-wifi-in-tx1-disconnect-sometimes/
https://discourse.osmc.tv/t/losing-wifi-signal-after-a-while/80511/29
It seems problem mainly reproduces in environment with Wifi Mesh system. True in my case as my one SSID hides three different MACs (2.4/5GHz bands + another 2.4Ghz only ârepeaterâ with the strongest signal which uses my TVBox).
As stated in the second link, it seems there are buggy drivers or bug directly in kernel as user was able to fix it by reverting to the older fw. Other workaround was to restart ânetwork-managerâ or other advice was to update itâŚ
Hopefully it will help finding the root cause and fix it or a find a workaround?
Thank you!