Hi,
I have a Galaxy Nexus, I just recently started using AOKP b33 and Franco's kernel. I'm on Rogers. I've noticed that sometimes, the call forwarding or the voicemail notifications will appear in the notification bar, even though I don't use call forwarding and don't even have voicemail. They'll then generally go away for a little while if I try to check the settings, or sometimes just on their own.
I've found several occurrences of this in the forum but no solution. I think it has something to do with AOKP or maybe the radio - I'm running UGCL1, but I've also noticed it with UGLA4. The only other thing I've noticed is that any time this happens, my carrier text changes from the normal ROGERS to "Can Rogers Wireless Inc U" -- maybe some sort of signal drop?
Anybody know what's causing this and how to fix it? Thanks!
Try ##002# in the dialer.
It fixed it for me, but it seems to have come back just the other day.
Sent from my Galaxy Nexus using xda premium
I'm gonna bump this cuz it happened again to me. I checked if my phone actually was forwarded but it's not, just says it is till I click on forwarding settings.
Sent from my Galaxy Nexus using xda premium
I am having the same problem on my GNex (AOKP Milestone 5) with TELUS. I'd really like to see a solution to this.
Bump
I'm having the same issue as well, sometimes it will automatically enable forwarding then when I go to the option it will automatically update and then disable it.
I'm on Rogers and having the same issue as the first poster. It doesnt actually forward the calls, and when I go to settings and click call forwarding, the icon disappears. I've looked around also and found no solution. I'll keep looking. I have the stock kernal, and build 35 currently.
Zak
Has anyone gotten to the bottom of this? I'm having these issues (exactly as described above) with AOKP M6 (using the included kernel.) I'm on Rogers as well.
crl34 said:
Has anyone gotten to the bottom of this? I'm having these issues (exactly as described above) with AOKP M6 (using the included kernel.) I'm on Rogers as well.
Click to expand...
Click to collapse
Follow-up in case someone comes upon this thread with the same issue: I replaced the default AOKP kernel (tuna I think?) with Air Kernel and this issue has not recurred since.
Related
Hey guys
I got a pretty weird problem here.
I have a Galaxy Nexus with Rogers running the stock USA 4.0.4 rom from google.
Since this morning, any incoming calls I get seems muted from both side.
Caller: no mic / no speakers
Me: no mic no speakers
But if i call bacl, it work.
So incoming bug, outgoing are fine......
Here's what I tried until now:
Clear cache
Reboot
Uninstall recently added apps
Reboot again....
My girlfriend is running a gnex from rogers with the stock canadian version (first version of ics) without problems.
Is anyone know about this issue and have a fix?
Btw, network seems fine, 3g work well, wifi as well
Try flashing the radio from the stock canadian version (or a later leaked one for your region is one is available) if you have unlocked the bootloader. The yakju builds contains radios adapted for the European market (based on the naming of the radio version, XXLA2 in this case) so could have incompabilities with other parts of the world.
Thing is that it's was working well until this morning. And it's the stock us Rom gave by google....
Other canadian are using it.....and if the phone is accepting outgoing call well, as same as receiving call but just not having mic\speakers, i don't thong it's because of the radio it is using. I'M not a programmer but it sound weird to me that it can work well for a few days then the radio decide it's incompatible all of sudden.
blunden said:
Try flashing the radio from the stock canadian version (or a later leaked one for your region is one is available) if you have unlocked the bootloader. The yakju builds contains radios adapted for the European market (based on the naming of the radio version, XXLA2 in this case) so could have incompabilities with other parts of the world.
Click to expand...
Click to collapse
What radio version did it include? XXLA2? You can check under Settings -> About.
Try running a logcat (ADB logcat) and then call your phone to see if it throws any errors.
There is a known signal issue with 4.0.4 which might be what you are experiencing. If you root your phone, you can try setting the min frequency to 700 MHz and flashing either UGKK7 or UGKL1, which are canadian basebands. I'm on AOKP b30 with UGKL1, and I have no issues, despite my min frequency being 384 MHz.
19250xxla2
blunden said:
what radio version did it include? Xxla2? You can check under settings -> about.
Try running a logcat (adb logcat) and then call your phone to see if it throws any errors.
Click to expand...
Click to collapse
The thing is that the main reason i downloaded that rom is because i want auto-update by google....if i root i will not get it.....if i change radio i will not get it as well......
TheSobadef said:
There is a known signal issue with 4.0.4 which might be what you are experiencing. If you root your phone, you can try setting the min frequency to 700 MHz and flashing either UGKK7 or UGKL1, which are canadian basebands. I'm on AOKP b30 with UGKL1, and I have no issues, despite my min frequency being 384 MHz.
Click to expand...
Click to collapse
I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.
MAN I THING YOU HAVE SOMETHING HERE
I'm suscribed to Rogers one number as same as you. I never used it since I registered but that could be related. I'll dig into that direction.
matd123 said:
I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.
Click to expand...
Click to collapse
Man as strange as it appear it now work...... (i did nothing) mayne Rogers is messing up with the network.....since LTE launched network act weird sometime.....but i'll take a look to the one number thing
matd123 said:
I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.
Click to expand...
Click to collapse
This issue seems to be all over the place, but I'm having extreme problems getting it fixed.
My GSM galaxy nexus regularly loses all signal everywhere I normally get full bars.
Also, sometimes I'll look at it WITH signal, and it enables Call forwarding and leaves that on until I go into the settings and try to disable it. (There is no option to disable it tho...it just automatically disables after it takes a minute to load call forwarding settings).
Has anyone else been having these problems and been able to fix it? I flashed new radios, roms, kernels....everything! And I just can't get the problem solved. Recently I flashed the UGLC1 radio and that worked for a couple days but now it's just as bad as it ever was.
MarkB709 said:
This issue seems to be all over the place, but I'm having extreme problems getting it fixed.
My GSM galaxy nexus regularly loses all signal everywhere I normally get full bars.
Also, sometimes I'll look at it WITH signal, and it enables Call forwarding and leaves that on until I go into the settings and try to disable it. (There is no option to disable it tho...it just automatically disables after it takes a minute to load call forwarding settings).
Has anyone else been having these problems and been able to fix it? I flashed new radios, roms, kernels....everything! And I just can't get the problem solved. Recently I flashed the UGLC1 radio and that worked for a couple days but now it's just as bad as it ever was.
Click to expand...
Click to collapse
if youre on stock just update to IMM76I thats the build just released to solve these issues
if your on a custom rom you may want to flash a kernel that has incorporated these fixes GLaDOS 1.30 for example
Wondering if anyone has seen this issue before. (see attachment)
If the caller is in my contact list, name is displayed without issues. However, if they are not, I get a string of strange characters appear as the name. Same goes for Private Callers, or unknown numbers.
The phone is a Samsung Galaxy S3 running AOKP d2att (4.2.1 JOP40D) Build 1.4.2012
Kernel Version: 3.0.57
Android Version: 4.2.1
Baseband: I747MVLDLK4
Model: SGH-I747(M)
Originaly purchased from Rogers (Canada) but used on the Fido network. I have had no other issues, LTE works great via FIDO or Rogers apn's and caller ID worked fine in stock.
I also have the same issue with CM10. Any help would be great!
I experience this as well. It started happening after i changed from running stock Touchwiz to Task's AOKP. It would be nice to have it fixed but as long as I can see the number of the caller that's good enough.
I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?
Lahey360 said:
I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?
Click to expand...
Click to collapse
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.
BAM1789 said:
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.
Click to expand...
Click to collapse
Agreed, and believe me, I have already been down that road numerous times. After a full wipe and reflash back to stock, everything works fine. As well as simply restoring to stock after AOKP/CM flash via CWM backup. Yet, as soon as a custom ROM is applied, good bye call display. Something has to be missing...
My friend is having this issue with his Fido Galaxy S3 running CM10 stable. A fix is definitely needed!
Same thing here on latest AOKP on SGS3 on Fido.
Rogers here, same issue. CM10 stable. If the person is in my contact list it shows normally, but the caller id is wonky as described above.
I think since people on the contact list show normally this issue takes a little while for some people to notice. At first I thought it was just some foreign guy calling me Then a few more calls... and I found this thread, although I would describe the display as "garbled" really. But obviously more than a few people have this issue.
This might be one of you guys, http://code.google.com/p/cyanogenmod/issues/detail?id=7074 -- talking about CM10.1, but this bug is in CM10 too obviously.
Possible fix
Hi guys,
I was thinking about this and noticed that people with this problem seemed to be on the I747MVLDLK4 baseband. It occurred to me to try switching it out and seeing if that had any effect.
Yes it does.
I used my co-workers phone (removing his phone number from my contacts first of course) and called my phone. Normally I get gibberish (I tested immediately before flashing to verify) and viola, my caller ID works now, with the tiny exception that there is a trailing "@" symbol. But otherwise it showed up correctly.
I flashed the I747MVLLH1 baseband and that *seems* to have fixed the issue. Apparently the speeds, connectivity and such can vary between basebands and your location so you may want to try a few basebands listed here and see if any of these work for you. Just remember not to flash an AT&T baseband on a Canadian phone or the other way around.
Post your results if this works for you. Cheers!
That is great news!!! I will test a few and post results.
Link is broken tho....
Edit:
http://forum.xda-developers.com/showthread.php?t=1831898
Edit2:
WORKED LIKE A F**KING CHARM!!!!!
Went down the list flashing each one and doing some various tests. Placing/receiving calls, LTE connectivity, speed tests, etc... Safe to say, I747MVLLH1 seems to be working best.
My phone is originally from Rogers, but service is with Fido (Fido sim) yet still using the Rogers APN settings.
Right on man Glad it worked for more than just me. That default base band actually seems pretty lousy in general, thinking back I'm not sure it was really working in the stock, factory firm ware either. I recall seeing unknown caller from phone numbers that I knew had id's.
Cheers!
Edit: can we mark this solved?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID
chasem said:
After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID
Click to expand...
Click to collapse
This worked for me as well, thank you.
Same problem on my LG P930 from Bell, unlocked and connected to rogers. Using CM 10.1 2/21 nightly currently, but it was happening on older nightly's too.
I guess I have to hunt down baseband options for my handset unless other solutions have come up since the last posts to this thread.
spindley said:
This worked for me as well, thank you.
Click to expand...
Click to collapse
Worked for me too.
Samsung Galaxy S3 i747 Rogers Toronto "I747MVLLH1"
Open jira report
There is an open JIRA report against CM10.1 RC3 in regards to this issue.
Yes flashing an older ICS modem will work temporarily but there is obviously a problem with the newer JB modems released for our devices that we can hopefully get resolved.
If you want to see this fixed, sign in to JIRA and vote for the issue to help get it some support.
https://jira.cyanogenmod.org/browse/CYAN-1202
I also understand that not all of you are necessarily using CM10.1 but you may be using a ROM that pulls it's base code from CM so there is a good chance if they fix it, it will be fixed for whatever other ROM you are using.
Thanks.
Using the SynergyROM for AT&T, we all seem to be getting the "+" sign prefixed to all of our incoming calls. This is a huge PIA to an otherwise very well done ROM. I recall having this problem months ago with a different ROM, but I can't for the life of me remember which one it was and what the fix ended up being. Can anyone remember any of the other ROMs they have seen this issue with? I know Task650s build had this problem, but it seems it's fixed in his ROM now.
Would love to know the answer to this as well. I tried SynergyROM and liked it quite a bit but this among some other annoyances pushed me to finding other ROMs.
I had this issue with one of Task's first 4.2.1 builds. Been fixed for a long time there.
I used a combination of contactscleanup and prefixer in the interim to handle the +.
It was one of the stock builds that had this problem, just wish I could remember which one.
I am also having this issue. I am on AT&T, GalaxyMod RLS16 ROM, KT Kernel(2/7 version). Android version 4.1.1.
The "+" sign is causing problems for me when my allowed contacts are not ringing through to me when the phone is in Call Block mode (I keep it this way while I am at work).
If anyone has any suggestions has a solution that I may have missed while searching, it would be appreciated if you would share. Thanks!
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?
If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.
movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while