Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. Please upload the AOSP patch following this guidance
mc...@gmail.com <mc...@gmail.com> #3
Change-Id: I9594ce3d2276127d2a585b9c630b672c857bede7
vi...@smartlauncher.net <vi...@smartlauncher.net> #4
vi...@smartlauncher.net <vi...@smartlauncher.net> #5
Regular: Recorded on a Pixel 6a running firmware AP3A.241105.007
Broken: Recorded on a Pixel Fold running firmware AP4A.241205.013
Steps to reproduce:
- Set any third-party launcher as the default launcher.
- Open any app.
- Perform the "home" gesture.
Expected behavior:
The transition animation should play smoothly when returning to the home screen.
Actual behavior:
On devices running firmware released after December 2024, the home gesture animation is skipped entirely (as shown in the "Broken" video).
This issue is consistent and requires no additional steps to reproduce.
ma...@gmail.com <ma...@gmail.com> #6
I'm confused as to why this ticket is marked as a duplicate. While the linked issue also related to gesture navigation, it still covers different behavior:
The seemingly duplicate issue is about a touch delay when returning home. Specifically, the user cannot interact with the 3rd-party launcher for a moment after triggering the home gesture.
This issue, however, is about missing animations. While the launcher is immediately ready for interaction, the return animation that should usually play in the launcher, including 3rd-party launchers if they implement the GestureNavigationContract, doesn't play anymore since the December 2024 Google Pixel security update. Please refer to my original report and the added comments and videos by #5. Thus, I ask you to please reopen this issue (and preferably fix it as soon as possible).
gi...@gmail.com <gi...@gmail.com> #7
If this was a mistake, please fix it as soon as possible. This issue affects everyone using our products and creates a competitive disadvantage for third-party launchers.
If it wasn’t a mistake, we believe better communication would help. Why was it marked as a duplicate?
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #8
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ma...@gmail.com <ma...@gmail.com> #9
We finally received the January update on our testing device. Unfortunately, while the behavior changed slightly, the issue is still present on AP4A.250105.002. I attached an updated screen recording and the requested bug report.
Description
Since the recent Android 15 December patch on Pixel devices, the animation that plays when returning to the launcher from an app (that's present on the home screen) is broken.
Please refer to the attached screen recording for an example. Niagara Launcher implements the GestureNavContract API, which usually allows the launcher to animate from the opened app to the home screen when using gesture navigation. The animation normally gradually shrinks the opened app into a circle-like shape and transforms it into the app icon, which is then animated to the correct location on the home screen. As of the recent update, this animation doesn't work when using third-party launchers, only the start and the end state are displayed, and no animation is shown in between. There's also a noticeable glitching/lag, as visible in the screen recording.
The attached screen recording was taken on a Pixel 8 with the December patch applied, the build number is BP11.241121.010. Furthermore, multiple reports from the community also reached us, and we received feedback from other launcher developers that the same API is also broken for them. Thus, we're confident that this is a framework issue, and not caused by our launcher implementation.
Note that a very similar issue also applies to Android 16 DP2, however, I can't confirm whether it has the same underlying cause.
Please let us know if you need any additional details on how to reproduce this bug.