Fixed
Status Update
No update yet.
Comments
ty...@google.com
vi...@google.com
Fixed in
Added itemColors function to NavigationSuiteDefaults so developers can do like so:
val itemColors = NavigationSuiteDefaults.itemColors(/* change only what they want to change*/)
NavigationSuiteScaffold(
navigationSuiteItems = {
item(
...
colors = itemColors
)
},
){...}
18...@163.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3-adaptive-navigation-suite:1.0.0-alpha06androidx.compose.material3:material3-adaptive-navigation-suite-android:1.0.0-alpha06androidx.compose.material3:material3-adaptive-navigation-suite-desktop:1.0.0-alpha06
vi...@google.com
18...@163.com
Thank you for your attention and look forward to more good news.
vi...@google.com
Our development team has fixed the issue you have reported. For reference, you may refer the
18...@163.com
I do not have permission to view and modify relevant information.
zy...@google.com
Please see the diff attached.
18...@163.com
Thanks！
ch...@gmail.com
Comment has been deleted.
Description
This form is only for reporting bugs found in the Android Generic System Image. Refer to [aosp report bug page](
Please describe the problem in detail, include the following information about your report:
Most of the info could be found in Android Device’s “settings > system > about phone” page.
--------------------------------------------
HARDWARE PLATFORM:
Device Manufacturer:NULL
Device Brand and Device Model:TV
Android OS Version (Base OS version before installing GSI image):Android 13
Android OS Build Number (please input the full string):
STEPS TO REPRODUCE:Power on the device.
OBSERVED RESULTS:Grabbed the boot log and found that the system_server crashed during the boot process, causing zygote to restart.
EXPECTED RESULTS:The system starts normally.
Analyze：
1.Through log analysis, the reason for the system error crash is： libc++abi: termination with uncaught exception of type NSt3__112system_errorE: condition_variable timed_wait failed: Invalid argument.
2.Analyze the code and locate the location where the problem occurs:android/frameworks/base/services/incremental/ServiceWrappers.cpp runTimers().
3.Through analysis and experiments, it is initially believed that the problem caused by the parameter "nextJobTs" passed to "mCondition.wait_until" is too large. We divide the initial value of the "static constexpr TimePoint kInfinityTs" by 2 and the problem no longer occurs.
Please help to analyze the root cause of this probabilistic problem.
1.Why is a probabilistic question？
2.Why is this issue no longer recurring when reducing the incoming time?
--------------------------------------------------------------------------
Please also run "adb bugreport" and archive the output.
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. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (
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