So I've had my OP6T for several months now and I've really enjoyed it and been impressed with it.
For the majority of the time I've used AEX as my custom rom. I always pick a rom with signature spoofing support so I can use microg. Also, my service provider is Verizon.
I finally decided after several months with AEX as my daily driver, I wanted a rom that is more up to date but I'm not really ready to update from 9 to 10. So I decided to flash The Skydragon rom. I flashed it super easy but could not make calls nor send texts. The entire time I used AEX, it made calls and sent SMS/MMS just fine. After I installed Skydragon I called Verizon and spent 2 hours on the phone with various tech specialists and in the end they said from their end everything looked like it should be working. They never got it making calls and sending/receiving texts.
It said out of service in the settings. I ended up switching back to AEX and as soon as I did, it began working properly again. I even tried to make calls and texts on my OP6T when it was 100% stock and it will not work
I wonder if it's because I was on AEX when I originally called Verizon last year and set it up? Am I correct in assuming that, each time I flash a different rom, my phone will appear to Verizon as a brand new phone? I couldn't get it to work on stock nor Skydragon but when I switch back to AEX it works as it's supposed to.
TRexombo said:
AEX it works as it's supposed to.
Click to expand...
Click to collapse
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
pbergonzi said:
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
Click to expand...
Click to collapse
My phone is international/unbranded. I'm not sure if the Roms were unmodified. I know AEX works and when I tried Skydragon I worked on it for close to 2 days trying to make it work. One of the options within the Skydragon settings was that I can choose the exact network to use. I chose LTE. After choosing LTE, in the settings it shows my phone number and my provider as Verizon but it says out of service under service state. The Verizon representatives told me on their end it shows that I am CDMAless and they did not have a solution.
I noticed in the Skydragon thread that some people were successful in getting their OP6T to work with Verizon but at least one other XDA member said he had no service.
Also, as I was in the process of switching back to AEX, I first went back to stock and booted up in stock and tried to make calls /send texts and it would not allow me to until I reflashed AEX.
What a nuisance. Since you're so familiar with flashing ROMs, maybe try some others, but I would first go back to stock again--completely back to stock, even if it means lowering your android version.
But follow the instructions very carefully--you may be in brick territory going back. I'd download the MSMTool just in case.
Good luck with whatever you do, if you don't stay on AEX.
Related
So i've tried pretty much every ROM out and wanted to post my findings with Call reception,data issues, APNs, etc and see if anyone else on Sprint has workarounds or advice on how to fix issues. On some ROMs i can get data but can't get calls/texts. On others i can get voice and data and hear people fine while on calls, but they tell me i'm breaking up constantly.
ROMs with voice and data, but poor voice delivery while on calls:
Resurrection Remix
AOKP
Turbo ROM
Temasek(i think...been awhile since i've flashed and can't remember)
Roms with data(sometimes) but cant make calls/texts:
PureNexus
DirtyUnicorn
ROMs with working data and good call quality:
AICP
Mokee
TruPureX(yes, i know it's not a custom ROM just putting it here because there are no issues with call reception or data on Sprint)
I believe if we were able to manually set APNs for some of these ROMs we could possibly correct this issue but for some reason the majority of ROMs i've flashed say "APN settings are not available for this user". Does anyone know a workaround for this issue? Please post other ROMs that i haven't commented on or other findings/workarounds
I know this is a long shot since this is an old post, but I was curious if you ever found anything on this? I had gone through a bunch of the ROMs mentioned and had the same experience. The only ROM I have had success with and has been almost flawless is Turbo. Yet I have the calling issue where everyone says I'm choppy and cut out so I am having to switch again. Everything else except TruePure I have had data issues with. LTE seems to drop and then I have nothing, it's almost like it can't hand off to 3g. Then I have no signal at all.
I'd go with the stock ROM, but that just has some horrible lag when operating. If I could pull whatever make Turbo work over to another ROM that would be great, but I've never set anything like that up.
Can it be a problem if you are using a XT1572 or XT1575? Maybe you need to be ROM specific when it comes to your device model.
This is the most annoying problem. At this point most roms I try have everything but 4g.
Ok, so typically my Google-fu is on point but I'm at a loss for finding relevant posts for my particular issue.
The issue is getting cellular data to work on the Galaxy S5 (Sprint edition), whilst using the Straight Talk carrier, while also on CM13 (snapshot). The phone was originally on Sprint, my wife just got the new Note 7 (lol - at time of the post is the day after the major announcement they'd be recalling all Note 7's), it was paid in full and as far as I can tell it is unlocked. I promptly put a new recovery on it and finished it off with CM.
I'm gonna take a moment to say something irrelevant. Oh. My. God. has rooting/custom ROM/bootloading improved over the years. Maybe it's the fact I finally have a device that was popular enough to have a real big community that worked on it, or what, but everything went SO much smoother than any experiences I've had putting custom roms on devices (then again, the fact that my other devices were always Verizon phones or Chinese tablets probably has something to do with it too). The only hiccup was recompiling an updated executable through a *nix shell. Anyways, back to the point.
I have LTE data working on stock ROM (backed it up before flashing to CM). When I switch to CM, I get working voice/text, but without all the data stuffs. What I suspect the issue may be is that the CM release that works with my phone (k1tespr) is trying to find the Sprint data network and use it. Everything works the way it should on Stock, and I've reinstalled CM multiple times now after verifying that LTE/Voice/Text works on stock, but still running into this wall when I go to use CM.
Hopefully because of the popularity of this device, and the popularity of Straight Talk BYOP's, someone figured this out!
Side Note: In the CM Cell data settings, when I go to "Select Carrier" at the bottom, it errors out, briefly rebooting the cell data settings. The error is "com.android.phone has stopped working". Looks/feels like a CM bug.
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
[email protected] said:
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
Click to expand...
Click to collapse
If you are bootloader unlocked, you can fastboot flash any radio.img you want. If you are not bootloader unlocked, no you can't. The radio.img is universal btw, not specific to a carrier.
Edit: the guide below will help you unlock the bootloader and learn fastboot if you are unfamiliar.
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk
Thanks. I will do that. I appreciate the help.
Is this a problem for other Verizon users too? If so, I just won't upgrade the radio firmware on mine either.
I would highly suspect that the problem is for everybody on Verizon especially since I replaced my device and did all this SIM card changes and things. It is very unnoticeable in that the only time you experience it or see it is if you are making a call on the new nougat radio 03.72, you will see the LTE icon disappear as soon as you make your call, regardless of whether you are on an 'HD call' or not. If you are on the older radio 03.61 that is on marshmallow, then you never experience that problem, ever, ever. Everything is perfect with that "radio." I've done a lot of testing on it, as I said, up to replacing my device, all to no avail. unless using 03.61 which is again, perfect. I wouldn't change if you can avoid it. If you do get the nougat radio though (03.72), it's a nuisance because after the majority of reboots overall, you will come up with everything normal-'looking' with the LTE icon there but when trying to make a call it will disappear and you'll have an exclamation point there until you hang up from the call and LTE comes right back. (unless you're on wifi off course in which case none of this apples). The solution if you find yourself with the 03.72 nougat radio with this happening, is to toggle airplane mode and then you're good to go until the next time you have to reboot. I always check afterwards by calling voicemail to make sure the LTE icon stays while on the call. It will disappear immediately.
I'm going to assume there is some sort of an "initial-boot-handshake" that's not taking place correctly, but DOES communicate correctly coming out of airplane mode when the device is already booted.
Regards
Edit: This may be a regional VZW issue and not a phone or baseband issue.
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
tech_head
Everything was working fine on mine with the marshmallow radio. I didn't have an issue until I updated to nougat.
Hearing what happened with yours makes me think that it's a regional Verizon thing. Hopefully they will fix soon. I'm not holding my breath because it's been about a month here in Central Kentucky
I'm glad yours is working now man.
Cheers!
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
heffe2001 said:
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
Click to expand...
Click to collapse
Best of luck. Let us know how it goes if you get the chance. Thanks!
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
bjoostema said:
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
Click to expand...
Click to collapse
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
**
As mentioned earlier in the thread, the radio is independent of the OS version, so why not take 1 or 2 minutes and flash an earlier radio? There is a radio / modem repository thread on XDA with all versions you can just grab and try out. Literally takes less than a minute and if you don't like the results, then just flash it right back. I use Fastboot, but TWRP, FF, NRT, etc. all work equally well. You may also post what you find under "Phone Settings" when typing " *#*#4636#*#* " into the dialer. Report back on your findings.
Here are the screenshot links for my phone settings.
Thanks
OP
http://forum.xda-developers.com/attachment.php?attachmentid=3882483&stc=1&d=1474502181
http://forum.xda-developers.com/attachment.php?attachmentid=3882482&stc=1&d=1474502181
tech_head said:
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
Click to expand...
Click to collapse
Are You running stock nougat now. If so, what is your simultaneous voice and data status with respect to my post.
Thanks
OP
[email protected] said:
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
Click to expand...
Click to collapse
No problem bud! I haven't flashed another radio yet either. I will report back after I test a few more things.
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
chaoticyeshua said:
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
Click to expand...
Click to collapse
It is still kind of up in the air. What I do know is that there is a software incompatibility somewhere within nougat here in Lexington, KY, at least. I assume it's the radio software but I'm not certain. I'm not bootloader unlocked at this point so I haven't yet tried to flash marshmallow radio on to stock nougat. I will probably try this in a few days when I have the time to deal with the factory reset it involves. Please refer back to the original post for questions about my reasoning.
It's quite interesting, the problem, as everything with stock nougat - voice and data-wise, works just like marshmallow after I toggle airplane mode after reboot. With marshmallow, it just worked. Very weird. But given I can just toggle airplane mode 1 time for every time I boot, it's just a slight nuisance. Once I toggle airplane mode, everything is good just like marshmallow, as if nothing was ever wrong. It could be something about the boot sequence. It's very interesting. I'm open to ideas at this point.
Thanks.
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
spjetrovic said:
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I appreciate your input. It doesn't sound like our issues are quite the same. I'm not sure though.
What is it that Verizon did for you. That may be the answer to my problems.
Thanks. Best Regsrds.
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.
I'm considering trying Lineage given the odd quirks I'm seeing with my rooted Oxygen.
What will I lose or gain by switching from Oxygen to Lineage?
Personally I like youtube vanced and, viper which I get from nolimits 12.0, I also like the native call record. So in my case, I stick to oos.
scorpio76r said:
Personally I like youtube vanced and, viper which I get from nolimits 12.0, I also like the native call record. So in my case, I stick to oos.
Click to expand...
Click to collapse
Thanks for the response. If I could resolve two quirks with OOS, I'd be happy to stay.
1. SMS/MMS database wiped at every restart. (Or is it the messages were never committed to system database?)
2. EcoBee & August use the same API or third party library to add smart home devices. They fail while all other vendors works fine. I had to add devices using a different unrooted phone.
#2 is annoying. #1 is a bigger deal.
kamiller42 said:
Thanks for the response. If I could resolve two quirks with OOS, I'd be happy to stay.
1. SMS/MMS database wiped at every restart. (Or is it the messages were never committed to system database?)
2. EcoBee & August use the same API or third party library to add smart home devices. They fail while all other vendors works fine. I had to add devices using a different unrooted phone.
#2 is annoying. #1 is a bigger deal.
Click to expand...
Click to collapse
I went from OOS to LineageOS 18.1. While I love LineageOS, I am having problems with all my calls going to Real Time Text mode after a hardware answer. I have Verizon as my carrier and this might be the issue. I cannot say for sure. There is no Google on my phone and I get along just fine without them. If I can solve this issue it would otherwise be almost perfect. My 2 cents.
joeliberty said:
I went from OOS to LineageOS 18.1. While I love LineageOS, I am having problems with all my calls going to Real Time Text mode after a hardware answer. I have Verizon as my carrier and this might be the issue. I cannot say for sure. There is no Google on my phone and I get along just fine without them. If I can solve this issue it would otherwise be almost perfect. My 2 cents.
Click to expand...
Click to collapse
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
Click to expand...
Click to collapse
Holy cow....thanks for the tip off. You don't dial 911 unless it's an emergency so I never knew. That would be complete NO NO and if I were LineageOS I would have a BIG warning to Verizon users NOT to use this. I went back to Android 10, HavocOS. Only issue I have is with MMS, but QKSMS is work around for it. I am going to place a test call to 911 now just to be sure. Thanks again.
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger de
flyoffacliff said:
I have Verizon too and same thing happens. It's a known issue with most Android 11 ROMs on this phone, except for one or two, who's developers found a workaround.
911 calls don't work either which is a bigger deal.
Click to expand...
Click to collapse
Which ROM's found a work around???
Click to expand...
Click to collapse
Pixen OS, but it's no longer supported and gave me battery issues. I think Jaguar OS has it fixed too. Not sure about pixel experience.
joeliberty said:
Holy cow....thanks for the tip off. You don't dial 911 unless it's an emergency so I never knew. That would be complete NO NO and if I were LineageOS I would have a BIG warning to Verizon users NOT to use this. I went back to Android 10, HavocOS. Only issue I have is with MMS, but QKSMS is work around for it. I am going to place a test call to 911 now just to be sure. Thanks again.
Click to expand...
Click to collapse
No problem, it could just be me but I think it's maybe related to the rtt issue. You should be fine on Android 10 based ROMs.