Related
The official update before the official release. Here's the link: http://android.clients.google.com/p...c0.signed-sojus-GRJ90-from-GRJ22.39fe4c59.zip. Enjoy!
What it does: "These enhancements should increase 4G data speeds and signal strength for users. The software update also improves Wi-Fi connectivity, speakerphone audio quality and adds TTY support for the deaf and hard of hearing,” the wireless carrier announced at that time.
Instructions:
1. To begin, download the update from the link above and rename it to update.zip (.zip being the extension.).
2. Copy the update to the root of your SD card and reboot your phone into recovery. (Hold the Volume up button as you press the Power button.)
3. Choose Recovery from the bootloader menu and you will see a triangle with an exclamation mark.
4. Press the Volume up key a few times till the recovery screen shows up.
5. Once in recovery, select Apply sdcard update.zip and this will begin the flashing process.
6. Once the installation is complete, simply reboot your device!
That’s it, your device should now boot up with the new 2.3.5 firmware!
It also removes the free hotspot apparently. Which was bound to happen sooner or later.
Also, this isn't the first thread on it.
Is it really required to name it update.zip? When you go through stock recovery it lets you pick whatever filename you want.
This was suppose to be a "Pure Google" phone. Why is Sprint screwing around with the build and modifying it to block the HotSpot feature? This is why I got the phone in the 1st place. I guess I'll live on 2.3.4 till further notice.
skizzled said:
It also removes the free hotspot apparently. Which was bound to happen sooner or later.
Also, this isn't the first thread on it.
Click to expand...
Click to collapse
wireless tether for root users... http://code.google.com/p/android-wifi-tether/
agonzalez1010 said:
This was suppose to be a "Pure Google" phone. Why is Sprint screwing around with the build and modifying it to block the HotSpot feature? This is why I got the phone in the 1st place. I guess I'll live on 2.3.4 till further notice.
Click to expand...
Click to collapse
check your contract.
Is this just a normal update that won't wipe /data?
Stock Rooted ROMs (GRJ90) are here: http://forum.xda-developers.com/showthread.php?t=1078213
You wont lose data but I recommend atleast wiping cache and dalvik cache.
I pushed the volume up key forever and it still never brought up recovery. Am I doing something wrong??
Sent from my Nexus S 4G using XDA App
I'm assuming since you need to boot into recovery to flash this update that you also need to have a rooted phone?
Yes you do have to boot into recovery but you don't need a rooted device.
Nevermind I figured it out. Updated with 2.3.5 and now rooted again
Sent from my Nexus S 4G using XDA App
I like the update...but I like the option to blacken the messaging app background. Any way I can change that??
Sent from my Nexus S 4G using XDA App
dblkspecial said:
I like the update...but I like the option to blacken the messaging app background. Any way I can change that??
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
i thought tht was just in Cm7 based stuff
agonzalez1010 said:
This was suppose to be a "Pure Google" phone. Why is Sprint screwing around with the build and modifying it to block the HotSpot feature? This is why I got the phone in the 1st place. I guess I'll live on 2.3.4 till further notice.
Click to expand...
Click to collapse
check your contract buddy, google builds it so if need be it can be used in their phones. go ahead and stay on 2.3.4 not like you can root your phone and use one of the apps in the market that still work and even tether 4g "for free".
I know you have some sort of entitlement to get something everyone else pays for. I can guess that your one of those people that write bad reviews for amazon free apps, just cause you wanted something else
BrianDigital said:
check your contract buddy, google builds it so if need be it can be used in their phones. go ahead and stay on 2.3.4 not like you can root your phone and use one of the apps in the market that still work and even tether 4g "for free".
I know you have some sort of entitlement to get something everyone else pays for. I can guess that your one of those people that write bad reviews for amazon free apps, just cause you wanted something else
Click to expand...
Click to collapse
wow there was really no need for this. my guess is his resentment towards sprint making moves to block tethering is real simple. the nexus on tmobile has free tethering and has had it since launch. the nexus s has had free tethering and still does, the nexus s 4g ships with 4g tethering, yet day 1 we get an update to stop that. whatever i can understand not overloading their already poor 4g network, but now the nexus s 4g is teh only nexus phone without tethering. i mean hell even chromebooks get a year of verizon tethering for free.
shabbypenguin said:
wow there was really no need for this. my guess is his resentment towards sprint making moves to block tethering is real simple. the nexus on tmobile has free tethering and has had it since launch. the nexus s has had free tethering and still does, the nexus s 4g ships with 4g tethering, yet day 1 we get an update to stop that. whatever i can understand not overloading their already poor 4g network, but now the nexus s 4g is teh only nexus phone without tethering. i mean hell even chromebooks get a year of verizon tethering for free.
Click to expand...
Click to collapse
How i see it aslong as im able to tether, im fine. Thats why i use the google tether apk... its all good i aint complaining lol. Remember sprint has true UNLMT data not like the other carriers that say unlimites data yett u only get 2gbs to start after that its a charge lol... where does unlimited fall into place when u only provided 2 gbs free to use? Thats why i dont complain about sprint cause they got it going
Sent from my Nexus S 4G using Tapatalk
dblkspecial said:
I like the update...but I like the option to blacken the messaging app background. Any way I can change that??
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Theres an option for that? Where? Mine is still normal.
Cool to see the update posted finally!
BrianDigital said:
i thought tht was just in Cm7 based stuff
Click to expand...
Click to collapse
I believe you are correct.
On the matter of tethering, I have heard some people can still tether while others can not after this update. Could this be a glitch? Sun spots perhaps? Chuck Norris threw up a tethering shield? We don't really know do we? I guess unless Sprint comes out and confirms this, we can only assume they intended to give us an update to block this feature.
I could be misinformed, for that, forgive me in advance and carry on.
If you have root, then be careful. If you authorize 10 devices (different ROMs) to your Google Account, then you can't add any more. It used to be as simple as deauthorizing devices every time you reach you limit. As of now, you can only deauthorize 4 device PER YEAR. Be careful...I just had to reupload all my music to a different account because of this.
MEGA SUPER ULTRA EDIT: Google appears to have fixed the issue. Both Adrynalyne and I can now deauthorize devices. It still says the 4 device restriction applies, but seems to be fixed. YAY GOOGLE!
Good thing I just deauthorized all but two devices! This blows
Sent from my Galaxy Nexus using xda premium
when did this start happening? I unauthorized devices all the time on my account.
I called and they said it happened within the last 60 days. They couldn't do anything, but passed it onto Level 2 Tech Support and will email me if they can manually deauthorize my devices.
Got phones?
...of the people, by the people, for the people...
How does Google determine if your device is the same or not? Something in build.prop? If when flashing between ROMs we keep this value the same, your device would always appear to be the same. Problem solved.
Sent from my Galaxy Nexus
snkrhead2323 said:
Good thing I just deauthorized all but two devices! This blows
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Me too! I did just check to make sure it wouldn't let me deauthorize anymore, and Amphibliam is correct. Quite a bummer. Do let us know if you are able to manually deauth any devices or if any other workarounds are found.
ragnarokx said:
How does Google determine if your device is the same or not? Something in build.prop? If when flashing between ROMs we keep this value the same, your device would always appear to be the same. Problem solved.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I think it has to do with how the app authenticates with your Google account. Each time you click "allow" on the prompt to allow the Music app access to your account counts as an activation.
I'm stealing this info thanks
Sent from my PG86100 using xda premium
Def. Need to find a way around this. I'm maxed out on deauthorizations and I'm at 8 devices.
Sent from my Galaxy Nexus using xda premium
codesplice said:
I think it has to do with how the app authenticates with your Google account. Each time you click "allow" on the prompt to allow the Music app access to your account counts as an activation.
Click to expand...
Click to collapse
Last time I changed ROMs and restored Google Music with data via MyBackup, it didn't ask me to authorize - it was already authorized. Potential work around?
Possibly. Doesn't help me at this point. My tenth device was reached when I upgraded to build 36. I forgot to flash gapps, so it killed all my google accounts. I tried restoring data from the Music app on my Inc2, but no dice. My guess is once this s**t really hits the fan, people are gonna find a fix. If this happens again with no workaround, my fix is called Amazon MP3.
http://support.google.com/googleplay/bin/answer.py?hl=en&answer=1230356
Sent from my Galaxy Nexus using xda premium
"Please note that you can only revoke access to four devices per year."
They can't provide an AOSP supported device and then limit Google services to it and not expect an uproar.
Seems to me a simple data wipe would do the same thing.
Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.
And yes, any data wipe would do the same thing, so I imagine if you have a phone with issues (like the Nexus) and you buy the first one, then try 2-3 data wipes/different ROMs to get signal drops/color/whatever fixed. That's 3 devices. Then, they get 2 more Nexuses, and try the same thing on the first, but the second device is fine, so they flash a ROM. That's already 7-9 devices right there. That means you can only flash 5-7 ROMs before you encounter this issue.
Amphibliam said:
Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.
Click to expand...
Click to collapse
Wiping a device has the same effect.
You don't need to flash a rom, because it doesn't change your esn, meid, or even your android_id.
I updated my post.
Amphibliam said:
I updated my post.
Click to expand...
Click to collapse
I am sure that once this issue is out in the open, it will be a rule that you can only deauthorize 4 unique devices each year. As of right now it is not differentiating between multiple instances of the same device.
I have no idea who to ***** at, but I'll support anyone who starts a complaint, petition, or whatever.
It was mentioned earlier but, what I do is restore my "accounts/sync" with titanium backup.
That way you don't have to authorize the device each time.
Be sure to:
After backing up all apps and system data, then after flashing a new ROM on first boot, install titanium backup (pro or not) VIA APK
Then run Titanium Backup and restore the accounts
Then restore the google music app with DATA via Titanium Backup
Then use the market and music like normal without any need for autorizing a new device etc..
Literally every time i check for software updates i get
"Communication failed"
The server is currently unavailable.
Your device will automatically check for an update within the next 48 hours.
Then if i check again it says device is up to date, you can check for updates again in XXhours. If i go into application manager -> AT&T Software Update and clear data, i can check for updates again but i get the same communication failed. I also tried clearing data and rebooting phone, and it still wont check.
And i can't get Samsung Kies running on my windows 7 pc for some reason, so i can't get updates from there either.
Is anyone else on AT&T experiencing these problems? Any fix for this? I really want that update that adds brightness control to the notification menu.
jefferson9 said:
I really want that update that adds brightness control to the notification menu.
Click to expand...
Click to collapse
I did not update, but hearing that update would disable local search, add new modem. Nothing about Brightness control
There is no brightness control on ATT update. I was having the same problem you were and exchanged the phone. There is no fix as far as I know for the error you are getting. It is a common issue. Search the annoyances (bugs) thread.
I don't know if the OTA update resolves your issue because they day after I exchanged mine the update came out.
Sent from my SAMSUNG-SGH-I717 using xda premium
I also haven't been able to get the OTA update. I assumed it was because I rooted and the device is listed as 'modified'. Is the update worth it?
It is in my opinion, and my usage habbits, for the WiFi stability increase that is gained.
Universal search is stripped (searches conducted on phone do not include on device results, ie contacts).
In other words, if you use the Google search by long pressing your menu button the results from your search will only be pulled from the internet.
I rarely use the search built in, so it hardly mattered to me.
Check out the developer forum for ways around the universal strip if you are rooted and want to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well i reseated the SIM card, and removed the little blue tape from the sd slot and the SIM slot, rebooted and still not working.
I wanted to avoid rooting, since the stock software runs so smoothly and i liked being on the latest at&t software. I guess since i can't get OTA updates now theres no reason not to root.
Will this issue be fixed eventually? Or would i be better off exchanging phones while i can?
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
the1stSecond said:
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Well speaking as a software engineer, i'm almost certain its a software issue, most likely with at&t's software update app, or on their servers. Mabey reinstalling the at&t software update application will help?
It sounds reasonable to me. Maybe try the method for No trip flash counter in devoplment? You would be upgrading to the newest firmware and have root and not trip the flash counter. You would still be able to check for ota updates (although should just return the status of your software is up to date since it is a totally stock ROM just with root injected). I imagine that would reinstall the software update service. Although with your knowledge you are way over my head. And whether or not when updating ROMs if that application is reinstalled is something I can't answer.
Maybe just try this first:
Settings> Application Manager> All> AT&T Software Update> Clear Data> Confirm
Power off Phone
Remove battery for at least thirty seconds.
Reinstall battery and power on device.
Try again after device boots up.
Sent from my SAMSUNG-SGH-I747 using xda premium
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
k3y0n4 said:
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
Click to expand...
Click to collapse
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So, if it's a software issue why is it two identical devices running the same software from the factory yield different results? I.e. my first device would do exactly as your original post outlines, then my replacement device had no issue checking for updates (same stock software, same device form factor).
If you search there are a lot of examples of complaints of this exact issue.
I am also very interested in this because even though there are many complaints out there, the only answers seem to be;
1) who cares this is xda and we update through Odin/cwm etc...
2) replace it.
Good luck, I hope you guys find an answer.
Sent from my SAMSUNG-SGH-I747 using xda premium
jefferson9 said:
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
k3y0n4 said:
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
Click to expand...
Click to collapse
You can bypass the wait time between checks by going into application managment -> at&t software update and clearing data. Then you can try to update again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've had similar issues checking for updates. i gave up and pulled the first update with the USALG1 rom posted in the development forum sticky. I too have several apps disabled (actually moved out of the system/app dir) and was wondering if that possibly caused issues. I never did try updating through kies though.
My kies wont even run on my windows 7 64 bit. There seems to be alot of people having problems with kies on win7 64 bit, nothing from samsung either. So theres really no way for me to get updates
This is How I Got My Phone to Update
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
AndroidLonghorn said:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
Click to expand...
Click to collapse
When you got it to work, exactly what apps did you force close and clear data? Just AT&T software update? Any others?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I force closed the At&T Software Update app and I think the Samsung Push Service. It is really the AT&T software update app that finally started downloading immediately after trying it again.
So I finally attempted the Keis connection and it worked immediately. I don't know what other problems people are having, but when I installed it on my Win7 x64 machine I had the S3 connected. After I ran the software for the first time it mentioned an update and proceeded to update it. Keep fighting the good fight jefferson9.
Is this app safe to use, thanks
tongphan said:
Is this app safe to use, thanks
Click to expand...
Click to collapse
So :good:far so good my friend
tyshemi said:
So :good:far so good my friend
Click to expand...
Click to collapse
my phone is not rooted, do i need to root my phone to use this app
tongphan said:
my phone is not rooted, do i need to root my phone to use this app
Click to expand...
Click to collapse
The app is literally called, FoxFi (WiFi Tether w/o Root).
https://play.google.com/store/apps/...ch_result#?t=W251bGwsMSwyLDEsImNvbS5mb3hmaSJd
TheFiveDots said:
The app is literally called, FoxFi (WiFi Tether w/o Root).
https://play.google.com/store/apps/...ch_result#?t=W251bGwsMSwyLDEsImNvbS5mb3hmaSJd
Click to expand...
Click to collapse
Lol this is very true
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've been using Wifi Tether very occasionally, a few times a month maybe. A few days ago received message from ATT telling me that my unlimited plan is about to be changed if I don't call them.
So while I'm on phone with ATT pretending like I have no clue what they are talking about, the person I talked to gave me a list of about 10 apps that they can detect, one of them was FoxFi. Basically anything available at google play is no good...
[email protected] said:
the person I talked to gave me a list of about 10 apps that they can detect, one of them was FoxFi. Basically anything available at google play is no good...
Click to expand...
Click to collapse
That's certainly interesting information. I guess the question is, do they care only because you're on an unlimited plan, or will they give anyone trouble for even limited tethering?
Is it legal for them to do that? I'm on a grandfathered unlimited data plan. Pretty sure there is nothing in my contract about restricted apps....
Samsung s3
The app is not illegal to use. If you get caught they will force you onto a tethering g plan, but not before warning you first
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm curious, how would they detect which apps I have installed?
Sent from my GT-P3113 using xda app-developers app
Is there no privacy laws that protect me from warentless monitoring on my cell phone?
Samsung s3
jcejohnson said:
I'm curious, how would they detect which apps I have installed?
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
I think it's more that they can detect patterns in tethering traffic that are not seen in standard mobile traffic, rather than knowing exactly which apps you have installed and are tethering with.
Keeping in mind I have no idea how this works (or if this approach would be legal), but it would be pretty simple to figure out based what content is frequently being accessed via your "mobile device". e.g. if your phone regularly contacts the Windows Update server, they may suspect you're tethering. Combined with some analysis of how you usually use data much more quickly and differently on a computer vs. a mobile, the patterns would become clear pretty quickly. I'm sure if you mapped out browsing traffic of 1 hour on a desktop vs. 1 hour on a mobile phone, they would look quite different for most people.
TheFiveDots said:
I think it's more that they can detect patterns in tethering traffic that are not seen in standard mobile traffic, rather than knowing exactly which apps you have installed and are tethering with.
Click to expand...
Click to collapse
OK, that makes more sense. I left my tin-foil hat at the cleaners and was worried that AT&T were sending their brain-rays into my head to determine what I've installed (e.g. -- that they have a deal with Google to get access to get a report of installed apps). While that could be true, I expect it is highly unlikely.
TheFiveDots said:
Keeping in mind I have no idea how this works (or if this approach would be legal), but it would be pretty simple to figure out based what content is frequently being accessed via your "mobile device". e.g. if your phone regularly contacts the Windows Update server, they may suspect you're tethering. Combined with some analysis of how you usually use data much more quickly and differently on a computer vs. a mobile, the patterns would become clear pretty quickly. I'm sure if you mapped out browsing traffic of 1 hour on a desktop vs. 1 hour on a mobile phone, they would look quite different for most people.
Click to expand...
Click to collapse
Indeed. But tethering my Android tablet for some bigger-screen browsing & such would't trip the sensors (or should I say "censors") with FoxFi's proxy mechanism. Like your Windows example, though, letting a friend tether their iDevice for a big app install might do so.
I beleive there are some proxies you can use to hide tethering but i have no idea as to how to find or implement them
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm reluctant to root and install a custom ROM. When does the official Lollipop update push over the air for our Nexus 7 (2013) WiFi?
It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app
im still waiting.. damn slow
Nam Huy Linux http://www.namhuy.net
What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Jhall8 said:
It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
arjun90 said:
What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Click to expand...
Click to collapse
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app
Darn it. That's Google's way of wishing us Merry Christmas. :good:
Jhall8 said:
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
No OTA for me yet....
No OTA for me too
I'm waiting, too.
Sent from my Nexus 7 using XDA Free mobile app
Waiting here as well for my nexus 7 2013...... (but my brother received two days ago on his nexus 7 2012).
I have two Nexus 7 2013's each on different Google accounts and to date '0 for 2' on this update. Phantomware to me so far. Tick-tock...
Same here... No Lollipop yet.
Still no update here yet in UK... Yet my missus got her update on her nexus 7 2012 few days ago
Yep. My old 2012 Nexus 7 got it a couple of days ago, my Nexus 5 got it a few hours after that, but still waiting on my new Nexus 7.
You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..
Zaphodspeaks said:
You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..
Click to expand...
Click to collapse
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.
krispy1 said:
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.
Click to expand...
Click to collapse
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once
If you've never seen this , give it a read, explains why the OTA may have not reached your device yet.
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f
Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again.
Click to expand...
Click to collapse
Neomagus, That's good info. I'm wondering at 8 days out whether we have days to wait vs another week or two to wait.
Sent from my XT1080 using XDA Free mobile app
Zaphodspeaks said:
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once
Click to expand...
Click to collapse
A google engineer replied to this on reddit
"Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient."
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f