Understanding and Improving Security of the Android Operating System

Total Page:16

File Type:pdf, Size:1020Kb

Understanding and Improving Security of the Android Operating System Syracuse University SURFACE Dissertations - ALL SURFACE December 2016 Understanding and Improving Security of the Android Operating System Edward Paul Ratazzi Syracuse University Follow this and additional works at: https://surface.syr.edu/etd Part of the Engineering Commons Recommended Citation Ratazzi, Edward Paul, "Understanding and Improving Security of the Android Operating System" (2016). Dissertations - ALL. 592. https://surface.syr.edu/etd/592 This Dissertation is brought to you for free and open access by the SURFACE at SURFACE. It has been accepted for inclusion in Dissertations - ALL by an authorized administrator of SURFACE. For more information, please contact [email protected]. ABSTRACT Successful realization of practical computer security improvements requires an understanding and insight into the system’s security architecture, combined with a consideration of end-users’ needs as well as the system’s design tenets. In the case of Android, a system with an open, modular architecture that emphasizes usability and performance, acquiring this knowledge and insight can be particularly challenging for several reasons. In spite of Android’s open source philosophy, the system is extremely large and complex, documentation and reference materials are scarce, and the code base is rapidly evolving with new features and fixes. To make matters worse, the vast majority of Android devices in use do not run the open source code, but rather proprietary versions that have been heavily customized by vendors for product dierentiation. Proposing security improvements or making customizations without suicient insight into the system typically leads to less-practical, less-eicient, or even vulnerable results. Point solutions to specific problems risk leaving other similar problems in the distributed security architecture unsolved. Far-reaching general-purpose approaches may further complicate an already complex system, and force end-users to endure significant performance and usability degradations regardless of their specific security and privacy needs. In the case of vendor customization, uninformed changes can introduce access control inconsistencies and new vulnerabilities. Hence, the lack of methodologies and resources available for gaining insight about Android security is hindering the development of practical security solutions, sound vendor customizations, and end-user awareness of the proprietary devices they are using. Addressing this deficiency is the subject of this dissertation. New approaches for analyzing, evaluating and understanding Android access controls are introduced and used to create an interactive database for use by security researchers as well as system designers and end-user product evaluators. Case studies using the new techniques are described, with results uncovering problems in Android’s multiuser framework and vendor-customized System Services. Finally, the new insights are used to develop and implement a novel virtualization-based security architecture that protects sensitive resources while preserving Android’s open architecture and expected levels of performance and usability. UNDERSTANDING AND IMPROVING SECURITY OF THE ANDROID OPERATING SYSTEM by Edward Paul Ratazzi B.S., Rensselaer Polytechnic Institute, 1987 M.S., Syracuse University, 1992 M.S., Rensselaer Polytechnic Institute, 2006 DISSERTATION Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Electrical & Computer Engineering Syracuse University December 2016 This is a work of the U.S. Government and is not subject to copyright protection in the United States. Foreign copyrights may apply. DISCLAIMER The views expressed in this dissertation are those of the author and do not reflect the oicial policy or position of the United States Air Force, Department of Defense, or the U.S. Government. v Dedicato a mio nonno, Edward Ratazzi, Sr. — Dedicated to my grandpop, Henry Paul, Jr. vi Acknowledgments My deepest gratitude goes to those around me who made completing this dissertation possible. First, to my advisor, Prof. Wenliang Du. Even though I met you with a career’s worth of experience already behind me, your insights about conducting research, distilling problems and critical thinking have changed my professional life. I will consider myself a great success if I can pass along to others even a fraction of what I learned from you. I am especially thankful for your patience, approachability, friendly style, and understanding of my outside commitments to work and family. To my defense committee, Prof. Joon Park, Prof. Shiu-Kai Chin, Prof. Jian Tang, Prof. Yuzhe Tang, and Prof. Heng Yin, for taking time out of your busy schedules to read this dissertation, provide valuable feedback and serve on my committee. To the Information Directorate of the Air Force Research Laboratory for its commitment to career-long learning and professional development. To my past and present colleagues there, including Dr. Warren Debany, Jr., Dr. Kamal Jabbour, Dr. Davy Belk, Joe Camera, Lt. Col. David Bibighaus, Dr. Dan Pease, and Dr. Lok Yan. You supported and guided my return to graduate school, and provided much-needed encouragement along the way. I am particularly indebted to my supervisor and friend, Jim Perretta. For the last four years you have sheltered me from many day-to-day distractions so that I could focus on conducting and documenting my in-house research. Now that I am done, I hope to rise to the new challenges and opportunities your leadership brings to me. To the current and former students of the Computer Security Research Group at Syracuse, vii especially Amit Ahlawat, Francis Akowuah, Ashok Bommisetti, Nian Ji, Dr. Yousra Aafer, Dr. Xiao Zhang, Jiaming Liu, Kailiang Ying, Yifei Wang, Hao Hao, Haichao Zhang, and Lusha Wang. I am in awe of your technical skills and grateful for the countless hours of discussions we’ve had, both in group meetings and one-on-one. I wish you all the best and hope we can collaborate again in the future. To everyone at the Griiss Institute, especially Bill Wolf, Regan Johnson, Tracy DiMeo, Dr. Josh White, and Jim Hanna. You provided a comfortable, quiet and well-connected environment in which to study, research, collaborate, and write. Without your support, completing this dissertation would have been tremendously more diicult and lengthy. To my parents, Randa and Ed Ratazzi. By example, you taught me the value of education, the need for perseverance, and the importance of optimism, all ingredients I found to be essential for completing my studies. Finally and most importantly, to my wife Shirley and children Emily and Nicholas. You encouraged me when things were tough, cheered my successes, and made countless sacrifices along the way. Your love and confidence are the cornerstone of this and all other accomplishments of mine. Syracuse, New York December 2016 viii Contents Abstracti List of Figures xiv List of Tables xvi 1 Introduction1 1.1 Security enhancements proposed by the scientific literature.............. 3 1.2 Security enhancements available to end-users ..................... 4 1.3 Thesis and Contributions................................. 7 1.4 Dissertation organization................................. 9 2 Background 10 2.1 Uniqueness of Mobile Devices .............................. 10 2.2 Tutorial on Android Security ............................... 12 2.2.1 Development.................................... 12 2.2.2 Download...................................... 14 2.2.3 Installation..................................... 15 2.2.4 Run-time ...................................... 17 2.2.5 Removal....................................... 19 3 Android Access Control Evaluation Methodology 20 3.1 Introduction........................................ 21 3.1.1 Threat Model.................................... 24 ix 3.2 Background ........................................ 25 3.2.1 Framework - userId ................................. 25 3.2.2 Framework - Permissions ............................. 27 3.2.3 Framework - Package Management........................ 28 3.2.4 Filesystem ..................................... 31 3.2.5 Kernel........................................ 32 3.2.6 Run-time ...................................... 32 3.3 Method and Model..................................... 33 3.3.1 Scope........................................ 34 3.3.2 Questions & Insights................................ 37 3.3.3 Hypotheses About Multi-User Security ...................... 38 3.4 Case Study Findings.................................... 40 3.4.1 Unprotected Activities............................... 40 3.4.2 Unrestricted Administrative Functions ...................... 43 3.4.3 Shared Package Information............................ 43 3.4.4 Use of Sensors and Hardware Devices by Multiple Users............. 50 4 Access Control Characterization 54 4.1 Introduction........................................ 54 4.1.1 System Services Customization.......................... 55 4.1.2 Motivating Example ................................ 55 4.1.3 Research Questions ................................ 57 4.2 Characterizing Android Access Controls ......................... 57 4.2.1 Access Control Feature Set............................. 63 4.2.2 Feature Vector Extraction ............................. 66 4.3 Comparing Android Access Controls........................... 69 4.4 Case Study......................................... 69 4.4.1 Procedure...................................... 70 x 4.4.2 Characterization Analysis
Recommended publications
  • Android-X86 Project Marshmallow Porting
    Android-x86 Project Marshmallow Porting https://drive.google.com/open?id=1mND8K-AXbMMl8- wOTe75NOpM0xOcJbVy8UorryHOWsY 黃志偉 [email protected] 2015/11/28 http://www.android-x86.org Agenda ●Introduction: what, why, how? ●History and milestones ●Current status ●Porting procedure ●Develop android-x86 ●Future plans android-x86.org About Me ●A free software and open source amateur and promoter from Taiwan ■ CLDP / CLE ■ GNU Gatekeeper ■ Android-x86 Open Source Project ●https://zh.wikipedia.org/wiki/Cwhuang android-x86.org Introduction ●What's Android-x86? ●Why needs Android-x86? ●How can we do it? android-x86.org What's Android-x86 ? ●An open source project aimed to provide a complete solution for Android on x86 devices ●Android BSP (Board support Package) for x86 platform ●At first we use ASUS Eee PC and Virtualbox as the reference platform. ●Some vendors donate tablets, like Tegatech Tegav2, 4tiitoo AG WeTab and AMD android-x86.org Why needs Android-x86? ●Android is an open source operating-system originally designed for arm platform ●It's open source, we can port it to other platforms, like mips, PowerPC and x86 ●AOSP officially supports x86 now ● AOSP doesn’t have specific hardware components ● Still a lot of work to do to make it run on a real device android-x86.org But what are the benefits? ●Understanding Android porting process ●The x86 platform is widely available ●A test platform much faster than SDK emulator ●Android-x86 on vbox / vmware ●Suitable for tablet apps android-x86.org Android architecture android-x86.org How to do that? ●Toolchains – already in AOSP, but old..
    [Show full text]
  • Dozyap: Power-Efficient Wi-Fi Tethering
    DozyAP: Power-Efficient Wi-Fi Tethering Hao Han1,2, Yunxin Liu1, Guobin Shen1, Yongguang Zhang1, Qun Li2 1Microsoft Research Asia, Beijing, China 2College of William and Mary, Williamsburg, VA, USA ABSTRACT Wi-Fi tethering (i.e., sharing the Internet connection of a mobile phone via its Wi-Fi interface) is a useful functionali- ty and is widely supported on commercial smartphones. Yet existing Wi-Fi tethering schemes consume excessive power: they keep the Wi-Fi interface in a high power state regard- less if there is ongoing traffic or not. In this paper we pro- pose DozyAP to improve the power efficiency of Wi-Fi tethering. Based on measurements in typical applications, we identify many opportunities that a tethering phone could sleep to save power. We design a simple yet reliable sleep Figure 1: Wi-Fi tethering. protocol to coordinate the sleep schedule of the tethering phone with its clients without requiring tight time synchro- vices can connect to the mobile SoftAP through their Wi-Fi nization. Furthermore, we develop a two-stage, sleep inter- interfaces. The mobile SoftAP routes the data packets be- val adaptation algorithm to automatically adapt the sleep tween its 3G interface and its Wi-Fi interface. Consequent- intervals to ongoing traffic patterns of various applications. ly, all the devices connected to the mobile SoftAP are able DozyAP does not require any changes to the 802.11 proto- to access the Internet. col and is incrementally deployable through software up- Wi-Fi tethering is highly desired. For example, even be- dates. We have implemented DozyAP on commercial fore the Android platform provided built-in support on Wi- smartphones.
    [Show full text]
  • Download Android Os for Phone Open Source Mobile OS Alternatives to Android
    download android os for phone Open Source Mobile OS Alternatives To Android. It’s no exaggeration to say that open source operating systems rule the world of mobile devices. Android is still an open-source project, after all. But, due to the bundle of proprietary software that comes along with Android on consumer devices, many people don’t consider it an open source operating system. So, what are the alternatives to Android? iOS? Maybe, but I am primarily interested in open-source alternatives to Android. I am going to list not one, not two, but several alternatives, Linux-based mobile OSes . Top Open Source alternatives to Android (and iOS) Let’s see what open source mobile operating systems are available. Just to mention, the list is not in any hierarchical or chronological order . 1. Plasma Mobile. A few years back, KDE announced its open source mobile OS, Plasma Mobile. Plasma Mobile is the mobile version of the desktop Plasma user interface, and aims to provide convergence for KDE users. It is being actively developed, and you can even find PinePhone running on Manjaro ARM while using KDE Plasma Mobile UI if you want to get your hands on a smartphone. 2. postmarketOS. PostmarketOS (pmOS for short) is a touch-optimized, pre-configured Alpine Linux with its own packages, which can be installed on smartphones. The idea is to enable a 10-year life cycle for smartphones. You probably already know that, after a few years, Android and iOS stop providing updates for older smartphones. At the same time, you can run Linux on older computers easily.
    [Show full text]
  • Crdroid 3.10.54 Crdroid 3.10.54 * Br Photos and Great Condition That Affects Men Ranked 5 of 18 Archways Prize Wheels
    Crdroid 3.10.54 Crdroid 3.10.54 * Br photos and great condition that affects men ranked 5 of 18 archways prize wheels. Gif beat ladbrokes roulettestrong at lowes. about B2b massage at shah alam2b massage at shah alam Binweevil hangman words Daughter incest.tumblr Speedway gp programme Crdroid 3.10.54 Cheating captions tumblr Menu - Baca komik bleach lengkap bahasa indonesia Maynards wife lei liaynards wife Crdroid 3.10.54. So now introducing our new rom.which is based on lp Friends links What is skypepm ezlog, Sissy kernel ( 3.10.54 ) mt6582 based cm rom which name is Tesla os Previous drawings prim, Wild things foursome post i have given u crDroid rom. Techzbyte is a blog about How to's, Tech full movie worldfree4u.trade, Download anime kindaichi shounen News, Apps, Education, Stock & Custom Roms, Custom recovery, Games no jikenbo tv sub indo and Internet freebies for Smartphones. 22-11-2016 · Hi friends .. introducing our new rom for mmx fire 4. crDroid Rom Based on lp kernel bloggers 3.10.54 Mt 6582 .. Based on cm (5.1) FEATURES : CyanogenMod theme. Hcpcs code for restylane Isabelle blais nue video [ROM][MT6582][LP][ 3.10.54 +] PACMAN V2 FOR GIONEE M3 Many of Trinh hoi s second wife mai thy you might not be aware of PACMan ROM. As the image shows, its a combinati. CRDROID OS-LP-MT6582- 3.10.54 + FOR MMX Q340 BY MANJUNATH YASHU FEATURES CyanogenMod theme supervisor; Power menu customizations; Nav bar tweaks (on/off toggle and. CRDROID OS-LP-MT6582- 3.10.54 + FOR MMX Q340 BY MANJUNATH YASHU CRDROID OS-LP-MT6582- 3.10.54 + FOR MMX Q340 BY MANJUNATH YASHU FEATURES CyanogenMod theme manager; Power.
    [Show full text]
  • Linux Based Mobile Operating Systems
    INSTITUTO SUPERIOR DE ENGENHARIA DE LISBOA Área Departamental de Engenharia de Electrónica e Telecomunicações e de Computadores Linux Based Mobile Operating Systems DIOGO SÉRGIO ESTEVES CARDOSO Licenciado Trabalho de projecto para obtenção do Grau de Mestre em Engenharia Informática e de Computadores Orientadores : Doutor Manuel Martins Barata Mestre Pedro Miguel Fernandes Sampaio Júri: Presidente: Doutor Fernando Manuel Gomes de Sousa Vogais: Doutor José Manuel Matos Ribeiro Fonseca Doutor Manuel Martins Barata Julho, 2015 INSTITUTO SUPERIOR DE ENGENHARIA DE LISBOA Área Departamental de Engenharia de Electrónica e Telecomunicações e de Computadores Linux Based Mobile Operating Systems DIOGO SÉRGIO ESTEVES CARDOSO Licenciado Trabalho de projecto para obtenção do Grau de Mestre em Engenharia Informática e de Computadores Orientadores : Doutor Manuel Martins Barata Mestre Pedro Miguel Fernandes Sampaio Júri: Presidente: Doutor Fernando Manuel Gomes de Sousa Vogais: Doutor José Manuel Matos Ribeiro Fonseca Doutor Manuel Martins Barata Julho, 2015 For Helena and Sérgio, Tomás and Sofia Acknowledgements I would like to thank: My parents and brother for the continuous support and being the drive force to my live. Sofia for the patience and understanding throughout this challenging period. Manuel Barata for all the guidance and patience. Edmundo Azevedo, Miguel Azevedo and Ana Correia for reviewing this document. Pedro Sampaio, for being my counselor and college, helping me on each step of the way. vii Abstract In the last fifteen years the mobile industry evolved from the Nokia 3310 that could store a hopping twenty-four phone records to an iPhone that literately can save a lifetime phone history. The mobile industry grew and thrown way most of the proprietary operating systems to converge their efforts in a selected few, such as Android, iOS and Windows Phone.
    [Show full text]
  • 2020 Spring Product Guide Final-Min
    2020 SPRING INTEGRATOR PRODUCT GUIDE COME SWIM WITH THE BIG FISH November 9 – 11, 2020 | Cleveland, OH | Huntington Convention Center Take control of your business success. Gain insights from the integration industry elite this November at Total Tech Summit. This uniquely powerful by invitation-only event drives extraordinary progress in the integration industry. Total Tech Summit is where the industry elite gather. Total Tech Summit helps to grow and improve your company through: › Educational, deep-dive sessions from the industry elite › 1-on-1 and boardroom meetings with new vendors that can take your offerings from better to best › Networking at every turn. Connect with both integrators in your industry and beyond to help give you fresh ideas and business strategies › Complimentary flights, hotel, “Gathering of professionals that registration, and meals to help you are non-competition to collaborate focus on what matters most on ideas to grow business in profits, procurement, strategies, staffing and general business practices is a wealth of knowledge at the cost of a couple days’ time and to also have the added benefit of meeting one on one with manufacturers that you may not have reached out to.” — John Rudolph, Vice President, PCD To learn more and to apply to join the best in the industry, please visit www.totaltechsummit.com Table of Contents Page 6 Audio ▶ Page 23 Control/Networking/Energy Management ▶ Page 36 Home Enhancements (central vacuum, wire and cable, tools, testers, furniture) ▶ Page 48 Security ▶ Page 53 Video ▶ Page
    [Show full text]
  • Greg Kroah-Hartman [email protected] Github.Com/Gregkh/Presentation-Kdbus
    kdbus IPC for the modern world Greg Kroah-Hartman [email protected] github.com/gregkh/presentation-kdbus Interprocess Communication ● signal ● synchronization ● communication standard signals realtime The Linux Programming Interface, Michael Kerrisk, page 878 POSIX semaphore futex synchronization named eventfd unnamed semaphore System V semaphore “record” lock file lock file lock mutex threads condition variables barrier read/write lock The Linux Programming Interface, Michael Kerrisk, page 878 data transfer pipe communication FIFO stream socket pseudoterminal POSIX message queue message System V message queue memory mapping System V shared memory POSIX shared memory shared memory memory mapping Anonymous mapping mapped file The Linux Programming Interface, Michael Kerrisk, page 878 Android ● ashmem ● pmem ● binder ashmem ● POSIX shared memory for the lazy ● Uses virtual memory ● Can discard segments under pressure ● Unknown future pmem ● shares memory between kernel and user ● uses physically contigous memory ● GPUs ● Unknown future binder ● IPC bus for Android system ● Like D-Bus, but “different” ● Came from system without SysV types ● Works on object / message level ● Needs large userspace library ● NEVER use outside an Android system binder ● File descriptor passing ● Used for Intents and application separation ● Good for small messages ● Not for streams of data ● NEVER use outside an Android system QNX message passing ● Tight coupling to microkernel ● Send message and control, to another process ● Used to build complex messages
    [Show full text]
  • MEDIATEK AP SDK 4.3.0.0 USER's MANUAL
    APSoC SDK 4.3.0.0 User’s Manual MediaTek Inc. MEDIATEK AP SDK 4.3.0.0 USER’s MANUAL Copyright © 2014 MediaTek Inc. All Rights Reserved. This document is property of MediaTek Inc., receipt, or possession of this document does not express, license, or imply any rights to use, sell, design, or manufacture from this information or the software documented herein. No reproduction, publication, or disclosure of this information, in whole or in part, shall be allowed, unless the prior written consent of MediaTek Inc. is obtained. NOTE: THIS DOCUMENT CONTAINS SENSITIVE INFORMATION AND HAS RESTRICTED DISTRIBUTION. APSoC SDK 4.3.0.0 User’s Manual Proprietary Notice and Liability Disclaimer The confidential Information, technology or any Intellectual Property embodied therein, including without limitation, specifications, product features, data, source code, object code, computer programs, drawings, schematics, know-how, notes, models, reports, contracts, schedules and samples, constitute the Proprietary Information of MediaTek (hereinafter "Proprietary Information") All the Proprietary Information is provided "AS IS". No Warranty of any kind, whether express or implied, is given hereunder with regards to any Proprietary Information or the use, performance or function thereof. MediaTek hereby disclaims any warranties, including but not limited warranties of non-infringement, merchantability, completeness, accuracy, fitness for any particular purpose, functionality and any warranty related to course of performance or dealing of Proprietary Information. In no event shall MediaTek be liable for any special, indirect or consequential damages associated with or arising from use of the Proprietary Information in any way, including any loss of use, data or profits. MediaTek retains all right, title or interest in any Proprietary Information or any Intellectual Property embodied therein.
    [Show full text]
  • Performance Tuning Guide
    Red Hat Enterprise Linux 7 Performance Tuning Guide Optimizing subsystem throughput in Red Hat Enterprise Linux 7 Red Hat Subject Matter ExpertsLaura Bailey Charlie Boyle Red Hat Enterprise Linux 7 Performance Tuning Guide Optimizing subsystem throughput in Red Hat Enterprise Linux 7 Laura Bailey Red Hat Customer Content Services Charlie Boyle Red Hat Customer Content Services Red Hat Subject Matter Experts Edited by Milan Navrátil Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2016 Red Hat, Inc. and others. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • The Android Platform Security Model∗
    The Android Platform Security Model∗ RENÉ MAYRHOFER, Google and Johannes Kepler University Linz JEFFREY VANDER STOEP, Google CHAD BRUBAKER, Google NICK KRALEVICH, Google Android is the most widely deployed end-user focused operating system. With its growing set of use cases encompassing communication, navigation, media consumption, entertainment, finance, health, and access to sensors, actuators, cameras, or microphones, its underlying security model needs to address a host of practical threats in a wide variety of scenarios while being useful to non-security experts. The model needs to strike a difficult balance between security, privacy, and usability for end users, assurances for app developers, and system performance under tight hardware constraints. While many of the underlying design principles have implicitly informed the overall system architecture, access control mechanisms, and mitigation techniques, the Android security model has previously not been formally published. This paper aims to both document the abstract model and discuss its implications. Based on a definition of the threat model and Android ecosystem context in which it operates, we analyze how the different security measures in past and current Android implementations work together to mitigate these threats. There are some special cases in applying the security model, and we discuss such deliberate deviations from the abstract model. CCS Concepts: • Security and privacy → Software and application security; Domain-specific security and privacy architectures; Operating systems security; • Human-centered computing → Ubiquitous and mobile devices. Additional Key Words and Phrases: Android, security, operating system, informal model 1 INTRODUCTION Android is, at the time of this writing, the most widely deployed end-user operating system.
    [Show full text]
  • Energy Consumption Studies for 3G Traffic Consolidation on Android
    Final thesis Energy Consumption Studies for 3G Traffic Consolidation on Android using WiFi and Bluetooth by Ugaitz Moreno Arocena LITH-IDA-EX-2014/ERASMUS-A{14/002{SE 2014-01-05 Final thesis Energy Consumption Studies for 3G Traffic Consolidation on Android using WiFi and Bluetooth by Ugaitz Moreno Arocena LITH-IDA-EX-2014/ERASMUS-A{14/002{SE 2014-01-05 Supervisor: Ekhiotz Jon Vergara Examiner: Simin Nadjm-Tehrani Abstract Mobile phones have evolved from being devices just to make phone calls to become smartphones with added capabilities like surfing the network. Wireless communication has played a very important role in the evolution of smartphones. The work in this thesis aims to study the potential to reduce the energy consumption of the 3G communications by using a hybrid architecture. An idea first presented in the paper by Vergara and Nadjm-Tehrani [1]. This architecture consists of a group of nodes that communicate using WiFi or Bluetooth to forward their traffic using one node's 3G interface. In this thesis the named energy sharing scheme is implemented on Android mobile devices and experiments have been performed using a number of realistic traces to assess achievable gains and the energy footprint of the scheme itself. Even though communication technologies, screen features, multimedia capabilities, or processing power have been taken to the highest level, phones' batteries have not improved at the same speed. Nowadays battery lifetime has become a major issue with respect to cellular communication. With 3G communications Internet connection anytime and anywhere is provided to the terminals but this technology is optimized for peak perfor- mance whereas in underutilization it wastes a lot of energy.
    [Show full text]
  • Tl-Wn723n(Eu) V3 Ug
    TL-WN723N User Guide 150Mbps Mini Wireless N USB Adapter REV4.1.0 1910011877 Contents About This Guide . 1 Chapter 1. Get to Know About Your Adapter . 2 1. 1. Product Overview . 3 1. 2. LED Status . 3 Chapter 2. Connect to a Computer . 5 Chapter 3. Windows. 7 3. 1. Install Driver and Utility. 8 3. 2. Join a Wireless Network. 11 3. 2. 1. Windows Wireless Utility . 11 3. 2. 2. TP-LINK Utility. 13 3. 2. 3. WPS (Wi-Fi Protected Setup) . 14 3. 3. Management . 18 3. 3. 1. Status. 19 3. 3. 2. Profile . 19 3. 3. 3. Advanced. 22 3. 3. 4. SoftAP . 22 3. 3. 5. About . 24 3. 4. Uninstall Driver and Utility. 24 Chapter 4. Mac OS X. 26 4. 1. Install Driver and Utility. 27 4. 2. Join a Wireless Network. 32 4. 2. 1. TP-LINK Utility. 32 4. 2. 2. WPS (Wi-Fi Protected Setup) . 34 4. 3. Management . 38 4. 4. Uninstall Driver and Utility. 40 Chapter 5. Linux . 42 About This Guide This guide is a complementation of Quick Installation Guide. The Quick Installation Guide instructs you on quick Internet setup, and this guide provides details of each function and shows you the way to configure these functions appropriate to your needs. When using this guide, please notice that features of the adapter may vary slightly depending on the model and software version you have. All screenshots, images, parameters and descriptions documented in this guide are used for demonstration only. Conventions In this guide, the following conventions are used: Convention Description Hyperlinks are in blue italic.
    [Show full text]