WhatsApp+ [Detail Review]





Hey there everybody,

Today we will review a much loved app called WhatsApp+ (earlier known as WhatsApp plus)

For those who do not know what WhatsApp is :-

WhatsApp Messenger is a cross-platform mobile messaging app which allows you to exchange messages without having to pay for SMS. WhatsApp Messenger is available for iPhone, BlackBerry, Android, Windows Phone and Nokia and yes, those phones can all message each other! Because WhatsApp Messenger uses the same internet data plan that?

You use it for email and web browsing, there is no cost to message and stay in touch with your friends.

In addition to basic messaging WhatsApp users can create groups, send each other unlimited images, video and audio media messages.The first year is available for free as a trial usage, after a year its less that  1 $,believe me its worth it after all it does not even come with ADS

Here is a link to the site, if you need to know more about it.



Now after a while you expect something more from this app, perhaps a new interface may spark up your mood. And lucky for you an amazing android themer called Rafalense ,modified the framework so that we can individually theme it, now is that not good?

Link to rafalense’s  post about whats app plus- click

Link to his pay-pal donation ID-click

Lets begin our journey 😀

To start with,

This app allows you to theme, almost every aspect of your what app

Lets start from the very beginning

1.The first option allows you to check is he has updated the apk file from the app it self

2.Themes-it gives you a option

  • Save your current theme
  • Load a saved theme
  • Download a theme  from some where
  • Share your theme
  • And reset

3.The conversation screen

—> Its basically the header and the conent in the chat like the chat bubble,  send button

4.Main/Chat screen

—>This is the screen that appears when you open whats app

5.Contacts Screen

—>This is bacically the screen which appears when search for your contatcs inside whatsapp

6.Pop-UP notification

—>This option allows you to modify the Pop Up notification that comes when some one buzzes you

7.Media sharing

—>This lets you change/increase/decerease the upload limit

—>Hide play/pause button and more

8.Other Mods

—>This lets you change the notification icon, squared pics, weather or not to show your pic in every chat line,etc


Here are the links to two themes i made

1.I made this for myself (screenies here click)

dowload   the above theme here (click)

2. I made this one for my girl(Screenies here  and another here)

download the above theme here (click)

To apply these themes follow these steps

  1. open whats app +
  2. click your menu button –> PLUS
  3. Themes
  4. Load
  5. it will bring you a file explorer
  6. now navigate to where ever you have download the file
  7. click and restart whats app
  8. and enjoy 😀

Here is the direct download link ,


WhatsApp+ Holo


WhatsApp+ theme collection



  • Rafalense
  • XDA-developers
  • 1cebox for creating this blog this site

Want the latest version of Android?

Want the latest Android version on your phone?
It’s that time of the year again. Google announces the next version of Android with a host of new features, and gets everyone talking excitedly about it. The user breathlessly reads about the new features, and sweats with wondering wether he’ll get it on his brand-new phone. After all, it’s a two-year contract he has signed, so no wonder he will get it, right?
Wrong. There’s a very less chance that he will get it, and it’s not because he does not have the the very top-of-the line flagship model of the company he has bought it from. After Google announces a new version of it’s OS, it is made available after one or two months to the manufacturers so they can release it to their customers as soon as possible. So our user-in-question should get it as soon as after a month, right? But what happens actually? Why do manufactures delay so much in providing an update to their users? Why is it always that all Apple users get an update around the globe, wherever they are, leaving Android users leaving in fury and shame?

The Android fragmentation

The Android diversity
Back in 2010, when Google announced its operating system, codenamed Android, there were not many oem’s who wanted to take the risk of trusting Google and making a phone based entirely off it. There was HTC, and then there were, well none. But Android began to grow at a very exponential rate, and now there are literally hundreds of oem’s making and selling Android devices. So how do the bug guys like Samsung, HTC, Sony, LG differentiate their products from others and make something that truely stands out?
These oem’s have no option but to skin what Google provides them and give their own user interface to it. This is the reason why,lets say, a Samsung phone and an HTC phone, both based on Ice Cream Sandwich, look complety different. If you have seen a nexus device, that’s how the original Android looked like before it landed to the manufacturers.

Skinning is hard
Making Android look how they want is not an easy thing. If you think it’s just a matter of copying a code and replacing it with what Google provides them, you’re entirely wrong. Skinning with their own UI is a tremendous task, and this takes months to complete. After that, they have to ensure that it is bug-free, so the user can actually enjoy instead of spending time solving the problem and cursing the manufacturer. If you are a Galaxy s3 user who recently upgraded to jelly bean, you know the problem of opening the app drawer from the homescreen- the smooth animation of ics is replaced with a hard, un-sophisticated animation if you open the app drawer after a long time. And make no mistake –  the end user is not forgiving. Even small mistakes like this ruin the feel and aesthetics of the device for him, making him hate the oem more and more. So, giving Android their own UI and ensuring that it is bug free is a daunting task, which takes months.

The carrier problem
After months of hard work, when oem’s are actually ready with the update, they have to give it to the carriers(if you have a carrier based phone) to ‘pass certificates’. Carriers will never be fast. And there will be no one to blame except yourself to have bought a carrier based phone. Things begin to take an evil turn if the phone you bought isn’t a nexus phone.

The ‘worrying sick’ problem
What drives these manufacturers to go crazy in dealing with all this hard work, when the updates are free of cost, is that users are becoming aware of technology and knowing that their device isn’t up to date with the latest innovation. The moment Google announces a new OS, forums, threads, blogs get filled with the same thing – which phones will actually be able to upgrade to it. Users search like crazy and hope that their phone will make it to the list. And when their manufacturers declare that their phone wont be receiving an update, users get frustrated – and promise never ever to buy from that manufacturer again. People turn to the absolute last option they have – custom ROMs, and without proper researching, they end with a big paper bill.

The solution
The fact is that – no one can change all this. The one thing, however, that you can do about it is change how you think. You must understand that it is really tough for oems and carriers to co-operate with one another to finally bring up the update to you. Ask yourself this question – does my device serve the purpose for which it is bought for? If the answer is yes, then most probably you don’t need an update. Or if you are the one that must be at the top of the Android version, straight away buy a nexus device. You’ll be ensured a speedy delivery of the updates, delivered straight from Google.

Nexus devices

What do you feel? Reply in the comments section below!

Kernels(Governors, I/O Schedulers)

First off, you all should know that EVERYTHING pretty much has a kernel.

Second, there are a total of about 20-25 Governors in total about now, maybe 21-22.

List that One V currently have

  • 1) Ondemand
  • 2)Conservative
  • 3) Interactive
  • 4) Interactivex
  • 5) SmartassV2 
  • 6) Lionheart
  • 7) SavagedZen
  • 8) Powersave
  • 9) Performance
  • 10) Scary

Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. Effectively, it uses the CPU busy time as the answer to “how critical is performance right now” question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle.

A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle.

Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle.

This is an Interactive governor with a wake profile. More battery friendly than interactive.

Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an “ideal frequency”, and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There’s no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery

Lionheart is a conservative-based governor which is based on samsung’s update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. The governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive

Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.

Sets min frequency as max frequency. Use this while benchmarking!.

Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).

Scary – A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it’s above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.

That’s all for Governors. Now, if you want to read more, you can read on: Here

I/O Schedulers

Q. “What purposes does an i/o scheduler serve?”

  • Minimize hard disk seek latency.
  • Prioritize I/O requests from processes.
  • Allocate disk bandwidth for running processes.
  • Guarantee that certain requests will be served before a deadline.

1) Noop

Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.


  • Serves I/O requests with least number of cpu cycles. (Battery friendly?)
  • Best for flash drives since there is no seeking penalty.
  • Good throughput on db systems.


  • Reduction in number of cpu cycles used is proportional to drop in performance.

2) Deadline

Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.


  • Nearly a real time scheduler.
  • Excels in reducing latency of any given single I/O.
  • Best scheduler for database access and queries.
  • Bandwidth requirement of a process – what percentage of CPU it needs, is easily calculated.
  • Like noop, a good scheduler for solid state/flash drives.


  • When system is overloaded, set of processes that may miss deadline is largely unpredictable.

3) CFQ

Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the ‘parent’ process. V2 of CFQ has some fixes which solves process’ i/o starvation and some small backward seeks in the hope of improving responsiveness.


  • Considered to deliver a balanced i/o performance.
  • Easiest to tune.
  • Excels on multiprocessor systems.
  • Best database system performance after deadline.


  • Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
  • Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.

4) BFQ

Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it’s budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it’s behavior.


  • Believed to be very good for usb data transfer rate.
  • Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
  • Considered an accurate i/o scheduler.
  • Achieves about 30% more throughput than CFQ on most workloads.


  • Not the best scheduler for benchmarking.
  • Higher budget assigned to a process can affect interactivity and increased latency.

5) SIO

Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.


  • Simple, so reliable.
  • Minimized starvation of requests.


  • Slow random-read speeds on flash drives, compared to other schedulers.
  • Sequential-read speeds on flash drives also not so good.

And that be all…. All credits to DroidPhile. Give his thread a look for more.

Understanding Your Android better / Glossary

Have you been in a position in which:

  • you want to show off an application on your phone and your phone refuses to respond
  • you wanted to call/message some one and your phone refuses to help you

and you abuse the hell out of your phone?

Well, I guess what we have all been in that particular situation and then we google out remedies to fix our phone revealing the other side of the medal: Rooting. Curiosity is known to humans so you just click on the first and second link, download a file and run it and 2 things of the following happens:

  • You were lucky enough to root it without screwing it.
  • Boom your phones screwed, it wont start.

So now you’re searching for a solution for this problem (unless you are the kind of person who is willing to spend a ton of cash to replace the motherboard)

Now for people searching for a solution, usually end up putting a question in the forums. In there, people post all these terms which you have no idea off, and when you ask them they get pissed (well i am one of them :p)

So i created this post with all  the terms you will ever need to know about rooting and a brief explanation about them, so that next time when some one says you have to flash your phone you wont ask whats flashing.

The Main Question- what is ROOTING

Android is based on Linux. On Linux and other UNIX-like operating systems, the root user is equivalent to the Administrator user on Windows. The root user has access to the entire operating system and can do anything. By default, you don’t have root access to your Android device(to prevent us from screwing with our phone), and certain apps won’t function without root access.

With root access, you can disable the bloatware(Samsung fun,htc skins,Motorola stuff,etc) that comes with your phone, manually deny app permissions, run a firewall, access the entire file system, or tether your device, even if tethering functionality has been disabled. You’ll find many apps that require root access in the Google Play store ,Even if they install on your unrooted phone they won’t function until you root your device.

The Most Basic Terms(they are in alphabetical order)

ADB:Android Debug Bridge

It is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:

•A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
•A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
•A daemon, which runs as a background process on each emulator or device instance.


A Linux-based operating system for mobile devices(smart phones).Versions are alphabetically codenamed after deserts:- Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich, Jelly bean.


Android application package file (APK) is the file format used to distribute and install application software and middleware onto Google’s Android operating system.


This small program’s only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.Bootloader increases the security of the phone preventing us from rooting, although companies like HTC provide a devloper site to help us unlock the bootloader


When your system recycles over and over without entering the main OS.(when u cant get pass the welcome screen)


Independent developers who like to customize their devices beyond the standard options provided often tend to release their labor for the rest to enjoy, in form of custom ROMs,etc


Cache is used by the central processing unit of a device to reduce the average time to access memory. The cache is a smaller, faster memory which stores copies of the data from the most frequently used main memory locations. As long as most memory accesses are cached memory locations, the average latency of memory accesses will be closer to the cache latency than to the latency of main memory.

Dual Core

A dual core processor is a central processing unit (CPU) that has two separate cores , each with its own cache. It essentially is two microprocessors in one. This type of CPU is widely available from many manufacturers. Other types of multi-core processors also have been developed, including quad-core processors with four cores each, hexa-core processors with six, octa-core processors with eight and many-core processors with an even larger number of cores.


This is The Android platform’s virtual machine.The Dalvik VM is an interpreter-only virtual machine that executes files in the Dalvik Executable (“.dex”) format, a format that is optimized for efficient storage and memory-mappable execution.

Dalvik Cache

Writable cache that contains the optimized bytecode of all apk files (apps) on your Android device. Having the information in it’s own cache makes applications load faster and perform better.(its where the apps store their stuff)


Short for “force close,” meaning an app that has crashed.(like when firefox closes unexpectedly)


A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:

  • fastboot reboot (reboots)
  • fastboot devices(displays the devices connected)
  • fastboot flash boot boot.img(installs the kernels)
  • fastboot flash recovery recovery.img (installs the recovery)
  • fastboot erase cache (Erases the cache partition)


It basically means installing.The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system


It’s mainly responsible for checking and initializing the hardware and starting the phone’s software. It can also be used for flashing official software releases, as well as a few other things. HBoot can be compared to the BIOS on a computer.

Kernel(a link between the hardware and OS)

A kernel is a layer of code that allows the OS and applications to interface with your phone’s hardware. The degree in which you can access your phone’s hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.


Nandroid is used to backup or restore backups from Recovery.Its a must for first time users,Cause if anything goes wrong u can just restore it.


The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the Data partition of the phone, or perform an update using an update.zip file on the root of the microSD card. It is common  to flash a patched Recovery image, such as TWRP or ClockworkMod Recovery. This allows you to run Nandroid backup from the device, and flash modifications, such as files to the device, essentially becoming a means to install software to the device. Recovery mode is separate from ‘normal’ mode, and can be entered by holding down home whilst turning the phone on.


A ROM is a modified version of Android. It may contain extra features, a different look, speed enhancements, or even a version of Android that hasn’t been released yet


ROM Upgrade Utilities(RUU) (for HTC phones) and System Boot Files(SBF) (for Motorola phones) are files direct from the manufacturer that change the software on your phone. RUU and SBF files are how the manufacturers deliver your over-the-air upgrades, and modders often post leaked RUU and SBF files for flashing when the updates haven’t been released yet. They’re also handy when downgrading your phone, if a rooting method isn’t available for the newest software version yet. You can flash RUUs right from your HTC phone, but Motorola users will need a Windows program called RSD Lite to flash SBF files.


On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be : root, administrator or0 supervisor.


S-On:Security on,means no access to the phones operating system.

S-Off:Security was exploited,now have access to the operating system.

Ok guys, these are the most basic terms you should know about before you go ahead and root your phone. If you have doubts, questions, ask in the comments section below!

Suggest this BLOG to other users if you found it useful. Thank you!

Most credits go to

  • Google
  • Wikipedia
  • How to geek
  • Lifehacker
  • Xda forums

HTC One V – Our day to day toy

                                                                                                  HTC One V

The HTC One V, known as HOV, features a unique curved-chin design that makes it easy to hold and a distinctive accessory to your life. But don’t be deceived by its compact size. Like all One series phones, it packs an impressive list of features including a best-in-class camera.

Camera- there’s no delay in the camera’s loading time and it also comes packed with a zero shutter delay also added to the awesomeness is the 720p HD video recording with a 5mp camera!

Sound- HOV comes with the mighty and powerful feature called ‘Beats Audio , so everything you listen on your phone, be it music or some random youtube video it all comes roaring with the powerful bass effect.

Design – The One V comes with a uniquely curved chin design and a metal body available in black, silver, brown colours and with a 3.7 inch touch screen – it’s all together a fantastic phone.

So my fellow bloggers, any question about the phone, ROMs available, rooting, you can ask in the comments section; all your queries will be answered as soon as possible by our team.

A simple debriefing mission

I think it is fair to say that we all heard of Android by now, sure as hell we already know what Google is and its products. From the world’s #1 Web search engine to world’s #1 OS for smartphones in just a couple of years. ANDROID!

If you are living under a rock and you didn’t understand what is all this Android stuff, have no fear, I will try to break it down for you in the next few lines. Here are a few facts about Android:

  • Android is a Linux-based operating system (OS), originally developed by Android, Inc. – a company which was later on bought by Google.
  • The first Android phone was sold in October 2008, the HTC Dream.
  • Android is an open-source OS, Google releasing the code constantly, under the Apache License.
  • Android had a world-wide smarth phone market share, with 75% points, back in 2012, with 500 millions devices activated in total.
  • Android, Inc. was founded in October 2003 by Andi Rubin, Rich Miner, Nick Sears and Chris White.
  • Google took Android, Inc. into custody on August 17, 2005. Key employees of Android, Inc. remained at the company.
  • Major releases are named in alphabetical order after a dessert or sugary treat (i.e version 1.5 was Cupcake, 1.6 was Donut etc.).
  • First version of Android was 1.5 a.k.a Cupcake.
  • Current version of Android is: 4.2.1, the very well known “Jellybean”.

Our team consists in Android enthusiastic fans, who are daily at the task to enjoy what Google created at first, but carried on by millions of people all over the world.

We are requesting all passengers to join us as we discover the Android experience at its finest!