Develop Bugs

[Guide]How to Compile PAC Rom

Hey guys, so a lot of you have be eagerly anticipating the release of PAC-4.4. Others of you may be seeking pac for a device that is not supported at this moment. So I thought I would take this opportunity to write a guide on how to compile PAC.
In order to compile Android, I recommend that you use a Linux distro. For the purposes of this guide, I shall be using Ubuntu 13.10. It is pretty easy to set up, even as a dual boot with windows.
The first thing you need to do, once you have installed Ubuntu, is to set it up to be able to compile Android. There are a lot of guides that show you how to do this, and this guide has pretty clear instructions. Follow all of his directions until you reach the point where he tells you to initialize the repository (The command he has as an example there is repo init -u git://github.com/AOKP/platform_manifest.git -b jb-mr2. Do not run this command or you will have downloaded the AOKP sources instead of the PAC sources)
To download the pac sources, we need to initialize the repository first. For this guide, I will be downloading the pac source to ~/android/pac. Run:
Code:
mkdir -p ~/android/pac
cd ~/android/pac
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Now it is time to download the source itself. Keep in mind that the source is rather large (~10+ GB), so you might want to make yourself a cup of tea (or 10 cups if you have a crappy isp) while waiting. Run:
Code:
repo sync
Now, it is time to do the actually compiling. If your device is already supported by PAC, please skip directly to post 3. Else, go to post 2.

Adding Support for a device
To add support for your device, the first thing you need to do is to hunt down your device tree. If you are not sure where your device tree is located, google it or ask in your device's subforum. Now, it is time to add the files required to build.
From the root of directory where you have downloaded the pac source (~/android/pac), go to the vendor/pac directory. This is where we will be making the changes necessary to build for your device. Here are the files that need to be modified/added. Obviously, substitute your devices codename for CODENAME.
1. dependencies/CODENAME.dependencies
This file grabs your device and kernel tree. Look at the dependencies file of a device that is similar to yours to figure out what you need to place in here. A list of all the devices we support and their respective codenames can be found here. Again, if you are unsure about what to place here, you may want to ask for help in your devices subforum. Whenever possible, try to use the CM device tree. For the vendor files, keep the account name as "Pinky-Inky-and-Clyde" but change the repository to the appropriate OEM (check here for repos). Do not worry if the vendor files for your device are not in that repository. We will be adding them later.
Here is a sample CODENAME.dependencies file for a Samsung device (note that the account names are case sensitive):
Code:
[
{
"account": "Pinky-Inky-and-Clyde",
"repository": "proprietary_vendor_samsung",
"target_path": "vendor/samsung",
"revision": "cm-11.0"
},
{
"account": "CyanogenMod",
"repository": "android_device_samsung_CODENAME",
"target_path": "device/samsung/CODENAME",
"revision": "cm-11.0"
},
{
"account": "CyanogenMod",
"repository": "android_kernel_samsung_CODENAME",
"target_path": "kernel/samsung/CODENAME",
"revision": "master"
},
{
"account": "CyanogenMod",
"repository": "android_hardware_samsung",
"target_path": "hardware/samsung",
"revision": "cm-11.0"
}
]
Once you have done this, go to the root of your pac source (~/android/pac for this guide), and run
Code:
./vendor/pac/tools/getdependencies.py CODENAME
This will attempt to create the file .repo/local_manifests/roomservice.xml and then sync up the sources. If you have to make changes to your dependencies, please remove the roomservice.xml file and re-run the script again to ensure that no incorrect repositories are left lingering.
Go to the vendor files directory (~/android/pac/vendor/YOUR_OEM), and search for the vendor files of your device. If they are not there, you will have to search for them online and copy them into the folder.
Alternatively, if your device has an extract-files.sh script, in the device tree (located in device/OEM/CODENAME), you can hook up your device via usb and run that command to grab the vendor files directly from your device. In this case, connect your device and run:
Code:
cd device/OEM/CODENAME
./extract-files.sh
2. products/pac_CODENAME.mk
Again, look at the same file for a device that is similar to yours and make the appropriate changes for your device.
Here is a sample pac_CODENAME.mk file for a hdpi device:
Code:
# Check for target product
ifeq (pac_CODENAME,$(TARGET_PRODUCT))
# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_hdpi
# PAC device overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/pac/overlay/pac/hdpi_480x800
# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x800.rle:root/logo.rle
# Copy bootanimation
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/480x800/bootanimation.zip:system/media/bootanimation.zip
# include PAC common configuration
include vendor/pac/config/pac_common.mk
# Inherit CM device configuration
$(call inherit-product, device/samsung/CODENAME/cm.mk)
PRODUCT_NAME := pac_CODENAME
endif
Note: for the PAC device overlay, look inside vendor/pac/overlay/pac for the available overlays. Likewise, for the bootanimation and boot logo, look in their respective directories for the available sizes.
3. vendorsetup.sh
Add a line that looks something like this in the appropriate area of this file (under the appropriate OEM, and in alphabetical order, please).
Code:
add_lunch_combo pac_CODENAME-userbebug
--- The below files are not necessary for successful compilation, but are required if you submit your device for official PAC support. ---
4. Contributors
5. Nightly.xml
6. XDAThreads
7. devices-breakdown.xml
For these files, follow the format of the other devices.

Building PAC
Now that we got all of the housekeeping out of the way, it is time to build the rom!
Open up a terminal and change directory to the base of where you downloaded the PAC source to begin compiling. Run (substitute your device's codename for CODENAME):
Code:
./build-pac.sh CODENAME
There are some additional options available in the build script. To see them all, simply run:
Code:
./build-pac.sh
If everything goes well, your build should be starting. Go take a walk or something while it is building. This may take a while if you have a computer with weak specs.

Submitting your device for official support
Once you have successfully built PAC for your device and tested it, you can submit your changes to our gerrit for official support and automatic nightly builds.
In order to do this, you need to first sign up on our gerrit and get your ssh keys set up. So head on over to http://review.pac-rom.com/ to register for an account. Next, we need to generate an ssh key pair in order to push changes to gerrit. To check if you already have a key pair generated, run
Code:
ls ~/.ssh
If it shows a id_rsa.pub, you already have your keys generated and you can skip to the adding your ssh key to gerrit part.
On the other hand, if there is nothing in your .ssh folder, run
Code:
ssh-keygen -t rsa -C "[email protected]"
When you run this command, it will ask you where you want to save this file. Just hit enter. Next, it will ask you for a passphrase for your private key. Enter a passphrase here that you can remember.
Now, it is time to add your public key to our gerrit. To copy your public key over, run:
Code:
sudo apt-get install xclip
xclip -sel clip < ~/.ssh/id_rsa.pub
(Alternatively, you can cat the file and just copy it, but the above mentioned way avoids any missing characters while copying.)
Now, login to our gerrit and go to your account settings > ssh public keys. Click on add, and paste the key and save.
It is time to upload your changes. We have a script to make this process easier. To grab the script, run:
Code:
cd ~/bin
wget http://pac-rom.com/downloads/pac-review
chmod a+x pac-review
Now, run:
Code:
cd ~/android/pac
cd vendor/pac
git add -A
git commit
This should open up a text editor (probably nano) where you can put a commit message. For our purposes, just write something along the lines of "Add support for ___." To save the file, hit Ctrl + o. To exit, hit Ctrl + x. Then, run:
Code:
pac-review -p
Follow the prompts and your changes should be automatically pushed and a link will show to your change on gerrit.
If you realize that you made a mistake in your commit, DO NOT submit a new change. Instead, make your changes, then run:
Code:
git add -A
git commit --amend
Update your commit message if necessary and then push with the pac-review script. This will create a new patchset on our gerrit instead of creating a new commit.
And that is all! If you have any questions, dont hesitate to ask them here. Ill try to get back to you as soon as possible

Hey iurnait, I didn't find any instructions on pac's github on how to clone the entire trees. Please help.

Ateekujjawal said:
Hey iurnait, I didn't find any instructions on pac's github on how to clone the entire trees. Please help.
Click to expand...
Click to collapse
cd into the directory where you are working, and then run
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
then run
Code:
repo sync

iurnait said:
cd into the directory where you are working, and then run
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
then run
Code:
repo sync
Click to expand...
Click to collapse
By doing this, will I get all the packages_apps_settings,frameworks_av etc.

Ateekujjawal said:
By doing this, will I get all the packages_apps_settings,frameworks_av etc.
Click to expand...
Click to collapse
this will grab everything needed to compile

How can I use linaro toolchain to compile pacman and where to download it.

Simplest Method you found here:
http://forum.xda-developers.com/showthread.php?t=2644910
You need only one a Machine with a Ubuntu ready,

Is this method also usable for the LG P990 (Optimus 2x) ?
If so, any special things I should look out for with this old device?
Sent from my LG P990 running CM11 (thnx tonyp) via xda-developers app

DavidLouwers said:
Is this method also usable for the LG P990 (Optimus 2x) ?
If so, any special things I should look out for with this old device?
Sent from my LG P990 running CM11 (thnx tonyp) via xda-developers app
Click to expand...
Click to collapse
If you can find your device here: https://github.com/PAC-man/android_vendor_pac/blob/pac-4.4/devices-breakdown.xml
it will work

@DavidLouwers
talk with tonyp and penguin77 if the device repos work PAC 4.4
You can only one use the Kernel/Device/Vendor Tree... (if you planned to run as nightly in jenkins) If tonyp use for her [email protected] other modified repos was normally is in PAC or Cyanogenmod... it can build but you must modifing default.xml in .repo/manifests. But then you can not add to nighlys...
if you want help, ask me, i had this device before and maintained PAC for p990

MetaIIica said:
@DavidLouwers
talk with tonyp and penguin77 if the device repos work PAC 4.4
You can only one use the Kernel/Device/Vendor Tree... (if you planned to run as nightly in jenkins) If tonyp use for her [email protected] other modified repos was normally is in PAC or Cyanogenmod... it can build but you must modifing default.xml in .repo/manifests. But then you can not add to nighlys...
if you want help, ask me, i had this device before and maintained PAC for p990
Click to expand...
Click to collapse
Thanks, I will! I will do everything in my power to make PAC ROM available for my phone! I used to have your PAC 4.3 ROM, which I loved, and that's the reason I really want a KitKat PAC ROM, because KitKat is optimised for phones with low memory, so it'd be awesome to have PAC 4.4 for the old P990.
I shall try to gather the penguins and port PAC to P990!
Langes said:
If you can find your device here: github site, can't post it because I'm a new member :/
it will work
Click to expand...
Click to collapse
Sadly enough, P990 isn't on it, but with the help of Metallica and the penguins, maybe we'll be able to make PAC available for the P990 anyway!

Ateekujjawal said:
How can I use linaro toolchain to compile pacman and where to download it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2348366

For now, there is only cm11 available for the note 3.
Does this matter?
If not, I can try to make it
Gesendet von meinem SM-N9005 mit Tapatalk

Thumper_ said:
For now, there is only cm11 available for the note 3.
Does this matter?
If not, I can try to make it
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
If there is a working cm 11 tree available, have a look at the second post on how to add PAC support. It shouldnt be too difficult considering you already have cm11
Sent from my Nexus 7 using Tapatalk

Thumper_ said:
For now, there is only cm11 available for the note 3.
Does this matter?
If not, I can try to make it
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
Would be great if you built it and shared the build..not much available for the note 3 yet
Sent from my SM-N900P using Tapatalk

nelsonator1982 said:
Would be great if you built it and shared the build..not much available for the note 3 yet
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Just downloading the repo
Let's see what I can do.
Gesendet von meinem SM-N9005 mit Tapatalk

Can't get it
where should I place the pac_CODENAME.mk ?
Then the dependencies?
Suppose, I am building for c1905, then the dependencies must be in /device/sony/c1905/c1905.dependencies?
Then
Is this pac_c1905.mk okay?
Code:
# Check for target product
ifeq (pac_c1905,$(TARGET_PRODUCT))
# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_hdpi
# PAC device overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/pac/overlay/pac/hdpi_480x854
# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x854.rle:root/logo.rle
# Copy bootanimation
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/480x854/bootanimation.zip:system/media/bootanimation.zip
# include PAC common configuration
include vendor/pac/config/pac_common.mk
# Inherit CM device configuration
$(call inherit-product, device/sony/c1905/cm.mk)
PRODUCT_NAME := pac_c1905
endif
Help Me out. I am trying to build for Xperia M.

[Q] How to add Sony Xpeira S binaries to AOSP rom build?

Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/knowledge-base/open-source/android-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?

anybody? please help

thsecmaniac said:
anybody? please help
Click to expand...
Click to collapse
Do pm to a developer.like abhinav2,or deadwar,op of carban rom
Sent from my LT26i using xda premium

thsecmaniac said:
Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/kno...droid-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?
Click to expand...
Click to collapse
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk

What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
abcdjdj said:
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk
Click to expand...
Click to collapse

thsecmaniac said:
What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
Click to expand...
Click to collapse
These files are known as the vendor blobs. They are proprietary files whose source code is not available to the public. Some of these vendor files are used by various components of the phone like the camera etc. The ones on the Sony website are very old so if you use them, it is quite possible that the camera might not function properly. As Sony released official updates, if I remember, they even fixed laggy 1080p recording. So it would be much better to use the latest blobs.
Sent from my Xperia S using Tapatalk

[ROM][6.0.1][K920][kingdom_row]CandySix for Lenovo Vibe Z2 Pro ROW

Unofficial build of CandySix for international Lenovo Vibe Z2 Pro
It's not using CM theme engine but RRO Layers.
Install gapps right after ROM, this thing has no browser without them.
DOWNLOAD
Google+ community
known bugs:
- flip cover not supported yet
- FM radio not working
- install latest stock ROM then CandySix, maybe it will fix echo
...
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="candysix-c6" />
<project name="frantisheq/android_kernel_lenovo_msm8974" path="kernel/lenovo/msm8974" remote="github" revision="cm-13.0" />
<project name="frantisheq/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="cm-13.0" />
</manifest>
Click to expand...
Click to collapse

frantisheq said:
Unofficial build of CandySix for international Lenovo Vibe Z2 Pro
It's not using CM theme engine but RRO Layers.
Install gapps right after ROM, this thing has no browser without them.
DOWNLOAD
Google+ community
known bugs:
- flip cover not supported yet
- FM radio not working
...
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
Click to expand...
Click to collapse
Hi
Download link is not working. No mirrors found. Eager to test this ROM

Very cool. Excited to test as well. Looking forward to the download links!

fixed download https://www.androidfilehost.com/?fid=24438995911973720

frantisheq said:
fixed download https://www.androidfilehost.com/?fid=24438995911973720
Click to expand...
Click to collapse
Pretty much the same UI as the other CM based ROMs but the themes are different and layered.
Some extra setting which otherwise can be managed with xposed installer and Gravity box on other CM ROMs.
Unfortunately the same issues of low call volume, echo to the other person, low resolution camera etc.. are observed here also.
Had to move out after testing.

new build https://basketbuild.com/filedl/devs....1-kingdom_row-UNOFFICIAL-frantisheq-0324.zip

Hello f****:
what's different from cm-13.0-20160325-NIGHTLY-kingdom_row.zip？
Sent from my Lenovo K920 using XDA Free mobile app

1-)When we are talking on the phone, it's makes an echo so you hear your, voice again.I don't hear any echo own echnly you hear.
2-)This problem occurs in all softwares except euphoria.What is wrong with other softwares .What can I do for that problem.To solve this problem in my mobile phone,could you give me any different modem software?

new build https://basketbuild.com/filedl/devs....1-kingdom_row-UNOFFICIAL-frantisheq-0330.zip

[ROM][10][Unofficial] Havoc OS 3.8 for Oneplus 6/6T (enchilada/fajita) [2020/09/01]

PSA: as of date there are new Official Havoc OS builds maintained by @ClintT available in the telegram channel Havoc-OS OnePlus 6/6T or on [email protected]. these include both cams and twrp. builds with and without Gapps are available.
there are currently no builds of Official Havoc OS here come some works-for-me-why-not-for-you builds of Havoc-OS for Oneplus 6/6T.
The ROM is based on the Havoc-OS manifest, Illusion kernel and modified Lineage sources at the time of building.
It includes recent Urnyx's Gcam mod as well as OOSCam and Gallery.
for
Oneplus 6 - A6003 (enchilada)
Oneplus 6T - A6013 (fajita)
Disclaimer: have fun, no guarantees, your warranty is now void, there's always the sun (for at least some time from now)
Note: The Oneplus 6T (fajita) build is released completely untested, while the Oneplus 6 (enchilada) is tested and works as expected. For known issues/not working check the sections below. Feel free to drop a line below if/how it runs on Oneplus 6T (fajita) so i can update the status.
Requirements:
- you might need to update to latest stock beforehand, get the Android 10 based OxygenOS(OOS) zips over at Oneplus support
- Mauronofrio's TWRP 3.3.1+ for Oneplus 6 (enchilada), Oneplus 6T (fajita)
- backup everything before install to be on the safe side, to be extra safe backup the backups from device to a harddrive (in the case you lose access to the data partition)
- wipe data when upgrading from another ROM
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP6/OP6T!!!!! You will loose data decryption keys up to the need to reinstall via Fastboot or MsmDownloadTool.
Installation:
Clean flash
1. boot into TWRP (Mauronofrio's TWRP suggested)
2. flash latest OOS
3. flash TWRP installer zip
4. reboot to recovery (switches active boot partition)
5. flash OOS again to make sure its on both slots
6. flash TWRP installer zip
7. reboot to recovery (switches active boot partition again)
--
8. flash ROM (Havoc-OS-*.zip)
9. flash TWRP installer zip
10. wipe data and cache
11. reboot to recovery (switches to the boot slot the ROM was just installed to)
12. flash Opengapps (optional)
13. flash Magisk (optional)(flash after setting up device)
14. reboot system (fingers crossed)
Dirty flash (when coming from earlier Havoc-OS 3.x)
1. flash Havoc & TWRP installer zips
2. reboot to recovery (switches to the boot slot the ROM was just installed to)
3. flash Gapps (optional)
4. flash Magisk (optional)
5. reboot system
Suggested apps/kernel:
- Eng.stk's unified Blu_spark kernel for OP6/6T xda thread, download
- Urnyx05's Gcam mod https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/
Not working:
dunno
Known issues:
you tell me
Download:
Oneplus 6 (enchilada) builds
Oneplus 6T (fajita) builds
Sources:
ROM-Manifest
https://github.com/Havoc-OS/android_manifest
Device trees
https://github.com/bdhay/havoc_device_oneplus_enchilada
https://github.com/bdhay/android_device_oneplus_fajita
Kernel
https://github.com/AOSiP-Devices/kernel_oneplus_sdm845
Others
see roomservice.xml below
Thanks:
to all Havoc-OS, LineageOS developers and everyone who contributed to this ROM
@AnierinB for helping to get OOSCam going
Mini-howto:
1. setup build env on a linux box as outlined on https://github.com/Havoc-OS/android_manifest, mainly install repo command from distro or google and init repository in a folder that will hold the build
Code:
mkdir -p ~/havoc
cd ~/havoc
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
2. after 'repo init ...' save roomservice.xml with the following content
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/oneplus/enchilada" remote="github" name="bdhay/android_device_oneplus_enchilada" revision="havoc-ten" />
<project path="device/oneplus/fajita" remote="github" name="bdhay/android_device_oneplus_fajita" revision="havoc-ten" />
<project path="device/oneplus/sdm845-common" remote="github" name="bdhay/device_oneplus_sdm845-common" revision="havoc-ten" />
<project path="kernel/oneplus/sdm845" remote="github" name="AOSiP-Devices/kernel_oneplus_sdm845" revision="ten" clone-depth="1" />
<project path="vendor/oneplus" remote="github" name="bdhay/proprietary_vendor_oneplus" revision="ten" clone-depth="1" />
<project path="device/oneplus/common" remote="github" name="bdhay/device_oneplus_common" revision="ten" />
<!-- inaccessable just now, uncomment if you want the cameras below built in
<project path="vendor/addons/google/camera" remote="github" name="Evolution-X-Devices/vendor_addons_google_camera" revision="ten" />
<project path="vendor/addons/oneplus/camera" remote="github" name="Evolution-X-Devices/vendor_addons_oneplus_camera" revision="sdm845" />
-->
</manifest>
to
Code:
.repo/local_manifests/roomservice.xml
Note: the folder .repo/ should already exist, just 'mkdir .repo/local_manifests' before adding roomservice.xml
the file contains the repos making the devices known to the build tree.
3. sync the repos
Code:
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
4. init environment
Code:
source build/envsetup.sh
5. check if device is there
Code:
breakfast enchilada
# or
breakfast fajita
and finally
6. start build
Code:
brunch enchilada
# or
brunch fajita

Changelog
2020/09/01
- fix OOSCam support
- include Urnyx05's Gcam mod and OOSCam
- Alert-Slider working now
- switch to Illusion-Kernel
2020/08/24
- initial release

buddhay said:
reserved
Click to expand...
Click to collapse
Cool....

chandu dyavanapelli said:
Cool....
Click to expand...
Click to collapse
Did you tried? How's it?

sschacko said:
Did you tried? How's it?
Click to expand...
Click to collapse
I try it soon buddy

chandu dyavanapelli said:
I try it soon buddy
Click to expand...
Click to collapse
Ok

Thought I would try and build from what you posted... #### failed to build some targets (13:32:46 (hh:mm:ss)) ####
Gotta love a fail LOL.

TrOjAnUK said:
Thought I would try and build from what you posted... #### failed to build some targets (13:32:46 (hh:mm:ss)) ####
Gotta love a fail LOL.
Click to expand...
Click to collapse
still waiting for peeps to say how the ROM is working out and the first real comment is 'Bob The Builder' gotta love xda folks
how about posting a longer stack? the above says just that it didn't work.
just to make sure i repeated my mini-howto after posting it. works for me :good::angel:

buddhay said:
still waiting for peeps to say how the ROM is working out and the first real comment is 'Bob The Builder' gotta love xda folks
how about posting a longer stack? the above says just that it didn't work.
just to make sure i repeated my mini-howto after posting it. works for me :good::angel:
Click to expand...
Click to collapse
Ahh sorry... wasnt asking for help.. just thought it was worth a post to amuse people after a 13 hour build.. I`ll get it fixed, wanted to try and get the OOS camera working.
Apologies for being a Bob the Builder

TrOjAnUK said:
Ahh sorry... wasnt asking for help.. just thought it was worth a post to amuse people after a 13 hour build.. I`ll get it fixed, wanted to try and get the OOS camera working.
Click to expand...
Click to collapse
ahh, nice! please share the recipe if you succeed. i am wondering if including the OOS Camera is not violating the GPL but obviously several roms do so on xda.
btw. consider enabling CCACHE=1 with a folder preferably on SSD/RAMdisk. speeds up subsequent builds considerably. obviously not if nothing changed, but after repo updates or when compiling the "other" device.

After a Day, it works for me without issues! (Enchilada) Everything is top. No FCs or something.

Baron1971 said:
After a Day, it works for me without issues! (Enchilada) Everything is top. No FCs or something.
Click to expand...
Click to collapse
nice!
still waiting for fajita owners to say their piece.

Not sure if I had a bad download or what I didn't even look to see how big zip was after it finished downloading but twrp kept telling me to boot to other slot after I'd already flashed OOS 10.3.5 on both slots and then rebooted recovery and was attempting to install havoc. Twrp would appear to begin install then stop and say reboot recovery or something like that..Using a 6t here. I'm downloading it again and will check to see once it's done then try and install again. Thanks for building Havoc for 6/6t! :good:
Will report back in a few.
Has anyone booted fajita Havoc 3.8?

When i attempt to flash Havoc on fajita in twrp (I used
twrp-3.3.1-32-fajita-Q-mauronofrio.img and also the twrp I've been using for months which is black themed 3.4.0 v1) the result is my attached screenshot. ?
Sidenote: I made sure I had a complete download..
Edit added: update.. I checked md5sums. I still am not successful at installing. I've probably flashed about 1k times on this device alone and owned three AB partitioned devices previous to this one.. Never had anything just not install in twrp until now. I find it almost impossible that nobody else with a 6t has flashed...? Anybody? Nothing is wrong with my device. Anything else flashes fine. ??

flash713 said:
When i attempt to flash Havoc on fajita in twrp (I used
twrp-3.3.1-32-fajita-Q-mauronofrio.img and also the twrp I've been using for months which is black themed 3.4.0 v1) the result is my attached screenshot. ?
Sidenote: I made sure I had a complete download..
Click to expand...
Click to collapse
that's not saying much. my guess would be an incomplete/broken zip file.
can you show an 'ls -l' of the zip file?
also please do an md5sum of it and compare it with the one on the download location.
ok, just read your 'Sidenote'. please proof you have the complete/proper download via checksumming.

buddhay said:
that's not saying much. my guess would be an incomplete/broken zip file.
can you show an 'ls -l' of the zip file?
also please do an md5sum of it and compare it with the one on the download location.
ok, just read your 'Sidenote'. please proof you have the complete/proper download via checksumming.
Click to expand...
Click to collapse
I just flashed enchilada, seems to be beautiful. I'm not gone deep, but any how really appreciated

I'm facing a brightness bug where adjusting the slider doesn't do **** I'm worried about my phone staying on max brightness all the time please fix this issue

Aduser345 said:
I'm facing a brightness bug where adjusting the slider doesn't do **** I'm worried about my phone staying on max brightness all the time please fix this issue
Click to expand...
Click to collapse
which device? works for me on enchilada. if auto is enabled or not makes no difference too. cannot test on fajita.
maybe try a clean flash. see OP

Hi, i want to build Havoc myself. I followed your Instructions, but i get the following Error:
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
Code:
Traceback (most recent call last):
File "/home/ivt/havoc/.repo/repo/main.py", line 49, in <module>
import event_log
File "/home/ivt/havoc/.repo/repo/event_log.py", line 167, in <module>
_EVENT_ID = multiprocessing.Value('i', 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
return Value(typecode_or_type, *args, **kwds)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 108, in Value
lock = RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
return RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
What can i do?

Baron1971 said:
Hi, i want to build Havoc myself. I followed your Instructions, but i get the following Error:
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
Code:
Traceback (most recent call last):
File "/home/ivt/havoc/.repo/repo/main.py", line 49, in <module>
import event_log
File "/home/ivt/havoc/.repo/repo/event_log.py", line 167, in <module>
_EVENT_ID = multiprocessing.Value('i', 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
return Value(typecode_or_type, *args, **kwds)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 108, in Value
lock = RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
return RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
What can i do?
Click to expand...
Click to collapse
well https://www.google.com/search?q=_multiprocessing.SemLock+repo&oq=_multiprocessing.SemLock+repo first result https://forum.developer.parrot.com/t/repo-sync-permission-denied/9341 suggests it's a permission error. try that.
also i am not sure that repo is still supposed to run on python2. try python3.

LineageOS 16 Unofficial Build

Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!

I suspect that by reverting this commit :
https://github.com/LineageOS/lineage_wiki/commit/3c7f61f7c5e2353202427d6ff44587770b644ce3
and with a few more hacks even newer versions of android could be built for the Oppo Find7, any gurus out there that could help with this task?

Just tried to compile LineageOS 17.1 sources. I'm taking a look at the oneplus one device tree because they use the same SoC and it has already received even LineageOS 18.1. To compile successfully I need to repopick 279639 279641 279647 and 266411.
There is no MindTheGapps 10 so I tried OpenGApps pico but could not flash due to limited space.
Finally I tried to boot anyway but with no luck like @farmatito with LineageOS 16. So yes we need a guru, maybe @mikeioannina jump on the train again?

As mentioned by @farmatito BiTGApps can be installed. And i got it boot but i could not take a screenshot because of insufficient memory. screenrecording was possible though

Hi,
this is great news, I hoped this would be possible! Keep up with the good work.
With a little help this could be a fully usable phone as the OPO is still supported IIRC.
P.S.: in the next week when high season is over I hope to post a new build of LineageOS 16.

I think you must compile ones a migration build to switch from official to your builds without wiping data. I have done it in the past with this script from lineageos.org.

Hi,
I've read about the script but had not the time to implement it, also I suspect that it would not be a good idea
to migrate users to user-debug keys but that you need to generate a private key. If I would use my private key
for this I suspect that it would have security implications for the user. So best would be to generate a private key
for every user at installation time to protect his privacy and security but then where do we store this key? onto the
device itself seems not a good idea...
This crypto stuff scares me as I don't fully understand it.
Best would be every body compiles it on his computer and uses his own key.

I don't know why LineageOS never officially integrated LVM support, but for me having only 3GiB of internal storage was always a problem. 16GiB looks much better, I think. And since twrp officially supports lvm as well...

Yes. I know. OmniRom had LVM working and I still somewhere have the zip files to flash but the build system needs also to be patched (there was a patch for this from omnirom to lineage but I lost it). It scares me to touch that pile of code and I hate git. There would also be chinese partitioning, should have the the exe somewhere, but even for that the build system needs to be patched with the new partition offsets (and the kernel?).

At least encryption doesn't work on my LVM build at the moment and there is no auto-detection whether LVM or not. So the user can decide if he wants to use LVM or not.

I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output

gcs88 said:
I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output
Click to expand...
Click to collapse
fdisk -l /dev/block/mmcblk0 | grep system
14 294912 3006463 1324M 0700 system
Hi,
I will try to build with your repo as soon as I have some spare time, at the moment I am busy with another
project that has some kind of deadline.
Ciao,
farmatito

OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.

gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.
Click to expand...
Click to collapse
Thanks for your try. Installed 6th October build and basics are working well. Didn't test much but Wifi/Bluetooth/Phone are just fine. Update from last official Lineageos required flashing twice (first went straight back to recovery, second time booted to system).
Gapps (tried OpenGApps nano no chance: got code 64 in recovery). I will try Bitgapps next free time slot
Keep up with the good work.

gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Click to expand...
Click to collapse
Hello and many thanks for that rom.
I do have a question but don't know if it exactly belongs here. Maybe someone can tell from experience.
I did change to "Chinese unification storage method" using "X9007_Android5.0_16G_20150520" for a Find7a (X9006) as explained in this post.
My device storage now is 16 gigs, 4 already used after a clean install of Lineage OS 17.1.
Weird for me is the "mobile storage" which now shows
a corrupted sd-card which can not be formatted (seems to be like a left over from the previous partition, like its there but not) and
my external sd-card, which works fine
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.

los 17 flashed using bitgapps and it works pretty fine. no screenshot saving issue
install procedure
- do unified storage procedure (LVM to Chinese unified storage thread)
- flash setup lvm and remove lvm zips (might not be required)
- wipe system, data and cache
- flash los 17, bitgapps then cm 13 unified patch
- boot up.
if you get wallpaper glitch on the lockscreen just change wallpaper.
color os stock cam doesnt work anymore on android 10. use bacon camera from playstore
open gapps pico may not work. it flashes normally but you either get bootloop, stuck on setup (wifi wont connect) or google play services will be broken.

morTimar said:
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.
Click to expand...
Click to collapse
Yes, that's ok for Chinese partitions. I have this problem on all versions of lineage

Sounds like for ringtone, notification or alarm can not be selected.
"android.process.media keeps stopping"
But good trial. At least I was able to flash Android 10 on my old Find 7 just for fun

farmatito said:
Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!
Click to expand...
Click to collapse
地址怎么用