| commit | c8a8f9f228686f13fface43b1bdc80b761e648be | [log] [tgz] |
|---|---|---|
| author | davidln <davidln@google.com> | Tue Dec 11 11:04:53 2018 -0800 |
| committer | davidln <davidln@google.com> | Wed Dec 12 09:30:24 2018 -0800 |
| tree | d9beb9cf935088d1c9b73f0b0f15dddba49aa609 | |
| parent | 3dee2a6c44ce6432c11b8592eb3ae88b19236fa6 [diff] |
Allow OEM configuration of the fragment to start at launch. Right now, the fragment to launch on app startup is hardcoded in Java making it difficult to customize. Moving the fragment to launch to a config resource will allow OEMs to overlay and update the fragment name to define the hierarchy root. Fixes: 120849211 Test: build and deploy, manually update value and ensure proper fragment launches Change-Id: I62cc9c33efd2bda928fb7ae6771f568aa29f1720