Open GoogleCodeExporter opened 9 years ago
Try to uncheck/disable "Force wifi-driver reload" in app-settings.
Original comment by harald....@gmail.com
on 14 Jul 2011 at 6:56
I tried "force wifi-driver reload" checked and unchecked.
Harald is there any logging data that I could provied you that mite help you
debug and or see what's going on? Just let me know what data you need.
Original comment by zman...@gmail.com
on 14 Jul 2011 at 7:20
Could you please uninstall beta2 and install beta1? I got reports (I don't own
a epic) that beta1 works flawlessly. beta2 should act the same way like beta1
does if you uncheck/disable the "force wifi-driver reload"-option.
So. Please let me know if beta1 works for you. (Do a reboot of the phone after
every change to make sure you have a "clean" starting-point).
Original comment by harald....@gmail.com
on 14 Jul 2011 at 9:05
Tried beta1 it turned ON and OFF 3 or 4 times before it locked up the whole
phone & needed a battery pull. But the first few time my Win7_sp1 x86 Sony
Laptop(WiFI Chip Intel 5300 Driver v_13.1.1.1 date 1/13/2010) would get an IP
but no internet access.
Yesterday on beta2 it would always work on first boot of phone but not again
until the phone was rebooted.
I'm restoring a good nandroid to start fresh and do some more testing with
beta2.
Original comment by zman...@gmail.com
on 14 Jul 2011 at 7:57
[deleted comment]
This is a known issue with beta 1 too. Reference issue #894...
http://code.google.com/p/android-wifi-tether/issues/detail?id=894
Original comment by mvanr...@gmail.com
on 23 Jul 2011 at 11:08
This issue exists on the Samsung Intercept using Epic 4G profile as well.
Original comment by gypsy3...@yahoo.com
on 26 Jul 2011 at 12:37
I just use Wireless tether app with my Epic, fortunately my Nook Color now can
connect to it via ad hoc mode. Wifi Tether inevitably crashes, sometimes with
and sometimes without provocation so I avoid using it. We should all chip in a
send an Epic to Harald so he can fix the issue ;)
Original comment by dimamal
on 28 Jul 2011 at 6:20
By mistake, I found a fix for this problem. I was already running wifi tether
(tethered to my laptop) when someone asked if I could test the wifi
connectivity of their phone, so without turning off my tether app (3.0-pre14),
I enabled wireless connectivity (Settings-> Wireless & Network-> Wi-Fi
Settings-> Turn on Wi-Fi), so my phone went from putting out a wireless signal
to searching for one to connect to. I got a toast notification that I've never
seen before, I couldn't tell what app the notification was from, but it said it
was taking back the wireless signal.
Anyways, after turning off the phone's ability to connect to a wifi network, I
went back to the wifi tether app and was able to re-start tethering without
having to reboot.
I think Samsung locks down something in the process of stopping wireless tether
in this app. I've reproduced this several more times and am able to start/stop
tether without having to restart my phone now. It's definitely some extra
steps, but it sure beats pulling out my battery if I need wifi but already used
it once already.
SuperClean Fascinate on Verizon
Original comment by matt.kel...@gmail.com
on 29 Jul 2011 at 7:38
Thank you comment 9 by matt.
This works for me. I tested it about ten times. I think that whatever controls
the Wi-Fi is the same that controls wireless tether and when you turn wifi on
it boots wireless tether off. Seems that wireless tether boots wifi off too. I
just tested. Turned on wifi, turned on wireless tether, wifi got turned off. No
error message this time.
Original comment by fredsb...@gmail.com
on 3 Aug 2011 at 7:03
I'm using a Samsung Galaxy Precedent (StraightTalk) and it is having a very
similar issue but the workaround mentioned here does not work. When I turn
tethering on it works the first time just fine. Then I turn off tether, try to
turn on the wifi but it says "Error" and will not turn on. I tried force
stopping the tether since I noticed it was still running in the background, but
it did not help. So I am forced to reboot the phone if I want to start
tethering again.
Original comment by fattylic...@gmail.com
on 4 Oct 2012 at 7:38
I use 3.1-beta6 wifi teather.......works like magic every time.....my settings
for S.talk precedent.......
device profile to....galaxy indulge
Setup method auto
enable encryption
wifi driver reload
disable update check
disable wake lock.....
When flashing through cwm u gotta mount everything before install.......
if not u will have no r/w to system partition........nothing will
work........all kinda errors.......had same ones here.........
mount everything in cwm before install........fixes ot all.......
precedent with cwm.....arearom 3.5........overclock genocide
988mhz............setup runs to smooth.........try it out........
Original comment by blackshe...@gmail.com
on 13 Aug 2014 at 1:32
Im also pulling standard wifi off this app on 2.3.7 g.bread........should only
have adhoc but pushes standard wifi..................tear it up
Original comment by blackshe...@gmail.com
on 13 Aug 2014 at 1:36
Original issue reported on code.google.com by
zman...@gmail.com
on 14 Jul 2011 at 2:45