Google announces a new version of Android.
They start to develop it for their reference terminal.
Platform Development Kit (PDK) is released.
When Google finishes development for their terminal, they release the PDK and the source code in Android Open Source Project (AOSP) so that processor manufacturers can decide if they are going to support the new version and start working on it.
Work for BQ.
When the processor manufacturer considers that the version is stable, our firmware department now have to develop it. They establish the modifications required so that the version works perfectly in our devices.
At times, support from the processor manufacturer is needed in this phase to ensure the correct operability of all our hardware components. In this phase, all BQ personal features are added and in-house quality control tests are performed.
Beta version is launched.
When the firmware is sufficiently stable it is shared with the in-house beta tester team, with MVP program users, and with beta testers who have signed up to the program through the “My BQ and I” community to start the test phase.
If bugs are detected, you need to go back to the previous step so that the Firmware department can resolve them.
Tests and certification.
We run more than 700 in-house tests in different phases, and when all work correctly, third-party tests are performed including the quality certification by Google, amongst others (CTS, GMS…).
When everything is ready, BQ launches the update via OTA.
The initials OTA stand for “Over-The-Air” and refers to the way in which firmware updates are download onto user devices using mobile data connections or Wi-Fi.