yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] chapas:
I've clear the cache and uninstalled tvheadend and installed the version from your post.

And then:

c:\Adb_Fastboot_143_Portable>adb root

c:\Adb_Fastboot_143_Portable>adb shell
1|darcy:/ $ ls -lar /dev/dvb
ls: /dev/dvb: No such file or directory
1|darcy:/ $ ls -lar /dev/dvb
total 0
drwxr-xr-x 2 root root 160 2019-05-08 21:26 adapter1
drwxr-xr-x 2 root root 160 2019-05-08 21:26 adapter0
drwxr-xr-x 19 root root 2600 2019-05-08 21:26 ..
drwxr-xr-x 4 root root 80 2019-05-08 21:26 .
darcy:/ $

In case you wonder the first "ls -lar /dev/dvb" is without the checkbox "Enable root for USB tuners" checked. Afterward, i checked and got 2 adapters. Still i can't see it in the config DVB Inputs / TV Adapters tab, but this is because it is the original boot.img, since the other image provided by lexyan as well as mine that i have compiled don't have Wi-Fi neither USB Ports!?!?!?
[Shield Android TV General] chapas:
One more thing you can try if after flashing a modified boot.img that end's up in a boot loop.

Flash the original boot.img image (hope this will boot up your shield)

With USB Debugging

[B]adb root[/B]
[B]adb disable-verity[/B]
Verity disabled on /vendor
Verity disabled on /system
Now reboot your device for settings to take effect
[B]adb reboot bootloader[/B]

Then on fastboot

[B]fastboot oem disable_dm_verity[/B]

Flash your modified boot.img again
[Shield Android TV General] locki:
yesturday i clear data in tvheadend reinstaled, tuned and now it works... i can stream to my KODI on PC and my mobile phone ... it should work also on Kodi on Shield!!! :) finally .... usb keybord works, but not working sheild gamepad i thing i must check it again after flashing boot image.... i didnt had time for this yesturday ...
[Shield Android TV General] chapas:
Ended my day with a factory reset. All clean, started from sctratch. Used "flashall.bat" from nvidia 7.2.3 rooted image.

Installed magisk and patched the original boot.img, flashed and booted ok.

All other builds (mine and lexyan's) dvb enabled images boot with no Wi-Fi nor USB ports, although debug port still works.

I wish i would't be so stubborn this is so frustrating.
[Shield Android TV General] lexyan77:
Hi chapas,

If the source from Nvidia are buggy, I can't do nothing.

Why using pre rooted image from Nvidia instead of official recovery image, when I tried magisk with firmware 5.x (long time ago) the rooted image partially brick my Shield.
[Shield Android TV General] BenouLM:
Good morning, everyone,

Here I have a ShieldTv 2017 with firmware 7.2.3.

On ShieldTv 2015 I managed to install the drivers for the Sony playtv.

But on version 2017 I can't do it. I don't know where to put the fw file.

Apparently it's in the vendor folder but it's write-protected.

Not all manipulations of this subject work.

Do you have any ideas?

Thank you. Thank you.
[Shield Android TV General] lexyan77:
Hi BenouLM,

If you use my modified kernel, you can copy needed firmware in '/data/dvb/firmware', it's a special folder I have created with read write permissions and correct SePolicy rules.

The system and vendor partition are protected with some checksum, if you try to copy files on it you can softbrick your shield.
[Shield Android TV General] BenouLM:
Thank you for your answer,

I don't have your modified kernel because it seems you have trouble with 7.2.3, right?

So I wanted to install the playtv drivers in an "official" way

Isn't there a solution?
[Shield Android TV General] lexyan77:
Right,

my kernel work great with Shield 2015 but unfortunately the source for shield 2017 broke wifi and probably usb
[Shield Android TV General] BenouLM:
Okay, I tried to put boot_7.2.3_darcy_userdebug.img on shieldtv 2017 and I have a bootloop. So don't work.

I also have a 2015 shieldtv that is unlock but not root. And here I can't put or boot on boot_7.2.3_foster_userdebug.img ( replace by boot_7.2.3_shield2015_userdebug.img in my code) by the fastboot command...

PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot flash boot boot_7.2.3_shield2015_userdebug.img
target reported max download size of 67108864 bytes
sending 'boot' (14526 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.043s
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot boot boot_7.2.3_shield2015_userdebug.img
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.040s

I don't understand why...
[Shield Android TV General] kyvaith:
Tbs-5520 se

[MENTION=2310389]lexyan77[/MENTION] Is it possible to add a support for a TBS-5520 SE device? There are drivers for Linux system here: https://github.com/tbsdtv/linux_media/wiki Thianks!
[Shield Android TV General] skyline78de:
Maybe some of these Points can fix the issue vor the 2017 shield.

https://xdaforums.com/showpost.php?p=80110657&postcount=18

https://xdaforums.com/showpost.php?p=80085877&postcount=14
[Shield Android TV General] skyline78de:
Wifi is also broken on nvidia shield 2015 pro (500gb).
[Shield Android TV General] skyline78de:
Wifi is also not working on nvidia shield 2015 (16gb).
[Shield Android TV General] kyvaith:
[MENTION=2310389]lexyan77[/MENTION] Are you panning to update your kernel for 8.0.1? Thanks.
[Shield Android TV General] nopnop9090:
jup, check your dmesg output (i.e. "adb shell dmesg") right after boot, it should tell you something about the usb initialisation, then the driver should load and as soon as tvheadend gets started the driver should load the firmware.
[Shield Android TV General] uronito:
Hi ,

i have avermedia volar a815, i put the firmware file for this, the program shows me the tv adapter but not working. Ican't see any channel and information dont show nothing.

I use boot img dvb-static.

Can you help me please?

Thanks in advance
[Shield Android TV General] xaudiblex:
Since the HDHomerun Extend is an ethernet based card, will it show under USB or somewhere else on the dmesg?
[Shield Android TV General] uronito:
I've gotten to work tvheadend with avermedia volar a815 , it detects muxes and channels , but the channels don't see. tvheadend is continuously brand continuity errors. This is my dmesg .

<6>[ 8.452657] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

<6>[ 8.452661] usb 2-2.2: Product: A815

<6>[ 8.452665] usb 2-2.2: Manufacturer: AVerMedia

<6>[ 8.452669] usb 2-2.2: SerialNumber: 302126301216000

<6>[ 8.455881] usb 2-2.2: dvb_usb_v2: found a 'AVerMedia AVerTV DVB-T Volar X' in cold state

<6>[ 8.458730] input: AVerMedia A815 as /devices/platform/tegra-xhci/usb2/2-2/2-2.2/2-2.2:1.1/input/input2

<6>[ 8.458835] hid-generic 0003:07CA:A815.0001: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-tegra-xhci-2.2/input1

<6>[ 8.466107] usb 2-2.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'

<6>[ 8.544202] usb 2-2.2: dvb_usb_v2: found a 'AVerMedia AVerTV DVB-T Volar X' in warm state

<6>[ 8.568028] usb 3-3: reset SuperSpeed USB device number 3 using tegra-xhci

<6>[ 8.933634] usb 2-2.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer

<6>[ 8.942266] usb 2-2.2: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...

<6>[ 8.950020] input: AVerMedia AVerTV DVB-T Volar X as /devices/platform/tegra-xhci/usb2/2-2/2-2.2/rc/rc1/input3

<6>[ 8.950103] rc1: AVerMedia AVerTV DVB-T Volar X as /devices/platform/tegra-xhci/usb2/2-2/2-2.2/rc/rc1

<6>[ 8.950112] usb 2-2.2: dvb_usb_v2: schedule remote query interval to 500 msecs

<6>[ 8.950121] usb 2-2.2: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully initialized and connected

<3>[ 37.379619] mc-err: [mcerr] (xusb_host) csw_xusb_hostw: EMEM decode error on PDE or PTE entry

<3>[ 37.403081] mc-err: [mcerr] (xusb_host) csw_xusb_hostw: EMEM decode error on PDE or PTE entry

<3>[ 37.427416] mc-err: [mcerr] (xusb_host) csw_xusb_hostw: EMEM decode error on PDE or PTE entry

<3>[ 37.452171] mc-err: [mcerr] (xusb_host) csw_xusb_hostw: EMEM decode error on PDE or PTE entry

<3>[ 37.475740] mc-err: [mcerr] (xusb_host) csw_xusb_hostw: EMEM decode error on PDE or PTE entry

What can happen?

Thanks
[Shield Android TV General] crnkoj:
Hey, this is great news, i was just planning to buy a satellite box/tuner, but saw this. I was browsing through the S2 options here in Europe:

http://geizhals.eu/?cat=vid&xf=802_HDTV~801_DVB-S2~800_USB+2.0

it appears the DVBSKY S960 and the Technotrend-s2-4600 would be the most reasonable choices from a price perspective (as otherwise a comparable box with all integrated and functioning would cost less than the shield+ tuner combo) and even the PCTV e461, sadly as i saw all would need a backported driver. Thers is some wiki here

http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers to get v4l working (for the DVBSKY for instance), but it appears to be more of a hack.

Anyhow does anyone have a better suggestion? perhaps even from the list of the available devices... (the Tevii s660 would work but is more expensive and has inferior encoding abilities..)

edit: ow i checked it once again and it appears that the Terratec s2 woudl fit best as its supported in kernel >=3.10

http://geizhals.eu/terratec-cinergy....html?hloc=at&hloc=de&hloc=pl&hloc=uk&hloc=eu

http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_S2_R2
[Shield Android TV General] slikerhael:
Ext4 support would be nice too
[Shield Android TV General] uronito:
Would you can add oscam compiled for shield, as tvheadend?

Thanks!!!!!!
[Shield Android TV General] gffmac:
If I install this kernel will I be able to ftp to the shield (running an ftp server of course) and write to attached NTFS USB drive?
[Shield Android TV General] umoraes2009:
Hi, Is it possible to package your DVB solution into a apk file ? Does it make sense ? or it requires bootloader unlock ? thanks
[Shield Android TV General] gffmac:
It requires a modified kernel which means bootloader unlock yes.
[Shield Android TV General] uronito:
hi,

when i try a record program or movie, tvheadend crash!!!!!!! In ntfs harddrive or sdcard android.

why?

Regards
[Shield Android TV General] xd4d3v:
and root, because it modifies /system
[Shield Android TV General] d8tahead:
Is there anybody who has tried kernel / driver support for rt2800usb and rtl8187 NIC's?
[Shield Android TV General] umoraes2009:
ok, so it means it's not simples as getting bootloader unlock and get everything packaged in a apk file - for easy install... right ?
[Shield Android TV General] nex86:
Hauppauge WinTV NOVA-T-Stick supported?
[Shield Android TV General] benjy214:
are you sure transcoding is working?

when i try to enable one of the x264 profiles, i get the following error:

is there a way for you to include the libx264 encoder?
[Shield Android TV General] ErAzOr2k:
has anyone tried to add m3u list with this tvheadend buld? I just get "unable to open http client"
[Shield Android TV General] slamride:
I have flashed the "static -build" ,installed tvheadend but am having driver issues. I am using a HDStar DVB-S2 TV Box tuner and it will not install driver. After alot of google and research I was able to get closer to fix(at first it was recognized as DS3000 not SU3000) It seems my a dvb-s2 is a SU3000 version not the DS3000 that the drivers seem made for. I cannot find SU3000 driver that works so I am needing help. I was able to convert and install a WIN 7 driver to my Ubuntu setup and it seems it is working so is it possible to pull that driver from Ubuntu and compile into build? Several firmware say they support SU3000 but all have failed when used. I know it is possible to compile my own and "insmod" but I am uncertain how.

DMESG below and any help would be appreciated as I am a newbie as far as Linux.

Thanks for all your work on this I was thinking of this setup but had no clue where to start. Wanting to create the "Ultimate Media Center" for my den and this seems VERY close to my plan.

<6>[28044.867700] usb 2-2: new high-speed USB device number 5 using tegra-xhci

<6>[28044.889017] usb 2-2: New USB device found, idVendor=1f4d, idProduct=3000

<6>[28044.889027] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

<6>[28044.889035] usb 2-2: Product: DVB-S/S2 USB Box

<6>[28044.889042] usb 2-2: Manufacturer: DVB-S/S2 USB Box

<6>[28044.889048] usb 2-2: SerialNumber: 080616

<6>[28044.890218] dw2102: su3000_identify_state

<6>[28044.890218]

<6>[28044.890229] dvb-usb: found a 'SU3000HD DVB-S USB2.0' in warm state.

<6>[28044.890249] dw2102: su3000_power_ctrl: 1, initialized 0

<6>[28044.890249]

<6>[28044.899847] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

<6>[28044.900095] DVB: registering new adapter (SU3000HD DVB-S USB2.0)

<3>[28045.218685] Invalid probe, probably not a DS3000

<3>[28045.223370] dvb-usb: no frontend was attached by 'SU3000HD DVB-S USB2.0'

<6>[28045.230669] input: IR-receiver inside an USB DVB receiver as /devices/plat

form/tegra-xhci/usb2/2-2/input/input5

<6>[28045.230801] keychord: using input dev IR-receiver inside an USB DVB receiv

er for fevent

<6>[28045.230809] dvb-usb: schedule remote query interval to 150 msecs.

<6>[28045.230819] dw2102: su3000_power_ctrl: 0, initialized 1

<6>[28045.230819]

<6>[28045.230826] dvb-usb: SU3000HD DVB-S USB2.0 successfully initialized and connected.

<3>[28047.378097] dvb-usb: recv bulk message failed: -110

<3>[28047.382993] dw2102: i2c transfer failed.
[Shield Android TV General] crnkoj:
hi, whats the default username and password for the tvheadend here? i cant seem to figure it out ...

thanks
[Shield Android TV General] xd4d3v:
I had the same problem.

just to the first few pages to see how to solve it.
[Shield Android TV General] crnkoj:
Ok, I'll try that. Though it appears to not be the same issue.

Btw did anyone try to build the kernel from op themselves I wanted to use a dvbs2 stick, that's not in the media kernel of op, so tried to compile like the instructions but it doesn't seem to work, throws out some errors... On my phone right now so I can't post the log.
[Shield Android TV General] slamride:
using adb run " /data/dvb/tvheadend -C -c /data/dvb/tvheadend/hts" or "/data/dvb/tvheadend -C -c /data/dvb/hts" . The second worked for my setup since that is where I put Tvheadend file. I also had issues with adb running command so I booted to recovery "TWRP 1.3" and ran command from there. Command resets Tvheadend so you can setup new Account and password.

---------- Post added at 04:11 PM ---------- Previous post was at 03:39 PM ----------

I built multiple versions using the instructions from the bitbucket link. I did find that changing any driver files caused errors and I had to search for different versions to work with. From all my searching I found that the easiest way was to build a complete set of my own (frontend,usb,etc)and copy them over before compiling. The media-build version has a very good set with it if you download the file set.

Directions were confusing for me at first ( I am a Noob to Linux) but i was able to to use them as a guide. This worked for me.

Recommend copying files to new folder....easier to delete and start again from scratch if build fails. I also setup my Ubuntu using the same packages as NOPNOP9090 "on Bitbucket page"

cd "where you have files" ie cd MYBUILD

export TOP=`pwd`

. build/envsetup.sh

setpaths

lunch foster_e-userdebug # (use "lunch foster_e_hdd-userdebug" if you got the shield tv pro)

mp bootimage -j9 # (change j9 to j<number-of-cpu-cores+1> for optimal build speed)
[Shield Android TV General] crnkoj:
Yeah managed to get it to build with the media build and defconfig as well as editing the .config through menuconfig like on other liunx distros normally. Managed to get my dvbs2 to get recognised, Terratex cinergy C2 HD revision 2 - had luck with it, cuz i could buy it locally used last week). Just had to enable DVB_USB and DVB_ds3000 and DVB_dw2102. Now to get the tvheadend to work...

Edit:

worked with your advice about setup for tvheadend. How do you automatically start it now?,, or do you run it every time? or how do i start is as a deamon?

Edit2: I just tried to run the boot script from op normally and it works, my adapter is being found. How do i make it execute on boot, cant seem to find any real useful init spot...

just need my dish to arrive (damn dhl tricked me it would be here today).

Edit3:

btw how do i get the livetv option in kodi, which plugin do i need to install and where to get it?
[Shield Android TV General] slamride:
After the initial setup it will run when Shield powers up...only one time command...runs in background on Shield

Latest Kodi comes with everything needed.

To view channels I have KODI with the Live tv enabled (goto system,settings,tv and click on enable ) tvheadend addon and (add-ons ,pvr,tvheadend,enable) and used factory settings and it was found. Takes a few seconds then will show on main kodi screen "TV"
[Shield Android TV General] orhon:
Sigh, great work but I wish there were some instructions for technical idiots like me :(

I mean, if people could just share the name of the tuners they use, the files to flash...and how to flash them (i really couldn't get this part, i am a newbie) lol
[Shield Android TV General] slamride:
Newbie myself until I found this post. Read all comments as well as post. There are replies with links to tuners list and setup steps. I would recommend "static build" to start. If tuner is not recognized at first still continue setting up tvheadend and KODI then look at tuner issue. I learned alot from trial and error. Since your only flashing the boot file its "fairly safe" (always a chance of mistakes) but very slim that you will "brick" shield. I have abused my shield with several changes flashing all sorts of modified firmware,recovery and boot images and it has survived.
[Shield Android TV General] crnkoj:
first you need a supported usb stick, best thing to do is, to look at the supported ones here:

http://linuxtv.org/wiki/index.php/DVB-S2_USB_Devices preferably choose one that has support in kernels 3.10 and lower, as the shield kernel is 3.1. otherwise you need to backport drivers with v4l, which is somewhat confusing and more work to do, havent bothered with it myself yet.

as far as im concerned, the kernels from OP dont have good dvb-s support, so i had to compile my own kernel from his bitbucket repo, branch media and edited the defconfig to my liking (cuz i only need for the dw2102, which is in 3.10 already supported), i didnt even bother with the additional modules, as these are through v4l backported and as already said i havent bothered with it for now.

than you need to flash that boot img, same as you flash any other boot img through fastboot, further on some of the sticks need a firmware, i used for mine the one on linuxtv

http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_S2_R2 https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-fe-ds3000.fw

than you have to get all the stuff onto the shield tv, hence need supersu, best through twrp flashed, thers enough tutorials here how to do it. Later you need to remount system as rw so you can copy the firmware onto it.

adb shell

su

mount -o remount,rw /system

copy firmware to /system/etc/firmware

copy the tvheadend and bootup script from op to /data/dvb/ as suggested

reboot

again adb shell

su

start tvheadend with the modified line from above

/data/dvb/tvheadend -C -c /data/dvb/hts

set it all up like tvheadend

https://tvheadend.org/projects/tvheadend/wiki/Install_and_initial_setup , set usernames and passwords

restart, now im not sure, slamride says it automatically starts, but i think the boot script has to be started every time booted, either through an init system (which i havent found/figured out yet on the shield tv stock software) or manually, again adb shell chmod 755 the boot script and run it, than you can connect through web browser.

finally you need to install kdoi and some of its plugins, which i havent tested yet...
[Shield Android TV General] orhon:
thanks for the info guys! really helpful!

seems a lot of work but i will get started and see how it goes :)

thanks again!
[Shield Android TV General] crnkoj:
damnit man, i got it all to work, kodi connects to the tvheadend backend, i can see both ttp and htsp connections, but the live tv tab doesnt appear, neither on the shield tv, nor on my android phone (both connect nicely to tvheadend)... The only thing i could think of , is that its not working because i dont have my antenna connected to it...

got any ideas?

edit:

btw here is th ekernel i compiled myself from ops sources with dw2102 support

https://mega.nz/#!BBISDbbb!waz1GH0MZ3BRFjkoO8EKPbpBtQUwmojehDF7XhC-sSo

as well as the .config for basically the same one but with config.gz support, forgot to do it in the first one

https://mega.nz/#!MIRFnbYC!SjtqFvw_5QpJOkfj-H_QqAwqZ18K_ruG94PZUhJDC8Q

edit: hmm i installed tvheadend, kodi, the usb drivers etc on my laptop on arch linux, all works, but live tv still doesnt show up in the confluence skin (its even grayed out in the settings screen) but if i use another skin they show up, yet without channels (clearly as no lnb is connected), might be that i need the antenna connected and than it should work.

BTW if i boot and connect the usb stick afterwards, it doesnt get recognised properly, i always have to boot it, connect it or boot with it connected, than retasrt and than its being recognized. As if the stick has to get "warm"

edit1:

so i managed to crosscompile the latest oscam so that it starts and runs oin the shield tv, now i have an issue, that i dont know where to get the kodi oscam addon needed... any ideas? thers nothing available, mostly just for openelex or for x86/x86_64
[Shield Android TV General] ErAzOr2k:
So Firmware 3.0 is out now.

Can you provide new modified Kernels for the new firmware?
[Shield Android TV General] nopnop9090:
sorry for being away lately and thanks to slamride, crnkoj and all the others that help out each other... as for the marshmallow update, i am waiting for nvidia to release the 3.0 sources, the updated package will be available shortly after.

tvheadend status: as there are issues getting hdhomerun network tuners working I am trying to patch the needed code into it - its progressing slowly because I have to wait for some testers to check out each build etc, but that way it may be even possible to get full hw accelerated transcoding to work (more on that later)

general status: there are some issues with the shield usb 3.0 controller and my usb tuners if there is more than 1 tuner connected to the shield at once. I am now trying to build a "immediate filter driver" that sits between the dvbsky t330 driver and the usb subsystem to filter out some garbage data - as with the tvheadend part, there is already some progress but there are definately not enough hours in a single day ..
[Shield Android TV General] benjy214:
can you pls update your bitbucket with the tvheadend sources you're using?

i tried building from the tvheadend master but with no success.
[Shield Android TV General] crnkoj:
Hi, thanks for the update. You might want to add the dvb-s tuners to your media build as well, perhaps enable config.gz in your builds as well, so that people can just pull the config from the working kernel.

Tvheadend seems to work for me, though I have to finally test it with the dish/antenna connected. Have you perhaps tried oscam? I managed to get I built and even started but don't have a plug-in for kodi for it....