[Q] T-Mobile Tethering Verification - X 2014 Q&A, Help & Troubleshooting

When turning on tethering though the system (not a separate app), I'm seeing a message along the lines of 'Verifying subscription with T-Mobile servers'. I never saw any message like this on my 2013 Moto X. Tethering still activates, but I'm worried about this causing any issues later.
Is anybody else seeing this? Any issues?
I'm on the $30/mo plan with a Moto Maker pure edition.

I see the same thing. It's normal.

My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.

nishmaster2k said:
My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.
Click to expand...
Click to collapse
I had that warning once. A restart fixed it. It was odd because I decided to call in to tech support first, then while on the phone I restarted my X and it started working again, hah.

nishmaster2k said:
My 2014 X on T-Mobile eventually stopped going past the "Verifying Account" stage. It now notifies me that I do not have T-Mobile Mobile Hotspot on my plan, and thus cannot use WiFi tethering.
I switched to PdaNet and Bluetooth instead, which is working fine.
Edit: This is a Pure Edition phone.
Click to expand...
Click to collapse
That's disturbing. I was thinking of getting this phone, but I don't want to give up tethering. I'm assuming a custom ROM (Cyanogen, etc.) would solve the problem?
Have you tried to see if this also makes USB tethering stop working?

Might be plan dependent

Does your plan include tethering?
Sent from my Nexus 7 using XDA Free mobile app

I thought all T-mobile plans supported tethering up to the LTE data limit per month?

Note10.1Dude said:
I thought all T-mobile plans supported tethering up to the LTE data limit per month?
Click to expand...
Click to collapse
I think all the new simple choice ones do.
I'm still using my Pure on Tmo, and tethering still works.

I thought if you had a stock rom or something like Cyanogen, they couldn't really block (or detect) tethering, regardless of plan, carrier, etc. Is that incorrect?

Yeah, the plan includes tethering. I've check my usage and I now see it split between "data" and "mobile hotspot usage" (see attached screenshot). On my 2013 moto x I've never seen the hotspot usage and any data used while tethering just fell under the "data" label - same as any other data on my line. I read something (forget where) about there being a change in 4.4.4 (for 2013 moto x) which tags data used by the hotspot as such. I assume this is how t-mobile can tell the difference.

techie91 said:
Yeah, the plan includes tethering. I've check my usage and I now see it split between "data" and "mobile hotspot usage" (see attached screenshot). On my 2013 moto x I've never seen the hotspot usage and any data used while tethering just fell under the "data" label - same as any other data on my line. I read something (forget where) about there being a change in 4.4.4 (for 2013 moto x) which tags data used by the hotspot as such. I assume this is how t-mobile can tell the difference.
Click to expand...
Click to collapse
I hate stuff like that. Carriers and manufacturers shouldn't be able to control and monitor how people use their devices so much. This does make me hesitate about the Moto X. I'm used to Nexus devices where I have a lot more control over things like this, even if it requires a custom ROM.

I agree. It really has me rethinking my decision to hold on to the x. Might move to the nexus when it releases.

Yeah, I'm feeling torn. The 2nd Gen. Moto X is about as close as anything has gotten to what I'm looking for in terms of hardware (if it only had OIS). And of course it is a near stock experience that can be modified with xposed to have features found in custom ROMs. But for the under the hood, keeping the user in control, and privacy stuff, I just trust Cyanogen and other ROMs more. And yet if the 1st Gen. Moto X is any indication, custom ROMs will break some of the unique features on the Moto X, like active notifications and always listening voice controls. On the other hand, if the next Nexus really has a 6" display, I just don't know if I want an enormous phablet. So it's a hard choice.

I had this trouble as well on the prepaid unlimited data plan. I should be entitled to 2 1/2 GB of tethering. I tried three or four times and restarted the phone and it eventually went through with no extra tinkering on my part. Good luck!

After a week of not having tethering, I tried a few things and got it working! I don't have tethering on my T-Mobile plan, and every time I tried to enable wireless tether in the settings menu, I got the T-Mobile verification failed. But that's all good, now.
So here's what I did:
1) Unlock Bootloader, Custom Recovery, Root (Basically, just get root access on your phone)
2) Download the Xposed Module "Xtether" and activate it. This gets rid of the verification message, but tethering still didn't work, it just got the wifi tether to turn on.
3) Download SQlite Editor from the app store
4) Go to Settings Storage (the one that has "com.android.providers.settings" at the bottom > settings.db > global
5) Add "tether_dun_required" with a value of "0"
6) Go to your APN settings. Create a new APN entry, and set it up the same as your fast.t-mobile.com one, except use IPV4 (IPV6 will not work)
7) Reboot, and you're good!
Wrote this hastily, so if you need clearer instructions, just ask!

Thanks for the explanation Moose8106.
So am I correct in understanding that the tethering function built into AOSP Android (and normally available on Nexus devices) is deliberately modified in the stock Moto X ROM to allow carriers to scrutinize (and possibly limit) how you are using your mobile bandwidth?

2104
cb474 said:
Thanks for the explanation Moose8106.
So am I correct in understanding that the tethering function built into AOSP Android (and normally available on Nexus devices) is deliberately modified in the stock Moto X ROM to allow carriers to scrutinize (and possibly limit) how you are using your mobile bandwidth?
Click to expand...
Click to collapse
I don't think it's deliberately modified for the Moto X ROM. I believe it's a restriction of AOSP Android: danielpocock.com/android-betrays-tethering-data
Tethering worked fine on my Galaxy Nexus and when I upgraded to the Moto X 2014 Pure I thought Motorola had applied this tethering restriction but further investigation led me to believe that even the Nexus devices have this issue.

aaronbc said:
I don't think it's deliberately modified for the Moto X ROM. I believe it's a restriction of AOSP Android: danielpocock.com/android-betrays-tethering-data
Tethering worked fine on my Galaxy Nexus and when I upgraded to the Moto X 2014 Pure I thought Motorola had applied this tethering restriction but further investigation led me to believe that even the Nexus devices have this issue.
Click to expand...
Click to collapse
Hmm, I've never had an issue on my Nexus One or my current Nexus 4 (though I'm still--lamely--using Jelly Bean, maybe KitKat introduces a problem). Well, accept that I find I have to change the DNS servers to OpenDNS on my laptop or otherwise I have problems connecting when I tether over USB.

cb474 said:
Hmm, I've never had an issue on my Nexus One or my current Nexus 4 (though I'm still--lamely--using Jelly Bean, maybe KitKat introduces a problem). Well, accept that I find I have to change the DNS servers to OpenDNS on my laptop or otherwise I have problems connecting when I tether over USB.
Click to expand...
Click to collapse
I believe this feature came on an update. It might have been 4.4.4. On Nexus 5, if you didn't want reporting tethering to the carrier you needed to modify the "tether_dun_required" line to 0. This being a Google Play purchased Nexus 5. Here's more info in the Nexus 5 forums.
http://forum.xda-developers.com/google-nexus-5/general/fix-nexus-5-tethering-block-t2581035
So, nothing to do with Moto X itself. I haven't tried it yet but yea, this method should also work on the the Moto X.

Related

[Q] Tethering after JB update (iptables help?)

Hello All,
My tethering hasn't worked since the upgrade, regardless of root, method or hack. It appears to set up the network fine and the laptop connects, but I can't pull up a site and troubleshooting points to DNS errors.
So it seems (after loads of research) that this is a known issue... But it's not an issue so much as a "feature" for our carriers: Apparently Jelly Bean allows Carriers to recognize and block tethering. That's why some folks lose tethering, and some don't. The "issue" is a switch that was enabled at the carrier's end.
For those of you who know that you are supposed to be able to tether per your agreement, the solution should be as easy as calling your provider and having them enable tethering.
For those (like me) who have been sneaking in the back door and wish to continue to do so, the fix seems to lie in iptables (root required). The simplest version I found was entering this in terminal:
Code:
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
...where "rmnet0" is replaced with the interface specific to your device. Apparently after this, one should be able to tether normally.
(Reference Android Google Code reported issue 38563, see comments 122, 125 & 131. Sorry... too noob to be able to post links)
Unfortunately this didn't work for me, but more than likely because I haven't a clue what I'm dabbling in. I sought out my "interface" by running "netcfg" in terminal with tethering disabled, and chose qmi0 (the one with a xx.xxx.xx.xx format IP address, the same as shows for the phone when it's successfully online). Does anyone know enough to see my mistake, or otherwise be able to help me with this?
Thanks in advance!
Actually FoxFi released an update that supports usb tethering and wifi hotspot for the Droid 4. No root required.
You have to uninstall earlier versions of FoxFi and it's certainly worth it to get the paid version!
You do have to establish a password/pattern unlock for your phone which I find slightly annoying, but that's the workaround FoxFi found to make it work under JB and certainly worth the minor inconvenience.
Works great! I am writing this from my tablet tethered through hotspot to my Droid 4.
I had a custom rom installed because I need the wifi hotspot, but now I can thankfully go back to the (extensively TiBu cleaned) stock rom since the CM roms all have unacceptable bugs and/or instabilities IMHO.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks for your response berndblb... I must admit, you got my hopes up!
Alas, it seems my problem runs deeper than FoxFi's solution. I downloaded, installed and gave it a shot, but basically got the same stuff I'd acco mplished already with root: I can build a network, I can connect to it (really adds to the optimism), but I can't reach the DNS server. No joy. My guess is that FoxFi still only manages to bypass Verizon's block, but not the switch that's the problem inherent to JB.
And so I maintain my hope to find a resolution via iptables as described here https://code.google.com/p/android/issues/detail?id=38563.
Help?
Strange, I can tether just fine on my Droid 4 (Verizon) with unlimited data using the SQL database edit and the stock Mobile Hotspot app.
I'm not supposed to have tethering but just browsed the web on my tablet tethered to my Droid 4 with no issues.
Who is your carrier? Every other Verizon Droid 4 owner who has done the SQL edit has been able to tether....
tcrews said:
Strange, I can tether just fine on my Droid 4 (Verizon) with unlimited data using the SQL database edit and the stock Mobile Hotspot app.
I'm not supposed to have tethering but just browsed the web on my tablet tethered to my Droid 4 with no issues.
Who is your carrier? Every other Verizon Droid 4 owner who has done the SQL edit has been able to tether....
Click to expand...
Click to collapse
Thanks for your response.
I'm with Rogers here in Canada (AT&T's counterpart). Agreed about the SQL database edit having been the trick. That's all it took to get me rolling in ICS with the stock hotspot app. When I upgraded to JB, I removed the entitlement check in the SQL database and thought I was set... but no joy. Everything looks good right up until I try to pull up a website. That's when I realize I'm not getting to the DNS Server, and therefore unable to surf. I know nothing's changed on Rogers' end, because I can still tether if I drop my SIM back in my old D2G.
My research led me here: https://code.google.com/p/android/issues/detail?id=38563#c122. Previous comments explain that tethering is now blockable at the carrier's end (what Verizon was attempting to add with their "entitlement check"). Comment 122 narrows down the source of this block as IP address related, and suggests a fix that worked for him. To quote:
I'm not sure exactly what it means for the device to "properly flag when data is for tethering purposes" (comment #105). My own observation was that the outbound data on the 'rmnet0' interface wasn't being NATted. The phone's IP address on that device was (for example) 10.182.48.29 and all its *own* data was coming from that address. And responses from the Internet were coming back just fine.
The phone assigns IP ranges in the 192.168.0.0/16 range to its clients on the USB and wifi tethering. And those 192.168.x.x addresses were being seen on the outbound rmnet0 interface unmolested. Perhaps that's how we're *supposed* to indicate that it's tethered data, and we let the carrier perform NAT for us at their end?
Either way, running this command seems to have 'fixed' it for me, and with my Samsung Galaxy S3 on Orange UK I now get functional tethering again:
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
Obviously there's nothing preventing your carrier from assigning addresses in the 192.168.0.0/16 range to the device itself, and I have no idea what the various rmnet[012] devices are, so this isn't a "fix" for the general case but most people with a rooted phone should be able to work it out from here...
Click to expand...
Click to collapse
Assuming I'm on the right track (symptoms are the same), I'm looking to figure out how to adapt this to work for me. Unfortunately messing with iptables is well over my head. Sigh...
Yeah i had the same problem FoxFi Worked for me as well
this will forcefully allow tethering no matter what...
If this is over your head, do NOT do it! You can permanently brick your phone!!!
http://forum.xda-developers.com/showpost.php?p=15931904&postcount=1
This goes to the hardware level and mods things to make it look just like your phone is pulling the data not tethering.
Technically this will work on any and every motorola phone
je2854 said:
this will forcefully allow tethering no matter what...
If this is over your head, do NOT do it! You can permanently brick your phone!!!
http://forum.xda-developers.com/showpost.php?p=15931904&postcount=1
This goes to the hardware level and mods things to make it look just like your phone is pulling the data not tethering.
Technically this will work on any and every motorola phone
Click to expand...
Click to collapse
Thanks for your recommendation je2854.
Good news: successfully made the changes, and phone is not bricked.
Bad news: same trouble as before. I can create a network and connect to it, but can't get a DNS server (for either USB tether or WiFi Hotspot).
Really frustrated here. I've reverted to a trashy LG L7 as my primary phone. Slow and no hardware kb, but at least it works. Sigh... Droid 4 going back in the drawer until someone figures out how to rewind to ICS.
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
cellzealot said:
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
Click to expand...
Click to collapse
speaking of flashing... I have purchase one of your OTG adapters.... b-e-a-utiful work you have there!
works amazing! even on the HP TouchPad! (it charges faster like it should)
Also you are correct, I used to have a D3 and that hack works well...
could you kinda point me in the right direction of the SQLite hack? I have that and would like to try it...
(Although I already have tethering enabled via family share)
WaHoo!! Consider yourself kissed!
I'm typing from my tethered laptop. Not sure what did the trick, as I've tried WiFi Tether before with no joy.
I did flash the 18_2 JB, though, and tried the WiFi Tether settings you recommended. Up and running. And grinning.
THANKYOUTHANKYOUTHANKYOU for bringing my Droid4 back out of the drawer it was banished to a couple months ago!
cellzealot said:
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
Click to expand...
Click to collapse
Yay!! Congrats! Glad to help out...D4 is still a great device and for better or worse it is still "best in class" of all the hardware qwerty keyboard phones.
Good luck!
none of above work for me.
verizon build # 9.8.20-72_vzw-18(debloated with script)
entitlement check edit works and keeps thru reboot
sqlite editor (install in play store)
goto:
settings storage: (hammer and wrench icon. says "com.Motorola.Android.providers.settings" below it)
settings:
66 entitlement_check:
long press over the 1, change to 0 and click save
exit and reboot
native hotspot works

[Q] VZW Moto X as Hotspot

So I am strongly considering the Moto X not that Verizon has Moto Maker and the 32GB verizon. The one thing I love on my current phone running CM10.2 is the ability to tether my laptop to it for internet access without getting charged extra by verizon while I travel. Usually in a monthly billing cycle when traveling with work I'll consume about 20GBs of data. Can I do this with the Moto X without getting charged tether fees? Do I need to root it to do this?
FYI: I'm i'm on an unlimited plan
If you root with RockMyMoto, yes..
For using Wifi Tether for Root app, see -> http://forum.xda-developers.com/showthread.php?t=2449534 You MUST use the specific version now linked in the first post, or it wont work.... In other words, do NOT get the version from the Play store. (I'm using this way with my Rooted X, also unlimited plan)
To use the built in tethering app see -> http://forum.xda-developers.com/showthread.php?t=2443562 (I haven't tried it, but there are many reports in that thread of it working).
If you don't want to root, then you could try Foxfi. Not sure if it works, I've never used it.
I have always used THIS, on multiple phones. I'm on the 3.3 beta 2 and it works fine. Go into settings, and make sure the device profile is Generic ICS/JB (wlan0), and check the WiFi driver reload, MSS clamping, and Routing fix options.
gokart2 said:
I have always used THIS, on multiple phones. I'm on the 3.3 beta 2 and it works fine. Go into settings, and make sure the device profile is Generic ICS/JB (wlan0), and check the WiFi driver reload, MSS clamping, and Routing fix options.
Click to expand...
Click to collapse
For some reason I couldn't get that version to work on my Verizon X. While the PC and tablet saw the X, it saw it as WLAN0, and never properly connected to the phone.
The thread I linked to has a patched version that works properly for me, including seeing the "hot spot" as the SSID I set on the phone, and letting the PC and tablet connect to the phone and get to the internet.
The x is awesome for one. All u gotta do is root and follow the thread to use built In tethering appreciate. Works great. Or better yet flash Nitro's eclipse ROM. Its all done and its a great rom
Sent from my XT1060 using xda app-developers app
KidJoe said:
For some reason I couldn't get that version to work on my Verizon X. While the PC and tablet saw the X, it saw it as WLAN0, and never properly connected to the phone.
The thread I linked to has a patched version that works properly for me, including seeing the "hot spot" as the SSID I set on the phone, and letting the PC and tablet connect to the phone and get to the internet.
Click to expand...
Click to collapse
I did notice the wlan0 where on the other device I had u could change it or use the ssid, but my tab and others will connect? The initial connection always funks up, usually just have to cycle WiFi from the device and cycle tether too. U try reboot, fix perms, and cache/dalvik wipes? Haven't tried modifying that system apk, heard about some issues and this never gives much, if any.
gokart2 said:
I did notice the wlan0 where on the other device I had u could change it or use the ssid, but my tab and others will connect? The initial connection always funks up, usually just have to cycle WiFi from the device and cycle tether too. U try reboot, fix perms, and cache/dalvik wipes? Haven't tried modifying that system apk, heard about some issues and this never gives much, if any.
Click to expand...
Click to collapse
I tried everything. Yes.
I liked the way wifi tether worked on my past phones. Using the patched copy found in this thread -> http://forum.xda-developers.com/showthread.php?t=2449534 , which is also needed for the GNex w/4.2, works just like it did on my Bionic, Thunderbolt, and other past phones. No issues. After initial config and allowing SU, just launch the app, tap to start tethering, go to my PC, Tablets, etc.. and connect and go.
The APK is originally from https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c109 however, I just noticed lower down in that discussion a patch was added to the experimental 3.4 ( https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c197 ) so I might try that.
I don't feel the need to mess with those system files to use the phone's built in tethering app. I don't have to. I only offered that because some were using it since Wifi Tether for Root wasn't working.
KidJoe said:
I tried everything. Yes.
I liked the way wifi tether worked on my past phones. Using the patched copy found in this thread -> http://forum.xda-developers.com/showthread.php?t=2449534 , which is also needed for the GNex w/4.2, works just like it did on my Bionic, Thunderbolt, and other past phones. No issues. After initial config and allowing SU, just launch the app, tap to start tethering, go to my PC, Tablets, etc.. and connect and go.
The APK is originally from https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c109 however, I just noticed lower down in that discussion a patch was added to the experimental 3.4 ( https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c197 ) so I might try that.
I don't feel the need to mess with those system files to use the phone's built in tethering app. I don't have to. I only offered that because some were using it since Wifi Tether for Root wasn't working.
Click to expand...
Click to collapse
editig one cell in the system settings to get the built-in hotspot app to work is hardly messing with the system files. i've done this on my last three phones and they've all worked flawlessly. plus the built-in app has decent security features.
640k said:
editig one cell in the system settings to get the built-in hotspot app to work is hardly messing with the system files. i've done this on my last three phones and they've all worked flawlessly. plus the built-in app has decent security features.
Click to expand...
Click to collapse
I know you read the one thread I posted a link to as you asked about doing the SQL edit, and posted a screen shot from your D4.. Its OP talks about replacing a bunch of APK files which are system files...
In Post #24 of that thread, thepolishguy the SQL tweak doesn't work.
... hence my saying I didn't want to mess with a bunch of system files.
Not to mention, side loading an APK and using it is easier. It might not be "cleaner" or seem as "integrated" but it works.
Awesome thanks everyone. I defintely plan on rooting my phone and installed xposed.

[Q] Native tether connects, but no data

I'm having connectivity issues with the wifi hot spot. I have a Moto X Developer Edition on Verizon with a grandfathered unlimited plan. I unlocked the bootloader and rooted. I ran the commands in this thread to load a new entitlement check apk, and everything looks like it's working. "Checking subscription status..." pops up briefly on load and then goes away. An access point is created and I can successfully connect to it with another device (Nexus 7). So far, everything looks exactly as it should.
The problem is there is no data. I can access data from the phone itself just fine, so I have a cellular data connection. If I disconnect the Nexus 7 and connect to the local wifi network, it gets data just fine, so the device itself is fine. When I try to hit any web page while connected to the Moto X's hotspot, I get the standard "This web page is not available." Trying to ping something from a terminal loses all packets.
It's acting as if the networks aren't bridged/routed properly on the phone. How do I go about troubleshooting this? Are there log files somewhere I can look at?
edit: I should also note that android-wifi-tether, which I used on my rooted HTC Thunderbolt previously, acts like it works fine, but there is no wifi access point broadcast/visible. I have no idea if the problems are related.
I have had a similar problem on my unrooted Moto X. Could use the tether and connect however no data could be transmitted and no web pages could be loaded.
To solve it all I did was go to settings and retype in my APN. I am on Koodo mobile with an unlocked Rogers Moto X so this solution might not work with you but it's just something I thought I could suggest. Hopefully this works! Best of luck.
Sent from my XT1058 using xda app-developers app
Unfortunately, it doesn't do anything for me. Did you have data on the phone directly before that? I thought the APN would affect all data, not just tethering.
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
and it works fine. Sometimes its a little slower (like 20-30 seconds) to hit "start" until my laptop or ipad will see the hot spot, but it always works.
KidJoe said:
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
and it works fine. Sometimes its a little slower (like 20-30 seconds) to hit "start" until my laptop or ipad will see the hot spot, but it always works.
Click to expand...
Click to collapse
Strange. I had tried that version of that app before, following some youtube video, same settings as you listed, but setting the device profile to generic ICS/JB (wlan0) and I could never see an access point created. Now when I go back and do it, the access point pops up fine. I can connect and get data.
It's a little quirky/buggy in that the AP name is always "wlan0" and changing the SSID doesn't change that. Also, I enabled encryption in the settings, but the connection remains open and unencrypted. That may just be part of the beta nature of the version of the apk. I used the non-beta release version in the Play Store on my HTC Thunderbolt and all that worked fine.
So it's functional if not ideal. I'll keep poking at it and will see if I can make sense out of the behavior I'm seeing. I'll post back if I learn anything.
icrf said:
Strange. I had tried that version of that app before, following some youtube video, same settings as you listed, but setting the device profile to generic ICS/JB (wlan0) and I could never see an access point created. Now when I go back and do it, the access point pops up fine. I can connect and get data.
It's a little quirky/buggy in that the AP name is always "wlan0" and changing the SSID doesn't change that. Also, I enabled encryption in the settings, but the connection remains open and unencrypted. That may just be part of the beta nature of the version of the apk. I used the non-beta release version in the Play Store on my HTC Thunderbolt and all that worked fine.
So it's functional if not ideal. I'll keep poking at it and will see if I can make sense out of the behavior I'm seeing. I'll post back if I learn anything.
Click to expand...
Click to collapse
The version apk and settings I listed allow me to change the ssid and use encryption. In fact using that got it working on my X like it did on my thunderbolt.
KidJoe said:
The version apk and settings I listed allow me to change the ssid and use encryption. In fact using that got it working on my X like it did on my thunderbolt.
Click to expand...
Click to collapse
Something didn't turn off properly. Attached is the battery graph while it was plugged into my computer (an admittedly low current charging source). I saw my phone reboot just before I had to leave, cursed it for being too early for random reboots (the TB did a lot of that). Turns out tethering draws significantly more than 500 mA, killed the phone, which turned off, then recharged to 3% and rebooted, and that's what I saw.
Whatever that application does doesn't get logged by the Android battery monitor, as it was definitely the primary drain, but doesn't show up in battery settings. I don't think it did on my TB, either. It also didn't log data usage on the TB (haven't used enough on the X to tell yet). Seems like that application lives in a pocket outside what Android itself is set up to log. Is that a factor of most root applications?
icrf said:
Something didn't turn off properly. Attached is the battery graph while it was plugged into my computer (an admittedly low current charging source). I saw my phone reboot just before I had to leave, cursed it for being too early for random reboots (the TB did a lot of that). Turns out tethering draws significantly more than 500 mA, killed the phone, which turned off, then recharged to 3% and rebooted, and that's what I saw.
Whatever that application does doesn't get logged by the Android battery monitor, as it was definitely the primary drain, but doesn't show up in battery settings. I don't think it did on my TB, either. It also didn't log data usage on the TB (haven't used enough on the X to tell yet). Seems like that application lives in a pocket outside what Android itself is set up to log. Is that a factor of most root applications?
Click to expand...
Click to collapse
I don't see that problem. When I use it, I just get regular draw as if I'm viewing a movie on my phone via Netflix. Stopping and exiting the wifi tether app does seem to exit it and end battery draw.
I'm using stock 4.4 on my VZW Dev X. I rooted via unlocking the booloader, installing TWRP, booting to TWRP and installing/flashing SuperSU.
Other option is grab the APK in this thread -> http://forum.xda-developers.com/showthread.php?t=2449534&page=2 and use it. And actually, that thread has you also check wifi-driver reload 2.

[Q] Switch from htc arrive wp7 to Samsung Ativ wp8

Gotta switch but, I was wondering if 2 things are available in wp8 for sprint. 1- Is there any restriction for downloads and is there free Internet sharing. I realize this question is redundant but I keep getting different answers.
I can't speak for Sprint specifically, but in general...
The restrictions for downloads (I assume you mean things like "apps over 20MB must be downloaded over WiFi" or some such thing) should be the same as on WP7. In theory it's possible for us to override those restrictions, although I don't think anybody has yet written an app to do it.
The built-in "Internet Sharing" feature works exactly like it does on WP7. If your Arrive is allowed to do it, your Ativ S Neo will be too.
thanks
Let me explain. Sprint charges for WiFi hot spot usage. With Leads rom on my arrive I am able to use internet sharing for free. I guess my main concern about a switch is whether I can do this still for free. Thanks
If you don't see anything here, its because it hasn't been found yet. I'm trying to find the same for Verizon, but LTE has made a mess of things. The Android gurus won't help either...
I hope a internet sharing/hotspot solution is available for Sprint.
I'm eligible for upgrade March 1st, and was going to get the Ativ S Neo just for a change of pace. Been using Android for 3 or 4 years now, the last windows phone I had was a Touch Pro 2.
Not a deal breaker, but I do use hotspot fairly regularly to get around works firewall...
Some people are experimenting with partially-customized ROMs for the Ativ S (no idea if they've gotten to the Neo yet; it's relatively new). Those *might* support the kinds of changes needed for free tethering.
Alternatively, you may be able to use wired tethering for free via the Diagnosis app. I can (my plan includes tethering at no extra cost, but it is capped; when I use wired tethering it doesn't report any tethered data usage).
GoodDayToDie said:
Some people are experimenting with partially-customized ROMs for the Ativ S (no idea if they've gotten to the Neo yet; it's relatively new). Those *might* support the kinds of changes needed for free tethering.
Alternatively, you may be able to use wired tethering for free via the Diagnosis app. I can (my plan includes tethering at no extra cost, but it is capped; when I use wired tethering it doesn't report any tethered data usage).
Click to expand...
Click to collapse
CDMA Tethering has changed these days. They have built in "entitlement checks" to see if your eligible for tethering. I went to one of the Verizon device threads and asked but no luck.
The device username is the only thing listed. On another note, Verizon's USB modems seem to talk directly through a Networking Adapter instead of a normal modem. Their VZManager might need looked at more.
Sprint might be different OTOH.
Sent from my Lumia 928 (RM-860) using Tapatalk

Re-enabling Tethering & Portable Hotspot option somehow on Stock or CM12.1/Nexus rom

Re-enabling Tethering & Portable Hotspot option somehow on Stock or CM12.1/Nexus rom
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).
Xplic1T said:
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).
Click to expand...
Click to collapse
How are you getting the internet to be shared via hotspot/tether onto the tablet if not via the WiFi?
Xplic1T said:
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).
Click to expand...
Click to collapse
Please explain what you are trying to accomplish so others are better able to assist. Are you trying to turn your device into an AP to serve out local content? What is the purpose of the tether and would it be used in conjunction with WiFi? While I don't have a solution in mind understanding what you are trying to do may surface some remedies. If the capability has been disabled in Android 5/6 as you claim then the only workaround will likely come via Xposed.
Davey126 said:
Please explain what you are trying to accomplish so others are better able to assist. Are you trying to turn your device into an AP to serve out local content? What is the purpose of the tether and would it be used in conjunction with WiFi? While I don't have a solution in mind understanding what you are trying to do may surface some remedies. If the capability has been disabled in Android 5/6 as you claim then the only workaround will likely come via Xposed.
Click to expand...
Click to collapse
Hi Davey, yes I'm trying to serve local content through a 3rd party app called KWS server. In order to do this on my other tablets, I need to enable a hotspot so that others can connect to it. This feature is invaluable to me as I make presentations that I host from an inconspicuous tablet. Google must of nixed it off the official dev path.
I've installed the XPOSED framework on the Nexus rom and they only had one plugin (X Tether I believe the name) and it didn't work.
All the 3rd party apps out there that say they do this absolutely suck.
Maybe there's some generic unofficial CM10 (Kitkat) rom out there I can try ?
Xplic1T said:
Hi Davey, yes I'm trying to serve local content through a 3rd party app called KWS server. In order to do this on my other tablets, I need to enable a hotspot so that others can connect to it. This feature is invaluable to me as I make presentations that I host from an inconspicuous tablet. Google must of nixed it off the official dev path.
I've installed the XPOSED framework on the Nexus rom and they only had one plugin (X Tether I believe the name) and it didn't work.
All the 3rd party apps out there that say they do this absolutely suck.
Maybe there's some generic unofficial CM10 (Kitkat) rom out there I can try ?
Click to expand...
Click to collapse
Yep - looks like it's a goner in Android 5.1+ in the absence of a mobile radio. Tried to force it but was only successful in disabling WiFi reception and amplifying a distant hotspot that I never connect to (standard WiFi weirdness in the presence of multiple radios). No sign of a functioning AP. The code is likely there but disabled when a mobile radio is not found. Possible it could be enabled via a build.prop tweak. Spent some time searching but didn't find any promising hits. Guessing it's not a high demand item that warrants a lot of attention.
Options (don't shoot the messenger):
- keep searching for a Lollipop solution ... good luck
- snag a cheap KitKat tablet that still supports single radio tethering. Many to choose from including rootable 3rd gen HDXs which have much better specs than 2015 Fire; supports Nexus and CM ROMs. I confirmed the portable hotspot function does work on HDX Nexus. A 2013 Nexus 7 is another fine choice.
- grab an older phone with decent memory specs (eg: Moto X or mini) that will support tethering regardless if running KitKat or Lollipop. You don't need to put it on a mobile plan; just use it as a stand-alone device/server.
Davey126 said:
Yep - looks like it's a goner in Android 5.1+ in the absence of a mobile radio. Tried to force it but was only successful in disabling WiFi reception and amplifying a distant hotspot that I never connect to (standard WiFi weirdness in the presence of multiple radios). No sign of a functioning AP. The code is likely there but disabled when a mobile radio is not found. Possible it could be enabled via a build.prop tweak. Spent some time searching but didn't find any promising hits. Guessing it's not a high demand item that warrants a lot of attention.
Options (don't shoot the messenger):
- keep searching for a Lollipop solution ... good luck
- snag a cheap KitKat tablet that still supports single radio tethering. Many to choose from including rootable 3rd gen HDXs which have much better specs than 2015 Fire; supports Nexus and CM ROMs. I confirmed the portable hotspot function does work on HDX Nexus. A 2013 Nexus 7 is another fine choice.
- grab an older phone with decent memory specs (eg: Moto X or mini) that will support tethering regardless if running KitKat or Lollipop. You don't need to put it on a mobile plan; just use it as a stand-alone device/server.
Click to expand...
Click to collapse
Thanks, yeah I figured that would be the case... It's a pretty big feature for them to just take off like that without input from people.
Whats weird is that none of the 3rd party ones work at all ... even FoxFi.

Categories

Resources