Android-Generic Project - PC/GSI Build Automation Toolkit

Search This thread

PremiumMediocre

Senior Member
Oct 5, 2012
105
15
I've been able to get touchscreen to work for Linux (tested for kernels 4.19 - 5.4, for both Manjaro and Mint) by compiling this goodix touchscren driver. This goodix driver is required for the chuwi hi12 tablet among others. I don't know how to build it it for a bliss install so I humbly submit this driver for your consideration for future inclusion.
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,938
4,993
Grand Rapids, MI
I've been able to get touchscreen to work for Linux (tested for kernels 4.19 - 5.4, for both Manjaro and Mint) by compiling this goodix touchscren driver. This goodix driver is required for the chuwi hi12 tablet among others. I don't know how to build it it for a bliss install so I humbly submit this driver for your consideration for future inclusion.
Do you know if there is a separate kernel module floating around for it?
 

PremiumMediocre

Senior Member
Oct 5, 2012
105
15
Do you know if there is a separate kernel module floating around for it?
I don't think so. The driver I linked to is just a modified clone from the mainline Linux which added better support for pen input and additional chip versions.

It builds on the modification which added support for the pen. The one I linked to in my previous post then added support for the 9111 chip version (9110 was already supported).
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,938
4,993
Grand Rapids, MI
Is it possible for bliss OS to switch to the new houdini android 11 in chrome OS?
Libndk from the emulator images cant run any game, its performance is slow
I pulled the latest available houdini from the v90 recoveries for the latest 11.14 builds, and all signs point to Google still using Android 9 on it.
If you can get me a link to a compatible recovery image with Android 11 houdini, please do ;)
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,938
4,993
Grand Rapids, MI
I don't think so. The driver I linked to is just a modified clone from the mainline Linux which added better support for pen input and additional chip versions.

It builds on the modification which added support for the pen. The one I linked to in my previous post then added support for the 9111 chip version (9110 was already supported).
I searched the git webz and didn't find much we could use for that that wouldn't mess up other models. so I'm still looking
 

PremiumMediocre

Senior Member
Oct 5, 2012
105
15
I searched the git webz and didn't find much we could use for that that wouldn't mess up other models. so I'm still looking
I see. I was under the impression that it only added functionality. I did a compare and I now see that the models of:

```
{ .compatible = "goodix,gt1151" },
{ .compatible = "goodix,gt5663" },
{ .compatible = "goodix,gt5688" },
```
are not included in the the newer driver, while it added only gt9111. Not sure if I'm interpreting that correctly but I'm sorry if I have misled.

Would it be possible to include the new driver module under a new name that isn't automatically used so that users could insmod it themselves after blacklisting the old goodix driver?
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,938
4,993
Grand Rapids, MI
I see. I was under the impression that it only added functionality. I did a compare and I now see that the models of:

```
{ .compatible = "goodix,gt1151" },
{ .compatible = "goodix,gt5663" },
{ .compatible = "goodix,gt5688" },
```
are not included in the the newer driver, while it added only gt9111. Not sure if I'm interpreting that correctly but I'm sorry if I have misled.

Would it be possible to include the new driver module under a new name that isn't automatically used so that users could insmod it themselves after blacklisting the old goodix driver?
That's the kind of creative suggestion I like to hear ;) Will see if we can narrrow down just the modules for it and compile those in external/kernel-drivers as old_goodix or something, then in device/generic/common/init.sh, we can match the device product ID to swap out the modules ;)
 

PremiumMediocre

Senior Member
Oct 5, 2012
105
15
That's the kind of creative suggestion I like to hear ;) Will see if we can narrrow down just the modules for it and compile those in external/kernel-drivers as old_goodix or something, then in device/generic/common/init.sh, we can match the device product ID to swap out the modules ;)
Excellent! Let me know if there is anything I could do to aid the effort.
 

Ictcreations

Member
Feb 29, 2012
24
2
Bliss Version 14... I read post about it been made available for download. i have looked everywhere via bliss clicked on as many links as i can, but i am always going round in circles. there is no acual direct link anywhere? am i missing something?
 

Ictcreations

Member
Feb 29, 2012
24
2
i found the link for it at last, sorry that was my fault.

It is working beautifully, and for me the bugs ive come across are:

1> Google Chrome... After a couple of mins it stops working and i get told to either wait or force close so that browser is not really usable atm.

2> This bug relates to both bliss 11, and the latest bleeding edge BlissOS14 (i do understand that its extremely early days for this one, so bugs bound to be present). I have a MS Surface Go 1st gen 2019. The issue is that the power button just turns the screen off. Even if i hold it in, the power menu does not show up. There is also no way to shut it down from either taskbar launcher, or stock as there are no power options. Eventually the screen just stops turning back on and i have to hold it in to force reboot the sarface itself. I have read that that is a bug with hardware/firmware combination, but I would still have expected the power menu to show?

I have also posted bug 2 on the bliss OS 11 thread just to be consistant and to make it trackable.
 

IamTheBRAVE

Senior Member
  • i found the link for it at last, sorry that was my fault.

    It is working beautifully, and for me the bugs ive come across are:

    1> Google Chrome... After a couple of mins it stops working and i get told to either wait or force close so that browser is not really usable atm.

    2> This bug relates to both bliss 11, and the latest bleeding edge BlissOS14 (i do understand that its extremely early days for this one, so bugs bound to be present). I have a MS Surface Go 1st gen 2019. The issue is that the power button just turns the screen off. Even if i hold it in, the power menu does not show up. There is also no way to shut it down from either taskbar launcher, or stock as there are no power options. Eventually the screen just stops turning back on and i have to hold it in to force reboot the sarface itself. I have read that that is a bug with hardware/firmware combination, but I would still have expected the power menu to show?

    I have also posted bug 2 on the bliss OS 11 thread just to be consistant and to make it trackable.
    The way you describe it looks like the bug i have. The screen turns black (not off) but no button seems to work including power button.
    The way to get out of it without force shutting the pc is to put it to sleep (Fn+F3) then push the power button. After waking, systemUI restarts and unlocks the lockscreen again (sometimes a soft reboot occurs with bootanimation playing)
     

    OakBricks

    New member
    Apr 7, 2021
    4
    0
    So i have a bug on VMWare and VirtualBox (With and Without debug mode and nomodeset) where it just brings me to a shell, no other information the only logs i can visibally see is some Network or Camera service failing to start in a loop.

    TLDR, Android does not boot into a GUI and gets stuck on a shell on VM software no matter what
     

    electrikjesus

    Recognized Contributor
    Apr 10, 2008
    2,938
    4,993
    Grand Rapids, MI

    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
     
    • 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...