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?
Hello out there,
since I wiped my phone and updated to the most recent CyanogenMod 7 build (#262), my problem regularly freezes when switching from 3G to 2G mode. The only thing to get the device running again is to remove the battery and reinsert it again. If i'm still in an area or room with only 2G coverage, the phone freezes soon after boot-up.
Help or advice would be greatly appreciated!
Thanks in advance,
toco
My phone:
HTC Desire (GSM)
PVT1 S-OFF
RADIO-5.17.05.23
CyanogenMod 7 20120225-NIGHTLY
Android ver. 2.3.7, kernel 2.6.37.6
What I'd do in this order:
1) stop using nightlies
2) change kernel
3) change radio
There was this guy whose phone froze every time he was in space with low or no 3G coverage, and I think changing kernel from snq's to some other solved it for him.
Sent from my HTC Desire using Tapatalk
Thanks for your quick response!
Ok, I appreciate your advice. If the problem keeps occurring I will switch back to the latest stable.
But, still something strange about it: I had absolutely no problem the first weeks i was using this nightly (262 was since November 2011 the latest nightly until today), the problem started to occur from one day to the other.
I am using the radio version since probably half a year or even more, without any problems.
Also, 262 was reported (cyanogenmod forums, other forums) to be very stable on the Desire, almost no people reported having problems with it. That's why i decided to update to build 262. I for my part am suspecting a software being the cause for the freezes, but i have no clue which one.. I even checked the system logs.
As for the kernel: Call me a noob, but how do i change the kernel? I know how to root devices, flash recoveries and roms, but how can i change the kernel directly?
Greetings,
toco
tocophonic said:
As for the kernel: Call me a noob, but how do i change the kernel? I know how to root devices, flash recoveries and roms, but how can i change the kernel directly?
Click to expand...
Click to collapse
Kernel is flashed the same way as roms are. Make sure you use a correct one, manU 2.1 is probably the most popular of those which will work on cyanogenmod.
Sent from my HTC Desire using Tapatalk
if that doesn't work:
Dialer/
*#*#4636*#*#
phone settings > network type: WCDMA only
Alright, one more thing: If I change the kernel to let's say Manu 2.1 - how can I switch back to the original CM7 kernel again? Just by reinstalling the CM7 ROM?
Thanks!
bortak said:
if that doesn't work:
Dialer/
*#*#4636*#*#
phone settings > network type: WCDMA only
Click to expand...
Click to collapse
Wait, if I set it to WCDMA only I can only access data services when in a 3G covered area, right? Thats not optimal either because i'm regularily visiting my parents on weekends, where only 2G coverage is available. Also in some buildings (esp. cellars) here in the city there is only 2G coverage.
tocophonic said:
Alright, one more thing: If I change the kernel to let's say Manu 2.1 - how can I switch back to the original CM7 kernel again? Just by reinstalling the CM7 ROM?
Thanks!
Wait, if I set it to WCDMA only I can only access data services when in a 3G covered area, right? Thats not optimal either because i'm regularily visiting my parents on weekends, where only 2G coverage is available. Also in some buildings (esp. cellars) here in the city there is only 2G coverage.
Click to expand...
Click to collapse
Yeah, but it can solve the issue, I get it intermittently sometimes too but after a reboot or two its usually fine.
Hi
I have similar problem, freeze mainly occuring when the radio reception is poor...
Tried almost evrything differents ROM, kernels, gparted my SD, full wipe....
For three weeks I have no freeze since i tried bending the slots cards like mentionned here :
http://forum.xda-developers.com/show...6&postcount=96
bertrand13 said:
http://forum.xda-developers.com/show...6&postcount=96
Click to expand...
Click to collapse
I'm afraid your link does not work bertrand I get a 404 there. Can u please repost the link?
bortak said:
Yeah, but it can solve the issue, I get it intermittently sometimes too but after a reboot or two its usually fine.
Click to expand...
Click to collapse
I would have written you a PM but as I'm not yet allowed to (too few xda posts) I have to put the question here: What happens on May 7th (your signature)? Because i'm looking for an adequate successor to my Desire (~3,7" display) as well.
tocophonic said:
I'm afraid your link does not work bertrand I get a 404 there. Can u please repost the link?
Click to expand...
Click to collapse
Sorry about late answer, I bought a Samsung SG2 so i forgot to check here
The right link is
http://forum.xda-developers.com/showpost.php?p=22302386&postcount=96
I have done that one month ago and no a SINGLE freeze
I had about 5 a week before
It was mostly difficult on a train trip.
I am a heavy user of those very fast french train and i suffered of freeze about 3 times per trip (3 hours running 300 kmh)
Since the "bending" of sim an sd card = SOLVED !!
Thanks, that seemed to help! Even if i don't get the logic behind that.. but i don't have to, i just want a working phone
Thanks again mate!
There seems to be a lot of people complaining about desire freeze
I thins this should be tried by those since it fixes freeze for me and for you too !!!
Happy this helps you
I am using an other rom, but had the same issues. Problems gone with new kernel.
Droidzones kernel did it 4 me, but i am on a sense 3.5 rom.
Try with uv and other governors too. But i think its a kerne related problem.
Sent from my rooted Transformer TF101
3G to 2G freeze - solved
Hi,
I had the same issue: on 3G to 2G network change the phone froze. When moved out of 3G coverage, sometimes during/after the call (probably due to 3G-to-2G handover during the call), seconds after forcing the phone to 'GSM only'. I tried different ROMs, different radios, no success. Finally the guilty component was found: microSD card.
I changed from class 10 to class 4 and suddenly the issue disappeared.
The logic behind this is hard to grasp, but I tried two different ROMs now on a slower card and no freezing for couple of days now.
I searched and didnt find anything that seemed to be the same topic.
I updated to 4.0.4, MoDaCo custom lr11 (lMM30B) from the factory ota 4.0.2 because it sucked. Now everything seems to work great but the wifi distance seems to have dropped. In places where my iphone and this phone on .2 had 3 to 4 bars on wifi the .4 now struggles to hold 1 bar. In my room with the router about 8 feet away I get 1 or 2 bars and only get all 4 when its within 2 feet. Any free wifi spot that I have saved and used to use perfectly is pretty much gone now. I wouldn't make a big deal of it but the area I am usually in most of the day is extended for me so I don't have 3 or 4g access.
Anyone know of a fix.
ty in advance
What baseband are you using? Most if not all custom roms exclude the baseband so you will need to update that manually.
Sent from my Galaxy Nexus using Tapatalk
same problem here! my radio signal, too, sucks a lot more compared to when i was on stock.
all started happening after rooting and flashing to aokp.
salivaman said:
same problem here! my radio signal, too, sucks a lot more compared to when i was on stock.
all started happening after rooting and flashing to aokp.
Click to expand...
Click to collapse
You need to change your baseband to a later version. There are issues if you have the old one while running a rom based on 4.0.3 or above.
Sent from my Galaxy Nexus using Tapatalk
yeah i have flashed to the latest one but the problem still persists on my aokp.
strangely i decided to flash a new rom which the bugless beast and so far it's working good.
Sorry, Baseband is
l515.09 V.EK05 / L515.EK02
I see the rom update Ir12 out there so I think I will update to it. I see a change log for a previous patch that addressed the signal stregth. Will post back if any changes. Hopefully will fix it.
salivaman said:
yeah i have flashed to the latest one but the problem still persists on my aokp.
strangely i decided to flash a new rom which the bugless beast and so far it's working good.
Click to expand...
Click to collapse
next time try flashing a different Kernel if your having issues and have tried flashing a different baseband. Faux or trinity seem to be best for me using AOKP
Nothing worked...
Tried several things from roms to just the radios and I couldnt get anything to upgrade. Guess I'll wait until .5 or something.
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
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