Related
Situation
Bought Nexus 4 refurbished, works great except for this issue. Back speaker works great, Google Search works with mic (Ok Google). Updated via OTA all the way to 5.0. Am using phone on a carrier in Ecuador.
Problem
When making a phone call over the local carrier, call connects (you can see the counter on screen), music, if playing, pauses as it should. But no audio from the earpiece, and the other side does not hear anything from my side. Tried putting call on speaker, nothing. Tried with headphones, nothing. However, when making a Hangouts call over data, mic/earpiece work fine. To me, this means the hardware functions, so it must be software related. The phone sends SMS without issue, so it works with the local carrier. Also data works without any issue.
What I've done so far
Searched high and low, and it seems this is a somewhat common problem that some have fixed in many different ways. Please let me know if you know of another that I may have missed.
Downgrading to 4.4.4
Upgrading back to 5.0
Factory Reset
Flash 5.0 Factory image
Upgrade to 5.0.1
Flash complete 5.0.1 Factory image
Flashed latest CM11 nightly
Tried several "solutions" found on Google Group forum, such as pluging headphones in and out
Flashed Hybrid modem with included audio fix
Switched SIM cards
Installed SoundAbout, and tried many different options - redirecting Phone Audio, even changing options for Headset detection (thought the phone was confused, thinking the headphones were in)
Tested mic with recording apps and by recording videos, all work fine.
Installed PAC-ROM without Gapps to see if it was the Google Play Services issue
Disabled the CheckInService
I think I've tried more, but can't remember them all. It's been over a week, and can't answer or make phone calls.
Coming to my wits end, and it's extremely frustrating since it doesn't seem to be a hardware issue, and I hate giving up on something I can fix. Any suggestions?
(Edited and added a couple more tests to the list)
yep, you are not the only one with this issue, it started to plague users just recently, including me and from what i've learned so far it has got something to do with google play services.
however for me, flashing 5.0/5.0.1 resolved it (i only encountered it on CM4.4.4 )
here is another topic bout this. good luck
http://forum.xda-developers.com/nexus-4/help/audio-call-nexus-4-cm11-t2924589
ps. this thread i linked above acutally contains some solution/workaround involving disabling one of the google play services. just read through the whole thread
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
I too had the exact same problem. I was on CM 4.4.4 nightlies. Moving to stock lollipop5.0 solved the problem.
Shooting Star Max said:
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
Click to expand...
Click to collapse
I tried that too. I installed PAC-ROM, the latest nightly, without GAPPS. Booted fine, all seems to be working except sound in calls.
I also tried disabling the CheckIn Service, as was mentioned in the other thread, still no luck. So frustrating!!
I'll try them all again...
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
BitteredBro said:
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
Click to expand...
Click to collapse
I'll give it a try. I had tried with the official CM11, both with and without Gapps, but no luck.
Hey all. I just got my Note 3 two weeks ago and I love it. The battery life is great, great specs, unlocked bootloader, and I find it easier to use in terms of size compared to the Galaxy S5. There is only ONE problem with this device.
The mic stops working during skype calls after random periods and the only solution is to hang up the call and call again. This lingers even after restarts of the app and phone.
Being a Nexus user since the Galaxy Nexus, the first thing I did was install TWRP and the latest CM nightly. I personally can't stand Touchwiz, which is why I sold my bootloader-locked GS5 to get this bad boy.
Has anyone else encountered this issue? Is it a Skype problem? Is it CM? Lollipop? My mic is fine, it works perfectly in every other application.
Also, I've noticed that USB 3.0 mode doesn't show up in the Connection type selection menu. Is USB 3.0 file transfer only supported in the stock kernel?
Okay so I'm gonna describe my problem as clearly as possible and will hope someone can find a fix for this.
Device: Nexus 6P
OS: Android 6.0.1 (latest vendor & security patch - June 2016)
Bluetooth devices used: Sony MDR 600BT, SOL republic tracks air, jbl synchros earphones, jbl flip 2 speaker.
1) pair earphones/speakers
2) start playing music on earphones/speakers
3) works fine on first run and when screen is off
4) when I switch on my screen to change the song the music stutters for 10 full seconds, then stuttering stops.
5) I change the song and again put screen off, works fine.
6) i put my phone in my pocket and suddenly my phone audio stops skipping??? Wtf???
7) so I change my pocket and put it in my hoodie pocket. (Nearer to earphones - maybe distance is the problem I thought)
8) audio still skips............:crying:
9) put my screen on to change song, audio starts stuttering again like crazy and then stops.
10) I request anyone here to heed this request and tell me how to workaround this problem
Currently running latest android MM 6.0.1 and no improvement .....:crying:
I don't understand one thing - top of the line flagship device and still these problems? Not getting value for my hard earned money. This is wrong.
I tried it with my iPod and it works like a charm. No stutters. No skips. Nothing.
Tried different Bluetooth headphones too in case my Sony earphones were the problem. NO IMPROVEMENT SAME PROBLEM PERSISTS.
TRIED USING IT ON ANY BLUETOOTH SPEAKER THE ABOVE THINGS KEEP HAPPENING AND I AM GETTING REALLY ANNOYED WITH THIS PHONE WHEN IT COMES TO BLUETOOTH.
I'm sorry for agonizing so much. But I hope you'll can understand my problem. And hopefully there's a fix somewhere in the world.
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
blackwrx02 said:
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
Click to expand...
Click to collapse
I can't speak for Zapjack12345, but I notice it with PowerAmp, Pandora, Spotify, YouTube, basically any app that is pushing audio through bluetooth. Audio is fine when the screen is off, but as soon as I pick up the phone, and turn it on to check notifications, things get screwy with the audio
Strange. I just checked with Pandora, YouTube, and IheartRadio and all seem fine with screen off and turning it on, using the pulldown menu, or changing songs. I'm using a cheap set of bluetooth earbuds from Amazon (no-name brand), and am stock with the phone, not rooted (yet) and on June updates. Phone was purchased in May new from Best Buy.
Same issue for me as well. I'm specifically using Amazon and Pandora most of the time. Its very annoying. On Chroma and franco kernel.
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
uodii said:
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
Click to expand...
Click to collapse
I'm currently on Pure Nexus 5/6/16. Nothing out of the ordinary installed. Tried clearing the Bluetooth cache, as the issue I am noticing was similar to issues that the Samsung S5 was having, but there was no difference.
I am going to look to go back to stock and see what happens, but looking at what OP posted, it looks like they're on stock, and having the same issue.
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
krakerx said:
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Click to expand...
Click to collapse
I had a little less issues when using the Dev Preview 3 but there was another issue that arised that I hope gets fixed.
If you're using bluetooth when driving around when you lose signal or drop/gain data connection the audio skips for a quick second. Through past testing I've done working with kernel devs on 2 phones, the issue is related to how the hotplugging works for the cores. If only one core is running when the connection drops there is an issue with how the cpu ramps up and/or turns on another core to handle the workload. I thought this regression was pretty interesting seeing as one the things they were boasting about at the Google conference was how android would fix slow downs and issues when losing/gaining network connectivity with N. Hopefully it'll be fixed before final release.
akarol said:
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You and me both. I am on my 3rd 6P and my BT problems are still the same. If the BT problems were only effecting one particular device I could understand but my Microsoft band, BT earbuds and car all seem to disconnect continuously on a bare/stock phone.
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Does anyone else have any updates regarding this issue? Literally wanted to throw my phone out of the window during the morning commute.
Zapjack12345 said:
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Click to expand...
Click to collapse
Don't use cm based roms
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Yep, this is 100% the reason. It is a CM issue. AOSP roms like Paranoid Android and Pure Nexus don't have this issue. I love Resurrection Remix, but this is starting to bug me. I may jump to PA rom soon...
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Thanks. Was about to ask this question. It is a CM issue.
I have had issues with BT dropping randomly in my car on 2 different 6P's. No rhyme or reason, and it doesn't happen often, but annoying when it does. Happened on MM and DP4 currently.
On the flip side, my audio quality went down on my S7E over BT when my smartwatch was connected. Somehow, that doesn't happen with the 6P meaning I can keep my watch on in the car, so I am happy.
Hey, I just found this thread and surprised it took me this long considering I've been having this issue since I got my phone in November.
My 64gb 6P was stock until earlier this week, when I finally rooted and flashed xposed. The issue stopped the day I rooted my phone, and I was thrilled.
After reinstalling most of my apps and getting back into my routine, the problem came back. I've tried booting my phone into safe mode several times before rooting so I'm fairly confident the issue doesn't exist because of a specific app interaction, but I can't figure out what it is to save my life. I might backup again and restore to the backup I made right after rooting to see if I can narrow down the problem.
Other than that, I am very new to this stuff and honestly just thrilled to have found other people having the same issue.
I only experience the problem while connected to my car (2015 Chevy Cruze), and not any other bluetooth device.
Let me know if you guys find/have found anything I suppose?
I kinda have up on trying to narrow down the issue. I tried PureNexus, Paranoid Android, I tried different kernels, different cases. Still kept skipping and jumping, no matter how far, or close it was to my Bluetooth device (car stereo, speakers, home audio system). I went back to stock, no root, no Xposed, pure and simple Android, and I have not had a single issue, it's beautiful.
Hi,
I'm trying to figure what options there are for robust call recording apps on rooted OP6Ts.
I'd like to know if a specific call recording application functions on Andriod Pie after rooting the device.
This application
here's the app: https://play.google.com/store/apps/details?id=com.appstar.callrecorder&hl=en_US
If those running a rooted OP6T would install the app and make a few calls I'd appreciate it.
Here's a number to Health and Human Services Office of Civil Right (all prerecorded menus; we won't bother anyone) to do test calls: (800) 368-1019
You may need to do some basic setup. Make sure call recording occurs automatically, or allow the overlay and manually engage the call recording.
For those willing to go to some effort, if at first the app doesn't work, the "Recording Settings" can be tweaked.
I don't know what the difference is between methods, other than that they change how the app tries to get voice data to record.
Can you hear both yourself and the the caller in the recording?
What recording settings were used?
What format did the recording save to (AAC/MP3/Wav?)
What is the sound quality of the recording?
Do any of the above change if you plug in a USB-C earbud/microphone or earbud/microphone attached via USB-C to 3.5mm/TRRS.
(note: bluetooth headsets have compatibility issues even on phones the app works; headset would need to be wired for this test, though info on Bluetooth would be nice if one is so inclined to provide it)
In the applications inbox for recordings, does the number or contact information show up, or is it listed only as "outgoing" or "incoming" call.
Alternatively, I'd be interested in any information/experiences rooted users may have with other call recording software. Such as Another Call Recorder - Unchained (https://labs.xda-developers.com/store/app/com.nll.acr). In particular, reliability and call recording quality (as good as 'the call').
Note: I'm aware Native Call Recording can be enabled via ADB. I have done this in my testing. The sound quality is awful on the OP6T I have (which is unrooted; uncertain yet if I need to return).
It seems the OP6T or the OP6T I received has issues with AAC/mp4 and other codecs, which may or may not involve something to do with how it's handling sampling rates - I recall reading that certain ROMs cause issues with audio frequency/sampling. It's a mystery to me. Looking to gather more information and hope that members of XDA can assist in this.
theres a magisk module to enable call recording. works perfect. at least it does on my 6t. recordings are clear. no issues at all. root your phone and try it. no need to install a recording app. the module even works on android 10 so.
OvrDriVE said:
theres a magisk module to enable call recording. works perfect. at least it does on my 6t. recordings are clear. no issues at all. root your phone and try it. no need to install a recording app. the module even works on android 10 so.
Click to expand...
Click to collapse
Well, so my understanding is the Magisk module basically enables the native call recorder.
I've done that via ADB without rooting the phone and the call recording quality is poor. The the call recording apps still don't work properly. Though some of them can use the native call recorder to record calls. But again, audio quality is poor.
Meanwhile, my galaxy s5 on Marshmallow records with excellent sound quality. Though some calls get missed or have issues, which why I want to upgrade/resolve this problem.
Also, the need to note who a call is from and what was spoke of so as to create a call database that allows making sense of matters, I need that to be able to go back and sort through notes. An app lets me do that: date, time, person, with brief synopsis of most relevant information taken directly after the call ended and was saved.
Anyways, I'm not sure if it's a problem with the phone I received (it is 'refurbished' via Amazon Renewed) or a problem with the 6T, but every application I've tried to make a voice recording or call recording using AAC or MP4 runs into this poor audio quality recording issue in addition to the 'other party' not being recorded. This poor audio quality issue exists even with the ADB command and native call recording. Meanwhile, if I call my Galaxy S5 and just speak through the OP6T through my earbuds connected via USB-C dac, the S5 records a perfectly audible call recording.
So...I was hoping to hear more from other 6T owners and see if rooting could be expected to change any of these problems, or at least determine if these are problems that can be observed by others. It's kind of hard to assess if rooting will help out without committing to keeping this phone. The moment I root, it's hard to return it if things turn out to not work out the way I need.
Rooting the phone takes 5 minutes, installing the module less than one. You'll have your answer in less time than it took you write your posts.
Experiment instead of being in the abstract. You'll know then if you have to return the phone, after uninstalling root. From OnePlus point of view, rooting doesn't invalidate the warranty.
Striatum_bdr said:
Rooting the phone takes 5 minutes, installing the module less than one. You'll have your answer in less time than it took you write your posts.
Experiment instead of being in the abstract. You'll know then if you have to return the phone, after uninstalling root. From OnePlus point of view, rooting doesn't invalidate the warranty.[/QUOTE @Stratium_bdr, is there a particular guide for rooting, twrp and Magisk you can recommend? I'm running the latest Open Beta, and pretty adb savvy, just a little confused by AB partitions lol. Thank you!
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse
why can't you restore the phone? the normal msmdownloadtool is for international 6t's theres even one available for the t-mobile 6t to return it to t-mo's firmware. do some looking. it's all available on this forum.
also why not try android q. why pie for this. i don't see the point in pie when q is out and pretty stable atm
Striatum_bdr said:
Rooting the phone takes 5 minutes, installing the module less than one. You'll have your answer in less time than it took you write your posts.
Experiment instead of being in the abstract. You'll know then if you have to return the phone, after uninstalling root. From OnePlus point of view, rooting doesn't invalidate the warranty.
Click to expand...
Click to collapse
So, I doubt they'd appreciate the phone being rooted. You're quite right that the most expedient method would be to root and find out, just one I hesitate to try. If rooting didn't turn out to be a solution, I must return the OP6T to the Amazon seller.
Looking into things, I've learned the OP6T has a history of problems with microphone audio in third party applications. And a post at one call recording app developer's forum suggested some phones have issues with sampling frequencies that are caused by ROM issues.
Some OOS update notes indicate fixes have been made in some versions for mic issues, but I'll have to update to see if the issues I'm encountering are the same they addressed. I'm trying to find the right ROMs from a trusted source to update the phone, as the auto-update just sits there and tells me 9.0.11 OOS is 'up-to-date'.
Strangely, OnePlus doesn't offer previous firmware's via their support site, just the latest, which updates to Andriod 10, and I have more issues with call recording exist with 10 than 9.
OvrDriVE said:
why can't you restore the phone? the normal msmdownloadtool is for international 6t's theres even one available for the t-mobile 6t to return it to t-mo's firmware. do some looking. it's all available on this forum.
also why not try android q. why pie for this. i don't see the point in pie when q is out and pretty stable atm
Click to expand...
Click to collapse
Does Andriod Q have some benefit to call recording? I recall a news article that postulated Google might be restoreing call recording, but it remains unclear if, how, or when.
OnePlus don't care about root. You can do whatever you want with your phone as long as your don't mess with hardware. It doesn't void the warranty at all. But if you prefer to colocate things it's up to you. Good luck.
Striatum_bdr said:
OnePlus don't care about root. You can do whatever you want with your phone as long as your don't mess with hardware. It doesn't void the warranty at all. But if you prefer to colocate things it's up to you. Good luck.
Click to expand...
Click to collapse
Well, when I chatted with their support they said their official recommendation was to not root. Which is pretty much what every manufacturer says. I'll keep it in mind. Going to await OnePlus supports assistance tracking down an older OOS version to flash; see what they does.
LastQuestion said:
Does Andriod Q have some benefit to call recording? I recall a news article that postulated Google might be restoreing call recording, but it remains unclear if, how, or when.
Click to expand...
Click to collapse
google actually removed the ability to record calls in q. even there api is no longer allowed. the reason for this is because call recording is illegal in probably 90% of the world. however since it is legal in a few places(specifically places oneplus sells there phones) oneplus allows it if you enable the feature by toggling it on. hence the magisk module for it. the call recording magisk module that installs an app also works really well on q but it's 10$ for the full app that gets installed. for me it was just easier to enable the built in feature. besides why pay 10$ if you dont have to.
OvrDriVE said:
google actually removed the ability to record calls in q. even there api is no longer allowed. the reason for this is because call recording is illegal in probably 90% of the world. however since it is legal in a few places(specifically places oneplus sells there phones) oneplus allows it if you enable the feature by toggling it on. hence the magisk module for it. the call recording magisk module that installs an app also works really well on q but it's 10$ for the full app that gets installed. for me it was just easier to enable the built in feature. besides why pay 10$ if you dont have to.
Click to expand...
Click to collapse
Does Andriod Q break call recording for OnePlus phones, or does the toggle still work?
Does rooting restore call recording to Q in other phones?
Do you think it's possible to create a custom ROM that adds back the call recording API to Q so that full call recording capability is restored?
LastQuestion said:
Does Andriod Q break call recording for OnePlus phones, or does the toggle still work?
Does rooting restore call recording to Q in other phones?
Do you think it's possible to create a custom ROM that adds back the call recording API to Q so that full call recording capability is restored?
Click to expand...
Click to collapse
why would it break it on q on oneplus phones. they have there own implimentation of it. it's disabled by default but can easially be enabled once on the official oneplus software. and yes this includes converted t-mobile 6t's
why would rooting restore call recording on other phones. this isnt other phones threads this is a oneplus 6t thread. you wanna know about other phones go ask in there threads not here
no. as i said google has disabled the feature in q and dropped the api for it so no it is not possible to add it to a custom rom that i know of.
you want anymore info ask elsewhere as i really dont know much more then what i have already mentioned
Hello there all hope everyone is having a great day
I am posting to see if anyone is having the same issue as me - Microphone not working on Messenger, Snapchat and only works on certain apps!! So I was reading some app developers are correctly using the right microphone and others are using the noise cancelling microphone? So installed a custom rom and it looks like it works fine. But i really want oxygen os to work with the microphone on all apps just how the custom rom works!!! Does anyone know and can confirm which oxygen os will make the microphone work properly???? I had oos beta and totally forgot about stable oxygen os and just install paranoid Android. Greatly appreciate if someone could guide me on how to use oos with the right microphone
Thanks
garethm56 said:
But i really want oxygen os to work with the microphone on all apps just how the custom rom works
Click to expand...
Click to collapse
Yeah the system uses the noise canceling microphone to pick up the audio, but you can't do nothing about it, it's a really old OOS bug (Since the 1+3 days I think) and it even happens with the newer models, so if you really need the mic to work properly, use a custom rom.