With Franco kernel shows this, is there any way the operation of DVB-T?
Last edited:
DVB-T dongle running on Nexus 7
- Thread starter martintzvetomirov
- Start date
I had the same issue. If someone had a compiled version of kernel modules and driver for rtl2832U it would be very kind to share with us these files.
PS: I'm running Android 4.3 with kernel 3.1.10-g1e8b3d8
Thank you in advance
Exact same issue here...
Code:
git checkout -b new_branch_name
HEAD is now at 1e8b3d8... ashmem: avoid deadlock between read and mmap calls
HEAD is now at 1e8b3d8 ashmem: avoid deadlock between read and mmap calls
*** Enabling DVB-T support ***
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
arch/arm/configs/tegra3_android_defconfig:594:warning: override: reassigning to symbol RC_CORE
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
make: *** Pas de règle pour fabriquer la cible « modules_prepare ». Arrêt.
*** Compiling drivers ***
WARNING: Symbol version dump /home/paille/dvb/ksrc/Module.symvers
is missing; modules will have no dependencies and modversions.- No rule to make target "modules_prepare". Stop.)
But I have this function not implemented as seen earlier and insmod is not really happy
I use an old NEXUS 7 with WiFi and with g1e8b3d8...
Last edited:
I just managed to compile the files for my kernel and now got rid of the "exec format error". But know I got another problem:
After executing the "startdvb" script I get this error:
"Unable to chmod /dev/dvb/adapter0/dvr0.ts: No such file or directory"
But the files exists. I also tried DroidTV but it doesn't work.
Nevermind got it all working finally. The only thing which sucks is that DroidTV and SDR Touch are not working together. Anyone got a solution for that?
After executing the "startdvb" script I get this error:
"Unable to chmod /dev/dvb/adapter0/dvr0.ts: No such file or directory"
But the files exists. I also tried DroidTV but it doesn't work.
Nevermind got it all working finally. The only thing which sucks is that DroidTV and SDR Touch are not working together. Anyone got a solution for that?
Last edited:
I don't know how much trouble as I have no idea how to compile, but if not too much can someone compile for USB ROM.. g25ab3af
Thanks
Thanks
Hello, can someone help me?
I have Android tablet with kernel 3.0.8+ and ICS 4.0.3 rooted and RTL2832 (ezcap dvbt stick).
Having the error:
"insmod: init_module 'dvb-usb-rtl2832u.ko' failed (Exec format error)"
..and same errors for other modules..
I sow DVB-T drivers that are for my device here on realtv.neoz.in
but when you extract and run script, you see that that are wrong modules in archive (3.1.10 and i need 3.0.8+).
Can someone, please, compile all dvb-t modules to use with kernel 3.0.8+ (ICS 4.0.3) ?
So, no 3.0.8 but 3.0.8+ ?
Please?
Thanks
RK3066 Kernel 3.0.8+ RTL2832U.ko
To me it has not worked because it hasn't built the tuner of my device, but it left to add to the kernel 3.0.8 + ARMv7 (RK3066). try it to see if it work for you.
Best regards.
Parron.
Here you are. After 3 days of learning, a lot of coffe and cigarettes. I managed to compile this module against a kernel 3.0.8 + BQ Maxwell PLUS (Jelly Bean).
To me it has not worked because it hasn't built the tuner of my device, but it left to add to the kernel 3.0.8 + ARMv7 (RK3066). try it to see if it work for you.
Best regards.
Parron.
The problem with compiling was that google disabled by default loadable module support in config file.
In script you should add after line >
# Write the requirements for DVB modules into the default tegra configuration file
echo " *** Enabling DVB-T support ***"
sed -i '$ a\
CONFIG_MODULES=y\
before
CONFIG_DVB_CORE=m\
In script you should add after line >
# Write the requirements for DVB modules into the default tegra configuration file
echo " *** Enabling DVB-T support ***"
sed -i '$ a\
CONFIG_MODULES=y\
before
CONFIG_DVB_CORE=m\
Last edited:
New app?
EDIT
Found a copy of droidtv.apk in the attachment here www . 2shared . com/file/uUlHRMfQ/dvbt-android308 . html
Thanks to those who posted at /www . slatedroid . com/topic/18812-howto-dvb-usb-support/page__st__60
The link to the droidtv app is dead and all of my searches have been dead-end also. Anyone have a link to a working app?:fingers-crossed:
EDIT
Found a copy of droidtv.apk in the attachment here www . 2shared . com/file/uUlHRMfQ/dvbt-android308 . html
Thanks to those who posted at /www . slatedroid . com/topic/18812-howto-dvb-usb-support/page__st__60
Last edited:
Which android version did you use the modules with? I'm wondering which kernel version the modules are compiled against.
---------- Post added at 02:09 PM ---------- Previous post was at 01:53 PM ----------
modinfo media/dvb/dvb-core/dvb-core.ko
filename: dvb-t/media/dvb/dvb-core/dvb-core.ko
license: GPL
author: Marcus Metzler, Ralph Metzler, Holger Waechtler
description: DVB Core Driver
depends:
vermagic: 3.0.8++ preempt mod_unload modversions ARMv7
parm: dvbdev_debug:Turn on/off device debugging (default
parm: debug:Turn on/off debugging (default
parm: dvb_demux_speedcheck:enable transport stream speed check
parm: dvb_demux_tscheck:enable transport stream continuity and TEI check
parm: cam_debug:enable verbose debug messages
parm: dvb_mfe_wait_time:Wait up to <mfe_wait_time> seconds on open() for multi-frontend to become available (default:5 seconds)
parm: dvb_powerdown_on_sleep:0: do not power down, 1: turn LNB voltage off on sleep (default)
parm: dvb_override_tune_delay:0: normal (default), >0 => delay in milliseconds to wait for lock after a tune attempt
parm: dvb_force_auto_inversion:0: normal (default), 1: INVERSION_AUTO forced always
parm: dvb_shutdown_timeout:wait <shutdown_timeout> seconds after close() before suspending hardware
parm: frontend_debug:Turn on/off frontend core debugging (default
parm: dvb_net_debug:enable debug messages
dmesg says:
frustrating! just post sources instead of the .ko objects.
so there's a Nexus 7 (2013) kernel that supposedly has the DVB modules prebuilt for Android 4.3
http://forum.xda-developers.com/showthread.php?t=2389022
I am already on Kitkat, so I am not sure if reverting back to try this out... Anyone here interested in trying it?
Also note that you will need a non-caf rom (regular Cyanogenmod wont work). Try this if you want
http://forum.xda-developers.com/showthread.php?t=2545197
http://forum.xda-developers.com/showthread.php?t=2389022
I am already on Kitkat, so I am not sure if reverting back to try this out... Anyone here interested in trying it?
Also note that you will need a non-caf rom (regular Cyanogenmod wont work). Try this if you want
http://forum.xda-developers.com/showthread.php?t=2545197
Saving time and your life: no need to recompile
For those who have another kernel version, you don't need to recompile dvb modules. If your kernel version is not in git revisions, you will just fail with 'fatal: ambiguous argument '3.1.10-xxxxxxxx': unknown revision or path not in the working tree'. Fortunately, there's a much faster and much simpler way to get dvb modules for your kernel version. You don't need git, make, toolchain, kernel source...
Nearly every Android kernel for Nexus 7 is based on 3.1.10 linux kernel (because of nvidia's closed source driver for graphics card), so kernel version for your Nexus 7 will be always 3.1.10-xxxxxxxx.
You can get directly precompiled binary modules (aka *.ko files) at post #1 and patch them for your kernel version:
Alternaties: Get precompiled binary modules at post #80 (more complete than modules from post #1) and patch them:
Alternaties 2: Post #129, the same way:
Basically this command replaces 'magic version' in *.ko files. Version mismatch will prevent insmod with an 'exec format error'.
Replace xxxxxxxx by your kernel-version, for example if your kernel version is 3.1.10-g30c5396, use:
That's it!
More info: This way works with Cyanogen Mod kernels/ROMs!!!
For those who have another kernel version, you don't need to recompile dvb modules. If your kernel version is not in git revisions, you will just fail with 'fatal: ambiguous argument '3.1.10-xxxxxxxx': unknown revision or path not in the working tree'. Fortunately, there's a much faster and much simpler way to get dvb modules for your kernel version. You don't need git, make, toolchain, kernel source...
Nearly every Android kernel for Nexus 7 is based on 3.1.10 linux kernel (because of nvidia's closed source driver for graphics card), so kernel version for your Nexus 7 will be always 3.1.10-xxxxxxxx.
You can get directly precompiled binary modules (aka *.ko files) at post #1 and patch them for your kernel version:
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-xxxxxxxx/g' *.ko
Code:
perl -pi -e 's/3.1.10-g22b4fcd/3.1.10-xxxxxxxx/g' *.ko
Code:
perl -pi -e 's/3.1.10-g05b777c/3.1.10-xxxxxxxx/g' *.koReplace xxxxxxxx by your kernel-version, for example if your kernel version is 3.1.10-g30c5396, use:
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-g30c5396/g' *.koMore info: This way works with Cyanogen Mod kernels/ROMs!!!
Last edited:
Some useful troubleshooting tips
I don't know if there is still someone who is interested on this, but here's some useful tips from my experience. I hope you can use these tips when you get problems.
- The folder for firmware is /system/etc/firmware (the same as /etc/firmware), not /lib/firmware. You need to remount read-write /system partition and / partition (using ES Manager, for example) to put firmware into its right place.
- If you experience 'Exec format error' while insmod, it may be because of version mismatch between *.ko module and kernel version (check with dmesg). Use right version for your modules or see my above post to patch *.ko module.
- If you experience 'No such file or directory' while insmod... Well, this is a misleading error message. If you check with dmesg, you will see Unknown symbol <some symbol name>... It's because of dependency between modules, at least one required module is not loaded before the current module. One line for RTL2832U based DVB-T dongle after insmod dvb-usb is enough, but one line for many DVB-T dongles is not enough. For example, dvb-usb-dib0700 depends on dibx000_common, dib7000p, dib0090, dib7000m, dib0070, dib8000, dib9000, dib3000mc, s5h1411, lgdt3305... You need insmod all these required modules before insmod dvb-usb-dib0700.ko. Failing to do that, you will get 'Unknown symbol' in dmesg, and 'No such file or directory' error.
To know which modules are required for your dongle, and which module depends on which modules, the easiest way is plug your dongle into a Linux PC (Ubuntu, for example) and check with 'lsmod' in linux terminal. Your dongle must work on Linux before it can work on Android.
Another way is know which modules are required and dependency is dmesg and guessing, or better with grep. For example, if insmod xxx.ko gives you Unknown symbol <some symbol name> in dmesg, use:
grep <the unknown symbol name> *.ko
to know which module yyy.ko containing that symbol name (because xxx.ko depends on yyy.ko)
- Use chmod -R 777 /dev/dvb* in startdvb
I don't know if there is still someone who is interested on this, but here's some useful tips from my experience. I hope you can use these tips when you get problems.
- The folder for firmware is /system/etc/firmware (the same as /etc/firmware), not /lib/firmware. You need to remount read-write /system partition and / partition (using ES Manager, for example) to put firmware into its right place.
- If you experience 'Exec format error' while insmod, it may be because of version mismatch between *.ko module and kernel version (check with dmesg). Use right version for your modules or see my above post to patch *.ko module.
- If you experience 'No such file or directory' while insmod... Well, this is a misleading error message. If you check with dmesg, you will see Unknown symbol <some symbol name>... It's because of dependency between modules, at least one required module is not loaded before the current module. One line for RTL2832U based DVB-T dongle after insmod dvb-usb is enough, but one line for many DVB-T dongles is not enough. For example, dvb-usb-dib0700 depends on dibx000_common, dib7000p, dib0090, dib7000m, dib0070, dib8000, dib9000, dib3000mc, s5h1411, lgdt3305... You need insmod all these required modules before insmod dvb-usb-dib0700.ko. Failing to do that, you will get 'Unknown symbol' in dmesg, and 'No such file or directory' error.
To know which modules are required for your dongle, and which module depends on which modules, the easiest way is plug your dongle into a Linux PC (Ubuntu, for example) and check with 'lsmod' in linux terminal. Your dongle must work on Linux before it can work on Android.
Another way is know which modules are required and dependency is dmesg and guessing, or better with grep. For example, if insmod xxx.ko gives you Unknown symbol <some symbol name> in dmesg, use:
grep <the unknown symbol name> *.ko
to know which module yyy.ko containing that symbol name (because xxx.ko depends on yyy.ko)
- Use chmod -R 777 /dev/dvb* in startdvb
Last edited:
Replace xxxxxxxx by your kernel-version, for example if your kernel version is 3.1.10-g30c5396, use:
That's it!
More info: This way works with Cyanogen Mod kernels/ROMs!!![/QUOTE]
Sure that's a noob question...
Do you run that patch on the device, meaning via a terminal window or adb? Just unzipping the modules and execute in that folder or do I think to easy? Thanks for helping.
Gesendet von meinem Nexus 7
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-g30c5396/g' *.koMore info: This way works with Cyanogen Mod kernels/ROMs!!![/QUOTE]
Sure that's a noob question...
Do you run that patch on the device, meaning via a terminal window or adb? Just unzipping the modules and execute in that folder or do I think to easy? Thanks for helping.
Gesendet von meinem Nexus 7
Code:
02-13 10:08:30.860: E/AndroidRuntime(2406): FATAL EXCEPTION: main
02-13 10:08:30.860: E/AndroidRuntime(2406): Process: com.chrulri.droidtv, PID: 2406
02-13 10:08:30.860: E/AndroidRuntime(2406): java.lang.NullPointerException
02-13 10:08:30.860: E/AndroidRuntime(2406): at com.chrulri.droidtv.ScanActivity.setEnabled(ScanActivity.java:885)
02-13 10:08:30.860: E/AndroidRuntime(2406): at com.chrulri.droidtv.ScanActivity$AsyncScanTask.onCancelled(ScanActivity.java:932)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.AsyncTask.onCancelled(AsyncTask.java:405)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.AsyncTask.finish(AsyncTask.java:630)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.AsyncTask.access$600(AsyncTask.java:177)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:645)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.Handler.dispatchMessage(Handler.java:102)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.os.Looper.loop(Looper.java:136)
02-13 10:08:30.860: E/AndroidRuntime(2406): at android.app.ActivityThread.main(ActivityThread.java:5017)
02-13 10:08:30.860: E/AndroidRuntime(2406): at java.lang.reflect.Method.invokeNative(Native Method)
02-13 10:08:30.860: E/AndroidRuntime(2406): at java.lang.reflect.Method.invoke(Method.java:515)
02-13 10:08:30.860: E/AndroidRuntime(2406): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
02-13 10:08:30.860: E/AndroidRuntime(2406): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
02-13 10:08:30.860: E/AndroidRuntime(2406): at dalvik.system.NativeStart.main(Native Method)could someone pls reupload nexusdvb.rar or the apk....
nexus 7 2012, kernel is perfect for the first option.
Much appreciated and thanks guys
nexus 7 2012, kernel is perfect for the first option.
Much appreciated and thanks guys
ko files for 3.4.0 kernel
hi
can anyone plz compile and upload ko files for kernel 3.4.0-perf-g1bd8e16 ( sony xperia tx android 4.3 )
i tried this post :
http://forum.xda-developers.com/showpost.php?p=50145034&postcount=254
but no success :crying:
when i enter : insmod dvb-core.ko
i get 'exec format error'
thanks in advance :good::fingers-crossed:
hi
can anyone plz compile and upload ko files for kernel 3.4.0-perf-g1bd8e16 ( sony xperia tx android 4.3 )
i tried this post :
http://forum.xda-developers.com/showpost.php?p=50145034&postcount=254
but no success
:crying:when i enter : insmod dvb-core.ko
i get 'exec format error'
thanks in advance :good::fingers-crossed:
Hi,
can someone compile files for Nexus 7(2012) with Android 4.4.2 and 3.1.10-g4776c68 kernel?
I don't have linux...
Thank you guys...
can someone compile files for Nexus 7(2012) with Android 4.4.2 and 3.1.10-g4776c68 kernel?
I don't have linux...
Thank you guys...
New posts
-
[10][UNOFFICIAL] CarbonROM | cr-8.0 [satsuki]- Latest: Omidbabadi11
-
-
{ROM}{A50}{OneUI-2.5} Infinity OS v4.0
- Latest: Subodh.993435
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone