Open GoogleCodeExporter opened 9 years ago
Rene,
What ROM and Kernel are you using? I got 1.4 to work for me with 3G, but I get
no connection when attempting to use 4G. As soon as I disable 4G, I get
connection again.
Original comment by mcgrif...@gmail.com
on 24 Aug 2010 at 1:08
Also, my Wireless tether now FC's, from what I'm assuming is renaming the
libnativetask.so located in /system/lib
Original comment by mcgrif...@gmail.com
on 24 Aug 2010 at 1:51
Yeah the libnativetask.so stuff seemed a little quirky to me. I think you could
remove the /system/lib one and uninstall both wireless tether and wired tether
and then reinstall both. I think that may work best. The inclusion in ROMs is
tricky.
Original comment by dligh...@gmail.com
on 24 Aug 2010 at 1:58
Guys ... remove libnativetask.so from /system/lib. This library is application
(wired or wireless tether) specific. Copying libnativetask.so from the wireless
tether-package to /system/lib will break wired tether and vice versa!
Simply install the app (copying the apk to /system/app or /data/app is NOT
INSTALLING) and the library is placed into the correct directory!
Installing vie adb:
adb install wired-tether.apk
From commandline (on your phone):
pm install /path/to/wired-tether.apk
Original comment by harald....@gmail.com
on 24 Aug 2010 at 9:09
Yeah, got both wired and wireless tether working by reinstalling both apps
after removing the /system/lib/libnativetask.so file.
My only problem now is that wired tether will not work when my phone has a 4G
connection. If I ping google.com, I get:
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 192.168.1.254: Destination net unreachable.
Reply from 72.14.204.103: bytes=32 time=95ms TTL=50
Reply from 72.14.204.103: bytes=32 time=80ms TTL=50
Reply from 72.14.204.103: bytes=32 time=86ms TTL=50
Reply from 72.14.204.103: bytes=32 time=85ms TTL=50
Reply from 72.14.204.103: bytes=32 time=75ms TTL=50
(It starts working as soon as I disable 4G and it kicks back over to 3G)
What are some of the troubleshooting things that I can be doing to help solve
this?
I'm using Fresh 3.1.0.2 with netarchy's stock kernel for fresh.
Original comment by mcgrif...@gmail.com
on 24 Aug 2010 at 11:10
I'm online w/1.3 & the fix now too. I get unsupported kernel when I'm using
stock deodexed 2.2 w/2.6.32.15 kernel. Click ignore & I'm online. Win7 & did
not require a driver.
Original comment by LAY...@gmail.com
on 25 Aug 2010 at 1:45
Laygo, did you try 1.4 with the fix? It should mostly be just removing the
unsupported kernel warning.
Original comment by dligh...@gmail.com
on 25 Aug 2010 at 1:49
I have almost the same situation as mcriffin on #55..Both wifi and usb tethers
work..I have 1.3 usb tether and I did not do the fix and I do have 2
libnativetask.so files and both tethers work..But usb will only work when on
4g..When I switch to 3g it stops working and starts when I turn 4g back on?
Original comment by jeep...@gmail.com
on 26 Aug 2010 at 12:04
Sorry I forgot....Im on Fresh 3.1.0.2 with netarchy 4.1.8 kernel using win7
32bit
Original comment by jeep...@gmail.com
on 26 Aug 2010 at 12:06
Hi jeep! Are you changing from 3g to 4th and vice versa while tendering is
running or do you restart it? Mgriffin said on XDA that he found his 4th isn't
working and that's his culprit.
Original comment by dligh...@gmail.com
on 26 Aug 2010 at 11:26
On my HTPC this app, with fix, it is working kind off acceptable, meaning I
have to restart app every so often ranging from 1-2 hours, and eventually it
requires a hard reboot of my HTPC as it locks up some USB ports. At home I
mainly am connected via 4G.
On my Laptop however, the app stops working, or rather transferring data much
more frequent, every 30-45 minutes, to the point of being to much of a hassle,
so that when I work on my laptop I instead use the wireless tether app
2_0_5-pre8 which is 100% reliable.
Original comment by RFeuerl...@gmail.com
on 27 Aug 2010 at 11:52
David,
Not sure what your preferred method of communication is, but I figured this
forum will do nicely, since it allows other to follow along with
troubleshooting.
I'm using an HTC EVO with Android 2.2 installed
I downloaded and installed 1.4, which gives me force closes. I applied the
libnativetask.so fix, which fixed the force closes.
Then, I still had the connectivity issues. Applied the symlink fix. That fixed
the connectivity issues, but it broke my 4g. Not only while tethering, but also
when using the phone (for browsing, maps, apps, etc). Turning off 4g restores
data, however.
Any ideas?
Original comment by aseli...@gmail.com
on 9 Sep 2010 at 8:39
aselivra,
I check in here every few days and also when I get updates emailed to me, but
my gmail is the fastest since it hits my phone the quickest and it's easiest to
respond from on the phone.
I'm not in a 4G area, so it's a little tricky for me to test those cases or do
work for it, but I'll do what I can. I thought some people had mentioned
successfully using 4G, including tethering, after these fixes, so I'm not sure
what is different between their setup and yours. Are you on the stock rooted
2.2, or are you on one of the custom ROMs? What about stock or custom kernel?
I'll try and compile a new list of working/problematic ROMs and kernels to see
if there's a commonality in there again.
How technical are you in regards to the phone (do you dabble with adb or
terminal? do you hack the kernel? or are you an out-of-the-box kinda guy?) --
I'm just trying to get a feel for what I can have you check or do comfortably.
Which would you prefer to have more at this point (in the interim while I try
to figure out the 4G issues), 4G and no tethering, or tethering and no 4G? I
can help get you to either I'm pretty sure, and I have a short-term idea in
mind that could probably even allow you to do both (but not 4G and tether at
the same time yet) with a small extra step in there.
Original comment by dligh...@gmail.com
on 9 Sep 2010 at 1:44
I created a couple of simple signed update.zip files to cover a couple of
different use cases (those wanting 4G working again at the expense of wired
tethering; and those that want both [only one or the other active at a time,
though] and are comfortable running a simple shell script).
Check over here at XDA for the full details:
http://forum.xda-developers.com/showpost.php?p=8083070&postcount=149
In short, SignedWiredTetherRestore.zip is to get back the original ip binary
instead of my previous symlink fix; SignedWiredTetherFixToggle.zip is for those
wanting the shell script to toggle the symlink between the original and toolbox.
Original comment by dligh...@gmail.com
on 10 Sep 2010 at 12:42
Attachments:
Original issue reported on code.google.com by
RFeuerl...@gmail.com
on 17 Aug 2010 at 9:37