IssueTracker

Thanks! Over to Nader to take a detailed look!

I believe we should dup b/187839528 and this ticket, what do you think Nader?

Yes definitely. Thanks Siyamed!

In the meantime there maybe other ways to work around it. The main issue is that surface implicitly creates a seaprate layer which impacts the behavior of the blending modes. Being ale to just set the Brush on the paint directly would work around this in the most straightforward way.

The issue is that the content depends on transparent pixels existing in the scene before the gradient is applied.

To address this you can do the following in order to force rasterization of the graphicsLayer into a separate buffer using CompositingStrategy.Offscreen, then only draw the gradient on top of the pixels rendered by the text Composable.

       Text("Hello World!", modifier =
        // Use offscreen compositing strategy so that there are transparent pixels in the offscreen buffer
        // to blend against with the SrcIn blend mode
            Modifier.graphicsLayer(compositingStrategy = CompositingStrategy.Offscreen).drawWithCache {
                val brush = Brush.horizontalGradient(listOf(Color.Red, Color.Blue, Color.Cyan, Color.Magenta, Color.Green))
                onDrawWithContent {
                    drawContent()
                    drawRect(brush, blendMode = BlendMode.SrcIn)
                }
            }
        )

my devices are available from the picker

but it looks like profiler doesn't work on them either.. so it's not just the inspector at this point

this part makes me particularly sad:

so essentially all relevant tools no longer work on this userdebug device, despite it running relatively recent android version (11 is not that old and we have to support it)

in case this bug is linked to Android R being too old, here is the same exact problem with Android V / 15:

ADB is working. ADB was started by the Android Studio, so I assume it is using the correct version. Yet - won't budge. This Pixel Tablet is also running a userdebug build.

API level is not the issue - we support Android 11.

Inspectors and profilers share the same infrastructure, so it makes sense that both have the same problem. I will get a device and flash it with a userdebug build, hopefully I can replicate.

I have tried on a lynx-userdebug 14. Everything works for me. Can you try with an emulator? I suspect it will work there.

I see this exception in the logs, which indicates that ddmlib is failing to copy the transport to the device. I am still not sure why.

2024-11-01 12:38:13,726 [  23834]   INFO - #com.android.tools.idea.transport.TransportFileManager - Pushing transport to /data/local/tmp/perfd/...
2024-11-01 12:38:14,073 [  24181]   WARN - #com.android.ddmlib - transfer error: couldn't create file: Permission denied
2024-11-01 12:38:14,073 [  24181]   WARN - #com.android.ddmlib - Error during Sync: couldn't create file: Permission denied
2024-11-01 12:38:14,073 [  24181]   WARN - #com.android.tools.idea.transport.TransportDeviceManager - Error when trying to spawn Transport
java.lang.RuntimeException: com.android.ddmlib.SyncException: couldn't create file: Permission denied
	at com.android.tools.idea.transport.TransportFileManager.pushFileToDevice(TransportFileManager.java:331)
	at com.android.tools.idea.transport.TransportFileManager.copyFileToDevice(TransportFileManager.java:269)
	at com.android.tools.idea.transport.TransportFileManager.copyFilesToDevice(TransportFileManager.java:137)
	at com.android.tools.idea.transport.TransportDeviceManager$TransportThread.run(TransportDeviceManager.java:255)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.android.ddmlib.SyncException: couldn't create file: Permission denied
	at com.android.ddmlib.SyncService.doPushFile(SyncService.java:752)
	at com.android.ddmlib.SyncService.pushFile(SyncService.java:442)
	at com.android.ddmlib.internal.DeviceImpl.lambda$pushFile$28(DeviceImpl.java:1338)
	at com.android.ddmlib.internal.DeviceImpl.logRun4(DeviceImpl.java:1849)
	at com.android.ddmlib.internal.DeviceImpl.pushFile(DeviceImpl.java:1320)
	at com.android.tools.idea.transport.TransportFileManager.pushFileToDevice(TransportFileManager.java:305)

(please disregard this comment, seems i've ran out of disk space)

edit: in the log i saw i am short on disk space (sigh).. let me clear up some space and try again.

in the log i saw i am short on disk space (sigh).. let me clear up some space and try again

Yes I was about to suggest this, would explain why the emulator doesn't start.

A few things to try on your physical devices:

1. adb push yourfile.txt /data/local/tmp/perfd, does this work?
2. Does running adb root make any difference? (if testing in Studio, it will require a restart after running the command)
3. How about adb shell setenforce 0? (this disables SELinux, so you might want to re-enable it after with adb shell setenforce 1)

1. yes, it does - in every case, including the virtual device

% adb -d push args.gn /data/local/tmp/perfd
args.gn: 1 file pushed, 0 skipped. 0.1 MB/s (53 bytes in 0.000s)
% adb -e push args.gn /data/local/tmp/perfd
args.gn: 1 file pushed, 0 skipped. 0.1 MB/s (53 bytes in 0.001s)

2. YES that seems to have done the trick THANK YOU! However, I can't run the adb root on emulator as all arm64 images i see appear to be production builds:

% adb root
adbd cannot run as root in production builds

3. that wouldn't - and doesn't work on the non-userdebug devices (for the right reasons). so adb root was the answer for physical devices - emulated ones don't work - unless i deploy an AOSP image, which does not include play services (needed by Chrome - at least by Chrome Search that I work on, as this work requires me to sign in with Google).

Question

are there images i can use with AS that include play services and are rooted? does ASwB include these maybe?

A newly created emulator (play services or not) should run the inspectors without issues, as long as the app is debuggable. In your case the emulator is not even detected.

Could you send the logs from the emulator too? although I expect to see the same issue from before.

To make sure, you don't have multiple versions of Studio running right? or Intellij with the Android Plugin.

sure - i've attached them.

things are far worse since yesterday, when the emulator images booted up to some usable UI. today, these images boot up to a white screen and are completely useless.

the only thing that changed since yesterday is that i work from the office.

i went as far as removing AndroidStudio completely, and deleting the entire ~/Library/Android folder, but that didn't change anything. the sad thing is that i am unable to get any work done, as i've left my physical devices at home (seeing that the emulator images did boot up yesterday)...