Murcielago
In my case it was the question of detailed configuration of both. Just at first moment, after full installation of eSIM and then adding back a phisical SIM from the 2nd carrier, there was an issue with preferential position of eSIM in the system, due to excessive permission scope self-granted by eSIM (it literally colonized the phone :)
After the proper set up, both SIMs work simultanously with no issue, each with its own config.
"Ask every time" function works fine, for calls and SMS.
I didn't tested yet incoming calls in possible combinations, but I hope it will work reasonably.
At the moment I'm very satisfied with the solution.
CircusAround
- Apr 4, 2024
- Joined Apr 2, 2024
- Edited
I'm actively dealing now with dual-SIM (SIM+eSIM) settings in Pixel (and it's my 1st dual-sim experience ever).
It's a bit annoying and time consuming process, and I see lots of strange behaviour of eSIM, that established itself in a master role in the system (!), where it's impossible to switch eSIM off (not yet sure if it's not possible the other way than normal in SIM mgt panel), and other weird combinations between eSIM/SIM, SIMs/System, and othe unexplained (to me) behavior.The systems, in general, often work in a very unexpected manner and the only reasonable way is to tweak and experiment, with different settings, multiple checking, restarts, on/off`s, changing order/sequence, etc. If you understand more or less what you're doing! ;)))
Worked well for me this time too, although I don't see it as a finished thing and am expecting to get issues during the full use of the phone in this configuration. But generally I'm impressed by how GOS manages that chaos :))) 5! *****You may finally need, as you wrote, to consult something wit the carrier(s), as stated here: https://web.archive.org/web/20240316175213/https://support.google.com/pixelphone/answer/9449293?hl=en#zippy=%2Cstop-using-a-sim-card%2Cturn-off-a-sim-temporarily
GOOD LUCK.
And don't forget to share your findings, wich is usually very helphul for others sooner or later.
_- Edited
Problem SOLVED. Surprisingly.
I keep my monologue with aim to help ppl with identical or similar problem.
The eSIM started to work after I allowed the phone to connect to a mobile network. (Location spoofing off, VPN off, GSF ON, then off after full initialization in the roaming network).
The physical SIM in carrier's home network has been disconnected and deactivated when installation of eSIM started.It is supposed that the error msg "Couldn't activate ... Subject code: 8.2.6, Reason: 3.8 ..." was issued only due to lack of connection to the mobile network to initialize the eSIM after successful download and installation.
Moderator note: Removed some inaccurate claims.
- Edited
sonicbackdrop
Or perhaps two standards of initial settigns to choose during installation, that could be kept as a default setting for the system/phone. One with permissions as we can see now, and the other with everything OFF (except the absolutely necessary for basic functions), naturally including WLAN and BT OFF.- Edited
P.S.
An interesting thing is the fact that the carrier has (and uses) the ability to make important changes in the system, with out our knowledge and approval. I observed it twice. The last time was after installation of an eSIM, where suddenly, out of nothing, ...the 'Nearby devices' permission appeared as switched ON for the "Phone' app.
It shows we have a real problem here.- Edited
other8026 I really have no idea what you're talking about here. You're talking about an open source app/service that's part of an open source OS. Everything is auditable. If you actually read through the code, you'd find that there's nothing interesting going on there. Like I mentioned earlier, the permission is probably there to do something boring, like to allow the app to see if there's a bluetooth device nearby or something, maybe to avoid blowing out someone's ears when sending an alert (just an example, I don't know what the app does in this case, just to be clear).
I don't see any reason to arbitrary leave the "Wireless emergency alerts" module impossible to switch off permanently, as well as the "Nearby devices" in it.
Sorry but, witha all due respect to developers (that I honestly admire), it's definitely not normal at all to have permanently such spying tool in the phone. Especially if all the rest is possible to control by the user.Regarding your 'Final thought': Maybe, but it was absolutely not intended. Graphene OS is the system of choice for me - the only one, that few years ago I've found trustworthy enough to use, and with installation etc. feasible and understandable as a whole by a bit more advanced ("computer literate +") user. I'm a very satisfied Graphene OS user, as I explained below.
And your "something as small as permissions granted to system apps"... Please be more serious. The MINIX OS is an old example that explains what WE (not only me) mean, and the technology advances very quickly so OUR concerns are fullu justified. Remember, we're talking here about a Google's product and many of US remember the year 2020/2021 with mass deployment of agressive spyware that used BT (not only) to map locations and people's interactions, impossible to switch off. If your'e intelligent (I believe you are) and not ignorant, you know very well the trend. Some people simply can't accept or even tolerate the reality imposed by them.
Pixel was my first 'smartphone' with chimpanzee keyboard nonsense, after BB and earlier Nokia E models of course. I resisted the unwanted as lon as I could. And finally Pixel + Graphene OS. And I don't regret. I can only COMPLIMENT and pr PRAISE its DEVELOPERS and the SYSTEM itself. It allowed me to live without Google (that I abandonned fullu and for ever in 2012, wnen I fully realized what Google really is), until technical need appeared for eSIM installation (I hope I can trust the advice and delete GS without affecting eSIM func.).
I can ridicule Google/Apple slaves (and I do) honestly, although the life can get complicated sometimes without that crap, so what. I've even purchased a typical google phone only for banking. For first 3 days and nights I kept it in the storage otside the house, after configuration I made when I could see with my own eyes all "goodies" inside that system. I knew before what to expect, but trust me, I was shaken quite seriously at the confrontation moment.
So, please don't accuse me of subversion. With a couple of discussed exceptions, I'm VERY satisfied with Graphene OS. It's a brilliant example of good alternative to the stuff imposed by The Cartel. Happily we have now (finally!) more and more of such good alternatives. I highly appreciate efforts of people contributing in all aspects of the project. None the less my (OUR) uncertainty and fears ARE based.
And I repeat: If not proved or publicly declared impossible to change, it's not justified to support the current state of "Wireless emergency alerts" (and maybe 'sensor permission' by default here and there).de0u
I wanted to replace the word "disgusted", after I found it a bit too strong, with the word "disappoited", but unfortunately the system doesn't allow edition after a very short time.
An I'm ready to pay for using the OS, especially if a bit more reliable in security aspects than it currently is (i.e. unmanageable and persistent "Wireless emergency alerts" module).- Edited
sonicbackdrop
Hi, You're perfectly right. To me it's totally ridiculous to see dozens of modules and apps with that permission active by design.
Not every one knows that Gyroscope and Accelerometer can work perfectly as a MICROPHONE. This ends the discussion.
The OS is trustworthy (to some reasonable extent of course) or is NOT.Similar issue I see regarding that mysterious "Wireless emergency alerts" module, where I'm not allowed by the masters to neutralize "Nearby devices" function/permission.
Why, in so numerous threads, almost nobody points at the issue?
Why Graphene OS developers did nothing about that until now?
The (more than)obvious application of that service is to help spying on people. So disgusting to see a possibility of so malicious use facilitated and protected by the "privacy oriented OS".
Perhaps the only way to end that comedy is to physically neutralize BT and NFC modules. And naturally Gyroscope + Accelerometer (that personally I don't need at all, both).- Edited
.
I started with scanning QR code and used the execution command on the right (square with arrow).It worked, but ended with error msg: Couldn't activate ... Subject code: 8.2.6, Reason: 3.8.
As on the images. * [ unfortunately it's not possible to upload any images here... So I can't show my 2 screenshots..]
I tried to reserch the issue, but unfortunately it's all well above my competences.
I only suppose that it happened due to the fact that SIM was not switched off befor eSIM installation attempt.
And I wodner if eSIM was installed or not. In the first case I understand that probably a new QR code is needed and a new attempt to install eSIM.
Now I can see a SIM (not eSIM) on the list, and it's switched OFF. Not clear if the profile has beed downloaded and installed.
I really don't know what to do with that. I only know, that the operator/carrier should not see that my phone is in another country, in any case. Until eSIM is not installed and working. Then the normal roaming status, after I switch ON that eSIM when ready.https://forums.att.com/conversations/more-att-prepaid-discussions/i-cannot-use-my-esim/65baecdfabeda37c5afe0773
https://support.google.com/pixelphone/thread/80980694/can-t-activate-esim-reason-code-3-8?hl=en
https://www.gsma.com/newsroom/wp-content/uploads//SGP.23-v1.6.pdf
https://forums.att.com/conversations/more-att-prepaid-discussions/i-cannot-use-my-esim/65baecdfabeda37c5afe0773
https://source.android.com/docs/core/connect/esim-error-handling
https://communaute.sosh.fr/t5/Ma-ligne-Mobile-SIM-PUK/Cannot-activate-esim-in-my-pixel-6/td-p/2620362
https://communaute.sosh.fr/t5/Livraison-ma-carte-SIM-mes/Probl%C3%A8me-d-activation-eSIM/m-p/2540230#M29464
And, naturally:
https://grapheneos.org/usage#sandboxed-google-play-configuration
https://grapheneos.org/usage#esim-supportCircusAround
It crashes differently, apparently depending on permissions given to G apps. It loops, it fully closes, or gives the screen "SIM manager keeps stopping" [app info / Close app / Show details].That's all I can provide as description of the problem....
- Edited
Hi guys,
I'm trying to install eSIM in 4a. In a specific situation, where I'm in other country than the carrier's (and the newly acquired physical SIM is not with me).
So, to avoid being blocked by the carrier due to foreign location, I prepared the operation as follows:- VPN (a good one): always ON, the "right location" ON;
- GPS emulator/spoofer: the "right location" ON, all seem to work properly;
And of course, the most unwanted stuff I can imagine, which is Google crap - installed: - G Play Services
- G Play Store
- G Services Framework
(with permissions: Network, Location where it aplies)
ALSO:
- "privileged eSIM management: Enabled;
- No physical SIM in the device;
- Location: ON;
- The device is connected to LAN.
- Airplane mode: ON (then OFF, but with the same result)
- The OS is up to date, no updates pending etc.
Unfortunately it didn't work. The installation process crashes before it actually starts.
In "Connect to mobile network"
> "Download a SIM instead? / Add a number using eSIM"
> "Download your eSIM" NEXT
> at ..."Checking network info" IT CRASHES [black screen], then goes back to > ""Connect to mobile network" .. "Download a SIM instead?"...I suppose it may be a problem with Permissions in G apps. But even adding extra permissions (i.e. Pnone, Camera) in Play Services and Play Store doesn't help.
What I did wrong? Can you help me with that? I badly need this stupid eSIM.
Also my question is: What are the minimum necessary permissions for each of 3 Google apps to support eSIM installation.
And, what is the correct status of Airplane mode for installation? ON or OFF?Thank you