Oh and yes, if you’re not following me on twitter yet, you’re losing out! Follow me @kalpik

Since Voodoo for Froyo is out, here I’ve packaged Doc’s JP6 rom (full, with fixed Swype) with Voodoo and Circle Battery Mod Version D.

Changelog:

19th Oct 2010: Initial release with Voodoo Pre3

20th Oct 2010: Updated to accommodate Voodoo Pre4 (which contains fixes for some rooting issues, and enables logging by default). For those of you who flashed the previous version, don’t worry, the rooting issues were already fixed in the ROM. So there is no need to update. For those who still want to update, you can get Voodoo Pre4 from here, and you will have to flash it via Odin as PDA, with no PIT and re-partition un-checked.

20th Oct 2010: WOOHOO! Do I have some good news for you! Got 2e recovery working with Voodoo! Now you can use Clockworkmod with this ROM New users follow the instructions as usual. Old users who are upgrading from any previous version have to do some extra steps as they don’t have the 2e recovery:

a) Take proper backup of your apps etc with Titanium Backup.

b) Disable Voodoo by creating a folder named “disable lagfix” inside the “Voodoo” folder in your internal sdcard (case matters), and then rebooting. Reboot will take time as Voodoo is disabled.

c) After the phone boots up, shutdown the phone, and flash the CFRoot Kernel by ChainFire for JP6. Download the kernel from XDA or from here. Flash the tar file as PDA with Odin (no PIT needed and don’t check re-partition).

d) After this you can download the updated ROM package from below and proceed as usual

Pre-Requisites:

1. Disable Voodoo if have it installed (create a folder named “disable lagfix” inside the “Voodoo” folder on your internal sdcard and reboot).

2. Make sure you’re running Eclair firmware (if you’re on Froyo, make sure you have the 2e recovery).

3. Make sure you have a backup of your /efs (not mandatory, but highly recommended).

4. This ROM will delete all your apps and data (not the stuff on the internal sdcard). So make sure you have proper backups (I recommend Titanium Backup)

Installation Steps:

1. Download the packaged ROM from here, and put it on your internal sdcard.

2. Download clockworkmod recovery from here. You need Clockworkmod, this won’t work with stock recovery.

3. Rename the clockworkmod recovery file to “update.zip” and put it on your internal sdcard.

4. Before shutting down your phone, make sure you remove the “disable lagfix” folder from the “Voodoo” folder.

5. Shutdown phone, wait for it to power down, then boot the phone into recovery mode (press volume up, keep it pressed, then press home button, keep it pressed, then press power button, keep it pressed until you see the Galaxy S screen. Release all three buttons when you see it).

6. Select “apply sdcard:update.zip” (use volume rocker to move up and down, and home button to select). Clockworkmod recovery will boot now (you may have to do apply update.zip twice for Clockworkmod to show up).

7. Once in Clockworkmod, select “install zip from sdcard” (use volume rocker to move up and down and the back button to select).

8. Select “choose zip from sdcard” and then select the ROM zip package. Choose yes then.

9. The update will start (will take some 5 minutes) and during the flashing you will see some strange big characters on the screen, don’t worry, that’s normal. After the process finishes, you will be dropped back into Clockworkmod recovery. From there, choose go back, and then reboot phone.

10. The first boot will take some time as the ROM will deodex, and also Voodoo will be applied.

Things to note:

1. Voodoo kernel does not have a 2e recovery as of now. Will update the package once it does.

2. You will see a small screen corruption when booting the phone. This is a known issue with Voodoo as of now.

Any questions? Shout out in the comments

http://afup.broadbandforum.in/

By the way, Airtel told me that they will resolve my complaint by 1:30 PM today and I haven’t heard from them yet. Will keep this group posted on the responses I get from them.

In the meantime people, let’s get this to the mainstream media and tell them how Airtel is out to screw their own customers. They won’t even flinch till someone starts talking bad about them and till the shareholders take notice.

So here are some suggestions:

• If you have a blog, then blog about this
• Join the Facebook group (there may be some issues for now about the Join link but they’ll get fixed)
• Write to all the India specific tech blogs and sites that you know of about this – Tech 2.0, Chip, TechTree, TechShout, PC World etc
• Log complaints with customer care about this and tell them that the customers were not apprised. If they use the word “TRAI” ask them for the specifics – Article, clause, URL etc of the TRAI ruling if any – just don’t let them use the word TRAI and get away with it

Some points to remember:

• We need “bandwidth huggers” who can get the best from the internet to spurn the economy in India by sharing the ideas that they find on the internet – if you can’t experience the best, how do you spread the word?
• Take the example of Miro HD Video Player | Free internet tv and video podcast player. which promotes free Internet TV with an abundance of useful information for Indian audiences
• Take the example of a household with 2-4 users of broadband on 1 Wifi connection who would use their unlimited connection for completely legitimate purposes and still hit the cap in 10-15 days
• Take the example of people who download various Linux distros via torrents to distribute them to people who don’t want to pirate a Windows and yet get a working operating system like Ubuntu for free
• Take the examples of Indian tech startups like Rajshri.com and In.com who are providing free video content on their sites to increase demand for their products and hence churn the economy

What Airtel is doing goes against all of the above. Yes, we might have alternatives but before that we need to know whether the culprit here is TRAI or Airtel or both. Till then, this needs an open debate before the TRAI implements something without consulting the consumers and sleeping with devils like Airtel.

1. Download the fixed meanwhile library (64 bit only) from here.
2. Install it using pacman:

pacman -U meanwhile-1.0.2-1-x86_64.pkg.tar.gz

3. Install the Arch Build System:

pacman -S abs

4. Run abs so that it can build a repository tree (kinda like portage in Gentoo):

sudo abs

5. Copy the pidgin directory of abs to /tmp:

cp -r /var/abs/extra/pidgin /tmp

6. Go to /tmp and open the pidgin PKGBUILD in nano:

cd /tmp/pidgin
nano PKGBUILD

7. Go to the “build()” section and make sure you remove “–disable-meanwhile” from the configure options. The line should look like this:

./configure –prefix=/usr –sysconfdir=/etc –disable-schemas-install \

8. Make the package:

makepkg

9. Install it:

pacman -U pidgin-2.5.3-1-x86_64.pkg.tar.gz

That’s it! Now you should have sametime support in Pidgin Remember though, you will always have to compile pidgin yourself whenever a newer pidgin version hits the Arch repos.

P.S. For those of you who want to compile a fixed meanwhile on i686 (32 bit) system, follow the instructions here.

Archlinux just released Kernel 2.6.28 into it’s [core] repo a few days back, and since then im in a dillema whether i should switch to EXT4, or be content with my current filesystem, JFS. Switching to EXT4 means that I will have to re-install Arch, once the new installer CD with EXT4 support comes in (which should be soon). And configuring Arch _exactly_ the same way as it is right now will be almost impossible! I mean with all the small tweaks and configuration changes i’ve done over one year now! Will be a HUGE task! And nowdays, i really dont have time to mess with something that’s working absolutely the way i want it to work.

Oh and yeah, while roaming around in Arch forums, i found this. It certainly does not give me a good feeling about EXT4! Therefore, im thinking ill wait for a while before jumping on the EXT4 bandwagon. But that leaves me with one thing less to mess around with But then again, i guess its OK, since KDE 4.2 is just around the corner and im hearing lots of good things about it! THAT can be my next test subject

I tried out the Alpha on Archlinux. It was working great with much more stability and lesser CPU usage, but unfortunately, it crashes Firefox for me, when i open Gmail. So, i have gone back to Flash 10 x86 + Nspluginwrapper for now. Will keep trying it as and when they release newer versions.

Download Flash 10 x64 Alpha.

Edit: The plugin works perfectly for me now! Not crashing the browser anymore