Android-Generic Project - PC/GSI Build Automation Toolkit

Search This thread

cjeu100

Senior Member
Jan 26, 2020
221
114
That is correct, but I think he's asking about Android Automotive, not Android Auto. Android automotive runs on the cars head unit hardware and is a totally different project than Android Auto.
Thank you so much for clarifying.
@mahir555 Darkmatter developers have made Internal-Audio-Recording (GearRec) using R_Submix {they say its the first public android-x86 nougat to have this}
* And they give credits to youling257 for initially making it possible for android-x86_nougat on March-2020.
https://groups.google.com/g/android-x86/c/ATpYSixSqoQ/m/h2oV1IiSAQAJ
in here buin.. @gmail.com is hmtheboy from darkmatter. I suggest you read this thread and try recording internal audio.
 
  • Like
Reactions: mahir555

cjeu100

Senior Member
Jan 26, 2020
221
114
My question might not belong to this thread, but are there android games that work on these builds?
I know for apps to run well they must support x86 libraries, so far i haven't had any luck running any...
Is there a specific thread for x86 games?
Bro now since the rise of chrome os google is getting developers to optimize their apps for x86 architecture so we are lucky. Game developers even add keyboard and mouse support (war robots have added keyboard mouse support for chromebooks)
So x86 android is getting a chance finally.
Tencent games don't have x86 but gameloft and aerofly, garena have support for x86 games. And only x86 games show on the play store in b12
Octopus doesn't work but there's a modded version of octopus keymapper which will work on androidx86
And tincore is unstable but works. And if you want to do gaming then install android os built by gamers that fix errors and optimized for games to fix graphical glitches and compiling resources bug. Android gaming os also have keymapper. Unless your game needs android 10 you should try those gaming android. Built by gamers for gamers. most importantly they also have arm apps support
 
Last edited:

electrikjesus

Recognized Contributor
Apr 10, 2008
2,970
5,039
Grand Rapids, MI
Bro now since the rise of chrome os google is getting developers to optimize their apps for x86 architecture so we are lucky. Game developers even add keyboard and mouse support (war robots have added keyboard mouse support for chromebooks)
So x86 android is getting a chance finally.
Tencent games don't have x86 but gameloft and aerofly, garena have support for x86 games. And only x86 games show on the play store in b12
Octopus doesn't work but there's a modded version of octopus keymapper which will work on androidx86
And tincore is unstable but works. And if you want to do gaming then install android os built by gamers that fix errors and optimized for games to fix graphical glitches and compiling resources bug. Android gaming os also have keymapper. Unless your game needs android 10 you should try those gaming android. Built by gamers for gamers. most importantly they also have arm apps support
But they are using closed sourced apps and sources, keymappers, etc. And on top of that Nougat... Ewww. LOL
 

bickfordman

Senior Member
Oct 14, 2010
254
38
i can get the GSI Roms on my Oneplus 8 pro but every rom i try there is a problem with sms text messaging. it doesnt receive them , unless you reboot your phone.
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,970
5,039
Grand Rapids, MI
AG-10 Generic Builds - 2020-11-03
!! Please remember to not quote these update posts, or any of the OP's !!

It's been a busy month for x86 builds. Lot's of advances across Pie/Q/R, so we will start things off with a few updates for AG. First off, I have updated the website again, so make sure you let me know your thoughts. And if any of you are web devs, I'm always open to improvements & bug fixes if you spot any. https://android-generic.github.io

For the builds this round, we have a bunch of updates under the hood for things. Changes in init, kernel, and UI improvements across the board. BoringdroidSystemUI updates that bring BoringdroidSettings into the mix, as well as a few other tweaks here and there. Check the changelogs for the details.

ROMs included this round:
  • Bliss OS
  • CarbonROM

Build Info

All Builds Include:

I was also able to get a website started for Android-Generic Project: https://android-generic.github.io

Gearlock kernel command Notes:
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.

Builds that have been uploaded:
  • AG-10-Bliss-OS-android_x86_64-202010270916_k-kernel-5.8-si-next_m-20.1.0_pie-x86_dgc-cros-nb_gms_cros-wv.iso
  • AG-10-CarbonROM-android_x86_64-202010291641_k-kernel-5.8-si-next-fs_m-cr-8.0_dgc-q-x86-generic_gms_cros-wv.iso

Known new issues:
  • Sleep states aren't working right on a few machines. Some can cause SystemUI to restart. Check VULKAN mode notes
  • Some machines still have volume/sound issues, use 3rd party EQ or volume control.
  • Nativebridge (ARM app compatibility) is still not working in Android 10. Please stop complaining that you can't play your favorite game on these builds. If Intel can't even get their own Houdini code to work in Android 10, what do you honestly think we can do about it? If you really want to help the cause, checkout Michael Goffioul's projects - https://github.com/goffioul/ax86-nb-qemu & https://github.com/goffioul/ax86-nb-qemu-guest and help get a real Open Source solution going.

Download:

Website has been created and has a download link
https://android-generic.github.io

Changelogs:

Code:
Changelogs are working for all AG builds and can be found in the download folder with the builds

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.
 

pepelillo

Senior Member
May 6, 2009
61
5
Iḿ also interested in Android Automotive native. I've been researching for months (not developer skills in my case, hardly I'm able to compile some AX86 Project). I've tested the Android Automotive in Android Emulator and for me is interesting for my projects, but honestly withount the companion libraries for every car is mostly useless (but BT HF profile). Project Celadon has some Android Automotive binaries but recently only support VM scenarios (I don't know how to install baremetal to test). Also you can check if you can deploy Android Automotive (celadon binaries) under ACRN or another hypervisor but this is Far from my skills.

I'd like to see if Generic Android can compile the Android Automotive with it's framework as you can compile this flavour as a lunch option in AOSP, maybe is possible but I haven't tried. If somebody tries it (with better skills than me) would be great to see the results.


I'm wondering if its possible to compile a different flavour of AOSP with this (e.g. TV or Automotive). I've been poking around a bit, and most of the documentation seems to be talking about switching vendors. If it is possible, I'd be happy to do any necessary modifications myself of course, just wanting to get some pointers on where the best place to look would be.
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,970
5,039
Grand Rapids, MI
Iḿ also interested in Android Automotive native. I've been researching for months (not developer skills in my case, hardly I'm able to compile some AX86 Project). I've tested the Android Automotive in Android Emulator and for me is interesting for my projects, but honestly withount the companion libraries for every car is mostly useless (but BT HF profile). Project Celadon has some Android Automotive binaries but recently only support VM scenarios (I don't know how to install baremetal to test). Also you can check if you can deploy Android Automotive (celadon binaries) under ACRN or another hypervisor but this is Far from my skills.

I'd like to see if Generic Android can compile the Android Automotive with it's framework as you can compile this flavour as a lunch option in AOSP, maybe is possible but I haven't tried. If somebody tries it (with better skills than me) would be great to see the results.
I've added the bits for Android Auto into AG for Android 11, and will be working on the documentation of things over the next few weeks.
 
  • Like
Reactions: mauam

electrikjesus

Recognized Contributor
Apr 10, 2008
2,970
5,039
Grand Rapids, MI
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.
 
Last edited:

IamTheBRAVE

Senior Member
The default firefox installed kept crashing since first boot so i installed the latest version from apkmirror and it works great now. I use kiwi browser as my daily, though, so no biggie...
Play store crashed once but reloaded just fine afterwards. And i needed to activate magisk to grant su to apps. Other than that... this is the classiest looking android version yet! Love everything about it...
Broken records aside, did i say thank you yet? Thank you! 😀
And merry chrismas🎄
 

g000n

Senior Member
Sep 4, 2015
417
144
Thanks to the Bliss OS team for your hard work, can you please make a Bliss OS for PC able to run live from USB with persistent data? so we can carry it with us?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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...