Status Update
Comments
bl...@google.com <bl...@google.com>
vo...@google.com <vo...@google.com>
al...@google.com <al...@google.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.
al...@google.com <al...@google.com>
ja...@google.com <ja...@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.
sh...@gmail.com <sh...@gmail.com> #4
ja...@google.com <ja...@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:
sh...@gmail.com <sh...@gmail.com> #6
sh...@gmail.com <sh...@gmail.com> #7
sh...@gmail.com <sh...@gmail.com> #8
ja...@google.com <ja...@google.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.
sh...@gmail.com <sh...@gmail.com> #10
ja...@google.com <ja...@google.com> #11
[Deleted User] <[Deleted User]> #12
ma...@starchey.com <ma...@starchey.com> #13 Restricted
ma...@starchey.com <ma...@starchey.com> #14
pa...@gmail.com <pa...@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.
ra...@gmail.com <ra...@gmail.com> #16
sh...@gmail.com <sh...@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:
sh...@gmail.com <sh...@gmail.com> #18
zi...@gmail.com <zi...@gmail.com> #19
pr...@gmail.com <pr...@gmail.com> #20
tu...@gmail.com <tu...@gmail.com> #21
pu...@gmail.com <pu...@gmail.com> #22
This is producing an enormous e waste problem.
Countless controllers going to waste.
A really poor Bluetooth implementation.
Shame on Google.
br...@gmail.com <br...@gmail.com> #23
On Mon, Sep 30, 2024, 7:07 PM <buganizer-system@google.com> wrote:
ja...@google.com <ja...@google.com> #24
al...@gmail.com <al...@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.
so...@gmail.com <so...@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)
le...@gmail.com <le...@gmail.com> #27
ja...@google.com <ja...@google.com> #28
Hi,
We've recently deployed a mitigation for this issue in the latest Play Store release.
Hopefully this has resolved the restart issue, but please comment on this bug if the issue is still happening to you (also please attach a bug report if you can reproduce).
ad...@gmail.com <ad...@gmail.com> #29
ja...@google.com <ja...@google.com> #30
We've made improvements in Play Store version 34.5, so as long your Play Store is updated you should benefit from them. (You can see the version in the Play Store settings menu or the Android settings app detail page)
If this is reproducible for you, could you collect and attach a
ma...@gmail.com <ma...@gmail.com> #31
I am still experiencing this problem as well. model: Android One S3-SH Android Ver: 10 Google Play Store Ver: 35.3.10-21 Is there a solution?
ja...@google.com <ja...@google.com> #32
Hi,
This shouldn't be happening on a recent play store version like yours.
Would it be possible for you to provide us with some additional information to debug this issue further:
- A bug report after the issue has happened (
https://developer.android.com/studio/debug/bug-report ) - Rate of reproduction: Does this happen to you 100% of the time, or only e.g. 20%? If known: Does it only happen on specific device models?
- If possible, could you provide us with steps on how you are able to reproduce this issue?
Thanks!
la...@gmail.com <la...@gmail.com> #33
1. It downloads the new version and starts installing.
2. After install it continues running the game, but the game is not updated
3. there is no error or anything
la...@gmail.com <la...@gmail.com> #34
vo...@itechart-group.com <vo...@itechart-group.com> #35
de...@gmail.com <de...@gmail.com> #36
de...@gmail.com <de...@gmail.com> #37
com.google.android.play:app-update:2.1.0
com.google.android.play:app-update-ktx:2.1.0
Google Play 서비스 36.2.11-29 [O] [PR] 539142984
ki...@gmail.com <ki...@gmail.com> #38
ki...@gmail.com <ki...@gmail.com> #39
Version 2.0.1
ro...@gmail.com <ro...@gmail.com> #40
kr...@gmail.com <kr...@gmail.com> #41
ku...@gmail.com <ku...@gmail.com> #42
After executing the IMMEDIATE update and leaving the background, the app update is completed in the background.
The app doesn't restart and is stuck in the update progress.
Pixel 6a, Samsung Note 8, Samsung Note 10 +
ca...@google.com <ca...@google.com> #43
Apologies for the late reply. We are currently revisiting our support queues. If you still need assistance, could you please raise a new request and provide as many details as possible in order to reproduce the problem?
When you submit new issues they'll only be visible to you, anyone you cc, and to Google.
Description
Have implemented Immediate In-App Update Workflow in my android app but have been observing this weird behaviour where after downloading/installing the app update, the api does not restart the app UI (have confirmed that the app is activated in the background) only on Android 10 and above. For Android 9 and below, the app is restarted and app UI is activated again all fine.
Is this the expected behaviour or am I doing something wrong?
Using the following version for the play core library:
implementation "com.google.android.play:core:1.9.0"
and followed the official documentation for IMMEDIATE in-App update here -https://developer.android.com/guide/playcore/in-app-updates