Database Users

[Q] CyanogenMod + Android Wear

Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan

sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
So far i know it works
Sent from my LG-D855 using XDA Free mobile app

I have an S4, and I haven't gotten mine to work on CM 11. I mean it does, but not very well. Gonna switch to a TW rom tonight.

S4 running CM11 and no issues with my LG g watch. Everything comes through with no disconnects.
Sent from my GT-I9505 using XDA Free mobile app

sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.

On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.

lost network connection
Hello I installed cm 10.2 through flash recovery. Onti my galaxy ace 2GT I8160 was gingerbread 2.3.6
Now its team conja jls361 if ive looked in the rite plce i still have iemi number and can recieve messages
But when i try and send or call it say no network ive been on to 3 my provider and they say its the phone
Please could you help with thi ive read it happens alot with this release of cm.. Would installing cm 11 sort it out im a newbie to being root ive already soft bricked it once so can see it being a bumpy ride so all the help i can get the better thank you
Also I looked at the build list and the radio and boitloader are unknown the biitloader has been like that when i got the phine that's bootloader not biitloader or bout loader dam key pad lol
My kernal is a i8160xxlk8 or it was I dunno if it still is

Connecting, running sync loop
Latoc said:
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
Click to expand...
Click to collapse
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....

Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
I don't know about s3, but you should try a few kernels and see what works...

FIXED
Latoc said:
I don't know about s3, but you should try a few kernels and see what works...
Click to expand...
Click to collapse
Well,
I tried a different kernel and still same issue. I flashed a TouchWiz based rom and it WORKED. Shows "connected". Battery life on moto 360 also vastly improved. Went from dead at 3:30 PM to 45% at same time!

I'm on DarkCM(11) for the xperia z1 and can't get it to work either.
Tested on my brothers stock xperia and that worked just fine. Il try downgrading to stock as well. :'(
If anyone gets CM on the z1 running with android wear please let me know.

I have a Oneplus One CM 11S works great on my old Gear Live and my new Sony Smartwatch 3
I read that MOTO 360 has (had) issues ?? Maybe the watch not the phones OS

Hi. My first post here and very New to all this. I have Samsung S4 with cm11 just got an Samsung galaxy gear2 neo and now i have to figure out how to get it to work with cm11 ? Can some body help

TechieInAK said:
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
Click to expand...
Click to collapse
Sorry for bringing up an old post. I wanted to check in on your Android Wear connection to CM ROMs. I have a Sprint S4 (jfltespr) running CM12. I will be getting a LG G Watch R in a few days but someone else on our ROM thread was having issues with his Moto 360 and the CM12 ROM. Have you experienced any issues not connection or remaining in a sync loop?
Has anyone else experienced Android Wear issues with CM 11 or CM 12 on S4 phones? Particularly jfltespr?

Cant speak for the S4 but my LG G3 has had nothing but issues with my G Watch R since I flashed CM12. I reverted back to CM11 (recent build) and its working great, never disconnects. With CM12 it would disconnect at least 10-20 times a day its unusable.

I just installed the Google Play Edition Lollipop on my GS4 and it paired perfectly with my ASUS ZenWatch. Lollipop AOSP is AMAZING and i am so stoked it works so great!

Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
"Connecting, running sync loop" is just a different message for the same thing - it is activated on some ROMs(?) apparently when you have Developer mode enabled. But it works the same, and this message in itself doesn't indicate there should be any battery drain.
Of course something in the ROM might be causing this problem - a logcat from the watch would help in that case, but my guess is you just need to let everything install, settle down and then reboot both devices, and the drain will be gone...

My Zenwatch works perfectly with my Oneplus One running the latest CM11S. Having bluetooth on all the time does drain a bit more battery, but that's it.

I am having an issue with google wear (zenwatch) completing some tasks:
It fails to launch a phone call from google wear (my watch simply says "try again using your phone")
It fails to launch google play for music (it gives the same error as above)
Setting reminders using google keep (same error)
Text messages sent from android wear are NOT working.
Starting navigation on my watch using voice commands works.
Other basic apps appear to be working as well.
So far I've only noticed the above listed (maybe a few others) google apps and dialer that fail to launch when initiated from the watch, I have tried another dialer to see if that was the issue.
Anyone have any suggestions or insight on what I might be able to do in order to get google wear working 100% with this ROM?
Any help is greatly appreciated.

Mine works well
I have OnePlus One with CM11 and everything works quite well so far with my G Watch R

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.

I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

CM12 on LG3 D852, positive experience

Hello, I am with FIDO Canada, I installed CM12 on D852 on February 13 Nightly version cm-12-20150213-NIGHTLY-d852.zip
I thought I give it few days and see how it works compared to other ROMS.. I tried Validus and had few bugs with ring volume not working and standby mode.
So far I have not found any bugs with CM12, runs super crazy fast, all my apps work, Bluetooth is even better than LG, reconnects automatically.
The only feature that I would like to have Auto switch in Data, like in LG it switches automatically between 2G,3G,LTE, this is missing in CM12 but I guess not a big deal (maybe can find app for it.)
Battery is great, maybe just tiny better from LG.
Contact list I way better with almost full screen picture when you dial someone.
For some reason cant play WAV files, player does not support it, will try to download other player.
CM12 is already rooted, you can enable/disable it in Developer options to use some other programs.
What I suggest to get:
In LG my icons were bigger which I really liked, in CM12 apparently you cannot make them bigger, everything is smaller but I installed Nova Launcher and even paid for it cause I really like it, you can enlarge your screen and everything is back from what I used to like, you can do so many fantastic things it is unbelievable, I highly recommend it have it installed.
Get Power Toggles!!!!!!! freaking great, makes your life easier.
Don't like camera, missing 4K. but I found better one which I really like and found it on some other forum. Don't remember where I download it but here is zip file you can google (MotoAppsMaterialAOSP.zip) and flash with TWRP.
By the way make sure you have backup and recovery TWRP version 2.8.3.0 the only version works with D852, don't get the latest.
It saved my life, I almost **** my pants few times and had to recover the phone. If you do not have this installed DON'T EVEN THINK ABOUT INSTALLING ANY ROMS!!!. there is high chance you can screw this up and all is left garbage bin.
For now I leave it like this because it is really stable, not planning to install later CM12 nighties, for 2 reasons: afraid to make it worth and because I am tired reinstalling apps.
If you are looking to upgrade your phone to a lollipop version and have it as close as LG I really recommend the same setup I have. it is worth it.
If you want to know how to do it you got to google first how to root, install recovery, make back up, the rest is easy. Just watch plenty youtube videos.
By the way to boot into recovery mod on LG G3 here is how (turn it off--> press volume down and power--> let go after you see LG logo, then press power and volume down again) after that you should see TWRP if you have it installed correctly.
I also uploaded small video on youtube what I looks like, I cannot post link on this forum, but if you search on youtube for user "ukrik" it will be there.

I've tried a few roms also
I find that bare CM12 is the best for me. After a Factory reset you have to redo the APNs - I'm on MTS and the apns are showing fido after any re-install/factory reset. I really like the battery performance and also the fact that it is blindingly fast compared to stock. I'm not a power user of the phone so I am quite satisfied with it's current capabilities. The icons diplaying your data connection type are a software glitch that my limited understanding is reporting a data connection but not necessarly showing accurately what type of connection 4g/3g/hspa/cdma/lte/gsm etc. because all of our carriers are not using the exact same network hardware but all are mostly compatible still - especially here in Canada. The network icons in the status bar are showing a data connection and your hardware is connecting but the labels are not quite right. By editing the build prop file you tell the phone whose network you are using so that it shows the right labels I don't think it's anything more than that.

Great ROM!
I confirm that it works on the D851 (T-Mobile, USA) model as well.

Anyone try the new radio with cm 12? How's the service and battery life? Both seem off for me.

Really annoying bluetooth problems on N6P

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.

Nexus 6 speaker issue POSSIBLE fix

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.