yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] spectrumfox:
The Galaxy Nexus is the first device I've encountered where you can't apply update.zip from stock recovery.
[Samsung Galaxy Nexus] aohus:
let us know the battery life. much appreciated. thanks. that is for anyone else on this new update as well. thanks in advanced.
[Samsung Galaxy Nexus] spectrumfox:
I'm still running my daily stress test on the new build. I will provide some results probably tomorrow.
[Samsung Galaxy Nexus] Rnd0209:
How is it looking so far?
[Samsung Galaxy Nexus] spectrumfox:
So far it's looking pretty sweet. A marked improvement over 4.0.2, no question about that.
[Samsung Galaxy Nexus] Rnd0209:
Oh boy oh boy! I actually spoke to VZW tech and the (Very Nice) lady on the other line told me that the GNEX will become a KILLER phone in the next few months, there are 16 issues that are going to be fixed after May. She has no idea about this update. Weird right!

I am seeing what the reports are so that I can exchange my razr maxx and its locked boot loader for the GNEX.
[Samsung Galaxy Nexus] player911:
I guess my question is how does this fair compared to the leaked 4.0.4 we've already had out in the wild?

Skimming through the thread it seems like the radios and such are the same. Is this anything to be excited over if we're already using 4.0.4 based roms?
[Samsung Galaxy Nexus] spectrumfox:
I definitely would exchange the Razr MAXX personally. I'll never go with another Motorola device after suffering with the Droid 3. Moto's UI and their locked bootloader policy suck badly.
[Samsung Galaxy Nexus] spectrumfox:
Too early to tell. So far I haven't been able to notice much of a difference, but I'm assuming the new 4.0.4 has more framework additions and bug fixes than the older 4.0.4.

The bootloader is the same from what I hear, but the radios are definitely different.
[Samsung Galaxy Nexus] Mr_Beefy:
What I did was open up control panel and then Device Manager. It said Android 1.0 with an exclamation point by it. I then went into the properties and clicked update driver. I searched for the driver manually using the second option and went to the gnex toolkit folder where the toolkit downloaded the drivers. I then selected the drivers folder and windows found it. Once the driver was installed it went right away.
[Samsung Galaxy Nexus] dalumberjack:
So stupid question.

I did the update and everything worked fine. I tried to reinstall cwm but I can't get root now. With my newbness I assume they have to reroot the phone since it got updated to 4.0.4 now and thats why recovery-clockwork-5.5.0.4-toro doesnt work?

I followed these (http://xdaforums.com/showthread.php?t=1392336&highlight=clockwork+mod) instructions like i did before but now I can't gain SU access.
[Samsung Galaxy Nexus] jonsgirl:
I had the same issue so did some research and found a different version of the su file that is known to work with this update. I'm not sure if I can post a link. I'll try but if not just search for ChainsDD's Superuser on this site.

Post #95 http://xdaforums.com/showthread.php?t=1610403&page=10

http://xdaforums.com/showthread.php?t=1610403&page=10
[Samsung Galaxy Nexus] Mr_Beefy:
Try the steps posted here
[Samsung Galaxy Nexus] jonsgirl:
My husband has a leaked 404 rom on his for about a month now. My signal is better than his and I'm pretty sure my battery usage is better. Still testint that theory.
[Samsung Galaxy Nexus] nexus9988:
thanks! worked great +1
[Samsung Galaxy Nexus] dalumberjack:
Thanks guys. All is well now
[Samsung Galaxy Nexus] flascrnwrtr:
OK, this will not work if you are not paying attention (i.e. being a dumbass, like me) and in Galaxy Nexus Toolkit you keep hitting #3 for GSM 4.0.2 instead of #9 for LTE 4.0.2. That may have been why I was getting the Status 7 error (gee, ya think?) Do not pass go, do not collect $200!! That'll teach me to not be so friggin' excited about something. Two hours down the tubes. Oh look... the package installed now! All are free to have this for their daily chuckle. :D
[Samsung Galaxy Nexus] strongergravity:
Don't feel bad - I did something similar 2 weeks ago. I was updating my Acer A500 and I forgot to install a driver. Wasted 2 hours banging my head against the wall. Follow direction = sucess in under 10 minutes!
[Samsung Galaxy Nexus] illcat2000:
Not really actually seems worst and I'm using glados which I had awesome battery like with.
[Samsung Galaxy Nexus] DirgeExtinction:
With this update, can any 4.0.4 rom be flashed?
[Samsung Galaxy Nexus] jonstrong:
Success!

I wish I had an answer for you -- but your post was the clue I need to resolve my issue with the "status 7" error. The failed assert in my case pointed to boot.prop (as it sounds like yours did)... So I started to compare your posted boot.prop to the one on my device...and I found 3 extra lines at the bottom of mine -- one blank, and 2 installed by Volume+ : as I recall this is an experimental feature to increase the number of volume steps available to control in-call volume.

Anyway -- I mounted the system directories, edited the file and deleted the last 3 lines, saved, and tried the update again -- and this time it worked perfectly!!! Took a few minutes in CWM, returned to the menu that allowed me to reboot the phone, and then there was another step once I was back in Android (something like optimizing apps, repeated for all the installed apps -- I didn't pay very close attention). After that, it came back to the normal home screen, and checking "about" shows me on 4.0.4, build IMM76K. Sweet!

I'll try it out tomorrow to see how reception and battery life seem. Thanks to everyone here for info, support, tools, advice -- most truly appreciated!

BTW: Last thought -- you might try pulling build.prop out of the zip and comparing it to the one on your phone (put both on PC and use a compare utility, or print out and compare line by line). If there's a difference, you'll have a clue about what's causing the assert to fail and the status 7 error to occur, aborting the update.

AND: for anyone else getting a Status 7 with an assert error: assuming it shows you a file name, it appears to be stating the the named file on your device doesn't match the corresponding file in your update zip. (not the only reason for a Status 7, but it IS the reason for a Status 7 coming from an assert error). Look at the named file, compare to the one in the zip, and I'll bet you'll see a clue regarding what's wrong. Only thought though -- if the one on your device is different, it really may indicate something else on the device doesn't match the patch file -- don't just assume you can replace the file because it's different -- but if the reason is obvious (as mine turned out to be), you might be able to fix it this way as I did. Otherwise -- do as suggested earlier in the thread: reflash an official stock image (see URL early in the thread) that is intended to be the base to which your intended patch update applies.
[Samsung Galaxy Nexus] tvBilly:
Since I've seen this a couple of times while reading this thread I thought I'd mention that this is ICS' way of telling you it's rebuilding the Dalvik Cache. Same thing happened in Honeycomb, but there was no message, just a MUCH longer boot time while the rebuild took place.

And as long as I'm typing, I noticed a bunch of "what's changed between the leaked 4.0.4 from a couple of months ago and this one" questions. I haven't installed IMM76K yet, (wish I was home now; I won't update my GN while I'm working on the road), but I did read a message from someone that has updated to IMM76K saying that Google finally fixed the NFC formatting problem (yea!).
[Samsung Galaxy Nexus] kicker22004:
Ok my Gnexs is already running CM9/unlocked.. But my wifes is still stock 4.0.2/locked, But rooted and CMW recovery. I've already installed the Radios but would like to bring her system to 4.0.4, My question is. Can i install this from her CWM recovery being that she does have it locked? Also unlocking is no option for her..(evil glares from wife :( ). Thanks guys
[Samsung Galaxy Nexus] spectrumfox:
If she already has CMW recovery, then yes you can install this 4.0.4 update. Simply put the ZIP file onto the root of /sdcard , rename it to update.zip, then boot into CMW and apply the update.

Keep in mind though, there's talk of this update maybe not being the "OFFICIAL" update that gets pushed out to everyone. If it ends up not being the official update, then her phone will be stuck off the OTA upgrade path and won't receive or be able to flash any future updates. In which case, you would need to flash and wipe the phone back down to 4.0.2 in order to be put back on the OTA path.
[Samsung Galaxy Nexus] kicker22004:
Thanks for the response... if it's not the OTA that's fine. Just don't wanna have to unlock for this one.
[Samsung Galaxy Nexus] littlewierdo:
I dont have a VNexus but my brother does, a quick search brought me the list of changes.

Changes in 4.04

Noticeably Faster

Android OS bug fixed (in battery stats)

Long-pressing on a blank spot on the last page of app tray bug is gone

New Radios. 3G/4G switching MUCH better. Don't even notice it changing.

Improved signal strength

New Power Menu. New from 4.0.2, familiar to those who have used a stock 4.0.3 rom.

PRIMELA03 Bootloader

Faster boot up time

Auto-brightness Functionality changed. Smooth transition

Holding down camera button now refocuses again

Multitouch issue seems resolved. Screenshot here

Autorotate is faster

Browser performance noticeably improved

Recent apps list opens faster

Miscellaneous camera UI changes

Increased volume

Keyboard fixes

Updated News & Weather app UI

Improved quick controls in browser. New when coming from 4.0.2. Present in 4.0.3
[Samsung Galaxy Nexus] segv11:
Nice update. I'm just curious if this will turn out to be "official" or if it will push me off the OTA upgrade path to which I'll need to flash stock to upgrade.
[Samsung Galaxy Nexus] spectrumfox:
I'm willing to bet this will not be the official 4.0.4 OTA as the battery life isn't as good as prior leaks.
[Samsung Galaxy Nexus] segv11:
Ah well. :-( I got sick of waiting, and the Google download link was so tempting... I guess I'll have some wiping and flashing to do, wherever VZW finally gets around to dropping the _real_ OTA.
[Samsung Galaxy Nexus] spectrumfox:
It's all a part of the game. :)
[Samsung Galaxy Nexus] D623:
Just flashed new bootloader and radio with the CWM flashable ZIP and so far so great on Team Kang M5 rom
[Samsung Galaxy Nexus] illcat2000:
My reception on this builds radio tanked my battery life even with glados kernal tanked I hope this isn't an ota.
[Samsung Galaxy Nexus] D623:
mine improved by 10 db and I also have full bars instead of 2-3 like before
[Samsung Galaxy Nexus] spectrumfox:
Those are good points about the battery, but the fact that there are radio issues as well, such as the phone having a hard time switching back to 4G from 3G, makes me think this update might be flawed and they noticed and took it down.
[Samsung Galaxy Nexus] TheAnarchist1:
I called Verizon support over a PRL issue, and made it to a Tier II service rep last night, who told me, that Samsung has an OTA in the works for this month, which is believed (at least as far as he knew) to be expected to fix a massive amount of the issues which we have had with this device. I have a little faith in this statement, since this build already 'leaked'. They surely do seem to have something in the works
[Samsung Galaxy Nexus] Rnd0209:
this is exactly what I heard from a VZW tech a few days ago but she told me after may.
[Samsung Galaxy Nexus] JayDaKissEP:
Flashed back to 4.0.2 then updated to the latest OTA 4.0.4 radios and my battery life is horrible!!! AOKP M5 with Lean Kernel.
[Samsung Galaxy Nexus] mwalt2:
Why did you flash back to 4.0.2 just to get the radios? Battery life has been the same or better for me with the stock rom and kernel.
[Samsung Galaxy Nexus] littlewierdo:
Strange, I thought the Nexus was all Google... The only thing Samsung does is make the hardware.
[Samsung Galaxy Nexus] Vosko:
so i put on imm76k. previously had imm30b. went to 4.0.2 then upgraded to imm76k. anyway new problem popped up that i never saw before. plugged the phone in to charge. woke it up with the power button and now the touch screen is non responsive. had to pull the battery to get the touch screen working
[Samsung Galaxy Nexus] krazie1:
Can anyone make a flashable zip of the Stock Kernel from this update?
[Samsung Galaxy Nexus] JayDaKissEP:
Because I used the patch, not your zip. I would like to see if other people can test. I have gone back and forth between 4.0.2 and the new 4.0.4 and according to the speedtest.net app, I'm seeing significatnly faster 3g speeds on 4.0.2. I'm sticking with 4.0.2 for now. can anyone else test and confirm?
[Samsung Galaxy Nexus] bloodiedwraith:
I can't confirm the 3G because I live in a 4G area, but the new radios halved the speed I was getting on 4G. I was using the original leaked 4.0.4 radios and was getting between 12-15 down and 10-12 up. As soon as I switched to the new radios I was getting between 5-6 down and 5-6 up. As you can guess, I reverted back to the old radios.
[Samsung Galaxy Nexus] byrds8:
Not sure if the radios are causing that. I am getting the same as I was before if not better. But then again there is no way to tell traffic each time you do a test. I got 26mbs down and 16 up at my house while down the road on a different tower I got considerably less.
[Samsung Galaxy Nexus] Sherwood1:
NO Signal improvement!!!!

Absolutely no signal strength improvement!!!!! Atlease for me. My droid Bionic gets a full signal and my galaxy Nexus barely holds a 3G signal.

My Fault I guess.... I fell for Samsung Specs over Samsung Quality. In my Eyes MOTOROLA is still the king of Android Quality and Build
[Samsung Galaxy Nexus] spectrumfox:
Too bad their bloated UI and skinned interface bogs down their phones performance and prevents them from receiving timely updates.
[Samsung Galaxy Nexus] Sherwood1:
Normally that Update argument would work on me.... But You honestlty think that the Galaxy Nexus ( Verizon Version) Is Zippier than a Droid Bionic? Even with its Bloat it seems faster. Even in Browsing. yes Its Bloated and I hate that. But a STOCK Galaxy nexus is SLUGGISH out the box.

ICS Launcher is sooooooooooo laggy. ( if it wasnt for Apex Id smash my phone LOL )

Again this is in my EYES .... So far The galaxy Nexus... is laggy, battery life is the worst of any droid ive had, and signal stinks.

Again this might just be my phone. I put 4.0.4 on and it seems my model has different HARDWARE because my radios are differnt. I dont have .09 I have .10 for radios.

BTW im just Venting lololol Frustration frustration frustration lolol... But I do love my Incipio NGP Case lol
[Samsung Galaxy Nexus] Dan76:
Wow, that was a little harsh. ...anyway, Sammy sure isn't a model for skinned (touchwiz) interfaces and timely (5 months vzw 4.0.2) updates either...:D
[Samsung Galaxy Nexus] htc_woe_is_me:
How do I go back?

I first apologize for this "question" but it is hopefully somewhat relevant to the thread.

If I want to go back to the 4.0.2 stock radio, can I just do a Nand restore to achieve that? Or do I have to reflash the stock 4.0.2?
[Samsung Galaxy Nexus] spectrumfox:
Harsh? No, honest. :)

The VZW Galaxy Nexus update is coming. And when it does, it'll be worth the wait.
[Samsung Galaxy Nexus] spectrumfox:
You can flash just the radios from 4.0.2. Rootwiki has a thread with a collection of all of the released radios for the VZW Galaxy Nexus.
[Samsung Galaxy Nexus] htc_woe_is_me:
Actually the 4.0.4 (newest one) is decent. Smooth, no problems at all so far. Still monitoring battery and charging times though.
[Samsung Galaxy Nexus] spectrumfox:
Yes, I'm noticing the radios from the newest 4.0.4 leak are pretty good. The build itself sucks and has battery drain issues. I'm currently running CM9 nightlies with Franco milestone 3 kernel and the newest 4.0.4 radios and I'm getting great battery performance.
[Samsung Galaxy Nexus] Realistpm:
i believe previously installing quake is keeping me from installing 4.0.4... i'm getting the system 7 error that others have gotten which stops at this file /lib/libglesv1_CM.so

found that file on this page

http://quake2android.googlecode.com/svn-history/r8/trunk/jni/Android.mk

i tried to rename that file but the same error comes up and stops on that same file (name hasn't changed)

now my phone just sits on the screen that says google with the unlock symbol...
[Samsung Galaxy Nexus] fix-this!:
What update?
[Samsung Galaxy Nexus] spectrumfox:
The pending 4.0.4 or 4.0.5 update that we keep getting leaked OTA's for.

It's coming. Don't know when though.
[Android Apps and Games] Bondos:
Hi All,

This app allows you scare an unexpected victim and record the “evidence” using the device's front facing camera (if available).

While there are many “scare your friends” prank apps on the market, this is the first that allows the user to record the footage (and share with their friends via facebook and twitter)

I would appreciate if you could test this app, and send any feedback to mark@scareapp.com

Attached is the free version APK, but if you would like to try out the pro version, send me an e-mail and I will send it to you.

Thanks in advance,

Mark
[Android Apps and Games] Mr Woolf:
Looks like a good idea, I'll give it a try.
[Android Apps and Games] Bondos:
Wow...how embarrassing!

Thanks a lot!!
[Android Apps and Games] CyaN1de:
While I appreciate your effort, I was not frightened in the least. If I could share the capture here I would to prove it. :-)

When I clicked on "play scare" all I got was a blank black screen.

Might work on small children and the elderly though. ;-)
[Android Apps and Games] Bondos:
Thanks for the feedback! Sorry it didn't scare you...but then again you knew it was coming, so there wasn't really much shock.

..maybe if you scared an unsuspecting victim, you might get more fun from the app!

As for the black screen, I assume the app detected a front camera and turned record on!?

If you have a chance to have a go again, try playing around with the video record settings (like turning off Custom Record)

The defaults settings work on most devices that i've tried, but not all

Thanks again :)
[Android Apps and Games] Bondos:
Hi Guys,

I've just released a new version of ScareApp to the market (and attached)

Some users have informed me that they are having trouble playing back the recorded video.

Could somebody PLEASE help and test the following...

Using any of the "Scare Options" and recording a scare

1) Does a thumbnail show a frame of the video on the screen after the scare (the one which has HAHAHAHA at the top and the play button(s) at the bottom)

2)on the play screen, does anything show? If not, can you click menu and see the options there, and does clicking on the screen cause anything to happen?

2) check if the video plays when looking at it from the "Saved Scares" menu (top left button on the main menu)

3) check if the video exists on the SD card (should be under [SD]/scareapp/videos) and whether it plays from there

4) check if a recorded video plays with different configuration (try turning ON "custom record settings" and changing the resolution and framerate)

(also, don't forget to note what device you are using!)

If you would like a (licence free) copy of the PRO version of the app, sent me a DM with your e-mail and I will forward it to you.

Thanks in advance...I appreciate the help!!

Regards,

Mark Bond
[Samsung Galaxy Nexus] rpolito73:
I just bought the galaxy nexus coming from sgs2 t989. After running speed tests, it says I have extremely low speeds over the air & wifi but when using the phone with data, it doesn't seem slower. Got 6gb/sec OTA & 12 wifi where on sgs2 12 gb/sec OTA & 20+ wifi....

Just wondering if anyone knows if speedtest.net app is accurate per your experiences?
[Samsung Galaxy Nexus] martonikaj:
Its as "accurate" as any speedtest can be. Its not exactly indicative of how fast data actually flows in real-world use.

Keep in mind that the T-Mo branded SGSII has a 42mbps HSPA+ radio, whereas the GNex has a 21mbps HSPA+ radio. Speeds will differ. As for WiFi, I'd say that's just a coincidence, speeds should be ~the same.
[Samsung Galaxy Nexus] xHausx:
It seems to glitch sometimes with the GN and only measure DL speeds for a split second before stopping, I was able to fix it by changing servers though.
[Samsung Galaxy Nexus] Smokeey:
It should be 100% accurate. It's feeding you your actual speeds. It's just that HSPA+ isn't as consistent as LTE or other technologies. I usually get a consistent speed of about 20mbps with 2 bars outside.
[Samsung Galaxy Nexus] rpolito73:
Thanks for the input! Its as fast as I need it to be so I'm fine with what I am getting either way. Would be nice to be able to do some surgery & make a hybrid of the two phones tho... haha

The nexus def looks and operates much better than sgs2.
[Samsung Galaxy Nexus] shadow65781:
I noticed something similar. It jumped to about 3mbs which is sadly typical for the tower closest to my house, stayed there for about a second then dropped to 500kbs for the rest of the dl test, but in real use it is typical of my sgs2 which test around 3mbs
[Samsung Galaxy Nexus] T4rd:
Has anyone else noticed that the bandwidth graphs (where it shows the spikes and how consistent the connection is) on both sides of the actual current bandwidth readout (near the bottom directly below the gauge) don't work most of the time? I'm not sure if it's an issue with ICS or what, but usually it's just a white blur that kind of moves around as the test runs. I've only actually seen the lines on the graph a few times since I've had my Nexus. Pretty sure it always worked good stock, but on most custom ROMs, it doesn't show the lines on the app. Sometimes it does, but not usually. I've played around with the options to see if it fixes it and it doesn't.
[Samsung Galaxy Nexus] RogerPodacter:
I see the graph every time. Turn off 2d hardware cause that breaks the speed test graph.
[Samsung Galaxy Nexus] NCguy:
What do you mean by turn off 2d hardware? I don't see that as an option:confused:
[Samsung Galaxy Nexus] ceribaen:
I turn the 'animations' slider all the way to better performance and seem to avoid the glitching issue with it.
[Samsung Galaxy Nexus] martonikaj:
He means turn off "force GPU rendering" in developer options.
[Samsung Galaxy Nexus] RogerPodacter:
Yeah force hardware acceleration is known to break the speed test graph. But I guess that's not your issue if you didn't know about that setting in the first place.
[Samsung Galaxy Nexus] NCguy:
Correct, didn't know until I read these posts and like you predicted it was turned off.
[Sony Xperia P, U, Sola, Go] unrealboot1:
xperia s has auto briightness which you cannot turn off.it wastes battery it does this by the ambient light sensor,anyone know an app to turn it off?
[Sony Xperia P, U, Sola, Go] K900:
You can change your brightness with any widget. Also from my experience auto brightness saves more battery than it drains.
[Sony Xperia P, U, Sola, Go] unrealboot1:
it dont work. i tried it when i put my finger over the ambient light sensor the brightness still changes i want that sensor to be off
[Sony Xperia P, U, Sola, Go] K900:
Set brightness to fixed.
[Sony Xperia P, U, Sola, Go] unrealboot1:
Tried it doesn't work. I set a brightness but when I put my finger over the sensor it changes the brightness. The brightness change is only like 10% either way from the set brightness. So its like partial auto brightness. But i want to turn it off altogether.
[Sony Xperia P, U, Sola, Go] chopra.harshit:
Go to Playstore and search "Toggle ALS Xperia"

Install this app Disable Automatic Brightness. And please note it needs u to be rooted :)
[Sony Xperia P, U, Sola, Go] tyrien:
Unless you're someone like me and can accomplish most tasks with 0% brightness.
[Sony Xperia P, U, Sola, Go] Pezo:
When set at 0% auto brightness is disabled it seems (to me).
[Sony Xperia P, U, Sola, Go] K900:
Are you sure you're human? I can hardly see anything at 0 brightness, especially under direct light.
[Sony Xperia P, U, Sola, Go] DarrenCarol:
Doesnt this defeat the object of having a HD screen? :S