Android

Android Advanced Interview Questions And Answers

2014-03-13T04:32:00.000-07:00

Q)Explain Service vs intent service ?

When to use?

The Service can be used in tasks with no UI, but shouldn't be too long. If you need to perform long tasks, you must use threads within Service.
The IntentService can be used in long tasks usually with no communication to Main Thread. If communication is required, can use Main Thread handler or broadcast intents. Another case of use is when callbacks are needed (Intent triggered tasks).

How to trigger?

The Service is triggered calling to method onStartService().
The IntentService is triggered using an Intent, it spawns a new worker thread and the method onHandleIntent() is called on this thread.

Triggered From

The Service may be triggered from any thread.
The IntentService must be triggered from Main Thread.

Runs On

The Service runs in background but it runs on the Main Thread of the application.
The IntentService runs on a separate worker thread.

Limitations / Drawbacks

The Service may block the Main Thread of the application.
The IntentService cannot run tasks in parallel. Hence all the consecutive intents will go into the message queue for the worker thread and will execute sequentially.

q) Difference between Service , Thread , IntentService, AsyncTask ?

	Service	Thread	IntentService	AsyncTask
When to use ?	Task with no UI, but shouldn't be too long. Use threads within service for long tasks.	- Long task in general. - For tasks in parallel use Multiple threads (traditional mechanisms)	- Long task usually with no communication to main thread. (Update)- If communication is required, can use main thread handler or broadcast intents - When callbacks are needed (Intent triggered tasks).	- Long task having to communicate with main thread. - For tasks in parallel use multiple instances OR Executor
Trigger	Call to method onStartService()	Thread start() method	Intent	Call to method execute()
Triggered From (thread)	Any thread	Any Thread	Main Thread (Intent is received on main thread and then worker thread is spawed)	Main Thread
Runs On (thread)	Main Thread	Its own thread	Separate worker thread	Worker thread. However, Main thread methods may be invoked in between to publish progress.
Limitations / Drawbacks	May block main thread	- Manual thread management - Code may become difficult to read	- Cannot run tasks in parallel. - Multiple intents are queued on the same worker thread.	- one instance can only be executed once (hence cannot run in a loop) - Must be created and executed from the Main thread

Some Android Advance Concept Links

2013-11-08T04:03:00.001-08:00

1) Android Content Providers :

http://tutorials-android.blogspot.in/2012/04/create-custom-or-own-content-provider.html

Details Explanation about Content providers :

https://thenewcircle.com/s/post/1375/android_content_provider_tutorial

2). Drawing with XML.

Drawing with XML means create Some Custom Button with user defined colors and user defined Back grounds using XML

http://tutorials-android.blogspot.in/2011/03/android-button-highlight.html

3) CANVAS Drawing Example ( this is Some sample project )

http://tutorials-android.blogspot.in/2013/11/android-simple-hand-drawing-on-canvas.html

4) Working with Google maps Extensions. ( this is Sample Basic Application )

http://www.androidhive.info/2013/08/android-working-with-google-maps-v2/

5) Managing HTTP Calls.

http://www.vogella.com/articles/AndroidNetworking/article.html

A) Make phone call

http://tutorials-android.blogspot.in/2012/04/how-to-make-phone-call-from-your.html

b) Send SMS

http://tutorials-android.blogspot.in/2013/11/how-to-send-sms-message-in-android.html

C) Check Network Connection

http://tutorials-android.blogspot.in/2011/09/android-how-to-check-network-statusboth.html

How To Send SMS Message In Android

2013-11-08T04:01:00.000-08:00

In Android, you can use SmsManager API or device’s Built-in SMS application to send a SMS message. In this tutorial, we show you two basic examples to send SMS message :

SmsManager API

	SmsManager smsManager = SmsManager.getDefault();
	smsManager.sendTextMessage("phoneNo", null, "sms message", null, null);

Built-in SMS application

	Intent sendIntent = new Intent(Intent.ACTION_VIEW);
	sendIntent.putExtra("sms_body", "default content"); 
	sendIntent.setType("vnd.android-dir/mms-sms");
	startActivity(sendIntent);

Of course, both need SEND_SMS permission.

<uses-permission android:name="android.permission.SEND_SMS" />

P.S This project is developed in Eclipse 3.7, and tested with Samsung Galaxy S2 (Android 2.3.3).

Note
The Built-in SMS application solution is the easiest way, because you let device handle everything for you.

1. SmsManager Example

Android layout file to textboxes (phone no, sms message) and button to send the SMS message.

File : res/layout/main.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/linearLayout1"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    android:orientation="vertical" >
 
    <TextView
        android:id="@+id/textViewPhoneNo"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Enter Phone Number : "
        android:textAppearance="?android:attr/textAppearanceLarge" />
 
    <EditText
        android:id="@+id/editTextPhoneNo"
        android:layout_width="fill_parent"
        android:layout_height="wrap_content"
        android:phoneNumber="true" >
    </EditText>
 
    <TextView
        android:id="@+id/textViewSMS"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Enter SMS Message : "
        android:textAppearance="?android:attr/textAppearanceLarge" />
 
    <EditText
        android:id="@+id/editTextSMS"
        android:layout_width="fill_parent"
        android:layout_height="wrap_content"
        android:inputType="textMultiLine"
        android:lines="5"
        android:gravity="top" />
 
    <Button
        android:id="@+id/buttonSend"
        android:layout_width="fill_parent"
        android:layout_height="wrap_content"
        android:text="Send" />
 
</LinearLayout>

File : SendSMSActivity.java – Activity to send SMS via SmsManager.

package com.mkyong.android;
 
import android.app.Activity;
import android.os.Bundle;
import android.telephony.SmsManager;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;
 
public class SendSMSActivity extends Activity {
 
	Button buttonSend;
	EditText textPhoneNo;
	EditText textSMS;
 
	@Override
	public void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.main);
 
		buttonSend = (Button) findViewById(R.id.buttonSend);
		textPhoneNo = (EditText) findViewById(R.id.editTextPhoneNo);
		textSMS = (EditText) findViewById(R.id.editTextSMS);

// main Logic to Send SMS 

	buttonSend.setOnClickListener(new OnClickListener() {


 @Override

public void onClick(View v) {
String phoneNo = textPhoneNo.getText().toString();
String sms = textSMS.getText().toString();
try {
SmsManager smsManager = SmsManager.getDefault();
smsManager.sendTextMessage(phoneNo, null, sms, null, null);
Toast.makeText(getApplicationContext(), "SMS Sent!",Toast.LENGTH_LONG).show();
} catch (Exception e) {
Toast.makeText(getApplicationContext(),"SMS faild, please try again later!",Toast.LENGTH_LONG).show();
 }
}
});
	}
}

File : AndroidManifest.xml , need SEND_SMS permission.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.mkyong.android"
    android:versionCode="1"
    android:versionName="1.0" >
 
    <uses-sdk android:minSdkVersion="10" />
 
    <uses-permission android:name="android.permission.SEND_SMS" />
 
    <application
        android:debuggable="true"
        android:icon="@drawable/ic_launcher"
        android:label="@string/app_name" >
        <activity
            android:label="@string/app_name"
            android:name=".SendSMSActivity" >
            <intent-filter >
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    </application>
 
</manifest>

See demo :

To call Built in Application in Your Activity

try {
Intent sendIntent = new Intent(Intent.ACTION_VIEW); sendIntent.putExtra("sms_body", "default content"); sendIntent.setType("vnd.android-dir/mms-sms"); startActivity(sendIntent);
} catch (Exception e) { Toast.makeText(getApplicationContext(),"SMS faild, please try again later!",
Toast.LENGTH_LONG).show(); e.printStackTrace(); }

ANDROID : SIMPLE HAND DRAWING ON CANVAS WITH ERASER.

2013-11-08T03:39:00.001-08:00

Sometimes we may need to create scratchpad in our Android application.
We can create it on CANVAS

First, create a main layout file for your activity.

<LinearLayout
         xmlns:android="http://schemas.android.com/apk/res/android"
                android:id="@+id/drawing_question"
                android:layout_width="match_parent"
                android:layout_height="match_parent"
                android:layout_marginLeft="40dp"
                android:layout_marginRight="30dp"
                android:background="#FFFFFF"
                android:orientation="horizontal" >

                <com.swap.handdrawing.DrawingView
                    android:id="@+id/drawing"
                    android:layout_width="0dp"
                    android:layout_height="fill_parent"
                    android:layout_marginBottom="10dp"
                    android:layout_marginRight="5dp"
                    android:layout_weight="1" >
                </com.swap.handdrawing.DrawingView>

                <LinearLayout
                    android:id="@+id/eraserView"
                    android:layout_width="50dp"
                    android:layout_height="fill_parent"
                    android:layout_marginBottom="10dp"
                    android:background="@drawable/custom_edit_text"
                    android:padding="5dp" >

                    <ImageView
                        android:id="@+id/eraser"
                        android:layout_width="40dp"
                        android:layout_height="40dp"
                        android:layout_gravity="center"
                        android:src="@drawable/eraser" />
                </LinearLayout>
</LinearLayout>

Next, create DrawingView class extending View & implementing OnTouchListener.

 
package com.swap.handdrawing;

import java.util.ArrayList;

import android.content.Context;
import android.graphics.Bitmap;
import android.graphics.Canvas;
import android.graphics.Color;
import android.graphics.Paint;
import android.graphics.Path;
import android.graphics.Point;
import android.graphics.Rect;
import android.graphics.drawable.BitmapDrawable;
import android.graphics.drawable.Drawable;
import android.util.AttributeSet;
import android.util.Log;
import android.util.Pair;
import android.view.MotionEvent;
import android.view.View;
import android.view.View.OnTouchListener;

public class DrawingView extends View implements OnTouchListener {
 private Canvas m_Canvas;

 private Path m_Path;

 private Paint m_Paint;

 ArrayList<Pair> paths = new ArrayList<Pair>();
 
 private float mX, mY;

 private static final float TOUCH_TOLERANCE = 4;

 public static boolean isEraserActive = false; 

 public DrawingView(Context context, AttributeSet attr) {
  super(context);
  setFocusable(true);
  setFocusableInTouchMode(true);

  setBackgroundColor(Color.WHITE);

  this.setOnTouchListener(this);

  onCanvasInitialization();
 }

 public void onCanvasInitialization() {
  m_Paint = new Paint();
  m_Paint.setAntiAlias(true);
  m_Paint.setDither(true);
  m_Paint.setColor(Color.parseColor("#000000")); 
  m_Paint.setStyle(Paint.Style.STROKE);
  m_Paint.setStrokeJoin(Paint.Join.ROUND);
  m_Paint.setStrokeCap(Paint.Cap.ROUND);
  m_Paint.setStrokeWidth(2);

  m_Canvas = new Canvas();
 
  m_Path = new Path();
  Paint newPaint = new Paint(m_Paint);
  paths.add(new Pair(m_Path, newPaint));
 
 }

 @Override
 protected void onSizeChanged(int w, int h, int oldw, int oldh) {
  super.onSizeChanged(w, h, oldw, oldh);
 }

 public boolean onTouch(View arg0, MotionEvent event) {
  float x = event.getX();
  float y = event.getY();

  switch (event.getAction()) {
  case MotionEvent.ACTION_DOWN:
   touch_start(x, y);
   invalidate();
   break;
  case MotionEvent.ACTION_MOVE:
   touch_move(x, y);
   invalidate();
   break;
  case MotionEvent.ACTION_UP:
   touch_up();
   invalidate();
   break;
  }
  return true;
 }

 @Override
 protected void onDraw(Canvas canvas) {
  for (Pair p : paths) {
   canvas.drawPath(p.first, p.second);
  }
 }

 private void touch_start(float x, float y) {

  if (isEraserActive) {
   m_Paint.setColor(Color.WHITE);
   m_Paint.setStrokeWidth(6);
   Paint newPaint = new Paint(m_Paint); // Clones the mPaint object
   paths.add(new Pair(m_Path, newPaint));
  } else { 
   m_Paint.setColor(Color.BLACK);
   m_Paint.setStrokeWidth(2);
   Paint newPaint = new Paint(m_Paint); // Clones the mPaint object
   paths.add(new Pair(m_Path, newPaint));
  }
 
  m_Path.reset();
  m_Path.moveTo(x, y);
  mX = x;
  mY = y;
 }

 private void touch_move(float x, float y) {
  float dx = Math.abs(x - mX);
  float dy = Math.abs(y - mY);
  if (dx >= TOUCH_TOLERANCE || dy >= TOUCH_TOLERANCE) {
   m_Path.quadTo(mX, mY, (x + mX) / 2, (y + mY) / 2);
   mX = x;
   mY = y;
  }
 }

 private void touch_up() {
  m_Path.lineTo(mX, mY);

  // commit the path to our offscreen
  m_Canvas.drawPath(m_Path, m_Paint);

  // kill this so we don't double draw
  m_Path = new Path();
  Paint newPaint = new Paint(m_Paint); // Clones the mPaint object
  paths.add(new Pair(m_Path, newPaint));
 }   
}

Then access DrawingView in your MainActivity. Toggle between eraser & pencil by changing isEraserActive & it’s image.

package com.swap.handdrawing;

import android.app.Activity;
import android.os.Bundle;
import android.view.Menu;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.ImageView;

public class MainActivity extends Activity {

 private ImageView eraser;


 @Override
 protected void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  setContentView(R.layout.activity_main);

  final DrawingView drawingView = (DrawingView) findViewById(R.id.drawing);

  eraser = (ImageView) findViewById(R.id.eraser);
  eraser.setOnClickListener(new OnClickListener() {

   @Override
   public void onClick(View v) {

    if (drawingView.isEraserActive) {
     drawingView.isEraserActive = false;

     eraser.setImageResource(R.drawable.eraser);

    } else {
     drawingView.isEraserActive = true;

     eraser.setImageResource(R.drawable.pencil);
    }

   }
  });

 }

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

}

You can get resources & drawables used in above tutorial by downloading source code. You can add colors to your drawing by changing color of path.

Any suggestions are always welcome.

Download Source Code

How to load Android app from Eclipse to my Android phone instead of AVD

2013-10-16T23:03:00.000-07:00

For TAB 3 Download Samsung Kies

First you need to enable USB debugging on your phone, then connect it to your computer via USB. Then eclipse should automatically start debugging on your phone instead of the AVD.

3 : After install Kies Restart Your system .

4: Go to Run Configuration

You can see three Columns Android,Target and Common.

Step5

Select the Target

Step 6

Choose Always prompt to pick device.Click Ok

Step 7

Now run your project you should see the emulator and your device. Select your device and click ok.

Hope it helps.

Android Architecture – The Key Concepts of Android OS

2013-09-01T23:12:00.001-07:00

In the earlier post on Android Development, we’ve learned how to install and setup a complete Android development environment. Now, before we start development, you should know the Android architecture in detail.

Being an Android user you may know how the basic functions such as making a call, sending a text message, changing the system settings, install or uninstall apps etc. Well! All Android users know these, but not enough for a developer. Then what else details are a developer required to know about Android, I’ll explain. To be a developer, you should know all the key concepts of Android. That is, you should know all the nuts and bolts of Android OS.

Here we start:
Android Architecture Diagram:

The above figure shows the diagram of Android Architecture. The Android OS can be referred to as a software stack of different layers, where each layer is a group of sveral program components. Together it includes operating system, middleware and important applications. Each layer in the architecture provides different services to the layer just above it. We will examine the features of each layer in detail.
Linux Kernel

The basic layer is the Linux kernel. The whole Android OS is built on top of the Linux 2.6 Kernel with some further architectural changes made by Google. It is this Linux that interacts with the hardware and contains all the essential hardware drivers. Drivers are programs that control and communicate with the hardware. For example, consider the Bluetooth function. All devices has a Bluetooth hardware in it. Therefore the kernel must include a Bluetooth driver to communicate with the Bluetooth hardware. The Linux kernel also acts as an abstraction layer between the hardware and other software layers. Android uses the Linux for all its core functionality such as Memory management, process management, networking, security settings etc. As the Android is built on a most popular and proven foundation, it made the porting of Android to variety of hardware, a relatively painless task.
Libraries

The next layer is the Android’s native libraries. It is this layer that enables the device to handle different types of data. These libraries are written in c or c++ language and are specific for a particular hardware.

Some of the important native libraries include the following:

Surface Manager: It is used for compositing window manager with off-screen buffering. Off-screen buffering means you cant directly draw into the screen, but your drawings go to the off-screen buffer. There it is combined with other drawings and form the final screen the user will see. This off screen buffer is the reason behind the transparency of windows.

Media framework: Media framework provides different media codecs allowing the recording and playback of different media formats

SQLite: SQLite is the database engine used in android for data storage purposes

WebKit: It is the browser engine used to display HTML content

OpenGL: Used to render 2D or 3D graphics content to the screen
Android Runtime

Android Runtime consists of Dalvik Virtual machine and Core Java libraries.

Dalvik Virtual Machine

It is a type of JVM used in android devices to run apps and is optimized for low processing power and low memory environments. Unlike the JVM, the Dalvik Virtual Machine doesn’t run .class files, instead it runs .dex files. .dex files are built from .class file at the time of compilation and provides hifger efficiency in low resource environments. The Dalvik VM allows multiple instance of Virtual machine to be created simultaneously providing security, isolation, memory management and threading support. It is developed by Dan Bornstein of Google.

Core Java Libraries
These are different from Java SE and Java ME libraries. However these libraries provides most of the functionalities defined in the Java SE libraries.
Application Framework

These are the blocks that our applications directly interacts with. These programs manage the basic functions of phone like resource management, voice call management etc. As a developer, you just consider these are some basic tools with which we are building our applications.

Important blocks of Application framework are:

Activity Manager: Manages the activity life cycle of applications

Content Providers: Manage the data sharing between applications

Telephony Manager: Manages all voice calls. We use telephony manager if we want to access voice calls in our application.

Location Manager: Location management, using GPS or cell tower

Resource Manager: Manage the various types of resources we use in our Application
Applications

Applications are the top layer in the Android architecture and this is where our applications are gonna fit. Several standard applications comes pre-installed with every device, such as:
SMS client app
Dialer
Web browser
Contact manager

As a developer we are able to write an app which replace any existing system app. That is, you are not limited in accessing any particular feature. You are practically limitless and can whatever you want to do with the android (as long as the users of your app permits it). Thus Android is opening endless opportunities to the developer.

How to Intercept HOME Key in Android?

2013-08-29T22:23:00.000-07:00

The solution is:

The prevailing wisdom says it cannot be done

public static final int KEYCODE_HOME

Key code constant: Home key. This key is handled by the framework and is never delivered to applications.

Maybe the below code would work the way we want it to. But I don't think you can trap the Home key absolutely.

Below method works for me. Hope this will work for you also....

Override below method in your activity.

@Override

public void onAttachedToWindow() {

super.onAttachedToWindow();

this.getWindow().setType(WindowManager.LayoutParams.TYPE_KEYGUARD);

}

After overriding above method, now you can easily listen HOME Key press in your activity using onKeyDown() method.

@Override

public boolean onKeyDown(int keyCode, KeyEvent event) {

if(keyCode == KeyEvent.KEYCODE_HOME)

{

//The Code Want to Perform.

}

});

Detect home button press in android and Notify when Our app is Closed

2013-08-29T22:16:00.000-07:00

In this Code I am explaining how to Notify when app is closed using Home button or Exit Button

From ICS to android not Supporting major Events when app is closed , so we can not now beofre application close , but using activity manager we can get Running app Package name and Its contained Activity class

use below code in your onPause so When ever your application close it returns true

// Method to Check Our app is running or Not
public static boolean isAppSentToBackground(final Context context) {
ActivityManager am = (ActivityManager) context.getSystemService(Context.ACTIVITY_SERVICE);
List<RunningTaskInfo> tasks = am.getRunningTasks(1);
if (!tasks.isEmpty()) {
ComponentName topActivity = tasks.get(0).topActivity;
if (!topActivity.getPackageName().equals(context.getPackageName())) {
Log.w(" YES TRUE ", "isAppSentToBackground ");
return true;
}
}
Log.w(" YES FALSE ", "isAppSentToBackground ");
return false;
}

// Checking while App is closed in Onpause or onStart or OnDestroy

mCtx=getApplicationContext();

@Override

protected void onPause() {

super.onPause();

if (isAppSentToBackground(mCtx)) {

// Do what ever you want after app close

// simply Close session

}

Session idle timeout in Google Android

2013-08-29T22:01:00.000-07:00

Control_Activity.java

package com.eae.time_out_application;
import android.app.Application;
import android.content.Intent;
import android.os.CountDownTimer;
import android.util.Log;

public class Control_Activity extends Application{

int count=0;
MyCounter timer;

private static final String TAG=Control_Activity.class.getName();

@Override
public void onCreate()
{
super.onCreate();
timer = new MyCounter(30000,1000);
timer.start();
  }

public void touch()
{
timer.start();
}

public class MyCounter extends CountDownTimer{

public MyCounter(long millisInFuture, long countDownInterval) {
super(millisInFuture, countDownInterval);
}

@Override
public void onFinish() {
System.out.println("Timer Completed.");
Log.e("finish is called", "finish is called");
Intent intent = new Intent();
intent.setClass(Control_Activity.this, Login_Page.class);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
startActivity(intent);
}

@Override
public void onTick(long millisUntilFinished) {
System.out.println("Timer : " + (millisUntilFinished/1000));
}
}

}

Control_Application.java

package com.eae.time_out_application;

import android.app.Activity;
import android.os.Bundle;
import android.util.Log;
import android.widget.RelativeLayout;

public class Control_Application extends Activity {

RelativeLayout mylayout;
private static final String TAG = Control_Application.class.getName();

/**
* Gets reference to global Application
* @return must always be type of ControlApplication! See AndroidManifest.xml
*/
public Control_Activity getApp()
{
return (Control_Activity )this.getApplication();
}

@Override
protected void onCreate(Bundle savedInstanceState) {
// TODO Auto-generated method stub
super.onCreate(savedInstanceState);
//setContentView(R.layout.activity_control__application);

}

@Override
protected void onDestroy() {
// TODO Auto-generated method stub
super.onDestroy();

}

@Override
public void onUserInteraction()
{
super.onUserInteraction();
getApp().touch();
Log.d(TAG, "User interaction to "+this.toString());
Log.e("My Activity Touched", "My Activity Touched");
   }

}

Login Page.java

package com.eae.time_out_application;

import android.app.Activity;
import android.os.Bundle;

public class Login_Page extends Activity{

@Override
protected void onCreate(Bundle savedInstanceState) {
// TODO Auto-generated method stub
super.onCreate(savedInstanceState);
setContentView(R.layout.login_page);
}

}

main.xml

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingBottom="@dimen/activity_vertical_margin"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
tools:context=".Control_Application"
android:id="@+id/totallayout">

<Button
android:id="@+id/button1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignParentLeft="true"
android:layout_alignParentTop="true"
android:layout_marginLeft="88dp"
android:layout_marginTop="44dp"
android:text="Button" />

<RatingBar
android:id="@+id/ratingBar1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_below="@+id/button1"
android:layout_centerHorizontal="true"
android:layout_marginTop="55dp" />

<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignLeft="@+id/button1"
android:layout_alignParentTop="true"
android:text="Large Text"
android:textAppearance="?android:attr/textAppearanceLarge" />

</RelativeLayout>

loginpage.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical" >

<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="TextView" />

<EditText
android:id="@+id/editText1"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:ems="10"
android:inputType="textPersonName" >

<requestFocus />
</EditText>

<TextView
android:id="@+id/textView2"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="TextView" />

<EditText
android:id="@+id/editText2"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:ems="10"
android:inputType="textPassword" />

<Button
android:id="@+id/button1"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="20dip"
android:text="Login" />

</LinearLayout>

Manifest.xml

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.eae.time_out_application"
android:versionCode="1"
android:versionName="1.0" >

<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="17" />

<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme"
android:name="com.eae.time_out_application.Control_Activity" >
<activity
android:name="com.eae.time_out_application.Control_Application"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />

<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:name="com.eae.time_out_application.Login_Page" />
</application>

</manifest>

Simply copy and past the code and run it.

If u have any doubts please reply to me

Thank You

Ten Job Search Rules to Break

2013-08-14T01:27:00.000-07:00

One of our clients – we'll call her Linda – got a job offer from a global oil & gas company last week. Her hiring manager, Jack, left a voicemail message to tell Linda that an offer letter was on its way. Next came an email message from the company's recruiter, sharing the same news.

Finally, a Fedex package arrived in the mail with the hard copy of Linda's offer letter.

"Gotta be honest, I didn't love the process right at the end," Linda told me.

"Jack called to say the offer was coming. Sarah Jane in HR sent an email message with the same news. Then the offer arrived – but nobody ever talked to me about what would be in it. They just sent it and told me it was coming, and they both used asynchronous means to convey the news, kind of a weenie move if you ask me."

"How does that make you feel?" I asked her.

"I still want to take the job, but I'm going to call Jack and lay it out straight," Linda said. "They've told me in a million ways during the interview process that they need me to get in there and help them step their game up. I guess this is my first chance to do that."

Linda called Jack and told him she'd been startled to get an offer whose contents were a mystery to her until she opened the package. Why wouldn't Jack have called her to talk about the offer before sending a hard copy (by Fedex, no less)?, she wondered.

"I had left you a voicemail a week ago, hoping to connect and talk about specifics," she said. "I know you're busy. I had the impression from you and others in the company that this is a high-priority role. It seems as though a live conversation by phone to talk about the offer details would have been an important step to take before committing anything to paper."

Jack reflected.

"You're absolutely right, Linda," he said. "I had the same reaction when I was being hired here two years ago, and to tell you the truth the same thought went through my head and I didn't say anything. I'm glad you brought it up. I have to be honest, I don't quite know how that pre-offer conversation would go. I haven't had one of those discussions before. Got any tips for me?"

Linda shared the Supposal™ process she had learned at a Human Workplace workshop. ASupposal™ conversation is one that says "I'm not making you a job offer at this moment, but we're moving in that direction. Supposing we were to make you an offer (and this conversation is part of the process that gets us there), what would that offer need to look like in order for you to accept it on the spot?"

Jack was grateful for the Supposal™ advice, and the conversation moved on to the specifics of Linda's offer. Linda and Jack ended up in a one-hour phone conversation that ended with a change in Linda's title, a shift in her bonus plan and most significantly, a reorganization in the Product Development group that gives Linda greater scope in her new role.

"I am SO glad I called Jack and told him the truth," she said.

We're not coached to tell the truth when we're job-hunting. We're told to be whoever we think the employer wants us to be, playing the part of a person who has our experience and talents but none of our quirks, complications or entanglements – and certainly none of our authentic feelings in evidence!

We're coached to grovel, beg and kiss whatever tush appears in front of us when we're job-hunting. It's heinous how we expect job-seekers to bow and scrape on a job search – and for what? All that bowing and scraping doesn't help anybody get hired, much less help companies make better products or outperform their competitors.

It's a new day on the job search front. Every organization has problems – we call those problems Business Pain – and they need people who can solve those problems and alleviate their pain. You bring all kinds of powerful medicine with you to a new job, so why would anyone expect you to grovel?

Remember: only the people who get you deserve you.

Here are ten traditional job search rules I hope you'll start breaking the second you get the chance.

Ten Job Search Rules to Break

1. Follow the defined process.

This is the first rule I want you to break. For many people it's the hardest one to ignore, because of all the follow-the-rules Kool-Aid we've drunk over the years.

We've been trained since childhood to do what we're told to do. The Black Hole will eat your resume and shred its atoms, but people keep lobbing resumes into those gaping corporate recruiting portals nonetheless. Don't do it! Reach your hiring manager directly with a Human-Voiced Resume™ and PainLetter™ instead.

2. If you know someone in the company, give that person your resume and tell them to give it to the hiring manager.

Just like in other kinds of marketing and sales efforts, your job search needs to focus on your message, your audience and the best channel to connect them. Your friend inside the company may be a great channel partner for you or a wretched one.

What good does it do to have your friend trudge down the hall to HR or even the hiring manager's office if your resume just gets dumped on a desk or re-routed right back into the same Black Hole you were trying to avoid?

Choose the most powerful channel for your job search, whether the channel is an intermediary friend, the direct approach via Pain Letter™, or a third-party recruiter. Don't assume that your in-house friend is your best job-search conduit.

3. Use a traditional zombie-style resume and cover letter.

Are you a zombie? I doubt it – zombies can't read. You're a creative, colorful and vibrant person, so don't brand yourself using zombie-style jargon like "Results-oriented professional with a bottom line orientation!" (Ropwablo for short.)

You can sound like yourself in your resume, and you'll make a stronger impression on a hiring manager if you do. As for your cover letter, toss that out the window and write a compelling Pain Letter™, instead.

4. In your overture to employers, emphasize the way your background matches the job spec.

If you have already held a job, you know that the typical job spec has as much in common with the actual job as I have in common withHuckleberry Hound. Focus on the pain behind the job ad, rather than the goofy and often arbitrary (not to mention delusional) bullets in the job ad.

5. Spend most of your energy applying for posted jobs, and do so online.

If you want to feel discouraged, isolated and very, very tiny on your job search, spend your days lobbing resumes into the gaping maw of the Black Hole. If you want to get your brand and story out, build your muscles and start pithy conversations with real people, step away from the Black Hole and take a more active role in your job search.

Split your job-search time three ways in equal proportions: spend one-third of your available time and energy responding to posted job ads, one-third of it reaching out to target employers whether or not they have jobs posted, and the final one-third networking.

6. Use your networking time and energy letting people know about your job search, your specific skills and how each friend can help you.

Your friends are awesome because they support you, not because they know hiring managers or might have an inside track on a certain opportunity. Use your networking to counsel your friends (nothing grows mojo better than coaching someone else) and to get their moral support in return.

Networking is for building glue, not trying to turn your friends into means to your job-search end. When people get jobs through networking – and they do, every day – it's because they focused on the relationship, not the transaction.

7. If you're asked to report your salary history, share every detail going back as far as the employer asks you to.

Why would an organization consider hiring you if they don't trust you? If they ask you to verify every salary you've ever had and you say "Fine!", what will the next request be: the names of the presidential candidates you've voted for, or the list of people you've gone past second base with? Keep your salary history to yourself.

8. When the employer asks you to jump, do it.

Remember Linda, way back in the first paragraph? She spoke her truth, let her new manager rise to the challenge she presented him, and walked away with a huge win. Don't start a new relationship by playing Doormat Guy (or Gal). A hiring manager will never love you more than they do the week before they hire you. If the love isn't showing in the interview process, run away fast.

9. Don't bring up the topic of salary – let the employer bring it up.

We demolished this bad advice over here.

10. Do whatever you need to do and say whatever you need to say to get the job.

When you swap your integrity for money, you are done. Your flame will get dimmer and dimmer that way. Survival is paramount, of course – you can take a survival job as a maitre d'or selling suits if you need to. You can even take a survival job in your industry in a firm or a role that doesn't feel great, just to tide you over. That's a perfectly fine strategy.

Just don't delude yourself that the survival job is anything more than that, and don't stop looking for something better and settle for a bad situation instead. If the water in the fishbowl looks murky from the outside as a job-seeker, you can bet it's even dirtier on the inside.

Stay yourself on the job search trail. The quicker you say "No thanks" to the wrong opportunities, the faster your awesome new assignment can roll in – the one that deserves your talents.

BONUS! Q & A

So Liz, how do I avoid making a job interview like a citizenship exam, where I answer each question and then sit there like a dork and wait for the next question?

You do that by answering the question (in depth or just a little) and then asking your own question back. Here's an example:

SALLY, HIRING MANAGER: So Linus, have you used Framemaker much?

LINUS, JOB-SEEKER: A bit – tell me, how do you use Framemaker here?

SALLY: Well, we create a lot of documentation and we use it for version control and so on.

LINUS: Do you want to hear a quick version-control story? It's a topic near and dear to course developers, as you can imagine.

SALLY: Sure!

LINUS: Well, one time at Acme Explosives we had a situation with a beep bop biddem boddem waddem chu...

... and off you go. Don't be passive on a job interview. Make it a human conversation!

=========================================================================

I don't know who Mumford & Sons is either, but I have a 20-year-old daughter and she told me to use Mumford & Sons in this badge (below). This is also the badge for our 12-week virtual coaching group JOB SEARCH AFTER FIFTY that begins August 24th.

If you want to send me a LinkedIn invitation at liz@humanworkplace.com, please do! In that case please send me a joke or a palindrome in the invitation. Thanks!

JOIN Human Workplace when you have time, and JOIN our LinkedIn group, too!

LIKE us on Facebook and follow us on Twitter (@humanworkplace)!

Our mission at Human Workplace is to reinvent work and career education for people. We're fanatical about people and their spirit, energy, creativity, randomness, resourcefulness, warmth and wit.

We're out to dismantle the destructive and mojo-sucking Godzilla structure of fear-based rules, policies, overpowering hierarchy and red tape that siphons the life out of organizations and keeps them from doing anything new or worthwhile.

We know there's a better way to lead people than that.

We teach Human Workplace ideas and methodologies, we promote them and we sing about them (no joke: listen to this podcast) and talk about them in our webinars and live presentations. Join the Human Workplace movement. We are bringing work to life and bringing life to work!

ScrollView inside ScrollView (Inner scrollview not scrollable)

2013-07-31T21:25:00.000-07:00

UI :
---

<ScrollView android:id="@+id/parent_scroll"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_weight="1"
android:focusableInTouchMode="false">

<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical" >

<ScrollView
android:id="@+id/child_scroll"
android:layout_width="fill_parent"
android:layout_height="100dp" >

<TextView
android:id="@+id/text_description"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:padding="5dip"
android:scrollbars="vertical"
android:text="Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."
android:textAppearance="?android:attr/textAppearanceLarge" />

</ScrollView>

<ImageView
android:id="@+id/imageView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_margin="10dp"
android:scaleType="fitXY"
android:src="@drawable/a" />

<ScrollView
android:id="@+id/scrollView1"

android:layout_width="match_parent"

android:layout_height="wrap_content" >

<LinearLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical" >

<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?"
android:textAppearance="?android:attr/textAppearanceLarge" />

</LinearLayout>
</ScrollView>

</LinearLayout>
</ScrollView>

Java :

MainActivity.java
public class MainActivity extends Activity {

private ScrollView parentScroll, childScroll;
private String TAG = "SNS";

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
parentScroll=(ScrollView)findViewById(R.id.parent_scroll);
childScroll=(ScrollView)findViewById(R.id.child_scroll);

parentScroll.setOnTouchListener(new View.OnTouchListener() {

public boolean onTouch(View v, MotionEvent event) {
Log.v(TAG,"PARENT TOUCH");
findViewById(R.id.child_scroll).getParent().requestDisallowInterceptTouchEvent(false);
return false;
}
});
childScroll.setOnTouchListener(new View.OnTouchListener() {

public boolean onTouch(View v, MotionEvent event)
{
Log.v(TAG,"CHILD TOUCH");
// Disallow the touch request for parent scroll on touch of child view
v.getParent().requestDisallowInterceptTouchEvent(true);
return false;
}
});
}
}

Top Programming Mistakes You Should Stop Making

2013-07-31T04:05:00.000-07:00

When you start out as a programmer, you can easily fall into the habit of following bad practices while programming.

As a programmer, you can't avoid mistakes and that's part of learning your programming lessons. You'll make many mistakes in your career - some unique, some common ones - and that's how you'll learn to avoid them in future.

But if you are a beginner, you'll likely make some mistakes more often than others. How do you avoid these common mistakes that many programmers do everyday?

To avoid any mistake, you've to become aware of it. And that's why I would like to share with you some common mistakes that many of us still do that keeps us from growing as a programmer.

But before I share that with you, you may want to know how do I know that these are mistakes and not the right methods?

There is a simple answer - I have done all of them at some point in my career. Some more often, while some only a few times. And I regretted doing them later.

But I didn't knew then that I was doing anything wrong by following such bad practices. Once I realized that I was doing the wrong thing I started avoiding them. And now my code is at least better than what I wrote before.

And you too can avoid doing such mistakes. Part of the solution is just to realize that what you're doing is wrong. I know that most programmers won't do anything wrong, if they knew right then that their actions can have a negative impact on their application and their professional growth.

Most of our wrong programming habits are due to our ignorance and nothing else.

To become a good programmer, we have to remove these ignorances one by one. And that's what good programming books try to show us.

Part of the reason that we do such mistakes is because they do get the work done. And isn't that what we are payed to do - make our programs run, and finish our day's work.

But to make something work is only part of your job. If your application is any good, you'll have to update it regularly, and fix any new bugs that may arise from time to time. And then the only thing that'll make your work easier is following good programming practices.

Also, while you can get away with such mistakes in small programs, you simply can't afford them when you make bigger applications.

If you still do them, your application may work and do the needful tasks. But it'll be buggy, full of unoptimized code, and hard to maintain. And even you'll find it difficult to understand the code, when you look at it after long time.

As programmers our job isn't just to make our applications work and let the users deal with the bugs. Our job is to make sure that there is no way users get undesired results even if they give it wrong input.

So to create high-quality applications, make sure you don't do these common mistakes while programming:

Copy-pasting code without understanding it

Often you'll find that the code you are looking for is already available in some other program. It's very tempting to copy the code entirely and use it as it is, without bothering to understand each and every line of it.

Sometimes, the code you are copying may be so large that you don't have time to understand it completely. If you copy any code this way, there is a risk of making your applications vulnerable and buggy.

While this may get the job done, but what if the code does some undesirable activities in the background. What if it slows down your application or does some malicious activity. For that you need to understand the code properly, or you need to be absolutely sure of the source from which you copied your code.

And if any bugs do arise later, you'll find it hard to understand the code as you didn't even write it. And you'll find it hard to trace out a bug and fix it, especially if you copy lots of code at different places in your program.

So be careful when you copy even a little piece of code. Make sure you understand it completely. If you have already used a piece of code before and are 100% sure about the way it runs, then it's safe to copy it. But otherwise be cautious.

Starting from scratch every time

This goes exactly opposite to what I said before but it's another mistake that many beginners do. You may think that it's best to start from scratchevery time you create a new application. But that's a huge waste of resources - your time, energy, and mind - that can be better used elsewhere.

If something you need to do is already out there, use it and make your job easier. There is no need to reinvent the same basic concepts again and again.

You can use the same time to make your application more better in other aspects.

If an API, framework, or game engine eases your task, there is no reason you shouldn't use it. Your goal shouldn't be to show off how talented you are, and how you can do everything on your own without anyone's help. Your goal should be to make sure that your application works perfectly, and it takes as little resources as possible to create it.

This way you can do the same work in less time and save tens or even hundreds of hours. And as time is money, even if you work for yourself, you earn more for the same amount of time.

Searching google without trying yourself

Many times, by habit, as soon as you come across a new problem, you hit google and search for solutions. This isn't the way to become a good programmer. If you always search for solutions outside, without even trying once on your own, you'll never challenge your mind.

When you stop challenging your mind, you stop growing thoseprogramming skills inside you. To become good at any skill you have to solve new problems on your own. That applies to programming too.

Else you'll only create what's already there. You'll never create any original work. Is that something you want to do?

While it's smart to look for existing solutions, but if you blindly do it, your laziness will stop you from becoming a better programmer. Even if you do want to look for solutions, it's alright, but first at least spend some time and think upon the problem.

Maybe you can solve it on your own without wasting much time. Maybe you can solve it in a better way than what others have done. Maybe your solution is more accurate than the other ones.

You'll never know these if you don't try.

Ignoring warnings

This is another mistake that I did earlier while developing applications. I can't tell you what a huge difference it makes when your application shows a hundred warnings and when it doesn't show even one - the most important being the ease with which you can recognize new problems.

Warnings are a sign that you are potentially trying to do something that may not work every time. Sometimes, these warnings aren't serious and it's safe to ignore them. But the real problem comes when you have a big application that shows hundreds of warnings, and something doesn't work right.

It becomes difficult to find the cause of that error. And you have to spend more time to analyze each warning and to find the root cause of the problem. Instead it's always better to resolve any warning issues at the start itself, as soon as they arise.

And usually you just need to use the right variables or functions to resolve most warnings. It doesn't take hours to do so; mostly a few minutes, if you remove them as soon as you come across them.

Try to remove any warnings as early as possible. A clean code not only looks good but works good too. Just remember the old saying - treat warnings as errors.

Making Quick fixes instead of Permanent ones

Yes. I am guilty of doing this one too. And I am not proud of it. So often, we just come up with a quick fix that's barely enough to solve the problem at hand.

And it works and makes the problem go away. But if you aren't careful it ends up coming back again and again in different ways.

Whenever you fix a problem, make sure that it doesn't break the system in any way. A fix should improve the overall working of a system, not make it slower or more bulkier.

Also, make a fix that'll solve the problem permanently. Think of long-term, not just short-term. Sometimes, due to our laziness or ignorance, we just want to do our work quickly, instead of spending more time on it. And that's why we write code that does the intended work, but might not work in all possible scenarios.

If you skip on doing your work now, you'll only have to work even more on that problem later.

Just knowing these above mistakes can help you in avoiding them. If you know what you're doing is wrong, most times you won't do it.

And to do a good job you should love what you do. If you don't like programming for some reason then you'll rarely take the extra steps that are needed to write good, maintainable programs.

And if you do intend to write such good programs then you need tochange the way you look at programming.

Think of programming as an art and yourself as an artist. Then you'll never make this mistake of being lazy or careless.

Would a writer write incomplete article and publish it? Would a painter leave his painting incomplete and sell it? Would a singer just sing any useless words between his songs?

Definitely not.

The same applies to programming. Don't write incomplete code that doesn't test all scenarios. Don't leave your application unfinished and ship it. Don't write useless code if you can do without it.

These are just some basic mistakes that we do, because we are tempted to do less work and do something else. But we can't go far with this approach. Sooner or later, you have to become responsible for your work and make sure that there is no flaw in your code.

The sooner you start practicing the right programming methods, the better it'll be for you and your users. Sometimes being a good programmer means just to make sure that you don't do the same mistakes that bad programmers do.

Thanks for reading this post. If you know anyone who unknowingly follows such programming practices please share this post with them and help them become a better programmer.

How to pass command line arguments in eclipse java ?

2013-07-23T21:01:00.004-07:00

If you use the Eclipse IDE, and want to be able to send command line arguments to your application, then there is an easy solution.

Firstly, select & highlight the class you are working on:

Go to Run > Run Configurations

Select the Arguments tab

In the Program arguments box, you can put whatever arguments you wish the same as if you were specifying them on the command line.

In this case, we want to send the argument dictionary.txt
Once you have filled in the Program arguments box, click Apply. Or if you wish to run the application, click Run
Done! This command line argument will be sent every time you compile the code.

Android Sample Application For Learners

2013-03-04T07:41:00.003-08:00

Hi Find out below attachment for Android Sample Application

Concepts :

Animations

AsyncTask

Shared preferences

GPS

Handlers

Mediaplayer

Notifications
Sensors

Speech to Text ( Voice recognization )

Store image in db

TextoSpeech

Source Code

Localization in android

2013-03-01T03:55:00.002-08:00

Android Localization Tutorial

Source

In this tutorial we show how to write multilingual Android apps.
To build multilingual Android apps you need to collect the texts into resource files and translate them.
Once you provide the translation, Android OS will choose the resources that match user’s locale. If your application is available in several languages, Android will select the language that the device uses.

In this tutorial, we’ll cover:

Android loads text and media resources from the project’s ‘res’directory. Additionally, Android can select and load resources from different directories, based on the current device configuration and locale.

1. Application Localization Process

For example, if the code loads a string called ‘R.string.title’, Android will choose the correct value for that string at runtime by loading the appropriate strings.xml file from a matching‘res/values’ directory.
In order to have a multilingual Android app you need to provide Android with the localized resource files.
If the locale is ‘en-US’, Android will look for a value of“R.string.title” by searching the files in the following order:

‘res/values-en-rUS/strings.xml’
‘res/values-en/strings.xml’
‘res/values/strings.xml’

When it manages to find the string in the resource file, it uses that value and stops searching. This means that the default language acts as a fall-back option and when translation exists, it’s used instead. It also means that you should either localize everything or nothing, as seeing half translated applications is usually worse than apps that are not translated at all.
Let’s go over a sample application to better understand the localization process. This is a very simple single-language application which displays a country’s image and a text view according to the language set in the device. The structure of the project will be as shown in the figure 1.

Figure 1: Structure of the sample project

The application doesn’t check the user’s locale and always executes the same, for any locale setting. A screen-shot of the sample application is shown in figure 2. Note that the background image refers to an image of the United States and the text is in English (default locale setting).

Figure 2: Snapshot of the sample single-language application.

Our first step towards localizing this app is to plan the way an it should display differently for different locales. We’ll add locale-specific information for Italy, France, Canada, and Russia. Table 1 details the different display options for different locales.

Table 1: Display options for different locales

Table 2: Location of “strings.xml” and background images for different locales

Table 2 shows the paths to the different resource files and which ones are used for which locale.

As shown in Table 1, we’ll have six background images (5 locales specific and one default). We’ll also have three sets of string translations (Italian, Russian and French).

Translations go under folders named values-<language>.

The language part of the folder name contains the language ISO code and an optional region code, preceded by lowercase r.

For example:

Without region code: fr
With region code: fr-rFR or fr-rCA

The application selects the resource files to load at run-time, based on the phone’s locale. If no locale-specific resources are available, it falls back on the defaults. For example, if we’re in Switzerland, and the phone’s language is set to French, Android will first look for a folder called fr-rCH. If it can’t find it, it looks forfr and if that’s not found too, it loads the resource files for the default language.

It does that for each resource type, so we can have French strings with the default graphics, or any other combination of translated resources.

2. Translating Strings

The application requires four strings.xml files, one for each in English, Italian, French, and Russian.

The procedure for creating strings.xml files is as follows:

Translate the strings.xml file to each language.
Create three new folders under res – values-it, values-fr and values-ru (The original values folder already exists).
Place the translated strings.xml files in the respective folders.

For fast and efficient and affordable translation, you’re welcome to try our professional Android localization service. Our system parses your resource files, extracts all the texts and then builds the translated resource files, ready to be used in Android.

3. Localizing Images

Our application also needs six more drawable folders, each containing a variant of the background image.

Place background image that has to appear for a respective language in corresponding folders under the project workspace of the sample application as specified in Table 3.

If your images contain texts, we recommend creating copies of the texts in your strings.xml file. This way, translators can translate just the texts, and you can rebuild the localized images.

Background image	Destination folder in project workspace
Italian	drawable-it-rIT/background.png
French	drawable-fr-rFR/background.png
French (Canada)	drawable-fr-rCA/background.png
English (Canada)	drawable-en-rCA/background.png
Russian	drawable-ru-rRU/background.png
US English	drawable-en-rUS/background.png
Default (Earth image)	drawable/background.png

Table 3: Background image and the respective destination folders.

After you save the strings.xml and background image files in their target folders, the project workspace looks like this:

Figure 3: Structure of the sample multi-lingual Android app

4. Running and Testing the Localized Application

Once the localized string and image resources are added to the project workspace, the application is ready for testing. To test it, we can set different locales via Home > Menu > Settings > Locale & text > Select locale.

Depending on configuration of the device, some devices may offer only a few locales or may not offer any alternate locales via the settings application. However, the Android emulator will offer a selection of all the locales that are available in Android OS. To set the emulator to a locale that is not available in the system image, you can use Custom Locale, available in the Application tab.

Figure 4 shows some of the expected results that we should see after setting the region and language in the phone.

Italian

French (France)

French (Canada)

English (US)

Default locale

Figure 4: Expected results after localization.

5. Localization Checklist

Now that we understand how to use the Android development framework for multilingual apps, let’s go over a short checklist which reminds us the steps we need to take.

Never hard-code strings or string constants; Instead use the R.string and strings.xml files.
Similarly, don’t hard-code images or layouts; use R.drawable and R.layout
Translate the strings.xml files and localize your images.
Place your localized resources in the appropriate directories under ‘res/’.

Sample Multilingual Android App

Throughout this tutorial we’ve used a sample application, written especially to explain how to create multilingual Android apps.

From developer doc android developer

For Sample Source Clik Source

Android Widgets

2013-02-28T21:21:00.003-08:00

Android Rating Bar :

The rating bar contains many configurable values. In this case, the rating bar contains 4 stars,
each increase 1.0 value, so, it contains the minimum of 1.0 (1 star) and maximum value of 4.0 (4 stars).
In addition, it made the 2nd star (2.0) selected by default.

Check Box :

Make CheckBox is checked by default Put android:checked="true" inside checkbox element to
make it checked bu default. In this case, “Android” option is checked by default.

Radio Button : Radio button selected by default. To make a radio button is selected by default, put android:checked="true" within the RadioButton element. In this case, radio option “Male” is selected by default.

What is Android layout?

Layout denotes the architecture of the application, where and how the controls should be organized
in the UI.It defines the layout structure and holds all the elements that appear to the user.

Android allows us to create layouts for the applications using simple XML file and those layouts must be placed in /res/layout folder. We can declare the layout in two ways and here we will discuss first way of doing it: Declare UI elements in XML Create UI elements at runtime using Java. Different kinds of layouts in Android are: Linear Layout Relative Layout Table Layout WebView Layout Grid View Tab Layout
List View

Table layout In a table layout, as the name suggests, all the controls are arranged into rows and columns.

Why Table layout? New Visitor? Like what you read?

Table layouts can be used for displaying tabular data or neatly aligning screen contents in a way similar to an HTML table on a web page. It organizes user interface controls, or widgets, on the screen in neatly defined rows and columns. Before we start with developing application,

download code from here to follow with the below listings.

Downloadable Source

Android facebook style slide

2013-01-04T03:38:00.000-08:00

The new Facebook application and its navigation is so cool. I was just trying to see how it can be emulated in my application. below download Link Contains 2 projects one is Library another one is Sample project Click This Link For Download

How to Create AVDS with Different Resolutions in Android

2012-11-14T03:06:00.000-08:00


                    In the AVD manager if you choose a Built-in skin then the Abstracted LCD density is ignored and it will set the density as described here:

Emulator Skins (from http://developer.android.com/tools/revisions/platforms.html)

The downloadable platform includes the following emulator skins:

QVGA (240x320, low density, small screen)
WQVGA400 (240x400, low density, normal screen)
WQVGA432 (240x432, low density, normal screen)
HVGA (320x480, medium density, normal screen)
WVGA800 (480x800, high density, normal screen)
WVGA854 (480x854 high density, normal screen)
WXGA720 (1280x720, extra-high density, normal screen)
WSVGA (1024x600, medium density, large screen)
WXGA800-7in (1280x800, high density, large screen) new
WXGA800 (1280x800, medium density, xlarge screen)
If you wish to set your own Abstracted LCD density you'll need to define your own resolution manually by clicking the Resolution radio button.

Here's some code you can use to test this:

DisplayMetrics metrics = new DisplayMetrics();
getWindowManager().getDefaultDisplay().getMetrics(metrics);
int density = metrics.densityDpi;
    if (density == DisplayMetrics.DENSITY_HIGH) {
        Toast.makeText(this, "DENSITY_HIGH... Density is " + String.valueOf(density),  Toast.LENGTH_LONG).show();
    }
    else if (density == DisplayMetrics.DENSITY_MEDIUM) {
        Toast.makeText(this, "DENSITY_MEDIUM... Density is " + String.valueOf(density),  Toast.LENGTH_LONG).show();
    }
    else if (density == DisplayMetrics.DENSITY_LOW) {
        Toast.makeText(this, "DENSITY_LOW... Density is " + String.valueOf(density),  Toast.LENGTH_LONG).show();
    }
    else {
        Toast.makeText(this, "Density is neither HIGH, MEDIUM OR LOW.  Density is " + String.valueOf(density),  Toast.LENGTH_LONG).show();
    }

How to Install FileZilla

2012-09-05T03:42:00.001-07:00

Linux, *BSD, Mac OS X and more
IPv6 support
Available in many languages
Supports resume and transfer of large files >4GB
Tabbed user interface
Powerful Site Manager and transfer queue
Bookmarks
Drag & drop support
Configurable transfer speed limits
Filename filters
Directory comparison
Network configuration wizard
Remote file editing
Keep-alive
HTTP/1.1, SOCKS5 and FTP-Proxy support
Logging to file
Synchronized directory browsing
Remote file search
What is new in version 3.5.1
New features:
Add menu item to hide toolbar
Bugfixes and minor changes:
Don't save server list in kiosk mode 2
Fix for predefined sites not appearing in all circumstances
OS X: Pasting formatted text into input boxes no longer changes their format
Fix typo in build script in detection of SQLite3
MSW: Small installer improvements
*nix: Fix character set conversion in desktop notification code
Merged upstream PuTTY changes for compatibility with PuTTY 0.61
Updated built-in TinyXML
Add support for another rate variant of MVS style directory listings

Install filezilla 3.5.1 using PPA
Open th terminal and run the following commands

Step 1- > sudo add-apt-repository ppa:n-muench/programs-ppa

Step 2- > sudo apt-get update

Step 3- > sudo apt-get install filezilla

Micro soft dot net power point presentations and programs

2012-08-19T23:12:00.002-07:00

Hi guys here we can find out some basics of c# and asp.net programs
and power point presentations .

ASP . Net presentations presentations

Programing in C# presentations

Dot Net Demo Programs presentations

dot net demo project presentations

Xml power point presentations presentations

WML power point presentaions

HorizontalScrollView And ScrollView

2012-08-14T04:17:00.001-07:00

java.lang.Object
↳	android.view.View
	↳	android.view.ViewGroup
		↳	android.widget.FrameLayout
			↳	android.widget.HorizontalScrollView

Class Overview

Layout container for a view hierarchy that can be scrolled by the user, allowing it to be larger than the physical display. A HorizontalScrollView is a FrameLayout, meaning you should place one child in it containing the entire contents to scroll; this child may itself be a layout manager with a complex hierarchy of objects. A child that is often used is a LinearLayout in a horizontal orientation, presenting a horizontal array of top-level items that the user can scroll through.

The TextView class also takes care of its own scrolling, so does not require a HorizontalScrollView, but using the two together is possible to achieve the effect of a text view within a larger container.

HorizontalScrollView only supports horizontal scrolling. For vertical scrolling, use either ScrollView orListView.

ScrollView and HorizontalScrollView are layout container for a view hierarchy that can be scrolled vertically or horizontally by the user, allowing it to be larger than the physical display. A ScrollView/HorizontalScrollView is a FrameLayout, meaning you should place one child in it containing the entire contents to scroll; this child may itself be a layout manager with a complex hierarchy of objects.

XML code :

------------

<?xml version="1.0" encoding="utf-8"?>

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"

android:orientation="vertical"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

<TextView

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="HorizontalScrollView And ScrollView "

<HorizontalScrollView

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<LinearLayout

android:orientation="vertical"

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<TextView

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="First HorizontalScrollView" />

<LinearLayout

android:orientation="horizontal"

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<Button

android:text="Horizontal A1"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal A2"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal A3"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal A4"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal A5"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

</LinearLayout>

</HorizontalScrollView>

<HorizontalScrollView

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<LinearLayout

android:orientation="vertical"

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<TextView

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Second HorizontalScrollView" />

<LinearLayout

android:orientation="horizontal"

android:layout_width="wrap_content"

android:layout_height="wrap_content">

<Button

android:text="Horizontal B1"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal B2"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal B3"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal B4"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal B5"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

<Button

android:text="Horizontal B6"

android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

</LinearLayout>

</HorizontalScrollView>

<ScrollView

android:layout_height="fill_parent"

android:layout_width="fill_parent">

<LinearLayout

android:orientation="vertical"

android:layout_width="fill_parent"

android:layout_height="fill_parent" >

<TextView

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView" />

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Button C"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView D"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView E"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView F"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView G"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView H"/>

<Button

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Vertical ScrollView I"/>

</LinearLayout>

</ScrollView>

</LinearLayout>

For Full Source Clik Here : ScrollView

Android companies List In Vishakapatnam

2012-08-13T02:06:00.003-07:00

Link Name
--------------------------------------------------------------
http://www.bluefrogindia.com blue frog

http://www.e-centricsolutions.com/ ecentric solutions

http://faqden.com/ faqden Labs

http://www.gaiansolutions.com/   gain softsoluations

http://www.jitworld.com     jit world

http://www.stellentsoft.com/   stellen and soft

http://www.xinthe.com Xinthe technologies

http://www.vizser.com vizser limited

Real time Android training in Vishakapatnam

http://techtrainin.blogspot.in/p/android-programing.html

Showing a progress Bar When uploading File using FTP in Android

2012-08-09T00:00:00.003-07:00

/**
* Asynchronous task to upload file to server
*/
class UploadImageTask extends AsyncTask<File, Integer, Boolean> {

/** Upload file to this url */
private static final String UPLOAD_URL = "http://thibault-laptop:8080/report";

/** Send the file with this form name */
private static final String FIELD_FILE = "file";
private static final String FIELD_LATITUDE = "latitude";
private static final String FIELD_LONGITUDE = "longitude";

/**
* Prepare activity before upload
*/
@Override
protected void onPreExecute() {
super.onPreExecute();
setProgressBarIndeterminateVisibility(true);
mConfirm.setEnabled(false);
mCancel.setEnabled(false);
showDialog(UPLOAD_PROGRESS_DIALOG);
}

/**
* Clean app state after upload is completed
*/
@Override
protected void onPostExecute(Boolean result) {
super.onPostExecute(result);
setProgressBarIndeterminateVisibility(false);
mConfirm.setEnabled(true);
mDialog.dismiss();

if (result) {
showDialog(UPLOAD_SUCCESS_DIALOG);
} else {
showDialog(UPLOAD_ERROR_DIALOG);
}
}

@Override
protected Boolean doInBackground(File... image) {
return doFileUpload(image[0], UPLOAD_URL);
}

@Override
protected void onProgressUpdate(Integer... values) {
super.onProgressUpdate(values);

if (values[0] == 0) {
mDialog.setTitle(getString(R.string.progress_dialog_title_uploading));
}

mDialog.setProgress(values[0]);
}

/**
* Upload given file to given url, using raw socket
* @see http://stackoverflow.com/questions/4966910/androidhow-to-upload-mp3-file-to-http-server
*
* @param file The file to upload
* @param uploadUrl The uri the file is to be uploaded
*
* @return boolean true is the upload succeeded
*/
private boolean doFileUpload(File file, String uploadUrl) {
HttpURLConnection conn = null;
DataOutputStream dos = null;
String lineEnd = "\r\n";
String twoHyphens = "--";
String boundary = "*****";
String separator = twoHyphens + boundary + lineEnd;
int bytesRead, bytesAvailable, bufferSize;
byte[] buffer;
int maxBufferSize = 1 * 1024 * 1024;
int sentBytes = 0;
long fileSize = file.length();

// The definitive url is of the kind:
// http://host/report/latitude,longitude
uploadUrl += "/" + mLocation.getLatitude() + "," + mLocation.getLongitude();

// Send request
try {
// Configure connection
URL url = new URL(uploadUrl);
conn = (HttpURLConnection) url.openConnection();
conn.setDoInput(true);
conn.setDoOutput(true);
conn.setUseCaches(false);
conn.setRequestMethod("PUT");
conn.setRequestProperty("Connection", "Keep-Alive");
conn.setRequestProperty("Content-Type", "multipart/form-data;boundary=" + boundary);
publishProgress(0);

dos = new DataOutputStream(conn.getOutputStream());

// Send location params
writeFormField(dos, separator, FIELD_LATITUDE, "" + mLocation.getLatitude());
writeFormField(dos, separator, FIELD_LONGITUDE, "" + mLocation.getLongitude());

// Send multipart headers
dos.writeBytes(twoHyphens + boundary + lineEnd);
dos.writeBytes("Content-Disposition: form-data; name=\"" + FIELD_FILE + "\";filename=\""
+ file.getName() + "\"" + lineEnd);
dos.writeBytes(lineEnd);

// Read file and create buffer
FileInputStream fileInputStream = new FileInputStream(file);
bytesAvailable = fileInputStream.available();
bufferSize = Math.min(bytesAvailable, maxBufferSize);
buffer = new byte[bufferSize];

// Send file data
bytesRead = fileInputStream.read(buffer, 0, bufferSize);
while (bytesRead > 0) {
// Write buffer to socket
dos.write(buffer, 0, bufferSize);

// Update progress dialog
sentBytes += bufferSize;
publishProgress((int)(sentBytes * 100 / fileSize));

bytesAvailable = fileInputStream.available();
bufferSize = Math.min(bytesAvailable, maxBufferSize);
bytesRead = fileInputStream.read(buffer, 0, bufferSize);
}

// send multipart form data necesssary after file data
dos.writeBytes(lineEnd);
dos.writeBytes(twoHyphens + boundary + twoHyphens + lineEnd);
dos.flush();
dos.close();
fileInputStream.close();
} catch (IOException ioe) {
Log.e(TAG, "Cannot upload file: " + ioe.getMessage(), ioe);
return false;
}

// Read response
try {
int responseCode = conn.getResponseCode();
return responseCode == 200;
} catch (IOException ioex) {
Log.e(TAG, "Upload file failed: " + ioex.getMessage(), ioex);
return false;
} catch (Exception e) {
Log.e(TAG, "Upload file failed: " + e.getMessage(), e);
return false;
}
}

private void writeFormField(DataOutputStream dos, String separator, String fieldName, String fieldValue) throws IOException
{
dos.writeBytes(separator);
dos.writeBytes("Content-Disposition: form-data; name=\"" + fieldName + "\"\r\n");
dos.writeBytes("\r\n");
dos.writeBytes(fieldValue);
dos.writeBytes("\r\n");
}
}

Secret Codes For Android Mobile Phones

2012-06-21T17:02:00.001-07:00

1. Complete Information About your Phone

*#*#4636#*#*
This code can be used to get some interesting information about your phone and battery.

Usage statistics

2. Factory data reset
*#*#7780#*#*
This code can be used for a factory data reset. It'll remove following things:
Google account settings stored in your phone
System and application data and settings
Downloaded applications
It'll NOT remove:
Current system software and bundled application
SD card files e.g. photos, music files, etc.
Note: Once you give this code, you get a prompt screen asking you to click on "Reset phone" button. So you get a chance to cancel your operation.

3. Format Android Phone

*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
Note: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone. So think twice before giving this code.

4. Phone Camera Update

*#*#34971539#*#*
This code is used to get information about phone camera. It shows following 4 menus:
Update camera firmware in image (Don't try this option)
Update camera firmware in SD card
Get camera firmware version
Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take your phone to service center to reinstall camera firmware.

5. End Call/Power

*#*#7594#*#*
This one is my favorite one. This code can be used to change the "End Call / Power" button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, AirPlane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.

6. File Copy for Creating Backup

*#*#273283*255*663282*#*#*

This code opens a File copy screen where you can backup your media files e.g. Images, Sound, Video and Voice memo.

7. Service Mode

*#*#197328640#*#*
This code can be used to enter into Service mode. You can run various tests and change settings in the service mode.

8. WLAN, GPS and Bluetooth Test Codes:

*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* - WLAN test (Use "Menu" button to start various tests)

*#*#232338#*#* - Shows WiFi MAC address

*#*#1472365#*#* - GPS test

*#*#1575#*#* - Another GPS test

*#*#232331#*#* - Bluetooth test

*#*#232337#*# - Shows Bluetooth device address

9. Codes to get Firmware version information:

*#*#4986*2650468#*#* - PDA, Phone, H/W, RFCallDate

*#*#1234#*#* - PDA and Phone

*#*#1111#*#* - FTA SW Version

*#*#2222#*#* - FTA HW Version

*#*#44336#*#* - PDA, Phone, CSC, Build Time, Changelist number

10. Codes to launch various Factory Tests:

*#*#0283#*#* - Packet Loopback

*#*#0*#*#* - LCD test

*#*#0673#*#* OR *#*#0289#*#* - Melody test

*#*#0842#*#* - Device test (Vibration test and BackLight test)

*#*#2663#*#* - Touch screen version

*#*#2664#*#* - Touch screen test

*#*#0588#*#* - Proximity sensor test

*#*#3264#*#* - RAM version

Basic Swings Programs

2012-06-08T00:28:00.001-07:00

Differences between Swings And AWT
Differences:
1) AWT stands for Abstract windows toolkit whereas le Swing is also called as JFC?s (Java Foundation classes).
2) AWT components use native methods Swing components use the methods that are written in Java. Therefore AWT is heavy weight component and swing is light weight component.
3) Light weight components have transparent pixels where as heavy weight is always opaque.
4) Light weight components are non-rectangular whereas Heavy weight components are rectangular
5) Swings components are made in pure java and they are platform independent whereas AWT components are platform dependent.
6) Swing provides look and feel feature whereas this feature is not supported by AWT.

DownLoad Swing Programs