Gearlock android что это

Software GearLock — Custom Recovery Replacement for Android-x86 7.3.3

GearLock is a command line program to help you customize & install custom software in your android-x86 OS. It has the capability of running in both GUI and TERMINAL with a early-recovery mode. GearLock has been a part of DarkMatter project until now, but I decided to make it universal for any android-x86 OS

Feature List

    Install any custom kernel / mesa or pretty much anything. There are also tons of other extension & packages available in our RESOURCES section for you to install with a powerful package-manager.

Install flashable zip files. (BETA)

  • Use RECOVERY-MODE even before your android starts.
    • MidNight Commander FileManager integration in recovery mode.
    • Repair corrupted EXT partitions before booting up the OS.

  • Decompress / extend the size of your system image

    Backup & restore your whole data

    Mesa Version faker

    Change CPU governor & frequency

    Change MAC Address

    Update google apps directly from a opengapps package

    Install latest/custom magisk version directly from github source by patching the ramdisk. (on-device)

    GoogleLess Mode feature

    Unity Game Engine Crash Fix

    Resolve the issue for magisk installation, in which magisk makes the tty unusable

    SU-Handler for switching between SuperSU & MagiskSU

    Introducing GearProp , which can force overwrite any system property.

    Purge / remove extra kernel modules from your system

    MultiLang support with UTF8. (EN, VN, CN, ES)

    Record screen with audio without any app. (Directly from gearlock with internal audio support)

    Very developer friendly with tons of easy to use tools

    Disable / Enable Laptop touchpad or keyboard

    Extensible by installing custom extensions

  • And many more! This list is probably outdated, lol.
  • Supported android-x86 OS List

    1. Official Android-x86
    2. Official PhoenixOS & DarkMatter
    3. Official PrimeOS
    4. Official BlissOS
    5. Official RemixOS
    6. LineageOS x86

    Boot-Flags

    You can control the behavior of GearLock early recovery screen with boot-flags.
    There are three kinds of flags you can use

    • NORECOVERY
    • ALWAYSRECOVERY
    • FIXFS
    • NOGFX

    In simple words, GearLock brings a whole range of pure linux utilities. Which includes bash, python, coreutils, nano and more ! (Runs system independently, meaning even if you delete the whole system these are still executable)

    Not only that, let me introduce you to GearLock-Dev-Kit. GDK is the thing which you can use for building such package/extension. There is also a ready-to-use kernel package-template alongside custom-core package for making extensions and so on.

    For full insights check the developer documentation

    Developer Guide

    GitHub — axonasif/gearlock: Custom Recovery Replacement for Android-x86

    Simply follow everything said at the link below:

    Installation and Updating

    How it looks and works like

    These previews can be really old from what it’s like in the latest version

    Metro Interface (Live system GUI)

    Metro Package Manager

    Flashable ZIP Compatibility

    If you want my honest word then you should know that about 99% of the available flashable zips out there will likely fail since they were never made for android-x86 and GearLock has nothing to do about that. In which most of them are flashable-roms which you obviously won’t be installing on android-x86. Currently I’ve had success with OpenGapps and a few other zips. Other than that will surely fail unless the developer itself implements android-x86 support.

    Читайте также:  Как уменьшить разрешение экрана андроид

    First of all I’d like to thank everyone in our community because without you guys I wouldn’t be able to do such stuffs. It’s been a pleasure to be a part of this community. Thank you.

    Special thanks to @HMTheBoy154 & @Night & @mido.fayad for bringing some awesome GearLock package & extensions alongside helping the community in various issues in their free time. They played a big role in this community They’ve been always there in the time of need.

    Thanks to the beta testers : @AngusX , @dabombUSA , @Fazeel.abbas2 , @P.B | D.B , @Kenny
    Thanks to everyone involved into the Android-x86 Project, because without it GearLock wouldn’t exist.

    Some last words from me

    I never thought I’d be able to do such stuffs before, it’s been an honor. More importantly, I really wanna thank android-x86. Because of it I could also learn a lot, yes and that includes some funny people also
    It hasn’t been easy to keep up till here. Required a lot of patience and hard work to make it here.

    Don’t forget to submit your review if you can

    Источник

    Gearlock android что это

    Android OS на x86

    В этой теме обсуждаются вопросы общие для всех Андроидов на платформе x86, конкретно проект портирования Android-х86, а также его братья, не имеющие отдельных тем обсуждения на нашем форуме.
    Android в виртуальную машину | Сайт и Форум проекта Android-х86 | Android от Intel

    Вопросы, касающиеся только проектов Phoenix OS , Remix OS x86 и Bliss-x86 , обсуждаются в своих темах.
    За работоспособность ваших устройств ответственность несёте исключительно Вы. Задавая вопрос, постарайтесь указать следующую информацию .

      Hardware List — список совместимого оборудования
        Если Вы не нашли в шапке или в листе совместимости версию для вашего компьютера/ноутбука (модификации железа), то следует попробовать разные версии и опытным путём подобрать оптимальную.

    • Графическое ускорение нормально работает на видеоадаптерах от AMD и Intel (кроме GMA 500, GMA 600, GMA 3600, GMA 3650, т.к. они основаны на PowerVR).
      Графика nVidia поддерживается начиная с Android-x86 4.4-R3; новое поколение начинает поддерживаться после выхода следующего.
    • Ситуация с поддержкой планшетов, Критическое замечание о звуке.
    • Чипы, которые реализуют одновременно и WiFi, и Bluetooth работают хуже, чем отдельные.

      Загрузочную флешку или диск необходимо записать с помощью Rufus, UNetbootin, LiLi, или WinImage. UltraISO использовать не рекомендуется потому, что созданные им флешки мало где грузятся.

    Раздел под Android рекомендуется форматировать в ext3 или ext4 (для версии 5.0 Lollipop и новее) чтобы иметь >4ГБ места под свои нужды и избежать проблем с SuperSU и другим софтом. Форматирование раздела лучше произвести до установки Android сторонним ПО (Acronis, GParted, др.): родной установщик не всегда справляется с этой задачей.

    title Android-x86 5.1-rc1
    kernel /android-5.1-rc1/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-5.1-rc1
    initrd /android-5.1-rc1/initrd.img

    title Android-x86 5.1-rc1 (Debug mode)
    kernel /android-5.1-rc1/kernel root=/dev/ram0 androidboot.hardware=android_x86 DEBUG=2 SRC=/android-5.1-rc1
    initrd /android-5.1-rc1/initrd.img

    title Android-x86 5.1-rc1 (Debug nomodeset)
    kernel /android-5.1-rc1/kernel nomodeset root=/dev/ram0 androidboot.hardware=android_x86 DEBUG=2 SRC=/android-5.1-rc1
    initrd /android-5.1-rc1/initrd.img

    title Windows
    rootnoverify (hd0,1)
    chainloader +1

    Тут default указывает номер пункта, котоый будет выбран автоматически после истечения timeout секунд. root и rootnoverify указывают с какого диска, и с какого его раздела загружать выбраную операционную систему. Как и в случае с default, нумерация начинается с нуля. Параметры загрузки прописываются в конец строки, которая начинается со слова kernel. Такими параметрами можно повлиять на многие аспекты работы Андроида с железом. К примеру настроить работу с внешним монитором.

    GRUB 2 — следующая версия GRUB. Разработчики писали GRUB 2 «с нуля», чтобы добиться переносимости и модульности.
    Используется в образах Android-x86 для компьютеров с новым UEFI-BIOS.
    Может хранить свои настроки в файле grub.cfg либо menu.lst. Обычно этот файл лежит на отдельном системном разделе EFI (ESP). Типичное содержимое:

    set timeout=60
    set gfxmode=1024×768
    terminal_output gfxterm

    Источник

    Gearlock android что это

    Introduction

    GearLock is a dynamically written bash program focused in performance with the intension of making modifications in android-x86 easier.

    It is also intended to replace the need for traditional custom-recovery software for android-x86 which are found in mobile phones.

    GearLock was made in a different perspective unlike traditional custom-recovery software for mobile phones.

    GearLock and everything within it are standalone programs and does not need to rely on the android system.

    It can be used both GUI and TTY in a user-friendly manner, including advanced CLI usage.

    Install any custom kernel / mesa or pretty much anything. There are also tons of other extension & packages available in our RESOURCES section for you to install with a powerful package-manager.

    Install flashable zip files. (BETA)

    Use RECOVERY-MODE even before your android starts.

    Decompress / extend the size of your system image

    Backup & restore your whole data

    Mesa Version faker

    Change CPU governor & frequency

    Change MAC Address

    Update google apps directly from a opengapps package

    Install latest/custom magisk version directly from github source by patching the ramdisk. (on-device)

    GoogleLess Mode feature

    Unity Game Engine Crash Fix

    Resolve the issue for magisk installation, in which magisk makes the tty unusable

    SU-Handler for switching between SuperSU & MagiskSU

    Introducing GearProp, which can force overwrite any system property.

    Purge / remove extra kernel modules from your system

    MultiLang support with UTF8. (EN, VN, )

    Record screen with audio without any app. (Directly from gearlock with internal audio support)

    Very developer friendly with tons of easy to use tools

    Disable / Enable Laptop touchpad or keyboard

    Extensible by installing custom extensions

    And many more! This list is probably outdated, lol.

    You can control the behavior of GearLock early recovery screen with boot-flags. There are three kinds of flags you can use.

    Spoiler (more details)

    • NORECOVERY
    • ALWAYSRECOVERY
    • FIXFS
    • NOGFX

    This helps you bypass the recovery countdown screen. You can either put NORECOVERY=1 in your grub-config or make a file named norecovery in your android-x86 partition.

    Grub config example:

    This lets you to auto-enter recovery mode always* without having to press ESC. Just like NORECOVERY, you can active this by grub ( ALWAYSRECOVERY=1 ) or by making a file named alwaysrecovery in android-x86 partition.

    This will auto-fix extFS on each boot from the option which you find in recovery mode.

    In other words, it will run fsck against your root partition.

    When this flag is found, GearLock does not attempt to get the best possible visuals during RECOVERY-MODE. There are some really rare cases among some users in which when GearLock tries to ensure better visuals, kernel panic happens during boot.

    Grub-Flag> NOGFX=1 File-Flag> nogfx

    Flashable ZIP Compatibility

    If you want my honest word then you should know that about 99% of the available flashable zips out there will likely fail since they were never made for android-x86 and GearLock has nothing to do about that. In which most of them are flashable-roms which you obviously won’t be installing on android-x86. Currently I’ve had success with OpenGapps and a few other zips. Other than that will surely fail unless the developer itself implements android-x86 support.

    GearLock is being proudly integrated with the following reputed distros:

    • BlissOS-x86
    • PhoenixOS DarkMatter

    If you’re working on a remarkable distro and want to bring GearLock into it then you’re welcome 🙂

    Development and Contributing

    Feel free to create a fork and help make this project even better.

    Your commits should follow Conventional Commits specification, otherwise they will be rejected.

    If you want to build GearLock then all you gotta do is run the following command:

    • From android-x86 distros (assuming you have GearLock installed)

    Then you should find the outputs at out/installer

    If you want to test bare basic functionalities of GearLock within a linux-distro for development porposes then run:

    For working over sources for the core files, take a look at core/ and core/_external_bin/

    Also check core/_lang_/ if you want to improve the language translations and concurrent strings.

    You might have noticed that there are prebuilt binaries in the repository but not their source code.

    I would need to setup a complete build system for them, what I’ve been doing was hand-compiling them.

    I will need a lot of free time to accomplish this since I’m a student, but you can surely expect this in the future.

    • GearLock dev-kit: https://github.com/AXIM0S/gearlock-dev-kit
    • GearLock core-pkg: https://github.com/AXIM0S/gearlock-core-pkg
    • GearLock mesa-pkg: https://github.com/AXIM0S/gearlock-mesa-pkg
    • GearLock kernel-pkg: https://github.com/AXIM0S/gearlock-kernel-pkg
    • GearLock dev-doc: https://wiki.supreme-gamers.com/gearlock/developer-guide

    Integration with Android-x86 source

    Adaptation for Android-Generic Project was done by: @electrikjesus

    Clone the repo into vendor/ from your aosp project root.

    Lastly, build ISO

    Android-Generic (x86/PC): build-x86 android_x86_64-userdebug

    BlissOS 11.x: build-x86.sh android_x86_64-userdebug

    Android-x86: lunch android_x86_64-userdebug && make -j4 iso_img

    Credits and thanks

    Here I’m trying to list all of the remarkable work by others which has been used to enrich GearLock.

    Without their open-minded years of hard work, GearLock wouldn’t have been the same.

    • The great legendary GNU communtiy for their free and opensource softwares.

    Источник

    Читайте также:  Usb регистратор с adas для android автомагнитол dvr u2 u3
    Оцените статью