yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bobbysixkiller:
i have the same issue, but also my data bars go grey at some points so i have some sort of signal but lose the internet and google services
[Samsung Galaxy Nexus] @rbiter:
The grey is not losing signal. It is just losing Google services, but occasionally I can't get data for a few minutes. It is the carrier side at that point. Most of time I recover data quickly unless it is too congested.

bow chicka wow wow.
[Samsung Galaxy Nexus] bobbysixkiller:
this issue started when i flashed to 404 though
[Samsung Galaxy Nexus] @rbiter:
I only drop data or cell after phone sleeps. Since doing the smart reflex edit everything is back to normal, including whatever happens when I see gray bars.

bow chicka wow wow.
[Samsung Galaxy Nexus] bobbysixkiller:
smart reflext edit?

ok i just followed a guide and have now rooted and unlocked my nexus..

so do i try a work around if so which one or go back to 402?
[Samsung Galaxy Nexus] efrant:
Try this: http://xdaforums.com/showpost.php?p=24545086&postcount=73
[Samsung Galaxy Nexus] Guto ViP:
What i need to do?

EDIT: Tnx Efrant.

---------- Post added at 06:04 PM ---------- Previous post was at 05:17 PM ----------

Test completed, no signal lost... So i dont need use this fix... But sometimes it came across my device with no signal and lost data transmission (3G or WIFI). I even thought about changing the modem...
[Samsung Galaxy Nexus] @rbiter:
Sometimes data loss just happens due to congestion or lack of signal. It coming back on its own is the problem. For those that don't want to run the script you can use terminal emulator and type su and the echo command mentioned above. But you will have to do it again on a reboot.

bow chicka wow wow.
[Samsung Galaxy Nexus] bobbysixkiller:
restored to 402 - cant be arsed any more, hate to say it but the nexus has been a big let down on many fronts... some of you have had no issues and others like myself first had the volume bug for 4 weeks! and now this...

good need to test stuff before they release it!
[Samsung Galaxy Nexus] @rbiter:
Has it been mentioned in this thread... does everyone keeping an eye on this thread have under volts set? Is it conflicting with smart reflex thus conflicting with radio? A couple of people I've talked to do NOT have under volts and don't have radio drops.

bow chicka wow wow.
[Samsung Galaxy Nexus] bobbysixkiller:
ok back on 402 and seem to be stable signal wise... phew!

i seem to have lost root, but remain unlocked bootloader wise, so if i do root again will that wipe the phone?
[Samsung Galaxy Nexus] memoreks:
I can't speak for anyone else, but the problem occurred for me with a brand-new, clean, nothing-else-installed stock ROM downloaded direct from Google.

However both the overclocking of the minimum CPU speed from 350mhz to 700mhz and turning off SmartReflex (which is IMO the current gold standard for sorting the issue) both fixed the issue for me.

I'm eagerly awaiting the results of testing the various SmartReflex parameters to see what's wrong. However I have heard that the SmartReflex parameters did not change from 4.0.2 to 4.0.4, which makes the issue slightly more complex.
[Samsung Galaxy Nexus] Theshawty:
I seemed to have solve the signal drop error by raising the minimum clock to 700 Mhz using No-Frills CPU Control.
[Samsung Galaxy Nexus] memoreks:
No. Only if you lock/unlock the bootloader does it wipe the phone automatically.
[Samsung Galaxy Nexus] Theshawty:
Correct. "Rooting" this phone only installs superuser.apk and some superuser binaries.
[Samsung Galaxy Nexus] bobbysixkiller:
ok how do i go about getting just root access then? as i have unlocked
[Samsung Galaxy Nexus] @rbiter:
Flash superuser image.

bow chicka wow wow.
[Samsung Galaxy Nexus] efrant:
Follow method 1 here.
[Samsung Galaxy Nexus] bobbysixkiller:
thanks will do that now

---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------

thanks all done
[Samsung Galaxy Nexus] jefbuan:
thanks
[Samsung Galaxy Nexus] Devilicus:
I'm on the CDMA Verizon Gnex, and I'm about at my wits end. I just got this phone yesterday and the constant dropping connection in sleep mode is driving me crazy (mostly because I just cancelled my Sprint contract for a similar but unrelated reason, ETF and all, and ironically end up with just as big a problem; but that's neither here nor there)

I can't receive calls or texts unless I'm constantly using the phone. I feel like I've tried every possible solution and none of them have worked. I tried using the radiosaver script, I tried clocking up to 700 mhz, I've tried flashing other radios (currently on one of the hybrid radios from here http://xdaforums.com/showthread.php?t=1469687), and I've tried multiple ROMs and restoring to factory settings using Wug's toolkit. Is there anything else I can try?

EDIT: The one solution that seemed to help the issue a bit was changing from LTE/CDMA to CDMA only. But I can't know for sure yet.
[Samsung Galaxy Nexus] Theshawty:
What worked for me was installing a CPU-app (No-Frills) and raising the minimum overclock from 350-ish Mhz to 700 Mhz. I can finally receive texts and calls while in sleep mode.
[Samsung Galaxy Nexus] Devilicus:
I appreciate the input but sadly I've already tried that :( all it did was kill the battery faster, didn't affect the dropping issue. Is it possible I just have a faulty SIM card or something? At this point I'm considering just returning the phone but for all I know a replacement could have the same issue.
[Samsung Galaxy Nexus] Theshawty:
Hmm.. how long have you had your current sim-card?
[Samsung Galaxy Nexus] Devilicus:
Only 24 hours; it's my first time using Verizon so the SIM is brand new.
[Samsung Galaxy Nexus] bobbysixkiller:
im on 402 and a new sim card and it has most stopped, however every now and then i lose signal, i have set lightflow to beep and flash when the signal goes, im starting to think my phone is faulty
[Samsung Galaxy Nexus] case0:
Yep you were right, it's not too bad. I usually have to charge my phone every night anyway and it still lasts the day. I can live with this for now :)
[Samsung Galaxy Nexus] hongkongtom:
With vro25 fixed not applied, I apparently don't have signal lost problem, however, I found that my data connection would sometimes lost while I could still dial and received calls, anyone experiences this?

Sent from my Galaxy Nexus

IMM76D (JameBond 3.1)

4.0.4

Rooted & CWM

Stock rom
[Samsung Galaxy Nexus] Rodrigo Ark:
Look at this

http://www.htcmania.com/showpost.php?p=4376163&postcount=69

It seems that Google its updating un secret. Look out the version: IMM76I
[Samsung Galaxy Nexus] bobbysixkiller:
that would be nice!
[Samsung Galaxy Nexus] rootusr:
Hi Guys, It's already being discussed here

http://xdaforums.com/showthread.php?t=1606029

but yes.. it's great!
[Samsung Galaxy Nexus] truwire:
I had this problem on my Bell GN. I ended up installing Franco and updated the baseband to LA4 - issue hasn't returned yet.
[Samsung Galaxy Nexus] Theshawty:
I'm about to rip my hair out. No matter what I do, my signal reception is always crap. It doesn't die in idle mode, though, but it's **** all the time.
[Samsung Galaxy Nexus] bobbysixkiller:
i flashed back to 402 and its better
[Samsung Galaxy Nexus] hongkongtom:
since IMM76I is out for fix signal drops, do I need to undo radiosavior.sh before moving on? or how do I disable radiosavior.sh?
[Samsung Galaxy Nexus] vro25:
You can just uninstall Script Manager.
[Samsung Galaxy Nexus] vro25:
You might benefit from a radio switch.
[Samsung Galaxy Nexus] vro25:
Might not be the same issue.. you're the only one on Bell to report the problem and it had nothing to do with radios.
[Samsung Galaxy Nexus] an430:
My gn seems no problem with the network but the wifi.

Once I turn on the screen, it shows no wifi signal. A few second later, the wifi comes again. Anyone?
[Samsung Galaxy Nexus] vro25:
Not at all what this thread is about, but since I'm still up...

You can change that in WiFi settings, hit menu, advanced and then "Keep Wi-Fi on during sleep"-> Always.
[Samsung Galaxy Nexus] hongkongtom:
Thx vro25, I've manually unchecked the su & boot and delete alias in script manager then uninstalled it, seems working well now with IMM76I.

Sent from my Galaxy Nexus

IMM76D (JameBond 3.1)

4.0.4

Rooted & CWM

Stock rom
[Samsung Galaxy Nexus] Theshawty:
Does anyone have an answer as to why my reception is always crap? I have tried all radios for my area and even gone back to as far as 4.0.1, but I still have crappy reception. Grey bars like 99% of the time and at max three bars but that's rare. I have mostly two solid bars.

I don't have a bad phone, do I?
[Samsung Galaxy Nexus] memoreks:
Installed the latest radio...

I have installed the latest build update:

yakju IMM76I from IMM76D: http://android.clients.google.com/p....signed-yakju-IMM76I-from-IMM76D.46cf01d3.zip

You can find install details in this thread:

http://xdaforums.com/showpost.php?p=20843237&postcount=1

I have removed Script Manager to disable the radiosaver.sh script and so far (the past 10 minutes or so) I have had no signal drops at all whilst the phone was was in sleep mode. Just a rock solid connection for all that time. On the previous radio version it would take a few seconds in sleep mode to drop signal.

Fingers crossed, but this appears to be the fix we were looking for. However, Google still haven't updated the issue on the Google Code site:

http://code.google.com/p/android/issues/detail?id=28133

If a few more people try it out and post their results here, I will update the Google Code issue to suggest this as a fix.
[Samsung Galaxy Nexus] an430:
Actually, I have set that already. But my problem is not often to happen, thanks
[Samsung Galaxy Nexus] vro25:
If you want to keep script manager you can just uncheck the boot option and then save.

If you don't need it anymore you can skip all those steps and just uninstall.
[Samsung Galaxy Nexus] Simmo3D:
Well it fixed the issue for me so I'm a happy camper
[Samsung Galaxy Nexus] cmstlist:
On the original yakju 4.0.4 I found the North American 4.0.4 radio UGLC1 to be unstable, and reverted to the North American 4.0.2 radio UGLA4.

After applying the upgrade, I now find the opposite is true. So I suggest using radios that came with 4.0.4 releases once you upgrade.
[Samsung Galaxy Nexus] eezdva:
Worked. Amazing after days of looking.
[Samsung Galaxy Nexus] bobbysixkiller:
the fix fixes nothing for me, still getting grey bars and signal going
[Samsung Galaxy Nexus] case0:
Just to update what I said before, the overclocking didn't help with signal problems after all. It might happen less often though. Still waiting for my rom to be updated to the new build which fixes the problem.
[Samsung Galaxy Nexus] stevexda:
I had a bad SIM card with the same signal loss symptoms. 18 hrs later (fingers crossed) I haven't had any signal drops that weren't attributable to poor coverage. Replacing the SIM is definitely something quick and easy to try.
[Samsung Galaxy Nexus] chubiprince:
I think there is something wrong with the radio or with unit after the update. Before the update, I am always connected to the internet using 'data connection'. I can anytime stop and turn it on every time that I wanted to. But after updating my radio, 'data connection' always stops every time GNex activates the sleep mode. And it is giving me a headache... it is interrupting my downloads.

My GNex is previously a yakjup before switching to yakju. No problems with calls, sms so far. Its just with the data connection. Any ways to solve this without rooting or flashing my phone again?
[Samsung Galaxy Nexus] hp13:
i am sticking with stock rom although i used all the rom out there (AOKP, CM9, eaglesbllod, petes, manhatten) all these roms have a bug but stock doesn't.. i even get no data drop with stock rom and stock kernel 4.0.4
[Samsung Galaxy Nexus] Flukester69:
Yes, good post. It's a known issue in 4.0.4. If you have this problem, this solution he's given you is temporary. Please post here if you have the problems and want it resolved. There are 500+ posts of people with the problem and Google is aware of it and provided the above temp solution. I rather have a full solution than a temp solution, but that's just me.

http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
[Samsung Galaxy Nexus] lucas.scott:
Im on 4.0.4 and I suffer from signal drops probably 7 or 8 times a day . I tried the above steps just to see if it would remedy the issue.......it does not.

Any other ideas? The setcpu route made my phone way too hot.
[Samsung Galaxy Nexus] MagicalSword:
Hi all,

I received the OTA on my free yakjuxw (it had 4.0.2) to IMM76K (4.0.4) and the signal is constantly dropping (and the phone is out of service, can't receive calls) ever since.

This is very annoying and worrisome, all solutions I have read so far involve rooting the phone or doing stuff, but if IMM76I solved this issue, how come it's back in IMM76K?

(3 days using this wonderful phone and already having problems :-(
[Samsung Galaxy Nexus] @rbiter:
I flashed the full .4 image and my signal drops went away. When I manually did the ota the problem improved immensely. I haven't even had a hint of signal drop on jelly bean but I've only been on it a week.

butter and jelly please...
[Samsung Galaxy Nexus] MagicalSword:
I would prefer not risking my warranty (I got this phone on Monday!) by unlocking or risking the phone in any way (Samsung Spain gave me a URL to a virtual customer services web page where I can't even sing in, as the web page won't even load all the form elements; I wouldn't like to add more problems to those).

Is there any way to go back to 4.0.2 without mucking into the bootloader, lock, root and so on? Like a temporary root to use setCPU until 4.0.5 or 4.1 is officially out?

thanks
[Samsung Galaxy Nexus] biscuitownz:
You can re-lock your bootloader. No point in buying a nexus if you're not going to unlock
[Samsung Galaxy Nexus] MagicalSword:
I will unlock it, sure, but ATM I have a brand new phone that, in 3 days, has gone from being a wonder to almost useless, and a 2 years warranty I cannot yet risk to void, as I don't even know if everything works as it should...

And I cannot even register for Samsung Support Services because their website won't let me register! I have tinkered a lot with my HTC ChaCha, but this phone is still a stranger for me (and quite more expensive as well).

Being yakjuxw, will we get the JB OTA soon enough or is this going to be a long wait?
[Samsung Galaxy Nexus] Flukester69:
You can unlock and re-lock your phone without Samsung knowing. You have to back it all up first of course. The only hurdle I ever had was the driver however since then its been great.
[Samsung Galaxy Nexus] MagicalSword:
OK, I was fedup of waiting, so I unlocked, rooted and have the script to turn SmartReflex off, so the bug is solved... :-)

After my HTC ChaCha nightmarish process, this was so sweet it's a bit scary... ^_^

I'm still on stock 4.0.4, though, because I'd like to get the stock JB as soon as it's out, although I guess that may be a while, since yakjuxw is not updated by Google but by Samsung, but anyway...

One question, though, will I get OTAs with the unlocked bootloader or do I have to lock it again?

Thanks for your help and support.
[Samsung Galaxy Nexus] efrant:
No need to re-lock. It makes no difference for OTA updates.
[Samsung Galaxy Nexus] Lord_Phoenix:
But it does for warranty, no?
[Samsung Galaxy Nexus] efrant:
How is anyone going to ever know if you can put your device back to the same state it was when you took it out of the box?
[Samsung Galaxy Nexus] Lord_Phoenix:
Well, it should not be unlocked, right? ;-)
[Samsung Galaxy Nexus] efrant:
You should lock it before sending it in.
[Samsung Galaxy Nexus] The Midnighter:
I had this issue while on 4.0.4 as well, I did not try the CPU clock method.

I now have Jelly bean 4.1, and this does not seem to be an issue anymore!

Whoot ^-^
[Samsung Galaxy Nexus] omid_1985:
:good:

Perfect, may i know which rom you used for flashing to JellyBean? do you have any Link for this ROM?
[Samsung Galaxy Nexus] rob61280:
Likewise I'm running stock rooted 4.1 and the signal problems I was experienced have gone away. I updated to the latest stock ROM including the latest radio and boot loader.

R
[Samsung Galaxy Nexus] smack:
Unfortunately I do seem to have this problem with a OTA 4.1.1 JB version (JRO03C). Actually checking with "No signal alert".

Anybody else experiencing this in JB?
[Samsung Galaxy Nexus] Flukester69:
Yep I get it with custom ROMs. Like this morning woke up and both bars grey. Google NLS off too. Its hugely annoying and nobody seems to care or do anything about it which makes it even more annoying. I have suspicions it is Google or that because people who make kernels f with voltages or WiFi versions and since they don't have problems its assumed we all don't. I just don't know. Hate pointing finger but what else can you do? I'm going to try and log everything on my phone and see if I can figure it out. I suspect too that the problem might not happen for me if I disable WiFi when I go to bed. I will test theory tonight.
[Samsung Galaxy Nexus] smack:
Strange, I am un-rooted and locked. So I suppose it has to do with the OS since under 4.0.4 there seems to have ben a OTA patch for thsi problem. I will try disabling WiFi too. Would not like to start overvolting and such.
[Samsung Galaxy Nexus] Flukester69:
The problem started in 4.0.4 and never fixed.
[Samsung Galaxy Nexus] wyco:
I keep having that one too, even in the CM10 JB prerelases...

---------- Post added at 01:12 PM ---------- Previous post was at 01:12 PM ----------

Setting the min cpu speed to 700mhz sounds like something that would drain the battery in a few hours, doesn't it?
[Samsung Galaxy Nexus] wyco:
Question. On SGS2 (not Galaxy), running the script (radiosaver.sh) says "can't create /sys/kernel/debug/smartreflex/sr_core/autocomp nonexistent directory". I've checked it, and it really doesn't exist. Any thoughts?

Thnx

ps. running Siyah latest.
[Samsung Galaxy Nexus] SENSATION_XE:
i have this problems as well. but i never have signal. there is always either a x-signal-bar or a empty-signal-bar. i cant recieve calls or call someone. this is so annoying, i just got my GNex today. what can i do

am on android4.0.4, XXLA2 baseband and IMM76K build
[Samsung Galaxy Nexus] MARVELMAZ:
I'm not sure how it is while wifi isn't available but you are experiencing signal loss with wifi aswell I would advice using "Wifi Fixer" by Zanshin-g1 once you download this app it will monitor your wifi real time and get rid of any connectivity issues when they are about to strike. I found it to be the perfect app to solve wifi issues. I hope it helps you aswell
[Samsung Galaxy Nexus] viniciusrsouza:
Guys, please sorry me if this was asked before, but I really couldn't find it.

Can this file be used only on Galaxy Nexus or I can try it on my Galaxy Note? I'm using AOKP 4.0.4 here and I'm experiencing exactly the same issue!
[Samsung Galaxy Nexus] GBPackerFanForLife:
Hmmm..
[Samsung Galaxy Nexus] viniciusrsouza:
Perfect description about this issue when you stated about we "can't scan for mobile network carriers and the more disturbing thing is that the APN settings are empty and you can't create new APN settings". This is so annoying! Here even turning Airplane Mode on and off does not solve this problem. Only rebooting.

As I said earlier, I'm using Samsung Galaxy Note and Android Open Kang Project 4.0.4, so this proves it's not a Galaxy Nexus (hardware) related issue, but a 4.0.4 bug!

Should I use the radiosaver.sh script here or I will mess everything up?! I don't want to set my CPU to 700 because I stay almost all day outside, and I don't want to loss battery, although Galaxy Note has a huge battery!
[Samsung Galaxy Nexus] MrSmileyJr:
has this been remedied in 4.2?
[Samsung Galaxy Nexus] icke68746:
Hello vro25,

unfortunately it does not work with my phone. It is the message: No such file or directory.

I have tried it over the skipt or via the terminal. Root privileges are available and have been granted. What can I do?

Thanks and regards from Germany, Mike

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

Hallo vro25,

leider funktioniert es bei meinem Handy nicht. Es kommt die Meldung: No such file or directory.

Ich habe es über das Skipt als auch über das Terminal probiert. Root-Rechte sind vorhanden und wurden erteilt. Was kann ich noch tun?

Danke und Grüße aus Deutschland, Mike
[Samsung Galaxy Nexus] mephissto:
@neotekz : I'm not in a weak 3G signal, and I still have the issue.

Someone on the Google code thread said that the issue disappeared when he flashed uikl3 radio. If someone want to try, as I can't do it myself right now :/
[Samsung Galaxy Nexus] dosmage:
I've been meaning to do more troubleshooting, but I was busy all day yesterday and today. Here's my two cents on the problem. I believe the issue is most definitely not a radio firmware issue because when I flashed to Cyanogenmod I didn't flash a new radio. Cyanogenmod 9 running 4.0.4 exhibited the same issue as the stock 4.0.4 rom. This problem is not signal strength related as the radio doesn't recover, reports that the mobile network is disconnected, and Opensignal Maps doesn't show radio information. It's obviously power management related as the issue occurs only when the phone is put in to standby. Here's where my knowledge of GSM is lacking. During the problem you can't scan for mobile network carriers and the more disturbing thing is that the APN settings are empty and you can't create new APN settings. Therefore I believe that perhaps the SIM card is being powered down in some way. I tried to find a SIM card app in the market, but all I could find was anti theft related apps. I haven't had a chance to figure out a way to test my theory and as I said I am not very GSM savvy.
[Samsung Galaxy Nexus] DaLoona:
I too had this "problem", as soon as it went into stand-by/sleep, I couldn't get incoming calls, no sms, whatsapp or anything else.

Had it on the OTA 4.0.4, which I got from XDA and I flashed by the way, currently on AOKP 29 + Franco r.116.

And as others before me posted, raising the minmum cpu speed from 350MHz to 729MHz did the trick. Standby now works for me.

And if it worked before and still on old 4.0.2 but not on newer versions of ICS I dont think it is a hardware fault, but something screwed up in the code.
[Samsung Galaxy Nexus] fishko:
Same problem here since the update on 4.0.4... Went back to 4.0.2 and the problem was gone... now testing on 4.0.4 cpu min speed 700mhz ... seems everythig fine.
[Samsung Galaxy Nexus] warhummer:
Interesting turn of events

I just flashed Android Revolution's 4.0.4 version and it appears I do not have the signal-drop-while-sleep anymore. The signal bars do occasionally turn grey, but they always had full bars and the "E" moniker (I'm firmly in a T-Mobile Edge-only area). I do have SetCPU installed, but it's not set to change the CPU speed (I think). I'm going to go back an verify in the meantime...my "scientific method" is getting sloppy in my old age.

I let phone sleep and made repeated phone calls at random points throughout the day, as well as text messages and all went through as expected.

If anyone has a similar experience, please let me know.
[Samsung Galaxy Nexus] fishko:
No signal loss anymore with 700 mhz min cpu speed. Yet another issue :) ... 5-10 %/h battery drain in stand by instead of 2-5%/h with cpu on 350 mhz...
[Samsung Galaxy Nexus] DaLoona:
With AOKP 29 and Franco r.116 Im getting ~2 %/h @729MHz in standby.

Edit:

This is not to be biassed by the way, but to show you can improve batterylife by trying different ROM's and kernels, this combno just works great for me :D