Obsolete
Status Update
No update yet.
Comments
as...@gmail.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, 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.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, 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.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
vi...@gmail.com
I sent you the google drive links to the bug report and attached some screenshots of the process.
Number 2 is network settings when physical sim is active and number 4 is network settings when esim is active and physical sim is present in sim tray but is not detected
Number 2 is network settings when physical sim is active and number 4 is network settings when esim is active and physical sim is present in sim tray but is not detected
to...@gmail.com
Hi, I'm having the same issue. I contacted Google Fi support and they gave me a manually switch Sims. It worked. To manually switch Sims
*#*#794824746#*#*
Not an ideal solution however it's a patch until they fix it.
*#*#794824746#*#*
Not an ideal solution however it's a patch until they fix it.
as...@gmail.com
Thanks for that code! Not ideal, but helpful!
da...@gmail.com
Another way to switch is to, hit the plus button on mobile network, download Sim, it'll fail
Now turn on airplane and turn off airplane..
Now turn on airplane and turn off airplane..
dt...@gmail.com
What if the Sim you are connected to is the esim not the physical sim?
da...@gmail.com
Same issue on my Pixel 2 XL after upgrading from Android 9 to 10. The workaround dialer code works.
vi...@gmail.com
I am facing this issue as well. I had to manually to remove the physical SIM and reinsert it to get it working.
cw...@gmail.com
Same here. This is a real and easy to reproduce issue.
cw...@gmail.com
I have the exact same issue. The other work around would be to unlock bootloader and downgrade to 9 or see if one of the 10 betas doesn't have the bug. I am seriously considering downgrading.
mi...@gmail.com
Same issue, just brutal and embarrassing
mi...@gmail.com
One more anecdote. Possibly out of date since this experience happened on Beta 2 in the second week of May.
The (physical) sim swaps did not help me, no matter how many times or in what order.
The only thing that worked for me was the dialer code that was provided by Fi support.
The (physical) sim swaps did not help me, no matter how many times or in what order.
The only thing that worked for me was the dialer code that was provided by Fi support.
mi...@gmail.com
Same issue. Must eject and reinsert ATT sim after switching to Fi eSIM
sh...@gmail.com
I've been trying different solutions. The only thing that works is to use the change sim code above. Google, you need to fix this.
mi...@gmail.com
Please share the gdrive link as mentioned in
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
ka...@gmail.com
This issue is extremely frustrating. I am currently traveling internationally and try to swap between T Mobile physical SIM and Google Fi eSIMdepending on the location. Can't do this anymore unless I ask for one of my wife's earrings to pop the SIM card out. She's getting slightly annoyed now. Hopefully there will be a fix soon.
ad...@gmail.com
Same issue please fix asap
dw...@sharpmind.de
Google please fix this. How can you release this version without testing this function? On the behalf of all international travelers using Pixel 2, 😠😡🤬
er...@gmail.com
Same issue, this is very annoying. If I had known this was an issue I would have waited for fix before upgrading.
er...@gmail.com
+1
gr...@gmail.com
I just had a layover in Cairo and it cost me $20 for a roaming package.
en...@google.com
dw...@sharpmind.de
I have been able to redownload an esim for Google Fi by uninstalling updates from the sim manager. Google Fi has activated now, but it is unclear whether it will successfully connect.
va...@gmail.com
Same problem on my Pixel 2. Google Fi esim and AT&T physical sim
Description
Noticed this behavior with the package installer through marketplace/ browser. Pick any app
from marketplace, for my test I'll use "US Yellow Pages Search".
1) Download the app from marketplace.
2) When it's finished downloading, open the notifications panel, and choose to run it.
3) App starts up.
4) Pause app by hitting the home screen.
5) Resume the app by hitting the Yellow Pages app icon from your app tray.
6) Hit the back button.
7) Now you can see that there was another instance of this app running underneath - the back
button should return you to the homescreen here, instead it brings you back to the other
instance of the Yellow Pages app you started from the marketplace launcher.
It's easier to see this behavior, when, on step #4, before pausing the app by hitting the home
screen, navigate to a new activity in the Yellow Pages app (do a search for some business, then
view its details, it will start a new activity). Then it's easier to see that when you resume the app,
instead of returning to the business details activity, you're shown a new instance of the app,
starting from its root activity.
This may be the same bug affecting developers using eclipse to launch their apps:
id=2373&q=defunct&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
you can see that when the marketplace / browser launches your app, it uses the same intent flag
as eclipse (which also exhibits this behavior):
Intent { flags=0x10000000
(FLAG_ACTIVITY_NEW_TASK?)
so it seems that if there's an instance of your app running which was launched with the above
flag, the system won't simply resume that running app if the user tries hitting that app icon from
the app tray.
This is confusing for the user, it would probably make more sense if the system just resumed
the already-running app for them.
--------------------
This behavior exists on 1.5 through 2.0, emulators and G1 / Droid / Hero (haven't tried on other
devices).
--------------------
**By "browser install", I mean you can host an apk file on a server, then download the apk
through the device browser. When downloaded, you're presented with the options "Open" or
"Done". If you choose "Open", the installer will use the flag mentioned above and this behavior
starts.