Yesterday, I flashed CM10.0.0 stable release via "ROM Manger Premium" app by ClockWorkMod from Play store after rooting my T-mobile Galaxy S3 along with app provided Gapps package. Everything works great and I was really liking this ROM and considered this as my primary ROM. However, the excitement was short lived when I called my girlfriend using skype and viber. I had very low volume issue on viber(according to my girlfriend) and weird sound(according to my girlfriend) issue on skype on my girlfriend's side of the call. Those problems went away when I hung up the call, reflashed my stock TouchWiz 4.0.4 on my phone and immediately called her back. I was wondering if any other people has or had the same problem and is there a fix on that issue? Thanks in advance.
sincerely,
DroidNoob74
Hi,
This is a member of the Viber R&D Team.
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 you have any questions.
Thanks,
Viber
I have seen some threads before where they discuss running Viber on CM or CM based ROMs but to no conclusion.
There was one post from a Viber rep as well and he/she basically said that they cannot support custom ROMs.
So I just wanted to find out if you were able to make/receive a Viber call on your custom CM 10.* or CM 10.* based ROMs.
On Viber(version 4.2.1) every time I try and make a call or receive a call, it fails. Resetting/Re-installing did not help either.
Chat is fine but voice call fails.
All help from users who were able to use it successfully will be great and much appreciated.
I have tried to find some definitive info on it in vain so far, hence this thread, feel free to close/remove this thread if its already discussed
somewhere else and also do post a link to the thread as well, if so.
meletios said:
I have seen some threads before where they discuss running Viber on CM or CM based ROMs but to no conclusion.
There was one post from a Viber rep as well and he/she basically said that they cannot support custom ROMs.
So I just wanted to find out if you were able to make/receive a Viber call on your custom CM 10.* or CM 10.* based ROMs.
On Viber(version 4.2.1) every time I try and make a call or receive a call, it fails. Resetting/Re-installing did not help either.
Chat is fine but voice call fails.
All help from users who were able to use it successfully will be great and much appreciated.
I have tried to find some definitive info on it in vain so far, hence this thread, feel free to close/remove this thread if its already discussed
somewhere else and also do post a link to the thread as well, if so.
Click to expand...
Click to collapse
Hi! Even though Custom Rom's are not fully supported we'd like to try to help.
Can you please elaborate? What do you mean by fail? Do you use 3G WiFi? Where are you from?
Viber Team said:
Hi! Even though Custom Rom's are not fully supported we'd like to try to help.
Can you please elaborate? What do you mean by fail? Do you use 3G WiFi? Where are you from?
Click to expand...
Click to collapse
Sure, when I make a call, I can see the green call button and also hear the call ring,
then when the receiver picks up the call, the screen flashes once, I get a standard (white on black) notification that its connecting and then
the call ends and I am back on the chat screen.
I have since moved to a sense based ROM so unfortunately cannot get the screenshots now.
I was on CM 10.1.
Hope this helps.
Location - UK, via Wifi or Data Connection (H)
Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.
Thank you!
ShotByMeir said:
Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.
Click to expand...
Click to collapse
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.
Corpal said:
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.
Click to expand...
Click to collapse
My wifi is working fine with any other router, my op3 just crashes when I connect to my Airport Extreme..
This seems to be a persistent bug because when i connect to my Apple airport Router my phone crashes too.
Hi
I've a same problem with connection on Airport. But my ROM is Ressurection Remix (Build 30/07/16). I think that the problem is present on all CM-Based ROM.
Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.
Wynztech said:
Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.
Click to expand...
Click to collapse
Yes me too, would like to post this in the Official CM13 Forum but can't since I'm a junior member :/
This is the only problem I have, CM13 is quite stable in its current condition
Seems to only be with the airport
Same problem
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.
rumagent said:
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.
Click to expand...
Click to collapse
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying
ShotByMeir said:
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying
Click to expand...
Click to collapse
Can you post the issue on the development thread. Please. I'm too new to do so.
akiva.r said:
Can you post the issue on the development thread. Please. I'm too new to do so.
Click to expand...
Click to collapse
Already did that. Someone was supposed to look into it but didn't. I provider logs, but I guess it is nog considered a very important bug I already started a thread in the cyanogen forums so let's hope that helps.
Btw if you want to use cm, you van use Arter97's build. That build with his kernel (you Have to add it manually) doesn't have the wifi bug official CM with his kernel also doesn't have the wifi bug.
Believe to have figured out the issue
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.
cquick7 said:
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.
Click to expand...
Click to collapse
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.
ShotByMeir said:
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.
Click to expand...
Click to collapse
Same issue with RR.How to solve using any zip or replacing files.?
amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Flash newer kernel over it or just wait for a new build.
amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Worked. Thanks a bunch.
There's a bug present in the OS for many days, it's the VoLTE bug. The problem faced is, whenever the mobile data in enabled, the VoLTE feature stops working. To make it work I have disable and then enable the 'Enhanced 4G LTE Mode' n the settings. After that one more problem is faced, when someone is trying to call me, the caller gets a busy tone.
Please fix this bug ASAP sir. I am using the lineage OS version 14.1-20170619-NIGHTLY-A6020. It's the latest one till date. The VoLTE bug is not resolved.
androidoverdoze said:
There's a bug present in the OS for many days, it's the VoLTE bug. The problem faced is, whenever the mobile data in enabled, the VoLTE feature stops working. To make it work I have disable and then enable the 'Enhanced 4G LTE Mode' n the settings. After that one more problem is faced, when someone is trying to call me, the caller gets a busy tone. Please fix this bug ASAP sir. I am using the lineage OS version 14.1-20170619-NIGHTLY-A6020. It's the latest one till date. The VoLTE bug is not resolved.
Click to expand...
Click to collapse
This question should be asked within the following Official LineageOS thread for your device.
[ROM][OFFICIAL][7.1] LineageOS/CM14.1 for the Lenovo K5/K5 Plus [VoLTE][Weeklies] by scritch007
In addition, the last post on the thread does address your question too.
If it doesn't, then you should be posting your issues there.
Good Luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
I'm getting chipmunk audio when checking voicemail and sometimes when getting other people's voicemail recording when VoLTE is enabled. Turning off VoLTE works around the issue but it's a non-solution as T-Mobile will be requiring VoLTE in just over a month.
Toggling to speaker and back seems to bandaid the issue.
It also doesn't seem to occur while connected to WiFi.
Using an Essential PH-1, on T-Mobile running the latest nightly.
Any assistance would be great, Thanks!
Like that
https://forum.xda-developers.com/es...t/lineageos-17-1-essential-ph-1-mata-t4066163
That links me to page one on a very long thread, I skimmed several pages but diddnt see anything related to the issue.
Could you please provide a bit more information on what you're guiding me to?
kiyolaka said:
That links me to page one on a very long thread, I skimmed several pages but diddnt see anything related to the issue.
Could you please provide a bit more information on what you're guiding me to?
Click to expand...
Click to collapse
It was just a wild guess, what operating system you have installed. If I'm right, you should post your question there.