Status Update
Comments
ki...@gmail.com <ki...@gmail.com> #2
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.
rh...@google.com <rh...@google.com> #3
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.
ki...@gmail.com <ki...@gmail.com> #4
rh...@google.com <rh...@google.com> #5
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:
ms...@gmail.com <ms...@gmail.com> #6
ro...@gmail.com <ro...@gmail.com> #7
as...@gmail.com <as...@gmail.com> #8
as...@gmail.com <as...@gmail.com> #9
That aside, as they said, many, many, people in the community are very happy to get this bluetooth update, but there is definitely a connection issue, I'm on a Moto G Stylus (nearly stock android) on Android 11 and similarly also have the issue, apparently it's also happening on other platforms as well, but something is wrong there and it is still a Google thing.
One thing I will add however, is that on Android if you go into the device's bluetooth settings and toggle it's Input permission off and on, it will suddenly start working again. Also, the issue you marked as a duplicate above doesn't seem to be open as far into the public as this post is, I can't read it and I doubt the original reporter of this issue can either.
ja...@gmail.com <ja...@gmail.com> #10
am...@gmail.com <am...@gmail.com> #11
co...@gmail.com <co...@gmail.com> #12
mi...@gmail.com <mi...@gmail.com> #13
dw...@gmail.com <dw...@gmail.com> #14
ma...@gmail.com <ma...@gmail.com> #15
It pairs and works fine, but then next time I want to use it, I need to remove it and pair again.
ss...@gmail.com <ss...@gmail.com> #16
wh...@gmail.com <wh...@gmail.com> #17
Here is what worked for me:
* forget all Stadia controller in BT settings
* (Re-)Pair stadia controller (make sure that it works fine)
* Restart CCwGTV through settings. Do not turn off the controller. (check that everything works after restart)
* Restart CCwGTV once again. While CC is restarting, power off and power on the controller. (check that everything works)
* Now power off then power on the controller while keeping CC on.
Once those actions are performed, CC should not lose Stadia controller anymore.
Source:
ki...@gmail.com <ki...@gmail.com> #18
ro...@gmail.com <ro...@gmail.com> #19
ki...@gmail.com <ki...@gmail.com> #20
ki...@gmail.com <ki...@gmail.com> #21
vi...@gmail.com <vi...@gmail.com> #22
This is producing an enormous e waste problem.
Countless controllers going to waste.
A really poor Bluetooth implementation.
Shame on Google.
ki...@gmail.com <ki...@gmail.com> #23
On Mon, Sep 30, 2024, 7:07 PM <buganizer-system@google.com> wrote:
be...@showhow.co <be...@showhow.co> #24
ki...@gmail.com <ki...@gmail.com> #25
When I pair the stadia controller to my LG TV, all works fine until controller is powered off and on again, then the controller connects to my TV but pressing any button on the controller, freezes all inout on the TV (including remote control)
I strongly suspect there some general BT compability issue with the current Stadia Bluetooth firmware, it would be very nice if Google could get this resolved before they stop supporting updates.
th...@gmail.com <th...@gmail.com> #26
Issue my TV shows is super irritating, and it seems to be somewhat persistant, re-paring does not fix the issue. (Seems something is remembered on one of the ends)
ki...@gmail.com <ki...@gmail.com> #27
ki...@gmail.com <ki...@gmail.com> #28
ki...@gmail.com <ki...@gmail.com> #29
Tbh I'm waiting fix since the first beta came out
ki...@gmail.com <ki...@gmail.com> #30
sa...@google.com <sa...@google.com>
vi...@google.com <vi...@google.com> #31
Please check for this issue on the latest beta build and share the new bugreport, If the issue persists.
Android bug report (to be captured immediately after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen Record of the Issue by enabling show taps
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
ki...@gmail.com <ki...@gmail.com> #32
ki...@gmail.com <ki...@gmail.com> #33
be...@gmail.com <be...@gmail.com> #34
Issue seems to appear when embedded videos are on auto play in a web application.
Got this in Chrome when I'm on Facebook and some ad/video is automatically played - suddenly Chrome feels extreme laggy.
When I restart Chrome it is fixed sometimes but not always - in the worst case the complete UI stays laggy even when Chrome is closed.
In that case only a complete reboot of the phone will help which is super annoying - never had that issue with Android < 14
TBH: I think the issue appears more likely with a higher system runtime (~2-3 days)
ki...@gmail.com <ki...@gmail.com> #35
in the worst case the complete UI stays laggy even when Chrome is closed. In that case only a complete reboot of the phone will help which is super annoying
For me playing some video in another app fixes the lags in whole system UI
be...@gmail.com <be...@gmail.com> #36
Since you already have a lot of videos and bug reports I tried to find a video which you can use to reproduce the issue. I found one where I can easily force the lag just by start/stop and scrolling up/down a few times.
I don't know what's the issue with that video but it happens more frequently in this - its a simple facebook video from a NFL pre game interview scene. Most likely the framerate / bad quality?!
PS: I dont know if I'm allowed to post links to Facebook here- if not please just delete.
ki...@gmail.com <ki...@gmail.com> #37
ro...@gmail.com <ro...@gmail.com> #38
I also have this issue on my Android 14 (not pixel) device.
The issue appears every time a 30fps video is on screen: the full UI is then rendered at 30fps. It can be the case watching a youtube video, or scrolling some apps with 30fps video previews.
In the log:
I DisplayDeviceRepository: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1080 x 1920, modeId 1, renderFrameRate 30.000002, defaultModeId 1, supportedModes [{id=1, width=1080, height=1920, fps=60.000004, alternativeRefreshRates=[], supportedHdrTypes=[2, 3]}], colorMode 0, supportedColorModes [0], hdrCapabilities HdrCapabilities{mSupportedHdrTypes=[2, 3], mMaxLuminance=500.0, mMaxAverageLuminance=500.0, mMinLuminance=0.0}, allmSupported false, gameContentTypeSupported false, density 420, 403.411 x 399.737 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type INTERNAL, address {port=0}, deviceProductInfo DeviceProductInfo{name=, manufacturerPnpId=, productId=, modelYear=0, manufactureDate=null, connectionToSinkType=0}, state ON, committedState ON, frameRateOverride {uid=10125 frameRateHz=30.000002} , brightnessMinimum 0.0, brightnessMaximum 1.0, brightnessDefault 0.39763778, hdrSdrRatio NaN, FLAG_ALLOWED_TO_BE_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, FLAG_TRUSTED, installOrientation 0, displayShape DisplayShape{ spec=1673867177 displayWidth=1080 displayHeight=1920 physicalPixelDisplaySizeRatio=1.0 rotation=0 offsetX=0 offsetY=0 scale=1.0}}
Note the 'renderFrameRate 30'
This was not the case with Android 13.
ki...@gmail.com <ki...@gmail.com> #39
be...@gmail.com <be...@gmail.com> #40
ro...@gmail.com <ro...@gmail.com> #41
Daily up.
ki...@gmail.com <ki...@gmail.com> #42
Some info which can be helpful:
- UI becomes more laggy with lesser video frame rate: you can see this on first (video is 15fps) and second (video is 20fps) screen records
- Some of 30fps videos causes UI lags only for the first 5 seconds (see screen record 3, after playing UI lags for about 2 seconds and then becomes normal)
- Some 30fps always causes UI lags (see screen record 4, it's not very noticeable on screen record, but actually UI feels too unsmooth)
al...@gmail.com <al...@gmail.com> #43
ki...@gmail.com <ki...@gmail.com> #44
ro...@gmail.com <ro...@gmail.com> #45
Adaptive refresh rate on Pixel was present also on Android 13, wasn't it?
ro...@gmail.com <ro...@gmail.com> #46
Up!
ki...@gmail.com <ki...@gmail.com> #47
br...@gmail.com <br...@gmail.com> #48
an...@gmail.com <an...@gmail.com> #49
be...@gmail.com <be...@gmail.com> #50
We are not your beta testers and you get our help for free so please get into it.
so...@gmail.com <so...@gmail.com> #51
ki...@gmail.com <ki...@gmail.com> #52
ro...@gmail.com <ro...@gmail.com> #53
Up!
wo...@hotmail.com <wo...@hotmail.com> #54
mt...@gmail.com <mt...@gmail.com> #55
- YouTube comments lag to 24~30FPS only when a video is playing
- The entire screen lags to 60Hz from 120Hz when a YouTube pop out player is going
- Discord chats lag to 24~30FPS whenever a GIF autoplays
- Telegram and Twitter are somehow fine
How did nobody at Google think to maybe not run the optimization when a finger is on the screen?? I know Samsung does this because I've seen mobile game devs complain that FPS tanks unless the screen is touched lol
ru...@gmail.com <ru...@gmail.com> #56
ak...@gmail.com <ak...@gmail.com> #57
Yesterday I noticed this in Google photos as well. When I play a video on Photos app the whole system will start to stutter, like quick settings, notification panel and all start stuttering.
vi...@gmail.com <vi...@gmail.com> #58
ki...@gmail.com <ki...@gmail.com>
ki...@gmail.com <ki...@gmail.com> #59
ps...@gmail.com <ps...@gmail.com> #60
ha...@gmail.com <ha...@gmail.com> #61
ki...@gmail.com <ki...@gmail.com> #62
ki...@gmail.com <ki...@gmail.com> #63
ro...@gmail.com <ro...@gmail.com> #64
Up
ki...@gmail.com <ki...@gmail.com> #65
do...@gmail.com <do...@gmail.com> #66
ki...@gmail.com <ki...@gmail.com> #67
ki...@gmail.com <ki...@gmail.com> #68
ki...@gmail.com <ki...@gmail.com> #69
lo...@gmail.com <lo...@gmail.com> #70
ki...@gmail.com <ki...@gmail.com> #71
ki...@gmail.com <ki...@gmail.com> #72
ki...@gmail.com <ki...@gmail.com> #73
ki...@gmail.com <ki...@gmail.com> #74
ki...@gmail.com <ki...@gmail.com> #75
ki...@gmail.com <ki...@gmail.com> #76
ki...@gmail.com <ki...@gmail.com> #77
ki...@gmail.com <ki...@gmail.com> #78
ki...@gmail.com <ki...@gmail.com> #79
do...@gmail.com <do...@gmail.com> #80
ha...@gmail.com <ha...@gmail.com> #81
fe...@gmail.com <fe...@gmail.com> #83
be...@gmail.com <be...@gmail.com> #84
br...@gmail.com <br...@gmail.com> #85
ha...@gmail.com <ha...@gmail.com> #86
ja...@gmail.com <ja...@gmail.com> #87
ni...@gmail.com <ni...@gmail.com> #88
Pixel 4a 5G
Still issue
be...@gmail.com <be...@gmail.com> #89
I was really hopeful and surprised to get an update after all - but unfortunatly its a kind of a bummer.
mo...@gmail.com <mo...@gmail.com> #90
cn...@gmail.com <cn...@gmail.com> #91
ki...@gmail.com <ki...@gmail.com> #92
sh...@gmail.com <sh...@gmail.com> #93
ha...@gmail.com <ha...@gmail.com> #94
li...@gmail.com <li...@gmail.com> #95
to...@gmail.com <to...@gmail.com> #96
sh...@gmail.com <sh...@gmail.com> #97
to...@gmail.com <to...@gmail.com> #98
I can't believe this hasn't been fixed yet. No more google phones for me lmao
vv...@google.com <vv...@google.com> #99
Thank you for reporting this issue. We have a fix rolling out in the next release.
ha...@gmail.com <ha...@gmail.com> #100
be...@gmail.com <be...@gmail.com> #101
Please publish a fix for that - I can't believe that I'm forced to dump my 3 year old 500€ phone which runs perfectly except this annoying bug!
sh...@gmail.com <sh...@gmail.com> #102
sh...@gmail.com <sh...@gmail.com> #103
ha...@gmail.com <ha...@gmail.com> #104
mc...@gmail.com <mc...@gmail.com> #105
sh...@gmail.com <sh...@gmail.com> #106
sh...@gmail.com <sh...@gmail.com> #107
sh...@gmail.com <sh...@gmail.com> #108
ne...@gmail.com <ne...@gmail.com> #109
ha...@gmail.com <ha...@gmail.com> #110
sh...@gmail.com <sh...@gmail.com> #111
fa...@gmail.com <fa...@gmail.com> #112
ni...@gmail.com <ni...@gmail.com> #113
si...@gmail.com <si...@gmail.com> #114
al...@gmail.com <al...@gmail.com> #115
ha...@gmail.com <ha...@gmail.com> #116
sh...@gmail.com <sh...@gmail.com> #117
jm...@gmail.com <jm...@gmail.com> #118
I also have a Pixel 4a(5G). This is very annoying. It turns out that, like someone said earlier, it likely has something to do with the Adaptive Refresh Rate feature, even though these devices don't support it. Notably, the issue arises when watching video at 30fps, any resolution, any app. If you play a 60fps video, the issue goes away.
I thought that there's probably a way to force the refresh rate without Settings. Did some research and found some ADB commands that appear to work. I ran the following commands on my Pixel 4a(5G) from my PC with "Debugging over USB":
adb shell settings put system min_refresh_rate 60.0 adb shell settings put system peak_refresh_rate 60.0
Interestingly, the issue went away! However, only for the System UI (Notification shade, opening app switcher, home screen swiping, etc.). In any apps playing video, the issue still appears to persist.
I'll attach some screen recordings when I get a chance.
jm...@gmail.com <jm...@gmail.com> #119
Fix comment:
adb shell settings put system min_refresh_rate 60.0
adb shell settings put system peak_refresh_rate 60.0
jm...@gmail.com <jm...@gmail.com> #120
I should also note that these changes don't appear to persist after rebooting the device. So you'd have to run them on each startup.
sh...@gmail.com <sh...@gmail.com> #121
sh...@gmail.com <sh...@gmail.com> #122
ha...@gmail.com <ha...@gmail.com> #123
xi...@gmail.com <xi...@gmail.com> #124
Commands provided by jm... seems to work, making 4a 5G at least a bit more usable. Thank you for doing Google's work!
sh...@gmail.com <sh...@gmail.com> #125
ha...@gmail.com <ha...@gmail.com> #126
sh...@gmail.com <sh...@gmail.com> #127
si...@gmail.com <si...@gmail.com> #128
in...@gmail.com <in...@gmail.com> #129
Please show us the same loyalty and issue the fix for the Pixel 4a 5g.
p3...@gmail.com <p3...@gmail.com> #130
ha...@gmail.com <ha...@gmail.com> #131
jo...@ynstein.net <jo...@ynstein.net> #132
be...@gmail.com <be...@gmail.com> #133
ha...@gmail.com <ha...@gmail.com> #134
ni...@gmail.com <ni...@gmail.com> #135
"We are no longer offering updates for the Pixel 4 and earlier devices (Pixel 4a (5G) / Pixel 4a / Pixel 4 / Pixel 4 XL / Pixel 3 / Pixel 3XL / Pixel 3a). Please see this support article for more information :
Seems like Google has no intention to update these devices that still have this user experience issue.
You're going to be stuck either completely wiping the phone to downgrade it or get a different phone.
ll...@gmail.com <ll...@gmail.com> #136
ad...@google.com <ad...@google.com> #137
If this issue still exists in a current Android build, we request that you log a new issue along with the bug report here
ni...@gmail.com <ni...@gmail.com> #138
However, with what was posted in this topic, already seems to solidify that Google has no intent or effort to fix phones that are no longer providing software updates to these phones affected by this bug. So with these phones no longer receiving software updates, the customers with these phones that update to the latest and only available software for their Pixel 4a 5G will be stuck with similar experience and just expected to ditch the 4a 5G for a newer phone.
Users with this phone that want to have a stutter free experience is now probably forced to either install an older version of the software to not have this stuttering issue or install custom software onto their phone to stay secure.
am...@google.com <am...@google.com> #139
The
Thanks.
Description
- Build Number: google/barbet_beta/barbet:14/U1B2.230922.006/10879723:user/release-keys
(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? Slow Performance
What steps would let us observe this issue?
1. Go to YouTube
2. Play some video
What did you expect to happen?
Smooth work
What actually happened?
Interface extremely lagging due video playback
How often has this happened?
Occasionally
What was the effect of this issue on your device usage, such as lost time or work?
Extreme - device was unusable
Debugging information
Google Play services
com.google.android.gms
Version 233717044 (23.37.17 (190400-570218080))
System App (Updated)
Android System WebView
com.google.android.webview
Version 593814031 (117.0.5938.140)
System App (Updated)
Network operator: Tele2You
SIM operator: Tele2You
Filed by Android Beta Feedback. Version (Updated): 2.37-betterbug.external_20230817_RC02 (DOGFOOD)
To learn more about our feedback process, please visit