Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.
caspian154 said:
Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.
Click to expand...
Click to collapse
U just delete the <project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" /> in the local_manifest.xml
yeah, I've tried that - it comes, but I don't get the zip file. I tried a couple of options in the local_manifests from another thread and actually got a zip!
Sent from my Nexus 4 using xda app-developers app
caspian154 said:
yeah, I've tried that - it comes, but I don't get the zip file. I tried a couple of options in the local_manifests from another thread and actually got a zip!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
can you post the link about the other thread ?
thanks a lot !!
ilpolpi65 said:
can you post the link about the other thread ?
thanks a lot !!
Click to expand...
Click to collapse
Yep - sorry, I haven't been near a computer until now. I haven't tested out the rom yet, but it definitely generated a zip file ~ 155 mb, which doesn't seem wrong. Anyway, here's the post I stole from: http://forum.xda-developers.com/showpost.php?p=46661249&postcount=5
here's specifically what I have in my .repo/local_manifests/roomservice.xml
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_broadcom.git" path="vendor/broadcom" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nvidia.git" path="vendor/nvidia" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_elan.git" path="vendor/elan" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_invensense.git" path="vendor/invensense" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_widevine.git" path="vendor/widevine" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nxp.git" path="vendor/nxp" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_asus.git" path="vendor/asus" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_imgtec.git" path="vendor/imgtec" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="omnirom/android_device_asus_flo" path="device/asus/flo" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="android-msm-mako-3.4-jb-mr2" />
<project name="omnirom/android_device_lge_mako" path="device/lge/mako" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="android-4.3" />
</manifest>
caspian154 said:
Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.
Click to expand...
Click to collapse
My bad, I'm the one who edited part of the doc there, and i was fearing some confusion, definitely need a bit of rewrite, as i wrote that doc prior to roomservice.xml intergration.
Basically, if you are using an omni.dependencies file in the device folder, you don't need to include mako kernel dependencies in local_manifest.xml, but you will need to lunch breakfast and lunch prior to brunch to actually sync this branch.
If you are not using omni.dependencies, you should ignore the first part of the doc, and only use the second part, with title "deprecated".
You should actually delete roomservice.xml if you're not using it to sync, or else you would have the problem you currently have.
In other terms, keep only that part
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/" />
<project name="android_kernel_lge_mako" path="kernel/lge/mako" remote="omnirom" revision="android-4.3"/>
</manifest>
in a local_manifest.xml in your .repo/local_manifests directory, and delete the roomservice.xml file which is useless until you use an omni.dependencies file.
Also delete the changes you made out of local_manifest.xml, rule is only one declaration per branch
The so called blobs ( i didn't write that part) are actually not part of that repo, you could add themuppets repo for mako in your local_manifest.xml, for legal reasons, i couldn't include it in Omni's wiki.
Hope this will solve your problem, will try to edit the doc tomorrow to allow roomservice usage.
thanks a lot! I figured that all made more sense for those that were more experienced ROM developers. I would rather use the also stuff and not rely on cm blobs. I'm building for educational purposes - I'd like to make some tweaks here and there, so I want it as close to what the omni nightlies will be when they arrive.
Thanks for your explanation and documenting all that you do! I've been leaching off ROM developers for years and want to join in and help out.
Sent from my Nexus 4 using xda app-developers app
caspian154 said:
thanks a lot! I figured that all made more sense for those that were more experienced ROM developers. I would rather use the also stuff and not rely on cm blobs. I'm building for educational purposes - I'd like to make some tweaks here and there, so I want it as close to what the omni nightlies will be when they arrive.
Thanks for your explanation and documenting all that you do! I've been leaching off ROM developers for years and want to join in and help out.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You're welcome, and you can actually ignore part of my previous post, I just fully edited the doc, now everything is using roomservice.xml and omni.dependencies, so all mako's files get synced when you launch brunch mako, only themuppets repo can be added manually in local_manifest.xml in your .repo/local_manifests directory.
Sorry for the delay in a proper doc, got quite busy, and had little time do write something accurate.
I'm sorry - I am still not getting a zip file when I follow the steps on the wiki.
I sync the repo using the instructions,
Code:
repo sync -j1
It completes, I don't make any changes to the repo. I run the build
Code:
. build/envsetup.sh
brunch mako
It seems to complete without any errors. I do see complaints that I don't have an omni.dependencies file. Do I need to manually create that? I really want the purest rom - nothing special.
I think you have to create it, but I'm not perfectly sure..anyone else?
22anl said:
I think you have to create it, but I'm not perfectly sure..anyone else?
Click to expand...
Click to collapse
No. If you don't get a zip in your out folder, you've got a build error.
OK, that helps, I will comb through the output and see if I can find out what I'm missing. Thanks!
Sent from my Nexus 4 using xda app-developers app
You may need to cherry pick from gerrit to get it to build right
Also, here's what it will look like if your build is successful
Sweet thanks guys! I got it building, I somehow missed that I needed to do breakfast before I did a sync and build.
Related
NOT ENOUGH HELP, CAN'T PORT THIS WITH MY CURRENT SCHEDULE. THREAD CLOSED.
Ubuntu Touch Porting Efforts to the Nexus 7 2013 (Flo)
Status: WIP
Why is this going to be so hard and take so long?
The biggest issue is that Ubuntu Touch is still based on CM10.1 (Android 4.2) and not CM10.2 (Android 4.3).
Not to mention that Android 4.3 images and binaries for this device have only recently been released.
Ubuntu Touch isn't yet (as of September 21st, 2013) compatible with an Android 4.3 base.
Lend a Hand
Ubuntu Touch Porting Wiki (Needs a HUGE Update): https://wiki.ubuntu.com/Touch/Porting
Ubuntu Touch Porting Wiki 2.0 (WIP): https://wiki.ubuntu.com/Touch/PortingFlippedInProgress
CM Device Source: https://github.com/CyanogenMod/android_device_asus_flo
CM MSM Google Kernel Source: https://github.com/CyanogenMod/android_kernel_google_msm
AOSP Kernel: https://android.googlesource.com/device/asus/flo-kernel/
AOSP Kernel Source: https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-jb-mr2
AOSP Kernel Tree for Qualcomm Chipsets: https://android.googlesource.com/kernel/msm/
~/working_directory/.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_asus_flo" path="device/asus/flo" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="cm-10.2" />
</manifest>
How to Initialize the CM-10.2 Branch (credit to @stbgs in Post #4)
Code:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo
Reserved.
Where to go from here...
Code:
[HIDE][email protected]:~/utouch$ . build/envsetup.sh && brunch flo
including device/asus/flo/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/goldfish/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
pull-lp-source: Downloading libhybris version 0.1.0+git20130606+c5d897a-0ubuntu16
pull-lp-source: Downloading libhybris_0.1.0+git20130606+c5d897a.orig.tar.gz from archive.ubuntu.com (0.483 MiB)
pull-lp-source: Downloading libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.debian.tar.gz from archive.ubuntu.com (0.082 MiB)
gpgv: Signature made Fri 09 Aug 2013 10:56:57 AM EDT using RSA key ID B16223A3
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.dsc
dpkg-source: info: extracting libhybris in libhybris-0.1.0+git20130606+c5d897a
dpkg-source: info: unpacking libhybris_0.1.0+git20130606+c5d897a.orig.tar.gz
dpkg-source: info: unpacking libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.debian.tar.gz
dpkg-source: info: applying 0001-Media-adding-initial-compat-files-for-media.patch
dpkg-source: info: applying 0002-Media-Recorder-adding-initial-support-for-media-reco.patch
dpkg-source: info: applying 0003-hybris-common-jb-Making-libhybris-buildable-x86-64.patch
dpkg-source: info: applying 0004-platforms-Makefile.am-temporarily-disabling-fbdev-to.patch
dpkg-source: info: applying 0005-common-hooks.c-adding-NVIDIA-HACK-needed-by-Nexus-7.patch
dpkg-source: info: applying 0006-jb-linker.c-allow-debug-of-the-linker-and-hooked-sym.patch
dpkg-source: info: applying 0007-jb-linker.c-ubuntu-touch-uses-dev-alog-instead-of-de.patch
dpkg-source: info: applying 0008-hooks-shm-fixing-logic-with-cond-is-negative-error.patch
dpkg-source: info: applying 0009-jb-linker.c-reduce-debugging-output-for-prelinked-li.patch
dpkg-source: info: applying 0010-hardware-include-adding-audio-hal-related-headers-fr.patch
dpkg-source: info: applying 0011-hooks.c-no-need-to-map-strcasestr.patch
dpkg-source: info: applying 0012-hooks.c-handle-invalid-mutex-in-pthread_mutex_destro.patch
dpkg-source: info: applying 0013-implement-getset-property-via-property-service.patch
dpkg-source: info: applying 0014-input_compatibility_layer.cpp-avoid-blocking-on-exit.patch
dpkg-source: info: applying 0015-camera_compatibility_layer.cpp-don-t-explicitly-rele.patch
dpkg-source: info: applying 0016-media-adding-files-for-media-codec-support-with-stag.patch
dpkg-source: info: applying 0017-common-hooks.c-handle-null-attr-in-pthread_rwlock_in.patch
dpkg-source: info: applying 0018-properties.c-better-handling-for-name-and-value-size.patch
dpkg-source: info: applying 0019-Fix-last-argument-to-pthread_cond_timedwait.patch
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 82, in <module>
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 410, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 448, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'[/HIDE]
Hey there
I am also in the process of trying to build ubuntu touch for flo
I realized the branch name are missing from build/tools/roomservice.py, however you can add the branch by setting up the ROOMSERVICE_BRANHCES env variable like so:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo
I am still having issues with the build though..
stbgz said:
Hey there
I am also in the process of trying to build ubuntu touch for flo
I realized the branch name are missing from build/tools/roomservice.py, however you can add the branch by setting up the ROOMSERVICE_BRANHCES env variable like so:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo
I am still having issues with the build though..
Click to expand...
Click to collapse
Thanks mate! Post your terminal outputs here after failed builds so we can help each other out .
Sent from my Nexus 7 (2013).
Also, how did you add the extra configs for the kernel? android/kernel doesn't exist. Also, device/asus/flo/aosp_base.mk doesn't exist.
Sent from my Nexus 7 (2013).
MikeyCriggz said:
Thanks mate! Post your terminal outputs here after failed builds so we can help each other out .
Sent from my Nexus 7 (2013).
Click to expand...
Click to collapse
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_asus_flo
Default revision: phablet-10.1
Checking branch info
Searching for repository on phablet.ubuntu.com
Repository not found on phablet.ubuntu.com
This may likely be an unsupported build target
Using fallback branch: cm-10.2
CyanogenMod/android_device_asus_flo already exists
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Didn't add any modifications to the kernel. and yes the file aosp_base.mk is being included from device/asus/flo/aosp_flo.mk, but my source tree doesn't have such file not sure why
stbgz said:
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_asus_flo
Default revision: phablet-10.1
Checking branch info
Searching for repository on phablet.ubuntu.com
Repository not found on phablet.ubuntu.com
This may likely be an unsupported build target
Using fallback branch: cm-10.2
CyanogenMod/android_device_asus_flo already exists
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Didn't add any modifications to the kernel. and yes the file aosp_base.mk is being included from device/asus/flo/aosp_flo.mk, but my source tree doesn't have such file not sure why
Click to expand...
Click to collapse
Can you post your repository to Git-Hub? It'll make the team effort much easier .
Sent from my Nexus 7 (2013).
Will do, as soon as I have something to add, so far I have only realized that ubuntu repos don't have the cm10.2 branch? (hence the missing files), we have to find a way to have the ubuntu toold build with the cm10.2 branch(which includes aosp 4.3 changes I think)
stbgz said:
Will do, as soon as I have something to add, so far I have only realized that ubuntu repos don't have the cm10.2 branch? (hence the missing files), we have to find a way to have the ubuntu toold build with the cm10.2 branch(which includes aosp 4.3 changes I think)
Click to expand...
Click to collapse
Yeah, this is going to take some makeshift hacks.
Sent from my Nexus 7 (2013).
I'm going to try and mod an aosp_base.mk file from another device (perhaps Mako, since it has a very similar chipset). I'll let you know how it goes.
Sent from my Nexus 7 (2013).
Got it to start compiling stuck at this:
Code:
Export includes file: system/su/Android.mk -- /home/criggs/utouch/out/target/product/flo/obj/EXECUTABLES/su_intermediates/export_includes
Notice file: system/su/NOTICE -- /home/criggs/utouch/out/target/product/flo/obj/NOTICE_FILES/src//system/xbin/su.txt
make: *** No rule to make target `frameworks/native/data/etc/android.hardware.bluetooth_le.xml', needed by `/home/criggs/utouch/out/target/product/flo/system/etc/permissions/android.hardware.bluetooth_le.xml'. Stop.
make: *** Waiting for unfinished jobs....
This line needs to be removed from 'device/asus/flo/aosp_flo.mk' in order to bypass the first error:
Code:
# Inherit from the common Open Source product configuration
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
Edit: Don't worry, the original 'aosp_flo.mk' will be backed up automatically as 'aosp_flo.mk~'.
MikeyCriggz said:
This line needs to be removed from 'device/asus/flo/aosp_flo.mk' in order to bypass the first error:
Code:
# Inherit from the common Open Source product configuration
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
Edit: Don't worry, the original 'aosp_flo.mk' will be backed up automatically as 'aosp_flo.mk~'.
Click to expand...
Click to collapse
Hey there I got it somwhat compiling, most of the changes are in the file:
.repo/manifest/defualt.xml
(the - lines are lines that go the removed the + are the opposite)
basically
added a few repos straight from cyanogen and the kernel straight from google.
I'm building we'll see if it finishes and then if it works
build like so
TARGET_PREBUILT_KERNEL=kernel/flo-kernel/kernel brunch flo
here are the changes I did
diff --git a/default.xml b/default.xml
index 48b4917..d6714b7 100644
--- a/default.xml
+++ b/default.xml
@@ -7,6 +7,9 @@
<remote name="github"
fetch="git://github.com" />
+ <remote name="google"
+ fetch="https://android.googlesource.com" />
+
<default revision="refs/heads/phablet-10.1"
remote="phablet"
sync-c="true"
@@ -53,6 +56,7 @@
<project path="external/icu4c" name="CyanogenMod/android_external_icu4c" />
<project path="external/jhead" name="CyanogenMod/android_external_jhead" />
<project path="external/jpeg" name="CyanogenMod/android_external_jpeg" />
+ <project path="kernel/flo-kernel" name="device/asus/flo-kernel" remote="google" revision="master" />
<project path="external/kernel-headers" name="CyanogenMod/android_external_kernel-headers" />
<project path="external/liblzf" name="CyanogenMod/android_external_liblzf" />
<project path="external/libncurses" name="CyanogenMod/android_external_libncurses" />
@@ -82,8 +86,8 @@
<project path="external/zlib" name="CyanogenMod/android_external_zlib" />
<project path="frameworks/av" name="CyanogenMod/android_frameworks_av" />
- <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" />
- <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" />
+ <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" remote="github" revision="cm-10.2"/>
+ <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" remote="github" revision="cm-10.2" />
<project path="frameworks/opt/emoji" name="CyanogenMod/android_frameworks_opt_emoji" />
<project path="hardware/broadcom/wlan" name="CyanogenMod/android_hardware_broadcom_wlan" />
@@ -101,7 +105,7 @@
<project path="hardware/qcom/gps" name="CyanogenMod/android_hardware_qcom_gps" />
<project path="hardware/qcom/keymaster" name="CyanogenMod/android_hardware_qcom_keymaster" />
<project path="hardware/qcom/media" name="CyanogenMod/android_hardware_qcom_media" />
- <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" />
+ <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" remote="github" revision="cm-10.2"/>
<project path="hardware/qcom/power" name="CyanogenMod/android_hardware_qcom_power" />
<project path="hardware/qcom/sensors" name="CyanogenMod/android_hardware_qcom_sensors" />
<project path="hardware/qcom/wlan" name="CyanogenMod/android_hardware_qcom_wlan" />
stbgz said:
Hey there I got it somwhat compiling, most of the changes are in the file:
.repo/manifest/defualt.xml
(the - lines are lines that go the removed the + are the opposite)
basically
added a few repos straight from cyanogen and the kernel straight from google.
I'm building we'll see if it finishes and then if it works
build like so
TARGET_PREBUILT_KERNEL=kernel/flo-kernel/kernel brunch flo
here are the changes I did
diff --git a/default.xml b/default.xml
index 48b4917..d6714b7 100644
--- a/default.xml
+++ b/default.xml
@@ -7,6 +7,9 @@
<remote name="github"
fetch="git://github.com" />
+ <remote name="google"
+ fetch="https://android.googlesource.com" />
+
<default revision="refs/heads/phablet-10.1"
remote="phablet"
sync-c="true"
@@ -53,6 +56,7 @@
<project path="external/icu4c" name="CyanogenMod/android_external_icu4c" />
<project path="external/jhead" name="CyanogenMod/android_external_jhead" />
<project path="external/jpeg" name="CyanogenMod/android_external_jpeg" />
+ <project path="kernel/flo-kernel" name="device/asus/flo-kernel" remote="google" revision="master" />
<project path="external/kernel-headers" name="CyanogenMod/android_external_kernel-headers" />
<project path="external/liblzf" name="CyanogenMod/android_external_liblzf" />
<project path="external/libncurses" name="CyanogenMod/android_external_libncurses" />
@@ -82,8 +86,8 @@
<project path="external/zlib" name="CyanogenMod/android_external_zlib" />
<project path="frameworks/av" name="CyanogenMod/android_frameworks_av" />
- <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" />
- <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" />
+ <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" remote="github" revision="cm-10.2"/>
+ <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" remote="github" revision="cm-10.2" />
<project path="frameworks/opt/emoji" name="CyanogenMod/android_frameworks_opt_emoji" />
<project path="hardware/broadcom/wlan" name="CyanogenMod/android_hardware_broadcom_wlan" />
@@ -101,7 +105,7 @@
<project path="hardware/qcom/gps" name="CyanogenMod/android_hardware_qcom_gps" />
<project path="hardware/qcom/keymaster" name="CyanogenMod/android_hardware_qcom_keymaster" />
<project path="hardware/qcom/media" name="CyanogenMod/android_hardware_qcom_media" />
- <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" />
+ <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" remote="github" revision="cm-10.2"/>
<project path="hardware/qcom/power" name="CyanogenMod/android_hardware_qcom_power" />
<project path="hardware/qcom/sensors" name="CyanogenMod/android_hardware_qcom_sensors" />
<project path="hardware/qcom/wlan" name="CyanogenMod/android_hardware_qcom_wlan" />
Click to expand...
Click to collapse
You're the man! I'll see if I can get any further later tonight. I have to compile PA for a few devices and do some things first.
Things are going pretty well for this port so far. Will push all of my work thus far to a GitHub repository as soon as I can.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Not having Ubuntu Touch available on the N7(2013) model has kept me from saving to buy one.
I've used Ubuntu Touch for at least 2 months now as a daily driver on my Original N7 and really love it. especially being able to hack unity8
Sent from my LG-LS970 using xda app-developers app
blmvxer said:
Not having Ubuntu Touch available on the N7(2013) model has kept me from saving to buy one.
I've used Ubuntu Touch for at least 2 months now as a daily driver on my Original N7 and really love it. especially being able to hack unity8
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, long time no see .
Hey man, I've been around if you haven't already seen them, I have some apps in the apps/games folder.
You know modifying unity8 and such.
Oh I have a question for you, How much do you know about the infographic circle on the greeter screen?
I want to modify it to capture the weather and maybe updates from friends.
Sent from my LG-LS970 using xda app-developers app
blmvxer said:
Hey man, I've been around if you haven't already seen them, I have some apps in the apps/games folder.
You know modifying unity8 and such.
Oh I have a question for you, How much do you know about the infographic circle on the greeter screen?
I want to modify it to capture the weather and maybe updates from friends.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I don't know much about the new welcome screen. I haven't been around the Ubuntu Touch scene for a bit. Let's not digress here, though. Send me a PM or ping me on Google Hangouts ([email protected]) .
Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
theschneidi said:
Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
Click to expand...
Click to collapse
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.
vigoos said:
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.
Click to expand...
Click to collapse
Thanks,
Still downloading all packages
Hope it will work
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" />
<project name="projects/marvel/kernel_htc_msm7227-3.0.git" path="kernel/htc/msm7227" revision="master" remote="cryptomilk" />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="Ganster41/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="ProjectLlama/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/>
</manifest>
vigoos said:
...
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
...
Click to expand...
Click to collapse
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk
vigoos said:
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
theschneidi said:
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
Click to expand...
Click to collapse
There's some problem in that XML it means, I'll study the XML from ma few other devices so I can get an idea where the problem is
Sent from my GT-P3100 using Tapatalk
theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk
vigoos said:
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
In some threads I read that they deleted those lines in the XML. I will try that method first. Hope I'll get a build this evening. I got some other errors, which I post here in a few days.
vigoos said:
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Click to expand...
Click to collapse
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Ok, I will try it. Some things I had to change in kernel. When all things from 3.0 don't work I switch to the good old 2.6.x kernel.
OWL-Predator works with Salsa, the last CM10 for icong is built with it.
Vielen Dank DjOlivier
djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Danke DjOlivier. It wasn't interrupting but it was rather a big boost.... So we will switch back to owl now. We are able to compile with owl properly, it is not a really big deal. And vielen dank for the XML. I'll fix it today.
Sent from my GT-P3100 using Tapatalk
No problem... Here's CM10.1 git for marvel. I'm utterly convinced CM10.1 will work on icong. 3.x kernel has also been discontinued because the developer lacks time. There are many other devs who have tried to continue, but none of them has succeeded yet. If you need help with CM10.1, I'm here. Also @Kevinjoa, @thehacka1 or @izi501 are experts from wfs fora...
Gesendet von meinem LT26i mit Tapatalk
I got a Question if you dont mind me asking, how stable or bugfree is CM10.1 for WFS? Also since 4.4 got out why not just go directly for that as it seems to be running on a lot of the older devices.
CM10.1 is 90-95% bugfree, there are some small bugs here and there but it depends on the user if he notices them or not.
As for CM11 (4.4), we are currently fighting with CM10.2 for WFS. I don't think it's possible to port it. Nah, wait: It's certainly possible, but that will cost you a huge amount of time and it will probably never run well. Support for ARMv6 was dropped long time ago and there are so many features that won't work on armv6. So let's better port CM10.1 and make it as stable as possible.
Gesendet von meinem LT26i mit Tapatalk
djolivier said:
...
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="cm-10.1"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="cm-10.1"/>
Click to expand...
Click to collapse
I would suggest the branch cm-10.1 instead of jellybean because it doesn't compile without error.
djolivier said:
<project name="airk000/hardware_qcom_display" path="hardware/qcom/display" revision="jellybean2" />
Click to expand...
Click to collapse
I try now airk000 instead of WinSuk.
The guys from AndroidARMv6 have a CM-10.2 and 11 branch too, so we can hope that maybe a device like Wildfire S or Salsa could run the newer Android versions. But that doesn't make sense, if only three or more people try to get these Android versions working. It is not very difficult but it takes a long time. I do that only in my free time as an engineer student.
EDIT:
@vigoos
device/htc/icong/libcamera/mt9v113.c:25:23: fatal error: linux/io.h: No such file or directory
I think media/mt9v113.h and mt9v113_regs.h could be the next error messages. I have to check this first, but mt9v113 is not in kernel 3.0.x. Switching back to an older kernel would be a better idea or I try to find the right files to integrate them into kernel.
I totally agree with you, but why not using WinSuk's qcom display?
As I said above, 4.4 is possible. But I also lack time since I'm a student (who goes to school) and a build environment. Back to Kitkat, it may work, but if not, we have to accept that armv6 development slows down and it's only a matter of time until even devs abandon their projects and move along to other devices (if they haven't already).
Gesendet von meinem ODYS-Chrono mit Tapatalk 2
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
Kevinjoa said:
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
Click to expand...
Click to collapse
In arch/arm/configs/cyanogen_msm7227_defconfig from OWL-Predator-KERNEL you find a config that works. Maybe CPU frequencies have to be changed.
Make me a icong.config and I will build rom again and you will tell me if it works
Thought of letting others know the steps how I build the ROMs for my Vibrant.
Here they are
1. Make sure you have the machine setup as per the instructions you find when you search for "Build CM 10.1 ROM" in google.( Ex. http://forum.xda-developers.com/showthread.php?t=1971645)
2. Download the source using git init and repo sync commands in the instructions above.
3. Go to .repo folder and create a folder with name "local_manifests". In this create a file called "roomservice.xml" and add the following lines to it.
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_vibrantmtd" path="device/samsung/vibrantmtd" remote="github" revision="cm-10.2"/>
<project name="CyanogenMod/android_device_samsung_aries-common" path="device/samsung/aries-common" remote="github" revision="cm-11.0"/>
<project name="CyanogenMod/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" revision="cm-11.0"/>
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-11.0"/>
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0"/>
</manifest>
4. run repo sync again. This would get the projects necessary to build the kernel for Vibrant and also some drivers.
5. run
Code:
. build/envsetup.sh
. Remember, there is space between "." and "build".
6. run
Code:
brunch vibrantmtd
this will take a long time as long as 6 hours based on the power of your machine.
These are the basic steps. You can then build any other ROM by cherry picking the features.
that's it.
Good luck.
Guides by other Developers
Stinga11 http://forum.xda-developers.com/sam...de-how-to-compile-install-unofficial-t2819616
sada23 said:
Thought of letting others know the steps how I build the ROMs for my Vibrant.
Click to expand...
Click to collapse
Hey bro, also I have a guide on how to build a CM11 rom for the Vibrant, you might want to share the link in your post, for help of the other users because my guide is more for beginners.
http://forum.xda-developers.com/samsung-vibrant/general/guide-how-to-compile-install-unofficial-t2819616
Thanks, good contribution.
Please, write faq to build original AOSP for Vibrant.
THANK YOU!:good:
Hi folks,
i want to share with my selfcompiled CM 12.1 nighlies after cm switch peregrine to CM13.
Some people like me dont update so quick but also want the last android security patches for CM 12.1
This is my first selfcompiled rom, it is works for me, i can give no support, i am no programmer, i am only put some sripts on my computer
So, if you brake your phone or something else it is your fault.
It is compiled with help docker container from michael_ch, release 0.30
http://forum.xda-developers.com/showpost.php?p=59811186&postcount=1734
git clone https://github.com/stucki/docker-cyanogenmod.git
cd docker-cyanogenmod
./run.sh
# Inside the container, run these commands:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
touch .repo/local_manifests/motorola-msm8226.xml
# Edit the file and paste contents from below
# Repeat the following commands whenever you want to make a new build:
repo sync -j 16
source build/envsetup.sh
make clean
brunch peregrine
Click to expand...
Click to collapse
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" />
</manifest>
Click to expand...
Click to collapse
No changes, original CM12.1 repos, nothing optimized
Download:
http://www.mediafire.com/download/mbfakd5nl96t88b/cm-12.1-20151209-UNOFFICIAL-peregrine.zip
MD5: 735db013275a356c08639f3f105eddb0 cm-12.1-20151209-UNOFFICIAL-peregrine.zip
Reposync 20151209, all december security patches
I will post updates if something important change in CM12.1 or new security patches will released and i am still on CM12.1
Special thanks to all the the people here on xda to make this possible for me!
Indeed it was excellent of you bro, there are some of us that are not supported by the cm13 and this is a wonderful option.
Nice. Pls can you post results from Stagefright Detector (https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector) and VTS for Android (http://www.appbrain.com/app/vts-for-android/com.nowsecure.android.vts)?
jccz said:
Nice. Pls can you post results from Stagefright Detector (https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector) and VTS for Android (http://www.appbrain.com/app/vts-for-android/com.nowsecure.android.vts)?
Click to expand...
Click to collapse
Sorry i do not install dubios testing software on my working telephone
Bastlwastl2010 said:
Sorry i do not install dubios testing software on my working telephone
Click to expand...
Click to collapse
OK. Maybe some other will be able to test it.
Hi there!
I'm receiving some pm about users that want to learn how to build LineageOS for the Galaxy Note 4 (snapdragon), so here is a quick guide:
Only supported device for now are trltexx/trltedt (N910F/N910G) and trltetmo/trltecan (N910T/N910W8)
I suggest to use a LTS version of ubuntu, in this guide I'll be using Ubuntu 16.04
Let's start with a bit of cleaning:
Code:
sudo apt-get remove openjdk-* icedtea-* icedtea6-*
Install java8:
Code:
sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update && sudo apt-get install openjdk-8-jdk
Install build tools:
Code:
sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven
Install repo:
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Edit ~/.bashrc (in this exaple I'm using gedit to do it):
Code:
gedit ~/.bashrc
Add those 2 lines at the bottom of the file (we are going to add also ccache to speed up our build time):
Code:
export PATH=~/bin:$PATH
export USE_CCACHE=1
Save it, close gedit and run:
Code:
source ~/.bashrc
Let's create some folders where we'll be doing the magic:
Code:
mkdir ~/android && cd ~/android
mkdir lineageos && cd lineageos
Initialize the local repo and download the source:
Code:
repo init -u git://github.com/LineageOS/android.git -b cm-14.1
repo sync --force-sync
It'll take quite some time, depends on your internet connection.
Once it's done downloading and checking out the files:
Code:
cd .repo
mkdir local_manifests && cd local_manifests
Now create a new file in this folder, name it "roomservice.xml" and add this into it:
For trltexx/trltedt:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="underscoremone/android_kernel_samsung_trlte" path="kernel/samsung/trlte" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trltexx" path="device/samsung/trltexx" remote="github" revision="cm-14.1" />
<project name="underscoremone/proprietary_vendor_samsung_trlte" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
For trltetmo/trltecan:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="underscoremone/android_kernel_samsung_trlte" path="kernel/samsung/trlte" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="cm-14.1" />
<project name="fat-tire/android_device_samsung_trltetmo" path="device/samsung/trltetmo" remote="github" revision="cm-14.1" />
<project name="underscoremone/proprietary_vendor_samsung_trlte" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
Now go back to the root of the source ("lineageos" folder) and repo sync again
Code:
cd ../..
repo sync
It'll now download the specific repositories for your device.
Then run
for trltexx/trltedt
Code:
. build/envsetup.sh && brunch trltexx
or for trltetmo/trltecan
Code:
. build/envsetup.sh && brunch trltetmo
And your build will start.
Once done you'll find your flashable rom.zip file in out/target/product/trlte**/
Congratulations you've successfully compiled LineageOS 14.1 for your device.
Remember to "make clean" every now and then.
------
Sometimes you'll get some errors, try to google the error and if you can not find a solution ask for help here at xda.
------
Hopefully I didn't forget anything.. if you have any trouble following this guide reply to this thread; myself or someone else will try to help you as soon as possible.
If you like to have the keyboard with the extra numbers row add this (before "</manifest>") to your roomservice.xml:
Code:
<remove-project name="LineageOS/android_packages_inputmethods_LatinIME" />
<project name="underscoremone/android_packages_inputmethods_LatinIME" path="packages/inputmethods/LatinIME" remote="github" revision="_cm-14.1" />
-----------------------------------------------------------------------------------------
If you want to include su to your builds you have to run
Code:
export WITH_SU=true
before starting the build.
If you want to always include it you can add the same line to your .bashrc (remember to run "source ~/.bashrc" after you modify .bashrc)
Hello,
First of all thank you for sharing this guide.
I haven't yet compiled with success but so far one of the errors I've encountered is that i need to include the following in my local manifest:
Code:
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
or else I'm getting an error about missing macloader.h
Running a compile now so i will return once that finished
Diload said:
Hello,
First of all thank you for sharing this guide.
I haven't yet compiled with success but so far one of the errors I've encountered is that i need to include the following in my local manifest:
Code:
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
or else I'm getting an error about missing macloader.h
Running a compile now so i will return once that finished
Click to expand...
Click to collapse
Yep, you're right; I've missed it. I've updated the op.
Edit:
Actually I thought it was going to be downloaded automatically because it is included in the dependencies of "android_device_samsung_qcom-common".. maybe I'm wrong. Anyway I've added it to the guide's trltexx.xml, you may want to be aware that we still need "android_packages_resources_devicesettings" "android_packages_apps_FlipFlap" and "android_hardware_sony_timekeep", they should be automatically added to your roomservice.xml (because they are included in our lineage.dependencies) but if it doesn't happen you probably want to add it to your trltexx.xml.
How are things different if I want to build for TMO? How much disk space you need?
Sent from my SM-N910T using Tapatalk
rob_z11 said:
How are things different if I want to build for TMO? How much disk space you need?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I've updated the op with the changes needed for trltetmo/trltecan.
You need approximately 60gb, but I would go with more if you can.
hi can you show me how to build for the n910w8 ?
outstanding
Sent from my SM-N9300 using Tapatalk
Okay so i finally got a working build compiled, got a lot of issues with java compiler and javadoc using too much memory,
if anyone is interested it is fixed by setting
Code:
$ export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
Just edit the 4G in the end to the amount of ram you would allow the java compiler to run, be aware that you would still need about an additional of 4,5 gigs of ram available other than what you specify here, at least that was the case for me, since the java compiler doesn't clear out when other stuff is processed during the compile (like c, c++ and javadoc compilation)
_mone said:
Yep, you're right; I've missed it. I've updated the op.
Edit:
Actually I thought it was going to be downloaded automatically because it is included in the dependencies of "android_device_samsung_qcom-common".. maybe I'm wrong. Anyway I've added it to the guide's trltexx.xml, you may want to be aware that we still need "android_packages_resources_devicesettings" "android_packages_apps_FlipFlap" and "android_hardware_sony_timekeep", they should be automatically added to your roomservice.xml (because they are included in our lineage.dependencies) but if it doesn't happen you probably want to add it to your trltexx.xml.
Click to expand...
Click to collapse
I don't know, when I run brunch it doesn't create the roomservice.xml file, i think that it gets done with the breakfast command, but that would create instances in my roomservice.xml that conflicted with the trltexx repos pulled from another source from the other local manifest.
So i ended up with this local manifest (i.e. trltexx.xml)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/trlte-common" name="Diload/android_device_samsung_trlte-common" remote="github" revision="cm-14.1" />
<project path="kernel/samsung/trlte" name="Diload/android_kernel_samsung_trlte" remote="github" revision="cm-14.1" />
<project path="device/samsung/trltexx" name="Diload/android_device_samsung_trltexx" remote="github" revision="cm-14.1" />
<project path="vendor/samsung" name="Diload/proprietary_vendor_samsung_trlte" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="cm-14.1" />
</manifest>
And it is now running on my phone
Well done @Diload :good:
elitedz said:
hi can you show me how to build for the n910w8 ?
Click to expand...
Click to collapse
If you want build for trltecan (N910W8) follow this guide and make the changes described for trltetmo. trltetmo and trltecan, like trltexx and trltedt can share the same ROM.
_mone said:
If you want build for trltecan (N910W8) follow this guide and make the changes described for trltetmo. trltetmo and trltecan, like trltexx and trltedt can share the same ROM.
Click to expand...
Click to collapse
thank you
how about some love for the N910V ???
hi! I how about NOTE 4 DUOS N9100 which has two sim? Now only one sim works，wifi and another sim donot work. how solve it？Thanks!
Nice clear info!
Thanks!
Especially the part about local manifest, other guides I've read in past never touch on that part. Thank you.
N910V never gets any love
ok so what would I have to do to make one strictly for the N910V ? id just change it to trltevzw ?
happy2472 said:
N910V never gets any love
ok so what would I have to do to make one strictly for the N910V ? id just change it to trltevzw ?
Click to expand...
Click to collapse
For trltevzw you may want to have a look at the verzion forum and ask the recognized developers that are building LineageOS to share their source. Good luck with that!
_mone said:
For trltevzw you may want to have a look at the verzion forum and ask the recognized developers that are building LineageOS to share their source. Good luck with that!
Click to expand...
Click to collapse
Im guessing thats like gold??
What's the point installing lineageos on note4?
Not trolling... Just curious.
I bet we will lose everything this phone is great about (s pen menu etc.).
Thanks!
bat0nas said:
What's the point installing lineageos on note4?.
Click to expand...
Click to collapse
This is probably not the right place for such a discussion as this is about building LineageOS yourself, based on the the guide that _mone has very kindly provided. I suggest opening a new thread yourself inviting discussion/advice, or maybe look around the various LineageOS dev threads to see what people are saying. The known issues / missing functionality is pretty well documented, but I'm sure people will be happy let you know in a thread where it is appropriate