This post applies only for Samsung Galaxy S Plus GT-I9001. These steps might not work on any other phone. Even, if you are on I9001 phone, proceed at your own risk. No one (including me & God) is responsible if anything happens to you or your phone ;)

Assuming you are running the stock Gingerbread Android OS, here are the steps:

1. Get all the required software
2. Enable development mode on your phone
3. Backup all your existing data
4. Root your phone
5. Install ClockworkMod Recovery 5.5.0.4
6. Reboot your phone in recovery mode
7. Install Ehndroix
8. Install S3 style pack
9. Reboot your phone

Backup all your existing data

Enable development mode on your phone. Go to Settings->Applications->Development->Enable USB Debugging.

I cannot emphasize enough of the importance of taking backups. Make sure you diligently backup everything. Crying later is of no use

1. Dump everything in your phone storage on your computer.
2. Dump everything in your external SD card on your computer.
3. Backup all apps. This app creates a nice list of existing apps on your phone, which you can use to reinstall apps from the Play Store. Download on your phone.
4. Backup SMSes. Use this app.
5. Backup call records. Use this app.
6. Then backup anything else you may want to.

Root your phone

1. Connect your phone to your computer via USB.
2. Transfer Root-I9001 to the internal SD storage of your phone.
3. There are 2 ways to reboot into recovery mode: a) Use the ADB recovery batch file downloaded above. b) Power off your phone. Then press Vol Up key and Power button together to enter into recovery mode.
4. In recovery mode, you will see a small white box and the android icon in the center of the screen. When you see this, touch the menu soft key on your phone a few times. The icon will alternate between bright and dull. After pressing it a few times, leave the icon in the dull state. After this, the recovery menu will appear.
5. Select, “Install update from the zip file”, then select the Root-I9001 zip file to install it.
6. Reboot your phone.
7. If your phone is rooted properly, the SuperUser app would be installed.

Install Clockworkmod Recovery 5.5.0.4

1. Connect your phone to your computer via USB.
2. Transfer the clockworkmod recovery 5.5.0.4 zip file to the internal SD storage of your phone.
3. Get into recovery mode and install clockworkmod recovery.

You could get into trouble here. Once you reboot and get into recovery mode again, the phone might be booting only in recovery mode. To overcome this:

1. Make sure the USB cable is disconnected.
2. Extract the AriesVE archive.
3. Open Odin.
4. In the “OPS” field, select the OPS file from the extracted AriesVE folder.
5. In the “Boot” field, select the Boot_loader.tar file.
6. Now, reboot your phone in “Download” mode. To do this, switch off the phone. Then press, Volume down button, center button and the power button together. It should enter download mode in no time.
7. Then connect the USB cable.
8. Odin should recognize the phone quickly.
9. Click on the “Start” button in Odin.
10. The boot loader should be repaired properly.

Transfer Ehndroix to the phone

1. Connect your phone to your computer via USB.
2. Transfer the Ehndroix mod and the S3 style pack to the internal SD card.
3. Reboot the phone in recovery mode.
4. You should be able to see the Clockworkmod Recovery instead of the stock recovery.

Note: At this point, if you happen to have a fresh micro-SD card with lots of space, consider backing up the entire system using the “backup and restore” option of Clockworkmod Recovery.

Install Ehndroix

1. Reboot your phone in recovery mode (By now you should have become an expert at this ).
2. Wipe data/factory reset.
3. Wipe cache partition.
4. Select “install zip from sdcard”.
5. Select the Ehndroix zip file. Installation will proceed.
6. Select “install zip from sdcard” again & pick the S3 style pack. That will also get installed.
7. Now reboot the phone.
8. The NitroX animation will show. After it ends, it will take between 3-10 minutes for the first time to boot.
9. If it doesn’t boot by that time, remove the battery, put it back and switch on the phone.

Enjoy ICS

What if the phone gets bricked?

If at any time in this process, your phone fails to boot properly or if you feel you have messed up royally, do this:

1. Disconnect USB cable.
2. Boot the phone in “download” mode.
3. Open Odin.
4. Select the AriesVE “OPS” file.
5. Then check the “one package” option.
6. Extract the stock ROM you downloaded. It will a [name].tar.md5 file.
7. Click the “one package” button and pick the tar.md5 file.
8. Connect the phone via USB. Odin will recognize the phone.
9. Then click on “Start”.
10. For me, this flashing process took about 5 minutes. It might vary for you.

Any questions? Leave comments.

Hope this post was useful to you.

After that, I wrote a simple utility script that will automatically do a full CSV export of Buxfer accounts data and email it. At the start of the script, there are couple of PHP variables that you can use to customize it – your buxfer id and password, from email address, to email address, email content etc. To automate it completely, use crontab to schedule its execution and rest in peace .

I have hosted the code at GitHub. Do check it out and let me know your feedback. Or better yet, fork it and add your bells and whistles.

You can access the GitHub repository here.

1. Get Firefox browser.
2. Get greasemonkey addon.
3. Grab my greasemonkey script here.
4. Login to www.meebo.com.

That’s about it. Fill up the textbox and hit send. The message will be sent to all your IM buddies.

If you are savvy enough, you can make some customizations to the script.

1. Right click on greasemonkey icon and click on “Manage User Scripts”.
2. Select “meebo all at once” and click “Edit” at the bottom of the window.
3. The script will be opened for editing in your favourite text editor.
4. Follow the instructions and make changes to the block marked in the source code.
5. Then reload www.meebo.com.

That’s pretty much it. I quickly hacked it up in couple of hours so there might be some loose ends. If so, please let me know and I will fix it at the earliest. If you wish to make improvements yourself, you can fork the script at the Github repository.

Summary

1. Link to the script.
2. Link to the repository.

If you are even more savvy, you might want to check the Meebo analysis below.

Analysis of Meebo

Meebo makes heavy use of the Comet programming paradigm. Once the user is logged on, the server returns a session key and a client ID. After that, it makes a series of “event” AJAX requests. Each of those requests receive a JSON response. E.g. {“rev”:3,”events”:[{“type”:”buddy::online”,”data”:{“user”:”aswinanand@meebo.org\/Meebo”, … The rev parameter that is sent with each request is incremented by one for every request from a given client ID. The list of buddies for a given provider – Yahoo! Messenger, Google Talk etc. – are received in parts over multiple long lived HTTP requests.

Once the list of buddies are received, it constructs a few javascript global objects based on the JSON response. Such objects include:

1. gBuddyList – instance of meebo.BuddyList
2. gNetworkMgr – instance of meebo.NetworkMgr. This is the core network manager that handles AJAX requests and their asynchronous responses.
3. gIMGateway – contains the client ID required to make the AJAX request

… and many more.

I found out these global objects by enumerating the properties of window javascript object. There’s a property called m_buddies in gBuddyList that contains the set of buddies and their related metadata such as whether the user is online or not, their status message, network (yahoo, gtalk etc.) and other such details. It also has a length property and a nice bunch of helper methods such as getByIndex, getBuddyById etc.

AJAX Requests

When a message is sent to a buddy, an AJAX request is fired to http://www.meebo.com/mcmd/send with a list of parameters that include: receiver, sender, protocol, clientID, sessionKey, mt, msg. In the usual scenarios, we need to reconstruct the AJAX request. But when we have gNetworkMgr global object, this stuff becames a breeze. Hence, a simple called to gNetworkMgr.doRequest(“send”, args) fired the request with the needed parameters. Here, args is a custom constructed javascript object that contains the request parameters. The first parameter “send” is used by gNetworkMgr to construct the actual URL at which the AJAX request has to be sent.

Currently, the script doesn’t monitor the AJAX response. But it could be done if required. Do try out the greasemonkey script and give feedback. Hope you enjoyed the lecture

Here’s a typical work flow for my trek photos:

Go on a trek –> Click nice pictures –> Transfer the photos to the computer –> Make minor modifications such as contrast, brightness, saturation, cropping etc. –> Remove duplicates –> Add signature, copyright notice –> Generate a low resolution version of the final photographs –> Upload them to Flickr/Picasa/Facebook to share them with the world.

With these powerful cameras, much of this can be done on the camera itself. For e.g. my camera already allows adding signatures to pictures through a text stamp feature. It also allows notes to be added to pictures. The pictures can be cropped and frame freezes can be obtained from HD videos shot with this camera. While cropping, a tiny popup containing contrast, saturation and brightness could be displayed. Pictures can be marked with a star so that they can be cycled through while viewing the clicks.

What I want now

Each camera should have a nice file system API, network API and GUI API. Using these APIs, third party applications would be able to fetch photos from the memory card and do the required modifications. More detailed descriptions would be added to the photos and they would be preserved as part of the picture’s EXIF data.

The memory card should be formatted in a special way so that it can hold third party applications in a separate shell. This shell would be accessible through an iTunes like desktop software from which third party applications for the camera can be installed or removed. Once an application is installed, it should be displayed in an Application settings screen on the camera, from where the application can be activated or deactivated.

Once the necessary modifications are done, using the network APIs and WiFi, the application should upload the “starred” photos to flickr, picasa, facebook or any other service the application supports. All these and other services support HTTP APIs. Instead of the camera themselves supporting various services, it could just provide nice APIs and let the developers do the magic. While uploading each picture, a very high resolution picture should be scaled down for the web dynamically.

Geo Tagging

Oh wait! I want to geo-tag the photos as well. So, while clicking each photo, they should be geo-tagged in the background so that the actual speed of clicking a photo isn’t affected. Manually geo-tagging photos are a huge pain in the wrong places.

So, there you go! Click pictures –> Geo tag them in background –> crop them & make other minor modifications –> add text stamp for copyright notice –> Generate low resolution versions dynamically (cache them if required) and upload them!

Since most of the work is done by software in digital cameras, I think the stuff mentioned above is very much feasible. At least geo-tagging should be brought in as a feature.

By now, everyone must have been aware of the recent Facebook announcement of the universal Like button. As probably talked about all over the web, this one button is like giving too much of power to one company. By now the Like button should have appeared on thousands of websites already. Famous press blogs running wordpress should have had the Like button along their standard ‘share this’ toolbar. Facebook’s 400 million+ user base is a huge audience to showcase your content to & everyone wants a piece of the pie!

However, this like button reopens an old problem in a new way… User Privacy. Few years ago, when doubleclick.net installed tracking cookies for sending customized advertisements, it created a huge uproar. Similar stuff happened when Google History came about. But now, Facebook uses a clever way to track users that, you cannot even opt out if you don’t like the process. It makes of full use of the way how the web and ultimately, HTTP(S) works.

I’m not even talking about the case where you are logged in to Facebook and click on a ‘Like’ button on a website. That’s voluntary. You like a piece of content and you spread it to your friends and fans on Facebook. I’m talking about the case where you just visit a certain website containing the Like button and that data will be harvested by Facebook.

Like this on Facebook to understand how it works:

How it works

Let us take it step by step:

1. Clear cookies on your browser. If you are using Firefox or Chrome, press Ctrl+Shift+Del.
2. Visit www.facebook.com
3. Login to Facebook.
4. Visit other websites to be tracked. So simple isn’t it?

When you first visit Facebook.com, it sets a cookie called “datr”, whose expiry is two years from now. So, if you visit Facebook.com today and never clear your browser’s cookies, you will be tracked for the first two years with “datr”. When that period expires, it will be replaced with a new cookie and you will continue to be tracked. After you login to Facebook, it sets some more cookies on your browser along with a cookie called “xs” which is the session cookie for your Facebook session. If you remove this cookie, you will be redirected to Facebook’s login page. After login, “datr” and “xs” cookies will be refreshed.

When you embed the Like button on your website, it loads in an iframe in the Facebook.com domain. When a request is sent to any website by clicking on a link or by typing it on the browser’s address bar, the browser sends all the active (non-expired) cookies to the domain. So, when the Like button loads on a website, it makes a request to http://www.facebook.com/plugins/like.php. Along with this request, it will send the “datr” and “xs” cookies. It will also set the HTTP ‘Referer’ header to the originating website. For example, if you click on a Facebook.com link from my website, the Referer header will be set as ‘www.aswinanand.com’. This is used by other websites to determine where the user is coming from.

Now, when the ‘Like’ button loads on a website inside Facebook’s iframe, the Referer header will be set to your website’s page, “datr” cookie will be sent and if you have already logged in to Facebook, “xs” cookie will also be sent. So, just by loading Facebook’s Like button, Facebook will know what websites you had visited. Since the expiry for “datr” is set to two years, it will associate your Facebook logins to this cookie… which means, even if you logout of Facebook, it will know who the user is. Moreover, when you are logged in and move from one place to another, Facebook will know during what times of the day you are active and during what times you are inactive. When you are active, it will know from where your web browsing occurs and by being able to find location from IP address, they will know where exactly you are moving. Don’t worry, all this data will also be combined with your Facebook mobile usage and a final stat will be arrived at! That’s scary because it could reveal so much about a user & all privacy is gone with the wind.

Targeted Advertisements

This kind of tracking is something the user cannot opt out because sending cookies and setting HTTP Referer headers are part of the protocol. That means, you are tracked by default. Without your knowledge, your online behaviour and all the websites you visit (assuming they have added the Like button) after logging into Facebook are tracked by Facebook. This is useful for a lot of cases. Say you visit IMDB after logging in to Facebook. Each of the movie pages will have the like button. So Facebook will know which movies you are visiting. When you click on the ‘Like’ button for a certain movie, it gets to know your tastes and offer more movies along similar lines when you visit IMDB next. This same technique could also be used by spammers to trick you in to ‘liking’ some random link of their choice.

Like this, through the iframe based ‘Like’ button, Facebook funnels all required data to create a customized and scary experience.

Why not Google?

Ideally speaking, this was something that Google should have done a year or two ago. Most people I know are logged in to Google all their day and web browsing happens simultaneously. Just think of what would would happen if Google had done this. With their already powerful search tracking user behaviour and statistics, adsense would use this data to send specific advertisements to users. Google analytics is already deployed on tons and tons of websites all over the web. This one ‘GLike’ button could also be used to track statistics so easily. Now all of that happens on Facebook. Facebook is luring developers and users alike with its huge user base . Combining a utility like ‘Like’ button with Google’s powerful anti-spam, anti-phishing and other anti-* mechanisms, it would indeed become a formidable force on the web.

What if you don’t want to be tracked?

If you don’t want to be tracked without your explicit approval, I would suggest browsing Facebook in Incognito browsing mode in Chrome, multiple profiles in Firefox or InPrivate browsing mode in Internet Explorer. All these modes will clear cookies and other history data when you close the browser window. So you might not be tracked as efficiently as possible.

I hope Facebook addresses this privacy concern. Facebook, please don’t be evil with our data. I wouldn’t be surprised if Facebook launches a general purpose search engine in the next couple of years!

The free SMS web service, that you have come to love and use, has been updated. You can download for the following languages here:

1. Java
2. PHP

If you are accessing the service through the URL mentioned here, then be rest assured that it will continue to work. Download the latest versions and enjoy!

If you are facing any problems, please do let me know in comments and I will try to address them at the earliest.

I had been using both browsers side by side for a few months now & came to feel that Opera Mini is a lot better for daily use and Skyfire is better for those one off toughie websites that must work with javascript and other stuff enabled.

Here’s an example: Recently, I started accessing my twitter account through Dabr from Opera Mini. The mobile UI rocks and zoom in and zoom out is instant. It happens in the client side. Opera Mini has an intelligent mix of client side and server side operations, whereas, all operations from Skyfire require an active internet connection. At best, internet access from mobiles through GPRS still remains patchy & hence, Skyfire should have that intelligent mix of operations and where possible, operations should be done at the client rather than server.

Opera desktop’s goodness of Speed Dial has arrived on Opera Mini 5. It’s awesome and saves you tons of clickety-clicks, which are irritating on a mobile. The whole menu system has been completely revamped. UI is smooth and fast (which is a downside with Skyfire)!

The best feature of Opera Mini of all is tabbed browsing. That blows away any other mobile browser on the planet. Being fast and loading heavy pages on separate tabs is a pretty awesome thing. By long pressing on a link, you can open them in new tabs inside Opera Mini. Hence, the Dabr + Opera Mini seems to beat any other twitter competition. Saved pages are really saved pages. They can be accessed even when there’s no connectivity.

Recently we had to book tickets to watch a movie at Mayajaal and Skyfire displayed the website amazingly well. Opera Mini suffered there. Similarly, Opera Mini rocks in opening popup windows (when clicked explicitly), whereas Skyfire fails. All in all, if you are going on a long journey with conservative power, Opera Mini is the way to go. Or if you want near desktop experience on your mobile for all websites, then Skyfire is the way to go.

Skyfire Gripes:

1. No tabbed browsing.
2. No landscape view of web pages and videos.
3. Phone heats up after about 15 minutes of usage. Doesn’t ever happen with Opera Mini.
4. Compared to Opera Mini, it is very heavy on battery.
5. No option to logout from your Skyfire account. You have to manually delete the “Preferences” file to logout.
6. The assumption that an active internet connection is always available.
7. Proxy server support and proxy authentication i.e. HTTP code 407. I have been asking this for so long that I’m beginning to feel that this feature won’t come at all.

Opera Mini Gripes:

1. No flash support.
2. Javascript should be supported better.
3. Zoom in to images is dismal. I hope this issue will be corrected when Opera Mini 5 comes out beta.
4. This browser also doesn’t have support for proxy servers and proxy authentication.

What are your opinions on these two browsers? What browser are you using on your mobile phone?

As mentioned in this Webbynode blog post, I happen to be one of the current VIP users having five invites. That’s right… five awesome invites. If you are looking for a VPS with a 15% discount for the rest of your life, this could be your chance to get it.

Post a comment with your email id and I shall send you an invite. First come, first served

Enjoy!

The biggest problem is that, their RSS feed doesn’t give the full content. Everytime new articles show up, I have to visit the website by clicking the link on the RSS feed. It soon got very frustrating.

So, here’s the result – http://feeds2.feedburner.com/DevOperaFullFeed. That link contains the RSS feed for Dev Opera Articles in full. That is, there are no one liners any more. This feed will give you the full content of the articles present on the Dev Opera’s original feed. Subscribe to this feed and live happily ever after