Full DVB-C/T/T2/S PVR running tvheadend and stock based kernel (incl NTFS support)!

Search This thread
maybe some rights? i did all under root ... in folder /root/shield-open-source/

and i cant see any: joe arch/arm64/configs/tegra_android_defconfig CONFIGDIFF.txt

you must install joe it need some packages apt-get install joe something something

Indeed, I didn't use root to do it. I used my own user. Don't really know if this is an issue.

Meanwhile, I have edited the file in question and made some change to that particular line. Rebuild and it got finished, so I think the next step is to flash and brick :)

I only know how to use 'nano', I tried 'joe' but I'm simply to dumb to know how to use (in a small time) one more tool that does probably the same when all i needed is to append what was modified to one file . I copied all .configs over FTP to windows, diff them and edite the file there and uploaded them again to the VM.

Did you build tvheadend for the shield?

ps: I have all this setup running on my RPI (PCTV416e + tvheadend + oscam ouputing on kodi) , only that it doesn't have enough CPU to process HD channels, hence all this effort to move this setup to the shield.
 

lexyan77

Senior Member
Jan 23, 2010
64
68
Paris
Indeed, I didn't use root to do it. I used my own user. Don't really know if this is an issue.

Meanwhile, I have edited the file in question and made some change to that particular line. Rebuild and it got finished, so I think the next step is to flash and brick :)

I only know how to use 'nano', I tried 'joe' but I'm simply to dumb to know how to use (in a small time) one more tool that does probably the same when all i needed is to append what was modified to one file . I copied all .configs over FTP to windows, diff them and edite the file there and uploaded them again to the VM.

Did you build tvheadend for the shield?

ps: I have all this setup running on my RPI (PCTV416e + tvheadend + oscam ouputing on kodi) , only that it doesn't have enough CPU to process HD channels, hence all this effort to move this setup to the shield.

Hi Chapas and Locki,

You don't need to be root to compile, root user must be use only for maintenance task.

Nvidia has made some change in the kernel source code, it's more an hybrid between kernel 3.14 and kernel 4.9 on some part.
Some part of code are kept from kernel 3.14 to keep compatibility with prebuilt binaries they use.

You must disable "VIDEO_EM28XX_ALSA" to compile without modification (Alsa is only used for analog TV).

Nano and Joe are identical text editor but Joe allow to open 2 or more files at a time so its more efficient to compare files.
 
Hi Chapas and Locki,

You don't need to be root to compile, root user must be use only for maintenance task.

Nvidia has made some change in the kernel source code, it's more an hybrid between kernel 3.14 and kernel 4.9 on some part.
Some part of code are kept from kernel 3.14 to keep compatibility with prebuilt binaries they use.

You must disable "VIDEO_EM28XX_ALSA" to compile without modification (Alsa is only used for analog TV).

Nano and Joe are identical text editor but Joe allow to open 2 or more files at a time so its more efficient to compare files.

Lexyan,
thanks for stepping in and clearing some doubts.
Do you know any more kernel options that i may need to add for my setup (PCTV416e + tvheadend + oscam ouputing on kodi)?

Whats the easiest way to add Magisk to boot.img?

Regards,
chapas
 
Ended up with a boot loop. I have to find out how to roll this crap back.
So much wasted time.

Beaten but not dead.
I've tried ALL 'boot.img' that I compiled along the way and all of them are stuck on a boot loop (even the clean and kernel untouched one; WTF).
I ended up by installing the boot.img from "NVIDIA SHIELD TV 2017 Developer Only OS Image / 7.2.3 / 2019/03/14", and that brought it back to life again.
Don't know what to do next. Any explanation for this or any similar results?
 
Basically, this is just me talking to myself out loud in the hope that someone (@locki or @lexyan77) ears me and decides to help;
So now I have different problems:

Did

Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot

Worked and went back to life, everything seemed OK after playing around with it for a while
Re-flashed my compiled "boot.img" file and to my surprise it started up, then came the problem:
- No wifi (only ethernet) and no USB ports.

Ideas?

Regards,
chapas
 

lexyan77

Senior Member
Jan 23, 2010
64
68
Paris
Hi chapas,

Glad your Shield is no more bricked.
To avoid problem, next time you want to test a kernel don't flash it, instead you can make the Shield boot on it with "fastboot boot boot.img", if something goes wrong you can reboot the Shield to retrieve original kernel.

I have recompiled the kernel for my Shield with almost all DVB devices included.
I have tested only the 2015 16G version (foster) with:
  • R820
  • R820/T2
  • Hauppauge WinTV-dualHD
  • PCTV Systems tripleStick T2 (292e)

If you want to test it you can find the 2017 version (darcy) in my dropbox Shield 7.2.3
I can probably provide support for the next week if you need it.
If all is working, I'll post a patch containing my modifications.


As usual you flash it at your own risk and i m not responsible for any damage that can occurred




Basically, this is just me talking to myself out loud in the hope that someone (@locki or @lexyan77) ears me and decides to help;
So now I have different problems:

Did

Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot

Worked and went back to life, everything seemed OK after playing around with it for a while
Re-flashed my compiled "boot.img" file and to my surprise it started up, then came the problem:
- No wifi (only ethernet) and no USB ports.

Ideas?

Regards,
chapas
 

ikarus.nc

Member
Sep 23, 2017
27
3
Hi chapas,

Glad your Shield is no more bricked.
To avoid problem, next time you want to test a kernel don't flash it, instead you can make the Shield boot on it with "fastboot boot boot.img", if something goes wrong you can reboot the Shield to retrieve original kernel.

I have recompiled the kernel for my Shield with almost all DVB devices included.
I have tested only the 2015 16G version (foster) with:
  • R820
  • R820/T2
  • Hauppauge WinTV-dualHD
  • PCTV Systems tripleStick T2 (292e)

If you want to test it you can find the 2017 version (darcy) in my dropbox Shield 7.2.3
I can probably provide support for the next week if you need it.
If all is working, I'll post a patch containing my modifications.


As usual you flash it at your own risk and i m not responsible for any damage that can occurred

Unfortunately Darcy version lead to a bootloop :(
 

ikarus.nc

Member
Sep 23, 2017
27
3
What I meant was that booting with that img will reset the Nvidia shield, I tried with "fastboot boot" ?
 

locki

Senior Member
Feb 1, 2008
203
47
It mean when you flash bad kernel you are littlebit f**ked :) and you need flash again correct boot image ... when you only boot it withou flash it is much easy, just turn it of and on and it is fixed :)

there is my output with xbox and mygica T230 tuner

Code:
[32m[  140.234191] [0m[33musb 1-3[0m: new high-speed USB device number 3 using tegra-xusb
[32m[  140.254995] [0m[33musb 1-3[0m: New USB device found, idVendor=045e, idProduct=02d5
[32m[  140.255001] [0m[33musb 1-3[0m: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32m[  140.255005] [0m[33musb 1-3[0m: Product: Xbox USB Tuner
[32m[  140.255009] [0m[33musb 1-3[0m: Manufacturer: Microsoft Corp.
[32m[  140.255013] [0m[33musb 1-3[0m: SerialNumber: 005091110615
[32m[  140.255412] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/control 1000 1000 644
[32m[  140.255678] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/autosuspend_delay_ms 1000 1000 644
[32m[  140.255758] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/wakeup 1000 1000 644
[32m[  140.265219] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/control 1000 1000 644
[32m[  140.265385] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/autosuspend_delay_ms 1000 1000 644
[32m[  140.265478] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/wakeup 1000 1000 644
[32m[  140.267310] [0m[33mtype=1400 audit(1557157480.433:10672)[0m: avc: denied { write } for pid=4067 comm="Binder:4067_6" name="timerslack_ns" dev="proc" ino=25311 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267321] [0m[33mtype=1400 audit(1557157509.785:10701)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=33129 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267493] [0m[33mtype=1400 audit(1557157509.785:10701)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=33129 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267503] [0m[33mtype=1400 audit(1557157509.785:10702)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34856 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267592] [0m[33mtype=1400 audit(1557157509.785:10702)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34856 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267599] [0m[33mtype=1400 audit(1557157509.785:10703)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34858 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267676] [0m[33mtype=1400 audit(1557157509.785:10703)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34858 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267684] [0m[33mtype=1400 audit(1557157509.785:10704)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34860 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267763] [0m[33mtype=1400 audit(1557157509.785:10704)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34860 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.267771] [0m[33mtype=1400 audit(1557157509.785:10705)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34862 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  140.280731] [0m[33maudit[0m: audit_lost=10166 audit_rate_limit=20 audit_backlog_limit=64
[32m[  140.280736] [0m[33maudit[0m[31m: rate limit exceeded[0m

https://www.linuxtv.org/wiki/index.php/Geniatech_T230
Code:
foster:/ # lsusb
Bus 001 Device 004: ID 0572:c688

[32m[  714.250250] [0m[33musb 1-3[0m: new high-speed USB device number 4 using tegra-xusb
[32m[  714.271011] [0m[33musb 1-3[0m: config 1 interface 0 altsetting 0 bulk endpoint 0x86 has invalid maxpacket 188
[32m[  714.271903] [0m[33musb 1-3[0m[31m: language id specifier not provided by device, defaulting to English[0m
[32m[  714.274855] [0m[33musb 1-3[0m: New USB device found, idVendor=0572, idProduct=c688
[32m[  714.274873] [0m[33musb 1-3[0m: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32m[  714.276142] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/control 1000 1000 644
[32m[  714.277710] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/autosuspend_delay_ms 1000 1000 644
[32m[  714.277798] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/power/wakeup 1000 1000 644
[32m[  714.277811] [0m[33mdvb-usb[0m: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[32m[  714.287172] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/control 1000 1000 644
[32m[  714.287251] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/autosuspend_delay_ms 1000 1000 644
[32m[  714.287318] [0m[33mueventd[0m: fixup /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/power/wakeup 1000 1000 644
[32m[  714.519104] [0m[33mdvb-usb[0m: will pass the complete MPEG2 transport stream to the software demuxer.
[32m[  714.519430] [0m[33mDVB[0m: registering new adapter (Mygica T230 DVB-T/T2/C)
[32m[  714.534708] [0m[33mi2c i2c-7[0m: Added multiplexed i2c bus 8
[32m[  714.534713] [0m[33msi2168 7-0064[0m: Silicon Labs Si2168-B40 successfully identified
[32m[  714.534716] [0m[33msi2168 7-0064[0m: firmware version: B 4.0.2
[32m[  714.536371] [0m[33msi2157 8-0060[0m: Silicon Labs Si2147/2148/2157/2158 successfully attached
[32m[  714.536383] [0m[33musb 1-3[0m: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[32m[  714.536765] [0m[33minput[0m: IR-receiver inside an USB DVB receiver as /devices/70090000.xusb/usb1/1-3/input/input5
[32m[  714.536845] [0m[33mkeychord[0m: using input dev IR-receiver inside an USB DVB receiver for fevent
[32m[  714.536847] [0m[33mdvb-usb[0m: schedule remote query interval to 100 msecs.
[32m[  714.536931] [0m[33mdvb-usb[0m: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[32m[  714.540390] [0m[33mtype=1400 audit(1557158071.277:11805)[0m: avc: denied { write } for pid=4067 comm="android.fg" name="timerslack_ns" dev="proc" ino=115722 scontext=u:r:system_server:s0 tcontext=u:r:untrusted_app_25:s0:c512,c768 tclass=file permissive=0
[32m[  714.540399] [0m[33mtype=1400 audit(1557158084.057:11897)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=33129 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.540754] [0m[33maudit[0m: audit_lost=11242 audit_rate_limit=20 audit_backlog_limit=64
[32m[  714.540757] [0m[33maudit[0m[31m: rate limit exceeded[0m
[32m[  714.541631] [0m[33mtype=1400 audit(1557158084.057:11897)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=33129 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541638] [0m[33mtype=1400 audit(1557158084.057:11898)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34856 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541733] [0m[33mtype=1400 audit(1557158084.057:11898)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34856 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541739] [0m[33mtype=1400 audit(1557158084.057:11899)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34858 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541799] [0m[33mtype=1400 audit(1557158084.057:11899)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34858 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541804] [0m[33mtype=1400 audit(1557158084.057:11900)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34860 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541862] [0m[33mtype=1400 audit(1557158084.057:11900)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34860 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
[32m[  714.541867] [0m[33mtype=1400 audit(1557158084.057:11901)[0m: avc: denied { write } for pid=4067 comm="ActivityManager" name="timerslack_ns" dev="proc" ino=34862 scontext=u:r:system_server:s0 tcontext=u:r:priv_app:s0:c512,c768 tclass=file permissive=0
foster:/ #


Q:it looks like mygica is recongnized ... what is next step?
A:
oster:/ # dmesg | grep dvb
[ 714.277811] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 714.519104] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 714.536847] dvb-usb: schedule remote query interval to 100 msecs.
[ 714.536931] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 1367.533381] si2168 7-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 1368.323606] si2157 8-0060: loading /data/firmware/dvb-tuner-si2158-a20-01.fw failed with error -13
[ 1368.323702] si2157 8-0060: loading /data/dvb/firmware/dvb-tuner-si2158-a20-01.fw failed with error -13
[ 1368.323716] si2157 8-0060: Direct firmware load for dvb-tuner-si2158-a20-01.fw failed with error -13

drivers! :)

it download drivers automaticly ...

[ 2121.366197] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.

Q:how to start tv i have some HTS Tvheadend 4.3-905~g9bed2c7-dirty but in tuners i cant see my device :( what are next step to tune?
 
Last edited:
Hi chapas,

Glad your Shield is no more bricked.
To avoid problem, next time you want to test a kernel don't flash it, instead you can make the Shield boot on it with "fastboot boot boot.img", if something goes wrong you can reboot the Shield to retrieve original kernel.

I have recompiled the kernel for my Shield with almost all DVB devices included.
I have tested only the 2015 16G version (foster) with:
  • R820
  • R820/T2
  • Hauppauge WinTV-dualHD
  • PCTV Systems tripleStick T2 (292e)

If you want to test it you can find the 2017 version (darcy) in my dropbox Shield 7.2.3
I can probably provide support for the next week if you need it.
If all is working, I'll post a patch containing my modifications.


As usual you flash it at your own risk and i m not responsible for any damage that can occurred

Thanks for your help lexyan,
you image didn't enter on bootloop like ikarus.nc mentioned on his post, but it has exactly the same problem as mine, no Wi-Fi device available. In turn i did connect a ethernet cable just to try out the rest.

Did
Code:
adb root
adb shell
darcy:/lib/firmware $ sudo cp /storage/emulated/0/Download/dvb-demod-m88ds3103.fw /lib/firmware/dvb-demod-m88ds3103.fw
[B]cp: /lib/firmware/dvb-demod-m88ds3103.fw: Read-only file system[/B]

how can i copy the firmware file there?

Code:
$ sudo dmesg | grep PCTV
$ sudo dmesg | grep dvb
yield nothing...
 

locki

Senior Member
Feb 1, 2008
203
47
Code:
$ sudo dmesg | grep PCTV
$ sudo dmesg | grep dvb
yield nothing...

you must run adb as root :

Code:
adb root shell
then just adb shell

and you have root access


and i have every time problem that remote control stop working with custom kernel with dvb-t support .... weird
 
Last edited:
you must run adb as root :

Code:
adb root shell
then just adb shell

and you have root access


and i have every time problem that remote control stop working with custom kernel with dvb-t support .... weird

I did! Check my post again.

That almost seems that the original boot.img is not compiled from the same source. I don't understand...
 
Last edited:

lexyan77

Senior Member
Jan 23, 2010
64
68
Paris
Hi chapas,

You can't copy file to "/lib/firmware" as this directory is on "system" partition, any modification on this partition prevent the Shield from booting.

My modification allow loading firmware files from "/data/dvb/firmware" and "/data/firmware" and you don't need to be root to copy files in it but you must reboot the Shield after copying files to have proper permissions on the files.


Locki, you need firmware files "dvb-tuner-si2158-a20-01.fw" placed in "/data/firmware" or "/data/dvb/firmware" for your dongle to work.


I did! Check my post again.

That almost seems that the original boot.img is not compiled from the same source. I don't understand...
 
Last edited:
Anyone, besides me, tried the 16gb 2017 version boot image?

I did, it booted, but no Wi-Fi for me.

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------

Hi chapas,

You can't copy file to "/lib/firmware" as this directory is on "system" partition, any modification on this partition prevent the Shield from booting.

My modification allow loading firmware files from "/data/dvb/firmware" and "/data/firmware" and you don't need to be root to copy files in it but you must reboot the Shield after copying files to have proper permissions on the files.


Locki, you need firmware files "dvb-tuner-si2158-a20-01.fw" placed in "/data/firmware" or "/data/dvb/firmware" for your dongle to work.

Thank's lexyan,
When you say "My modification", can you be more explicit so I can do the same when I compile an image again.
 
Did you do something particular? I just did "fastboot boot boot.img" whatever is the name of the image, and the shield reboot with its own kernel, thank you for your help.

Well,
I didn't do anything in particular. Just what you did.
Make sure the file is complete (15MB).
Make sure you are the same version 7.2.3 (if you can).
Read the 3 previous pages on this thread, there is a lot of information there.
If I were in your shoes I would download the version 7.2.3 from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
and do what I've done from:
https://forum.xda-developers.com/showpost.php?p=79363874&postcount=366
and then the "fastboot boot boot.img" again.
 

ikarus.nc

Member
Sep 23, 2017
27
3
I did, it booted, but no Wi-Fi for me.

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------



Thank's lexyan,
When you say "My modification", can you be more explicit so I can do the same when I compile an image again.

Well,
I didn't do anything in particular. Just what you did.
Make sure the file is complete (15MB).
Make sure you are the same version 7.2.3 (if you can).
Read the 3 previous pages on this thread, there is a lot of information there.
If I were in your shoes I would download the version 7.2.3 from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
and do what I've done from:
https://forum.xda-developers.com/showpost.php?p=79363874&postcount=366
and then the "fastboot boot boot.img" again.

I have 7.2.3, and did all the steps maybe the img I downloaded was corrupted, I'll retry that, thank you
 

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    About the Shield TV PVR Project
    I wanted to use my NVidia Shield TV not just for gaming and Netflix, but did not like the idea to loose the (in my view) really cool wifi remote and gamepad by switching to 'that other full android' image that is currently available on xda. So i decided to jump on the road and add those few additional features I was missing to the stock system by myself..

    After some (many) hours of work to get the nvidia supplied source packages trimmed down and fixing bugs in the kernel, I can finally say its running pretty good now!

    Here is what is working right now:
    - A full kernel compile can be done in just about 3-8 minutes contrary to more than one and a half hours when using the unmodified nvidia package

    - The stripped down development package I built is only taking about 1.5 GB of harddrive space, there is no need to download all of these 20+ GB of mixed stuff from the slow nvidia servers anymore, no need to wait for the repo tool to unpack and etc - its just fetch and compile a bootimage right away.

    - I have added full NTFS (r+w) support to the kernel, so you can just plug-in any ntfs formatted harddrive or usb stick and use it like the fat32 formatted drives that were already supported.

    - I have added DVBAPI support back into the kernel so you can plug-in a supported DVB-C/DVB-S/DVB-S2/DVB-T/DVB-T2 tuner stick and use it to watch, record and stream live TV from your shield - full PVR powers baby! :) (I had to patch the base kernel to allow that as there was some 32/64 bit ioctl compatibility issue that I think was one of the reasons why nvidia did not include dvbapi - it took a long time googling around to get this working..)

    - I have built the latest tvheadend server version from source aswell, on my shield it gets started using a bootscript and its really easy to install using adb

    This is my current setup:
    I have connected 3 DVBSky DVB-C/T/T2 USB tuner sticks to a powered USB 3.0 hub and plugged that into the shield. Since there were no drivers for my usb stick brand available, I have patched the dvbsky branch of the kernel tree with a backported version of these drivers. (For those of you that have different brand sticks, there are 2 other branches available, one with all the stock kernel-supplied dvb drivers, one with all the drivers from media_tree). It is now easily possible to

    watch live TV (using Kodi with tvheadend htsp plugin) with full EPG etc

    stream live TV to the kids room (my kids are using kodi installed on a fire tv stick that is connected to an old 19" lcd screen)

    stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet

    record tv shows on demand, timers can be programmed using a smartphone (tvheadend helper app) aswell as through the kodi interface

    All these features are in heavy use by my family right now and without any real impact on the overall speed of the shield console - read: completely transparent in the background! (I have attached a 500 GB USB 3.0 hard drive (ntfs formatted) to the shield for storage of the recorded tv shows - obiously.)

    Get yourself a Shield PVR
    Just grab a linux-supported tuner stick and a harddrive, flash one of the precompiled kernels and install tvheadend from my androidfilehost area - it surely is not for the fainthearted as there are currently no step-by-step instructions, but I think everyone with a little knowledge on how to use adb and fastboot can do it.

    Of course I will try to help out if you run into problems, you can post your questions/suggestions/bug reports into the issue tracker or to my thread at xda.

    Contribute
    If you want to say thanks and help continuing my work you can hit that donate button on my androidfilehost area, it is not in any way required tho. If you want to contribute code/patches/ideas - just do so using the usual channels (issue tracker, xda thread).

    How do I get set up for development?
    Check the official repo wiki page, I have added some scripting code examples and etc to the wiki there.

    Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!

    Code:
    Androidfilehost (prebuilt images): https://androidfilehost.com/?w=files&flid=48701
    Github repo: https://bitbucket.org/nopnop9090/shieldtv-kernel
    Wiki: https://bitbucket.org/nopnop9090/shieldtv-kernel/wiki
    5
    Hi all,

    Sources for Shield Experience 5.1 are on my bitbucket repo aprox 1GB to download instead of 15GB for official source.

    Precompiled kernel for 16gb shield[2015] on my dropbox here

    For 2017 shield and pro version, you can compile your kernel from my source.


    New link here
    5
    The developer is probably busy.
    If there are any other devs out there that can contribute.. don't be shy

    Hi All,

    I have compiled the kernel for SATV-3.0 with static drivers and ntfs-rw support. My cheap RTL2832U usb tuner works great.
    To autostart tvheadend provided by nopnop9090, i need to install SuperSu 2.65 through TWRP and put boot script in /su/su.d.
    You can find it in my dropbox. https: // www . dropbox . com / s / zosrn6j759bal01 / SATV.3.0.dvb.static.tar.bz2 ? dl=0

    Some adapter needs firmware files to work.

    Any reviews are appreciated.
    4
    Kernel with DVBSky module and NTFS support for 16GB Shield would be great :)

    Kernel for 16G version recompiled with builtin loadable modules and media_build modules.
    I have modified kernel to search firmware files in /data/firmware to avoid modifying /system.

    You need to load kernel modules in the right order (tuner module before dvb-usb* modules)

    https: // www. dropbox. com/s/1xbw11x4obfhf6j/kernel-modules-media_build.tar.gz?dl=0
    4
    So Firmware 3.0 is out now.
    Can you provide new modified Kernels for the new firmware?
    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 ..