Hello xda, I have this strange issue on stock touchwiz lollipop. I understand that when the phone is on LTE, a switch needs to be made to 3G in order to receive or make a call, and the phone automatically does that.
What my issue is, when i receive a call, the network changes to 3G but it actually takes a while before my phone starts ringing, whereas on the caller's end the phone is already ringing. In other words it takes the caller 2-3 rings before my phone actually starts ringing. I dont think its a modem issue because this issue doesnt exist on CM 12 or any other non-touchwiz based roms. Any ideas?
P.S. i did use search, did not find anything similar to this.
P.P.S. it would also be great if someone could reproduce this issue and confirm.
I would still try to change the modem and see if it changes anything. Besides that I have no clue.
Lennyz1988 said:
I would still try to change the modem and see if it changes anything. Besides that I have no clue.
Click to expand...
Click to collapse
Tried different modems too.. Sadly no avail. Can you reproduce this?
TheAwesomeBit said:
Tried different modems too.. Sadly no avail. Can you reproduce this?
Click to expand...
Click to collapse
No I cannot. I'm running CM
Lennyz1988 said:
No I cannot. I'm running CM
Click to expand...
Click to collapse
oh yeah i should have realised. Hope someone else replies soon!
Related
I upgraded to jf1.5 and experienced problems with text messages&my network.
my text's would get to a friend 2 hours later*i wouldnt get even half of their messages in return. in addition i cant use any thing that uses the internet.
if anyone knows a solutin please help me out,I would gladly appreciate it.
well the text might just be your carrier being slow... it happens sometimes... in terms of internet I dunno... do you have TMo internet or are we talking about WiFi? I think a wipe could do you good...
Im using tmobile network for my internet.got the data plan.
along the lines of the titile of thread... i had a problem when flashing a phone to JFv1.5
for some reason i cannot access my ringtones or any of my alerts.. is there a link missing or something i can run to check or undo?
it sounds like you're not using the correct radio (even though i know the old radio should work) or the update is not complete. could you check the "baseband version" in about phone in settings?
if you mean the built-in ringtongs, they're probably all removed to save space
doubleokneegro said:
along the lines of the titile of thread... i had a problem when flashing a phone to JFv1.5
for some reason i cannot access my ringtones or any of my alerts.. is there a link missing or something i can run to check or undo?
Click to expand...
Click to collapse
yeah, it did that for me. make sure in your ringtones volume settings that you have ticked "use incoming call volume for notifications".
related... i flashed to JF1.5 and now if i have my headphones plugged in and music playing, any other noise (ie ringtone or text) doesnt play,and neither will the music. it does the same for calls too. so if i get a call incoming and answer it while music is playing, it will pick up but there is no sound either way. im not sure if it is a setting or the headphone cable.
kthxbye
Did you happen to find a fix for this?
Seems several of us are experiencing the same issue, and none of us have been able to resolve it. Any suggestions are appreciated.
What build were you originally coming from? If it's a non JF build, it'll do you good to wipe and reflash
go point in the thread for his build, stop making these posts or take it to general. this is not development
Moved to Dream General
Mike
Please delete
blueheeler said:
Did you happen to find a fix for this?
Seems several of us are experiencing the same issue, and none of us have been able to resolve it. Any suggestions are appreciated.
Click to expand...
Click to collapse
i just reflashed the radio thing.
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
XxsydenxX said:
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
Click to expand...
Click to collapse
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
flipzmode said:
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
Click to expand...
Click to collapse
Thanks Flipz, I appreciate the feed back, yes I'm on sprint. Using chompSMS, which to my understanding uses Mms.apk as it's middle man.
Anyways i'll update and get back to you on it. And no i didn't replace it.
EDIT: Also tested it using the default messaging app.
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
XxsydenxX said:
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
Click to expand...
Click to collapse
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
flipzmode said:
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
Click to expand...
Click to collapse
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
XxsydenxX said:
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
Click to expand...
Click to collapse
That's actually a known bug with this leak and affects all roms based on it. It's some type of conflict with HTC music. You can check here for a possible fix: http://forum.xda-developers.com/showthread.php?t=657244
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
XxsydenxX said:
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
Click to expand...
Click to collapse
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
flipzmode said:
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
Click to expand...
Click to collapse
Just like a tootsie-pop.... THE WORLD MAY NEVER KNOW.
Hello
i recently updated to latest firmware through odin on my n910c and I've been having problems with my calls. At first people couldnt hear me but I could hear them. I rebooted and now the other side can hear me but apparently they can hear themselves as well making it more difficult to talk for them. Rebooting doesnt help anymore.
:??
bump. really no ideas?
quadlt said:
bump. really no ideas?
Click to expand...
Click to collapse
That problem usually is carrier-related. It's likely your network operator is the source of error, not the Note.
Chefproll said:
That problem usually is carrier-related. It's likely your network operator is the source of error, not the Note.
Click to expand...
Click to collapse
Nope, tried putting the same SIM into my old Sony and there were no problems on both ends. I have rooted my phone so I don't think my repair service will take my warranty anymore so I am left with fixing it myself.
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.
Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
rm83855 said:
Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Konsstantine34 said:
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Click to expand...
Click to collapse
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
rm83855 said:
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
Click to expand...
Click to collapse
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
rm83855 said:
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Click to expand...
Click to collapse
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
rm83855 said:
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
Click to expand...
Click to collapse
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Konsstantine34 said:
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Click to expand...
Click to collapse
Yeah its a strange one, have you made any progression towards a fix? I can't live with a phone that can't make calls lol
rm83855 said:
Yeah its a strange one, have you made any professional towards a fix? I can't live with a phone that can't make calls lol
Click to expand...
Click to collapse
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Konsstantine34 said:
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Click to expand...
Click to collapse
Did your issue just solve itself? i replaced the mixer_path with no luck
rm83855 said:
Did your issue just solve itself? i replaced the mixer_path with no luck
Click to expand...
Click to collapse
When I flash a Tmobile based rom, I use this way to fix it and it works ok. Present days Im using Note 5 rom which is n920G.. based. Havent replaced anything but no problem with calls. If you havent had that issue before the custom rom or something you flash which causes this issue, its probably a software issue. Otherwise Im gonna think your mic has broken down..
Same problem here. Did you manage to fix it by any chance?