Mobile hotspot/tethering?

[peashooter14]

December 10th, the day someone somewhere said they would have LTE provisioned and VVM. Online with Chat support now. Any side bets?

 

[peashooter14]

Chat told me to try this document to set the APN>

https://forums.windowscentral.com/e...rce%3Dredirect%26refer%3Dmycsp&token=9H0JhQhE

 

[TechAbstract]

Mine is working fine. Tried it out today.

How is yours working and not for everyone else? Do you have the Lumia 950 XL Dual Sim? Which plan on AT&T?

 

[GSOgymrat]

I have the dual sim Lumia 950 XL with AT&T and I am typing this on a Nook tablet connected to my phone. Bluetooth is on on both the phone and the tablet but they are connected with WiFi. I've used the Hotspot about four times and have have not had any issues.

 

[Babs75]

How is yours working and not for everyone else? Do you have the Lumia 950 XL Dual Sim? Which plan on AT&T?

Yep, Lumia 950XL Dual Sim. I am on unlimited talk, text, 10gb data with tethering from AT&T. Works just like it always did on my Android phone. My laptop is connected to it right now.

 

[TechAbstract]

Yep, Lumia 950XL Dual Sim. I am on unlimited talk, text, 10gb data with tethering from AT&T. Works just like it always did on my Android phone. My laptop is connected to it right now.

Maybe just the GoPhone plan that isn't compatible. I don't want to be under contract.

 

[Sunstorming]

Wrong. AT&T has no tethering problems, in fact it says right in the details for GoPhone that tethering will work. The problem is, of course, Microsoft and their $650+ entry into their high end beta handset market.

 

[Mark Morales]

Wrong. AT&T has no tethering problems, in fact it says right in the details for GoPhone that tethering will work.

True it says the GoPhone plan supports tethering on the AT&T website but it seems that those 950XL users with a GoPhone plan can't get it to work while those 950XL users with a non prepaid AT&T plan can. That would indicate that it is a problem with AT&T's system (provisioning?) as opposed to the 950XL hardware/ software since it works fine for the AT&T non prepaid plans and all the other carriers... The problem is only the GoPhone plans.

 

[TechAbstract]

I am on T-mobile prepaid Simple Choice plan now. Mobile hotspot works just fine. Windows 10 mobile automatically detected T-Mobile APN. Didn't have to add it in manually.

 

[snakebitten]

AT&T corporate SIM in slot 1 = Hot Spot LTE
AT&T Corporate SIM in slot 1- Panamanian Claro SIM in slot 2 (set to data) = HotSpot LTE
AT&T Family Plan SIM in slot 1 = Hot Spot LTE

But,
AT&T Corporate SIM slot 1 - AT&T Family plan SIM slot 2 (set to data) = Hotspot struggles and drops to 4G and loses DNS
Requires a reboot to get it working again, but doesn't stay consistant

Dual SIM has a lot going on under the hood that the user can't see. With just one AT&T Sim on board it gets stable LTE, stable Hotspot, and faster data speeds.
Not a heartbreak for me since I have lots of devices and SIMs for Hotspotting with. But my dream machine would be the Dual Sim working perfectly with any SIM config I choose. LTE stability and solid Hotspot.

Love the 950XL though. No way am I giving it back.

 

[Dlothenb]

What build of WM 10 are you on? I also have the dual sim 950 XL with AT&T and the mobile hotspot does not work. It worked when I originally got it with build 10586.00 but stopped working when the phone was upgraded to .29. It now has the latest firmware version but is still on build .29 and the mobile hotspot still doesn't work. I've tried everything.

 

[Bill Berry]

I'm not sure if this is the correct thread to post on, but I have the Verizon variant HTC One M8 for Windows using a Straight Talk (Verizon) SIM Card. Prior to upgrading to Windows 10 Mobile...currently 10586.420, when I had Windows Phone 8.1 installed on the device I had no trouble using the Tether-X Pro app and the proxy setup on my laptop. Since upgrading to Windows 10 Mobile TP builds I have had no success in making this setup work. Is there something I'm missing or another way to set this up; thank you?

 

[PGrey]

I'm not sure if this is the correct thread to post on, but I have the Verizon variant HTC One M8 for Windows using a Straight Talk (Verizon) SIM Card. Prior to upgrading to Windows 10 Mobile...currently 10586.420, when I had Windows Phone 8.1 installed on the device I had no trouble using the Tether-X Pro app and the proxy setup on my laptop. Since upgrading to Windows 10 Mobile TP builds I have had no success in making this setup work. Is there something I'm missing or another way to set this up; thank you?

I think you want to start a new thread (maybe a moderator will move it for you), since this is a non-native hotspot/tethering issue, and all the discussion so far was surrounding issues with the native one. This is for your issue with "Tether-X Pro".
My wife's got an M8 running 420, as of yesterday, I'll try the (native) hotspot on hers, tonight. If you can't get the native one to work, ping me, or add to this thread, since it's about the native app, and I'll let you know what I found out on our M8.

 

[Bill Berry]

I don't believe if I use a T-Mobile or AT&T Sim card this will make any difference; it's a Verizon variant M8W. If I use their branded Sim, it all works, no problem. I've successfully done this with WP8.1, but to no avail with W10M 10586 builds, but I'll repost this as a new...I appreciate what you're doing though; thank you!

 

[PGrey]

I don't believe if I use a T-Mobile or AT&T Sim card this will make any difference; it's a Verizon variant M8W. If I use their branded Sim, it all works, no problem. I've successfully done this with WP8.1, but to no avail with W10M 10586 builds, but I'll repost this as a new...I appreciate what you're doing though; thank you!

Either way, I finally remembered to test this (W10m HTC M8 tethering), this evening. It worked fine. In fact I'm sending this reply tethered to the phone, from my desktop. This is on AT&T, prepaid.

Earlier in this thread, someone was having a problem with the "Bluetooth can enable hotspot automatically" function, but that's probably not relative to your issue, and probably long fixed.