Droidcon London 2017 talk - http://uk.droidcon.com/#program

1. How do you use your Android phone?
Pexels/CC0 Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 1

2. Mobile Navigation
©Google Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 2

3. android.location - A Tool for Developers or
GNSS Researchers?
droidcon London 2017
Lukasz K Bonenberg @LKBLab
26th October 2017
Nottingham Geospatial Institute
3

4. How mobile device navigates?

5. Google Play Services (android.gsm.location)
developers.google.com/awareness-location/
developer.android.com/guide/topics/location/strategies.html
©Google Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 5

6. Why so excited about android.location?
©Google Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 6

7. Fused location provider
©Google Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 7

8. How accurate is your phone?
Courtesy of Ms Alina Wang Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 8

9. Can we get more accurate?

10. Differential solution
Courtesy of Prof Renato Filjar Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 10

11. Differential accuracy now
Figure 1: Time series and CDF for current Android hardware
S. Riley et al (2017) Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 11

12. Expected future performance
Figure 2: CDF for upcomming dual-freq Android chpsets with mobile phone
antenna equivalent
S. Riley et al (2017) Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 12

13. Predictive intelligence
S. Roberts et al (2017) Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 13

14. Localised corrections and API encapsulation
14

15. Is this all about position?

16. Position is not everything
SplitShire/BY0 Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 16

17. Sensors everywhere
William Starkey/CC0 Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 17

18. Interconnected
©Eric Fischer/bigthink.com Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 18

19. Privacy concerns
19

20. Outlook and Summary

21. What we discussed
1 How mobile device navigates?
2 Can we get more accurate?
3 Is this all about position?
4 Outlook and Summary
21

22. Take away
• For raw GNSS observations use android.location native library; for
other sensors use android.hardware1
.
• Current hardware is not perfect, future dual frequency chip-sets and
external antennas will be a large improvement.
• For GNSS, position is not everything. Think outside of the box.
• There are privacy concerns with spatial data.
1
GNSS knowledge required as android.gms.location encapsulation is missing. We are addressing
this in FLAMINGO H2020 project.
22

23. Knowledge is the key... Useful links
• Android Location Google I/O’17
https://www.youtube.com/watch?v=5MIBNOTD_mM
• Google GNSS devs http://g.co/gnsstools
• GSA user report http://bit.ly/2i36aRj
• GSA GNSS Android RAW measurements (TBA...)
• ”Privacy and IoT” Gilad Rosner
• My introduction to calculating pseudoranges at
github.com/DfAC/AndroidGNSS
Lukasz.Bonenberg@nottingham.ac.uk @LKBLab 23