Skip to content
Snippets Groups Projects
  1. Dec 15, 2023
  2. Nov 17, 2023
    • Android Build Coastguard Worker's avatar
      [coastguard skipped] Merge sparse cherrypicks from... · e762bf2a
      Android Build Coastguard Worker authored
      [coastguard skipped] Merge sparse cherrypicks from sparse-11084887-L36700030000358185 into udc-qpr1-release.
      
      COASTGUARD_SKIP: Id31878f5943ef7095df8d75cfae6297e58360979
      COASTGUARD_SKIP: Ia40cfacbee6fc174c90db8e3687838ae01e2858b
      
      Change-Id: I03f767328f3bfc08b09f427a3d3d97a6d11591e3
      e762bf2a
    • Android Build Coastguard Worker's avatar
      Merge cherrypicks of ['googleplex-android-review.googlesource.com/25327380']... · 0e8cfe1e
      Android Build Coastguard Worker authored
      Merge cherrypicks of ['googleplex-android-review.googlesource.com/25327380'] into sparse-11084887-L36700030000358185.
      SPARSE_CHANGE: Ia40cfacbee6fc174c90db8e3687838ae01e2858b
      
      Change-Id: Id31878f5943ef7095df8d75cfae6297e58360979
      0e8cfe1e
    • Nikhil Kumar's avatar
      Refactored switchUSer to handle user switch back to the current user · 5dd74cdf
      Nikhil Kumar authored
      The existing implementation of user switching puts subsequent user switches into a queue if there is already a user switch in progress. For example, if the current user is A and there is a user switch sequence to switch to user B and then to user C, the UserController#switchUser method will put the user switch to C into a pending user switch list and perform it once the existing user switch to B is finished.
      
      However, if the sequence is to switch from user A to user B and then back to user A, and when switch to user A reaches the UserController#switchUser method before the switch to user B is completed, the method will think that the current user is A and that there is no need to switch to user A, and will therefore skip that switch.
      
      The refactored code handles this scenario by adding an extra condition which additionally verifies that there are no further switches scheduled in case the target user is equal to the current user and the switch is going to be skipped.
      
      Bug: 303743201
      Test: tested manually with switch user scenario current user is 0 switch to user 10 and then switch back to user 0.
      (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:1e3d4f48ab24593ec401ccbc968efbc0a82fea40)
      Merged-In: Ia40cfacbee6fc174c90db8e3687838ae01e2858b
      Change-Id: Ia40cfacbee6fc174c90db8e3687838ae01e2858b
      5dd74cdf
  3. Nov 16, 2023
  4. Nov 10, 2023
  5. Nov 03, 2023
  6. Nov 02, 2023
  7. Oct 26, 2023
  8. Oct 23, 2023
  9. Oct 20, 2023
Loading