Intel outs Android 4.2.2 alpha dev code dual-boot with Windows 8




What we expect for may be come true. To have such mobile phone with dual boot option. Intel is on a mission to prove that it isn’t too late to catch up to other chipset manufacturers yet in the ever-growing world of Android. And its latest move involves releasing Android 4.2.2 Jelly Bean developer code that has been optimized for Intel hardware.

Although Intel has been a bit slow with the updates, at least they have been coming out more consistently over the past year. The developers at its own Open Source Technology Center have no doubt been hard at work over the last six months, which is why the world can now enjoy access to Intel-optimized Android 4.2.2 alpha dev code.

So what exactly does this new release code bring to the table, anyway? For starters, it now offers UEFI boot support, as well as support for dual-booting with Microsoft’s Windows 8. It is also powered by the Linux 3.8 kernel now and includes an interactive installer which should make it easier to work with.

Intel warns all those who intend on downloading and using this new release about bugs and general pre-alpha quality issues. So while this is mostly good news, you should know that if you hit the source code below, you are doing it at your own risk.

How to Enable and Use S Beam on Androids (Share More)





There are many ways to share files between to mobile phone at this current technologies. Android 4.1 Jelly Bean lets you share photos and videos between phones with a tap, but that’s only over a slower Bluetooth connection. Samsung kicks things up a notch with S Beam on the Galaxy S III. It takes the same concept of using NFC for establishing a connection between two devices with a tap, but then leverages Wi-Fi Direct instead of Bluetooth after than initial handshake to make transfers lightning fast.

Bluetooth and Wi-Fi Direct are two of today’s most popular means to share files and data between two mobile devices. The downside to these methods, however, is that they require some setting up before you can use them.

But, with the help of Near Field Communication (NFC) technology, you can skip the setting up part and, in its place, will only need tapping devices against each other.

NFC and Android Beam work hand in hand to share data to other NFC-capable devices over a Bluetooth connection. These could be contact information, map directions, web page URLs, Google Play Store pages for app downloads, and more. Unfortunately, Bluetooth transfers at lower speeds and works better with small files. This means that larger files, such as images and videos, may take a long time to beam.

Samsung adopted NFC’s hassle-free system in its S Beam feature, available on certain high-end Samsung Android devices like the Galaxy S3 and Galaxy Note 2. The feature uses NFC in tandem with Wi-Fi Direct rather than Bluetooth, allowing users to beam large files to other S Beam-capable devices within seconds.

In this guide, learn how to use S Beam on your Samsung device. 

Enabling S Beam

Before you can beam files through S Beam, you must first activate S Beam on your Samsung device:

  • Go to the Settings page.
  • Under Wireless & Networks, tap on More Settings.
  • Tap on S Beam to turn it on. NFC will also be automatically enabled. If NFC is not active, S Beam won’t work.
  • S Beaming content


Or follow this step:

1. Pull down the Notification Shade and select the Settings icon in the top right corner.

2. Select More Settings.

3. Select S Beam.

4. Turn it ON.

5. Bring up the content you want to share on the screen (i.e. a picture from the gallery).

6. Hold the back of your Galaxy S III up to the back of another Galaxy S III and it will prompt you to “Tap to Send”.

7. Tap the item and then your S III will ask you to pull the devices apart.

8. The content should soon appear on the screen of the other device.

To successfully share files and content through S Beam, take note of the following:

Both the sender and receiver devices must have the S Beam feature and it must be active. NFC must also be active on both devices.
Neither of the devices should be asleep or locked. The receiver device must preferably be on the Home screen.
The phones will make a sound and vibrate slightly when they detect each other.
Only separate your devices when you are prompted to. Separating them before beaming may prevent the transfer from starting.
S Beam only sends locally saved files. Files saved in your Picasa account, for example, cannot be beamed.
General way to beam content

S Beam works just like Android Beam. The general steps for sending content from a device to the other is as follows:

  • Open the file/content to be shared on the sender device.
  • Place the backs of both devices against each other. The devices will beep and vibrate slightly (if supported) to confirm that they are within beaming range.
  • On the sender device, you’ll see “Touch to beam” on the screen.
  • Tap on the sender device’s screen to start sending the content.
  • When prompted to do so, separate the devices to begin beaming.
  • Upon completion, the content will be opened by the appropriate handler app on the receiver device.


Beaming photos or images

To beam images, just follow the standard way for S Beaming content. Open a photo or image from the Gallery and beam away. The receiver device’s Gallery app will show the image after transfer is completed.


Beaming music

Beaming music tracks follows the same standard procedure for S Beam. Just play the music track in the sender device’s Music Player app and beam away. When beaming completes, the receiver device automatically plays the received track.


Beaming videos

To beam local videos, just play the video on the sender device’s Video Player app and beam away. The receiver device automatically opens and plays the received video after beaming completes.


Beaming contacts

You don’t need to manually copy contact information from one device to another anymore. With S Beam, you can easily share contacts. Just open the contact’s info page on the sender device, then beam away in the usual way. When beaming completes, the receiver device will ask where to save the beamed contact to.


Beaming apps

Just like with Android Beam, you can also share Android apps via S Beam. This procedure doesn’t send the app’s files to the other device, though. Instead, it will send the app’s Google Play Store URL to the other device. To share an app, just launch the app to be beamed, then beam it in the usual way. The receiver device opens the app’s page on the Google Play Store. An Internet connection is needed to access the Google Play Store.


Beaming webpages

When you S Beam a webpage, the sender device doesn’t beam the page itself. Instead, only the URL is sent and the receiver device opens it in its native browser app. To beam a webpage, just open the page in the sender device’s browser app, and beam away as usual. An Internet connection is needed to open webpages, of course.


Beaming YouTube videos

Want to share the YouTube video that you’re watching? Go ahead. Just open the YouTube video page on the sender device, beam in the usual way, and the receiver device automatically opens it in the YouTube app upon beam completion. Both devices need to be connected to the Internet, of course; otherwise, YouTube won’t open.

Beaming other content

You can also beam many other types of mobile content, such as Google Maps data and Google Search results, between supported Samsung devices.

So, Let's share what we have to our friends...

How To Update Samsung Google Nexus 10 P8110 to Android 4.2.2 Jelly Bean




Samsung Google Nexus 10 P8110 is another tablet presented by Samsung and Google. the device can't be used for calling, sms and internet connection without wi-fi only. But we can use any modem pluged to the device. Samsung Google Nexus 10 P8110 itself has been presented with the operating system of Android Jelly Been and could be update to the latest version of Jelly Bean.

For those who can't update the device, this article will explain some methods used to update th edevice manually. You just need to prepare such things required to do the update.

Note: everything below is working from the assumption that you’re running stock Android and not a custom ROM. If you have a custom ROM installed, you’ll have to find an updated version of that ROM to get Android 4.2.2 on your device. Otherwise you’re going to have to download your stock image from Google and install the factory image fresh (which will erase everything).

Method 1: Easy

The first thing that rooted users should try is :

1. Please going to Settings >> Apps >> All and scrolling to find Google Services Framework.
2. Tap the “Clear Data” button and confirm by tapping “OK”. From there, use the back button to get to the main Settings screen.
3. Scroll all the way down and tap About Phone, then tap System Updates.
4. You’ll see the “Check Now” button to have the device check for updates, and you should notice that the last time the device will be reporting it checked was back in 1969 (which I like to pretend is an artifact of time travel).
5. Tapping “Check Now” should result in beginning the download of Android 4.2.2 and update process for many. It will ask you to confirm that you want to install the update.

Most root users already know that updating the device will remove your root. There are a few ways around this. Clockwork Mod recovery can not only protect itself from being over-written, it can also attempt to retain your root for you. For my own devices, I prefer to use OTA Rootkeeper by Project Voodoo. As long as the update doesn’t format or overwrite the /system partition, OTA RootKeeper helps to maintain a working root (including backing up your su binary).

Method 2: Slightly Harder

If you can’t get the update over the air, your next best bet is to flash the update from your recovery. This involves downloading the update, moving the update to your device, then booting your device to recovery and initiating the install.

1. The first step is finding the Android 4.2.2 update. You can download the Nexus 10 update here.
2. Download these to your computer, transfer them to your device in whatever manner suits you best, and reboot into recovery.
3. For those who aren’t used to it, booting to recovery is pretty simple on a Nexus: you power down the device, and then power it up while pressing (and holding) the volume up and down buttons.

You boot to a screen with a big (green) colored arrow pointing to where your power button is, and Andy the Android in the background. From here, you can use the volume up and volume down to choose different boot options. Boot to recovery by pressing volume up or down until the arrow is red and says “Recovery mode”, then pressing the power button.

Once in recovery, you’re going to want to find the option to install from a zip. This should require you to specify a zip, which is the file you saved to your device. Install the Android 4.2.2 update from that zip file, then reboot your device. The update will run its final steps before you boot to the lock screen and can enjoy the Andriod 4.2.2 goodness.

Method 3: Kinda Hard, Using ADB

This method assumes you have adb installed. This also assumes you’re updating from 4.2.1 and not an earlier build. If you’re not sure or you have adb installed, you can probably find a good set of instructions here. As always, use at your own risk. This method has also been covered before.

1. Plug the USB data cable from your computer to your device. Be sure you have the Android 4.2.2 update file for your device– again, grab the Nexus 10 update here.
2. Once the file is downloaded, move it to the same folder where ADB is located. Using the steps described above in the previous method, boot into recovery.
3. Within the recovery mode menu you should find the option to “sideload” or “apply update from adb”.

At this point, you must open a command-line window on your computer to run the adb commands. You may need to change directory to your ADB folder. These are the commands that you will run for your device:

Nexus 10:
adb sideload eaef14432ff5.signed-mantaray-JDQ39-from-JOP40D.eaef1443.zip

After you run these commands, you’ll see a progress bar as the update loads onto the device. The progress will reach 100% and then you’ll see the device installing the update. The update will finish, at which point you can reboot the device from the recovery menu. As Android completes booting up it will run the final install processes, and then you should be at your lock screen.
Once the update completes, enjoy Android 4.2.2!

Nexus 10 Problems updating to Android 4.2.2? There’s A Fix For That.

There are some Nexus 10 devices that will hit an error during the Android 4.2.2 update process. This is because there’s corruption on the system partition of the device that’s causing the update to fail. The symptom for this is a ‘Status 7’ error during the install process. For me it was when the ‘set_perms’ process was showing during the update.

To fix the problem you need to run the e2fsck command on the device, but you must do it through adb on your computer. The way you do this is by following all of the directions I gave above to prepare for sideloading the update, but instead of running the sideload command, you must run the following:

adb shell “e2fsck -y /dev/block/platform/dw_mmc.0/by-name/system”
(Include the quotes above, since they contain the command being run on the device)

The command above will only work on the Nexus 10. If you’re experiencing this symptom on other devices do not run the command as shown above. Improperly using e2fsck can ruin your partition table on your device, bricking it. For help walking through fixing corrupted partitions on other devices, I strongly recommend finding someone who is familiar with the command line and have them help you find your partition layout. It’s not difficult, but it’s also not very forgiving. I came across this specific issue with the Nexus 10 because there was a corrupted update that some people received, which corrupted the file system.

After running the file check above, go back and try to update the Nexus 10 to Android 4.2.2. Try Method 1 first, since the main problem for the update will have been fixed.

How To Update Asus Google Nexus 7 to OS Android 4.2.2 Jelly Bean




The Nexus 7 is powered by one of the two chipsets at the heart of current flagship phones and tablets - NVIDIA's Tegra 3. You get a quad-core CPU and good graphics muscle at a time when the only quad-core tablets around are pricy 10" models.

The 7" screen might be a compromise to some, but others will see an advantage in the excellent portability. 7" tablets fit in a coat pocket or purse. Plus, WXGA resolution and 216ppi pixel density sound more than reasonable. For comparison's sake, an Amazon Kindle Fire offers 170ppi, and even the new iPad isn't too far ahead with its 264ppi.

Apparently there is some update available for the users. For those who have a difficult time to update the device, this article will show you some methods to mannual update the Nexus 7.

Note: everything below is working from the assumption that you’re running stock Android and not a custom ROM. If you have a custom ROM installed, you’ll have to find an updated version of that ROM to get Android 4.2.2 on your device. Otherwise you’re going to have to download your stock image from Google and install the factory image fresh (which will erase everything).

Method 1: Easy

The first thing that rooted users should try is :

1. Please going to Settings >> Apps >> All and scrolling to find Google Services Framework.
2. Tap the “Clear Data” button and confirm by tapping “OK”. From there, use the back button to get to the main Settings screen.
3. Scroll all the way down and tap About Phone, then tap System Updates.
4. You’ll see the “Check Now” button to have the device check for updates, and you should notice that the last time the device will be reporting it checked was back in 1969 (which I like to pretend is an artifact of time travel).
5. Tapping “Check Now” should result in beginning the download of Android 4.2.2 and update process for many. It will ask you to confirm that you want to install the update.

Most root users already know that updating the device will remove your root. There are a few ways around this. Clockwork Mod recovery can not only protect itself from being over-written, it can also attempt to retain your root for you. For my own devices, I prefer to use OTA Rootkeeper by Project Voodoo. As long as the update doesn’t format or overwrite the /system partition, OTA RootKeeper helps to maintain a working root (including backing up your su binary).

Method 2: Slightly Harder

If you can’t get the update over the air, your next best bet is to flash the update from your recovery. This involves downloading the update, moving the update to your device, then booting your device to recovery and initiating the install.

1. The first step is finding the Android 4.2.2 update. You can download the Nexus 7 update here.
2. Download these to your computer, transfer them to your device in whatever manner suits you best, and reboot into recovery.
3. For those who aren’t used to it, booting to recovery is pretty simple on a Nexus: you power down the device, and then power it up while pressing (and holding) the volume up and down buttons.

You boot to a screen with a big (green) colored arrow pointing to where your power button is, and Andy the Android in the background. From here, you can use the volume up and volume down to choose different boot options. Boot to recovery by pressing volume up or down until the arrow is red and says “Recovery mode”, then pressing the power button.

Once in recovery, you’re going to want to find the option to install from a zip. This should require you to specify a zip, which is the file you saved to your device. Install the Android 4.2.2 update from that zip file, then reboot your device. The update will run its final steps before you boot to the lock screen and can enjoy the Andriod 4.2.2 goodness.

Method 3: Kinda Hard, Using ADB

This method assumes you have adb installed. This also assumes you’re updating from 4.2.1 and not an earlier build. If you’re not sure or you have adb installed, you can probably find a good set of instructions here. As always, use at your own risk. This method has also been covered before.

1. Plug the USB data cable from your computer to your device. Be sure you have the Android 4.2.2 update file for your device– again, grab the Nexus 7 update here.
2. Once the file is downloaded, move it to the same folder where ADB is located. Using the steps described above in the previous method, boot into recovery.
3. Within the recovery mode menu you should find the option to “sideload” or “apply update from adb”.

At this point, you must open a command-line window on your computer to run the adb commands. You may need to change directory to your ADB folder. These are the commands that you will run for your device:

Nexus 7:
adb sideload 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

After you run these commands, you’ll see a progress bar as the update loads onto the device. The progress will reach 100% and then you’ll see the device installing the update. The update will finish, at which point you can reboot the device from the recovery menu. As Android completes booting up it will run the final install processes, and then you should be at your lock screen.

Once the update completes, enjoy Android 4.2.2!

How To Update LG Nexus 4 E960 to Android 4.2.2 Jelly Bean Manually




LG Nexus 4 E960 is the next generation of Nexus smartphones which in this time made by LG and Google. It has announced to bring such great features on it that we could difficult not to see the device. Come with the latest Android 4.1 Jelly Bean, now we have some methods to manually update the device into the Android 4.2.2 Jelly bean version.

Note: everything below is working from the assumption that you’re running stock Android and not a custom ROM. If you have a custom ROM installed, you’ll have to find an updated version of that ROM to get Android 4.2.2 on your device. Otherwise you’re going to have to download your stock image from Google and install the factory image fresh (which will erase everything).

Method 1: Easy

The first thing that rooted users should try is :

1. Please going to Settings >> Apps >> All and scrolling to find Google Services Framework.
2. Tap the “Clear Data” button and confirm by tapping “OK”. From there, use the back button to get to the main Settings screen.
3. Scroll all the way down and tap About Phone, then tap System Updates.
4. You’ll see the “Check Now” button to have the device check for updates, and you should notice that the last time the device will be reporting it checked was back in 1969 (which I like to pretend is an artifact of time travel).
5. Tapping “Check Now” should result in beginning the download of Android 4.2.2 and update process for many. It will ask you to confirm that you want to install the update.

Most root users already know that updating the device will remove your root. There are a few ways around this. Clockwork Mod recovery can not only protect itself from being over-written, it can also attempt to retain your root for you. For my own devices, I prefer to use OTA Rootkeeper by Project Voodoo. As long as the update doesn’t format or overwrite the /system partition, OTA RootKeeper helps to maintain a working root (including backing up your su binary).

Method 2: Slightly Harder

If you can’t get the update over the air, your next best bet is to flash the update from your recovery. This involves downloading the update, moving the update to your device, then booting your device to recovery and initiating the install.

1. The first step is finding the Android 4.2.2 update. You can download the Nexus 4 update here.
2. Download these to your computer, transfer them to your device in whatever manner suits you best, and reboot into recovery.
3. For those who aren’t used to it, booting to recovery is pretty simple on a Nexus: you power down the device, and then power it up while pressing (and holding) the volume up and down buttons.

You boot to a screen with a big (green) colored arrow pointing to where your power button is, and Andy the Android in the background. From here, you can use the volume up and volume down to choose different boot options. Boot to recovery by pressing volume up or down until the arrow is red and says “Recovery mode”, then pressing the power button.

Once in recovery, you’re going to want to find the option to install from a zip. This should require you to specify a zip, which is the file you saved to your device. Install the Android 4.2.2 update from that zip file, then reboot your device. The update will run its final steps before you boot to the lock screen and can enjoy the Andriod 4.2.2 goodness.

Method 3: Kinda Hard, Using ADB

This method assumes you have adb installed. This also assumes you’re updating from 4.2.1 and not an earlier build. If you’re not sure or you have adb installed, you can probably find a good set of instructions here. As always, use at your own risk. This method has also been covered before.

1. Plug the USB data cable from your computer to your device. Be sure you have the Android 4.2.2 update file for your device– again, grab the Nexus 4 update here.
2. Once the file is downloaded, move it to the same folder where ADB is located. Using the steps described above in the previous method, boot into recovery.
3. Within the recovery mode menu you should find the option to “sideload” or “apply update from adb”.

At this point, you must open a command-line window on your computer to run the adb commands. You may need to change directory to your ADB folder. These are the commands that you will run for your device:

Nexus 4:
adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip

After you run these commands, you’ll see a progress bar as the update loads onto the device. The progress will reach 100% and then you’ll see the device installing the update. The update will finish, at which point you can reboot the device from the recovery menu. As Android completes booting up it will run the final install processes, and then you should be at your lock screen.
Once the update completes, enjoy Android 4.2.2!

Micromax A110 Canvas 2 Review, a Dual SIM Budget Phone in 5-inch LCD



The A110 Canvas 2 is its successor and features several hardware and design upgrades. The phone is overall slimmer (9.7mm vs 11.9mm), even though the weight remains unchanged at 168 grams. It now has a dual core processor instead of the single core on the A100 and the camera is upgraded to 8MP with dual LED flash (compared to 5MP with single LED flash).

The display size and resolution remains the same (5-inch, 854 x 480 pixels). However, it has improved viewing angles and improved outdoor visibility becuase Micromax now uses an IPS panel.

Overall build quality is impressive with curved edges and a textured back panel. We did feel that the edges of the front panel were unnecessarily sharp.

The camera module sticks out from the back of the device, this could lead to scratches on the camera lens over a period of time.

Performance from the phablet was average. Even though it has a dual core processor, the 512MB RAM makes the phone feel sluggish if more than five apps are running in the background. You only get 2GB internal storage, so an 8GB (or more) microSD card becomes a necessity. The 8MP camera takes good pictures in daylight, but indoors there is visible noise — it's good enough to share on social networks.

You can consider the Intex Aqua 5.0 or the Spice Stellar Horizon. Both offer a 5-inch display with similar hardware specifications, but the Spice offers a larger 2,400 mAh battery comapred to 2,000 mAh on the Micromax.

GENERAL
2G Network GSM 900 / 1800 - SIM 1 & SIM 2
3G Network HSDPA 2100
SIM Dual SIM (Mini-SIM)
Announced 2012, October
Status Available. Released 2012, November

BODY
Dimensions 147 x 76.5 x 9.7 mm (5.79 x 3.01 x 0.38 in)

DISPLAY
Type IPS LCD capacitive touchscreen, 16M colors
Size 480 x 854 pixels, 5.0 inches (~196 ppi pixel density)
Multitouch Yes
Protection Yes

SOUND
Alert types Vibration, MP3, WAV ringtones
Loudspeaker Yes
3.5mm jack Yes

MEMORY
Card slot microSD, up to 32 GB
Internal 4 GB (2 GB user available) storage, 512 MB

DATA
GPRS Yes
EDGE Yes
Speed HSDPA, HSUPA
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi hotspot
Bluetooth Yes, v3.0 with A2DP
USB Yes, microUSB v2.0

CAMERA
Primary 8 MP, 3264 x 2448 pixels, autofocus, dual-LED flash
Features Geo-tagging, touch focus, face detection
Video Yes
Secondary Yes, VGA

FEATURES
OS Android OS, v4.0.4 (Ice Cream Sandwich)
Chipset MediaTek MT6577
CPU Dual-core 1 GHz
GPU PowerVR SGX531
Sensors Accelerometer, proximity
Messaging SMS(threaded view), MMS, Email, Push Email, IM
Browser HTML5
Radio FM radio
GPS Yes, with A-GPS support
Java Yes, via Java MIDP emulator
Colors Black, White
- SNS integration
- MP3/AAC/WMA/WAV player
- MP4/WMV/H.264/H.263 player
- Organizer
- Document viewer
- Google Search, Maps, Gmail, Youtube, Calendar, Google Talk
- Voice memo/dial
- Predictive text input

BATTERY
Li-Ion 2000 mAh battery
Stand-by Up to 180 h
Talk time Up to 5 h

You can watch the unboxing video here:


Panasonic 20-inch Tablet Features 4K Windows 8 Has Been Revealed at CES




Currently there has been some advance made by Panasonic to announce a bigger tablet than any tablet can be found now. In times when people are slowly starting to migrate from bigger 10-inch tablets to the more convenient 7-inch ones, Panasonic has decided to go the other way. And perhaps a bit too far, if I might add.


What you see above is Panasonic’s latest ‘tablet’, a 20-inch monstrosity that has a mind-boggling 4K resolution display. And on the inside it’s running on the full Windows 8 operating system.

Here are the full specs of the device:

Display: 20.0 inch IPS Alpha Panel
Resolution: 3840 x 2560 pixels (230 ppi): Approx. 16.77 million colors
Aspect Ratio: 15:10
OS: Windows 8 Pro 64 bit
CPU: Intel Core i5 3427U vPro 1.80 GHz
Graphics: NVIDIA GeForce Graphics
Memory: 4GB (max.16GB)
Flash Memory Drive (SSD): 128GB
Interface: High resolution digital pen (Anoto Live pen), Electrostatic multi-touchpanel (10 fingers)
Wireless: IEEE802.11a/b/g/n, Bluetooth v4.0
USB Port: USB2.0 x 1
Expansion Slots: microSD memory card slot x 1 (supports microSDXC memory card)
Embedded Camera: Resolution: HD 720P, Effective pixels: max. 1280×720 pixel
Battery Life: Approx. 2 hours (using internal battery)
Size: 18.7″ (W) x 13.1″ (D) x 0.4″ (H)
Weight: 5.3 lbs

The device is aimed at photographers, designers, architects and such. It remains to be see when it would be launched, what it would be priced at and who would want to lug around something so big with just two hours of battery life.

You can watch a hands-on video of the device here.