Category: Tips


It’s been a while since that leaked 4.3 rom for Nexus 4 is out in the wild. There are many guides out there which takes you through the steps for installing the rom on your device. I personally followed this guide to install it on mine. Since the download link mentioned in this post seems very slow, I resorted to Google to find if any other mirror is available to serve the rom. I strongly suggest downloading from this link instead, it’s fast and doesn’t seem to be overloaded with requests as of now. Also I followed this guide to boot into TWRP recovery instead of flashing it and replacing the stock recovery. Remember that this won’t flash your data but you should use the backup options available in recovery before flashing the rom.

Advertisements

Yes, that’s true. You can boot into any recovery of your choice on your Android phone by following this guide. No need to flash and replace the stock bootloader. Though I have tested this method on Nexus devices only but I am pretty sure that it’ll work on other phones as well. Custom recoveries give you a lot of options for performing some important tasks, like backup and restore your phone and wiping out caches.

Prerequisites

  • An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
  • ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
  • A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)

Guide

  1. Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
  2. Launch terminal (or command prompt on Windows).
  3. Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
  4. Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
  5. Connect your phone to your computer.
  6. On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
  7. Your phone will restart and will boot into the recovery mode.

That’s it. As simple as it can get!

Native dialogs in Android are boring! Open-mouthed smile if you are developing an app having some cool and customized theme then doing something about those dull dialogs is a must. They wouldn’t just compliment the overall look of your application. I faced this kinda scenario recently and while experimenting and trying different suggestions on forums, I finally got around it and made it to work!

First things first, as far as my experience went, AlertDialog is not going to help you here. It just don’t get rid of that black background that is there by default (talking about gingerbread dialogs here). No matter what you do, it’ll always show the black background from behind your image (if you have any). Anyways, to create a custom dialog, we need to create a layout first in a separate xml file. Here’s an example:

Capture

This is just a simple layout having a background image that has irregular borders. Now we just need to write a few lines of code in order to make it work:

Capture

Here, we are setting the background color to transparent in order to get rid of the default dialog background color. After that, we just need to assign the layout resource to the dialog and that gets the job done.

Notice the resultDlg.getWindow().clearFlags(WindowManager.LayoutParams.FLAG_DIM_BEHIND); This will remove the dim effect that makes your parent layout a bit darker. You can also set some additional flags like adding a blurred effect to the background/host activity from which this dialog is invoked. To do this, simply use the addFlags function with FLAG_BLUR_BEHIND flag. Here’s the exact statement:

resultDlg.getWindow().addFlags(WindowManager.LayoutParams.FLAG_BLUR_BEHIND);

This will create a very nice blur effect which I find more neat than the original dim effect. And that ends this post here. Feel free to comment and ask questions, I’ll try to answer them as swiftly as I can.

Quite a long title, isn’t it? Smile

On-screen keyboard usually takes around half of the screen space while it’s shown. Most of the times it hides important controls/views that you want to be shown to the user all the times. Consider a layout having a EditText widget at the top, a list or some other control in the middle and some Buttons right at the bottom. While the user is writing text in the EditText view through on-screen keyboard, the buttons would be hiding behind it. Luckily, Android has an option to handle this scenario automatically without writing much code.

To enable a layout to adjust itself while the keyboard is shown, you need to configure an attribute for its host activity through AndroidManifest.xml file. Here’s how to do it:

<activity android:name="TestActivity" android:windowSoftInputMode="adjustResize" android:screenOrientation="portrait">

By setting android:windowSoftinputMode of this activity to adjustResize you are telling it to resize itself while the on-screen keyboard is shown. This will let the activity to shorten it’s layout in order to show everything that’s present over it. For example, if you have some buttons at the bottom of the screen, this setting will show them just above the keyboard helping the user to interact with them without closing the keyboard.

There’s one important catch in this however, this configuration DOES NOT work if the application is bound to run in full-screen. This is normally done by setting it’s android:theme attribute to @android:style/Theme.NoTitleBar.FullScreen in AndroidManifest.xml file.

This is one simple and neat technique to make your layout more flexible and user-friendly.