Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
project report on bluetooth controlled car
Typology: Summaries
1 / 53
This page cannot be seen from the preview
Don't miss anything!
A Project Report On Android Guided Arduino Car Submitted to Amity University Uttar Pradesh In partial fulfillment of the requirements for the award of the degree of Bachelor of Technology In Information Technology By Rohit Shwetank Rajput Dhananjay Yadav Under the guidance of Mr. Sunil Chowdhary DEPARTMENT OF INFORMATION TECHNOLOGY AMITY SCHOOL OF ENGINEERING AND TECHNOLOGY AMITY UNIVERSITY UTTAR PRADESH NOIDA (U.P.) May 2015
We, Rohit, Shwetank Rajput and Dhananjay Yadav, students of B.Tech (IT) hereby declare that the project titled “Android Guided Arduino Car” which is submitted by us to Department of Information Technology, Amity School of Engineering and Technology, Amity University Uttar Pradesh, Noida, in partial fulfillment of requirement for the award of the degree of Bachelor of Technology in Information Technology, has not been previously formed the basis for the award of any degree, diploma or other similar title or recognition. Noida Date Name and Signature Rohit (A2305311005) Shwetank Rajput (A2305311055) Dhananjay Yadav (A2305311007)
Keep away from people who try to belittle your ambitions. Small people always do that, but the really great make you feel that you too, can become great. We take this opportunity to express my sincere thanks and deep gratitude to all those people who extended their wholehearted co-operation and have helped me in completing this project successfully. First of all, we would like to thank Mrs. Nitasha Hasteer (HOD) for creating opportunities for us to enhance our skill through the project. Her inspiring suggestions and timely guidance enabled me to perceive the various aspects of the project in a new light. Special thanks to Mr. Sunil Chowdhary (Faculty Guide) & (Programme Leader) for all the help and guidance extended to me by him in every stage during my project. We am highly indebted and graceful to Mrs. Sapna Shukla for their strict supervision, constant encouragement, inspiration and guidance. Working under him was an enrich experience. We would also like to thank our parents & project mates for guiding and encouraging me throughout the duration of the project.
The project aims is to design an android interface, arduino bot and write program in to the arduino microprocessor. Arduino car contains arduino microcontroller with basic mobility features. Arduino programs contains instructions mediating between android controller and Arduino car. Android mobile controller uses different mobile sensors to supervise motion. An appropriate program in the arduino microprocessor to interact with the android controller has to be created. The program has been successfully complied through arduino IDE to the arduino microprocessor & loaded in to it after proper checking of logic to decrease any loss/damage of hardware. We have to create an android application that will provide user an interface to interact with the arduino powered car. The interface is easy to use and provide feedback from the arduino microprocessor through the bluetooth after giving instruction to arduino for various actions through interface via bluetooth module. The android application is to create with the help of android studio that provide us with more capability & stability. After doing all of this we have test this project thoroughly and find the maximum no. of error & wrong logic in the microprocessor program. After doing this only we can say that we have been able to create as per our goal described.
1. Introduction 1.1. Purpose of Plan As most of the work in this area has been done regarding the Arduino & its application, what left out most of the time is the Android controller. In this project we are trying to exploit the android open accessory Bundle so that we can give a) More realistic experience to the user. b) Better Connectivity to the Arduino Chip. c) Increasing the efficiency in controlling of Bot. 1.2. Project objectives In this project we will be constructing the android guided Arduino Car by extracting the powers of both the open source technologies- Android and Arduino Programming. 1.3. Project goals To develop an android application that will provide user an interface to interact with the Arduino powered car. To develop an appropriate program in the Arduino microchip to interact with the android controller. To compile all the developed modules that we constructed above. To produce Arduino car that is controlled by android phone remote which can be used in various fields, like defence, scientific expeditions and so on. 1.4. Scope Definition The project is limited to designing an android interface, Arduino bot and write program in to the arduino microprocessor. Arduino car contains Arduino microcontroller with basic mobility features. Arduino programs contains instructions mediating between android controller and Arduino car. Android mobile controller uses different mobile sensors to supervise motion.
have completely different importance levels that are strictly ordered. The ensuing importance hierarchy for method categories feels like this (descending from highest importance, Foreground: A method that's running an Activity, a Service providing the Activity, a beginning or stopping Service or a presently receiving BroadcastReceiver. Visible: If a method holds a paused however still visible Activity or a Service absolute to a noticeable Activity and no foreground elements, it's classified a visible process. Service: A method that executes an already started Service. Background: associate degree Activity that's now not visible is hold by a background method. Empty: These processes contain no applications program elements and exists just for caching functions. If the system is running low on memory, the importance of a method becomes an important half within the system’s call that method gets killed to free memory. So empty processes are killed possibly followed by background processes then on. Typically solely empty and background processes are killed that the user expertise stays unaffected. The system is intended to go away everything untouched as long as doable that's related to a noticeable part like associate degree Activity. Processes will contain multiple threads, love it is common on Linux primarily based systems. Most androidian operating system applications include multiple threads to separate the UI from input handling and I/O operations or long running calculations, thence the underlying processes are multi-threaded. The threads used on application level area unit commonplace Java threads running within the Dalvik VM Applications & tasks Android applications are surpass processes and their enclosed threads. The 2 terms task and application are joined along tightly, only if a task may be seen as associate degree application by the user. In truth tasks are a series of activities of presumably multiple applications. Tasks primarily area unit a logical history of user actions, e.g. the user opens a mail application {in that during which within which} he opens a particular mail with a link enclosed which is opened during a browser. During this situation the task would come with 2 applications (mail and browser) whereupon there also are 2 Activity
elements of the mail application and one from the browser enclosed within the task. A plus of the task conception is that the chance to permit the user to travel back step by step sort of a pop operation on a stack. Application internals The structure of associate degree golem application relies on four completely different elements that are: Activity, Service, BroadcastReceiver and ContentProvider. Associate degree application doesn’t essentially consists of all four of those elements, however to gift a graphical computer program there needs to be a minimum of associate degree Activity. Applications will begin alternative applications or specific elements of alternative applications by causing associate degree Intent. These intents contain among alternative things the name of desired dead action. The IntentManager resolves incoming intents and starts the correct application or part. The reception of associate degree Intent may be filtered by associate degree application. Services and broadcast receivers enable applications to perform jobs within the background and supply further practicality to alternative elements. Broadcast receivers may be triggered by events and solely run a brief amount of your time whereas a service could run a protracted time. The compiled code of the appliance elements and extra resources like libraries, pictures and alternative necessary information is packed into one .apk file that forms the feasible golem application. AndroidManifest.xml All androidian operating system Dalvik applications got to have a XML document within the application’s root directory referred to as AndroidManifest.xml. This document is employed by numerous facilities within the system to get body and structure data concerning the appliance. Within the manifest file predefined part varieties area unit allowed to specify among alternative things the appliance name, the elements of the appliance, permissions, required libraries and filters for intents and broadcasts. Throughout development the manifest file holds the management data for instrumentation support. a number of the weather within the manifest file area unit mentioned in additional detail in alternative chapters, wherever it matches the context. Activities An Activity could be a single screen of associate degree application sort of a browser window or a settings page. It contains the visual components that gift information (like
Intents may be filtered by associate degree application to specify that intents may be processed by the application’s elements. The list of filters is about within the application’s manifest file, therefore androidian operating system will confirm the allowed intents before beginning associate degree application. Content provider The data storage and retrieval in androidian operating system applications is finished via content providers. These suppliers can even be wont to share knowledge between multiple applications, providing the concerned applications own the right permissions to access the information. Androidian operating system already has default suppliers for e.g. images, videos, contacts and settings which may be found within the golem.provider package. AN application queries a ContentResolver that returns the suitable ContentProvider. All suppliers square measure accessed like databases with AN URI to work out the supplier, a field name and also the knowledge style of this field. Applications solely access content suppliers via a ContentResolver, ne'er directly. If AN application desires to store knowledge that doesn't have to be compelled to be shared, it will use a neighborhood SQLiteDataBase. Background activities Applications may have to perform some supporting operations within the background or while not a graphical interface in the least. Androidian operating system provides the 2 categories BroadcastReceiver and repair for these functions. If solely a brief operation needs to be performed, the BroadcastReceiver is most well-liked and for long running jobs a Service is most well-liked. Each categories don't essentially imply that the background part runs as a thread or perhaps in its own method, thence androidian operating system doesn't enforce this sort of behaviour. so as to not freeze a running application, the service or broadcast receiver sometimes is running in its own thread, otherwise androidian operating system tends to kill such AN application because it appears not responsive. The BroadcastReceiver is activated through the onReceive() technique and gets nullified on come back from this technique. This makes it necessary to solely use synchronous ways in a very receiver. A broadcast commonly is unordered and sent to any or all matching receivers at a similar time, however it may be ordered too. During this case androidian operating system sends the printed solely to the one receiver at a time. This receiver runs as was common {and will|and may|and might} forward a result to future receiver or it can even abort the entire broadcast. A Service
permits AN application to perform long running tasks in background and supply a number of the application’s practicality to alternative applications within the system. A service may be utilized in 2 ways that, it's either started with one command or started and controlled by an incoming association that creates use of Remote Procedure Calls. each receiver and repair have to be compelled to be declared within the application manifest file to permit androidian operating system to work out the service’s or receiver’s category although the applying isn't running. Application lifetime & states The state androidian operating system application is in, is decided by the state of its parts, most significantly its activities. Because the application parts alter their states, the application’s underlying method sort is adjusted. On application begin the individual parts start And just in case of an activity the subsequent hooks square measure referred to as sequential: onCreate(), onStart(), onResume(). The primary hook is just referred to as once in AN activities time period, however the opposite 2 ways will get referred to as additional typically. If AN activity loses the main focus, the onPause() technique is termed and if the activity isn't any longer visible, onStop() is termed. Before deleting AN activity, it’s onDestroy() technique is run that ends the activity time period. Every technique gets referred to as on a special event to permit the activity to preserve its state or begin and restart properly. The subsequent list describes the aim of those hooks and the way the inflicting events amendment the applying state. onCreate() This technique is termed for initialisation and static originated functions. it should get passed AN older state for resuming. Future technique is often onStart(). onRestart() when AN activity is stopped and near to be started once more, this hook is termed and when it onStart(). onStart() the applying method sort changes to visible and also the activity is near to be visible to the user, however it’s not within the foreground. onResume() The activity has the main focus and may get user input. The applying method sort is about to foreground. onPause() If the applying loses the main focus or the device goes to sleep, this hook is termed and also the method sort is about to visible. When running this hook, the system is allowed to kill the applying at any time. All CPU intense operations ought to be
Application security The security model of golem heavily depends on the multi-user capabilities of the underlying Linux. Every application runs with its own distinctive user id and in its own method. All Dalvik applications run in a very sandbox that by default prohibits e.g. communication with alternative processes, access to others knowledge, access to hardware options like GPS or camera and network access. Opposing to platforms with native binary executables, androidian operating system makes it straightforward to enforce a particular application behavior, as its application VM Dalvik directly controls code execution and resource access. Platforms like iOS, webOS, Symbian or MeeGo don't have this chance, therefore their sandboxing systems square measure supported means that on kernel-, filesystem- or process-level and a few of those means that square measure utilized by androidian operating system too. The basic sandbox denies all requests from AN application unless the permissions square measure expressly granted. The permissions square measure originated within the application manifest file with the tag. That enables the system to raise the user or a package manager direct at install time for the application’s needed permissions. Once put in, AN application will assume that everyone needed permissions square measure granted. During the installation method, AN application is appointed with a novel and permanent user id. This user id is employed to enforce permissions on method and classification system level. AN application will expressly share files by setting the file mode to be world legible or writeable, otherwise all files square measure non-public. If 2 applications ought to share a similar processes or use a similar user id, each of the applications have to be compelled to be signed with a similar certificate and invite a similar sharedUserId in their manifest files. The individual parts of AN application can even be restricted, to confirm that solely bound sources square measure allowed to begin AN activity, a service or send a broadcast to the application’s receiver. A service will enforce fine grained permissions with the Context.checkCallingPermission() technique. Content suppliers will prohibit overall scan ANd write access furthermore as grant permissions on an URI basis.
Native applications Android applications that require additional performance than the Dalvik VM offers, may be divided. One half stays within the Dalvik VM to produce the applying UI and a few logic and also the alternative half runs as native code. This manner applications will profit of the device capabilities, even though robot or Dalvik don't provide a particular feature. The native code components of Associate in an application are shared libraries that are referred to as through the Java Native Interface (JNI). The shared library has got to be enclosed within the applications .apk file and expressly loaded. The code from the native library is loaded into the address house of the application’s VM. This results in an attainable security hole, as of revision four of the Native Development Kit (NDK), the code will build use of the ARMv5TE and ARMv7-A directions sets. Additionally the Vector Floating purpose (VFP) and atomic number 10 (Single Instruction Multiple knowledge instructions) extensions may be utilized in ARMv7-A code. Code utilized by native applications ought to solely build use of a restricted library set that amongst others includes the libc, libm, libz and a few 2nd and 3D graphics libraries. The performance speeding of native code over Dalvik taken code was examined. The results show that there's a large distinction between native and taken code, however the benchmarks were run on Associate in Nursing early androidian operating system version that e.g. didn't provide a simply in time compiler. Dalvik VM Android applications and also the underlying frameworks are nearly entirely written in Java. Rather than employing a normal Java virtual machine, robot uses its own VM. This virtual machine isn't compatible to the quality Java virtual machine Java me because it is specialized and optimized for tiny systems. These little systems sometimes solely give very little RAM, a slow central processing unit and aside from most PCs no swap file to compensate the little quantity of memory. At now androidian operating system tells itself aside from alternative mobile operative systems like Symbian, Apple’s iOS or Palm’s webOS that use native compiled application code. The most programming languages used there are C, C++ and objective C, whereat e.g. internetOS permits alternative largely web primarily based languages like JavaScript and hypertext markup language further. The mandatory computer memory unit code interpreter – the virtual machine – is termed Dalvik .Instead of mistreatment normal computer memory unit code, Dalvik has its own computer memory unit code format that is adjusted to the
this string would solely exist once within the .dex file and also the multiple occurrences ar simply tips to this one string. Constant mechanism is employed for technique names, constants and objects which ends up in smaller files with a lot of internal “pointing”. Byte code format The Dalvik computer memory unit code is intended to cut back the amount of necessary memory reads and writes and inflated code density compared to Java computer memory unit code. For this purpose Dalvik uses its own instruction set with a set instruction length of sixteen bit. Moreover Dalvik could be a register primarily based virtual machine that among alternative things reduces the required code units and directions. The given register dimension is {32|thirty 2} bit that permits every register to carry two directions, sixty four bit values are hold in adjacent registers. Directions shorter than sixteen bit zero-fill the unused bits and pad to sixteen bit. Dalvik is aware of a pair of56 completely different op codes whereof twenty three are unused in robot 2.2, resulting in an actual total op code variety of 233. Optimizations of the computer memory unit code is generally done by the dexopt tool at installation time. Install time work For the beginning of an application, the associated .dex file has a minimum of to be verified for structural integrity. This verification will take a while and is required just one occasion, as application files don’t amendment unless the applying is updated or uninstalled. As a result of that, the verification method may be done either at the primary startup or throughout the installation or update method. In androidian operating system this verification method is completed at installation time, in order that the least bit application startups later solely e.g. a check of the .dex file is required to verify it. Verification The verification and improvement procedure is performed by the dexopt program. To verify a .dex file, dexopt hundreds all categories of the file into a concisely initialized VM and runs through all directions all told strategies of every category. This manner amerciable directions or instruction mixtures may be found before the applying truly runs for the primary time. Categories during which the verification method succeeded
get marked by a flag to avoid rechecking this category once more. So as to visualize the .dex files integrity, a CRC-32 check is keep among the file. Optimization After the successful verification of a .dex file, it gets optimized by dexopt. The optimizations aim at performance increase through reduced code size or reduced code complexness. The improvement mechanisms heavily rely upon the target VM version and also the host platform that makes it laborious to run dexopt elsewhere than on the host. The ensuing code is unoptimized Dalvik computer memory unit code mixed with optimized code mistreatment op codes not outlined within the Dalvik computer memory unit code specification. If necessary for the processor design endianness, the code is computer memory unit swapped and aligned consequently. For code reduction dexopt prunes all empty strategies and replaces them with a no- operation op code. Inlining some fairly often referred to as strategies like String.length() reduces {the technique|the tactic|the strategy} decision overhead and virtual method decision indices get replaced by vtable indices. Moreover field indices get replaced by computer memory unit offsets and short knowledge varieties like char, computer memory unit and boolean are incorporate into thirty two bit kind to save lots of valuable central processing unit cache house. If it's attainable to pre-compute .dex file knowledge, dexopt appends the ensuing knowledge that reduces the central processing unit time required by the executing VM later. Each verification and improvement ar restricted to method only 1 .dex file at a time that results in issues at handling dependencies. If a .dex file is optimized, it contains a listing of dependencies which may be found within the bootstrap category path. So as to ensure consistency just in case of changed .dex files, solely dependencies to .dex files within the bootstrap category path ar allowed. this manner the verification of strategies looking on external .dex files aside from those in bootstrap can fail and also the connected category won't be optimized. Optimizations of memory allocation and usage In Dalvik there are a unit four completely different forms of memory to differentiate which will be sorted to clean/dirty and shared/private. Typical knowledge residing in either shared or non-public clean memory area unit libraries or application specific files like .dex files. Clean memory is protected by files or alternative sources and might be
