Isn't that essentially what the dock would provide?
I don't have an android phone anymore, but the only way I could imagine AT&T would know I'm tethering is if Android added some header information that the network would sniff, almost like a dog tag. Or they read the user-agent headers per request and saw that it was a non-mobile browser making the requests...I would think that booting into Ubuntu would show the same results unless your spoof your user-agent, but then you might end up getting the mobile version of the site instead of the full desktop version...it's all just a big mess.
If anyone knows how AT&T or other mobile ISP's would differentiate mobile traffic from tethered traffic, I would love to know.
Also, I did have to unlock my device and put a new ROM on my phone to enable tethering.
The TTL on tethered packets is 1 less than on packets originating from the phone. That's the easiest way, and one that most tethering solutions don't fix.
I don't have an android phone anymore, but the only way I could imagine AT&T would know I'm tethering is if Android added some header information that the network would sniff, almost like a dog tag. Or they read the user-agent headers per request and saw that it was a non-mobile browser making the requests...I would think that booting into Ubuntu would show the same results unless your spoof your user-agent, but then you might end up getting the mobile version of the site instead of the full desktop version...it's all just a big mess.
If anyone knows how AT&T or other mobile ISP's would differentiate mobile traffic from tethered traffic, I would love to know.
Also, I did have to unlock my device and put a new ROM on my phone to enable tethering.