yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] TEK112:
That would make you the man.

Seriously, all of us appreciate the help. I think you will like sensorly a lot. It literally maps your entire drive and tells you what signal was available. Plus, it displays LTE and 3G signal strength simultaneously. I thought that was a nice touch.
[Samsung Galaxy Nexus] ATnTdude:
Yeah, but Sensorly can only read what the hardware tells it. If it's really a siloed vs true mean issue, it's not going to tell us anything since the RIL/baseband is just reporting the same data to the system app and Sensorly.

In order to verify a mathematically significant difference between the two h/w versions, r10 would need to report a signal 10dbm or higher than r09, in order to clear the rounding that r09 does to the figure. Anything less than 10dbm isn't proof of anything, I'm afraid. Even if it does provide a 3dmb increase, we'd have no proof, so we'd be back to the subjective and conjectural crap that has littered most of this thread.

A better way of furthering the investigation is whether r10 also range-bands the data. Does it jump from (say) -90dbm right to -100dbm, or does it scale up (it shows -91 to -99 inclusive)?
[Samsung Galaxy Nexus] EyeOfTruth:
The other question might be if the baseband that was released in this thread is more of a fix for .09 hardware and not .10 hardware. The reason I Ask that is I think the baseband in this thread tricks the phone into thinking it has a better signal then it really does.
[Samsung Galaxy Nexus] TEK112:
Remember, start with the basics and get a baseline, then complicate the tests. I agree with your approach, but it is worth starting small. Sometimes the most basic of tests will tell you what you need to know after some trending. I don't necessarily need a fluke to tell me a port has internet when I could just try plugging it into the PC.
[Samsung Galaxy Nexus] ATnTdude:
I'm not complicating the test, I'm defining the requirements needed to prove the hypothesis.

H0: A difference of less than 10dbm (well, a delta of ~6dbm could be enough if the test was extensive enough)=No statistical proof of reception delta.

H1: A delta of >10dbm=significant difference between hardware revisions and a therefore a justified reason for me to give Verizon a verbal beat down for knowingly selling me a defective unit.

Furthermore, Sensorly doesn't give dbm readings, which is what we need here, at least it didn't the last time I used it. It wouldn't satisfy the null hypothesis, because it's not quantitative.

We need a better test. What we need is to

1) Find out whether r10 gives banded signal readings readings.

2) Use the results to refine the null and alternative hypothesis to define the minimum theoretical delta needed to prove the alternative hypothesis.

3) Test for alternative using something that leaves a numerical log.
[Samsung Galaxy Nexus] TEK112:
I understand your test and mostly agree with your approach. Sensorly does indeed show dBm and I think it is perfect for our needs and trending. Also, it can give us a good delineation of service/no service during handshaking by monitoring no service time and calculating it in with 4G and 3G, all separately. It gives percentages too!

However, your initial hypothesis was concerned with hardware reporting and I am not sure how you will get dBm readings without using the handset internals. If you use something else to measure signal strength (stand alone device) how would you separate mic gain values between the devices and determine which is true reporting?

https://market.android.com/details?...251bGwsMSwyLDEsImNvbS5zZW5zb3JseS52aWV3ZXIiXQ..

Check it out. It has changed a lot since its inception.
[Samsung Galaxy Nexus] ATnTdude:
I stand corrected. I haven't used the app in about a year. That sounds almost ideal.

That's basically my point: the hardware and/or RIL is gimped. R09 lacks the granularity we need, so the required H1 is huge.
[Samsung Galaxy Nexus] TEK112:
Then what the hell should we do? LOL

Let's call Verizon and tell them to send someone out... :D
[Samsung Galaxy Nexus] klobkelosh:
Thank you!
[Samsung Galaxy Nexus] klobkelosh:
Could someone also post the old (stock) radio zip, again, since mega upload is down? Mil gracias!
[Samsung Galaxy Nexus] dp92180:
So, sorry to keep asking the same question, but is there nothing in the kernel that could improve signal acquisition and how signal retention is managed.
[Samsung Galaxy Nexus] ATnTdude:
Well...we follow your idea of using sensorly. We record the data. If there isn't a significant difference, enough to overcome the rounding down on r09, then we have no way of knowing which device really does get better reception.

---------- Post added at 07:58 PM ---------- Previous post was at 07:51 PM ----------

No. The signal is handled by the baseband. The kernel can interact with the baseband (via the RIL, which is basically the driver for the radio) when it wants to put the radio into standby when it's not needed by the application layer. Thus it can alter power consumption by the radio, to an extent, but it cannot change signal.

Basband > RIL (Radio Interface Layer) > Kernel > Applications.
[Samsung Galaxy Nexus] tsk138:
So does this app store a log locally of readings and locations over time?

I see where it will map your trip and upload a report but I don't see where I can access this data.

When I get home later this week I'll put this on my wife's phone(r09) and mine(r10) and let it record while we do our normal running around over the weekend. Then what?
[Samsung Galaxy Nexus] TEK112:
Sadly it is not that robust, at least that I know of. However, it will tell you the number of points of 3G and 4G during that trip. You can compare the numbers between the two phones to see if they are on point. You can then compare the maps you just drove with their interface to see where one gets it and one does not. As a separate test you can use the main page to measure 3G vs 4G real-time and compare signal strength in optimal and not so optimal areas. This should give you a nice picture of .09 vs .10.

There is also a very interesting app called netmointor (free on the market) that logs all signal information with GPS coordinates. However, it is cdma only.

edit: I just found this which I am downloading now.

http://www.freeware4android.net/mot...e-2277/rf-signal-tracker-download-111302.html
[Samsung Galaxy Nexus] EyeOfTruth:
For the most part I figure the default baseband is designed to try to cover up the glitch, because with the rounding it makes it hard to get real info.You almost need to put both phones on baseband version EK06 because that version on my 09 looks to give more info Ive watched my phone go from -100 to -112 to -104. This was all just by picking up the phone and moving it all within a foot radius. The only problem is ek06 isnt an official release and they can say its not an official release so thats why there is bad reception.
[Samsung Galaxy Nexus] Firon:
Mirrors for y'all.

4.0.2 radio + bootloader (stock)

4.0.3 radio + bootloader
[Samsung Galaxy Nexus] mac208x:
The signal keeps on jumping between -96 and -113 constantly at my local mall in this one particular spot. No windows or anything. I'm on the 4.0.2 radio tho. Didn't bother to flash the 4.0.3 as it does not do any much than change the signal -10 dbm
[Samsung Galaxy Nexus] ATnTdude:
Not really. Like I've been saying, the output is banded. So your phone is probably getting between something like -93 and -99, but because of how the number is displayed to you, it jumps all the way to -113.

Google the AnandTech Galaxy Nexus Review for more info.
[Samsung Galaxy Nexus] compnird:
Excellent!

Loaded this up on Monday. I had previously noted that my Thunderbolt consistently pulled in a better 4G signal than my GNex... After this update they are nearly identical and I have a better 3G signal in areas which don't have LTE.

I see better switching in borderline areas of 1 bar 4G and better 3G signal and much more reliable internet connections in general.

When officially released it will help a LOT of people out who I know are having signal issues. Thanks for the leak!

(Tested in Seattle, Tacoma and Los Angeles metro areas)
[Samsung Galaxy Nexus] BillLee3:
Didn't read entire thread, but I'll note that I believe 4.0.3 radios radically improved my Bluetooth connectivity to my 2011 Toyota Camry. Older radios would not stay connected.

Am using LeanKernel on CodenameDroid ROM and updated those components during similar timeframe, but believe it was the radio that fixed the Bluetooth.
[Samsung Galaxy Nexus] k.electron:
i dont think they resolved it in the thread so here i ask:

is there a known definite improvement in the HW version 10 as opposed to 09?

thanks.
[Samsung Galaxy Nexus] TEK112:
Hasn't been verified. See this thread also:

http://xdaforums.com/showthread.php?t=1433963
[Samsung Galaxy Nexus] Protocol 7:
Can someone reupload these? All download links from the OP are dead.

EDIT: Nevermind, spoke too soon. But; in case someone else wants to download the radio more easily, here you are: http://www.ipwnage.com/android/403radios_btldr.zip
[Samsung Galaxy Nexus] vick1377:
Can anyone share the zip files? I can't download at all from the link provided in the beginning of this thread. I would like to flash these radios but can't download files.
[Samsung Galaxy Nexus] jst07:
These helped me tremendously. I was having major signal black outs so I went back to VZW and got a new SIM card. After that I was just having occasional signal drops, but this fixed it entirely.
[Samsung Galaxy Nexus] Protocol 7:
Here you go:
[Samsung Galaxy Nexus] eeforme:
Are there changelogs available for the actual radios? Or are they Google confidential? I'm super curious.
[Samsung Galaxy Nexus] dynamicpda:
I wonder if a new SIM card would help me.

I've gotten crappy reception at home from day one out of the box. The leaked 4.0.3 has definitely made 4G/3G switching more decisive but it hasn't improved the signal.

My house is located a two or three hundred yards from a huge apartment building that should be well served by all the carriers. Sprint 4G worked perfectly fine.

Verizon LTE, 3G, and SMS don't work well. I rely on WiFi and I get duplicate SMSs and send failures because the signal is bad. I've been assuming that this is a case of the Thunderbolt-would-get-better-signal which would be fixed by an official 4.0.3 or 4.0.4 radio.

I should add that the signal in the middle of the street is awesome. It's only when I get indoors, away from the strongest signal areas, that the reception sucks. Sometimes it's only twenty feet from the street in a bar.

It's almost February and no new radio yet. Would a new SIM card help? (Doesn't seem like it.)
[Samsung Galaxy Nexus] ATnTdude:
A SIM helps in 4 occasions:

1) Inability to access the network. Akin to trying to login into a website without the user ID or password, but a lot more complex to avoid cloning. Usually a result of a damaged SIM.

2) Update failures (they build a new tower across the street and you SIM won't connect because it doesn't see the tower as in-network). GSM SIM's receive pushed OTA updates rather than manual PRL updates.

3) Tower switching issues. Your phone bounces between towers too quickly, or stays on one too long, or doesn't switch towers without a reboot.

4) Provisioning issues in the carrier's backend. In this case, the SIM itself is fine, but the activation of a new chip flushes out whatever was messing things up on your account.

It will not increase signal strength.
[Samsung Galaxy Nexus] Tikerz:
Speaking to the HW revision .10 vs .09 discussion, I checked my coworkers phone and he had a .10, but his build date was in early November whereas mine is a .09 with a build date in early December.

If .10 is supposed to be a "later" revision, then what I saw today doesn't make any sense.
[Samsung Galaxy Nexus] EyeOfTruth:
That could go along with what I heard recently. It looks like from what was told to someone I know by someone at the exec office the .10 is really a software update which really doesn't make since. and looks like the update is not really even planned to come out till march. Both me and my friend are taking it with a grain of salt because typically .10 or .09 would be hw version and 10 is greater then 9. But the nice part would be he is supposed to get an email with that information in it.
[Samsung Galaxy Nexus] reverepats:
holy hell. Guy you dumpep your EVO? Good to see ya here brotha. How u liking it? Loving Verizon man. Hope all is well bro.
[Samsung Galaxy Nexus] luckylui:
Indeed I did! Lol. Sprint was overall going ****, so hell here I am on Verizon kicking it. Loving it so far especially with this beast of a phone! How ya been?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] anton2009:
I got my phone like in the second week of January and I'm I151.10 V.EK05 / I515.EK02. I'm not really having problems with my 4g though (-93 dBm ~40asu), 2 bars everywhere I go... so I'm hesitant about flashing because I really don't have any complaints or problems.
[Samsung Galaxy Nexus] TEK112:
As always, use at your own risk. Just know that you can flash back if you don't like the results.
[Samsung Galaxy Nexus] tannor:
It can't be software. I am on .10 and have even reflashed everything back to stock directly from Google and still shows HW 10. If it was software would show 9
[Samsung Galaxy Nexus] luckylui:
How come I have 3 bars and it's telling me -94dBm ~42asu? .09 Hardware I'm running... wtf lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] EyeOfTruth:
I know, and I agree its not a software update it was a hardware revision. But until my friend gets the email he should get it makes it harder to pin it on verizon.
[Samsung Galaxy Nexus] dp92180:
I called and got to level 2. I asked about the different versions and whether or not I would get better 4g with .10, was told there is only 1 hardware version. My house is clearly in a 4g area according to their map and the tech agreed. I also told him that i have seen a thunderbolt side by side holding on to full 4g while mine barely grabs 3g. He tried "resetting" something with no improvement to show for it. He was sending a ticket to level 3...will update once I hear back.

When asked, he did mention that it wasn't the first time they have heard of this issue, but did say that it should have been resolved with the initial software upgrade.

I just wish they would be more upfront with what is going on, the phone (my second one, still showing .09) clearly should be picking up 4g at my house but it doesn't...maybe for a few minutes but then switches back to 3g until I reboot again, cycling through airplane mode doesn't help anymore.
[Samsung Galaxy Nexus] jmartino5920:
Related???

Delete post, just noticed 13 is 3g and 14 is 4g
[Samsung Galaxy Nexus] TEK112:
I just got off the phone with tier 2 technical support. They informed me that Samsung was preparing a software update that had a release date of mid-January. The technical rep said that she would reach out to the moderators of their internal forum and see if she can get a better answer on the date.

In the meantime, I found out that performing *22899 or any variation thereof will most likely destroy the Sim card. she therefore instructed me to pick up a new Sim card tomorrow at any local Verizon store and she would follow-up with me on Monday to see how my device communicates with the network.

She offered to send me out a replacement, but candidly told me that odds are it is a software problem not a hardware one and that a replacement may not be in my best interest. I really appreciated her honesty because I have a brand-new shiny phone that is less than two months old and I really don't want a refurbished device. on a more interesting note I found out that because the galaxy nexus is so new there are not many real certified like new devices to send out as replacements. A lot of the replacements that they are sending out are phones that were returned during the worry free guarantee period of 14 or 30 days depending on when the phone was originally purchased.

Sorry for the little diatribe, but I hope that this information helps someone.

*For all the lazy bastards who are going to skim this till the end - Do not perform a star *22899 or any variation thereof otherwise it will most likely damage your Sim card.*
[Samsung Galaxy Nexus] jmartino5920:
Damnit! When I got my GNex replaced the first week after getting on launch, the rep dialed just *228 but I quickly told him that 4G phones do not require it and quickly ended the call...just wondering if he messed up my SIM because I could have sworn that my initial phone got better reception! Feel like getting a new SIM! Only thing is that I get good up and down speeds when reception is great, but experience crazy 3G to 4G handoff and sometimes 4G will go to no data!

What should I do?

jmar
[Samsung Galaxy Nexus] TEK112:
Getting a new sim is a good idea. The tier 2 technical service representative also said that they were putting a block on start *228. Some phones are able to dial it, some phones receive a warning message saying that it does not apply to 4G phones, and some phone still allow it. Play it safe and get a new one.
[Samsung Galaxy Nexus] AcE XBOX:
It's a known issue that the Nexus is having issues. Even my Nexus sitting right next to the repeater will something drop down to 2 bars. My coworkers Nexus will lose 4g and jump to 3g sitting next to the repeater.

We have 2 repeaters in the Verizon store I work with. Every phone has perfect reception. The Nexus likes to dance around from full to nothing. I hope we get a fix soon.

---------- Post added at 06:15 AM ---------- Previous post was at 06:12 AM ----------

No, the sim card is fine because the phone won't dial out when you dial *228 or *22899. Give it a try. I used to try it on my Thunderbolt from time to time for demo purposes. That phone with the data throttle removed it would always sit close to 20mbps down and 12mbps up.

Funny thing is that 4g phones WILL dial out to *22899 when they are trying to activate.
[Samsung Galaxy Nexus] TEK112:
Some phones can't dial *228, but some do. The tech even told me that. They can't block all phones. It is a rolling update to the system on their end that blocks it. The block is on VZWs end. Also, there are threads around here suggesting adding *22899 as a contact and dialing it to bypass the local block on the phone. Damaging a sim in this way won't render it useless. However,it will impede its abilities.
[Samsung Galaxy Nexus] anton2009:
So ultimately I ended up flashing the new 4.0.3 radio and for me it was just a cosmetic fix. Only thing different is that when it's -93/-93 dBm I'm getting 3 bars instead of 2 (4g)... but, I haven't noticed this before, when I take it to campus at the University, I get four full bars with an up/down speed of about 30/20mbps (4g). So... I will have to revert back to 4.0.2 and see if it's the same thing since I haven't noticed it before.
[Samsung Galaxy Nexus] luckylui:
This what happens when you dial *22899 :D it doesn't damage nothing! Lol, its just the activation.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
As I said before, it does not affect all phones in this manner. Some phones have the block in effect and some phones do not. Verizon hasn't made it fool proof, yet. It is hit or miss. We have established that the PRL is updated upon every reboot and therefore *228 (regardless of what it used to do) does not work on 4G equipped phones. I guess my point is, why even try if there is no upside?
[Samsung Galaxy Nexus] luckylui:
*228 asks for you to press 1 for update and 2 for updating your roaming capabilities. The *22899 just straight forward updates the phone. From looks of it, its working with all the Verizon phones I have in hand. Three of them 4G and one not.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dp92180:
Does it change your PRL? It changed mine the first time I did it, but not after that.
[Samsung Galaxy Nexus] TEK112:
I hear you, but it is different for each phone. My phone would not dial *228. In fact, read through the threads. Most of the G Nexus' can't dial *228. When you press send it just erases the line. The back door way was to create a contact with *22899 and then dial it from your contacts.
[Samsung Galaxy Nexus] illcat2000:
I read a few pages and I'm sure I missed it but did anyone in the central Florida area flash the 4.0.3 radio and see an improvement. I'm on stock 402 just because of the horror stories some shared saying their data connectivity was destroyed by the new radio.my data is OK now but my reception is consistent at 0-2 bars in and around my house.
[Samsung Galaxy Nexus] wayneb02:
From what I understand it doesn't really change your signal, but instead displays it more acccurately
[Samsung Galaxy Nexus] luckylui:
It did as a matter of fact and I'm fine with that because the PRL is the main control to getting good signal strength. I was originally on a 1xxxx now I'm on 5xxxx. So far so good with signal strength.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Lost Dog:
After some serious issues with 4G on my phone I decided to flash 4.0.3 to see if it helped. I have the issue when 4G is active it will lose data and connectivity every few minutes. This drops calls as well. If I was set to CDMA only there were no issues... only with LTE.

With 4.0.3 I had fewer dropouts however signal was much worse and very sporadic. I could be standing in one spot and get 83db one moment then 104db the next.

I'm going to go back to 4.0.2 and compare again...
[Samsung Galaxy Nexus] Snake42490:
I have read everyone of these threads from start to finish about the new radio and i have been bouncing back and forth between doing this. anyway, I went from 110 to 83... phone seems much quicker download wise. I haven't checked numbers. But it was quick and painless, and it worked great for me!
[Samsung Galaxy Nexus] luckylui:
Well as it went down that PRL update did a big impact on my signal strenght...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BusyPooping:
trippy.

Also. Where are the .10 radios
[Samsung Galaxy Nexus] photolarry:
New VZW Ques

So I just got GN and rooted. And I believe I have the most current software but I do not know if I have the more recent PRL/Radio. On my HTC device it was easy to tell what it was. You just booted into fastboot/bootloader and read the info. Is it similar on this device? I have not tried yet. I have only been using the phone a few hours and been tinkering lots. Thanks
[Samsung Galaxy Nexus] luckylui:
If you look in the boot loader it will tell you either 9 or 10 if you have 10 then your pretty much good for gold bro. A lot of people have the 9...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] txyaloo:
My original .10 phone had exactly the same problems. I was in a VZW store for over 3 hours while they messed with it. They replaced the SIM 4-5 times. Finally said it was a known issue and to leave it on 3G for now. I walked out to the car and lost 3G service.

Went back inside and got a new phone. It's a .09 phone, but I've had 0 issues with signal.
[Samsung Galaxy Nexus] pauliewalnutted:
Yeah same here. From the sound of it, .9 people aren't having the issues .10 people are. I've had hardly any issues for the most part on .9
[Samsung Galaxy Nexus] mistermojorizin:
which prl number are you on now? mine is 52642
[Samsung Galaxy Nexus] Lost Dog:
That's frustrating... I'm thinking of heading the VZW store at lunch tomorrow and seeing that they say. I've emailed one of the employees who helped when we go the phones and she had not heard of the issues...

Maybe I'll walk in there and show them!
[Samsung Galaxy Nexus] dp92180:
I originally had a PRL that started with 1, but now mine says 52642, I'm in MA.
[Samsung Galaxy Nexus] luckylui:
Same as you. The previous one was the 1xxxx. Sprint does there updates so much easier! Wtf vzw!! Lol.

Sent from my Galaxy Nexus