Just got my Nexus 4 activated on Rogers. Is there any reason not to do the OTA 4.2.2 update? I know about LTE being disabled in 4.2.2 - anything else that I need to be aware of?
thanks
thanks
Feb 27th, 2013 9:43 am
Feb 27th, 2013 10:13 am
No other reason not to. It a) improves battery life significantly, b) improves/fixes the bluetooth issue and c) other minor changes.
Feb 27th, 2013 11:27 am
You will need to flash factory image. Refer to the XDA thread it has all your answers
Feb 27th, 2013 12:21 pm
He has busy box installed and no custom kernel. See his previous posts...martinwales28 wrote: ↑Did you check out this thread? http://forum.xda-developers.com/showthr ... ?t=2145848
Sounds like you are:
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Section C: Let’s get back to stock
OR
Option #3) Forgo the OTA entirely and flash the JDQ39 Factory Image in fastboot. https://developers.google.com/android/n ... ages#occam
If you need help with this follow efrant's guide
wilsonlam97 wrote: ↑I have a feeling you installed busy box because some root app asked you to do it.
Feb 27th, 2013 12:50 pm
I know but of the scenarios in the thread this matched his situation best because of the modifications.
Feb 27th, 2013 7:07 pm
Feb 27th, 2013 8:28 pm
Feb 27th, 2013 8:42 pm
Well you got it correct there. Google requires it be linked to your Gmail account/Google Wallet account. Reason being for proof of purchase that it was purchased from them. Sorry, it depends. So if bought from the Play Store, yes you need to have proof of purchase aka your Gmail/Google Wallet account linked to the purchase.
Feb 28th, 2013 9:36 am
Thank you, in the past to tether other device to my nokia phone. I have to do nothing but provide a password for the other device.djemzine wrote: ↑Video is being uploaded for this. I enabled my data connection on my Galaxy Nexus. Then connected my Nexus 4 to my GN via BT and vice versa.
Then I went into the settings via the BT connected devices and viola. The video will explain the rest.
Edit: Can't you take out your sim card from your Nokia phone or whichever device has the sim card + data plan and just move it to your Nexus 4? Also, BT tether setup on the Nokia phone and N4 might be different since its not the same eco system as per my video...
Yes
Feb 28th, 2013 9:40 am
Just want to add that the seller can call google and get the warranty be transferred to you. I bought mine from kijiji and had to do that.djemzine wrote: ↑Well you got it correct there. Google requires it be linked to your Gmail account/Google Wallet account. Reason being for proof of purchase that it was purchased from them. Sorry, it depends. So if bought from the Play Store, yes you need to have proof of purchase aka your Gmail/Google Wallet account linked to the purchase.
If the phone was bought from a carrier/retailer - Fido, Virgin, The Source, Wind then a receipt should suffice.
I would check with the seller from Kijiji to double check. PS might be beneficial to buy one off a RFD user with BST Feedback. That way you know its legit and will be a smooth transaction! All the best!
Feb 28th, 2013 10:24 am
No other paper work for that? Will Google send the new owner a proof that the warranty has been transferred or?martinwales28 wrote: ↑Just want to add that the seller can call google and get the warranty be transferred to you. I bought mine from kijiji and had to do that.
Feb 28th, 2013 10:54 am
Seller called and he told me "filed a case to have it transferred to your name. The agent couldn't do it at the time, so she told me that she will escalate it to a higher support to assist the ownership transfer"
Feb 28th, 2013 11:26 am
Thanks for the heads up. Will pass this along to a friend of mine.martinwales28 wrote: ↑Seller called and he told me "filed a case to have it transferred to your name. The agent couldn't do it at the time, so she told me that she will escalate it to a higher support to assist the ownership transfer"
Took about half a day and then I had to call to verify information and that it was indeed transferred and then initiated an RMA.
Google support is great every agent i've dealt with takes ownership of the problem and makes sure it gets resolved.
Feb 28th, 2013 11:44 am
Feb 28th, 2013 1:31 pm
Feb 28th, 2013 1:45 pm
I thought this updated version takes it from beta and makes it better? Or at least what I read online. Shall keep note of this. ThanksSushi Roll wrote: ↑An update just came out for Google Chrome and I recommend people avoid it. I hit the update button on the play store and regret it. Last version was rock solid stable, very smooth, and with just a tiny bit of lag. New version is unstable (already froze once for me), stutters like crazy during scrolling, has "fuzzy" looking text when a web site has small fonts, and is buggy at rendering web sites that used to be fine before (mobile version of The Verge only renders a quarter of the more button). This should have stayed in beta. Not ready yet for prime time
Feb 28th, 2013 4:12 pm
+1 for me. It's been stable and blazing fast but the font seems fuzzy, everything else in the update is great for me though. Hope they fix the fuzzy looking issue.Sushi Roll wrote: ↑An update just came out for Google Chrome and I recommend people avoid it. I hit the update button on the play store and regret it. Last version was rock solid stable, very smooth, and with just a tiny bit of lag. New version is unstable (already froze once for me), stutters like crazy during scrolling, has "fuzzy" looking text when a web site has small fonts, and is buggy at rendering web sites that used to be fine before (mobile version of The Verge only renders a quarter of the more button). This should have stayed in beta. Not ready yet for prime time
Feb 28th, 2013 4:24 pm
Feb 28th, 2013 5:01 pm
Your reply prompted me to do research on this since mine was nowhere near blazing fast. Turns out the update somehow got messed up with my previous version of Google Chrome due to it's stored cache files. To fix it, I went to settings / privacy and clicked on the "clear browser data" button near the bottom. I then checkmarked all the fields in the next screen and it wiped my Google Chrome cache.
Feb 28th, 2013 5:54 pm
There are currently 2 users viewing this thread. (0 members and 2 guests)