Early last week Google finally announced the name of Android Oreo and then shortly afterwards uploaded the source code for the new update. As we were combing through those commits to find some new changes, Google then uploaded the system images for the update for supported Pixel and Nexus devices. Manually flashing those images will wipe the data from your phone though, so last night the company published the OTA images for this new update.
Google's OTA update system can feel incredibly slow if you aren't picked to be included in the first phase or two of the roll out. At least back in the KitKat days, Google would send a new update to 1% of their users within the first 24-48 hours. During this time, Google checks the return rates, device checkins and error reports (if any). Assuming there aren't any issues here, the company then sends these OTA update notifications to 25%, 50% and then 100% over the next couple of weeks.
Any critical errors they find during this process can delay the OTA update roll out so they can find the issue. This means it can sometimes be favorable to actually wait for the update notification to be pushed to you. However, if you want to manually download and install this new Android Oreo update then you can do so on the Pixel, Pixel XL, Pixel C, Nexus 6P, or the Nexus 5X. This process requires you have ADB installed on your computer and that you type in a few commands via the terminal or command prompt.
However, you also might get away with spamming the Check Update button within the system updates section of the Settings application. I discovered this worked when other people were receiving the Android Wear 2.0 update for the Huawei Watch, and it just worked again about 10 minutes ago for my Pixel C. It's not guaranteed to work, but after 5-6 quick retries it just may trigger and prompt you to download and install the update.
Source: Google
from xda-developers http://ift.tt/2vJOIE8
via IFTTT
No comments:
Post a Comment