Related
I have just upgraded my Defy MB525 (green lens) to Jelly Bean 4.1.2, using CyanogenMod's Quarks.ru 2012-09-24 nightly build (the last one made for the MB525). It's working like a charm, the system is very smooth and bug-free, and I've noticed that battery life is longer, too. I'm loving it, except that predictably, I lost the ability to record calls (yes, it is legal here, that feature has helped me in more than one instance, and it is important for me).
Formerly, I used my carrier's official version of Froyo, with two modifications: it was rooted, and I replaced a system module with a Chinese Android version to enable call recording, as I saw this tip in various forums. It worked perfectly, with Sanity recording all incoming and outgoing calls crisply both ways. Now Sanity has stopped working; it tries to record the call, but it sends a message saying that it couldn't. I can make it record from the microphone, but then it only records what I say, not what the other person said on the call.
I won't risk using that Chinese module again, because it's an old tip and it was a Froyo module. Most certainly, it won't work with Jelly Bean and may even break the system. I have only found tips to enable call recording on Samsung phones, and an old one for Gingerbread on the Defy+ (MB526) with the warning that it caused phones with Ice Cream Sandwich not to boot. Not only is the MB526 a different model, but if ICS won't boot with that modification, so won't Jelly Bean.
Does anyone know how to restore full call recording capability to my phone? Thanks a lot.
You need to flash this http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip
It says it's for MB526 but it's for both MB525 and MB526.
Make a data wipe before flashing, you don't need to flash anything else, you can flash the gapps.
Once done, go-to Phone, press menu button, go-to settings, and find the option to enable call recording. The recorded files are stored in /sdcard/CallRecording
Sent from my MB526 using xda premium
Thanks a lot, hackergnome. :good: I'm going to try it and will post the results after it's done.
Call recording still not working after update
Well, I flashed the 2013-04-09 ROM, and thanks again to hackergnome for it, because I had Android 4.1.1 and now I have 4.1.2. I wish there was a 4.2 ROM that worked on the MB525.
I had two little scares while doing it. The first was that CyanogenMod reboots twice right after updating to 4.1.2, and both reboots take a very long time, with the LED lit in red, a behaviour I had never seen before. I almost panicked, but waited, and in the end the system booted fine.
The second scare was that until 4.1.1, there was a language choice option on first boot with all available languages. Now it's limited to English (UK and US) and Spanish, so for a moment I thought that Brazilian Portuguese was not available in this distribution. I'm fluent in English and have a reasonable working knowledge of Spanish (plus, there are some spelling and grammar mistakes in the PT-BR localization); I could use either language in the interface, but there are regional settings and utilities such as T9 and dictionary that are handy to have in the language I use most. Fortunately, Brazilian Portuguese was still available after boot in the phone's Settings.
Unfortunately, call recording is still not working. After configured to do so, the native phone feature only records the first 2 to 5 seconds (average 3 seconds) of both incoming and outgoing calls. Sanity was still unable to record calls (whether or not native call recording was enabled). After I uninstalled Sanity (thinking that one app might be interfering with the other), the native app still records only the first few seconds of each call.
Any hints? Thanks.
Working so-so after exploring further apps
I kept researching and found that some people had success installing Alsa Mixer. Supposedly, it has the same effect as that Chinese libaudio version had on Froyo, and makes call recording apps work. Here, it didn't work, and Alsa Mixer itself only presented a blank screen. I uninstalled it. I'm only mentioning this because other users may find the same tip. Don't waste your time with it - it may work with other phones, but not the Defy with CM10.
So, I kept trying the many call recording apps available from Google Play. User comments show that they all have an erratic record, working on some phones and not on others, so it's a matter of trial and error. I finally succeeded with Call Recorder by Clever Mobile (there are many apps all named "Call Recorder," so you have to differentiate them by the developer). Sound quality isn't the best (especially on the other party's side) and you have to make sure the app is on every time you turn on the phone. It doesn't register whether the call is inbound or outbound in the file name and doesn't register the phone number either; in fact, all file names are "Unknown." But at least it's working. The app is free with a small ad banner; there is a paid version without ads.
I really miss Sanity's options, flawless operation and crisp recordings that I used to enjoy when I was on Froyo. A pity that it doesn't work on Jelly Bean (at least not on the Defy with CM10). Sanity's development was stopped 2 years ago, so a new working version won't be coming. But now at least I can explore other options, knowing that I'll always be able to come back to Clever Mobile's solution if they don't work. I can't do it now due to time constraints, but if I find a better app, I'll post it here, so others with the same phone, OS and problem can use it as a reference.
So when I bought my Nexus 6P I knew I was going to get the latest updates as soon as Google released them. I also expected to find minor bugs because we are getting updates much faster as well.
What I was not expecting is to both, bugs that make for a nearly unusable device and minor annoying ones. For my device the bugs that hit me hard are;
Max Volume Bluetooth Speaker Bug - Most bluetooth speakers are stuck in max volume mode and can't be turned down. Distorts the audio and creates a situation were you could blow out the speaker. Not all speakers are effected.
No LTE On Boot - Annoying to have but "fixable" by putting the device in Airplane mode. Otherwise no Data or SMS until you do and hope your phone doesn't reboot in you pocket while waiting for an important message.
No Phone Calls - You can't make or receive calls. As a result you can't check VM either. No amount of Airplane mode or rebooting will fix it. Neither will the phone service menu.
My concern here is that Google hasn't patched these bugs yet, even after releasing another update to 6.0.1 M. For now I'm fine with downgrading to 6.0.0M but I'm missing out on updates.
To add to insult any ROM build with the 6.0.1 source is effected by these bugs, so I can't even use most ROMs unless I find an older version.
I guess my main question here is this:
Is this normal? Does Google usually go so long without patching the bugs?
Seems really silly to have a phone, but not be allowed to make or receive calls at all and not be able to send SMS or email unless you do a few tricks first. It's a phone. Don't they test these things?
Disclaimer: I already know not all 6P or Nexus devices are effected. That does add to my confusion as they all should be the same exact device.
EDIT: I also wanted to add that when I got the device I could do all these things however even downgrading will no longer allow phone calls. Something is retaining.
Well that's weird mate. I'm on 6.0.1 and have none of these problems.
I was experiencing awful battery life after the latest update but clearing the cache has made a huge difference
Have you tried reaching out to Google? It would be helpful if you could share how you upgraded to 6.0.1? As mentioned above did you clear cache? The more info you can provide; the faster someone can help you.
The Bluetooth volume issue is the only one I have and only on one of my speakers. The others with fine.
Huh, ya 6.0.1 here too and none of these issues are present.
Flashing the very first 6.0.0 (MDA89D).
In my ventures this last week or so, after dealing with the Battery issue (15-30% power off range) and having my speakerphone mysteriously stop working (It was as if I hit mute to the person on the other end) I have been doing all the research and tinkering I could think of to see if these were indeed hardware or software issues with our 6P.
So in my venture, It may be that 7.1.1 fixed the battery issue for me, as after 3 full rundowns over the past few days, I was able to run down to 3% and then 1% 2 times before shutdown which is immensely better than shutdown anywhere from at best 13% to ~25-30% at worst when you're trying to use your phone through the day.
This was done by running the Mountain app to put a load on the device while I do other things. Once I see it hit 15% I allow it to turn on Battery Saver and watch as it ticks down to 1-0% and goes into Shutdown.
Not sure how truly comprehensive this test is, but so far, it is pretty incredible to have such an improvement over what many of us have been experiencing with our battery life being a cointoss through the day.
I only had 7.1.1 flashed as a fresh image straight from google, TWRP 3.0.2-3 and SuperSU 2.78 SR5 for Root for this test. No Google Account connected or anything else syncing or updated that would touch the battery or run in the background.
Now for my Speakerphone issue. I cannot recall exactly when the issue happened, but since I have been running PN since literally the day I got my Nexus, somewhere in that time, with a lot of dirty flashing from one MM update to the next, messing with Kernels, and overall going quite a while between clean flashes until I finally did one for the move to 7.0, I lost my Speakerphone Mic and only the sound for speakerphone was coming out of the bottom speaker. After testing my Refurb replacement and now my "fixed" original 6P, sound for the speakerphone is supposed to use both Speakers when everything is working normally.
The test for this was easy to do with the Skype Test Call. Just call it and turning on Speakerphone would either work, it records my voice and plays it back, or when it wasn't working, it would just end quickly telling me it doesn't hear anything (and the audio only comes through the bottom speaker).
So TL/DR and plainly, my recommendation if you haven't already done so, and you are having similar interesting and semi baffling issues such as these, try flashing the oldest Image available for our 6P as I did (Directly from google, I just did the Flash-all.bat file as it was included with the minimal ADP terminal on Windows 8.1) and let it do its thing. Once I was in the original MM build, I just skipped my way to my homescreen, downloaded Skype from apkmirror, and logged into that to do the test. Boom! After the test was a success, I downloaded the 7.1.1 image, flash-all.bad'ed that and did the same skip to test.... And Boom! Speakerphone Continues to work normally.
Now to test the battery side by side with both devices to see how bad my old one has degraded if it indeed has done so... or if 7.1.1 has indeed fixed that as well.
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.
updated 2022-03-26 [discontinued]
Why do we need this?Recently I've spent a lot of time trying to find an Android 9+ ROM for my S7 flat that would have those two things working: 1. fingerprint in applications like Keepass2Android and other (banking), and 2. camera to not crash after 20 minutes of video conference. The main reason it took many hours is that most ROM topics do not have a reliable issue list ("Not working" part is usually empty). If you search the thread, assuming that you know what issue to look for, then usually you may find it (but not always).
So I decided that it would be nice to have one place, where anyone looking for a S7 ROM could find a more adequate list of issues so that it would also help decide which one has the required functionality that someone needs. Anyone installing a ROM and finding there an issue, can comment here and I'll update the list. This way we will have a very nice place to look for a ROM or compare them. This can also be a good place for developers of ROMs to find out who managed to figure out a solution for a specific issue, so that they can reach out to ask for information. Without further ado, here's the list (in alphabetical order):
S7 flat ROM issues
ROM name/linkAndroid versionLast ROM build dateMaintainerIssuesAICP 16112021-08-25@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
crDroid v7.13112022-01-11@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
NFC is not working
crDroid v8.1122022-01-21@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
DotOS v5.2112021-07-22@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
Evolution X102020-10-10@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
Evolution X 5.9.3112021-10-12@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
FloydQ V6.0102021-04-01@ananjaser1211
fingerprint won't work in some applications like Keepass2Android
there is echo issue in some applications like Facebook Messenger, less than LineageOS, but still. Here's @ananjaser1211's explanation on it.
phone encryption is not working
Havoc OS 3.x102020-08-08@expressluke
fingerprint won't work in some applications like Keepass2Android
during a speakerphone voice call other party can hear some echo of their own voice
SELinux: Permissive
LightROM92020-01-15@yash92duster
fingerprint won't work in some applications like Keepass2Android
Lightheart OS92020-10-30@Skulldron
fingerprint won't work in some applications like Keepass2Android
LineageOS 16.0 *92020-07-12@Ivan_Meler
during a speakerphone voice call other party can hear echo of their own voice
LineageOS 16.0 for MicroG92022-02-04@expressluke
SELinux disabled so the ROM is less secure, some applications will complain and for good reason. There are workarounds, but you may have hard times with some banking applications.
during a speakerphone voice call other party can hear echo of their own voice
LineageOS 17.1 *102022-03-15@Ivan_Meler
during a speakerphone voice call other party can hear echo of their own voice
LineageOS 17.1 for MicroG102022-02-17@expressluke
during a speakerphone voice call other party can hear echo of their own voice
LineageOS 18.1 for MicroG112022-02-20@expressluke
during a speakerphone voice call other party can hear echo of their own voice
LineageOS 18.1 *112022-03-12@Ivan_Meler
LED stops working after some time
during a speakerphone voice call other party can hear echo of their own voice (verified in Facebook Messenger video conference)
LineageOS 19.1 *122022-03-22@Ivan_Meler
during a speakerphone voice call other party can hear echo of their own voice
(verified in Facebook Messenger video conference)
MKUltraBlack92021-02-11@MKUltraBlack
fingerprint won't work in some applications like Keepass2Android
NFC payment is not working, Google Pay message: "The phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
SELinux: Permissive
NfeSuperleggera92020-12-12@arcatarc
fingerprint won't work in some applications like Keepass2Android
SELinux: Permissive
PixelExperience 11112021-09-23@expressluke
camera crashes after 20 minutes of video chat
during a speakerphone voice call other party can hear echo of their own voice
PixelExperience 12122022-03-12@expressluke
during a speakerphone voice call other party can hear echo of their own voice
ResurrectionRemix 8.x102020-10-08@expressluke
fingerprint won't work in some applications like Keepass2Android
built in microphone not working in some applications like Facebook Messenger (only headphones works for it)
echo issue in some other apps
* Some applications report this ROM as rooted and won't start. The reason is LineageOS comes with adb root feature by default. To fix it you will have to install root (Magisk with Zygisk or Magisk hide) to hide this state from those applications. Usually it works, but not always. It is not a bug and AOSP rules state that ROM should not fake it's status without user's knowledge, so I don't include it in the issue list. Still, it may be a disadvantage for some users.
As you can see some issues repeat on the list. The reason is if an issue is related to LineageOS on which many ROMs are based, most of them will have same issue.
One more thing: This topic is about ROM issues. I don't value here which ROM is better or worse, because there are many other aspects than just an issue list. Also please don't ask me to add here information about features. It may be fantastic but for another topic.
Camera crash is a known issue:
Camera doesn't close fd, resulting in crash after prolonged use · Issue #5 · 8890q/android_device_samsung_universal8890-common
This is caused by removal of fd close from libexynoscamera3.so lib 77e12d1 thing is with this edit both fd close are likely removed while we need it to stay so fds get closed properly figure out wh...
github.com
Update: will be fixed in February 2022 updates
Fingerprint on secure apps likely won't be fixed on the P/Q based stock os, however was fixed on aosp with the below:
android_device_samsung_universal8890-common/config.xml at d080020b8059bed189b3454737c6eb16ad137502 · 8890q/android_device_samsung_universal8890-common
Contribute to 8890q/android_device_samsung_universal8890-common development by creating an account on GitHub.
github.com
For anyone who is interested in knowing.
I was just about to write about this exciting news from @Ivan_Meler but you were first
There's one more issue that I know about and that affects probably all LOS ROMs which is echo that during a call other party can hear of his own voice, but I didn't test it personally on all the ROMs, so I can't be sure. I know for sure Pixel Experience 11 is affected and if anyone can confirm it for any other ROM please comment.
Again surprisingly LineageOS 16.0 for MicroG is somehow free of this issue ¯\_(ツ)_/¯ (from my tests not in 100%, but it's good enough).
how about GSI images? i wanna try them but my sd card just died for unknown reason and cant back up my current data(rom)
waayo69 said:
how about GSI images? i wanna try them but my sd card just died for unknown reason and cant back up my current data(rom)
Click to expand...
Click to collapse
If you will test it please let me know the results and I'll be happy to add those to the summary.
sure! btw how do i install gsi roms ? they're on .img file. twrp only has boot and recovery when installing img files
waayo69 said:
sure! btw how do i install gsi roms ? they're on .img file. twrp only has boot and recovery when installing img files
Click to expand...
Click to collapse
[Treble][AOSP][G930X/G935X]Project_Pizza TreblePort V2.0
Welcome to Project Pizza Treble For Galaxy S7 / S7 Edge Exynos Some information you should know.. This is a full Samsung based Treble Vendor/Kernel implementation for the Exynos8890 If you want to report a Bug, read the F.A.Q First Then...
forum.xda-developers.com
for android 9/10 gsi (then you can flash img files)
android 11 up
Release LineageOS 18.1 vndk30 treble for herolte · Kethen/lineage_build_scripts
Credits https://github.com/8890q/ for LineageOS 18.1 on 8890 https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs Notes: I do not o...
github.com
I think the "echo" issue is now the most important one for LineageOS based ROMs. There's a lot of postings about it for S7 (flat and Edge) since 2016 (so 6 years now). Some of those:
Echo when using Speaker during call
Desperate search for solution of echo problem
Is there any rom does not have echo for S7 with Android 10
Strong echo in handsfree calls due to the output to the wrong speaker?
Echo voice Phone Calls S7 edge Issue
Problem with Whatsapps and VoIP apps S7
How to build ROM with echo fixed
S7 Edge Call Echo HELP!!
And here's an explanation by @Ivan_Meler why this issue is so hard to fix. Apparently the issue do not affect all of S7 devices so lucky ones would not have problem with it when using LineageOS.
Hi,
Very useful post, the one you should definitely read before testing rom's ; indeed, the echo issue unfortunately makes many of them unusable.
Thank you.
edit : echo issue with Ressurection Remix 8.6.2
edit.2 : no echo issue with FloydQ V6.0
woam said:
Hi,
Very useful post, the one you should definitely read before testing rom's ; indeed, the echo issue unfortunately makes many of them unusable.
Thank you.
edit : echo issue with Ressurection Remix 8.6.2
edit.2 : no echo issue with FloydQ V6.0
Click to expand...
Click to collapse
Thank you @woam . About the echo issue I've spent some time today to test it across different ROMs. For FloydQ it is in fact much better than LineageOS based ones. Interesting thing about FloydQ that there's no echo in WhatsApp (LineageOS has echo here), but there is echo in Facebook Messenger. For ResurrectionRemix other party couldn't hear me at all in Facebook Messenger as if my telephone's microphone didn't work, I had to use headphone's microphone and then it was ok.
Summing up my today's echo tests:
LineageOS based ROMs: echo for both WhatsApp and Facebook Messenger (even on Android 9 / LineageOS 16)
Samsung OneUI ROMs:
Android 10:
FloydQ: WhatsApp no echo, Fb Messenger has echo (didn't find any other sound issues in FloydQ)
ResurrectionRemix: mic not working on Fb Messenger
Havoc OS: some echo in Fb Messenger, it's like the echo is less, but also the volume on both sides is lower so the call is not that comfortable
Android 9:
MKUltraBlack, NFESuperLeggera, LightROM, Lightheart - no echo for both WhatsApp and Fb Messenger
Hi Kootarsh, your table does not say that LOS 19.x has the "hears echo of their own voice" problem. Is it really true?
Thanks!
I checked the forum and the echo issue (link) is also there present.
.Michael. said:
Hi Kootarsh, your table does not say that LOS 19.x has the "hears echo of their own voice" problem. Is it really true?
Thanks!
I checked the forum and the echo issue (link) is also there present.
Click to expand...
Click to collapse
I've tested the latest build. @Ivan_Meler fixed it mostly in the last build, so in my tests of this ROM echo very rarely appears (it doesn't bother other party). The only issue now is that other party hear my voice to be quiet, so it may be still bit uncomfortable.
Sounds like mic sensitivity is either always too low to prevent echo, or too high with most custom ROMs for S7, could be missing a sweet spot but i assume it lacks decent audio filtering that the stock firmware has.
For now i will stay on stock android 8, honestly it feels OK with most bloat disabled. Got a this device for free anyway as someone who never buys smartphones. But my OCD craving for an fully functional android device free of bloat and in fully in users control remains here. Just as Linux with laptops i always had problems with custom android ROMs.
If a piece of mobile phone hardware existed with actual fully accessible hardware and drivers for devs i would consider buying it; if that even exists.
For now i will do a battery replacement and just enjoy my S7 as it is.
XV1001 said:
Sounds like mic sensitivity is either always too low to prevent echo, or too high with most custom ROMs for S7, could be missing a sweet spot but i assume it lacks decent audio filtering that the stock firmware has.
For now i will stay on stock android 8, honestly it feels OK with most bloat disabled. Got a this device for free anyway as someone who never buys smartphones. But my OCD craving for an fully functional android device free of bloat and in fully in users control remains here. Just as Linux with laptops i always had problems with custom android ROMs.
If a piece of mobile phone hardware existed with actual fully accessible hardware and drivers for devs i would consider buying it; if that even exists.
For now i will do a battery replacement and just enjoy my S7 as it is.
Click to expand...
Click to collapse
mic sensitivity is not any lower than on stock its actually a bit higher, reason why i lowered is that samsung limited mixer gains in frameworks and aosp doesnt do that.. People tend to take anything from changelog as a placebo so even if i dont change something and post it in changelog they would say they feel the difference
Ivan_Meler said:
mic sensitivity is not any lower than on stock its actually a bit higher, reason why i lowered is that samsung limited mixer gains in frameworks and aosp doesnt do that.. People tend to take anything from changelog as a placebo so even if i dont change something and post it in changelog they would say they feel the difference
Click to expand...
Click to collapse
I honestly did not study the changelog at that time, as i never used a custom rom for the s7 prior. Only for Moto Gs in the past. First ROM tried was 19.1
I liked everything, camera was fine too for VDO calls (it has network bottleneck anyway with most applications) , i didnt notice microphone issues myself, but it was my SO complaining, and hanging up/re calling 3 times to check what was wrong, it was then after that ,that i told i was on a different android ROM. Havent tested it with video recording, but if she noticed it that badly while barely knowing what a ROM is(let alone changelogs); then i have to believe by that.
After flashing stock rom, i dived into different threads about S7 microphone issues with various ROMs.
Hi,
Thank you Kootee83 for this list.
I am posting about the sound problems during phones calls. (echo and bad quality sound)
I have tried LOS from 17.1 to 19.1 and I have always a problem with echo on the other party for LOS17.1 and LOS 18.1 with good sound quallity on my side.
For LOS 19.1 I have echo on the other party and bad sound quality on my side.
A lot of replies stated a hardware problem on some phones.
But I installed Havos OS 3.x and with this ROM I don't have any issue with echo or bad call quality and this, on two different S7( Canadian versions).
So can someone please try to explain to me why the argument about different hardware is the cause for these problems still valid.
Why for my two phones Havoc OS 3.x is working perfectly, what is the difference between Havoc 3.x and the LOS.
I am not a coder and I mean no disrespect for those who build amazing ROMS but the sound problem is a real bummer.
Thank you all.
lebon00 said:
A lot of replies stated a hardware problem on some phones.
But I installed Havos OS 3.x and with this ROM I don't have any issue with echo or bad call quality and this, on two different S7( Canadian versions).
So can someone please try to explain to me why the argument about different hardware is the cause for these problems still valid.
Why for my two phones Havoc OS 3.x is working perfectly, what is the difference between Havoc 3.x and the LOS.
Click to expand...
Click to collapse
Hi @lebon00 ,
I don't know details but in fact I've seen in many comments that Havoc OS behaves differently even though it states it is based on AOSP like LOS is. I believe Havoc may have proper settings in the mixer_paths_0.xml for your phone. Seems that different settings are needed for different S7 devices.
I've spent a lot of time trying to find a ROM that would work good enough, that I could use it daily for calls without sound issues like echo. I don't need any of those fancy tunes and improvements, just reliable working phone
Unfortunately I haven't found anything good for my S7 better than Android 9 (NFE port ROMs). FloydQ is quite good, but unfortunately has also echo in some applications. On the other hand all those stock based ones (including FloydQ) have the fingerprint issue - it's a bit annoying. So, summing up, best reliable ROM for S7 is still Android 8. If you can live with not working fingerprint in some banking apps then Android 9 (NFE port) like LightROM would be my choice. If you wouldn't care about echo in some communication apps then you'd have more choices.
Kootee83 said:
I've tested the latest build. @Ivan_Meler fixed it mostly in the last build, so in my tests of this ROM echo very rarely appears (it doesn't bother other party). The only issue now is that other party hear my voice to be quiet, so it may be still bit uncomfortable.
Click to expand...
Click to collapse
At my phone (a device bought in Germany) nothing changed, I currently use LOS 17.1-20220407 version.
This:
LED stops working after some time
I have also since the beginning.
.Michael. said:
At my phone (a device bought in Germany) nothing changed, I currently use LOS 17.1-20220407 version.
This:
LED stops working after some time
I have also since the beginning.
Click to expand...
Click to collapse
Same also happened already in LOS16, first LED stops for notifications, then also for charging indication.
i think i may have found a new one too, it is the wifi, after several hours on 5ghz (more time on 2.4) it disconnects and can't find any network until i turn off then on the wifi toggle
in the meantime untill it disconnects some hicups do happen, like some big lags in the game "war alliance" or even game disconnect for "8 ball pool", but on ookla speedtest nothing appears, speeds seem fine
tested on crdroid 7.13 and lineageos 18.1, will test more builds soon
anyone else can confirm please (wifi must be used, some traffic must happen)