Running LOS 14.1 (10/16 build). I'm using a CDMA SIM with Ting (a Sprint MNVO). Incoming texts are really delayed, sometimes by several days, and may randomly appear if I make an outgoing text or get an incoming voice call. Happens with texts from TMo and Verizon users for sure, not sure about other carriers. Using the stock Messaging app, v 1.0.001. Also tried using Android Messages from the play store, didn't make any difference.
I'm downloading (at about 50k/sec so it's taking several hours) the update to the latest LOS, but I'm just wondering if anyone has ideas I can try before that? I've already done an update Profile and update config.
Related
Hi,
I have a T-Mobile MDA with the latest firmware.
The problem is even though I have multiple voicemails waiting, the notification still shows only 1 voicemail.
Has anybody else noticed this problem? or it only my problem?
Thanks
Your not alone. I did notice when I upgraded to AKU 3.2 that it now says you have 1 or more messages it just doesn't say how many. It's a real bummer as you need to stay on top of your voicemails especially if you run any GPRS apps which will force any calls to the voicemail.
Hey!
I have been following the swiftdroid project from the sidelines for a while, and i am currently on the latest version (2.0 M3)
Yesterday I put Swiftdroid onto my friends GT540, his is currently on 1.8 (the only speedboot version i had saved)
he has told me about issues he has been having with calls: when he rings certain people the call is silent, i seems it wont connect, then beeps and the dialler closes. i have been having the same problem with certain numbers.
SMS messaging is fine.
My friend and i both use giff gaff (the uk phone network) and have had APNs set by the giffgaff APN app from the market place.
any help? Thanks a lot.
Its a network problem.
Sent from my GT540 using XDA App
It cant be
I dont see how it could be a network problem, my friend was on the phone to his girlfriend an hour before the upgrade, and he has never had a problem in the months of using 2.1. Now it wont let him call her, it does however accept incoming calls.
I have had the same problem with certain contacts:
incoming calls = fine
sms messages sending = fine
sms messages receiving = fine
but outgoing calls just wont connect.
I changed from the stock OS of my HD2 to hyperdroid, but I have two problems.
1) When I miss a call, it is only shown in the history if my phone was on at the time or had reception. Strangely, if someone sends a text to my phone while it is off, I receive it once my phone has been turned on again. Even if it does not shown a missed call under those circumstances, I can still receive voicemails from them.
2) There are no options in the original contacts section to add/remove/important so on. I installed the hotfix from the Hyperdroid yet it still does not work. An app for another contact list works, but the original one does not.
Can anyone please help me with those issues?
Thank you for the time.
#1 is by design. That is how GSM works. Calls you miss when the phone is off or out of coverage area can be notified as SMS alerts, but only if the network provider supports that feature.
I don't use the ROM you have, so can't help on #2...
Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.5)
Same problem
My problem is that I can't receive any calls what so ever.
I have been using this ROM for only 2 days and my call log shows that there has been incoming calls but the phone simply sends them directly to voice-mail.
is the a fix or tweak for this?
Please S.O.S!!!!!!!!
Hi,
I successfully sim unlocked my sprint s4 to work here in the Bahamas and it works perfectly on Touchwiz Roms. However, on any aosp or aokp ROM, I can't receive any incoming calls. The call rings as normal on their end but I get no notification that a call is coming through. I have searched for the past two days and could find no one who has experienced the same problem. Other than that, everything works fine, including data.
Same here, came in france, unlocked, and everything works except incoming calls
dredre2017 said:
Hi,
I successfully sim unlocked my sprint s4 to work here in the Bahamas and it works perfectly on Touchwiz Roms. However, on any aosp or aokp ROM, I can't receive any incoming calls. The call rings as normal on their end but I get no notification that a call is coming through. I have searched for the past two days and could find no one who has experienced the same problem. Other than that, everything works fine, including data.
Click to expand...
Click to collapse
Still having problems with this?
Same for me
Outgoing calls and texts work fine. Incoming calls never ring through.
Change apns
Sent from my SPH-L720 using Tapatalk
I'm trying to use the Nexus 6P's native dialer to make calls through my SIP provider. I have a configuration that works perfectly on the Nexus 5X and older 6 (shamu). I entered all my information in Dialer > Calls > Calling accounts > SIP accounts, and then enabled the account under ... > Calling accounts > All calling accounts. However, whenever I attempt to make a call through my SIP provider on the 6P, a message pops up saying "Can't make outgoing calls while call barring is on." Does anyone have an idea what might be causing this? Note that:
I can make regular phone calls from my mobile number just fine, tested with both a Verizon and a T-mobile SIM. However, the SIP call barring problem persists regardless of which SIM is in the phone.
I can make SIP calls using other apps, like CSIPSimple, so it's not a port blocking issue.
I can receive incoming SIP calls (to my DID number) just fine when enabling ... > Calling accounts > Receiving incoming calls, so clearly I didn't mistype my SIP account password. (I visually checked that all the other settings are identical between my 5x and 6P.)
I'm definitely on WiFi when I experience the problem. To be extra sure, I even tried it with airplane mode and WiFi both on, which is fine for CSIPSimple or incoming calls but still doesn't work for outgoing calls with the android dialer.
The message pops up instantly, making it seem like a setting on the phone rather than a response to network messages.
For what it's worth, I'm running build MMB29M (android 6.0.1). My phone is unlocked but not rooted. (I can still get root access to /data by booting TWRP, but have never mounted my system partition read-write.) The one thing it might be is that I put a Verizon SIM in my Nexus 6P when first booting it, whereas my other phones were all first booted with a T-mobile SIM. I think that caused some VZW apps to be installed that I since removed; perhaps it messed up other settings. I'm a bit reluctant to wipe my phone and try again, but will do it if people think it's the only solution.
Thanks.
My 6P won't allow the SIP account. Gives me an error every time I try to set it up.
skinnytoo2 said:
My 6P won't allow the SIP account. Gives me an error every time I try to set it up.
Click to expand...
Click to collapse
Do you have Verizon, or a different carrier?
15xda said:
Do you have Verizon, or a different carrier?
Click to expand...
Click to collapse
Yup Verizon
Sent from my HUAWEI NXT-AL10 using Tapatalk
Tmobile
I experience the same problem on a Nexus 5X with Android 6.0.1 SIP calls only exhibit this problem when the SIP username looks like a 10 digit phone number. All other outgoing SIP calls work correctly.
mndrix said:
I experience the same problem on a Nexus 5X with Android 6.0.1 SIP calls only exhibit this problem when the SIP username looks like a 10 digit phone number. All other outgoing SIP calls work correctly.
Click to expand...
Click to collapse
I am having this same exact issue on a Nexus 5X using Cricket. Anyone come up with a solution?
SOLVED
Okay, I finally broke down and wiped my Nexus 6p, flashing the latest google ROM with fastboot -w. This time I booted it with a T-mobile SIM for the first time. Lo and behold, outgoing SIP calls started working again.
This is super nasty behavior, because merely switching the SIM and even reflashing without -w did not solve the problem. The mere act of having a Verizon SIM in your phone the first time you boot it ends up crippling the SIP feature. On the plus side, it will probably continue to work even if I pop the Verizon SIM back in.
So now I'm going to lose an hour redoing all my settings on my wiped phone, but I'm super happy to have SIP working again.