Develop Bugs

[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....

[Q] help with cyanogenmod 10.1

hi
after installing cm10 everything working smooth
but i surprised when i found a big problem with my note 2
know when i make any call no sound going or coming to me while the call is connected
also the one who call me he can't here any thing
so my phone now is like small ipad
please help me

Maybe you can play with flashing kernels? Sometime the problem with no audio can be solved by flashing new kernels...
hdooooy said:
hi
after installing cm10 everything working smooth
but i surprised when i found a big problem with my note 2
know when i make any call no sound going or coming to me while the call is connected
also the one who call me he can't here any thing
so my phone now is like small ipad
please help me
Click to expand...
Click to collapse

sphuyal said:
Maybe you can play with flashing kernels? Sometime the problem with no audio can be solved by flashing new kernels...
Click to expand...
Click to collapse
o.k dear
any suggest kernal with link from you, please

N.e.a.k kernel from original android development section.
Sent from my GT-N7100

It's a recent issue to do with some changes they made to the RIL. Should be fixed in the next few nightlies, you can revert to an older one, 2013/07/08 or earlier should be fine I think.

[ROM][JB 4.3][Sep 04] Unofficial CyanogenMod 10.2 | Fully Working

It'sabout this ROM Port by tommypacker
http://forum.xda-developers.com/showthread.php?t=2438832
Hey, I was happy to find a working 4.3 JB for Desire.
All Tests were fine until I recieved a call. The person on the other phone couldn't hear me, even when I called her back.
Seems like mic doesn't work at all during a phone call. It's always muted. Anybody else having this issue?

What radio are you on?

32.56.00.32u_5.17.05.23

Floy83 said:
32.56.00.32u_5.17.05.23
Click to expand...
Click to collapse
Thats the latest, so thats not the problem.
It could just be an issue with the rom. Its an early release of a port.

Floy83 said:
It'sabout this ROM Port by tommypacker
http://forum.xda-developers.com/showthread.php?t=2438832
Hey, I was happy to find a working 4.3 JB for Desire.
All Tests were fine until I recieved a call. The person on the other phone couldn't hear me, even when I called her back.
Seems like mic doesn't work at all during a phone call. It's always muted. Anybody else having this issue?
Click to expand...
Click to collapse
same here, rom working perfectly, but mic is dead.

Ammon-Ra said:
same here, rom working perfectly, but mic is dead.
Click to expand...
Click to collapse
ROM issue. The dev won't be working on it until 2014, so you better switch to you previous ROM.

abaaaabbbb63 said:
ROM issue. The dev won't be working on it until 2014, so you better switch to you previous ROM.
Click to expand...
Click to collapse
Yep, I'm on Chromium now, trying build 11. Very good experience with build 10 so far.

what's the most stable alternative?
Hi I've been running aokp 4.2.2 on HTC Desire for some time - it's great except for the video issues when using the camera (I understand that's an issue for many 4.2.2 roms?) - so I'd like to move to a 4.3 or 4.? rom that's recommended
Is the Desire S better supported on 4.3? - I've just put a CM version on an old Desire S (that's got some faults, so I can't tell for sure) and it seems OK at first look.
Many thanks, Geoff
Ammon-Ra said:
Yep, I'm on Chromium now, trying build 11. Very good experience with build 10 so far.
Click to expand...
Click to collapse

[Q&A] [ROM][5.0.1][OFFICIAL]Team UB ROM for T0LTE [16/12/2014]

Q&A for [ROM][5.0.1][OFFICIAL]Team UB ROM for T0LTE [16/12/2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.1][OFFICIAL]Team UB ROM for T0LTE [16/12/2014]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

c:
Is working in boot 4.4.2?

Zarcose said:
Is working in boot 4.4.2?
Click to expand...
Click to collapse
yes, i think so.

is there a way to turn off capacitive button lights... I see no option in settings..

Thanks to the team!
Hi everybody, I'm certain new to the Xda forum and I wanna start with a big thanks for the effort of developers of this ROM.
First of all it's been awhile since i frequently read this forum I wont detail since which roms I've tried , of course must be some 2 years ago L
I've tested cyanideL lately but I came back to TB , seems for me much more well quality well finished code!
Nothing major noticed except I struggle to find a fix for netflix. I was really searching and I found this post
http://forum.xda-developers.com/showpost.php?p=56946778&postcount=1698
which really "bingo" in my device. For those who may try just to let them know netflix works very well in my device with the latest Team UB Cm12-261220014.
The only problem that it really bother me now is the "unfortunately, gallery has stoped" Camera seems to work very well. I ve tried clear, cash the app, I've moved all my DCIM picture on a ext card(pc), I even really clean reflesh the ROM. For first part it worked but then after i installed some other apps form titanium backup....I had the same problem. I really assume now that there is one app that my conflict gallery code....but to be honest i had so many to restore it's an enigma to guess which would be !
If someone would had a clue or encountered the same issue would guide me please!
Once more thanks from a sgh-i317m-telus successfully operated with this ROM

re gallery crash
....so no one has this pb ? ...i need apparently a couple of posts to write in diff spots of the forum...

How can I get color icons in taskbar the notification one on the left?
Also what is the star on the right side?
And last one for now how to make a screen shoot?
Sent from my GT-N7105 using XDA Premium 4 mobile app

i'm really happy The OPs reopened the ROM thread !!! thanks guys

Chromcast doesn't connect
I just noticed another issue - i couldn't connect my device with chromecast, it looks not supported yet on this cm12 ver yet....lollipop 5.0.2 yet in development..looots of work....

Hello all, I am new at testing Customized ROMS and let me say that this is a great ROM, When the phone had Omni ROM installed began with this issue, when I am charging my phone while it is off, the battery icon animation gets stuck and I cannot turn my phone on, the phone does charge, I did not have this issue on Kit Kat stock for I317, Can somebody help me? Also, is there any way to make proximity sensor to work while making calls? also, is there any way to disable vibration while pressing capacitive buttons?
Thanks in advance.

luisfit said:
Hello all, I am new at testing Customized ROMS and let me say that this is a great ROM, When the phone had Omni ROM installed began with this issue, when I am charging my phone while it is off, the battery icon animation gets stuck and I cannot turn my phone on, the phone does charge, I did not have this issue on Kit Kat stock for I317, Can somebody help me? Also, is there any way to make proximity sensor to work while making calls? also, is there any way to disable vibration while pressing capacitive buttons?
Thanks in advance.
Click to expand...
Click to collapse
The sensor fix is here:
https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
taken from post #2 on this page:
http://forum.xda-developers.com/galaxy-note-2-att/development/rom-cyanogenmod-1212-15-2014-t2973762
I just flashed this UB ROM and had the sensor issue. Flashed the above t0lte_sensor_fix.zip and my sensors now work perfectly.
By the way, this ROM is by far THE best t0lte lollipop ROM I've flashed yet.
Great job to the developer.

So far so good 5 hours on and all set up. Switched from W03 Slimkat. Had one force close after the first flash while phone was resting. "...Email" but noticed nothing nor any issues with my Gmail. Thanks

E: error executing updater binary in zip \external_sdcard\cm-12.0 - 20141230.zip
TWRP 2.8.3.0
SlimKat 4.4.4

UB-ROM for TOLTE sound issues
Overall very happy with the UB ROM 20150106, however the sound issue, specifically the one relating to bluetooth streaming has gotten worse.
The typical behaviour now is that when phone syncs with the car and music starts, audio fx and google music crashes.

iliaa said:
Overall very happy with the UB ROM 20150106, however the sound issue, specifically the one relating to bluetooth streaming has gotten worse.
The typical behaviour now is that when phone syncs with the car and music starts, audio fx and google music crashes.
Click to expand...
Click to collapse
I had this issue and flashed the shift kernel. However after a while, charging did not play nice with it. I am now using the kernel from DU lollipop ROM. It is very fast and has no issues with charging or bluetooth. Just use 7zip to copy the boot.img from the DU zip to the UB zip and flash as normal. You will get a warning asking you if you want to copy and overwrite, just click yes or OK.. This is a fantastic ROM

note 2 using Team UB rom 5.0.1
hello guys, just flashed this sweet lollipop rom, but i noticed that it has no support for s pen. Any recommendations on what app to use or mod? also, i couldn't get the music to stop being soo choppy over bluetooth while screen was off. any help is appreciated, and thanks DEVS for such great work!!!

That's strange, s pen is working on mine. No customizations or 3rd party apps either. Just stock ROM. As for Bluetooth did you try overstuffedcows suggestion of the DU lollipop kernal?

No music output if screen locked?
There is no music output if screen is locked, when a headphone without a microphone is plugged in. I can't hear the music when screen is locked (although music app is still playing the music silently (muted), but when I turn the screen on, the music plays. It seems like the music itself has been playing in the background, because sound is the thing that's muted not the app itself.
Strangely, music plays well when screen is locked when a headphone with a microphone is plugged in.
Is it sort of a bug? I think many will have this kind of problem..
Help!

Since update 1/19/15, the proximity sensor does not work
Since update 1/19/15, the proximity sensor does not work. Screen does not turn off during call, and I downloaded some apps to test the sensor and it seems that the sensor does not work at all..

My sensors are still working with 1/19. Try flashing the sensor fix I posted up above??

The ECHO

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.