Verified
Status Update
No update yet.
Comments
nu...@gmail.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 9fe209b0b6489fc3eba5be3c646beaf0efe8ed7e
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Aug 25 11:55:49 2020
Remove observers when unregistering ActivityResult
Currently, if you register an ActivityResult using a LifecycleOwner and
then go through process death, we add an Observer to fire the registered
callback once the lifecycle goes to STARTED. In the case of
unregistering, we should make sure to remove any observers that may have
been added.
Test: Added ActivityResultRegistryTest#testLifecycleOwnerCallbackUnregistered
Bug: 165608393
Change-Id: If81142b1a6abc72b105986a2460e4aeb96e29eaf
M activity/activity/src/androidTest/java/androidx/activity/result/ActivityResultRegistryTest.kt
M activity/activity/src/main/java/androidx/activity/result/ActivityResultRegistry.java
https://android-review.googlesource.com/1410730
Branch: androidx-master-dev
commit 9fe209b0b6489fc3eba5be3c646beaf0efe8ed7e
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Aug 25 11:55:49 2020
Remove observers when unregistering ActivityResult
Currently, if you register an ActivityResult using a LifecycleOwner and
then go through process death, we add an Observer to fire the registered
callback once the lifecycle goes to STARTED. In the case of
unregistering, we should make sure to remove any observers that may have
been added.
Test: Added ActivityResultRegistryTest#testLifecycleOwnerCallbackUnregistered
Bug: 165608393
Change-Id: If81142b1a6abc72b105986a2460e4aeb96e29eaf
M activity/activity/src/androidTest/java/androidx/activity/result/ActivityResultRegistryTest.kt
M activity/activity/src/main/java/androidx/activity/result/ActivityResultRegistry.java
r....@gmail.com
This has been fixed internally and will be available in the next release of Fragments.
ha...@google.com
bo...@google.com
ya...@google.com
Hi,
would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?
would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?
nu...@gmail.com
Hi,
I'm currently not able to change this option, it is greyed out.
I'm currently not able to change this option, it is greyed out.
ya...@google.com
Hi,
there are 2 ways to set it:
1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:
hw.gpu.enabled=yes
hw.gpu.mode=host
there are 2 ways to set it:
1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:
hw.gpu.enabled=yes
hw.gpu.mode=host
nu...@gmail.com
Hi,
Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).
Will this option be enabled "out of the box" in a future version?
Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).
Will this option be enabled "out of the box" in a future version?
ya...@google.com
Hi,
we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.
we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.
ya...@google.com
Hi Devki,
would you help to cp aosp/2451107 to next stable and canary releases? Thank you!
would you help to cp aosp/2451107 to next stable and canary releases? Thank you!
de...@google.com
ya...@google.com
Hi Devki,
Could we cherry-pick it to canary release as well? Thanks!
Could we cherry-pick it to canary release as well? Thanks!
de...@google.com
@yahan it will be picked up in the next canary since we are doing snaps!
ya...@google.com
Thanks!
is...@motorolasolutions.com
Was able to force the emulator to use the host GPU by opening it via the terminal with
./emulator -avd Resizable_API_33 -gpu host
cs...@google.com
I believe this is still happening in 33.1.10
ya...@google.com
Chris, would you help to send us the verbose log?
cs...@google.com
User on
bo...@google.com
do you still have this problem with latest 33.1.20+ ?
cs...@google.com
nu...@gmail.com
If that question is for me, I've tested changing the config.ini back to "hw.gpu.mode=auto" and it appears to be fine. I have 33.1.2.0.
bo...@google.com
with 34.1.x stable already, are there still any performance degradation ?
let us know
let us know
nu...@gmail.com
Can confirm the flag is correctly set for new emulators on 34.1.18
Description
After updating to Emulator v33.1.1 and SDK Platform Tools 34.0.0, emulator performance took a big hit.
It was working ok on previous version, with Apple M1 chip.
I've tried creating a new emulator, but it's a general issue.
Could you give me instructions on how to downgrade to previous version?
```
Build: AI-223.8214.52.2231.9601041, 202302132341,
AI-223.8214.52.2231.9601041, JRE 17.0.6+0-17.0.6b802.4-9586694x64 JetBrains s.r.o., OS Mac OS X(aarch64) v13.2.1, screens 3456.0x2234.0, 3840.0x2160.0; Retina
AS: Giraffe | 2022.3.1 Canary 5
Kotlin plugin: 223-1.7.21-AS7571.182
Android Gradle Plugin: 7.4.1
Gradle: 8.0
Gradle JDK: JetBrains Runtime version 17.0.6
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Source: send_feedback_icon
IMPORTANT: Please read
```