Related
Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?
stm999999999 said:
Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?
Click to expand...
Click to collapse
If you gain root access to your XPERIA S(LT26i) you should be fine.
You can then use CIFS Manager and Samba Fileshaing as is your want.
I chose to use RaymanFX' ELiTE V2 Kernel on my XPERIA S in case that is a factor in making CIFS and Samba share operational, but I don't think it's required.
I'm using CIFS and Samba file sharing without any problems, no *.ko downloads required.
CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.
I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
You can find some source code patches in the internet. Maybe I'am patient enough to try building my own kernel.
stm999999999 said:
CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.
Click to expand...
Click to collapse
mattes13 said:
Maybe I'am patient enough to try building my own kernel.
Click to expand...
Click to collapse
I did build the kernel with the applied patch, but it didn't solve the problem. I guess I have to do some more research within the kernel forums. So no cifs yet.
mattes13 said:
I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
Click to expand...
Click to collapse
Okay, for anybody, who is interested: I have not tried the following using the stock kernel of .200 or .211 since I'm on Forzaferrarileo's JB kernel at the moment. However, after a lot of internet research I found out how to configure the cifs manager app to mount Samba shares again.
Share Path: //<ip>/<share>
Mount Point as you like it
Username as needed
Password as needed
Options: sec=ntlm,iocharset=utf8,unc=\\\\<ip>\\<share>
It appears that the Samba developers changed their mounting syntax. Although the app states to start the share path with the ip, you need the double slash. And although the share path is already defined, they want it again in the options with the unc option. There you need to double all backslashes. If you have spaces in the unc path, use double quotation marks around your path.
Additional info: currently, I'm using busybox version 1.20.2.
Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Sent from my LT26i using xda app-developers app
Forzaferrarileo said:
Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Click to expand...
Click to collapse
Forgot to mention that explicitly, thx.
Not sure if this question really fits in here but here it goes.
As Linux kernel is running under Android, how would one write applications that would run native (without Java overhead)? Additionally to the first question, I would like to access camera in that arrangement, like one would for example use v4l2 on PC or similarly?
Thanks,
Damjan
damjandakic said:
Not sure if this question really fits in here but here it goes.
As Linux kernel is running under Android, how would one write applications that would run native (without Java overhead)? Additionally to the first question, I would like to access camera in that arrangement, like one would for example use v4l2 on PC or similarly?
Click to expand...
Click to collapse
It really depends on the camera and the kernel the device is running.
If kernel > 2.6.26 (which it should be, as Android 1.5 was using 2.6.27 already) and your camera is supported by UVC, then it's easy (V4L being the best choice). Otherwise, you will need the source and/or binary SDK, which is usually quite difficult to get ahold of.
fhd kernel ( ZE551 ) & POSSIBLY hd (ZE550) with KVM & Bridge compiled. *need help*
MODERATOR NOTICE:
All thread posted in the Development section must have a link to kernel sources to meet GPLv2 requirements. Because this thread does not have proper sources linked and because development has stopped, the thread has been closed.
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Edit:
I uploaded a new flashable kernel img based off 2.19. This one should support: kvm, bridge and NTFS read/ *LIMITED* write, swap and ignore kernel module signatures. XDA only allows 8mb for .img files, so I tar'd it.
Edit2:
I compiled a ZE550 kernel ( called hd ) and if some brave souls want to try it, I also put together a boot.img.
Edit3:
New fhd kernel has been compiled with additional usb modules. Kernel should now load kvm related modules automatically, so you shouldn't need to use the script anymore.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Edit 4:
New fhd & hd kernels for 2.20
Edit 5:
New exfat.ko module
ycavan said:
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Click to expand...
Click to collapse
Why 2.12? 2.18 kernel source is available...
That just happened to be the kernel source linked in Android development. If this test works out, I can probably do the same thing with whichever kernel source is available.
Our phones are pretty amazing to be able to compile their own kernels natively on the device.
Sent from my ASUS_Z00AD using XDA Free mobile app
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/ *LIMITED* Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
One suggestion would be to flash the zImage using
Code:
fastboot flash zImage nameofzImage
or test it using
Code:
fastboot boot nameofzImage
but I dont know if the phone supports the "boot" command.
I´m not sure about the modules either and I can´t test it, as my phone didn´t arrive yet.
Other solution, try this:
http://forum.xda-developers.com/showthread.php?t=2670512
ycavan said:
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
Click to expand...
Click to collapse
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
TheSSJ said:
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
Click to expand...
Click to collapse
I added CONFIG_NTFS_FS=m ( you could set to that y ) and CONFIG_NTFS_RW=y in /{working directory}/device/asus/moorefield/fhd/mofd_fhd_diffconfig
when you make the kernel, it's going to ***** about the config files not matching; follow the directions and manually update all of the other config files and it will finally compile.
Building for Android is a pita. )
Well, then here come the disappointing news (I discovered that when I wanted to include NTFS USB-OTG support directly by the kernel for my TWRP and it didn't mount it as R/W):
CONFIG_NTFS_RW is just a partial write support. It won't create files or folders, it can only overwrite existing files and only by the size they currently have
config NTFS_RW
bool "NTFS write support"
This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to.
Click to expand...
Click to collapse
Only possibility available is to include ntfs-3g driver using fuse
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
ycavan said:
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
Click to expand...
Click to collapse
Please keep me posted, I'd like to remove the dependency of ntfs-3g in recovery. I fear there actually is no native support of NTFS (googling was not helpful unfortunately)
1) modify module loading function to ignore module version/magic strings.
2) compile the kernel with toolchain used by ASUS (or close to it)
3) use pre-compiled tntfs.ko from original boot.img
I don't have right now the patch for module loading procedure. Need to check old Galaxy S3/S4 custom kernels source (but it's should be easy to patch by finding error string). In time when exFat module source wasn't available, this trick was very common in samsung custom kernels for exFat support.
Thanks
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
LUCKYSHOT52 said:
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
Click to expand...
Click to collapse
It's only in theory.
In reality, there is no Z35xx support in windows, and i doubt anyone will write drivers by himself (windows isn't opensource). Officially Z35xx is Android-only SoC.
FajarMF28 said:
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
Click to expand...
Click to collapse
The source is already available, so no worries there, since this is source that Asus released.
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
ycavan said:
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
Click to expand...
Click to collapse
is there extra features such as other governor or i/o scheduler?
cangcan said:
is there extra features such as other governor or i/o scheduler?
Click to expand...
Click to collapse
To be honest? I can't remember since my main focus was getting kvm compiled in.
I've attached my .config for the 20150707 build ( in the boot image ).
I've also attached a screenshot of Windoze 7 being installed.
Commandline for Arch Linux x86_64 to start qemu-kvm to install windoze:
qemu-system-x86_64 -display none -vnc :1,password -monitor stdio -m 1G -smp 4 -enable-kvm -drive file=/mnt/0/machine1.img,format=raw -cpu host -cdrom /mnt/MicroSD/Vcd/en_windows_7.iso -boot menu=on --usbdevice tablet
breakdown of the command line:
-display none = no display, I did this to test the virtual machine. normally, you would probably use -display sdl w/ XServer-XSDL running
-vnc :1,password, This says to set up a vnc server with normal port + 1 ( 5901 ) and you expect a password to be set later
-m 1G, 1 gig of ram
-smp 4, our VM will use 4 cores
-enable-kvm, enable Kernel support Virtual Machines
-drive file=/mnt/0/machine1.img,format=raw, my "disk" file
-cpu host, use the same cpu information
-cdrom /mnt/MicroSD/Vcd/en_windows_7.iso, my Windows 7 install cd turned into an iso
-boot menu=on, enable the boot menu ( hit F12, etc.. )
--usbdevice tablet, Qemu's Vnc server sucks at tracking mouse positions so using tablet mode keeps the mouse pointer .. well on-point
Tks for share
Kernel great work
But how to install window 7 ? ?
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk
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
Great work!
I tried to follow the link to the wiki on your bitbucket, but only get a message that I don't have access to it. Maybe some permissions that should be changed?
This is excellent work. What usb tuners are supported?
---------- Post added at 10:09 PM ---------- Previous post was at 09:28 PM ----------
i just tried the version compiled on the 28th on retail firmware it doesnt boot
Wow! This is EXACTLY what I wanted to do with my Shield TV but didn't think it would be possible. Is that dvb-s2 by chance?
andersh said:
Great work!
I tried to follow the link to the wiki on your bitbucket, but only get a message that I don't have access to it. Maybe some permissions that should be changed?
Click to expand...
Click to collapse
should be fixed as of now - shame on me!
xd4d3v said:
This is excellent work. What usb tuners are supported?
---------- Post added at 10:09 PM ---------- Previous post was at 09:28 PM ----------
i just tried the version compiled on the 28th on retail firmware it doesnt boot
Click to expand...
Click to collapse
hm, please try to install the developer firmware first, and i would recommend the build id 11c80e6 for first testing - I will try to make it work on retail when everything else is a bit "matured" of course
gumbi2400 said:
Wow! This is EXACTLY what I wanted to do with my Shield TV but didn't think it would be possible. Is that dvb-s2 by chance?
Click to expand...
Click to collapse
dvb-t/t2/c/c2/s/s2 - doesent matter as long as there is a kernel driver for the tuner available. and if its not already included in the kernel you can use the media_build release where a lot more tuners are supported - its a little tricky to get it running because with media_build you would have to find out which tuner.ko file you need to "insmod" - so better try the "static" build id 11c80e6 before anything else and please post a dmesg capture if it doesnt recognize your tuner.
Haven't actually purchased a tuner yet, but am thinking about doing it soon now! I'll try and find one that's well supported under Linux already.
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
sorry for that, I made a silly mistake in my script when I built the stripped down environment and published it for the first time - i now have pushed the fixed source to the repo and a full set of new bootimages to the androidfilehost page. it should be all working now but please report any problems you may find as I cannot test everything by myself (because of lack of hardware, obviously)
could you enable Webcam drivers too so we can use Skype video
chemstar said:
could you enable Webcam drivers too so we can use Skype video
Click to expand...
Click to collapse
+1 to this.
Also, since you're compiling the kernel, it might be worth adding the systemless root.
at the end of the day, it makes no difference without the supersu app, so users can decide to have root or not, by installing the supersu app.
chemstar said:
could you enable Webcam drivers too so we can use Skype video
Click to expand...
Click to collapse
all available webcam drivers have been enabled in the media_build branch, you will have to find out which .ko modules to insmod though. the stock kernel
does not have much (if any) drivers for webcams I think.. hmm.
xd4d3v said:
+1 to this.
Also, since you're compiling the kernel, it might be worth adding the systemless root.
at the end of the day, it makes no difference without the supersu app, so users can decide to have root or not, by installing the supersu app.
Click to expand...
Click to collapse
hm, sounds like a pretty good idea - I will have a look at it shortly
Does this also work with [ROM][Full Android for Shield TV][v.2.2] shield-tv ?
ErAzOr2k said:
Does this also work with [ROM][Full Android for Shield TV][v.2.2] shield-tv ?
Click to expand...
Click to collapse
i dont know, the other rom doesnt use a full stock-based kernel I think. ask the rom creator?
This looks great, good job so far!
stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet
Click to expand...
Click to collapse
Does this mean you are using nvenc for transcoding? Or are you not using any hardware acceleration? How is that performing (how many streams can you transcode simultaneously)?
I am really looking for a solution to make transcoding easier. From what I've seen with using nvidia's nvenc is that the CPU is only decoding the streams, encoding is completely offloading, giving a massive decrease in overall server load. Now I know the new nvenc has a hard limit to allow up to 2 streams transcoding on normal GeForce gfx cards, but I wonder if the same limitation applies to the Tegra X1 chips..
In short: hardware transcoding makes this the ultimate tvheadend server/set top box!
PS: Also, the links in your Wiki entry to your Androidfilehost profile don't seem to work. I think they are account links (only for you when you are logged in). The correct link seems to be https://www.androidfilehost.com/?w=files&flid=48701. Maybe also add it linkable to your OP?
Can you please explain how exactly do we apply your file?...
Is it enough to just flash the zip file with twrp, or do we have to do something else?
nopnop9090 said:
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
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.
Since I am a new registered user at xda I am not able to provide a live download link right now - but I give you a hint: bitbucket and my nickname should get you going
Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
Click to expand...
Click to collapse
This is really great !!!!! congratulations for that... I'm looking for this since I shileld was released. Can you post a video on youtube of your system up&running tvheadend on Kodi ?
thanks!!!
Hi i am a new user, how do i download the link?
how do i download the link for the rom? thanks
nopnop9090 said:
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
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.
Since I am a new registered user at xda I am not able to provide a live download link right now - but I give you a hint: bitbucket and my nickname should get you going
Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
Click to expand...
Click to collapse
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
umoraes2009 said:
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
Click to expand...
Click to collapse
to all asking how to do this.
you don't need to root for this, however, you need to unlock the bootloader
once the bootloader is unlocked, you need to boot into fastboot mode, and flash the boot.img.
you will need root to install tvheadend though, and knowledge of command line.
If we're nice maybe we can ask nop to package it up into an apk wink wink.
I managed to play with it for a while, and installed tvheadend, just can't figure out the web-ui password!
thanks again for the great work.
let me know if I can help in anything, I'm not a developer, but used to be a Solaris sysadmin back in the day.
angel2000med said:
Can you please explain how exactly do we apply your file?...
Is it enough to just flash the zip file with twrp, or do we have to do something else?
Click to expand...
Click to collapse
currently you need to flash the image with fastboot haveing previously unlocked the bootloader.
check nopnop9090/shieldtv-kernel/wiki on bitbucket - i have added some basic instructions at the bottom of the wiki.
umoraes2009 said:
This is really great !!!!! congratulations for that... I'm looking for this since I shileld was released. Can you post a video on youtube of your system up&running tvheadend on Kodi ?
thanks!!!
Click to expand...
Click to collapse
as i am still not allowed to post links here: search youtube for my nickname, i have a small video showing kodi live tv up there. i plan on producing a complete walkthrough sometime in the future..
icombina said:
how do i download the link for the rom? thanks
Click to expand...
Click to collapse
check nopnop9090/shieldtv-kernel/wiki on bitbucket - androidfilehost link is in there. i suggest starting with the boot-099a0b601ae3-dvb_static bootimage.
umoraes2009 said:
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
Click to expand...
Click to collapse
check nopnop9090/shieldtv-kernel/wiki on bitbucket - androidfilehost link is in there. i suggest starting with the boot-099a0b601ae3-dvb_static bootimage.
xd4d3v said:
to all asking how to do this.
you don't need to root for this, however, you need to unlock the bootloader
once the bootloader is unlocked, you need to boot into fastboot mode, and flash the boot.img.
you will need root to install tvheadend though, and knowledge of command line.
If we're nice maybe we can ask nop to package it up into an apk wink wink.
I managed to play with it for a while, and installed tvheadend, just can't figure out the web-ui password!
thanks again for the great work.
let me know if I can help in anything, I'm not a developer, but used to be a Solaris sysadmin back in the day.
Click to expand...
Click to collapse
try to manually start tvheadend from adb shell for the first time like this:
Code:
/data/dvb/tvheadend -C -c /data/dvb/tvheadend/hts
(the -C will let tvheadend enter into intial setup mode where you can enter passwords etc. for subsequent starts skip -C.)
i only want to give some feedback regarding webcam drivers.
my booth devices have been recognized
unfortunately i didn't have luck getting them to work with skype. i think there is something missing inside camera hal implementation. maybe zulu can give us some usefull hint how to fix this.
Hi
first sorry for my bad english.
I would like backup my stuff every day (or week) at my local samba server. I would do this with a rsync script which will be executed by tasker. (I already have similar scripts like kill spotify app after unplug audio jack for example). But for this, I need cifs support to mount a samba share on my phone. I think I only get cifs support when I add cifs module to the kernel source and compile a kernel but I dont have an idea how do I do this. My ROM ist currently Lineage OS 17.1 (and it will be Lineage OS 18.1 very soon).
Is there a way to get cifs support?