Develop Bugs

[ROM][SGT7-UT][20130515] Ubuntu Touch [DEV][RETIRED]

Code:
*** Disclaimer by cdesai
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
I'm starting this thread to see if DEVs and collaborators get motivated and help. I'm not really a DEV but...
Ubuntu Touch is still a WiP itself, and this is a Work-in-Progress of getting it to our SGT7 Tabs - P1000, P1000N/L/R/T/CDMA/etc
Click to expand...
Click to collapse
Features
Works: touch, wireless, camera...
Doesn't: audio, brightness, sensors, 3G/Mobile...
Click to expand...
Click to collapse
Installation instructions
Regular flash through CwM Recovery:
Wipe/Factory Reset
Flash cm-10.1-YYYYMMDD-UNOFFICIAL-p1.zip or cm-10.1-YYYYMMDD-UNOFFICIAL-p1c.zip
Flash quantal*.zip
Flash hdpi_overlay.zip
Click to expand...
Click to collapse
Changelog
UT ROM based on CM10.1 with humberos' kernel, p1 and p1-common. OS image directly from Ubuntu downloads.
Click to expand...
Click to collapse
Code:
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation, manual brightness.
2013-05-10
[note] My first UT boot.
[new] Thread created.
[changed] built and booted
[fixed] Now it boots!
Downloads
Base ROM
cm-10.1-20130515-UNOFFICIAL-p1.zip - fourth update!
cm-10.1-20130515-UNOFFICIAL-p1c.zip - fourth update! - NOT working - bad kernel without recovery. Reported by @sxfx
Ubuntu Touch Quantal from the MWC Demo:
quantal-preinstalled-phablet-armhf.zip
Ubuntu Touch Saucy:
saucy-preinstalled-touch-armhf.zip
Screen configs - changes screen resolution and proportions
hdpi_overlay.zip 20130515
Sources
https://github.com/sgt7-ut - maybe someday. :cyclops:
Mods/Addons/Themes/User Art
Ubuntu Touch Auto-debloater & Ubuntu Logo Welcome Screen
Click to expand...
Click to collapse
FAQ
The FAQ section in a thread is bound to grow over time... check for updates.
Q: How do I flash?
A: Learn that before coming here.
Q: How do I restore my {fill in here} ROM?
A: Learn that before coming here.
Q: How do I use ODIN?
A: Learn that before coming here.
Q: How do I use Heimdall?
A: Learn that before coming here.​
Click to expand...
Click to collapse
​
Links and References
Ubuntu for Tablets
Touch install
UT Porting Guide
UT Building
Quantal MWC Demo CD Images
XDA Ubuntu Touch General Porting Discussion Thread
XDA Ubuntu Touch Forum - For non-device specific stuff
How to use apt-get through ADB + Apache Proxy without Networking
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* humberos, the latin kernel king.
* cdesai
...

Building Ubuntu Touch
First of all have your CM10.1 build up to date.. if you can't build CM10.1 then you shouldn't even try this.
[UPDATE 20130515]
Successful build for p1 and p1c!
Basically follow the Porting guide. Initialize the repo as instructed, using phablet-dev-bootstrap.
My draft for building... soon we will have the sgt7-ut repo that will do most of it for us.
Not necessarily in order.. you might have to start compiling untill you get the error and come back and check the steps again.
Code:
## our manifest
copy the roomservice.xml to .repo/local_manifests/
## clean
rm -rf out kernel
make installclean
make clean
* edit as porting guide:
kernel/samsung/aries/fs/proc/array.c
* add extra lines from the porting guide to the end of:
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1ln_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1c_defconfig
* also change the following config in each of the 3 kernel configs:
CONFIG_TOUCHSCREEN_QT602240_ROT90=n
## prepare stuff
source build/envsetup.sh
breakfast p1
breakfast p1c
./get prebuilts in vendor/cm/
comment P1Parts, tvouthack and Torch from device/samsung/p1-common/device_base.mk
copy from your cm10.1 build - out/target/product/p1/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
copy from your cm10.1 build - out/target/product/p1c/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
?? cp out/target/product/p1/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1/obj/EXECUTABLES/make_ext4fs_intermediates/
?? cp out/target/product/p1c/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1c/obj/EXECUTABLES/make_ext4fs_intermediates/
Add chmod line in device/samsung/p1-common/init.p1-common.rc, like this:
# System server can control backlight brightness
chown system system /sys/class/backlight/s5p_bl/brightness
chmod 0666 /sys/class/backlight/panel/brightness
## Now build!
source build/envsetup.sh
breakfast p1
time make -j3 bacon # use -j1 to check for errors in their right order
breakfast p1c
time make -j3 bacon
.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="humberos/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="humberos/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" revision="cm-10.1-dev" />
<project name="humberos/android_device_samsung_p1" path="device/samsung/p1" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1c" path="device/samsung/p1c" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1-common" path="device/samsung/p1-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>
Change ro.sf.hwrotation to 0 in build.prop!

reserved 3
reserved 3

Wow, thnx! I'm downloading!:beer:
send from my Nexus

:beer::thumbup:
Sent from my GT-P1000 using xda app-developers app

That is one of the ubuntu, unless my eyes are cheated by some spell

Nice Ubuntu Logo in CWM
Hi,
first test. Don't get nervous, while unpacking ubuntu file lasts (4.5 minutes)
Also be patient during boot, first time i thought the Tab went off.
ubuntu boots, i can activate the start menu, but no further actions.
Thank you for your great work, alroger and humberos!
cinq

So, I sort of flashed this and nothing happened. It's just a fresh CM installation. Am I supposed to build something on device?
Edit: had a brain fart, got it generally working.
Sent from my SCH-I510 using xda premium

alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)

cdesai said:
alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)
Click to expand...
Click to collapse
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?

alroger said:
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?
Click to expand...
Click to collapse
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.

cdesai said:
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.
Click to expand...
Click to collapse
Cool, it works!
Hey, isn't there a ROT180 to use to invert the landscape? Or can you point me to the right file to edit this ROT90 config?
EDIT: Found it.. gonna try hacking a new ROT180 config.
EDIT2: Yay, I did it! My first customized kernel config: CONFIG_TOUCHSCREEN_QT602240_ROT180

Have you fixed the touchscreen bug? Can you please reupload the recompiled cm?
Thanks!

UPDATE 20130515 it works!
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build! let us know if it boots!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation
Building tips in Post #2.

Ubuntu Saucy
It works with the latest Ubuntu Sacy Salamander, but no wifi. Download link added.
Must edit /usr/bin/ubuntu-session manually in the ZIP and change:
Code:
# defaults
GRID_UNIT_PX=8
QTWEBKIT_DPR=1.0
FORM_FACTOR="tablet"
Don't use hdpi*zip on this one.

Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.

UPDATE 20130515 rotation fixed! brightenss fixed!
dexterash said:
Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.
Click to expand...
Click to collapse
Rotation fixed! New uploads!
Camera is aligned with then screen now.
Brightness fixed - uncheck Automatic brightness and you can choose your brightness.
Enough for today...

Is WiFi and mobile data working?
Sent from my GT-P1000 using xda app-developers app

Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app

areshinakya said:
Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
No, the base ROM is the base for any UT. But as I said it's working only with that build. Saucy worked also but without wireless.. there are new daily updates for raring and saucy every day... gotta keep on trying.

[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

[Guide] Build Your Own [UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

In the spirit of open-source, if there's one ROM that deserves to be "home-brewed" in addition to AOSP and Lineage, it's LineageOS4Microg. This guide will explain how to do so using Docker. LineageOS and Microg are explained below followed by the guide.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Known issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Building Requirements
1. A fast PC or VPS account such as Google Compute Engine. Minimum PC recommended requirements are Intel i5 or equivalent, 4 cores 8 threads minimum (more cores and better CPU recommended), 16GB ram, SSD and 300GB free drive space minimum, fast internet connection (you will download over 30GB of sources).
2. Ubuntu 18.04 is supported here. If you use Windows or another version of Linux, let others know of your tweaks and workarounds.
3. Patience and time. Downloading sources, setting up and building a rom will take hours if not days (depending on your PC hardware and internet speed).
Environment Setup & Build​1. Install Docker on Ubuntu (run each command once in terminal)
Code:
sudo apt-get update
sudo apt install docker.io
sudo systemctl start docker
sudo systemctl enable docker
2. Test that docker is running (run command in terminal)
Code:
docker run hello-world
You should see something like this, "docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world ca4f61b1923c: Pull complete Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. ..."
3. Pull lineageos4microg docker onto your pc (run command in terminal)
Code:
docker pull lineageos4microg/docker-lineage-cicd
4. After pull is complete, create the following directories in your home/YOURUSERNAME directory
lineageos4microg
lineageos4microg/src
lineageos4microg/ccache
lineageos4microg/local_manifests
lineageos4microg/keys
lineageos4microg/logs
lineageos4microg/zips
So it might look something like this: home/JoeAndroid/lineageos4microg
5. Copy the 4 attached xml files (bottom of this post) to your local_manifests folder
These are: ocean.xml, include_proprietary.xml, proprietary.xml, and custom_packages.xml
6. In terminal, cd into the lineage4microg folder, and copy and paste the following commands all at once after changing YOURUSERNAME to your username in ubuntu. For an explanation of options, see the link at bottom of post. This code will download sources, sync your repos with newest updates and start your build. This step could take hours. It is downloading sources, syncing repos and building your rom!
Code:
sudo docker run \
-e "BRANCH_NAME=lineage-16.0" \
-e "DEVICE_LIST=ocean" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension " \
-e "INCLUDE_PROPRIETARY=false" \
-v "/home/YOURUSERNAME/lineageos4microg/lineage:/srv/src" \
-v "/home/YOURUSERNAME/lineageos4microg/zips:/srv/zips" \
-v "/home/YOURUSERNAME/lineageos4microg/logs:/srv/logs" \
-v "/home/YOURUSERNAME/lineageos4microg/cache:/srv/ccache" \
-v "/home/YOURUSERNAME/lineageos4microg/keys:/srv/keys" \
-v "/home/YOURUSERNAME/lineageos4microg/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
7. Your build should be in the zips folder when complete! Flash in twrp/ofox.
8. If your build fails, check the log in lineageos4microg/logs/ocean folder. If you receive the following error, "Can not locate config makefile for product "lineage_ocean"" you will need to copy the 4 xmls from lineageos4microg/local_manifests to lineageos4microg/manifests.​
References and links:
https://phoenixnap.com/kb/how-to-install-docker-on-ubuntu-18-04
https://github.com/lineageos4microg/docker-lineage-cicd
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Thanks to Dark98, Electimon, Barry and many others for initial help and repos when building this rom.

Reserved #1

Reserved #2

Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?

skalnas said:
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
Click to expand...
Click to collapse
Can you take a picture of the screenshot including how you typed in the commands? Need a bit more info

I just pasted the code changing username screenshot attached

skalnas said:
I just pasted the code changing username screenshot attached
Click to expand...
Click to collapse
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?

Bernie_nix said:
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Click to expand...
Click to collapse
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.

skalnas said:
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
Click to expand...
Click to collapse
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script

Bernie_nix said:
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Click to expand...
Click to collapse
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again

skalnas said:
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
Click to expand...
Click to collapse
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.

Bernie_nix said:
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Click to expand...
Click to collapse
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks

skalnas said:
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
Click to expand...
Click to collapse
Awww... Well I had that happen before. Even if you have an old platter hdd (not ssd) as long as it's got the GBs of space it will take a little longer to build but for these purposes will do just fine. I use both SSD and hdds to build.

Got my dual boot set up. First tried Ubuntu but it kept locking up, went with Linux mint. Got a 250 GB partition, going to give it another go tommorow.

View attachment 4980819well, after switching from VM to dual boot, I gave it another go, and i got a msg in linux mint that i ran out of space about 3 1/2 hrs into build. I had set up 250gb partition as you suggested. I did 30gb root, 220 GB home,4 GB swap.
Can you take a look at the logs, i'm not clear looking at logs how much of build completed.
There was the zip file about 604 mb in the zips folder, which I could open(along with an sha and md5 files, which i dont know anything about.) I'm thinking possibly the build completed despite the warning in linux about running of free space.
I shrank the /root partition in gparted to 20gb and tried to extend the extra 10gb to home, but i couldn't.
Is it possible to specify 25gb ccache in the docker script somehow so that instead of the 50 it seems to allocate, maybe that will solve the space issue?
Thanks again, looks like progress.

Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?

skalnas said:
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
Click to expand...
Click to collapse
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
boot.img already exists, no need to overwrite...
dtbo.img already exists, no need to overwrite...
system.img already exists, no need to overwrite...
vendor.img already exists, no need to overwrite...
Total of 704512 4096-byte output blocks in 23 input chunks.
Total of 147456 4096-byte output blocks in 13 input chunks.
done.
Click to expand...
Click to collapse
Where is "Missing "vendor/lineage", aborting." appearing?

Bernie_nix said:
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
Where is "Missing "vendor/lineage", aborting." appearing?
Click to expand...
Click to collapse
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.

skalnas said:
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
Click to expand...
Click to collapse
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?

Bernie_nix said:
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Click to expand...
Click to collapse
The zip was 604mb, i did successfully flash it, thanks again for your help and guide building my first rom!
so the xml file should be edited to:
<project name="bernie-nix/android_device_motorola_sdm632-common-1" path="device/motorola/sdm632-common" remote="github"/>
?
btw, i don't see your repos on github anymore.

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