I cant hear incoming or outgoin calls ...the only way i can is speakerphone or through the headphones...ive run different roms n problem still exsists....can any1 helppp...
try a wipe
Can you give some details. What rom are you running? What radio version you have?
Related
Has anyone ever successfully make/answer a TAPI data call? I can have the voice call working but not the data one.
Can someone point me some example?
thanks.
look into source code at www.cryptophone.de
the idea is to kill cprog.exe application so that it does not pops up at incoming call. Than you can answer the data call as usual using TAPI.
When I was making a data call, the receiving XDA did not popup the cprog at all. And my program at receiving side didn't show any message either. (But it works fine with voice call and the cprog showed up to intercept the call). Does this problem indicate that the data call doesn't work at all?
If I can get rid of the cprog, do you think the data call will get through?
thanks,
- David
this seems to be a problem of your operator. Maybe it does not support incoming data calls.
Hey all , my issue is about making DATA CALLS !!!!
I have managed to get the modem in my XDA2 to respond to my AT COMMANDS however i dont think that a data call is possible the old way. So i want to investigate TAPI , i have managed to write up a function which calls a number by the function TapiRequestMakeCall but i am not too sure how to use the other functions .... wanna HELP ?>??
Is it actually possible to make data calls by using TAPI ???
Yes it is.
Did you look at an answer I gave you a while back ?
http://forum.xda-developers.com/viewtopic.php?t=1716
Cheers
Paul
I recall seeing a post from here about the same issue. I was trying to look for it but no luck. So here goes nothing. I remember reading about forwarding calls from the number that the HTC Shift uses and the device will always reject the calls before it even gets forwarded. Just wondering if this still stands true. And if not, forwarding calls doesn't mean forwarding text too, correct?
Once again, sorry if this is a repost, but i tried.
There is still no solution 'til now for this issue. Shift will reject incoming calls by first ring tone. After this (in German T-Mobile network) I receive a SMS on the Shift with the data of the incoming call.
GSIAK
I have elfin and skype can not work. I can chat but i can not call or recive calls. When i try to make a call it rings and then skype shuts down. then i can see the icon of a phone on the top of my display and that is it. I can not make a call. I nead to start the skype again and then is the icon gone but the calling is still a mistery. does anybody know what do i nead to do to fix that
maybe it doesn't work because it didn't meet the requirements to make a call... Try using wifi connection... it might work
no luck with wifi to. same problem. thanks for adwice but i nead to find another solution
Hi!
After installing the Stock rom 4.3 deodexed from this thread , http://forum.xda-developers.com/showthread.php?t=2010887 , i have the following problem : after being online on WiFi i do not receive any calls at all. To the caller it shows that it rings normal but on my device there is no ringing or no optical sign ( number who is calling ) at all. But after i reboot and do not go online then all incoming calls reach me. If i connect via WiFi again and disconnect then again no incoming calls.
Any solution?
Thanks
Hi all,
I can imagine this is a general Android feature but since I use the OP5 I thought of asking here.
I noticed while using f.e. WhatsApp voice calls (over WiFi) that they drop when a network call is incoming.
Is there a way (rooted or not) to change that priority and keep the VoIP call alive and just show that someone is calling you normally ?
Thank you in advance
apologies for not responding with a fix for you - but there's definitely some issue with the latest build of oxygen OS and voip - in addition to call drops there are problems with voice/SIP/RTP itself. This is not just limited to whatsapp - but also Tango and skype.
Only real way to isolate the issue seems to be to reflash to older stock ROM and see if the problem persists. But is it worth it?