Android KitKat

Android KitKat

Prepare for a sweet new treat 

 

Android is the operating system that powers over 1 billion smartphones and tablets. Since these devices make our lives so sweet, each Android version is named after a dessert: Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich, and Jelly Bean. As everybody finds it difficult to stay away from chocolate we decided to name the next version of Android after one of our favorite chocolate treats, Kitkat®!

To make this release even sweeter, Kit Kat is giving you the chance to win a Nexus 7 or Google Play credit. Just look for specially branded Kit Kat candy bars featuring the Android robot in a store near you.

Support Library Features

Support Library Features

The Android Support Library package contains several libraries that can be included in your application. Each of these libraries supports a specific range of Android platform versions and set of features.

This guide explains the important features and version support provided by the Support Libraries to help you decide which of them you should include in your application. In general, we recommend including the v4 support and v7 appcompat libraries, because they support a wide range of Android versions and provide APIs for recommended user interface patterns.

In order to use any of the following libraries, you must download the library files to your Android SDK installation. Follow the directions for downloading the Support Libraries in Support Library Setup to complete this step. You must take additional steps to include a specific Support Library in your application. See the end of each library section below for important information on how to include the library in your application.

v4 Support Library

---

This library is designed to be used with Android 1.6 (API level 4) and higher. It includes the largest set of APIs compared to the other libraries, including support for application components, user interface features, accessibility, data handling, network connectivity, and programming utilities. Here are a few of the key classes included in the v4 library:

• App Components
  • Fragment - Adds support encapsulation of user interface and functionality with Fragments, enabling applications provide layouts that adjust between small and large-screen devices.
  • NotificationCompat - Adds support for rich notification features.
  • LocalBroadcastManager - Allows applications to easily register for and receive intents within a single application without broadcasting them globally.
• User Interface
  • ViewPager - Adds a ViewGroup that manages the layout for the child views, which the user can swipe between.
  • PagerTitleStrip - Adds a non-interactive title strip, that can be added as a child of ViewPager.
  • PagerTabStrip - Adds a navigation widget for switching between paged views, that can also be used with ViewPager.
  • DrawerLayout - Adds support for creating a Navigation Drawer that can be pulled in from the edge of a window.
  • SlidingPaneLayout - Adds widget for creating linked summary and detail views that appropriately adapt to various screen sizes.
• Accessibility
  • ExploreByTouchHelper - Adds a helper class for implementing accessibility support for custom views.
  • AccessibilityEventCompat - Adds support for AccessibilityEvent. For more information about implementing accessibility, see Accessibility.
  • AccessibilityNodeInfoCompat - Adds support for AccessibilityNodeInfo.
  • AccessibilityNodeProviderCompat - Adds support for AccessibilityNodeProvider.
  • AccessibilityDelegateCompat - Adds support for View.AccessibilityDelegate.
• Content
  • Loader - Adds support for asynchronous loading of data. The library also provides concrete implementations of this class, including CursorLoader and AsyncTaskLoader.
  • FileProvider - Adds support for sharing of private files between applications.

There are many other APIs included in this library. For complete, detailed information about the v4 Support Library APIs, see the android.support.v4 package in the API reference.
This library is located in the <sdk>/extras/android/support/v4/ directory after you download the Android Support Libraries. This library does not contain user interface resources. To include it in your application project, follow the instructions for adding libraries without resources.
The Gradle build script dependency identifier for this library is as follows:

com.android.support:support-v4:18.0.+

This dependency notation specifies the release version 18.0.0 or higher.

v7 Libraries

---

There are several libraries designed to be used with Android 2.1 (API level 7) and higher. These libraries provide specific feature sets and can be included in your application independently from each other.

v7 appcompat library

This library adds support for the Action Bar user interface design pattern.

Note: This library depends on the v4 Support Library. If you are using Ant or Eclipse, make sure you include the v4 Support Library as part of this library's classpath.

Here are a few of the key classes included in the v7 appcompat library:

• ActionBar - Provides an implementation of the action bar user interface pattern. For more information on using the Action Bar, see the Action Bar developer guide.
• ActionBarActivity - Adds an application activity class that must be used as a base class for activities that uses the Support Library action bar implementation.
• ShareActionProvider - Adds support for a standardized sharing action (such as email or posting to social applications) that can be included in an action bar.

This library is located in the <sdk>/extras/android/support/v7/appcompat/ directory after you download the Android Support Libraries. This library contains user interface resources. To include it in your application project, follow the instructions for adding libraries with resources.
The Gradle build script dependency identifier for this library is as follows:

com.android.support:appcompat-v7:18.0.+

This dependency notation specifies the release version 18.0.0 or higher.

v7 gridlayout library

This library adds support for the GridLayout class, which allows you to arrange user interface elements using a grid of rectangular cells. For detailed information about the v7 gridlayout library APIs, see the android.support.v7.widget package in the API reference.
This library is located in the <sdk>/extras/android/support/v7/gridlayout/ directory after you download the Android Support Libraries. This library contains user interface resources. To include it in your application project, follow the instructions for adding libraries with resources.
The Gradle build script dependency identifier for this library is as follows:

com.android.support:gridlayout-v7:18.0.+

This dependency notation specifies the release version 18.0.0 or higher.

v7 mediarouter library

This library provides MediaRouter, MediaRouteProvider, and related media classes that support the Google Cast developer preview.
In general, the APIs in the v7 mediarouter library provide a means of controlling the routing of media channels and streams from the current device to external screens, speakers, and other destination devices. The library includes APIs for publishing app-specific media route providers, for discovering and selecting destination devices, for checking media status, and more. For detailed information about the v7 mediarouter library APIs, see the android.support.v7.media package in the API reference.
The v7 mediarouter library is located in the <sdk>/extras/android/support/v7/mediarouter/ directory after you download the Android Support Library. It's provided as a library project with a dependency on the v7 appcompat library, so you'll need to include both libraries in your build path when setting up your project. For more information on how to set up your project, follow the instructions in adding libraries with resources. If you are developing in Eclipse/ADT, make sure to include both the android-support-v7-mediarouter.jar and android-support-v7-appcompat.jar files.
If you are using Android Studio, all you need to do is specify the Gradle build script dependency identifier com.android.support:support-v7-mediarouter:<revision>, where "18.0.0" is the minimum revision at which the library is available. For example:

com.android.support:mediarouter-v7:18.0.+

The v7 mediarouter library APIs introduced in Support Library r18 are subject to change in later revisions of the Support Library. At this time, we recommend using the library only in connection with the Google Cast developer preview.

v8 Support Library

---

This library is designed to be used with Android (API level 8) and higher. It adds support for the RenderScript computation framework. These APIs are included in the android.support.v8.renderscript package. You should be aware that the steps for including these APIs in your application is very different from other support library APIs. For more information about using these APIs in your application, see the RenderScript developer guide.

Note: Use of RenderScript with the support library is supported with the Android Eclipse plugin and Ant build tools. It is not currently supported with Android Studio or Gradle-based builds.

v13 Support Library

---

This library is designed to be used for Android 3.2 (API level 13) and higher. It adds support for the Fragment user interface pattern with the (FragmentCompat) class and additional fragment support classes For more information about fragments, see the Fragments developer guide. For detailed information about the v13 Support Library APIs, see the android.support.v13 package in the API reference.
This library is located in the <sdk>/extras/android/support/v13/ directory after you download the Android Support Libraries. This library does not contain user interface resources. To include it in your application project, follow the instructions for adding libraries without resources.
The Gradle build script dependency identifier for this library is as follows:

com.android.support:support-v13:18.0.+

This dependency notation specifies the release version 18.0.0 or higher.

Installing the Eclipse Plugin

Android offers a custom plugin for the Eclipse IDE, called Android Development Tools (ADT). This plugin provides a powerful, integrated environment in which to develop Android apps. It extends the capabilities of Eclipse to let you quickly set up new Android projects, build an app UI, debug your app, and export signed (or unsigned) app packages (APKs) for distribution.
If you need to install Eclipse, you can download it from eclipse.org/downloads/.

Note: If you prefer to work in a different IDE, you do not need to install Eclipse or ADT. Instead, you can directly use the SDK tools to build and debug your application.

Download the ADT Plugin

---

1. Start Eclipse, then select Help > Install New Software.
2. Click Add, in the top-right corner.
3. In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following URL for the Location: https://dl-ssl.google.com/android/eclipse/
4. Click OK. If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
5. In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
6. In the next window, you'll see a list of the tools to be downloaded. Click Next.
7. Read and accept the license agreements, then click Finish. If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
8. When the installation completes, restart Eclipse.

Configure the ADT Plugin

---

Once Eclipse restarts, you must specify the location of your Android SDK directory:

1. In the "Welcome to Android Development" window that appears, select Use existing SDKs.
2. Browse and select the location of the Android SDK directory you recently downloaded and unpacked.
3. Click Next.

Your Eclipse IDE is now set up to develop Android apps, but you need to add the latest SDK platform tools and an Android platform to your environment. To get these packages for your SDK, continue to Adding Platforms and Packages.

Download the ADT Translation Manager Plugin

---

Join the translation pilot

Google Play is offering translation services as part of a pilot program. If you are interested, sign up for the pilot program on the APK page in your Developer Console.

ADT Translation Manager Plugin is an Android SDK Tools plugin that helps you work with strings that you are localizing. It's designed to work with the translation services built into the Google Play Developer Console that let you quickly find and purchase translations of your app from a list of pre-qualified vendors.
The plugin simplifies the management of strings during translation. It lets you easily export your default strings and upload them directly to the Developer Console, from which you can get estimates or purchase translations. When your translations are ready, the plugin lets you quickly download and import them back into your project. During import, it moves all of the translated resources into the correct locations under res/values, so that localization works instantly.
For more information about translation services in Google Play, see Purchase professional translations through the Developer Console.
To install the ADT Translation Manager Plugin follow these steps:

1. Install the ADT Plugin, as described above.
2. In Eclipse, select Help > Install New Software.
3. Click Add, in the top-right corner.
4. In the Add Repository dialog that appears, enter a repository name for the Name and the following URL for the Location:

   https://dl.google.com/alt/

5. Click OK.
6. In the Available Software dialog, select the checkbox next to Android Developer Tools - Translation Manager and click Next.
7. In the next window, you'll see a list of the tools to be downloaded. Click Next.
8. Read and accept the license agreements, then click Finish. If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
9. When the installation completes, restart Eclipse.

Installation notes

• The full ADT Plugin must be installed in your Eclipse environment before you install the ADT Translation Manager Plugin.
• ADT Translation Manager Plugin is designed for use with the translation services offered through the Google Play Developer Console. It is not designed for general purpose import/export of strings.
• To use the plugin, you must set up a Developer Console account.
• Currently, translation services are available through the Developer Console only as part of a pilot program. To use the plugin, you must first sign up for the pilot program by visiting the Developer Console.
• If you downloaded ADT as part of the SDK ADT bundle, you may encounter an error when attempting to download the ADT Translation Manager Plugin from the remote repository. In that case, open the Install New Software, uncheck "Contact all update sites during install to find required software" at the bottom and try again.

Troubleshooting ADT Installation

---

If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions:

• If Eclipse can not find the remote update site containing the ADT plugin, try changing the remote site URL to use http, rather than https. That is, set the Location for the remote site to:

  http://dl-ssl.google.com/android/eclipse/

• If you are behind a firewall (such as a corporate firewall), make sure that you have properly configured your proxy settings in Eclipse. In Eclipse, you can configure proxy information from the main Eclipse menu in Window (on Mac OS X, Eclipse) > Preferences > General > Network Connections.

If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you can download the ADT zip file to your local machine and manually install it:

1. Download the ADT Plugin zip file (do not unpack it):

   Package	Size	MD5 Checksum
   ADT-22.2.1.zip	14476845 bytes	97176754a1e86adf2e5e05f44dc7229e

2. Start Eclipse, then select Help > Install New Software.
3. Click Add, in the top-right corner.
4. In the Add Repository dialog, click Archive.
5. Select the downloaded ADT-22.2.1.zip file and click OK.
6. Enter "ADT Plugin" for the name and click OK.
7. In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
8. In the next window, you'll see a list of the tools to be downloaded. Click Next.
9. Read and accept the license agreements, then click Finish. If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
10. When the installation completes, restart Eclipse.

To update your plugin once you've installed using the zip file, you will have to follow these steps again instead of the default update instructions.

Other install errors

Note that there are features of ADT that require some optional Eclipse packages (for example, WST). If you encounter an error when installing ADT, your Eclipse installion might not include these packages. For information about how to quickly add the necessary packages to your Eclipse installation, see the troubleshooting topic ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui".

For Linux users

If you encounter this error when installing the ADT Plugin for Eclipse:

An error occurred during provisioning.
Cannot connect to keystore.
JKS

...then your development machine lacks a suitable Java VM. Installing Sun Java 6 will resolve this issue and you can then reinstall the ADT Plugin.

Install Eclipse

Setting Up an Existing IDE

You should have already downloaded the Android SDK Tools. (If you downloaded the ADT Bundle, you should instead read Setting Up the ADT Bundle.)
The SDK Tools package is not the complete SDK environment. It includes only the core SDK tools, which you can use to download the rest of the SDK packages (such as the latest system image).

Getting started on Windows

Your download package is an executable file that starts an installer. The installer checks your machine for required tools, such as the proper Java SE Development Kit (JDK) and installs it if necessary. The installer then saves the Android SDK Tools into a default location (or you can specify the location).

1. Double-click the executable (.exe file) to start the install.
2. Make a note of the name and location in which it saves the SDK on your system—you will need to refer to the SDK directory later, when setting up the ADT plugin and when using the SDK tools from the command line.
3. Once the installation completes, the installer offers to start the Android SDK Manager. If you'll be using Eclipse, do not start the Android SDK Manager, and instead move on to Installing the Eclipse Plugin. If you're using a different IDE, start the SDK Manager and read Adding Platforms and Packages.
   
   

   Getting started on Mac

   1. Unpack the ZIP file you've downloaded. By default, it's unpacked into a directory named android-sdk-mac_x86. Move it to an appropriate location on your machine, such as a "Development" directory in your home directory. Make a note of the name and location of the SDK directory on your system—you will need to refer to the SDK directory later, when setting up the ADT plugin and when using the SDK tools from the command line.
      
      
   2. If you're using Eclipse, move on to Installing the Eclipse Plugin. Otherwise, if you're using a different IDE, read Adding Platforms and Packages.

   Getting started on Linux

   1. Unpack the .tgz file you've downloaded. By default, the SDK files are unpacked into directory named android-sdk-linux_x86. Move it to an appropriate location on your machine, such as a "Development" directory in your home directory.Make a note of the name and location of the SDK directory on your system—you will need to refer to the SDK directory later, when setting up the ADT plugin and when using the SDK tools from the command line.
   2. If you're using Eclipse, move on to Installing the Eclipse Plugin. Otherwise, if you're using a different IDE, read Adding Platforms and Package

 

What is Android??

Introduction

Android  is a Linux-based operating system designed primarily for touchscreen mobile devices such as smartphones and tablet computers. Initially developed by Android, Inc., which Google backed financially and later bought in 2005, Android was unveiled in 2007 along with the founding of the Open Handset Alliance: a consortium of hardware, software, and telecommunication companies devoted to advancing open standards for mobile devices. The first Android-powered phone was sold in October 2008.

Android is open source and Google releases the code under the Apache License. This open-source code and permissive licensing allows the software to be freely modified and distributed by device manufacturers, wireless carriers and enthusiast developers. Additionally, Android has a large community of developers writing applications ("apps") that extend the functionality of devices, written primarily in a customized version of the Java programming language. In October 2012, there were approximately 700,000 apps available for Android, and the estimated number of applications downloaded from Google Play, Android's primary app store, was 25 billion. A developer survey conducted in April–May 2013 found that Android is the most popular platform for developers, used by 71% of the mobile developer population.

 

History of Android

History

Android, Inc. was founded in Palo Alto, California in October 2003 by Andy Rubin (co-founder of Danger), Rich Miner (co-founder of Wildfire Communications, Inc.), Nick Sears (once VP at T-Mobile), and Chris White (headed design and interface development at WebTV) to develop, in Rubin's words "smarter mobile devices that are more aware of its owner's location and preferences". The early intentions of the company were to develop an advanced operating system for digital cameras, when it was realised that the market for the devices was not large enough, and diverted their efforts to producing a smartphone operating system to rival those of Symbian and Windows Mobile (Apple's iPhone had not been released at the time). Despite the past accomplishments of the founders and early employees, Android Inc. operated secretly, revealing only that it was working on software for mobile phones. That same year, Rubin ran out of money. Steve Perlman, a close friend of Rubin, brought him $10,000 in cash in an envelope and refused a stake in the company.

Google acquired Android Inc. on August 17, 2010, making it a wholly owned subsidiary of Google. Key employees of Android Inc., including Rubin, Miner and White, stayed at the company after the acquisition. Not much was known about Android Inc. at the time, but many assumed that Google was planning to enter the mobile phone market with this move. At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel. Google marketed the platform to handset makers and carriers on the promise of providing a flexible, upgradable system. Google had lined up a series of hardware component and software partners and signaled to carriers that it was open to various degrees of cooperation on their part.

HOW TO USE COMPUTER WITHOUT MOUSE?

The General Shortcuts

We’ll kickoff the list with some really general shortcuts that you often used.

• CTRL+C (Copy)
• CTRL+X (Cut)
• CTRL+V (Paste)
• CTRL+Z (Undo)
• Delete (Delete)
• Shift+Delete (Delete the selected item permanently without placing the item in the Recycle Bin)
• CTRL while dragging an item (Copy the selected item)
• CTRL+Shift while dragging an item (Create a shortcut to the selected item)
• F2 key (Rename the selected item)
• CTRL+RIGHT ARROW (Move the insertion point to the beginning of the next word)
• CTRL+LEFT ARROW (Move the insertion point to the beginning of the previous word)
• CTRL+DOWN ARROW (Move the insertion point to the beginning of the next paragraph)
• CTRL+UP ARROW (Move the insertion point to the beginning of the previous paragraph)
• CTRL+Shift with any of the arrow keys (Highlight a block of text)
• Shift with any of the arrow keys (Select more than one item in a window or on the desktop, or select text in a document)

• CTRL+A (Select all)
• F3 key (Search for a file or a folder)
• Alt+Enter (View the properties for the selected item)
• Alt+F4 (Close the active item, or quit the active program)
• Alt+Enter (Display the properties of the selected object)
• Alt+Spacebar (Open the shortcut menu for the active window)
• CTRL+F4 (Close the active document in programs that enable you to have multiple documents open simultaneously)

• Alt+Tab (Switch between the open items)
• Alt+ESC (Cycle through items in the order that they had been opened)
• F6 key (Cycle through the screen elements in a window or on the desktop)
• F4 key (Display the Address bar list in My Computer or Windows Explorer)
• Shift+F10 (Display the shortcut menu for the selected item)
• Alt+Spacebar (Display the System menu for the active window)
• CTRL+ESC (Display the Start menu)
• Alt+Underlined letter in a menu name (Display the corresponding menu)
• Underlined letter in a command name on an open menu (Perform the corresponding command)
• F10 key (Activate the menu bar in the active program)
• RIGHT ARROW (Open the next menu to the right, or open a submenu)
• LEFT ARROW (Open the next menu to the left, or close a submenu)
• F5 key (Update the active window)
• Backspace (View the folder one level up in My Computer or Windows Explorer)
• ESC (Cancel the current task)
• Shift when you insert a CD-ROM into the CD-ROM drive (Prevent the CD-ROM from automatically playing)

Dialog Box board ShortcutsKeyboard Shortcuts

• CTRL+Tab (Move forward through the tabs)
• CTRL+Shift+Tab (Move backward through the tabs)
• Tab (Move forward through the options)
• Shift+Tab (Move backward through the options)
• Alt+Underlined letter (Perform the corresponding command or select the corresponding option)
• Enter (Perform the command for the active option or button)
• Spacebar (Select or clear the check box if the active option is a check box)
• Arrow keys (Select a button if the active option is a group of option buttons)
• F1 key (Display Help)
• F4 key (Display the items in the active list)
• Backspace (Open a folder one level up if a folder is selected in the Save As or Open dialog box)

Accessibility Keyboard Shortcuts

• Right Shift for eight seconds (Switch FilterKeys either on or off)
• Left Alt+left Shift+PRINT SCREEN (Switch High Contrast either on or off)
• Left Alt+left Shift+NUM LOCK (Switch the MouseKeys either on or off)
• Shift five times (Switch the StickyKeys either on or off)
• NUM LOCK for five seconds (Switch the ToggleKeys either on or off)
• Win +U (Open Utility Manager)
• Windows Explorer Keyboard Shortcuts
• END (Display the bottom of the active window)
• HOME (Display the top of the active window)
• NUM LOCK+* (Display all of the subfolders that are under the selected folder)
• NUM LOCK++ (Display the contents of the selected folder)
• NUM LOCK+- (Collapse the selected folder)
• LEFT ARROW (Collapse the current selection if it is expanded, or select the parent folder)
• RIGHT ARROW (Display the current selection if it is collapsed, or select the first subfolder)

Shortcut Keys for Character Map

• After you double-click a character on the grid of characters, you can move through the grid by using the keyboard shortcuts:

• RIGHT ARROW (Move to the right or to the beginning of the next line)
• LEFT ARROW (Move to the left or to the end of the previous line)
• UP ARROW (Move up one row)
• DOWN ARROW (Move down one row)
• PAGE UP (Move up one screen at a time)
• PAGE DOWN (Move down one screen at a time)
• HOME (Move to the beginning of the line)
• END (Move to the end of the line)
• CTRL+HOME (Move to the first character)
• CTRL+END (Move to the last character)
• Spacebar (Switch between Enlarged and Nor mal mode when a character is selected)

Microsoft Management Console (MMC) Main Window Keyboard Shortcuts

CTRL+O (Open a saved console)

CTRL+N (Open a new console)

CTRL+S (Save the open console)

CTRL+M (Add or remove a console item)

CTRL+W (Open a new window)

F5 key (Update the content of all console windows)

Alt+Spacebar (Display the MMC window menu)

Alt+F4 (Close the console)

Alt+A (Display the Action menu)

Alt+V (Display the View menu)

Alt+F (Display the File menu)

Alt+O (Display the Favorites menu)

MMC Console Window Keyboard Shortcuts

CTRL+P (Print the current page or active pane)

Alt+- (Display the window menu for the active console window)

Shift+F10 (Display the Action shortcut menu for the selected item)

F1 key (Open the Help topic, if any, for the selected item)

F5 key (Update the content of all console windows)

CTRL+F10 (Maximize the active console window)

CTRL+F5 (Restore the active console window)

Alt+Enter (Display the Properties dialog box, if any, for the selected item)

F2 key (Rename the selected item)

CTRL+F4 (Close the active console window. When a console has only one console window, this shortcut closes the console)

Remote Desktop Connection Navigation

CTRL+Alt+END (Open the m*cro$oft Windows NT Security dialog box)

Alt+PAGE UP (Switch between programs from left to right)

Alt+PAGE DOWN (Switch between programs from right to left)

Alt+INSERT (Cycle through the programs in most recently used order)

Alt+HOME (Display the Start menu)

CTRL+Alt+BREAK (Switch the client computer between a window and a full screen)

Alt+Delete (Display the Windows menu)

CTRL+Alt+- (Place a snapshot of the active window in the client on the Terminal server clipboard and provide the same functionality as pressing PRINT SCREEN on a local computer.)

CTRL+Alt++ (Place a snapshot of the entire client window area on the Terminal server clipboard and provide the same functionality as pressing Alt+PRINT SCREEN on a local computer.)

Internet Explorer navigation

CTRL+B (Open the Organize Favorites dialog box)

CTRL+E (Open the Search bar)

CTRL+F (Start the Find utility)

CTRL+H (Open the History bar)

CTRL+I (Open the Favorites bar)

CTRL+L (Open the Open dialog box)

CTRL+N (Start another instance of the browser with the same Web address)

CTRL+O (Open the Open dialog box, the same as CTRL+L)

CTRL+P (Open the Print dialog box)

CTRL+R (Update the current Web page)

CTRL+W (Close the current window)

Google Doodle

Latest Google Basketball doodle - Play basketball in Google

Google already came out with so many Doodle based on Olympics 2012. It is the 13th Google's Olympic Doodle. In 7th August, Google introduced Hurdles Doodle, which got popular worldwide. So the next day Google came out with another similar interactive doodle. The name of the Doodle is Basketball 2012.

At first, Go to Google.com or click this link

How to make windows genuine using cmd in just less then 1 min??

Hello guys..

This is amazing trick i came across for making your windows genuine in less than a minute using command prompt..This trick is tested on windows 7.Follow this simple steps for making your windows genuine.

1) Go to run and type in search cmd and run it as administrator.

2) Type the command SLMGR -REARM

3) And you are done next step you will be asked for restart..Restart your comp and you had make your windows as genuine..

This trick is for windows 7.


Now i will show you

How to Make Windows XP Genuine Forever

1) Click start and choose run

2) Type regedit in run

3) Now you will be directed to registry editor and now expand  HKEY_LOCAL_MACHINE

4) Now navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WPAEvents   and you will be here as shown

5) Now modify oobe timer (right click on OOBETimer and click modify)

6) In the Edit Binary Value Window,remove all the data value from the data box. Click ok and exit the registry editor.

7) Now go back to run and type %systemroot%\System32\oobe\msoobe.exe /a

8) Now in the Acitivate Window Wizard,chooose the second option.It should be " Yes,I want to telephone a customer service representative to activate Windows."  Click on next.

9) Click on Change Product key

10) Enter your genuine key in the New Key box and click on Update.

11) Check whether your Windows XP is genuine (optional). Type the following command in Run without quotation marks: "oobe/msoobe /a".

If a box appears saying “Windows is already activated," it means your Windows XP is genuine.