Fixed
Status Update
Comments
xa...@google.com <xa...@google.com> #2
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.
yt...@gmail.com <yt...@gmail.com> #3
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
xa...@google.com <xa...@google.com> #4
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.
gk...@uber.com <gk...@uber.com> #5
Thanks for that code! Not ideal, but helpful!
yt...@gmail.com <yt...@gmail.com> #6
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..
xa...@google.com <xa...@google.com> #7
What if the Sim you are connected to is the esim not the physical sim?
km...@gmail.com <km...@gmail.com> #8
Same issue on my Pixel 2 XL after upgrading from Android 9 to 10. The workaround dialer code works.
xa...@google.com <xa...@google.com> #9
I am facing this issue as well. I had to manually to remove the physical SIM and reinsert it to get it working.
gl...@fitbit.com <gl...@fitbit.com> #10
Same here. This is a real and easy to reproduce issue.
xa...@google.com <xa...@google.com> #11
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.
xa...@google.com <xa...@google.com>
gl...@fitbit.com <gl...@fitbit.com> #12
Same issue, just brutal and embarrassing
xa...@google.com <xa...@google.com> #13
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.
sk...@gmail.com <sk...@gmail.com> #14
Same issue. Must eject and reinsert ATT sim after switching to Fi eSIM
mt...@gmail.com <mt...@gmail.com> #15
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.
xa...@google.com <xa...@google.com> #16
Please share the gdrive link as mentioned in comment #3 .
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.
yt...@gmail.com <yt...@gmail.com> #18
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.
mt...@gmail.com <mt...@gmail.com> #19
Same issue please fix asap
mt...@gmail.com <mt...@gmail.com> #20
Google please fix this. How can you release this version without testing this function? On the behalf of all international travelers using Pixel 2, 😠😡🤬
mt...@gmail.com <mt...@gmail.com> #21
Same issue, this is very annoying. If I had known this was an issue I would have waited for fix before upgrading.
ad...@google.com <ad...@google.com> #22
+1
an...@gmail.com <an...@gmail.com> #23
I just had a layover in Cairo and it cost me $20 for a roaming package.
xa...@google.com <xa...@google.com> #24
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.
an...@gmail.com <an...@gmail.com> #25
Same problem on my Pixel 2. Google Fi esim and AT&T physical sim
xa...@google.com <xa...@google.com> #26
Also experiencing this on my Pixel 2 while in the midst of an international trip.
[Deleted User] <[Deleted User]> #27
I spent an hour in chat with Google. Trying to figure out there's a different work around. They told me that they are aware of the problem in an engineer is working on it. In the end the final work around is to downgrade to pie. The technician told me that you need to restart your device seven times in a row. That's the first I've heard of that. Have not tried it. I'm going to give it a few more weeks. Anyone else learn anything?
ba...@allegro.com <ba...@allegro.com> #28
Same issue. Very annoying!! My sim connections are also much less stable.
xa...@google.com <xa...@google.com> #29
Same problem on my Pixel 2 xl. It's important to me ,pls fix it
xa...@google.com <xa...@google.com> #30
Same issue with me. Can't switch back to physical SIM once switched to Google Fi. I am using Pixel 2. Please help asap as I am roaming and need switching to both SIMs seamlessly
b....@gmail.com <b....@gmail.com> #31
Same issue. Google Pixel 2. Project Fi and physical SIM (Deutsche Telekom, if that matters).
xa...@google.com <xa...@google.com> #32
Same issue. Pixel 2, Google Fi eSIM and Cell C (ZA) SIM
ba...@allegro.com <ba...@allegro.com> #33
Same issue, Pixel 2, Google Fi eSIM and physical SIM. Switching is now painful.
xa...@google.com <xa...@google.com> #34
Manually dialing the code in #4, above (https://issuetracker.google.com/issues/140447170#comment4 ) works to switch both ways. It is a work-around.
My mobile network switched after I copied and pasted the code into the phone dialer. It would not switch upon saving the code as a contact's phone number and dialing the number. Apparently that is a known limitation. Seehttps://android.stackexchange.com/questions/191201/can-i-save-a-star-hash-code-as-contact , where an alternative is suggested:. Tasker. Any other ideas, anybody?
My mobile network switched after I copied and pasted the code into the phone dialer. It would not switch upon saving the code as a contact's phone number and dialing the number. Apparently that is a known limitation. See
xa...@google.com <xa...@google.com> #35
I have this same issue, the number seems to work But its a painful process.
Another workaround I discovered was : pop out the SIM from the phone slightly, Go to the + new sim option in the carrier settings area, it will prompt to enter a new SIM, push it back in, and select the new SIM and it will mount it and work on that network again.
Definitely a problem for those of us who use GoogleFi + another carrier.
Another workaround I discovered was : pop out the SIM from the phone slightly, Go to the + new sim option in the carrier settings area, it will prompt to enter a new SIM, push it back in, and select the new SIM and it will mount it and work on that network again.
Definitely a problem for those of us who use GoogleFi + another carrier.
Description
We need to provide a DSL that allows higher level matching strategies.