Develop Bugs

Call Screening in UK? Is there a way to get it working?

I got my Pixel 3 XL today - UK release day - and I am sure like many other was disappointed to see call screening restricted to the US.
It doesn’t make any sense as we speak the same language and I am prepared to change the settings to get it to work.
So I changed the language to US, I changed my Google account location - but nothing still no call screening option.
Anyone have any ideas? Thanks.

Spinstorm said:
I got my Pixel 3 XL today - UK release day - and I am sure like many other was disappointed to see call screening restricted to the US.
It doesn’t make any sense as we speak the same language and I am prepared to change the settings to get it to work.
So I changed the language to US, I changed my Google account location - but nothing still no call screening option.
Anyone have any ideas? Thanks.
Click to expand...
Click to collapse
It's a server side feature, has nothing to do with settings. From what I have read- it will be coming to the UK eventually.

So one of the main features I bought the phone for is restricted to the US which they didn't even make clear to us. nice.

I wonder if there are some GDPR issues. Google is monitoring the call, transmitting it to this servers...it warns you the call is being recorded.
Still, they should have been clear on availability.

Nothing is transmitted to their servers, it's all done locally on the device. I imagine the feature will roll out to us in an update, like the night mode on the camera.
Very disappointed to see both features not present in the UK from day one, considering they're two main selling points of the phone. Pisser.

Elicx said:
So one of the main features I bought the phone for is restricted to the US which they didn't even make clear to us. nice.
Click to expand...
Click to collapse
They made it perfectly clear, announced at the keynote: https://youtu.be/EsoQGTA1SxY
Posted on their blog on 10/9:
First, starting out in English in the U.S., Pixel 3’s on-device AI helps you screen phone calls and avoid spam calls. Imagine you’re at dinner with family or in a meeting at work and a call from an unknown caller comes in.
Click to expand...
Click to collapse
https://www.blog.google/products/pixel/google-pixel-3/
So on, and so forth.

uicnren said:
They made it perfectly clear, announced at the keynote: https://youtu.be/EsoQGTA1SxY
Posted on their blog on 10/9:
https://www.blog.google/products/pixel/google-pixel-3/
So on, and so forth.
Click to expand...
Click to collapse
Welp, I must be both death and blind. Apologies for my idiocy there. Thanks.

It is an on phone feature so surely there must be a string or something like with night sight to enable it... maybe someone can make a modded phone app?
I really want to use this rather than wait an inderterminate period of time for it to be released in the UK.
Interestingly I put a Project Fi SIM in my Pixel 3XL and the call screen option appeared but then when I want to try it it was gone... even with a Fi SIM and a US phone number....

Someone in Reddit claims to have activated it in India (on a rooted 2xl)...
So hopefully only a matter of time. (I'm waiting for it in Aus)
Sent from my Pixel 3 XL using Tapatalk

I was also really disappointed as they had never mentioned this in their marketing messages. Then I found this https://www.tpsonline.org.uk/tps/whatistps.html
Apparently, this is a legitimate solution for filtering nuisance calls.
No point in waiting until Google make this available in the UK.

Spinstorm said:
It is an on phone feature so surely there must be a string or something like with night sight to enable it... maybe someone can make a modded phone app?
I really want to use this rather than wait an inderterminate period of time for it to be released in the UK.
Interestingly I put a Project Fi SIM in my Pixel 3XL and the call screen option appeared but then when I want to try it it was gone... even with a Fi SIM and a US phone number....
Click to expand...
Click to collapse
I'm in the U.S. but I got it working on my P2XL, including transcripts about a month ago using this mod , but this requires root. Then I bought a P3XL and was irritated that transcripts hadn't rolled out officially even though I had been using them on the P2XL for quite a while. So I opened up the .xml file in the P3XL and the same flags were there. I only changed 2 flags to true and boom, transcripts were working. This is very easy to do and easily reversible (especially when you save a copy of the original xml file). When reading the mod OP, note there are locale based flags to avoid the U.S. location check and I think it's worth a shot if you are rooted. Give it a go and report back if it is working for you. Here are the strings I am referring to:
Code:
<boolean name="__data_rollout__SpeakEasy.OverrideUSLocaleCheckRollout__launched__" value="false" />
<boolean name="G__speak_easy_bypass_locale_check" value="false" />

Follow the below post and it works irrespective of where you are. (It needs root though)
https://forum.xda-developers.com/pixel-2-xl/themes/root-enable-call-screening-pixel-t3861350

yokuoh said:
Nothing is transmitted to their servers, it's all done locally on the device. I imagine the feature will roll out to us in an update, like the night mode on the camera.
Very disappointed to see both features not present in the UK from day one, considering they're two main selling points of the phone. Pisser.
Click to expand...
Click to collapse
And you believe them? Google cannot be trusted. I assumed everyone knew this by now.
Call screening is an awful feature and if you use it to filter spam or robocalls in the UK you will end up getting even more as answering a robo call will simply tell the spammers that you are active and they will bombard you.

Jonathan-H said:
And you believe them? Google cannot be trusted. I assumed everyone knew this by now.
Call screening is an awful feature and if you use it to filter spam or robocalls in the UK you will end up getting even more as answering a robo call will simply tell the spammers that you are active and they will bombard you.
Click to expand...
Click to collapse
Wow. CS is the best thing ever, and I very much enjoy using it. It works very well on non-spam calls as well when you just cannot take the call or it's a reminder from your doctor, pharmacy, etc. Google already screens out the majority of spam calls (they are marked spam) and makes it easy to block these and any other repeat callers. Yeah, it's still whack a mole but now you don't even need to pick up the phone. As for the UK users, you can try the mod if rooted. Otherwise know it will be there "soon".

Anyone w/S7 Active on Red Pocket? Mobile hotspot & tethering just broke

Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob

Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!

I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.

bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.

This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?

Is VoLTE possible

I have a Singapore variant of the tab S4 it makes and receives calls just fine over 3G but wont make them over LTE is VoLTE even possible on this? I travel the country and have ran into a few instances where I have LTE coverage but not 3G

It looks bad
Samsung has disabled VoLTE in every tablet that supports it, tab s3, s4, s6 and s7. It won't comment on this. I suggest contacting Samsung and asking for an update to address this issue. I understand there is a complex hack to accomplish this, but it involves editing a binary file.

If Samsung won't do it, maybe the carrier firmware can enable VoLTE?
AT&T says its Tab S4 variant will continue to work after their 3G shutdown.
Tab S4 (SM-T837A) is listed in their compatible devices:
https://www.att.com/idpassets/images/support/wireless/Devices-Working-on-ATT-Network.pdf
Maybe this means VoLTE is enabled for calling? Or they might mean it will keep working but only for data LTE.

There is no carrier tab s4 that will work for calls, and I don't think sms either! The carriers have a system in which you can have data/talk/text on a samsung Tab 3,4,5,6,7,8 if you also have a samsung phone.
Samsung also has a setting you can enable to make calls on your tablet if you also have a phone, if both devices are logged into your Samsung account. No security flaw there! Not sure if the phone must be Samsung too, but it would seem so!
I'm not going to say what I think about a manufacturer going out of its way to reverse a setting, intentionally crippling its flagship products, so customers need to purchase more stuff to obtain the expected functionality!
I did write to the CEO of Samsung Electronics, Co., Ltd.. I asked for a firmware update to enable VoLTE in the Tab S series beginning with the S3.
Earlier Tab S don't have compatible hardware. If you clear your browser data, so no one can tell you're a hacker, and google 'Samsung investor relations', you can find his name and address.
I'm not going to dox him here. But if anyone wants to write him, please be very civil, clean, upright, and simply ask for an update, followed by, "I only ask for Samsung to live up to its reputation! I think my request is more than reasonable! Thank you for taking your valuable time to read my message. Best Regards, name"
Don't use spinglish--words and phrases that mean one thing implied to mean something else. And example in reverse is when Dell dubbed one of its laptops exploding into flames, 'a thermal event'!
Just be direct, brief, polite and honest.

Samsung chat says:
Hi, thank you for contacting Samsung Care. I’m D-- ....
... It will be updated in coming update. You will receive a notification on your tablet once it got updated.
‎8:36 PM When do you think the update will be?
‎8:37 PM Profile SEA Digital Messaging We don't have the exact information. Hope it will update will release in couple of weeks.
‎8:38 PM This is due to the 3G shutdown? That will work then, with the update I'll be able to download a phone app from the app store?
Thank you
‎8:38 PM Profile SEA Digital Messaging It is not about the 3G shutdown, the feature is not available on the tablet. Carrier have not permitted to use this feature on Samsung tablet. You can use caling feature on third party applications like WhatsApp ETC.
‎8:41 PM ok yes. Then I will wait for the update. Is this official it will be updated?
the tablet will be updated to download a phone app?
‎8:42 PM Profile SEA Digital Messaging Yes it will be official once the Update released you will get notification on your screen.
Once you get the Update it will update automatically to make the calls.
‎8:44 PM ok thank you D
Click to expand...
Click to collapse
So maybe it'll be soon I'm hoping to use VoLTE for my tablet soon. Otherwise Singapore firmware might allow VoLTE calls currently? Why is that? I can't download or install or side-load any phone app currently.
edit update: I flashed to t-mobile using odin and that lets me send and receive texts just fine using messenger app. I use tello so I can place outbound calls over wifi too, so I can just use google voice for any other phone call inbound. I've heard other versions outside usa might be able to place calls though?? Suppose we'll get an update here soon anyway hopefully.
-Cat_F

There will be convoluted ways to get data/talk/text on the Tab S models without adding VoLTE compatibility.

awesome14 said:
There will be convoluted ways to get data/talk/text on the Tab S models without adding VoLTE compatibility.
Click to expand...
Click to collapse
?

Cat_F said:
?
Click to expand...
Click to collapse
Like calling on other devices, if both a phone and tablet are logged in to your Samsung account, you can use your tablet for Data/talk/txt, because it's actually using the phone.

Connecting mobile data issues

I'm having trouble connecting to the data even though I'm connected to the carrier services.
I'm able to make calls and access to texting. Any one else got similar issues?
I have to use my WiFi to use the internet.

Readytowait said:
I'm having trouble connecting to the data even though I'm connected to the carrier services.
I'm able to make calls and access to texting. Any one else got similar issues?
I have to use my WiFi to use the internet.
Click to expand...
Click to collapse
The rm5g has many issues, this one of them. Its really a shame. Im sending mine back.

My issues with the device are the fact it claims to have band 66 support but only connects to 2 or 4 around me. 66 is much faster

joemossjr said:
My issues with the device are the fact it claims to have band 66 support but only connects to 2 or 4 around me. 66 is much faster
Click to expand...
Click to collapse
It has no b66, check the website. The idiots removed it. 66penetrates buildings better too. I will be returning this piece of garbage, and getting a rog3 when it comes out.

Quick shortcut maker is my friend
Ok, short and sweet and to the point. Until or unless you root this thang. Quick shortcut maker is my friend since the lg g3. Network issues. Use it. No root use it. This is a wonderfull tool. So that being said there is the device info where you can choose network, hint to you is choose unknown. And on the other menus it unlocks choose global. Well it's kinda that easy. But you just gotta fool with it. You knew it was coming when you bought this phone. So buck up and just do it
---------- Post added at 11:14 PM ---------- Previous post was at 11:08 PM ----------
If your like me you love this stuff. I try to get any phone I can that the networks can't chase. Call it old habits. And I'm gonna say I love this phone and I loved the rm3. I knew when I bought this phone what I started. I also bought it less then red magic sells it for and hot it on April 20 th. It's full on Chinese rom. Ver. 2.46. red magic support says mid May we will finally have a global rom. Liars I say. But get out that quick shortcut maker and shortcut master. And mess with it. Oh it's radio info. My bad. Set the network to unknown. It's the only way I could get data, mms,internet and phone calls every other setting either gave me phone no data, or data no phone. But unknown gave me both and click the 5g on.

VZTech said:
The rm5g has many issues, this one of them. Its really a shame. Im sending mine back.
Click to expand...
Click to collapse
Sadly, seems I have similar problem (Sweden)....I have also sent a question to Red Magic support..lets see..
..I also try to manually add or change APN..but seems not possibly to key in needed info...

Try putting roaming on. Works for me in Sweden.

same issue here cannot get the mobil data to work but the calls work any idea what the issue is (sweden aswell)

G7 Power (XT1955-5) kicked off AT&T network despite being VoLTE compatible?

Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.

Unless I'm misreading the list, this is a whitelisted device on the AT&T network.

Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?

They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.

I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.

MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.

(deleted, mistook carrier)

I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.

MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.

From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.

FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.

Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.

I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.

The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE