Android-Generic Project - PC/GSI Build Automation Toolkit

Search This thread

virbr0

Member
Apr 24, 2021
5
1
Anybody tried this on QEMU on WIndows? I seem to be bootlooping in AG10AOSP and AG11Bliss both (latest version), gives some readonly disk error. This is my qemu command line:
Code:
qemu-system-x86_64 -accel hax -m 4096M -cpu Skylake-Client-v1 -cdrom 'F:\Etc\AG Builds\AG-AOSP-10-android_x86_64-202009231416_k-kernel-5.8-si-next-rmi_m-android-10.0.0_r41_dgc-q-x86-generic_cros-wv.iso' -drive file=AG10AOSP.qcow2,if=virtio,readonly=off -M q35 -display sdl
 

cjeu100

Senior Member
  • Jan 26, 2020
    190
    102
    Use Bliss OS 11.13 and install the mesa 20.1.0 gxp from sourceforge, then it works. Someone posted a solution on bliss os discord server https://discord.gg/SyFwWuSyzu
    Anybody tried this on QEMU on WIndows? I seem to be bootlooping in AG10AOSP and AG11Bliss both (latest version), gives some readonly disk error. This is my qemu command line:
    Code:
    qemu-system-x86_64 -accel hax -m 4096M -cpu Skylake-Client-v1 -cdrom 'F:\Etc\AG Builds\AG-AOSP-10-android_x86_64-202009231416_k-kernel-5.8-si-next-rmi_m-android-10.0.0_r41_dgc-q-x86-generic_cros-wv.iso' -drive file=AG10AOSP.qcow2,if=virtio,readonly=off -M q35 -display sdl
     
    Last edited:
    • Like
    Reactions: virbr0

    jacko69210

    Member
    Dec 10, 2020
    30
    17
    FR
    Kernel 5.10.9 is good for both old and new PC, I have tested it on multiple PC, and it works, support more hardware than the kernel 4.19 used in Bliss OS. Usually newer kernel is the best. Upgrading your kernel can be compared to updating drivers in Windows.
    Hi cjeu100,

    Thanks a lot for your usefull advices on this thread... :cool:
    I just tested Gearlock on my AIO MSI Pro 22XT 9M-029XEU with android-x86 8.1--r5.
    very simple to use : I'm now with the latest xanmod Kernel 5.10.26 (THX to HMTheBoy154)

    I will be now able to re-test the android-x86 9.0-r2 where i had worries with Wifi Intel 3168 NGW... or finally switch to the BLISS 11.13 Rom :unsure:

    @+ (y)
     

    Attachments

    • MSI.jpg
      MSI.jpg
      112.4 KB · Views: 46
    Last edited:
    • Like
    Reactions: cjeu100
    May 1, 2021
    8
    0
    I got this error from running AG-11-Bliss_OS-14-x86_64-202012190914_kernel-5.8-si-next-fs_r_egapps_libndk_wv_m in virtualdub and running it from a usb drive with rufus-3.13 , it says something about os error 30 failed to remove existing /system/xbin/su and fails to load its non installer mode, I wanted to test it before even installing it, also tried to run it on install made on virtualdub no luck in getting it to run, for some reason I have no problem running android x86 iso images like android 9 but I have problems getting Bliss OS to run at all either in virtualdub or from my usb drive, is it the iso image the problem or what it thinks my hardware should be? I have two 3D cards both nvidia 3D cards, and running an intel i7.

    Device name
    Processor Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz 3.60 GHz
    Installed RAM 32.0 GB
    System type 64-bit operating system, x64-based processor
    Pen and touch No pen or touch input is available for this display
    Operating System: Windows 10 Pro 64-bit (10.0, Build 19042) (19041.vb_release.191206-1406)
    System Manufacturer: Gigabyte Technology Co., Ltd.
    Memory: 32768MB RAM
    Available OS Memory: 32684MB RAM
    Page File: 12831MB used, 24717MB available
    Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 12
    BIOS: F12w (type: UEFI)
    Card name: NVIDIA GeForce GTX 1050 Ti
    Manufacturer: NVIDIA
    Chip type: NVIDIA GeForce GTX 1050 Ti
    DAC type: Integrated RAMDAC
    Device Type: Full Device (POST)
    Device Key: Enum\PCI\VEN_10DE&DEV_1C82&SUBSYS_11C3196E&REV_A1
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
    Device Problem Code: No Problem
    Driver Problem Code: Unknown
    Display Memory: 20360 MB
    Dedicated Memory: 4018 MB
    Shared Memory: 16342 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)

    Card name: NVIDIA GeForce RTX 2060
    Manufacturer: NVIDIA
    Chip type: NVIDIA GeForce RTX 2060
    DAC type: Integrated RAMDAC
    Device Type: Full Device (POST)
    Device Key: Enum\PCI\VEN_10DE&DEV_1F08&SUBSYS_20673842&REV_A1
    Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
    Device Problem Code: No Problem
    Driver Problem Code: Unknown
    Display Memory: 22322 MB
    Dedicated Memory: 5980 MB
    Shared Memory: 16342 MB

    anyway this is my desktops information that may be needed can you recommend an android 10 or android 11 that can run on my hardware?
    again I would prefer one on an emulator that newer androids, I do own a android 10.1 tablet with 10 on it

    I use stuff like Epic Games Launcher so I do need to keep windows 10 running for my free games from them, otherwise I am just playing with android on my desktop, I can dual boot linux and ubuntu on my pcs, but I currently am not dualbooting os at this time.

    I have not used gearlock, nor do I think I need it on my home computer, that software program I heard of but never used before, my tablet is an samsung brand, I am guessing gearlock is a pc based program I have not look much into that software, never used it with linux or android x86 before.
     

    Attachments

    • VirtualBox_Android X86_01_05_2021_14_17_55.png
      VirtualBox_Android X86_01_05_2021_14_17_55.png
      5.3 KB · Views: 23
    May 1, 2021
    8
    0
    I also tried using AG-AOSP-10-android_x86_64-202009231416_k-kernel-5.8-si-next-rmi_m-android-10.0.0_r41_dgc-q-x86-generic_cros-wv in virtualdub seems to load gearlock recovery mode then loop reboots into gearlock reovery mode, twice at least, I have not tried it with my real hardware, but I am not sure since Bliss OS doesn't seem to be as easy to use as android x86 images work on my hardware at least this boot into the android these builds I have not found any Bliss OS that run yet for me. maybe I am just downloading the wrong images or need some boot command to make them work with nvidia and intel i7 hardware etc.. I have not put AG AOSP 10 on my usb drive yet to see if it loads anything other than gearlcok reovery mode which doesn't seem to run the android x86 build yet. again I could be missing a command that I need to get them to work on my hardware.
    again the reason I am using virtualdub is because I do need windows for pc video games and just playing with android os on my pc, since I also own a android tablet. also played with using Nox its android 7.1 for windows which is old, and MEmu software also an android 7.1 os for windows, I prefer android that doesn't spam with video games, which is ok that if offers them but I also use it for my ebooks etc.. and Nox does run Kindle app but fails to run it in the correct size window on my desktop, so even thou that software can run it, it doesn't run it correctly in my display on my pc. but I do also play android video games once and a while. with the nor software you can use microsoft Launcher runs on it, unlike MEmu which will not let you set microsoft Launcher as the default desktop android screen thats why I prefer Nox player on windows to that MEmu one and NoxPlayer is coming out with an android 9 version around may 6 at least its startup screen says that.
     
    Last edited:

    VTArxelus10873

    New member
    May 9, 2021
    2
    0
    Bliss 14 working on a N4000 laptop with 4GB ram. Bluetooth, of course, is not working, but everything else is working, even GPS. Is there a timeline on the proper Bluetooth fix, or is there maybe a hotfix that can be performed in the meantime? I have the Bliss server on Discord if you'd like an error log for reference.
     

    electrikjesus

    Recognized Contributor
    Apr 10, 2008
    2,939
    4,993
    Grand Rapids, MI
    Bliss 14 working on a N4000 laptop with 4GB ram. Bluetooth, of course, is not working, but everything else is working, even GPS. Is there a timeline on the proper Bluetooth fix, or is there maybe a hotfix that can be performed in the meantime? I have the Bliss server on Discord if you'd like an error log for reference.
    I need the contents of a logcat & lsmod please
     

    electrikjesus

    Recognized Contributor
    Apr 10, 2008
    2,939
    4,993
    Grand Rapids, MI
    AG-11 Android-x86 mod - x86_64 Generic - Google Kernel 5.4 LTS - Mesa-21.1.0 - Release Date 2021-05-09/10
    !! Please remember to not quote these update posts, or any of the OP's !!

    We're getting some more time for development recently, so I thought we would start making a couple more alpha releases of Android 11 for PCs.
    This build is mostly Android-x86 (Thanks to Mauro Rossi & Michael Goffioul for all the work on the bringup) , removing some packages, adding some configs, etc. Also only FOSS, and including BoringdroidSystemUI as the primary Desktop UI method.

    Updates:
    • Android 11 r35
    • Google's android-12-5.4-lts kernel, with x86 PC additions
    • Mesa 21.1.0
    • Minimal FOSS Apps (Aurora Store/Aurora Droid)
    • Completely re-worked graphics stack to be more inline with Android-x86 pie

    Notes on sleep states:
    - They work on most machines when using Vulkan mode or gbm_gralloc. DRM/GRALLOC mode results may vary.

    To run in Vulkan mode:
    - You will need to select Vulkan from advanced grub menu, or manually add "VULKAN=1" to Grub command line

    Builds Details:
    • ax86-11-android_x86_64-202105031742_k-5.4.112-android_m-21.1.0-devel_w13_foss.iso
      Unrooted - This build includes mesa-21.1.0, and comes with various updates to our FOSS apps suite (This also includes the first Astian FOSS app, Midori browser) **No working su binary in this build**
    • ax86-11-android_x86_64-202105101056_k-5.4.112-android_m-21.1.0-devel_w13_foss_magisk.iso
      This build includes Magisk as default SU, as well as a couple fixes to init for certian devices as well as ability to access lib/modules. Also adds updates for BoringDroid SystemUI/Settings to allow for selection of fullscreen apps.

    Native Bridge (Source: Google x86_64 Emulator Images):
    Is pre-enabled in these builds. ARM/ARM64 support included

    Known new issues:
    • Some install issues have popped up, If you have issues, use the included .exe installer or the one from Supreme-Gamers
    • BoringdroidUI PC Mode launches all apps maximized. We are looking into this issue still
    • Sleep states might not be working right by default on non Vulkan & IA-Hardware-Composer builds (Still working on it). Some can cause SystemUI to restart (lockscreens won't be of any use due to this)
    • Power buttons may still not work on a few machines.
    • Some SDcards might not mount right. Please use SDCARD=/dev/sdx from Grub or manually mount from alt-f1 console

    Changelog: NOT WORKING RN, will fix next builds Fixed now :)
    Code:
    Changelogs are working again, check the build download folder for the changelogs.

    Downloads
    Can be found in the sourceforge repo:

    Thanks, and have a Blissfull time!!

    Head on over to http://blissroms.com for info on Bliss or http://blissos.org for more info on Bliss OS. Also checkout more of what we're doing as a nonprofit at https://blisslabs.org. We're always running around wearing multiple hats on Bliss too, so we are looking for developers, designers, social media personnel. If that's you, you can find the Join Team Bliss link on our nonprofit page.
     
    Last edited:
    • Like
    Reactions: IamTheBRAVE

    Top Liked Posts

    • There are no posts matching your filters.
    • 1

      Android-Generic Project 2.0


      Initial alpha release of Android-Generic Project 2.0 has been pushed to GitHub

      Those that would like to test it in its current state, please supply feedback on what improvements you would like to see, or any feature requests.

      Website has also been updated with new builds
      Check the project readme for full details
    • 15
      BhvNtbW.png


      Android-Generic Project - Android for PCs & GSI devices

      What is Android-Generic Project?:

      Android-Generic is a collection of scripts, manifests & patches that allow for rapid prototyping of Android projects based off AOSP to produce generic images for Android GSI or Linux PC hardware.

      For a more in-depth description of the goals and progressions leading up to this project, please read
      this blog post

      Vision:

      To fill you all in on the grand scheme of things with Android-Generic, the plan come in stages.

      * Stage 1 is laying the groundwork for all ROMs to build both PC and GSI builds by supplying them with a standard set of minimal patches. Thanks to Android-x86 & PHH-Treble, thats done. now we collect them and make them easy to apply for everyome. DONE

      * Stage 2 is collecting variations of the conflicts those standard patches could potentially have and simplifying the process as we go. This is where all the Android ROMs come in ;) STARTED

      * Stage 3 is to use the variations of conflict resolutions from each ROM folder to further automate the process and have vendor patches be automatically figured out by trying each resolution until one sticks. STARTED

      * Stage 4 is to continue to automate elements of the process until things are almost too easy STARTED

      -----------

      Development Chats:

      Telegram:

      GSI/Treble

      PC/x86/x86_64


      Resources:

      Images:
      Android-Generic Logos

      Basic Project Info

      This is a development project for ROM developers that want to add PC or GSI support to their builds.

      Prerequisites:

      You will need to have synced a ROM and know how to build Android prior to adding this to your build envirnment.

      ROMs that have PC builds (so far):

      - BlissROM
      - AOSP
      - Tesla
      - WIP - Tipsy
      - WIP - Lineage OS
      - WIP - Validus
      - CarbonROM
      - WIP - PixelExperience

      ROMs that have GSI builds (so far):

      - BlissROM
      - AOSP

      Please make sure you're well versed in building AOSP: AOSP building instructions before proceeding.

      What you need to get started

      Follow the link below, and checkout the full project documentation. I'll try to update the readme as often as possible to allow you all to keep up with changes as things are going to ramp up exponentially.

      android-generic

      Credits

      We'd like to say thanks to all these great individuals first:
      @phhusson @cwhuang @maurossi @goffioul @me176c-dev @bosconovic @farmerbb @aclegg2011 @eternityson @utzcoz and many others

      And these great teams second:
      @Google @LineageOS @GZR @OmniROM @SlimROM @ParanoidAndroid and many others, for you still lead the way for Open Innovation in the Android community.

      XDA:DevDB Information
      Android-Generic Project, Tool/Utility for the Android General

      Contributors
      electrikjesus, jackeagle

      Version Information
      Status: Alpha

      Created 2020-07-11
      Last Updated 2020-08-16
      5
      AG-11 Generic Builds - 2020-12-19
      !! Please remember to not quote these update posts, or any of the OP's !!

      OK, it's been a little while since we've posted any updates in here. So I'd like to first announce that our PC's now have Android 11 (before most phones even get it). With this first round, we have a minimal Bliss OS, using kernel 5.8, mesa 20.1.0, etc.

      But wait, that's not all, as we've also put together a solution for extracting libndk_translation, gapps, etc. from Google's emulator images, and we've worked out most of the kinks in getting not just gapps, but also ARM & ARM64 apps working in our PC builds with it. Source is WIP, but you can find it here:
      https://gitlab.com/android-generic/android_vendor_google_emu-x86

      Also, since Android 11 made our past method of hiding the navbar obsolete (overscan method), we have to use the old qemu.hw.mainkeys as a backup plan, so there is a script (toggle_nav.sh) that can be used to disable/enable the soft navbar and use Taskbar if you prefer. Just remember that you will need to remount / as RW (mount -o remount,rw /dev/loop(0) /) Use cat proc/mounts to see where / is mounted for your install.

      But wait, there's more...
      New member of Bliss, and creator of Gearlock, @AXIM0S just happens to have a few tricks up his sleeve still for A11, and his first one comes in the form of Rusty-Magisk ( https://github.com/AXIM0S/rusty-magisk/releases/tag/v0.1.3 ), allowing us to have a built in compatibility layer with Magisk. Currently, most magisk modules aren't working, but development is ongoing.

      Gearlock is also working with most A11 builds too, but there are some issues, so instead of installing it for you by default, you all can make that decision on your own. Some of our builds will have a _g in the filename, representing that it contains a Gearlock installer binary in system/etc/. Just follow the instructions from gearlocks main thread to figure out how to install it. Be careful though, as it is easy to mess things up when using low-level tools like Gearlock. Use common sense please.

      We will be updating the website with links soon, so please keep posted.
      https://android-generic.github.io

      With all this being said, if you or anyone you know is interested in working along side me and the rest of the team, please reach out and let us know. Thanks!!

      Build Info

      All Builds Include:
      • Updated to Kernel-5.8
      • Script for disabling navbar
      • Taskbar (Desktop Mode Launcher)
      • Launcher3 (normal tablet mode launcher)
      • Lots more, check the changelog

      Gearlock info:
      ( https://supreme-gamers.com/r/gearlock-custom-recovery-replacement-for-android-x86.40 )

      NOGFX=0 - Do not override kernel CLI options (needed if you plan on using Vulkan mode)
      NORECOVERY=0 - Do not enter recovery or show countdown for it (should not combine any other Gearlock options with this)
      NOSC=0 - Do not supercharge the system partition/image on boot
      ALWAYSRECOVERY=0 - Always boot into recovery first.

      !!WARNING!! The builds that use Kernel-5.2+ are no longer compatible with the AUTO_LOAD=old kernel command line option. If you are using this option to boot, then you will not be able to. It will bootloop.

      PLEASE NOTE I recommend everyone testing to also use this in Vulkan mode or boot using gbm_gralloc, as I am considering making it the default. Vulkan mode can be done from the Advanced grub menu if you installed using the bootable installer, or if you used a different grub, you will want to add "VULKAN=1" to the grub entry before the word "quiet". If your device doesn't support Vulkan, you can add "GRALLOC=gbm" to the same place in your grub entry. Sleep states should work fine after that.
      Other bootloop issues can also be solved by booting with GRALLOC=gbm command -line option.

      Recommend Installers (easy mode):
      These builds will work with Axon's installer:
      As well as ours:

      Other installation methods (Virtualbox, EFI stub, etc.):
      Please review the Install section of the Bliss wiki: https://wiki.blissroms.org/index.php?title=Bliss_OS

      Builds that have been uploaded:
      • AG-11-Bliss_OS-14-x86_64-202012190914_kernel-5.8-si-next-fs_r_egapps_libndk_wv_m.iso

      Known new issues:
      • Sleep states aren't working right on a few machines. Some can cause SystemUI to restart.
      • Some machines still have volume/sound issues, use 3rd party EQ or volume control.
      • Bluetooth on some devices
      • Rotation not working on some devices
      • Most magisk modules
      • Some ARM/ARM64 apps still do not work. Gimme logs
      • No Alt-f1/f7 console this round. If you need to mount as RW, or need access to root console, please boot in debug mode or add DEBUG=(0/1/2) for logging level.
      • Some soundcards still start up quiet AF, please use an EQ app like Volume Booster by Goodev or follow the alsa instructions from Android-x86 docs/groups.
      • Widevine is not working yet, enjoy most other video formats for the moment
      • Firefox browser force quits on some machines. Will be updating asap

      Download:

      Website has been updated with download link added to the "Other AG Flavors" section of the site:
      https://android-generic.github.io

      Changelogs:

      Code:
      Way too many changes to list here. Please see the changelogs for each build, or check the history in the Android-Generic repo to see what we're working on. https://gitlab.com/android-generic/vendor_android-generic/-/commits/r11

      Thanks, and #stayblissful ;)

      Head on over to http://blissroms.com for info on Bliss or http://blissos.org for more info on Bliss OS. And while you're there, feel free to checkout more of what we're doing as a nonprofit. We're also always looking for developers, maintainers, designers and social media peeps to volunteer their time. If that's you, you can find the Join Team Bliss link on our nonprofit page.
      4
      Downloads

      These are experimental builds and since I want to focus on helping developers through this project, we will not be supporting any of these builds. They are strictly for testing purposes only.

      AG Website: https://android-generic.github.io

      Downloads so far:
      PC
      • Bliss
      • AOSP
      • Tesla OS
      • CarbonROM
      • PixelExperience
      • Dirty Unicorns
      • Resurrection Remix
      • LineageOS
      • Bootleggers

      GSI:
      • None
      4
      I've also been having this same issue on VMware Workstation, using a 64GB drive. The issue seems to come from GRUB somehow. The OS seems installs fine without GRUB, but obviously, this is a problem, as GRUB is necessary for it to boot. Choosing to install GRUB is what causes this issue.

      EDIT: I wanted to point out that the issue seems to be independent of hardware. It occurs both with SATA and IDE drives, and the GRUB part makes me think it's probably not a VM configuration error, but rather some kind of error with calculating space requirements in the installer.

      I will put looking into the installer on my list of things to do soon
      3
      Is there any news on this?
      Sorry, nothing yet. I had to leave out of state for work and haven't gotten back home yet. It's been about a month on the road so far...