• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root WORKING WIFI Tether

JollyRoger87 said:
Isaacs with the over clock kernel
Click to expand...

Both Tickerguy's and Isaac's kernels are the same right?

Edit: Wait the Umph kernel with Isaac's build? Thought the Umph kernel was based on 2.2?<--Dunno Why I thought that....durr...

Edit2: I see he's using Doomlord's overclock kernel patch so that's based on 2.3. So It must be because op is using Tickerguy's which maybe there is something changed between the two.
 
clc130 said:
To prevent the wifi lock-up issue, I believe both cm7 versions (tickerguy + issac) are set to turn off wifi on screen lock (regardless of settings). That would of course cause the tether to be disconnected.
Click to expand...

On my HD2 there was an option to keep it on. It has CM7. Just a thought. Have you guys tried looking to see if there is an option for it? If not, I'm sure it's possible to have it added.
 
Mine works in tickers latest build, but I also had to go in and shange setup-method to WEXT (Ad-Hoc). I am tethering to a generation 1 ipad at this moment.
 
this was on page 8 of Isaac's thread posted by him, just after he updated to the 9/18 build....

Wow, that's incredible. Later I'll add some new governors for you guys to play with. I also have a new build with the WIFI lockup fix coming up. I'm still experimenting, but I'll let you guys know. - isaacj87

which means that the wifi lockup issue was not included in his build because that was posted a day after his 9/18 build, but i have to say i have had no issues with wifi locking my phone up at all. i have it on right now on my phone and my phone slept about 5-10 minutes ago, and oh i just hit my power button and my phone turned on.....

lol shouldn't have spoken too soon. phone just locked up and i had to do a battery pull.... of course
 
poler166 said:
Thanks for the Update on the Name change, and thanks for the info really hope the wifi tether gets fixed for everyone :/
Click to expand...

It will, it will just take a little while. I'm sorry if I got your hopes up (or anyone for that matter.) When I had discovered it I was like "YES! I MUST SHARE WITH ALL!"

I shall keep you all updated on what I know, and change the OP as needed.
 
Clamping definitely works on my kernels and always has. The OS now supports it as well as of the 9/25 build, which means the internal tethering (Bluetooth only for now) will use it.

For add-on applications this is a kernel issue - if the kernel does not have the options enabled it will not work - period. Iptables must also support it unless the application provides its own version of iptables, and that was not in my builds (or any other CM7 builds) until the 9/25 update. It is also off by default in Froyo builds.
 
ceejay83 said:
it's not working for me on ticker's cm7. i have mss clamping and ad-hoc on.
Click to expand...

tickerguy said:
Clamping definitely works on my kernels and always has. The OS now supports it as well as of the 9/25 build, which means the internal tethering (Bluetooth only for now) will use it.

For add-on applications this is a kernel issue - if the kernel does not have the options enabled it will not work - period. Iptables must also support it unless the application provides its own version of iptables, and that was not in my builds (or any other CM7 builds) until the 9/25 update. It is also off by default in Froyo builds.
Click to expand...

I would have to say if your device that you are tethering supports Bluetooth PAN, go for that over this. The Bluetooth is more secure (you have to make your device discoverable) and it doesn't use half the power as WiFi does...
 
I installed the 9/24 build of CM7, then I installed the free Barnacle WiFi app from the Android Marketplace. The WiFi tethering worked great. I didn't change any settings in Barnacle, just ran it with the default settings.

I also tried the Bluetooth tethering, and that worked great too.

Thanks TickerGuy!!!
 
lifeblows10 said:
I would have to say if your device that you are tethering supports Bluetooth PAN, go for that over this. The Bluetooth is more secure (you have to make your device discoverable) and it doesn't use half the power as WiFi does...
Click to expand...

tether actually works, but the HP touchpad doesn't support adhoc :mad:

can you tether without adhoc?
 
Ceejay, if you have Bluetooth there's no "ad-hoc" involved - it's a NATIVE tether on the 9/25 load.

The libra problem may make a native (AP-style) Wifi tether impossible on the Triumph. We simply don't have source to the driver, Motorola (or Foxconn) stripped the symbols that have to be in there for it to work, and the other similar devices drivers (which have the symbols) refuse to load - they're just different enough from our hardware that they don't work. So unless someone can pry source to the libra driver out of someone odds are this is not fixable. I haven't entirely given up on it, but if I manage to figure out a way around this problem it's going to be like winning the lottery in terms of odds.
 
tickerguy said:
Ceejay, if you have Bluetooth there's no "ad-hoc" involved - it's a NATIVE tether on the 9/25 load.

The libra problem may make a native (AP-style) Wifi tether impossible on the Triumph. We simply don't have source to the driver, Motorola (or Foxconn) stripped the symbols that have to be in there for it to work, and the other similar devices drivers (which have the symbols) refuse to load - they're just different enough from our hardware that they don't work. So unless someone can pry source to the libra driver out of someone odds are this is not fixable. I haven't entirely given up on it, but if I manage to figure out a way around this problem it's going to be like winning the lottery in terms of odds.
Click to expand...

don't know why but my touchpad can't detect my triumph
 
tickerguy said:
Ceejay, if you have Bluetooth there's no "ad-hoc" involved - it's a NATIVE tether on the 9/25 load.

The libra problem may make a native (AP-style) Wifi tether impossible on the Triumph. We simply don't have source to the driver, Motorola (or Foxconn) stripped the symbols that have to be in there for it to work, and the other similar devices drivers (which have the symbols) refuse to load - they're just different enough from our hardware that they don't work. So unless someone can pry source to the libra driver out of someone odds are this is not fixable. I haven't entirely given up on it, but if I manage to figure out a way around this problem it's going to be like winning the lottery in terms of odds.
Click to expand...

Would contacting Google assist in possibly getting the symbols? I know that the Googlorola deal isn't finalized but Google may have some pull in the matter.
 
mss clamping is in the setting for wifi tether application.

I was able to get this running however if the screen falls asleep I loose the connection. A minor annoyance, but I just have it set to always stay awake while plugged in. If I was using on the go I guess I could have the time out be set to 30 minutes, alhtough that would kill my battery really quick.
 
Yeah, me too... when phone falls asleep I lose the connection. Oh well, I'll just have to remember to force it to stay awake when I tether. Will drain battery faster, but still this is a free solution.
 
I can't figure out how to tether with Bluetooth to my iPad. The phone and iPad do get paired. But on the phone, it says my iPad is "paired but not connected". I can't find any info on setting up bluetooth tethering on this forum. Can anyone help?
 
You must log in or register to reply here.
Back
Top Bottom