[MTCB Android Head Units General] germinus:
Full Post translation and download link

Here is the full post with download link, please donate to the dev if you like his work.

The firmware is designed as a "designer" under both options screen resolutions (800x480 and 1024x600). Everyone can afford to assemble his own version. How to assemble the firmware is described in detail here:

The order of assembly of the firmware

The firmware is available as a set designer or "do it yourself" - as anyone this thing called - and is a set of modules for self-assembly of the finished image of the firmware. The assembly is made on a computer running Windows (versions from XP and higher).

How to assemble:

1) Download the archive unpack into any empty folder on your computer (the full path to the folder does not contain spaces, non-Latin characters, punctuation marks and special characters, so not recommended for unpacking on the desktop, in the "My Documents", etc. )

2) turn in this same folder

3) Run start_rus.bat file (or start_eng.bat, if you are dearer to the English interface)

4) you will be asked to choose a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers specified opposite processor type, and then pressing the Enter key

5) The following sentence - to select the screen resolution. Options are also two - 800x480 and 1024x600. The selection is made in the same manner as in the previous paragraph

6) After this, the firmware build process, which takes less than 10 seconds.

7) The result of the process - file update_ <vash_protsessor> _ <vashe_razreshenie> .img, which, after renaming update.img you can sew in a familiar way radio When you first start after flashing is (as usual in my firmware) conducted preset application and then fit /system/build.prop configuration file under the processor type and resolution (800x480 for the recorder will be installed screen density of 160 to 1024x600 - 240). Then reboot, after which the tape recorder will be completely ready for operation.

Features flashing process. Due to the fact that changing breakdown flash memory sections (including as compared with previously released on FUSE-firmware Android 4.4.4), the process can be performed in two stages, both stages are the same.

That is, you normally install firmware mode rekaveri (thus necessarily choosing the option with full data cleaning). The device is rebooted and ... hang on animated screensaver. If you want to wait, wait - but the result is not guaranteed. If you do not want to wait, press the RESET, then (without releasing RESET'a) - POWER. Without releasing the POWER, release the RESET, waiting 3 seconds and release POWER. All - a few seconds later we are back in rekaveri mode where once again just repeat the flashing process - again, choose the menu item, involves the installation of firmware and data cleaning, and ... forward. After the second cassette recorder firmware to be released to the operating mode (although longer than usual, as is the formation of the primary file system).

Option: instead of the second flashing, you can try to select a lower menu item - "clean and reset to factory condition."

As you understand, all your data will be lost after flashing, so advance reservations and they do not say I did not warn.

Attention!!! Those who do not have the RESET button and mechanical buttons. Before flashing be sure to ask if you can overload the radio in rekaveri mode from the "hung" or off state. If this method is not, then you better not reflash.

OTA-upgrade

The firmware is the possibility of prompt automatic updates. OTA (Over the Air - "air") or FOTA (Firmware Over the Air) - a technology that allows to (semi-) automatically obtain and install the update packages. User Intervention here minimum - it is only necessary to press the button, confirming compliance with the installation. Well, there is still a button manually check for updates. And all the rest State makes self - sends a request to the server, downloads the update package, checks it for validity (verifies the certificate used to sign the update package with a key available in the firmware), reloads the State in rekaveri mode where automatically launches the update process, and finally PG reboots to the operating mode.

Naturally, for the possibility of State OTA-update should have a working Internet connection. Automatic prompting to check for updates are sent automatically after every download SI operating mode and communication with the Internet. If desired, you can request a renewal of the "out of order" by pressing the appropriate button in the dialog "Settings" - "About your device" - "OTA update system." Another essential requirement to enable OTA updates - is the availability of free space on the "GPS-card" (/ mnt / external_sd), and (of course) the availability and serviceability of the card itself. In case of problems with the card update can be downloaded to start, but then will be a network error. Available space on the card must be two times larger than the size of the update package. As practice shows, the usual pack "weighing" of up to 20 MB. Although there are cases of 55-MB blocks. In general, if you keep on the card 120 MB of free space, the problems you should not be.

Cancellation OTA update? Unfortunately, a simple interactive option is not provided. But you can do the following: Open the file for editing /system/build.prop. Find it (towards the end of the file) option ro.product.ota.host = www.booroondook.ru: 2300. Replace the URL-address of the update server (www.booroondook.ru:2300) to something "obscene". For example, suppose that this line will look like this: ro.product.ota.host = localhost. Save the file, restart the SU. Everything - Updates you will not torture any more.

Disclaimer: The self-fulfilling complicated technical procedure for flashing the device, you will definitely take full responsibility for possible negative consequences up to the irrevocable failure of your head unit.

Version - from 06/03/2016

Link to the firmware (made on the basis of KLD-20160511): https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU

Innovations regarding the factory options:

- Cloning a resolution of 800x480 by kernel patch (kernel.img)

- Completely redesigned Russian translation

- Root access running SuperSU

- 5 launcher to choose from ( "Settings" - "Desktop")

- 4 options "Bluetooth" application ( "Telephone"), 5 application options, "Music" and "Radio". Alternative applications are installed through the "OEM" application, return to the original (nominal) version - after the usual removal of the application settings ( "Uninstall updates")

- In settings Added "For Developers", "Screen" - "Font size" and "Display" - "Display Density"

- In settings added to the monitoring data

- OTA-update functionality

- Added missing "OEM" applications, "Weather", "DVR" (Annex "Weather" - in the version revised respected vitarkananda)

- Added widgets "Weather", "Music", "Telephone", "Video" and "Navigation", ported from the firmware for MTCD

- Partition "OEM" is increased to 384 MB. This section can be used, for example, as a "warehouse" APK-relevant distributions

- Built-in support for working with trip computer Multitronics MPC-800 (Bluetooth-name DUAL-SPP)

Attention:

1) please do not ask questions why this firmware does not work Xposed. The answer is - it does not work and on the drive firmware, and generally have Xposed big problem with Android 5 (or higher). When someone finds a way to get to work on our Xposed firmware, in principle, I immediately implement it in its firmware.

2) Management of screensaver (MTCScreenClock.apk) is only possible through /system/build.prop File Edit (parameters ro.product.screenclock = true | false and ro.product.screentimeout = 5 | 10 | 15 | 20 | 30 | 60 ). Interactive control timeout in the factory firmware is not provided, and I realize it too failed.

Note: Because an application "Weather" uses a revised version of vitarkananda, the new version of the application (as they become available) can be installed instead of the usual simple by replacing labor-intensive system file.

For developers, the public certificate signed APK following: MTCBlueTooth.apk, MTCMusic.apk, MTCRadio.apk, MTCScreenClock.apk. This means that signing their "swing" application to the same certificate (and increasing code version), you can give users the ability to easily install your development instead of forcing them to carry out the replacement of system files with setting permissions.

https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU