Related
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
So i finally gave cm 12.1 a chance because it's been rolling for a while now... and i was actually pretty impressed. The one issue i couldn't deal with is the bluetooth audio playback in my car. Basically it was playing too fast, then pausing every 10-20 seconds and then continuing to play too fast again (also at a slightly higher pitch). I was able to temporarily fix the problem by turning bluetooth off and on but it came back. other than this i didn't see many issues and thought it was pretty good, but for no i'm going to go back to stock until this issue is fixed, i did find that it was already reported to the cyanogenmod team and they are already working on a fix so i'm waiting impatiently until it's fixed and i'll probably be moving from stock kitkat as my main rom to cm 12.1. How has everyone elses experience been with cm 12.1 nightlies so far?
What doesn't work. (if i missed something here post so i can update)
- saving 4k video (1080p works tho)
Battery life ?
- used to be terrible but it's almost as good as stock now but with better performance.
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Brtnsk said:
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Click to expand...
Click to collapse
1. Quickcircle won't work. To make it work again you have to install a special app. Google text-to-speech works ok for me (I haven't test it too much). LG features/apps won't work
2.For me the quality of pics and videos are the worst I have ever seen!!!! (Much better in the stock LG)
My experience with CM12.1 was average. I was waiting for something better. Camera is awful in the Custom roms. Battery life wasn't the best. In terms of performance the cm12.1 is better than the stock lg.
i've only been running cm 12.1 for a few days now so i don't have alot of substantive input, i did find a fix for the bad bluetooth car audio using a macro/tasker app but i think they have fixed it in the nightly released today, i'm downloading it now it says bluetooth stream parameters in the patch notes so i wont bother sharing my fix until i try this nightly to see if they already fixed it. i'll give a better review of whats working and the camera/video quality after i have a chance to play around with it more.
by the way anything running ART instead of DALVIK cache/runtime is going to perform better but it's at the price of xposed modules and such, i'm not expert on it but i know they switched to ART cache/runtime to be more competitive with the iphone. On Kitkat and lower an android device needs better hardware to output the same performance as an iphone with lesser hardware. ART should fix that problem. If you are curious google ART vs DALVIK
*edit* yeah bluetooth is fixed with the newest nightly update... atleast for my car which is a mazda 3. (yay)
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
it's getting alot better every day now
netmaniack said:
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
Click to expand...
Click to collapse
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
c_brown93 said:
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
Click to expand...
Click to collapse
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
I switched to stock kitkat, I love CM, been running CM since it was 10.1, the problem is that it starts really really fast and after a while CM 12.1 becomes laggy it drives me crazy, other than that is the camera quality which doesn't bothers me as the performance issue,
I guess we'll need to wait for LG to release the G3 source file but who know's when that's gonna happend
good news the latest daily added some balancing between power and battery life. I went from losing a huge chunk of my battery during work when my phone is in my pocket to going 9.5 hours at work and coming home with 94% battery. (that is alot of standby but i use my phone at lunch and have bluetooth running for about 50 minutes of driving). Basically it got alot better, i'm not sure what they did but i did notice that there is a balanced setting in battery screen that i didn't notice before. Anyways I think those who were concerned about battery drain my have had their wishes answered over the last few nightlies.
netmaniack said:
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
Click to expand...
Click to collapse
i still can't get 4k video to save but 1080p did.
Do knock on and knock code work?
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Knock on works but knock code doesn't, which is quite normal considered it's an LG feature.
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Partly working. You can turn screen on by clicking anywhere, and turn it off by knocking at notification bar.
Phone encryption not working?
I've just flashed the 20150603 CM12.1 and I cannot seem to get the phone encrypted. On the reboot to start the encryption, the phone gets stuck in the CM boot animation and the encryption process never starts. Any ideas or suggestions? Many thanks in advance.
I'm on 06/05 nigthly. When I plug the phone in my computer, it's not being recognized. If I change from MTP to PTP, then it works.
I've tried going to Device Manager, and could see that my phone is being recognized as a Nexus device. I tried installing latest drivers from Google's website, but I got a message saying that I'm already on the latest version. So that didn't do anything. I've tried uninstalling that "nexus" driver and rebooting my PC, but it somehow came back when I plugged my phone in. Trying to update gave me the same message.
If I run "adb devices", I can see that there's no devices (it's enabled in developer settings). If I enable ADB over WiFi and try to connect -- it works, and I can do whatever I want. But only over WiFi and not via USB.
Tried different cable and different port as well.
Hello XDA,
I recently got my hands on an S5 (SM-G900F) and it seems better than my Nexus 5, so I want to make it my main phone. As I do with all my phones, I immediately removed the vendor's bloatware/spyware by rooting and installing some custom ROM. This time I started with CM12.1, which seemed to be OK based on various comments here and reviews online.
However, I've run into several serious problems.
1.) Erratic Bluetooth behavior:
When paired with my car audio system, there are frequent pauses and "static" noises. Also, sometimes, when it pairs with the car, I can control the music via the car's navigation buttons but the music plays through the phone's speakers (!?!?). One more annoying issue: it pairs but sometimes wont start the music player, no matter how many times I press the "Play/Next" button on the car system.
2.) Wi-Fi Issues:
No matter which Wi-Fi I connect to, after a couple of hours I get the warning icon and I cannot access the internet (and it won't even switch to mobile data), so I miss important stuff without realizing. This is fixed by simply turning the Wi-Fi off and on again but, still, it's a show stopper.
3.) Random vibration:
I don't understand why the S5 just randomly vibrates in my pocket or why it vibrates and the screen turns on whenever I move it. I've found it unlocked and with random apps open, many times, after taking it out of my pocket...
4.) Bad Camera app
The Camera app that came with CM12.1 cannot take a single good picture; they're all blurry. It seems to have a problem with auto-focus. I had to install Snap Camera to take pics.
Since I originally installed CM12.1 based on positive feedback here on XDA, I would like to be a bit more cautious this time and ask people with more hands-on experience with the S5 to suggest a more stable ROM for me. I don't have any particular preferences. Anything that can run Nova Launcher is fine.
Thank you very much for your help
sekl_ said:
Hello XDA,
I recently got my hands on an S5 (SM-G900F) and it seems better than my Nexus 5, so I want to make it my main phone. As I do with all my phones, I immediately removed the vendor's bloatware/spyware by rooting and installing some custom ROM. This time I started with CM12.1, which seemed to be OK based on various comments here and reviews online.
However, I've run into several serious problems.
1.) Erratic Bluetooth behavior:
When paired with my car audio system, there are frequent pauses and "static" noises. Also, sometimes, when it pairs with the car, I can control the music via the car's navigation buttons but the music plays through the phone's speakers (!?!?). One more annoying issue: it pairs but sometimes wont start the music player, no matter how many times I press the "Play/Next" button on the car system.
2.) Wi-Fi Issues:
No matter which Wi-Fi I connect to, after a couple of hours I get the warning icon and I cannot access the internet (and it won't even switch to mobile data), so I miss important stuff without realizing. This is fixed by simply turning the Wi-Fi off and on again but, still, it's a show stopper.
3.) Random vibration:
I don't understand why the S5 just randomly vibrates in my pocket or why it vibrates and the screen turns on whenever I move it. I've found it unlocked and with random apps open, many times, after taking it out of my pocket...
4.) Bad Camera app
The Camera app that came with CM12.1 cannot take a single good picture; they're all blurry. It seems to have a problem with auto-focus. I had to install Snap Camera to take pics.
Since I originally installed CM12.1 based on positive feedback here on XDA, I would like to be a bit more cautious this time and ask people with more hands-on experience with the S5 to suggest a more stable ROM for me. I don't have any particular preferences. Anything that can run Nova Launcher is fine.
Thank you very much for your help
Click to expand...
Click to collapse
Hello, first time posting on XDA.
Recently bought a G900F aswell, rooted and flashed straight away the latest build of CM 12.1. Glad to see someone with the same issues as me.
Starting with the camera, I also notice the blur and the extreme auto focus problem. Good to know that others have it because I didn't even try it on stock so I was worried it was a hardware problem, going to give it a try on it or on another ROM to see the difference. I had a P970 and it also had camera problems initially with CM so I'm guessing it's normal for klte since there are only a few nightlies out yet.
The random vibrations are a thing, the phone heats sometimes and the battery autonomy isn't the best.
As for ROM's I'm going to start with SIXPERIENCE 7.0 because CM isn't kinda giving it to me yet, but I'd gladly hear which ones you guys recommend.
Stock ROMs are incredibly stable and smooth with a new launcher like Nova
Since the last dev preview up to the final release, I've been having some major issues getting Viper4Android to work properly with Spotify and Google Play Music. For whatever reason, it works for a few minutes after the initial Nougat setup, then stops working whenever I'm steaming music. When I look at the driver status, it says "processing: no."
However, on Pocket Casts things are running normally - which is less than ideal since I turn it off when listening to podcasts.
I've forced permissive mode at boot, removed MusicFX, the audio effects file in the root folder, yet I still can't get it to work properly. I've even flashed various "fixes" and versions of Viper4Android, still, nothing changes.
This is exactly what kept me from staying on the dev previews, and I'm bummed to see nothing has changed since the final release.
I'm on the verge of pulling my hair out! Has anyone successfully gotten Viper4Android to work properly on Nougat, and if so, how?
It is entirely possible that viper needs to be updated due to changes in the coding. This would be something you may want to ask about over at the actual viper forum
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.