WAI
Status Update
No update yet.
Comments
co...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
From the provided description it seems you are reporting this bug from an end user's perspective. Kindly confirm the same.
Could you please share a bugreport.
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
From the provided description it seems you are reporting this bug from an end user's perspective. Kindly confirm the same.
Could you please share a bugreport.
jo...@gmail.com
The devices I have experienced this on are:
Samsung Galaxy S22+
Android 13
Build number TP1A.220624.014.S906USQ2BWA2
Hisense 65U6H TV with Google TV
Android 11
Build number RTT2.220118.001
I understand you are primarily looking for Pixel or AOSP specific bugs, but the problems are discussed affecting multiple Android products and if the problem is with the firmware update to the controller, I'd like to at least draw attention to it in hopes it reaches the correct people to address.
Yes, I am reporting from an end user's perspective.
I had tried to include a bug report numerous times prior to submitting this issue, but my phone would not generate it. I never received a notification that it had been generated. I will continue to try and attach it.
Samsung Galaxy S22+
Android 13
Build number TP1A.220624.014.S906USQ2BWA2
Hisense 65U6H TV with Google TV
Android 11
Build number RTT2.220118.001
I understand you are primarily looking for Pixel or AOSP specific bugs, but the problems are discussed affecting multiple Android products and if the problem is with the firmware update to the controller, I'd like to at least draw attention to it in hopes it reaches the correct people to address.
Yes, I am reporting from an end user's perspective.
I had tried to include a bug report numerous times prior to submitting this issue, but my phone would not generate it. I never received a notification that it had been generated. I will continue to try and attach it.
co...@google.com
Bug report attached
co...@google.com
It looks like you are raising this request as an Android user, rather than an Android Open Source Developer. Our Android Support team will be in contact with you shortly.
In the meantime, here are helpful resources:
jo...@gmail.com
Please visit the Stadia community forum where Product Experts may be able to assist you further: https://community.stadia.com/t5/Community/ct-p/en_community . We are marking this public bug status as "Duplicate" as it will be duplicative of the feedback you provide via the suggested channel. We will no longer provide responses or updates on this bug, but rather will investigate further based on the feedback you submit.
co...@google.com
I appreciate looking into this. Stadia is completely shut down. From my understanding, they will no longer provide support. Thus why I looked for help here.
jo...@gmail.com
The Stadia forums have been locked in read-only mode die to the shutting down of the Stadia service also. This is a widespread problem which I hope Google will fix for all former-Stadia clients.
Description
Setting the style of a TextInputLayout to R.style.Widget_MaterialComponents_TextInputLayout_OutlinedBox_Dense using ContextThemeWrapper fails to produce the same results as setting the style via XML.
Expected behavior:
Setting the style programmatically should function the same as through the style attribute.
Source code:
val contextThemeWrapper = ContextThemeWrapper(
context
, R.style.Widget_MaterialComponents_TextInputLayout_OutlinedBox_Dense
)
TextInputLayout(contextThemeWrapper).apply {
hint = "Example"
addView(TextInputEditText(contextThemeWrapper))
}
Design Library Version: 1.0.0
Android API version: 27
Device: OnePlus5