Status Update
Comments
ag...@google.com <ag...@google.com>
bo...@google.com <bo...@google.com>
bo...@google.com <bo...@google.com> #2
Branch: androidx-master-dev
commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date: Wed Sep 18 16:55:49 2019
Change the way to detect mismatch between POJO and query
This fixes cursor mismatch warnings with expandProjection.
Bug: 140759491
Test: QueryMethodProcessorTest
Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt
bo...@google.com <bo...@google.com> #3
se...@gmail.com <se...@gmail.com> #4
Branch: androidx-master-dev
commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date: Thu Apr 16 16:47:05 2020
Re-factor how errors are dismissed when query is re-written
This CL changes how we handle errors/warnings if query is
re-written.
There was a bug in expandProjection where we would report warnings
for things that Room already fixes automatically (
The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
solved it by deferring validating of columns until after re-write
decision is made. Unfortunately, this required changing PojoRowAdapter
to have a dummy mapping until it is validating, make it hard to use
as it does have a non-null mapping which is not useful.
This CL partially reverts that change and instead rely on the log
deferring logic we have in Context. This way, we don't need to break
the stability of PojoRowAdapter while still having the ability to
drop warnings that room fixes. This will also play nicer when we
have different query re-writing options that can use more information
about the query results.
Bug: 153387066
Bug: 140759491
Test: existing tests pass
Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f
M room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
bo...@google.com <bo...@google.com> #5
that video is very helpful, and it is webcam ? how about emulated camera?
have you tried to use standalone version of emulator ?
also Koala canary is out, maybe try that ?
Carlos/Ranjit, could you help with reproducing this ?
bo...@google.com <bo...@google.com> #6
this does happen when the camera is set to webcam0 on mac, and it seems emualted camera is ok
but webcam does slow down the ui interaction quit apparently. we might be dong something strange
in the background, it does not show up in the guest 'top'; I do not see memory pressure is cauing issue
could be related to gralloc ?
please hellp.
rk...@google.com <rk...@google.com> #7
I think this is because we call expensive vImage*
functions in
rk...@google.com <rk...@google.com> #8
I suspect something (on the host side) is still running (and e.g. fighting for locks) even after you close the webcam.
rk...@google.com <rk...@google.com> #9
More details regarding [captureSession startRunning]
, the performance is not affected with time anymore.
rk...@google.com <rk...@google.com> #10
Dave, could you please suggest what we can do here?
dm...@google.com <dm...@google.com> #11
So I tried building using
and initially got:
android/rebuild.sh --gfxstream
-bash: android/rebuild.sh: /bin/sh: bad interpreter: Operation not permitted
which was fixed by clearing the xattr
on android/rebuild.sh
using xattr -c android/rebuild.sh
Then I ran into ninja
isn't available, but as you can see at the bottom of the paste, ninja
is on my PATH
. Any thoughts?
rk...@google.com <rk...@google.com>
ja...@google.com <ja...@google.com> #12
Looks like we implicitly assume ninja is on the path. Let's fix that.
ja...@google.com <ja...@google.com> #14
Ah, the ninja
message is just how cmake reports that things are not right.
It appears that we are unable to find the right sdk:
Running /Users/dmaclach/src/emu-master-dev/external/qemu/android/scripts/unix/gen-android-sdk-toolchain.sh '--host=darwin-aarch64' '/Users/dmaclach/src/emu-master-dev/external/qemu/objs/toolchain' '' '--aosp-dir=/Users/dmaclach/src/emu-master-dev' '--aosp-clang_ver=clang-r487747c' '--verbosity=2'
CMake Error at android/build/cmake/toolchain.cmake:63 (message):
Unable to retrieve sdk info from
/Users/dmaclach/src/emu-master-dev/external/qemu/android/scripts/unix/gen-android-sdk-toolchain.sh
--host=darwin-aarch64
/Users/dmaclach/src/emu-master-dev/external/qemu/objs/toolchain :
Could you try running:
/Users/dmaclach/src/emu-master-dev/external/qemu/android/scripts/unix/gen-android-sdk-toolchain.sh \
'--host=darwin-aarch64' \
'/tmp/toolchain' \
'--aosp-dir=/Users/dmaclach/src/emu-master-dev' \
'--aosp-clang_ver=clang-r487747c' \
'--verbosity=2'
Share what it reports and re-assign the bug to me?
rk...@google.com <rk...@google.com>
tt...@gmail.com <tt...@gmail.com> #15
Everyone facing this issue should try this Android emulator specifically designed for Apple Silicon Macs. On my MacBook Pro M3 running the latest macOS Sonoma, the camera function works perfectly without any freezing or slow performance. In contrast, the Android Studio emulator's camera causes it to stop running.
gi...@gmail.com <gi...@gmail.com> #16
co...@gmail.com <co...@gmail.com> #17
rk...@google.com <rk...@google.com> #18
workarounds
Downgrade your MacOS.
le...@gmail.com <le...@gmail.com> #19
+ Is this issue being worked on actively ? Thanks
Description
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 33.1.24-11237101
HAXM / KVM Version: HVF 14.3.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 14.3.1
CPU Manufacturer: Apple CPU
Virtualization is supported
Bare metal
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint: google/sdk_gphone64_arm64/emu64a:14/UE1A.230829.036.A1/11228894:user/dev-keys
AVD Details: Name: Pixel_API_34
CPU/ABI: arm64
Path: /Users/kaspi/.android/avd/Pixel_API_34.avd
Target: google_apis_playstore [Google Play] (API level 34)
Skin: 1920x1080
SD Card: 2000 MB
AvdId: Pixel_API_34
PlayStore.enabled: true
avd.ini.displayname: Pixel API 34
avd.ini.encoding: UTF-8
disk.dataPartition.size: 20000M
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: yes
fastboot.forceFastBoot: no
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: webcam0
hw.camera.front: webcam0
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a7
hw.device.manufacturer: Google
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: landscape
hw.keyboard: yes
hw.lcd.density: 420
hw.lcd.height: 1920
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSize: 2048
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-34/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: /Users/kaspi/Library/Android/sdk/skins/pixel_silver
tag.display: Google Play
vm.heapSize: 228
Steps to Reproduce Bug:1. Set up the front camera on webcam0
2. Launch the emulator
3. Launch the built-in camera app
4. Switch to the front camera
5. After these actions, the emulator will run very slowly and freeze, even if you close the camera application.
Expected Behavior:
Observed Behavior: