yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] the_endjinn:
Yeah, am considering boot unlock and flash stock 4.0.2. Means I have to redo all but then I'll get titanium backup for next time etc and will be a real boy.

PITA though
[Samsung Galaxy Nexus] EddyOS:
If it was still going do you there would be threads with people complaining they've not it? Google pulled 4.0.2 for the GN but the code is still out, and have delayed 4.0.3 due to issues on the NS. The next likely update will be 4.0.4>
[Samsung Galaxy Nexus] ogdobber:
the only ota that pulled was the nexus s ota 4.0.3 ...never the gnex 4.0.2. I think people just got confused between the two, hearing something was pulled and they haven't received the latest yet. toro ships with .2, the most notable change was the volume bug fix
[Samsung Galaxy Nexus] efrant:
I don't really like the word "pulled" as, to me anyway, it implies that it was removed from the server -- I would rather "halted from being pushed out", but anyway, this user posted on Jan 8th that he got the update:

Jan 8th: http://xdaforums.com/showpost.php?p=21164441&postcount=2

---------- Post added at 03:42 PM ---------- Previous post was at 03:39 PM ----------

EDIT: ogdobber beat me to it! :)
[Samsung Galaxy Nexus] apratomo:
OK, I think my point is not everybody wants to loose their data, which caused by unlock boot loader, but if they already have then its good for them.

Flashing an update is not long an complicated as far as you already have those requirements.

Yes, I know some people like stock, as I do love stock rom with some root spices
[Samsung Galaxy Nexus] efrant:
Yeah, you're right. That is why I always recommend to people to unlock the bootloader as soon as you take it out of the box, regardless of whether or not you want to root or flash a custom ROM...

Now, assuming you re-locked your bootloader, but have either root or a custom recovery, you are still ok to update without any data loss...
[Samsung Galaxy Nexus] versd:
im still on the 4.0.1 build and factory kernel. When i got the phone, the first thing I did was root it and unlock the bootloader, but have not flashed anything from there. Don't feel the need to! Previous phones have had lag etc which pushed me to overclock etc, but i am not experiencing much if any lag so im waiting until CM9 release and the best optimised kernel at that time.
[Samsung Galaxy Nexus] efrant:
Another one got the OTA to 4.0.2 today: http://xdaforums.com/showpost.php?p=21259818&postcount=233
[Samsung Galaxy Nexus] ogdobber:
My guess is the majority of people "complaining" about not getting the ota must be on anything but yakju....:confused:

also, this is the most popular nexus device to date, ota's aren't going to be as quick (for everbody) as the 1 or s (or until google steps it up)
[Samsung Galaxy Nexus] efrant:
Even when I had my Nexus One, people were complaining, but it took weeks if not months for everyone to get the OTA pushed to them. Whether we like it or not, this has been the norm in the past... That is why hopefully, those who get the OTA updates first will post the update URL so that all of us can update... :)
[Samsung Galaxy Nexus] uranum:
i received the 4.0.2 build ICL53F OTA size 8.8mb before ten hours;)

http://www.google.com/support/forum...b3&hl=en&fid=695d98786861b3b30004b63e3d0feba9
[Samsung Galaxy Nexus] EddyOS:
In which case I stand corrected. It just seems like too big a gap in people getting it for it to seem like it's being rolled out 100%. 1 or 2 people every other day isn't a roll out IMO
[Samsung Galaxy Nexus] tk123456789:
I still don't have 4.0.2. I'm on ITL41F still.
[Samsung Galaxy Nexus] redlik:
Yeap, sad but true. 4.0.1 still

R.
[Samsung Galaxy Nexus] luffyp:
If you guys want the "OTA" update to 4.0.2, here's the incremental update from Google. Just flash like you normally would via CWM. I did and now I'm at 4.0.2 stock (and rooted afterwards).

A bit of warning though, you might find 4.0.2 a bit laggy. You might not. Read this thread. So I suggest you back up your 4.0.1 first.
[Samsung Galaxy Nexus] the_endjinn:
Definitely yakju maguro on ITL41F still. It's obviously coming, from reports, but slow as anything.
[Samsung Galaxy Nexus] 1Speed:
I am still using 4.0.1 with yakju, however I just transitioned over from yakjuzs last night.
[Samsung Galaxy Nexus] BuddyJoe83:
Was still on 4.0.1 untill yesterday where I have experienced random reboots, G/Email bugs and errors.. Very odd all.

SGNexus was working perfect untill yesterday.

Then thought to myself: I'll manually update the phone to 4.0.2, the bugs I have posted shouldn't be fixed just by updating but what the hell, I just wanted the 4.0.2 :)

Installed ADB/Fastboot + updated drivers that come with it.

Unlocked bootloader (check xda +youtube how to) through fastboot, flashed the yakju ICL53F images that are on Google's official Nexus releases page.

Now on 4.0.2, I read on various places that 4.0.3 won't be launched, they pulled 4.0.2 back it seems, so it is waiting for 4.0.4 someday??
[Samsung Galaxy Nexus] case0:
Well last night my phone went into an irreversible boot loop (I'd never rooted or flashed anything etc, 100% stock).

Turns out the only solution was to flash the image from the Samsung site through the ODIN thing. It worked, although it wiped everything on my phone so that was annoying.

Anyway, getting to the point.. I then had a clean install of 4.0.1, and shortly after I got updated to 4.0.2. I'm not sure if I actually want 4.0.2 as people have said it is laggy and has bad battery life, I suppose I'll have to wait and see!

Before this I was stuck on 4.0.1 for ages so I don't think it was a coincidence. Maybe if you want 4.0.2 you can get it this way, although I don't know if it's actually better than 4.0.1..
[Samsung Galaxy Nexus] efrant:
Odin is not the only solution. Despite being a Samsung device, this is still an Nexus Android device -- Nexus Android devices have unlockable bootloaders that allow you to use fastboot (an Android tool, as opposed to Odin which is a Samsung tool) to flash any partition on your device individually. Moreover, Google provides images for all the versions of Android here that are flashable through fastboot.

Additionally, with fastboot, you can also boot a custom recovery, which will allow you to back up your data (for those that get stuck on a boot loop) -- you cannot do this with Odin.

Not sure why people are hung up on Odin as being the only solution.
[Samsung Galaxy Nexus] wadyas:
Just to let you guys know I have just received an OTA update to 4.0.2 today. Well am abit sad that it isn't 4.0.3 but its better than nothing.

I have the true Google build.
[Samsung Galaxy Nexus] pcphobic:
How I updated mine to Android 4.0.2

Part 1: Getting ADB to work with your Android phone and your PC

http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

Tip: To ensure your PC recognises your device and install the ADB and USB drivers, try installing PDAnet first on your PC and on your phone.

Link: http://junefabrics.com/android/download.php

Part 2: Rooting process

http://theunlockr.com/2011/12/14/how-to-root-the-samsung-galaxy-nexus

Part 3: Installing ClockworkMod Recovery

I have tried installing clockworkmod by following the other guides but after rebooting again, it revert back to the stock recovery.

Then I found the solution at this forum posting http://xdaforums.com/showthread.php?t=1357642

Since you have rooted and unlocked your bootloader, you skip to the section "How to install clockworkmod"

Part 4: How to manually update your GSM Galaxy Nexus with the Android 4.0.2 OTA

Since you have already Rooted, Unlocked Bootloader and Installed ClockworkMod, you just have to download the Android 4.0.2 update from Google via a link at this website http://www.androidcentral.com/how-manually-update-your-gsm-galaxy-nexus-android-402-ota and copy over that zip file to the root level of your Galaxy Nexus internal storage space.

Then boot the phone into bootloader mode, then select Recovery and it should go into ClockworkMod Recovery. From there, just select the Apply Update from SD card and let things run their course. Once done select Reboot from the ClockworkMod Recovery menu.

Tip: You might wanna do a backup using ClockworkMod as an insurance. This backup is actually a Nandroid backup.
[Samsung Galaxy Nexus] case0:
Ok well if you want to be pedantic, I should have said 'the only solution without modifying the phone'.
[Samsung Galaxy Nexus] efrant:
When you are finished with the fastboot method, you phone is not modified at all. It is in the same condition as if you used Odin. While there are a few more steps using fastboot, it is more flexible, and gives you more choices. If you want to flash the same image that you did, you can, as it is available. If you want to flash the latest official build from Google, you can.
[Samsung Galaxy Nexus] dello:
Likewise - woke up to an update to 4.0.2 waiting for me this morning! So far i have not noticed any difference whatsoever!
[Samsung Galaxy Nexus] the_endjinn:
4.0.2 this morning, no difference noticed but not really the point. The Nexuses/Nexii/Nexus' are supposed to get updates first, glad to see it happening.
[Samsung Galaxy Nexus] jonathan3579:
Still no update on my yakju here. :(
[Samsung Galaxy Nexus] bunghole:
Received an update just about an hour ago (in Germany).

Version: 4.0.2

Build-Nummer: ICL53F

Size: 8.8 MB
[Samsung Galaxy Nexus] Nooners:
OTA update to 4.0.2

So a few weeks ago I flashed the yakju over the Samsung build i had, used that Version checker app and it said i would be updated by Google. Today I installed the prompted OTA update. When it was done i checked and I was on 4.0.2 and still updated by Google according to that checker app. Guess they are still rolling out 4.0.2. Don't know if anyone else has gotten a 4.0.3 OTA update yet. Well check back if this 4.0.2 update has the bugs the original one did!
[Samsung Galaxy Nexus] EddyOS:
There is no 4.0.3 OTA yet
[Samsung Galaxy Nexus] KahunaSFO:
OTA Update to 4.0.2 just now in Germany

The title says it all.

Nothing obvious changed. (I did not follow the details of this update :rolleyes: )
[Samsung Galaxy Nexus] rock3r:
Got 4.0.2 OTA, but it failed due to having cwm. Installed manually the OTA, lost root. GNToolkit did not apply root correctly, so I manually reflashed Superboot. Piece of cake!

GSM Galaxy Nexus, unbranded on Vodafone Italy
[Samsung Galaxy Nexus] twentyways:
Is there anyway to get the samsung program monitor apk to work on a rooted nexus 4glte. I have root explorer and have tried to add it but when i try to install it it says not installed. I'm thinking the apk needs to be modded or has a Rom conflict. I have no idea though any help or if anyone knows how to add it please post. I have added the apk that i took from my galaxy tab 10.1 if anyone knows how to mod it ~thanks~
[Samsung Galaxy Nexus] twentyways:
bump bump bump please any help
[Samsung Galaxy Nexus] twentyways:
Can anyone help?
[Samsung Galaxy Nexus] twentyways:
I have had more then one task manager on my phone b4 when i didnt like the facrory one and i dont recall seeing a task manager on this gn i like the program monitor because it is a widget that just shows whats running and its one click gone. This cant just be a simple no answer. If someone could point me to a thread on editing apks to work on other rom systems i would appreciate it. I couldnt find one. Thanks for responding.
[Samsung Galaxy Nexus] unremarked:
Most Samsung apps require the TouchWiz interface APIs. More than likely until someone decides to port TouchWiz in its entirety(I.e. a ROM), it won't work no matter what you do.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] twentyways:
? I wish i was more verse in Roms. It seems it should be an easier method but thxs for the response..
[HD2 Android Q&A, Help & Troubleshooting and Genera] hiteshsavaliya:
I have htc hd2

it take so much heat when I use please take me to right way:confused:
[HD2 Android Q&A, Help & Troubleshooting and Genera] matoflash:
Try not using it, then it will not be hot. :)

Seriously, it's got a fast processor and so it gets hot easily, and hd2 has no air conditioning :)

Just if you use it too much, let it cool down once in a while. And don't hold it so firm in your hands, let it breathe a bit.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Funnydwarf:
many roms over here support undervolt, that's the best solution both for battery heating and life, do a search.
[HD2 Android Q&A, Help & Troubleshooting and Genera] JoonatanO:
Your hands are a better thermal conductor than air, so it's better to wrap your hand around the hot part to transfer the heat to your hands. Even better, lick the hot part of the back of the phone then blow some air on it, evaporative cooling will quickly make the phone cool again. It's the same reason why it feels cold when you blow on your hand after dipping it in water.
[Galaxy S I9000 Q&A, Help & Troubleshooting] danielwayne:
Hey Guys,

please excuse my bad english and my stupid questions.

I am not very good in the development things and I don't have much know-how, so I have to post "unnecessary" questions.

I am waiting for ICS for my Samsung Galaxy S Plus, currently running Android 2.3.5. I know that an official version won't be released, so I need a Rom.

At first, I thought that a SGS + is just a "tuned" version of the I9000, but I think this is wrong. So I can't use a I9000- Rom for my I9001.

But is there a rom currently in development? Is somebody portating the I9000 Roms for the I9001?

I can't find another thread to post my question. This is simply:

How can I get a working Rom of ICS for my SGS + (I9001)?

Thank you for your replies and your "patience",

Daniel
[Galaxy S I9000 Q&A, Help & Troubleshooting] pikachu01:
Wait for a dev to port it to i9001 :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] danielwayne:
Sorry, but I don't know what a dev is and I don't know how to port that to i9001...
[Galaxy S I9000 Q&A, Help & Troubleshooting] robogo1982:
Wait until one or more ROM developers (dev, devs) port an existing ICS ROM to I9001.
[Galaxy S I9000 Q&A, Help & Troubleshooting] danielwayne:
Ah, okay, now I've understood. Does it need a long time until such a port exists? I've seen lots of Roms for the I9000, but no one for the I)001... is there no Dev Team that is interested in a port for the 9001? Or is it easyer to take a 9000 rom and port it for the 9001 because it i quite similar!?
[Galaxy S I9000 Q&A, Help & Troubleshooting] kvandermade:
dev=developer...
[Galaxy S I9000 Q&A, Help & Troubleshooting] amashaym:
edit
[Samsung Galaxy Nexus] bobhilton6969:
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.

I've tried different drivers, uninstalling and reinstalling.... no luck.....

Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?

Please help,

Thanks,

Bob
[Samsung Galaxy Nexus] diablonyc2:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
[Samsung Galaxy Nexus] bobhilton6969:
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...

device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....

... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
[Samsung Galaxy Nexus] bobhilton6969:
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
[Samsung Galaxy Nexus] djmcnz:
adb is for android or recovery

fastboot is for bootloader

adb won't recognise the device when it's in fastboot mode.

Try:

fastboot devices

And you don't need adb to unlock the bootloader, the command is:

fastboot oem unlock

So not entirely sure why you're chasing adb...
[Samsung Galaxy Nexus] j1mmyg88:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.

Using win7 64bit
[Samsung Galaxy Nexus] copkay:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
[Samsung Galaxy Nexus] Clancy_s:
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
[Kindle Fire General] samomamo:
Hi, I had beautiful widgets installed and it was not findeing the location automatically, I had to put the zipcode or the city. Now I copied the networklocation.apk from my phone to the kindle's in the system app folder and now it is finding it by geolocation.
[Kindle Fire General] krelvinaz:
I gave this a shot with nogo... CityID it pulls up with is jibberish and non-locational to where I am at.

Just so you know what I did...

o Copied com.google.androidlocation.apk to /system/app

o Rebooted the device

o Used BeautifyWidgets, selected Weather Widget Setting

o Selected Set Location

o Clicked Geolocation

Errors said Geolocation was not on

o told it to use it anyway

o Saved the settings.
[Kindle Fire General] samomamo:
When you copy the app in the settings l, long press the app and choose permissiones and you must have it setup like the pic
[Kindle Fire General] irishmyles003:
Will this work with Google Maps as well?

EDIT: Yup, I am now finding my location in Google Maps as well. Saaweeet!
[Kindle Fire General] krelvinaz:
Used the same permissions as everything else in the /system/app directory

0644
[Kindle Fire General] samomamo:
Well my location is working I don't know why yours doesn't .
[Kindle Fire General] rpw128:
Samomamo, where did you get the NetworkLocation.apk package from, also did you have to adjust anything in Settings.db for any network settings?

I am completely stumped and have been scouring through myriads of posts for some shred of helpful info, so far this post and this one:

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

but have had no luck with either one. I am wondering if the answer lies in from where you got your NetworkLocation.apk. Any help would great! Thanks!
[Kindle Fire General] samomamo:
I got the apk from my T-Mobile Galaxy s2
[Kindle Fire General] irishmyles003:
I downloaded the networklocation apk from the CM7 gapps. The followed the directions and it is now showing my location. I believe it will only show my location if connected to wifi though.

Gapps is found here : goo-inside.me/gapps/
[Kindle Fire General] rpw128:
Solved issue by adding files and editing framework-res.apk

If anyone searching is interested in how I was able to solve this I could not simply add the Google Network Location APK, I had to force the Amazon "framework-res.apk" file to recognize it by editing the '/res/values/strings.xml' with the following lines:

Same ol' disclaimers - I'm not responsible for whatever you do with this info, if you brick your device, its your decision to try and not my fault or issue to fix. This is nothing new I just put the various pieces together from research through other posts, forums, etc. so credit where credit is due.

irishmyles003 and samomamo thank you very much for your input. Though I wish your solutions would have worked I am glad I had this challenge as I think I taught myself a little more about how to mess around and tweak the system a bit.

I still added the NetworkLocation.APK as stated and explained by Samomamo, but I had the do the following steps in order to get the framework to actually react to network location requests, since it kept returning "null".

<<Original>>

<string name="config_networkLocationProvider">@null</string>
<string name="config_geocodeProvider">@null</string>

<<Modded>>

<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>

Steps:

Use ApkTool to pull "framework-res.apk" and decompile

Replace the lines above to match the modded section

Recompile the APK to "unsignedframework-res.apk"

Copy and rename original "framework-res.apK" -> "originalframework-res.apk" (put this file aside in case you need to flash if you make a mistake)

Rename the original and newly compiled files to .zip (so you can extract, edit, etc)

- "framework-res.apk" -> "framework-res.zip"

- "unsignedframework-res.apk" -> "unsignedframework-res.zip"

Extract "resources.arsc" from unsigned and paste (and overwrite) to the "framework-res.zip" file

Rename "framework-res.zip" -> "framework-res.apk"

Push "framework-res.apk" to device (need to mount /system r/w)

chmod 644 (i.e. <rw, r, r> for root explorer)

Reboot and voila it worked (for me at least)!

Sources / Props to the authors of these links:

I could not give correct props because I got these from outside links, but chaoslimits@mydroidworld and the Enable CRT Animation guide at freeyourandroid.com and the APKtool tutorial at miui-au.com

Also if you google using the info above you will find you can also enable the AOSP GB CRT Animation by editing a line in the bools.xml, I tried this and it works! Enjoy!.

EDIT: After applying the framework-res.apk and rebooting I just realized that my accounts were lost. I just had to re-add them via SyncSettings (Market: com.francesandmarky.android.syncsettings) - Amazon, Gmail, and Facebook.
[Kindle Fire General] andTab:
Could someone post the modified framework-res.apk?

Why does it work for some but not others?
[Kindle Fire General] rpw128:
andTab, I tried but the max filesize is 8 mb for APK files, the framework-res.apk is 27-31 mb. I couldn't figure out why the original posters were able to do it by just adding the files. When I unpacked the APK it was intentionally set to null not allowing usage of the google location framework.

xxx.multiupload.com/5FJ4ZTH6TX (take out the x's, it wouldn't let me post the address b/c I am new)
[Kindle Fire General] atomiclama:
Thanks for your work guys...

I downloaded and applied this frame work apk, the crt animation is now enabled, but google maps still not finding my location in the middle of Los Angeles.

Hmmmm
[Kindle Fire General] rpw128:
You still need NetworkLocation.Apk from Gapps put into /System/App (also run it from your SD Card), then reboot. The adjusted lines in the Framework-Res points to this framework.
[Kindle Fire General] atomiclama:
So my evo 3d is running ICS, can I still use the file? Or could someone post a working one?
[Kindle Fire General] rpw128:
I'm not too sure, if you're working off stock the Kindle Fire uses 2.3.4 so I would use the 8/28 version from the website irishmyles003 provided.
[Kindle Fire General] atomiclama:
Hmm still not having a whole lot of luck.

I downloaded the networklocations apk from gaps of the correct date. Also installed the updated framework. Like I said Im seeing CRT change.

I've set up the geo location through beautiful widgets.. but still not finding location.

What am I missing?

thanks

also when I placed the network locations apk I set correct permission and tried to install it, it said application not installed. Could to be part of the problem?
[Kindle Fire General] krelvinaz:
Placing it in the /system/app area is installing it.

Make sure you reboot for the system to see it though.

Note: I've not tried this patch...
[Kindle Fire General] rpw128:
I'm not exactly sure why it isn't working for you. I spent a few days looking at logcat's and forums. Don't forget to change the permissions (mentioned earlier in this thread) to 644.