Status Update
Comments
ap...@google.com <ap...@google.com> #2
jb...@google.com <jb...@google.com> #3
*School grade hack,
*hack into email accounts,
*all social media accounts,
*school database to clear or change grades,
*Retrieval of lost documents
*DUIs
*company records and systems,
*clearing bad driving and criminal records,
+ credit score hack,
+ Monitor your partners phone,Whatsapp,Facebook.
You should visit us
Phonixhacker41 @gmail. com or via WhatsApp ‪+1 (916) 250‑1771‬
ap...@google.com <ap...@google.com> #4
Rahul, don't know if this is a real issue or a benchmark being coded poorly thing. Passing along due to profileinstaller.
lb...@gmail.com <lb...@gmail.com> #5
jb...@google.com <jb...@google.com> #6
Hi Marcelo, can you please take a look at this when you get a chance ? If not, I can come and take a look when I get back.
lb...@gmail.com <lb...@gmail.com> #7
I'm pretty sure the offending PR here is aosp/2333568 - that is the only PR touching the profile transcoding.
It fixes an important bug with compressed profiles but it seems that the new code is slower than before.
jb...@google.com <jb...@google.com> #8
If you look in the dashboard, the commit link is wrong, since it doesn't encompass all builds since the previous (9385400). Correct build range link is here, which includes Ben's CL:
(If a build goes missing for any reason, it corrupts the commit link. In general, you can always go to dashboard, and create range link like the above)
as...@google.com <as...@google.com> #9
Yes, it looks like my change introduced this regression.
If I read
That would mean the change makes opening the file slower by about 1000 times.
Chris: Given this runs on a background thread and is not blocking app startup, is it urgent to address this or can it wait for the next release cycle?
lb...@gmail.com <lb...@gmail.com> #11
Uploaded aosp/2355662 to address the problem.
as...@google.com <as...@google.com> #12
The CL mentioned in
lb...@gmail.com <lb...@gmail.com> #13
Branch: androidx-main
commit b7fc1b0247a4f4883b37c1998e3f12b4f0c0b7b0
Author: Ben Weiss <benweiss@google.com>
Date: Wed Dec 14 15:49:17 2022
More detailed compressed profile handling
Just replacing openFd with open dramatically decreased the performance
of opening a profile. This new handling goes back to openFd and
introduces a diagnostic code to hint at updating bundletool.
Bug: 261998144
Test: :profileinstaller:profileinstaller:test
RelNote: Add diagnostics for compressed profiles
Change-Id: I8641387ad6073dde588d0d764da4a3b24b1c8ee4
M profileinstaller/profileinstaller/api/current.txt
M profileinstaller/profileinstaller/api/public_plus_experimental_current.txt
M profileinstaller/profileinstaller/api/restricted_current.txt
M profileinstaller/profileinstaller/src/main/java/androidx/profileinstaller/DeviceProfileWriter.java
M profileinstaller/profileinstaller/src/main/java/androidx/profileinstaller/ProfileInstaller.java
as...@google.com <as...@google.com> #14
The landed CL has moved the benchmark down to normal levels again.
lb...@gmail.com <lb...@gmail.com> #15
lb...@gmail.com <lb...@gmail.com> #16
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.profileinstaller:profileinstaller:1.3.0-beta01
lb...@gmail.com <lb...@gmail.com> #17
This is something that was said to use instead of clearing the stack itself:
So you wouldn't want to show the MainFragment there, and instead you'd want to allow to skip directly to the Activity behind, even though MainFragment is in the back-stack of the navigation.
Sadly even there on this documentation, there is no sample and there is a lot of missing code.
Description
API 34 provided a new Predictive Back Gesture that allows seeking when going back and provides a View of the previous Activity.
Now that this feature is available between Activities it would be nice if it was also available between Fragments. Fragments need to handle multiple effects system to get this working and this bug will focus on providing support for Transitions.