Hey Guys!
I got my Nexus 4 from Play Store on December 6th. I loaded it with the T mobile micro sim activation kit yesterday. When I placed a call, I couldn't hear anything and the people on the other side also could not hear anything. I have full signal.
I called customer care and they asked to wait for 24 hrs. It's 24 hours and I am still not fixed.
They asked me to reset the handset and that didn't help.
Now they say that it would be a defect.
I am able to call from apps like Skype and Groove IP.
What should I do? Should I call Google or try Att or something else?
So I called Google Play customer care. They said it is NOT a hardware problem. Would go to a T mobile store.
I have same problem! how you decided the situation?
Try a different Sim card.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Try a different Sim card.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
already tried, does not work
I got this problem after upgrading to 4.2.2 (manually flashed each individual image file). Anybody ever find a fix? Happened on both phones that I upgraded, worked fine before upgrading.
I'm on value contract btw.
I'm having this same issue after upgrading 4.2.2. I'm on the Nexus 4 with the update directly from Google and using Straight Talk.
I have another friend on the Galaxy Nexus on Straight Talk with 4.2.2 and they have had no problems with this. Hoping I don't have to downgrade to get this working again.
I`m having the same issue. Before updating to 4.2.2 the phone was fine. After that, I can`t hear anyone on the phone.
I tried to downgrade, I flashed another radio baseband as well, but this did not fix the issue.
I tried other ROMs as well....no luck
Any other suggestions ?
I noticed this today, it said dialing, but I couldn't hear a ring or anything , a few seconds later the call dropped (tmo sucks with dropped service)
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
If you aren't on .48 baseband you can't hear phone calls. Get off the old radios. Seems like they **** blocked them possibly. I just had to upgrade to .48 baseband because I couldn't hear any phone call placed on .33
Has anybody found a working solution .
It took me some pain, but I finally fixed it:
I tried normal reset (didn't work)
factory reset (didn't work)
factory boot reset (didn't work)
then I finally loaded via the sdk on command console (adb sideload) a module (latest one) downloaded from google, and that did it
I posted the fix in the big post in google groups, lets see if others catch up
Here is a fix, but it only works on 4.2.2 so you can't downgrade, also all LTE functionality will be disabled, so if you want LTE stay on 4.2.1
http://d-h.st/8Jx
Download and flash the following zip and it should work
Sent from my Nexus 4 using xda app-developers app
Related
hi guys can anyone help ...
i have nexus 4 and i had no problems on 4.2.1 but last night i updated to 4.2.2 but now i have in call problems
i cannot hear anyone or the cannot hear me ......
this only happened after the update
everything is standard and i have not rooted or flashed anything as i am not great when it comes to that stuff
i contacted google this morning and they want me to send my phone to lg for warrenty
but i said why the hardware isnt at fault as voice comand still works on google now ect so the mic isnt defective ect
if anyone can help that will be great as i am lost without it
cheers in advance
lee
gsracinguk said:
hi guys can anyone help ...
i have nexus 4 and i had no problems on 4.2.1 but last night i updated to 4.2.2 but now i have in call problems
i cannot hear anyone or the cannot hear me ......
this only happened after the update
everything is standard and i have not rooted or flashed anything as i am not great when it comes to that stuff
i contacted google this morning and they want me to send my phone to lg for warrenty
but i said why the hardware isnt at fault as voice comand still works on google now ect so the mic isnt defective ect
if anyone can help that will be great as i am lost without it
cheers in advance
lee
Click to expand...
Click to collapse
I wish I could help you. I am having the same issue. When attempting to make a call, it sometimes takes 30seconds to connect, and when/if it connects, roughly 45ish seconds into the call, it will drop. then trying to reconnect is difficult. Uhg, I love this phone, but I do occasionally need to make a call.
jc0187 said:
I wish I could help you. I am having the same issue. When attempting to make a call, it sometimes takes 30seconds to connect, and when/if it connects, roughly 45ish seconds into the call, it will drop. then trying to reconnect is difficult. Uhg, I love this phone, but I do occasionally need to make a call.
Click to expand...
Click to collapse
You guys should both re-flash the 4.2.2
Sent from my Nexus 4 using xda app-developers app
BigDig said:
You guys should both re-flash the 4.2.2
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Did this fix the issue ? I got the same issue and a permanent dull green led ?
I am having the same issue, I just updated manually to 4.2.2 from 4.2. someone help!
milesxd said:
I am having the same issue, I just updated manually to 4.2.2 from 4.2. someone help!
Click to expand...
Click to collapse
What "Baseband version" version do you have? This is a known issue when using 4.2.2 with any radio image older than .48
The culprit in this matter is not a rom issue but rather the baseband that you are on. For most people who retained to the older .33 baseband or lower have been experiencing the same issues you have encountered. If you upgrade your baseband to .48, the ability to hear calls will return by doing so. Unless you want to return to the 4.2.1 rom and use the .33 baseband.
Hey all...
i've got a simple problem on my nexus 4 running PA 3.65 ..
i keep getting a notice that says (Restricted Access Changed) and when i pull down the notification drawer it disappears right after..
it shows up every 5-10 mins, it's not really annoying but when i activate HALO .... well it is
if there is no solution to this problem then maybe someone knows the app that causes this notification so i can Black list it from HALO....
Thanks in advance :angel:
That message "restricted access changed" is it for certain app? I am running HALO and I don't see any message like that from the system or any stock app.
Sent from my Nexus 4 using Tapatalk 4 Beta
badboy47 said:
That message "restricted access changed" is it for certain app? I am running HALO and I don't see any message like that from the system or any stock app.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i think it has something to do with my carrier or network ... because when i remove the sim it doesn't show up anymore
i don't want to go through all system apps and black list them from HALO ... that would take a LONG time
Yep its your carrier. Usually happens when there is a a lot of stress on the towers and network.
Sent from my Nexus 4 using Tapatalk 4 Beta
I think it has to do with the new app lock feature on PA. It's still buggy.
Sent from my Nexus 4 using Tapatalk 2
Thanks guys you've been really helpful ... i fixed the problem by Black listing all of the apps related to phone calls and carrier network (Not sure which app exactly)
Finally a perfect rom for daily use :laugh:
Help please
HI
i have bought a new mobile and i got same error till i inserted sim card in to it.
restricted access changed
restricted access changed nexus 4 i got the same thing but mine never went away right after that i lost network calls in out text in out but data still worked not wifi data i tried 5 sims from wind rogers fido bell nothing worked tryed to get network it would not so anything im with wind canada they tryed not go its a pos i hsde to send it off to lg to be fixed
i live just in the center of Zagreb so the stressed network could be it, but the strange thing is that until a few weeks ago it happened rarely, since than i'm practically used to having that permanent notification up there
the 2nd strange thing is that I never once lost any data, calling or texting, its working perfectly only this is coming up..
i'm running a rooted HTC One International with AOKP Milestone 4.2 (July 2013 release)
I'm posting my experience in hope someone who solved it will let me know how
matijar said:
i live just in the center of Zagreb so the stressed network could be it, but the strange thing is that until a few weeks ago it happened rarely, since than i'm practically used to having that permanent notification up there
the 2nd strange thing is that I never once lost any data, calling or texting, its working perfectly only this is coming up..
i'm running a rooted HTC One International with AOKP Milestone 4.2 (July 2013 release)
I'm posting my experience in hope someone who solved it will let me know how
Click to expand...
Click to collapse
I'm getting the same issue, me too living in the same place, but i'm with an untouched, unrooted Sony Xperia Z1 (it comes with 4.3).
I'm with VIP as operator, and until a week ago all was working fine, with a good LTE signal.
But the strangest thing is that i'm having this noisy issue only when i'm at home (near the center of Zagreb), never happened in no other places in the town.
I'm pretty sure it is an operator issue, cose i've tried the sim on a non-LTE smartphone with the same results...
Same
Sent from my ATRIX HD using Tapatalk
If I were you, I'd wait until tomorrow or later and download the next nightly. The first CyanogenMod 12 nightly's texting and phone are broken.
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
If I were you, I'd wait until tomorrow or later and download the next nightly. The first CyanogenMod 12 nightly's texting and phone are broken.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up!
Sent from my SM-G900P using XDA Free mobile app
Is anybody else having trouble with the cyanogenmod 12 nightlies for kltespr? They released the 2nd nightly a few hours ago and the calling and texting is still broken for me, but the network still works. Hmm... If I download albinoman's Alpha release, everything works just fine, but official nightlies are broken for me. Strange.
ethomas94 said:
Is anybody else having trouble with the cyanogenmod 12 nightlies for kltespr? They released the 2nd nightly a few hours ago and the calling and texting is still broken for me, but the network still works. Hmm... If I download albinoman's Alpha release, everything works just fine, but official nightlies are broken for me. Strange.
Click to expand...
Click to collapse
Downloading now, I'll post my results after flash.
Texting and calling is working, but looks like Bluetooth is broken. It works after a reboot, but is very choppy.
Definitely not working. 2 fresh installs. Phone will ring with a different tone than normal but there is no option to answer it. When the other end hangs up, the phone keeps ringing until you reboot it.
Appears inbound texting works but the send button in the stock mms app can not be pressed. Did not bother with testing 3rd party apps.
Have not seen any commits in the changelog which may fix this, so yeah I'd definitely hold off for another day or two before heading to nightlies.
GGTheGooch said:
Texting and calling is working, but looks like Bluetooth is broken. It works after a reboot, but is very choppy.
Click to expand...
Click to collapse
Hmm, that's very strange.
magoo5289 said:
Definitely not working. 2 fresh installs. Phone will ring with a different tone than normal but there is no option to answer it. When the other end hangs up, the phone keeps ringing until you reboot it.
Appears inbound texting works but the send button in the stock mms app can not be pressed. Did not bother with testing 3rd party apps.
Have not seen any commits in the changelog which may fix this, so yeah I'd definitely hold off for another day or two before heading to nightlies.
Click to expand...
Click to collapse
This is the exact problem that I have. I can type text, but I can't press the send button. The phone acts weird and won't actually hang up when I press the hangup button. So some people have the issue and others don't. At least it's not just me.
Sent from my SM-G900P using XDA Free mobile app
Here is a new issue. I tried to connect to my Bluetooth car stereo and it errored out, but my phone started making a ringing noise. No matter what I did, or which service I stopped, it kept ringing. Reboot did not fix the issue, but a power down and power back up worked. Also, regarding the SMS issue. Same issue with the stock app, but I use Textra and it works perfectly.
I've heard that updating the recovery might fix some rom issues, so I updated to the newest TWRP. And the same problem persists. So it's not the recovery, unfortunately. I'm back to using KT TWRP 2.8.0
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
Hmm, that's very strange.
This is the exact problem that I have. I can type text, but I can't press the send button. The phone acts weird and won't actually hang up when I press the hangup button. So some people have the issue and others don't. At least it's not just me.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
I had the same problem with messaging. I had to download Google messenger to send texts. Calling was not working for me. I could see when my brother was calling via LTE would turn off, after he hung up it switched back to LTE. I also noticed that it wasn't recognizing the sim card in the phone. Would this cause the problem possibly? I'll post pictures.
Picture one shows that sim card isn't being recognized.
Picture two shows the LTE is switched to off when he calls.
Picture three shows that I do have LTE. (even tho it is crap signal atm I took screen shot)
Forgot to add flashed using TWRP 2.8.3 (whatever latest version is)
That's very interesting. Unfortunately, I don't know how to fix this. I'll just wait until the next nightly.
Sent from my SM-G900P using XDA Free mobile app
I looked up the changelog for tonight's upcoming nightly and it includes a few network and telephony fixes (about 4). Let's hope this is the one!
Sent from my SM-G900P using XDA Free mobile app
I'm currently using the third build of CyanogenMod 12 official nighties for kltespr and the calling/messaging problem persists. It also appears that I have lost root for some reason. That isn't a big deal, but the calling and texting issues are kinda weird. Do they just not know about it I wonder?
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
I'm currently using the third build of CyanogenMod 12 official nighties for kltespr and the calling/messaging problem persists. It also appears that I have lost root for some reason. That isn't a big deal, but the calling and texting issues are kinda weird. Do they just not know about it I wonder?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Don't know about the phone and messaging but for root you might have to enable it in developer options. I had to do that then it was fine but I'm on a different build.
After a few mins, my external SD card disappears.
I've tried the official CM12 kltespr builds from 9, 10 & 11th.
Not even a root file explorer can see it. Have to reboot to fix,
Anyone else get this?
Hello , I have these problems I can not take pictures with flash activad ,
upgrade in today's problems with incoming calls qualms , I have no problems with messages . but the time is changed
I am on the latest build and using Textra and Hangouts Dialer, SMS/MMS and phone calls work perfectly. GPS works well, but I have not yet attempted Bluetooth. Calls with the stock dialer work, but the phone call does not hang up.
Just verified Bluetooth is still broken.
biship said:
After a few mins, my external SD card disappears.
I've tried the official CM12 kltespr builds from 9, 10 & 11th.
Not even a root file explorer can see it. Have to reboot to fix,
Anyone else get this?
Click to expand...
Click to collapse
I've actually never heard of this. This is new. The only things I can guess about it are it being bad install, of the cache/dalvik cache wasn't cleared. I might try wiping everything (even system; it's in advanced wipe in TWRP) and reflashing it.
telekata said:
Hello , I have these problems I can not take pictures with flash activad ,
upgrade in today's problems with incoming calls qualms , I have no problems with messages . but the time is changed
Click to expand...
Click to collapse
I had that too. I took off the option "automatically find time" or whatever it's called. I just found the timezone manually and it was fine.
GGTheGooch said:
I am on the latest build and using Textra and Hangouts Dialer, SMS/MMS and phone calls work perfectly. GPS works well, but I have not yet attempted Bluetooth. Calls with the stock dialer work, but the phone call does not hang up.
Click to expand...
Click to collapse
I have this problem too. I reinstalled Touchwiz and will try again later when I know Cyanogenmod has fixed the issues.
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.
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
SirMiks said:
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
Click to expand...
Click to collapse
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Sent from my iPhone using Tapatalk Pro
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Same problem
Hello. I'm trying to solve my Moto's mic for over a week now.
I was trying many ROMs, but ended up using TruePureXMM ROM along with franken kernel.
It was all working fine, except some overall phone lag and constantly trying out other kernel auditor settings...
...untill about 2 weeks ago. Phone's microUSB port got damaged, and I had to return my phone to repair service.
After I received it back, I wanted to try out some Nougat ROMs, and tried couple of them, but found out that the mic isn't working properly there.
Decided to return back to stock, using this forums tutorials, done it without any single errors or problems in the process, I did many devices roms changes before.
It didn't help at all. The receiver don't hear me at all, the only sound they can hear is when I blow into the mic's direction.
*Note that when I change to speaker mode, the receiver hear me with some breaks in between, but it's the only way to call from now on...
I'm confused now, completely no idea if it is really the OS problem, or if it's just something with the microphone itself.
Looking forward for any tips, thanks for help.
SR3TLAW said:
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Click to expand...
Click to collapse
I hope so. It's been a few weeks already... If it doesn't fix itself then hopefully the nougat update will help.
Sent from my Moto X Pure using XDA Labs
acejavelin said:
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Click to expand...
Click to collapse
I have tried that too. Nothing send to help and I've been searching online for a while for a solution with no results. I don't think being Att has any relevance but figured I'd share that anyways just in case.
Sent from my Moto X Pure using XDA Labs
Also on att with September security update and speaker phone works fine.