|Unable to Tether after 2.3.6 update||Matridom||9/2/11 7:39 AM|
Device: nexus S I9020A
Country / Language: English
OS / Browser / build number (if applicable): 2.3.6
Since this update, whenever I tether, I loose 3G connectivity, either through Wifi tethering or USB tethering.
If i use an alternative APN (a secondary APN for VPN access) I am able to tether.
|Re: Unable to Tether after 2.3.6 update||alzakx||9/2/11 7:44 AM|
I can confirm this happened after the recent 2.3.6 update. Google, do something about it.
|Re: Unable to Tether after 2.3.6 update||alexblack456||9/2/11 7:45 AM|
Device: Nexus S I9020AUCKF1
Same here, when I turn on the wifi hotspot, I lose 3g/2g data connectivity, e.g. I can no longer surf the web, check twitter, get new emails etc.
|Re: Unable to Tether after 2.3.6 update||Priit-Android||9/2/11 7:47 AM|
I have the same issue (as I am sure does everyone else who just updated to 2.3.6)
Can't use the phone as a hot spot, since enabling that options completely drops the 3g connectivity.
At least now I can use the phone (since 2.3.6 the search bug seems to have been fixed)
But seriously Google ... one issue fixed and a whole new aswesome issue caused .. SERIOUSLY !?!?!?
I am slightly ashamed to recommend the Nexus S to my friends who are considering it... I used to be a big proponent of Android and the choices it gave to customers, but this lacklustre "phone" has been SUCH a dissappointment, that I can't in good conscience recommend it to anyone I know.
|Re: Unable to Tether after 2.3.6 update||Feather Dust||9/2/11 7:51 AM|
What do you mean by using an alternative APN for tethering
|Re: Unable to Tether after 2.3.6 update||Matridom||9/2/11 7:55 AM|
On the standard Telus APN, you are unable to establish a VPN tunnel. If you pay for VPN access ($5/month) you are able to use a secondary APN that *will* allow you to create a VPN tunnel. The downside to this alternative APN is that you can only VPN, nothing else will work.
When i connect to the VPN access point, I am able to tether without any hitchs. And since i tend to only tether for work reasons, this issue will not affect me too much.
Also, reading around, someone who has installed the new modem on the cyanogen nightly is able to tether as per normal. So this "bug" has been introduced into the kernel of the phone. Reverting back to 2.3.4 would likely fix it. Then flash the newer modem to get ride of the search bug.
|Re: Unable to Tether after 2.3.6 update||Lastfall||9/2/11 8:00 AM|
I think I will keep the search button bug and not update 2.3.6 since I often use the hotspot
|Re: Unable to Tether after 2.3.6 update||jbolts||9/2/11 8:03 AM|
the 2.3.6 update did not solve the search bug issue and now activating tethering or mobile hot spot kills 3g connection.
I called Fido and they told me to pull battery and sim card abdicate that didn't work to go into a Fido store and have them look at it.
Every update makes the phone worse are they doing it on purpose or what??
also my little cursor to edit text is now offset...the "handle" does not align properly and it behaves erratically also ...
|Re: Unable to Tether after 2.3.6 update||Feather Dust||9/2/11 8:04 AM|
I replace my phone about a month ago and I haven't had the search bug since.
The new update was automatically downloaded and looks like it will install next time I reboot.
Any idea if there is a way to cancel it.
|Re: Unable to Tether after 2.3.6 update||LiqduifireAK||9/2/11 8:41 AM|
I have this issue too.
After i updated to 2.3.6 i got cant tether or have a wifi hotspot
|Re: Unable to Tether after 2.3.6 update||Infomanic||9/2/11 8:43 AM|
I'm having the same problem.
When I activate hotspot or USB tethering, and the 3G icon disappears, and neither the phone or any device attached to the hotspot can get data connectivity.
When I disable the hotspot, the 3G icon returns, and the phone can access data as normal.
I did notice that after the update, my hotspot name had reverted to AndroidAP. This is something that has not happened on any previous update.
|Re: Unable to Tether after 2.3.6 update||MaximeRoy77||9/2/11 9:39 AM|
|Re: Unable to Tether after 2.3.6 update||elvisglazier||9/2/11 9:53 AM|
I have the same problem as everyone else. Without tethering my tablet has been rendered competely useless. Can someone post how to downgrade to 2.3.4
Do I need to root my phone to downgrade?
Are the developers at Google competely withot intelligence?
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/2/11 11:13 AM|
Help, I have the same issue... I want my money BACK!!!!
I also need to downgrade to 2.3.4..
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 11:23 AM|
Hey Google, this is me on my way to Best Buy to return this NOW hunk of junk. If you people don't announce something by the end of the working day about this I'll be returning it. Also, how do you people release somthing without testing it. It's not like you rushed it through. Just amazing.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 11:24 AM|
Come to think of it, I might return my Xoom also since that is a waste of time also now. Idiots.
|Re: Unable to Tether after 2.3.6 update||Tom9020||9/2/11 11:56 AM|
Same problem here (on Rogers in Canada). The update scrambled my settings for Wi-Fi tethering and when I re-entered them the tethering still didn't work. Switched to USB tethering and that still worked but only on 2G.
to the people freaking out here.... this is a serious bug, but we shouldn't judge them on this alone - all companies make the mistake of rolling out OS updates with serious bugs - we should judge them on their response.
I would like to see them stop the update from rolling out, provide a fixed update as soon as possible, and communicate with us about how long that will take. But don't expect a fix tomorrow - they are going to have to create a new candidate image and test it (and hopefully they will test it properly this time).
So, yes, this is a huge inconvenience, but it happens.
Personally, I think they should implement update channels for Android, same as they have for Chrome and Chrome OS.
|Re: Unable to Tether after 2.3.6 update||fxb005||9/2/11 11:56 AM|
Wow - these bugs seriously makes me regret buying a nexus s.
I am with telus and now I can't use tethering anymore because of the update. But before the update I had the search bug.
No patch notes - no information from google whatsoever. I am really disappointed...
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 12:20 PM|
@Tom9020, yes it's a serious bug and this bug is costing some people money.
Also, although there may not be a fix by tommorow, there's ZERO excuse for them to not make an acknowledgment announcement of some sort so that
we know that they're on it and it wasn't some sort of intentional move on their part because the U.S. carriers or whatever.
Personally I find it hard to believe that they're this stupid and I think this quite possibly was intentional. I hope I'm wrong. Regardless, I'm going to double check my bill and if I have time and they haven't announced anything, I'm returning it.
|Re: Unable to Tether after 2.3.6 update||elvisglazier||9/2/11 12:37 PM|
Don't hold your breath if you're waiting for a fix for this. I just found out in a very reliable source that all the nexus s phones in canada will no longer have tethering option out of the box.
This is due to pressure put on them by the telecoms here in canada. I would recommend that if you haven't upgraded to 2.3 .6 you shouldn't.
Rumor is also that the new version of ice cream sandwich will have the option completely removed from the phone.
|Re: Unable to Tether after 2.3.6 update||yumifaeldo||9/2/11 1:05 PM|
it seems like the affected ones are those with I9020A. Anyone with i9020T (TMobile version) having the same issues with tethering?
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/2/11 2:50 PM|
But, only affect the candaian Nexus S or also the At&T NS??
|Re: Unable to Tether after 2.3.6 update||TheCharles||9/2/11 3:02 PM|
Will be rolling back to 2.3.4 ...
|Re: Unable to Tether after 2.3.6 update||sergeyle||9/2/11 3:45 PM|
This is not at all a 2.3.6 issue. It is known since 2.3.4. See, for example this thread: http://forum.xda-developers.com/showthread.php?t=1195531 (and many others).
My Nexus S is
and it had this from the very first day I bought it.
As elvisglazier noted above, this not at all looks like a bug, but rather like an arrangement Google came to with the telecoms.
What I'm really curious about is whether the folks that pay for a tethering package also experience this problem. And if they don't, I would really like to know what mechanism Android is using to check if a given line is eligible to tether.
|Re: Unable to Tether after 2.3.6 update||alexblack456||9/2/11 4:06 PM|
Hi paul, I installed the update this morning, and now I just experienced a few mins of almost non stop symptoms of the bug, so its not fixed. This happened while driving on the highway just north of Barrie so perhaps related to a weak connection.
I am with rogers. I was watching a YouTube video when the problem started up.
Thx, hope you guys can resolve the problem fully.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 4:20 PM|
@alexblack456 I spoke Rogers earlier and I was told that that everything that needs to be done to my account for tethering is done. That tells me A) The morrons at google did this for the U.S. carriers without any thought to their canadian customers or B) The morrons at google did this to increase sales of their 3g Xooms or C) the morrons at google screwed up again after months of working on getting it right.
I don't understand how stupid a company as a whole has to be in order to understand that when you screw up like this it represents millions. Do they make so much that they don't care. I know I'll never buy Nexus or Motorola again. I can only imagine how many are thinking the same thing. Based on what I've read, there's a lot.
This is making me miss my Iphone.
|Re: Unable to Tether after 2.3.6 update||alzakx||9/2/11 4:40 PM|
If you think of it, we all were mayor screwed. First Google announces that Gingerbread will provide tethering features to share your data conection with other devices. To users that seems fair, you pay for it don't you? Its your right to use it however you want. Network providers can, if the want, limit your data to X amount of GB per month, it's up to you to eat up that data any way you want.
So what happens? Network providers pressure Google to remove this feature so that they can sell more of the Mobile Network/Air Cards plans hoping customers who pay for $30mo for data on their phone, are forced to pay another $30 for data with their Air Cards. That's Network Providers greed at its best right there.
So, going back to Google, they attract customers to buy their Gingerbread devices with the premise that they will be able to tether (if allowed by the provider) and lots and lots of NS are sold. Everyone thinks this is so cool. Once users are in, BAM! Google closes the "offer" of tethering and removes it. What happens? We are trapped and feel cheated on and ripped off.
What we need to wait and see if the TMobile version gets an update too that screw them out of tethering also.
I simply don't understand, if this piece of sh*t is supposed to be the developer phone, it is supposed to be open for all bands and networks. More so, if you buy an unlocked version, you should get a completely unrestricted device to use as you please.
This is just stupid. And like I said, we will not hear from anyone at Google for the next few days. Maybe next Tuesday, if at that.
I don't think they will show their face here for a long long time.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 4:46 PM|
I'm paying just under 100, I'm on the verge of going backwards as far as phone goes and getting a simple voice and text phone.
|Re: Unable to Tether after 2.3.6 update||Msroest||9/2/11 5:36 PM|
I was able to get tethering working again on my Fido Nexus S by editing my APN's and adding dun to the APN Type setting of my default APN.
Settings->Wireless and Networks-> Mobile Networks -> Access Point Names-> Touch default APN.
Scroll down to APN Type
and add ,dun to the end of the list.
|Re: Unable to Tether after 2.3.6 update||mola2012||9/2/11 6:33 PM|
@msroest - that worked for me!
|Re: Unable to Tether after 2.3.6 update||alzakx||9/2/11 6:58 PM|
Well well well, what do we have here... if you are running on AT&T the correct settings to make tethering working on the APN Type field are:
and if that doesn't work, try
Before that I used to have
and did not work when adding ,dun at the end.
**Please remember to SAVE the APN, not just hit the back button. **
If someone else can confirm it works on ATT for them that would be great. If it does please run this test:
- Power off your phone
- Turn on your phone
- Enable tethering
At this point mine does not work anymore so I have to go and update the APN again to get ir working
|Re: Unable to Tether after 2.3.6 update||JustCallMeWen||9/2/11 7:43 PM|
,dun works for tethering but for portable hotspot, its a hit and miss situation.... got my OTA update... with Koodo mobile
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/2/11 7:43 PM|
Nope, doesn't work with Rogers
|Re: Unable to Tether after 2.3.6 update||TyFerguson||9/2/11 8:57 PM|
Default,supl, dun only worked the first attempt for me, but after turning off hot spot then back on there was no 3G connection.
Using other APN types did not work, not even going back to default,supl,dun after a while made it work the first time. Gunna talk to a couple retailers tomorrow and pass on forum.
Using Telus in the kawartha lakes area
|Re: Unable to Tether after 2.3.6 update||Tom9020||9/3/11 9:17 AM|
Playing with APN's didn't work for me.
Tethering is a critical feature for me so this is a huge problem.
I find it hard to believe that Google did this on purpose (shut down tethering). After all, the tethering facilities and options are all still there - they are just broken.
I'm still hoping that Google will respond soon and in a way that restores my faith in them...
|Re: Unable to Tether after 2.3.6 update||Beavis8||9/3/11 10:43 AM|
Same here. I did the OTA from Telus yesterday and tethering is now broken.
I never had issues with the Voice Search so I would rather have 2.3.4 back!
Hello Google... anyone there?
|Re: Unable to Tether after 2.3.6 update||Eusquesio||9/3/11 2:52 PM|
i have a I9020-T and running 2.3.4 at the moment; will I lose tethering facilities after updating to 2.3.6?
(i never ever had the search problem for some reason, and i have always being able to share my connection through hotspot. I don't really need those issues!)
|Re: Unable to Tether after 2.3.6 update||s3abreeze||9/3/11 4:57 PM|
Thanks for the 'dun' suggestion. I'm on koodo and added dun to the list.
Tethering comes on sort of randomly. I've been turning on the 'portable wifi hotspot' , wait to see if 3g turns off, if it does i go into mobile networks : manually turn off 'data enabled' / wait 10 seconds / turn it back on and the 3g appears again with tethering and stays on. This is working for me most of the time. Sometimes I have to turn off the data again, wait 10 secs. and then back on.
|Re: Unable to Tether after 2.3.6 update||Nick Presta||9/3/11 11:21 PM|
Link to bug report: http://code.google.com/p/android/issues/detail?id=19780
|Re: Unable to Tether after 2.3.6 update||Alexandre T.||9/4/11 7:45 AM|
I call support technique at Rogers. They told me hard reset my device after update. I dont really want to try for nothing. Anyone has tried that?
|Re: Unable to Tether after 2.3.6 update||Alexandre T.||9/4/11 10:21 AM|
Problem fixed. I changed APN type. I erased supl and put dun instead.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/4/11 2:56 PM|
I change the apn, but doesnt work...
|Re: Unable to Tether after 2.3.6 update||hichew||9/4/11 4:33 PM|
Wireless & Networks/Mobile Networks/Access Point Names/Rogers/APN Type:
APN Type: default, supl, mms, dun
|Re: Unable to Tether after 2.3.6 update||Tom9020||9/5/11 8:09 AM|
"I call support technique at Rogers. They told me hard reset my device after update. I dont really want to try for nothing. Anyone has tried that?"I'd hesitate. Usually, it is not really meant to fix your problem - it is just their generic advice given for any problem.
The only relevant effect I can imagine from doing this is that it would cause your phone to pick up the APN settings from the SIM again, but that won't help - the default SIM settings don't work. And besides, I think you can reset the APN settings via an option in Android settings - without having to reset the phone.
|Re: Unable to Tether after 2.3.6 update||cafebabe||9/5/11 11:39 AM|
I replaced "supl" by "dun" and it seems to work (I'm with Telus)!
|Re: Unable to Tether after 2.3.6 update||fxb005||9/5/11 1:44 PM|
Replacing "supl" with "dun" only works partly for me. Sometimes my 3g signal disapears. I am with telus.
|Re: Unable to Tether after 2.3.6 update||Chonex||9/5/11 7:14 PM|
I also had this issue: after upgrading to 2.3.6 my Nexus S wouldn't tether.
my solution came from north49 in xda-developers which some of the the guys here like alzakx also suggested.1. create new apn, copying the values from your default apn.
2. apn type: default,dun
-----> ",dun" seems to be the key here.
3. save it
4. activate it
5. not sure it has any effect, but turn the phone off and then on again
6. turn on tether
7. try itthis post is being written with a xoom tether to my fixed nexus s.
not sure I will be able to tether in the future as flawlessly as before.
|Re: Unable to Tether after 2.3.6 update||girishv||9/5/11 10:03 PM|
I am on Fido... I just added dun to the end of the list for the Fido Internet apn..seems to be working but... After I restarted my phone it wasn't working but I just go to the list...get into it and choose to save..and go back again and turn it on..seems to be working. It seems like it doesn't work the first time for some reason. Hopefully this is fixed soon. I am posting this through my tethered connection.
|Re: Unable to Tether after 2.3.6 update||nothappyontario||9/6/11 7:01 AM|
I'm with rogers. APN fix didn't work or me. Voice search bug is gone but no hotspots or tethering. Time for a product recall. Question is will it be forced, or voluntarily?? Tonight, I will post contact #'s for Canadian consumer affairs.
AlexandreT, restoring my phone to factory on the weekend did nothing to help and despite enabling backup, I lost most of my apps.
|Re: Unable to Tether after 2.3.6 update||halbertabeef||9/6/11 11:09 AM|
Device: Nexus S I9020A
Purchased: May 19/11
Out-of-box: 2.3.3, upgraded to 2.3.4 late May/early June?, "upgraded" to 2.3.6 Sep 2/11 to fix spontaneous voice search
Ran on 3G Google-earthing realtime from vehicle all day Saturday Sep 3, in fringe- or full-coverage areas, and no voice search pop-ups. That's the good news...
Enabled Tethering or portable hotspot and this knocked out the 3G symbol and internet coverage. Disabled Data and re-enabled it -- 3G appeared for a few seconds and then disappeared.
Disabled Tethering, but 3G would not come back until I searched carriers and re-registered with Telus.
Today, in APN, edited "default,supl, ..." to "default,dun .." as suggested by several contributors above, saved, turned on Tethering; 3G disappeared momentarily and then came back; seemed to remain solid while I tested with wifi PC.
Powered off phone; then powered it on. Turned on Tethering, 3G remained on for 10 seconds or so and then disappeared. Disabled Data; then re-enabled it, and 3G came back and stayed on. Not sure if this procedure will work next time!! This is *not* the way tethering should work -- an internet connection should be *there* the moment the hotspot becomes active.
Tethering was a key feature in my decision to buy this phone and enroll in the 10 GB 55+ data plan: it would allow me to abandon a much more expensive landline/internet account. So while Telus/Google/Samsung try to shift the blame to each other, I'm laying out $70 per month for a seemingly cursed and whimsical "dumbphone", *and* paying for the landline.
Seems to me this is getting very close to "breach of contract" on the part of Telus, if they continue to buy the line that this is a software problem.
A few Nexus S users have written saying they've had none of the problems noted in this forum (and others), but for those of us who've experienced these several months of frustration, I think it's time Google, Samsung, and the retailers/carriers bite the bullet and issue a blanket recall on this wretched phone. Those who wish to trade "up and away" from the Nexus S should be given that opportunity, no questions asked; those who think they're having no problems can ignore the recall if they wish.
|Re: Unable to Tether after 2.3.6 update||alzakx||9/6/11 12:11 PM|
And like I said, all of them went on vacation for the long weekend, came back to work today and said: Oops! we f*ucked up.
I bet my n*t sack that we will NOT hear from anyone at Google even today.
By the way Sean O'Shea is asking users how received the update to do a interview with him so he can do a follow up and expose the case today on Global Toronto.
Contact him at = 1.800.387,.8001 extension 5467 or email s...@globalnews.ca.
I'm not in Canada but if I were then I would definitely do the interview.
|Re: Unable to Tether after 2.3.6 update||Paul||9/6/11 12:12 PM|
We're looking into this now. Thanks for letting us know you're experiencing this issue.
|Re: Unable to Tether after 2.3.6 update||alzakx||9/6/11 12:15 PM|
Oh sh*t! I lost the bet, hold on let me go get a pair of scissors...
So here we go again... 4 more months, sigh...
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/6/11 12:21 PM|
Yeahhh. It took 4 days.... well...
|Re: Unable to Tether after 2.3.6 update||ArclightX||9/6/11 1:29 PM|
Nexus S GT-I9020A
Canada / English
Android ver. 2.3.6
Baseband ver. I9020AUCKF1
Kernel ver. 18.104.22.168-g21fb4cb
Hardware Build 11.03
Mine's Rooted but I'm still running the stock ROM, for the moment. That's gonna change real real soon if a fix isn't forthcoming, and by forthcoming I don't mean in the next 4 months.
I hate to sound like a broken record from when the v2.3.4 update was met with some difficulties but that event like this one will for force many to live on XDAdevelopers for a few months as I did. Now I can root, load custom ROM's/Skins/Themes/Kernels with the best of them. I'm glad I know this stuff now but frankly being forced to learn that sort of thing out of neccessity rather than by choice is rediculous for a company like Google.
|Re: Unable to Tether after 2.3.6 update||mkslt04||9/6/11 5:17 PM|
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/6/11 5:21 PM|
So Paul, tell me, who's the complete freaking morron at Google that thought it would be a good idea to release an untested update? On a Friday? with not one freaking Google employee to catch the fire? Is Google really so stupid and thoughtless? Don't try and tell me this was tested. If it was then you people employ complete freaking morrons. To me this is the same, if not worse than the Iphone antenna screw up and the morron in charge there got fired for it. I hope to hear about the morron responsible at google for this, getting fired. Short of sabotage, THERE IS NO BLOODY EXCUSE. Do you people have no self respect?
Thanks again for ruining my weekend plans, I'm sure I wasn't alone.
|Re: Unable to Tether after 2.3.6 update||alzakx||9/6/11 5:45 PM|
Here is re follow up by Sean OShea on the issue. Conveniently named "Android Anger".
Thank you Sean for helping us in our fight.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/6/11 5:58 PM|
Thanks alzakx, I'm going to be posting that link to a different blog/forum once a day until they fix the phone.
|Re: Unable to Tether after 2.3.6 update||ArclightX||9/7/11 6:47 AM|
Lol, alzakx you rock. The irony alone is priceless.
|Re: Unable to Tether after 2.3.6 update||mareid||9/8/11 7:11 AM|
I'm losing precious productivity hours to this bug and all you can give me for consolation is a post on a random discussion thread reassuring me that "Paul from Google" is "looking into this"? And that was two days ago! Use a tiny fraction of your billions to pay people to work around the clock until this is fixed and keep us posted with regular updates.
|Re: Unable to Tether after 2.3.6 update||mareid||9/8/11 3:51 PM|
Why the silence, Google? This is not some weird bug that can't be reproduced. You've killed a major part of the Nexus S' functionality with BP explanation. We don't even know if you intend to bring it back! Why can't you update a simple discussion board post? A simple "gosh, we're sorry and we hope to have this fixed in by Friday" would be nice.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/8/11 3:55 PM|
Yea.... Nexus S = Iphone 4 with this "limitation"... Please...
|Re: Unable to Tether after 2.3.6 update||mkslt04||9/8/11 6:56 PM|
The feature should be brought back after the bug is ironed out. From what I understand the update has been halted so it can be ironed out.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/9/11 3:58 AM|
"Why they silence" that's simple, because they can and they have ZERO RESPECT FOR THEIR CUSTOMERS.
|Re: Unable to Tether after 2.3.6 update||mareid||9/9/11 4:35 AM|
It seems to me that Google is in breach of contract every bit as much as a company who sold you a car and then decided to disable the "braking" function without notice and without being willing to tell you if the feature was coming back or when. Do we buy new cars or walk to work while we hope that the brakes will start to work again?
Am I the only one annoyed that this thread is now marked as "answered"?
|Re: Unable to Tether after 2.3.6 update||aritafari||9/9/11 8:38 AM|
How is this answered?
I just wish Google will tell us if the break was intended or just a bad update.
|Re: Unable to Tether after 2.3.6 update||TheCharles||9/9/11 12:18 PM|
I'ts been a week now!!! I've tried to create a new APN with the correct string for APN Type, but no luck here on Koodo; 3G gets disconnected every time.
|Re: Unable to Tether after 2.3.6 update||xG2x||9/9/11 1:27 PM|
The most simple of fixes would be to simply switch to a different ROM running anything but 2.3.6
To do so will require root access to the device.
As for a beginner ROM without bloatware I highly recommend CyanogenMod - very user friendly and updated often.
ROM Manager (searchable in the market) will point you to other compatible ROMs for your device - and then everything is fine.
Rooting your phone will invalidate your warranty - but who needs those?
Sit and play with yourself - I mean APNs, or join the world of power Androids users, root your phone, and make it cook! (In the good way) You'll find updated kernels for overclocking and undervoltinf your processor.
|Re: Unable to Tether after 2.3.6 update||Tom9020||9/9/11 1:49 PM|
I'm happy that that option exists for the Nexus (and many Android phones) but I'm not interested in doing that at this time and I would suggest that most users are the same.
The Nexus is not just a phone for power users. It is also a phone for users who want a straight-forward Google experience. Many of us hoped that, in buying a Nexus rather then the latest and greatest dual-core monster, we could get a reliable, straight-forward and problem free experience (without having to enter Steve's jail).
|Re: Unable to Tether after 2.3.6 update||mareid||9/9/11 3:40 PM|
Aritafari, if Google _intended_ to break our phones, then we would certainly have case for a lawsuit. I have paid Google for a phone that does tethering and I've paid my carrier to allow me to tether. Even if some company asked Google to shut off tethering for non-paying tetherers on their network, it would not give Google the right to shut the feature off for those who have paid for this service. It would be like shutting off the heating elements in all GE stoves, just because some owners of GE stoves haven't paid their electric bills.
I suspect this was an honest mistake on Google's part--after all, the option to tether is still in the OS. What drives me bonkers is that they've broken it buy they have announced no specific plans to either fix it or to compensate people whose livelihood has been affected by the issue. It's the contempt that bothers me. I love Google's products, but their customer service seems to be virtually non-existent.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/10/11 5:44 AM|
I don't think this was on purpose, I think this was careless idiots that don't care about the consiquences of what they do. They don't care because these idiots have bad managers, this is why they feel they can do whatever they want and there won't be any consequences. They're obviously arrogant and that must be coming from that punk Page. Frankly I'm not surprised when half your executive team look like punks that have zero life experience and are clearly out of touch. They don't respect us, they have contempt for us. Not that Apple or MS are any different as far as contempt goes but at least Apple knows how to fake it and not make it so obvious. They do little things like update in a timely manner. Something that seems to be a "we'll get to it when we get to it and if we don't then f the customer, we got their money" kind of thing. Tell me I'm wrong Google or even better, prove me wrong.
|Re: Unable to Tether after 2.3.6 update||Nexus S Rogers||9/10/11 9:28 AM|
First, why is this thread marked as 'answered'..? Paul's 'we're investigating' comment was our freaking answer? I have completely lost all respect for Google since i started using the Nexus S. Every time my friend comes to me (im the geek) looking for an advice for a new handset, i always insist on staying away from Google/Samsung.
That being said. Paul, lets walk through Google's philosophy.
Our philosophyTen things we know to be true
Focus on the user and all else will follow.
It’s best to do one thing really, really well.
Fast is better than slow.
Democracy on the web works.
You don’t need to be at your desk to need an answer.
You can make money without doing evil.
There’s always more information out there.
The need for information crosses all borders.
You can be serious without a suit.
Great just isn’t good enough.
I want to emphasize on 'Focus on the user and all else will follow.', as you (Google) have obviously failed to carry out..
Fix this and stop giving us corporate BS using phrases like 'fix is coming' or 'were investigating'..
|Re: Unable to Tether after 2.3.6 update||Paul3456||9/10/11 10:29 AM|
I have a Canadian model Nexus S purchased on eBay and running on the AT&T network here in Chicago. I put my AT&T sim card in the phone about 5/5 and immediately was notified there was an update to 2.3.4, which I downloaded.
Everything worked fine until about 8/15, when I started having the unprompted search/voice search problem that everyone else is experiencing. The phone is now a disaster.
I have received no 2.3.6 update even after doing the check-in.
Google, please tell me that this issue will be fixed soon and I am not stuck with an expensive paperweight.
|Re: Unable to Tether after 2.3.6 update||pmamt||9/12/11 12:49 PM|
I am also very frustrated with the inability to tether. I am a consultant and need access to the Internet at client meetings. Without the ability to tether hinders my ability to demonstrate things to my clients on the Internet. Please fix this ASAP Google. Thanks!
|Re: Unable to Tether after 2.3.6 update||TheCharles||9/12/11 7:45 PM|
It's been over two weeks now... Installed CyanogenMod (2.3.4), tethering is back, so long Vanilla.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/13/11 3:53 AM|
Unfortunately rooting is risky at best as far as comprimising the security of your phone and until there's a TRUE one click rooting option, it's not an option for most people.
|Re: Unable to Tether after 2.3.6 update||Matridom||9/13/11 4:57 AM|
I fail to see how rooting can cause a security risk, The super user app allows you to maintain control of what apps gain access and what apps don't. With the fact that the bootloader can be unlocked (and relocked) means that you can gain root without using exploits in the operating system. A true "One click" rooting process uses an exploit or security hole in the operating system to gain the appropriate permissions. If a one click app can do it, then so can apps in the market place. If you think that the thought is overblown, read here:
I would prefer not to have loopholes in the security of the operating system and maintain control of what apps gain root rights. This is the main reason I chose to go with a Nexus over any other phone that has a hard locked bootloader.
The security risk that does come with rooting is that a lot of people are "Yes" clickers and see the prompt for root and authorize it, without judging if the app truly needs it. A good example is the "Paradise Island" app that is so popular, they had an update that would cause the phone to request root rights, they then removed it due to the negative feedback. They never did explain why it was needed.
Me however, i want my titanium backup, VooDoo Sound and market enabler.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/13/11 4:42 PM|
@Matridom, I can't speak intelligently about it as I'm frankly too new to android. All I've read is, the only reason you have to worry about android and the security of your phone is if you root. I've never read about being able to control the security with the super user app.
Even if it's not a one click option, something better has to be created. I've jailbroken my old iphone and it wasn't nearly as difficult as the youtube how to's I've see make it seem for the nexus. Admittedly I haven't tried yet. Perhaps a better tutorial has to be created as every one I've seen looks so half a$$ed that it gets confusing and there's always missing info in the tutorials. Heck it took me half a day just to install the drivers as my system refused to see them.
Part of the reason I came to android is so I wouldn't have to jailbreak/root. Now here I am again, having to root in order to get the phone working the way I want.
I don't know how I missed the importance rooting but that's my fault for not researching android better.
|Re: Unable to Tether after 2.3.6 update||Matridom||9/13/11 5:30 PM|
XDA is a wonderful resource for modifying your phone. The following thread will give you all the details to unlock your bootloader, install an alternate recovery and root your phone in easy to follow steps
My favorite reason for rooting is the ability to backup your application data between roms/phones etc. This means that if i switch phones, I don't start from scratch, I started on an HTC desire (temporary phone), then moved to a galaxy S, I then put cyanogenMod on it, now the nexus (both stock and cynogen), my angry birds game has carried over from device to device, rom to rom and will continue to do so.
You can backup your entire ROM through ClockWorkRecovery Mod (i made a backup before applying 2.3.6, it sucked, so i restored). Think of it like the "System restore" you have in windows.
Individual applications can be backed up through Titanium backup.
In regards to superuser, it's a control application that allows you to allow/deny what apps have root access. The Elite version (paid) will even lite you hide the superuser app itself, set a pin code to allow a new application etc. Well worth the cost, even if it's just to support the guy who supports the su binary and codes the superuser app.
I've pretty much settled myself that regardless of what smartphone i go with, I'll be modifying it to suite my needs properly. So if you have to do it, might as well enjoy it, hence why i went with android.
If a patch is not out by the end of the month for the search key and tethering, I'll move back into a galaxy S, then start sending my phone in for repairs. After it's been through 3 or 4 times (late Oct or mid Nov) I'll have enough of a case for my ISP to upgrade me to a new phone, and my understanding is that's right around the time the next generation of nexus is due to be released. (nexus Prime)
On a side note, just to clarify something about rooting; Unlocking the bootloader does NOT root your operating system, you need to install the su binary. What unlocking your bootloader DOES do is allow you to change your rom, this includes rolling back to a previous version (through Clockwork Recovery mod).
|Re: Unable to Tether after 2.3.6 update||alzakx||9/15/11 10:56 AM|
I think someone posted a while back that Samsung and Google were working on a fix for this issue and was supposed to be released in the next 2 weeks. This fix is supposed to once and for all deal with the voice and the newly introduced tether issue. I think their two seeks will be up next tuesday but let cut the a slack and say its next friday.
Still no word from Google other than they are working on it. Guess 4 more months are once again the turn around time for this. Don't hold your breath on Ice Cream Sandwich being released to your NS on october or november. My guess is that maybe sometime during january or february.
|Re: Unable to Tether after 2.3.6 update||Lanhoj||9/15/11 12:18 PM|
Here's what worked for me with a Nexus S from Koodo running stock Android 2.3.6:
1) Settings --> Wireless & Networks -->Mobile Networks --> Access Point Names --> Koodo --> Scroll down to the "APN Type" and replace "default,supl,mms" with "default,dun,mms" --> Save
You'll see your 3G icon go off & on
2) Settings --> Wireless & Networks --> Tethering & Portable Hotspot --> Portable Hotspot [ ] Turn it on
You'll see your 3G icon go off
3) Settings --> Wireless & Networks --> Mobile Networks --> Data Enabled [ ] Turn it off & back on
You'll see your 3G icon go back on
Devices you connect to it will now be able to share your Data.
***Note: You'll have to do steps 2 & 3 each time you want to tether.***
|Re: Unable to Tether after 2.3.6 update||Soloduenos||9/15/11 7:15 PM|
Poco serio todo esto por parte de Google, alguien deberia dar la cara y poder brindar una respuesta profesional a este asunto indicando tiempo de solucion del problema y pidiendo disculpa a los usuarios. GOOGLE un poco de ETICA please.
|Re: Unable to Tether after 2.3.6 update||air4color||9/18/11 3:53 AM|
i won't mention anything hear, but if intrested in more of the tethering issue, i may be able to help get android AP "TEXTPLUS" and text me at 9134164194
|Re: Unable to Tether after 2.3.6 update||air4color||9/18/11 3:56 AM|
TEXTPLUS available for some androids, but definately IPHONE, IPAD, etc..
|Re: Unable to Tether after 2.3.6 update||Tony49122||9/19/11 10:16 PM|
Thanks Lanhoj for posting,Confirming your steps worked for me on a Telus Nexus S in Vancouver BC. My variation using "Telus" in place of "Koodo". That was the only change I made to get wifi hotspot working again.
p.s. What is the difference between "supl" and "dun"? That's not "dial up networking" from the modem days is it?
1) Settings --> Wireless & Networks -->Mobile Networks --> Access Point Names --> Telus --> Scroll down to the "APN Type" and replace "default,supl,mms" with "default,dun,mms" --> Save
Confirmed the 3G icon stayed on and I was able to connect to the Nexus S hotspot with an iPad and watch some YouTube.
Thanks for posting, it saves the day and brings my phone back to full function again.
|Re: Unable to Tether after 2.3.6 update||klakomatic||9/23/11 9:00 AM|
I have tried this on the Bell network and it doesn't work. The 3G appears for a few seconds, then goes away, so hotspotting is still broken. We are on three weeks now and no word from Google. So disappointed. Really hoped Google would be different than the big-company, no-caring service we are used to with the big carriers in Canada.
Google, with this attitube, Facebook and Apple will eat your lunch.
|Re: Unable to Tether after 2.3.6 update||reelfernandes||9/26/11 12:19 PM|
You have to swap supl & dun back & forth everytime you want to use the tethering option....
|Re: Unable to Tether after 2.3.6 update||lawrencetaur||9/26/11 10:29 PM|
Just updated to 2.3.6 on my Nexus S
Tethering works out of the box. Phew! I believe it is carrier based. Not sure why everyone is blaming Google for this.
BUT, i noticed a change, my hotspot name was changed to AndroidAP and it had its own password set.
I tried that, and it worked.
I had issues with EDGE(yes i still dont have 3G) disappearing randomly. Will let you know if it has been fixed!
Issues i noticed with 2.3.4(actually ever since i got my phone):
-SMS bug, typing a recipients name and the cursor moving to the first character. anooyed me so much i installed GoSMS Pro.
|Re: Unable to Tether after 2.3.6 update||Stufyou100||9/27/11 4:06 AM|
@lawrencetaur If you take a moment to READ you would know that the complaints on this forum are from people on various carriers. Tethering was broken with GOOGLE'S update. THAT is why Google IS to blame for this.
|Re: Unable to Tether after 2.3.6 update||Paul||9/27/11 9:43 AM|
We're sending an over-the-air update to address tethering. Thanks again for alerting us to this issue.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/27/11 9:44 AM|
|Re: Unable to Tether after 2.3.6 update||Paul||9/27/11 1:46 PM|
Diegodbm: the OTA has already started.
|Re: Unable to Tether after 2.3.6 update||pongster68||9/27/11 3:06 PM|
Paul ...I have a Nexus One ....I received the 2.3.6 OTA update yesterday (Sept 26 2011) and it just basically screwed up the tethering function ..... devices dont connect to the hotspot anymore ....please ask Google to fix ASAP! thanks!
|Re: Unable to Tether after 2.3.6 update||champdemars||9/27/11 3:34 PM|
Hello, I just got the 2.3.6 ota this morning on my nexus one, too. I was running 2.3.4 before... my tethering does not work anymore, too! Build is grk39f.
Please fix it!
|Re: Unable to Tether after 2.3.6 update||dbg2kidd||9/27/11 11:31 PM|
On Sep27-'11, I too updated from from 2.3.5 to 2.3.6 & was also unable to connect my laptop to the internet via my Nexus S Portable Wi-Fi hotspot tethering & confirmed via online reading that this was a known bug. Today, Sep28-'11, I noticed that the upgrade had reset the "Network SSID" (accessible via Wireless & Network Settings > Tethering & portable hotspot > Portable Wi-Fi hotspot settings > Configure Wi-Fi hotspot).
By simply re-instating my old settings ("Network SSID" & "Password"), I was able to once again connect to the internet. I hope others will find this helpful. -DBG
|Re: Unable to Tether after 2.3.6 update||Eyolf||9/28/11 6:15 AM|
I'm with Telus. I also started having issues with tethering once I received the 2.3.6. Update. I have yet to receive an OTA Update. My tethering will still not work.
Every time I turn my tethering on so that I can broadcast a wireless AP. It turns off my data but my data stays turned on in the settings. When I try and connect my computer it will not have an internet connect.
What the heck Google?!
|Re: Unable to Tether after 2.3.6 update||halbertabeef||9/28/11 9:17 AM|
The post from Lanhoj (above, on Sep 15) provides a workaround that brings back tethering. I've found that sometimes you may have to repeat his step 3 a time or two, or if that still doesn't work, Select a Network Operator, and re-register with your current carrier.
|Re: Unable to Tether after 2.3.6 update||champdemars||9/28/11 9:54 AM|
I also did what dbg2kidd have done, and it worked fine after.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/28/11 10:11 AM|
I'm still waiting for the OTA!!!
|Re: Unable to Tether after 2.3.6 update||pongster68||9/28/11 12:55 PM|
Ok for those with Nexus One ...all you have to do is just reset the password on the tether hotspot and it should work! (I read this on a different forum and tried it myself and yes my tethering is back up and running!)
|Re: Unable to Tether after 2.3.6 update||brouilld||9/28/11 4:23 PM|
I'm with Telus, Quebec, Nexus S with 2.3.6. Solution from Lanhoj (sept 15) worked for me, but using "Telus" instead of "Koodo". Not a definitive solution, but at least it works! Thanks Lanhoj!!!
|Re: Unable to Tether after 2.3.6 update||d.drake||9/29/11 5:49 AM|
After receiving the OTA for 2.3.6 for my Nexus S I can no longer tether as well. I will try some of the solutions mentioned above and see if they work. I am glad I also keep my Nexus 1 on standby and did not update it.
|Re: Unable to Tether after 2.3.6 update||d.drake||9/29/11 8:18 AM|
If any one is still unable to tether with NS: 1. Edit APN Type: default,dunn: 2. Made sure my Wi-fi network matched my device being tethered. (open or secure). Tethering returned.
|Re: Unable to Tether after 2.3.6 update||Tom9020||9/29/11 8:29 AM|
Lots of us are still unable to tether. I have tried most of the solutions here and I get only occasional relief, i.e. finding solutions that work sometimes but not others.
We really need the OTA fix and I hope Google will expedite getting that rolled out.
|Re: Unable to Tether after 2.3.6 update||sdickert||9/29/11 8:37 AM|
Forget tethering - I can not even access 3G anymore.
I bought my phone in the US (SIM from tmobile) and using a Vodafone SIM from the UK. OTA happened last night and have not been able to access 3G in Italy since I landed.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||9/29/11 6:24 PM|
Paul where's the ota?
|Re: Unable to Tether after 2.3.6 update||alexblack456||9/29/11 6:31 PM|
I received a new update yesterday on my Rogers Nexus S, here in Guelph. I'd previously received the first 2.3.6 update, and it caused the phone's data connection to get disabled when wifi-tethering was turned on, and I continued to experience the search button bug in places outside of cities.
It looks like tethering now works again, I haven't used it yet, but the data connection stays active when I enable tethering now. I haven't yet experienced the voice search bug again, but, I also haven't been to the places where I'd experienced it before.
The phone still says 2.3.6, kernel 2.6.35-7-gf563ef, android-build@apa28 #1
Here's hoping the voice search bug stays gone, and that Google got it right this time.
|Re: Unable to Tether after 2.3.6 update||alexblack456||9/29/11 6:32 PM|
Oops, thats kernel 22.214.171.124-gf5f63ef
|Re: Unable to Tether after 2.3.6 update||xajax7||9/30/11 4:34 AM|
Just updated my NS, 2.3.6, kernel 2.6.35-7-gf563ef, android-build@apa28 #1
I tried enable Wifi tether and the 3G connection still working fine.
I enable the USB tether at the same time and the 3G connection still working fine.
|Re: Unable to Tether after 2.3.6 update||SteveColyer||9/30/11 9:20 AM|
I too received the OTA update yesterday, but I'm still having difficulty getting tethering to work.
Nexus S 4G
Android version 2.3.7
Kernel version: 126.96.36.199-gf5f63ef android-build@apa28 #1
Build number: GWK74
By setting the Network SSID to both AndroidAP and a private name and the Security to both Open and WPA2 PSK with a free form password, none of these work. As soon as I start the HotSpot up, the 3G marker comes off my status line in the top margin and I can't access. The 3G marker stays off a while after I shutdown the hotspot, but then comes back on.
Additionally, I can find no way to update an APN on my phone. If I go to Wireless & network setting -> Mobile networks, the only 3 things that are under that section are Data enabled, Data roaming and System select. Nothing else. The commentary under the Mobile networking header says I can change APNs, but there is only those 3 areas. Nothing about APNs.
While the HotSpot is on, I can communicate with the phone from a MacBook. Just neither the phone nor the MacBook can reference anything outside.
My questions are:
1) What Network SSID and Security settings are people using when tethering works?
2) How are people setting the APNs after the OTA, as per d.drake mentioned on page 3 of this problem?
3) What am I missing getting this to work?
Thanx for any help you can provide
|Re: Unable to Tether after 2.3.6 update||chakitca||9/30/11 10:42 AM|
I HATE GOOGLE, I PLEDGE NEVER AGAIN I WILL BUY A GOOGLE PRODUCT, WONT EVEN SUGGEST ANYONE TO GO FOR IT BUT WILL ALWAYS ASK PEOPLE NOT TO BUY A GOOGLE PRODUCT. THE ONLY THING THEY ARE GOOD IN AND WILL BE IS THE EMAIL CLIENT SERVICES AND SEARCH ENGINE. THEY ARE JUST AN SMALL IDIOTIC SEARCH ENGINE THEY ARE IMPOTENT TO PRODUCE A HIGH QUALITY PRODUCT LIKE A IPHONE
|Re: Unable to Tether after 2.3.6 update||chakitca||9/30/11 10:58 AM|
I WONDER WHY GOOGLE DOES NOT REVIEW THE APPS IN THE ANDROID MARKET AS APPLE DOES, THIS WAY THEY KNOW WHICH APP IS NOT GOOD FOR ANDROID AND REJECT OR REMOVE THAT APP FROM MARKET, AS THEY DONT PERFORM THERE DUTY VERY WELL THEY END UP WITH MALWARE APPS, VIRUS APPS AND ANDROID PROBLEMS. I THINK THEY ONLY WANT TO COMPETE WITH APP STORE WITH NUMBERS, APP STORE HAVE MORE THAN 600000 APPS AND ANDROID HAS ONLY 200000 SOMETHING AND FOR NOW THEY JUST WANT TO GROW AS FAST AS POSSIBLE TO COMPETE THE SECURE-IPHONE APPS WITH THERE MALWARE APPS. I HATE GOOGLE AS MUCH AS I LOVED IT BEFORE I BOUGHT A ANDROID BASED PHONE- NESUS S
|Re: Unable to Tether after 2.3.6 update||jirik777||9/30/11 6:33 PM|
Nexus One PASSWORD RESET did the job! Tethering works like a dream again.
|Re: Unable to Tether after 2.3.6 update||Diegodbm||10/1/11 5:26 AM|
With the ota this issue was solved ... thanks Google ....
|Re: Unable to Tether after 2.3.6 update||matherton||10/1/11 12:12 PM|
anyone else with Telus get the OTA yet?
|Re: Unable to Tether after 2.3.6 update||sdickert||10/3/11 2:21 PM|
I found out that the problem that I was having was with Vodafone IT. Once I got back to England, much better.
|Re: Unable to Tether after 2.3.6 update||Eyolf||10/7/11 3:25 AM|
OTA update fixed it. I can tether again with no fix. The point wasn't to fix it myself as referenced to me. I did that with the help of user's in this forum. I thank you for that. The point was for Google not to offer a faulty product. Which they fixed. Thank you.
In regards to the Anti-Google poster. I am certain Apple offers many a similar program in their own store and although I could be mistaken I don't doubt I am correct. It is probably worse with the Android Market. Yes. Though if one takes a look at many well used popular programs that are similar between Android and Apple. You'll notice "spyware" is rampant in such companies such as Facebook as well. And both Apple and Android have a facebook application.
Your privacy is monitored by every one. Google may have allowed an open market, but that does just as much good as it does harm. So don't state Android is bad because it's an open market because you're too ignorant to accept the same spyware exists on Apple. Be semi-intelligent and read the permissions.
|Re: Unable to Tether after 2.3.6 update||Tayeule||10/7/11 8:56 AM|
Still having this problem on fido.
Android version 2.3.6
Build number: GRK39F
I OTA updated last monday (10/03/2011) and it killed my tethering. Anywhere i can manually get a package that will fix this? No OTA updates available atm says the phone.
|Re: Unable to Tether after 2.3.6 update||aritafari||10/7/11 4:02 PM|
I have the phone details as you except that my provider is AT&T.
After updating to 2.3.6, I lost wifi tethering but USB works just fine.
This is what I have done to get it working (similar to suggestions posted in earlier threads but with some modifications)
1. I set the APN type to blank (don't know if or how this affects MMS since I don't do MMS), but I noticed in Android2.3.4 it was blank.
A. When I want to tether I turn on Portable Wi-Fi Hotspot, as soon as it is on, I turn it off
B. I turn Mobile Data off, then turn it back on
C. Lastly, I turn Wifi Hotspot on
It has worked each and every time (I wait about 5 - 10 seconds before turning back on.
Additionally, I have made a widget with the Tasker app (to automate the above. Easier and quicker than going through the steps above. Tasker is in my considered opinion a must have for all Android users.
|Re: Unable to Tether after 2.3.6 update||Zeitgeist Leitmotiv||10/9/11 5:51 PM|
DEFINITIVE ANSWER to my question would be more than welcome: will the update from 2.3.4 to 2.3.6 harm my Wifi Tethering or not? (Koodo Quebec, Canada)
|Re: Unable to Tether after 2.3.6 update||HelloAndroid||10/11/11 7:26 AM|
My Nexus S Singapore Singtel
also updated to 2.3.6 in recent days.
My top bar show "G" instead of "3G" and the internet browsing speed is slow down, I just realize in this 2 days, maybe this update is a actual downgrade.
Even I restored APN, but still "G" only. "3G" didn't return back.
|Re: Unable to Tether after 2.3.6 update||cojod||11/15/11 7:57 PM|
No problem on Mobilicity network. It must be Rogers
|Re: Unable to Tether after 2.3.6 update||playnasc||12/4/11 5:04 PM|
Won't work either.
help i cant find the Apn
|Re: Unable to Tether after 2.3.6 update||LucaCasagrande||3/16/12 3:53 AM|
Vodafone - IT