https://github.com/phhusson/treble_experimentations

Notes about tinkering with Android Project Treble
https://github.com/phhusson/treble_experimentations

Last synced: 28 days ago
JSON representation

Notes about tinkering with Android Project Treble

• Host: GitHub
• URL: https://github.com/phhusson/treble_experimentations
• Owner: phhusson
• Created: 2017-11-23T16:26:28.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2023-11-06T22:22:45.000Z (about 1 year ago)
• Last Synced: 2024-10-01T20:40:45.187Z (about 1 month ago)
• Language: Smali
• Size: 6.33 MB
• Stars: 3,377
• Watchers: 132
• Forks: 658
• Open Issues: 1,390
• Metadata Files:
  • Readme: README.md
  • Changelog: ChangeLog.md

Awesome Lists containing this project

README

        
# Community

* IRC: irc://irc.freenode.net/#phh-treble

* WebIRC: http://webchat.freenode.net/?channels=%23phh-treble&uio=d4

* Matrix: [#phh-treble:matrix.org](https://matrix.to/#/#phh-treble:matrix.org)

* Telegram https://t.me/phhtreble

* xda-developers threads: https://forum.xda-developers.com/search.php?do=finduser&u=1915408&starteronly=1

# How to build

* clone this repository

* call the build scripts from a separate directory

For example:

    git clone https://github.com/phhusson/treble_experimentations

    mkdir Lineage; cd Lineage

    bash ../treble_experimentations/build-rom.sh android-8.1 lineage

## More flexible build script

(this has been tested much less)

  bash ../treble_experimentations/build-dakkar.sh rr \

    arm-aonly-gapps-su \

    arm64-ab-go-nosu

The script should provide a help message if you pass something it

doesn't understand

# Using Docker

clone this repository, then:

    docker build -t treble docker/

    

    docker container create --name treble treble

    

    docker run -ti \

        -v $(pwd):/treble \

        -v $(pwd)/../treble_output:/treble_output \

        -w /treble_output \

        treble \

        /bin/bash /treble/build-dakkar.sh rr \

        arm-aonly-gapps-su \

        arm64-ab-go-nosu

# Conventions for commit messages:

* `[UGLY]` Please make this patch disappear as soon as possible

* `[master]` tag means that the commit should be dropped in a future

  rebase

* `[device]` tag means this change is device-specific workaround

* `::device name::` will try to describe which devices are concerned

  by this change

* `[userfriendly]` This commit is NOT used for hardware support, but

  to make the rom more user friendly