Manually updating your Nexus 10 to Android 4.2.2

I just manually updated my non-rooted, stock Nexus 10 from Android 4.2.1 (JOD40D) to Android 4.2.2 (JDQ39).

This is totally done at your own risk but here is what worked for me.

Since this is an update that patches the already installed system I strongly advice against trying this on anything but an non-rooted JOD40D device.

• Download the JOD40D to JDQ39 update.
• Make sure you have ADB up and running. I used this guide.
• Turn off the Nexus 10.
• Start the Nexus 10 while holding down both volume up and down.
• You should get an Android lying on it's back and some device information.

• Press volume down until the left vertical text says "RECOVERY MODE"

• Press power to reboot into recovery mode. 
• You'll now get a smaller Android robot, still on it's back, with a red triangle.

• Hold power and press once on volume up to enter the recovery menu.

• Press volume down to select "apply update from ADB"
• Press power once.
• It will now tell you to type "adb sideload <filename>" so connect the Nexus 10 to your computer with the USB cable if you have not already done so.

• On the computer type "adb sideload eaef14432ff5.signed-mantaray-JDQ39-from-JOP40D.eaef1443.zip" and watch the magic happen.

App of the week on AndroidPIT.com

Starting today and ending on the 17th of Februari 23:59 (GMT+1), External Keyboard Helper Pro is App of the week on AndroidPIT.com.

That means you get buy it for only $1.48 (1.06€) during the campaign.

It's the end of the WoT as we know it...

The end is near, only about 900 pages away now... The last and final book of Wheel of Time, a fantastic story started by the late Robert Jordan and now finished by Brandon Sanderson.

I got it few days ago but haven't started reading yet. While waiting I've read through most of Brandon Sandersons books and I was halfway through Warbreaker when the book arrived and I wanted to finish it first. Before that I read through the Mistborn Trilogy, The Alloy of Law, The Way of Kings, Legion and The Emperor's soul.

12 years after I started reading the first Wheel of Time book I will now read the final volume. To bad Robert Jordan isn't here with us to see the completion of his masterpiece.

EKH Tutorial 6 - Workaround for Samsung devices

The is the sixth tutorial for External Keyboard Helper. You'll find a all the tutorials here.

This tutorials is only interesting for Samsung users. I'm going to use my Galaxy S3 as an example but the problem is present with most (if not all) Samsung firmwares.

The problem looks like this:

Just a little information popup, how could that be a problem? Well, once you press OK on the dialog it will change your Input Method to "Samsung Keyboard" so it's just not informing you what it thinks you should use, it also makes you use it whether you want it or not.

On my Galaxy S3 this pops up whenever I connect a Bluetooth keyboard but only if "Samsung Keyboard" is not the currently selected Input Method. So let's say I use SlideIT as my preferred Input Method:

 
Now let's say I connect my Bluetooth keyboard and since I'm using External Keyboard Helper it will show the Input Method selector. However first Samsung will show their dialog and then the Input Method selector puts itself on top of it.

So I first select External Keyboard Helper and then I get back to the Samsung dialog and press OK. What happens now is that the Input Method will be switched to "Samsung Keyboard" which is not what I wanted. Not good!

I do not think there is a way to prevent the Samsung dialog from starting unless you are rooted and willing to mess around on your system partition. Still there is a workaround, it's not perfect but it's better than nothing.

What we need to do is to increase the Detection delay in the Advanced settings for External Keyboard Helper. In this example I set it to 4 seconds but most people will probably settle for 2 seconds after getting used to the procedure.

Now we bought us 4 seconds where we can press OK in the Samsung dialog before External Keyboard Helper brings up the Input Method selector. What we do is that we let Samsung first set the Input Method to their own one and then we switch it back to External Keyboard Helper.

So by setting up a delay we can make sure that Samsungs switch takes place before our switch and not the other way around.