Skip to main content

Using Google Nexus One in Istanbul Turkey

Yes, it is possible. The device is compatible and can connect to the local 3G network (Turkcell) with minimal hassle. In addition, even though I had to purchase a two-year T-mobile subscription with my phone, the device is unlocked!

Disclaimer: I purchased this phone directly from Google in May 2010. Google is no longer doing this.

As soon as I landed in Istanbul, I went to the Turkcell kiosk, registered my IMEI number, purchased a prepaid card, and activated it. You MUST register your phone with the government agency or it may be banned permanently.

The next step is to subscribe to the 3G internet service. There are two types of 3G services:

1. Faturali (invoiced) 3G Internet

http://www.turkcell.com.tr/bireysel/3G/3Ginternet/tarifeler/faturali3Ginternet

Subscription for this plan is automatically renewed every month. And there is an overuse charge which is currently 0,050 TL/MB.

2. Faturasiz (non-invoiced) 3G Internet

http://www.turkcell.com.tr/bireysel/3G/3Ginternet/tarifeler/faturasiz3Ginternet

This is an on-demand plan which is limited by time and/or usage. It does not renew automatically; you need to repurchase it at the end of your subscription period or if you hit your usage limit before your plan expires.

After getting a prepaid card, activating a 3G plan is as simple as sending an SMS message to the appropriate number defined on the links above. [In my case, I was not properly briefed by the sales people at the airport kiok so I ended up purchasing the first plan.]

The last step is to do a little bit of setup. Go to Settings > Mobile Networks > Access Point Names, click on Turkcell, and set the APN to "internet" - without quotes.

You should be able to connect to the Edge network. If not, reboot your phone. Some time later (for me it took over a day) you should receive an SMS confirmation message for your 3G subscription request and the 3G icon should replace the Edge icon. (There is an unnecessary opt-in process after you purchase a 3G package. It should happen automatically. If not, simply call the support center.)

Comments

  1. I too agree with you....Your information was very useful...I too enjoyed the same privilege..but mine was not unlocked..I unlocked it through a third party unlock service, Classicunlocking.com and removed the network restriction permanently.Afterwhich i was able to switch over to a local network in Istanbul.

    ReplyDelete

Post a Comment

Popular posts from this blog

Securing Symfony2 REST services with FOSOAuthServerBundle

Overview In my previous article, I wrote about setting up a Symfony2 REST service using FOSRestBundle. However, this REST service was behind a firewall protected by a generic form_login provider. Not really ideal if you wish to open your REST API to other applications. So in this article, I will try to explain how to set up FOSOAuthServerBundle to protect your REST API methods using OAuth2. Before we start getting into the gritty details, it is a good idea to have a look at the official OAuth2 documentation . Let's begin... FOSOAuthServerBundle Installation You have to install v1.1.0 of FOSOAuthServerBundle if you are using Symfony 2.0.x. If not, see the docs . First, add the following entries to your deps file: [FOSOAuthServerBundle] git=git://github.com/FriendsOfSymfony/FOSOAuthServerBundle.git target=bundles/FOS/OAuthServerBundle version=origin/1.1.x [oauth2-php] git=git://github.com/FriendsOfSymfony/oauth2-php.git Run the vendors script to install these...

Adding post-login logic to FOSUserBundle

Having finally figured out how to use FOSUserBundle in my project, I decided to keep track of all logins next. The implementation turned out to be a breeze thanks to Symfony2's security listener mechanism. As usual, the first step is to create a MongoDB document for this purpose. This is a very simple document that contains a user's id, session id, IP address, and login date. src/Acme/UserBundle/Document/LoginHistory.php namespace Acme\UserBundle\Document; class LoginHistory { protected $id; protected $userId; protected $sessionId; protected $ip; protected $createdAt; /** * Get id * * @return custom_id $id */ public function getId() { return $this->id; } /** * Set userId * * @param int $userId */ public function setUserId($userId) { $this->userId = $userId; } /** * Get userId * * @return int $userId */ public function getUserId...

Unexpected token "name" of value "if" ("end of statement block" expected) in "WebProfilerBundle:Collector:logger.html.twig"

Encountered this WebProfilerBundle error message when I ran the bin/vendors script to update my Symfony2 bundles. Make sure your deps file is up to date; you need to pay special attention to your version values. In this case, update your twig version to v1.2.0 as illustrated below: [twig] git=http://github.com/fabpot/Twig.git version=v1.2.0 Run the vendors script to update your bundle and the error message should disappear. You can get the most up to date deps file from the symfony-standard repository located at: https://github.com/symfony/symfony-standard/blob/master/deps