Hello all,
I own an S6 Edge G925I zeroltedv.
Every custom rom I try has a severe echo experienced by anyone that phones me or when I phone them.
Does anyone out there have a G925I with a custom rom that doesn't echo?
I have tried lineage 14.1 and 16.1 and a couple of oreo ports from elsewhere, and the official pie version of resurrection remix specific to the zeroltexx and zerltecan released Jan 2019.
I know I am not alone here, as others report the same issue in various forums here and elsewhere. I have read most of the threads where this issue appears and have tried their solutions, yet the echo continues.
Any ideas?... Anybody?
Or am I destined to the eternal servitude of my debloated 7.0 nougat overlord?
UPDATE
I have been reading a lot more on this echo problem with custom roms on the S6 edge and none of the solutions work for me apart from using earphones on one occasion.
I find this disappointing. Particularly when most of the threads end with the developer going quiet about this subject, yet answer other questions not related to this echo problem.
I do appreciate all efforts made by anyone offering their work for free and/or a handful of shirt buttons, yet I am pulling my hair out to find the definitive answer to this dam echo.
Why do some have success with other S6 edge models when myself and others don't?
I follow the instructions to the letter. Everything works fine after install, even openGapps installs seamlessly. Never any crashes, boot loops or soft bricking. Every thing works, including fingerprint, camera... I can't fault their performance.
Yet there's this confounded echo at the other party's end during a phone call.
Surely there is some bright spark out there with a solution to this that actually works.
Why does my stock rom have no echo? Is it because of something proprietary?
Related
Anyone else experiencing the other party complaining of an echo when your using speakerphone? I’ve read that it may be an issue with some cases, so I removed mine and had a few tests with no good results. I’m trying to narrow the problem down to either software or hardware related. I have lightly blown out both microphones and both speakers with compressed air. running uclf6 flapjaxxx latest update
simbill said:
Anyone else experiencing the other party complaining of an echo when your using speakerphone? I’ve read that it may be an issue with some cases, so I removed mine and had a few tests with no good results. I’m trying to narrow the problem down to either software or hardware related. I have lightly blown out both microphones and both speakers with compressed air. running uclf6 flapjaxxx latest update
Click to expand...
Click to collapse
I'm having the same issue with the 2.9b update. I'm currently look as well. if I find the issue, I'll post it here. Thanks.
joey30 said:
I'm having the same issue with the 2.9b update. I'm currently look as well. if I find the issue, I'll post it here. Thanks.
Click to expand...
Click to collapse
I have the same problem - Revolt ROM. Any progress?
I have tried two roms now (ReVolt, SlimBeam), and BOTH are producing the 'echo' issue on speakerphone. Does anyone have a handle on this or can they point me in the right direction to fix? Search has not been helpful so far.
Thanks!
The last ROM I ran that didn't have the speaker phone echo was the JamieD81 SlimBean 20130420 build. I believe there were some changes in the CM10.1 code that all the devs for aocp and aokp ROMs use that is causing this. That's just my guess though, I'm only a user not a developer. The only way I've found to get around the problem is to plug in my ear buds when I use speaker phone.
Speaker Phone Echo
Really now said:
The last ROM I ran that didn't have the speaker phone echo was the JamieD81 SlimBean 20130420 build. I believe there were some changes in the CM10.1 code that all the devs for aocp and aokp ROMs use that is causing this. That's just my guess though, I'm only a user not a developer. The only way I've found to get around the problem is to plug in my ear buds when I use speaker phone.
Click to expand...
Click to collapse
Yes I have noticed it on all of the CM10.1 based roms Collective, Pandroid, but on BlackStar no issue.
You're right about the Black Star ROM. It's built from the new 4.1.2 Samsung release and not on the CM 10.1 base. I did downgrade to the official Samsung release and didn't have echo nor on a debloated and deodexed version of it although it wasn't Black Star. And while I appreciate that we finally got an official release they were a little late to the party as far as I'm concerned. I'll take the occasional bugs in the CM 10.1 variants along with the speaker phone echo. Looking back to when we first got JB last summer the devs have made tremendous improvements and brought us options and customizations that the stock ROMs will never have.
I'm trying to figure out what the most stable and functional ROM is for my MDK VZW S4. I've tried to research this several times but I find that I have to essentially read through every thread for every ROM, and even then there are things that are left out. My previous phone was a Galaxy Nexus, so I was probably spoiled by the wealth of information about the various ROMs, but there's no reason we can't have a thread like this.
History of my ROM usage with my S4
I started out with Hyperdrive ROMs but later decided I just couldn't deal with TW no matter how much work the Hyperdrive guys did try to clean it up (kudos to them for the best ROM for people stuck with a locked bootloader though!).
Next up I went to Gummy ROM to try out 4.4, which honestly hasn't really impressed me. My GPS never works right, seemingly related to the compass problem? Not sure here, but this is a major deal breaker for me.
Problems I've had and seen mentioned in multiple threads; are these fixed in ANY ROM???
The above mentioned compass problems. I've read about factory calibration issues, I'm going to try a few of those fixes, but I also see a LOT of people saying this is a driver issue? Which is it?
HDR camera doesn't work, attempting to use it just makes solid black pics.
Bluetooth audio playback problems. I've heard this mentioned many times, but haven't had a chance to test myself. This only becomes a big deal for me in the summer when I'm using this feature to stream music to the stereo on my boat.
Thanks!
Dan
Hi, are there any problems with this smartphone? I'm coming from a Moto G4 with a screen burn-in issue, and I've read somewhere that this phone has it too, but I hope only some phones have it.
Also how is the microphone issue that some people claim it to have a bad quality? Has it been solved with official updates or only with community solutions?
Any other issues that I should be aware of?
I'm using xiaomi.eu rom right now, first time unboxing i got global stable MIUI8 rom, updated it to MIUI9. These 3 rom i haven't encounter any bugs related to audio, incall is fine, speakerphone doing good, recording audio or video went nice.
But i also try aosp custom rom, AEX, RR, even Xenon HD gave me the incall bug, nobody hear me whether i do the call or i took some calls.
the only way i can chat is using the apeakerphone mode.
i'm reading and searching for the same problem but no one did.
they had aosp custom rom running fine
do i did something wrong while flashing the rom?
only God knows
At some point in time my garage door opener app (MyQ by Chamberlain) stopped working. I upgraded a while ago to android 10 and have tried multiple flavors, settling on StagOS. The app now gives me a "error connecting to server" message when trying to do anything (log in, sign up for new account, forgot password, etc). Not sure what the issue is. I've tried fresh installs of StagOS and Potato with the same result. Have also recently (?) started failing safety net /CTS profile, so I'm not sure if that has something to do with it or not. No problems with my older tablet and wife's stock S9 running 10. Was hoping someone could install the app and see if they get the same issues, maybe let me know what ROM you're using. Thanks.
Anybody?
Seriously, nobody is willing to try this?
You're looking for a very specific user who 1) comes to XDA, 2) has a MyQ system, 3) has StagOS. It's not surprising you're not getting an answer, as there may not even be another person here with the exact setup you have... so how do you expect someone to test this? Your best bet is probably to ask on the StagOS thread, as you'll have more luck? (I haven't even heard of StagOS, but I also don't run a custom ROM.
Bottom line, you'll have to do the testing yourself, as you are probably too specific for others to help. For example, I don't have Pie, StagOS, or MyQ, so I can't help... I'm sure many others are in the same boat for various reasons.
Actually, I'm looking for someone who has any custom ROM to see if it's specific to this one, all lineage builds, Android 10 only, maybe a Google play services update broke it, etc. And you don't need a myq system. You just need to install the app and hit "sign up" to see if you get the error.
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
schwinn8 said:
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
Click to expand...
Click to collapse
I think he does need someone with an Android 10 LOS ROM. Not necessarily StagOS, but still an LOS ROM vs stock. I can't help either.
Yeah, if anyone has any other Android 10 custom ROMs it would be helpful to know if any work. I got safety net to pass, but that didn't do it either
Hi there, everyone. Relatively new to all this custom rom stuff, but I have been able to change roms and such with a usable level of success. A few months ago I ran into an issue that I can't seem to fix on my own, so I'm reaching out to see if someone more knowledgeable might have some experience and can point me in the right direction.
After test-driving a few different roms for a few months at a time, I ended up trying out ArrowOS. While I really enjoyed the rom itself, my phone would only ever use the speaker phone, even when it was set to use the regular ear speaker. Recently, I changed to LineageOS thinking the issue was with the Arrow rom, but the issue persists. I figured it was a firmware issue so today I flashed the firmware package and, to my surprise, the phone is still behaving the same way.
The firmware I flashed in was (fw_curtana_miui_CURTANAGlobal_V12.5.6.0.RJWMIXM_84796eb2cc_11.0.zip). It flashed with no errors, so I assume everything is fine there.
Anyone have any tips for me to follow? Much appreciated!
EDIT: This might be a newbie mistake, but the firmware I have flashed says it's for Android11 and the LineageOS I'm using is an Android 12 base. I wouldn't think it would make such a difference, but this is coming from a long-time Windows user who is used to getting by on old drivers when necessary. The ArrowOS I was using when the problem first popped up was Android 11, but I hadn't updated the firmware of the device so it may have still been on Android 10 (or even 9, I don't know).
Double posting for clarity. After trying multiple roms and firmwares, the problem still persists. The weirdest thing is that when using a hardware testing app, the earpiece speaker works fine. I've also tried using other dialer apps and they all act the same way. I am completely stumped on this. If anyone can help I would appreciate it, otherwise I guess I give up. This is way beyond me.