Wireless tether for root users

loserpunk701 · #1 (**permalink**) 04-12-2010, 02:20 PM

Ok, so I had previously flashed to ZE14 and was using wireless tether fine. I was having trouble with the auto-rotation, was suggested to re-flash with a diff kernel. I used joeykrims final kernel. Now when I open wireless tether it says "sorry, but your kernel does not have all necessary features for running this application"

and when I click ignore and do it anyway, it says "wireless tether started with errors."

does anyone else get this problem... I'm just gonna go back to ze14....

**rainfreak** · #2 (**permalink**) 04-12-2010, 02:34 PM

Sorry but I stuck with Zeife's kernel on my Moment because, other than the occasional lines, it worked too well not to.

loserpunk701 · #3 (**permalink**) 04-12-2010, 02:42 PM

yea well, I am gonna flash back to zefies, but everytime I try to do it since after the first time I flashed to a custom kernel I CANNOT get a usb connection for SHIT.

**rainfreak** · #4 (**permalink**) 04-12-2010, 02:55 PM

I only had that problem once (between flashes). To fix it, I uninstalled SWUpdate, restarted my laptop, reinstalled SWUpdate and then it worked fine. If all else fails, give that a try.

WisdomWolfX · #5 (**permalink**) 04-12-2010, 05:12 PM

The problem is that joeykrims kernel doesn't have netfilter. I would suggest Speedrabbit 1.7 as it's based on joeykriims, but has netfilter added in order to support wifi tether.

chibucks · #6 (**permalink**) 04-12-2010, 06:46 PM

Quote:

Originally Posted by loserpunk701

yea well, I am gonna flash back to zefies, but everytime I try to do it since after the first time I flashed to a custom kernel I CANNOT get a usb connection for SHIT.

you could also reflash zefie / joey / speedrabbit's kernels via recovery using the ZIP files they provided... its faster and you don't have to mess with the computer.

loserpunk701 · #7 (**permalink**) 04-19-2010, 03:45 PM

I am back to ZE14.3 and now I am having problems again... why me?

So I am using wireless tether so the old lady can use her laptop.... it lasts about 10 minutes, and the computer no longer can surf the web. there seems to beem to problem that you can see. just that it stops browsing the web. I have to completely reboot my phone and start tether again to use it, and it only works for another ten minutes... so on and so on.... anyone? ...anyone?

[edit] also Idk if this is related or not, but I'm having data issues. as in, I cannot send pciture messages for some reason. I am using handcent, deleted the oem msging. downloaded chomp and it does the same thing, just has the little sprint circle spinning and spinning...... err. other misc. data problems. wtf did I do?

**rainfreak** · #8 (**permalink**) 04-20-2010, 09:05 PM

For the tethering to work, I thought you had to use setCPU and back the processor down to 266 mhz. I have never needed to tether but I thought that is what I read to make sure that it is able to function with stability.

WisdomWolfX · #9 (**permalink**) 04-21-2010, 02:43 PM

Quote:

Originally Posted by loserpunk701

I am back to ZE14.3 and now I am having problems again... why me?

So I am using wireless tether so the old lady can use her laptop.... it lasts about 10 minutes, and the computer no longer can surf the web. there seems to beem to problem that you can see. just that it stops browsing the web. I have to completely reboot my phone and start tether again to use it, and it only works for another ten minutes... so on and so on.... anyone? ...anyone?

[edit] also Idk if this is related or not, but I'm having data issues. as in, I cannot send pciture messages for some reason. I am using handcent, deleted the oem msging. downloaded chomp and it does the same thing, just has the little sprint circle spinning and spinning...... err. other misc. data problems. wtf did I do?

This is a very well known issue with the Moment. It's that CDMA lockup bug that happens randomly with or without tethering. It's better in 2.1, but not fixed yet. Speculation is that it's caused by the RIL (Radio Interface Layer) that Samsung used since 1.5 had no build in CDMA support.

As Rainfreak suggested using setCPU to limit the CPU to 266MHz when tethering has been reported to reduce the liklihood of this problem.