Fixed
Status Update
No update yet.
Comments
wa...@gmail.com
We have passed this to the development team and will update this issue with more information as it becomes available.
pu...@google.com
pu...@google.com
Similar problem in my apps when using ScrollView in activities and dialogs. When scrolling up or down there is no animation when we reach the edge. There is no possibility to scroll in the opposite direction until we press the screen. Many apps have this problem. Please fix this issue. Bad user experience.
wa...@gmail.com
Still not fixed in "UPB4.230623.005". Please fix this issue before the final release. Bad user experience in many apps using ScrollView.
pu...@google.com
The issue has been fixed and it will be available in a future build.
wa...@gmail.com
Unfortunately, this issue has only been partially fixed.
After scrolling the ScrollView content down and then up to the very beginning, the ScrollView content does not return to its starting position. When the screen is pressed again, the ScrollView content returns to its starting position. Same problem when scrolling up and then down to the very end.
Please fix this issue completely before the final release. Bad user experience.
After scrolling the ScrollView content down and then up to the very beginning, the ScrollView content does not return to its starting position. When the screen is pressed again, the ScrollView content returns to its starting position. Same problem when scrolling up and then down to the very end.
Please fix this issue completely before the final release. Bad user experience.
wa...@gmail.com
redacted
pu...@google.com
For us to further investigate this issue, please provide the following additional information:
- Request for you to attach the bug report captured on 4.1 build on the same drive link shared in
comment#1 https://developer.android.com/studio/debug/bug-report#bugreportdevice .
ni...@gmail.com
Ok
da...@gmail.com
Based on my testing, the behavior is now partially fixed for ScrollView and completely unfixed for HorizontalScrollView. As for the correct behavior, please refer to RecyclerView scrolling behavior, it works well, and is unaffected by this bug.
I've added a new directory "
Please check and fix the issue before final release. Thanks!
ah...@gmail.com
I cannot provide bug report because it includes sensitive data (e.g. e-mail addresses). I opened a separate thread for this issue:
https://issuetracker.google.com/u/1/issues/293474517
Can't reproduce the issue? In the attached video you can see what is still wrong.
Can't reproduce the issue? In the attached video you can see what is still wrong.
da...@gmail.com
We have passed this to the development team and will update this issue with more information as it becomes available.
jo...@gmail.com
Still not fixed in Android 14 Beta 5
th...@gmail.com
The issue has been fixed and it will be available in a future build.
ad...@google.com
Unfortunately the issue still exists in Android 14 Beta 5.2. Please fix this issue before the final release.
pi...@gmail.com
Still not fixed in Android 14 Beta 5.3! Please fix this issue before the final release.
Description
What
User experience
What type of Android issue is this?
Fingerprint Auth
What steps would let us observe this issue?
What did you expect to happen?
Double press power button should launch camera WITHOUT requiring fingerprint unlock
What actually happened?
Double pressing power button launched camera app but would attempt to scan finger print instead of allowing user to press shutter button (user missed the photo because of this)
What was the effect of this issue on your device usage, such as lost time or work?
Slight
Additional comments
I was hiking when this happened to me. It wasn't every time I launched the camera app from an off lock screen, but it did happen more than once on the current OTA update I'm running. I tried to replicate it just now but it worked as expected. I'm wondering if there was something to do with proximity sensing from coming out of my pocket, the double press timing on the power button, or something else, but it did make me miss the picture and it wouldn't let me take a picture until I got it to scan my fingerprint properly.
Tis my first time joining the beta team and first time running a bug report so please don't hesitate to reach out for clarification on anything.
When
Time and frequency
When did this happen?
Jun 5, 2024 2:58 PM GMT-06:00
How often has this happened?
Occasionally
Where
Component
Suggested component: <not visible> (1498455)
Build and device data
- Build Number: google/husky_beta/husky:VanillaIceCream/AP31.240426.023.B4/11882682:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 242213039 (24.22.13 (190408-638740827))
System App (Updated)
Android System WebView
com.google.android.webview
Version 642214833 (125.0.6422.148)
System App (Updated)
Network operator: AT&T
SIM operator: AT&T
Filed by Android Beta Feedback. Version (Updated): 2.43-betterbug.external_20240522_RC03 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit