yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] josteink:
Consider this a wild guess, but it sounds like you have some really sub-optimal NTP servers setup in /etc/gps.conf.

Default is some north american ones. You could consider changing to more local NTP servers. I recall a market-app called "Fasterfix" could do this for you on the SGS1 but last I checked it doesn't work on the Galaxy Nexus.

Personally I recommend asking in Q&A about what tricks people have for improving GPS, but a better NTP-server is one of those things which can do wonders.
[Samsung Galaxy Nexus] rolear8:
Thank you, i will try to find something.

Very good post by the way.

---------- Post added at 12:27 PM ---------- Previous post was at 12:08 PM ----------

I checked and i have this in my gps.conf:

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

SUPL_HOST=supl.google.com

SUPL_PORT=7276
[Samsung Galaxy Nexus] josteink:
Thanks.

I say make a thread about it somewhere. Preferably Q&A. We might all learn something.

I guess a quick test would be to try to ping that NTP-server via the phones console or the phones shell via adb, when its not on wifi. If you get 100ms or more, it will probably make it hard to get an accurate lock.
[Samsung Galaxy Nexus] rolear8:
Got it i will create the topic. Thanks again.
[Samsung Galaxy Nexus] philipseth:
I am using XXKK6 and have not had any issue. everything works like a charm..
[Samsung Galaxy Nexus] rolear8:
Could you be so kind to post what do you have in your gps.conf under /system/etc please?
[Samsung Galaxy Nexus] spectre85:
I'm running XXKK6 and below is my GPS

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

SUPL_HOST=supl.google.com

SUPL_PORT=7276
[Samsung Galaxy Nexus] rolear8:
Thank you very much, i have used the same seeting in your gps.conf but same issue, maybe is a hardware problem...

I will investigate this further.

EDIT: Im not sure if there should be some spaces in the code under gps.conf becuase i used FasterFix app and then looked at the gps file and was the same just with the difference of a space between the server and the SUPL HOST adn SUPL PORT.... seems that now is working.. but it takes some time the first time, then not that much (using GPS Test and GPS status and google maps for testing)

I will keep testing.
[Samsung Galaxy Nexus] philipseth:
I just tried XXKL1 and it seems to be buggy. phone already has frozen...
[Samsung Galaxy Nexus] philipseth:
I will post more details about setting on morning
[Samsung Galaxy Nexus] Timmyfoxeh:
Just flashed UGLC1 and I'm having very good initial results, however I'll use it for a few days before I can make an actual judgement.
[Samsung Galaxy Nexus] pcphobic:
I am on Digi and when I tried XXLA2, I noticed in my battery usage history chart, there were a lot of period where there was no signal.

So I reverted to UGLA4.

Will test UGLC1 tomorrow
[Samsung Galaxy Nexus] kobik77:
Is it recommended to update to bootloader?

how big is its impact if there is at all on the GNEX?

Back at my days with the SGS and CM7, Gingerbread's bootloader brought us a great impact on the battery life.
[Samsung Galaxy Nexus] jeetS:
UGLC1 working great so far
[Samsung Galaxy Nexus] cmstlist:
I am not aware of any functional difference between the various GN bootloaders.
[Samsung Galaxy Nexus] rashidi_zin:
I'm on DiGi too. Had some bad experience with XXLA2 but not as much as UGLC1. However I notice when I'm in Petaling Jaya area the coverage is pretty bad.
[Samsung Galaxy Nexus] Timmyfoxeh:
Been about a day now with UGLC1.

So far my signal has been stable and overall good, better than I can say about my about a week long experience with XXLA1. I haven't given UGLA4 a try, but both XXKK4 and XXKL1 worked good for me, though speed isn't that much of a factor for me unless it's clearly noticeable (like I don't do any real intense speed tests as network signal and coverage can change drastically within a matter or seconds/minutes as well as depending on area and time of the day. I do however do some initial speed tests just to try it out after flashing a new radio). But either way, I haven't noticed any big lag or downtime with sending messages over IM clients, where with XXLA1 it could take up to 5-6 seconds with a few messages before they were reported as sent, this can however also have potentially been influenced by the person on the other end as I'm not sure if my IM clients report messages from when they successfully have been sent or if it also has to be received by the person on the other end before it's marked as sent.

Either way, after after just a days use I think this might be about on par with XXKK4 and XXKL1 for me in terms of visible performance.

I'm located in Europe, more specifically Norrköping, Sweden (south eastern-ish part of Sweden) and is on the Telenor carrier.

I'm also running AOKP b29 with Franco.Kernel r116/r121
[Samsung Galaxy Nexus] ellesshoo:
Can you or someone else reverify the fastboot img MD5? I've downloaded it twice resulting in MD5: 244326e506717a904da401428c4cc150

EDIT: Never mind, I didn't realize the MD5 posted was for the img inside the zip and not the zip itself
[Samsung Galaxy Nexus] efrant:
As I had mentioned in an earlier post, fastboot will NOT flash a corrupt radio image, so there is no real need to worry about MD5 for the fastboot image.
[Samsung Galaxy Nexus] pcphobic:
Bro, that's the thing with Digi... Due to their on-going upgrading work, there will be network disruption on and off.

My problem now is...how do I know if my network stability issue is caused by the radio or by Digi's upgrading exercise?
[Samsung Galaxy Nexus] pcphobic:
I have experienced intermittent disconnection with UGLC1 so today I am reverting back to UGLA4
[Samsung Galaxy Nexus] maniac2403:
Guys,

I am currently in India for a business trip and the cell reception just sucks anywhere I travel. Does anyone recommend a radio which works well in India with Vodafone (Mumbai, Delhi)?
[Samsung Galaxy Nexus] motopig:
I have UGLC1 and I can make but not receive calls. Data connection is fine. I have another issue so I can still try factory reset. If that doesn't help I am also reverting to UGLA4. All I can read here says to me XXLA2 isn't any better.
[Samsung Galaxy Nexus] aa_chow:
I have tried both UGLC1 and XXLA2. They are about the same on Mobilicity in Toronto. I have tested them both in Markham and downtown Toronto. No problem with calls or anything. I have yet to test if roaming works correctly.

I have noticed the following. With the Nexus S, the i9020T (T-mobile/Mobilicity/Wind AWS version) came with XX*** basebands, while the i9020a (ATT/Rogers/Telus/Bell) has the UC*** basebands.

With Galaxy Nexus, UG*** basebands are supposed to be "optimized" for North America. I wonder if the optimization is for ATT/Rogers/Telus/Bell frequencies? On the other hand, does that mean XX*** is for AWS band?
[Samsung Galaxy Nexus] efrant:
Don't think so. There are some Fido and Wind users (maybe others as well) that seem to be having issues with non-UG radios, related to roaming and other issues.
[Samsung Galaxy Nexus] nikulogical:
Nope. Since its pentaband it shouldn't matter in theory but the UG ones do fix regional bugs.
[Samsung Galaxy Nexus] SurlyDuff:
Hmm I remember people mentioning roaming bugs with UGKK7 for Wind users, but I haven't seen anything regarding XXLA2 or any of the other XX radios. I also personally haven't noticed anything with XXLA2, but I've also stayed well within the Wind Home zone since updating to 4.0.4.
[Samsung Galaxy Nexus] :
I was just in India at the beginning of March, and the service in general just sucked everywhere. I was using Airtel network on the UGKL1 baseband. I stayed in mostly Southern India, so YMMV.
[Samsung Galaxy Nexus] efrant:
I think you're right about Wind. It was Fido users that were having a roaming bug with the XX radios.
[Samsung Galaxy Nexus] svtfmook:
what is the general opinion on which radio for AT&T in NE US?
[Samsung Galaxy Nexus] :
I'm using UGKL1 here in California, but I honestly don't think there is much difference between the radios for AT&T. It's more dependent on your towers than on the radio.

In fact, I think the only reason I'm still with AT&T is because its GSM and because I have a grandfathered plan. If I ever lost it, I'd jump to Verizon (T-Mobile sucks in my city).
[Samsung Galaxy Nexus] maniac2403:
Yea, same here. Luckily I will be back in Canada soon. I guess since the phone hasn't been launched in India, optimized radios don't exist yet.
[Samsung Galaxy Nexus] Wolfglance:
Very true efrant, I am a Fido user and had the roaming bug with the XXLA2 radio.

It was showing R (roaming) all the time eventhough the roaming was disabled from the settings. I changed to UGLA4 as you suggested and everything went back to normal.

Not sure but it can be my very very old prepaid sim card the reason, again not sure !
[Samsung Galaxy Nexus] scott8281:
I'm using UGKL1 in Kentucky with At&t and its working fine for me. I'm running CyanogenMod nightly 4/4/12
[Samsung Galaxy Nexus] ArmanUV:
no roaming problem with fido here.

I have data drops after 4.0.4 though. Google is on a bad roll with ics updates.
[Samsung Galaxy Nexus] returnzer0:
@codebutler was saying that Google could have caught this bug before official release if they seeded betas to developers like Apple does with iOS. I would love to see that happen lol
[Samsung Galaxy Nexus] ArmanUV:
I totally agree. It seems like QC is nonexistant at google right now. Google is supposed to be more open than apple for god's sake.

This is my first android phone and every new update has major bugs. This time it's data, 4.0.2 had nfc, multitouch and market issues, etc.

I don't want to sound all negative but I'm starting to lose my confidence in Google. (This is partly because I started using Google Music and I'm having serious distortion issues.)
[Samsung Galaxy Nexus] jankonz:
:mad::p;) i´m not a galaxy nexus:D:D:D:D:D
[Samsung Galaxy Nexus] DanSheps:
I just wanted to chime in here and say that I am using the UGLA4 baseband on MTS(Also known as MTS Allstream) here in Canada. The phone originally had UGKL1, I have this far experienced better signal when browsing but I have not had a chance to make any calls.

I believe Rogers and MTS share a network so this baseband should(YMMV) work with Rogers as well.
[Samsung Galaxy Nexus] superlutin:
"new" phone!

Got XXKL2 installed today and went from zero connection to 3 bars out of 4. Yes, I'm staying far out in nowhere...
[Samsung Galaxy Nexus] caysman:
I posted my bug report here https://code.google.com/p/android/issues/detail?id=28474&thanks=28474&ts=1333955192

Signal lost irrecoverably when Galaxy Nexus is in Standby/idle, and unable to re-connect data, phone signal bars jammed and misleading - Android 4.0.2 and 4.0.4

Reported by michaelt...@gmail.com, Today (3 minutes ago)

Phone: Samsung Galaxy Nexus

Version: GSM

OS: Android 4.0.4

Build: IMM76D

Baseband: I9250XXLA2

Kernel: 3.0.8-g034fec9

android-build@vpbs1 #1

SMP PREEMPT tue Mar 13 15:46:20 PDT 2012

(previous was a YAKJUXW phone from Singapore's SINGTEL)

When phone is left untouched overnight, data connected via WIFI, both WIFI and GSM indicators will show blue and everything seems normal.

When move out of WIFI range, the GSM strength bars will not change at all, like it's jammed. It will also not be able to form a G, 3G or H data connection at all.

When the phone is in this condition (ie. jammed signal bars, out of wifi range):

1) GSM Signal Monitoring test will show cell stations strength changing as per normal but cell strength bars on the Galaxy Nexus does not change at all.

2) Any telephone calling in to the Galaxy Nexus will get a `out of service' message.

3) SMS sent to this phone will not be received.

4) If you initiate a call with this phone, it will take more than 10 seconds to hear the first ringtone (usually 3-4 seconds). However, once you hear the first ringtone, the G sign will appear signifying resumption of data connection. Once this is done, the phone is properly reconnected and will receive voice, SMS and data properly.

5) If you put the phone to AIRPLANE MODE, then deactivate AIRPLANE MODE, GSM and data will reconnect properly, and everything will be fine.

Steps to reproduce the problem.

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

Leave phone untouched overnight.

Notes:

a) Behaviour remained unchanged from 4.0.2 to 4.0.4 - all unrooted stock phones.

b) This issue differs from issue 28133 because issue 28133 does not happen to me at all.

c) This behaviour happens both when roaming and in the home network.
[Samsung Galaxy Nexus] josteink:
I see there's been some action here while I was away ;)

I've added UGLC1 radio and MD5sums to OPs. Anything else I should be aware of or include? :)
[Samsung Galaxy Nexus] speehush:
I just flashed UGLA4 via CWM. Its working fine so far in Saudi Arabia ..

Running 4.0.4 .

As per the radio index listed in the initial post , the Saudi radio should be JP---- , but I did not find this radio anywhere ... can you please help ?
[Samsung Galaxy Nexus] efrant:
Welcome back! :)

I think the UGLC1 radio is the only new development.

P.S. It is UGLC1, and not UILC1... ;) You have it correct in the OPs.
[Samsung Galaxy Nexus] josteink:
Thanks. Edited. Working with a super-MICRO usb keyboard as my Logitech diNovo edge BT keyboard evidently needs a bit of a charging after a full vecation without any power ;)

Typos come easy that way :D

Edit: Proof!!!
[Samsung Galaxy Nexus] josteink:
Getting 7,9/2,6 up/down with UGLC1 here in Oslo. Haven't been around enough to test stability, but will do tomorrow.

I've definitely seen worse. Will see if it comes at the cost of battery-time or anything else :)
[Samsung Galaxy Nexus] pesc96:
In one week I´m going to the UK, can anyone say me if this baseband ( SC04DOMKKD) works in the UK?
[Samsung Galaxy Nexus] esuohe:
UGKL1 to UGLC1 to UGLA4

Roger's user running CM9 nightlies (currently 04042012).

Experiencing 5 Mbps down/2 Mbps up with UGLA4 in downtown metropolitain area.

In suburbs, 3/1 with UGLA4, much better compare to UGKL1.
[Samsung Galaxy Nexus] josteink:
Hey. This thread has been stickied? Cool :D
[Samsung Galaxy Nexus] pcphobic:
UGLA4 is still the best.
[Samsung Galaxy Nexus] efrant:
:)

I guess it depends on each's usage pattern. For me personally, based on everyday use (no speed tests, benchmarks, etc.), I have not noticed ANY discernible difference between any of the following radios: UGKK7, UGKL1, UGLA4, XXKK6, XXLA2. If I actually used a speed test, maybe I would notice something, but for my real world use, no.
[Samsung Galaxy Nexus] pitflyer:
Any reason to choose to flash these via fastboot rather than CWM? Fastboot is a new world for me - used to CWM from other phones. If I use CWM to flash a new radio, do I wipe cache afterwards (as I think I saw was the recommendation on the fastboot option)?

Does it make sense to just download all the radios and then I can flash back and forth with impunity? I'm happy with XXLA2, but will be doing some international travel in the future, so have no idea if it will work as good over there with other carriers. Having the others available 'just in case' and I can flash 'on the fly'?
[Samsung Galaxy Nexus] efrant:
Fastboot is generally regarded as "safer", as fastboot will not flash a corrupt image, while dd (which is what is used in these CWM packages) will. That said, as long as you check the MD5 hash, you are fine using either method.

Not necessary, but I would.

Sure, why not.

Yup.
[Samsung Galaxy Nexus] pitflyer:
So one last question, if I do flash a corrupt radio through CWM, will the phone no longer boot, or will it boot and just have no radio?

I ask because there's a good chance when I travel I would not have my computer (which I think is a requirement to use fastboot) so CWM would be my only option. If an image for some reason gets corrupt, (at least in theory..) should I be able to go back in and flash another working CWM radio?
[Samsung Galaxy Nexus] jeetS:
I like UGLC1 best reception in my patchy area
[Samsung Galaxy Nexus] efrant:
I can't answer that for you, as I have no experience with bad radio flashes with CWM.
[Samsung Galaxy Nexus] huyha707:
I'm not getting 3g for T-Mobile USA. Must be a baseband thing. I have baseband TDVKK6. Anyone known what that is?

Edit: nvm I found it. Its from Australia. I assume I have to flash a base and that is compatible with T-Mobile network right?
[Samsung Galaxy Nexus] josteink:
Looks like First initial baseband listed in second post on Page one for i9250t, telstra.

Try any of the UG* basebands.
[Samsung Galaxy Nexus] huyha707:
I just flashed several different radios. Ones that is stated that it is compatible with T-Mobile USA 3g. Still no dice only getting edge. I'm on aokp milestone 4 and Franco kernel milestone 2. Any ideas guys?

Edit: I fixed it :)
[Samsung Galaxy Nexus] ygvuhb:
hi all

i just make a request to google

for force the phone receiving specific 3g band

as i suffer a very bad 2100 signal (no internet connection) but good connection when receive 900 (in my office)

if you guys have similar problem or any opinion, please leave your comment in this thead

hope goole accept this request

thanks all

http://code.google.com/p/android/issues/detail?id=28644
[Samsung Galaxy Nexus] thanksgiving60:
yea shet dont stick :mad:
[Samsung Galaxy Nexus] SUPARSTARX:
Who's in the NYC area with this phone and getting more than 10megabits on Tmobile? I can't even break out of 3g. What's up with my phone?
[Samsung Galaxy Nexus] tonyny13:
I'm in NY are Nassau County and i just purchased Galaxy Nexus IS9250 networks seems to be ok not as fast as my previous phone (GSII) whats actually bothering me its the fact that it reboots by itself sometimes, and it doesn;t seem to find an update currently running on ICS 4.0.1 is this common>?
[Samsung Galaxy Nexus] chimaki1:
what radio did you end up using that worked? i also have the australia build on US T-Mobile and having radio issues, on the AOKP and Franco setup.
[Samsung Galaxy Nexus] Lush78:
This is an extremely informative thread... Thanks to the efforts and updates from the OP...
[Samsung Galaxy Nexus] PlaidStallion:
Just flashed XXLA2 as it said it was the Euro baseband. I am running on O2 in Germany. I just recently got this phone as I just moved to Europe. I am running AOKP B31 with Lean Kernel. I have never flashed a baseband before but got to looking into the fact that apparently a new rom does not mean a new radio is flashed. I immediately rooted my G-Nex from 4.0.1 and flashed from there so I was still on XXKK1. Thanks to this thread I see I should not run that baseband on anything higher than 4.0.1.

As I stated, I see that XXLA2 is the newest for 4.0.4 but can anyone recommend anything better for Western Germany on the O2 network?

Will any of these baseband revisions work for me just performance may vary or do I have to stick to euro basebands? Thanks if anyone can help.
[Samsung Galaxy Nexus] heo_con184:
Any of these radios will work for your GNex, you should try the lastest ones XXLA1 / UGLC1 / etc.
[Samsung Galaxy Nexus] :
I'm running uglc1 in Germany and o2 without any problems :)
[Samsung Galaxy Nexus] SNaReX:
In Los Angeles & California area with GSM GNex for T-Mobile which radio are you using?

I have been using XXKL1 for a long time. I think it is time to try something new.
[Samsung Galaxy Nexus] neolee:
Thank you for your excellent work.

I'd like to test some to enhance my signal
[Samsung Galaxy Nexus] Flukester69:
I was using that and I switched to UGLC1, so far it's pretty good.
[Samsung Galaxy Nexus] Peejay571:
Not sure if this has anything to do with the baseband. I had ported my number from Rogers to Wind, waited a couple days, then decided to root it. Which I have done many times before. After installing my first ROM, in setting under about then status my number reads the temporary Wind number I had during the porting and I cannot send texts anymore. Any help would be fantastic, Thanks
[Samsung Galaxy Nexus] myrdog:
I'm running UGLC1 in London, Ontario, Canada on TELUS. I was originally on an older XX version. Battery life and signal strength improved dramatically afterwards.
[Samsung Galaxy Nexus] josteink:
Late reply. I know. Sorry :D

I've flashed a few bad radios via CWM (while trying out my radio-ripper tool and packaging CWM-files).

From what I can tell, your phone boots fine, but may be confused about what baseband it is actually on.

I quickly fixed this by flashing a good image, as I have no idea if being on a corrupted baseband image is healthy or not for the underlying hardware.

So. You should be fine, but it's probably a good idea to get back on a good baseband as soon as possible :)
[Samsung Galaxy Nexus] maniac2403:
It is an issue with WIND. I had the same issue when I ported my number as well. They eventually had to change the sim card for me.
[Samsung Galaxy Nexus] meminiau:
Just wanted to share in particular with those in Australia....

I'm currently running AOKP build 31 with the latest Franko nightly kernel. I've flashed a heap of times, using various different ROMs and kernels. I have always kept on using the stock Telstra radio, except for one of the first times I flashed when I gave a different radio a go, and for the one time when I flashed one of the latest 4.0.4 ROM's and it flashed a new radio over the Telstra one.

I've always been happy with the performance of the Telstra radio. I have always had good signal strength along with high data rates. I just wanted to put it out there that you don't have top update the Telstra radio just because you aren't running 4.0.1 anymore :-)
[Samsung Galaxy Nexus] P500:
I'm using AOKP b31 without any further modifications.

UGLA4 is best for me in Southern-East Germany using o2. XXLA1 was slower, unstable and thus not reliable enough.
[Samsung Galaxy Nexus] javi3k:
can i ask i dont see alot of latinamerican in here which is the best radio for colombia ? i was gonna try to flash the brazil one, but not sure yet if i wanna play whit the radios, any repercusion if do it ?
[Samsung Galaxy Nexus] theSpam:
Thanks for the info...it seems that Samsung devices are extremely robust and are pretty hard to brick (unlike HTC devices where a bad radio flash means that you're toast).
[Samsung Galaxy Nexus] Fountainhead931:
Wrote my Yakjuzs to Yakju 4.04, no problems at all, reception didn't get any better but never was really good unless I could see a tower. Had to switch to wifi in certain areas of my home, but with my Atrix and Nokias, had signal all over.

So, this weekend I used fastboot to switch from xxla02 to uglc1 and I must say, signal reception is much improved, I get the "H" and more bars all over the house. However, the speed is much reduced with Speedtest. I'll have to wait to Sunday AM here in Orlando that's when I'd get my all time best speed, 6 down and 1 up. This speed is consistent with results with Atrix and Nokias. Right now getting 1.2 to 1.8 down and 1 up.

Anyone else in Orlando area got any results to report?
[Samsung Galaxy Nexus] MuT7:
After using it for a few days, I'm happy to say that UGLC1 is an upgrade over UGLA4 for anybody on Wind in the north Oshawa region. Though, arguably the signal here is still crap, it's now marginally better.
[Samsung Galaxy Nexus] nxt:
Guess I'll post of my experiences.

I'm in Southern California on T-Mobile.

Was using UGKL1 for a while, then went to UGLA4 then UGLC1

Where I work T-Mobile isn't very good unless I'm outside in the open.

Inside any buildings totally suck.

With UGLC1 at my desk at work, I get either 0-1 bars H or I get Edge... I was on this Radio for a week and it was painful.

With UGKL1 I get 2-3 bars H at work.

So till a new UG radio comes out, I'm sticking with UGKL1 for me.
[Samsung Galaxy Nexus] Razer(x):
What's the suggested baseband to try for Italy? (TIM)
[Samsung Galaxy Nexus] denis4o:
Have been using XXLA2 + PRIMELA03 for a week in Bulgaria (M-Tel) and I don't know if the network has been upgraded or the baseband+radio combo helped but my 3G speed (download) went up from 400 KB/s to 1100 KB/s