EOF - 3G Hell
In June of this year, I arrived in Paris for a five-week stay, during which I had hoped to enjoy my new Android Nexus One phone and maybe get some development started on the Android version of an app I'm working on. I'm about halfway through the trip right now (early July), and I have gotten nowhere with data on the Android, outside of Wi-Fi in our rented apartment. (And I won't bother going into the problems there.) But, I am learning some hard lessons along the way—mostly about the hostility of mobile phone carriers toward Internet usage. What I don't yet know is what to do about it, other than get along without it. Maybe we can come up with some fresh ideas.
My saga began when I went cheerfully to the nearest Orange store in Paris and spent 40 euros on a SIM card with prepaid phone service and 450Mb of data for Net access. When I stepped outside, I found that the data didn't work (no browsing, nothing from Google Maps), so I went back in and asked the saleswoman what was up. She told me to wait 24 hours. So I did. Still didn't work. When I went back to the store, a different salesperson told me he didn't understand the Android phone because Orange didn't sell it. So I went to another Orange store. They told me that only the first store could help me. I went back to the first one, and a different person there told me that he couldn't help me at all—and basically, to please leave. And I wasn't behaving badly (other than not knowing enough French).
The next day, my mood lifted during an excellent lunch with Henrik Moltke of Mozilla Drumbeat. Afterwards, Henrik kindly spent a couple hours with Orange on his own phone, trying to make data work for my Android. Finally it did, for a few minutes, after which the phone would only take calls, but no longer make any. So, I gave up while we spent the next week with friends on a boat we rode down canals through Lorraine and Alsace, at the far end of which I took time out from enjoying Strasbourg to submit my Android to the mercy of one more local Orange store. There, a young man who spoke good English gave me the low-down. “Just don't use data”, he said. “It's too expensive.” He also explained that I had somehow used up my 40 euros and needed to “recharge” the prepay deal. So I bought 35 euros worth of prepaid minutes and no more data. An hour later, the phone would only take calls, but not make any. One more check with an Orange store made it clear that I somehow had used up my fund again.
I spent the next week in the UK hanging with alpha geeks, including Kevin Marks, one of the prime movers behind both microformats and OpenSocial. After inspecting my settings, Kevin suggested that Twitter was to blame. Or rather, me. I had left on Twitter, which went on data hunts frequently. “Hitting the API uses a lot of data”, he said. “It's a lot more than the 140-character postings.”
Since then, I have discovered that 3G data over mobile connections is almost entirely a national affair. Buy 3G data access in one country, and you can't use it in another without risking enormous bills. This is even true in Europe, where the low hurdle to international phone dialing is entering national prefixes, and on many phones, that's automatic. But data is bizarre. It has national borders, like phone systems five decades ago. Responding to a blog post (blogs.law.harvard.edu/doc/2010/06/30/orange-crush) on my woes, Maarten Lens-Fitzgerald of Layar (a Netherlands-based augmented-reality app developed first for Android) commented, “seriously, this is an issue. I always use my local SIM while abroad. apart from the cost i mostly don't get past gprs/edge speeds as i am visiting on the network....The world is not flat for mobile subscriptions.”
At least my damage was limited to a couple prepaid funds that ran out. The risk is much higher for 3G customers who don't know they've stepped over a line. Look up 3G bill shock, and you'll get a half-million results, most with high-priced tales of woe. One, in the Guardian (www.guardian.co.uk/money/2010/feb/21/broadband-dongle-roaming-bill-shock), tells of a £7,648.77 bill by Orange for a UK student using his 3G dongle in a normal way, but in France.
I still don't know why international companies like Orange, Vodaphone and T-Mobile have data “roaming” between their own national divisions, while phone roaming has no extra costs. Maybe the problem is regulatory. I don't know—yet. What I do know is that the Net over which Linux was developed, and on which it continues to mature, thanks to code contributions from all over the world, was not made to be fenced off this way. And there should be a limit to our tolerance of it.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
7 hours 13 min ago - BASH script to log IPs on public web server
11 hours 40 min ago - DynDNS
15 hours 16 min ago - Reply to comment | Linux Journal
15 hours 49 min ago - All the articles you talked
18 hours 12 min ago - All the articles you talked
18 hours 15 min ago - All the articles you talked
18 hours 17 min ago - myip
22 hours 41 min ago - Keeping track of IP address
1 day 32 min ago - Roll your own dynamic dns
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




Comments
This site is very helpful,
This site is very helpful, especially while traveling Europe, regarding 3G options: http://prepaid-wireless-internet-access.wetpaint.com/.