Database Users

issue calling one particular number??

I'm having a strange issue with my nexus one. This started a few days ago. I can not call my brother's cell phone with it. It will ring once and than I hear a beep and it just closes the phone app. I have not had this problem with any other phone number and he can call me fine. Has anyone else seen this issue?
I'm on t-mobile and my phone is not rooted also.
Thanks,
Dave

dave98rt said:
I'm having a strange issue with my nexus one. This started a few days ago. I can not call my brother's cell phone with it. It will ring once and than I hear a beep and it just closes the phone app. I have not had this problem with any other phone number and he can call me fine. Has anyone else seen this issue?
I'm on t-mobile and my phone is not rooted also.
Thanks,
Dave
Click to expand...
Click to collapse
to rule out other possibilites have you tried to call him from a different cell phone or land line?

I can call him fine from other cell phones and from land lines. It even works if I call him on my nexus one using google voice. I still haven't tried switching my sim card back to my g1 to see if that allows me to call him.

to narrow it down, delete him from the phonebook and try again.
maybe his entry is corrupt and the dialler crashes whe trying to display the incall info.

Tried that as well. I deleted him, called the number without saving it and got the same result.

Going one step further (though I would swap and test with your g1 first if you can) wipe the phone and try again.

Try:
Settings>call settings>additional settings>caller id>network default.
It looks like your brown has some sort of blocked number rejector on his phone.

Update: I fixed it. I finally was home today to play with both phones and somehow I was in the block list on his G1. He claims he didn't even know how he did that. Is there a shortcut or anything that he could have hit by accident or in his pocket?

Dropped calls.

I have a really annoying problem on my SGS2.
The phone ends calls randomly by itself. It is a pain in the ass when I have been on hold for 10min and then I am the next in line and CLICK! I want to throw the phone into the wall when that happens.
Or when I need to call my friend back 7 times during a conversation.
Anyone else have this problem?

i have not had a single dropped call and i use at least an hour per day. here are the three things i would do
1. make sure you have a fairly new 3g sim card (or bull**** 4g depending on which provider you have). i used to have issues with rogers when i had the htc magic and getting a new sim card fixed them.
2. check which apps you have installed on the phone. some apps turn off data for periods of time and you might be having an issue when data comes back online. i have read about different android devices that let data have a priority over voice, so if you are on a call and your device tries to download an email you might drop a call. i would uninstall or freeze any apps which could do this and use the phone for a couple of days to see if the issue stops.
3. if you still have issues i would backup whatever was important and hard reset the phone (deletes all info) and start from scratch. you might have a corrupted file or something
good luck

May be your network sucks. No dropped call issues here.
Sent from my GT-I9100 using XDA Premium App

1. I use the same card as I had on my N900, didn't have this issue, but will check it.
2. I live in Europe where we can Call and surf at the same time, so not a problem.
3. I flashed the phone to KE7 2 weeks ago, and factory reset it too. Gonna try to change the modem kernel when I get the time.
Kirdroid: No, it happens everywhere, and hasn't happened with any other phone before this.
Gonna see if changing the modem kernel can help.

Weird Galaxy S II Problem

Today I decided to use my new Galaxy SII mobile phone (had it locked away in its box for 4 weeks as I had to wait for my new case to arrive from overseas). Well anyhow what I did was I removed the SIM card from my Omnia i8000 and inserted it into my Galaxy SII phone. Booted the phone up, all went well, and it booted up nicely recognising all my Crazy Johns settings etc.
Now here's the weird problem. When ever anyone tried to ring me, I will see their number come up on my screen, it will ring for 1 sec or prob slightly more than all of a sudden it will cut out/hang up, no call at all will go through, just simply cut our after 1 sec or so. Ok now the problem gets more weird here, I also have another mobile (Samsung i780) which is my work phone, so what I did was I got the i780 and called my Galaxy SII to test it out, and it rang perfectly. But from any other phone, this means my friends mobiles and LAN line it would just simply cut off after 1 sec or so, no call will go through. The only call that goes through is from my 2nd Samsung i780 in which I dont have any problems at all.
Help would be appreciated

See if any groups/persons are added in Black List or not. Check under Settings- Call- Call rejection- Black List.
Regards.

Done all that and no, non of my friends that I've tried on their mobiles to call me is listed there.
Like I said in my post above, the weird thing is, is I call from my i780 it works fine and rings, but any other phone it simply rejects.

Try another sim card..
Sent from my GT-I9100 using xda premium

Could it be a faulty SIM card, but it works in my previous Samsung i8000 Omnia.

Just give it a try...
Sent from my GT-I9100 using xda premium

It may work..
Sent from my GT-I9100 using xda premium

Ok fair enough, but my Q here is, why does it accept calls from my Samsung i780 mobile, dont have a problem there at all ?

Ok now this is more weird. I am now visiting and staying at my parents place, I tried to call my Galaxy SII from my Mums mobile and it worked great, did the same from their home phone and it worked great too, so no probs there what so ever, I will need to start testing with more phones.
Now I am wondering will it only accept calls for only those contacts that are in my address book, and who is not listed in my contact book it will blacklist and reject, just doesnt sound right to me.

On your Galaxy S II go to Settings, Call, Call Rejection...check the Auto Reject Mode. What is selected in your phone?

[yey first post]
i had the same problem.. do you keep your phone on gsm instead of 3g with the data connection on? if so apparently when it tries to sync stuff it basically keeps your phone line busy so if people try to call you they'll get cut off. after i turned 3g with data connection on the problem disappeared. hope this made sense!

you dont have your own number in contact list right? this is reason why it dont get rejected ... check the black list and see that "unknown" is checked or not

i have same kind of problem. some people call me but they say that my phone is off. but my phone was next to me and i wasnt calling some one else. is this a carrier or phone problem?

The setting for call rejection is OFF

Try with your phone company and see if you are not transferred into any of those family call plans

[Q] Nexus 4 repeated signal loss and calls not coming through

I've got some serious issues with my Nexus 4, I've found posts with similar problems but not exactly what I have. I'm at a loss what to do next so any advice would be much appreciated.
I bought a N4 around March this year, direct from Google, and connected it to TPG Mobile here in Australia which uses the Optus network.
It was fine until about the end of May or beginning of June where it started losing signal regularly. First thing I noticed is it would start dropping calls and displaying "No network available", the triangular status bar at the top would go blank (completely black, not grey) for about 30 seconds, then it would return to normal signal and I could make calls again. However it would do this every few minutes, whether I was on a call or not, and each time it would last roughly 30 seconds and then return to normal.
Around the same time I started to receive SMS on either a delay, or they'd arrive on-time, but then keep sending multiple times for about the next hour.
I rang Google, they got me to go through recovery mode, then it worked fine, for about 24 hours, before it started again. They sent me a new device, which did the same thing within hours of activation, so I requested a 3rd device. At the same time I thought it might be the sim card, so I got a new one of those too.
My 3rd device and new sim card worked perfectly for about 3 days then the same problem started. Factory resets etc seem to fix the problem for either minutes or hours, but never permanently.
Then last week I noticed further weird symptoms, I started getting the usual sms to say someone had called and left a voicemail, however my phone never showed any sign of a call (visual, audio or missed call in the call log). I confirmed with several people who tried calling me and they confirmed the phone rang on their end before going to VM. I tried it myself from a landline and it randomly rings or doesn't ring on my end, however I also noticed when I hung up on the landline without answering my Nexus 4, it continued to ring indefinitely, ie. it hadn't registered the caller hung up.
My provider assures me there isn't an issue in my area, my wife uses the same provider (with an iphone) and has not had these issues. I can't swap sim cards with her though as she has a full-size sim. I tried another sim with my phone for a few hours and it worked fine, however my phone with my sim will sometimes go a whole day without issues so it wasn't long enough to truly test it.
I've deleted all apps that might somehow affect it and the hasn't helped either.
Basically I'd like to know is this likely to be a phone issue, and I pursue the issue with Google, or some sort of network/sim issue and I pursue it with my provider?

[Q] Help: Can't Answer First call if phone is asleep

My friend has a new stock s5 and can not answer calls if the phone is asleep(screen off)
The phone rings and the screen turns on with the answer slider.
He slides the answer call and then it just sits there for a few seconds like it is frozen, but never answers the call.
He can then call the number back and everything works fine, or if the person who called calls back while the screen is still on then he can answer just fine.
We live in a village in alaska (phone company is GCI) which only has edge data.
When he is in anchorage he can answer calls just fine even when the phone is asleep.
He has put his sim card in his old iphone and it works fine.
His wife got an S5 at the same time and both of their phones have the same exact issue.
I have no problems in the same area with my old S2 or my newer S4.
Any idea on what he can change in order to answer calls the first time?

NarfiWillem said:
My friend has a new stock s5 and can not answer calls if the phone is asleep(screen off)
The phone rings and the screen turns on with the answer slider.
He slides the answer call and then it just sits there for a few seconds like it is frozen, but never answers the call.
He can then call the number back and everything works fine, or if the person who called calls back while the screen is still on then he can answer just fine.
We live in a village in alaska (phone company is GCI) which only has edge data.
When he is in anchorage he can answer calls just fine even when the phone is asleep.
He has put his sim card in his old iphone and it works fine.
His wife got an S5 at the same time and both of their phones have the same exact issue.
I have no problems in the same area with my old S2 or my newer S4.
Any idea on what he can change in order to answer calls the first time?
Click to expand...
Click to collapse
No thoughts or ideas on this issue?

I also have this same issue. It does it when its asleep and it also does it when its awake. For some reason it just wont slide over to answer its weird. Mine doesnt do it every time it does it 3 out of 4 times though.
Sent from my Sexy Samsung S5

There have only been a very small number of reports across several phone models of this behaviour.. and AFAIK no one has elucidated a pattern that would elucidate a cause with any certainty. I can tell you that my 900T with the Phoenix ROM does not have this issue.
Unfortunately, no one who has posted with this issue has provided nearly enough details about their configuration to narrow anything down but as pure speculation it may just be a delay in waking up that effectively misses the window in which you could answer the call. If so, then debloated ROMs, faster data connections and those utilizing less power saving features i.e. typically throttling the active processor would likely see the problem less or not at all.
.

Perhaps try reducing the proximity sensor delay time. In theory that may reduce the transition time from screen saver to dialer /home screen.
Edit (or add if not present) build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
ro.telephony.call_ring.delay=0
ring.delay=0
.
.

fffft said:
Unfortunately, no one who has posted with this issue has provided nearly enough details about their configuration to narrow anything down
Click to expand...
Click to collapse
NarfiWillem said:
My friend has a new stock s5
Click to expand...
Click to collapse
Stock. Not rooted and no new roms.
Both his and his wifes phones are new and stock and have the same problem.