Status Update
No update yet.
Comments
fa...@gmail.com
Having a recurrence of the issue with none of the databinding abstract base classes being found. It's again consistent across several consecutive clean + rebuild cycles. I've dumped a complete file listing from the app/build folder to look at and after filtering down to files matching a specific binding name here's what exists:
app/build/generated/data_binding_base_class_source_out/debug/out/com/example/myapp/databinding/MyBinding.java
app/build/generated/source/kapt/debug/com/example/myapp/databinding/MyBindingImpl.java
app/build/intermediates/javac/debug/classes/com/example/myapp/databinding/MyBinding.class
app/build/intermediates/javac/debug/classes/com/example/myapp/databinding/MyBindingImpl.class
app/build/intermediates/project_dex_archive/debug/out/com/example/myapp/databinding/MyBinding.dex
app/build/intermediates/project_dex_archive/debug/out/com/example/myapp/databinding/MyBindingImpl.dex
It looks like the base Binding.java files are actually getting generated but in a completely separate directory from the implementations. It seems Android Studio is not currently including the data_binding_base_class_source_out directory as a generated source location (nothing in there shows up under java (generated) in the Android Studio project view).
Without removing any of the generated files or changing any code I've now forced a gradle sync with an editor window open on the source for a fragment with references to a binding class. The fragment source immediately went from full of errors about the missing binding class back to completely normal. None of the generated files listed above have moved. The bases still don't appear listed under java (generated) in the android studio project view. Opening one of the generated binding implementations in an editor window marks several errors stemming from Cannot inherit from final 'com.example.myapp.databinding.MyBinding'.
Still not sure how to actually reproduce this state in the first place. Manually forcing gradle sync seems like a quick and easy workaround at least. Is this a bug or misconfiguration somewhere on my end?
fa...@gmail.com
Can you attach your IDEA.log? I've exceptions get thrown that screw up the timing and cause this to happen. Thanks!
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? User Interface, Display, or Rendering issue
When did this happen?
Apr 12, 2023 7:25 AM GMT+02:00
What steps would let us observe this issue?
1. Turn off the screen
2. Wait around 5 seconds
3. Tap the screen
What did you expect to happen?
The display should turn fully on
What actually happened?
The device shows no signs of waking up, and keeps showing the always on interface.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Moderate
Additional comments
Picking up the device still works, and wakes the device.
Pressing the power button correctly works.
Settings that might be relevant:
I changed the "DPI setting" to a higher value (always done that);
although I have the "Force peak refresh rate" option inactive, the device seems to stay at 90hz.
I set up the Android Screen Saver (clock) although that doesn't work.
Debugging information
Google Play services
com.google.android.gms
Version 231354044 (23.13.54 (190400-520938292))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567202444 (113.0.5672.24)
System App (Updated)
Network operator: VERY
SIM operator: VERY
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit