Database Users

Mobile Data stops working, and MMS does not work (CM 13)

First the basics. Nexus 6p received 3/30. I did NOT turn it on and update it to the latest stock firmware before proceeding. Rather I immediately unlocked bootloader, installed TWRP, installed CM13 and GApps Nano from OpenGApps. Running on T-Mobile's network using a cut down Micro SIM from my Oneplus One down to Nano size.
I'm running the latest CM13 release snapshot, ZN0EAO1T5, and my mobile data will work initially with LTE upon boot or restart. After a short time (minutes) it will no longer have a data connection. Calls and SMS still go through. While the data is active, if I turn on Wifi and then later return to mobile data the data is not active. In the status bar it just has the triangle signal icon without any indication of type of data connection (i.e. LTE, HSPA+, 3G, etc.). When I pull down the quick setting menu it does list LTE on the mobile connection quick setting button.
Additionally, MMS does not work no matter what I do. Mobile data connection or Wifi. I've researched the T-Mobile APN settings thinking this could have been the issue and no editing there changed anything.
I will likely try to restore to current factor images and begin again to see if that helps. I'll probably go get a proper Nano SIM from T-Mo today too just in case there is any issue along that front.
Anyone else experience this? Anyone else run across others having this issue? It seem separate from the 6.0.1 issues I witnessed with stock ROMs while searching but perhaps I'm wrong.

Currently installing most current stock image and then will try again. Noticed the bootloader and radio were older versions. Hopefully restarting from scratch with the newest system will solve these issues. Fingers crossed.

Boom! Working!
Restarted from scratch after flashing the most current stock ROM. All Set. Thanks for all the help!

... Spoke too soon.... Same problems are right back. I think it may be related to this workaround to stop some of the error messages:
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
I ran this to get rid of the error and I think that caused the problem. So I tried to re-flash only the vendor.img as I've read that as a fix to a few things and it did not help.
I'll have to start from scratch again and see if I'm right. Clearly there is something I'm doing causing this. I just can't figure out what...
AFWall+, Adaway, CM13 superuser, Privacy Guard ??? Ugh.

You don't think it's from the cut down sim getting damaged?
Sent from my Nexus 6P using XDA-Developers mobile app

frigidazzi said:
You don't think it's from the cut down sim getting damaged?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I did not update this sooner.
No, that is not that issue. I did end up determining that the problem is AFWall. There is, apparently, some changes in marshmellow that the developer, ukanth, needs to update AFWall to work with it more appropriately. So I've disabled AFWall for the time being.
I'm not programmer/developer, so it just seems to me to be related to this: https://github.com/ukanth/afwall/issues/520
ukanth notes in that thread this will be fixed in the next update.
I was able to get 100+mbs on LTE in a few different places, so definitely not that SIM.
Sent from my Nexus 6P using XDA-Developers mobile app

stewa2jm said:
Sorry I did not update this sooner.
No, that is not that issue. I did end up determining that the problem is AFWall. There is, apparently, some changes in marshmellow that the developer, ukanth, needs to update AFWall to work with it more appropriately. So I've disabled AFWall for the time being.
I'm not programmer/developer, so it just seems to me to be related to this: https://github.com/ukanth/afwall/issues/520
ukanth notes in that thread this will be fixed in the next update.
I was able to get 100+mbs on LTE in a few different places, so definitely not that SIM.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
You can try the 2.50 radio as well. I was getting similar issues with the latest radio on a variety of roms until I downgraded to that radio. Now I don't have any service issues at all.

messiahfreedom said:
You can try the 2.50 radio as well. I was getting similar issues with the latest radio on a variety of roms until I downgraded to that radio. Now I don't have any service issues at all.
Click to expand...
Click to collapse
Thanks for the suggestion. If AFWall isn't updated soon I'll try it out. I've noticed quite a large increase in data usage already this month without AFWall.
Sent from my Nexus 6P using XDA-Developers mobile app

stewa2jm said:
I did end up determining that the problem is AFWall.
Click to expand...
Click to collapse
You're a saviour man. Was plagued by the data connection issue since yesterday and happened to stumble upon this thread. Disabled AFWall+ and the data started working properly. Thanks a lot for the help man. :good::highfive:

inimaitimepass said:
You're a saviour man. Was plagued by the data connection issue since yesterday and happened to stumble upon this thread. Disabled AFWall+ and the data started working properly. Thanks a lot for the help man. :good::highfive:
Click to expand...
Click to collapse
I had to abandon afwall some time ago due to all of this. Now I'm running CopperheadOS, which is not rooted, so cannot use it anyway. Android 7.* has some decent settings to control permissions by app anyway, so afwall doesn't add enough for me to worry about it anymore.
Sent from my Nexus 6P using Tapatalk

WiFi calling doesn't work on OP5 with Oreo

WiFi calling was working fine with nougat, it doesn't work after I upgraded to Oreo. I have OB4 installed on the phone with T-Mobile USA. I am in remote place without T-Mobile signal. I put Sim card into my Nexus 6, Wi-Fi calling works fine.
So Oneplus team breaks Wi-Fi calling on Oreo?

I have TMobile and I'm on OOS 5.0.1, no issues with WiFi calling here.
Occasionally I will have to toggle airplane mode for it to work, but I had that issue before Oreo.

Still doesn't work on beta 5

HTC_FUZE said:
Still doesn't work on beta 5
Click to expand...
Click to collapse
Have you enabled WiFi calling in the Sim & Network settings?

If you are using Magisk v15.3 get module VoEnabler v1.1 created by Toucan.
I did not even seen option in the sim and network until I install this module...

I have no problems with US T-Mobile, although it does not work with German T-Mobile. In another thread it was explained that Oneplus and the respective carrier need an agreement to make it work. If your carrier doesn't have one, it will not work.

I don't have the option in Sim&Network for WiFi calling until I did fresh installation. Now it is working.

akxak said:
I have no problems with US T-Mobile, although it does not work with German T-Mobile. In another thread it was explained that Oneplus and the respective carrier need an agreement to make it work. If your carrier doesn't have one, it will not work.
Click to expand...
Click to collapse
That's true, without the agreement of German T-mobile no volte or vowi won't work. They want you to buy a galaxy s8 for example which is enabled for both...

It is really strange. WiFi calling option disappear after I switch on the cellular and then switch back to airplane mode.

HTC_FUZE said:
Still doesn't work on beta 5
Click to expand...
Click to collapse
If you are using magisk with OB5, flash VoEnabler and it works.

I know why. The t-mobile sim card must be selected for data.

HTC_FUZE said:
I know why. The t-mobile sim card must be selected for data.
Click to expand...
Click to collapse
You read answer / reply from other people? You talk alone and don't answer to users try help you. In XDA there a "Thanks" button or "Quote/Multi-Quote", i advise to use that.

Pho3nX said:
You read answer / reply from other people? You talk alone and don't answer to users try help you. In XDA there a "Thanks" button or "Quote/Multi-Quote", i advise to use that.
Click to expand...
Click to collapse
I am not talking alone, I am sharing my finding for all people so every one reading the topic can find the clues if they faces similar problem.

atistang said:
I have TMobile and I'm on OOS 5.0.1, no issues with WiFi calling here.
Occasionally I will have to toggle airplane mode for it to work, but I had that issue before Oreo.
Click to expand...
Click to collapse
i know this is a crazy old thread, but have you ever been able to fix this? i'm still having this issue even after ditching OOS and going to a custom ROM. this has to be a bug in the modem firmware, but i've reported it to OP and they seem uninterested in fixing it...

crackers8199 said:
i know this is a crazy old thread, but have you ever been able to fix this? i'm still having this issue even after ditching OOS and going to a custom ROM. this has to be a bug in the modem firmware, but i've reported it to OP and they seem uninterested in fixing it...
Click to expand...
Click to collapse
Nope. I even installed enterprise networking equipment in my home since and it seems to be better (probably placebo). I have also done a factory reset which didn't help.
It seems like I can always receive a call, but can only make a call 75% of the time. There has been times where I tried to call people I know several times when it was acting up, then I would message them telling them to call me and my phone rings minutes later.
What usually works (but not always) is to reboot the phone, then turn airplane mode on, wait a few minutes, then turn it back off.

atistang said:
Nope. I even installed enterprise networking equipment in my home since and it seems to be better (probably placebo). I have also done a factory reset which didn't help.
It seems like I can always receive a call, but can only make a call 75% of the time. There has been times where I tried to call people I know several times when it was acting up, then I would message them telling them to call me and my phone rings minutes later.
What usually works (but not always) is to reboot the phone, then turn airplane mode on, wait a few minutes, then turn it back off.
Click to expand...
Click to collapse
that may be a different issue then...mine always works when it's turned on, but seems to just stop working randomly for no reason. the vowifi and volte icons disappear, and the only way to get them back (and get it working again) is to toggle airplane mode or reboot the phone...
Sent from my ONEPLUS A5000 using Tapatalk

Wifi Calling on PH-1

I have enabled Wifi Calling on my PH-1 and I know for a fact that my carrier supports it. It works fine too, but it's set to "Mobile Preferred". I chose this setting because my Wifi isn't too reliable. However, whenever I call, it uses Wifi even though I am getting LTE+? Is there any way to fix this?

Does anyone have any idea? I have looked all over the internet but have not found any solution? Could it possibly be my carrier?

When I try to enable wifi calling, my launcher crashes. So you are one step ahead of me
Sent from my PH-1 using Tapatalk

yqazi27 said:
I have enabled Wifi Calling on my PH-1 and I know for a fact that my carrier supports it. It works fine too, but it's set to "Mobile Preferred". I chose this setting because my Wifi isn't too reliable. However, whenever I call, it uses Wifi even though I am getting LTE+? Is there any way to fix this?
Click to expand...
Click to collapse
Is your phone a Sprint Variant?

I have a Sprint variant and wifi calling is working perfectly fine for me, I am rooted as well and also using Nova

mexicandroid said:
Is your phone a Sprint Variant?
Click to expand...
Click to collapse
I'm not sure. I have seen 3 Sprint system apps though under "Apps and Notifications", but I don't know if that counts. I got it straight from Amazon, if that helps.

yellk20 said:
I have a Sprint variant and wifi calling is working perfectly fine for me, I am rooted as well and also using Nova
Click to expand...
Click to collapse
yqazi27 said:
I'm not sure. I have seen 3 Sprint system apps though under "Apps and Notifications", but I don't know if that counts. I got it straight from Amazon, if that helps.
Click to expand...
Click to collapse
I finally got it working by installing the Open Market Oreo firmware, setting up WiFi calling them updating to Pie firmware

mexicandroid said:
I finally got it working by installing the Open Market Oreo firmware, setting up WiFi calling them updating to Pie firmware
Click to expand...
Click to collapse
Is there any way to do this without rooting or unlocking the bootloader? I want to preserve my warranty for as long as possible.

yqazi27 said:
Is there any way to do this without rooting or unlocking the bootloader? I want to preserve my warranty for as long as possible.
Click to expand...
Click to collapse
Not that I know of. I don't think they would look at your WiFi calling settings if sent out for repairs. Once you install Oreo open market firmware just relock the bootloader, setup your phone including TMobile WiFi calling settings. Once you update to Pie they shouldn't be able to tell anything because all different variants use the same firmware and your bootloader will be locked encase you send your phone out for repairs.

The other option is to use Google Voice. WiFi calling works great on it.

spotmark said:
The other option is to use Google Voice. WiFi calling works great on it.
Click to expand...
Click to collapse
But does it use your carrier phone number or are talking about the Google appointed number?

mexicandroid said:
But does it use your carrier phone number or are talking about the Google appointed number?
Click to expand...
Click to collapse
You do have to use your GV number. In my case it's irrelevant because I ported my number over to GV some time ago.

spotmark said:
You do have to use your GV number. In my case it's irrelevant because I ported my number over to GV some time ago.
Click to expand...
Click to collapse
So your carrier number and Google number are the same?

mexicandroid said:
So your carrier number and Google number are the same?
Click to expand...
Click to collapse
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.

spotmark said:
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.
Click to expand...
Click to collapse
I like having a different number for when I do mechanic work, don't want to get calls for every little thing at different times of the night, specially when it's unrelated to what I fixed lol

I have the same problem. Set my wifi calling to Mobile preferred but sometimes my calls use wifi calling even when I have cellular reception. Please let me know when you find a solution.
and I think it's funny that nobody addressed your original issue.

spotmark said:
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.
Click to expand...
Click to collapse
I also use this same setup and it works great.

coolmaster121 said:
When I try to enable wifi calling, my launcher crashes. So you are one step ahead of me
Click to expand...
Click to collapse
I have the same issue. It was working fine on Oreo. I tried flash.all fastboot using the stock firmware without success. Let me know if you have a solution. Ty
Edit: I got it fixed by flashing flashall back to stock Oreo 8.1 open market from Essential website then let it updated OTA to Pie and my WiFi calling still working fine.
Updated 10/22
My WiFi stopped working again after I turned it off but I can't turn it back on just like before. Any time I tried to turn it on the phone app forced close.

Considering thanks to T-Mobile's wonderful coverage (says I have good signal strength, but it's not) I have Wi-Fi calling enabled all the time and it works well on the 5Ghz ac side of the router...not so well on the 2.4Ghz b/g which is fine. Again something carrier specific. I went to Pie and kept the WiFi calling running.

Caltinpla said:
I have the same issue. It was working fine on Oreo. I tried flash.all fastboot using the stock firmware without success. Let me know if you have a solution. Ty
Edit: I got it fixed by flashing flashall back to stock Oreo 8.1 open market from Essential website then let it updated OTA to Pie and my WiFi calling still working fine.
Updated 10/22
My WiFi stopped working again after I turned it off but I can't turn it back on just like before. Any time I tried to turn it on the phone app forced close.
Click to expand...
Click to collapse
Updated 11/5
Surprisingly, my WiFi calling is now working after updated my phone to today's November security update.

GSI LTE Fix

I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script

Any chance it solves LTE problems with stock OS as well?

Renovatio33 said:
Any chance it solves LTE problems with stock OS as well?
Click to expand...
Click to collapse
IDK about what problems your talking about, but it definitely won't as the stock OS already has the necessary ims.apk.

In my case, even after installing this, (I use verizon) it won't even detect the sim no matter what rom I use...

CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
So are you able to receive text messages on LTE now?

Tredah212 said:
So are you able to receive text messages on LTE now?
Click to expand...
Click to collapse
Yes, I'll usually have to reboot and it starts working properly

I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.

Reznor7 said:
I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.
Click to expand...
Click to collapse
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?

jal3223 said:
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?
Click to expand...
Click to collapse
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.

Does anyone have the knowledge to make a Magisk Module making these changes? It would make it much easier to switch between different builds to test.

CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks

DarkestSpawn said:
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks
Click to expand...
Click to collapse
I have yet to get an Android 10 rom to work on my phone AND my phone is currently out for repairs, so I haven't been able to test it for Android 10.

CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR

My carrier just enabled VoLTE for me today and I gave it a try.
While VoLTE works on Havoc 2.9 with this apk, I couldn't properly hang up the phone call and I have to reboot the phone.
By the way, I'm also having the issue of being unable to access the Phone Information menu. Nothing happens after typing *#*#4636#*#* on the dialpad.
EDIT: Turned out I set the default dialer to something else (Emerald Dialer) and the system would refuse to send secret code from non-default dialer for security reasons. However, it appears third party dialers may not be able to handle such codes correctly as when I typed the code on Emerald Dialer, it crashed. I set the system default dealer back to the stock one and now I could enter the Phone Information menu.
However, I'm yet to figure out what might have caused VoLTE to get stuck when hanging up...

Reznor7 said:
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.
Click to expand...
Click to collapse
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem

GalacticGLI said:
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem
Click to expand...
Click to collapse
I could never get Verizon to work at all on any Gsi. Have you gotten it to work on 9.0 Gsi roms?

I'm running Havoc (latest Pie version)
For the first 2-3 minutes after boot, I see 'Verizon 4G' as my carrier info. After that, the signal in the status bar changes to have a little x on it, and all branding disappears. It says No Service and Emergency Calls Only.
I'm not sure what I'm doing wrong

rrusek said:
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR
Click to expand...
Click to collapse
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.

Straum said:
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.
Click to expand...
Click to collapse
Has anyone figured out the sms issue on Q gsis yet? It's the only thing holding me back, and I'd rather avoid the Digits app.

tried to install. installed. did not change anything.
edit: tested also from phone info - no IMS menu and no buttons for enable VoLTE.

LineageOS 19.1 Issues

Hey guys, just wondering if anyone else is having weird issues with the new LineageOS 19.1 update? I upgraded from 18.1 and am having a bug where certain apps can't connect to the internet am forced to use WiFi instead of mobile data in order to use the app. I do have my mobile data turned on and check the info of the app and allow the app to connect to the internet. Was wondering if its just me and need to reformat or is there anyone else coming across this issue as well.
Build: lineage_fajita-userdebug 12 SP2A.220405.004 ba65ac2b7e
Status update: I reformatted the phone the issue still persist.

MRRAGEXXX said:
Hey guys, just wondering if anyone else is having weird issues with the new LineageOS 19.1 update? I upgraded from 18.1 and am having a bug where certain apps can't connect to the internet am forced to use WiFi instead of mobile data in order to use the app. I do have my mobile data turned on and check the info of the app and allow the app to connect to the internet. Was wondering if its just me and need to reformat or is there anyone else coming across this issue as well.
Build: lineage_fajita-userdebug 12 SP2A.220405.004 ba65ac2b7e
Status update: I reformatted the phone the issue still persist.
Click to expand...
Click to collapse
maybe apn settings are wrong?

Brettroth said:
maybe apn settings are wrong?
Click to expand...
Click to collapse
Nope. I checked those and they were correct. I even reset back to default to see if that would work but nothing the situation stayed the same and didn't work properly. I managed to get into contact with Metro to reactivate my sim card as well I went a little further than I should but I wanted to know if it was Metro network or my phone and still was having issues. All in all I decided to go back to stock firmware and I may try again later months to see if the issues have been fixed.
To be honest I doubt it am having way too much fun with Gpay at the moment.

MRRAGEXXX said:
Nope. I checked those and they were correct. I even reset back to default to see if that would work but nothing the situation stayed the same and didn't work properly. I managed to get into contact with Metro to reactivate my sim card as well I went a little further than I should but I wanted to know if it was Metro network or my phone and still was having issues. All in all I decided to go back to stock firmware and I may try again later months to see if the issues have been fixed.
To be honest I doubt it am having way too much fun with Gpay at the moment.
Click to expand...
Click to collapse
Could try some other roms. I've never really liked lineage much but any of severalt's new roms are great. Zero issues for me