Galaxy S II wifi hotspot not working

Forums › Android › Galaxy S II wifi hotspot not working

1 | 2 | 3 | 4 | 5 | 6 | 7

10 posts

Wannabe Geek

#561313 24-Dec-2011 23:58

Has anyone found a solution to this issue
I also have a telecom galaxy s2 with the same problems. WIFI tethering is very temperamental and even when it works lasts less than a minute

I've tried to use USB tethering but windows can't seem to find the right driver for it. Looked online but couldn't find it either. Any idea where i can find this driver?

AliExpress

Shop now on AliExpress (affiliate link).

gzt

16986 posts

Uber Geek

Lifetime subscriber

#561387 25-Dec-2011 15:15

Does the WIFI tether issue occur only with Vista SP2 and later?

gzt

16986 posts

Uber Geek

Lifetime subscriber

#561394 25-Dec-2011 16:07

chaminda: I've tried to use USB tethering but windows can't seem to find the right driver for it. Looked online but couldn't find it either. Any idea where i can find this driver?

Latest Kies version (dec 5 2011) will have it: http://www.samsungapps.com/about/onPc.as

saenglish

65 posts

Master Geek

#562884 30-Dec-2011 13:41

Hi,

Just thought that I would add my 2 cents to this problem.

Wifi tethering on my s2 works well with a galaxy tablet. As soon as I connect using either of the two win 7 machines I have, I manage to get about 4 more pings (on a previously set up continuous ping) and then the tethering stops on the s2. i.e can not ping phone from either tablet or win 7. Interestingly neither say they have lost wifi connection.

I then turn of the tethering. It takes about 6 seconds and returns a blue error message and the tethering symbol is still on at the top of the screen and the other machines are showing that the s2 wireless is still there.

If I then turn the tethering back on it comes back but on the continuous ping from the win 7 machine i normally get about 1 to 2 pings before the tethering is broken again.

one good thing I guess is I am getting much better at using the tablet.

Currently on hold with Telecom.

I thought I would try usb tether to one of the win 7 machines and wireless tether by the tablet and the other win 7. The second windows 7 did not kill the wireless tether until I stopped the usb tether.

Talking to 2nd helpful telecom person. My apns are both set to internet+mms I do not have the option to set it to internet+mms+dun, which is what she says I need.

That is where I am at, at the moment

regards

saenglish

65 posts

Master Geek

#562949 30-Dec-2011 17:43

More Info,

When talking with telecom the person at the other end wanted to see what apn s I had. I had the standard 2 telecom ones. Both were set to internet + mms. She said that it should be internet + mms + dun. I do not have that option. I only had internet + mms, internet or mms. She said that she was looking at a GS2 which had the fourth option. We checked version and build numbers and they were both the same.

When I went to the telecom shop we had a look at another GS2. I only checked it TelecomData apn and that was set to dun only. But when the options were looked at it did not have a dun option. Just the same three that I had. They were at a loss as to how the dun had been set in the APN type (didn't have time to finish the conversation so will continue the hunt at telecom tomorrow morning.

cheers

rjl

38 posts

Geek

#563049 30-Dec-2011 22:01

Interesting that usb tether from one win 7 machine seems to make wifi tether stable from another one. That could actually be a useful workaround for me until Telecom comes out with a fix (if they ever do).

Don't hold out too much hope for the interent + mms + dun setting. I thought that sounded really promising when OpenMdia posted that right up at the top of the first page of this thread - but though it changed the behaviour a bit for me it didn't solve it. It had solved things for OpenMedia, but he wasn't using a a windows 7 machine.

Incidently, did you try following the instructions for that setting exactly as OpenMedia posted them - that let me make that change on mine.

CdTDroiD

869 posts

Ultimate Geek

Trusted

#563090 30-Dec-2011 23:27

I havent bothered to read through the whole thread but have you guys tried to update the modem ?

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

rjl

38 posts

Geek

#563163 31-Dec-2011 10:43

What modem? I have no idea what you mean.

CdTDroiD

869 posts

Ultimate Geek

Trusted

#563165 31-Dec-2011 10:47

Maybe look into it a bit more then:

Galaxy S2 Modems

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

saenglish

65 posts

Master Geek

#563487 1-Jan-2012 14:33

Hi,

Okay,
Was back at the telecom shop saturday morning. Did a factory reset on the phone. That gave me all the options for the APN. Now set to ...+dun. It didn't help.

Now have a reference number with samsung with a promise to call me back at the end of the week.

I agree that the usb tether / wireless tether will work for me at the moment

@CdTDroiD I am assuming I would have to have rooted the phone to change the modem file. Currently not interested in rooting phone.

cheers

CdTDroiD

869 posts

Ultimate Geek

Trusted

#563509 1-Jan-2012 15:27

No you assume wrong, you dont have to root to update the modem but thats up to you. APNs dont have anything to do with it and Telecom wont help you either, they probably know just as much as you do. But heres whats for sure... 1. Its not a hardware fault, 2. It could have something to do with what you are trying to connect it to and drivers etc, otherwise 3. Modem

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

rjl

38 posts

Geek

#563514 1-Jan-2012 15:56

It's pretty clear from all the experiences with S2s on other carriers' networks that Samsung know all about the problem and have released fixes for other carriers - based on Android 2.3.4. I know Telecom are in touch with Samsung on the issue, but have no idea if or when there will be a new Telecom release.

The possibility of upgrading the modem without rooting the phone is interesting - I hadn't realised that was an option - like saenglish I'm not interested in rooting the phone.

@CdTDroid: thanks for the link to S2 modems - though I have to confess it left me none the wiser about which of the many options to consider or how to go about upgrading.

saenglish

65 posts

Master Geek

#565381 6-Jan-2012 14:55

hi,

Have now spoken directly with Samsung, They are now requesting that I give them my phone for further testing. They are still appear to trying to see this as a single unit fault. So if you have this fault and have not contacted telecom and samsung (0800 726 7864 New Zealand) then please do.

regards

saenglish

65 posts

Master Geek

#570751 19-Jan-2012 11:53

The phone is back. Totally unhappy with the final experience of telecom nz, telegistics and samsung.
It was samsung that requested I return the phone to telecom. Telecom sent it to telegistics. The fault read "Wireless tethering is not working with windows 7"

On checking telegistics site and the work order their records showed.

11/01/2012 3:17:12 p.m.

Unable to verify fault. Phone bench test and working normal, applications are working normal, on air test passed, tested ear/loud speaker and microphone are working normal, tested display, touchscreen, wifi tested ok, web connection test passed. keypad, camera functions, general functions and charging ok. pass to software reflash as per precaution.12/01/2012 8:52:08 a.m.SW REFLASHED.

I then rang them to find out if they had even tested it with a windows 7 machine. The had not. I spoke to the "technical manager" who said he assumed the test had been done. On talking with them again the next tuesday He said they still had not don the test and hoped to be able to do it tomorrow.

What sort of service centre is this they don't even focus on the actual fault. Hey but I am pleased they tested the speaker and microphone, keypad, camare etc. Because those all have so much to do with wireless tethering.

As stated it was samsung that requested(supposedly from level 3 support) i send the phone in. I rang samsung to see what part they were playing in this. I was told "no the phone will stay with telegistics, we will only be involved if they contact us for help". Not great support from them I fell.

Telecoms part. Well they are the ones I have a contract with so I rang them to complain about the inability of their contracted service centre to actually follow up a fault with valid tests. still haven't heard from them.

After telegistics returned the phone this is what the rest of the work order says

18/01/2012 9:08:49 a.m.
Tested wireless tethering with Windows 7 OS - working ok. (Connected Win7 laptop to the device thru WiFi hotspot in the device and browes internet for 2-3 hrs . Laptop connected to the device without any problem.) If the fault persists ,Pls check this forum for more info : http://androidforums.com/samsung-galaxy-s2-international/353504-wireless-tethering-sgsii-windows-7-a.htm
l18/01/2012 11:10:24 a.m.
TRANSCEIVER, BATTERY, BACK COVER CHECKED

That reference has no useful info in it at all, and what did they really think I hadn't been there already.

Mean while have a brand new aspire onee with a fresh install of windows 7 - all updates, latest wifi driver
It connected with the s2 tether and lasted 56 pings. Enough to surf about 4 pages and download flash plugin.

Then it stopped and we are back to where we were. Well done Telecom, Telegistics and Samsung.

I have asked telegistics to inform me of the version of window 7 it was tested with. All my machines are widows 7 enterprise.

rjl

38 posts

Geek

#570765 19-Jan-2012 12:25

I followed up on my case with Telecom yesterday.

I think my case must have followed a different route in Telecom - I think it went to a specialist Mobile Broadband group rather than Telegistics.

I was told that they had tested with one of their devices using 2 Windows 7 machines before Christmas. They had intermittent failures with one of the Windows 7 machines and I'm slightly unclear whether it always worked or never worked with the other one. Anyway, they acknowledged the problem and had escalated this to Samsung before Christmas - but no reply yet. I was promised a further update by the end of the week.

1 | 2 | 3 | 4 | 5 | 6 | 7