IssueTracker

PLEASE READ:

This form is only for reporting bugs found in the Android Generic System Image. Refer to [aosp report bug page](https://source.android.com/setup/contribute/report-bugs#platform) for other issues.

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:
Google

Device Brand and Device Model:
Pixel 9 Pro Fold

Android OS Version (Base OS version before installing GSI image):
15.0.0

Android OS Build Number (please input the full string):
Stock software: AP3A.241005.015
GSI: AP41.240925.009 (Issue also occurred with previous GSI)

STEPS TO REPRODUCE:
1) Setup factory software on device with an eSIM, and leave standard SIM tray empty. Ensure SIM is detected and mobile network is functional
2) Install GSI+GMS with DSU Loader
3) Reboot into GSI once complete, and complete initial device setup, including network activation step. Confirm SIM is detected and mobile network is functional.
4) Reboot back into stock system, and allow network to connect. Confirm SIM is detected and mobile network is functional.
5) Reboot back into DSU GSI.

OBSERVED RESULTS:
After step 5, SIM is no longer detected in GSI, and mobile network is unavailable.
I noticed that on the factory software, the eSIM is listed as "SIM 2", however when the GSI activates the SIM, it's activated as "SIM 1". If rebooting within the GSI, rather than back to the stock system, the SIM continues to be recognized; it's only after rebooting back into the stock system, and then back into the DSU GSI that the SIM is no longer detected. That's why I believe it may be related to this issue.

EXPECTED RESULTS:
eSIM should continue to be detected and functional.

--------------------------------------------------------------------------

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 (https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

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 (https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

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

Bug Report Drive Link:
bugreport-gsi_gms_arm64-AP41.240925.009-2024-10-23-17-44-38.zip - https://drive.google.com/open?id=1-8cXdDUz7_SAhMW-IpT_Ea6k0m2as7cx