Database Info

[REF] Building AOKP -- Transient Issues -- 2012/09/18

At the present time, it appears that AOKP is again moving some of their git repositories around. As a result, the Team Acid build environment is "broken" until AOKP updates their repo manifest. It doesn't matter if you are doing this manually, or through Acidify.
Please read the entire thread as work-arounds have been changing from day to day.
One of the issues is that AOKP's frameworks/base and prebuilt git repos are returning
Access to this repository has been disabled by GitHub staff due to excessive use of resources. You'll need to contact support to restore access to this repository. Read here to learn more about decreasing the size of your repository.​
That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt. If you do, you can call repo -f sync which will skip a given git repository if there is a failure and continue with the rest.
Here are some work-arounds for the other issues
Patch your .repo/local_manifest.xml to replace the old git repos with their new location. Mine now looks like
Check yours after sync to the TeamAcid repo, either direct or thorugh Acidify, as FB has updated the TeamAcid version
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="AOKP/android_hardware_libhardware" />
<remove-project name="AOKP/android_hardware_msm7k" />
<remove-project name="AOKP/android_hardware_qcom_media" />
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
<project path="hardware/msm7k" name="AOKP/hardware_msm7k" remote="gh" revision="ics" />
<project path="hardware/qcom/media" name="AOKP/hardware_qcom_media" remote="gh" revision="ics" />
<!-- Projects we're removing -->
<remove-project name="AOKP/vendor_aokp_ics" />
<remove-project name="AOKP/vendor_samsung" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<!-- Projects we're replacing them with -->
<project path="vendor/aokp" name="fbis251/vendor_aokp" remote="gh" revision="ics" />
<project path="vendor/samsung" name="teamacid/proprietary_vendor_samsung" remote="gh" revision="ics" />
<project path="bootable/recovery" name="teamacid/Team-Win-Recovery-Project" remote="gh" revision="master" />
<!-- Projects we're adding -->
<project path="kernel/samsung/galaxys4gmtd" name="teamacid/android_kernel_galaxys4gmtd" remote="gh" revision="ics" />
<project path="device/samsung/galaxys4gmtd" name="fbis251/android_device_samsung_galaxys4gmtd" remote="gh" revision="ics" />
</manifest>
<!--
teamacid's AOKP local_manifest.xml
=================================
vi: ts=4:sw=4:et:noai
-->
Also, a line snuck into the device/samsung/galaxys4gmtd code that will cause a compile error. Adding a declaration for the parameter resolved the build problem.
Check your version (git log) as FB incorporated the patch on the 18th. "Patch to fix config_backKillTimeout build issue for AOKP" is the log entry you are looking for.
Code:
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 9bdf1b1..2cae795 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -199,6 +199,7 @@
<!-- Timeout in MS for how long you have to long-press the back key to
kill the foreground app. -->
+ <add-resource type="integer" name="config_backKillTimeout"/>
<integer name="config_backKillTimeout">1500</integer>
<!--Boolean to enable stk functionality on Samsung phones-->

I have a fix for the overlay but I will use your patch instead. I was finally working with aokp again last night and I got a build ready but still need to change a few things.
EDIT
Do you know if your overlay patch will fix the issue and build fine with CM9 instead of just AOKP? I'd like to push this to the main Team Acid repo when I can.

I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.

jeffsf said:
I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.
Click to expand...
Click to collapse
It's good that it builds. I'll try to remember to push it tonight

I saw they were re doing their repos for jellybean..a whole new start of it

Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?

fzhh said:
Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?
Click to expand...
Click to collapse
I've been able to repo sync using jeff's changes to local_manifest.xml.

Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
error: revision ics in AOKP/hardware_libhardware not found
Click to expand...
Click to collapse

Theraze said:
Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
Click to expand...
Click to collapse
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware

hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.

FBis251 said:
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware
Click to expand...
Click to collapse
Same error I've gotten since the first time jeff said to fix it in the github issues thread.
Most recently, I copied and pasted the local_manifest above fully to replace mine.
But as he said... apparently they removed the ics version and are currently only offering jb and master. Joy. Wonder if master is ics, or if they just screwed it up.

jeffsf said:
hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.
Click to expand...
Click to collapse
We can always try pushing the ics branch to our personal githubs and temporarily editing the local_manifest to reflect this.

As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of framework/base and prebuilt of the ics branch. I tried the Jeff's local_manifest.xml but the sync will fail at the end complaining to framework/base.

fzhh said:
As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of "framework/base and prebuilt".
Click to expand...
Click to collapse
I've uploaded my local repository of hardware/libhardware into my github profile:
https://github.com/fbis251/hardware_libhardware
You can use this by changing the line in jeff's local manifest from:
Code:
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
to
Code:
<project path="hardware/libhardware" name="fbis251/hardware_libhardware" remote="gh" revision="ics" />
Try a repo sync after that and I think it'll all work fine.

Little farther, but the new error is 211/314:
error: revision ics in AOKP/hardware_msm7k not found
Click to expand...
Click to collapse
Wild guess here, but qcom/media will probably have the same error, since those are the 3 repos that get replaced together...

I'll try to upload those repos with the ICS branch when I'm not on my school's wifi. They seem to not like letting us ssh over their wifi. :/

Okay I got the changes made:
https://github.com/teamacid/teamacid.github.com/commit/1afa77a372a9aeec9b1c90daa6bb3224f51e9325
Someone test it out by grabbing the local manifest file:
http://teamacid.github.com/manifests/sgh-t959v/AOKP/local_manifest.xml

I still got the following error:
Fetching projects: 100% (314/314), done.
Checking out files: 100% (19168/19168), done. files: 3% (635/19168)
Checking out files: 100% (4743/4743), done.
Checking out files: 100% (9386/9386), done.out files: 17% (1628/9386)
Checking out files: 100% (3156/3156), done. out files: 31% (991/3156)
Checking out files: 100% (24618/24618), done.
Syncing work tree: 61% (192/314) error: revision ics in AOKP/frameworks_base not found

Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...

Theraze said:
Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...
Click to expand...
Click to collapse
Actually an acidify sync should take care of him (NOT repo sync, since repo sync doesn't grab the updated local_manifest.xml)

[TUTORIAL]Compile rom from source[janice]

Compile rom from source for janice
0. Before you start make sure to have Ubuntu 12.04 installed, a decent internet connection and a fast pc (quad core, 4-8 GB ram)
Click to expand...
Click to collapse
1. Setting up the build environment
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
2. Installing required packages
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 \
gcc g++ cpp gcc-multilib g++-4.6-multilib
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Click to expand...
Click to collapse
3. Set up ccache
Code:
nano ~/.bashrc
Add these two lines
Code:
export USE_CCACHE=1
export CCACHE_DIR=[COLOR="Red"]#[/COLOR]
Replace # with your cache directory
Press ctrl+x and then Y
Click to expand...
Click to collapse
4. Setting up repo tool
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Click to expand...
Click to collapse
5. Create working directory and initialize the repo
Code:
mkdir [COLOR="red"]#[/COLOR]
cd [COLOR="red"]#[/COLOR]
repo init -u [COLOR="red"]@[/COLOR]
Replace # with the name of the working dir (choose one)
Replace @ with the platform_manifest (or android) repository (for AOKP @ = https://github.com/AOKP/platform_manifest.git -b jb-mr1)
Click to expand...
Click to collapse
6. Set up local manifest
Code:
mkdir .repo/local_manifests
touch .repo/local_manifests/local_manifest.xml
nano .repo/local_manifests/local_manifest.xml
Add these lines to let the repo sync download the vendor, device tree and the kernel
4.3.1
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/samsung/u8500" name="TeamCanjica/android_kernel_samsung_u8500" revision="cm-10.2" remote="github" />
<project path="device/samsung/janice" name="TeamCanjica/android_device_samsung_janice" revision="cm-10.2" remote="github" />
<project path="device/samsung/u8500-common" name="TeamCanjica/android_device_samsung_u8500-common" revision="cm-10.2" remote="github" />
<project path="vendor/samsung/u8500-common" name="TeamCanjica/android_vendor_samsung_u8500-common" revision="cm-10.2" remote="github" />
<project path="hardware/u8500" name="TeamCanjica/android_hardware_u8500" revision="cm-10.2" remote="github" />
<project path="patches" name="KINGbabasula/STE_patches" revision="cm-10.2" remote="github" >
<copyfile src="patch.sh" dest="patch.sh" />
</project>
</manifest>
4.4.2
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/samsung/u8500" name="TeamCanjica/Samsung_STE_Kernel" revision="3.0.31" />
<project path="device/samsung/janice" name="TeamCanjica/android_device_samsung_janice" revision="cm-11.0" remote="github" />
<project path="device/samsung/u8500-common" name="TeamCanjica/android_device_samsung_u8500-common" revision="cm-11.0" remote="github" />
<project path="hardware/u8500" name="TeamCanjica/android_hardware_u8500" revision="cm-11.0" remote="github" />
<project path="vendor/samsung/u8500-common" name="TeamCanjica/android_vendor_samsung_u8500-common" revision="cm-11.0" remote="github" />
<project path="patches" name="KINGbabasula/STE_patches" revision="cm-11.0" remote="github" >
<copyfile src="patch.sh" dest="patch.sh" />
</project>
<project path="packages/apps/DeviceSettings" name="TeamCanjica/android_packages_apps_DeviceSettings" revision="master" />
</manifest>
Here editing the local_manifest.xml you can change/add/remove repositories to download to make sync faster
To remove a repository write this in the local_manifest.xml[/CODE]
Code:
<remove-project name="" />
Replace # with the name of the repository (example )
Click to expand...
Click to collapse
7. Time to sync!
Ok this is a boring part...
Code:
repo sync -j[COLOR="Red"]#[/COLOR]
Replace the # with the number of cores
It can take from 10 minutes to 2 hours. It depends by your connection and your pc specs
Click to expand...
Click to collapse
8. Download arm-eabi-4.6 toolchains
Code:
cd prebuilt/linux-x86/toolchain
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Building
9. Applying the patches
Code:
. patch.sh
Click to expand...
Click to collapse
10. Finally... Time to build!!! :laugh:
This can be boring too if you have bad pc specs
Code:
. build/envsetup.sh
lunch full_janice-userdebug
make -j[COLOR="Red"]#[/COLOR] otapackage
Replace # with the number of cores of your pc
Click to expand...
Click to collapse
Click to expand...
Click to collapse

If you edited something after building... Rebuild!
cd to working dir and type this
Code:
. patch.sh
. build/envsetup.sh
lunch full_janice-userdebug
make clean
make -j[COLOR="Red"]#[/COLOR] bacon
Replace # with the number of cores
Click to expand...
Click to collapse

Understanding where are the bugs
The first thing to do to understand where the bugs are is taking logcat
1.Open a terminal
2.cd to the adb folder
3.Write this to check that the device is recognized
Code:
adb devices
If serial shows continue
4.Now write this
Code:
adb logcat > logcat.txt
5.Wait 30 seconds and close the terminal
6.logcat.txt is the file containing the logcat
Or download my little tool from attachments and run logcat.bat
Click to expand...
Click to collapse
Reading the logcat
Search for the
Code:
E/> = error
F/> = fatal
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Thanks a lot. This was very useful. I'm going to try to compile an AOKP ROM later. :thumbup::thumbup::thumbup:
Sent from my GT-I9070 using xda premium

Abhinandh Ajay said:
Thanks a lot. This was very useful. I'm going to try to compile an AOKP ROM later. :thumbup::thumbup::thumbup:
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
LOL.. Im done repo sync part of aokp.. Ok i let you to build aokp while I'm trying to repo sync again for liquid smooth.. do we need to fork and sync some repos from paul/diego ch github?
Sent from my GT-I9070 using xda premium

assassin0408 said:
LOL.. Im done repo sync part of aokp.. Ok i let you to build aokp while I'm trying to repo sync again for liquid smooth.. do we need to fork and sync some repos from paul/diego ch github?
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
I don't remember exactly

You need to sync device, vendor and kernel repos from TeamCanjica github
Sent from my GT-I9070 using xda app-developers app

frapeti said:
You need to sync device, vendor and kernel repos from TeamCanjica github
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Thank you!
This is what i didn't remeber

Edited and added 4th post. now should be all ok

KINGbabasula said:
Edited and added 4th post. now should be all ok
Click to expand...
Click to collapse
Now you should switch to TeamCanjica repos instead of diego-ch (local_manifests), it's forked and updated from diego repos
Sent from my GT-I9070 using xda app-developers app

frapeti said:
Now you should switch to TeamCanjica repos instead of diego-ch (local_manifests), it's forked and updated from diego repos
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Will do soon
Sent from my GT-I9070 using Tapatalk 4 Beta

I'm sorry i don't know why some parts became blank i will update tomorrow
Sent from my GT-I9070 using Tapatalk 4 Beta

frapeti said:
Now you should switch to TeamCanjica repos instead of diego-ch (local_manifests), it's forked and updated from diego repos
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
i get this error when trying to build
bash: ./build/envsetup.sh: No such file or directory
Click to expand...
Click to collapse

assassin0408 said:
i get this error when trying to build
Click to expand...
Click to collapse
Yes don't try. I wrote that some parts became blank. I'm rewriting them now. You have to sync again

assassin0408 said:
i get this error when trying to build
Click to expand...
Click to collapse
Updated, now should be fine

KINGbabasula said:
Updated, now should be fine
Click to expand...
Click to collapse
Ok wait..i didnt sync the kernel.device and etc etc related to our device but instead i donwnloaded manually all required sources and put in directory. Is it wrong method?
Sent from my GT-I9070 using xda premium

assassin0408 said:
Ok wait..i didnt sync the kernel.device and etc etc related to our device but instead i donwnloaded manually all required sources and put in directory. Is it wrong method?
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
I never tried doing this but I think that won't work

KINGbabasula said:
I never tried doing this but I think that won't work
Click to expand...
Click to collapse
So i need to resync?owhh man..LOL..if using local manifest.it will sync the sources in local manifest or sync also on manifest?its quite complicated thast local manifest thingy..
Sent from my GT-I9070 using xda premium

assassin0408 said:
i get this error when trying to build
Click to expand...
Click to collapse
Do '. build/...' Instead of './build...'
Sent from my GT-I9070 using xda app-developers app

[Q]who is trying to build CM11

tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info

yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell

ShadowsDie said:
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell
Click to expand...
Click to collapse
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os

yjosipy said:
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os
Click to expand...
Click to collapse
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you

ShadowsDie said:
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you
Click to expand...
Click to collapse
i had 4 gb and one card died anyway i will try it:cyclops:

yjosipy said:
i had 4 gb and one card died anyway i will try it:cyclops:
Click to expand...
Click to collapse
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice

ShadowsDie said:
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice
Click to expand...
Click to collapse
and how much of source code do i need to download i mean how many gigabytes

yjosipy said:
and how much of source code do i need to download i mean how many gigabytes
Click to expand...
Click to collapse
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
Click to expand...
Click to collapse
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia

ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia
Click to expand...
Click to collapse
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one

yjosipy said:
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one
Click to expand...
Click to collapse
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy

ShadowsDie said:
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy
Click to expand...
Click to collapse
tnx for that i think i can handle it
Edit:started to syncing

yjosipy said:
tnx for that i think i can handle it
Edit:started to syncing
Click to expand...
Click to collapse
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok

ShadowsDie said:
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok
Click to expand...
Click to collapse
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading

yjosipy said:
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading
Click to expand...
Click to collapse
Good job, let me know if something happens, i'll try to help as much as I can

ShadowsDie said:
Good job, let me know if something happens, i'll try to help as much as I can
Click to expand...
Click to collapse
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests

yjosipy said:
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests
Click to expand...
Click to collapse
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...

ShadowsDie said:
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...
Click to expand...
Click to collapse
yes why not my fb name is joosipp

i invited someone with that name thell me if its you

ShadowsDie said:
i invited someone with that name thell me if its you
Click to expand...
Click to collapse
nope try this www.facebook.com/joosipp

yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
I have successfullly ported cm11 to our device!!
But I can't upload It and share It with you due to bad internet connection (upload speed~12 Kb/s).... :crying: :crying: :crying: :crying:

[DEV] [sm-t320 == tab pro 8.4] CM-11.0 unofficial bringup for mondrianwifi USA

This thread is for developers only and I will not be posting ROMs here.
I am posting this here in the hope that someone else has time, skills and motivation to help work on this. If so, please PM me and/or send me pull requests.
I am basing this off of the HLTE kernel because it is being very well maintained and has many huge advances from CAF.
Links:
Kernel: https://github.com/crpalmer/android_kernel_samsung_mondrianwifi
Device: https://github.com/crpalmer/android_device_samsung_mondrianwifi
Vendor: https://github.com/crpalmer/android_vendor_samsung_mondrianwifi
I am also using these dependent repositories:
Code:
<project path="device/samsung/msm8960-common"
name="CyanogenMod/android_device_samsung_msm8960-common"
remote="github" revision="cm-11.0"
/>
<project path="device/samsung/qcom-common"
name="CyanogenMod/android_device_samsung_qcom-common"
remote="github" revision="cm-11.0"
/>
<project path="hardware/qcom/display-caf-new"
name="CyanogenMod/android_hardware_qcom_display-caf-new"
groups="caf"
/>
<project path="hardware/qcom/media-caf-new"
name="CyanogenMod/android_hardware_qcom_media-caf-new"
groups="caf"
/>
<remove-project name="CyanogenMod/android_hardware_invensense" />

This was the status but since I got further faster than I was expecting, there is now a build thread which has the status there.

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
* CM 11 boots and the base seems to be generally not horrendously broken
Hardware status:
* display: backlight doesn't work, therefore it also won't turn back on once it turns off
* usb: adb works, nothing else tested
* WiFi: doesn't work
* everything else: haven't even looked at it, and therefore probably doesn't work
Click to expand...
Click to collapse
The source has been published by Samsung.
opensource.samsung.com
Sent from my SM-T320 using XDA Premium HD app

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
Click to expand...
Click to collapse
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!

blulite said:
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!
Click to expand...
Click to collapse
The cwmr that I am using is the one that gets built by running a full CM build using the repos I pointed toward. If you can build CM then you should be able to build a recovery that works on at least my tablet. However, I am definitely not sharing a build because of the fact that it is based on the hlte kernel and could be causing serious problems.
I'm going to try to merge the official source into the hlte kernel and see if I can get that working. If so, it will be a fair bit less risky (although it is still risky because random people like me are playing with how the hardware gets used including voltages, current, etc.).
If you were trying to build a recovery yourself, yeah, you probably ran into problems because the bootloader requires a boot.img with a device tree and the DT needs to be version 2 format which is quite new.

Updated the kernel link. It is a merge of the KK_NA source released by samsung into the hlte kernel from cyanogenmod. It builds but the display is still borked (the left hand of the screen now turns back on, but the right does not...).
If anyone was working with these repos, please do not use the original hlte fork any longer.

[WIP] Unofficial SLIMROM MM

Hello Developers,
I'm working on SLIM MM, but stuck on boot screen (i.e. MI logo).
Tried to capture logcat but while booting it says "waiting for device..."
local_manifests :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!--Ferrari Device-->
<project name="Ferrari-Dev-Team/android_device_xiaomi_ferrari.git" path="device/xiaomi/ferrari" remote="github" revision="cm-13.0"/>
<project name="Ferrari-Dev-Team/android_kernel_xiaomi_ferrari" path="kernel/xiaomi/ferrari" remote="github" revision="cm-13.0-new"/>
<project name="Ferrari-Dev-Team/android_vendor_xiaomi_ferrari.git" path="vendor/xiaomi/ferrari" remote="github" revision="cm-13.0"/>
<!--snapdragon stuff-->
<project name="CyanogenMod/android_external_stlport" path="external/stlport" revision="cm-13.0" />
</manifest>
Any suggestion ??
Built, if someone can look in that.
A HUGE Thanks @faizauthar12 for helping me in this.

1.

2.

@fire855 @Shahan_mik3 @haikalizz @Rohan purohit
@ƒεηιx @faizauthar12
Any Inputs ?

Toruk.Makto said:
@fire855 @Shahan_mik3 @haikalizz @Rohan purohit
@ƒεηιx @faizauthar12
Any Inputs ?
Click to expand...
Click to collapse
sorry, i have no idea with it
if possible, i will download slim rom source :fingers-crossed:
and give it a try

faizauthar12 said:
sorry, i have no idea with it
if possible, i will download slim rom source :fingers-crossed:
and give it a try
Click to expand...
Click to collapse
Great.
Instead of SLIM, could you please give a try to Mokee MM ?? Just saying..... it's upto you.

Remove the old boringssl and clone the aospa boringssl.
Sent from my MI 4i using XDA-Developers mobile app

ƒεηιx said:
Remove the old boringssl and clone the aospa boringssl.
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Already tried that..... but still no luck

@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ

Toruk.Makto said:
Already tried that..... but still no luck
Click to expand...
Click to collapse
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app

ƒεηιx said:
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Code:
adb shell cat /proc/kmsg > ABC.txt
Will it work ?? I'll be fetching logs on Windows 7 ???

anbuchelva said:
@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ
Click to expand...
Click to collapse
I didn't get any such errors.

anbuchelva said:
@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ
Click to expand...
Click to collapse
You could try from CM repo

ƒεηιx said:
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Nopes, it didn't help as well. Tried below commands on Windows Machine.
C:\adb>adb shell cat /proc/kmsg > kernelmsg3.txt // It generated few o/p but I didn't reboot device after flashing ROM/Gapps, Mayb be it's capturing just flashing logs which are not useful for us.
C:\adb>adb shell cat /proc/kmsg
error: device '(null)' not found
C:\adb>

Toruk.Makto said:
Nopes, it didn't help as well. Tried below commands on Windows Machine.
C:\adb>adb shell cat /proc/kmsg > kernelmsg3.txt // It generated few o/p but I didn't reboot device after flashing ROM/Gapps, Mayb be it's capturing just flashing logs which are not useful for us.
C:\adb>adb shell cat /proc/kmsg
error: device '(null)' not found
C:\adb>
Click to expand...
Click to collapse
Build rom again with engineer mode so adb will work on this mode.
Sent from my MI 4i using XDA-Developers mobile app

i would appreciate if someone guide me what's wrong in this. thanks!!
http://pastebin.com/b9G3VyzT
pls ignore..

anbuchelva said:
i would appreciate if someone guide me what's wrong in this. thanks!!
http://pastebin.com/b9G3VyzT
pls ignore..
Click to expand...
Click to collapse
Can i see your manifest?
Seems you're using kernel 3.10.49...
Also,did you clone boringssl from ferrari dev team?

faizauthar12 said:
Can i see your manifest?
Seems you're using kernel 3.10.49...
Also,did you clone boringssl from ferrari dev team?
Click to expand...
Click to collapse
i got it fixed.. will be uploading the build soon. :good:
and the local manifest:
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- BoringSSL fix -->
<remove-project path="external/boringssl" name="platform/external/boringssl" groups="pdk" />
<project path="external/boringssl" name="Ferrari-Dev-Team/android_external_boringssl" remote="github" revision="cm-13.0"/>
<!-- Device repos -->
<project path="device/xiaomi/ferrari" name="Ferrari-Dev-Team/android_device_xiaomi_ferrari" remote="github" revision="cm-13.0"/>
<project path="kernel/xiaomi/ferrari" name="Ferrari-Dev-Team/android_kernel_xiaomi_ferrari" remote="github" revision="cm-13.0-new"/>
<project path="vendor/xiaomi/ferrari" name="Ferrari-Dev-Team/android_vendor_xiaomi_ferrari" remote="github" revision="cm-13.0"/>
<!-- Snapdragon Stuff -->
<!--project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" /-->
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<!-- remove darwin -->
<remove-project path="prebuilts/clang/darwin-x86/host/3.6" name="platform/prebuilts/clang/darwin-x86/host/3.6" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/arm/arm-eabi-4.8" name="platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.8" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.9" name="platform/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.9" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/host/headers" name="platform/prebuilts/gcc/darwin-x86/host/headers" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/host/i686-apple-darwin-4.2.1" name="platform/prebuilts/gcc/darwin-x86/host/i686-apple-darwin-4.2.1" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9" groups="pdk,darwin,mips" />
<remove-project path="prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9" groups="pdk,darwin,x86" />
<remove-project path="prebuilts/python/darwin-x86/2.7.5" name="platform/prebuilts/python/darwin-x86/2.7.5" groups="darwin,pdk,pdk-cw-fs" />
</manifest>

What happened to this ROM. Please continue