The ECHO - LineageOS Questions & Answers

When placing or receiving a voice call (LOS 14.1, Samsung Galaxy S6, current build) the other party hears their own voice echo back in approximately 1.5 to 2 seconds. It depends on what is being used on the S6 to make the call. If the built-in microphone and speakers are used, the echo is very problematic. It is less noticable with a Bluetooth headset, and it is completely not there if one uses a wired headset (in this case a pair of Samsung wired earplugs). With the stock ROM, this does not occur. Perhaps there is a set of build.prop entries or other yet-to-be-documented settings to address the noise cancellation issue ? An otherwise rather excellent ROM, it would be a shame to not be able to use it if it required earplugs for voice calling. An extensive search through the other Galaxy S6 forum postings and the forum specific to the ROM reveals nothing of particular value, but maybe something was overlooked. Suggestions, anyone?

nezlek said:
When placing or receiving a voice call (LOS 14.1, Samsung Galaxy S6, current build).......
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3738447
I did come across the following thread that may be helpful for what you are looking for.
https://forum.xda-developers.com/showthread.php?t=3795558
If all else fails, and you don't receive any support from the above threads, then your next best bet is to post this question within the following Q&A thread that's specific to your device and variants as well.
https://forum.xda-developers.com/showthread.php?t=3110220
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

Thanks
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3738447
I did come across the following thread that may be helpful for what you are looking for.
https://forum.xda-developers.com/showthread.php?t=3795558
If all else fails, and you don't receive any support from the above threads, then your next best bet is to post this question within the following Q&A thread that's specific to your device and variants as well.
https://forum.xda-developers.com/showthread.php?t=3110220
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks again for the interesting and useful suggestion(s). I thought I had exhausted the possible S6 support locations on XDA, so it a always a pleasant surprise to find even more. Unfortunately, no news was to be found there, either. I suspect that some "out of the box thinking" might be required to address this one, which is why I have floated this inquiry beyond what might be thought of as the usual places. Lots of other device owners (e.g. One Plus, etc..) seem to have reported echo problems on voice calls using LOS, with a variety of suggestions about how to address the problem. I can't believe that everyone uses headphones (which do make the problem go away) for all of their voice calling, so somewhere there is an answer. What I have found most peculiar is that MY device has no echo issues. It is the device on the other end of the connection that is exhibiting the echo, regardless of who makes the call. As the saying goes: "curiouser and curiouser..."

nezlek said:
Thanks again for the interesting and useful suggestion(s). I thought I had exhausted the possible S6 support locations on XDA, so it a always a pleasant surprise to find even more. Unfortunately, no news was to be found there, either. I suspect that some "out of the box thinking" might be required to address this one, which is why I have floated this inquiry beyond what might be thought of as the usual places. Lots of other device owners (e.g. One Plus, etc..) seem to have reported echo problems on voice calls using LOS, with a variety of suggestions about how to address the problem. I can't believe that everyone uses headphones (which do make the problem go away) for all of their voice calling, so somewhere there is an answer. What I have found most peculiar is that MY device has no echo issues. It is the device on the other end of the connection that is exhibiting the echo, regardless of who makes the call. As the saying goes: "curiouser and curiouser..."
Click to expand...
Click to collapse
Same here. I still wondering what causing the problem on my Note 5 (RR&Lineage). Have you found any solution other than using a wired headset to receive and make call?
I'm still thinking about this answer from https://forum.xda-developers.com/general/help/echo-problem-callers-phone-t3550550: "It seems to me that your mic is picking up the sound that your speaker is emitting and then feeding back to their phone. If you are on stock, try turning the in call volume down so that your speaker isn't so loud."
And I'll try to reduce the in-call volume and will report it later.

Echo
Same here with Samsung A15 and Lineage 16 custom ROM
Caller hear a strange echo
I tried change in build prop the value setting of fluence.speaker = false with no succes

Anyone found a solution yet?
I'm having the same problem.

Same problem.

So evidently this is a source problem propagated all over the all kind of ROM based on this project

Brignoud said:
So evidently this is a source problem propagated all over the all kind of ROM based on this project
Click to expand...
Click to collapse
Where can I find more info about that?

Same thing for me on my SM-G920F using 15.1.2019022-UNOFFICIAL-zerofltexx.
Call if fine for me, but other person can hear themselves with a couple of seconds delay. Doesnt matter who starts the call or what method for me. Did the same using bluetooth setup in car.

Brignoud said:
So evidently this is a source problem propagated all over the all kind of ROM based on this project
Click to expand...
Click to collapse
Exactly my thoughts, because in have 3 different devices on Lineage 15.1 and 16 that all exhibit this behavior.
Seems like it would be an easy and IMPORTANT fix to the base/source. Just correcting the issue somewhere in the base code should correct it for everyone...

KeepingItCuttingEdge said:
Exactly my thoughts, because in have 3 different devices on Lineage 15.1 and 16 that all exhibit this behavior.
Seems like it would be an easy and IMPORTANT fix to the base/source. Just correcting the issue somewhere in the base code should correct it for everyone...
Click to expand...
Click to collapse
Yeah, this is affecting me on three different devices all running 16.0. Sad, I had to go back to the stock firmware because I cannot talk to loved ones.

Hello, i have the same problem with Samsung Galaxy S7 edge (SM-G935)
I found a video on youtube "How to fix mic and speaker in custom ROMs ?"
Use BUILDPROP EDITOR to edit and add "ro.qc.sdk.audio.fluencetype=none"
but don't work for me

Tonio0 said:
Hello, i have the same problem with Samsung Galaxy S7 edge (SM-G935)
I found a video on youtube "How to fix mic and speaker in custom ROMs ?"
Use BUILDPROP EDITOR to edit and add "ro.qc.sdk.audio.fluencetype=none"
but don't work for me
Click to expand...
Click to collapse
YouTube? Really? I guess the download link for your ROM was from YouTube also. Without telling you, who actually built it? Thats the person you shouting ask for a fix.

kurtn said:
YouTube? Really? I guess the download link for your ROM was from YouTube also. Without telling you, who actually built it? Thats the person you shouting ask for a fix.
Click to expand...
Click to collapse
Hi kurtn, i just try to fix a problem, I sought "ro.qc.sdk.audio.fluencetype" and i found a video that explain how to edit the prop .. i don't understand your reply ?

Tonio0 said:
Hi kurtn, i just try to fix a problem, I sought "ro.qc.sdk.audio.fluencetype" and i found a video that explain how to edit the prop .. i don't understand your reply ?
Click to expand...
Click to collapse
Do you have a custom ROM insalled? What exactly?

kurtn said:
Do you have a custom ROM insalled? What exactly?
Click to expand...
Click to collapse
Yes, lineage OS 16.0 + magisk.
The echo is only with the speaker on, the caller hears himself speak

Tonio0 said:
Yes, lineage OS 16.0 + magisk.
The echo is only with the speaker on, the caller hears himself speak
Click to expand...
Click to collapse
Maybe you should post there https://forum.xda-developers.com/s7-edge/development/beta-lineageos-16-0-s7-edge-hero2lte-t3842464
Or downgrade to 15.1

Possible solution? Confirmation needed
Hello, I'm new as a poster here.
I had the problem with my Galaxy S4 VE (jfvelte). I had ResurrectionRemix (Marshmallow) for years and found LineageOS 16 for my device, so I installed it successfully and all seemed to be better, Camera is much more stable, better battery drain. After two days I noticed the problem with the echo for caller on two different devices (Modem I9515XXU1BPK4).
I didn't find any solution, only an open issue on GitHUB.
I downgraded to 15.1, same Problem.
I downgraded once more to 14.1. Problem fixed. All fine, but I didn't want to stay with this old sticky nougat stuff .
From the audio fix patch from sombree i knew that the problem is somewhere into the two files "audio_platform_info.xml" and "mixer_path.xml", but his fix is for 14.1, and not for 16.
So I tried to reinstall 16, and replaced the two files with the ones from 14.1 (the path have been modified from /system/etc to /system/vendor/etc).
NOW I HAVE 16 WITH NO ECHO PROBLEM. Other sound devices seem to work (Tested Speaker, Bluetooth and headphones/headset).
Being a Windows developer and no Android/Linux expert, I have no real idea from what I've done, so I wanted someone (maybe a real expert) to tell me:
Is my solution working (seems to be so)?
Why didn't someone had the Idea before?
Why have they (LineageOS devs) broken it?
Maybe I could help, and please fix it directly in ROM.
I've build a flashable patch with the "ZIPme" app. Should I upload it?

DarthNAL said:
Hello, I'm new as a poster here.
I had the problem with my Galaxy S4 VE (jfvelte). I had ResurrectionRemix (Marshmallow) for years and found LineageOS 16 for my device, so I installed it successfully and all seemed to be better, Camera is much more stable, better battery drain. After two days I noticed the problem with the echo for caller on two different devices (Modem I9515XXU1BPK4).
I didn't find any solution, only an open issue on GitHUB.
I downgraded to 15.1, same Problem.
I downgraded once more to 14.1. Problem fixed. All fine, but I didn't want to stay with this old sticky nougat stuff .
From the audio fix patch from sombree i knew that the problem is somewhere into the two files "audio_platform_info.xml" and "mixer_path.xml", but his fix is for 14.1, and not for 16.
So I tried to reinstall 16, and replaced the two files with the ones from 14.1 (the path have been modified from /system/etc to /system/vendor/etc).
NOW I HAVE 16 WITH NO ECHO PROBLEM. Other sound devices seem to work (Tested Speaker, Bluetooth and headphones/headset).
Being a Windows developer and no Android/Linux expert, I have no real idea from what I've done, so I wanted someone (maybe a real expert) to tell me:
Is my solution working (seems to be so)?
Why didn't someone had the Idea before?
Why have they (LineageOS devs) broken it?
Maybe I could help, and please fix it directly in ROM.
I've build a flashable patch with the "ZIPme" app. Should I upload it?
Click to expand...
Click to collapse
Could you please post there?
https://forum.xda-developers.com/galaxy-s4/unified-development/official-lineageos-16-0-t3954912
I think that issues are device specific.

Related

[Q] viber and mobile voip problems

Hi guys,
I had issues with viber and mobile voip ( voip application ) on the original sense rom when i got the phone new last time. Because of that and the advantages of custom roms, i went to CM based roms. It was great. Thing is i missed the sense look and feel....Long story short, i now have Renovate Rom with the kernel supplied with it. I am facing the same problems again. People on the other end cant hear me, and call connection is poor. A friend of mine said its due to sense 4+. Please do help me solve this, as i love the sense, just that this is whats putting me off...Thanks guys.
Hi,
This is Viber's rep. I'm here to help.
It sounds like the typical Custom ROM issue - some custom ROMs alter the microphone definitions of your phone, causing Viber not to recognize the phone's microphone properly. That is the reason that Viber cannot transmit your sound to the other side. We discussed this issue in detail with our users in this thread on XDA Forums: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
Please note that in that thread, a workaround was suggested *by a user* that seemed to have solved the problem for Galaxy S+S2 users.
Let us know if the issue persists.
Thanks,
Viber
Viber Team said:
Hi,
This is Viber's rep. I'm here to help.
It sounds like the typical Custom ROM issue - some custom ROMs alter the microphone definitions of your phone, causing Viber not to recognize the phone's microphone properly. That is the reason that Viber cannot transmit your sound to the other side. We discussed this issue in detail with our users in this thread on XDA Forums: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
Please note that in that thread, a workaround was suggested *by a user* that seemed to have solved the problem for Galaxy S+S2 users.
Let us know if the issue persists.
Thanks,
Viber
Click to expand...
Click to collapse
Hi, and thanks for the link...checked it out....well, i was having the same problem earlier with the original htc rom when i bought the phone...thats the reason i was soo eager to change to custom roms....Its working excellently on cm based roms, so is my mobile voip....My friend also said, he had issues with bad internet/wifi when he updated his old one x to sense 4+, and everything was fine on sense 4.0......The link u suggested says to change some stuff which it says for samsung galaxy.....It would be really great if you would be able to point me to the right direction on this, as i believe its not just because its a custom rom as i had the exact same issues with original HTC rom....Thank you very much...Hope to hear a solution from u soon...
Hi again,
I apologize for my late response.
Unfortunately there is not much we (Viber) can do to help, as official representatives
The fact that the problem was solved on CM, but is now present again on the new ROM you're using, suggests that it is indeed a problem with the ROM (and not Viber). We recommend that you contact people on that thread, or in other threads here on XDA, who might have had similar issues. At this stage we (Viber) will not be able to suggest a solution for this problem, caused by the Custom ROM
Viber Team said:
Hi again,
I apologize for my late response.
Unfortunately there is not much we (Viber) can do to help, as official representatives
The fact that the problem was solved on CM, but is now present again on the new ROM you're using, suggests that it is indeed a problem with the ROM (and not Viber). We recommend that you contact people on that thread, or in other threads here on XDA, who might have had similar issues. At this stage we (Viber) will not be able to suggest a solution for this problem, caused by the Custom ROM
Click to expand...
Click to collapse
Its alright...Thank you very much...i hope someone else on standard htc rom can help, or maybe if sense 5 comes out for one x, it would be solved.....I love viber on CM10.1.....like a regular call..best off all, free.....support you guys all the way....

Known ROMs with working phone mic?

Are there any known 4.3 or 4.4 ROMs with working phone mic?
I've used CM 10.2 Stable (4.3) and Carbon Rom (4.4.2). Both work great, the only issue is that the headset is not usable for calls (low mic output). My solution for now is using the earbud/mic, but I'm curious to know if anyone has made progress on this. Aside from this, the various ROMs are near perfect for my needs.
I'm not very knowledgeable on the details of writing ROMs, but would any type of source code release from LG help developers solve this? Curious to know what the main hurdles are for the devs and what tools they need.
Thanks.
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Neroga said:
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
markusrussell225 said:
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
Click to expand...
Click to collapse
Still no luck on a solid working phone microphone (low volume on other end). And the search continues.
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
markusrussell225 said:
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
Click to expand...
Click to collapse
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
ja.andro said:
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ask because this is a problem has existed on all known roms since 4.3.1 for the E980 on ATT. Never been able to get a straight answer anywhere so I figure I would generically post it. I have reached out to some devs but not luck.
Any success on your searching?
thureos said:
Any success on your searching?
Click to expand...
Click to collapse
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
markusrussell225 said:
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
Click to expand...
Click to collapse
I saw that solution but I went back to rooted and debloated stock, I am very pleased with speed and stability.
Thanks
i've made the edits suggested on that post and still get the same issue...i dont remember having this issue before but i thnk youre right and the previous roms werent 4.4...oh well i live on the phone for work so back to stock for me. for now i guess...wanting a new phone anyways, hope we get the g pro 2 or g3 soon

[ROM] MIUI Port

This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409
Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?
If you want mae some cool port, i thikn sense rom is good candidate...
Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far
Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.
Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support
uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?
jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video
uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?
jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.
uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.
justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.
good luck
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:

GOOD NEWS CM 12 on E980 every thing work LTE-phone work

GOOD NEWS CM 12 on E980 every thing work LTE-phone work.
http://forum.xda-developers.com/optimus-g-pro/general/data-voice-heard-phone-t3061313
DangNavyCM12-F240L-Fix fix dial audio after I mod .
PS.. when update the new rom voice not heard,don't forget to update my mod .
By DangNavy
Now I can go spring fishing, 2 days of the testing, happy got my lollipop ,any girls want some.HA HA HA
PS...Don't forget give me some love
Go fishing
Audio call fix
Can you explain what this does exactly? I have needed to install your mod for every CM nightly, and also for Blisspop on my e980 running on tmobile. Just curious what it does, in case your patch file stops working for new version.
Thanks again!!
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
damainman2015 said:
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
Click to expand...
Click to collapse
In the earlier version of the blisspop, the dev had changed the values in the build.prop file so the users would not needed to do so them selves. Since this was such an old issue according to that posting, perhaps dev thought that it was no longer necessary to change those two values.
Hi I'm using stock g4 ux4.0 lollipop g pro v12 final rom and during phone calls I have to use headphones whit mic because there is no sound without them . Will this fix work for me?
It may, though I think with the ROM you're using there is a patch for the sound issue, check the dev's thread first. Otherwise try the solution we've discussed here with prop.mod editor anyway, since it will not harm your device even if, it doesn't fix your problem. Just remember to reboot the phone once you're done with changing the values.
hawkwind212 said:
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
Click to expand...
Click to collapse
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
ShadySquirrel said:
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
Click to expand...
Click to collapse
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Couldn't agree more. Since this is variant specific thing, I won't change anything... I've put an info about that in Slim's thread, but it looks like people really don't like reading.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Just wanted to state, this patch is what fixes the no call audio issue for me while utilizing the TMobile network.

Custom 7.0 ROM for the Galaxy s6 edge Plus!

This device may be a few years old, but its still great. Support for it has almost disappeared, but there are still people out there like me that are on this device that can't/won't upgrade for one reason or another. Sure, Superstock is a great ROM, but lollipop is outdated, and having the features of custom ROMS but on a newer base would be freaking great. I am right?
I may have missed them, but as far as I could find on XDA, I couldnt find any nougat custom ROMs for this device. I would super excited to petition for one of the awesome developers out there to make a new ROM, even if it might be the last for this phone. Or maybe there is one, and I have just been much to dense to see it. Let this thread be for all posts related to the development of a custom Nougat rom, or sharing of one that already exists. Thanks everyone for reading and participating! :laugh:
EDIT: SM-G928T is the model number, just in case it isn't implied
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Talysdaddy said:
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Click to expand...
Click to collapse
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
There is a audio fix on the T mobile Galaxy Note 5 page, it worked for me using Dr Ketan's rom
N
LEGONIKES said:
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
Click to expand...
Click to collapse
I do know that theres a few different "audio fixes" available. Im thinking they differ bcuz of the Android version? Just a guess, but what I'll do, is, I'll use only Roms that another 928T user already reported their success using it. I dont want to waste my time and effort being the guinea pig and then, for it not to work. Usually, whomever confirmed compatibility, will also list anything thats needed additionally to get it running, like the audio fix, along with link(s) to get it. If it doesn't work, they'll usually state the issues they found. Someone else's issue with it, might not be relevant to another person so they may decide to run it.
The best way to do this is to simply go to the OP of the Rom thread, in the upper right corner, you'll see a "search" option/box, (depending on browser or app, might see 3 dots instead, its a drop down list) click on it and enter our phone model, "928T, 928-T" or "T-Mobile, Tmobile, TMO " I try to cover the different variations, others here use to identify the phone. Seems like the search function, searches only the exact characters, as entered in the box, doubting it can identify and include similar known ones, so rather be thorough and not miss something. It searches your entry only in that particular thread and lists the results.
If you're braver than I, and dont mind going where no other TMO'rs have gone before and found only the in call audio isnt working, then its likely, flashing the audio fix is all thats needed.
The best way to solve this is, again, with a simple search. This time I'd recommend, a broader search using Google's search engine, type "XDA T-Mobile audio fix," bcuz this will search all XDA forums, more importantly, both S6 E+ and N5, carrier and int'l forums all at once. Then just go down the list if results, making sure that youre in either of the 4 forums, above, locating the download. Last I checked there was 3 or so fixes available, this was many months ago though. Anyway, having more isnt a bad thing, less would mean needing to go back and finding the one you missed. Once you have them, flash each one seperately, in recovery, reboot, confirm whether you're issue is fixed or not. If not, then continue these steps till it works. Flashing the audio fix won't mess your phone up. No need to reset, clear cache or anything of the sort, between each audio fix, just flash only the audio fix and rebooting is necessary. If you want to be organized, you can cross reference the dates of each audio fix, with the current firmware available at the time. That way you can flash any Rom you desire and will already have the fix ready.
Wow, my apologies, talk about rambling on about nothing more than finding correct file, flash your device, confirm its fixed, if not then repeat till its fixed. If no fix is found then, Rom isnt compatible...
Sorry, one last thing, Im sure that you'll help many others like yourself, if you had minute to post your experience with whichever Rom(s), you chose.
For example, "Rom works great, needed this (link to audio fix) for in call audio on the TMO variant"
It seems like you're the first 928T to try the Rom you have so,
report your experience, posts are permanent, its there forever, for any curious new comers, you'd be their hero! It'd most def get a "thx" from me.. :good:
Any updates on your experience here?
Zulmonster said:
Any updates on your experience here?
Click to expand...
Click to collapse
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
LEGONIKES said:
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
Click to expand...
Click to collapse
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
Nearly lost my phone today and realized find my mobile does not work on NFuel XL. Would not recommend if your one to lose you phone like me.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
I've just finished cooking a second version of my custom rom. Haven't had any issues so far. It's Called TrueStockN.
Here's a list of ROMs I was able to get working for the G928T:
Khongloi's s8 Port
Nemesis s7 Port
N-Fuel
TrueStockN
These are just Nougat roms I that worked for me off the bat, no additional audio fix required. Of course, there may be more, but these are the ones I know of and have used extensively.

Categories

Resources