Related
Hello, after I started using Snapchat I noticed pretty big (and extremly annoying) bug. When I use Snapchat on my Nexus 4 with stock 4.4.2 android, it just randomly restarts the whole phone, sometimes it happens after a longer time, sometimes almost instantly after I open snapchat, so this bug makes snapchat absolutely unusable on Nexus 4 :/ So I've done some research and I found out that it's a software related bug that many users encounter since 4.3 and it's related to some bug in the camera API (so it's not snapchat's fault).
Well my question is if this can be solved by using custom rom, or if someone made (or is going to make) some fix that I haven't heard of, because obiviously Google doesn't give a sh*t about their ex-flagship phone
Nexus 4 is awesome but this bums me alot...
I am not sure but this issue is fixed on semaphore kernel. You might check it's thread a for more information.
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.
Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...
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.
I had retired my Nexus 6 a while ago due to the speaker issue that's been plaguing these devices. I decided not to sell it as it would be an issue for the next user, so I instead kept it in case of an emergency.
Certain issues have lead me to recommission the device, so I decided I'd see what's new. So far it is clear that there was never a fix, and some people swear that pressing on the speakers fixes the problem (whether temporarily or permanently). I never believed this as the only thing that seemed to fix it (temporarily) when touching the speakers is tapping on the speakers, but that seems to be related to the device rotating (which has also been known to let the volume go back up) and something within the gyroscope (something that some have brought up as well). My Nexus 6 unlike many others has the bigger problem where the volume will go down regardless of battery percentage, and it was terrible as there was never an instance in which I could truly use the speakers.
Reading around I have seen other "solutions" emerge, but never anything concrete. On a YouTube video's comment sections I saw one person mention that Franco.Kernel fixes this, for me this did nothing. On another forum I read a guy who said his issue stopped using Lean Kernel, and that it may have something to do with mp_decision. Unfortunately for me, I like to stick to the latest version that was officially released (in this case 7.1.1) and Lean Kernel doesn't seem to have made it that far. I gave up on experimenting for the sake of the speakers at this point and settled on my favorite rom which is Dirty Unicorns, using the final 7.1.1 build (somebody was nice enough to provide links as I could not find it anywhere and their official page only has their Oreo based builds). Obviously the speaker issue persisted here. At this point I wanted to see if there was a Kernel with good features and battery life and came across a thread that mentioned BL4CKB1RD Kernel. I flashed that and was a happy camper as my phone runs cooler (no difference has been made to my 4 hour average screen on time) and ultimately lag free. Reading the maker of the kernel's current set up using the kernel, I decided to copy it a bit by limiting my maximum CPU frequency to 2.5GHz and using said governor profile. I came across the mp_decision setting and turned it on just out of curiosity (I have no clue what it does). Later on, I went to watch a YouTube video and before I could connect my headphones, the video was playing...with perfect sound. I thought I was going crazy, so I let it play for a bit longer. No volume drop. I picked up the phone, moved it around, rotated it, blasted the volume to the max and still not a single drop. For literally an hour I watched videos and absolutely no volume issues. I decided to undo all kernel changes and reboot to see what would happen. Still no volume changes. I also decided to lock the CPU and GPU maximum frequency to produce more heat, still nothing. I played Subway Surfers which was a guaranteed instant volume drop, nothing. Rebooted several times more, let the battery die, speakers are still perfect. Could this kernel have fixed my issue? Maybe. It is also worth noting that before flashing the kernel, I ran a command via terminal emulator (requires root) that I read about BEFORE flashing the custom kernel, and I never rebooted my Nexus 6. The command can be found here (there was another thread that also included it but also linked to this thread):
https://forum.xda-developers.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518
Anyone with the speaker issue should perhaps start by this command, reboot and see what happens. If not, try using BL4CKB1RD kernel and see what happens? If still nothing, try toggling mp_decision on and then test.
Crossvxm said:
I had retired my Nexus 6 a while ago due to the speaker issue that's been plaguing these devices. I decided not to sell it as it would be an issue for the next user, so I instead kept it in case of an emergency.
Certain issues have lead me to recommission the device, so I decided I'd see what's new. So far it is clear that there was never a fix, and some people swear that pressing on the speakers fixes the problem (whether temporarily or permanently). I never believed this as the only thing that seemed to fix it (temporarily) when touching the speakers is tapping on the speakers, but that seems to be related to the device rotating (which has also been known to let the volume go back up) and something within the gyroscope (something that some have brought up as well). My Nexus 6 unlike many others has the bigger problem where the volume will go down regardless of battery percentage, and it was terrible as there was never an instance in which I could truly use the speakers.
Reading around I have seen other "solutions" emerge, but never anything concrete. On a YouTube video's comment sections I saw one person mention that Franco.Kernel fixes this, for me this did nothing. On another forum I read a guy who said his issue stopped using Lean Kernel, and that it may have something to do with mp_decision. Unfortunately for me, I like to stick to the latest version that was officially released (in this case 7.1.1) and Lean Kernel doesn't seem to have made it that far. I gave up on experimenting for the sake of the speakers at this point and settled on my favorite rom which is Dirty Unicorns, using the final 7.1.1 build (somebody was nice enough to provide links as I could not find it anywhere and their official page only has their Oreo based builds). Obviously the speaker issue persisted here. At this point I wanted to see if there was a Kernel with good features and battery life and came across a thread that mentioned BL4CKB1RD Kernel. I flashed that and was a happy camper as my phone runs cooler (no difference has been made to my 4 hour average screen on time) and ultimately lag free. Reading the maker of the kernel's current set up using the kernel, I decided to copy it a bit by limiting my maximum CPU frequency to 2.5GHz and using said governor profile. I came across the mp_decision setting and turned it on just out of curiosity (I have no clue what it does). Later on, I went to watch a YouTube video and before I could connect my headphones, the video was playing...with perfect sound. I thought I was going crazy, so I let it play for a bit longer. No volume drop. I picked up the phone, moved it around, rotated it, blasted the volume to the max and still not a single drop. For literally an hour I watched videos and absolutely no volume issues. I decided to undo all kernel changes and reboot to see what would happen. Still no volume changes. I also decided to lock the CPU and GPU maximum frequency to produce more heat, still nothing. I played Subway Surfers which was a guaranteed instant volume drop, nothing. Rebooted several times more, let the battery die, speakers are still perfect. Could this kernel have fixed my issue? Maybe. It is also worth noting that before flashing the kernel, I ran a command via terminal emulator (requires root) that I read about BEFORE flashing the custom kernel, and I never rebooted my Nexus 6. The command can be found here (there was another thread that also included it but also linked to this thread):
https://forum.xda-developers.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518
Anyone with the speaker issue should perhaps start by this command, reboot and see what happens. If not, try using BL4CKB1RD kernel and see what happens? If still nothing, try toggling mp_decision on and then test.
Click to expand...
Click to collapse
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
DerrickTight said:
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
Click to expand...
Click to collapse
Yes it is common and does effect custom ROMs as well
DerrickTight said:
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
Click to expand...
Click to collapse
For most the issue occurs at low battery, and the drop isn't major. I've seen some videos of people with this specific problem and I laugh because they don't know have it as bad as us with the major drops regardless of battery life. So pretty much the low battery volume issue is more common than the worse one, and you could say it is a common issue.
We had a white one that had absolutely no issues except a faster battery drain (perhaps because the speakers worked?!).
Crossvxm said:
For most the issue occurs at low battery, and the drop isn't major. I've seen some videos of people with this specific problem and I laugh because they don't know have it as bad as us with the major drops regardless of battery life. So pretty much the low battery volume issue is more common than the worse one, and you could say it is a common issue.
We had a white one that had absolutely no issues except a faster battery drain (perhaps because the speakers worked?!).
Click to expand...
Click to collapse
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
My Nexus 6 arrives tomorrow and I'll be flashing it right away. If I have a volume issue I'll definitely keep your kernel in mind. Thank you
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
Dumb question does your kernel already have these included?
xconwayx said:
Dumb question does your kernel already have these included?
Click to expand...
Click to collapse
Yes.
For what it is worth, mp-decision is Qualcomm's own hotplug: it turns the processor cores on and off depending on need. I guess it may use other tricks as well, to optimize power / performance.
No obvious reason that it should affect the speakers, but you never know.
Does this thread address the issue with SEVERAL 8.1 ROMs I've used, in which the speaker phone does not function during calls... and during calls alone. I can play media just fine... IMMEDIATELY after the speaker not working on the calls. I CAN however plug a headset in and communicate normally . Just desperately seeking an answer or I guess I'll go back to 7.1.2
So now nexus 6 is running pie roms nearly perfect . Unfortunately this sound problem persists… it is truely fristrating
So is there any kernel that can fix it in pie roms? Thanks
I have been using my nexus 6 for a couple of years now and had the speaker issue about a year ago and went into recovery and wiped cashe and the. Did a factory reset. Did an OTA update and everything was fixed.
Last weekend I finally flashed TWRP and then rooted with Magisk. Went to install myself5's Bata version of Carbon room running pie... Not sure what happened but had error code 7 and bricked the phone. Had to wipe it out and went though Google to get an old OTA and reflashed and thankfully got my phone back. Tried the process 3 other times and got the same result. Each time no speaker issue.
The last time I tried it I left it alone and didn't even put TWRP on it but now the speaker problem comes and goes.
5 min agot I was playing YouTube music with no issues, made a phone call, then back to YouTube and now the bottom speaker quit and the top speaker is very quiet.
Any ideas on what could have cause my issues and can someone direct me to where Ii can find more information or what I'm doing wrong on on flashing new roms?
Currently running Android 7.1.1 build NGI77B
Suffeln said:
I have been using my nexus 6 for a couple of years now and had the speaker issue about a year ago and went into recovery and wiped cashe and the. Did a factory reset. Did an OTA update and everything was fixed.
Last weekend I finally flashed TWRP and then rooted with Magisk. Went to install myself5's Bata version of Carbon room running pie... Not sure what happened but had error code 7 and bricked the phone. Had to wipe it out and went though Google to get an old OTA and reflashed and thankfully got my phone back. Tried the process 3 other times and got the same result. Each time no speaker issue.
The last time I tried it I left it alone and didn't even put TWRP on it but now the speaker problem comes and goes.
5 min agot I was playing YouTube music with no issues, made a phone call, then back to YouTube and now the bottom speaker quit and the top speaker is very quiet.
Any ideas on what could have cause my issues and can someone direct me to where Ii can find more information or what I'm doing wrong on on flashing new roms?
Currently running Android 7.1.1 build NGI77B
Click to expand...
Click to collapse
I've honestly encountered this problem a couple times but rebooting/flashing fixed the problems. Worst case scenario go back latest Google ROM with WUG's software, then you can install TWRP, then a custom ROM like Nitrogen ROM.
Sent from my shamu using XDA Labs
I know nothing about what anyone is saying, but I would like to add that using Viper4Android, and using "eXtra loud" at "Moderate" with the max gain at 4x and the max output at 0db completely gets rid of the low volume problem. Viper works system wide so it fixes it for Netflix, etc
Hope this helps guys
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
Sorry for the late reply, I had to put the Nexus 6 on hold due to another issue with it. I tried your kernel with the latest official version of Dirty Unicorns, but unfortunately it does not boot. It will boot fine without flashing the kernel.
mahir555 said:
So now nexus 6 is running pie roms nearly perfect . Unfortunately this sound problem persists… it is truely fristrating
So is there any kernel that can fix it in pie roms? Thanks
Click to expand...
Click to collapse
Having this same issue using the NitrogenOS Pie rom. Updated from 7.1.1 (didn't have this issue with 7.1.1).
Is it better with the Oreo 8.1?
centerpide said:
Having this same issue using the NitrogenOS Pie rom. Updated from 7.1.1 (didn't have this issue with 7.1.1).
Is it better with the Oreo 8.1?
Click to expand...
Click to collapse
No . I can confirm that all oreo roms got the same bug .
For me am using android x unofficial pie rom with popcorn kernel. This combination seems to fix this bug !
Try them or even try the kernel with nitrogen os rom .It may work..
El Gunslinger said:
Does this thread address the issue with SEVERAL 8.1 ROMs I've used, in which the speaker phone does not function during calls... and during calls alone. I can play media just fine... IMMEDIATELY after the speaker not working on the calls. I CAN however plug a headset in and communicate normally . Just desperately seeking an answer or I guess I'll go back to 7.1.2
Click to expand...
Click to collapse
Unfortunately no. Mine WAS working perfectly. The charge port broke after about two weeks after I made this thread (my luck), and after having it repaired, the problem seems to have gotten worse. For one, it no longer works in the configuration I mentioned in this thread (mind you, I did not reset it or anything). It also now varies from rom to rom, with the bigger issue now being that the top speaker ceases to function on certain roms, including the way I had it. Now, it drops volume for everything, and most of the time the top speaker will be weaker for the slight moments both decide to work.
New problem
Hi Crossvxm. I have had a Nexus 6 for two years. When I wiped it to sell it, the audio problem started. I had PureNexus.
I did what you suggested. I turned on mpdecision with BlackBird kernel and kernel auditor. I installed su terminal, to execute these commands with root access:
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0034/force_calib
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0035/force_calib
And the full volume audio came back! Videos, youtube, all working again! But, the audio in calls worked no more. So, after that, I wiped all, installed PureNexus 7.1, Nitrogen 8.1, stock 7.1... I tried everything, but the audio in calls never returned. When I reinstalled all these roms, the low volume problem appeared again, but the audio in calls never came back. Even WhatsApp calls have no audio. The microphone still works, because the other person indeed can hear you.
Do you have an idea about how can I solve it? At least to leave it usable as phone. Thank you very much for sharing your knowledge and time.
Butifarra said:
Hi Crossvxm. I have had a Nexus 6 for two years. When I wiped it to sell it, the audio problem started. I had PureNexus.
I did what you suggested. I turned on mpdecision with BlackBird kernel and kernel auditor. I installed su terminal, to execute these commands with root access:
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0034/force_calib
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0035/force_calib
And the full volume audio came back! Videos, youtube, all working again! But, the audio in calls worked no more. So, after that, I wiped all, installed PureNexus 7.1, Nitrogen 8.1, stock 7.1... I tried everything, but the audio in calls never returned. When I reinstalled all these roms, the low volume problem appeared again, but the audio in calls never came back. Even WhatsApp calls have no audio. The microphone still works, because the other person indeed can hear you.
Do you have an idea about how can I solve it? At least to leave it usable as phone. Thank you very much for sharing your knowledge and time.
Click to expand...
Click to collapse
This sounds like what happened to me recently. The configuration I mentioned in the very first post worked perfectly. After taking it to have the charge port fixed, the top speaker stopped working, and you could not hear the top speaker at all during calls. I thought the store broke it, but after giving up using it for some time, I realized that it would randomly try to output sound from the top speaker. After starting all over (flashing back to stock and flashing my same configuration again), the problem changed to where the top speaker was very low in sound when both speakers felt like working. I flashed the latest Dirty Unicorns based on 8.1 along with Popcorn Kernel by athulele but unfortunately it did not boot (as mentioned in his thread, the kernel is Lineage based).
I gave up on the Nexus for a few more days. When I decided to give it another go, I flashed the latest LineageOS (along with root for it via their own separate flashable zip), flashed Popcorn Kernel, installed Kernel Adiutor from Google Play (yes, it's spelled that way), installed the Terminal Emulator for Android and ran the command as well as checking the kernel settings to ensure MP Decision was on, capping the max frequency to 2.4Ghz (feels much less hot) and making sure everything was set to "set on boot". Unfortunately it did not work. The only way I got it to work again was to give up again, flash back to stock and flash Lineage and Popcorn Kernel exactly as I explained in this second paragraph.
So why did it work this time around? Everything was done the same, what could possibly make it work? I have a theory. When it was taken to the shop for repair, the battery died since it was already at 20%. As you can see I mentioned a few times "I gave up" on it, meaning I stopped bothering to fix it, and eventually it would run out of battery mainly from wifi and notifications. Every time it was dead, it was usually dead for at least 24 hours. Each time around, the issue would change. I don't know what it has to do with anything, but I do believe it plays a key role. Try letting your battery die, charge it back up to 100% and then try the process from either paragraph two or from my original post. After it began working again, I abused the heck out of the speakers, rebooted the phone, tried calls, etc. all without letting the battery die and it has not stopped working. I recently sold it as is and was contacted by the person who purchased it who was confused as he did not experience any sound drops either. He was originally buying it to replace the screen on his but decided to stick with mine since it was working perfectly so far.