yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tsekh501:
You were saying that UGKL1 gets you better performance at work, but you are sticking with UGLC1?
[Samsung Galaxy Nexus] Simmo3D:
Just bought a brand new Galaxy Nexus since I dropped and destroyed my last one. First thing I did was flash the latest 4.0.4 straight from Google. Have not had the issue with signal loss in sleep so I'm really happy.

I'm on Telstra 850MHz Next-G network and the radio is set to AUS2.

Speeds could be a little faster but ill stick with XXLA2 until 4.0.5 hits. I was thinking of trying a UG based radio but I haven't heard of anyone using it with Telstra and I cbf flashing if its no good.
[Samsung Galaxy Nexus] tzviki:
baseband

Hi

i'm currently using XXKK6. (originally installed)

I have some WIFI issues - the signal is too weak, comparing to other devices.

I am from israel.

which baseband should I use?

thank you
[Samsung Galaxy Nexus] rashidi_zin:
Have you try switching to other kernel instead? That might help.
[Samsung Galaxy Nexus] tzviki:
could recommend a specific kernel ?

I'm using 4.0.2
[Samsung Galaxy Nexus] bendirkss:
Franco.
[Samsung Galaxy Nexus] tzviki:
But it is not working with 4.0.2...
[Samsung Galaxy Nexus] bendirkss:
Update to .4
[Samsung Galaxy Nexus] wildguess:
I am on Wind Mobile and had roaming problems with XXKL1.

When I was outside the home zone the phone did not detect that it was there and was not turning off the data.

I did not have a chance to check if the problem was fixed in XXLA2, but XXLA2 and UGLC1 look pretty much the same to me when it comes to the Mobile network connection and signal strength, but the Wi-Fi DL speed is much much better. It is two much faster with UGLC1 than with XXLA2

---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------

Do not flash Franco on 4.0.2!!!

It may brick your phone.

The kernel is for 4.0.3 and 4.0.4 only.

P.S. Sorry, I did not notice that it has already been answered.
[Samsung Galaxy Nexus] efrant:
You know, it is not really necessary to say that. It just scares people who haven't really experimented with their device.

It will NOT "brick" your phone. That kernel may not work on 4.0.2, but all the user has to do is flash back his old kernel, and bam... a working device again...

It is very difficult to "brick" a GNex (brick meaning that it cannot be restored to working order without returning it or JTAG).
[Samsung Galaxy Nexus] wildguess:
OK. If you flash Franco kernel on Android 4.0.2 in Rom Manager or Franco Kernel Updater and forget to turn USB debugging mode on:

1. You phone will not be able to start.

2. You will not be able to flash another kernel via USB cable.

That is how you brick your phone.
[Samsung Galaxy Nexus] efrant:
No, because you do not need USB debugging to be ON to flash a kernel via fastboot. Phone is not bricked. You boot into fastboot mode and flash the kernel via fastboot, or boot into recovery, and flash in recovery. Both methods do NOT require USB Debugging to be on...
[Samsung Galaxy Nexus] Razer(x):
Having poor wifi with franco too
[Samsung Galaxy Nexus] bendirkss:
Strange, ive never had an issue.
[Samsung Galaxy Nexus] cmstlist:
Not to mention:

If you're smart enough to do a nandroid backup before flashing a kernel (and really if you don't, why are you flashing custom kernels?), all you have to do to revert is an advanced restore of boot.img only.
[Samsung Galaxy Nexus] wildguess:
Having fast and strong wifi with Franco M2 (UGLC1 radio).

The only downside is that the phone may crash and restart once in a week which was not happening with stock 4.0.4.

I have never flashed nightlies, though.
[Samsung Galaxy Nexus] wildguess:
Can anyone confirm that the roaming problem for Wind and Fido customers has been fixed in the latest XX radios as well?
[Samsung Galaxy Nexus] maniac2403:
According to me, most Google phones are very very hard to brick. Nandroids, fastboot, JTAG would allow you to get back to a working phone.

I flashed f135 over 4.0.2 and I was just stuck in a boot loop. Restored from nandroid, and all was fine again.
[Samsung Galaxy Nexus] aa_chow:
Roaming bug was fixed in UGLA4. I can also confirm no problems with XXLA2.
[Samsung Galaxy Nexus] josteink:
Incorrect on all parts. You have a phone which doesn't boot without corrective measures. That is not a brick. The term "brick" comes from damaging your hardware to the point where it cannot be recovered and hence is "as useful as a brick".

If all you need to do is boot to recovery and restore a backup, flash another kernel, or in worst case scenario restore to factory via USB and fastboot or download-mode that is by no means a brick. It is a easily recovery piece of hardware which can be brought to a full level of functionality and recover its full value fairly easily.

So: It's not a brick and not anywhere close. You are using the term wrong, and people here are right to point it out.

TLDR: It's not bricked and don't scare people into thinking the GNex is that easily brickable.
[Samsung Galaxy Nexus] Theshawty:
One question: Can the radio from the 4.0.4 image (XXLA02) be used without problems in android 4.0.2 or .3?

I'm wondering, because I'm gonna try a rooted 4.0.3 stock ROM to verify why my reception is crap. If my reception is crap in 4.0.3 as well, then my carrier has breakdowns. Radio is okay and SIM is okay.
[Samsung Galaxy Nexus] efrant:
I don't see why not. Try it. If it doesn't work the way you want it, flash a different one. No big deal. It won't hurt anything, that's for sure.
[Samsung Galaxy Nexus] unity04:
Does anyone have the build img for this:

I'm trying to get my phone back to stock settings to return and so far I have this:

Baseband (Android 4.0.2):

I9250UGLA4

Kernel:

3.0.8-gaaa2611

android-build@apa28#1

Build Number:

ICL53F

I'm trying to get the Build Number to match the image I attached exactly by having the .I9250UGLA4 at the end.

Any help is greatly appreciated.
[Samsung Galaxy Nexus] nxt:
Don't thread jack.

Go read this on how to revert to stock

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

Use the files obtained here: https://developers.google.com/android/nexus/images
[Samsung Galaxy Nexus] efrant:
What's worse: thread-jacking, or responding to the post and giving the thread-jacker the wrong information?

You were originally on a yakjuux build, but now you are on yakju. Look in the dev forum: someone posted a nandroid backup of a yakjuux build from Wind. Restore that in CWM, and you will be on build ICL53F.I9250UGLA4

And please don't post the same question simultaneously in more than one thread..

Now, back on topic.
[Samsung Galaxy Nexus] etche:
Anyone with a galaxy nexus in argentina??

I have tried 4 radios already and the Max speeds I'm getting are 700 kbps down and 300 kbps up. My apn are set correctly and I'm having full bars on either H or 3G.

Should I keep trying basebands? I don't think it will get any better..

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Theshawty:
Well, to be honest, flashing radios scares the crap out of me. I mean, if it somehow would fail, I have just acquired an expensive paperweight I have on contract for two years.

Though I don't see how it would fail since I make sure to be set before doing it. I always check MD5's before flashing radios or bootloaders. Not system/boot or recoveries, though.
[Samsung Galaxy Nexus] josteink:
Incorrect. No reason to be afraid.

If the flashing goes wrong, at worst you wont get any reception, and then you just need to flash a working radio image and reboot.

The Galaxy Nexus (and Samsung phones in general) are damn near impossible to **** up to a point where you can't recover them.
[Samsung Galaxy Nexus] tzviki:
As recommended in this thread, I flashed AOKP (4.0.4) and franco kernel (milestone2) and wifi still poor.

I'm using xxkk6, and I am from Israel.

which baseband should I use ?
[Samsung Galaxy Nexus] Theshawty:
Are you absolutely sure about this? I remember on my old Nexus One if a radio flash would **** up, the phone would instataneously turn into a brick and wouldn't even pass the first splash screen. That was an HTC, though, adn Samsung phones may act differently.

If what I've heard is true, the Wifi reception issue is in the 4.0.4 source code, so unless Google fixes the bugs and makes a new release for ROMs to be based on, we will have poor wifi reception and poor network reception.
[Samsung Galaxy Nexus] tzviki:
Had the same problem even in 4.0.2
[Samsung Galaxy Nexus] efrant:
Yes, Samsung phones are different. HTC devices are notorious for bad flash due to the way the radio and bootloader were stored on the device. Samsung devices are different. But regardless, fastboot will not flash a bad image to your device. It verifies the signature before flashing so you are safe in any case use fastboot. The CWM files in this thread were created using dd to flash them. This could result in a bad flash if your download was corrupt. I have never had a bad flash, but others have, and they just re-flashed a working radio with no issues.
[Samsung Galaxy Nexus] [[ Cold ]]:
I have used XXKK6, XXLA1 and XXLA2 and they all work ok, since last week I´ve been having some dropouts with TIGO, I´m flashing UGLC1 right now to test
[Samsung Galaxy Nexus] Flukester69:
I just switched back to UGLA4 because UGLC1 is crapping out on me too much. I get up in the morning and cannot restore my connection. It's grayed. Didn't have this problem with UGLA4. Another thing I noticed with UGLC1 is that it's always jumping for H to 3G constantly.

Update: the problem was not the radio it was my APN settings. If you don't have the proper APN settings your MMS etc might work but your data will go down. I think I finally have this fixed however I will stay with UGLA4 because like I said, UGLC1 seems to have some funky issues with 3G and H speeds.
[Samsung Galaxy Nexus] Theshawty:
Alright, thanks for this, good to know. ^^

I've tried all radios for my area and they are all they same. Crappy signal reception and crappy 3g/hsdpa.
[Samsung Galaxy Nexus] Wolfglance:
Hello there,

a quick question - What is the best efficient way to test a radio ?

what digits, numbers, infos ... should we look at ?

Thanks !
[Samsung Galaxy Nexus] efrant:
This is my answer to your question (although you and many others will probably not like it) :) :

Try each one out for a few days. See if you notice any difference in "real life", not in some benchmark. If you notice that one radio is slower speed-wise, or weaker reception-wise, than another, strike it off your list and move to a different one.
[Samsung Galaxy Nexus] Wolfglance:
Hey efrant, thanks for the quick reply as usual ! :D

I hear you lolllll (it is kind of stupid question but I read a lot of " i did a test , i will test ...etc.." ) and i was asking myself what kind of test are these guys undergoing ..lol

Cheers
[Samsung Galaxy Nexus] efrant:
They were probably using something like Speedtest for data throughput and latency, and some other app like Network Signal Info to see the signal attenuation.
[Samsung Galaxy Nexus] Jijonhyuni:
Thanks to :)
[Samsung Galaxy Nexus] Darksorcerer123:
Signal symbol?

So I have two questions 1) Does the H symbol on the Gnex's status bar ever turn blue? I read somewhere it did to indicate HSPA+ speeds but I have yet to see it. 2) Is it normal for t-mobile's 4g network to drop you down to HPDA when you are not using data? Perhaps that is the source of some people's problems using programs like speedtest. For example, I am clearly getting 4g speeds on it but it calls my network type cell.
[Samsung Galaxy Nexus] pitflyer:
I used this file to update since the Google update fails because I use cwm rather than stock... thanks efrant
[Samsung Galaxy Nexus] maniac2403:
1) Yes, when you are connected to the Google servers, the data bars turns to blue. It does indicate HSPA speeds.

2) No, the 4G symbol does not drop down, unless you are in a bad 4G reception area, or if you are using some sort of battery saving technique to drop to 3G if phone is on standby.
[Samsung Galaxy Nexus] ArmanUV:
Is UGLC1 still from that 1 guy who got a leaked ota? Or is it widespread/official now?
[Samsung Galaxy Nexus] efrant:
Still from "that one guy". Does it make a difference?
[Samsung Galaxy Nexus] ArmanUV:
ABSOLUTELY YES.

A leak is not a official radio that goes through QC and whatnot. There could be critical bugs that prevented it from being released publicly.

I'm not saying this radio is bad or particularly buggy, and there seems to be little QC when it comes to gnexus, but an official radio is still more encouraging.
[Samsung Galaxy Nexus] steve.garon:
The official radio is available on Google's official stock firmware web site. Download the stock firmware zip file, extract the radio and flash it using flashboot...
[Samsung Galaxy Nexus] efrant:
The thing is, it is NOT a leak. It just happens to be an OTA that was only pushed out to a limited number of devices. That does not make it a leak.
[Samsung Galaxy Nexus] ArmanUV:
what? Nobody asked for official radio here. we're talking about how ugcl1 was only pushed to 1 person and therefore it may be better to stay on ugla4.

And google stock radios are intended for europe. It's recommended that north american users stay on the UGXXX radios.
[Samsung Galaxy Nexus] efrant:
I think you are making a lot of assumptions there.

Saying that it was only pushed to one person (just because only one person on XDA had reported receiving it) is a pretty big assumption if you'd ask me.

Secondly, have you disassembled the radios to see what makes the UG radios for N.A., different from the XX radios for Europe, and makes you say that those in N.A. should stay on UG and those in Europe should stay on XX? I certainly haven't, but what I can tell you is that in real world performance, I have not noticed any difference WHATSOEVER between all the radios that I've tried: XXKK6, UGKK7, UGKL1, XXLA2, UGLA4.
[Samsung Galaxy Nexus] ArmanUV:
You're right that it may not be just 1 person, but it certainly wasn't a full blown deployment. Otherwise, we would have heard from at least a few other people, and not just on xda.

And yes radios are closed source and nobody knows what the difference is. I said it's RECOMMENDED to use UG radios in NA. It seems logical that they didn't go through the trouble of naming it differently if it was identical to XX radios. It also seems logical that canadian careers optimized the radio for their network.

In NA, the difference between UGKK7, UGKL1, UGLA4 and UGLC1 is *probably* very small and mostly related to bug fixes for drops/battery/etc and not data speed. However, there has to be a difference otherwise they wouldn't go through the trouble of releasing new versions.
[Samsung Galaxy Nexus] pcphobic:
Anybody have the radio from latest build IMM761?

http://www.android-advice.com/2012/unlocked-gsm-samsung-galaxy-nexus-imm761-update/
[Samsung Galaxy Nexus] Timmyfoxeh:
IMM76I didn't include a new radio, that's the same XXLA2 from the initial ICL53F 4.0.4 update.
[Samsung Galaxy Nexus] efrant:
Although I have never seen that from Google or Samsung, let's take it as true for the moment. Looking at an analogy, Volkswagen recommends that I use a certain type of oil in my R32. If I use a different oil, say a synthetic blend, which actually performs better, does it makes sense to use the recommended oil?

You'd be surprised what companies do. Years ago, Black & Decker put out a "new" line of "professional-grade" tools. Turns out they were the exact same B&D tools, just a different color plastic and different name. It was made public; big scandal.

This seems possible, but I have yet to see any difference between UG and XX.

Assuming that it is "very small", then does it really matter? :)
[Samsung Galaxy Nexus] Theshawty:
This is my input, if anyone bothers to read.

http://cdn.memegenerator.net/instances/400x/19227394.jpg
[Samsung Galaxy Nexus] unknown00:
i'm still on 4.0.2, if i upgrade to 4.0.4 will my radio baseband be automatically updated?
[Samsung Galaxy Nexus] ellesshoo:
Pretty much what I've been silently wondering. With my NS there were huge differences with some of the radios that were easily observable (eg. UMTS radios had capped upload speeds). However, I haven't personally noticed any difference among the GN radios I've tried.
[Samsung Galaxy Nexus] josteink:
I've had very different performance profiles for the different radios.

I guess what they say about radio-tweaking not being an exact science and that lots of factors (location, provider, usage-pattern, etc) does play a lot into what people observe still holds true :)
[Samsung Galaxy Nexus] sk3201:
Switching from xxkl1 to xxla2 made my speeds very low. Same position same signal level.....back on kl1
[Samsung Galaxy Nexus] hk6162:
Thanks for your collection ,just want to try a new baseband!:rolleyes:
[Samsung Galaxy Nexus] Rogoshin:
Me to, my first radio was terrible.
[Samsung Galaxy Nexus] nxt:
Google is now directly selling GSM HSPA+ Galaxy Nexus to the USA.

They put up the Factory Image file for it.

Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet)

4.0.4 (IMM76I)

https://dl.google.com/dl/android/aosp/takju-imm76i-factory-e8c33767.tgz

Looking at the file it includes XXLA02 Radio...

Weird that they're using the international European radio, also an old one.

Hopefully they'll release a USA specific radio.
[Samsung Galaxy Nexus] colocynth:
After flashing the newest Europe baseband XXLA02, my signal sign becomes often turn blue, showing a good connection with google servers. Love radio flashing :D
[Samsung Galaxy Nexus] efrant:
Not sure why the released it under a different name, but takju is identical to yakju in every respect, except for the addition of Google Wallet.

Regardless, this lends support to my theory that there is not much difference between the UG and XX radios.
[Samsung Galaxy Nexus] castaway1:
i have problem with wifi "freezing" its fast but if i downloading it freeze for 5-6seconds then it go and over again... can new Baseband help me?

i have also problems with signal droping whish i know should other baseband fix.

thanks.
[Samsung Galaxy Nexus] Wolfglance:
Radio - Technical Question

Hello there,

does the "sim card" affect a radio performance ?

(i.e. An old one)...

Thanks
[Samsung Galaxy Nexus] Timmyfoxeh:
It shouldn't. It's possible you'll have a slight delay upon boot for it to connect to the network, but it shouldn't affect data speeds or performance overall. I have however heard rumors (~2 years ago) that a new one can improve battery life.
[Samsung Galaxy Nexus] tneRRot:
I'm curious about everyones data connection. My phone constantly switches between 3G and HSPA, generally landing on 3G and staying there 85% of the time no matter where I am in the city. I have tried a few radios (Whatever stock 4.0.1 had, UGLC1 and UGLA4), all of which yield the same results.

Generally speaking does your connection stay solid on HSPA? Is trying additional different basebands the most likely solution or should I start looking at custom ROM's or Kernels (waiting for the next milestone of AOKP before I start venturing there).

Thanks.
[Samsung Galaxy Nexus] netmasta10bt:
I'm running AOKP 33 atm (there is a nifty option to switch it to 2g when screen is off too). But even stock it would stick on 3g when it was idle, once I opened an app that wanted data it would move to HSPA
[Samsung Galaxy Nexus] tneRRot:
Hmm, that is interesting. I guess I assumed it would always be connected to HSPA and that the constant switching was it having trouble connecting. Now that you mention I tried just using Chrome to surf and it seems to connect to HSPA while loading a page then drop back to 3G and sit there.

Curiously on a couple Speedtest.net tests it definitely stuck on 3G as well but perhaps where I was testing at that time there was only 3G. I just did a test right now and got 4436kbps vs. 1467kbps previously. Still doesn't seem like particularily decent speeds for HSPA but meh. Will have to test some more but you might be onto something :)
[Samsung Galaxy Nexus] turdferguson00:
i rarely ever see hspa for more then a second... but i still pull down 8mb down/3mb up... not sure what hspa is supposed to be but thats more then enough for virtually anything you will ever do on your phone... so i could really care less what it says... lol... my .02
[Samsung Galaxy Nexus] josteink:
I use AOKP's power-saver feature to force it to 2G when phone is idle, which in itself saves me more battery-time than any good radio ever will. This alone makes AOKP worth the ride.

As for your root issue: I say radios are what you need to look into. Thresholds for when to switch to what network mode (unless overridden by phone, like 2g-only) are (afaik) controlled by the radio itself depending on signal quality and lots of factors.
[Samsung Galaxy Nexus] tneRRot:
Ok, that is good info - sounds like constant flipping between 3G and HSPA is the norm so I'll stick with the radio I'm on for now.

I'm still getting a feel for the stock baseline (IMM76I & UGLA4 which I have found to be the best combo for me so far) before going to a custom ROM but when AOKP M5 drops I'll be there =]

T
[Samsung Galaxy Nexus] hp13:
i really want AOKP M5 to be rock stable. Mostly all the roms are nightly with bugs and nothing is stable yet and phone has been out since dec. i really like the development community in GS2 i9100.. They really have rock stable roms. missing it :(
[Samsung Galaxy Nexus] maniac2403:
I have been using AOKP since I got my phone and don't have many bugs which I can't live with. Nothing which hampers the performance.
[Samsung Galaxy Nexus] dcdttu:
My $0.02

I switched my Nexus from XXLA2 (4.0.4 update's European baseband) to UGKL1 (the one for North America) because after the update to 4.0.4, my phone would sporadically lose data connectivity, or get hung while trying to access data.

The update to UGKL1 seems to have fixed that issue. I've gone days and my 3G data has held strong. I'm in Austin, TX.

I also hear there was an update to 4.0.4 to aleviate a data connectivity problem, but I don't know if it was an update to the basband or the Android OS. Either way, I'm not running 4.0.4 right now, and the baseband install fixed my issue.

Yay!
[Samsung Galaxy Nexus] josteink:
The data-hang issue is a Android 4.0.4 issue and not directly tied to radio as far as I know.

Flashing a new radio seems to have reduced the problem, but not fixed it entirely. I still need to turn on (and off) flight mode every now and then to regain data-connectivity.

On the plus side, not having data saves helluvalot of battery :p
[Samsung Galaxy Nexus] josteink:
So far AOKP has served me better and provided me with more stable builds for my Galaxy Nexus than any build, including factory images, for my old SGS1 (I9000).

So by my standards things are pretty good all over :)
[Samsung Galaxy Nexus] Cptsamir:
Anyone found a good radio for tmobile in the chicagoland area? I was getting speeds around 18 megs with my stock rom, and w/e the stock radio was, but now that I decided to try other roms I am only getting somewhere around 5-8 on all of them that I try, wondering if anyone has had better luck with them. Thanks.

-Edit- Just ran another test getting around 12megs, but my friend who is sitting right next to me is getting 22 on his htc one s. Something tells me I will never reach those speeds without a official tmobile phone....
[Samsung Galaxy Nexus] colocynth:
you may try cm9. I don't observe any reboot in my phone so far.

can't stand the unstability of aokp. switched back to cm after 1 hour trial.

---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------

no update on baseband. It uses the same basebands.
[Samsung Galaxy Nexus] uoY_redruM:
So, if I JUST got my phone from the Playstore today, would there be a radio image better recommended then the one it ships with?
[Samsung Galaxy Nexus] urinsane:
I stumbled across this thread checking to see if the play store nexus had an updated radio. What version radio did yours ship with?
[Samsung Galaxy Nexus] uoY_redruM:
XXLA1 is what it shipped with.
[Samsung Galaxy Nexus] nxt:
What I wrote a few days ago:
[Samsung Galaxy Nexus] unknown00:
how do i flash new radio? boot into cwr and select zip and reboot?