• home
  •  > 
  • Utilities
  •  > 
  • Kernel version 3.0 36. Android from A to Z: What is the Android kernel

Kernel version 3.0 36. Android from A to Z: What is the Android kernel

This post will describe the kernel update for Ubuntu, its reasons and results. I will also tell you about installing the Virtualbox module on it.

As the “happy” owner of a laptop with a processor, I never cease to be surprised that Linux still does not correctly support integrated video. Although in Lately were, however, with the 3.1-rc10 kernel, which I tried, it failed to boot.

So what do we have on this moment. Integrated graphics are not supported on kernels 2.6.36 - 2.6.38; there are patched kernels from Adam with which it works fine. 2.6.37-vaioz worked stably for me (except for the Gnome session crashing after entering Enter). Fresh Ubuntu 11.10 with kernel 3.0.4, it didn’t work for me. And I really hoped so. The 3.1.x kernels are still somewhat damp, because... are in development.

On the hub in the topic about a wonderful one slipped through to the ppa repository with kernels in deb packages. This was good news for me, because... Now I could just go through all the kernels and figure out which ones would work with my hardware. I started with the . The system booted, but then went into kernel panic. Ok, then I tried it. The system has booted and has been working normally for half an hour (pah-pah-pah). I guessed right on the second try, not bad. Next there will be an installation manual. Although everything is simple there in general.

Installing kernel 3.0.8 + kernel module for VirtualBox

1. Download three packages from the repository:

Wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.8-oneiric/linux-headers-3.0.8-030008_3.0.8-030008.201110250135_all.deb wget http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.0.8-oneiric/linux-headers-3.0.8-030008-generic_3.0.8-030008.201110250135_amd64.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/ v3.0.8-oneiric/linux-image-3.0.8-030008-generic_3.0.8-030008.201110250135_amd64.deb

2. Install the packages.

Sudo dpkg -i ./linux-headers-3.0.8-030008_3.0.8-030008.201110250135_all.deb sudo dpkg -i ./linux-headers-3.0.8-030008-generic_3.0.8-030008.201110250135_amd64.deb sudo dpkg -i ./linux-image-3.0.8-030008-generic_3.0.8-030008.201110250135_amd64.deb

I am writing so that, firstly, I myself do not forget the order, and secondly, so that there is a clear algorithm.

3. Reboot the system, select a new kernel in grub. Loading up with fingers crossed
4. If you have downloaded, then install the module for VirtualBox:

Sudo /etc/init.d/vboxdrv setup WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.

* Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ]

Now the virtual machines should start normally. Let's check.

The glitches with the session crashing during login have disappeared, the only thing that bothers me is that the LED of the selected video card does not light up on the laptop.

Thank you!

If this article helped you, or you want to support my research and blog, here is the best way to do so: Users mobile devices I am not always satisfied with the work and capabilities of my gadgets. For this reason, users are looking for the best way how to flash the kernel operating system Android. On the one hand, this action can be easily carried out with your tablet or smartphone. Thousands of users have successfully flashed the kernel without any difficulties or problems. But, on the other hand, any mistake during this process can lead to problems, including failure of the gadget and the need for expensive service. At different stages there is a risk of not choosing correct version

kernel firmware, which was created by unqualified developers, or does not fit your mobile device. We recommend that you be extremely careful when carrying out any actions that make changes to the software part of the device at a low level. After successfully flashing the kernel, many people feel like they are holding a completely new device in their hands. Advanced users can thus customize the gadget to their needs and preferences, while gaining new knowledge and experience about modern mobile technologies.

The kernel of the Android operating system and its firmware

What is the core of a mobile device? The operating system kernel is the basis of the software that controls the hardware of the device. The basic parameters of any gadget depend on it. It should be noted that it consists of three interrelated components - the Linux kernel, vertical machine Dalvik and various low-level services and libraries. If we are talking about custom firmware, then only two components are affected, which allow you to add new ones system services

Those wishing to install the kernel on Android should understand that there is a difference between the concepts of custom kernel and custom firmware. The latter is an unofficial version of the software. Custom firmware was developed by a team of specialists for specific devices. The custom kernel is based on the Linux kernel, representing it unofficial version. Often a custom kernel comes bundled with firmware. But it can be installed separately after changing the firmware. Essentially, it does not replace the native core of the mobile device, which is the ultimate goal of such an operation.

Android kernel firmware is mainly done to increase the operating time of the device by several hours by adjusting the power consumption parameters. Perhaps this is the main reason why users carry out complex conversions of the software of their gadgets. The firmware will allow you to change the video chip without consequences for your smartphone or tablet. Advanced users customize the screen in this way, changing its color rendering and sensitivity. Kernel firmware allows you to improve the sound of the device, update drivers and introduce support for non-standard external gadgets.

Before flashing the kernel, we recommend making sure that you have chosen a good version that was created by experienced developers. In addition, it is important to make sure that it is suitable for your Android firmware version. It is advisable to read the reviews of people who managed to install suitable version kernels to your mobile phone. Reviews may contain important information about problems that may arise at the stage of firmware or further operation of the device.

Flashing the gadget via Fastboot

You can reflash your Android device using Fastboot. But first you need to install the utility on your gadget. There are two versions of this program. The first involves downloading Fastboot in combination with official program Android SDK. The second version involves downloading the utility separately.

We recommend checking whether your mobile device can see your laptop or computer. To do this you need to do . After downloading and installing the Fastboot utility on your computer or laptop running the Windows operating system and connecting your smartphone, you need to open the command line. To do this, open Search. In Windows 8, to do this, just move the mouse cursor to the right side of the screen and select the appropriate section. In Search you need to enter “cmd”, after which the command line will appear in front of you. The device should be switched to firmware mode. Next, you should enter a command that will test the interaction between your computer and mobile device:

fastboot devices

If everything works, you need to download the correct version of the kernel firmware boot.img. We do not recommend flashing the kernel original firmware, as this may cause problems with your smartphone. The file should be saved to a pre-created partition on drive C called “Android”. After this, you need to boot the mobile device into Fastboot and connect it to the computer. The message “Fastboot USB” will appear on the screen.

  • cd C:\Android.
  • fastboot flash boot boot.img.
  • fastboot erase cache.
  • fastboot reboot.

It is very important to enter all words correctly, taking into account case and spaces. The cd command opens the required folder that contains the required files. After this, flashing occurs. fastboot command erase cache deletes the Cache partition. Last command- fastboot reboot reboots the device from firmware mode to normal. If you performed all the above steps correctly, the process will be successful.

Firmware using ClockworkMod Recovery

ClockworkMod Recovery(or CWM for short) is a recovery system that is used instead of the original factory Recovery. CWM allows you to install new firmware to a mobile device, flash the kernel, make backup copy files and restore the shell. Such a system can work with firmware update files in zip format. ClockworkMod is installed in, replacing factory recovery. To launch CWM, you need to know the key combination that is suitable for your gadget. In most cases, this is a combination of the Volume Down and Power buttons that should be pressed while the device is booting.

To flash the kernel firmware, download the archive from zip extension. It must contain the META-INF folder. Then there are two options. In the first case, you need to specify the firmware file. The second option involves placing the firmware file in the /sdcard folder. After this, you should activate ClockworkMod Recovery, find the Apply update from sdcard function there and specify the required file.

It should be noted that the ClockworkMod Recovery menu is convenient and understandable for most users. In addition to this recovery system for firmware, you can use TWRP Recovery. This tool is convenient and popular among Android users. The main thing is to choose correct file firmware.

Flashing the Android kernel is a procedure that we do not recommend resorting to if you are completely satisfied with the operation of the gadget. Such actions are driven by the desire to increase productivity. mobile phone or tablet. Advanced users have the opportunity to set parameters at a lower level. But without certain knowledge and objective reasons, it is better not to change the software part of the mobile device, since this is associated with risk and malfunctions in its operation.

We have already written more than once about custom firmware, root applications and alternative boot menus. All this standard themes in the Android hacker community, however, in addition to all of the above, there is also such a thing as a “custom kernel”, which can provide almost unlimited possibilities for managing a smartphone and its hardware at the lowest level. In this article I will tell you what it is, why it is needed and how to choose the right custom kernel.

Custom kernel?

What is a custom kernel? As we all know, Android is a pie made up of three base layers: Linux kernel, a set of low-level libraries and services and virtual machine Dalvik, on top of which runs a graphical shell, high-level tools and services, as well as almost all applications installed from the market. The creators of most alternative custom firmware usually work only with the top two layers, adding functions to the graphical shell (for example, buttons in the curtain), changing it (theme engine in CyanogenMod), as well as adding new system services (equalizer in CyanogenMod) and optimizing existing ones.

The authors of popular firmware also make changes to the Linux kernel whenever possible: they optimize (build with more aggressive compiler optimization flags), include new functionality (for example, support for Windows ball), and also make other changes, such as the ability to raise the processor frequency above that provided by the manufacturer . Often all this remains behind the scenes, and many users of custom firmware are not even aware of these possibilities, especially since the same CyanogenMod comes with a custom kernel only for a limited range of devices, for which both the source code of the native kernel and the ability to replace it are available. For example, almost all CyanogenMod firmware for Motorola smartphones use a standard kernel - it is impossible to replace it with your own due to the impenetrable protection of the bootloader.

However, the kernel in smartphones with an unlocked bootloader can be replaced separately from the main firmware. And not just replace, but install a kernel with a huge amount various functions, which require certain technical knowledge to manage, and therefore are usually not built into the kernels of popular firmware such as CyanogenMod, AOKP and MIUI. Among these functions you can find support for high processor frequencies, control of screen gamma, energy saving modes, highly efficient power managers and a huge number of other features.

In this article we will talk about what the creators of custom kernels can offer us, we will look at the main custom kernels for various devices, and we’ll also try to install the kernel independently of the main firmware and check everything the hard way. So, what do developers of alternative kernels usually offer?

Smart traffic controller

In OMAP35XX SoCs, used, for example, in Galaxy S II and Galaxy Nexus, there is a SmartReflex function that plays the role smart system voltage adjustment when the load on the processor changes. Essentially, it eliminates the need for fine tuning of voltage by the user.

Optimizations

Often the main goal of building a custom kernel is to optimize performance. Usually the vendor mobile technology tries to maintain a balance between performance and stability, so even good optimization techniques that can significantly increase the speed of the device can be rejected by the manufacturer only on the basis that after using them, some applications began to crash every tenth launch. Of course, enthusiasts are not bothered by such little things, and many of them are ready to apply any compiler options, power saving algorithms to the kernel of their own assembly and raise the processor frequency as high as the device can handle. Among all optimization techniques, four are the most common:



Another type of optimization: changing the default I/O scheduler. The situation in this field is even more interesting, since instead of understanding the principles of operation of schedulers, some kernel builders simply read documents on the Internet on I/O schedulers for Linux and draw conclusions. Among users, this approach is even more widespread. In fact, almost all of the most powerful and intelligent Linux schedulers are completely unsuitable for Android: they are designed for use with mechanical data stores, in which the speed of data access varies depending on the position of the head. Scheduler uses different schemes combining queries depending on the physical location of the data, so queries against data that are located close to current situation heads will receive higher priority. This is completely illogical in the case of solid-state memory, which guarantees the same access speed to all cells. Advanced schedulers will do more harm than good on a smartphone, and the most clumsy and primitive ones will show the best results. Linux has three similar schedulers:

  • Noop (No operation)- the so-called non-scheduler. A simple FIFO request queue, the first request will be processed first, the second second, and so on. Good for solid state memory and allows you to fairly distribute application priorities for access to the drive. Additional plus: low processor load due to very good simple principle work. Disadvantage: no consideration of the specifics of the device’s operation, which may result in performance failures.
  • SIO (Simple I/O)- an analogue of the Deadline scheduler without taking into account the proximity of sectors to each other, that is, designed specifically for solid-state memory. Two main features: the priority of read operations over write operations and the grouping of operations by process, allocating a time slice to each process to perform operations. In smartphones, where the speed of the current application and the predominance of read operations over write operations are important, it shows very good performance. Available in Leankernel, Matr1x kernel for Nexus 4 and SiyahKernel.
  • ROW (READ OVER WRITE)- a scheduler specifically designed for mobile devices and added to the kernel just a few months ago. The main goal is to process read requests first, but distribute fair time for write requests as well. It is considered the best scheduler for NAND memory at the moment; it is used by default in Leankernel and Matr1x.

It is worth saying that almost all standard firmware and half of custom ones still use the kernel with the standard Linux CFQ scheduler, which, however, is not so bad, since it can work correctly with solid state drives. On the other hand, it is too complicated, creates greater load on the processor (and therefore the battery) and does not take into account the specifics of the mobile OS. Another popular choice is the Deadline scheduler, which is as good as SIO but is redundant. You can view the list of available schedulers using the following command:

# cat /sys/block/*/queue/scheduler

To change the following is used (where row is the name of the scheduler):

# for i in /sys/block/*/queue/scheduler; do echo row > $1; done

Some kernel builders also use another type of optimization related to I/O. This disables the fsync system call used to forced reset changed content open files to disk. There is an opinion that without fsync the system will access the drive less often and thus save processor time and battery power. Quite a controversial statement: fsync is not used very often in applications and is really only used for saving important information, but disabling it can lead to the loss of the same information if the operating system crashes or other problems. The ability to disable fsync is available in the franco.Kernel and GLaDOS kernels, and is controlled by the file /sys/module/sync/parameters/fsync_enabled, in which you should write 0 to disable or 1 to enable. Again, it is not recommended to use this feature.

Adding new functions to the kernel

Of course, in addition to optimizations, tweaks and different systems advanced hardware management, in custom kernels you can also find completely new functionality that is not in standard kernels, but which can be useful to users.

These are mainly various drivers and file systems. For example, some kernels include support for the CIFS module, which allows you to mount Windows shares. Such a module is in the Matr1x kernel for Nexus S, faux123 for Nexus 7, SiyahKernel and GLaDOS. By itself, it is useless, but there are several applications on the market that allow you to use its capabilities.

Another useful feature is the inclusion of the ntfs-3g driver in the kernel (more precisely, in the package with the kernel; the driver itself works as a Linux application), which is necessary for mounting flash drives formatted as a file NTFS system. This driver is found in the faux123 and SiyahKernel kernels. Usually it is activated automatically, but if this does not happen, you can use the StickMount application from the market.

Many cores also include support for the so-called zram technology, which allows you to reserve a small amount of space random access memory(usually 10%) and use it as a compressed swap area. The result is a kind of expansion of the amount of memory, without any serious consequences for performance. Available in Leankernel, enabled using Trickster MOD or zram enable command.

Last two interesting features- this is Fast USB charge and Sweep2wake. The first one is nothing more than forced inclusion mode " fast charging", even if the smartphone is connected to the USB port of the computer. Fast charging mode is available in all more or less new smartphones, however, due to technical limitations, it cannot be enabled simultaneously with access to the memory card. The Fast USB charge function allows you to always enable this mode, while disabling access to the drive.

Sweep2wake is a new way to wake up a device, invented by the author of Breaked-kernel. Its point is to turn on the smartphone by sliding your finger over the navigation keys located below the screen, or across the screen itself. It's really convenient function, but as a result of turning it on, the sensor will remain active even while the device is sleeping, which can significantly drain the battery.

Overclocking, voltage and energy saving

Overclocking is popular not only among owners of desktop computers and laptops, but also among mobile technology enthusiasts. Like x86 architecture stones, processors and graphics cores Mobile technology is excellent in pursuit. However, the overclocking method itself and the steps taken to implement it are somewhat different. The fact is that standard drivers for SoCs, those responsible for energy saving and changing the processor frequency are usually locked to standard frequencies, so for fine tuning you have to install either alternative driver, or a custom kernel.

Almost all more or less high-quality and popular custom kernels already include unlocked drivers, so after installing them, the ability to control the “power” of the processor is significantly expanded. Usually custom kernel builders do two things that influence the choice of frequency. This is an extension frequency range beyond the initially specified ones - you can set either a higher processor frequency or a very low one, which allows you to save the battery and increase the gradation of frequencies, for example, instead of three possible frequencies, there are six to choose from. The second is the addition of the ability to adjust the processor voltage, so you can reduce the processor voltage at low frequencies to preserve battery charge and increase it at high frequencies to increase stability.

All this can be controlled using the well-known paid utility SetCPU or the free Trickster MOD. Management recommendations are the same as for desktop systems. It is better to set the lower processor frequency to the minimum, but not lower than 200 MHz (to avoid lags), the upper threshold is increased gradually while testing the stability of operation, if it drops, it is recommended to slightly increase the voltage for this frequency. There are no recommendations for voltage, since each processor is unique and the values ​​​​will be different for everyone.


In addition to changing frequencies, builders often add new energy-saving control algorithms to the kernel ( automatic control processor frequency), which, in their opinion, can show better results in comparison with standard ones. Almost all of them are based on the default in new versions Android algorithm Interactive, the essence of which is to sharply increase the processor frequency to the maximum in case of increased load, and then gradually reduce it to the minimum. It replaces the previously used OnDemand algorithm, which smoothly adjusted the frequency in both directions in proportion to the load, and makes the system more responsive. Collectors of alternative kernels offer the following algorithms to replace Interactive:

  • SmartAssV2- rethinking the Interactive algorithm with a focus on saving battery. The main difference is that you don’t have to yank the processor high frequencies in case of short bursts of load, for which low processor performance is sufficient. The default is used in the Matr1x kernel.
  • InteractiveX- tuned Interactive algorithm, main feature which is locked in the processor at the minimum user-specified frequency and de-energizes the second processor core while the screen is turned off. Default is used in Leankernel.
  • LulzactiveV2- essentially a reinvented OnDemand. When the load on the processor exceeds the specified one (60% by default), the algorithm raises the frequency by a certain number of divisions (1 by default), and lowers it when the load decreases. It is of particular interest because it allows you to independently set operating parameters, therefore it is suitable for hardened geeks.

In general, kernel builders really like to come up with new energy-saving algorithms because of the ease of their implementation, so you can find a dozen others. Most of them are complete rubbish, and when choosing a scheduler you should be guided by the rule: either one of the three described above, or the standard Interactive, which, by the way, is very good. You can make a choice using the same Trickster MOD.

Control Interfaces

Most popular custom kernels include several mechanisms for fine-grained control of various driver parameters, the most common of which are ColorControl, GammaControl, SoundControl and TempControl.

The first two interfaces are available almost everywhere, including CyanogenMod kernels, the second two are available in Leankernel and maybe in others. One way or another, all of them can be controlled using Trickster MOD.

Cores

Which core should you choose? There is no clear answer to this question, and not because “to each his own,” but because there are a huge number of Android devices in the world and almost as many different kernels. However, there are several popular kernels that are being developed for several devices at once. One way or another, I mentioned many of them throughout the story, and here I will give a brief description of them.

  • Leankernel is the core for the Galaxy Nexus, Nexus 7 and Galaxy S III. The main emphasis during development is on simplicity and speed of work. Energy saving algorithm: InteractiveX V2, I/O scheduler: ROW, all of the above control interfaces, support for Fast USB charge, Swap and zram, flexible overclocking options for CPU and GPU. One of best kernels. Customizable using Trickster MOD.
  • Matr1x (http://goo.gl/FQLBI, goo.gl/ZcyvA) - kernel for Nexus S and Nexus 4. Simple and unoverloaded kernel. Support for CPU and GPU overclocking, GammaControl, Fast USB Charge, Sweep2wake, I/O schedulers: SIO, ROW and FIOPS. Performance tweaks. Customizable using Trickster MOD.
  • Bricked-Kernel (http://goo.gl/kd5F4, goo.gl/eZkAV) - a simple and unoverloaded kernel for Nexus 4 and HTC One X. Optimizations for Snapdragon S4 and NVIDIA Tegra 3, redesigned power saving mode for Tegra 3, the ability overclocking, energy saving algorithm: tuned OnDemand (also available Interactive).
  • SiyahKernel - kernel for Galaxy S II and S III. Flexible overclocking options automatic calibration batteries, improved driver touch screen, energy saving algorithms: smartassV2 and lulzactiveV2, I/O schedulers: noop, deadline, CFQ, BFQV3r2 (default), V(R), SIO. CIFS and NTFS drivers (with auto-mounting). Configurable using ExTweaks.
  • franco.Kernel - kernel for Nexus S, Galaxy Nexus, Nexus 4, Nexus 7, Nexus 10, Galaxy S III, Galaxy Note, Optimus One and One X.

Kernel capabilities vary greatly from device to device, so you'll have to check the details on site. However, by flashing this kernel, you will get the ability to overclock, driver tuning, excellent performance, as well as support for various power saving algorithms and schedulers. In fact, the kernel includes almost all the tweaks described in the article. Considered one of the best kernels available. There is an application for automatic update franko.Kernel Updater. You can configure it using Trickster MOD.

How to install?

All kernels are distributed in standard Android ZIP archives, which should be flashed through the recovery console in the same way as alternative firmwares. Usually the kernels are compatible with any firmware, therefore, choosing the right kernel, you can safely install it. The only thing you should pay attention to is the version of Android with which the kernel is compatible. It can either fit all available for the device Android versions, and work with only one (the developer usually explicitly talks about this). Before flashing the firmware, be sure to make a backup of the current firmware using the same recovery console. If something goes wrong, you can always roll back.

conclusions

As you can see, custom kernels have many advantages over kernels used in standard or third-party firmware. And what’s even more important is that you don’t need to know all the intricacies of Android to use them; just download and install the ZIP archive.

Many owners Android devices On various forums and websites one often comes across mention of something incomprehensible, which is called the kernel, or in English kernel. It can be changed and it is mentioned in the device settings menu, in the “About tablet (phone)” section.

If you dig deeper, you will find that the kernel is part of the operating system, and not only Android has it, but also other operating systems: Windows, iOS, MacOS and others. But we will be interested Android kernel, and I will try to explain what it is at the level of novice users.

You probably know that any operating system, including Android, is, by and large, a set of programs that control the operation of the entire device and are responsible for launching custom applications, such as games, file managers, web browsers and others.

And the Android kernel is practically the most important part of the operating system, which is responsible for the interaction between all the hardware and the software part of the system. The kernel consists of a set of drivers for all the equipment in the device and a subsystem for managing memory, networking, security, and other basic functions of the operating system.
For example, when you touch the screen to launch an application, the driver touchpad screen determines the location where the click occurred and reports the coordinates to other programs, which again, using the kernel, will find it in the device’s memory the right application and launch it. This is, of course, a very simplified model, but it reflects the essence of the operating system.

Thus, we found out that when any software needs the tablet or phone hardware to do something, it turns to the operating system kernel to do it.

The kernel controls absolutely all equipment: Wi-Fi, Bluetooth, GPS, memory and other devices. The “heart” of the device – its processor – is no exception. The core can control its frequency and power supply.
Operating core Android systems, borrowed by its developers, Google, from the Linux operating system.

Since the kernel controls all the hardware, and the hardware of all tablets and phones is different, the basic Android kernel is modified by the manufacturer for each device separately.

Like firmware, kernels can be stock (factory) and custom - alternative, created by independent developers.

Why do we need custom kernels? The stock core is maximally optimized by the manufacturer for specific device, but it usually blocks such important functions kernels, such as CPU frequency control. And if you need to overclock the processor of your tablet, you will need to change the kernel to a custom one, in which the processor frequency control function is unlocked.

In addition, custom kernels are usually based on more recent versions Linux kernels. Here is an approximate list of features that custom kernels give us:

  • Change the processor frequency within a wide range;
  • Overclocking the graphics subsystem (GPU);
  • Reducing the processor frequency and voltage, which allows for longer battery life;
  • More recent and high-quality drivers, for example, speeding up GPS or adding new functions;
  • Wide range of options for customizing and configuring sound and color range screen;
  • Support for alternative file systems(XFS, ReiserFS and others).

Since alternative kernels are created by independent developers, there is no guarantee that your tablet or phone will work without problems after installing a custom kernel. Therefore, before flashing a new kernel, it is advisable to make a full backup of the system.

Of course, I read a lot of reviews about Highscreen Boost. But, as they say, until you try it yourself... - that’s what I was taught. Although I was taught this way: - only fools learn from their mistakes! And I was also taught not to buy cheap things (.. I’m not rich enough to buy cheap ones...)... Time passes, and the Chinese IT industry moves forward, and it goes by leaps and bounds... And now China is already ahead of the rest... but oh what am I?

Highscreen Boost is a Chinese smartphone based on Android 4.1.2.

Battery 4200mA. (...If Skype is turned on, 4-5 days are enough. Otherwise, a week is sure. But I talk a little - 10 minutes a day, maximum...).

...My device lived in light mode for almost 9 days...

Combat software for Highscreen Boost - OS: Android 4.1.2
The set of software is initially minimal.
Kernel version - 3.4.0
Build number - V2.2 (how to flash (http://highscreen.org/products/communicators/highscreen-boost/) at the bottom of the technical info page).
Communication module firmware - V2.0 (supports the network better than V2.2)

From my own experience:

Firmware V2.0, I immediately flashed V2.2 from the support site. (periodically lost the network, infrequently.), read 4pda.ru. I decided to update the RM (radio module) to v2.0. I flashed the radio module. The network no longer loses.

Experience:
copy Boot_2.0.zip (http://4pda.ru/forum/index.php?showtopic=463222&st=140#entry22871436) to the root of the memory card. Reboot your phone into recovery*. Select the very last item “advance” - go into it (top right book). select the line “enable signature verification”, activate it with the right button. The line will change to “disable signature verification”, go back to the recovery menu and select “ apply update from external storage", point to the file Boot_2.0.zip. If everything is done correctly, then an inscription should appear, but it didn’t appear for me - update complete. Select recovery reboot again.

Works on one charge:
Like a telephone - 5-6 days, if you just call and answer.
Like a smartphone, with average load - 3-3.5 days.
Under heavy load - 2 days (Wi-Fi, Browser, ICQ, Skype, VPN, Lan, RDP...).
In the car, as a navigator, with active GPS - 8 hours!

After flashing:
Kernel version - 3.4.0
Build number - V2.2
The communication module firmware is V2.0 (the network holds better than V2.2).

Software - which an IT specialist should have:
install-su-cwr.zip - root, install via ANY recovery and for ANY firmware. (http://4pda.ru/forum/index.php?showtopic=434918&st=2240#entry21764093) SuperSU_PRO+v1.32.apk Adobe+Reader+10.6.0.apk Adobe_Flash_Player_11.1.115.17.apk
AK_Notepad_2.4.5.apk - A program for creating notes with reminders.
AndFTP+Pro+3.0.apk
BusyBox+Pro+v9.7.3.apk
com.android.aldiko_2.2.3.apk
Dolphin+Browser+v9.4.2.apk
ES_File_Explorer_3.0.4.apk
hackerskeyboard-v1034-mod6.7.apk - great keyboard
LuckyPatcher+3.3.4.apk
OfficeSuite+Pro+7+(PDF+&+HD)+v7.1.1237.apk
PocketCloud.Remote.Desktop.Pro.v1.3.216.apk
QuickPic_2.9.4.apk - replacement for the standard gallery
Remote_RDP_3.6.4.apk
Remote_VNC_Pro_2.0.apk
CIDRCalculator_1.9.apk
in.introkun.setmacaddress_v2.0.1.apk
Root+Explorer+(File+Manager)+v3.01.apk
Root Explorer 2.21.1.apk
Total Commander 2.02b3.apk
FTP plugin (File Transfer) 2.02.apk
LAN plugin ( General access Windows) 2.01.apk
Plugin TotalBox (Dropbox) 0.1.34b.apk
USBStick plugin (USB drives) 1.0.2.apk
WebDAV plugin (WEB folders) 2.03.apk
com.bmsrecord.apk - record conversations from the line. (In order to write, click on the icon..., in short, the icon should be red)
Skype_3.2.0.6673_v19_rus_by_ms.apk
Taskiller_Full_v3.5_Rus_allexx71.apk
TeamViewer-udalyonnaj_dostup_8.0.1055.apk
WhatsApp_2.10.222.apk
Wifi_Analyzer__3.6.apk Wifi_Connecter_Library_2.0.1.apk
xScope_Browser_Pro-Web_File_v7.27_RUS.apk
WeatherPro+v2.3.apk - weather + widget for ch. screen
Tiny_Compass_v1.2.1.apk
WAFA-B-2.0.1147-prodc.apk
xlive_2.1.3_mod_icq_status.apk
VPlayer+Video+Player+v3.1.8+FULL+.apk
Luks Manager - encryption - Mounts the encrypted file as a folder
Notepad+ from the market
Terminal emulator.
Games:
250++Solitaire+Collection_2.2.0.apk
preferans.apk
Preferans_v1_2_6.apk
Angry_Birds__1.6.1.apk
Angry_Birds__3.1.2.apk
ChessBuddy_1.02.apk

GPS: Navitel_full_7.5.0.0_RePack

*How to login Recovery menu? With the device turned off, press the VOLUME_UP + POWER keys simultaneously. Navigation with volume keys, selection with on button.

*The radio does not want to tune to a flat frequency - 107.0. In the settings, set the region to Russia.