International Journal on Recent and Innovation Trends in Computing and Communication ISSN: 2321-8169

Volume: 4 Issue: 6 438 - 440

_______________________________________________________________________________________________
Smart mobile service that helps users to access the applications faster
Mr. Amit Rohra, Mr. Nikesh Posam Prof. Nishi Tiku
Post Graduate, MCA, Post Graduate, MCA, Senior Lecturer, H.O.D,
Vivekananda Education Societys Vivekananda Education Societys Vivekananda Education Societys
Institute of Technology, Institute of Technology, Institute of Technology,
Collectors Colony, Chembur. Collectors Colony, Chembur. Collectors Colony, Chembur.
Mumbai - 400 074 Mumbai - 400 074 Mumbai - 400 074
[email protected] [email protected] [email protected]

Abstract:-Our target, todays generation, we are targeting the root of todays generation i.e. Mobile phones (Smart phone). Our intent is to
engineer a service that will be running on operating system to access the application.

Keywords:-App, Activity, Drawer, Layout, Coordinates, Service

__________________________________________________*****_________________________________________________

1. Introduction 2.1.2 Android Runtime

In todays generation smart phones have become one essential It includes many libraries mostly written in the Java
part of human being. We use the mobile phone throughout the programming language, which provide a lot of the
day. There are numerous application softwares have been functionality of the Java core libraries. The Android Runtime
developed for mobiles operating system to get most out of the layer also offers the Dalvik Virtual Machine (DVM) which is
mobile phone. Our concept is to provide the user a quicker being described in 2.2.
access to the application installed on the system. Our main
focus is on Android operating system as it is the only operating 2.1.3 Libraries Provides
system that has larger number of users as compared to others C/C++ libraries which are used by many other components
but we can process the same service for other operating system within Android. Those libraries are e.g. the System C library,
like Windows, iPhone & Blackberry OS. SQLite, 3D libraries and so on.

2. Android 2.1.4 Application Framework

Android is a mobile operating system developed by Google. Android offers an extensive framework enabling application
The first version was brought to market in 2008. Since then to easily communicate and share data with each other.
Android is experiencing a great increase in market share. It is Furthermore the framework simplifies accessing systems
largely open-source and is based on Linux 2.6. Application resources such as hardware, location data and background
programming is done in Java but is being compiled to so called services.
DEX bytecode and is being run by the Dalvik Virtual Machine
(DVM). This section describes fundamentals of Android 2.1.5 Applications
including system architecture and runtime environment. On this layer Android applications accessible by the user are
located. Android comes with some standard applications
System Architecture such as Contacts, Messaging etc.
Android uses a 4-layered system architecture depicted in
figure. The layers are described in the following. Dalvik Virtual Machine
Android applications are developed using the Java
2.1.1 Linux Kernel programming language. Nevertheless you cannot make use
Provides low level operating system functionality such as of the full Java framework since Android ships with its own
memory management, security, process management etc. It framework. Java language features such as Reflection are not
also facilitates all the hardware drivers. supported by this framework due to performance issues. The
Dalvik Virtual Machine (DVM) is a virtual machine which is
optimized for (low-resource) mobile devices. Unlike the
virtual processor model of the Java Virtual Machine (JVM)
the DVMs processor model makes use of machine registers
thus taking advatage of modern mobile CPUs. In addition
bytecode for the DVM (called DEX bytecode1 ) is much
smaller than Java bytecode and can be executed much faster.
How a Java source file becomes DEX bytecode is described
in the following and illustrated in figure 2. Given a Java
source file (*.java) the Java compiler javac creates a Java
bytecode file (*.class). Now the dx tool transforms it to a
*.dex file which is capable of being executed by the DVM.

438
IJRITCC | June 2016, Available @ http://www.ijritcc.org
________________________________________________________________________________________________________
International Journal on Recent and Innovation Trends in Computing and Communication ISSN: 2321-8169
Volume: 4 Issue: 6 438 - 440
_______________________________________________________________________________________________
component has an Intent Filter to receive the Intent whereat
the Intent must match the conditions of the Intent Filter.

Intent Filters
Intent Filters are defined in a manifest _le called
AndroidManifest.xml. An example is shown following.

<receiver android:name="org.example.MyReceiver">
Android Applications <intent - filter >
Android applications consist of DEX bytecode, resources and <action android:name="org.example.TEST" />
data and are deployed as *.apk files. They are subject to a </ intent - filter >
lifecycle and are executed in a so called Sandbox". That is </ receiver >
every application runs in its own DVM in an independent
Linux process. When an application is being installed to an The XML tag <receiver> stands for a Broadcast Receiver.
Android device it is being assigned a new user and group ID. This Broadcast Receiver is annotated with an Intent Filter
Concerning security there is no possibility to illegally access whose action name is org.example.TEST meaning the
another process or its data since the user and group IDs are Broadcast Receiver is able to process actions with that name.
different. So we have an explicitly defined interface through which the
component can be used. That applies to the first point of the
3. Android's Component System definition of a component.
Before going into the details of Android's component system I
first want to introduce what a software component really is. In Intents
1996 the European Conference on Object-Oriented Intents Amongst other information Intents contain
Programming (ECOOP) defined it as follows: information about the desired target component. Intent can
A software component is a unit of composition with either be explicit or implicit. Explicit means that the target
contractually specified interfaces and explicit context component is known by its Java name. Implicit means that
dependencies only. A software component can be deployed the target component is not known but the desired action is.
independently and is subject to composition by third parties." In case of an implicit Intent the Android system is
In short the following defines a component: responsible for finding a component suitable for executing
1. contractually specified interface the action. If more than one component is found the Android
2. explicit context dependencies system asks the user interactively which one to choose. If
3. independent deployment none is found Android will display an error message.
Components must conform to a component model which
specifies form and properties of a component as well as how /* explicit intent */
components interact with each other and how they can be Intent ei = new Intent ( org. example . MyReceiver . class );
combined.
/* implicit intent */
Components in Android Intent ii = new Intent (" org. example . TEST ");
Android allocates four different types of components:
4. Concept
Activities are suitable for interacting with the user and Traditionally user to open any application user needs to open
presenting the user interface. the application drawer, then swipe to the screen where the
application is present and then click on the application to
Services can be used to run background tasks. They do not launch it. These steps wont trouble you if you have few
have a user interface. screens in the drawer (i.e. less applications installed). But
now a days single user have many number of applications
Content Providers are suited for providing data to other that leads to many screens in application drawer, so to launch
applications. Thus it is possible to break out" of the Sandbox the application user has to swipe n screens to locate the
and provide data through a defined interface. application and it is also a brain teaser for users to remember
the screen & location of each & every application.
Broadcast Receivers are used to receive broadcasts either
from the Android system or from other applications. While implementing the proposed daemon, user need not to
open the application drawer & swipe the screens to locate the
Communication between Components application, rather user just have to tap the location on the
As a major aspect of a component model is the interaction Home screen of mobile phone, now this tap location will
between components this subsection is to clarify how it is query the application drawer & fetch links to the applications
implemented in Android. The communication between installed at tap location in every screen & pops up a window
components in Android is done by using Intents and Intent which will display the shortcuts to the applications present at
Filters. The calling component uses Intent to announce the the location.
wish for communication with another component. The called
439
IJRITCC | June 2016, Available @ http://www.ijritcc.org
________________________________________________________________________________________________________
International Journal on Recent and Innovation Trends in Computing and Communication ISSN: 2321-8169
Volume: 4 Issue: 6 438 - 440
_______________________________________________________________________________________________
5. Proposed UI [5] Michael Burton Android App Development for
Following images shows the proposed UI for the mobile Dummies.
phones: [6] Marko Gargenta & Masumi Nakamaru Learning
Android.

As shown in the picture we can get the location of the screen

when w tap on the screen, subsequently we can pass this
coordinates location to the application drawer and fetch the
links to applications present at the supplied position from all
the screens. These links will be used to create the invisible
shortcut on the home screen. So when user clicks on the screen
he gets the direct access to the application from home page
without going and swiping the application drawer.

6. Conclusions
Opening the drawer, browsing and locating the application
requires more user efforts and power consumption in
traditional operating system. By implementing this service in
the mobile operating system, user gets the faster access to the
application and he dont need to remember the location of the
each and every application. This service can be integrated with
operating system services so it will not take more power in
terms of battery consumption which will increase the battery
performance to some extent.

7. Acknowledgment
This research was supported by Vivekananda Education
Societys Institute of Technology. We are thankful to our
colleagues who provided expertise that greatly assisted the
research, although they may not agree with all of the
interpretations provided in this paper. We are also grateful to
Prof. Nishi Tiku for assisting with Mobile Application
Development and moderated this paper. We have to express
out appreciation for sharing their pearls of wisdom with us
during the course of this research.

8. References
[1] Rick Boyer, Kyle Mew Android Application Development
Cookbook .
[2] https://homepages.thm.de/~hg51/Veranstaltungen/MasterS
eminar1011
[3] https://developer.android.com/reference/android/app/Servi
ce.html
[4] Jakob Iversen, Michael Eierman Learning Mobile App
Development (A hands-on guide to develop i-os and
android application).

440
IJRITCC | June 2016, Available @ http://www.ijritcc.org
________________________________________________________________________________________________________