Skip to content
Snippets Groups Projects
  1. May 10, 2024
  2. May 09, 2024
  3. May 08, 2024
  4. May 07, 2024
    • Ryan Prichard's avatar
      681514f3
    • Yan Yan's avatar
      Make VCN HSUM compatible · 43ee23b0
      Yan Yan authored
      Require VCN to be used by a "main user" instead of a "system user"
      since "system user" will no longer be a full user on HSUM devices
      
      Bug: 310310661
      Test: FrameworksVcnTests, CtsVcnTestCases on non-hsum and hsum devices
      Flag: android.net.vcn.enforce_main_user
      Change-Id: I5abfa7ba82055cd953083b1ab3f83e61bafd8a55
      43ee23b0
    • Yan Yan's avatar
    • Zach Lee's avatar
      2c11b9ff
    • Aurélien Pomini's avatar
    • Inseob Kim's avatar
      Use no_full_install: true instead of installable: false · 8541b878
      Inseob Kim authored
      So far, we have used `instalable: false` to avoid collision with the
      other modules that are installed to the same path. A typical example was
      <foo> and <foo>.microdroid. The latter is a modified version of the
      former for the inclusion of the microdroid image. They however both have
      the same instalation path (ex: system/bin) and stem (ex: foo) so that we
      can reference them using the same path regardless of whether we are in
      Android or microdroid.
      
      However, the use of `installable: false` for the purpose is actually
      incorrect, because `installable: false` also means, obviously, "this
      module shouldn't be installed". The only reason this incorrect way has
      worked is simply because packaging modules (ex: android_filesystem)
      didn't respect the property when gathering the modules.
      
      As packaging modules are now fixed to respect `installable: false`, we
      need a correct way of avoiding the collision. `no_full_install: true` is
      it.
      
      If a module has this property set to true, it is never installed to the
      full instal path like out/target/product/<partition>/... It can be
      installed only via packaging modules.
      
      Bug: 335369205
      Bug: 337993945
      Test: m droid aosp_cf_system_x86_64
      Change-Id: If9c053968bde39c3eb3b852f1df1d475161bd846
      8541b878
    • Ryan Prichard's avatar
      aapt2: fix dangling reference to diag · cbcff740
      Ryan Prichard authored
      The lambdas that ManifestFixer::BuildRules attach to XmlActionExecutor
      outlive ManifestFixer::BuildRules, so they need to capture diag
      by-value instead of by-reference.
      
      Bug: 339119172
      Test: aapt2_tests
      Change-Id: I6b9b6a8733875247a5be12111413b45b99727e1f
      cbcff740
  5. May 06, 2024
    • Treehugger Robot's avatar
    • Juan Yescas's avatar
      Consume consecutive delimiters at beginning of refilled buffer · dc0a5b1f
      Juan Yescas authored
      This change makes sure that the consecutive delimiters at the
      beginning of the just refilled buffer are consumed.
      
      Previously, if there were consecutive delimiters at the beginning
      of the just refilled buffer, they were not being consumed and were
      causing parsing errors. This was also causing fatal exceptions.
      
      ```
      04-22 12:37:53.077   607   707 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: CachedAppOptimizerThread
      04-22 12:37:53.077   607   707 E AndroidRuntime: java.lang.NumberFormatException: invalid long: READ
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.invalidLong(ProcFileReader.java:238)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.parseAndConsumeLong(ProcFileReader.java:220)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextLong(ProcFileReader.java:183)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextLong(ProcFileReader.java:172)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextInt(ProcFileReader.java:246)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.os.ProcLocksReader.handleBlockingFileLocks(ProcLocksReader.java:111)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.server.am.CachedAppOptimizer$FreezeHandler.handleMessage(CachedAppOptimizer.java:2267)
      04-22 12:37:53.077   607   707 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:107)
      04-22 12
      ```
      
      Bug: 336208153
      Bug: 338416108
      Bug: 331988929
      Test: atest --host-unit-test-only -c  ProcFileReaderTest
      Change-Id: I12813fa204d53d53687ffe6e8e3c0a85595b7e25
      dc0a5b1f
    • Yan Yan's avatar
      Support disabling IPsec packet loss detector · ec173dea
      Yan Yan authored
      Allow disabling detector for better configurability
      
      Bug: 336638836
      Test: atest FrameworksVcnTests(new tests) && atest CtsVcnTestCases
      Flag: android.net.vcn.allow_disable_ipsec_loss_detector
      Change-Id: Icd7183d12fb287399a500ea9c0ee4125c749275c
      ec173dea
    • Yuyang Huang's avatar
    • Eric Biggers's avatar
    • Treehugger Robot's avatar
    • Kangping Dong's avatar
      Merge "[Thread] add Thread icon" into main · 710143f5
      Kangping Dong authored
      710143f5
    • Kangping Dong's avatar
      [Thread] add Thread icon · a1df9d2a
      Kangping Dong authored
      This is imported from material icon at https://fonts.corp.google.com/icons?selected=Google%20Symbols%3Athread_logo%3AFILL%400%3Bwght%40400%3BGRAD%400%3Bopsz%4024
      
      But system notifications and settings also need to use this icon. For
      example, it will be used in Settings > Connected devices > Connection preferences.
      
      Bug: 327583301
      Change-Id: I08ef9c90b7d4085f9b901b3d9c41b57258aa9680
      a1df9d2a
    • Fredrik Ryden's avatar
      Fixed graphical glitch in lockpattern view · 52098a13
      Fredrik Ryden authored
      Fixed end point correctional animation for cell to cell animations
      during lock pattern drawing.
      
      In the lock pattern view, cells have an area of slop around them to
      allow for drawing the pattern without hitting the exact center of cells.
      
      When a cell is hit, the end point of the line drawn between that cell
      and the previous is adjusted with an animation from the hit coordinate
      and the exact center of the cell.
      
      With LockPatternView_keepDotActivated set to true, cell animations for
      the previous cell are recreated when a new cell is hit to allow changing
      how a cells color is updated as the pattern is drawn.
      
      This caused a glitch where the starting position of the end point
      correcting animation for said previous cell would be recreated with the
      current finger position coordinate, making it jump ahead to be closer to
      the current latest cell, and animating back towards the target.
      
      This fix makes the animation instead continue from where it was last, in
      the case where the animation is recreated.
      
      Test: manual, set a short, tight lock pattern, and try it in rapid
      motion.
      Bug: 328088937
      
      Change-Id: Id445266cbc834fec7a514dbb227557f2ceae9dba
      52098a13
    • Rongxuan Liu's avatar
      Merge changes from topic "cherrypicker-L83000030003604164:N29900030057840634" into main · e933e38c
      Rongxuan Liu authored
      * changes:
        [Audiosharing] Fix address type usage in  QR code format if address not present
        [Audiosharing] Update QR code format to follow BT SIG standard
      e933e38c
    • Rongxuan Liu's avatar
      [Audiosharing] Fix address type usage in QR code format if address not present · e4aaa19f
      Rongxuan Liu authored
      Bug: 327599769
      Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
      (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6428ed9fb9f9f1873dede7963d86c3913522ab8d)
      Merged-In: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed
      Change-Id: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed
      
      NOTE FOR REVIEWERS - errors occurred while applying the patch.
      PLEASE REVIEW CAREFULLY.
      Errors:
      Error applying patch in packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothLeBroadcastMetadataExt.kt, hunk HunkHeader[311,7->311,7]: Hunk cannot be applied
      
      Original patch:
       From 6428ed9f Mon Sep 17 00:00:00 2001
      From: Rongxuan Liu <rongxuan@google.com>
      Date: Wed, 06 Mar 2024 03:14:00 +0000
      Subject: [PATCH] [Audiosharing] Fix address type usage in  QR code format if address not present
      
      Bug: 327599769
      Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
      Change-Id: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed
      ---
      e4aaa19f
    • Rongxuan Liu's avatar
      [Audiosharing] Update QR code format to follow BT SIG standard · 8cc1ff3c
      Rongxuan Liu authored
      Bug: 324655158
      Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
      Test: manually tested with broadcast source and assistant by QR code
      (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4abfa5bed1a35a9a9b5ac54951296b3edde4ee9a)
      Merged-In: I798666b89c4e3558c7528bace0346caf8218dc53
      Change-Id: I798666b89c4e3558c7528bace0346caf8218dc53
      8cc1ff3c
    • Treehugger Robot's avatar
  6. May 04, 2024
Loading