Google Git
Sign in
android / platform / hardware / interfaces / 4e04150188ed8be329cf6acbf9c36fe6970532c7
commit4e04150188ed8be329cf6acbf9c36fe6970532c7[log] [tgz]
authorJan Kowal <jan.kowal@aptiv.corp-partner.google.com>Thu Jan 21 12:44:44 2021 +0100
committerJan Kowal <jan.kowal@aptiv.corp-partner.google.com>Thu Jan 21 12:44:44 2021 +0100
tree8b6463c16b9840de4a4468018c2f97e3ac727afc
parent4cd0571bd6d3529c57aa88a8073fb9434c550a13 [diff]
broadcastradio@2.0 VTS uses FM frequency invalid in some regions

In Japan FM frequency range is 76-95MHz thus FmTune test using
hardcoded 101.1MHz fails on devices preconfigured for this
region when TunerSession::tune returns INVALID_PARAMETER.
Proposed new frequency is valid in all regions.

Test: run VtsHalBroadcastradioV2_0TargetTest on hardware units
configured for Europe, US, Japan (and preferably other) analog
tuner regions

Bug: b/177916339

Change-Id: I86081fc3e1c0e0959039d5a00d96873fca454da6
1 file changed
tree: 8b6463c16b9840de4a4468018c2f97e3ac727afc
  1. atrace/
  2. audio/
  3. authsecret/
  4. automotive/
  5. biometrics/
  6. bluetooth/
  7. boot/
  8. broadcastradio/
  9. camera/
  10. cas/
  11. common/
  12. compatibility_matrices/
  13. configstore/
  14. confirmationui/
  15. contexthub/
  16. drm/
  17. dumpstate/
  18. fastboot/
  19. gatekeeper/
  20. gnss/
  21. graphics/
  22. health/
  23. identity/
  24. input/
  25. ir/
  26. keymaster/
  27. light/
  28. media/
  29. memtrack/
  30. neuralnetworks/
  31. nfc/
  32. oemlock/
  33. power/
  34. radio/
  35. rebootescrow/
  36. renderscript/
  37. secure_element/
  38. security/
  39. sensors/
  40. soundtrigger/
  41. tests/
  42. tetheroffload/
  43. thermal/
  44. tv/
  45. usb/
  46. vibrator/
  47. vr/
  48. weaver/
  49. wifi/
  50. .clang-format ⇨ ../../build/soong/scripts/system-clang-format
  51. Android.bp
  52. CleanSpec.mk
  53. current.txt
  54. METADATA
  55. NOTICE
  56. OWNERS
  57. PREUPLOAD.cfg
  58. TEST_MAPPING
  59. update-base-files.sh
  60. update-makefiles.sh