\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Performance Assessment of WhatsApp and IMO on Android Operating System (Lollipop and Kitkat) during Voip Calls using 3G or WiFi},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2016-01-15 (revised: 15 January 2016)}
\def\TheID{\makeatother }
\def\TheDate{2016-01-15}
\title{Performance Assessment of WhatsApp and IMO on Android Operating System (Lollipop and Kitkat) during Voip Calls using 3G or WiFi}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{R.C. De  Oliveira}

             \author[2]{H.M. De  Oliveira}

             \author[3]{L.P.S.  Viana}

             \affil[1]{  Amazon State University}

\renewcommand\Authands{ and }

\date{\small \em Received: 15 December 2015 Accepted: 2 January 2016 Published: 15 January 2016}

\maketitle


\begin{abstract}
        


This paper assesses the performance of mobile messaging and VoIP connections. We compared the CPU requirements of WhatsApp and IMO under different scenarios. This analysis also enabled a comparison of the performance of these applications on two Android operating system (OS) versions: KitKat or Lollipop. Two models of smartphones were considered, viz. Galaxy Note 4 and Galaxy S4. The applications behavior was statistically investigated for both sending and receiving VoIP calls. Connections have been examined over 3G and WiFi. The handset model plays a decisive role in CPU requirements of the application. t-tests shown that IMO has a statistical better performance that WhatsApp whatever be the Android at a significance level 1%, on Galaxy Note 4. In contrast, WhatsApp requires less CPU than IMO on Galaxy S4 whatever be the OS and access (3G/WiFi). Galaxy Note 4 using WiFi has always better performance than S4 in terms of processing.

\end{abstract}


\keywords{}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{I. Introduction}]{I. Introduction}\par
nstant messaging and VoIP (voice over IP) for mobile phones are growing importance in the contemporary society. The instant messaging (IM) is a set of communication technologies used for text-based communication between two or more participants usually over the Internet \hyperref[b1]{[2]},  {\ref [8]}. In particular, IM in mobile phones is becoming a worldwide fever \hyperref[b9]{[12]}, \hyperref[b0]{[1]}, \hyperref[b7]{[10]}. In performance evaluation of electronic devices is commonplace to build a base for comparison (baseline, \hyperref[b3]{[4]}). Usually this database is constructed by applying tools that collect performance metrics (e.g. CPU, disk, memory and network statistics). Through such a baseline, the analyst can pinpoint where the drawbacks are, and carry out performance adjustments so as to improve the throughput of a given application. The choice of performance metrics, how performing data collection, and data analysis are common steps of performance evaluation. We conducted a performance assessment of the WhatsApp as compared with the performance of IMO through 3G and Wifi, on different operating systems Android  {\ref [15]}, \hyperref[b4]{[5]}. The performance of such applications remains rather unexplored both from the theoretical viewpoint as well as in academia. See \hyperref[b2]{[3]} for a comparison between WhatsApp and standard SMS. 
\section[{II. Materials and Methods}]{II. Materials and Methods}\par
The analysis delimited in this study is just VoIP on smartphones. The analysis carried out in this study would be limited to monitoring the processing when instant messaging or voice call applications. The universe of study of this investigation is characterized by the scope of operation of mobile devices. The field of study covered the transmission by wireless LAN (WiFi) or 3G networks \hyperref[b11]{[14]}. It was not taken into account the coding, nor programming logic or source code of applications. Android OS is a multitasking operating system for for mobile devices, including smartphones and tablets, which have different versions \hyperref[b6]{[9]}, \hyperref[b4]{[5]}. The main purpose is the analysis of cross-platform instant messaging for smartphones, viz. WhatsApp and IMO, with versions of Android, KitKat and Lollipop. For the present experiment we used an analysis tool, techniques measurements and statistical methods. The scope of the study was carefully designed to avoid interference from outside or assumptions that were not linked to the analysis. Moreover, for the proper background collecting of logs on mobile applications is essential to select software that is able to perform the performance data capture. Sampling tests were performed by selecting an appropriate tool to collect specific logs. Our choice fell upon the Little Eye and thereafter it was possible to analyze the resources and ways processing  {\ref [7]}. Test devices were Samsung Galaxy S4 (S4) and Samsung Galaxy Note 4 (N4), both with different hardware and which have been installed Android. To build the environment, it was also required to install and configure a wireless network as well as the availability of carrier chip with 3G transmission. ? Analyze: It brings information about the background of the data collected creating graphs and statistics for analysis;\par
? Optimize: Suggest improvements in resource consumption by optimizing the operating system. For tool installation the following requirements is necessary:\par
Java JRE or SDK -V 1.6 + (Java 6 or higher) and Android SDK; USB debugging is enabled on the phone; Set the device to connect to as "camera (PTP)" rather than "media device (MTP)"; Test device drivers are required when using Windows OS.\par
With everything set (hardware and software environments), Little Eye starts. Once started, it loads applications under test on the device. After listing all applications, simply select the application to be tested (WhatsApp or IMO), and then configure the measurements of interest, as illustrated in the following screen (Fig. \hyperref[fig_0]{1}). Case Study: The application under test is monitored with VoIP call duration of 1 minute, 5 minutes and 10 minutes. The data were collected during these periods. In a preliminary analysis, 30 calls with WhatsApp and IMO were refereed. The same test environment is applied to both Android KitKat (KK) and Lollipop (LL) systems, i.e., the same test conditions and analysis are adhered so there is no bias in results. Standard hypothesis tests were conducted to ascertain a performance difference between IMO and WhatsApp applications. Two-tailed t-test for the population mean of IMO under a cornucopia of scenarios. Let \textunderscore  be the mean of CPU requirements of the application during a 10 minutes VoIP call (sending or receiving). The statistical hypothesis at 1\% significance level (\textunderscore  = 0:01) were:\par
(1) Also, left-tailed t-test showed evidence that IMO performance was higher than WhatsApp. Bean plot is also used to visualize performance data http:// boxplot.Tyerslab.com/. 
\section[{III. Performance of Whatsapp and Imo}]{III. Performance of Whatsapp and Imo}\par
Data collection was conducted using the Little Eye software as application performance analysis tool  {\ref [7]}. In this software, it is possible to collect smartphone application logs and analyze the processing consumption. This tool has a number of resources available to perform the analysis of applications, ranging from battery consumption to processingoverhead. In these experiments, however, the scope has been narrowed to the study of behavior around the CPU. The test was carried out by collecting 30 calls lasting 10 minutes and the logs generated took the average for all sampling measures. These graphs show the applications are processed for use in receiving (also transmitting) a VoIP call through WhatsApp and the IMO using a WiFi connection as communication in both versions of Android [15]. Figure  {\ref 2}, illustrates two instances of selected CPU requirements measures for achieving 30 calls, lasting 10 minutes. Each point is the average calculated from 30 samples. All correlations between performances in different scenarios were calculated: Higher performance correlations were obtained for the handset Galaxy S4 than for the Galaxy Note 4. The highest correlation coefficient among all tested scenarios was obtained for the Galaxy S4 with operation with LL. Considering now the IMO application, in the 3G operation under Galaxy S4 smartphone, the general performance behavior is weakly sensitive to the selected version of the android system. Nevertheless, the performance of KK OS was approximately twofold more efficient than LL, as concerning 3G transmission. In contrast, the lowest correlation coefficient was found for KitKat in the two handset models, where the WhatsApp and IMO application performance for 3G calling were noncorrelated. Low correlations were also achieved for 3G connections on the smartphone Galaxy Note 4: the performance for KitKat and Lollipop were also uncorrelated.\par
Table  {\ref 1} : Average CPU requirements for different scenarios. Smartphone Galaxy Models: N4 and S4. The calls were all made lasting 10 minutes. In each case, they were considered N = 30 samples (each is an average obtained from 600 measurements). Values in parenthesis refer to the sample. standard deviation. Significance level of t-test: \textunderscore  = 0:01 a 3G transmission with the android version KK. For WhatsApp using the KitKat OS, the smartphone Galaxy S4 presented some correlation between 3G and wifi.\par
The KK android version yielded performance results not so sensitive to the selected network (3G or wifi operation) and their memory requirements were pretty close. Still handling with WhatsApp on the device S4 operating on wifi, there is a performance correlation between the two android OS version, but the KK performance is roughly twice more efficient than the It was observed that a few specific moment, the processing occupation reached to zero. Sometimes this is expressed by display off (device screen hibernated,) it reduced the kernel processing consumption. It was noticed that the tester there are three or more CPUs and the WhatsApp test has shown the using of a single CPU. But this led to the idea that some features of the devices were being processed by other CPUs. In some cases it was perceived that the application falls under Lollipop, but it is emphasized that troubles may have occurred during the collection of logs. An example is the Internet itself both 3G as WiFi, tool communication with the device or operating failures. In the beanplot (a variant of Tukey boxplot) shown in Fig. \hyperref[fig_1]{3}, one can see the behavior of CPU requirements for measurements comparing the transmission medium (3G \textunderscore  WiFi) for WhatsApp and IMO. For 3G, a marked performance difference is observed between Whatsapp and IMO in the Samsung Note 4, showing a superior performance WhatsApp is statistically indistinguishable (t=1.826, p-value=0.078). p-values were p < 10?5 in most cases. Also, left-tailed test have shown evidence to accept the hypothesis \textunderscore IMO < \textunderscore WhatsApp (or \textunderscore WhatsApp < \textunderscore IMO). t-tests on Galaxy Note 4 have shown that IMO app has a statistical better performance that WhatsApp OS and the access network (3G/Wifi). Finally, Galaxy Note 4 using WiFi outperforms Galaxy S4 in terms of processing. whatever the Android, at a significance level 1\%.In contrast, WhatsApp requires less CPU than IMO on Galaxy S4 at the same significance level, whatever the of IMO. In contrast, underWiFi, these differences are not so remarkable. Table  {\ref 1} (tx) and 2 (rx) present the transmission medium (3G \textunderscore  WiFi). Null hypothesis (Eqn.\par
(1)) is rejected at 1\% significance level in all cases, but fKK,N4,wifig where the performance of the IMO and statistics of average CPU requirements obtained in the pairwise measurements in order to compare the performance of WhatsApp and IMO. A marking with different letters (e.g. a and b) indicates that the average CPU requirements were different at a significance level of 1\% (so the hypothesis H0 can be rejected). A pairwise comparison with the same letter (a and a) indicates that the null hypothesis cannot be discarded at 1\%, i.e. there is no statistical evidence of performance difference between the two scenarios compared. In the first table, only the operating system version is changed (KitKat \textunderscore  Lollipop). In the second one, it is varied just the There is visible the increased processing generated by the application in the version of Lollipop compared the KitKat version. However, both on WiFi and 3G connections, there is insufficient data here to unveil the very reason, but we know that changes made to the KitKat to Lollipop are focused on managing resources, such as energy consumption \hyperref[b10]{[13]}. Based on the results we can say that the operating system indirectly affects in the response in terms of CPU processing, although it may not be decisive. When comparing the same operating system on different chipsets we realize that the application the way it was developed directly contributes to the device performance. This claim comes from the realization that IMO on Galaxy S4 requires more CPU than WhatsApp, but on the other hand, this does not occur in the Galaxy Note 4. It is also observed that WiFi under Galaxy Note 4 has better performance than the Galaxy S4 in terms of processing, for both operating systems. This is quite likely to happen due to the CPU management, since each chip has its own managing way. In the 3G scenario, more CPU is required in both IMO and WhatsApp. It is assumed that the chipset combination, application development, Android OS and the network technology (WiFi/3G) is crucial in CPU performance. The total processing using this application be given by the sum of CPU usage by the user (application) and CPU usage by the kernel generated by the application itself. Nevertheless, findings suggest the need for a more specific analysis from the perspective of resources exploited by each application. Ascertain the impact of energy consumption with the device update to the Android Lollipop version should also be examined, since it is one of the notes issued for this release. It is so recommended as future research a deep investigation on energy consumption \hyperref[b8]{[11]}, \hyperref[b5]{[6]} achieved with the Applications should have the chipset/OS as a key observance with a view on battery consumption.  
\section[{V. Acknowledgment}]{V. Acknowledgment}\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{figure4}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-5.png}
\caption{\label{figure5}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-6.png}
\caption{\label{figure6}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-7.png}
\caption{\label{figure7}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2} \par 
\begin{longtable}{P{0.7248730964467005\textwidth}P{0.008629441624365481\textwidth}P{0.025888324873096447\textwidth}P{0.012944162436548223\textwidth}P{0.03020304568527919\textwidth}P{0.047461928934010154\textwidth}}
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep 7.\\
device\tabcellsep to\tabcellsep update\tabcellsep the\tabcellsep version\tabcellsep Lollipop.\\
\multicolumn{5}{l}{(http://cs.gmu.edu/?astavrou/research/}\tabcellsep \\
\multicolumn{6}{l}{Android\textunderscore Power\textunderscore Measurements\textunderscore Analysis\textunderscore SERE\textunderscore 12.pdf).}\end{longtable} \par
 
\caption{\label{tab_1}Table 2 :}\end{figure}
 			\footnote{Year 2016 ( ) © 2016 Global Journals Inc. (US)} 			\footnote{© 2016 Global Journals Inc. (US)} 			\footnote{Performance Assessment of WhatsApp and IMO on Android Operating System (Lollipop and Kitkat) during} 			\footnote{( ) © 2016 Global Journals Inc. (US) 1} 		 		\backmatter   			 \par
The authors thank to Samsung Ocean, Manaus, for the valuable hardware support as well as to its general coordinator, Prof. Antenor Ferreira Filho for many interesting suggestions. 			  			 			 			  				\begin{bibitemlist}{1}
\bibitem[Inc (2016)]{b4}\label{b4} 	 		\textit{Android, the world's most popular mobile platform},  		 			Google Inc 		.  		 \url{http://developer.Android.com/about/index.html}  		February 2016. p. 29.  	 
\bibitem[Butler (2011)]{b0}\label{b0} 	 		‘Android: Changing the Mobile Land scape’.  		 			M Butler 		.  		 \xref{http://dx.doi.org/10.1109/MPRV.2011.1}{10.1109/MPRV.2011.1}.  	 	 		\textit{IEEE Pervasive Computing}  		Jan.-March 2011. 10  (1)  p. .  	 
\bibitem[O'hara and Kenton ()]{b9}\label{b9} 	 		‘Everyday dwelling with WhatsApp’.  		 			K O'hara 		,  		 			P Kenton 		.  		 doi: 10.1145/ 2531602. 25316 79.  	 	 		\textit{Proceedings of the 17th ACM conference on Computer supported cooperative work \& social computing},  				 (the 17th ACM conference on Computer supported cooperative work \& social computing)  		2014. ACM.  	 
\bibitem[Ghosh et al. ()]{b3}\label{b3} 	 		 			A Ghosh 		,  		 			J Zhang 		,  		 			J G Andrews 		,  		 			R Muhamed 		.  		\textit{Fundamentals of LTE. Pearson Education},  				2010.  	 
\bibitem[Kundu and Kolin ()]{b5}\label{b5} 	 		‘Improving Android Performance and energy efficiency’.  		 			T K Kundu 		,  		 			P Kolin 		.  		 \xref{http://dx.doi.org/10.1109/VLSID.2011.63}{10.1109/VLSID.2011.63}.  	 	 		\textit{IEEE 24th International Conference on VLSI Design},  				2011. p. .  	 	 (VLSI Design) 
\bibitem[Mehrotra et al. ()]{b6}\label{b6} 	 		‘Instant Messaging Service on Android Smart phones and Personal Computers’.  		 			P Mehrotra 		,  		 			T Pradhan 		,  		 			P Jain 		.  	 	 		\textit{International Journal of Information and Computation Technology}  		2014. p. .  	 
\bibitem[Saksonov ()]{b10}\label{b10} 	 		\textit{Method to Derive Energy Profiles for Android Platform},  		 			A Saksonov 		.  		2014.  		 			University of Oldenburg 		 	 
\bibitem[Murmuria et al. ()]{b8}\label{b8} 	 		‘Mobile application and device power usage measurements’.  		 			R Murmuria 		,  		 			J Medsger 		,  		 			A Stavrou 		,  		 			J M Voas 		.  		 \xref{http://dx.doi.org/10.1109/SERE.2012.19}{10.1109/SERE.2012.19}.  	 	 		\textit{IEEE Sixth International Conference on Software Security and Reliability (SERE)},  				2012. p. .  	 
\bibitem[Montag et al. ()]{b7}\label{b7} 	 		 			C Montag 		,  		 			K Blaszkiewicz 		,  		 			R Sariyska 		,  		 			B Lachmann 		,  		 			I Andone 		,  		 			B Trendafilov 		,  		 			.. 		,  		 			A Markowetz 		.  		 \xref{http://dx.doi.org/10.1186/s13104-015-1280-z}{10.1186/s13104-015-1280-z}.  		\textit{Smartphone usage in the 21st Century: who is active on WhatsApp? BMC research notes},  				2015. 8 p. 331.  	 
\bibitem[Cherry (2002)]{b1}\label{b1} 	 		‘Talk is cheap’.  		 			S M Cherry 		.  		 \xref{http://dx.doi.org/10.1109/6.999798}{10.1109/6.999798}.  	 	 		\textit{IEEE Spectrum}  		May 2002. 39  (5)  p. 55.  	 	 (text is cheaper [mobile messaging) 
\bibitem[Tanenbaum and David (2011)]{b11}\label{b11} 	 		‘Understanding the Why and What of Android Performance’.  		 			A S Tanenbaum 		,  		 			J W David 		.  		 \url{http://www.littleeye.co/blog/2013/05/28/understanding-the-why-and-what-of-android-performance/index.html}  	 	 		\textit{Computer Network}  		2011. Accessed 29 February 2016. 15 p. .  	 
\bibitem[Church and De Oliveira ()]{b2}\label{b2} 	 		‘What's up with whatsapp?: comparing mobile instant messaging behaviors with traditional SMS’.  		 			K Church 		,  		 			R De Oliveira 		.  		 \xref{http://dx.doi.org/10.1145/2493190.2493225}{10.1145/2493190.2493225}.  	 	 		\textit{Proceedings of the 15th international conference on Human-computer interaction with mobile devices and services},  				 (the 15th international conference on Human-computer interaction with mobile devices and services)  		2013. ACM.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
