yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dipdeol:
My wife just got the 4.0.2 OTA on her nexus in Canada (yakjuux, unlocked bootloader, rooted, stock recovery) last night. I haven't received it on mine yet, but immediately after the update, any time she tries to click on an app in the market to get the details view, the market force closes. I tried clearing data and cache for the market and wiping /cache from recovery, but no luck. Clicking "Uninstall updates" for the market (version 3.4.4) makes the problem go away temporarily, but it returns shortly thereafter when the market updates itself again. Users in other forums are experiencing similar problems with the market after the same OTA for yakjuux. Does anybody have any ideas that don't involve a data wipe? I didn't re-root it after the update. Could this be related?
[Samsung Galaxy Nexus] leobg:
Try clearing market app data from settings/apps.
[Samsung Galaxy Nexus] avrus:
I didn't realize I had the same issue until I saw OPs message. Clearing the data and cache as well as force stopping market and rebooting does not resolve the issue.

Edit: To clarify, my device is stock and non-rooted.
[Samsung Galaxy Nexus] Dr Tone:
What a kick in the balls.

You get it held back from you for months and then when they release it, it has serious issues in comparison to the straight yakju builds.

I'm glad I moved to yakju.
[Samsung Galaxy Nexus] OpusX11:
Interesting, I don't have the update available. Still at 4.0.1 on stock yakjuux (non-rooted, locked bootloader still) and just checked..
[Samsung Galaxy Nexus] dipdeol:
I already tried this. No luck

I don't have it on my phone yet, but my wife got it last night. I'm sure it will come soon.
[Samsung Galaxy Nexus] OpusX11:
What I did notice today was that I had to accept the Market Terms/conditions again (I did not clear data) and the version is 3.4.4 which is what I thought I already was on, but perhaps I was wrong
[Samsung Galaxy Nexus] Valynor:
OP, go one step further and do this:

-clear download manger AND market data AND cache

-uninstall market update (this reverts to your ROM market version)

-reboot without doing anything else

Market will autoupdate itself again after a while. Downloading a free app may speed this up.
[Samsung Galaxy Nexus] avrus:
Instructions followed, does not resolve issue.
[Samsung Galaxy Nexus] Valynor:
:-(

If you can't think of anything else, reset to factory default or install the 4.0.2 yakju images directly from Google. This should certainly fix it.

Link: http://code.google.com/intl/de-DE/android/nexus/images.html
[Samsung Galaxy Nexus] virtualcertainty:
Great... I suppose this means that Google will cease the update again for another 4 weeks.

The really unfortunately part is that Google has been busy weeding out bugs in releases that they thought were ready 8-12 weeks ago. That means all work on future releases (4.1, 4.2, etc) has probably been moved back and delayed. Somewhere in Mountain View, a middle management executive that pressured devs to cut corners and make deadlines now has some tough questions to answer.
[Samsung Galaxy Nexus] al2k86:
I got the update yesterday and in addition to Android Market crashing, NFC options seem to be missing now.

This is probably the reason Market is crashing because when I preview the crash report it says "java.lang.NullPointerException" in the "Nfc.java" source file....

I have to say I'm pretty disappointed having to wait months longer to get the update only to be worse off than 4.0.1. I guess that's what I get for being too lazy to look into rooting and flashing a yakju build.
[Samsung Galaxy Nexus] grumphy:
Hi there, struggled all day with this. Found out that it is not a good idea to remove gapps (which I don't use anyway) with the system app remover.

re-installed gapps and the issue seems to be solved (for now)

AOKP B27, no custom kernels etc.
[Samsung Galaxy Nexus] rylake:
Weird issues. When I was looking at the update zip file, I definitely saw the nfc.apk included. Maybe there is a problem with the update script and how it is being applied. Anyways, try checking out the update file and even manually pushing the nfc files to the phone and see if that fixes any of the issues. You will probably need root access to push them to the correct directory though.
[Samsung Galaxy Nexus] aleks07:
Where is the update.zip located?
[Samsung Galaxy Nexus] dipdeol:
Definitely looks NFC related:

03-02 08:45:33.767 E/NFC (3094): could not retrieve NFC service

03-02 08:45:33.767 W/dalvikvm(3094): threadid=1: thread exiting with uncaught exception (group=0x40a581f8)

03-02 08:45:33.775 E/AndroidRuntime(3094): FATAL EXCEPTION: main

03-02 08:45:33.775 E/AndroidRuntime(3094): java.lang.NullPointerException

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.google.android.finsky.utils.Nfc$IcsNfcHandler.<init>(Nfc.java:165)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.google.android.finsky.utils.Nfc$IcsNfcHandler.<init>(Nfc.java:161)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.google.android.finsky.utils.Nfc.getHandler(Nfc.java:36)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.google.android.finsky.activities.DetailsDataBasedFragment.onActivityCreated(DetailsDataBasedFragment.java:113)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:891)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1080)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:622)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1416)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:420)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.os.Handler.handleCallback(Handler.java:605)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.os.Handler.dispatchMessage(Handler.java:92)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.os.Looper.loop(Looper.java:137)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at android.app.ActivityThread.main(ActivityThread.java:4340)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at java.lang.reflect.Method.invokeNative(Native Method)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at java.lang.reflect.Method.invoke(Method.java:511)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)

03-02 08:45:33.775 E/AndroidRuntime(3094):	at dalvik.system.NativeStart.main(Native Method)

03-02 08:45:33.783 W/ActivityManager(196): Force finishing activity com.android.vending/.AssetBrowserActivity

03-02 08:45:34.306 W/ActivityManager(196): Activity pause timeout for ActivityRecord{41834f80 com.android.vending/.AssetBrowserActivity}

03-02 08:45:37.228 W/ResourceType(196): Invalid package identifier when getting bag for resource number 0x7f0c0008

03-02 08:45:39.556 E/CACHE (1940): cleared
[Samsung Galaxy Nexus] rylake:
http://android.clients.google.com/p...160b66b23.update_yakjuux_ITL41F_to_ICL53F.zip
[Samsung Galaxy Nexus] aa_chow:
I just got the OTA update (yakjuux 4.0.1 --> 4.0.2) 30 minutes ago, despite reading problems with NFC and Market crash. After the update, I had the exact problems: NFC is missing and Market crashing.

I "fixed" it by doing the following. I cleared Market data and cache and uninstalled Market updates. I then opened Market again, but the problem returns.

I then did a factory reset (via Settings > Backup & Reset > Factory data reset). Voila! NFC is working again (option is there, and confirmed with NFC-enabled card), and Market no longer crashes.

I know this is not the ideal fix as it requires a reset, but at least the phone is usable again.

Hope this helps!
[Samsung Galaxy Nexus] avrus:
What gets blown away / what do you have to restore when you do a factory reset? I'm assuming all your applications (which will redownload), pictures any stored documents, application settings and your contact list and calendar (which should resync with Google) ?
[Samsung Galaxy Nexus] rylake:
Maybe someone with this build can try going into Settings>Apps>All and disable the nfc service, then re-enable it. It may trigger it to preform correctly. Just a thought.
[Samsung Galaxy Nexus] EP2008:
So, is this problem affecting all 4.0.2 users, or just a few, or just Canadians? LOL
[Samsung Galaxy Nexus] dipdeol:
As far as I can tell, this is affecting all Canadians (yakjuux).
[Samsung Galaxy Nexus] al2k86:
@aa_chow

Thanks for the info.

IMO though, if I have to do all that to get Market and NFC to work again I may as well just root it and flash. Since 4.0.2 has been out for a while, I can only believe it was something Samsung did that messed up the update. Hopefully by putting a Yakju image on it I'll get something that Google has QA'd themselves and get timely updates.
[Samsung Galaxy Nexus] dipdeol:
I've been tempted to go flash yakju myself for quite some time. Is there an easy way to do that while keeping the new radio from the 4.0.2 OTA? Will that prevent me from getting future OTAs on yakju?
[Samsung Galaxy Nexus] leobg:
I was going to suggest factory reset, but saw people already did this and it worked. Sorry, I guess you guys have to go thru the hassle.

I am on CM9 nighties and am not "affected".. :)
[Samsung Galaxy Nexus] aa_chow:
I did a backup (not Nandroid, just file copying) before I hit reset, just in case. After reset, all apps are automatically re-downloaded, and most settings (e.g. saved WiFi access points, keyboard sound/vibration settings, etc.) are restored. Contacts and calendars and pictures on Google Picasa/Google+ were automatically resynced.

The things I have to re-enter are my exchange/imap email account settings, and settings/login info in each app (e.g. Facebook, Twitter, etc.).

Again, it does fix Market crash and NFC, but not ideal.

---------- Post added at 04:30 PM ---------- Previous post was at 04:18 PM ----------

I agree. I was about to flash Yakju today and was making a Nandroid backup. Right after unlocking bootloader (and hence device wipe), I got the OTA notification and installed. Since I wiped once already, I may as well try wiping again; luckily, it fixed the problems.

---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------

From what I have read on XDA, you can flash yakju and then flash the new UGLA4 radio (or in fact another radio of your choice). If you flash a different radio, it will prevent you from getting future OTAs on yakju (again, from what I have read on XDA).

All radios are available at http://xdaforums.com/showthread.php?t=1405345
[Samsung Galaxy Nexus] rajivd:
I just cleared all data for markey app, uninstalled updates and launched market again. that seemed to fix the issue and I was able to install a free app. I haven't yet been told to update market app again. so not sure if it will start crashing once I update it again.

[EDIT]: Well.. that didn't last for too long. Just got notification that two apps had updates available and when I tried to update google+, market started crashing again. I will try factory reset route once I reach home from wifi. don't want to update month's worth of emails over data connection ...
[Samsung Galaxy Nexus] OpusX11:
I'm on yakjuux and have yet to receive the update. For those that do have it, are you experiencing the lag the others have reported on 4.0.2 ?
[Samsung Galaxy Nexus] dipdeol:
Is 4.0.2 supposed to be worse than 4.0.1? 4.0.1 was already pretty laggy. I've only had the update for a couple of hours and haven't stressed it much, but so far it seems a bit snappier to me. There is still a bit of lag when swiping through the app drawer/widgets, but its no more than it was before the OTA. The multitasking menu seems to popup a lot quicker now. What sort of scenarios are supposed to cause lag?
[Samsung Galaxy Nexus] OpusX11:
I think it was around keyboard lags:

http://code.google.com/p/android/is...ag&colspec=ID Type Status Owner Summary Stars
[Samsung Galaxy Nexus] dipdeol:
I had landscape keyboard lag in 4.0.1. It was so bad it was unusable. I just tried now and it seems to lag a bit, but it's much better than before. Take this with a grain of salt though since I haven't played with it too much.
[Samsung Galaxy Nexus] yongwanee:
SOLUTION

I found a solution that elegantly fixes the problem.

I didn't notice the NFC option going missing, but searching through Google Groups reported past issues with buggy Market.apk from Google themselves, and I'm pretty sure that the issue lies with Google's provided version of the Market.

I'm on Bell Mobility, by the way, completely stock, and had the Market crash after the 4.0.2 OTA update.

-- SOLUTION --

As people have said, reverting the Market's version to the previous version will fix the problem. But also as people have said, this is temporary because the Market will auto-update. So,

1) Use a file manager and navigate to

system/app

Then find the file "MarketUpdater.apk"

Either backup the file somewhere else and delete it, or rename it.

This will ensure that when the Market is updated again to a stable version, you can restore this file to update.

Then proceed to revert to the old version of the market.

2) Settings > Apps > All > Market

Then click "Uninstall updates"

Hope this helps!
[Samsung Galaxy Nexus] scroucher:
Any chance Bell or google will fix this problem in the near future?
[Samsung Galaxy Nexus] virtualcertainty:
Bell? Bell has nothing to do with the Nexus.

Google? One would hope so.
[Samsung Galaxy Nexus] EP2008:
Does this require root?
[Samsung Galaxy Nexus] Haesslich:
Given you're mucking around with system files, of course you need root.

At that point, you might as well flash to yakju.... since you're already unlocked.
[Samsung Galaxy Nexus] EP2008:
Yeah, point taken.
[Samsung Galaxy Nexus] CASz:
double darn on the NFC loss. If I have to factory reset I may as well root a the same time.
[Samsung Galaxy Nexus] MerkurMan:
Bummer. I was so anxious for the OTA that I installed it without thinking yesterday. Usually I check the forums for reports and user experiences before installing any software updates.

Now I guess it's finally time to root and ROM this sucker. Something I never had to do on my N1, because it just worked. Something I was hoping I didn't have to do to this thing. I guess the word Nexus doesn't mean anything any more. :(

My only concerns are with backing up my apps. There are some apps that I don't wish to update to the latest version, for whatever reason. Is there any way I can backup all my current app versions so I can go back to them after I wipe the device?

Thanks! And I hope this goes smoothly...
[Samsung Galaxy Nexus] catfish:
I am thinking of going from Docomo's rom to yakju.... goolgle rom but wasn't sure if I should and after reading of all of the issues after changing the rom I'm less sure if I should.
[Samsung Galaxy Nexus] gotak:
I can't post links so...

code.google.com/p/android/issues/detail?id=26358

Canucks, hit that star button! Lets get some attention from Google. God knows any updates would take them ages to roll out.
[Samsung Galaxy Nexus] Shawn_230:
This is beyond ridiculous... I flashed 4.0.2 manually and been waiting for 4.0.3 to be pushed out or at leas the image to be posted on Google code.

I was getting angry that we didn't have 4.0.3 pushed out yet to yakjuu, but now I find out 4.0.2 hasn't even been pushed out to yakjuux until this very day, and now that it has it breaks NFC and much more importantly your access to Market.

This is lame, defeats my main reason for buying a Nexus phone. I want the latest update when every other Galaxy Nexus gets it, and I want it to not break something as fundamental as Market access. I don't believe that is too much to ask of the flagship Android phone.
[Samsung Galaxy Nexus] gotak:
It has been a mickey mouse show for the galaxy nexus in Canada.
[Samsung Galaxy Nexus] bourne-nolonger:
I am honestly surprised to see this issue affecting so many people!

Pretty sad that an update breaks something as crucial as the Market.

Hopefully Google is prompt in bringing a resolution to this issue.

I managed to get Appbrain installed so I can use that until Google can fix the issue.
[Samsung Galaxy Nexus] virtualcertainty:
Good idea. Can't hurt to communicate our frustration through the proper channels - voting up the bug.
[Samsung Galaxy Nexus] aa_chow:
In my opinion, the Nexus is a developer phone, not really meant for consumers who just expect their phones to "just work". Because it is a developer phone, things will not work and part of the fun of the Nexus is to figure out how to fix things.

If you want a phone that "just works", get something else that has updates that get pushed later, after all the bugs are fixed.
[Samsung Galaxy Nexus] ChrisAG:
If it's a "developer phone" why does every carrier market it as a high-end mass-market phone?

Even Google, in their own advertising, emphasizes the cool features to the masses ("check out 'Face Unlock!' Impress your friends!"), not so much to the developers.
[Samsung Galaxy Nexus] kalinf:
That might be your opinion but that is certainly not how Google is marketing the phone within the UK in their TV ad campaign or in the full page adverts in newspapers. Those adverts have appeared very frequently recently, enough that all my non-techy friends are all aware of it and the gimicky ICS face unlock.

Those people rightly won't be very pleased at paying £500 for a phone that has random reboot/boot loop issues that have been ongoing from day 1. Let alone updates that take a long time to arrive and then break fundamental things that should have been noticed in testing almost immediately.
[Samsung Galaxy Nexus] virtualcertainty:
This is absolutely a mass market phone, not just bleeding edge developer phone. It is the only Android phone on every retail shelf in the world. The prime mission of the Nexus may be to drop ICS in the hands of manufacturers and app developers and assist them in the smooth transition to the latest OS with their own devices/apps, but that doesn't waive any expectation of QA. The Nexus One may have been a dev-only phone, but Google left that business model behind two years ago.
[Samsung Galaxy Nexus] MerkurMan:
And to add to that, I never experienced a major fundamental feature being rendered incapacitated by an OEM software update in the two years I owned my Nexus One. It performed flawlessly (aside from the buggy touchscreen, which was a HW issue) and "just worked."

Here's hoping Google hears our cries and doesn't try to pawn off responsibility towards Samsung.
[Samsung Galaxy Nexus] fnord:
I spoke with TELUS tech support this morning. They were aware of the issue (I wasn't the 1st person to call in). I was told that Google was also aware, and because the issue was "severe" they expected a fix shortly.

Who knows how quick they'll respond, but figure the more people that call their carrier, the harder the carriers will push back for a fix.
[Samsung Galaxy Nexus] aa_chow:
I see. I was not aware of TV ad campaigns in the UK.
[Samsung Galaxy Nexus] MerkurMan:
Not to jump down your throat, but Bell promoted the GN pretty heavily in print and TV ads for quite a while during its release, and they were touting the phone as a premium device for the everyday person.

In any case, I don't wish to argue semantics and just hope that we can put this all behind us soon! :)
[Samsung Galaxy Nexus] efrant:
The TV ad campaigns were here in Canada as well...
[Samsung Galaxy Nexus] billsan101:
im on Virgin Mobile in Quebec with my GN and still on 4.0.1, this is ridiculous

Anyone else on virgin?
[Samsung Galaxy Nexus] Socamonarch:
I had to do a factory reset to restore the NFC as well..
[Samsung Galaxy Nexus] bourne-nolonger:
I just checked and NFC is gone for me as well.

I never noticed it before because I don't really use it.

I wonder why it isn't showing?

Was this intentional?

Or just a bug to go along with the market crashing?

btw.. You can still push app installs from the Android Market website down to your phone with no issue.
[Samsung Galaxy Nexus] matthewr87:
So you are on Telus and have received the OTA update? I am also on Telus and have not received a notification. In light of this bug I will probably not install it at this juncture anyway.
[Samsung Galaxy Nexus] aa_chow:
So can someone who is familiar with Android update process confirm my guess? It doesn't solve the problem but just curious.

We know 4.0.1 -> 4.0.2 update is the causing NFC + Market crash problem, but 4.0.2 itself is fine (confirmed by factory reset). So perhaps their is a bug at the "optimizing applications" stage? Something to do with not compiling the NFC java code correctly (post #16 of this thread)?
[Samsung Galaxy Nexus] dipdeol:
I tried wiping the dalvik cache before I did the factory reset, and it didn't change anything.
[Samsung Galaxy Nexus] kappa2:
Just got a update for the market to 3.4.6 which is now the Google play. No more force closing.
[Samsung Galaxy Nexus] OpusX11:
Same with me, no update on yakjuux. I check periodically out of curiosity and I always am told that I am up to date (4.0.1). Perhaps they pulled the update?
[Samsung Galaxy Nexus] bourne-nolonger:
So Google appears to have "fixed" the crashing issue by replacing the Market all together with "Play Store".

Am I the only one that didn't know this was coming?
[Samsung Galaxy Nexus] matthewr87:
I was not aware of this either. I tried downloading a free app yesterday and was greeted with a Google Play user agreement message. At first I thought it said Google Pay or something like that and was confused because I was sure I clicked on a free app. After I clicked accept it downloaded a 7mb update.
[Samsung Galaxy Nexus] jeff72k:
I got the update to yakjuux 4.0.2 and after that I had some issues with the Market force closing when adding apps also.

I did resolve the issues by doing a "Backup & reset" "Factory data reset" on my phone. This reset my phone and fixed the Market issue. FYI (realize this erases all your data so back your stuff up).

yakjuux Android 4.0.2

PRIMEKK15

ICL53F.I9250UGLA4

I also just noticed I have the updated Google Play "Market" now too, but it did work before this after I did the Factory reset.

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

Here is the link information for the yakjuux 4.0.1 to yakjuux 4.0.2 update:

http://xdaforums.com/showpost.php?p=23119522&postcount=160

That main thread link is here:

http://xdaforums.com/showthread.php?t=1419170
[Samsung Galaxy Nexus] matthewr87:
Still no 4.0.2 for me on Telus in Canada. Anybody else receive the OTA update on Telus?
[Samsung Galaxy Nexus] virtualcertainty:
The fact that you are on Telus is irrelevant to Nexus updates. The 4.0.2 update for the Canadian Nexus variant appears to have been stopped by Google due to bugs (breaking NFC).
[Samsung Galaxy Nexus] matthewr87:
Oh I see. It just seemed to me that people on different carriers started receiving notifications on slightly different days. Also, I thought that the update to the "Google Play" store fixed the NFC issues? Or is that something unrelated?
[Samsung Galaxy Nexus] virtualcertainty:
A couple of sites incorrectly reported carrier specific rollouts, so the perception of that happening still exists. Around here, where people go bonkers at the first sign of an OTA update, people reported devices from all carriers began getting updates at the same time. It just takes a while for everyone to get it.

The updated broke NFC and that seemed to affect the market. The Google Play update seemed to resolve the crashing issue, but NFC remains broken for those who got it.
[Android Q&A, Help & Troubleshooting] 3PIC:
WELL, guys ive ported a rom from desire to defy and there is this one error in CWM....pic attached

View attachment 926974

....I don't know wat to edit in the updater-script so that I can get the rom working plzz someone help

And here is a link to my boot.img and updater script

http://db.tt/5EPodBOx