[Q] viber, nimbuzz issue on NAND android - HD2 Android Q&A, Help & Troubleshooting and Genera
hello all
i have a strange issue on my device, which is T-Mobile HD2.
Problem Details:
if i used Viber or Nimbuz to call someone after that i can not use my phone (GSM Service i mean).
for example, if i called a friend on Viber, and after hanging up with him, if i recieved a normal phone call andi answered it, the phone will freez and after a while a messege will appear (Activity Phone in process com.android.phone is not responding) and two options "Close, Wait" if i selected wait nothing will happen, if i selected close the dialar will close and i will lose the signal and it will come again after a while, but still i can not use my device as a phone, i have to reboot my phone to be able to use it again.
My Radio version is 2.15.50.14
Issue happened with CLK and MAGLDR on every android build i tried (i tried a lot of them)
please any one have this issue for viber or nimbuzz or any free calling application?
Thank you in Advance
Yamen
i have same issue with skype and nimbuzz. I use boyppc gingerbread v33. Have you a solution for that?
No and no one is even trying to help
Sent from my SGH-T959 using XDA App
have no idea gents. if I use skype I can call out no problem
I am having similar problem with Viber as well, and i've got a gut feeling this is audio-routing related, possibly Bluetooth routing related. Viber got no "test call" number, so i have to actually call someone in order to test this, produce some logs etc, meaning i can't really try looking deeper right now.
Anyway, hopefully i'll try doing the following tomorrow:
1) Try without the Bluetooth support enabled in Vipers and without the Bluetooth being on at the phone, just to see if i can still reproduce the issue or not without any Bluetooth audio routing involved at any level.
2) Reproduce the issue with a log cat, maybe i'll be able to spot something interesting in there.
PS: The nasty part is, the chances of me finding the problem are really low, and even if i do find it, i don't have the environment to recompile a thing, meaning i couldn't even try fixing it. I am not exactly an Android junkie/guru/etc :-(
EDIT: Just tried without bluetooth, still getting the issue. It isn't immediately clear what's going on here from the diffs between the good and the bad log either, at least, not for me. The logs are just kinda state the obvious - the good one ends up starting the voice, the bad one does not. Also, in the bad log the system starts killing unrelated services (not shown in the log part below), can be coincidence, but can also be the system running out of memory because of some dynamic stream buffer, too.
I really hope someone with proper knowledge and experience is going to notice this thread and helps us.
Good log:
Code:
I/phone ( 963): acceptCall: incoming...
D/AudioHardwareQSD( 103): Setting mic mute to 0
I/AudioService( 579): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 103): setMode(IN_CALL)
D/AudioFlinger( 103): setParameters(): io 1, keyvalue routing=1, tid 113, calling tid 103
I/AudioHardwareQSD( 103): Routing audio to Handset
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): Switching audio device to
D/AudioHardwareQSD( 103): Handset
D/AudioHardwareQSD( 103): Voice Started!!
D/AudioHardwareQSD( 103): Setting in-call volume to 100
Bad log:
Code:
I/phone ( 961): acceptCall: incoming...
I/AudioService( 579): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 103): setMode(IN_CALL)
D/AudioFlinger( 103): setParameters(): io 1, keyvalue routing=1, tid 113, calling tid 103
I/AudioHardwareQSD( 103): Routing audio to Handset
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): Switching audio device to
D/AudioHardwareQSD( 103): Handset
I don't know if this is too late or not, but since I can't post in any development forums (low post count issue)
I'm using AmericanAndroid NAND Rom and I had this problem, where I can't make or receive normal GSM calls after using VIBER calls.
I used the other version of file libaudio.so from this post
http://forum.xda-developers.com/showpost.php?p=17900515&postcount=198
and replaced my existing file in system/lib .. changed the premissions(i did it with root explorer), rebooted the phone, and it seems that i solved the problem not being able to receive or make a call over GSM.
Phone application is a little bit slow on first call after using Viber ,.. but after that it functions normaly.
NOTE: Backup ur old libaudio.so from System/lib - don't delete it and make sure premissions are set to rw-r--r-- othervise u won't be able to boot up your phone after restart.
The best success I have had was with tytung 12.4 kernel and GPC's libaudio.so from 2.8E... But even then viber made me lose sound- though did not get a dialer FC. I have removed viber ever since, but the no sound issue is far from dead...
Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.7)
I must reply on my self...
The problem seems to be resovled but only for a few seconds..
I tested a VOIP call over Viber for a few seconds and it was OK. Then i used normal phone, and also got full response, tried to make a call, tried to receive a call - all OK but my tests were few seconds long.
When I wanted to make an actual call that is supposed to last longer than few seconds I got another problem: Other side could hear me only on first 10-20 seconds, after that period, other side would hear just muble jumble from me (connection quality = excelent).
exactly same problem here with viber
I counducted one more test...
While making a call in viber i tried not to trigger "scheen shutdown sensor"... in vibers case Screen would't shut down but only go black...
and i managed to make call that lasted more than a few seconds. As soon as the sensor gets triggered and screen goes black (not off), my problem occures. (Othes side can't her what am I saying only rubbish, and i have to hang UP and make a call again).
As long as i keep the my display sensor from triggering everything is well...
I don't know is there a way to disable the sensor in Viber or not but other than that I'm able to make a Viber call, and GSM calls with the libaudio file from above post.
After few more tests I concluded that the Sensor might not be an issue...
I'm now puzzled more than ever
For all of you havin issues with VOIP apps like Viber try libaudio from this post:
http://forum.xda-developers.com/showpost.php?p=16016409&postcount=5967
It's an older version of libaudio.so and for now it showed best results with Viber on my ROM (AmericanAndroid NAND Version) .. Sometimes it gets a bit laggy but didt crash, and I can still answer incomming GSM calls.
Warning: this libaudio might have some other issues with other devices or something else ... but for for the purpose of using Viber and making GSM calls it showed best results..
and also don't forget to set the proper rights rw-r--r--
twoborg said:
and also don't forget to set the proper rights rw-r--r--
Click to expand...
Click to collapse
I would like to try,but i don t know what rw-r--r-- permission I have to set
Just one advice... do not overwritte your actual libaudio.so just rename it to libaudio_old or something else.
Copy the new libaudio.so in system/lib and tap and hold ond the file. You'll get a new menu ... choose premissions and enable read and write for owner... and just read for all other (user and group)
If all set as told you will get rw-r--r-- shown in root explorer (i'm using it and not sure how are premissions shown in other file managers...)
After and only after you set the premissions restart the phone
Issue with this lobaudio is that you cant use bluetooth headset when making a call...but you can use viber and gsm phone without issues ... if you need bluetooth go back to the libaudio_old rename it and restart the phone.....
ok i ve only installed the zip file,i don t need the bluetooth headset.Untill now seems to work
Axel85 said:
ok i ve only installed the zip file,i don t need the bluetooth headset.Untill now seems to work
Click to expand...
Click to collapse
yes but that libaudio.so has the dont remembering volume level problem in calling out...
some solution
check out my findings here
Related
BUG:NO RINGTONE COMING,HELP PLEASE...
There is a bug on my Qtec 2020(FW:166)- when someone calls me no signal goes to my QTEC(But the beep signal goes from calling phone)-sometimes signal goes only at the end of the call,and i see a call as missed. what is it :?:
It is difficult to say exactly what could be causing this kind of problem. Might I suggest some troubleshooting tips? 1. Backup your device 2. Hard-Reset 3. Try some incoming calls to see if they work correctly. 4a. If 3 did not fix, try flashing your ROM with the newest version. 5a. If that solves your problem, re-install all of your programs and you are finished. 6a. If it does not solve your problem, you may have a hardware problem, contact the vendor. 4b. If 3 did fix your problem, re-install your programs one-at-a-time, giving time for testing between loading programs. Only after you have proven that call reception still works do you install the next program. In this way you determine if a program you have loaded is causing your problem. HTH!
if I understood you correctly, you have a problem where the Incoming Call bubble doesn't show, not ringing sound when someone calls you. And sometimes, it takes like 5 seconds delay before it shows or rings? i experienced this after installing some phone related software. i suspected that the system somehow is overloaded, and the memory is somehow insufficient to handle incoming call and notify you in time. Do you have RingtoneX, PocketZenPhone, IA Caller ID, Caller2Picture, Cell Profiler ... etc installed? What are the phone related apps you have installed? Or perhaps, could you list what are in your \Windows\Startup, let us troubleshoot the culprit.
chriswo said: if I understood you correctly, you have a problem where the Incoming Call bubble doesn't show, not ringing sound when someone calls you. And sometimes, it takes like 5 seconds delay before it shows or rings? i experienced this after installing some phone related software. i suspected that the system somehow is overloaded, and the memory is somehow insufficient to handle incoming call and notify you in time. Do you have RingtoneX, PocketZenPhone, IA Caller ID, Caller2Picture, Cell Profiler ... etc installed? What are the phone related apps you have installed? Or perhaps, could you list what are in your \Windows\Startup, let us troubleshoot the culprit. Click to expand... Click to collapse YES.YOU ARE RIGHT. From your list i installed only POCKET ZEN PHONE(but i also had this problem before i'v installed PocketZenPhone). WINDOWS/STARTUP: AFlashMan CFlashMan CheckAutorun ChgDflnk IA_Caller_ID(MAYBE THIS IS BUG :?: -but i have not it ins.on my QTEC) MMReg NFlashMan poutlook stk TFlashMan GUYS,Please,help...
So,what causes the bug :?: :roll:
I am running PocketZenPhone also, and do not experience this problem. Unfortunately, I still believe that a HR is the only way you can prove that the problem is caused by software you have installed and not the hardware. It sounds drastic, but you must start from a clean PPC and prove that it works, then figure out which software is causing the problem.
ok,i'll soon try it. BUT i wanna hear from chriswo what to do,cos he got the same bug. :arrow:
I've got a similar sort of bug, not sure what causes it though and its a pain, I cant get the volume slider for the phone to stay above zero, i raise it and it beeps as i do it, and i close the volume control, open it againg and it back at the bottom, If i recieve an incomming call, all that happens is the screen flashes with the incomming call alert but no ringing tone at all?
how are the phone settings set ? as in ring type ? and how are the sounds and notifications settings
just checked them and they all appeared to be ok, but i wend back in and changed my ring tone and then tried to change it back and it said 'this ring tone is not working properly, You may want to choose a different one to use.' Very strange, so i am now using oldphone as my ring tone and it is working perfectly!, looks like one of my ring tones has got corrupted somehow
I had the same problem also Fix by HARD RESET. At that time I try to test many Phone edition program. (on XDA 1 2002). After that everytime when I try to install some new program, I'll backup my data first.
so,i still waiting for chriswo,cos he knows this sort of bug...
Please excuse me for posting Smartphone qustion here
Hi, On a smartphone 2003 device. I am playing a fairly big wave file (approx 30 secs long) in a standalone app. When i get an incoming call/or place an outbound call using default Phone app it disables the speaker (I am guessing may be by sending an AT command) hence the wave file is not audible for the time that the default app is in focus/active. Is it possible to do one of the following 1. Turn the speaker ON while phone call is in progress, so that the wave file being played in the stanalone app is audible. 2. If it is not possible to turn on the speaker while phone call is in progress is it possible to figure through some API calls as to when the speaker would be available again. Any help will be greatly appreciated. thanks a ton folks -Larry
you cannot. And it is not an "AT" command. Speaker is electrically switched off
Thanks for your reply mamaich. Is it possible to query the availability of speaker using an API call?
You can determine that the call is in progress. If it is - speaker is unavailable for playing sounds. I don't remember the exact API, read TAPI documentation. And on some devices you have to reinit wave IO after the call is finished.
Hermes/TyTN: Severe audio failure when microphone is used (except for phone calls)
I have to face a severe audio failure as soon as I need to use microphone functionality (except for phone calls). For exemple, Voice Speed Dial does not work (even after hard reset and no other software installed). When it opens and prompts for talking, there is no progress bar and, after a few seconds, I have a message confirming that the device did not hear anything (Microphone ACG activated or not). No voice tag is recordable except (surprisingly !) for the "Contact" category (which prooves that the microphone works from a hardware point of view). Any attempt for using microphone is followed by a total sound desactivation for the whole device (even the keyboard does not make any sound anymore). Soft reset is needed to recover its normal behavior. Video recording with sound fails (in standard or MMS format). Here again, need to make a soft reset. Third party softwares, such as Skype, Wengo, SJphone, ..., crash as soon as the microphone needs to be used... MS Voice command fails too. HTC technical support contacted. They suspect a software problem (since the microphone works well in phone mode and for recording contact names). But they can not do anything before the next rom is being released (February ?) Has anyone experienced this kind of problem ? Is it coming from the french rom only ? Thanks in advance for your comments.
Note 2 other party can't hear me during call
I only decided to flash my Note 2 phone with version 4.45 because I had problem with data connection (phone doesn't turn data on when WiFi is turned off or after switching air plane mode off). Now, about half of the calls I make result in the other party not hearing me. This is quite random but usually the first call is OK. Subsequent calls are a consistent failure. Usually receiving a call is OK but if I then make a call afterwards, the other person can't hear me even if they call back. This is so annoying so I hope someone can help. Thank you.
Your best bet for help would be in your device forum since that device is not officially supported. This would be a device specific issue not particularly related to the core of the ROM. #stayparanoid
Paranoid rom voice failed Hi I have had this problem as well, the data connection does not cause this to happen, but with any android custom rom from cyanogenmod source 4.4.2 to 4.4.4, the problem is that the kernel is from the cyanogenmed source tree so if you can find and then flash a non caffinated cyanogenmod kernel the dialer and the voice should function correctly. Or update to a new lollipop rom as the dialer and sound is working right. The actual reason for the sound problem is in the file itself that controls the sound routing, example ( the sound file contains numbers for routing to in-call speaker) if routing number or file structure for file is corrupt= no in-call speaker because the default file has a routing text that has been mis-writtin by cm. it would be like this "in-call speaker ui" in the etc folder under mixer paths.xml or snd soc msm fusion2x3. these files need to be corrected as they have a space or something where it shouldn't be causing the routing for in-call ui speaker to be off instead of on ( volume ) "67.5 " or this without the space between the comma and the 67.5 or this is fixed= "67.5" one of these mistakes is what I believe is breaking #All#kitkat cyanogenmod based roms. So find the correct file structure from an old rom that works right as it will have the same sound file across versions for your device the file stay's the same and can be copied and pasted into your paranoid roms etc folder before installing the rom with a file manager. Confused yet? if this helped or if you need more info please leave message, thanks.
Non native phone app
All of a sudden last week, I am getting no sound on my GS4 when making calls--no outbound or inbound sound and neither side can hear. The call is going through. Voice recorder and playback indicate that it is not a mic or speaker problem. I have hard reset the phone to no avail. Every now and then, it will allow me to make one call but then it goes out again. My question here, other than if anyone knows how to fix this, is if there is another phone application instead of com.android.phone that I can install and use instead of the native phone app? Phone is rooted.