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
Related
***EDIT*** I believe that I have found the solution to this issue (at least for me) by flashing the FuGuMod Kernel as advised to do by 2 users (jetrii and slyydrr) who advised me of this in the following thread here http://forum.xda-developers.com/showthread.php?t=1487056 on pages 7 and 8 respectively.
This fix may NOT work for you but I can say that it has worked for me. Please see post #33 (and onward) in this thread.
I have painstakingly been trying to find a solution to this issue and it SEEMS as if I have FINALLY found one so if I have helped you in any way then I ask that you please press the "Thanks" button and please visit the thread above and say thanks to jetrii and slyydrr as well. I also recommend that if this works for you that you go to the FuGuMod thread here http://forum.xda-developers.com/showthread.php?t=1438417 and pay tribute to nikademus for his kernel!!! I know I sure have... Also... Make SURE that you flash the correct kernel version for your ROM ie: 4.0.3 ROM = 4.0.3 Kernel, etc...
Thanks...
Hi everyone,
I have decided to start a fresh thread here as I have seen (and replied to) many threads regarding people with the GSM version of the GNEX (like I have) that are suffering from random signal loss of both data and GSM services for apparently NO REASON.
If you are also experiencing these issues I ask that you please post them here so that they are easy to follow and I also ask for anyone with ANY answsers to please post them here as well. Also... Please post what firmware you are running and any steps you have tried to fix this issue be them a failure or a success. I have done the following...
I am currently on the FoxHound v1.0 AOSP 4.0.3 firmware and experience these random signal drops. I have flashed NUMEROUS radios / modems to try and fix this with no success. I had been told by someone that the issue MAY be a BUG in the 4.0.3 AOSP ROMS but I have a hard time believing this as some people do NOT experience these same issues while on 4.0.3 ROMS.
What did work was to flash to the Android Revolution 4.0.2 ROM and on this I do NOT experience these random drops which COULD mean that the problem DOES lie in the AOSP builds of 4.0.3 but again... I have a difficult time believing this but it could be true. Also... Stock firmware (4.0.1) for me here in Canada does not experience these random signal losses either.
This is very annoying as I want to run the 4.0.3 custom ROMS for their customization capabilities, etc but I cannot keep my device in a USABLE state when on 4.0.3 so I have to go back to my trusty SGSII.
Again, please post here to voice your concerns and opinions on this and perhaps SOMEONE will be able to find us a solution.
Thanks,
are you using your carrier supplied radio?
s2d4 said:
are you using your carrier supplied radio?
Click to expand...
Click to collapse
Yup. Im on UGKL1 which is the radio that shipped on my device. I have also tried other radios (XXKL1, UGKK7, XXKG6, etc) as I mentioned as well and I still experience the same issue and others have mentioned the same things as well with no successes.
There was this one time that I had lost signal randomly (while on stock unmodified out of the box ICS) but I was able to get it back with a factory reset. After that it never happened to me again.
jonnyg1097 said:
There was this one time that I had lost signal randomly (while on stock unmodified out of the box ICS) but I was able to get it back with a factory reset. After that it never happened to me again.
Click to expand...
Click to collapse
Thanks for the comment. May I ask what Radio your device has on it? Are you running any sort of custom ROM now? If so, what are you running?
Right now the radio is KK6 (im on stock yakju 4.0.2 now) but at the time it was what came with the phone (shipped from Rogers)
jonnyg1097 said:
Right now the radio is KK6 (im on stock yakju 4.0.2 now) but at the time it was what came with the phone (shipped from Rogers)
Click to expand...
Click to collapse
Hmmmm... Interesting... You got an OTA update to 4.0.2? I have seen other posts that people here in Canada are complaining that they have not received ANY OTA updates at all... When did you get this?
Since I have been on a custom ROM I have not seen this update obviously...
I'm on GSM with Rogers as well. I haven't noticed any significant signal drops with the exception of my basement (no cell phones get signal there - its a fortress lol). I am on 4.0.3 as well. I have read that the 4.0.4 has improved radio... so it may be worth looking into. I saw a WIP 4.0.4 GSM Rom here.
I've been experiencing this as well. I'll have a great signal, then suddenly it totally disappears, and after a few seconds the signal comes back. It's even happened during voice calls as well. I experienced this on the stock device (4.0.1). I'm now using the GummyNex rom on 4.0.3 (w/ a stock radio), and I'm still experiencing these random signal loses. (T-mobile USA in NYC, btw).
It's not a constant problem, but it happens a few times a day. enough to be an mild annoyance.
grantith said:
I've been experiencing this as well. I'll have a great signal, then suddenly it totally disappears, and after a few seconds the signal comes back. It's even happened during voice calls as well. I experienced this on the stock device (4.0.1). I'm now using the GummyNex rom on 4.0.3 (w/ a stock radio), and I'm still experiencing these random signal loses. (T-mobile USA in NYC, btw).
It's not a constant problem, but it happens a few times a day. enough to be an mild annoyance.
Click to expand...
Click to collapse
Hmmmmm... I ONLY seem to get these signal drops on 4.0.3... Weird... You have a GSM device right? Not CDMA - LTE?
I found something new to try when I get home but if anyone may want to try it now and post your results it would be very helpful and appreciated.
This is a radio from the Japanese variant of the GNEX and most people who have tried it have had good success with it... See the link below...
http://forum.xda-developers.com/showthread.php?t=1478685
I THINK I am experiencing this. My phone keeps going from H+ to 3G non stop at the top. How can you tell if your signal is being dropped? (sorry new to this) I've seen posts with a network screen? showing connection but I can't seem to find this.
Haven't had any issues as far as that. There were times when I was using the browser and it said network error but everything still worked.
Sent from my Galaxy Nexus using XDA Premium App
mattymac said:
I THINK I am experiencing this. My phone keeps going from H+ to 3G non stop at the top. How can you tell if your signal is being dropped? (sorry new to this) I've seen posts with a network screen? showing connection but I can't seem to find this.
Click to expand...
Click to collapse
You will notice because the signal bars icon will go "completely blank" and for example... If you are on your lockscreen and you can see the name of your provider...It will disappear completely for a couple of seconds and then come back...
No I guess I am not experiencing this. I'm not exactly sure what the difference between H+ and 3G is but my phone seems to stay in 3G until it transfers data, when its transferring data, it goes into H+, then back into 3G. Maybe this is normal. I was just curious because I did flash Yakju and the radios when i bought it.
mattymac said:
No I guess I am not experiencing this. I'm not exactly sure what the difference between H+ and 3G is but my phone seems to stay in 3G until it transfers data, when its transferring data, it goes into H+, then back into 3G. Maybe this is normal. I was just curious because I did flash Yakju and the radios when i bought it.
Click to expand...
Click to collapse
Yes... That is normal...
yiannisthegreek said:
Hmmmm... Interesting... You got an OTA update to 4.0.2? I have seen other posts that people here in Canada are complaining that they have not received ANY OTA updates at all... When did you get this?
Since I have been on a custom ROM I have not seen this update obviously...
Click to expand...
Click to collapse
Well, when I first flashed 4.0.1 yakju I got notifications of being able to upgrade it OTA. However, at the time I must of messed something up when I flashed it because the updates werent successful when I went to update it. So I got fed up with it and I flashed 4.0.2 manually via fastboot.
yiannisthegreek said:
I found something new to try when I get home but if anyone may want to try it now and post your results it would be very helpful and appreciated.
This is a radio from the Japanese variant of the GNEX and most people who have tried it have had good success with it... See the link below...
http://forum.xda-developers.com/showthread.php?t=1478685
Click to expand...
Click to collapse
So I flashed this radio and I get SOMEWHAT better stability but it only accesses the EDGE network and NO 3G/H... Guess this is a no go too...
HD Rom, Latest build.
Radio - XXKK6
Had the stock radio with the HD Rom, and thought that my random lost connections on market were due to my not flashing the recommended radio. Flashed the recommended radio (current), and still experienced them. Signal is better, and oddly enough voice doesn't get lost. Phone doesn't show that there is no signal, in fact it is at 3 bars on H.
Edit: I use a regional carrier, that doesn't list APN settings. By leaving APN type blank, I seemed to have solved the problem. Also dramatically increased the signal strength (Using Network Signal app).
finch8423 said:
HD Rom, Latest build.
Radio - XXKK6
Had the stock radio with the HD Rom, and thought that my random lost connections on market were due to my not flashing the recommended radio. Flashed the recommended radio (current), and still experienced them. Signal is better, and oddly enough voice doesn't get lost. Phone doesn't show that there is no signal, in fact it is at 3 bars on H.
Edit: I use a regional carrier, that doesn't list APN settings. By leaving APN type blank, I seemed to have solved the problem. Also dramatically increased the signal strength (Using Network Signal app).
Click to expand...
Click to collapse
What is the name of this network signal app? Developers name and what does it do exactly?
So first a little bit about my phone:
It's a GSM Galaxy Nexus on Telus in Canada. It's rooted and running AOKP M4. I had just flashed Franco Kernel M2, but that's when my trouble started to I just wiped my data, reflashed AOKP M4 and restored from a back-up from before I flashed that kernel. I've never flashed a new radio.
The problem is as follows: when the screen goes to sleep, I lose signal altogether. I don't receive calls, I don't receive texts, nothing. But as soon as I wake the screen, the signal comes back (and it's strong - 3 or 4 bars so it's not a service issue).
Has anybody else had a similar problem? What's the fix?
Any help would be appreciated...thanks!
------------UPDATE--------------
Confirmed that I had no issues after flashing back to 4.0.2 stock. Went back to stock 4.0.4 and the problem surfaced again. Tried B29 of AOKP and utilized a minimum CPU setting of 700 MHz which resulted in no issues with the phone signal after going to sleep. I was able to duplicate the problem when I set the CPU to a minimum of 350 MHz. Went back to 700 MHz minimum and everything is working fine.
I'm wondering if the stock 4.0.4, in an effort to squeeze more battery life, lets the processor speed dip down below the threshold require to keep the phone "listening".
-------------------------------------
I've had the same issue after upgrading my phone to 4.0.4. It started life as a 4.0.2 GSM GNex with the Samsung ICS build on it. I flashed the Google version, then manually updated to 4.0.4. I've been searching the forums and found quite a few people with the same problem, but no real solution yet. I'm going to try a few things before taking a swag at a new radio.
I have the exact same problem
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
-------------------------------- UPDATE ---------------------------------------------
I concur with warhummer. After rooting my Nexus again after the 4.0.4 update, and installing CPU Tuner from the Market place, I increased the minimum CPU speed to 700mhz (up from 350mhz) and it appears to be keeping its signal now. This would also tally with the fact that while my Nexus was doing things in the background it would maintain signal, but as soon as it was idle, within a few minutes the signal would die.
--------------------------------------------------------------------------------------
memoreks said:
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
Click to expand...
Click to collapse
I've confirmed a fix (for myself anyways) that if you can get a CPU app that can modify the processor speed, try that via the stock 4.0.4. I'm going to flash mine now.
I have the exact same problem. I was on a Rom stock 4.0.2 with root, and after flashing the OTA, I had the problem when the screen is off.
To be sure I flashed the factory image in 4.0.4 but I still had the problem.
I looked at logcat and I had this error that seems to be the problem:
Code:
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 10.114.222.1 32 0.0.0.0} failed with code 400 : {Failed to remove route from default table (No such process)}
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 0.0.0.0 0 10.114.222.1} failed with code 400 : {Failed to remove route from default table (No such process)}
I'm going to send my phone to repair and hope they change it, or if someone has a solution.
Right now I flashed the 4.0.2 factory image to be able to use my phone.
PS : maybe someone know how to contact a Google dev ? To report the problem to them ?
SetCPU fixes it
How to sort out the problem of losing signal when GNexus goes into Standby:
1. Install 4.0.4 Stock ROM
Either use the OTA patch or do a clean 4.0.4 install from the Google Stock ROMs page.
2. Root your GNexus
There's lots of info about rooting you GNexus. I used CWM to root mine.
3. Install SetCPU
4. Run SetCPU, and raise the minimum CPU speed from 350mhz to 700mhz. Then tick "Set on Boot". (see attachment)
This should now mean your phone functions perfectly well again, and you benefit from the other good stuff in 4.0.4.
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
mephissto said:
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
Click to expand...
Click to collapse
i'm having this problem too. but would it be a hardware problem? i don't remember this happening in 4.0.3. you might just be returning it for another phone with the same problem if you update to 4.0.4
It might be a harware problem caused by a some code that was not in Android 4.0.2
I tried CyanogenMod 9 which is on Android 4.0.4 (same bootloader and radio as stock 4.0.4) but AOSP and I had the same issue.
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
I stopped having this problem in 4.0.2 and 4.03, when I updated to 4.0.4.
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
Click to expand...
Click to collapse
then that's called a software problem lol
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
....
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
Click to expand...
Click to collapse
I also have exactly the same errors in logcat.
Sent from Galaxy Nexus
I have raised a bug report with Google
I have raised a bug report with Google.
Unfortunately I cannot post a URL, so you need to go to:
code.google.com/p/android/issues/list and search for issue 28133
It might help if those of you who are experiencing this problem add comments to the post, try and raise its profile with Google somewhat.
@ceejay83 : I know, but only a few devices have this issue, that's why I assume it's also related to hardware.
@memoreks : Thanks for the link, I'll go there to also post a comment.
---------- Post added at 11:17 PM ---------- Previous post was at 11:08 PM ----------
Here is the link to the issue on Google code : http://code.google.com/p/android/issues/detail?id=28133
Please star this issue so Google notice it
I've starred the issue at the link posted, and I'm trying radio UGLC1 from the link below to see if it helps to use a newer radio.
http://forum.xda-developers.com/showthread.php?t=1405345&page=37
I found this thread about radios days ago, where you can find all existing radios, if you want to try others.
http://forum.xda-developers.com/showthread.php?t=1405345
Found your thread on google code. This is what I posted there:
I have a similar issue. My phone doesn't lose signal for good, it just drops and comes back on 5 seconds later and this loop keeps repeating with random times between drops(1 minute intervals most of the time). It started right after updating to 4.0.4. I installed an app to help track when signal drops, I attached and screen of the app. I also tested with AOKP build 28 based on 4.0.3 and the problem was still there. I will test a 4.0.2 build soon.
does it only happen in a weak 3g area? i noticed my phone having signal problems after updating to 4.0.4 too. In the secret menu, *#*#4636*#*# the preferred network type is set and stuck to wcdma preferred and if you are like me and are in a weak 3g area the phone will still prefer a weak 3g to a strong 2g signal. it prefers 3g so much that it will still hold on to it for hours even when the signal is too weak to make or receive calls. With 4.0.2 it was set to gsm/cdma prl which prefers a strong 2g but will switch when there is a strong 3g signal. unfortunately you cannot change this setting in 4.0.4.
i tried ugkl1, ugla4,, xxla2 and now using uglc1. they all had similar signal strength and will hang on to a weak 3g, so i dont think the radio is at fault here. an option for those running aokp is to go into the power saver settings and you can set your phone to go to 2g when the screen is off.
I have been having this issue since 4.0.3 on my GSM Nexus. I have tried multiple radio's and multiple kernels. I was having to change the min cpu to 700mhz. I tried FuGuMod's Kernel and it seems to have fixed my signal issues. I am able to keep the min cpu at 350mhz. If you search the thread he explains what he thought was causing the issue. Once he disabled that feature in the kernel my signal issues went away.
http://forum.xda-developers.com/showthread.php?t=1438417
I think its a mix between software and hardware issues. There is some software setting that the hardware doesnt like. But since this doesnt happen to everyone running a certain kernel and only some people there must have been a bad batch of hardware from samsung.
I think I am going to try a warranty exchange with Samsung.
For me at least, it is occurring in both 2G and 3G areas. I have tested it in both, and also in strong and weak reception areas.
Memoreks
Sent from my Galaxy Nexus using xda premium
Hello recently unlocked and flashed my Galaxy Nexus (purchased from a Telstra Shop).
Android Version: 4.0.3
Baseband Version: I9250TDVKK6
Kernal Version: 3.0.8-franco.Kernal-Milestone3
[email protected] #150
Build Number: aokp_maguro-userdebug 4.0.3 IML74K eng.
roman.20120307.183117 test-keys
Mod Version: aokp_maguro_milestone-4
Basically what has been happening is when I leave the phone sit, it loses all reception and displays "Emergency calls only", unlock it picks up reception straight away. Thought the Radio might have been update with the Rom, however recently found out this isnt the case, radio appears to be stock. Have not tried another Rom as I'm pretty darn happy with my AOKP.
Have been into the test menu and altered the Radio band and preferred network to multiple combinations. Currently set to GSM/CDMA (auto) and Radio band to Automatic and in the past 15 or so minutes haven't encountered the issue.
Rather annoying issue as its the only thing that could possible sway me to going back to a Stock Rom as being able to receive calls and messages all the time is a requirement for me.
Anyone seen something like this happen before.
Thanks in advance.
I am also with telstra and have only seen this once.... I have checked a fair few times because I wanted to make sure I had a bug... Im using milestone 5 though.... Never had a problem with milestone 4...I also have run Franco kernel since purchase... Did u full wipe.. Format system and fix permissions.... Hmmmm
Sent from my Galaxy Nexus using Tapatalk 2
That sounds like the signal loss on sleep thing that was reported by many people on 4.0.4, which is really odd.
If it is due to the same thing (smart reflex power saver thingy stopping too much, which is the limit of my research) then installing Franco M5 kernel or pretty much any new release of one of the gun kernels might fix it as all they all contain the fix for the smart reflex problem.
Thanks for the rapid replies. Work long days so haven't had much of a chance to get it sorted out. Planning on wiping, fixing permissions as stated before then updating to a newer rom (assuming there is one) and a newer mod version.
Will post back with the results.
Cheers, Matt.
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.
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