Galaxy S II wifi hotspot not working

Forums › Android › Galaxy S II wifi hotspot not working

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

38 posts

Geek

#556829 12-Dec-2011 10:58

I've now tried from an XP machine and it works fine. I also tried from a 3rd Windows 7 machine and it fails in exactly the same way - so it really looks to be Windows 7 related. But as I say, I've connected to numerous other wireless networks from this laptop without problems. Sort of suggests that windows 7 is doing something slightly different in it's negotiation with the access point which most access points can cope with but the SGSII can't handle.

A Microsoft product and a Google product failing to play nicely together, surely not...?

AliExpress

Shop now on AliExpress (affiliate link).

jonb

1769 posts

Uber Geek

Trusted

#556849 12-Dec-2011 11:29

Slightly un-related?, but I had the same kind of trouble with a new Windows 7 laptop (acer 5750) not recognising our wi-fi network. It recognised others without a problem though. There's quite a bit of information online about this (windows 7 not recognising some wireless networks), I ended up removing the wireless driver and re-installing again and that seemed to fix it.

Technofreak

6523 posts

Uber Geek

Trusted

#556851 12-Dec-2011 11:33

rjl: I've now tried from an XP machine and it works fine. I also tried from a 3rd Windows 7 machine and it fails in exactly the same way - so it really looks to be Windows 7 related. But as I say, I've connected to numerous other wireless networks from this laptop without problems. Sort of suggests that windows 7 is doing something slightly different in it's negotiation with the access point which most access points can cope with but the SGSII can't handle.

A Microsoft product and a Google product failing to play nicely together, surely not...?

There will be a way to get this to work, just a matter of how you set it up on the laptop and your phone. It can be very frustrating that's for sure.

Sony Xperia XA2 running Sailfish OS. https://sailfishos.org The true independent open source mobile OS
Samsung Galaxy Tab S6
Dell Inspiron 14z i5

robjg63

4082 posts

Uber Geek

Subscriber

#556856 12-Dec-2011 11:44

Id' make sure you have ALL the windows software patches/updates you can get installed.
Make sure you have the latest drivers for your networking hardware installed.

Apparently a lot of people find that WLAN AutoConfig (xp called it wireless zero config I think) can cause issues. Apparently it constantly polls a connection and sometimes clobbers it try disabling it (or enable it if its off).

I sympathise - for all its worth ....

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

rjl

38 posts

Geek

#556886 12-Dec-2011 12:32

Also worked fine from a Macbook in the Telecom shop.

@robjg63: The fact that it happens from different windows 7 machines with different wireless network management software (win 7 default and Sony's OEM s/w) makes me think it's something generic in windows 7 rather than the AutoConfig stuff. Plus I keep coming back to the fact that it causes the phone to go into an error state.

robjg63

4082 posts

Uber Geek

Subscriber

#556890 12-Dec-2011 12:40

rjl: Also worked fine from a Macbook in the Telecom shop.

@robjg63: The fact that it happens from different windows 7 machines with different wireless network management software (win 7 default and Sony's OEM s/w) makes me think it's something generic in windows 7 rather than the AutoConfig stuff. Plus I keep coming back to the fact that it causes the phone to go into an error state.

Yes - it sounds that way doesnt it.
Wifi networking isnt completely broken on windows 7 though, so it must be a combination of things in windows 7 hardware/software and the sammy hardware/software.

Did you have a look around for hints on the WLAN AutoConfig area?

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

robjg63

4082 posts

Uber Geek

Subscriber

#556898 12-Dec-2011 12:47

Actually I found this thread (its what you describe - dated July) :
http://community.vodafone.com.au/t5/iPhone-and-Android/Vodafone-Samsung-Galaxy-S2-Wifi-hotspot-tethering-not-working/td-p/18473/page/4

Have a look down the list (25/July) and this comment appears:
Thank you to everyone for being patient, and for the incredible amount of troubleshooting you've done. OzBoy1, thank you especially, for your posts and sharing the information you have with the other members of the Community.

We've escalated the issue through our internal testing team and to Samsung and have confirmed both the fault and the specific cause. Samsung advise they are planning a maintenance release to address this, but we don't have an ETA right now.

Then later in that thread:
Just a quick post to let you know that a couple of users over at xda who had this problem found that if they upgraded to 2.3.4 it went away

Have a cruise through that thread and see if anything helps - You might need to hassle telecom...

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

openmedia

3288 posts

Uber Geek

Trusted

#556932 12-Dec-2011 13:34

They released a WIFI fix for the S2 back in September
- http://blog.vodafone.com.au/blog/samsung-galaxy-s-ii-mr-update-dukh1/

I hoped this fix would fix my own HotSpot issues with a Telecom S2, but it turns out that the default APN settings are incorrect.

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

rjl

38 posts

Geek

#556936 12-Dec-2011 13:40

@robjg63: Thanks for that thread - I'll pass it on to the Telecom MBB helpdesl level 2 guy who is currently trying to reproduce the issue on his SGSII from windows 7.

robjg63

4082 posts

Uber Geek

Subscriber

#556973 12-Dec-2011 14:31

Hi Openmedia - Did you get the correct APN settings from Telecom?
If so I am sure rjl would be keen to try them out.

That thread on the vodafone forum also starts suggesting the APN after a while.....

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

openmedia

3288 posts

Uber Geek

Trusted

#556996 12-Dec-2011 14:52

Here are the details provided by Telecom. Their default settings have the TelecomData APN with an APN type of dun which breaks some of the tethering support.

Name: TelecomDefault                                                  Name: TelecomData

APN: wap.telecom.co.nz                                              APN: internet.telecom.co.nz

Proxy: not set                                                                  Proxy: not set

Port: not set                                                                    Port: notset

Username: not set                                                           Username: not set

Password: not set                                                           Password: not set

Server: not set                                                                Server: not set

MMSC: http://lsmmsc.xtra.co.nz                              MMSC: not set

MMS Proxy: 210.55.11.73                                             MMS Proxy: not set

MMS Port: 80                                                                   MMS Port: not set

MCC: 530                                                                         MCC: 530

MNC: 05                                                                            MNC: 05

Authentication type: PAP                                               Authentication type: PAP
APN type: internet + mms                                            APN type: internet + mms + dun

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

rjl

38 posts

Geek

#557011 12-Dec-2011 15:02

So just to be clear, is the suggestion installing the Vodafone 2.3.4 firmware and then manually updating the APN details to the Telecom APNs? If so, I'm not sure how to - Kies only seems to offer the Telecom firmware. If that's not the suggestion then I'm definitely confused.

@openmedia: Not sure I really understand all the APN settings, but I wonder if setting TelecomData to "internet + mms + dun" without providing any MMS settings might break MMS on that APN? I don't use MMS, so I don't care, but just noting it in case anyone else reading this does.

BTW, I'm really impressed by (and grateful for) the level of interest and responsiveness on this thread - I've never used Geekzone before, but I can see I will be in future. Thanks everyone for your help.

gzt

16882 posts

Uber Geek

Lifetime subscriber

#557022 12-Dec-2011 15:27

rjl: Also worked fine from a Macbook in the Telecom shop. @robjg63: The fact that it happens from different windows 7 machines with different wireless network management software (win 7 default and Sony's OEM s/w) makes me think it's something generic in windows 7 rather than the AutoConfig stuff. Plus I keep coming back to the fact that it causes the phone to go into an error state.

Vista/7 got a new TCP/IP protocol stack over XP and effectively a bunch of changes to TCP/IP defaults. There is an MS whitepaper on the registry settings (many of them are designed to be set by netsh). It will take work to narrow it down but it might be something simple like one of the window settings. Sniffing and comparing xp and vista negotiation might give a head start.

I see you have the possibility of an update resolving it, far better : ).

gzt

16882 posts

Uber Geek

Lifetime subscriber

#557027 12-Dec-2011 15:37

@openmedia - is there anyway for the OP to tell if his S2 is already running the GINGERBREAD.DUKH1 build with the wifi fix?

http://blog.vodafone.com.au/blog/samsung-galaxy-s-ii-mr-update-dukh1/

rjl

38 posts

Geek

#557040 12-Dec-2011 15:56

My phone says it's got GINGERBREAD.DOKH1 (not DUKH1).

I think this Vodafone link refers to a patch for an earlier hotspot issue (slow throughput). I've seen suggestions that this patch fixed that issue but introduced another one (potentially the one I'm hitting). The one referenced in the Vodafone link is still Android 2.3.3, whereas the fix for the later issue moved to 2.3.4.

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