Database Info

Building paranoidandroid from source

Here's a guide on how to build paranoidandroid from source for skyrocket.
Note this assumes you already have a build environment setup.
First is ics:
First make a working directory:
For example: mkdir ~/paranoid; cd ~/paranoid
Initialize the repo:
repo init -u git://github.com/ParanoidAndroid/android.git -b ics
Create a local_manifest.xml with these contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/hercules" name="CyanogenMod/android_device_samsung_hercules" remote="github" revision="ics" />
<project path="device/samsung/skyrocket" name="CyanogenMod/android_device_samsung_skyrocket" remote="github" revision="ics" />
<project path="device/samsung/msm8660-common" name="CyanogenMod/android_device_samsung_msm8660-common" remote="github" revision="ics" />
<project path="kernel/samsung/msm8660-common" name="CyanogenMod/android_kernel_samsung_msm8660-common" remote="github" revision="ics" />
<project path="vendor/samsung" name="TeamChopsticks/proprietary_vendor_samsung" remote="github" revision="ics" />
</manifest>
Then checkout the source:
repo sync
Before building:
go to device/samsung/skyrocket and open vendorsetup.sh:
change cm_skyrocket to pa_skyrocket save and exit
Now open cm.mk
and add:
Code:
# Inherit PA stuff
$(call inherit-product, vendor/pa/config/pa_common.mk)
under:
Code:
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/gsm.mk)
so that it looks like:
Code:
$(call inherit-product, device/samsung/skyrocket/full_skyrocket.mk)
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/gsm.mk)
# Inherit PA stuff
$(call inherit-product, vendor/pa/config/pa_common.mk)
# Enhanced NFC
$(call inherit-product, vendor/cm/config/nfc_enhanced.mk)
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SGH-I727 TARGET_DEVICE=SGH-I727 BUILD_FINGERPRINT="samsung/SGH-I727/SGH-I727:4.0.4/IMM76D/UCLF6:user/release-keys" PRIVATE_BUILD_DESC="SGH-I727-user 4.0.4 IMM76D UCLF6 release-keys"
TARGET_BOOTANIMATION_NAME := vertical-480x800
PRODUCT_NAME := pa_skyrocket
PRODUCT_DEVICE := skyrocket
now run lunch and select pa_skyrocket-eng
then make -j4 bacon
I'm pretty sure that's it. If I missed anything lt me know.
Here's my build, untested of course:pa_skyrocket-1.6a-16AUG2012-130315.zip

For paranoid jellybean: still building will post a guide once I have a build, so I know that it works.

Maybe an aokp guide if people want it.

any news on jb guide?
Skickat från min GT-N7000 via Tapatalk 2

Utacka said:
any news on jb guide?
Skickat från min GT-N7000 via Tapatalk 2
Click to expand...
Click to collapse
Go to project rookie. Should have all you need. Plus the community over there can certainly help you with any questions you have.
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398

[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

Someone, please, compile CM11 snapshot for bacon

Yesterday CM build server compiled bunch of CM11 ROMs, even dedicated article was posted on CM blog. But there's no build for bacon. Since there are a lot of clever guys on XDA, may I ask you for help? Someone, please, do CM11 snapshot for bacon, "as is" or with newer TP drivers, nothing more. I think it can be very famous build since KitKat is still popular around Android users.

ImmortAlex said:
Yesterday CM build server compiled bunch of CM11 ROMs, even dedicated article was posted on CM blog. But there's no build for bacon. Since there are a lot of clever guys on XDA, may I ask you for help? Someone, please, do CM11 snapshot for bacon, "as is" or with newer TP drivers, nothing more. I think it can be very famous build since KitKat is still popular around Android users.
Click to expand...
Click to collapse
Great idea, but should be in the general section.. Tp drivers definitely..
Sent from my A0001 using XDA Premium 4 mobile app

Thats awesome! I would love 2 see someone give KK some attention!

I tried recently, but there are errors during building

CraZY_BoY^ said:
I tried recently, but there are errors during building
Click to expand...
Click to collapse
To bad...

I've got a day off work tomorrow. If I've got time, I'll do a repo sync and build it for you. Did a build a couple of months back of CM11 so should have most things set up still.

Nickamina said:
I've got a day off work tomorrow. If I've got time, I'll do a repo sync and build it for you. Did a build a couple of months back of CM11 so should have most things set up still.
Click to expand...
Click to collapse
Any news already?

EasyGoingXD said:
Any news already?
Click to expand...
Click to collapse
Sorry mate, I haven't forgotten - I've just been busy. I'll get on it when I can.

Nickamina said:
Sorry mate, I haven't forgotten - I've just been busy. I'll get on it when I can.
Click to expand...
Click to collapse
Get healty first thanks for reply

No luck when I tried this evening, gents. Getting this error. I've got work in the morning so no time to troubleshoot at the moment. Any ideas what the problem is?
Code:
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
libcore/luni/src/main/java/java/util/EnumMap.java:162: error: incompatible types: Object cannot be converted to E
return type.get(new MapEntry(enumMap.keys[prePosition],
^
where E is a type-variable:
E extends Object declared in class EnumMapIterator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
3 warnings
make: *** [/home/nicklip/android/system/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
@CraZY_BoY^ are these the errors you got?

Nickamina said:
No luck when I tried this evening, gents. Getting this error. I've got work in the morning so no time to troubleshoot at the moment. Any ideas what the problem is?
Code:
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
libcore/luni/src/main/java/java/util/EnumMap.java:162: error: incompatible types: Object cannot be converted to E
return type.get(new MapEntry(enumMap.keys[prePosition],
^
where E is a type-variable:
E extends Object declared in class EnumMapIterator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
3 warnings
make: *** [/home/nicklip/android/system/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
@CraZY_BoY^ are these the errors you got?
Click to expand...
Click to collapse
Nope, i dont remember exactly what was it, but not your error.
Maybe it's because of incorrect java version?
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac

CraZY_BoY^ said:
Nope, i dont remember exactly what was it, but not your error.
Maybe it's because of incorrect java version?
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac
Click to expand...
Click to collapse
I'm sure it's something java related. Tried a couple of quick java changes already but I'll give your idea a go when I get home. Cheers.

http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.

Aka91 said:
http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.
Click to expand...
Click to collapse
Ah wonderful! That saves me some effort! What do you mean by mostly stable? It's cm11 so I would have thought it would be rock-solid at this point.

Aka91 said:
http://forum.xda-developers.com/showpost.php?p=61581110&postcount=570
I am using this build for 3 days now, mostly stable.
thanks to @obtained.
Click to expand...
Click to collapse
Yep, we know, but we want to know how to resolve this error(s).

Make sure you are on OpenJDK 1.6:
This guide here goes through how to change versions for all components of Java.
Also your manifests file should look like this (this is what mine looks like for building 0702):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" />
<project name="CyanogenMod/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="CyanogenMod/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="CyanogenMod/android_kernel_oneplus_msm8974" path="kernel/oneplus/msm8974" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" />
<project name="CyanogenMod/android_frameworks_opt_connectivity" path="frameworks/opt/connectivity" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
</manifest>
Manifests courtesy of @Muurahainen
Anyway, I build 0702 and uploaded it here: https://www.androidfilehost.com/?w=files&flid=33863

[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