• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[9.0][GSI] Bootleggers [Discontinued] [ARM64-A/AB]

Search This thread


Senior Member
Jun 13, 2011
OnePlus 8T
I have a quick question/request since you are building .. could you look at the battery app it seem to be a bit out of wack , 6 days since last recharge.. It only changes when I reset the app
Thanks ..


  • Screenshot_20190520-141457_Settings.png
    110.1 KB · Views: 284


Senior Member
Jun 2, 2008
  • Like
Reactions: vatsal_chandan


Senior Member
Jun 2, 2008
How about start building DotOS?

Edit: @Technical, saw your post asking about dark notifications in RR thread. DotOS notifications are themed dark. :)
DotOS is not a high customizable ROM, just medium in my opinion. I'm still trying Havoc (although another developer is compiling it), Liquid and PixelDust (again).
I'll let other ROMs for a second round, after I gave up on that other three.
  • Like
Reactions: svbarbosa


Senior Member
Oct 13, 2012
Bad news. Unfortunately, Bootleggers team removed two must-have repositories to build it:


I've tried to figure out a solution with "generic" Treble device, but couldn't find any.
Right now, development halted until Bootleggers start to be compatible again.

I'm really sorry. If anyone could help me figure out how to move on, please, drop me a message.

you don't need these repo in first place , these are already used when you sync phh repos
sync the source , apply the patches and build it.


Senior Member
Jun 2, 2008
you don't need these repo in first place , these are already used when you sync phh repos
sync the source , apply the patches and build it.
I really appreciate your help, but I'm not managing without them. Worse, I'm not being able to build Havoc using the same techniques you've thought me some months ago. I also tested Liquid and PixelDust. You know how time-consuming this could be.


Aug 11, 2018
Yes double tap to wake is present.

GSIs doen't do anything with the kernel, if you want a custom kernel you just have to flash it separately.

kernel in my device was already have double tap to wake/sleep and sweep up to wake... but why on any ROM I didn't found any settings for control it. my device is Asus X00RD, the feature was controlled by ZenMotion. please tale me, how to activate on GSI ROM? I was try using sh script but the problem is, I didn't knew name and where kernel which control it in sys. somebody help, sorry my English

Top Liked Posts

  • There are no posts matching your filters.
  • 22


    Bootleggers ROM is an aftermarket firmware based on AOSP with some patches and fixes from LineageOS and various other projects. The idea is to bring custom features and some of the most useful apps on your device, with the goal of Making you feel like 家.

    With an almost stable source, this ROM is also packed with some custom wallpapers (available on ShishuWalls), ringtones, fonts, and themes to bring to your device into a fresher look and give you always a good experience.

    Also, for the official versions, we have our Telegram Group to talk about the ROM, share some love, ideas or even have fun with us!


    Some of the features that are included on this ROM are:

    * QS Rows and Columns
    * Volume Keys: Wake up, skip tracks and switch according to rotation
    * Show song album cover, visualizer and battery info on Lockscreen
    * Power Menu Items
    * Battery LED light settings
    * Suspend Actions: Make your device disable GPS and switch to 2G when you're not using it
    * AppOps: Manage your apps permissions in an advanced way
    * Recent Styles: Dig the new Pie Quickstep recents, go back to the classic layout or use the Android Go layout
    * Network icons: Show or hide the cross, switch between 4G or LTE, use the classic icon layout before Pie or toggle roaming icon too!

    Also, you can check a full list of Features available here.


    Thanks to this people, this ROM could be possible:

    * Shishu (for being there)
    * phh (for all Treble stuff)
    * Ground Zero ROMs Team
    * AOSPExtended
    * ABC ROMs
    * NitrogenOS
    * AICP
    * DirtyUnicorns
    * Lukas Koller (Camera Roll dev)
    * fxckingdeathwish (for the amazing photos for wallpaper/headers)
    * OmniROM
    * CyanogenMod/LineageOS
    * PixelExperience
    * PureNexus
    * merothh
    * Resurrection Remix
    * AOSiP
    * CrDroid
    * CypherOS
    * PureKat
    * theimpulson
    * MatiHalperin
    * Project Xtended
    * Pixeldust Project
    * AquariOS
    * Alejandro Ponce (Quetzal/Calypso dev)
    * PixysOS
    * The Memedo Testers team
    * Every maintainer who decided to give our project a shot
    * You for your interest on our project

    Also if you got some ideas, bug fixes, stability improvements or want to help to support features for your device, you can do it by sending a Pull request on Bootleggers Github (check downloads and sources part) or tell us on our Telegram group (Check about us section), will be really appreciated. Got some questions about some terms we use? Check our FAQ or feel free to ask us. We appreciate your feedback and help.


    arm64 GSI A/B and A-Only (vanilla, i.e., no Gapps and no su included)



    ROM Sources
    Bootleggers Github
    phh's treble device
    phh's patches
    phh's treble
    apn sources
    A bit of story and future steps. Building unofficially means you're alone, not a part of a team. On April, Liquid made quite some changes for their official devices that made me move to Havoc. On May, Havoc followed the same way. Generally, it's more complicated to build for a-only than for ab (at least for me). Bootleggers is still working on ab, but a-only started to fail. The future is not promising this way: each build became a very time-consuming task especially if we're building 2 ROMs x 2 devices types.

    It's not time to stop. But it's time to think, test and discover an alternative way to build consistenly (yes, seems to have at least one). I'll make tests during next weeks because time-consuming tasks are not sustainable in long-term for a single person building unofficially for free. You can see how many ROMs come and go.

    Both ROMs (Havoc and Bootleggers) from late April are working very well (at least on the single device I have to test). Thanks for your patience and comprehension.
    Major effort to bring all the stable patches from phh Treble up to April 2019 (AOSP 9.0 v112).

    Listing only the successful applied ones:
    Applying: "remaining" of HAL onEnroll is actually a percent of progress
    Applying: Actually restore pre-P mutex behavior
    Applying: Add a property toggle to enable high brightness range on samsung device
    Applying: Add japanese S9
    Applying: Add props to control supported features and states (#1)
    Applying: Add Qualcomm starlte
    Applying: Add route to gateway on null netmask
    Applying: Allow deletion of symlink
    Applying: Also create vendor_ce (same reason as vendor_de)
    Applying: AOSP 8.0/8.1 didn't use presentOrValidate, so it's broken. Don't use it
    Applying: CameraService: Support calling addStates in enumerateProviders
    Applying: Change SignalStrentgh to change behaviour based on property
    Applying: Change SignalStrentgh to change behaviour based on property
    Applying: Choose a more generic prop.
    Applying: Create vendor_de. This is done by /init.rc on system-as-root device
    Applying: Different value for astarqlte. Probably more devices to add later
    Applying: Don't set esdfs or exfat genfscon. Assume OEM does
    Applying: Enable multipl_decls by default. This is needed because 8.0 init doesn't add -m
    Applying: FIH devices: Fix "Earpiece" audio output
    Applying: First drop_privs (which may fail) and only run thread that might be scheduled before us
    Applying: Fix backlight control on Galaxy S9(+)
    Applying: Fix OP6 brightness
    Applying: Fix typo on fnmatch return value check
    Applying: Fix WiFi-Display on Huawei devices (EMUI 8.0)
    Applying: Huawei Kirin 960:: accept broken rpfilter match
    Applying: Huawei:: HWC doesn't understand 0,0,0,0 == fullscreen damage. Set it to the whole visible surface
    Applying: idmap: Don't silently ignore RROs with same priority
    Applying: Ignore /proc/kmsg if reading from it faults
    Applying: Increase default log_level to get actual selinux error in kmsg
    Applying: Initial support of in-display fingerprint sensor
    Applying: Kirin:: Remove lock to prevent self-lock
    Applying: Kirin:: Workaround some conflicting Kirin tether SELinux context
    Applying: Make BTM_BYPASS_EXTRA_ACL_SETUP dynamic
    Applying: Make MAX_CONNECTIONS_GSM settable from property
    Applying: power: Disable keyboard/button lights while dozing/dreaming
    Applying: property-matching RROs: allow to prefix the value with + to do glob match instead of exact match
    Applying: Read SDK version override from property
    Applying: Relax /proc read from ueventd, huawei needs it
    Applying: Re-order services so that it works even without qtaguid
    Applying: Revert "logd: add "+passcred" for logdw socket"
    Applying: Revert "Set rlimit rtprio for cameraserver"
    Applying: Revert "SupplicantManager: Remove |ensure_config_file_exists|"
    Applying: S9 brightness override only for screen
    Applying: Set ro.build.fingerprint in system/etc/prop.default
    Applying: Show APN Settings for CDMA carriers
    Applying: Some kernel crashes when using too recent sdcardfs options. Force everyone to old options
    Applying: Start supplicant later
    Applying: Support hostap on O/O-MR1 vendors
    Applying: Support new samsung light hal
    Applying: Support Samsung's implementation of exfat, called sdfat
    Applying: Switch samsung light fingerprint match to regexp, to include Note9
    Applying: Telephony: Don not call onUssdRelease for Huawei RIL
    Applying: Try to make brightness more generic using property set by rw-system
    Applying: Use Samsung fingerprint percent thingy on all Samsung devices
    Applying: We might not have a mFlashlight at this state, but that's ok

    I’ll be out for the next three weeks. So, bear with me on updates until then.
    New May security patches + AOSP Patches v113 from phh.

    Coming soon!​