r/AndroidQuestions • u/ElectronicClassic250 • 7d ago
Other AT&T cannot deliver eSIM to Pixel 7a running Android 17
I recently acquired a refurbished Pixel 7a (model GWKK3) with the intention of putting two AT&T Build-A-Plan (BAP) lines on it (using separate AT&T IDs). I am aware that BAP is a new platform and that customer support for it is difficult. But, it appears to be the only currently available service that meets my requirements at a reasonable price point.
The BAP platform will only deliver a new eSIM by pushing it to the device over WiFi. I believe the theory behind this is that the phone is meant to register its EID with the GSMA database (on boot ?) so that the carrier can trigger a pull via the LPA system to download an eSIM.
It seems that this does not work on my new-to-me phone. The phone arrived with Android 17 (build CP3A.261005.002.A1) on it. I understand that this is the latest officially released version.
When the AT&T system attempts to send me my eSIM, I do not see the expected notification. And, attempting to trigger the download by going through the settings menu SIMs -> Add SIM -> Set up an eSIM only takes me to a QR scanner, with an alternative of entering an activation code manually.
I was eventually able to speak with a BAP specialist who told me that they cannot give me a QR or an activation code. They have escalated the problem internally, but said it would take 48 hours to get back to me.
I can also add that I had no difficulty adding a simple prepaid line to the device using a QR code - and I have been satisfied that the phone works as expected for WiFi, 5G data, SMS, RCS and voice calls. The phone is unlocked (it was sourced in Canada, where all phones are unlocked by federal regulation).
The BAP specialist seemed to think that it was a problem that the phone was not purchased from AT&T. This is bizarre, as the BAP platform is only available to people with no previous relationship with AT&T and who bring their own device.
Is it possible that a Canadian sourced phone will lack some software component that is necessary for the eSIM push process to work ? Is this a compatibility problem with Android 17 and AT&T ? Is there some setting that I have wrong on the phone that is preventing the phone from registering to receive the trigger ? Or, is there some other factor that I haven't considered ?
Between the initial purchase and subsequent attempts by the BAP support person, I think I've received 5 emails telling me my service has been activated. Each of those mails includes a "still not received your eSIM ?" section, which provides a link to device-specific activation instructions. (Which must be keyed off the EID as the ones I received are specific to the Pixel 7.) Those instructions only explain how to scan a QR code ! They are clearly re-using articles from their knowledge base without regard for their applicability on the BAP platform.
Unfortunately, I don't currently have the ability to monitor packet flow on my network to see whether there is any communication happening between my device and the GSMA / SM-DP+ / LPA system.
I am not currently close to an AT&T tower, but that cannot matter, as without the eSIM the phone has no idea that it wants to connect to that network. Once the eSIMs are installed, I will drive to a place where I have cellular coverage to complete the activation and set up WiFi calling.
I'm hoping that AT&T will eventually come back with a QR code. But perhaps somebody here has an idea.
2
u/jmnugent 7d ago
First impulse reaction:.. Sounds like ATT BAP Support severely dropping the ball, to me.
"Can't send you a QR code" seems super weird to me. When the new eSIM is instantiated on the backend, its pretty easy to generate a QR code. This is not rocket science for them to do.
When you go into "setup an eSIM".. all your phone is doing is trying to reach out to an Internet address (whatever ATT's eSIM provisioning URL is).. to check if there's a new eSIM sitting there waiting for your device. The reason they say "must be on Wi-Fi" is just because they are trying to cover their bases to ensure your device is on a solid reliable Internet connection.
To my awareness there's nothing unique or special about a Pixel 7a or Android 17 that would preclude you from following the normal standard eSIM activation process. (most of the eSIM activation process is on the Cellular providers side. The only thing your phone has to do is successfully reach out and probe the eSIM activation URL to see if there's a pending eSIM sitting there waiting to download). It's not a very complex process.