IssueTracker

Project: platform/frameworks/support
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

https://android-review.googlesource.com/1123258
https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

  The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/)
  Release Track: (https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
  Created: 2019-10-14 17:23:42.610596+00:00
  Changes: aosp/1123258
 

Project: platform/frameworks/support
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 (b/140759491).
    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

https://android-review.googlesource.com/1288456

Thank you for the above, this fixed a long-standing problem for me!

For those coming after, you get to this setting when you start up the emulator, even though it's not starting up normally, click on the three dots on the toolbar to the side of the emulator window, click Settings, then on the right side you'll see Advanced at the top. That's where to choose autoselect as in above screenshot.

Checked with the latest Android Studio, gpu auto should be the default option.

Also, cannot repro the issue with any gpu settings. If anyone could repro it, please run the emulator from command line:

/path/to/emulator -avd [your_avd_name] -feature GLESDynamicVersion -verbose

and upload the logs here. I will close the issue for now, and will reopen if there would be more reports or logs.

I just updated to the current emulator release. The issue still reproduces for me if I set the renderer to "Desktop native OpenGL" and API level to "Compatibility" (but not if I leave both on auto).

I have attached the output from ~/Files/Android/sdk/emulator/emulator -avd Pixel_4a_API_33 -feature GLESDynamicVersion -verbose 2>&1

Tested just now using Android emulator version 32.1.12.0 (build_id 9751036) on a MacBook Pro 14" with M1 Pro CPU.
Launching a Pixel 4a AVD using API 33.
surfaceflinger (inside the AVD) still crashes if I set the renderer to "Desktop native OpenGL" and API level to "Compatibility".
Everything still works just fine if I set both settings to auto.
So, no change from 2 Feb, when I last reported that setting both things to auto fixed this.

For me, using emulator 32.1.13, API 33 is starting OK with auto OpenGL ES Renderer. But on any API < 32, I have to select SwiftShader, or I only get a black screen.

I have tested just now using Android emulator version 32.1.13.0 (build_id 10086546) on a MacBook Pro 14" with M1 Pro CPU.
Launching a Pixel 4a AVD using API 33 (revision 12).

I tried all combinations of Desktop/Swiftshader + Compatibility/Max. Only Desktop + Compatibility results in surfaceflinger crashing. I included the other logs as well in case they prove useful.

I noticed on the crashing one that surface flinger crashed just after the line "SurfaceFlinger: Enter boot animation" in logcat so I trimmed the other logcats shortly after that line (since they were otherwise over 2.5M).

Hopefully something in there helps...

This issue not reproducing in Emulator version: 32.1.14-10330179

Re #16,

it looks like a different bug. Would you file a new issue with all the emulator console output attached? Thanks