Present user-facing UI when VHAL fragment cannot be used

With SELinux enforcement turned on, the Vehicle HAL fragment does not
have permission to connect to the HAL instance.

This could be fixed but it would require a decent amount of effort,
and in general the VHAL tool should only be really useful during early
bringup, when SELinux is likely to be turned off anyway. In all other
scenarios, the car property test UI should be preferred.

Bug: 150336686
Test: setenforce 1 and load VHAL fragment
Change-Id: I4070cf786d27bde0896a6e5576f0bd3aab5a728a
1 file changed
tree: 7e469c9a1276eaed1f9e67c03e5d39ffe9eec754
  1. car-bugreportd/
  2. car-default-input-service/
  3. car-lib/
  4. car-maps-placeholder/
  5. car-systemtest-lib/
  6. car-test-lib/
  7. car-usb-handler/
  8. car_product/
  9. computepipe/
  10. EncryptionRunner/
  11. evs/
  12. experimental/
  13. FrameworkPackageStubs/
  14. obd2-lib/
  15. procfs-inspector/
  16. service/
  17. surround_view/
  18. tests/
  19. tools/
  20. user/
  21. vehicle-hal-support-lib/
  22. watchdog/
  23. .clang-format
  24. .gitignore
  25. Android.mk
  26. CleanSpec.mk
  27. CPPLINT.cfg
  28. OWNERS
  29. PREUPLOAD.cfg
  30. README.md
README.md

Native (C++) code format is required to be compatible with .clang-format file. Run

git clang-format --style=file --extension='h,cpp,cc' HEAD~

Note that clang-format is not desirable for Android java files. Therefore the command line above is limited to specific extensions.