I’m in direct contact with some TBS developers.
I am sending you the request that you described.
I hope to get a response to your request.
Because we have a private group of users who use TBS.
We would like to use SBC as khadas plus TBS.
Instead of using TBS +Linux +Tvheadend, anyone who uses TBS knows that it is perfect in linux and windows.
TBS make some nice kit and in the last couple of years they made the positive step of open-sourcing all their code and maintaining drivers in a public repo. This gets my general thumbs-up, but the next step is to get their code out of their github repo and into the mainline kernel … and I don’t see much effort or progress on that, which is a shame. Froms a distro maintainers perspective it would be nice to have DVB drivers that don’t break with every kernel bump (as with media_build).
The happiest DVB users that I know bought Digibit R1 or SiliconDust network tuners. It’s an expensive approach but the tuners support multiple “dumb” client devices around the house well and the vendors have historically provided good long-term support. If budgets are lower I would still recommend people run tuners on a separate device as this architecture allows the head-end to run an OS with a stable combination of kernel and drivers while cheap client devices run more bleeding-edge code.
1-TWRP is a specialist third party recovery app, you need to take up porting it with the TWRP project not Khadas.
2-The Android ROMs supplied by Khadas are all rooted.
3- ?
Hi VIM3L backers:
We just completed the 1st batch VIM3L SMT process, and our guys are running the QA process now and will complete it before 5th Nov on next Monday.
At the same time, CoreELEC team are optimizing the CE image for VIM3L.
Sorry for the few days delay we will post some photos here of VIM3L production.