Posts by madmalkav

Non-update update: I haven-t had any time to work on this. Current DTS works OK if you don't try to use WiFi or BT and if you have good cooling. I will perhaps come back to try to make it work with the new images based on kernel mainline in a month or two. No promises. Anyone can continue from where I left with the files linked, if someone wants to try to do a quick file to get remote support without compiling I can try to help with that.

Please open another thread to ask for advice on your device.

You need proper DTS file for your box.

Sorry for not replying sooner, life's being a bitch lately and I barely have any free time. I was thinking that probably we can use the generic nightly build with the DTS file and a keymap file instead of compiling the keymap with the kernel, so that way we can test nightlies with minimal effort. To be honest, I'm not sure how to fix stuff like what theAlevan reported, and probably it is not specific to our device anyway.

A lot of devices including mine use that wifi chip without problems. But the DTS need to have the correct info on how the chip is connected on the device to work. And you can't just copy Android DTS info to the Linux DTS info, because they are mapped differently. I'm probably not explaining it very well but if you take a look to some DTS that are not decompiled but properly written i.e. in the kernel code you will probably see what I mean.

I did clone Libreelec to my computer, I didn't fork it. I plan to fork , apply my patches, upload to github and do a PR to LibreElec as soon as I have ironed out some stuff. My goal is still to mainline this if possible. I will share the links here as soon as possible.

Updated first post with info on how to use MCE type remote with the embedded IR receiver. Getting closer...

ukmark62 I'm myself not very familiar with this process. I started working based on a DTS file available in Armbian forum. To compare values with Android, I connected to the device running Android with adb and copied the info on /sys folder . If there is any other dtb with working wifi , even if it is a disaster in every other aspect, I suggest to extract the DTS or ask balbes150 for the DTS file and try to copy the wifi section from one to the other.

Updated first post with new information about whitelist.

Updated with some aditional info about BT and suspend.

buximze I've been testing and definitively seems my issue was caused by poor cooling. Also, when it fails on my box, audio continues but video never ever catch up, so I don't think it is the same issue.

My unit gets way hotter than that on similar room temp, I will have to investigate why.

Sorry for the lack of upgrades, life being a bitch lately, I hope to get some spare hours to continue working on this soon.

Am I getting blind or theAlevan 's last post is completely blank?

Thanks for reporting back. I feel really curious about why I seem to have far more unstable playback than you

Can you please verify if you can enable 24p output modes? I don't know if this is a real problem or just my test setup won't support it and therefore LE doesn't show it.

Also, can you connect by SSH and see the cpu temperature with cputemp at the middle of a playback? What is the ambient room temperature aprox?

Thanks for the info. Will keep investigating the issue.

The thread you linked talks about problems with 4.19 kernel , but rockchip images uses kernel 4.4 , so probably not related.

Anyway, I have also found some playback issues that seems to only happen when using SMB on my attempts to get A5X Max tv box supported. I haven't tested deeply enough to confirm that is the case but it certainly seems possible.

Got bundled remote working OK. Also tried with a MCE remote, but it didn't work out of the box as it seems rc6 protocol is not enabled by default on RK3328 devices?

Anyway, I'm updating the first message of this thread with current status and ToDo list.

You watched it from SMB share or USB drive?

After about 50 minutes of playback, video freezes, but audio continues, and the GUI remains responsive. Tried changing to interactive cpu governor but the problem remains.

I'm currently out of ideas on how to solve the known issues and finding new ones, any ideas would be really appreciated.

Thanks to vpeter and chewitt for they patience and support on IRC.

My initial dts file was garbage, but I got a promising one from user armar in Armbian forums.

In this one, network, wifi and bluetooth work, playback works OK, USB 3.0 drives seems to give the expected speeds,... The things to improve are:

- Seems when BT is used, Wifi and BT becomes unstable / have cuts. On the armbian forums an alternative firmware is proposed and seems to solve the issue, I'm trying to figure now where does LibreElec grab the firmware it uses to see if it is an older / newer / alternate version.

- IR still doesn't work. I have modified the dts file to set it the PWM entry to: compatible = "rockchip,remotectl-pwm"; I have also added to the kernel config CONFIG_ROCKCHIP_REMOTECTL=y and CONFIG_ROCKCHIP_REMOTECTL_PWM=y . Dunno why it doesn't work. Any idea on how to fix it or at least debug it would be appreciated.

Even if this dts file seems pretty good, I can see differences between the info in this file and the devicetree info in /sys on my device , so I think there is room for improvement.

If I can fix those two issues (BT / Wifi stability and IR ) , I will try to make the dts into something that can be merged and try to iron up some other minor issues (wifi interface seems duplicated in two devices, wlan0 and p2p0 , trying to move the IR support to Linux instead of having the keymap in the dts, ...)

Current version of the dts file available at: GitHub - madmalkav/TV-Box-DTS

PS: I don't have a way to test CEC , analog audio out or SPDIF.