yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] memoreks:
I have tried this on my GNexus 4.0.4, and it works great. I can now clock the CPU minimum state back down to 350mhz and still maintain a signal. Once su rights are assigned to the script manager app, "remembered" by the superuser app, then it doesn't require any intervention after set-up, even on a reboot.

It's not the official fix, but at the moment it appears to be the best we have!
[Samsung Galaxy Nexus] vro25:
If you're going 15 minutes without a drop in signal during sleep than I think you're fine. The main test is that you're still getting phone calls and battery life hasn't gone down since upgrading to 4.0.4.

If you check Settngs->Battery->Cell Stanby an it has a lot of "Time without signal" than you may have the problem - or you could just have poor cell coverage ;-)
[Samsung Galaxy Nexus] arhung:
Will there any side effects cause by this method?

thx:)
[Samsung Galaxy Nexus] memoreks:
The only problem with this (and any other method mentioned here) is that you require root permissions to affect the necessary change. However it appears better than the CPU speed increase as it does not reduce battery life. I am noticing better battery life now I have implemented the scripted fix.
[Samsung Galaxy Nexus] rootusr:
Same here, i have no noticed side effeceffects implementing the script fix. Please keep in mind that this is a temporal fix, lets push Google to release a permanet fix.
[Samsung Galaxy Nexus] sblantipodi:
Imho the problem is the root itself. Phones without root does not have this problem.
[Samsung Galaxy Nexus] rootusr:
That is in fact a posibility, when i noticed the problem I tried flashing stock image and not root for a few minutes and I did not notice the signal drop then I root it and after a while it happened again, I would need to test again without for a while.

Are you guys not having the problem are root?
[Samsung Galaxy Nexus] vro25:
Not only is that comment utterly untrue, but your opinion is not based on any testing or research.

If you had done any testing you would quickly realize your theory was unsubstantiated.

If you had read thought the official Google support thread you would have seen the problem was reported by unrooted users who were pushed the update by Google.

Root access does not affect the kernel but simply allows greater permissions - you would know this if you understood how the superuser.apk works. Granted, a root user who is running setCPU or some other non-stock kernel modifications could have issues - but this is not the case here.

I have personally re-imaged my device DOZENS of times trying to resolve the issue - using official factory (4.0.1, 4.0.2, 4.0.4) images and radios and upgrading by "official" and forced means.

Making uninformed comments are not just a waste of everyone's time but insulting to those that invest their own time and effort trying to figure out solutions for everyone's benefit.
[Samsung Galaxy Nexus] efrant:
@vro25

I tried your little test, and it doesn't seem like I have the issue. I'm running 4.0.4 which I update from 4.0.2 with CWM using the update URL.

Edit: I tried it again with the NoSignalAlert app, and it does not seem to do what yours is doing. However, when I rebooted, but before the screen went off, the app gave me two alerts, one immediately after the other. Loss of signal followed by signal. Not sure if that was just the app starting up for the first time, but that was it. No loss of signal.
[Samsung Galaxy Nexus] DynamicRam:
for me this only occurs in areas with weak signal
[Samsung Galaxy Nexus] rootusr:
That is normal, no signal alert reports a drop just a moment before reboot and after reboot followed by the recovery alert.. The problem should appear after that is there are for you.

Regards
[Samsung Galaxy Nexus] efrant:
Then I do not have the issue.

And, btw, I am rooted... ;)
[Samsung Galaxy Nexus] vro25:
Efrant, where did you get your phone - from Rogers or did you import it?
[Samsung Galaxy Nexus] efrant:
Bought it from Virgin Mobile here in Canada.
[Samsung Galaxy Nexus] memoreks:
Yes they do. Mine was not rooted at all when I went to 4.0.4, and it occurred then. The only reason I rooted it was to attempt a kludge suggested at the start of this thread. If you look at the Google Code issue entry, you'll see hundreds of people have this problem with no root.
[Samsung Galaxy Nexus] vro25:
So you're Nexus was from the original batch (Bell & Virgin got it first).

Is anyone who bought at the end of last year from Bell/Virgin having the issue?

Under my battery it says my model is GT-I9250M - but I think that's standard. To the right of the serial number I have an "11.12".
[Samsung Galaxy Nexus] efrant:
Yeah, I bought mine the first day it was available for sale on QC. Dec 8th I think.
[Samsung Galaxy Nexus] cbkitt:
Same here. Problem went away!
[Samsung Galaxy Nexus] rootusr:
So you flashed that radio and the problema went away? If that is the case please wait for an hour or more, it happened to me and then the problem returned

Regards
[Samsung Galaxy Nexus] tacz:
Hi guys,

So I have result after long testing but I am not sure if it is accurate as I was awake only 1 hour during that testing.

The configuration is as following: I use lightflow to notify signal loss (all other notification were turned off to not mess up the notification lights), keep wifi on during sleep only when plugged in, mobile data on, e-mail sync for corporate account on, google account sync on, facebook contacts sync on. The phone is freshly restarted for testing so no other application is running on the background. Battery level at time starting the test 51%.

I waited aprrox. 1 hour but no signal loss notification at all so I tried to call my phone and no problem. So I went sleep at approx. 12am, get up at 8am and first thing is to ring my phone and also no problem. I also notified that the phone really went to Idle mode as the battery level at 8am is 46%. Battery usage as following: phone Idle is 18%, cell standby 10% from which time on 1d 6h, time without signal 0%.

That was the test with normal usage behavior. Today I will try to turn off all syncs, mobile data, and wifi to see if the problem will occur.

My phone is on stock yakju IMM76D, baseband I9250XXLA2, rooted.
[Samsung Galaxy Nexus] vro25:
Your battery life is good and, most importantly, you have 0% time without signal. Congratulations, you don't have the problem :-)

When did you buy your phone?
[Samsung Galaxy Nexus] twitchcity:
Is it possible the radiosaver.sh fix would work on a Motorola Milestone as well? This phone drops the signal whenever it is left unattended for a few minutes.
[Samsung Galaxy Nexus] vro25:
Is it a stock milestone? It shouldn't have the same issue, but it wouldn't hurt to try it. You can just remove it if it doesn't work.
[Samsung Galaxy Nexus] benrees21:
I have run the radiosaver script and still get the same problem. Very annoying.
[Samsung Galaxy Nexus] vro25:
Is your problem exactly as described here?

If so, more than likely the script wasn't setup correctly. Open the Script Manager app, click on the script and then hit the "Run" button on the top left, take a screenshot of the output and post it here. Most likely problem is that it didn't run as root.
[Samsung Galaxy Nexus] twitchcity:
It is a rooted Milestone, running CyanogenMod-7.1.0-11.10.05-Milestone.

I'm going to try just upping the minimum CPU frequency for now, and if that doesn't work, I'll try the radiosaver script.
[Samsung Galaxy Nexus] benrees21:
http://t.co/M8SS6YHD

Sent from my Galaxy Nexus, running Slim ICS and the ever so beastly Trinity kernel.
[Samsung Galaxy Nexus] msedek:
+ 1 :D
[Samsung Galaxy Nexus] vro25:
That looks good. Are you running No Signal Alert? Does it beep as soon as you power off the screen?
[Samsung Galaxy Nexus] tacz:
My purpose is just to report config of my phone which seems likely not being affected by the problem so that you guys may realize where is the problem (the batch, carrier, country, or something else...)

My phone is from "Made in Korea by Samsung" batch for french carrier SFR.
[Samsung Galaxy Nexus] msedek:
I had some other problems with my radio, it was like all ****ed up, to change from wifi to Carrier was a pain in the ass, took about 10 mins ti get signal, i changed from xxkk6 to xxkl1 and with the setcpu fix i got no signal drops and seems like now i can switch from wifi to Carrier normaly :o

Its not like im glad having my freq in 700 mghz but theres not other option than waiting for the official fix, im not trying the scrip since the setcpu fix works for me and also i paid for the App :banghead:
[Samsung Galaxy Nexus] benrees21:
It takes a few minutes sometimes and other times about 20~30 seconds before I lose signal. I have lightflow activated for no signal.

Sent from my Galaxy Nexus, running Slim ICS and the ever so beastly Trinity kernel.
[Samsung Galaxy Nexus] vro25:
No reason you can't use both. SetCPU is good to have to conserve battery. You could use the radiosaver script to fix the issue and use SetCPU to further improve your battery by lowering the clock speed.
[Samsung Galaxy Nexus] vro25:
So far you're the only person reporting the kernel setting fix doesn't work. Likely it's related to your ROM/kernel combination.

The only way to know for sure is for you to re-image from factory yakju 4.0.4.
[Samsung Galaxy Nexus] benrees21:
I'm not gonna mess about any more I will just wait for the official fix. Thanks for your help.

Sent from my Galaxy Nexus, running Slim ICS and the ever so beastly Trinity kernel.
[Samsung Galaxy Nexus] vro25:
The official fix will likely be a patch that does the same thing as the script.

Anyway, you're running a custom ROM and kernel - you're not going to be getting the official fix :-)
[Samsung Galaxy Nexus] benrees21:
But once the ROM gets updated to 4.0.5 then it's fixed. Hope it ain't to long.

Sent from my Galaxy Nexus, running Slim ICS and the ever so beastly Trinity kernel.
[Samsung Galaxy Nexus] vro25:
Yeah, but if you have the same issue everyone else has then the script should have worked. Does the SetCPU fix work for you?
[Samsung Galaxy Nexus] benrees21:
Yes it does. Set at 691Mhz.

Sent from my Galaxy Nexus, running Slim ICS and the ever so beastly Trinity kernel.
[Samsung Galaxy Nexus] vro25:
Then I think the auto voltage disable command isn't working on your kernel.
[Samsung Galaxy Nexus] vro25:
Hmmm.... I've just upgraded another Bell Nexus to 4.0.4 and it also works fine.
[Samsung Galaxy Nexus] rootusr:
vro25

I have just documented an spanish version and your fix for our mexican android users community mexdroid, can you share your twitter ID (if any) to link it in the post for give you the credits of the workaround?

So far the readiosaver script is working fine for me, I have also found 2 users in our community that are not having that problem, one with root and other unrooted, both with stock 4.0.4. Gnex in mexico was relased about 3 weeks ago, so they and I have the same HW version (in theory). I'm asking people in mexdroid to report the issue to google too.

Thanks
[Samsung Galaxy Nexus] E15i:
Maybe you have something here..but on lower OTA there was no signal problems, not that I remember. maybe they didn't test it enough, just wanted to make it work with that Car/Desktop dock, we all know that NEXUS are made mostly for developers, and bugs like that can happen, but on other hand, some users do report problems, some not, and there no any pattern in that problem.
[Samsung Galaxy Nexus] vro25:
Rootusr,

No need for credit - the info came from nicholasbgr's earlier post - I just found an app to get it to run at boot ;-)

Just point them back to this thread if they want to follow along...
[Samsung Galaxy Nexus] hystrix0:
Vro25, I like your line of troubleshooting to consider if there is a hardware difference between those who are having the problem and those who are not. Clearly the problem is triggered by software (4.0.4), but perhaps it is exposing a hardware variance. Maybe that is why some who submitted debug data on android #28133 received an email from Google asking if they could share the details with Samsung.

Mine is a White Galaxy Nexus (yakjuxw) purchased on leap day from dailysteals. The manual I think was in Polish...

I had zero problems with signal on 4.0.2 with the Samsung updated build.

After switching to factory 4.0.4 (yakju) I noticed a signal/battery/sleep issue. I tried flashing different radios (including the one that was working perfectly on 4.0.2) to no avail.

Happy at least there is a reason, and that I am not alone.

I have not seen it asked, but has anyone done a

cat /sys/kernel/debug/smartreflex/sr_core/autocomp

on the factory 4.0.2 build to see if this feature was enabled/present before?

-- signed someone who thought he was buying a Nexus to have a working android phone without having to scour xda (at least from the start) ;) But glad the community is here to save the day yet again.
[Samsung Galaxy Nexus] vro25:
I'm annoyed at myself for not thinking of that when I was on 4.0.2 or before I upgraded my friend's phone yesterday... I think earlier on in this thread they were saying that setting that value to 0 resolved the issue - but you're right - they never said if it was changed from previous versions.

I'm backing up my phone right now so I can re-image it on 4.0.2 and check. If there's anyone currently on 4.0.2 that can check, it would save me some time ;-)

---------- Post added at 10:54 PM ---------- Previous post was at 10:10 PM ----------

So this is interesting, in factory yakju 4.0.2 the setting is the same as in 4.0.4:

/sys/kernel/debug/smartreflex/sr_core/autocomp=1

So the value of the setting did NOT change, something else changed that had a negative impact on our phones...
[Samsung Galaxy Nexus] hystrix0:
vro25, thank you for checking. Very interesting indeed.

Because I did (just now) confirm that the setting does indeed prevent the problem from occurring on my device.

Maybe others can help us confirm or rule out specific hardware manufacturing runs or other variables.

Those of you who are exhibiting the radio signal sleep issue with the yakju 4.0.4 factory image, please post your device and carrier information:

original product id: {yakjuxw, yakju, etc}

Build Date from SN: [C2] {2012, Feb}

To find look at SN: behind your battery (see xda post 1519606)

Read the 4th and 5th char from left:

The 4th one defines the Year (Z - 2010, B - 2011, C - 2012)

The 5th one defines the Month (1...9 - January...September, A - October, B - November, C - December)​

Manufacturer/Country: {Made by Samsung} (some have "Made in [country] for Samsung")

Carrier of Operation: {T-Mobile, AT&T, etc.}

My Device Info

original product id: yakjuxw (white)

Build Date from SN: C2 (2012, Feb)

Manufacturer/Country: Made by Samsung

Carrier of Operation: T-Mobile
[Samsung Galaxy Nexus] vro25:
I restored my phone to factory 4.0.4 (from 4.0.2) and then restored my CWM backup. My script stopped running because it was on /sdcard and was wipe during the re-image and was not backed up by CWM.

Since the restore I have not had the issue, and my script is not running. I checked /sys/kernel/debug/smartreflex/sr_core/autocomp and it is set to 1.

I have no idea what is going on...

**Update**

Ok, I still have the issue. My phone was connected to my laptop the first two times I rebooted (using adb). Even after I unplugged it did not exhibit the issue. Once I rebooted without it plugged in (at boot) it had the issue right away. I didn't test for an extended period, but it seems if you boot with the phone connected to a laptop it does offer some protection against the issue.

*******

Anyway, I found a slight difference between 4.0.2 and 4.0.4:

4.0.2

/sys/kernel/debug/smartreflex/sr_core/errminlimit=0x000000f4

4.0.4

/sys/kernel/debug/smartreflex/sr_core/errminlimit=0x000000f9

Even as root I am unable to change those values.

I'm too tired to explore any further, someone feel free to figure it out overnight ;-)

---------- Post added at 12:19 AM ---------- Previous post was at 12:10 AM ----------

My Device Info

original product id: yakjuux

Build Date from SN: BC (2011, Dec)

Manufacturer/Country: Made in China

Carrier of Operation: Purchased from Telus[/QUOTE]

I wonder if the batteries are different?

Side A

NFC

3.7V/6.48Wh

GB/T18287-2000

Made in Korea/Finished in China

Side B

EB-L1F2HVU 1750mAh

SN: NA1BC227S/4-B

2011.12.22
[Samsung Galaxy Nexus] floomat:
My Device Info

original product id: maybe yakju ?? (don't really know where to find this information)

Build Date from SN: C2 (2012, Feb)

Manufacturer/Country: Mady by Samsung

Carrier of Operation: Purshased from T-Mobile Germany

I have a different problem, my phone normally does not lose signal when it's idle. but it does when i put it in my pocket for a few seconds. which really is annoying...

I'm running a Xoom with the "same" SIM-Card(Multi-Sim), this sometimes has the bad effect that my Xoom catches up some phone calls (it even can't be used as phone...).
[Samsung Galaxy Nexus] memoreks:
So, as you may already know, my GNexus exhibits the aforementioned radio problem.

My device info is:

original product id: yakju

Build Date from SN: BC (2011, Dec)

Manufacturer/Country: Made by Samsung

Carrier of Operation: Purchased from Vodafone UK and used on Vodafone UK

Baseband: I9250XXLA2

Build No. IMM76D
[Samsung Galaxy Nexus] bobbysixkiller:
have google said anything about this? surely a simple fix if it worked in 402 - grrrrrrrrrrrr im missing calls i NEED !
[Samsung Galaxy Nexus] SnowmanAndy:
I'm NOT getting this issue at all, nice solid signal for me. Added for reference. Let me know if this post will clutter but thought it would be useful to have the details of a working example.

Upgraded to 4.0.4 using CWM from 4.0.2 using the update URL - Bootloader unlocked, Rooted.

My device Info

Original product id: YAKJU

Build Date from SN: BB (2011, Nov)

Manufacturer/Country: MADE IN KOREA BY SAMSUNG

Carrier of Operation: Purchased from O2 UK on UK release date and used on O2.

Baseband: I9250XXLA2

Build No: IMM76D

Battery

Side A

NFC

3.7V/6.48Wh

GB/T18287-2000

Made in Korea

Side B

EB-L1F2HVU 1750mAh

SN: NA1BB08DS/4-B

2011.11.08
[Samsung Galaxy Nexus] bobbysixkiller:
ok so i have 2 batteries and it only does this with the newer one... is this just pure randomness ?
[Samsung Galaxy Nexus] SnowmanAndy:
Its sounds unlikely to be down to battery IMO, but that's not fact. I posted details of mine for completeness.

Post the details of your phone and batteries as above if you're having the issue.
[Samsung Galaxy Nexus] efrant:
I do NOT have the issue, but in case this helps anyone, here is some of my info:

Model: GT-i9250M

IC: 649E-GTi9250M

FCC ID: A3LGTI9250M

Made in Korea

S/N: ###BB###### 11.11

Original build: yakjuux ITL41D

Purchased from: Virgin Mobile Canada

Purchase date: 08 Dec 2011

Current carrier: Rogers Wireless

Current build: flashed to yakju ICL53F and manually updated to IMM76D when it came out.

Current radio: XXLA2

Current kernel: stock IMM76D

Current battery: 2000mah OEM Samsung

Bootloader unlocked.

Rooted.
[Samsung Galaxy Nexus] bobbysixkiller:
will post my specs later, odd that it only does it with my new battery so far.
[Samsung Galaxy Nexus] vro25:
I'm currently leaning toward battery as the hardware of the two Nexus I had over the weekend (one working, one not) seems to be the same judging by the serial numbers/manufacture origin/dates on the phone.

Just waiting on information about the other battery...

**UPDATE**

The battery in the WORKING phone almost the same:

Made in Korea

SN: NA1BC03DF/4-B

2011.12.03

Note, the battery above was manufactured in Korea - no mention of "Assembled in China".

The real test will be to swap batteries and see if there is a difference - not sure when I'm going to have a chance to do that.

Efrant, do you have more details on your battery?
[Samsung Galaxy Nexus] efrant:
Side A

NFC

3.7V/7.40Wh

B053H001-1006

NA21211

Made in Korea

Side B

NFC

EB-L1F2KVK 2000mAh

SN: NA1BC12NV/4-B
[Samsung Galaxy Nexus] bobbysixkiller:
OK SO TESTING PROVES FOR ME I ONLY HAVE THE ISSUE WITH ONE OF MY TWO OFFICIAL BATTERERS

battery with the issue for me

EBL1F2HVU 1750/MAH

S/N NA1C1026S/4-B

02/01/2012

made in Korea finished in China

------------

WORKING BATTERY

EB-L1F2HVU 1750MAH

S/N NA1BB09DS/4-B

09/11/2012

MADE IN KOREA (JUST KOREA)
[Samsung Galaxy Nexus] vro25:
I'm starting to see a pattern...

**Update**

I was just at a Bell store and as a test I swapped out my battery for one of their replacement batteries.

This battery was "Made in Korea" but had a manufacture date of March 2012. The other data looked the same.

It did not resolve the issue

I still need to test with the older battery from the working phone.

******
[Samsung Galaxy Nexus] bobbysixkiller:
would u f'ing believe it.... scratch that its doing it again on the other battery, that's that theory out the water
[Samsung Galaxy Nexus] andQlimax:
my battery is the same as ur "not working battery", made in korea and finished in china (2012.02.05).. and i don't have signal lost issue

but mine was bought on a tuesday, maybe this make the difference :p
[Samsung Galaxy Nexus] @rbiter:
I've had the issue on 4.0.2. I am still having the issue with .4. I do need to flash my radio tonight from xxla2 to ugla4. I am using set CPU 700/700 temp fix for now. Problem seems to happen when signal is lost for long periods of time which happens frequently where I work. Rarely happens at home or even at my folks house. I don't get great signal at my parents but where I work I can lose signal for hours at a time.

---------++++---------

iPhone. helping computer illiteracy become popular since 2007.
[Samsung Galaxy Nexus] vro25:
You're not experiencing the same issue. I think you just have bad cellular coverage.
[Samsung Galaxy Nexus] bobbysixkiller:
so have google responded to this issue?
[Samsung Galaxy Nexus] we3monks:
hmmm

so I had this problem, and the phone would lose signal every time I turned off the screen. I flashed back to 4.0.2 and used the 4.0.2 - 4.0.4 update patch (not full wipe) and so far even with exact same apps running and everything. No signal loss notifications.
[Samsung Galaxy Nexus] knudsen81:
My phone is stock 4.0.4 and i have signal lost then screen is off
[Samsung Galaxy Nexus] memoreks:
Only to ask for more information from those of us experiencing the problem. There's been no official or unofficial update on the status of the bug.

I think the fact that it only occurs on a subset of GNexus phones means it's not a complete PR nightmare, and thus doesn't have as high a priority as one would like :(
[Samsung Galaxy Nexus] @rbiter:
I have the issue. What I meant when I lose signal for hours at a time is working in an elevator hoist way or underground and then coming back up to a known good spot and I can't get back on data unless airport mode or reboot.

---------++++---------

iPhone. helping computer illiteracy become popular since 2007.
[Samsung Galaxy Nexus] Melhouse:
I don't think you have the issue. This issue is regarding loosing signal when screen is off and the CPU is in deep sleep.
[Samsung Galaxy Nexus] @rbiter:
I usually use wrenches and screwdrivers to work on elevators. Not my phone. :rolleyes:

---------++++---------

iPhone. helping computer illiteracy become popular since 2007.
[Samsung Galaxy Nexus] Melhouse:
Lol! nice catch :)
[Samsung Galaxy Nexus] vro25:
I upgraded from 4.0.2 multiple times as well as flashed factory 4.0.4. It doesn't matter how I get to 4.0.4, once there I have the issue. That seems to be the consensus here as well.

Sometimes the issue doesn't seem to get triggered right away if your phone was plugged in at boot. I have always gotten it to repeat by following the instructions I posted back on post #78.

Most important is to make sure it is not plugged in at boot.
[Samsung Galaxy Nexus] tabii:
I have this issue too but got it fixed by flashing faux123 kernel. Smarflex is off by default but battery is amazing. Latest AOKP rom has faux123 14m kernel preinstalled, so I wouls suggest people with this issue to flash either the kernel or rom to get it over with.