I discovered a problem with both the kernal for myn's warm donut and mssmison's eclair roms. Apparently the switch for Netfilter is not turned on, which is required to run wireless tethering.
I told myn about this and he said to bring this to the boards attention, is there anything we can do about this?
FWIW the wired tethering has the same issue.
mrono said:
Is there anything we can do about this?
Click to expand...
Click to collapse
You could just compile the kernel with the options you need enabled!
Never mind, I've done it now with all the netfilter iptables options selected. zImage and vogue NBHs are on my site, if you need kaiser or polaris NBHs you'll have to make them yourself.
dzo said:
You could just compile the kernel with the options you need enabled!
Never mind, I've done it now with all the netfilter iptables options selected. zImage and vogue NBHs are on my site, if you need kaiser or polaris NBHs you'll have to make them yourself.
Click to expand...
Click to collapse
Thank you, I have no idea how to compile the kernel myself but I have a vogue so it's a non-issue
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
EDIT:
Damn, The usb one says no netfilter still and the wireless one says unable to start tethering, please try again...
How do I go about compiling it my self?
mrono said:
How do I go about compiling it my self?
Click to expand...
Click to collapse
http://www.androidonhtc.com/wiki/Get_Involved
Vogue at the bottom.
Unfortunately, this is only for building a zImage. You could use kexec to launch the new zImage and test the changes.
You still need Wine with LinuxRomKitchen, Yang, and NBMerge.exe (wine) to build a NBH.
The NBH/bootloader builder is in: http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
You need the tinboot repo, as well as the bootenv repo. Put the initrd.gz from the bootenv and the zImage in the tinboot directory and type compile.
As for wired tethering, I've never tried EasyTether or PDANet, but I was under the assumption they worked?
jnadke said:
http://www.androidonhtc.com/wiki/Get_Involved
Vogue at the bottom.
Unfortunately, this is only for building a zImage. You could use kexec to launch the new zImage and test the changes.
You still need Wine with LinuxRomKitchen, Yang, and NBMerge.exe (wine) to build a NBH.
The NBH/bootloader builder is in: http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
You need the tinboot repo, as well as the bootenv repo. Put the initrd.gz from the bootenv and the zImage in the tinboot directory and type compile.
As for wired tethering, I've never tried EasyTether or PDANet, but I was under the assumption they worked?
Click to expand...
Click to collapse
that sounds like alot of work and preparation , although flashing the vogue sounded like alot of work at first as well.
wired tethering programs do work if they either use the usb debugging method or have a program on the other end like easy tether and pdanet. these two tethering programs don't use another program, the wired one makes your phone show up as a 'windows based usb internet device' or something, same as if you tethered with winmo, and the wireless one makes it into either a mobile hotspot(which vogue can't do) or uses bluetooth PAN.
mrono said:
that sounds like alot of work and preparation , although flashing the vogue sounded like alot of work at first as well.
wired tethering programs do work if they either use the usb debugging method or have a program on the other end like easy tether and pdanet. these two tethering programs don't use another program, the wired one makes your phone show up as a 'windows based usb internet device' or something, same as if you tethered with winmo, and the wireless one makes it into either a mobile hotspot(which vogue can't do) or uses bluetooth PAN.
Click to expand...
Click to collapse
If your host is Windows, the wired programs won't work, because we don't have support for rndis in the kernel. If it's *nix... I don't think we have that driver either. Tethering over BT should be doable.
If you don't mind can you try it on your vogue DZO, see if it's just me?
If other people don't mind i'd like them to try it too, i've had problems that are limited to just my handset before
I compiled my own and it didn't work (both USB and bluetooth).
USB doesn't work. Our kernel seems to be missing some stuff that identifies the USB device as RNDIS capable. It's in the newer 2.6.27+ kernels (and on the HTC MSM Experimental tree), but not in our 2.6.25 kernels.
http://android.git.kernel.org/?p=ke...ff;h=9d7686ec6e8330c380fa2abec6e20d6b084fc467
Not sure if this is the issue.
I'm not sure what's up with bluetooth. I'm not surprised, since it's still a WIP.
With Bluetooth, I get the "Unable to start....".
I wish it'd work. I'd love to be able to use this.
Hmm... well, I was able to reverse tether over bt once (laptop internet -> bt -> phone) a while back so I'm intrigued that it's not working the other way. Can you setup the kind of connection you want manually now that iptables is available?
Anyone have any luck getting this to work?
Related
I upgraded my blue angel to WM6, which is brilliant. Only problems I'm getting are: turning off the phone from the menu leaves the green led flashing, and the phone can't be turned back on without a soft reset. That I can live with.
Second, it seems the upgraded rom doesn't use a serial connection over USB any longer, which is a pain, as I use Linux and the device doesn't appear as /dev/ttyUSB0 any more
Thirdly, when using wm2003 I was able to add my Linux box as a NAT router and surf via bluetooth. The router was discoverable, and the PAN service appeared on the list of services, now it doesn't, and I have no way of using the internet via bluetooth any more. Any suggestions welcome. I like using the upgraded rom too much to go back.
I can help with the USB over serial change. (I am also a linux user). search for rndis kernel module and use it with opensync and a perl plugin for opensync. I am sorry I don't have the names, but I have not yet fully configured it and am syncing in XP inside vmware. I plan on readdressing this as soon as I got a break from work.
Sorry for being vague but I expect that if you successfully synced WM2003 and linux you will be able to use these hints with skill.
Appreciate it, thanks I'll look into that. It seems the rom upgrade syncs via TCP/IP, as xp needs its DHCP service enabled for activesync to work. With wm2003, I was able to sync with my Debian box over bluetooth and wifi as well as the cradle with synCE, which was very nice, and I miss it now it's gone. I'll persevere.
Just bumping this thread to say it's all working, syncing nicely with evolution. The Ubuntu howto in the link below applied equally to my Debian installation as far as packages were concerned (well, Ubuntu's Debian-based after all) and with appropriate changes here and there should help users of other Linux distros too.
http://www.synce.org/moin/SynceWithUbuntu
... I was just wondering if anyone has a solution that allows the Nexus One to be used as a USB modem in Mac OS.
I know I can use WiFi tethering and I know of PDANet, I am not looking for alternative solutions but rather to find out if the FroYo USB tethering functionality can be used with Mac OS X (Snow Leopard).
Any help is appreciated.
well before someone comes up with a real answer (since i dont have osx) the easiest thing to do is just plug in the n1 to usb and not mount the device and turn on wifi tethering. This way its charging and being your hotspot.
Why dont you just try to see if the usb tether on froyo works on your macbook and tell us what happens? It could possibly only take 10 minutes to flash froyo plug in, test (stay there if its works), and nandroid restore (if it doesnt).
miketlo said:
well before someone comes up with a real answer (since i dont have osx) the easiest thing to do is just plug in the n1 to usb and not mount the device and turn on wifi tethering. This way its charging and being your hotspot.
Why dont you just try to see if the usb tether on froyo works on your macbook and tell us what happens? It could possibly only take 10 minutes to flash froyo plug in, test (stay there if its works), and nandroid restore (if it doesnt).
Click to expand...
Click to collapse
I have of course tried this and nothing happens, it is not mapped as a network card like it is if I reboot into Windows 7.
Furthermore, I have searched and found several posts saying that it does not work due to a lack of drivers in Mac OS.
However, this being XDA and the innovative nature of many of the people on this forums made me think that someone may have a solution that works.
Linux drivers
If any one can provide hints where the Linux drivers that that add USB tethering ability can be found ? May be we are just able to port them with little modifications if any would be needed at all.
The problem is
Simply and has been for ages (since HTC had this kind of USB tethering integrated since the Hero days) that the solution google uses probably is the same as htcs it relies on rndis, which OSX has no proper support for. RNDIS is perfectly supported on OS level in windows and Linux but not in OSX.
Apple has dropped the ball on this protocol for ages, but up until now this has not really hurt but now it does somewhat (thankfully Google also has provided Wifi tethering, which is an easy fix to the problem)
I've searched and searched, and I hope that someone has figured this out.
Has anyone tethered their Captivate to a Mac? USB tether only please. I know of Wifi tethering, but I like to enjoy my battery when I am done with my laptop.
I have it working in WinXP with Kies, but I would like to get it working on my Mac.
Thanks
Unfortunately, my snow leopard device is DOA right now, so I can't test it, but I think it should be as simple as plugging it in through USB when you have "PC Internet" chosen as your USB settings. I know it works instantly on Linux (without any drivers) and on windows with the drivers installed.
According to most references, a mac doesn't require any sort of "drivers" or kexts to get our phone compatible with it, so I would suggest just plugging it in and disabling your other connections to check
no go, it finds it as a modem, but won't connect... I found something online that said to add settings here and there, but it still isn't working...
Yes, it works on my Mac computer. Either you can configure it with complicated settings without any other software, or you can use PDAnet. You can get it on the market but it is censored by AT&T so you will need market enabler or be in airport mode with the wifi on
Anyone have any suggestions for a wired tethered app? I've used PDAnet and Easytether, but both have trials that eventually block secure sites. I use wireless tether but it makes my phone hot as heck...any tips?
frostbyte32 said:
Anyone have any suggestions for a wired tethered app? I've used PDAnet and Easytether, but both have trials that eventually block secure sites. I use wireless tether but it makes my phone hot as heck...any tips?
Click to expand...
Click to collapse
have you tried wired tether http://code.google.com/p/android-wired-tether/ I'm assuming you are rooted since you've tried wireless tether. Also the froyo roms have built in wired tether in the settings.
I'm using Froyo v39...what do I need to do to use the wired tether on that?
frostbyte32 said:
I'm using Froyo v39...what do I need to do to use the wired tether on that?
Click to expand...
Click to collapse
menu/settings/wireless and network settings/tethering and portable hotspot/ then check the usb tethering while phone is plugged in and it should connect automatically.
Will this work on any computer without having to install anything?
frostbyte32 said:
Will this work on any computer without having to install anything?
Click to expand...
Click to collapse
I think that you need a driver installed for windows...not sure exactly cause I use linux and it works without needing anything else. If you already had pdanet installed it probably uses the same driver but not 100% sure about that. Best way to find out is to try it....
from the wired tether link i posted earlier...
This program has been tested with Linux and Microsoft Windows clients. The client needs to support RNDIS. Windows Vista/7 comes with RDNIS-support out of the box. Windows XP requires to download and install a driver. I recommend using the HTC Sync (for the HTC Hero) which contains the required driver. The driver is located under C:\Program Files\HTC\HTC Driver\Driver Files\XP_x86 in case it's not automatically installed when plugging in.
Click to expand...
Click to collapse
I still think the htc sync driver is the same one pdanet and easytether installs so you should be fine.
Conap said:
I think that you need a driver installed for windows...not sure exactly cause I use linux and it works without needing anything else. If you already had pdanet installed it probably uses the same driver but not 100% sure about that. Best way to find out is to try it....
from the wired tether link i posted earlier...
I still think the htc sync driver is the same one pdanet and easytether installs so you should be fine.
Click to expand...
Click to collapse
Just wanted to add my confirmation that HTCSync is all that's needed to install to get the correct driver(s) for wired tethering.
I'm looking to understand what options exist for tethering the NC to a phone for data. I believe the only method currently supported is by creating an ad-hoc wifi network using software on the phone, and joining this network from the NC.
I have a Blackberry 9700, which cannot be setup as a wifi hotspot. With the release of CM7 build 17, it sounds like Bluetooth works (with limited range). My phone supports Bluetooth tethering because I've set it up with my Windows 7 laptop. I'm curious to find out whether this will be possible with the NC as well.. if not, what other options are there for getting online with my NC (besides having to purchase a phone that has hotspot capability). I used to use PDANet with a Palm Treo back in the day.. I'm also not opposed to physical cable-tethering if this is a possibility.
Thanks in advance.
I would like to know this as well. My Evo is not rooted and I'd like to keep it that way for now, so my only options are PDAnet via physical cable and bluetooth (which I can utilize on CM7 but it breaks wifi) or Easytether (physical).
neoshi said:
I would like to know this as well. My Evo is not rooted and I'd like to keep it that way for now, so my only options are PDAnet via physical cable and bluetooth (which I can utilize on CM7 but it breaks wifi) or Easytether (physical).
Click to expand...
Click to collapse
So are you confirming that you've got Bluetooth tethering working with your phone using CM7? Does the build break wifi permanently, or is it only during BT tethering?
Haven't tried it yet but now that you mention it.. I'm going to try it!
Excellent, can't wait to hear the results..
Will pair, won't connect
Well, that takes that option out of the running. I really prefer a physical connection though, and so far, I haven't seen any micro-micro (assuming this is because of power requirements anyway).
Even with the phone right next to the NC? That's disappointing.. by micro-micro, are you referring to the type of USB cable needed? I don't have the device yet, so I'm not sure what kind of connections it has available. Tethering over BT is the last feature I'm waiting for before pulling the trigger on this bad boy. I plan to use it as a removable CarPC (using my phone for data and an external Bluetooth receiver for GPS).
Yup right next to it. Now, I've seen some guys report that GPS works though via bluetooth and I plan on trying that next (need to charge my BT receiver.. hope the battery still works!). They said you needed a GPS app to fix your location though.
As for micro-micro, yep USB. But then we would probably need a client side app to be able to recognize that kind of connection.
And wifi seems broken with BT ENABLED (not on, just enabled).. going to revert.
Thanks for doing all that testing. Let me know how the pairing goes with your GPS receiver.. if you get that working, you would need GPS software that has all of the maps built-in (since Google Maps, etc, requires a data connection).
My primary use for the NC will be as a car PC, so the only thing holding me back is the Bluetooth tethering with my Blackberry (uses the Dial-Up Networking feature set).
I've been hoping to BT DUN working for my BB 9700 also. At the moment it appears that ppp needs to be enabled in the kernel for this to work. When I run pppd from the comand line it complains about ppp missing from the kernel.
It looks like the pppd program is being compiled with the CM7 build and that the ppp modules can be found in the kernel sources so there is hope. We could ask to have it added as a dynamic module but I not sure how to go about making the request. (I am a noob to the forums and not allowed post in Dev and there may be a another way to make requested that is preferred in any case. )
I also found this program that claims to set up a BT DUN connection via ppp and it does run without faulting on my NC:
android.gval.biz
Thanks for sharing your experiences. I found a post in the developers forum where someone asked how to do the same thing. The link in the response discusses how to get Bluetooth GPS and WiFi tethering to work, but it does not mention Bluetooth tethering to a phone. Unfortunately, I don't have enough posts under my name to respond to that thread, but I've subscribed to it in the hopes that someone else will point it out..
http://forum.xda-developers.com/showpost.php?p=12282264&postcount=281
Same same same same.
Unrooted Evo and although I am having fun with all the great things we can do to our NC's I am really not ready to root my Evo just yet. Having that phone with me is the only reason I am able to walk away from my keyboard at all and just because you can doesn't mean you should.
I run Fedora on my laptop and can tether to my Evo using Azilink and USB cable without a problem but if I wanted to drag my lappie everywhere then the NC wouldn't be any fun atall!
Weird is when we can pair the Evo and the NC via Bluetooth (yes a few inches apart right now) but neither one wants to do the actual connection. The message pops up on both Evo and NC asking to acknowledge the "secret" code and what else to do but say yes to them both. Then they both try and fail to connect.
I guess there is a fix for AdHoc on CM7 but I am not sure how to get the unrooted Evo to create an AdHoc network for the NC to connect to. If anyone has that answer can you let us know? I will keep searching as well.
Deirdre