Develop Bugs

[Q] Wifi Tethering on DIAM100 with XDANDROID 2.2.1

Hi Everybody,
I have an anoying problem: I can't get wifi tethering to work. Read millions of posts on XDA but still no results. I love android on my freaky winmo!
This is my status:
Running XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
Settings -> Wireless -> Wifi -> switch on = OK
Settings -> Wireless -> Tethering -> Wifi Hotspot -> switch on = NOK.
It simply says 'error' and it also switches my Wifi off. After this switching on Wifi also fails and giving me the same message: error.
(PS all the menu's are in my native language and I just translated them directly to english. Haven't figured out yet how to switch everything to english)
I tried different kernels (and modules). The last one I tried:
zImage-2.6.27.46-01250-g8f8207c
modules-2.6.27.46-01250-g8f8207c.tar.gz
Remember I read something about wifi and Radio ROM on the phone, but I have not HardSPL-ed it yet. Is there a minimum Radio version required?
Anyway, Hope somebody can help me a bit. I am desperate .
Kind regards,
Mo

Read this thread
http://forum.xda-developers.com/showthread.php?t=711692
download the:
XDANDROID-wifi-tether
Patch (.apk)
hope it work

Wifi Tethering on DIAM100 with XDANDROID 2.2.1
Thanks for your reply,
I already did that. Put the APK file in my AndroidApps folder. Once booted in Android I ran the application, but unfortunately to no avail. It says: Unable to start tethering, is your device rooted? This seems strange, because I am under the impression that the version on my phone already has root privileges?
Kind regards,
Mo

[SOLVED] CM7 | Wifi needs a minute to connect | started with nightlys about Jan.

Hi all,
having troubles with my Wifi. It needs a minute to connect and doesn't connect when screen is off eventhough settings are to always on.
I started asking in CM7 nightly thread about my problem but it's better to have a new thread for that.
So far I didn't find a solution.
I tried:
- replace tiwlan_drv.ko with new one by deleting old one
- compared wpa_supplicant, tiwlan.ini and other data in that folder without significant outcome
- tried old 2011.11.16-nightly where it still worked
Anyone got an idea what I have to copy from my old nightly where it still worked?
This is what happened:
measel said:
sorry, for bringing this up again, since I'm the only one having this issue but I just collected a few logs. maybe someone has a clue what is going on there:
Code:
2012-02-13-19-35-37_wifion.txt > when turning wifi on it needs more than a minute to connect
2012-02-13-19-37-37_wifiscan.txt > wifi instantly connects after starting 'wifi analyzer' app or open the wifi settings window
2012-02-13-19-45-25_wifiscreenoff.txt > when screen is of, wifi doesn't connect eventhough settings are to "always on"
/edit: ok i just tried to read the logs myself and I think you can't really see any reason for that behaviour... am i right that the possible settings I have to look for are in the 'tiwlan.ini'?
Maybe someone provide me a backup of his/her tiwlan.ini for comparison... (I don't have any idea what I'm doing but that doesn't mean I couldn't try. )
I added my tiwlan.ini as well
/edit: compared to tiwlan.ini: no differences. Must be something else.
Click to expand...
Click to collapse
measel said:
Could you please check your logs if it needs exactly a minute to connect? could be a proof that there is some setting involved.
Click to expand...
Click to collapse
measel said:
I just went back to an older version: 2011-11-16 and the problem was gone.
Thank you.
/edit: Ok might have bin the wrong folder... did it have to be /data/misc/wifi/? Argh it's hard when one knows nothing. :|
/edit2: I'm so sorry: I compared wrong files and folders (system and data). I come back here, when I really found something. *shame on me*
Click to expand...
Click to collapse
[] AL [] said:
I'd just copy the module tiwlan_drv.ko [in /system/lib/module] from that older nightly and replace it on the newer build first.
Don't forget to set its permissions afterwards..
You can do this with RootExplorer or with Terminal (from the app tray) by entering these 5 lines:
Code:
su
cd /system/lib/module
mount -o remount,rw /system/
chmod 644 tiwlan_drv.ko
chown 0.0 tiwlan_drv.ko
and reboot.
Click to expand...
Click to collapse

none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap

No wifi problems here... I'm using my personal home wifi network most of the time, but other networks works well too.
Red lense German Vodafone Froyo based
CM7.2 Nightly 02102012

I have this issue if I configure my Router security to WPA. With open I can connect immediately

crakeron said:
none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap
Click to expand...
Click to collapse
can't really say that. It's great in 111116-nightly so I just wanna figure out what I have to change to get the speed back!
Motorola Defy CM72120121, german Froyo base

I have this problem, too.
Nobody else?
Would be great if some devs could please look this up.

SOLUTION
Hello all,
first off: delete wpa_supplicant and everything is fine!
I gave up and did a factory reset/wipe data. After that it worked w/o problems.
> Now I will restore all my apps and check if it's still working afterwards. > still working
> restore wifi access points > NOT WORKING ANYMORE!
> with shame I delete wpa_supplicant > WORKS AGAIN!
I'm so ashamed. :/ Should have done that like months ago.
I go back to my backup and try it there. > deleting the wpa_supplicant worked!!!!

My Wifi has a problem with WRT54G Wireless Router, with Froyo Stock ROM and CM7.1 RC1.5-jordan.
WIFI connect, signal is good but connection is very slow.
On notebooks, the connection is faster with this same router.
In another Wireless routers connection is normal from Defy. The problem is only between Defy x Linksys WRT54G.
I have set Defy and Router to work only in G mode, but the problem persist.
With the same configurations the problem don´t occour with another routers from D-link, Cisco or other.
Anyone know how can I solve it?
Tnks.

A100 with ICS and Ad-hoc: The right wpa_supplicant

After an hour or so of searching for the right file, I want to share with A100 owners how to enable ad-hoc support for their ICS-running tablets. All the work was done by other users on this forum, but I just want to compile the right links and method here.
1) Root your device. Follow the instructions on http://forum.xda-developers.com/showthread.php?t=1531646 and you should be set.
2) Remount /system as rw. In a root terminal,
Code:
$ su
# mount -o remount,rw /dev/block/mmcblk0p3 /system
For the next few steps, I recommend using a file manager.
3) Navigate to /system/bin and backup your original wpa_supplicant file.
4) Copy the wpa_supplicant from http://forum.xda-developers.com/showpost.php?p=25356357&postcount=136 to /system/bin.
5) Change the permissions of your new wpa_supplicant file to match the old one. It should be -rwxr-xr-x.
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!

It's does not work on my phone.
My phone is Galaxy note ICS.

bunkhun said:
It's does not work on my phone.
My phone is Galaxy note ICS.
Click to expand...
Click to collapse
The right wpa_supplicant varies by device, which is why it took so much trial-and-error for me to find the right one. This one I can confirm to work on Acer A100 running ICS. You'll have to look for a wpa_supplicant that works on the Galaxy Note. Look around on the forums and experiment with wpa_supplicants and you might get lucky (just don't forget to backup your existing one)
Sent from my A100 using XDA

I guess I'm not sure what this ad-hoc really does. I can tether my phone's 3G network as a hotspot. My A100 running Flexreaper ROM can connect to it and browse the internet just fine without modifying the wpa_supplicant. Maybe civato already included the modified wpa_supplicant in the ROM?

That's probably right; the Flexreaper ROM probably has an ad-hoc compatible wpa_supplicant. I'm pretty sure Cyanogenmod has, too. Ad-hoc allows a wireless device to connect to another peer-to-peer style (i.e., without a router). Cell phones that broadcast hotspots are ad-hoc networks. For some reason the stock Android OS does not allow connecting to ad-hoc networks, so a modified wpa_supplicant must be used.
Sent from my A100 using XDA

I copied the file over. I used root explorer for everything. I will check it momentarily.
---------- Post added at 12:58 PM ---------- Previous post was at 12:53 PM ----------
Are you tethering using Bluetooth or are you using a cable? If you are using a cable, what kind of cable. I have looked for a micro usb to micro usb cable but cannot find one. Please advise.
---------- Post added at 01:33 PM ---------- Previous post was at 12:58 PM ----------
Okay, it's working perfectly over Bluetooth. My speed to New Orleans was 1.9mbps down and .9 mbps up. Not bad at all on 3g, Bluetooth. I am very pleased. Now if I could SMS my son. He does not care for google chat or google plus, but he has unlimited texting. I don't because I don't text much.
Thanks for compiling this for us.

Thanks!
Thank you! That was really quick and painless! I now can connect my A100 to my Nokia E72 using Joikuspot!!
Initially, I followed the instructions but I could not mount RW even after successful rooting - not sure why. If you have the same problem, you can try the following:
1. Turn off your Wifi before proceeding
2. Save the modified wpa_supplicant provided in the given link to your PC - e.g. the desktop (you'll need to unzip it)
3. Connect your A100 to the PC via the USB cable.
4. Copy the wpa_supplicant file to anywhere in your A100 (temporarily) using your PC's usual file manager.
5. Use a good file explorer on your A100 (I used Root Explorer - very powerful! But must purchase from Googleplay - $5 Singapore dollars only) to get into the file directories of your A100 and find the modified wpa_supplicant file. Long touch the file until the menu appears and choose 'cut' from the menu.
6. Use Root Explorer to set "mount R/W" which is a convenient button near the top left of the screen
7. Now navigate to the /system/bin folder and find the original wpa_supplicant file - long touch it until the menu appears. Rename it to something like 'wpa_supplicant_original' or whatever you like.
8. Paste the new wpa_supplicant file
9. Exit and go back to settings to turn on the Wifi
10. You should be able to see a (*) next to E72-Joikuspot_XXXXXXX (assuming your phone is on and Joikuspot is on). Now just connect the usual way and now you have adhoc access!

CombatCube said:
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!
Click to expand...
Click to collapse
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?

childoftheworld said:
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?
Click to expand...
Click to collapse
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.

pio_masaki said:
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.
Click to expand...
Click to collapse
Which forum should I be posting this in?

childoftheworld said:
Which forum should I be posting this in?
Click to expand...
Click to collapse
Either your device specific forum, if there is one, or if not there's a forum for devices without their own forum. Some things are universal to a point and others aren't, so if something here doesn't work it'll likely need something based on your device or one with similar hardware.
Tapatalked from my Galaxy S II.

[Q] Another 4.3 Wifi Tether TrevE problem thread

I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.

atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.

bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??

Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.

I'm running synergy 4.3 rom and native hotspot works no problem. .

I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.

Lollipop tethering (working)

Thanks to datawrhsdoc for translating the OP
datawrhsdoc said:
1. Root your phone
2. Either modify your existing APN to use IPv4 and adding 'dun' to the list of APN types, or create a duplicate APN with the same modifications
3. Set the modified/new APN as your default.
4. Download tether_counter_kill.txt from the OP's first post, and rename the file removing the txt extension (http://forum.xda-developers.com/showpost.php?p=59858654&postcount=1)
5. Install Smanager from Play Store
6. Navigate to tether_counter_kill from Smanager, and set both 'Su' and 'Boot' options. Run it (you won't need to do this again)
7. Start Mobile Hotspot on your phone, and connect to the hotspot from your devices
8. Immediately start a VPN client from your device(s) which will tether. VPN must redirect ALL traffic (e.g., TorGuard).
9. Enjoy unlimited WiFi tether
Click to expand...
Click to collapse
You can also try adding this to your build.prop (I don't know if this does anything):
net.tethering.noprovisioning=true
Click to expand...
Click to collapse
Idea for the script taken from:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
Click to expand...
Click to collapse

RussianBear said:
Looks like the settings.db is on a lock-down. I can't access it via sqlite any longer. It says: "the database is currently locked by another process"
Any ideas? @autoprime ?
Quick Edit: was able to copy settings.db to sd card and open it up with sqlite. couldn't change any parameters, as sqlite would fc. Downloaded this guy (http://sqlitebrowser.org/) and made changes, then overwrote the one in data/data directory. We'll see how/if it works.
Click to expand...
Click to collapse
Any luck so far?

Fhuron said:
Any luck so far?
Click to expand...
Click to collapse
Nope, something over-writes the tethering back to "1" after each reboot. I'm sure @autoprime can figure this one out, as he did for KK.

You are right I'm on LG G2 with official T-Mo lollipop and I was able to edit settings.db...not with sglite but with SQLite Debugger.
After reboot, the changes i made to the tethering reverted back to dafault 1.

For those that want to use wireless tether, try the app from this thread (it's $2.5):
http://forum.xda-developers.com/note-4-tmobile/general/unlimited-wifi-tethering-t2914057
I'm more interested in making the usb tethering work. I'll try using IPv4 + vpn tonight. Pretty sure it's going to fail because of the tether.dun set to 1...
P.S. additional links:
http://forum.xda-developers.com/note-3-tmobile/help/tethering-fix-t3068545
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/unlimited-tethering-t3073884

Another quick update. The guide from here works for tether_dun settings: http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
You can use this command in terminal emulator, pending you are rooted.
su
settings put global tether_dun_required 0
Click to expand...
Click to collapse
or those having issues with tethering. I tested it out today and had issues. It would connect but would not resolve dns. I have unlimited tethering on Three, it's always worked until now.
Doing this resolved my issues. I suspect this issue will be resolve by Three when an official uk build is released.
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
Click to expand...
Click to collapse

RussianBear said:
Another quick update. The guide from here works for tether_dun settings: http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
You can use this command in terminal emulator, pending you are rooted.
Click to expand...
Click to collapse
anyone tested does this work with no tether tracking?

Uploading a tether_dun_required=0 script (needs root) that you can use with Smanager to either trigger it via a desktop widget, app, or set it on boot. Remove ".txt" from the end and navigate to it via Smanager. I will test tethering later tonight.
Make sure you click/select the SuperUser icon in Smanager's options.
You can also try adding this to your build.prop:
net.tethering.noprovisioning=true
Click to expand...
Click to collapse

Looks like we're money, at least on usb tethering. I will update the op.

any specific settings on Wifi Tether Router? I'm unable to get an SSID to show up using the instructions from wifi tether router's website.
updated APN to ipv4
ran script posted above..

rihc55 said:
any specific settings on Wifi Tether Router? I'm unable to get an SSID to show up using the instructions from wifi tether router's website.
updated APN to ipv4
ran script posted above..
Click to expand...
Click to collapse
Try using stock wifi tether and see if it's counting. I haven't used the other app yet.

RussianBear said:
Try using stock wifi tether and see if it's counting. I haven't used the other app yet.
Click to expand...
Click to collapse
Ohh okay. even better.. ill try it and report back. thanks
EDIT:
Strange, i cant even get an SSID to show up on the native hotspot now. I know it worked before -- i used it last Sunday. The hotspot turns itself off after like 30 seconds.

Okay.. So I did a factory reset because i didnt know how to fix my problem from my previous post.
Then I:
1) added the same APN as IPV5
2) did this:
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
3) used the native tether app
I haven't tested it very extensively but from what i can tell, i am able to tether and it just shows up as normal data vs mobile hotspot. I transferred bout 600mb as a test. will test more later.
Thanks for your help RussianBear!
EDIT:
I lied. i think tmobile was delayed in reflecting my usage. it showed up today.

My hot-spot was broken by LP. Devices connect fine but have no Internet whatsoever. I'm able to USB tether without issues using PDANet and just selecting level 1 hide tether usage works fine. No needs for UA switching or anything like that. Just wish the WiFi tether worked, even if it's counting.

Could anyone help with step by step instructions. I am new at this and dont want to do anything wrong. Plus i dont see the script.

dreday3223 said:
Could anyone help with step by step instructions. I am new at this and dont want to do anything wrong. Plus i dont see the script.
Click to expand...
Click to collapse
Dre, are you rooted? Script is attached to the bottom of the first post.

RussianBear said:
Dre, are you rooted? Script is attached to the bottom of the first post.
Click to expand...
Click to collapse
I am. What exactly do i have to do? Where do i place that command? This is all very new to me and I'm not trying to mess up my phone so the simplest of instructions would be great.

dreday3223 said:
I am. What exactly do i have to do? Where do i place that command? This is all very new to me and I'm not trying to mess up my phone so the simplest of instructions would be great.
Click to expand...
Click to collapse
Download smanager from the playstore, download the script, then using smanager navigate to the script and run it. You will need to select the su icon from the smanager's script options. Let me know if/where you get stuck.

Script Works for WIFI Tether
It appears that this method is working for WIFI tethering as well. I watched an 11 minute Youtube and then emailed myself a 5.5MB Powerpoint. Here are my results:
Before After
Mobile Hotspot 92.2 92.4
Data 462.2 527.1
Not sure where that 0.2MB came from, but that's not much of my 5GB plan, so I don't much care.
Update 1: Figured out where the 0.2MB came from. My testing used all encrypted traffic over HTTPS, and TMO couldn't track it. I then ran a CNN.com video and the Mobile Hotspot counter spiked. Still not quite there yet.
Update 2: Enabled my VPN, and no traffic at all is being tracked by TMO. No user agent required. Yipee!!

datawrhsdoc said:
It appears that this method is working for WIFI tethering as well. I watched an 11 minute Youtube and then emailed myself a 5.5MB Powerpoint. Here are my results:
Before After
Mobile Hotspot 92.2 92.4
Data 462.2 527.1
Not sure where that 0.2MB came from, but that's not much of my 5GB plan, so I don't much care.
Update: Figured out where the 0.2MB came from. My testing used all encrypted traffic over HTTPS, and TMO couldn't track it. I then ran a CNN.com video and the Mobile Hotspot counter spiked. Still not quite there yet.
Click to expand...
Click to collapse
Are you using a vpn service or just agent switchers?