Latest Updates

View More Articles

Thursday, July 3, 2014

Setting Up Wearable Apps Development Environment In AndroidStudio

Today in this article i will cover google wearable apps development starting process in android studio . here in this article i will show how to start developing android wearable apps using android studio. before developing wear able apps you must to need configure android studio.
In Android Studio SDK Tools if you are not Show Google Play service Rev.18 Google Repository Rev.9 Complete the following steps to get special access to all the things you need to start developing.

Start SDK Manager.

Update the Android SDK Tools and Platform-tools to versions 23 and 20 respectively.
Click Tools > Manage Add-on Sites > User Defined Sites.

Click New,
Enter into the text field,
Click OK.

Click Close.

You should now see new Google Play service Rev.18 Google Repository Rev.9  Update it .
Run on the Emulator

To setup the Android Wear emulator install the latest Android API and updates lineup in the Android SDK Manager. Remember to install the ‘Android Wear ARM EABI v7a System Image’.

Then create Android Virtual Device (AVD) for Wear using the system image just updated. There are two skins available for the Android watch round and square. I have chose square watch.

Sunday, June 29, 2014

How to Using ActionBarSherlocka as library project in Android Studio

Today in this article i will discuses and implement ActionBarSherlocka . First we need to Know about ActionBarSherlocka

What is ActionBarSherlocka ?
ActionBarSherlock is an extension of the support library designed to facilitate the use of the action bar design pattern across all versions of Android with a single API.
The library will automatically use the native action bar when appropriate or will automatically wrap a custom implementation around your layouts. This allows you to easily develop an application with an action bar for every version of Android from 2.x and up.
Add Using Android Studio
In Android Studio, you might do it the Graphical user interface (GUI way).

Select the module
Click Dependencies
Click the green arrow
Select 1 Maven dependency
If you don't know actual full name of actionbersherlock simple Input sherlock and press enter to search
Wait few moment Maven Look up your search than finally you will see
Select com.actionbarsherlock:actionbarsherlock:4.4.0@aar Click OK

This will automatically add it to your build.gradle
Now Open your build.gradle File and see the actionbarsherlocka add as dependencies
dependencies {
    compile ''
    compile 'com.actionbarsherlock:actionbarsherlock:4.4.0@aar'

Importing Action Bar Sherlock Library to your Project
Open the Action Bar Sherlock Library you have downloaded earlier and extract it somewhere (for example to your ( C:\Users\aamsuzon\Downloads ). After extraction, the directory should look like this:
Copy the directory called "actionbarsherlock" to your Project Root directory. After copying, your Project Root directory should look like this:

Now we need to modify the settings.gradle to tell Gradle that we have to include another project on our build. settings.gradle is located on your Project Root ( YourApplicationProject/settings.gradle ).

Let us include the actionbarsherlock directory in your settings.gradle:
 include ':YourApplication', ':actionbarsherlock' 

Now your Gradle are ready to compile. But before you can start coding, we need to configure Android Studio and tell about the library.

Adding Action Bar Sherlock library to Android Studio

Select the module
Click Dependencies
Click the green arrow
Select  Module Dependency
Select the actionbarsherlock and then click Apply then OK to quit the Project Structure. Restart again the Android Studio.

You can now start coding your project using the Action Bar Sherlock.

Testing the Action Bar Sherlock

Open File in your project . Import this line

Now  lets change the Activity to SherlockActivity. We need to remove the onCreateOptionsMenu override method as this does not exists.
package com.example.yourapplication;

import android.os.Bundle;
//import android.view.Menu;


public class MainActivity extends SherlockActivity {

    protected void onCreate(Bundle savedInstanceState) {

/*    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
        // Inflate the menu; this adds items to the action bar if it is present.
        getMenuInflater().inflate(, menu);
        return true;

Almost Done Now we Just need to modify the AndroidManifest.xml of our application to change the theme to the Action Bar Sherlock library themes.
To Action Bar Sherlock Light Dark Theme apply add this line

Your application will now able to run the Action Bar Sherlock library

If you face any problem to do this please write a comment .

Saturday, June 21, 2014

Unable to upload new APK file to Android google Play store

today here is an common issue and solution most developer are do it in first time.when Generated Signed APK most are put Build Variant in Debug able . then the apk file are getting error when upload on play store .
 If you are getting below error while trying to upload new APK file in google play developer console.
Upload failed

You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play.

If you're using Android Studio, the simplest way is to open the "Build Variant" toolbar on the left bottom and change it from "Debug" to "Release" then "Build" -> "Generated Signed APK".

Build Variant Screen in android studio

change it from "Debug" to "Release"

Sunday, June 8, 2014

Android Studio: Unable to start the daemon process fix Solution

When import a gradle project in Android Studio you may facing the below error.
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at
Please read below process output to find out more:  

I'm Personally Face this problem and i will fix Solution for this problem. Basically when you update android studio & others Plugins  and import lot project android studio use separate version of gradle build. Sometimes You just open too much applications in Windows and make the gradle have no enough memory to start the daemon process.So you may face this type of problem .

Solution for Unable to start the daemon process
  1. First Close your android studio     
  2. Try deleting your C:\Users\aamsuzon\.gradle  directory.
  3. Now Open Android Studio & open the project 
  4. Synchronize the project gradle now android studio will create again .gradle directory under the user . 

Sunday, June 1, 2014

UNEXPECTED TOP-LEVEL EXCEPTION Multiple dex files define - Android Studio

Many time when you debug or deploy your apps you will face this type of problem  Error:Execution failed for task ':app:dexDebug'.  

the problem are duplicate dx.bat file that's why new file are not generated by IDE
Error:Execution failed for task ':app:dexDebug'.
> Failed to run command:
 C:\Android\android-studio\sdk\build-tools\19.0.3\dx.bat --dex --output C:\Newproject\TraditionalMehendi\app\build\dex\debug C:\Newproject\TraditionalMehendi\app\build\classes\debug C:\Newproject\TraditionalMehendi\app\build\dependency-cache\debug C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\classes-48d144ddea6f49f726182658d2cd8e370ccc3aaa.jar C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\classes-9f4d5885611b2cd25e7d8eab67c143627ce2b90e.jar C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\cordova-2.9.0-ed7f0ff9375df6df791502102448d1e17b9157d8.jar C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\google-play-services-951d8a946461792fa0ed722eaf024834954f8800.jar C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\libGoogleAnalyticsServices-b42dc6d8aa0346a80f1328d54575ffcd87dd725e.jar C:\Newproject\TraditionalMehendi\app\build\pre-dexed\debug\support-v4-19.1.0-949793351ba251d9ea726b83e38d287075a5b846.jar
Error Code:
 UNEXPECTED TOP-LEVEL EXCEPTION: Multiple dex files define Lcom/google/ads/AdRequest$ErrorCode;
Solution for Fix this problem :
1 . Your google play services library is being exported from other dependencies of your project and at the compile time the dex compiler gets confused.
If you're using Gradle then including this in your project's build.gradle should exclude the support library from being exported into your main project.
apply plugin: 'android'
apply plugin: 'crashlytics'

/** Must exclude exported support jars from dependencies, or get dex duplicate class      error.
*  we're
configurations {
    all*.exclude group: '', module: 'support-v4'
    all*.exclude group: '', module: 'play-services'
If you're using the andoid studio build system. Then you should go to File -> project structure and disable -> modules. Go through each module the and click on the dependency tab, uncheck the export column for for the support library and google play services library.

2.Make sure you have downloaded Support Repository to use support library dependency in build.gradle.

If these all are there already installed sync your project with gradle once using the button available.

3.Because you may include two same libs in your project. check your build.gradle file.
dependencies {
    compile ''
    compile files('libs/android-support-v4.jar') 
if your file includes compile '' and compile files('libs/android-support-v4.jar'), it will have this problems. delete this sentence: compile files('libs/android-support-v4.jar')
To Change Make it

dependencies {
    compile '' 
4. If you are try the way but not solve the problem than this this another way . hope you will solve the problem .

Simple go to  Project Folder Remove  .gradle  .idea  folder 
And Go to yourproject\apps\build Remove All Directory in this Build Folder Now go to Android Studio And sync your project with gradle once using the button. And Sunc the project you will now debug the apps hope you never face this problem in this project again
If you Again Face this Problem than Post A Comment Here I will hardly Try to Solve your problem 

Friday, May 9, 2014

how to install hibernate tools in android studio

Know About Hibernate :
Hibernate ORM (Hibernate in short) is an object-relational mapping library for the Java language, providing a framework for mapping an object-oriented domain model to a traditional relational database. Hibernate solves object-relational impedance mismatch problems by replacing direct persistence-related database accesses with high-level object handling functions.
Hibernate is a free software that is distributed under the GNU Lesser General Public License.
Hibernate's primary feature is mapping from Java classes to database tables (and from Java data types to SQL data types). Hibernate also provides data query and retrieval facilities. It generates SQL calls and relieves the developer from manual result set handling and object conversion. Applications using Hibernate are portable to supported SQL databases with little performance overhead Know more

Download Hibernate Tools :
First Download the file from here save it in your computer 
Download it – Hibernate Tools

Install Hibernate
Go to File -> Settings ->Plugins

From this Windows Click Install Plugin from disk..
From this Choose Plugin File brows your Hibernate Tools Download.jar file and click OK 
Now you will see Hibernate Tools Show on your Android Studio Plugins List Menu . and now we need to Apply And Restart Android Studio

Successfully Install the Hibernate Tools Plugins and Android Studio . now time to check the tools option in android studio After opening android studio see the Toolbar Menu you will see Hibernate Tools Look Blow Image
Right Click Project Show the Hibernate tools

Wednesday, May 7, 2014

How to install & configure Apache Maven

Maven is a build automation tool used primarily for Java projects. Maven addresses two aspects of building software:
First, it describes how software is built, and second, it describes its dependencies. Contrary to preceding tools like Apache Ant it uses conventions for the build procedure, and only exceptions need to be written down.
An XML file describes the software project being built, its dependencies on other external modules and components, the build order, directories, and required plug-ins.
It comes with pre-defined targets for performing certain well-defined tasks such as compilation of code and its packaging. 
Maven dynamically downloads Java libraries and Maven plug-ins from one or more repositories such as the Maven 2 Central Repository, and stores them in a local cache.
 This local cache of downloaded artifacts can also be updated with artifacts created by local projects. Public repositories can also be updated. More

Maven Installation
To begin with, download the latest Maven from
I downloaded and extracted it to C:\apache\apache-maven-3.2.1
Maven Configuration
Now Need to setting Environment Variables
Go to your System Properties Environment Variables.

Create a JAVA_HOME System Variable and point it to your Java installation. I pointed mine to C:\Java\jdk1.7.0_45.
Create an M2_HOME System Variable and point it to your Maven installation. I pointed mine to C:\apache\apache-maven-3.2.1.
You should now have JAVA_HOME and M2_HOME System Variables.
Add %JAVA_HOME%\bin;%M2_HOME%\bin; to your Path System Variable. This puts your Java and Maven executable in the System Path so that they can be executed without their fully qualified paths.

Open a command prompt window, and at the command prompt, type
 mvn -version
You should see a message displaying the version of MavenSW and the version of JavaSW.
Next, at the command prompt, try typing a command
mvn clean
You'll probably see that some jarW files downloaded from the Maven central repository to your machine. After that, we see a 'BUILD ERROR'. This message is fine. This is telling us that we ran the command but that there was no pom.xml file present in the directory where we ran the command.

After running the mvn clean, if we go to our user home directory ( for me, C:\Users\aamsuzon\.m2 ), we can see that an .m2 directory has been created by mavenSW. Within .m2, we can see a repository directory. This is the default location for your local maven repository.
This local repository directory contains things such as the jar files that your projects use. In addition, it contains the jar files and things that maven itself needs. When we ran the 'mvn clean' command, we asked maven to do a 'clean' command, which requires the maven-clean-plugin jar file. If you look back at the command prompt output after the 'mvn clean' command, you can see that the maven-clean-plugin jar file was downloaded, since maven realized that it needed this jar file in order to do the 'clean'.

Copyright @ 2014 Bijoy Technology .
The content is copyrighted to Abdullah Al Mahamud and may not be reproduced on other websites.