
Android Sensor Programming By Example
Beschreibung
Alle Preise
Weitere Details
Weitere Ausgaben
Person
Varun Nagpal has been developing mobile apps since 2005 and has developed and contributed to more than 100 professional apps and games on various platforms, such as Android, iOS, Blackberry, and J2ME. Android app development has been his main area of expertise, and he has developed apps for a wide variety of Android devices, such as Android phones, tablets, watches, smart TVs, Android Auto, and Google Glass. He moved to Chicago in late 2013, and since then, he has become a seasoned mobile architect. He has worked in different roles (mobile architect, technical lead, senior developer, and technical consultant) for a variety of various global clients (Allstate, Verizon, AT&T, Sydbank Denmark, SiS Taiwan, Chams PLC Nigeria, and Nandos South Africa) in order to implement their mobile solutions. He has SCJP (Core Java) and SCWD (JSP and Servlets) certifications from Sun Microsystems and MCP (C#) and MCTS (ASP.NET) certifications from Microsoft. You can find his blogs on mobile technology and white papers written by him on his website at http://www.varunnagpal.com/. When he's not working, Varun can be found meditating or playing the flute. He also loves to develop meditation apps and fun games in his free time. He has developed about 40 meditation apps and games available on Google Play (https://play.google.com/store/apps/developer?id=Creative.Software.Studio) and the Apple App Store (https://itunes.apple.com/us/artist/creative-software-studio/id574745824) under the name of Creative Software Studio, his part-time start-up company (http://creativesoftwarestudio.com/).
Inhalt
- Cover
- Copyright
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Table of Contents
- Preface
- Chapter 1: Sensor Fundamentals
- What are sensors?
- Types of sensors
- Types of sensor values
- Motion, position, and environmental sensors
- Motion sensors
- Position sensors
- Environmental sensors
- Sensors' coordinate system
- Android Sensor Stack
- Components of the sensor framework
- SensorManager
- SensorEventListener
- Sensor
- SensorEvent
- Sensor's sampling period, power, and battery consumption
- The reporting modes of sensors
- Dealing with specific sensor configuration
- Checking the availability of the sensor at runtime
- Declaring the sensor as mandatory feature
- Sensor availability based on the Android API level
- Best practice for accessing sensors
- Summary
- Chapter 2: Playing with Sensors
- Understanding the sensor framework callbacks
- Seeing the big picture
- Time for action - using sensors in the foreground activity
- What just happened?
- Time for action - listing the available sensors on a device
- What just happened?
- Time for action - knowing individual sensors' capabilities
- What just happened?
- Time for action - getting the sensor values and updating the user interface
- What just happened?
- Time for action - processing the sensor values in the background service
- The phone handling algorithm
- What just happened?
- Summary
- Chapter 3: The Environmental Sensors - The Weather Utility App
- The weather utility app's requirements
- Understanding environmental sensors
- Time for action - using the temperature sensor
- What just happened?
- Getting air pressure from the phone's pressure sensor
- Time for action - calculating the altitude using the pressure sensor
- What just happened?
- Getting relative humidity from the phone's humidity sensor
- Time for action - calculating the dew point and absolute humidity
- What just happened?
- Time for action - comparing the temperature, humidity, and pressure values from web services to phone sensors
- Third-party web service - open weather map
- Using Google Play Services Location API and AsyncTask
- What just happened?
- Summary
- Chapter 4: The Light and Proximity Sensors
- Understanding the light and proximity sensors
- The automatic torch light and screen brightness app requirements
- Time for action - turning the torch light on and off using the proximity sensor
- What just happened?
- Time for action - adjusting the screen brightness using the light sensor
- What just happened?
- Wake locks, wakeup sensors, and the FIFO queue
- Wakeup and non-wakeup sensors
- The sensor's hardware FIFO queue
- Summary
- Chapter 5: The Motion, Position, and Fingerprint Sensors
- Understanding motion-based sensors
- The accelerometer sensor
- The gyroscope sensor
- The gravity sensor
- The linear acceleration sensor
- The significant motion sensor
- Understanding position-based sensors
- The magnetometer sensor
- The orientation sensor
- The fingerprint sensor
- Time for action - shake detection using the accelerometer sensor
- Time for action - the compass using orientation sensor and orientation APIs
- Time for action - using the fingerprint sensor
- What just happened?
- Summary
- Chapter 6: The Step Counter and Detector Sensors - The Pedometer App
- The pedometer app's requirements
- Understanding the step counter and step detector sensors
- The step counter sensor
- The step detector sensor
- Time for action - using the step counter sensor in activity
- Time for action - maintaining step history with the step detector sensor
- What just happened?
- Understanding the walking, jogging, and running signatures using the accelerometer sensor's data
- The walking signature using the accelerometer sensor
- The jogging or fast walking signature using the accelerometer sensor
- The running signature using the accelerometer sensor
- The type of step detection algorithm
- Making it battery- and CPU-efficient using sensor fusion
- Scope for improvement
- Time for action - type of step (walking, jogging, and running) detection using the accelerometer sensor
- What just happened?
- Summary
- Chapter 7: The Google Fit Platform and APIs - The Fitness Tracker App
- The Google Fit platform
- Google Fitness Store
- REST APIs
- Android Fitness APIs
- Sensors API
- Recording API
- History API
- Sessions API
- Bluetooth Low Energy API
- Config API
- Platform basics
- Data sources
- Data types
- Data point
- Data set
- Authorization and permission scopes
- Registration with the Google developer console
- Authorization from a user in the application
- Fitness scopes
- Installing and running time permissions
- Fitness tracker app using fitness APIs
- Fitness tracker application requirements and architecture
- Time for action - working with live fitness data using the Sensors API
- What just happened?
- Time for action - recording fitness data in background using Recording API
- What just happened?
- Time for action - getting history fitness data using the History API
- What just happened?
- Asynchronous versus synchronous results callback
- Summary
- Index
Systemvoraussetzungen
Dateiformat: ePUB
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat ePUB ist sehr gut für Romane und Sachbücher geeignet – also für „fließenden” Text ohne komplexes Layout. Bei E-Readern oder Smartphones passt sich der Zeilen- und Seitenumbruch automatisch den kleinen Displays an.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.
Dateiformat: PDF
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat PDF zeigt auf jeder Hardware eine Buchseite stets identisch an. Daher ist eine PDF auch für ein komplexes Layout geeignet, wie es bei Lehr- und Fachbüchern verwendet wird (Bilder, Tabellen, Spalten, Fußnoten). Bei kleinen Displays von E-Readern oder Smartphones sind PDF leider eher nervig, weil zu viel Scrollen notwendig ist.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.