DVB-T dongle running on Nexus 7

[Mungulz]

Might be a dumb question, but are these USB tuners digital or not? Analogue TV reception is being phased out here and all will require a digital tuner.

Sent from my Nexus 7 using Tapatalk 2

 

[lionsh]

DVB is Digital Video Broadcating

Might be a dumb question, but are these USB tuners digital or not? Analogue TV reception is being phased out here and all will require a digital tuner.

Sent from my Nexus 7 using Tapatalk 2

 

[Mungulz]

DVB is Digital Video Broadcating

Thanks for the quick response. Just confirmed that for myself with Google lol.

Off to buy a USB tuner and OTG cable.

does this work OK without an amplified antenna? Assuming close to window/outdoors in a good coverage area.

Sent from my Nexus 7 using Tapatalk 2

 

[Sikki]

Might be a dumb question, but are these USB tuners digital or not? Analogue TV reception is being phased out here and all will require a digital tuner.

Sent from my Nexus 7 using Tapatalk 2

"DVB" means "Digital Video Broadcasting"

Also, no luck on finding channels on mine. Hmm.

 

[lionsh]

i have copied the firmware also. did you d\l it from http://linuxtv.org/wiki/index.php/DV...T_USB_Devices?

when you ran startddvb script did you receive any errors? I get an error that the files in /dev/dvb/adapter0 are missing.
only when i create the files manually it passes, but then i can't initialize droid tv.

which kernel version do you use? i have 3.1.10 g52027f9

can you upload the files+script that you used?

thanks.

Quote:

"DVB" means "Digital Video Broadcasting"

Also, no luck on finding channels on mine. Hmm.

 

[Sikki]

i have copied the firmware also. did you d\l it from http://linuxtv.org/wiki/index.php/DV...T_USB_Devices?

when you ran startddvb script did you receive any errors? I get an error that the files in /dev/dvb/adapter0 are missing.
only when i create the files manually it passes, but then i can't initialize droid tv.

which kernel version do you use? i have 3.1.10 g52027f9

can you upload the files+script that you used?

That's where I got my firmware, yes.

I still get the init failed on all files, but I assume it's because they're already been "done" once, so theres no need to do it again. Thus it saying "File Exists). So on the first time I added a .ko file to the script, that file didn't produce an error.

Upon further examination, and don't ask me why, it started working when I was browsed to the dev/dvb/adapter0 -folder with the system mounted as Write with my EsExplorer as I plugged in my receiver. Only then will it create the 4 files needed in the folder, and I have no idea why. Maybe because of the terminal used?

So far no luck with getting any channels though. It shows going through all the different frequencies, but gives an error at the end.

 

[lionsh]

Thanks for the info. i know that the second time it says file exists, but for some reason file dvb-usb-af9015.ko is always failed with file not found although it is. and running demsg gives some error in this ko file. it is strange that it works for you... since we use the same files and same system.

i'll keep investigating further.

That's where I got my firmware, yes.

I still get the init failed on all files, but I assume it's because they're already been "done" once, so theres no need to do it again. Thus it saying "File Exists). So on the first time I added a .ko file to the script, that file didn't produce an error.

Upon further examination, and don't ask me why, it started working when I was browsed to the dev/dvb/adapter0 -folder with the system mounted as Write with my EsExplorer as I plugged in my receiver. Only then will it create the 4 files needed in the folder, and I have no idea why. Maybe because of the terminal used?

So far no luck with getting any channels though. It shows going through all the different frequencies, but gives an error at the end.

 

[Sikki]

Thanks for the info. i know that the second time it says file exists, but for some reason file dvb-usb-af9015.ko is always failed with file not found although it is. and running demsg gives some error in this ko file. it is strange that it works for you... since we use the same files and same system.

i'll keep investigating further.

Can't say for certain, but the af9015 fail seemed to go away when I added the af9013.ko file and put it to the script as well.

A lot of this goes slightly over my head, and I'm pretty sure there's more randomness than patterns in what happened.

 

[Psych0Chimp]

Mine's a Freecom DVB-T USB Stick that I got working using dvb-usb-dtt200u.ko and zl10353.ko. I also put dvb-usb-wt220u-zl0353-01.fw in /etc/firmware.

You have to make sure all your permissions are correct. The first script posted has a mistake in it which doesn't set the correct permissions for the /dev/dvb/adapter0 directory.

Is Droid TV working for those who have got their tuner in the "warm state"?

 

[bmxchampga]

Is there any way to get an ATSC tuner running using this method?

Sent from my ADR6400L using Tapatalk 2

 

[martintzvetomirov]

I don't have the time to go through all individual questions now but will try to generalize

Yes, droid TV is highly unstable. I started writing my own app and will do the tuning via NDK so will see I don't want to give promises when it's going to be ready since it's a learning experience for me as well.

If you get "file missing" error with dmesg saying "missing symbol" then there's a missing dependency. I.e. modules need to be loaded in order and you didn't load a module in this case. I can try to figure out which module was missing by the exact error, but as I said I currently don't have enough time.

A device will work only if it's in a warm state and all permission s are correctly set. The droidTv will do the scanning. If for some reason something behaves funny, try with a hub with external power. If the device is in warm state and permission s are set I see no reason that it won't work. Unless ofcourse there `s something wrong with droidtv, but we don't currently have any alternatives...

In theory everything that can be compiled to Linux from source can be compiled to android. But for example some devices have precompiled drivers which do not work (I have an AverMedia Volar HX which has a proprietary driver precompiked for x86, so no chance running on Android...)

 

[lionsh]

Thanks Martin,

Can you please explain how to compile these KO files, what are do i need? How to compile them for a different Kernel/android version?

Thanks a lot.

I don't have the time to go through all individual questions now but will try to generalize

Yes, droid TV is highly unstable. I started writing my own app and will do the tuning via NDK so will see I don't want to give promises when it's going to be ready since it's a learning experience for me as well.

If you get "file missing" error with dmesg saying "missing symbol" then there's a missing dependency. I.e. modules need to be loaded in order and you didn't load a module in this case. I can try to figure out which module was missing by the exact error, but as I said I currently don't have enough time.

A device will work only if it's in a warm state and all permission s are correctly set. The droidTv will do the scanning. If for some reason something behaves funny, try with a hub with external power. If the device is in warm state and permission s are set I see no reason that it won't work. Unless ofcourse there `s something wrong with droidtv, but we don't currently have any alternatives...

In theory everything that can be compiled to Linux from source can be compiled to android. But for example some devices have precompiled drivers which do not work (I have an AverMedia Volar HX which has a proprietary driver precompiked for x86, so no chance running on Android...)

 

[martintzvetomirov]

First get the cross compiler by doing

git clone https://android.googlesource.com/platform/prebuilt

This is a really useful wiki entry. Follow the steps they recommend for compiling the kernel.

http://code.google.com/p/smartphonebrainscanner2/wiki/Nexus7#Compiling_Kernel

I think on step "Configure kernel. Two things you will want to change are: " you would like to select the DVB drivers to be configured as modules.

Afterwords rather than compiling the whole kernel you would do

make ARCH=arm SUBARCH=arm CROSS_COMPILE=[B]PUT_YOUR_CROSS_COMPILER_HERE[/B] modules

Where PUT_YOUR_CROSS_COMPILER_HERE is (for me for example it's crosscompiler/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-)

In theory this should work. And it should be easy enough. Please share if you had any success.

Otherwise here's what I actually did.

I did it a bit differently. My "kernel configuration" step was modifying the drivers/media/dvb/dvb-usb/Makefile, by changing all obj-SOMETHING to obj-m i.e. forcing components to be built as modules. And modifying the /arch/arm/configs/tegra3_android_defconfig b/arch/arm/configs/tegra3_android_defconfig to include

 CONFIG_DVB_CORE=m
+CONFIG_USB=m
+CONFIG_I2C=m
 CONFIG_DVB_USB=m
+CONFIG_RC_CORE=m

Then doing

make ARCH=arm SUBARCH=arm CROSS_COMPILE=[B]PUT_YOUR_CROSS_COMPILER_HERE[/B] tegra3_android_defconfig

Before compiling modules. I also needed to update the main Makefile to always output the version of the Android kernel I had for my nexus by doing

kernelversion:
	@echo $(KERNELVERSION)

(around line 1468 in the main Makefile). And adding this to top of the Makefile

VERSION = 3
PATCHLEVEL = 1
SUBLEVEL = 10
EXTRAVERSION = -g52027f9

. I hope I'm not missing something...

P.S. At some point during the next month I will sit and write a comprehensive guide on how to build the modules, since to be honest I did a lot of "hacking around" to make it work, there's definitely a simple way. (even possibly make a script that does the compilation for you)

 

[martintzvetomirov]

I created the files :
frontend0
demux0
dvr0
dvr0.ts

in /dev/dvb/adapter0 and now i don't get an error on running sh startdvb (except on *9015.ko being not found)
when i open droid tv and select DVB-T and some country using dvb-t i get an error of unable to determine frontend
so something still missing/wrong.

UPDATE

using dmesg i saw an error for init 9015.ko - Unknown symbol af9013_attach (err 0)
maybe the compilation of this driver was not right, since it is 9015 and not 9013?

I do hope that it's the lack og 9015.ko which is keeping me from watching DVB-T. If I had the dvb-usb-IT9135.ko file i could try a different DVB-T tuner.

You would need to insmod af9013.ko before insmod-ding dvb-usb-af9015.ko

 

[joerlo]

Loving the progress on this, for me dtv isn't what I'm looking for I would love to see a working live video input displayed on my nexus for a project I'm working on using a usb composite video in Interface the type you use to rip vhs to the computer, I'm guessing and hoping the solution is pretty much the same? Any advise and help on this please?
Thanks

Also interested in this. Keep us posted.

 

[micks_address]

keeping an eye on this thread as im currently withouth my nexus 7 but should have it back over the weekend.. if anyone gets working with a ps3 play tv tuner let us know.. cheers mick

 

[impoze]

i've got up to droidtv scanning, lists a lot of numbers e.g. 592599: (time:04:24)
and then doesnt do anything

is my reception too weak?

thanks

can't wait to see your alternative to droidtv, keeps crashing

----------------------------

OK, plugged into wall aerial and could scan for channels but now when I open a channel it just stays black

am I missing something?

thanks

 

[Kas206]

I cant get it to work. I got all the modules files in the right place. but i keep getting the error below

This is what i get when I dmesg. So i know my dongle is recognised

This what happenes when i start Droid TV

 

[martintzvetomirov]

I cant get it to work. I got all the modules files in the right place. but i keep getting the error below

This is not an error. This is a success It means that the modules are already loaded. Now you have everything set up! You need to go to /dev/dvb with your favorite file explorer (like ES) and change the permissions to this dir and all subdirs and files to writable and voilà! It should be working

i've got up to droidtv scanning, lists a lot of numbers e.g. 592599: (time:04:24)
and then doesnt do anything

is my reception too weak?

thanks

can't wait to see your alternative to droidtv, keeps crashing

----------------------------

OK, plugged into wall aerial and could scan for channels but now when I open a channel it just stays black

am I missing something?

thanks

Where you from? There is a chance that DVB-T in your country could be MPEG-4 and that DroidTV might only support MPEG-2. Those are just speculations though. Is your dongle working fine with the same antenna via your PC?


Sent from my Nexus 7 using xda app-developers app

 

[Kas206]

I found another way to stream from the PC to Nexus 7

Connect the adapter to your pc

Download Nero Media Home from the link below. Run the setup and scan for TV channels.

http://www.softpedia.com/get/Internet/File-Sharing/Nero-MediaHome.shtml

Install DK UPNP/DLNA Player from the Play store (Only one that works for me)

https://play.google.com/store/apps/details?id=com.upnp.upnpctrl&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS51cG5wLnVwbnBjdHJsIl0.

open the app and click on nero media home and all channels should be listed there.

Use Mx player to play them