am i alone or is any one else facing this issue.. in settings even after enabling this option i get calls from random numbers.. any suggestions?
Related
I have observed one thing..whenever there is a short missed call and my phone is in locked state..it wakes up in 3-4 sec..if this call happens to be a missed call (only 1-2 rings heard on the caller's end), my phone doesnt recognize that number (even if it is present in my contacts) neither it shows which number i missed...so frustrating..any body else experienced this?
any workaround? i tried many registry tweaks posted on internet, nothing helped..hard reset my phone..but problem still there..
Same problem here, I suppose it's a bug on Phone part of the ROM, maybe it will be fixed in future versions. I try all the CPU performances and the problem persist.
It takes a little bit of time before the caller ID number comes through and get matched to your contact list. Depending on how many contacts you have on your list, it may also take a bit longer to find a match in a long list. So if your caller calls and ends call shortly, then the match may not be completed. It's not a bug.
But when my screen is on..i dont see this issue at all, i have checked many times giving as short call as i could..
i issue comes when the device is locked..so i think while waking the device up it takes long and there somehow it doesnt activate the callerid service, so the unknonw caller issue occurs..
When your screen is locked, your phone is in sleep mode. So it takes longer time to wake up first, then receive the call.
Hello,
I have a samsung h1 (i8320) phone, and my problem is that when someone calls me
the phone is not ringing. The caller phone display redirection active, and the caller can only hear a small beep and the call time counter starts after that.
I can call anyone and recieve sms without problems.
(if i put my simcard to a nother phone there is no problem with incoming calls)
I think i caused this error, when i used the root menu *#197328640# to test my gps signal, but accidentaly i changed some setting related to networking i think.
The phone now displays EDGE instead of GPRS, (network mode gsm 900/1800).
I am able to recieve calls again by enabling GCF test mode in the root menu, but i dont know what it does.
I flashed the phone and made a factory reset, but the root menu settings where not reseted.
I would like to know if there is any way to reset settings in the root menu to default?
Thanks,
Gaszton
A test is needed to verify if it's a software problem (less possible) or an hardware problem (more possible).
Bring it in warranty assistance if you have or just try to reinstall roms or updates.. i hope you know how to.
Maybe, if you have some time, you may try the android rom for that phone... go here and give a check...
http://samsungi8320.freeforums.org
I'm on stock KK and quiet mode works good except for whitelist but i allowed some numbers for call on the whitelist (mostly family for emergencies) but when i activate quiet mode and call from one of those allowed contacts my phone doesn't ring at all, call is ended (from the phone calling i go directly to voicemail) and i have notification of missed call when i wake up the phone.
The option to let them pass through if they call twice in less than 3 minutes work as expected, but the whitelist doesn't. Does it work for you?
any thoughts?
fdbailes said:
I'm on stock KK and quiet mode works good except for whitelist but i allowed some numbers for call on the whitelist (mostly family for emergencies) but when i activate quiet mode and call from one of those allowed contacts my phone doesn't ring at all, call is ended (from the phone calling i go directly to voicemail) and i have notification of missed call when i wake up the phone.
The option to let them pass through if they call twice in less than 3 minutes work as expected, but the whitelist doesn't. Does it work for you?
any thoughts?
Click to expand...
Click to collapse
i am also facing the same issue.
nikilsahil said:
i am also facing the same issue.
Click to expand...
Click to collapse
glad to see i'm not the only one, i also tried to modify contacts number and add country code and regional code to match exactly the number when you receive a call, but the option of 2 call in less than 3 min works anyway even if the number doesn't have country code.
Hope someone knows something about this.
I cannot make any outgoing call. Whenever i try dialing any number it disconnects showing cant call. Sometimes it does connect and rings and then disconnects showing same error.
Since i have updated the OPT to marshmallow i have been facing this issue.
This is quite inconsistent behavior, now i have been facing this from last week. Before that i had faced it a month ago.
Kindly help, i wont be able to dial any one in case of emergencies.
I am also facing the same problem. Can someone help?
So far i noticed that opening folder will crash mifavor launcher if all animations are disabled in developer settings. While all animation are enabled this will not happen.
call settings/carrier settings/additional settings will crash com.android.phone which is where u find waiting calls option.
P.S
Call settings/carrier settings/additional settings crash can be resolved deactivating both sim cards and activating again in dual SIM settings.
** Microphone still doesn't work when making calls (randomly) from one of two sims
Maybe it's important to mention that this occurs more when calling fixed lines (land lines) then mobile. Haven't test it yet if it's lack of land code prefix issue.
wallor77 said:
So far i noticed that opening folder will crash mifavor launcher if all animations are disabled in developer settings. While all animation are enabled this will not happen.
call settings/carrier settings/additional settings will crash com.android.phone which is where u find waiting calls option.
P.S
Call settings/carrier settings/additional settings crash can be resolved deactivating both sim cards and activating again in dual SIM settings.
** Microphone still doesn't work when making calls (randomly) from one of two sims
Maybe it's important to mention that this occurs more when calling fixed lines (land lines) then mobile. Haven't test it yet if it's lack of land code prefix issue.
Click to expand...
Click to collapse
what's the point of a bug reporting thread of a 4-builds-old system?
Get 7.1.1...