yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] thesmall24:
i have a galaxy nexus i9250m that doesn't connect to any gsm network in dominican republic, it has cyanogenmod 10 with xxla1 radio, i flashed stock yaksu 4.2.1 and have xxlh1 radio...

bootloader primeC03L or something like that...

I have tested some radio's but no luck.... please help....

it founds all gsm networks but doesn't register it says "cannot connect to this network, try again later.
[Samsung Galaxy Nexus] m.is.for.michael:
I have an intermittent issue where the APNs all disappear and I lose connectivity. A reboot usually fixes it.

If not, see if you can find your carrier's APN settings on Google and create one yourself.

Also, look around the phone advanced settings screen *#*#info#*#* and see if changing your frequency helps.

Sent from my brain using telepathy

---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------

See if you're set to automatic frequency in the advanced settings phone menu as above.

Sent from my brain using telepathy
[Samsung Galaxy Nexus] thesmall24:
OK this is weird. I have a Sim card on it, it says emergency call with no signal bars, but the data is working, I have full internet access....
[Samsung Galaxy Nexus] thesmall24:
look at this screenshot
[Samsung Galaxy Nexus] thesmall24:
I think that the radio is draining the battery....
[Samsung Galaxy Nexus] Pkt_Lnt:
You might try fastboot flashing a stock Google image. This will wipe your SD, reinstall stock bootloader, recovery and ROM, so backup what you need to your computer first.

If that does not solve it, you have a hardware issue that requires service.
[Samsung Galaxy Nexus] thesmall24:
I don't know what is the stock boot loader...
[Samsung Galaxy Nexus] Pkt_Lnt:
If you fastboot flash a Google image, your phone will be the way you got it. Unrooted, stock ROM, stock recovery, stock bootloader. It might solve your problem and you can start over.

See this thread.

http://xdaforums.com/showthread.php?t=1626895
[Samsung Galaxy Nexus] The Gingerbread Man:
thesmall24 You may want to hide your phone number and Imei

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thesmall24:
ok

sorry about the imei thing... :S

i live in dominican republic, the network i'm trying to use is hspa+15 850mhz, wich radio img you recommend....?????

Sent from my Galaxy Nexus[/QUOTE]
[Samsung Galaxy Nexus] Lancez:
Another option u can try, download GetRIL from market then run it. See what the app says, install proper RIL file for your modem(radio) and reboot, it should fix your problem
[Samsung Galaxy Nexus] iammagicboy:
Sorry to double post but

I flashed the latest baseboard XXLH1 in CWM,

When I rebooted,In setting,under baseboard it said "Unknown"

The same goes with the GetRIL App

I could however use 3G and dial flawlessly.

Is it a problem?

http://xdaforums.com/showthread.php?t=2069871
[Samsung Galaxy Nexus] josteink:
That sounds weird. Tried downloading and flashing it again?
[Samsung Galaxy Nexus] ChazzMatt:
osm0sis, but you are now using Brazil/South America UILH1?

Even though you live in Canada? Would you mind sharing why?

​
[Samsung Galaxy Nexus] osm0sis:
Yeah giving it a spin. ;) I was having some drops on XXLH1 I wanted to see if a different radio would resolve.

Working pretty well so far! A little better than UGLH1 perhaps. Not sure if I'd say it's better than XXLH1 yet, but it's at least equally good where I am at the moment.
[Samsung Galaxy Nexus] enel_:
I've got a problem with CM 10.1 and wifi, sometimes my wifi turns itself off when the screen is locked, sometimes don't, even if I set it to "always on" during sleep. With CM 10 I don't have this issue.

Could it be a modem issue?

I'm using LF1.

Thanks...
[Samsung Galaxy Nexus] m.is.for.michael:
No. Wi-Fi is controlled by the kernel, not the radio.

Sent from my brain using telepathy
[Samsung Galaxy Nexus] Batou069:
My question is, when should I concider flashing a new radio?

I am on XXKL1 the phone came like this.

should one flash only with signal problems or are there other reasons to change radio?

with this code from the OP i see in my phone info that my sygnal strength is between -61 and -69 dBm 24 asu ..HSDPA

thank you for help
[Samsung Galaxy Nexus] bimasakti85:
When you are upgrading your ROM and doesn't get match with getRIL...
[Samsung Galaxy Nexus] marcocsh:
where can i download XXKL6? I googled a bit but no clue:confused:
[Samsung Galaxy Nexus] Mach3.2:
What version of android are you running?

Beamed from my Maguro.
[Samsung Galaxy Nexus] marcocsh:
4.2.1
[Samsung Galaxy Nexus] ChazzMatt:
XXKL6? That would be a December 2011 radio build.

If you are on 4.2.1 or any Jelly Bean-based ROM, you probably want one of the three radios built AFTER Jelly Bean was officially released July 2012.

There are currently three radios built in August 2012, AFTER Jelly was released:

XXLH1 = Europe/International, 2012, August

UGLH1 = North America, 2012, August

UILH1 = South America, 2012, August

All other radios out there were built BEFORE Jelly Bean was released and are ICS-era or older.

XXLH1, while designated "Europe" is also the default radio for ALL the Galaxy Nexus phones. UGLH1 was found in a Canadian Jelly Bean OTA and may have some tweaks for Canada and/or North America (as UG is the traditional North America prefix). UILH1 was found in a Brazilian Jelly Bean update, but UI is the prefix for an area larger than Brazil -- possibly all of South America.

http://xdaforums.com/showthread.php?p=34939600#post34939600
[Samsung Galaxy Nexus] efrant:
You know what would be an interesting exercise: if someone diff'ed those radios (say XXLH1 and UGLH1) and actually took a look to see if there is anything different besides the naming. There probably would be a bunch of things different, but then again, you never know - it could just be a naming change only. I've seen stranger things! :)
[Samsung Galaxy Nexus] Gafanhotz:
Hey guys, I'm right now testing the XXLH1 on my Nexus (Brazilian one, transformed into GNEX), someone from Brazil already tested the UILH1?

The only question is: The UILH1 have an matching RIL for it? I tried flashing it but I don't like to have it with an mismatched RIL, so I flashed the XXLH1 to match with my RIL, but right now I can't do field testing on it.

(Brazil users: If someone tested the UILH1 please contact me via PM. )
[Samsung Galaxy Nexus] osm0sis:
Follow the RIL link in my sig. RILs don't actually go with radios, and GetRIL and the OP should probably be altered to reflect that at some point. RILs go with Android builds, so if you're running a current ROM odds are your RIL is fine.
[Samsung Galaxy Nexus] Gafanhotz:
Thanks, probably at this point the best for me (@CM10.1) is the XXLH1 and the JOP40D (default on the rom). But it's like I said, I need further testing with this combination, if I don't have any problems I'll stay with it, since it's the "stock" for the 4.2.

Hope it reduces a bit of my battery consumption.
[Samsung Galaxy Nexus] josteink:
People seem to have a different opinion on this depending on who you ask. I haven't seen any real data showing that ril "matching" is of any importance at all and if anything I'm considering rewording it to downplay it all together as it seems to be the source of a million confusions, in fact most of the confusion in this thread.
[Samsung Galaxy Nexus] Gafanhotz:
I've made a lot of tests on various devices a few days ago, and matching RIL/Baseband bought better signal and/or better battery life. But it depends a lot on what rom, what country you live (signal quality from your operator, etc) and a few things more.
[Samsung Galaxy Nexus] osm0sis:
Yeah please do. As I wrote in my RIL comparison post people shouldn't worry as much about it since if you're on a recent ROM and radio they'll be matching anyway. Anyway all I was suggesting for the OP was to explain that, as a vendor binary driver, RILs match the ROM (specifically by the Android build), not the radio. My post is hard data for that at least.
[Samsung Galaxy Nexus] osm0sis:
Sounded like fun. Done. ;)

There are some minor changes in what appear to be header and preamble areas, then just vast chunks of unique raw data which I assume are the binary radios themselves. So they are different.

One interesting thing is that we have a legitimate builddate string as part of one of the area headers (starting at offset 69070, generally ending at 6911B, with a hex length of AC):

SP6260_Q1_01.1230_DB120726 2012-Aug-1 22:05:19 .
PDB_NOT_AVAILABLE ..SP6260_Q1_01.1230_DB120726.I9250XXLH1
.1176407 ..<no label>.9ed34d38...........

SP6260_Q1_01.1230_DB120726 2012-Aug-2 20:10:19 .
PDB_NOT_AVAILABLE ..SP6260_Q1_01.1230_DB120726.I9250UGLH1
.1176787 ..<no label>.9ed34d38...........

SP6260_Q1_01.1218_DB120502 2012-Aug-10 14:30:57 .
PDB_NOT_AVAILABLE ..SP6260_Q1_01.1218_DB120502.I9250UILH1
.1178925 ..<no label>.9ed34d38...........

From this you can see that UILH1 is technically the newest by build date, at August 10th. But you have to wonder about the difference in DB# earlier/later in the string and whether that has any bearing on what it was built from. If that's the case then XXLH1 and UGLH1 have a higher DB# than UILH1 (1230_DB120726 vs. 1218_DB120502), meaning they could potentially still be built from newer code even though they are older by about 8 days.

XXLH1 and UGLH1 have the exact same DB#. Based on this I ran a comm -1 -2 on XXLH1 and UGLH1 to see exactly how much they have in common. There are some parts of their raw radio sections that match, but the majority of what matched was empty space around sections. Judging by the comm and the diff for these two, they are still mostly different, despite the matching DB#.

So.. What have we learned? The more you know, the more questions you have. :p
[Samsung Galaxy Nexus] josteink:
This is definitely new intel. Based on this I might redo the somewhat debated "chronological" first-page post. We'll see if I remember (and bother) once I have time ;)

(Now I'm trying to get some tf101 cm10.1-kangs going :p )
[Samsung Galaxy Nexus] efrant:
Hmmm. Your theory seems interesting. I wonder if the DB# is the actual date of the code used? In other words, is 120726 (July 26th, 2012??) the date of the code, and the date that we see in the header the date of actual compiling?
[Samsung Galaxy Nexus] osm0sis:
I definitely think the date in the header is the compile date, since it matches the LH1. It hadn't occurred to me that the DB number could be the literal code date, but that's a good thought! I was focusing on the 1230 and 1218 wondering what was up with them too if it was Dec. 18 and 30th, but that would be very old code so your idea would make more sense.

We'll have to see some more build strings from the older radios to get a better idea I think (if we see a DB111535 for example). No time to go slogging through them all myself at the moment but if someone has a bit of time they could grab all the radios, a hex editor (HxD is a decent free one) and go to offset 69070 to copy their build strings so we can maybe figure it out! :)
[Samsung Galaxy Nexus] efrant:
Here is XXLA2:

SP6260_Q1_01.1202_DB120111 2012-Jan-13 17:35:22 .
PDB_NOT_AVAILABLE ..SP6260_Q1_01.1202_DB120111.I9250XXLA2
.1097090 ..<no label>.9ed34d38...........

And here is XXKK6:

SP6260_Q1_01.1145_DB111110 2011-Nov-18 15:01:21 .
PDB_NOT_AVAILABLE ..SP6260_Q1_01.1145_DB111110.I9250XXKK6
.1080698 ..<no label>.fc12bf5b...........

Does seem that those 6 digits (that I was referring to) look like dates...
[Samsung Galaxy Nexus] aamadorj:
I think those 6 digits after DB can be a date in near ISO standard: YY-MM-DD.

DB could stand for database, but this is a wild guess.
[Samsung Galaxy Nexus] osm0sis:
Nice work! :) Interesting though, because 11-11-10 (db) is a lot closer to 11-11-18 (radio), and 12-01-11 (db) is a lot closer to 12-01-13 (radio), than what we're seeing with the LH1s; days apart to months apart. Also, perhaps the 1202 and 1145 are the corresponding times that go with the DB date?
[Samsung Galaxy Nexus] efrant:
The two I posted were from yakju/takju builds, as was xxlh1, while uglh1 and uilh1 are not. I would suspect that the dates should be closer together for yakju/takju than for the others, given they are compiled by Google while the others are compiled by Samsung.
[Samsung Galaxy Nexus] osm0sis:
True, I guess UILH1 with the May 2nd DB date is the only odd one out there. I wonder why Samsung chose to go back. It's actually performing quite well for me in PEI, Canada.

Edit: Just an update. UILH1 continues to exceed my expectations here. 0% time without signal in my day-to-day where I was usually at 5% before. Getting green for signal on my detailed battery graph where I usually wasn't before. Maybe they rolled back the code base for a reason! Best radio I've used I think. :D
[Samsung Galaxy Nexus] agent00f:
Quick question:

My US gnex (bought in US) w/ latest 4.2.1 stock update has the XXLH1 radio for some reason. Should I flash it with something different for better performance? I'm on T-mobile.

EDIT: Ok, I updated to UGLH1. Now my question is that GetRIL wants to use a matching RIL from 4.1.1 (for XXLF1/UGLH1). Is it right to get RIL from older version of android?

Thanks.
[Samsung Galaxy Nexus] josteink:
Don't. Getril is basically updated based on reports in this thread.

Don't update ril to something older. Messing with the ROM should not be needed in most cases.
[Samsung Galaxy Nexus] rolear8:
So UILH1 > UGLH1 ?
[Samsung Galaxy Nexus] osm0sis:
For me in my area. I think maybe, yes. ;)
[Samsung Galaxy Nexus] haxor:
The latest baseband is xxlh1 ? For jelly bean 4.2.1 ?
[Samsung Galaxy Nexus] bartolinio:
@amit.meena05 for Standard European baseband - Yes
[Samsung Galaxy Nexus] bwarmerdam:
This might be a bit of a n00b question, but I'm new the radio side of phones. If my phone (running OVERDRIVE rom, Android 4.2.1) has, under Settings -> About Phone, I9250UGLH1 as the baseband version:

Does that mean that I have the same radio that is linked to in the first post of this thread? or is that a newer/tweaked version of the same radio?

I just want to know if there's a point to flashing it, or if I would just be flashing the same radio I already have installed.

Thanks in advance!!
[Samsung Galaxy Nexus] osm0sis:
Google/Samsung are the only ones making radios so it's the same. :)
[Samsung Galaxy Nexus] darkvice01:
No need to flash the newer radio and RIL coz the ROM developer used that older version coz thats the radio that is stable for their ROM
[Samsung Galaxy Nexus] aswinrulez:
I got an i9250m running 4.2.1 (xylon 15) with baseband I9250UGKL1.My gprs is not working.I wanna test if it is issue with the radio?which radio is good for indian users?

UGLA4 or UGLH1 or any other?

got data pack by

Going to Settings>>More..>>Mobile Networks>>Access Point Names. Here either create a new apn or open the current one and change APN to TATA.DOCOMO.INTERNETHVC and then saving it and turning data off and back on

but still i would like to know about radio
[Samsung Galaxy Nexus] Milamber33:
You'll have to test yourself. There are so many variables it's hard to say which ones will work better and which will work worse.
[Samsung Galaxy Nexus] aswinrulez:
But i heard someone say that "if ug works for u try getting the latest one". So which one is the latest in UG?
[Samsung Galaxy Nexus] Pkt_Lnt:
post #3

http://xdaforums.com/showpost.php?p=20569019&postcount=3
[Samsung Galaxy Nexus] aswinrulez:
so UILH1 is the latest?will it be ok for me to use it eventhough my RIL is XXLH1 as per getRIL?im got this from ebay and its canadian model i9250m but im from India.
[Samsung Galaxy Nexus] osm0sis:
Answered one page back..
[Dell Streak 7] ramtix:
Hi All,

Just saw online that Optus is selling the DS7 for 279AUD. I was thinking about getting one, dont really need it because I've got a DS5 and I'm happy with my 5inch Streak. I just want to play with it and maybe enjoy a larger screen.

So ,DS7 owners..are you happy with the device? Is it worth it? I know that there are more powerful and better tablet out there. But I kinda loyal Dell fan(lame ..I know).I've got a Dell XPS17 and a Dell Streak 5..I think it will complete Streak family If I get the DS7.
[Dell Streak 7] TheManii:
279 AUD is approx the same in USD.

I'd say if you can get it under $250 or so it's a pretty good device, at least in the US it's not difficult to get one for that depending on what condition device you want.

It's pretty great if you take the price into account, I use my s7 the most out of the entire series (and I own the entire series). There might be better or newer devices, but the s7 is in a pretty sweet spot as it's more powerful then the kindle fire or so and cheaper then the gtab7+.

The screen isnt amazing, but it's not terrible.
[Dell Streak 7] ramtix:
thanks The Mannii for the input.I am gonna get this, I know I wont regret it. By the way this is not a WiFi only version I'm talking about.Its 3G, so I guess its a pretty sweet deal.
[Android Q&A, Help & Troubleshooting] absolute79:
If I can find at least 5 users who'a willing to pay USD60-100 each, is there anyone willing to develope a carrier unlock solution for this model?

I'll try to get at least 10 users from all around the world to sign up for this. Currently, I'm keeping in touch with 2 others guys from Europe. Finding another 5 guys shouldn't be that difficult.

Hope someone from XDA can help us with this. been a pain in the ass for while now trying to get my phone to work.

Hope i can get a good news asap.

Regards,

Steven.
[Android Q&A, Help & Troubleshooting] cdesai:
You want it to be carrier unlocked or rooted?

From my fingers to your eyez
[Android Q&A, Help & Troubleshooting] absolute79:
Hi cdesai,

I need to Carrier Unlock, I get this msg " This SIM card cannot be recognized"

I'm sure there's a solution to this as there's unlocked unit found in eBay but for a bomb.
[Android Q&A, Help & Troubleshooting] ahsanshah:
I need to unlook T-01 C Can u help me please?
[Samsung Galaxy Nexus] AardvarkAdventure:
Anybody having issues with the Google Voice app? The icon to compose SMS on the widget is grayed out on the widget, and the functionality seems to be missing from the app itself.

This may have been covered before, and I apologize if it has, but hey- this is the Q&A forum, right?

Thanks!
[Samsung Galaxy Nexus] EpiphanyMachine:
No issues, stock + root 4.0.2 updated from Google s images.
[Samsung Galaxy Nexus] AardvarkAdventure:
Hmmm....here's what I've got going on (note: inbox is working fine, I just cleared everything and reinstalled, which is why it's empty):
[EVO 4G Q&A, Help & Troubleshooting] robskilz:
Recently I have been having a problem with error 16. It happened of course when I activated on boost mobile. Then 3 days later it hit me 2 days in a row. And now a week later I am getting error 16 again. Did some research and couldn't find a fix. I know how to get it to go away I just need a way to make it stop repeating. Any info? Thanks
[EVO 4G Q&A, Help & Troubleshooting] robskilz:
I'm on a boost prl. And a custome Rom.
[EVO 4G Q&A, Help & Troubleshooting] Klown80:
Did you flash your phone yourself or did you pay to have someone do it for you? I know how to fix the error but lets figure out why it keeps happening also. The only time I've ever got that error is when I first activated the phone. Also, did you have to apply a fix each time it gave you the error or did it fix itself?
[EVO 4G Q&A, Help & Troubleshooting] foolish.av:
What prl are you using? Also would that work for me?
[EVO 4G Q&A, Help & Troubleshooting] foolish.av:
I just flashed to boost... Would like some input.
[EVO 4G Q&A, Help & Troubleshooting] vasiaeva:
ERror 16 FIX is .......Just call 365
[EVO 4G Q&A, Help & Troubleshooting] richdarula:
How do you fix i have recently been having the same issues. it comes and goes. ill make a call and sometimes get the error then i just hang up and try again then will usually fix itself
[EVO 4G Q&A, Help & Troubleshooting] 9h0s7:
The only time this happens to me is when I turn on the donor phone, I don't even have to make a call with it, and then turn on the Evo.

This is the only time this ever happens to me.
[EVO 4G Q&A, Help & Troubleshooting] meitiv:
In my experience error 16 happens when Boost initiates an OTA PRL update and when the flashed phone does not respond correctly (as a Boost phone would) it is flagged and error 16 results.

What you need to do to avoid it is to wait for an automatic PRL update after you activate the donor phone and only then flash the receptor phone.
[EVO 4G Q&A, Help & Troubleshooting] Dean_L:
Error 16 is a "Sprint" security Flag. It not related to Boost at all. What typically causes it is the radio still has some of the old MEID or ESN locations. When you flashed your new phone did you find the correct amount of locations in hex memory? I think 9 for MEID and 11 for ESN? Any less and the old info is still in hex memory and it will NOT authenticate. When you do your ##debug# I bet you'll see AN/AAA authentication = failed or so... check that out.

As far as clearing it, the only I know is to let the call go thru to Sprint. They will verify your Boost account and then reset your account. But if the phone is not fully flashed it will work but error out again later on.
[EVO 4G Q&A, Help & Troubleshooting] ganjamatik:
hello i got this error and let teh call go through but instead of sending to a rep it just says please contact your customer support provider at the end -- it hap[pened before but it went to asprint rep who helped me.. any ideas?
[EVO 4G Q&A, Help & Troubleshooting] grushko:
I don't know if it's actually related, but I'm getting that error only when I change Network Name through Service Programming from Sprint to Boost Mobile. After i verified account by talking to rep that error never happened again to me. Bt I'm still on old baseband and a PRI for over a month without any issue (except for battery life). Will update PRI and baseband now to see what is gonna happen.

Does anyone know is it ok to update NV from this thread?

[ Radios ][ 9-5 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
[EVO 4G Q&A, Help & Troubleshooting] richdarula:
just stay on the line and talk to the rep. they know exactly whats wrong and will fix no ??? asked. just remember to tell them the donor phone when asked what kind of phone
[EVO 4G Q&A, Help & Troubleshooting] kc3:
I've had this problem also anytime I turn on the donor phone, it's a super easy fix and you don't have to talk to anyone. What you need to do is find a temporary MEID, there's a topic at http://www.howardforums.com/showthr...ow-ESN-s-for-activations-here-(NO-QUESTIONS!) with tons of them (many are in use but look around) than (while leaving your donor phone off) go into your My Account on the boost website and change your MEID to the temporary MEID, wait a few minutes and change the MEID back to your correct MEID. This will fix the error number 16 problem. Keep in mind as well than anytime I've done this Ive left my Evo turned on, didn't have to restart or anything.

A second solution as the post above, you could wait on the line and tell them you're just trying to make a call, give them the description of your donor phone and they will call you back on another number and have you make a test call etc (make sure you do it from your Evo). They may or may not need to call you back though, this is just what I've always been told. The only solution I ever needed with this problem is the first one.
[EVO 4G Q&A, Help & Troubleshooting] slickrichierich:
Cool thanks i will try your first method next time!!
[EVO 4G Q&A, Help & Troubleshooting] Papa Smurf151:
Offering to sell a service is against the rules. Posting a paid service will warrent a ban