hi there,
I need help please, right now i have 2 issues with my phone
1st and most important I cant hear anything whenever i make or receive phone calls, I have to turn on the speaker.
2nd I want to access the edit menu and when I enter the MSL it displayed a message "modem error modem exception occurs"
Im using cyanogenMod 10.1-10130411
thanks
Dandroi said:
hi there,
I need help please, right now i have 2 issues with my phone
1st and most important I cant hear anything whenever i make or receive phone calls, I have to turn on the speaker.
2nd I want to access the edit menu and when I enter the MSL it displayed a message "modem error modem exception occurs"
Im using cyanogenMod 10.1-10130411
thanks
Click to expand...
Click to collapse
The first issue sounds like a hardware problem, were you able to hear when making or receiving calls before you flashed CM 10.1?
For the second issue, what carrier are you using?
Thanks for helping me, I was able to hear before installing CM
And the 2nd issue is already fixed
Sent from my SPH-D700 using xda app-developers app
Dandroi said:
Thanks for helping me, I was able to hear before installing CM
And the 2nd issue is already fixed
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Did you make a back up of your set up when the speaker worked last? If so flash back to that back up and see if it works to rule out hardware issues.
No I didn't , I'm thinking about going back to stock and see if it works, and then try to update using some other room
Sent from my SPH-D700 using xda app-developers app
That would be my suggestion.
If the earpiece doesn't work on stock, I would take it to Sprint or who ever your carrier is.
Sent from my SPH-D700 using Tapatalk 2
Related
I thought I had seen an app to do this but I can't seem to find it so hopefully somebody can correct me for being wrong. Or point me in the direction I can't seem to find this morning. I thought somebody had written an app that would notifiy you when you had an LOS so you would know to reboot your phone. Am I wrong in this?
Here you go ...
http://forum.xda-developers.com/showthread.php?t=1301880&highlight=tasker
Signal Alert is free in the market and will notify you when you connect and disconnect from the network. It will also keep a log of connection events and you can set it to ring or vibrate and flash the notification light. It's worked well for me so far but I uninstalled because I never have LOS.
Sent from my SPH-D710 using xda premium
go here: http://forum.xda-developers.com/showpost.php?p=18728533&postcount=3022
goes into enough detail for ya. will reboot for you automatically anytime you get a LOS
I tried and get a error on tasker about must be 3 alpha numeric I will try better when I get home
Sent from my SPH-D710 using xda premium
Epix4G said:
I tried and get a error on tasker about must be 3 alpha numeric I will try better when I get home
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
just import my profile xml file
Hi,
I am facing a typical problem that during every call if I swipe the middle white phone icon to the left to disconnect call, of does not work. I tried it multiple times. Can someone please suggest if I am doing it improperly.
Thanks for your time.
Sent from my Galaxy Nexus using xda app-developers app
Um. If you're talking about the big red bar with the phone icon all you do is press it.
Sent from my Nexus 7 using Tapatalk 2
bangdrum said:
Um. If you're talking about the big red bar with the phone icon all you do is press it.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply.
I just tried to make a call from another phone to my GNex to verify and my phone is coming as Switched off. Whereas my Gnex is ON and I am able to make phone calls from it to others, but unable to receive any.
Does anyone reported similar issues?
I don't understand your problem. Your first post says you are unable to decline incoming calls. The second post says you can't receive any calls. Which one is it?
Sent from my Galaxy Nexus using Tapatalk 2
I was just doing some tests to decline incoming calls and found the second issue. Below are the problems I am facing -
1. I am unable to decline / disconnect any incoming call. If I swipe the white middle call icon to left the phone vibrates but do not disconnect the call.
2. If phone screen is off for more than 1 hours (appx.) then I think phone goes into deep sleep mode. If I try calling my gnex from other mobile then a switched off message comes. This problem is fixed once I make a dummy call / send any message to other phone.
My phone is not rooted. I would appreciate the feedbacks.
Nvm, misread
Sent from my Galaxy Nexus using Tapatalk 2
NP.
I was just searching the forums but could not any similar thread on these problems. Am I doing something wrong or is it a phone H/W issue?
I've never heard of it before. If you're on stock rom the only thing to try could be a hard reset and if that doesn't help manually reflash factory images. If all fails, I'd return the phone.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks again for your response.
I have few apps purchased, so will these be removed once I hard reset my phone? Is there any way to get them back without purchasing again.
bhupinder08 said:
Thanks again for your response.
I have few apps purchased, so will these be removed once I hard reset my phone? Is there any way to get them back without purchasing again.
Click to expand...
Click to collapse
Google play will remember the purchases. They are tied to your Google account. After you login with your Google account you can download them again without charge. Even on a different phone.
Sent from my Galaxy Nexus using Tapatalk 2
I did a hard reset of my gnex. The call disconnect bug got fixed automatically but not the other one (problem# 2). My phone is still coming as switched off at times.
Anything else I can do to fix it.
Sent from my Galaxy Nexus using xda app-developers app
bhupinder08 said:
I did a hard reset of my gnex. The call disconnect bug got fixed automatically but not the other one (problem# 2). My phone is still coming as switched off at times.
Anything else I can do to fix it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
this might be a dumb question, but are you running jelly bean or ice cream sandwich 4.0.4? Because 4.0.4 had signal problem...
Sent from my Galaxy Nexus using xda app-developers app
have you paid your bill?
Sent from my Galaxy Nexus using xda app-developers app
bhupinder08 said:
I did a hard reset of my gnex. The call disconnect bug got fixed automatically but not the other one (problem# 2). My phone is still coming as switched off at times.
Anything else I can do to fix it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'd try:
1) unlock bootloader (if you haven't done this already)
2) backup /sdcard
3) flash stock JB images: https://developers.google.com/android/nexus/images
Petrovski80 said:
I'd try:
1) unlock bootloader (if you haven't done this already)
2) backup /sdcard
3) flash stock JB images: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I will give it a try and update. Thanks again for your time and support.
gagb1967 said:
have you paid your bill?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yes Dude. My SIM works perfectly on other phones.
bhupinder08 said:
I will give it a try and update. Thanks again for your time and support.
Click to expand...
Click to collapse
Good luck, and I obviously got steps 1 and 2 mixed up: first backup /sdcard, because unlocking your bootloader will wipe it.
I am not sure if it is bug but here is what I observed in past 6 hours.
There is network issue with gnex (phone is coming switched off intermittently) when Mobile networks -> Data Enable flag is NOT checked.
But when data network link is enabled there is no issue with my phone and it works without issues or disconnects.
I have still not rooted / flashed the phone.
Sent from my Galaxy Nexus using xda app-developers app
bhupinder08 said:
Yes Dude. My SIM works perfectly on other phones.
Click to expand...
Click to collapse
I was just trying to put some humor to a stressful situation...... and double checking
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
I was just trying to put some humor to a stressful situation...... and double checking
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
NP, I can understand.
When I get a phone call the person calling me gets an echo but it's fine on my end... I was on aokp/cm10, then went back to stock and the problem still persists. Any ideas?
Sent from my SGH-T999 using xda premium
jwalters1123 said:
When I get a phone call the person calling me gets an echo but it's fine on my end... I was on aokp/cm10, then went back to stock and the problem still persists. Any ideas?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Same. Every time I talk to my girl she asks if I put her on speaker phone when I didn't.
Sent from my SGH-T999 using xda premium
That's weird, what all did you do after you went back to stock? Wiping process, what rom, and kernel?
I just got off two calls that said I was echoing really bad. I haven't been on cm in a while, and had no reports of it yesterday. What roms are you guys running.
Sent from my SGH-T999 using xda premium
jwalters1123 said:
When I get a phone call the person calling me gets an echo but it's fine on my end... I was on aokp/cm10, then went back to stock and the problem still persists. Any ideas?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you're still on stock then try this:
open up your "Phone" app or dialer then press the menu button then "Call settings" then scroll down to "Additional settings" then uncheck the "Noise reduction" feature.
Now try making a phone call to check if whoever you call hear themselves echo. Good Luck.
ssmokey727 said:
If you're still on stock then try this:
open up your "Phone" app or dialer then press the menu button then "Call settings" then scroll down to "Additional settings" then uncheck the "Noise reduction" feature.
Now try making a phone call to check if whoever you call hear themselves echo. Good Luck.
Click to expand...
Click to collapse
I did still the same. Rom xquizit v16 stock kernel
Sent from my SGH-T999 using xda premium
ssmokey727 said:
If you're still on stock then try this:
open up your "Phone" app or dialer then press the menu button then "Call settings" then scroll down to "Additional settings" then uncheck the "Noise reduction" feature.
Now try making a phone call to check if whoever you call hear themselves echo. Good Luck.
Click to expand...
Click to collapse
Thanks and thanks again. I didn't think that would be checked naturally. That's what I get for rooting my phone and flashing the first hour I got it. Thanks again.
Sent from my SGH-T999 using xda premium
I was on aokp when it first started doing it, then restored a backup which was stock + root, checked the settings, problem persists, went to aokp rc1 did a full wipe, dalvik, cache partiton, formatted system, and problem is ongoing.... beginning to wonder if its a network problem?
Sent from my SGH-T999 using xda premium
Been flashing custom firmware ever since this phone came out and never had this problem until now...
Sent from my SGH-T999 using xda premium
The only other thing I can think of is Odin back to straight stock, no root and see if that fixes it, when I get home I will try it and report back.
Sent from my SGH-T999 using xda premium
jwalters1123 said:
Been flashing custom firmware ever since this phone came out and never had this problem until now...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Same here, but for some reason I've been very happy with the latest stock build.
I've noticed that some units are fine with the "Noise reduction" setting checking in and some don't regarding the echo problem.
It wouldn't hurt to try to replace your SIM card. Head out to a T-Mobile store to get a free replacement (If your current line is under your name in the account) SIM cards do go bad...
Does this happen everytime, on every call?
The echo you mentioned, do you mean to the other person you sound echo-y like in a cave or tin can, or is it that the other person hears what they are saying with a half second or so delay, where it makes it hard to talk because they are trying to talk over themselves?
If its the hollow cave/can sound it may well be your phone, if it happens every time. If its the other issue its probably a bad connection. Every time its happened to me, if I hang up and call again it would work normally again.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Does this happen everytime, on every call?
The echo you mentioned, do you mean to the other person you sound echo-y like in a cave or tin can, or is it that the other person hears what they are saying with a half second or so delay, where it makes it hard to talk because they are trying to talk over themselves?
If its the hollow cave/can sound it may well be your phone, if it happens every time. If its the other issue its probably a bad connection. Every time its happened to me, if I hang up and call again it would work normally again.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yeah, every time... and the person on the other end hear themselves echo, not me.
Sent from my SGH-T999 using xda premium
ssmokey727 said:
Same here, but for some reason I've been very happy with the latest stock build.
I've noticed that some units are fine with the "Noise reduction" setting checking in and some don't regarding the echo problem.
It wouldn't hurt to try to replace your SIM card. Head out to a T-Mobile store to get a free replacement (If your current line is under your name in the account) SIM cards do go bad...
Click to expand...
Click to collapse
Yeah thanks, I will do that tomorrow if I can't fix it tonight
Sent from my SGH-T999 using xda premium
Odd. I've never seen that happen on every call! Is it hat way for everyone you call?
Try flashing through the radios again testing each one.
I've seen where some were having probs or just no improvement with a new radio but reflashing it solved everything.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Odd. I've never seen that happen on every call! Is it hat way for everyone you call?
Try flashing through the radios again testing each one.
I've seen where some were having probs or just no improvement with a new radio but reflashing it solved everything.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
did a full wipe again, went back to stock, and now the issue seems to be corrected. :good:
So I went back to stock using Odin, that took care of the problem for me, then I went back to aokp last night, my gf called me and said the echo was back... I hung up on her, restored my new stock backup, called her back, and no echo... I'm not saying it's the Rom or anything but that's what had happened.
Sent from my SGH-T999 using xda premium
Walters? Did you read the thread of AOKP or any of the cm10 variants. Cause half the reports of the last 10 pages include talk about the echo. Just a heads up. It is a cm10 issue, and known. And seems to be being worked out.
Sent from my SGH-T999 using xda premium
mt3g said:
Walters? Did you read the thread of AOKP or any of the cm10 variants. Cause half the reports of the last 10 pages include talk about the echo. Just a heads up. It is a cm10 issue, and known. And seems to be being worked out.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
No I haven't, i was going on Twitter and goo.im taking whitehawx latest builds, for a while their wasn't a active aokp thread, so I all but gave up on xda and was getting it from alternative sources. But it's good to know it's just a bug and not something that was an anomaly with just my phone lol.
Sent from my SGH-T999 using xda premium
Definitely, there is a thread in the dev section. Someone is playing the mirrors from twitter and goo.im so you can see there what the issues and stuff are.
Sent from my SGH-T999 using xda premium
Newly rooted and flashed Goodness Reborn then get the error code 16 every time I try to make a call. Anyone know what this is about? Did a few searches and ultimately had to call sprint to reset the sync from their side. Can they detect root now? Any thoughts greatly appreciated!
Sent from my SPH-L710 using xda premium
Anyone heard of this happening recently?
Sent from my SPH-L710 using xda premium
ssaggy said:
Anyone heard of this happening recently?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
No they cant detect root now, error 16 means your phone made more than 10 unsuccessful attempts to authenticate on their network, or if you flashed then you had both phones turned on at the same time. Its happened to me a few times all you do to fix it is try and make a call, then et error 16.... just stay on the line and automated message will ask you to enter your phone number, then you get transferred to some authentication department(live person 24/7/ 365) they ask you account security questions and then tell you to turn your phone off and back on and it will work fine again. Simple.
When one of my contacts tries to call me, my phone rings and I am only able to see their phone number but not their name. Their phone info will show in this format 1-234-567-8910; oli;63
When I try to call one of my contacts, it acts normal and also shows in the phone logs. I restored the phone to factory settings, but still not able to solve the problem. Any ideas?
Thanks
Sent from my SM-N900T using Tapatalk 2
Let me guess: T-Mobile // WIFI calling?
Getting the same issue.
ceroglu said:
When one of my contacts tries to call me, my phone rings and I am only able to see their phone number but not their name. Their phone info will show in this format 1-234-567-8910; oli;63
When I try to call one of my contacts, it acts normal and also shows in the phone logs. I restored the phone to factory settings, but still not able to solve the problem. Any ideas?
Thanks
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Is that what is causing it? Man, I have been trying to fix this all day. I did two factory resets!
Sent from my SM-N900T using Tapatalk 2
It's a known issue with wifi calling. ... disable it and everything will be fine
Sent from my SM-N900T using XDA Premium 4 mobile app
Never had this problem with any other Wifi calling device. Hopefully it gets fixed in the next update.
Sent from my SM-N900T using Tapatalk 2
Questions and request for assistance go in the Q&A section not in the General section. Please pay attention to the rules in the future.
Thread moved
Have a great day!
Same here on WiFi calling.
Pedro2NR said:
Same here on WiFi calling.
Click to expand...
Click to collapse
Same problem.
Resolved by disable WiFi Calling, wait 60 secs, and turn in back on (if needed)
I Called T-mobile and Tech support sent me couple of SMS and made me turn off and then turn on the phone and called me again and it
seemed to have fixed the problem , but then I realized that problem is fixed from receiving calls from T-mobile numbers or land lines, but the from Verizon number it came with the ;oli;63
This is very strange, hopefully gets fixed soon.
Well I am having another problem now. That is, my phone calls are being rejected automatically when on Wifi calling when the phone is in a deep sleep. I checked under the call settings and changed the auto rejection mode off, but the problem is still there. Can someone else confirm this by chance?
Sent from my SM-N900T using Tapatalk 2
I'm having the same WiFi calling issue. Sucks
Sent from my SM-N900T using xda app-developers app
If you are having this issue please report it to T-Mobile so they are aware that it is a wide spread issue and work to fix it.
Sent from my SM-N900T using xda app-developers app
foriesg said:
If you are having this issue please report it to T-Mobile so they are aware that it is a wide spread issue and work to fix it.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Ready reported it to T Mobile. Not sure if they will fix it soon enough.
Also not getting HD Voice at all.
I have the same issue. I don't have service in my house, so the wifi calling feature is amazing. I've always used a nexus and hard to use third party apps and voips and connect with gv. For the most part if you recognize the number minus the olli, it's no big for now. I'm glad I can still make calls. Update should fix. At least it doesn't happen on reg network.
Sent from my SM-N900T using XDA Premium 4 mobile app
I called tech support in T Mo and they are sending me a new Note 3. But I doubt that will resolve the issue.
tdoughone said:
I have the same issue. I don't have service in my house, so the wifi calling feature is amazing. I've always used a nexus and hard to use third party apps and voips and connect with gv. For the most part if you recognize the number minus the olli, it's no big for now. I'm glad I can still make calls. Update should fix. At least it doesn't happen on reg network.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I turned wifi off; but now when a call comes in it is reported as "unknown." could this be an issue with root? would odining back to factory resolve this?
Charlie
Alright, just called tmo and they said that they are aware of the problem and working to fix it. Hopefully we should see a fix soon!
Sent from my SM-N900T using Tapatalk 2
When I spoke to TMO yesterday the tech guy said they should have the fix by Thursday. If it is still happening by Friday I will bug them again, so far call from landline and tmobile number are comming in fine.
Sent from my SM-N900T using xda app-developers app
Superdad_98 said:
When I spoke to TMO yesterday the tech guy said they should have the fix by Thursday. If it is still happening by Friday I will bug them again, so far call from landline and tmobile number are comming in fine.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I got a second Note 3 from T Mo and still see the same Caller ID issue along with no HD Voice call capability.
I am returning mine until they fix the bugs (no HD Voice call support, 5Ghz WiFi connection instability, and this Caller ID problem)
I really would like to keep the phone... I love the huge display... but I think I will have to stick with my HTC One for now.
surfsnow said:
I got a second Note 3 from T Mo and still see the same Caller ID issue along with no HD Voice call capability.
Click to expand...
Click to collapse
How can one tell when HD Voice calling is active/inactive?