yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] oscillik:
If your phone came with build ITL41D, then Samsung didn't do a thing to your phone except open the box, take the phone out, and go "duuuuhhhhhooooohhhhh" and put it back, and seal it.

By all accounts on here so far, Samsung have done sweet F-A to handsets before sending them out to retailers.
[Samsung Galaxy Nexus] burnduck:
I'm yet to receive the OTA, google hates me! :(

But i've made a video showing the CPU impact pre-OTA and I will make another video once OTA hits.

http://www.youtube.com/watch?v=LlPN7XgXXsw
[Samsung Galaxy Nexus] oscillik:
Very interested to see what the result is after the patch.
[Samsung Galaxy Nexus] Alexander T.:
Sorry for offtoping, but what does F-A mean? :)
[Samsung Galaxy Nexus] braingravyuk:
Fu*k all - k thx bai
[Samsung Galaxy Nexus] Chirality:
It modifies the system and recovery partitions. It doesn't do anything to the bootloader. Those block device references you saw are for the recovery and system partitions.
[Samsung Galaxy Nexus] Shodney:
I tried a similar test before using the 'show CPU usage' in developer settings, but to be honest I didn't really understand what the bars were doing :D

Also couldn't figure out how much of the usage was attributed to showing the volume bar graphics, and how much was just the CPU trying to handle all the inputs.

It'll be a good comparison though :)
[Samsung Galaxy Nexus] burnduck:
the three numbers (something like 0.0 / 0.0 / 0.0) are the average loadings of the past 1 / 5 / 30 minutes

say the phone's got 2 processors, a 100% loading on both cores would be represented by 2.0 but the figure could go over 2.0 if there are processes waiting to be processed (too many things to do and too slow processor = traffic jam!)

edit: this page seems to do a better job explaining linux loads: http://blog.scoutapp.com/articles/2009/07/31/understanding-load-averages
[Samsung Galaxy Nexus] regorsnas:
Me too ! If there is a diference betwen before and after patch in the CPU use. We will see...
[Samsung Galaxy Nexus] oscillik:
This is a very good point actually...
[Samsung Galaxy Nexus] Nail_s:
Guys, mine was from the first batch from Handtec and had two seals as well... That means Handtec employees lied about devices beeing "flashed" or have been misinformed...

P.S. Still waiting for OTA... :/
[Samsung Galaxy Nexus] jms.flynn:
I swear to god if i haven't had an update by the end of the day tomorrow I am doing what oscillik has done and flash via clockwork. I am f*cked off with this, I know i have taken one back and then got a slightly later batch by a week I still feel that i should have had the update by now. Very angry and not impressed.
[Samsung Galaxy Nexus] rs20:
It's an interesting point, but not at all important, right? As long as the CPU doesn't show any changes/spikes at all when a 2G mobile is nearby, the problem is fixed. If the phone still hogs the CPU trying to figure out what's going on when it's getting interference, I would consider that an unacceptable fix -- so why does the break-down of faulty CPU usage matter?
[Samsung Galaxy Nexus] Nail_s:
Received my update 15 minutes ago :> I was trying to reproduce the issue with no success. For me problem is solved. Thank you for everyone who participated in this thread and good luck with the rest of us who didn't received OTA yet, I think you'll get it in the next 24 hrs :)
[Samsung Galaxy Nexus] kristovaher:
My OTA also finally arrived, so this epic chapter is finally over with for me personally. I've never experienced such an epic drama about any product I've ever owned before. Hopefully Google and Samsung learned something from this product launch.
[Samsung Galaxy Nexus] burnduck:
:( still waiting for some love from google / samsung, time is killing my unrequited love

---------- Post added at 11:53 PM ---------- Previous post was at 11:52 PM ----------

did you guys go into settings and check for updates or it just popped up in notification?
[Samsung Galaxy Nexus] Skysurfer69:
Great idea. I won't be able to take a video but I'm going to enable the CPU stats on my morning commute (which is when I'm most affected) and then grab a few screen caps after that pissy mofo little bug strikes.

Effing stoopid little sub-Mb OTA
[Samsung Galaxy Nexus] Nail_s:
I was checking every 15-30 min... :-)
[Samsung Galaxy Nexus] MatthewPL:
Sorry, not block device but device file (in /dev). And one of them is named omap (just like CPU?). Little believe that maybe patch will fix it (I didn't saw anyone saying that patch didn't fix (official fix downloaded OTA) bootloader :P).

Thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you!

You did really great job. Cannot wait for after-fix video.
[Samsung Galaxy Nexus] sblantipodi:
can't wait to see the "after" video, thanks.
[Samsung Galaxy Nexus] samizad:
I just received the OTA notification. I chose the option to update later. Will I receive another notification later or what?

If I go to settings > about phone > system updates, I get nothing. It says system is up to date.
[Samsung Galaxy Nexus] Chirality:
I know what you are talking about, but read carefully.

mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");

This mounts the /system partition

apply_patch("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4151296:b817d9b3fbde74f355fffae95862c309f4aa382e:4151296:dc81bd5ed6cc8c5cf7a8c2898be14033cf1ab5ae",
"-", dc81bd5ed6cc8c5cf7a8c2898be14033cf1ab5ae, 4151296,
b817d9b3fbde74f355fffae95862c309f4aa382e, package_extract_file("patch/boot.img.p"));

This patches the boot image.

applypatch EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4151296:dc81bd5ed6cc8c5cf7a8c2898be14033cf1ab5ae EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery 7728f38d3bc8649019ab422eeb70e34f06282a37 4491264 dc81bd5ed6cc8c5cf7a8c2898be14033cf1ab5ae:/system/recovery-from-boot.p

This patches the recovery image.

Nothing in this patch touches the bootloader.
[Samsung Galaxy Nexus] zipr0:
Anyone with a UK Nexus got their OTA-notification OUTSIDE the UK?

I'm starting to wonder whether UK devices get the update if they're not in the UK. I'm in Switzerland, have a UK SGN from Clove and have still not received the upgrade notification.

I'm asking because I had a UK Nexus S before and never got any OTA updates - had to install everything by hand :-/
[Samsung Galaxy Nexus] samizad:
I am in Korea and had my O2 locked Galaxy Nexus shipped to me here from UK. I had an update notification this morning.
[Samsung Galaxy Nexus] bleets:
Yep, i'm sure they've learned that people are ungrateful, impatient, disrespectful etc etc...
[Samsung Galaxy Nexus] zipr0:
? you call people who shed 700$ for a device that had a drastic problem (which still hasn't gotten fixed for many of them) impatient and disrespectful? If anyone's disrespectful here, it's Google / Samsung.

---------- Post added at 07:33 AM ---------- Previous post was at 07:32 AM ----------

Good to know - thanks! Anyone with an unlocked UK device who got a notification outside the UK?
[Samsung Galaxy Nexus] andrew.k:
Please, when you finally get your update and make after-update video, try also to adjust volume manually while exposing the handset to 900MHz radiation. It's interesting whether the patch affects responsiveness. Thank you very much in advance!
[Samsung Galaxy Nexus] zipr0:
well, I tried several things now:

- UK SIM-card (3 UK) with and without UK VPN: no update available

- German SIM-card (O2) with and without UK VPN: no update available.

I'd say the jury is still out.
[Samsung Galaxy Nexus] Alexander T.:
2 burnduck

Please, test the handset in the bootloader mode as well after you recieve the update.
[Samsung Galaxy Nexus] nevuk:
I just got the update (overnight). I am checking it out now
[Samsung Galaxy Nexus] kristovaher:
I checked, but if you don't check then it should pop up within few hours. The device automatically checks every now and then (I wish I could turn it off for battery reasons, but hey, minor concern).
[Samsung Galaxy Nexus] nevuk:
Seems to be working fine. I am on vodafone and I forced it two 2g networks which used to cause havoc with the volume. No apparent problems now and I am not noticing any lag.
[Samsung Galaxy Nexus] rbs_uk:
Whre is my f**** update :mad::mad::mad: Handtec phone/Vodafone UK.
[Samsung Galaxy Nexus] mark.m.moran:
Here in Dublin on an unlocked Vodafone handset and no OTA update yet!!
[Samsung Galaxy Nexus] jabok:
I tried this - Old SE K750i with a Voda sim would send my volume haywire but now it does not. Also, the volume controls work normally - with single presses and with press-and-hold. All seems good with respect to responsiveness. :) Haven't done any CPU analysis or anything though.
[Samsung Galaxy Nexus] tylose:
Excellent idea. We'll know if this is actually a "fix".
[Samsung Galaxy Nexus] Duddyroar:
Got the update around 11PM last night (Tesco Mobile, phone was purchased PAYG from a 3 store in the UK).

I've tested using a Sony Ericsson Xperia Play in 2G network mode, no problems whatsoever.

Anyone know of any decent CPU logging apps that I can download to check if any load is being placed on the processor?
[Samsung Galaxy Nexus] IvanDobskey:
Still no damn update here! How long does it take to roll out a 1mb patch to a few thousand phones? Utterly stupid! Getting rather narked off with the whole scenario here. Samsung/google have a few things to learn when launching new phones. Shocking.
[Samsung Galaxy Nexus] bleets:
and where they going to learn them from? apple? :)
[Samsung Galaxy Nexus] davej777:
They seem to be treating it like a standard non-critical OTA update, which it is not.
[Samsung Galaxy Nexus] mingoid:
Just received my second nexus, this time from Expansys. It has the ITL41F update pre-installed :)
[Samsung Galaxy Nexus] bushbrother:
Day 2 with my new Nexus, very impressed so far, I did however see the volume bug on my way home last night when I left my nice office with great signal. I can see how that would be annoying if it occurred all day! No OTA for me either yet :(
[Samsung Galaxy Nexus] TheMafro:
Still waiting for my update too, I'm on Vodafone.
[Samsung Galaxy Nexus] bleets:
So vodafone now list the device for sale/order on their website...only a day or 2 after the fix goes out...which kind of makes it seem 90% voda were holding the phone back due to this issue...which makes you wonder why the likes of o2 dont test handsets.
[Samsung Galaxy Nexus] Scarygore:
I just phoned Samsung ‘customer services’.

I first phoned them on the 22nd to ask about the fault and I was told I’d get a call back inside of five working days.

No returned call.

A few moments ago, when I rang them, I was informed by ‘customer services’ that the fix for the call volume bug is not released yet and that Samsung engineers are still working on it.

So, either:-

1, There’s a problem with the part released update and there will perhaps be another, new and improved super-update.

2, There is no update available yet and lots of unbiased people on here are just pretending to have had an OTA.

3, Samsung’s ‘customer services’ lie to customers to get them off the phone.

It’s going to be option 3 isn’t it.

As you can probably tell by the sarcasm I’m not very impressed by their ‘customer service’.

I’ll get back to checking for updates.......
[Samsung Galaxy Nexus] kristovaher:
Customer Service may simply not know what you are talking about, it is a shame, but reality is that this is often a problem with huge companies.

The fix is indeed out and it works, I've not had a single problem since the OTA update and battery seems to last as long as before.
[Samsung Galaxy Nexus] bleets:
I think the fix is out...

I tend to trust what CNET UK say...they're a kind of major site. :)
[Samsung Galaxy Nexus] WhiteHartMart:
Its good to see the update has fixed things - just a shame even the update delivery is poor!

I'm in no rush for it as I'm unaffected on 3, but there are people with launch day phones and no update and others with phones only a few days old who have got the update via OTA already!

Seems a tad unfair that those struggling with the problem the longest don't get the phone fixed near the front of the queue!
[Samsung Galaxy Nexus] floateruk:
Sorry if this is a repost and I've missed it but:

There is a manual way of adding the OTA update

http://m.androidcentral.com/how-manually-flash-ota-your-galaxy-nexus

It does wipe your phone though. For those severely effected this may be an ok option.
[Samsung Galaxy Nexus] TheMafro:
I was pretty shocked O2 were selling it with a known problem that would affect it's network. Vodafone did the right thing.
[Samsung Galaxy Nexus] Scarygore:
I'm sure your right and I'm equally sure the update IS out.

If I'd had my call returned, (as my wife did with the same issue, same phone, same day of inital contact!) and had I not just been lied too, I'd feel a lot better about waiting.

I realize I probably sound petulant but at the moment the damn thing wont make a reliable phonecall!
[Samsung Galaxy Nexus] AntonyStark:
O2 only sold it for a day or 2, people who ordered on the 21st only got their phones in the last couple days. TBH I haven't had the bug yet.

Google are sending the update out in small amounts at the start, they have stated this. They don't want to send out a mass update that breaks something else and leaves more people with problems.
[Samsung Galaxy Nexus] M2281088:
Bleets pull your head in and stop being a troll.
[Samsung Galaxy Nexus] bleets:
...being a troll is showing a major news site have said the update is indeed out?

riight...put the crack away :rolleyes:
[Samsung Galaxy Nexus] gagaohlala:
Incredible

Hey i received my GN today from Expansys. It's incredible ! I think i'm lucky cause i hzve the new build ITL41F ! So my GN is without bug normaly !

I don't make mistake right ???
[Samsung Galaxy Nexus] FirstToTheLast:
This is certainly true for me, got my phone 2 days ago having ordered on 21st. Unfortunately it wasnt patched and still not received OTA notification.

I am in central london though and only experienced the bug once with a vodafone user right next to me as i took his number (not during a call).

IMO this has been handled well, those complaining about lack of communication obviously dont understand the reality of managing very large releases over large complex systems & how actually saying nothing is so much easier to manage than updates all the time (esp if there are testing issues/delays internally).

Also consider peeps that releasing OTA may not be that simple, they will need to push out to many servers, verify packages, download and test again for themselves etc etc, this all takes time over and beyond fixing it.... And if anything this whole saga proves they needed more days testing.

Just my 2p, bug should never have gotten released granted, but they did a good job fixing/masking the issue in a proper fashion.
[Samsung Galaxy Nexus] oscillik:
There is only one server for the OTA and it is here

There aren't multiple locations for it, this is the only place it is gotten from. As for the testing, that is what Google have been doing since the 21st November. So the slow roll out of the OTA cannot really be excused by what you're proposing.
[Samsung Galaxy Nexus] dirtyhank:
Actually this URL can map to several different servers:

android.clients.google.com. 0	IN	CNAME	android.l.google.com.

android.l.google.com.	54	IN	A	209.85.148.138

android.l.google.com.	54	IN	A	209.85.148.100

android.l.google.com.	54	IN	A	209.85.148.101

android.l.google.com.	54	IN	A	209.85.148.113

android.l.google.com.	54	IN	A	209.85.148.139

android.l.google.com.	54	IN	A	209.85.148.102
[Samsung Galaxy Nexus] oscillik:
Ahh I'm wrong again then!

But if there are that many servers holding the same file, why is it taking so long?
[Samsung Galaxy Nexus] AntonyStark:
Because they are only selecting a few handsets at a time at the moment, this number will increase. Some people just got lucky and when they just recently got the phone their IMEI was one of the chosen.
[Samsung Galaxy Nexus] Alexander T.:
So, is it still present in bootloader? I know its not so important, but anyway, would like to know.
[Samsung Galaxy Nexus] hotchy:
I thought id sign up and say thanks to the people of this thread who have kept the news up to date on the developments of this issue :D i am now able to go out and buy the nexus this sunday (pay day) and ill let you know if its the updated version or not!

Bye bye Iphone 3gs hellooooo free angry birds.. i mean android. First android iv had as my first ever smartphone was a 3gs 3 years ago ish after upgrading from my nokia 3310 lol i hope it fullfills my expectations, if not atleast i wont need to zoom into twitter to read my celtic updates :D
[Samsung Galaxy Nexus] mark.m.moran:
LOL...free Angry Birds...SO true though :-)
[Samsung Galaxy Nexus] neovisage.HD2:
Ta guys !i was feed up with GN and samsung.Never again samsung.Love my new motorola
[Samsung Galaxy Nexus] FirstToTheLast:
We think we know fix was found in 1hr, so based off of that, this is my guess on the whole process (not that i am bored at work or anything!):

1 Day - Build Work (finding it, writing code to fix and unit testing)

1 Day - Fix and development testing

1 Day - Build team to create patch

2 Days - QA/Testing teams

1 Day - Internal sign offs/politics

1 Day - Deployment packaging

1 Day - Deployment & Deployment testing (test mode so not visible to us)

1 Day - Deployment planning and implementation

For an enterprise product with many planners, developers, testers etc I think its a good turn around time for a complete fix.

Also their deployment method might not be liked (by those still waiting) but it shows they are not releasing anything willy-nilly in one shot to avoid mass histeria again.

I had a worse experience with my iPhone 4 and getting a new case so i could hold it lol :)
[Samsung Galaxy Nexus] oscillik:
I'm not taking issue with how long it took for the fix to finally get released, I'm taking issue with how long it is taking to actually push the fix out to handsets now that the fix has been cleared and given the OK.

But thank you for the informative breakdown :)
[Samsung Galaxy Nexus] Shaldy:
Can't find any info about CPU load after OTA, anyone tested it yet?
[Samsung Galaxy Nexus] M2281088:
You are not wrong Oscillik, this address you gave is a DNS CNAME not a DNS A record. There may be multiple servers behind it BUT it makes no difference.
[Samsung Galaxy Nexus] jms.flynn:
Hows the locked bootloader, gingerbread and motoblur treating you? Well?
[Samsung Galaxy Nexus] M2281088:
I am very curious. Has anyone on the Vodafone UK network had the OTA update?
[Samsung Galaxy Nexus] rbs_uk:
I was also between RAZR and GN, but went with GN due to screen size and sleek looks.

Android 4 is fresh out, so it will be full of bugs. Give it few months and Google will iron out all creases.
[Samsung Galaxy Nexus] ShiroEd:
Not yet!!! :mad:
[Samsung Galaxy Nexus] rbs_uk:
Same here :(
[Samsung Galaxy Nexus] ShiroEd:
Can UK GN owners WHO HAVE RECEIVED the OTA please post what network they are on please?

Do you guys think the rollout is in any way related to network?
[Samsung Galaxy Nexus] AntonyStark:
Only if a network had a bunch of IMEI numbers due to get the update at the same time. but technically no.
[Samsung Galaxy Nexus] rokfor2000:
Come on people, in pre-OTA part of the thread so many people were concerned with CPU load after the patch, you were arguing for 100 pages about impact of the fix on performance. Isn't there really a single person who already has a patch and who could check if there is any traffic jam on the CPU?
[Samsung Galaxy Nexus] Bilbo Fraggins:
Why are you so desperate to find fault with the phone? Even if CPU usage does increase, so what? I'm no technigeek but I'm assuming no processor runs at 100% efficiency due to software. If they had found this before release and implemented the same fix you'd all be "omg this phone is aces omg lol" being none the wiser that Samsung had possibly stolen some of your megahertz to fix it.
[Samsung Galaxy Nexus] braingravyuk:
The way this patch is being distributed very frustrating and the change from /sdcard to /cache for patch locations doesn't help things.

I had a Nexus One and unlocked the bootloader due to Vodafone taking an age to release the Froyo release for it but I wasn't able to lock it afterwards unlike the Nexus S and the Galaxy Nexus.

So just wondering if there is an issue with leaving your bootloader unlocked? Thinking on leaving like that so I can apply future updates without having to wait for OTA notification.
[Samsung Galaxy Nexus] s.m.knipe:
No it is not related to network, but rather an ID in each handset itself.

If you are curious, start a thread with a poll giving options for all of the carriers and whether people have received the update...
[Samsung Galaxy Nexus] rokfor2000:
Because I am curious! Good enough?

I didn't say anything that "some stolen megahertz" would be a problem for me, so I don't know what is your problem.
[Samsung Galaxy Nexus] Shaldy:
It's not about stolen megahertz, it's about phone going to deep sleep mode.

So if interference cause CPU spike even after OTA update, it wakes the phone up, affects battery performance.
[Samsung Galaxy Nexus] IvanDobskey:
I'm fuming at the length of time it is taking to roll out a 1mb patch to make my £500 phone work as a phone :mad: I'm really not impressed!
[Samsung Galaxy Nexus] enlli:
Not sure about CPU loading as I've no way to check at the moment. I've been running for the past 12 hours and not noticed any change in performance or battery drain.
[Samsung Galaxy Nexus] gambiting:
Are people still waiting for the update? My Nexus still hasn't received it, and I tried checking it in the about menu.
[Samsung Galaxy Nexus] Bilbo Fraggins:
That doesn't sound like much of a fix to me...
[Samsung Galaxy Nexus] Baguett:
Why are people still posting so much in this thread?

Google has announced a fix, and someone has already received it, so i dont see the problem? Are folks still having issues after the fix?
[Samsung Galaxy Nexus] IvanDobskey:
I think the issue is that at the speed google is rolling out this mythical patch only about three people have it so far :mad: By the time I get it OTA it will be time to upgrade to something else :rolleyes: It's great that my £500 super smart phone can't be used as a phone eh?
[Samsung Galaxy Nexus] bleets:
errm...

you only got the phone on wednesday whereas others have been waiting 2 weeks...the downfall of society
[Samsung Galaxy Nexus] N0matter:
Some people still have this issue because google are taking so long to roll the OTA update out. Unfortuntley i'm one of them.

Come on google, why the wait?
[Samsung Galaxy Nexus] Bilbo Fraggins:
No but by God we'll be ready if they do!
[Samsung Galaxy Nexus] burnduck:
i am still waiting for the fix
[Samsung Galaxy Nexus] Skysurfer69:
Nope...

Still waiting in vain like Bob Marley did...

---------- Post added at 08:54 PM ---------- Previous post was at 08:28 PM ----------

So excuse my ignorance if I've not understood this correctly...

Is there an reason to not use this option? Has anyone here done it this way and were/are there any repercussions aside from wiping the phone? Are we all just being martyrs in waiting for the OTA?

I for one am not overly concerned about the affect this has on call quality as my journey on the train every day takes me through far too many tunnels for me to have a decent conversation anyway, so for the most part my primary use of the device is to listen to choons and that is as much - if not more - of a horrible experience with this bug (for me anyway).

Never-mind that fact that if you're browsing, playing games or using the screen in any way, that stoopid volume bar renders the screen useless...