Related
So this is the second S5 I've had and same issue. First one, people could hear me if I called, but if they called me 90% of the time they couldn't hear me on the 1st call. If they called right back or I called them it was fine, usually. I've seen a lot of complaints about this on the S5 online. I even have a copy of the my youmail voicemail that I made on my S2 that was crystal clear and more louder/pronounced if that makes sense, and the voicemail I made on my S5 was all fuzzy and kinda garbled like I was talking 4 feet away from it. Replaced with another S5, and it started happening again except now I'm rooted so no more warranty and they can't/won't do anything. Stock or rom, it happens. So I know a few S5 owners, 3 of them have the same problem. All different networks so not specific to any provider (like if it were an at&t issue etc).
I tried clearing the pin hole at the bottom but didn't seem to make a difference. People think the S5 does this maybe b/c it's water resistant and theirs a membrane inside that hole for the mic that makes it garbled. Speaker phone it works fine. Just pissing me off, I love the phone otherwise, but this is my work phone as well and it's so nice and professional to keep playing phone tag with clients .
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
fffft said:
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
Click to expand...
Click to collapse
Pry exaggerated as a bit frustrated. Away for business and on phone right now. I just googled various call issues and saw same/similar on other phones, quite a few S4 reports (like googling S5 can't hear me, or can't hear calls, or android can't hear calls etc). Again not exactly the same but similar, found older Android phones people talking about the same. S5 people I saw post in various threads on different forums, not necessarily made a thread of theirs (like they found an issue like that and bumped thread even if it was a different phone). I'm on AT&T, 3 friends one is T-Mobile and others are Verizon. Though theirs isn't near as bad as mine, theirs happens infrequently on both ends which makes me think maybe carrier related, whereas mine is almost always the caller on my end not hearing me well on the first call. I have two employees with S5s as well and no issues with theirs like this.
I don't know what user config info you want? I've rooted and flashed android for years, I hardly ever touch anything volume/call mod related. I don't know what settings you'd be talking about, stock or rom is the same (didn't install viper, didn't do anything with volume controls on DK as their borked on this version etc). Changed background noise on/off but didn't do anything.Not sure how I use the phone would do anything, they call, I answer, I call, they answer? Happens anywhere no matter signal, whether full bars at house, or office, or lose a few bars when traveling, time of day doesn't matter happens anytime. I just had a conference call where I ended having to use speaker phone for them to hear better but they still said it wasn't clear. Wife just called me and she said through the phone or speaker it's like I'm talking through a towel (speaker not as bad). My AT&T store said they've had a few people come in with complaints of call issues on their S5 but in various ways, and sometimes a factory reset worked, sometimes not. Which didn't work for me, and I blew a canister of air and use a small pin like some said they did to see if anything was clogged in the Mic port but no difference.
I'll be back in a bit, but I could try to record a call with my wife. And I'll upload the files from youmail voicemail where you can hear how loud/pronounced and clear my message is from my S2, and the garbled message from both S5's.
Think I fixed it, let's hope. So I went into safestrap, tried a few things, fix permissions etc. No difference. Restored a few times, no difference, did 3 factory resets, no difference. Each time I either message someone to call me to test, or I logged into youmail to record a new greeting and heard it fuzzy/garbly. Did one more factory reset, msg'd wife to call again, she called and first thing she said was omg it's way louder and cleaner sounding like I'm not muffled. I logged into youmail, did a new greeting and yup it's 100% normal sounding. So no clue why this worked all of a sudden with all my other tries today and before. My first S5 they tested at the AT&T store and it luckily did the issue there so they could hear what I meant and note it. They gave me a loaner and it was sent in, and I guess luckily it was reproducing that same issue when it was checked as they did a replacement since the phone was only 2 months old. And now that I think about it I doubt the tech or whomever was checking it out sat there and did multiple restores/resets like I did, and I guess I was really lucky they didn't get it and test only to have it operate normal like the 10% of the time or whatever it did.
Being rooted now sending in was pointless, as knowing people over the years that have even if sent with stock rom, warranty was denied. F'd up thing is they have to prove rooting caused the issue, I don't have the time nor want to deal with that crap. Example I love cars/trucks and mod everything we have, and with the Magnuson-Moss Act they have to prove your "mod" directly affected the failed part/problem. In the phone world you end up just getting transferred around and dealing with crap trying to sort that out. I have one of my cars modded (ctsv) with pulley swap, full exhaust with lt headers etc, custom tune yada yada, one of my trucks has custom tune/intake/headers/no cats/custom exhaust etc and neither had problems with getting warranty work done, b/c doing a custom tune and pulley etc isn't going to make your radio or nav fail. In the phone world on the other hand they'll tell you to pound sand, root and mic fails, oh that'll be our diagnostic fee part replacement $ have a nice day. lol
i'll try to upload audio files from youmail showing the sound quality difference when I get a chance. I know one of my friends tried a factory reset and didn't work. Guess I'll tell him and the other two to keep doing resets over and over till it works lol, whether that means 5 or 10 times. Why it didn't work on the 1st or even 2nd try is beyond me
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Sent from my XT1575 using Tapatalk
Same issue here ! immediately after MM OTA update on my XT1575 (stock vanilla) people start complaining they cannot hear me well !
After sorting most of MM issues this is a major pain in the a**
Let Moto know about this as it makes the phone crippled.
How come there aren't any more complaints about this serious issue !
This is 100% MM related - People complain they can barely hear me on the other end of the line - I sound muffled, stuttered and basically bad to the point they cannot continue the conversation and demand I call them from a land line !
Forget all MM bugs, problems, etc (need I mention the Equalizer went AWOL) now this Smartphone which I highly praised and loved became a ...smart something - with no phone feature.
Help me let Moto support be aware of this issue.
Thanks
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
alon3232 said:
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
Click to expand...
Click to collapse
Did all that on a call to Motorola after the first replacement phone failed to address my issue. No surprise, it made no difference.
That was followed by a factory reset and a test prior to connecting to my Google account and downloading any apps. Also, made no difference.
Now I'm waiting for my second replacement.
Sent from my XT1575 using Tapatalk
I have a thread on the Motorola forums for this issue.
My second replacement arrived yesterday. It solved the background noise issue! Unfortunately it came with loose buttons which actually rattled when shook or when the phone vibrated. Back to Amazon it goes.
Unfortunately, now Amazon wants to pull the plug on the purchase and take it all back. I'm not ready to give up though. Besides really liking the phone, I've also invested in a screen protector and car mount. I'll have to talk to Amazon today and see what we can do.
Sent from my XT1575 using Tapatalk
It's all boxed up and ready for UPS. I'm really unhappy that I could not get a good MXPE. As I consider other options, it's tough, especially at the $350 price point.
I'm actually giving the ZTE Axon Pro some thought, but undecided so far. And if the was a sale on the Nexus 6P that brought it down $100, it would be a contender. I'll pay a few more bucks for a Nexus. Given the right price, I may even give the MXPE anther shot, after they work through this stock of bad phones.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Don't get the axon. If you can't get the. 6p I'd go with Nexus 6 some places U can get it under 3 I think
Sent from my XT1575 using Tapatalk
Solved
Hi guys ive got the solution to this problem, my mic used to not work at all on handset calls and wud work on speakerphone. After diagnosing for 24 hrs I was able to understand the problem, all you need to do is replace top mics with bottom mics in music_path.html file If someone is not able to do it lemme know on twitter ill email u my edited file, just replace yours with mine. N nw the mic works like a charm. I am not a regular xda user, so won't be able to check back frequently, my twitter id is @smartphoniac
Have seen ppl replacing motherboards and phones in service center, also some use it on Bluetooth or handsfree, trust me its nt needed just do what i wrote above and issue is solved, if u r a noobie tweet me ill email u my file so that u will have to do jst the copy pasting and this painful issue will be gone forever.
Edit: This will also solve the problem if caller gets his own voice as echo. After this editing even that issue will be solved
Hi guys,
I've just bought a Moto X Style and I'm having the same problem as the original poster - constant background noise (kinda buzzing/hissing) during phone calls, coming through the upper speaker:
jswclw said:
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Click to expand...
Click to collapse
So far I've tried booting into safe mode, wipe data/factory reset, different carrier/SIM card - no difference.
I'm running Android 6.0.1 and I upgraded right after I bought the phone, so cannot tell if the problem existed on Android 5.
However - and this is my question - since you claim that it's a software thing and Marshmallow-related, is there anyone who tried flashing a Nougat ROM and has it helped? I don't know if I should try and get a replacement phone (especially that some people had the same issue on 2-3 consecutive phones) or just wait for the Nougat update, assuming that it helps.
Thanks for advice!
Hi, it's me again - just wanted to tell you that I've flashed the 7.1.1. AICP ROM and the background noise is still there while calling Is it really a software issue? So many people say it appeared after MM upgrade and there were no problems on Lollipop, but maybe my speaker/mic is simply broken? Is there any ROM you can flash to get rid of this issue? All help is really appreciated! :good:
I'm not a developer or support any ROMs I just like spreading the good word and helping people when I can. I'm not responsible if your device breaks or you lose data. So make a TWRP backup if you are worried.
This is not a perfect method and it needs improvement so if we can work together and try to fix the issues maybe we can get full support from the OPs' of the note 7 ports.
You must be on MM bootloader, unlocked, rooted, with most recent version of TWRP to ensure everything goes smoothly.
Download most recent Ram Kernel for Verizon:
https://forum.xda-developers.com/note-4/orig-development/kernel-ramkernel-t3472138
Download aurora Verizon data fix:
https://forum.xda-developers.com/showpost.php?p=69066109&postcount=2681
Find a Note 7/S8 ROM that you want to try on the snapdragon note 4 thread:
https://forum.xda-developers.com/note-4/snapdragon-dev
1. Clean install desired ROM (wipe everything 3 times except SD card)
2. Flash datafix
3. Flash kernel
4. Wipe caches and boot into ROM
5. Play around with your new phone lol
If you do not have root for whatever reason download the su zip from nseven thread and flash it in recovery.
https://forum.xda-developers.com/note-4-verizon/development/note-4-grace-7-t3434155
These ROMs do not support Verizon apps including visual VM and MyVerizon. They also don't support Wi-Fi calling. Check the bugs of the ROM so you know what to expect.
If you are having issues check the original ROM thread for answers or post a question on here and maybe somebody can help.
The bugs that I know so far that are Verizon specific across all ROMs:
- MMS does not work on the stock messenger (*See below for fix)
- Phone FC when the person on the other end hangs up first (really want to figure this one out)
- Texts are sometimes delayed for some reason
Some ROMs might require you flash gapps for some reason so follow the op instructions for the ROM you choose, just ignore any modem or bootloader flashing instructions.
I've tried Norma ROM and Racerom. I've had the best experience with Racerom but that is just my personal preference. Any questions please ask.
Cheers!
Thanks to @chevyrhoads for all his time and effort on nseven. I cannot thank you enough sir! And thanks to all the other developers sharing these great roms, data fix, and kernel for everyone to enjoy.
MMS Fix:
1. Extract others.xml from nseven ROM found in system/csc folder and save it to your SD.
2. Edit the others.xml file and delete everything within the <FeatureSet> tags.
3. Paste this feature within the <featureset> tags:
<CscFeature_Message_ConfigMmsMdnTagName>X-VzW-MDN</CscFeature_Message_ConfigMmsMdnTagName>
and save the changes.
4. Paste the others.xml file in your current ROMs system/csc folder (In my case there was no others.xml file to swap or replace) and change the permissions of the file to 644 and reboot.
5. You should now be able to send MMS on the stock messenger app !
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Sorry for not responded sooner
derSA7 said:
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
Click to expand...
Click to collapse
I guess that ROM does not work with this setup I'm sorry.
jBMWguy said:
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
Click to expand...
Click to collapse
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
bishop0114 said:
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Click to expand...
Click to collapse
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
jcip17 said:
Sorry for not responded sooner
I guess that ROM does not work with this setup I'm sorry.
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Replied to the OP instead of editing it. Disregard this post lol.
jcip17 said:
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
That sounds great, referring to the CSC! I'll put you on the Alpha/Beta Testers list as soon as I can. We may be able to get together and create a universal one in all datafix using aroma installer to allow the user to "Select" the ROM they would be using. The only issue would be of there was a major platform upgrade by the developer of the ROM of their choosing, but even so, we could just have it "Null Out" as to not harm or change anything etc. Yup I've got many of these note 4"s best phone for the money IMO.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Sent from my SM-N930V using Tapatalk
jcip17 said:
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Click to expand...
Click to collapse
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
jafferkhan said:
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
Click to expand...
Click to collapse
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Sent from my SM-N930V using Tapatalk
jcip17 said:
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Click to expand...
Click to collapse
That's a great analysis bro. Thanks for the feedback I really appreciate it. Kyubi is the best Rom for this phone period. I've tried all of them except nseven but kept coming back to kyubi because of its stability. It's fast, smooth and very good on battery. I missed the note 5 themes which I get here plus the theme store and more. I think kyubi is more of what a stock Rom should have been. I know it's developer is very good, everything works flawlessly, I've had zero issues on it since its almost 9 months that I've been using it. Close your eyes and flash it, it's that good!
Testing....
Sent from my SM-N930V using Tapatalk
I'm on Verizon now and if I get another VZW N4 I'll build a proper N7 or S8 rom with everything working as it should. other than Iris scanner and fingerprint scanner.
But just know that these international port Roms are not setup for the CDMA networks so they will not work right. Even these "fixes" are only partial things that are missing and there's more smali framework edits needed to make them work right. The best option is to build a Rom using the actual VZW software and this will solve most all of these issues. Been there done that with my UN5 and UN7 Roms. I have the S7 edge now but to be honest I'd much rather go back to the N4 running my ported N7 rom so I can have my IR blaster and removable battery. The N4 is the best phone in my opinion.
note 4 is died and is a new way to do this fast and easy
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!
I recently moved to the 6T from a 3XL because of several hardware issues with that device. So far this device has been a beast. After spending about a week with it, I have a few questions I'm hoping some of you can answer for me!
1. I noticed the lock screen reverts night light if enabled, so the fingerprint scanner can work efficiently. Just wondering if there is any way night light can remain on during the lock screen/fingerprint scan? Or is this impossible because will it impact success rate of fingerprint unlocks?
2. Because of the lack of fingerprint scanner on custom ROMs, I've decided to stay on OOS. This is a long shot but is there any way Substratum overlays can be shown without having to reboot? It's a bit of a hassle to build and update overlays, reboot, apply them, and reboot for full changes to take effect.
3. I don't know if this one is by design, but I noticed my display will wake during calls - if the lift to wake display option is enabled. Anyone else have this issue and know of a fix (other than disabling lift to wake)?
4. My notification bar is tough to pull down while I'm in a call. The only way to get it down is if I drag my finger almost all the way down the screen. Is this also by design?
5. Another call-related issue - sometimes people will tell me they can hear their own voice during a call. Has anyone else experienced this?
6. I'm in Canada with Fido, and OnePlus ensured me VoLTE and VoWiFi will both be an option for me since the device is "globally unified". I'm not seeing any VoLTE icon during calls. I've tried the dialer key combo and enabling VoLTE there, as well as the VoEnabler Magisk Module. Neither of those seem to result in a VoLTE icon. Could anyone confirm if it's just not possible with Fido in Canada, or maybe another solution is out there?
7. This one seems a bit more widespread - some apps using the wrong mic during audio/video records. I've only experienced this in making a video in WhatsApp so far, and I'm wondering if anyone knows of a fix? Or do we just need to wait for OnePlus to come out with an update? Or, do the apps themselves need to be updated to better work with the 6T?
I apologize for so many questions, but if any of you could even answer some, if not all of these questions, I would greatly appreciate it! And I also apologize if some of these questions have already been addressed in previous threads.
Interesting post... Will subscribe because I have experienced some of the issues mentioned. I am also on my first week of use.
Sent from my ONEPLUS A6013 using Tapatalk
@rickysidhu_
1. I'm pretty sure this is by design and it's supposed to be that way. When there were early builds of Havoc for the 6T, some users got FP to work on an all white background with the brightness all the way up. So I'm assuming it's so it can read your fingerprint.
2. Sadly, not that I know of. Swift Installer is the same way. Apply overlays, reboot, reboot again to finish themeing.
3. Due to the notch being a teardrop design, there's little space to pack every sensor into the notch. Happens to me all the time when on a call. I'm pretty sure it's because of the proximity sensor. Once you move the phone from your face just a tad, the screen kicks on. No fix that I know of, yet.
4. Again, proximity sensor I'm assuming. Haven't really tested this too extensively mainly because if I have to use my phone for anything while in a call, I'll put it on speakerphone and use it.
5. I haven't heard anything from the other person. However, I do sometimes hear myself like an echo when talking to someone.
6. I have the T-Mobile variant of the device and immediately switched to International firmware as soon as I got the device, can't remember if it showed those icons or not when I was running the T-Mobile branded software, I do have VoLTE and VoWiFi icons on International firmware.
7. Haven't had this issue since I don't use WhatsApp. I do not seem to have the problem when making calls via Facebook Messenger. It's a known problem since the 6 and OnePlus knows about it, they just haven't issued a fix yet. Sorry I can't be more help with this.
GLHF.
TheKnux said:
@rickysidhu_
1. I'm pretty sure this is by design and it's supposed to be that way. When there were early builds of Havoc for the 6T, some users got FP to work on an all white background with the brightness all the way up. So I'm assuming it's so it can read your fingerprint.
2. Sadly, not that I know of. Swift Installer is the same way. Apply overlays, reboot, reboot again to finish themeing.
3. Due to the notch being a teardrop design, there's little space to pack every sensor into the notch. Happens to me all the time when on a call. I'm pretty sure it's because of the proximity sensor. Once you move the phone from your face just a tad, the screen kicks on. No fix that I know of, yet.
4. Again, proximity sensor I'm assuming. Haven't really tested this too extensively mainly because if I have to use my phone for anything while in a call, I'll put it on speakerphone and use it.
5. I haven't heard anything from the other person. However, I do sometimes hear myself like an echo when talking to someone.
6. I have the T-Mobile variant of the device and immediately switched to International firmware as soon as I got the device, can't remember if it showed those icons or not when I was running the T-Mobile branded software, I do have VoLTE and VoWiFi icons on International firmware.
7. Haven't had this issue since I don't use WhatsApp. I do not seem to have the problem when making calls via Facebook Messenger. It's a known problem since the 6 and OnePlus knows about it, they just haven't issued a fix yet. Sorry I can't be more help with this.
GLHF.
Click to expand...
Click to collapse
I really appreciate you taking the time to reply to all my questions! Very kind of you.
As for the VoLTE stuff, maybe I'll continue to do more digging since you say you're seeing the icon but I'm not. That tells me VoLTE is not properly enabled on my device (I assume). Thanks again, much appreciated :highfive:
I can't find it, but there are several threads on enabling VoLTE & VoWIFI.
One involves entering the hidden menu, via *#808#, then toggling the appropriate settings.
That's what I did (USA version). I was on the 9.07 firmware, which didn't support it, but VoLTE
popped up and started working, when the 9.11 version hit.
rickysidhu_ said:
I really appreciate you taking the time to reply to all my questions! Very kind of you.
As for the VoLTE stuff, maybe I'll continue to do more digging since you say you're saying the icon but I'm not. That tells me VoLTE is not properly enabled on my device (I assume). Thanks again, much appreciated :highfive:
Click to expand...
Click to collapse
You are very welcome. You may want to try using the MSM Tool found here. https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307
That's should fix some problems you may be having, especially the VoLTE and VoWiFi issues. I know you're not using the T-Mobile version of the phone, so I'm not sure if this will help you much or not, but a MSM Tool that's meant for your device should work.
OP, I have enabled volte on op6t on Rogers. Fido should work, too. It seems nobody enables WiFi calling on op6t in Canada.
https://forum.xda-developers.com/on...-volte-vowifi-german-carriers-t3817542/page75
Sent from my SM-G935W8 using Tapatalk
p51d007 said:
I can't find it, but there are several threads on enabling VoLTE & VoWIFI.
One involves entering the hidden menu, via *#808#, then toggling the appropriate settings.
That's what I did (USA version). I was on the 9.07 firmware, which didn't support it, but VoLTE
popped up and started working, when the 9.11 version hit.
Click to expand...
Click to collapse
ma678 said:
OP, I have enabled volte on op6t on Rogers. Fido should work, too. It seems nobody enables WiFi calling on op6t in Canada.
https://forum.xda-developers.com/on...-volte-vowifi-german-carriers-t3817542/page75
Click to expand...
Click to collapse
Gave both of these a try and still don't see the volte icon. It's hard to tell if it's enabled even though the icon isn't showing.
I appreciate both your guys' responses though! I didn't know about these additional menus!!
I have the T-Mobile version on T-Mobile and also don't see the VOLTE icon, but if I go to Settings/About Phone/SIM Status, it shows Mobile voice network type LTE. I assume that means VOLTE is enabled.
Telyx said:
I have the T-Mobile version on T-Mobile and also don't see the VOLTE icon, but if I go to Settings/About Phone/SIM Status, it shows Mobile voice network type LTE. I assume that means VOLTE is enabled.
Click to expand...
Click to collapse
I'm in the US and I have TMobile as my carrier, and both of VoLTE/VoWiFi enabled by default
Looks like you have the International version of the OP6T. My T-Mobile version doesn't have the Enhanced Communications section in Settings/Wi-Fi & internet/SIM & network and I don't see an Icon Manager screen anywhere either, though I have the WiFi Calling switch.
Telyx said:
Looks like you have the International version of the OP6T. My T-Mobile version doesn't have the Enhanced Communications section in Settings/Wi-Fi & internet/SIM & network and I don't see an Icon Manager screen anywhere either, though I have the WiFi Calling switch.
Click to expand...
Click to collapse
Mine is TMobile version but I converted it to OOS using this tool: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 in case you're interested.
I've read about that but after rooting/custom ROMing just about every Android device I've ever had (up to the ZTE Blade V8 Pro, anyway), I just don't have the inclination to do it with this phone. Everything works and VoLTE is enabled by default, so I'm fine with that.
I've tried to enable as much as I could (full port switch, VoLTE provisioning, enabled in settings) and still don't see the icon.
Very strange and at this point I'm almost prepared to just accept I won't see that icon lol
Telyx said:
I've read about that but after rooting/custom ROMing just about every Android device I've ever had (up to the ZTE Blade V8 Pro, anyway), I just don't have the inclination to do it with this phone. Everything works and VoLTE is enabled by default, so I'm fine with that.
Click to expand...
Click to collapse
I hear ya! I quit rooting since I got the Essential phone. Android stock rom now a days much better so I don't need root either. I just converted this phone so I can use the dual SIM cards and faster updates rather than waiting for TMO.
After making some videos via WhatsApp and Snapchat, my question #7 is starting to become a bigger issue than enabling VoLTE/WiFi
It's very obvious the wrong mic is being used during video records because the audio just sounds terrible.
Seems like a widespread issue since there are many articles about it. Is there any known fix out there for us rooted users?