Obsolete
Status Update
No update yet.
Comments
dn...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
sh...@gmail.com
I start the same app three times for each device and `adb bugreport` all the message.
attachment contains start time and bugreport of android O and N
attachment contains start time and bugreport of android O and N
sh...@gmail.com
Assigned to dn...@google.com
dn...@google.com
dn...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
dn...@google.com
@shawn17665080958@gmail.com:
Can you please share application(com.example.uc.uc_first) which you have used to reproduce this issue?
Can you please share application(com.example.uc.uc_first) which you have used to reproduce this issue?
dn...@google.com
sh...@gmail.com
attachment is my application.it is a "Navigation Drawer Activity" created by androidstudio.
dn...@google.com
dn...@google.com
We have deferred this to a future release, but leaving this open for now.
sh...@gmail.com
hi, I want to konw:
Does this release really have this problem ,or just I get mistake.
Does this release really have this problem ,or just I get mistake.
sh...@gmail.com
hi, I want to konw:
Does this release really have this problem ,or just I get mistake. Have you do something about the issue or just defer it.
Does this release really have this problem ,or just I get mistake. Have you do something about the issue or just defer it.
is...@google.com
sa...@google.com
We will be closing this bug due to being logged in a Preview version of Android. If the issue is still relevant and reproducible in the latest public release (Android Q), please capture a bugreport and log the bug in https://goo.gl/TbMiIO . If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.
Description
For comparison,I start the same app on android N and android O.The answer shows the android O will spent more time for starting
I use command `adb shell am start -W com.example.first/com.example.first.MainActivity` to get answers. I test many times on virtual device and get the average value. The answer is below:
app name android level device ThisTime TotalTime waitTime starting type
test android O nexus 5x 350 350 366 hot start
test android N nexus 5x 285 285 291 hot start
test android O nexus 5x 838 838 850 cold start(kill the process and start)
test android N nexus 5x 741 741 752 cold start(kill the process and start)
The time test on piexl device is almost same between android O and N. but android O will spent more time on starting app by testing on other device,including real device.
attachment is my device picture.