tree 5c609d9af00962bc2820db181b3ca326ee22c18d
parent a2ea959366a264fffb4ee8254015d90161e93cd2
author Yoshiaki Naka <yoshiaki.naka@sony.com> 1528419934 +0900
committer android-build-team Robot <android-build-team-robot@google.com> 1532998844 +0000

SecureElementService may be unavailable when NfcService is started

Currently NfcService attempts to get an interface to
SecureElementService only in its constructor, so there is no chance to
do it later again if it fails. Introducing a lazy initialization
mechanism is required.

Bug: 111775064
Bug: 110121800
Test: Confirmed that NfcService gets SEService even if it failed once.

Change-Id: I2b3c873d7661cde63af8c9f8c05945c3568f012f
(cherry picked from commit a9ef080f9964f46d4983bf7637a2c52a6e0eadd2)