News for hackers. Stuff that matters.
Re:The Cheap Phones Quietly Winning the U.S by dharma1 on Friday September 04, 2015 @08:23AM (#10169935)
I have Moto G. Software updates are fairly regular, but I still switched to Cyanogenmod. I'd say there isn't much difference between CM and stock android. You can tether with CM without worrying about telco tethering blocks, something that doesn't work on stock android
Re:The Cheap Phones Quietly Winning the U.S by rahimnathwani on Friday September 04, 2015 @09:07AM (#10170121)
"You can tether with CM without worrying about telco tethering blocks, something that doesn't work on stock android"

Doesn't that depend on your carrier? IIRC some carriers detect tethering by looking for packets with different TTL values (which would represent different devices' defaults, or indicate an extra decrement as the packet went through the phone), or inspecting HTTP User-Agent.

Re:The Cheap Phones Quietly Winning the U.S by dharma1 on Friday September 04, 2015 @10:31AM (#10170685)
potentially, but stock Android tells the carrier it's tethering, and there's no way around it. CM doesn't. http://danielpocock.com/android-betrays-tethering-data

You can hack around both TTL values and user-agent btw. Deep packet inspection, maybe less so

Re:The Cheap Phones Quietly Winning the U.S by dublinben on Friday September 04, 2015 @11:54AM (#10171236)
I was unable to replicate his results on my Nexus 5 running AOSP. This behavior has possibly changed in newer versions of Android.

Also, DPI can be trivially bypassed by running all traffic from your phone through a VPN. All traffic, tethered or not, will be indistinguishable to your carrier.

Re:The Cheap Phones Quietly Winning the U.S by dharma1 on Friday September 04, 2015 @12:42PM (#10171511)
On my Android Moto G, running Android 4, I could not get around my carriers (Three UK) tethering block. CM solved that.

VPN would work for DPI true, hassle though.

Re:The Cheap Phones Quietly Winning the U.S by dublinben on Friday September 04, 2015 @02:57PM (#10172216)
Are you running the 'stock' Google-provided ROM, did you try an actual fresh installation? I'm running a clean AOSP ROM, without any kind of CM customizations.