In this post I will try to explain the delay in the appearance of the firmware update in the different regions, and why some of its successful swing, while others do not see the new items.
Yes, the forum this information is all there, but those who know how to torment search - nothing really new here is not drawn. Fasting is not intended to be global and complete scientific explanation of the processes.
Let's look at how the Fota & Ota firmware update. In very rough approximation - At one point you said - I found on the server firmware update, let's download and install, as well? or - I have already downloaded, let me update.
How is it? Among the many system applications that do not have an external interface is one that is just at 12 o'clock \ day \ week makes a request for an internet address - and if there is something new to me, such a parameter (phone model and firmware version - China or Global, stable or dev, daily or weekly). If the answer is yes - then twitches demon "system update" (three points), which Tishkov shakes OTA-update, and then update the phone offers or gives a notice - "update found, the owner, let's swing it, see how great and powerful developed
... write new code "
The second option - you hand in the application and use the "Check for Update" and ignoring the phone schedule queries immediately. Further actions are identical - no update - ban from you again and again presses the treasured button (because the forum has said that the Chinese in this case, have released a new firmware) would look like the action to Check for Updates from the phone.
How does it look the part of developers and servers.
As tested, and going to the firmware inside the company - I will not write, it's too big a leap away from the topic. I will start from the date of filling the firmware on the server mayor - is the name conventionally, the server - in fact it is the data center, with dozens of physical servers, one of the objectives of which - the issuance of request to the firmware file. But I hope you do not think that the whole world will download updates from one physical data center? Worldwide rental server and data centers, which are almost completely duplicate Primari server in India its servaki, its in Europe, North and South America - the. Ideally, when you add or delete files, all changes should be immediately replicated to the secondary server. In real life, it "immediately" stretched for hours and sometimes days. Somewhere worth checking the schedule every hour, and where a lot of problems, and the system is weak - less, just 3-6-12 hours. Some of the "abled" admins checked manually after kicks from the authorities of the head office, it happens sometimes, unfortunately. So, this is a way to spread themselves firmware files over the world.
Now I want to go back to the phone request for renewal - or rather, the way he has done from the phone to the server Primari. Considered easier on my example - a local provider in the Moscow region.
The request itself is called (https://bigota.d.miui.com)
The first 4 jump (hop`a) are in my opinion, the local ISP, the transition to a larger receiving 99% of the dynamic white address. Second, a major provider transmits Megafon request (in this case), or other backbone providers (who has the right to buy and let traffic through the border) abroad have 2 way or bypass - a long but fast across Europe, either through Asia in China.
Now we went to Europe, to be exact - 9-13 - jumping in Europe, and the last - in North America, Kansas, in a physical data center, it would seem, Bingo! Interior done, but! At this point, there is often something from which there is a lot of questions at the end user. - The server sees that you are from Russia, and forwards the packet to the server in Europe or Russia. Poor request is returned to the Russian Federation on the leased server, which should be based on the new firmware, but there has not yet passed replication, and receives a response that the new firmware is available. And you back the answer that there is no upgrade.
Sometimes the server is not synchronized with the master, and with one of the secondary, ie it is necessary to add a few more hours at the time of occurrence of the firmware. There are load balanced - there are a few physical servers with the same name, separated geographically - Moscow, St. Petersburg, Novosibirsk, Irkutsk, Rostov. And depending on whom you get closer you are to automatically send and provider. And so it turns out that the guys from Kaliningrad, gravitating to the German server updates - see and shake to update from the server, and on Sakhalin and in Siberia - Update no. All of the above must be added the accident on the highways, incorrect and misconfigured server. The clearest example - protection of DDoS attacks - to pass on any server 100 requests per millisecond, and others simply reject, or one external (white ip address) - skip up to 10 requests. And how many people are in a large provider can simultaneously check to update?
So, be patient when checking for updates and if you personally phone or computer will not see anything - it is not necessary to write in the forum, that "there is refreshed vyvsevroti!" And "pachimu me nothing yet preshlos ???"
If you have anything to add and correct - write.Post has been editedinneren84 - 29.06.18, 21:43