Samsung Smart Call - Samsung Galaxy Note 10+ Questions & Answers

I've got unlocked Note 10+ and I flashed the U firmware because of video calling that's missing on U1. Now I found that on T Mobile version there is no Smart Call and it is replaced by T Mobile NameID, which I consider inferior and I'd have to pay for full functionality.
Anybody knows if there is any way how to get the stock Samsung dialer with Smart Call back? I'd hate to flash the U1 ROM and go through the restore process again. Even with Samsung cloud, Google and SD backups it took me almost half day to get it set as I had it before.

Stank0 said:
I've got unlocked Note 10+ and I flashed the U firmware because of video calling that's missing on U1. Now I found that on T Mobile version there is no Smart Call and it is replaced by T Mobile NameID, which I consider inferior and I'd have to pay for full functionality.
Anybody knows if there is any way how to get the stock Samsung dialer with Smart Call back? I'd hate to flash the U1 ROM and go through the restore process again. Even with Samsung cloud, Google and SD backups it took me almost half day to get it set as I had it before.
Click to expand...
Click to collapse
My past experience with Samsung Smart Call, was that i found that even though, its baked into Samsung Firmware, it is Service Provider depended. to "activate /work".
I might be wrong, but i personally believe so, based on my experience.
Just to recap, my experiences with my old Note 8 and my Note 9 (both devices not rooted)
I also flashed Stock Samsung firmware .. different CSC onto these devices.
I found on both occasions i lost the function of th Smart Call.
( Hiya services), also Volte function etc etc.
I could see the Smart Call settings in firmware, but it was greyed out.
Could not enable it at all.
When i flashed my old Samsung Firmware (Service Provider CSC) Smart Call (Hiya services), was enabled again and working.
I'm sure in your case, you'll will find it's Service Provider depended.
Good luck.

willcor said:
My past experience with Samsung Smart Call, was that i found that even though, its baked into Samsung Firmware, it is Service Provider depended. to "activate /work".
I might be wrong, but i personally believe so, based on my experience.
I'm sure in your case, you'll will find it's Service Provider depended.
Good luck.
Click to expand...
Click to collapse
The thing is, after I purchased and set up the phone on stock Samsung firmware, VoLTE and Smart Call worked perfectly fine. But stupid me wanted to try the video calling. I found that the video calling is not different than Google Duo and I will NEVER use RTT texts. I see no real advantage from using T Mo firmware in comparison with stock Samsung (provisioned for T Mo of course)
Actually quite the opposite. For me, the signal strength and battery life is practically the same on both and again, FOR ME Smart Call is much more useful than video call and RTT.
If anyone knows any benefits from keeping T Mo firmware over stock, please enlighten me. I really don't want to go through the flashing the whole thing and restoring dance again, but I'm afraid I will have to.

Stank0 said:
The thing is, after I purchased and set up the phone on stock Samsung firmware, VoLTE and Smart Call worked perfectly fine. But stupid me wanted to try the video calling. I found that the video calling is not different than Google Duo and I will NEVER use RTT texts. I see no real advantage from using T Mo firmware in comparison with stock Samsung (provisioned for T Mo of course)
Actually quite the opposite. For me, the signal strength and battery life is practically the same on both and again, FOR ME Smart Call is much more useful than video call and RTT.
If anyone knows any benefits from keeping T Mo firmware over stock, please enlighten me. I really don't want to go through the flashing the whole thing and restoring dance again, but I'm afraid I will have to.
Click to expand...
Click to collapse
Ha, your post reminds me,
that when i flashed
my branded Samsung Firmware ( Voda CSC) with the Samsung unbranded Firmware,
The reason, was also to get video calling working.
As my branded device did not have video calling option on dialer.
I could only activate video, if someone else, video called me... only then the video option, would appear.!
I then afterwards, realized that i lost my Smart Call functions. and flashed back to the branded software.
This was on my Note 9.
So i had no video call option on dialer ,but Smart Call.
Now...
again, with my branded( Voda CSC) Note 10 +,
i see that my device has video calling on dial pad.....!
So, the Service Providers, chop and changed.
A year back, they disabled video calling option, from dial pad.
Now video calling is back on the dial pad plus Smart Calls is working fine.
Good luck

So.... I bit the bullet and flashed back the U1 firmware. The only thing I lost is the video calling. I still have RTT button on my dialer. Whether it works or not I haven't tried yet. I know it wasn't there on the original dialer when I purchased the phone. Maybe because I didn't flash USERDATA? Who knows.
I'm happy I've got Smart Call back.

CSC N975U
Good afternoon, I have the n975u model, my question is what firmware should I install, to get the smart call and video calls by duo?. Or is csc the one that has these functions active?
Thanks!!
excuse my english, google translator.

I have a Verizon Note10+ running Android 11 (3.1) I paid my cell off 4 mo ago. Verizon confirmed for me that my cell is carrier unlocked. I've tried everything to get the Smart Call app on my phone to work. The only thing I haven't tried is rooting it cause I don't know how. I have 3 versions of the apk and can't make them work. Can anyone help?

Related

M8 can't receive calls, flashed wrong ROM? (4G problem)

Yesterday I flashed my AT&T HTC M8 to a custom ROM (Wolla) because my phone was really laggy after the Lollipop update, and I noticed that although I am still able to make calls, I cannot receive calls anymore. I am wondering if it is possible that I messed up a step somewhere (especially step 3), or if I flashed my phone with the wrong ROM?
I also looked around on XDA more, and realized a few people also had this problem, and it was resolved by turning 4G data off. Apparently this is a problem with AT&T activating Voice over LTE, and the custom ROM not supporting/compatible. Is there a suggested fix to this problem (eg. flash back to the RUU on HTC's site)?
Here are the instructions that I followed to flash the new ROM:
Unlocked my phone via the HTCDev website
Installed TWRP
(Here is where I think the problem occured). I downloaded the Wolla Marshmallow ROM from the XDA thread, and took the boot.img image from the .zip into my fastboot folder.
Then in fastboot, I typed in "fastboot flash boot boot.img", then "fastboot reboot" to reboot my phone.
HOWEVER, my phone would be stuck in white Android booting screen, and wouldn't move for around 10 minutes, so I thought it was stuck.
I redid step 4 a few times, but the same thing always occured.
Finally, I decided to take the boot.img file from an RUU from HTC's website, and use that instead of the boot.img from the Wolla .zip file.
Now my phone boots, and everything seemed to work.
The only issue is that although I can make phone calls, I cannot seem to receive phone calls. It doesn't "ring" on the caller's end, and goes to voicemail in the end.
Does anyone have any experience with this?
My phone is an HTC One M8 bought from AT&T, unlocked about a year ago.
You're on the right track (AT&T's deployment of VoLTE is the problem), and there is one more suggestion I can make: call AT&T and have HD Voice (their branding of VoLTE) turned off for your account. Details here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Not a true "fix" as obviously, you will not have VoLTE if you do this. But its not a bad compromise, IMO. Not may folks are going to miss VoLTE, and at least the above workaround will allow you to use the custom ROM you want, and have LTE data.
Your other option, is to use an AT&T-based ROM. But who the heck wants that?
I think I'll hit up AT&T chat support today to turn it off, thanks!
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Edit: I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?
Kwkevinlin said:
I think I'll hit up AT&T chat support today to turn it off, thanks!
Click to expand...
Click to collapse
Note that the base level customer service probably can't turn off HD Voice (won't know what you are talking about, or even wrongly claim it can't be done). Ask to talk to a Tier 2 (or some such term) tech support.
Kwkevinlin said:
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Click to expand...
Click to collapse
If you click on the full thread, for which my previous linked post is from, you'll see that there are a good number of folks that had the same issue. And that is just on that one thread, there have been others (like this one of yours).
Plus, there are other variables that will effect whether AT&T users (on "international" based ROMs) will see this issue or not, such as whether HD Voice has been deployed in their market or not (heck, lots of places don't even have LTE yet, much less HD Voice), or whether the HD Voice feature was ever turned on for their account.
Personally, I have yet to see this problem, despite being on several different non-ATT ROMs and frequently travelling to various US regions. So I'm guessing in my case, HD Voice was never activated on my account.
Kwkevinlin said:
Edit: [/B]I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?
Click to expand...
Click to collapse
From what I can gather, this is entirely an AT&T issue. Although nothing is a sure bet when travelling international, I'm sure you probably already well know if you travel abroad occasionally. In particular, LTE implementations seems a lot less standardized from one country to another than 3G or 2G. But falling back to 3G is not a bad option, if you end up needed to. Really, unless you are streaming video a lot, or downloading huge files, 3G is really all you'll need most of the time.
So I think I found might have accidentally found a way to deal with this problem without calling AT&T.
On my stock ROM, I turned of the VoLTE (HD calls or whatever) options under data connections.
Made a few calls to myself to made sure that it was dropping to 3G (ect...) when I called it.
Afterwards I flashed a custom ROM (the new sense 8 rom by sundream) and my phone could still receive calls as it dropped it for 3G.
While you don't have VoLTE you could avoid the hassle of calling AT&T.

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.

How to Record Calls on SM-N975U1 Android 10 (Samsung Note 10+)

Hello Everyone, I hope this is not a noob question...
I bought an unlocked Samsung Note 10+ SM-N975U1 directly from Samsung... Long story short - Samsung said it could record calls, then after my return window expired and several calls with Samsung Techs, they finally admitted that this "feature is locked" and I'm stuck with this $#!T.
I have tried several different call recording apps, and none work.
So my question is, Can someone tell me how to enable call recording on this phone? or direct me to link with the answer...
I really appreciate any help.
I have been looking for answers with no luck
Any one can help
Call Recorder - ACR by NLL works fine.
I download it
I can't here any sound even mine
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
I have no problem to root my room or install new official rom just to have call recording active
Dr.TofyGuy said:
I have been looking for answers with no luck
Any one can help
Click to expand...
Click to collapse
I am going to file a complaint with the Consumer Financial Protection Bureau against Samsung, because they mislead me to be believe that this phone did and had the ability to record calls. They kept saying that it should be fixed in the next software update 2 or 3 times, then after my return window expired, they said this feature is disable and there is no fix. At the same time, they said that the you cannot return this phone. This is fraud and deceptive business practices.
I bought an unlocked phone directly from samsung to avoid having rooting issues and all the carrier bloatware... instead i get this ****.
netnerd said:
Call Recorder - ACR by NLL works fine.
Click to expand...
Click to collapse
I tried it too, but for whatever reason, it only records my voice and not the caller. Thanks for the suggestion.
It's not possible without rooting.
Nastrahl said:
It's not possible without rooting.
Click to expand...
Click to collapse
I figured as much... Thanks
I'm using the free version of Cube ACR and it works great on my unrooted UK model [emoji41]
https://play.google.com/store/apps/details?id=com.catalinagroup.callrecorder
Sent from my SM-T860 using Tapatalk
ACR works fine ! no root needed.
or maybe get it at amazon or galaxy app store version.
they said most recorder app WONT work on wifi call, that why i disabled wifi calling.
BucWiLD said:
I am going to file a complaint with the Consumer Financial Protection Bureau against Samsung, because they mislead me to be believe that this phone did and had the ability to record calls. They kept saying that it should be fixed in the next software update 2 or 3 times, then after my return window expired, they said this feature is disable and there is no fix. At the same time, they said that the you cannot return this phone. This is fraud and deceptive business practices.
I bought an unlocked phone directly from samsung to avoid having rooting issues and all the carrier bloatware... instead i get this ****.
Click to expand...
Click to collapse
It does, it depends on the country and state. Also if you get carrier branded vs unlocked...
Google Dialer
I know some people have found success using the new Google dialer app, which has call recording baked in. I haven't tested myself, but it may warrant further research if it is truly possible.
https://www.xda-developers.com/google-phone-app-call-recording-hands-on/

Port Samsung Dialer to ROM?

Hi all,
TL;DR: can I port the original Samsung dialer (with call recording) to a custom ROM?
Long version: Ok so... I'm completely depressed because I've been trying to upgrade my now well overused S9 for a while, but I just CANNOT find a good replacement which has all my requirements and works properly in Canada. After trying out a few phones (and returning them all) I went back to my S9. But... I want to go the ROM route since the stock one is arguably dated. However, I have the dialer with call recording enable and I'd like to keep it on say, LineageOS. Reason being it can record calls while on Wifi Calling, which I am regularly, as opposed to other call recorders.
So... any advice for me? I'm spending too much time on this...

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

Categories

Resources