Related
Have this working well and thought this info may help others...
First, your phone needs to be rooted and busybox properly installed. If you've rooted in the past few days, you're fine as the current payload-update.zip does install busybox with all of the links, but if you rooted early please confirm this before continuing.
Next, grab the tun.ko module from the OpenVPN thread.
Then follow the instructions for the Motorola Droid at the VPN Connections site, using the tun.ko you downloaded previously. The one caveat here is that you have to copy the module in recovery on the Incredible as we don't yet have rw access to the /system partition when booted normally.
Once you've restarted your phone after installing tun.ko, just install the latest VPN Connections apk and you're ready to go!
One point that confused me (for longer than I care to admit) is that once you create a VPN profile, you have to long-press on it to bring up the menu for connect/disconnect.
Enjoy!
Dave
which vpn connections. I downloaded latest from the store it opened but did not work.
then tried the latest from the site and it forces close. I'll start over tonight and try again.
-------------------------------------
Sent via the XDA Tapatalk App
I was working on this the other day, but I cannot get the phone to connect to my company's VPN - I setup the IPSEC ID/PW correctly as well as my user IP/PW, but I get an ISAKMP_N_AUTHENTICATION_FAILED. The one thing I didn't do was copy tun.ko in recovery mode - I just did a modprove /sdcard/tun.ko...it didn't complain and it seems like VPN Connections can find the device node without a problem.
On my linux box, I can run the same config options in vpnc and connect no problem...
I got it working after a couple days playing with it. My problem was that I had not installed busybox to xbin like their instructions outlined since it was already installed to sbin. once installed to xbin and proper permissions were granted, it worked like a charm.
Please someone post a complete how to. I cannot get this working. Busybox will not "--install" to xbin
Is there a secrete to getting busybox installed? I know this is weak sauce, but I need help.
Did you try installing busybox while in recovery mode?
where do I install busybox? /system/xbin or sbin?
Kulaa said:
where do I install busybox? /system/xbin or sbin?
Click to expand...
Click to collapse
I've got it in both places. It needs to be in xbin for the vpnc-script. I tried modifying the vpnc-script but running in to too many problems.
Those to configured their ASA
I am trying to setup the ASA for this VPN. Numerous vague (to me) unresolved errors. Phase 1 completes (easy).
Phase 2 Failure: Mismatched attribute types for class Encapsulation Mode: Rcv'd: Tunnel Cfg'd" Transport
Group = <group>, Username = <username>, IP = <IP Address>, All IPSec SA proposals found unacceptable!
" " Duplicate Phase 2 packet detected. No last packet to retransmit.
I am not finding the answers to these issues. I have not been working on VPNs for long but have setup A LOT of client (Any Connect & SSL) VPNs. I tried to "match" those configurations and have failed.
Anyone know of a tut they used to set the VPN up on the Firewall side? Im sure one of these guys I work w/ can set it up in mins but learning the hard way is what "they" prefer. < a week later is enough, I concede!
Bump ~ 10 ~
Bump ~ 10 ~
Console output?
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
supagene said:
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
Click to expand...
Click to collapse
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
johnnybags said:
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
Click to expand...
Click to collapse
./vpnc --script ./vpnc-script --gateway gateway.domain.com --id "Default Initial G
roup" --username supagene
Enter IPSec secret for Default Initial [email protected]: *******
Enter password for [email protected]: *******
uname: not found
basename: not found
grep: not found
which: not found
grep: not found
which: not found
grep: not found
which: not found
[: not found
readlink: not found
[: not found
[: not found
hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)(24)
check group password!
I know about the comment to check the group password, but I copy and pasted it so I know it is correct. Any suggestions? Do I copy the busy box from sbin to xbin or do I need to look for another busybox, where do you recommend me getting it form? Sorry for the noob questions.
Ok So I looked and found that the Procudures I followed for Rooting didn't actually copy busybox to xbin so maybe the first post should be updated to mention to check that xbin actually has busybox. I used the same busybox that was included in the rooting guide.
Now I'm at a different error.
Error binding to source port. Try '--local-port 0'
Failed to bind to 0.0.0.0:500: Address already in use
that's fine, it means you probably have another process of vpnc running that didn't terminate. just ad --local-port 0 to the end of your command line.
So how is your ASA configured? Is it the latest software or 8.2? ???
Kulaa said:
So how is your ASA configured? Is it the latest software or 8.2? ???
Click to expand...
Click to collapse
Not sure. I just know that the Admin can connect with his Cyanogen Modded G1 and it works great for him. He has his NAND fully unlocked of coarse.
Thanks for all the help I'll post my next issue tomorrow.
Following this thread that was linked for helping to get this working on the Incredible.
I'm getting a constant "unable to connect" error... Where do I need to enable logging to find out more about where the error is happening at? On my ASA or on the Incredible?
Thanks.
I've never got it working but if you look above you'll see how I ran this thin in adb shell. That will output everything to console and tell you what is wrong.
I have decided not to build a ROM anymore. Instead, I have been working on the "Proxy Configuration Tool for Alternate Carriers" so that you can use almost ANY ROM (including CM6) with MetroPCS AND Cricket, yes, the Proxy Configuration Tool for Alternate Carriers will also support Cricket.
As you can see, the Proxy Configuration Tool for Alternate Carriers is an open-source project and you can contribute to it.
Here's the current TODO list:
- BUG: Proxy actually not updating properly when setting it through the sqlite db.
- Find out the correct ip for the mms proxy server for both MetroPCS and Cricket.
- Find out the correct network interface used by the Motorola Droid on FroYo.
- Find out the correct eri.xml file for cricket.
- Setup screen first time it runs & check for the following on every boot.
- Automatically setup APN.
- Check build.prop and modify it if it's needed (backup too) (ask for restart if modified)
- Check /data/eri.xml and install the new one if it's needed (backup too) (ask for restart if installed)
- Check for u2nl binary, if not available install it in /system/bin/, it's in the assets folder. (ask for restart if installed)
- Check for sqlite3 binary, if not available install it in /system/xbin/, it's in the assets folder. (ask for restart if installed)
- Drop database tables and replace them with appropriate Carrier Settings in: /data/data/com.android.providers.telephony/databases/telephony.db
- Document, organize and maybe improve configuration screen.
- It needs a better icon.
As you see, at this point is not complete, mostly due to the fact that the Proxy is not changing properly unless you reboot. It must be a stupid mistake on my part. I have been really busy lately and I have only been working on this when I get some free time, I figured somebody could contribute to this
If you'd like to test it go to the github link here and click on the Downloads tab and there should be an alpha version in there. I'll be building new versions whenever I clear out any of the items in the TODO list above.
Thank you.
[RESERVED]
How do you get metropcs on the Dinc....I would love to know
Sent from my ADR6300 using XDA App
there's shops that will flash any cdma phone over to metro. That's why you see sprint and verizon phones with bad ESN #s selling on craigslist
mexicanigga said:
How do you get metropcs on the Dinc....I would love to know
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
- Use the ##778 programming instruction just like as if you were flashing a Droid Eris.
- Find somebody (a dealer most likely) to put the ESN into MetroPCS's database.
- Flash this rom (hopefully it'll be completely done soon)
WOW!! Ok I am currently running CyanogenMod 6.0RC1 on a HTC Sprint Hero and had a vendor here in town who gets ALL Verizion\Sprint CDMA phones on MetroPCS hook me up. He uses DamageControl 1.0 and everything works except the market of course..It does work on WiFi however.
My problem began when I just did NOT have consistent internet. It just was hit and miss. WiFi worked no problems. So I started messing around with different ROMS with NO luck at all. I have wiped and wiped (phone and SD card)everything you could do..Still notta!!! So I am super curious if this would work? I really just need my dam internet to work..It would be awesome if it was on this CyanogenMod 6 ROM...It's smoking and appears to be the best ROM I have found for a Hero..Man if anyone could help me get this baby on the net...I would be willing to pay. I think my settings are off honestly...HELP!
Your thoughts?
CyborgNM156 said:
WOW!! Ok I am currently running CyanogenMod 6.0RC1 on a HTC Sprint Hero and had a vendor here in town who gets ALL Verizion\Sprint CDMA phones on MetroPCS hook me up. He uses DamageControl 1.0 and everything works except the market of course..It does work on WiFi however.
My problem began when I just did NOT have consistent internet. It just was hit and miss. WiFi worked no problems. So I started messing around with different ROMS with NO luck at all. I have wiped and wiped (phone and SD card)everything you could do..Still notta!!! So I am super curious if this would work? I really just need my dam internet to work..It would be awesome if it was on this CyanogenMod 6 ROM...It's smoking and appears to be the best ROM I have found for a Hero..Man if anyone could help me get this baby on the net...I would be willing to pay. I think my settings are off honestly...HELP!
Your thoughts?
Click to expand...
Click to collapse
It will work for you, but you must be sure to take one very important step before you attempt this, or you will end up with a bricked phone.
Buy a HTC Droid Incredibile
Using this rom, or any other rom for the incredible on a device that is not an incredible will result in an unusable phone, if not bricked forever!
Teksu said:
It will work for you, but you must be sure to take one very important step before you attempt this, or you will end up with a bricked phone.
Buy a HTC Droid Incredibile
Using this rom, or any other rom for the incredible on a device that is not an incredible will result in an unusable phone, if not bricked forever!
Click to expand...
Click to collapse
That's completely right.
The beauty of what I'm doing here, is that, just like I did for the Droid Incredible and the Droid, it could also be done for the Hero and the EVO, since CM supports all of these devices. As long as the source is completely open of course.
Once I fix these issues with the u2nl binary not working properly, I'll update my winzip and build the "roms" for the Droid, EVO and Hero.
For now, this build above only works for the Droid Incredible.
Nice would this work for my flash metropcs hero? Please let me know.
Thanks
velazcod said:
I have forked and prepared a vendor repo to build CM6 for MetroPCS on the Dinc.
DO NOT FLASH THIS UNLESS YOUR PHONE IS ON METROPCS AND YOU KNOW WHAT METROPCS IS.
Reason why I did this was so that anyone that wanted to "flash" a Dinc/Droid to MetroPCS didn't have so much of a hard time doing it, and also so that everything worked out of the box (including internet on apps, connected to wifi or not).
I also managed to build a little service "app" that runs on the background and detects changes on the state of wifi connections, and it activates/deactivates proxy (and u2nl) depending on that.
Wifi Disconnected = Proxy/U2NL activated
Wifi On = Proxy/U2NL deactivated
When proxy/u2nl is active, all data goes through MetroPCS's proxy server, otherwise use wifi's internet connection.
At this point, it works great, but it's unfinished.
- Calls and SMS work perfectly with no issues at all.
- MMS can be sent and received with no issues either.
- On wifi, everything works perfectly.
- On MetroPCS data, only browser works, for some reason the u2nl binary it still not working properly.
This is meant to be free and open sourced. Not a paid solution.
The "proxy switcher" also has a configuration screen which allows to change the configuration. You can use a custom proxy, activate/deactivate proxy/u2nl, etc.
If you have the time and know about this, please figure out a way to make the u2nl binary work properly, or contact me, my twitter is in my signature, or you can PM me and we can gchat or email. I have had limited time to work on this these past few days.
Everything is open sourced,
vendor config is here http://goo.gl/ISk6
"wifi switcher" (for proxy) is here: http://goo.gl/2wwM
Also,
If you are interested on doing this on the Motorola Droid, here's the vendor config:
http://goo.gl/kuX3
Here's a built rom, if you'd like to test it
http://bit.ly/aBa5Qr
As soon as you install it, let it boot, and open APN configuration (use AnyCut or BetterCut).
Edit the one that says "metropcs" and on on the username, make replace "MDN" with your phone number, press menu, save, and then click on the radio button for that entry. After that, MMS will work.
This is based off CyanogenMod-6.0.0 and it hasn't been modified at all. All credits go to the CyanogenMod team
Click to expand...
Click to collapse
I'll tell you what work for me.
You need to the u2nl.zip from whiterabbit.org
In that file you will find the autostart.sh file for htc hero eris under metropcs folder.
I have to edit the autostart.sh file in order to work getting rid off some lines.
This is the file I'm using. autostart.sh
export PATH="$PATH:/system/bin"
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F
iptables -t nat -F
iptables -X
iptables -t nat -A OUTPUT -o rmnet0 -p 6 ! -d 10.223.2.4 -j REDIRECT --to-port 1025
u2nl 10.223.2.4 3128 127.0.0.1 1025 >/dev/null 2>&1 &
exit 0
and that's all
I've pushed the files via adb in Clockwork recovery console mounting system and data
adb shell su
cd /data/
mkdir opt
chmod 0777 /data/opt/
chmod 0777 /system/bin/
exit
adb push autostart.sh /data/opt/autostart.sh
adb push u2nl /system/bin/u2nl
adb shell
chmod 0777 /data/opt/autostart.sh
chmod 0777 /system/bin/u2nl
reboot
Result is working
ahernandez4110 said:
Nice would this work for my flash metropcs hero? Please let me know.
Thanks
Click to expand...
Click to collapse
That question was answered in the post right before yours.
diegov600 said:
I'll tell you what work for me.
You need to the u2nl.zip from whiterabbit.org
In that file you will find the autostart.sh file for htc hero eris under metropcs folder.
I have to edit the autostart.sh file in order to work getting rid off some lines.
This is the file I'm using. autostart.sh
export PATH="$PATH:/system/bin"
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F
iptables -t nat -F
iptables -X
iptables -t nat -A OUTPUT -o rmnet0 -p 6 ! -d 10.223.2.4 -j REDIRECT --to-port 1025
u2nl 10.223.2.4 3128 127.0.0.1 1025 >/dev/null 2>&1 &
exit 0
and that's all
I've pushed the files via adb in Clockwork recovery console mounting system and data
adb shell su
cd /data/
mkdir opt
chmod 0777 /data/opt/
chmod 0777 /system/bin/
exit
adb push autostart.sh /data/opt/autostart.sh
adb push u2nl /system/bin/u2nl
adb shell
chmod 0777 /data/opt/autostart.sh
chmod 0777 /system/bin/u2nl
reboot
Result is working
Click to expand...
Click to collapse
Yeah, if you take a good look at the vendor source I posted on the OP, this is basically what I'm doing (especifically this file). At first I tried building u2nl from scratch that didn't work, then, just to try it, I tried the u2nl binary found in whiterabbit.org and that didn't work either.
There's still something wrong with this setup I'm using, but I haven't been able to track it down yet, I did this about 2 weeks ago but lately I haven't had the time to troubleshoot it all
Link to your ROM is dead.
Been trying to get the new Skyraider 3.0 to work on Metropcs
dannystang said:
Link to your ROM is dead.
Been trying to get the new Skyraider 3.0 to work on Metropcs
Click to expand...
Click to collapse
Sorry, I was messing with some files and screwed up the links.
I'm currently rebuilding it again with a few changes I made and also sync'd everything with CyanogenMod's source.
Will post new link tonight and also have builds for the Motorola Droid and HTC EVO.
Updated OP with latest build. This is based on latest CM6.
http://bit.ly/incredibleMetro
http://bit.ly/bh4wbh - Google Apps (Latest)
Thanks! I couldn't sleep so I finally figured it out
I mounted the Skyraider 3.0 RC2 release, everything works except hulu on data without wifi which is ok cause metro is slow data anyhow.
I read past instructions to get data to work I just used whiterabbit u2nl File but it seems he has a "new" folder with an edited autostart which when I pushed it on works fine...
No need to edit anything, I can switch on and off wifi no problems...
dannystang said:
Thanks! I couldn't sleep so I finally figured it out
I mounted the Skyraider 3.0 RC2 release, everything works except hulu on data without wifi which is ok cause metro is slow data anyhow.
I read past instructions to get data to work I just used whiterabbit u2nl File but it seems he has a "new" folder with an edited autostart which when I pushed it on works fine...
No need to edit anything, I can switch on and off wifi no problems...
Click to expand...
Click to collapse
That is strange, nothing works for me except the browser, as in, only the proxy is working and not the u2nl... I'll work on this tomorrow again
diegov600 said:
I'll tell you what work for me.
Result is working
Click to expand...
Click to collapse
+1 This worked for me on Skyraider 3.0 RC2.
Thanks!!!
Will try it on CM6 now.
Edit: Won't work on CM6 NIGHTLY 08/24.
Works on IncredibleDoes AOSP - FRF91.
I got it working on CM6 RC3.
Now we just need Skyraider with the Froyo Final
Why did you guys have to use the edited autostart though?
Wondering why mine works and its so different...
We now have a working cifs.ko and nls_utf.ko. I was able to mount my win7 shares using cifs_manager and stream a few movies using mvideoplayer from the mounted share.
My initial problem seemed to be that I used the android ndk toolchain and the nook kernel is compiled with the codeSourcery toolchain.
After I re-compiled using the codeSourcery toolchain everything works (at least for now)
For those who want to try this.
Download the cifs.ko and nls_utf8.ko modules.
http://dl.dropbox.com/u/16190398/Nook Color 1.0/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.0/nls_utf8.ko
Mount /system as read write and create a directory under /system/lib called modules. Copy the cifs.ko and nls_utf8.ko modules under this directory.
Type the following from your windows or linux console
adb shell
#mount -o remount,rw /dev/block/mmcblk0p5 /system
#su
#cd /system/lib
#mkdir modules
#exit
#exit
Now you are back in your windows or linux command prompt
adb push cifs.ko /system/lib/modules
adb push nls_utf8.ko /system/lib/modules
adb shell
#su
#insmod /system/lib/modules/cifs.ko
#insmod /system/lib/modules/nls_utf8.ko
if everything went well you should see no errors.
#lsmod
(THis should give you a list of running modules)
You should see something like
nls_utf8 1856 0 - Live 0xbf153000
cifs 240060 0 - Live 0xbf113000
#exit
#exit
Download cifs_manager from the android market and follow the instructions from
http://forum.xda-developers.com/showthread.php?t=756158
If you have Astro file manager installed then tapping on the mounted share from cifs_manager will automatically launch Astro and list the folder/files under that share.
BTW, you can copy the modules anywhere you like even under /sdcard/modules but the default path used by cifs_manager is /system/lib/modules. You can edit the path from cifs manager to point to the location of your cifs.ko module.
---- 05/06/2011 Update ------------
New version of cifs.ko, slow-work.ko for the 1.2 update. This is for kernel version 2.6.32.9
Note, cifs.ko requires some symbols from slow-work.ko so you will need to load slow-work.ko first. If you use cifs-manager, under advanced settings
you can check load modules at startup via insmod and put the path to multiple modules for e.g /system/lib/modules/slow-work.ko:/system/lib/modules/cifs.ko.
Everything seems to be working fine for me. Let me know if you run into issues.
http://dl.dropbox.com/u/16190398/Nook Color 1.2/slow-work.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/nls_utf8.ko
Alright! This is fantastic! I can even play my SNES roms over wifi. Thanks for sharing.
The only issue I have noticed is that you need to run the insmod commands every time you reboot the device, and I reboot a lot. For now I'm just using gScript to run the 2 commands whenever I need, but it would be great to have them run when the program starts. I know you're just sharing and this has been mentioned in the app thread, just wanted to make my observations known.
Edit: Found a nifty toggle in the settings of cifs managaer that runs the insmod command at startup. I guess I should look before I complain...
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
thetoady said:
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
Click to expand...
Click to collapse
Setting up the environment is ridiculously easy esp if you have access to a linux box. There is a very well documented wiki page which outlines the process of building your own custom kernel for the nook color.
http://nookdevs.com/NookColor:_Build_the_Original_Kernel
I downloaded the codesourcery tool chain and did the minimum install as I did not care about the IDE and added the path to my environment. THat was about it. Everything else I followed the wiki page.
Here is my .config file if you like. When you run "make menuconfig" you can choose to load an alternate config file instead of the default. Just put this .config (after renaming it to .config_myconfig or something) under your distro/kernel directory.
Let me know if you need anything specific and I'll try to help. I had to add the .txt extension to the config file for xda upload but you can rename it to anything you want.
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
Seems more like an error in configuring CIFS_Manager.
If the module doesnt load you get a different error from Cifs_Manager
"No such device".
Can you try using adb shell and use insmod to load the module manually.
CHeck with lsmod if the module is loaded.
Can you post you cifs_manager screen for the share that you are trying to mount.
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I'm sure you noticed that there's an error in dascud instructions... the 2nd insmod command has a filename typo..
its should read
HTML:
#insmod /system/lib/modules/nls_utf8.ko
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
madrascafe said:
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
Click to expand...
Click to collapse
Done. Were you able to mount the CIFS shares ?
dascud said:
Done. Were you able to mount the CIFS shares ?
Click to expand...
Click to collapse
Yes. No problem at all. I even opened files from root explored & played some music. Thank you for this
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
ctos said:
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
Click to expand...
Click to collapse
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
I've followed the instructions, but trying to launch the cifsmanager I get
Application not installed on Device
from reading the FAQ on the cifsmanager page, it says its a problem with the launcher. is this because I've updated the NC to 1.01? thanks
dascud said:
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
Click to expand...
Click to collapse
gscript works for me. thanks a lot!
Sent from my LogicPD Zoom2 using XDA App
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I got this when I put the computer name in the share path. I switched to using IP address instead and it worked.
Hi,
Thanks for the files. I didn't follow the steps in the instructions because there is an easier way. Like mention before, ClifsManager only need cifs.ko.
I basically just copy cifs.ko to my sd card. In the CM setting, just change path to
/sdcard/cifs.ko
Setting up shares is easy too, share path is your ip/<sharefolder>, mount point /sdcard/<foldername> and your user/pwd. This worked with Windows 7.
ClifsManager is definitely one of the must have on the NC.
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
smlong426 said:
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=889736
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
KryptoNyte39 said:
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
Click to expand...
Click to collapse
What you need is a Samba server for Nook. Looks like this has already been accomplished. Maybe you can post a howto once you get this working.
http://forum.xda-developers.com/showpost.php?p=8239139&postcount=128
As many of you do, I connect to lots of Cisco based VPN's and could not function without this. So, after reading and tweaking, I managed to finally get VPN Connections to work with the Note. Apparently the problem is that the app crashes when it tries to locate the PID for the vpnc process and it can't. I found a patched, repacked APK of v97 floating around which uses a different method to do this on Samsung phones. This worked along with a small init.d script I created to create the tun symlink dependencies. Obviously, you have to be rooted, have tun compiled into the kernel with /etc/init.d support for it to work.
The script is called S95Tun in /etc/init.d:
Code:
#!/system/bin/sh
mkdir /dev/net
chmod 777 /dev/net
ln -sf /dev/tun /dev/net/tun
Make sure you chmod 755 on S95Tun to make it executable. This gives appropriate permissions to the /dev/net folder and creates the symlink that VPN Connections needs to use the tun device. Also, after more testing, I found that you need a resolv.conf in /system/etc and busybox 1.18.4 installed to /system/xbin. The app looks for files in /system/xbin like ip, ps, and ifconfig (maybe more).
/system/etc/resolv.conf:
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4
This was my particular scenario, you may have to do more tweaking on yor ROM, etc. DO ALL THIS AT YOUR OWN RISK! I will answer questions he best I can. Enjoy!
wasnt there already support for VPN connections in stock kernel ?
ookba said:
As many of you do, I connect to lots of Cisco based VPN's and could not function without this. So, after reading and tweaking, I managed to finally get VPN Connections to work with the Note. Apparently the problem is that the app crashes when it tries to locate the PID for the vpnc process and it can't. I found a patched, repacked APK of v97 floating around which uses a different method to do this on Samsung phones. This worked along with a small init.d script I created to create the tun symlink dependencies. Obviously, you have to be rooted, have tun compiled into the kernel with /etc/init.d support for it to work.
The script is called S95Tun in /etc/init.d:
Code:
#!/system/bin/sh
mkdir /dev/net
chmod 777 /dev/net
ln -sf /dev/tun /dev/net/tun
Make sure you chmod 755 on S95Tun to make it executable. This gives appropriate permissions to the /dev/net folder and creates the symlink that VPN Connections needs to use the tun device.
This was my particular scenario, you may have to do more tweaking on yor ROM, etc. DO ALL THIS AT YOUR OWN RISK! I will answer questions he best I can. Enjoy!
Click to expand...
Click to collapse
could you please explain this out a bit more. im not able to connect.
thanks man,
jason
tids2k said:
wasnt there already support for VPN connections in stock kernel ?
Click to expand...
Click to collapse
Yes. The stock OS and kernel allow connections to limited non-cisco PPTP AND L2TP servers. Cisco VPN requires vpnc which allows connection to Cisco based VPN routers and concentrators.
jason370 said:
could you please explain this out a bit more. im not able to connect.
thanks man,
jason
Click to expand...
Click to collapse
Will do when I get in front of a PC. Basically you need to make sure all of your Cisco credentials are correct including group and user for it to properly connect.
ookba said:
Will do when I get in front of a PC. Basically you need to make sure all of your Cisco credentials are correct including group and user for it to properly connect.
Click to expand...
Click to collapse
are you using this alone as the vpn client or in conjunction with?
Meh, no SSL support. My crappy university switched from "standard" (ehmehm...) Cisco to Cisco SSL VPN which no damn crap mobile device seems to be able to handle.
In Switzerland all major public WiFi providers are linked together and students - by using a VPN conx - can happily surf for free virtually everywhere. But as I said: crappy Uni switched to SSL VPN, no no more love without having a notebook at hand... crap.
schaggo said:
Meh, no SSL support. My crappy university switched from "standard" (ehmehm...) Cisco to Cisco SSL VPN which no damn crap mobile device seems to be able to handle.
In Switzerland all major public WiFi providers are linked together and students - by using a VPN conx - can happily surf for free virtually everywhere. But as I said: crappy Uni switched to SSL VPN, no no more love without having a notebook at hand... crap.
Click to expand...
Click to collapse
You can try the Cisco Anyconnect client from the market for that.
jason370 said:
are you using this alone as the vpn client or in conjunction with?
Click to expand...
Click to collapse
Standalone. I connect to a handful of Cisco VPN routers and this helps tremendously.
ookba said:
You can try the Cisco Anyconnect client from the market for that.
Click to expand...
Click to collapse
There is one (now)...? Wow, will check!
Sent from my GT-N7000
Hi ookba,
I am unable to get VPN connections to work. I used your apk on my Note and it still failed to connect. I've verified the group and user passwords are correct. Do you know if there is any logs I can check on the Note for troubleshooting? My Note is rooted with N7000ZSKK1 Hong Kong ROM. thanks.
felix
felixjai said:
Hi ookba,
I am unable to get VPN connections to work. I used your apk on my Note and it still failed to connect. I've verified the group and user passwords are correct. Do you know if there is any logs I can check on the Note for troubleshooting? My Note is rooted with N7000ZSKK1 Hong Kong ROM. thanks.
felix
Click to expand...
Click to collapse
+1, exactly the same story
Sent from my GT-N7000 using xda premium
felixjai said:
Hi ookba,
I am unable to get VPN connections to work. I used your apk on my Note and it still failed to connect. I've verified the group and user passwords are correct. Do you know if there is any logs I can check on the Note for troubleshooting? My Note is rooted with N7000ZSKK1 Hong Kong ROM. thanks.
felix
Click to expand...
Click to collapse
Did you add the script:
Code:
#!/system/bin/sh
mkdir /dev/net
chmod 777 /dev/net
ln -sf /dev/tun /dev/net/tun
Or just adb shell:
C:\> adb shell
# mkdir /dev/net
# chmod 777 /dev/net
# ln -sf /dev/tun /dev/net/tun
Then try to connect.
ookba said:
Did you add the script:
Code:
#!/system/bin/sh
mkdir /dev/net
chmod 777 /dev/net
ln -sf /dev/tun /dev/net/tun
Or just adb shell:
C:\> adb shell
# mkdir /dev/net
# chmod 777 /dev/net
# ln -sf /dev/tun /dev/net/tun
Then try to connect.
Click to expand...
Click to collapse
I don't really understand how to add this script. Could you please elaborate a bit on this?
Sent from my GT-N7000 using xda premium
If your running Windows, open MS Dos promt (or command prompt), then type inn the following:
First: you are to place youself here: C:\>
Then type: adb shell (Press enter)
# mkdir /dev/net (Press enter)
# chmod 777 /dev/net (Press enter)
# ln -sf /dev/tun /dev/net/tun (Press enter)
*done
jason370 said:
I don't really understand how to add this script. Could you please elaborate a bit on this?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You just create a text file with no extension called : S95Tun in the /etc/init.d/ folder. But you have to change its permission to 755, which means:
Owner r w x
Group r x
Public r x
In other word, just do in Windows command instead which is easier.
mkdir /dev/net #create directory called /dev/net
chmod 777 /dev/net #set the folder /dev/net permission to full access by anyone (777)
ln -sf /dev/tun /dev/net/tun #force create a symbolic link at /dev/net/tun, which points to the actual file at "/dev/tun"
I did it in adb shell. But still having problems. So I'd like to know if there is any debugging logs I can check to see what the problem is. (I don't have access to the Cisco VPN device to see the logs there). Thanks again for your help.
felixjai said:
I did it in adb shell. But still having problems. So I'd like to know if there is any debugging logs I can check to see what the problem is. (I don't have access to the Cisco VPN device to see the logs there). Thanks again for your help.
Click to expand...
Click to collapse
It's hard to debug. I found the problem by running vpnc directly in a shell and entering my Cisco VPN credentials. The main problem I had was the app Force Closing. If you're simply not connecting, then it's a problem with your IPSec ID, IPSec Secret, or username/password. Took me while to get all those entered correctly. Like I said, everyone's scenario may be a bit different. You can also try the latest, unmodified VPN Connections apk to see if it works.
Hi,
I have the 0.97 debug apk installed and the S95Tun script is placed under /etc/init.d
(originally there was no init.d folder under /etc)
But I still get a force close when I try to connect with VPN Connections.
Which busybox version are you using ?
Ans where is busybox installed on your device ?
mrmrmrmr said:
Hi,
I have the 0.97 debug apk installed and the S95Tun script is placed under /etc/init.d
(originally there was no init.d folder under /etc)
But I still get a force close when I try to connect with VPN Connections.
Which busybox version are you using ?
Ans where is busybox installed on your device ?
Click to expand...
Click to collapse
What kernel are you running? Stock or CF-Root kernel does not support init.d so you will have to run S95Tun manually. Also, make sure you have a /system/etc/resolv.conf.
Hello Ookba,
I have never managed to get a simple pptp vpn connection to work. While vpn connects the access to internet drops. With all my searching I have only found that this is an android bug. Is there any chance you could help me?
Thanks!
Sent from my GT-N7000 using xda premium
Note: The information below is quite dated. If you are interested in watching TV on Android without root with the RTL-SDR dongles check out Aerial TV on XDA.
--------
Ok guys, I am proud to announce that I was able to run a DVB-T tuner on my Nexus 7
If your kernel is 3.1.10-g52027f9 and your dongle is RTL2832U based
If you have a rooted Nexus 7 with kernel 3.1.10-g52027f9 and a RTL2832U based DVB-T dongle, then you can also have your dongle up and running in a matter of minutes. Here are the steps:
Download http://dl.dropbox.com/u/24106229/NexusDvb.rar
Install droidtv.apk from the rar (you can also find it at https://github.com/chrulri/droidtv)
Get a Terminal emulator and cd to the folder where you have extracted the rar. Type in:
su
sh startdvb
Make sure that all of the files and folders inside /dev/dvb have highest permissions.
Start DroidTV and enjoy!!!
Different dongle, kernel 3.1.10-g52027f9
If you have the same kernel and a dongle that has its drivers built in the kernel according to http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices , then you can download this rar file - http://dl.dropbox.com/u/24106229/all-modules.rar (Last updated 20 Aug 22:22 GMT). Those are all of the kernel modules I compiled. You may be able to find your usb driver there.
Compiling kernel modules
If you don't have the same kernel or a dongle is not supported, you will need to get the kernel source and compile the modules yourself. Here's how you do that.
Make sure you are running Linux and have make and git already installed
Download dvbn7comp and put it into a new directory. Make sure dvbn7comp is executable by running chmod +x dvbn7comp inside the folder
Invoke the script like this ./dvbn7comp <kernel_version>. For example if you want to have the modules compiled for 3.1.10-g05b777c, you would run ./dvbn7comp 3.1.10-g05b777c
Wait - it may take a while. Usually about 15 minutes depending on your network and CPU speed.
After the script finishes running, the .ko files would be put in a directory called output_3.1.10-g05b777c
That's it!
Note: The script will download the kernel source and the toolchain and it will attempt to find the commit that contains the required kernel version. Then it will configure the kernel for DVB-T support and will compile the modules and copy them to the output folder. If you run the script again and the sources are already present, it will not download them again, so any subsequent runs of the script would be faster!
Patching the precompiled binaries [NEW]
phamthanhnam said:
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
Alternaties: Get precompiled binary modules at post #80 (more complete than modules from post #1) and patch them:
Code:
perl -pi -e 's/3.1.10-g22b4fcd/3.1.10-xxxxxxxx/g' *.ko
Alternaties 2: Post #129, the same way:
Code:
perl -pi -e 's/3.1.10-g05b777c/3.1.10-xxxxxxxx/g' *.ko
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:
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-g30c5396/g' *.ko
That's it!
More info: This way works with Cyanogen Mod kernels/ROMs!!!
Click to expand...
Click to collapse
How to modify the startdvb script
Code:
echo "Starting DVB support"
insmod dvb-core.ko # core support for DVB
insmod dvb-pll.ko # I am not sure if this is even needed
insmod rc-core.ko # Support for remote control, some drivers won't load otherwise
insmod dvb-usb.ko # Support for usb tuners
insmod dvb-usb-***** # Add here your driver. If more than one needed, add another line
# if firmware is needed, make sure the firmware is in the right folder, it should be /lib/firmware, but I'm not 100% sure
# Also some devices won't need the steps below
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb* # The original script doesn't have it, but try adding a -R before 777 might ease things a bit
echo "DONE!"
Troubleshooting
If any error message occurs, type in dmesg in the terminal. This will give more information why something failed.
How do I know if I'm successful
To check whether you have insmoded the kernels right and after connecting the device whether it has been discovered, use dmesg and look for message similar to "Found DVB device xxx in warm state".
I got it running!!!
If you got it running, please do share with us! It seems like there's a lot of fiddling for some devices to be done so any information will prove invaluable for somebody!!!
NOTE: I don't have the time to support this thread any more, sorry if I am not responding to it! All of the directions above are still valid and working! Browse the comments, you might find that someone has compiled the correct modules for your device/kernel or you might ask someone to do it for you! If you want any of the information above to be edited, please PM me!
Where to get the DVB tuner
Hi,
Thanks for posting. it is very interesting.
can you post where did you buy the tuner from and the price?
the only one i could find with RTL2832U is priced at 27$ from ebay.
How can i compile the kernel modules for a different device?
thanks.
Very cool!
Could a similar technique could be used for ATSC here in the U.S.?
I actually have compiled all of the drivers that come with the Linux kernel as well
You can get them from here - http://dl.dropbox.com/u/24106229/all-modules.rar
If your device is listed as compatible somewhere here - http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices then you may be lucky You just need to know which kernel module to load with insmod (see the startdvb script to see how to do it).
If it's not there or you have a different kernel version, you will need to follow https://source.android.com/source/building-kernels.html . Except for you only need to build the modules, and you need to fiddle around with the Makefiles in order to force some of the components (like the dvb-usb.ko) to be compiled as modules. Good luck!
As far as the tuner I am using, it's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120958257586 this one. I actually got it for another purpose (http://sdr.osmocom.org/trac/wiki/rtl-sdr), which if I have the time I can try to build an app to bring it to the Android as well
another question
Thanks for the quick reply!
I couldn't find the right *.ko file in the modules you attached (it is supposed to be af9005 and af9015, and for my other dvb-t - IT9135)
Could i bother you to upload these, since i have no idea how to compile them.
I tried using af9013.ko that you attached but with no success, most likely because i had to use af9005 instead.
I added insmod af9013.ko to your script, attached is a screenshot from my emulator:
Thanks again. Your help is much appreciated!
another question
double post by mistake
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Cheers,
Mick
martintzvetomirov said:
I actually have compiled all of the drivers that come with the Linux kernel as well
You can get them from here - http://dl.dropbox.com/u/24106229/all-modules.rar
If your device is listed as compatible somewhere here - http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices then you may be lucky You just need to know which kernel module to load with insmod (see the startdvb script to see how to do it).
If it's not there or you have a different kernel version, you will need to follow https://source.android.com/source/building-kernels.html . Except for you only need to build the modules, and you need to fiddle around with the Makefiles in order to force some of the components (like the dvb-usb.ko) to be compiled as modules. Good luck!
As far as the tuner I am using, it's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120958257586 this one. I actually got it for another purpose (http://sdr.osmocom.org/trac/wiki/rtl-sdr), which if I have the time I can try to build an app to bring it to the Android as well
Click to expand...
Click to collapse
---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------
Here is the driver i need... i assume i need to be able to produce a .ko file some way for it?
http://linuxtv.org/wiki/index.php/Sony_PlayTV_dual_tuner_DVB-T#Drivers
aspletec this
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
micks_address said:
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Cheers,
Mick
---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------
Here is the driver i need... i assume i need to be able to produce a .ko file some way for it?
Click to expand...
Click to collapse
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
lionsh said:
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
Click to expand...
Click to collapse
you need to update the startdvb script to inclue ismode yourdriver.ko
micks_address said:
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
Click to expand...
Click to collapse
I edited the startdvb file to reference the dib0070.ko but i get init failed.. i wonder doesn the nexus have enough power to power the tuner via USB?
Cheers,
Mick
lionsh said:
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
Click to expand...
Click to collapse
micks_address said:
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
Click to expand...
Click to collapse
You need to add the line 'insmod dib0070.ko' to startdvb.
You will probably also need to copy the 'dvb-usb-dib0700-1.20.fw' firmware file from that link you posted earlier into /etc/firmware.
OK guys, my bad! I didn't originally submit all of the files. Please, redownload again - http://dl.dropbox.com/u/24106229/all-modules.rar
I didn't compile the usb drivers, the ones that you would actually need Now everything should be there.
lionsh said:
Thanks for the quick reply!
I couldn't find the right *.ko file in the modules you attached (it is supposed to be af9005 and af9015, and for my other dvb-t - IT9135)
Could i bother you to upload these, since i have no idea how to compile them.
Click to expand...
Click to collapse
You will need dvb-usb-af9005.ko and possibly dvb-usb-af9005-remote.ko
micks_address said:
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Click to expand...
Click to collapse
You will need dvb-usb-dib0700.ko and the firmware from the web page you pointed me at.
micks_address said:
I edited the startdvb file to reference the dib0070.ko but i get init failed.. i wonder doesn the nexus have enough power to power the tuner via USB?
Click to expand...
Click to collapse
It was able to properly power my tuner without external power but surely this won't be the case with all of them. That can't cause the init to fail though! Use dmesg to get more info on why this has happened.
lionsh said:
you need to update the startdvb script to inclue ismode yourdriver.ko
Click to expand...
Click to collapse
Yes, that's right. So here's how to do it
Code:
echo "Starting DVB support"
insmod dvb-core.ko # core support for DVB
insmod dvb-pll.ko # I am not sure if this is even needed
insmod rc-core.ko # Support for remote control, some drivers won't load otherwise
insmod dvb-usb.ko # Support for usb tuners
insmod ***** # Add here your driver. If more than one needed, add another line
# if firmware is needed, make sure the firmware is in the right folder, it should be /lib/firmware, but I'm not 100% sure
# Also some devices won't need the steps below
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb* # The original script doesn't have it, but try adding a -R before 777 might ease things a bit
echo "DONE!"
Hope this helps!
If any error message occur, type in dmesg in the terminal. This will give more information why something failed. Also to check whether you have insmoded the kernels right and after connecting the device it has been discovered, use dmesg again and look for message similar to "Found DVB device xxx in warm state"
Hi Martin,
first of all many thanks!
i used 9005,9005-remote and 9015 ko files and updated the script as follow:
Code:
echo "Starting DVB support"
insmod dvb-core.ko
insmod dvb-pll.ko
insmod rc-core.ko
insmod dvb-usb.ko
insmod dvb-usb-af9005.ko
insmod dvb-usb-af9005-remote.ko
insmod dvb-usb-af9015.ko
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb*
echo "DONE!"
I receive several errors.
first i get 9015.ko file not found, i'm attaching screen shot with ls that clearly lists the file (WTF?!)
and *dvr0.ts file is also written as no such file/dir.
I even copied the .fw files for 9005 and 9015 to etc/firmware
can you take a look ,i must be missing something stupid.
also, is there a dvb-usb-IT9135.ko file?
many thanks for your contribution.
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.
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
Great work on this, so far I've managed to get my DVB tuner properly configured and connected!
The only issue is Droid TV seems very unstable... Are there any alternatives?
I get reboots when scanning for channels. Might try recompiling a newer version of w_scan when I get a minute.
The channels I manually added only have a signal of 20% with no picture. The signal is fine when the tuner is connected to my PC though.
Maybe the Nexus doesn't give it enough power?
Hi,
Can you state which module do you use for your DVB-T tuner?
Psych0Chimp said:
Great work on this, so far I've managed to get my DVB tuner properly configured and connected!
The only issue is Droid TV seems very unstable... Are there any alternatives?
I get reboots when scanning for channels. Might try recompiling a newer version of w_scan when I get a minute.
The channels I manually added only have a signal of 20% with no picture. The signal is fine when the tuner is connected to my PC though.
Maybe the Nexus doesn't give it enough power?
Click to expand...
Click to collapse
lionsh said:
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.
Click to expand...
Click to collapse
I have an A-Link dongle that seems to be running Afatech inside. Among the things you have done, I also attached and insmodded af9013.ko and got my receiver mounted in warm state and its actually scanning the channels in DroidTV as we speak. (No luck on the first try).
I have dvb-usb-af9015, 9005, 9005-remote, af9013 and the af9015 firmware (in the etc/firmware folder).
These seemed to do the trick.
that is so strange, i tried all these combinations, including af9013.ko with no luck.
did you get an error on af9015 like i did?
i have copied the firmware also. did you d\l it from http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices#DVB-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?
Sikki said:
I have an A-Link dongle that seems to be running Afatech inside. Among the things you have done, I also attached and insmodded af9013.ko and got my receiver mounted in warm state and its actually scanning the channels in DroidTV as we speak. (No luck on the first try).
I have dvb-usb-af9015, 9005, 9005-remote, af9013 and the af9015 firmware (in the etc/firmware folder).
These seemed to do the trick.
Click to expand...
Click to collapse