Status Update
No update yet.
Comments
ak...@google.com
Information redacted by Android Beta Feedback.
da...@gmail.com
What
More information
It turns out, this issue happens almost every time. If it crashes a certain way (probably if it's happening too quickly or too many times), the device will reboot. Last time, it took me to the Android recovery saying along the lines of "Can't load Android ... Your data might be corrupted" and the options were try again or factory reset.
The screen recording was done on the first attempt. Thankfully I can unlock after the lock screen crashes using the pin or fingerprint. Fingerprint can also work right from AOD.
But when after a few crashes, some worse than others (the display doesn't stay on and I had to press the power button), the device rebooted and entered me into a recovery screen. The second bug report was taken after that.
When
Time and frequency
Time when bug report was triggered: Mar 14, 2025 5:26 AM GMT+07:00
Where
Build and device data
- Build Number: google/panther_beta/panther:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250960035 (25.09.60 (260400-732198584))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: Telkomsel
SIM operator: Telkomsel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ak...@google.com Restricted
ak...@google.com
This is quite bad. Now it happens every time.
The crash also sometimes happen when turning off the screen. In which case, the AOD likely won't work. I have to turn on the display before unlocking but thankfully looks like it doesn't crash again if it crashes when turning off the screen.
New bug report and screen recording on next post.
ak...@google.com
What
More information
While on the home screen, it crashes when turning off the display. Somehow, I can't replicate this while recording, and I had to turn on Do Not Disturb (Bedtime) for it to crash when turning off again.
Later in the recording, the crash happens repeatedly. Every time this happened previously, the lock screen and AOD didn't recover and the phone rebooted.
The last one happened while I was attempting to record this, and I saw the old white "Power Off" dialog with the spinning circle UI before it rebooted to the same recovery screen again. I couldn't find that recording after.
The bug report was taken after the attached (successful) recording.
Where
Build and device data
- Build Number: google/panther_beta/panther:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250960035 (25.09.60 (260400-732198584))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: Telkomsel
SIM operator: Telkomsel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ak...@google.com
Information redacted by Android Beta Feedback.
da...@gmail.com
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ak...@google.com
ak...@google.com
Turning off AOD seems to avoid the issue on my P7 too, so far. It's a bit inconvenient but necessary for now. Thank you for the suggestion.
an...@google.com
ak...@google.com
What
More information
As I turned off the AOD, the unexpected shutdowns have completely disappeared
When
Time and frequency
Time when bug report was triggered: Mar 17, 2025 5:57 AM GMT+05:00
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: PAK - PL
SIM operator: ZONG
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
an...@google.com
Information redacted by Android Beta Feedback.
Description
If the issue is caused by an app and not a platform issue, we will do our best to route the issue to the app developer. However, note that it is up to the app developer to actually address reported issues.
Before logging your issue, check to see whether it is a known issue described in the current release notes at:
or has already been reported at:
If the issue has already been reported, you can "star" or comment on the existing report if it corresponds to the issue you are seeing.
To expedite resolution of your issue, please provide as much relevant and specific information as possible. This will probably require some work from you. Most reports should include at least the following:
* Are you an Android developer?" (Y/N) - /Y
* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example TPB3.220624.005).- UPB3.230519.008
* Is this a regression from Android 13 to 14? yes
* What device are you using? (for example, Android Emulator, GSI, Pixel 6) Pixel 6 Pro- 14 beta-3
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.) On launching the applications, detects the device as rooted and not allowing to go further
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc- Accessing build props using NDK
* What was the expected result? ro.secure and ro.debuggable flags from system props should be there in file to validate whether the device is rooted or not. But in 14 beta, ro.secure and ro.debuggable flags are missing and hence app detects as rooted
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
* Relevant logcat output.
* Link to captured Android bug report (shared privately in Drive.)
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Please note, bug report attachments should not be included directly in issue reports.
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes