Will custom ROMs ever be sorted for this phone? - ZTE Axon 7 Questions & Answers

I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?

I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.

ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.

I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.

Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...

Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...

ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.

Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.

Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.

Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.

piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.

Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.

Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.

piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.

Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )

Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital

Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.

rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.

supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!

Related

Bluetooth Headset w/Media & Phone enabled.

I have been searching for an answer to this for two weeks with no success. I apologize in advance if the question has already been answered… I couldn't find it.
On Sprint's Hero, when setting up a headset (in my case the car radio BT adapter) one can enable both Phone and Media. Supposedly, this should allow a user to listen to tunes/podcasts/Sprint Nav and be able to use the phone when needed through the BT. Unfortunately, it doesn't work this way.
If I'm listening to something on the phone and wish to place a call, I will enter the contact and start the call. The phone responds by pausing the audio program I'm listening to as it should, but I get NO AUDIO from the phone! Nothing! The call is placed and the recipient hears nothing also!
Now; If I'm listening to something and a call comes in, again, as would be expected, the audio program gets paused and the phone rings through the BT. Unfortunately, there is no auto-answer in Android 1.5 (grrr!), so I reach over and press the Answer button. Lo and behold, it answers! but over the phone's speaker and mike instead of the BT!
They refused to accept that it was a problem with the phone at Sprint. Is this fixable? Can I look forward to it working in Android 2.1? Is there anyone else experiencing this problem?
As far as I have read/heard its a known issue that I think one of the roms here may have corrected. I will look around and see if I can find the thread, its been more than a month since I read it. Maybe MoDaCo but again, I will have to track it down.
EDIT:
Personally I wouldn't look towards anything in android 2.1, sprints release could be as far as 6 months away.
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Las_Vegas said:
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Click to expand...
Click to collapse
So maybe no one fixed lol

[Q] Notification halts music playback

So I've searched using "keywords" and scoured through many similar posts on this issue within the forum and through Google with no luck, so I'm posting this request now.
Is there any way to prevent a new message/text notification sound from halting music playback?
I hook up my phone to the car to blast the music but when I get a text, it stops/halts/pauses the song, plays the notify sound, and then resumes playback.
I don't want to turn off the notifications all the way, I just want to have the notify sound play OVER or ON-TOP of the music playback
The phone is still running just the stock rom, but if you guys suggest an app or rooting, then I will do whatever it takes, thanks!
This is part of MOST phones. My phone does it, the G1 does it, my friends BB does it.
thanks fenixnr....so is there nothing that can be done to correct this on an Android device?
I know in the past I've had Windows Mobile devices with the same issue (Xperia X1) and some of the ROMs I flashed on it corrected the issue while others did not. My HD2 doesn't have this problem and it has a dedicated 3.5mm headphone jack too.
Am I the only one who has noticed this
I was hoping someone else would have wanted the same thing resolved.
solarleox said:
thanks fenixnr....so is there nothing that can be done to correct this on an Android device?
I know in the past I've had Windows Mobile devices with the same issue (Xperia X1) and some of the ROMs I flashed on it corrected the issue while others did not. My HD2 doesn't have this problem and it has a dedicated 3.5mm headphone jack too.
Am I the only one who has noticed this
I was hoping someone else would have wanted the same thing resolved.
Click to expand...
Click to collapse
There is nothing to "resolve" as I am pretty sure that is by design how it should work. I cannot test this now, but try putting your phone into a silent mode when listening to your music... Of course, keep your media volume up for your music.
If memory serves me right I think that cm kanged expresso rom had the feature to play notification out of the speaker when headphones were plugged in. Cm6 might have that feature too. I'm not sure though.
Sent from my MR1 V4 Remix 3G using XDA App
slinky1914 said:
If memory serves me right I think that cm kanged expresso rom had the feature to play notification out of the speaker when headphones were plugged in. Cm6 might have that feature too. I'm not sure though.
Sent from my MR1 V4 Remix 3G using XDA App
Click to expand...
Click to collapse
So CyanogenMod-6 might have improved on this? [http://forum.xda-developers.com/showthread.php?t=755118&highlight=kanged]
Sounds exactly like what I was looking for and this is a Froyo build too? Thanks slinky, I'll give it a shot!
solarleox said:
thanks fenixnr....so is there nothing that can be done to correct this on an Android device?
I know in the past I've had Windows Mobile devices with the same issue (Xperia X1) and some of the ROMs I flashed on it corrected the issue while others did not. My HD2 doesn't have this problem and it has a dedicated 3.5mm headphone jack too.
Am I the only one who has noticed this
I was hoping someone else would have wanted the same thing resolved.
Click to expand...
Click to collapse
honestly if its only a problem when you plug your phone into the car, just put your phone on vibrate or turn the notification off.
Yeah this is honestly the one thing buggin' me right now.
I walk to work it's about a half hour walk to and from and I don't give a damn about my notifications during that time. Hah.

ED12 Thanks and Questions

First and foremost to everybody over at ACS thank you for bringing Gingerbread to my Epic. For the most part I have a fairly bug free, fully functioning installation.
I did want to mention a couple of things:
- I am getting an interruption in charging (I know this was a known bug)
- I have fully functioning GPS (I got a lock in GPS Status right before I did the install, left GPS on, shut the phone down and did the install, when my phone booted up after the install I turned on GPS and got a lock right away!)
- My voicemail won't verify! (I can still receive voicemail, I just don't get the voicemail-to-text to work) Plus, my voicemail icon in the notification bar NEVER goes away! (Hoping there might be a fix for that coming soon)
- ED12 does something absolutely no ROM I have had does... I listen to Pandora in my car with an auxilary cable plugged into the headphone jack. I also have my bluetooth headset paired and connected. In the past, whenever I received a phone call or wanted to make a phone call I had to unplug the auxilary cable in order for the phone to route call audio to my headset... NOT THE CASE ANYMORE!!! In a very awesome twist all call audio automatically routes to the bluetooth! Also, amazing bluetooth compatability with Google voice, Voice Search, etc.
So, all in all, Gingerbread has made me totally happy! I am sorry that I put this in the General forum apparently I am too new to post on Development pages so I understand if this gets moved.
Curious, when do you think we will start seeing ROMs and Bug Fixes for ED12?
Also, I saw that Jez2cool's thread with the tar version, however the link to the file was dead (just came up with a Dropbox error page), will there be a flashable version for me to Odin coming soon? Will that version fix some of the issues I am seeing on the version I have installed through CWM?
Once again to the whole team at ACS thank you!
I will be looking forward to further development!
Larry
Samsung Epic 4g
ED12 - ACS-Leaky Gingerbread
There wont be any bug fixes for ed12. It will just be another rom that samsung will make. Its just a test build. Hopefully we can get another leak when another version comes out. Also the tar and flashable version thru recovery is the same thing.
Sent From My Evo Killer!
lldolendi said:
- ED12 does something absolutely no ROM I have had does... I listen to Pandora in my car with an auxilary cable plugged into the headphone jack. I also have my bluetooth headset paired and connected. In the past, whenever I received a phone call or wanted to make a phone call I had to unplug the auxilary cable in order for the phone to route call audio to my headset... NOT THE CASE ANYMORE!!! In a very awesome twist all call audio automatically routes to the bluetooth! Also, amazing bluetooth compatability with Google voice, Voice Search, etc.
Click to expand...
Click to collapse
I know an IRC channel that will love to hear that. Everyone has been complaining about that issue since the beginning of the Epic.
Whosdaman said:
I know an IRC channel that will love to hear that. Everyone has been complaining about that issue since the beginning of the Epic.
Click to expand...
Click to collapse
I know!
It's actually so unbelievable that I think Samsung just hasn't overwritten that part of the code yet in attaching their skin to GB...
We probably won't be seeing a TAR to Odin since that file is off-limits until Sprint releases it to the public.
bertm13 said:
We probably won't be seeing a TAR to Odin since that file is off-limits until Sprint releases it to the public.
Click to expand...
Click to collapse
I think ACS just released that too. Same problems as their ROM though. So better off flashing the EC05 modem back. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1056411
Ive never had that issue with the aux plug with calls pandora games nithing sins 2.1
So I had a my Modem crash yesterday... First time that has ever happened to me. Anybody else get that yet?
Also, the date on my lock screen is cut off...
lldolendi said:
So I had a my Modem crash yesterday... First time that has ever happened to me. Anybody else get that yet?
Also, the date on my lock screen is cut off...
Click to expand...
Click to collapse
The lock screen date is a universal problem, not just ED12.
its a alot of bugs they dont say about this rom
I'm running gingerbread ED12 stock ROM right now for the first time. My first impressions are "Amazing." This ROM seems like it is the direct port from the Nexus S with TouchWiz on top of it. Everything seems to be working...I know people said they are having a lot of problems, but I haven't seen any too major ones. My battery meter is fine, GPS is working, and the phone isnt crashing.
WiMax doesn't work, which I assumed. And the lockscreen has the date cutoff like every other ROM in May. That's a problem with Samsung's TouchWiz that they need to fix.
EDIT: And again the "Time Without Signal" issue is still here. I wish they would fix that
gingerbread was way cool, but the thing main that stopped me from running it full time was the fact that visual voicemail wasn't working. Couldn't download vm's and wanted me to call the vm service like I was on a dumb phone. Eff that
There were some other minor bugs that I was willing to put up with, like not waking the phone when the keyboard is opened and only having the CRT power off animation but not [/i]on[/i]
Then there are the things that samsung/sprint seem entirely unwilling to fix like the date on lockscreen and whatever it is that causes google sky maps to always point at the southern hemisphere.
still, I was willing to forgive all that for HALF of the badass CRT animation.. it was THAT cool imo, but i just couldn't deal with calling to get voicemails LOL
Just use Google voice dude its better
Sent from my SPH-D700 using XDA Premium App
MaxPatlick said:
gingerbread was way cool, but the thing main that stopped me from running it full time was the fact that visual voicemail wasn't working. Couldn't download vm's and wanted me to call the vm service like I was on a dumb phone. Eff that
There were some other minor bugs that I was willing to put up with, like not waking the phone when the keyboard is opened and only having the CRT power off animation but not [/i]on[/i]
Then there are the things that samsung/sprint seem entirely unwilling to fix like the date on lockscreen and whatever it is that causes google sky maps to always point at the southern hemisphere.
still, I was willing to forgive all that for HALF of the badass CRT animation.. it was THAT cool imo, but i just couldn't deal with calling to get voicemails LOL
Click to expand...
Click to collapse
That's a problem with the Sprint data being uploaded. It seems the 3G uploading is borked as well. You can test it with "SpeedTest.net" app

Crackling sound on AOSP Rom

Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Alan_Hill said:
Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Click to expand...
Click to collapse
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
jakhan86 said:
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
Click to expand...
Click to collapse
But mine work with Samsung based rom without any issue like this one .
You tried a few AOSP roms, well ain't that cute.
But not once did you read the first posts or a few last posts of the rom thread. If you would, I'm sure you'd found at least a hint on this bug.
And do learn how to Google search !
Sent from my N9005
Had the same problem too, this issue is for all AOSP roms as I see .. but after some restart and charges he go away .. No worries to have man
Same problem. Been having it ever since I installed cm12.1. Most sounds work like they should, but certain apps only crackle. Like, my gf got a vanilla note3,and we both have the game "just get 10". To her, the sound is as it should be. To me it's horrible.
I've been using it ever since the unofficial ports, and been updating nightlies ever since. The problem still persist. If this could be fixed, it would be amazing!
I've also tried the equalizer ports of dsp mamager and audiofx, but no changes whatever I do.
Headphones, and Bluetooth headset works fine.
I too have experienced that allot. And have noticed that it occurs mostly when you use different sound drivers. Like if even on TW you flash beats audio mod or maxx audio you can hear the same crackling.
I suggest you use temasek rom. Its a solid and very stable one.
Hey thanks man, I'll do that
Edit, I've done did it and now everything works flawlessly. It's also a great rom, good battery. Thanks man.
This problem exists in all AOSP based ROMs and after some research I found the solution:
Go to settings -> apps manager -> select google app -> permissions -> disable the microphone permission.
Done
Worked on Galaxy S7 Edge

What are the pros and cons of using Lineage OS over Oxygen OS?

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.

Categories

Resources