Database Users

[Q] Issues during a call?

Hello to all of you,
I am new the forum and I got my Omnia 7 just about 2 weeks ago. I really like it because of the excellent screen and build quality.
I also like the smooth and sleek feeling of Windows Phone 7.
However, I had regular issues during calls.
During about a third of my calls (including incoming and outgoing calls), I was not able to hear anything at some point during the conversation. The person called or the person who called me could also not hear me anymore.
The phone seems to work (no freeze) and the signal was ok. Turning the speaker on did not help.
Moreover, when I stopped calling and called back everything was fine and working again.
Sometimes it happened already when I picked up a call, sometimes after just a few words and sometimes in the middle of a longer conversation.
It seems to be random but regular, since about one out of three of my calls was interrupted.
It is really annoying and the phone is therefore going back.
However, I really liked the Omnia 7 and I would get another one, if the unit I got was just faulty.
So I would like to ask other Omnia 7 users if you have experienced a similar behavior of your Omnias during calls? Was my unit faulty or is it a general issue?
I would appreciate your feedback.
Thank you in advance.

Does really no one want to comment about how his Omnia 7 handles calls?
I would really appreciate your feedback, even simply stating your Omnia 7 works fine without any mic ans speaker issue.
I thus just added a poll to the thread, so that it becomes even easier to give some feedback.
Thanks in advance for your input.

Same with me on my Omnia 7 - A1 Telekom Austria
Spoke to Samsung but they were not able to help me out but sending me a contact info to a service partner (Extreme Communication in Vienna, btw)
Service Partner told me that there are issues with the Omnia 7 (amplitude control) and I should send my device to them...
As were are having the same troubles on approx 20 devices (95% of handed out devices) I have to check if repairing is an option (warranty from our provider)
will post later, if I have my device back...

No problems here, I've had an Omnia7 16GB since early February. It was unbranded about a week after I received it. No one I've heard of has had such issues but one who complains of "modem-like" sounds for him and the other part prior to missing a call. He also reported this happening every third time or so...

leoms17 said:
... but one who complains of "modem-like" sounds for him and the other part prior to missing a call. He also reported this happening every third time or so...
Click to expand...
Click to collapse
count me in...
having modem-sounds (or robot sounds) as well
and it's not only me - my co-workers have the same issues
but there are more issues:
it's annoying that my Omnia 7 (8gb version) is hardly able to receive calls at the first time (approx 75% of the incoming calls) - if I call back, most of the time it seems to be ok
these problems do not only affect my device, but about 95% of Omnia 7 we handed out to our co-workers
I had the chance to test a HTC 7 Trophy - none of the errors I have on my Omnia happened on the Trophy!

I have the same issue, using T-mobile in the netherlands, I just always assumed it was them.
I've noticed this only happens on 3G and 3G+ networks, if i turn off data and use the normal G network, I don't get call problems, which why I assumed it was t-mobile.

I'm having the same issue on most of my calls. In the beginning I thought it was a network issue. Haven't been able to figure out how to fix it so far. Will call Samsung support.

Has anyone here updated their ROM to the latest XENJK from samfirmwares.com? I had issues with the mic going silent during calls til I upgraded to that
Sent from my OMNIA7 using Board Express

simon marktl said:
count me in...
having modem-sounds (or robot sounds) as well
and it's not only me - my co-workers have the same issues
but there are more issues:
it's annoying that my Omnia 7 (8gb version) is hardly able to receive calls at the first time (approx 75% of the incoming calls) - if I call back, most of the time it seems to be ok
these problems do not only affect my device, but about 95% of Omnia 7 we handed out to our co-workers
I had the chance to test a HTC 7 Trophy - none of the errors I have on my Omnia happened on the Trophy!
Click to expand...
Click to collapse
Please post on your service results! Are you using 3G and 3G+?

Blade0rz said:
Has anyone here updated their ROM to the latest XENJK from samfirmwares.com? I had issues with the mic going silent during calls til I upgraded to that
Sent from my OMNIA7 using Board Express
Click to expand...
Click to collapse
I also have the latest from samfirmware.com. Maybe that does it? Someone?

Thanks for your comments so far...
At least I am not alone with this issue...
I am now really wondering if this could be a software/ROM/firmware issue given Blade0rz comment...
How can I check the firmware/ROM on the Omnia 7?...my Omnia 7 is unbranded from Germany and the "About" section in the settings of my Omnia 7 does not give any info on a build or version number...does anyone know?
@simon marktl:thanks for your feedback...actually 19 faulty units out of 20 sounds quite bad...I would be pleased if you could let us know if the service point could resolve the issue and especially how they did it once you get your device back...
@eqzgkxokwa: I would be pleased if you could let us know about the solution proposed by the Samsung support...thanks (by the way eqzgkxokwa, that´s a tricky nickname )
@ Phyx and leoms17: I actually use the 2G network 99.9% of the time...but as explained I have the issue regularly....so it is not limited to 3G or 3G+...but if 3G off helps for you it just makes the issue even more curious...I do not think it is due to the network, rather something is going on with the phone...

in diagnostic screen hit *#1234# you'll get all your info. Firmware ending in JK1 is the latest.

Thanks leoms17...I may sound stupid but how do I actually get in the "diagnostic screen"?...I did not find it in the menu, so I assume there is some trick...actually I do not want to brick the phone or do something wrong...
Is there no possibility to get a simple info about the firmware without using a crazy code?

also have this issue, assumed it was a poor signal or something like the death grip. Does not seem to make a difference whether im being called or place the call myself.
I got it several times, suddenly it just goes silent. Holding the phone away from the ear so the diplsay turns on seems to make it work again but not for very long.
I had the original T-mobile Germany branded firmware I8700DTMJJ6, updated to JK1 yesterday, but did not test if its fixed now.
One final idea would be to play around with the volume settings in diag mode, increasing volume for incoming calls or something.
Btw, did anyone notice that there is absolutely no background noise during a call, even if the person is in a noisy environment?

leoms17 said:
Please post on your service results! Are you using 3G and 3G+?
Click to expand...
Click to collapse
Yes, I'm on 3G and 3G+
Turning off 3G seems to help a little bit - at least I'm not running into troubles as often as having 3G enabled...

malin_77 said:
@simon marktl:thanks for your feedback...actually 19 faulty units out of 20 sounds quite bad...I would be pleased if you could let us know if the service point could resolve the issue and especially how they did it once you get your device back...
Click to expand...
Click to collapse
good morning
as soon as I have a feedback from my provider if the repairing is covered by our warranty contract, I'm going to send in a few more phones to the service point...
of course I will post the results here, but could take a while...
til later
simon

I've had this issue with my Omnia 7 (T-Mobile US) as well. There were a couple instances where I answered a call and was not able to hear the person on the other end.

malin_77 said:
Thanks leoms17...I may sound stupid but how do I actually get in the "diagnostic screen"?...I did not find it in the menu, so I assume there is some trick...actually I do not want to brick the phone or do something wrong...
Is there no possibility to get a simple info about the firmware without using a crazy code?
Click to expand...
Click to collapse
just dial ##634#
wait about 2 seconds, than you are in the diag menu
after dialing ##634# you'll find diagnosis on your phone for future use

leoms17 said:
I also have the latest from samfirmware.com. Maybe that does it? Someone?
Click to expand...
Click to collapse
I had this issues with the original firmware from my provider (I8700XXJJ3)
and I still have them with
Phone I8700XXJK1
PDA I8700XXJK1
CSC I8700XENJK1
Software on Phone itself is 7.0.7008.0, no NoDo available yet
Maybe the new firmware I8700XXKA1 (January) helps out - but I wasn't able to download it anywhere

Same issues here
I have issues with both modem/robot-calls but lately it's gone from 1/3 of the calls beeing robot to 3/4 of the calls loosing all sound after 20-60 seconds. Robotic cals are not as common. For me I have problem only when I receive calls and never when I make the call.
I have had my Omnia in for service a month ago but the short message from them was that they found no problems. They upgraded the firmware to the latest version but I still have issues as stated above.
My radio hardware version is
0.0.0.2
I have seen posts where radio hardware is much higher. Can the problem be related to old radio hardware?
I am hoping nodo and new firmware from Samsung will fix this but so far I havn't got it.

call log ( missed calls) not working after root.

I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?

Me too!
Bam9 said:
I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?
Click to expand...
Click to collapse
I am also experiencing the exact same issue. Rooted Vzw g2 on page plus. I've searched phone for a log file that looks like it corresponds to the call logs but no love. It is a little obnoxious as I have no idea who calls me if I miss the call.
Have you found a solution?

me, too!
Any insight?

I've not found a thing that will help us, I've found others experiencing the problem, but no solution. I'm running a stock debloated rom and i think therein lies the problem. Something that was removed that was seen as bloatware is most likely what actually tracks the call log. I've been searching for a rooted bloated stock rom, but to no avail. I ran a few other roms and had a call log, but the roms overall sucked and i like the ui of the stock especially the camera app....I'll keep looking, but hopefully someone in the know sees this post and helps us out

I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..

I am running through the same issue, no recent and missed call history, my messaging is fine. The G2 was rooted and flashed to PP. I am wondering if you have solved the problem, if so, could you please share your solution, very much appreciated.
Bam9 said:
I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..
Click to expand...
Click to collapse

same issue
I am having the same issue. I flashed to pageplus, rooted and installed xdabebbs rom. I dont see call history in my recent calls app. Please let me know of a solution

No solution yet, see someone say it could be because of flashing, so how you do the flash, yourself or someone help you.

Find out solution, simply reflash NAM only, i used DFS.

same problem here.
@gjbwj what for you mean reflash NAM?
Running VS982.5 ROM if it maters.
Pretty sure it was something I restored with TiBU that caused it. My wife's phone has the same ROM but I didn't restore anything but apps on her phone.
I would rather not have to start over for what should just be one file corrupted.

If people call me, the first call never works (can't hear me but I can hear them)?

So this is the second S5 I've had and same issue. First one, people could hear me if I called, but if they called me 90% of the time they couldn't hear me on the 1st call. If they called right back or I called them it was fine, usually. I've seen a lot of complaints about this on the S5 online. I even have a copy of the my youmail voicemail that I made on my S2 that was crystal clear and more louder/pronounced if that makes sense, and the voicemail I made on my S5 was all fuzzy and kinda garbled like I was talking 4 feet away from it. Replaced with another S5, and it started happening again except now I'm rooted so no more warranty and they can't/won't do anything. Stock or rom, it happens. So I know a few S5 owners, 3 of them have the same problem. All different networks so not specific to any provider (like if it were an at&t issue etc).
I tried clearing the pin hole at the bottom but didn't seem to make a difference. People think the S5 does this maybe b/c it's water resistant and theirs a membrane inside that hole for the mic that makes it garbled. Speaker phone it works fine. Just pissing me off, I love the phone otherwise, but this is my work phone as well and it's so nice and professional to keep playing phone tag with clients .

This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.

fffft said:
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
Click to expand...
Click to collapse
Pry exaggerated as a bit frustrated. Away for business and on phone right now. I just googled various call issues and saw same/similar on other phones, quite a few S4 reports (like googling S5 can't hear me, or can't hear calls, or android can't hear calls etc). Again not exactly the same but similar, found older Android phones people talking about the same. S5 people I saw post in various threads on different forums, not necessarily made a thread of theirs (like they found an issue like that and bumped thread even if it was a different phone). I'm on AT&T, 3 friends one is T-Mobile and others are Verizon. Though theirs isn't near as bad as mine, theirs happens infrequently on both ends which makes me think maybe carrier related, whereas mine is almost always the caller on my end not hearing me well on the first call. I have two employees with S5s as well and no issues with theirs like this.
I don't know what user config info you want? I've rooted and flashed android for years, I hardly ever touch anything volume/call mod related. I don't know what settings you'd be talking about, stock or rom is the same (didn't install viper, didn't do anything with volume controls on DK as their borked on this version etc). Changed background noise on/off but didn't do anything.Not sure how I use the phone would do anything, they call, I answer, I call, they answer? Happens anywhere no matter signal, whether full bars at house, or office, or lose a few bars when traveling, time of day doesn't matter happens anytime. I just had a conference call where I ended having to use speaker phone for them to hear better but they still said it wasn't clear. Wife just called me and she said through the phone or speaker it's like I'm talking through a towel (speaker not as bad). My AT&T store said they've had a few people come in with complaints of call issues on their S5 but in various ways, and sometimes a factory reset worked, sometimes not. Which didn't work for me, and I blew a canister of air and use a small pin like some said they did to see if anything was clogged in the Mic port but no difference.
I'll be back in a bit, but I could try to record a call with my wife. And I'll upload the files from youmail voicemail where you can hear how loud/pronounced and clear my message is from my S2, and the garbled message from both S5's.

Think I fixed it, let's hope. So I went into safestrap, tried a few things, fix permissions etc. No difference. Restored a few times, no difference, did 3 factory resets, no difference. Each time I either message someone to call me to test, or I logged into youmail to record a new greeting and heard it fuzzy/garbly. Did one more factory reset, msg'd wife to call again, she called and first thing she said was omg it's way louder and cleaner sounding like I'm not muffled. I logged into youmail, did a new greeting and yup it's 100% normal sounding. So no clue why this worked all of a sudden with all my other tries today and before. My first S5 they tested at the AT&T store and it luckily did the issue there so they could hear what I meant and note it. They gave me a loaner and it was sent in, and I guess luckily it was reproducing that same issue when it was checked as they did a replacement since the phone was only 2 months old. And now that I think about it I doubt the tech or whomever was checking it out sat there and did multiple restores/resets like I did, and I guess I was really lucky they didn't get it and test only to have it operate normal like the 10% of the time or whatever it did.
Being rooted now sending in was pointless, as knowing people over the years that have even if sent with stock rom, warranty was denied. F'd up thing is they have to prove rooting caused the issue, I don't have the time nor want to deal with that crap. Example I love cars/trucks and mod everything we have, and with the Magnuson-Moss Act they have to prove your "mod" directly affected the failed part/problem. In the phone world you end up just getting transferred around and dealing with crap trying to sort that out. I have one of my cars modded (ctsv) with pulley swap, full exhaust with lt headers etc, custom tune yada yada, one of my trucks has custom tune/intake/headers/no cats/custom exhaust etc and neither had problems with getting warranty work done, b/c doing a custom tune and pulley etc isn't going to make your radio or nav fail. In the phone world on the other hand they'll tell you to pound sand, root and mic fails, oh that'll be our diagnostic fee part replacement $ have a nice day. lol
i'll try to upload audio files from youmail showing the sound quality difference when I get a chance. I know one of my friends tried a factory reset and didn't work. Guess I'll tell him and the other two to keep doing resets over and over till it works lol, whether that means 5 or 10 times. Why it didn't work on the 1st or even 2nd try is beyond me

CM problem with no Emergency Calls

I'm currently running Temasek's 12.1 ROM, but have flashed the nightly cm-12.1-20150528-NIGHTLY-hlte and there seems to be a problem with Emergency calls. It's not just Australia, but USA, Brazil and several other locations have all got the issue. We've tried a wide variety of possible ROM's but the problem appears to be generic to CyanogenMod.
Can people please check if they can actually make an emergency call to their local country number? Specifically those running AOSP ROMs, but also those with Custom stock-based ROMs. Emergency calls work on firmware from Sammobile so it is either only CM base or perhaps custom ROMs as well.
Symptoms are, the normal emergency number says 'Dialing' but nothing happens - a soft reboot is required to hang up the call, even though it SAYS 'hanging up' It doesn't seem to matter if you dial from the phone app or do Emergency call from the lock screen.
Putting the country dial code in front of the emergency number brings a response that the number is incomplete.
e.g. In Australia, 000 fails, 61000 and +61000 all bring the error.
This is a fairly serious issue if it is generic and not just those of us who have flashed Temasek. You may not use Emergency call often, but when you need it, it is likely to be literally life or death.
Can people please note if they succeeded or not and which ROM, Phone model and kernel they are using?
Also if anyone knows just which file deals with emergency calls that could be useful.

Bump...
No CM/AOSP users have read this?

No one cares because everybody dies eventually.

I am having the exact issue you have described. Tried running Tamasek 12.1 on Sprint Note 3. Could not connect to 911 or different variations of the number.

kenny1991 said:
No one cares because everybody dies eventually.
Click to expand...
Click to collapse
- it's HOW we die that matters...
Plus it may not be Self but significant other that needs the emergency help.
supra2121 said:
I am having the exact issue you have described. Tried running Tamasek 12.1 on Sprint Note 3. Could not connect to 911 or different variations of the number.
Click to expand...
Click to collapse
I've raised an 'issue' over on the CM forum site - so far it appears to have escaped notice. I wonder how they'll feel if peiople start posting about the injured, mugged, assaulted etc. that can't be reported?
Strangely I thought it would be seen as an urgent issue. Go figure...

I was told by Zelendel that all CM ROM's have the issue but it is OK on AOSP ROMS. I have now tried SlimROM and BlissPop ROMs, both AOSP and neither of them can call Emergency.
Given some countries have legislated that all phones must be able to dial Emergency, there comes a question of whether we are committing illegal acts in modifying a phone so it cannot call Emergency...

For anyone that finds no emergency calls to be a deal breaker, the Alliance ROM works and is a very good ROM for being able to set it up how you like - very configurable and with good support.

I am having the exact issue you have described.

sseuorosal said:
I am having the exact issue you have described.
Click to expand...
Click to collapse
Valid point! You can only check by making a real call. And what I am going to tell the police or the fire department? “Sorry I was just wondering if my ROM is supporting emergency calls!” And that’s the deal breaker why nobody dares to make a call

dnize77 said:
Valid point! You can only check by making a real call. And what I am going to tell the police or the fire department? “Sorry I was just wondering if my ROM is supporting emergency calls!” And that’s the deal breaker why nobody dares to make a call
Click to expand...
Click to collapse
Update re the Emergency call issue - at CYAN-6622 - issue has been upgraded to major and apparently people can vote on it so if you're concerned that you don't have a phone that can be used to save your (or others) life in an emergency, please vote there.
Also apparently the issue goes back to at least CM10 and possibly CM7 days and it is on multiple phones, not just Note 3's.
Anyone got access to a nexus? If the issue is so widespread it would almost have to be in the base from Google. So maybe if it also happens (or doesn't happen) on a Nexus we can get Google to fix things.
For Americans concerned about dialling 911 you can call your local station and ask to make a test call, then when you do you can tell 911 you have the Despatch permission for a test call - so no fines.

Thanks to all those who got involved in the Jira issue - apparently it is now resolved and Temasek will have the fix in his update due today. Those on other AOSP/CM ROM's might like to nudge your devs about getting the fix. Should be in CM nightlies today I think.

Rooted P10+ not connecting calls (mostly indoors)

Hi there- I have a VKY based P10 Running B124. As of the last couple of months I am noticing my placed calls are taking forever to connect when in my house, and almost all calls go straight to voicemail without any ring or even notification of a missed call. I am a T-Mobile user in the northeast US. I was hoping someone could give me some suggestions on figuring out the source of this issue.
1. OS based issue? Would updating be a factor on dialing calls?
2. Bad SIM card? Phone behaves more normally outside, so this seems less likely?
3. Phone physically damaged or degraded? Nothing remarkable has happened, and in other respects the phone has actually been terrific.
Phone repair people in the US won't talk to me. T-Mobile tells me I need to buy one of their phones. I am assuming looking around android and Huawei sub reddits will tell me to update.
Any suggestions? I am pretty miserable over here, and people are getting mad about not being able to reach me.

Issue was resolved with new FW. Turned out to be compatibility issues with T-Mobile