Assigned
Status Update
Comments
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. Please upload the AOSP patch following this guidance
tz...@gmail.com <tz...@gmail.com> #3
Add IMS and XCAP APNs for Almadar Carrier ID 2006 MCC606 MNC01
Change-Id: I9594ce3d2276127d2a585b9c630b672c857bede7
Change-Id: I9594ce3d2276127d2a585b9c630b672c857bede7
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #4 Restricted+
Restricted+
tz...@gmail.com <tz...@gmail.com> #5
But there is no crash. This is a behavioral error.
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #6
Thanks for the above information. For us to further investigate this issue, please provide the following additional information:
Please provide the screen recording and full bug report:
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:https://developer.android.com/studio/debug/bug-report#bugreportdevice
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Please provide the screen recording and full bug report:
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
vi...@google.com <vi...@google.com> #8
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
vi...@google.com <vi...@google.com> #9
Could you provide the full bug report to proceed further with our analysis:
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
tz...@gmail.com <tz...@gmail.com> #11
The bug occures when the TYPE_APPLICATION_OVERLAY window uses the LayoutParams.FLAG_ALT_FOCUSABLE_IM. You can comment the flag in the supplied project to see the difference.
Description
* What device are you using?
Pixel
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
1. Download the sample project:
2. Run the app, it creates a TYPE_APPLICATION_OVERLAY window.
3. Open Telegram, open a chat window and select the Attach file icon.
* What was the expected result?
The menu should be above the keyboard. You can check the expected result by closing the TYPE_APPLICATION_OVERLAY window
* What was the actual result?
The menu is hidden behind the keyboard
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)