Status Update
Comments
ap...@google.com <ap...@google.com> #2
ap...@google.com <ap...@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.
ap...@google.com <ap...@google.com> #5
ap...@google.com <ap...@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.
ap...@google.com <ap...@google.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.
ap...@google.com <ap...@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)
co...@google.com <co...@google.com>
pr...@google.com <pr...@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?
Description
What's your ask from the WebView team (implement an existing WP API, add a new developer API functionality, add a new JS API functionality, change the UX behaviour of a WebView):
Implement a new developer API to allow calling apps to tag the traffic and attribute it to other apps with TrafficStats. If it is easier, at least in the short term, it would be ok to just tag all of WebView traffic with one tag, value of which needs to be carefully chosen, and probably baked in the platform. In the long term I anticipate that we will still need to have the proper APIs.