Friday 13 April 2012

Top 10 Anti-viruses 2012


#1. Bitdefender Antivirus Plus

Windows 7 Performance
Protection Score----100%
Repair Score---------83%
Usability Score-------92%
Windows XP Performance
Protection Score----100%
Repair Score---------92%
Usability Score-------92%
Source: malwaredatabase

#2. Kaspersky Antivirus

Windows 7 Performance
Protection Score----100%
Repair Score---------75%
Usability Score-------83%
Windows XP Performance
Protection Score----92%
Repair Score---------92%
Usability Score-------83%
Source: pandasecurity

#3. Panda Antivirus Pro

Windows 7 Performance
Protection Score----83%
Repair Score---------92%
Usability Score-------83%

Windows XP Performance
Protection Score----92%
Repair Score---------83%
Usability Score-------83%
Source: ultimate10

#4. F-Secure Antivirus


Windows 7 Performance
Protection Score----92%
Repair Score---------83%
Usability Score-------83%
Windows XP Performance
Protection Score----92%
Repair Score---------83%
Usability Score-------83%
Source: softwareindustryreport

#5. AVG Antivirus

Windows 7 Performance
Protection Score----83%
Repair Score---------58%
Usability Score-------92%
Windows XP Performance
Protection Score----92%
Repair Score---------75%
Usability Score-------50%
Source: present-technology

#6. Avast! Antivirus


Windows 7 Performance
Protection Score----83%
Repair Score---------42%
Usability Score-------83%
Windows XP Performance
Protection Score----83%
Repair Score---------67%
Usability Score-------75%
Source: gdatasoftware

#7. G Data Antivirus


Windows 7 Performance
Protection Score----92%
Repair Score---------75%
Usability Score-------67%
Windows XP Performance
Protection Score----92%
Repair Score---------67%
Usability Score-------67%
Source: softcns

#8. BullGuard Antivirus


Windows 7 Performance
Protection Score----75%
Repair Score---------50%
Usability Score-------75%
Windows XP Performance
Protection Score----83%
Repair Score---------58%
Usability Score-------75%
Source: blogspot

#9. Avira Antivirus Premium


Windows 7 Performance
Protection Score----67%
Repair Score---------67%
Usability Score-------75%
Windows XP Performance
Protection Score----58%
Repair Score---------75%
Usability Score-------67%
Source: computercaredubai




#10. Eset NOD32 Antivirus


Windows 7 Performance
Protection Score----58%
Repair Score---------42%
Usability Score-------83%
Windows XP Performance
Protection Score----67%
Repair Score---------58%
Usability Score-------92%




Source: http://rexrider.hubpages.com/hub/Top-10-Antiviruses-2012

Thursday 12 April 2012

Why the Galaxy Nexus uses OMAP instead of Exynos

OMAP Galaxy Nexus 
The rumors seemed strange from the start — a Samsung phone with a Texas Instruments processor? Last year’s Nexus S was a Samsung device, and it was Samsung through and through with a 1GHz Hummingbird system-on-a-chip (SoC). Now here we are looking at the new Google flagship, the Galaxy Nexus, and it has a TI OMAP4460 on the inside. Why not Samsung’s own Exynos part?
There area few factors at work here, but the most important one is related to how the Nexus program works. Back when Google announced the Motorola Mobility buy, the company finally revealed a bit about how it operates the Nexus program. This was done in an effort to show that Motorola won’t be getting preferential treatment.
According to Google’s Andy Rubin, each year Google selects a device maker that it wants to work closely with on the next Nexus phone. But it’s not just the OEM that is involved — Google decides on components in the phone individually. Unlike other devices, Google gets it way with the Nexus.
So the team that will eventually “huddle together in one building” will be made up of the OEM, and several component makers that supply things like the SoC and radios. Then 9-12 months later, a little Nexus is born. Last year, Google went with Samsung for the device itself, and the SoC. This year, Google has decided to put Texas Instruments on the processor team.
Galaxy Nexus LeakSo now the OMAP4460 is getting quite a lot of scrutiny, even though it isn’t exactly a new chip. This dual-core SoC is clocked at 1.2GHz, and uses ARM Cortex-A9 architecture, just like the Exynos. That’s not a problem, but the older GPU, the PowerVR SGX540 is. We were hoping for a step up in the graphics department.
Why did Google choose the OMAP for its new Nexus? Well, it might not live up to the high graphical standards set out by the iPhone, but it is a solid chip in its own right. The OMAP4 platform makes use of an additional hardware accelerator called IVA 3 that makes encoding and decoding HD video a snap. The Galaxy Nexus has an HD screen, so this hardware focus on video is a big plus.
Google engineers were likely also drawn to the OMAP for its use of a dual-channel memory controller. Android’s multitasking system means that data is constantly being moved into, and out of, active memory. This is definitely a strength of TI’s OMAP parts.
Google will be developing the new version of Android on OMAP for the next year, so be ready for more devices based on this one. Much like the Nexus One started the Snapdragon revolution two years ago, this could be TI’s time to shine. If that OMAP4460 starts looking old and tired to OEMs in the coming year, there is always the upcoming OMAP4470 (which is armed with the much-newer and faster SGX544 GPU) to maintain compatibility and increase performance, too.

Why OEMs need months to deliver Android updates to your phone

Android update facts

Share This article

For Android OEMs, getting a new version of the operating system onto devices can be a multi-layered endeavor fraught with peril. It’s not as easy as picking up the code from Google one afternoon, and pushing updates out the next. There is a significant amount of software development, testing, and certification to go through. Both Sony Ericsson and Motorola have released some details on the process, giving us a look at how Android gets from Google, to OEMs, to carriers, and ultimately to you.

The code drops

The whole process starts when Google drops the open source code into the Android Open Source Project (AOSP) repository. This usually happens around the time that the new Google experience device (that’s the Galaxy Nexus this time) is released. OEMs have to take that code, and integrate it with the in-house code trees to begin work. The only exception to this is the hardware partner for the official Google experience device, which gets the code early and works closely with Google. For the last two years, that was Samsung, and before that it was HTC.
The first order of business according to both companies is to start optimizing the Hardware Abstraction Layer (HAL). This is the software layer in Android that gives the software access to device hardware. In the case of Android 4.0 Ice Cream Sandwich, Google used TI OMAP as the template for the operating system so many manufacturers have to replace the HAL.
Android Open Source ProjectSony Ericsson, and indeed most OEMs, rely on a fairly consistent hardware design across a range of products. Chips are usually sourced from the same makers, and the internals reuse many smaller parts. Sony Ericsson uses Qualcomm’s Snapdragon processors in phones, so a new HAL is required. At least its consistent design saves some time and will allow the company to update all 2011 phones.
Motorola is currently straddling both Tegra and OMAP-based products, so its task could be more complicated. The newer OMAP devices like the Droid Razr and Bionic could get preferential treatment because of easier development. In fact, Motorola’s OMAP devices are the only products it has confirmed will get Android 4.0. Users of the Photon 4G or Droid X2 could have a longer wait on their hands.
All OEMs also have to contend with small differences in various other hardware modules like audio, WiFi, and Bluetooth. The HAL will need changes on a per-device basis taking into account different form factors, screen sizes, and specs, too.

OEMs tweak and test

The next order of business is a bit more controversial: OEMs start changing Android to suit the needs of carriers and other partners. Patches, custom interfaces, and other miscellaneous changes are made, and the resulting software image is tested. Sony Ericsson went to great pains to point out that many of the internal patches it develops are useful for the Android platform in general, and it contributes those back to the AOSP.
All OEMs have to do extensive internal testing after making changes to the Android platform. A huge concern on a multitude of devices is battery life, and this is the phase to test that. Quite a few of the changes made to localization and features have the potential to turn out buggy and damage power efficiency. The carriers of course want to do network testing, which can occasionally root out still more bugs.
After what is ostensibly the final code has been internally tested, it sometimes has to be certified by regulatory agencies. The device will of course have been certified by regulators in various nations around the world prior to the original release, but sometimes new inspections are required. Any time software changes the function of a wireless chip, for example the Bluetooth stack in Android 4.0, that component needs to be re-certified, adding additional delays. Compliance with hardware standards may also need verification.

The rollout

Android UpdatesThe act of rolling the update out will vary greatly depending on the device and the carrier branding, if any. Motorola prefers to use a small group of testers to sweep for bugs one more time, then send the update to a group of a few thousand regular users. This is called a “soak test.” The manufacturer probably has dozens of test devices, but there is no way it can test every possible combination of software and settings. More than a few updates have been pulled back after a disastrous soak test. If all goes as planned, the update is released, and everyone can rejoice.
The entire process is a much more tangled web than we would have expected, and remember that OEMs have to do this for every device that gets updated. Sticking to a single hardware platform like Sony Ericsson or HTC has will be of help in getting all devices up to date. Motorola might leave some phones from the first half of 2011 behind for this reason.
Trying to get official word on the fate of one device or another in respect to updates can be nearly impossible, and this is why. The process is long and complicated. OEMs simply don’t want to say the wrong thing, and have to backtrack later. One component that is found to be non-compliant during testing can set things back dramatically.
These new details, especially Sony Ericsson’s forthrightness, help explain why the process takes so long. Hardware differences among different OEMs, and even different devices made by the same OEM, can require unique software builds. Certifying an upgrade takes time as well; apparently longer than actually building the software does. Add to that the lengthy carrier testing phase, and its no surprise that custom ROM makers can get updates out faster. They get to skip the more tedious bits.

Screenshot Tour of Android 3.0 Honeycomb, Built for Tablets

Google gave us a glimpse of Android 3.0 Honeycomb earlier this year, but today they released more details on the upcoming OS. Here's a look through what we can expect. Spoiler alert: It's awesome, and it fixes many of Android's biggest annoyances.

The Tablet UI

The biggest change in Android 3.0 is the general layout of the UI. Since it's built specifically for tablets, you have much more space on your home screen for icons and widgets. This is a pretty stark contrast to the iPad, which just enlarged the iPhone's 4x4 grid with big, spaced out icons—as you can see in the screenshot above, you actually have a much denser grid than you would on an Android phone, meaning you can pack a whole lot of stuff into one home screen.

The Notification Bar

The notification bar has been moved to the bottom of the screen, and they've added a few navigation buttons to it that seem to take the place of the capacative hardware buttons we all know and love on our Android phones. The three buttons, from left to right, are Back, Home, and Recent Apps. The new recent apps window is pretty handy, taking advantage of the extra space to show you the current state of each running app.

The Home Screens

The home screens themselves are pretty similar to regular Android as far as functionality—you can add app shortcuts and widgets wherever you want, swipe between five different screens, and expand your app drawer to access anything not already on the home screens. That said, the entire thing has this new 3D look to it that's really awesome (which we caught a glimpse of in our first look). As long as the hardware can keep up with the new UI, it'll be pretty awesome (we all remember how laggy the original Motorola Droid was).

The Action Bar

Screenshot Tour of Android 3.0 Honeycomb, Built for Tablets
Probably the most welcome change in the new UI, however, is what Google is calling the Action Bar. In every application, the top bar is reserved for contextual options, navigation, or other buttons. The Email app, for example, has a new message button and a refresh button at the top. When you select a message, that action bar changes to display a move to folder button, a mark as read button, a star message button, and a delete button. Of course, it also has dropdown menus for any buttons that overflow off to the side.
Why is this so awesome? These are the kinds of buttons that, on the 2.0 cycle of Android, are usually buried in menus that you access with your phones Menu button. Now, instead of having to hit Menu (and God forbid a "More" button), those options will be available right at the top of your screen. Really, this is one of my biggest complaints about Android, and it makes me wonder why we don't have this action bar in 2.x, too.

Keyboard and Copy/Paste

The new soft keyboard is an improvement over the iteration we're all familiar with, including larger, reshaped keys for easier targeting. What's cooler is that it also includes some keys we're more familiar with on full keyboards, like Tab, which will make us desktop users more comfortable.
Screenshot Tour of Android 3.0 Honeycomb, Built for Tablets
Copy and paste on Android has never been the most friendly feature, but 3.0 takes a step in the right direction by making it a much faster affair: just long-press on any text and it will select that word. From there, you can drag the selection area to include more text. The action bar will also show Select All, Cut, Copy and Share buttons while you're selecting text too, which is fantastic (seriously, why isn't that action bar in Android already?). Overall, working with text in Android 3.0 is going to be a much more pleasant experience.

Tablet-Optimized Core Apps

Screenshot Tour of Android 3.0 Honeycomb, Built for Tablets
There aren't any Google apps in the SDK (like Gmail or Google Talk), but the non-Google core apps like the Browser, Camera, Contacts, and Email have all been updated to more efficiently use the extra space you'll get with a tablet. The browser has tabs built in (hallelujah!), bookmark syncing with Chrome (double hallelujah!), Incognito mode (ahem), and automatic sign in to Google sites using the Google account tied to your device. I don't need to tell you guys how cool all these features are. These are usually things we have to download an alternate browser for, both on Android and iOS. This is a big step forward.
Screenshot Tour of Android 3.0 Honeycomb, Built for Tablets
The other core apps aren't quite as revolutionary, but still nicely redesigned. The camera app is definitely cool (see above), and the Contacts and Email app are basically two-pane versions of the same apps we already know and love—not unlike the difference between the iPhone and iPad versions of Contacts and Mail in iOS. They're a good use of space, but nothing revolutionary (unless you're counting the aforementioned action bar that I still can't get over).




Android 2.4 coming April, leaving 2.3 dead on arrival - not Ice Cream

Viewsonic has exclusively told Pocket-lint that its recently announced ViewPad 4 smartphone will be packing Android 2.4 when it launches in April. And the update will produce an OS that has the ability to work with Honeycomb apps.

The news, aside from confirming the new handset’s release date, confirms that Android’s 2.4 OS will be out earlier than we previously expected.

And there’s a reason for that.

According to our source, the release date of version 2.4 has been brought forward to ensure that dual-core apps designed for Honeycomb (v3.0) will be able to work with single-core devices running v2.4.

Currently, our man on the inside says that’s not possible with version 2.3 (Gingerbread) hence the need to push to the next iteration and version number, but not change the name. It's most likely to be one of the main reasons we’ve yet to see any major manufacturer gunning to get Android 2.3 handsets out there.

“It’s to ensure compatibility with dual-core apps,” our agent explains before adding that “it will still be called Gingerbread.”

Wait, what?

That’s right, in a move that shows there is some kind of cover-up of the mistake of the lack of Android 2.3 devices on the market (aside from the Nexus S) 2.4 will still be called Gingerbread, as the only new feature it adds will be this ability to support dual-core apps on a single-core device.

This chimes with sources talking to Phandroid on Friday that stated:

"We’ve just gotten word from a trusted source that Google has begun building a new branch of code - being called GRI17 (Gingerbread post-Honeycomb, aka “Ice Cream”) - that aims to bring some of the new elements found in Honeycomb over to phones."

However, we now understand that not to be Ice Cream. Our source at Viewsonic tells us that he believes Ice Cream to be 3.1, making us believe that Google intends to spilt the 2+ and 3+ OS variants going forward.

Certainly, Viewsonic is excited:

“This latest update to the ViewSonic Europe ViewPad range will position the device as one of the first multi-media handsets to be supported by Google’s new operating system,” our man exclusively told us.

Aside from Android 2.4, the ViewPad 4 will pack flash 10.1, have HD 720p video recording, playback, upload, and mini-HDMI 720p display output. There’s a 5-megapixel auto-focus camera, Bluetooth 2.1 and 802.11 b/g/n wireless connectivity. You’ll also get a 4.1-inch screen for your trouble.

Google Ice Cream landing in time for the summer

Google Ice Cream landing in time for the summer. Phones, Mobile phones, Google, Android 2.4, Ice Cream, 0
Google will release the next version of its mobile phone operating system, Android 2.4, in the summer, Pocket-lint has learnt.
According to multiple sources familiar with the matter, Android 2.4, otherwise known as Ice Cream, is set for a June/July timeframe this year with an announcement expected at the company’s IO conference at the beginning of May in San Francisco.
The news comes as a Sony Ericsson Xperia Arc, supposedly running the yet-to-be-announced mobile OS, was found on the show floor at CES.
"It was actually a mistake. We had different prototype versions in different units and somewhere the software labelling got corrupted with 2.4. It isn’t 2.4 it’s 2.3. It’s a labelling error in the software," Steve Walker, acting head of global marketing at Sony Ericsson told Pocket-lint in a one-to-one interview. "Of course we are always prototyping new features in the products, and somehow we’ve managed to label the android version as apposed to our own version of software."
Although Sony Ericsson has told Pocket-lint that this was owing to a software corruption issue on the device rather than it actually running Android 2.4, our sources have confirmed that the new OS is coming, and coming in the not-too-distant future.
Ice Cream follows on the back of the launch of Donut (D), Eclair (E), Froyo (F), Gingerbread (G) and Honeycomb (H) with the next iteration in the list of releases Ice Cream (I).
Google has previously said that it was slowing down the timeline for Android, focusing on two major updates a year. With Gingerbread announced in December and Honeycomb in January, a June timeframe fits that ethos.
While those good at maths will realise that it does bring up the tally to three in the last 6 months, many experts we’ve talked to at CES in Las Vegas believe that Honeycomb, although not officially the company’s tablet OS, is unlikely to make it onto mobile phones, instead staying on devices like the Motorola Xoom, again giving us more pieces of the jigsaw to place.
Unfortunately, when we asked our sources to go on the record, there was more seat shifting than on the Underground at rush hour.

Next iteration of Android to be 'Ice Cream Sandwich'


Ice cream sandwiches make for a delicious Android summer treat.


During a recent interview with TechCrunch, Android's head honcho Andy Rubin let slip that the name of the next release of the mobile platform will be Ice Cream Sandwich.

Once rumored as Ice Cream, Ice Cream Sandwich will follow OS 3.0, or Honeycomb, which landed on its first device, the Motorola Xoom, last week at CES. Availablity is uncertain, but one theory suggests that Ice Cream Sandwich would arrive as OS 2.4 later this summer.

The timeline makes sense, but the version number leaves me scratching my head. As to why Google would backtrack on the number isn't clear at this point. If anything, it would leave a lot of people confused and add fuel to the fire of fragmentation. Android 3.0 clearly is optimized for tablets, but it should make its way onto smartphones as well. Google has done a terrific job of letting developers see how the mobile OS has evolved, providing a platform versions chart among other tools.

I foresee Google officially announcing Android 3.0 when the Moto Xoom is ready to roll, which should be over the next two months. Ice Cream Sandwich then could make its debut in the summer, or perhaps in May at Google I/O. Regardless of when it does show up, Google certainly shows no sign of slowing release cycles down to around one per year.

Monday 2 April 2012

Using Blogrush to Turbocharge your blog traffic

All of us bloggers are always running after ideas and new tips to get more traffic to our blogs. This traffic is the prime reason why we bust our backs day in and day out writing new posts everyday so that someone somewhere reads it and appreciates it. The more people read it and appreciate it we all get a kick out of it (at least I do). That this leads to a small profit to us is a small matter...

Every day I scan the net for new ways and means to get this elusive traffic and every day I am looking for more. Internet Marketing Guru John Reese has come up with an excellent tool just what I have been looking for all this time. Its called Blogrush, and what it basically does is that when you add this small Blogrush widget on your blog, you will get to see a list of posts posted on the blogs by other Blogrush users. The system works on the principal of reciprocality. If you give a page-view of 100 to the Blogrush widget, then your blog post title will be visible on the same widget in 100 other Blogrush user pages.

This gives an enormous visibility to your blog as well as you benefit from the affiliate program of the system. This widget shows the first 40 characters of your post titles, therefore writing good titles within 40 characters are of the essence if you want good traffic from the Blogrush network.

Using Yahoo Answers to Generate Traffic


Another great way to generate a traffic surge is to use this free service from Yahoo. This involves people asking questions about various fields and then experts in those fields answering them. Fairly simple isn't it? But it presents a unique opportunity to get free traffic to your website/blog.

The process is very straight-forward. You need to have a yahoo account and then you choose a category of your choice where you think you are an expert or at least for which you can answer questions from newbies or other people looking for answers. There are many categories to choose from and you will definitely find a category that suits you.

After this you should wait to get questions from the other users of the service and prepare to give solutions to their problems. While answering give logical answers to the queries and try and satisfy the person. The thing you need to do here is to add a link to your website/blog in this answer and lo behold you have a free link to your site from Yahoo Answers. Now the trick here is to be the early bird and answer a question before other experts answer it. This gives you more exposure and increases your reputation.

If your answer is fairly good other readers will be inclined to click on your link to know more about you and your work. This will further give a booster dose of free incoming traffic.

So go ahead and start answering questions - you never know that helping somebody might actually give you some real Karma points...You might earn something also.

If you like this post then please do leave your comments and you can also subscribe to the RSS feed that will inform you when I update this the next time.

Article Source: http://adsensemastertips.blogspot.in/

7 Steps to Create Scannable Content



One thing you must keep in mind while putting up content online is that the online reader is very finicky about what he or she wants to read. If your post is quite lengthy and deals with an arcane subject, then it is quite possible your reader might dump you in between.

This calls for making your content tailor made for such readers. In 16% average web users actually go through every word of what you have put down, rest scan your page keywords of interest and only read the relevant sections that are of interest. So I present today some measures to take to keep such readers happy and not lose their interest.
1.     Make Lists: Always try and present your facts and figures in list form. If you have a bunch of things to tell your audience then it is advisable that you list them out in numbers and make headings of each point, much like how I am presenting these points to you right now. Therefore avoid putting your text in lengthy essay form and always favor bulleted lists instead.
2.     Bold and Italized: Wherever you are referring to important points take special care to either italize the text or make it Bold. This grabs the attention of the reader and if the topic of discussion is of interest to him then he wont go anywhere before reading it fully.
3.     Headers: Structure your post body so as to include headings and sub-headings to stress upon key areas of the topic. This will ensure that all points being covered in your article will be seen by the visitors and will not remain unread.
4.     Graphics: It is said that a picture says a thousand words and here too if your article uses an image or a graphic to illustrate a point then it is always better. The picture will attract the attention of the reader and the words will deliver the whole story.
5.     Borders: You can enclose certain key points and sections within borders to stress importance.
6.     White Space: Always leave ample space around your article and do not try to fill up all the page real estate. A fully filled up page gives a feeling of claustrophobia to the reader and the empty space give a feeling of freshness to the reader, give it to him.
7.     Keep it short:Always keep your points short and if required break them up in small parts. Also place these points in separate paragraphs.
I sincerely hope that the above points will sure help you to create such content that will attract readers who are only looking at posts and only reading them if it is of interest.

Article Source: http://adsensemastertips.blogspot.in/