Status Update
Comments
ad...@google.com <ad...@google.com> #2
ja...@gmail.com <ja...@gmail.com> #3
kr...@gmail.com <kr...@gmail.com> #4
ad...@google.com <ad...@google.com> #5
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Screen Record of the Issue
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.
Android bug report (to be captured 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.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
ja...@gmail.com <ja...@gmail.com> #8
to...@gmail.com <to...@gmail.com> #9
za...@gmail.com <za...@gmail.com> #10
ja...@gmail.com <ja...@gmail.com> #12
kr...@gmail.com <kr...@gmail.com> #13
ki...@gmail.com <ki...@gmail.com> #14
sa...@google.com <sa...@google.com> #15
Please provide few more details for better understanding:
- Is it specific to any app or just chat apps?
- Is it reproducible for other keyboards like swiftkey as well?
- Does it go away after reboot or factory reset?
Please follow these steps while capturing fresh bugreport in latest beta 3.1 build:
- Reproduce the issue and don't interact with the device (essentially don't navigate away from current screen).
- Using shell, trigger a bug report: "adb bugreport"
- Keep screen on, don't navigate away from screen until bug report capturing completes
sa...@google.com <sa...@google.com> #16
- Also, do let us know if you have talkback enabled, thanks.
ad...@google.com <ad...@google.com> #17
dj...@gmail.com <dj...@gmail.com> #18
I installed SwiftKey and tested it, the same occurs. I do not have talkback enabled.
ja...@gmail.com <ja...@gmail.com> #19
sh...@gmail.com <sh...@gmail.com> #20
This needs to be looked at as a priority issue
Also on pixel 5 beta 5
ja...@gmail.com <ja...@gmail.com> #21
sh...@gmail.com <sh...@gmail.com> #22
za...@gmail.com <za...@gmail.com> #23
to...@gmail.com <to...@gmail.com> #24
ja...@gmail.com <ja...@gmail.com> #25
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Happens to me as well.
Filed by Android Beta Feedback. Version (Bundled): 2.18-betterbug.external_20210512_RC04
To learn more about our feedback process, please visit
ja...@gmail.com <ja...@gmail.com> #26
ja...@gmail.com <ja...@gmail.com> #27
za...@gmail.com <za...@gmail.com> #28
di...@gmail.com <di...@gmail.com> #29
ka...@gmail.com <ka...@gmail.com> #30
This is only with notifications that show on-screen. Notifications that don't create the pop-up window at the top, don't change focus. I can confirm this happens with new incoming text messages, Ring doorbell alerts, Discord messages, and every temporary on-screen notification window.
I don't know if it could be affected by special app permissions, such as admin apps, etc. Possibly the view usage permission? Or notification access permission. I run Nova Launcher (Nova7) as my default launcher and it has this access (as well as admin), but these have not changed between builds. I also use Sesame, which has notification access. Though these didn't previously cause an issue on the last beta build of June feature update preview, possibly a code change with notifications isn't playing well with notification access permissions.
I created a trace to hopefully help. Here's a rundown of what I was doing during the trace. I started the trace, pulled down notifications. Replied to a friend and asked her to send me another text. I switched apps to Chrome and began typing in the search/url bar. Random characters. After about a minute of waiting, I sent myself a text message from my other phone. The notification arrived on screen and my keyboard closed and the notification gained foreground. I swiped the notification up to send it to the notification blind, pulled down notifications and tapped to stop the trace. I also enabled Core Services, RenderScript, and Runtime Resource Overlay prior to tracing.
System trace is shared with android-bugreports@google.com
Hope this helps.
ka...@gmail.com <ka...@gmail.com> #31
And just to reiterate from before, this is "in production"
ka...@gmail.com <ka...@gmail.com> #32
le...@gmail.com <le...@gmail.com> #33
ji...@gmail.com <ji...@gmail.com> #34
jj...@gmail.com <jj...@gmail.com> #35
ka...@gmail.com <ka...@gmail.com> #36
Rebooting the device always resolves the problem.
sa...@gmail.com <sa...@gmail.com> #37
ko...@gmail.com <ko...@gmail.com> #38
ga...@gmail.com <ga...@gmail.com> #39
ga...@gmail.com <ga...@gmail.com> #40
When notification comes nothing work on another app even also not going back.
mr...@gmail.com <mr...@gmail.com> #41
ju...@gmail.com <ju...@gmail.com> #42
ad...@google.com <ad...@google.com> #43
Android bug report (to be captured 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.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
as...@gmail.com <as...@gmail.com> #44
je...@gmail.com <je...@gmail.com> #45
ad...@google.com <ad...@google.com> #46
vo...@gmail.com <vo...@gmail.com> #47
Hope this helps!
jo...@gmail.com <jo...@gmail.com> #48
Here's a screen video that clearly shows the issue.
>
I followed your steps and the keyboard bug is now gone.
Thanks for sharing your interesting find.
ad...@google.com <ad...@google.com> #49
mi...@gmail.com <mi...@gmail.com> #50
Now, everything is working properly on my Pixel 7 Pro.
ad...@google.com <ad...@google.com> #51
ed...@gmail.com <ed...@gmail.com> #52
ad...@google.com <ad...@google.com> #53
Screen Record of the Issue
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.
Android bug report (to be captured 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.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
br...@gmail.com <br...@gmail.com> #54
ry...@gmail.com <ry...@gmail.com> #55
mi...@gmail.com <mi...@gmail.com> #56
The issue is back on July 2023 monthly update. I tried with the steps I mentioned in my older comment, but I'm still having this issue.
mi...@gmail.com <mi...@gmail.com> #57
I just tried again, I also installed the latest Google Play system update and rebooted, and now the issue disappeared again.
ff...@gmail.com <ff...@gmail.com> #58
While the notification ribbon is there, no amount of tapping will bring the keyboard back.
Border line unusable.
ka...@gmail.com <ka...@gmail.com> #59
What devices are you experiencing this regression on? And what build number? If a dev can identify the possible modules, I can try to find the regression, but I haven't spent enough time with AOSP to narrow the scope enough.
Definitely need to know which devices you guys are using though and confirm your build number
ka...@gmail.com <ka...@gmail.com> #60
It looks like it was fixed in the 23 Q1 release, then regressed in Q3 on Android 13 but will wait to confirm
ka...@gmail.com <ka...@gmail.com> #61
It seems >
ad...@google.com <ad...@google.com> #62
gu...@gmail.com <gu...@gmail.com> #63
ad...@google.com <ad...@google.com> #64 Restricted+
ad...@google.com <ad...@google.com> #65
- Please share a screen record & bug report (see
)comment #53
ad...@google.com <ad...@google.com> #66
si...@gmail.com <si...@gmail.com> #67
ad...@google.com <ad...@google.com> #68
Regarding
si...@gmail.com <si...@gmail.com> #69
ad...@google.com <ad...@google.com> #70
mi...@gmail.com <mi...@gmail.com> #71
Build number: TQ3A.230705.001
ad...@google.com <ad...@google.com> #72
ad...@google.com <ad...@google.com> #73
ti...@gmail.com <ti...@gmail.com> #74
ti...@gmail.com <ti...@gmail.com> #75
ad...@google.com <ad...@google.com> #76
Please also share a bug report & corresponding video (see
ad...@google.com <ad...@google.com> #77
ka...@gmail.com <ka...@gmail.com> #78
I will capture a bug report ASAP. Had to reboot to stop issue as I was in the middle of something. Can confirm regression on Android 14 UPB4.230623.007 raven.
Keyboard closing and notification steals focus until the notification is swiped away or closed. No gestures work.
Tried clearing cache and storage of Android System Intelligence after force stopping and then force stopping again after clear, with no effect.
This is one persistent bug... Bug report coming soon.
us...@google.com <us...@google.com> #79
A friend of mine has the same issue on Pixel 6 with Android 13 (build number: TQ3A.230705.001).
Others have already attached screen recordings and bug reports so I will skip that. Please tell me if an additional one would help.
If you use your keyboard a lot and get a lot of notifications, this makes the phone very annoying to use. I disabled a lot of notifications because of this.
Based on the number of upvotes, I believe this should be a P0 or at least a P1. Also I think
ad...@google.com <ad...@google.com> #80
ad...@google.com <ad...@google.com> #81
ka...@gmail.com <ka...@gmail.com> #82
It's one of those bugs that, well, last time I experienced it, I will check, I may have done a trace recording. If so I'll share it to you guys. But several other people had isolated it (seemingly) to Android Intelligence Service. As per
Of note, I have not experienced the issue on my Pixel 3 XL since I upgraded to the Pixel 6 Pro as my main device. My P3XL is running Pixel Experience 13 Plus build. It is not a GSI or GKI build and uses legacy build. It's meant to provide the native Pixel experience with security patches beyond Google's EOL. The kernel is a custom kernel of 4.9.xx.
I use the phone the same way as with the factory firmware, and the bug has not appeared in the 2 years since upgrading. I know that 3rd party firmware is not supported, but it seems that the code base they built AOSP from, the bug is not present. Since AOSP for P3XL stopped at 12, it doesn't appear to exist in the final release for the P3XL, and has not regressed from any of the patches applied from API 33.
This info might be useful to someone. Hopefully.
ad...@google.com <ad...@google.com> #83
Others who are still facing this issue on the latest build : Please share a bug report from UPB4.230623.007 (or later) build.
us...@google.com <us...@google.com> #84
Filed
I think the issue stopped happening for me for some time. I have no idea if it matters, but I was in a different country at that time. Then it started happening again.
us...@google.com <us...@google.com> #85
also I think it's not only the keyboard, the 'back' button also doesn't work when there is a notification
ad...@google.com <ad...@google.com> #86
ad...@google.com <ad...@google.com> #87
ad...@google.com <ad...@google.com> #88
ad...@google.com <ad...@google.com> #89
Unfortunately the issue will be closed within 7 days if there is no further update.
ad...@google.com <ad...@google.com> #90
je...@gmail.com <je...@gmail.com> #91
ad...@google.com <ad...@google.com> #92
Please provide the info requested in
ad...@google.com <ad...@google.com> #93
Please provide the info requested in
Unfortunately the issue will be closed within 7 days if there is no further update.
d....@gmail.com <d....@gmail.com> #94
Have same issue since July
ad...@google.com <ad...@google.com> #95
Regarding
ad...@google.com <ad...@google.com> #96
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
ad...@google.com <ad...@google.com> #97
ff...@gmail.com <ff...@gmail.com> #98
Nevertheless, here is another bug report of the same issue on build UP1A.231105.003:
As well as a screen recording of it.
(Note: As you can see I touched the screen right before the keyboard disappeared, but this was just a coincidence, the bug also occurs when I don't touch the screen.)
I tried to open a new issue as requested in
So if anybody else reads this and has the required permission, feel free to repost this material into a new issue.
I just want this annoying issue fixed ASAP.
Description
- Build Number: google/coral/coral:S/SPB2.210513.011/7465093: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? Input / Keyboard
When did this happen?
Jun 24, 2021 19:17 GMT-04:00
What steps would let us observe this issue?
1. Open keyboard
2. Let a notification come in
What did you expect to happen?
To be able to still use the keyboard when the notification came in
What actually happened?
Keyboard minimizes and can't bring it back up unless you swipe away notification
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
Still happening on beta 2.1