3 URL: https://github.com/googlevr/gvr-android-sdk
6 Revision: 233e7fe922a543e0bc55382d64cacd047307d0e7
13 The GVR Android SDK supports both Daydream and Cardboard, including a simple API
14 used for creating apps inserted into Cardboard viewers, and the more complex API
15 for supporting Daydream-ready phones and the Daydream controller.
18 - Due to binary size concern, we have decided to use a static shim library
19 instead of the shared library that comes with this checkout. The static
20 libraries are downloaded from a public storage through gclient sync.
22 - For Version 1.10.0, we have two date: 6 Dec 2016 and 10 Feb 2017. The latter
23 version cherrypick a CL that fix a crash on K and L.
25 - All JNI calls in the static library also needs to be manually registered. So
26 we have 3 jni related files. These files were generated by
27 base/android/jni_generator/jni_generator.py from Java files. Modifications to
28 these generated files are documented in the files.
30 - The files generated by jni_generator.py use base::size which is not available
31 from third_party; std::extent<decltype> was used instead, which is standard C++
34 - In order to run automated end-to-end tests on VR features, VR Services
35 (com.google.vr.vrcore) and in some cases Daydream Home
36 (com.google.android.vr.home) need to be installed before running tests. These
37 are downloaded into test-apks/vr_services and test-apks/daydream_home,
38 respectively. The downloaded APKs are the release APKs that are or were
39 publicly available via the Play Store.
41 - In order to run automated end-to-end tests that involve a Daydream controller,
42 controller_test_api.aar needs to be present. This allows us to send controller
43 events using broadcasts like a real controller sends them over Bluetooth. The
44 library is open-sourced similar to the other .aars, but since it's only useful
45 for Chromium at the moment, it is uploaded to storage instead of to GitHub like