Develop Bugs

[Kernel][Source] Samsung Galaxy Note II kernel source

This is the complete kernel source zip from Samsung.
http://db.tt/iN5NXOUr
I've spent a few hours downloading and trying to compile. As far as I can tell it is broken. Erroring out on the mali drivers. I don't have enough experience to fix this. So I'm offering the zip from a faster download source.

Thank you so much!

I think Samsung just release the ROM source code here. I haven't download it yet so I could be wrong.

ima bring this thread back. the code builds fine with 4.4.3 GCC i never had any fatal errors just "warning: value computed is not used [-Wunused-value]" these all can be fixed pretty easy.

Evolutionmods said:
ima bring this thread back. the code builds fine with 4.4.3 GCC i never had any fatal errors just "warning: value computed is not used [-Wunused-value]" these all can be fixed pretty easy.
Click to expand...
Click to collapse
Whoa you got a note? !
Sent from my SPH-L900 using Tapatalk 2

[Reference] Building Android / Kernels for the LG E980 (ATT)

Howdy Everyone!
Here's my quick guide to compiling Android for the Optimus G Pro for ATT.
Basic Reference
For reference, this phone's codename is "geefhd" per the stock boot.img, however the kernel defconfig is "gkatt_bcm".
Simplicity sake dictates that I would like to use the kernel defconfig's name as the device codename.
From here on out, I'd like to refer to this phone in code as gkatt, yet we'll call the kernel source dir geefhd.​
Prerequisites
Building Android for this phone requires quite a bit of familiarity with the Android build system. If you are unfamiliar with things like makefiles and bash, I do not recommend trying this, as you'll pull out more of your hair than you can afford to lose.
That said, I'd recommend you have at least repo installed, or in your $PATH variable to make this guide a little easier to follow.
You also need to have the build utilities installed. See the CyanogenMod wiki for the build dependencies and how to install them.​
Getting your tree set up
Well, it ain't Christmas, but let's put up the tree anyway.
For this guide, I'm going to assume you're like me, and you put all your Android projects in ~/android/.
Let's begin.
Code:
mkdir -p ~/android/cm-10.1/
cd ~/android/cm-10.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync
Now after a few hours, you'll have a empty tree set up. Let's decorate!​
Getting the device repos set up
Once you have the basic CM skeleton in place, we need to add our device support files.
Code:
mkdir -p ~/android/cm-10.1/device/lge
cd ~/android/cm-10.1/device/lge
git clone -b cm-10.1 https://github.com/TeamLGOG/android_device_lge_gee-common.git gee-common
git clone https://github.com/thecubed/android_device_lge_gkatt.git gkatt
Congrats. Now you have the Android side of things ready, however you're not fully ready to start building-- you need a kernel!​
Getting the kernel repos ready
Next up: kernel.
Code:
mkdir -p ~/android/cm-10.1/kernel/lge
cd ~/android/cm-10.1/kernel/lge
git clone https://github.com/thecubed/android_kernel_lge_geefhd.git geefhd
You should now have a nice folder containing the kernel and everything you need to build it.​
Great! What do I do with this?
You now have two options -- do you want to build Android AND a kernel, or just a kernel?
Let's assume you want to build a kernel only first.
Code:
cd ~/android/cm-10.1/kernel/lge/geefhd
. envsetup.sh
Now you'll see some neat text from my setup script, it'll tell you what commands it just added to your shell and how to use them.
To build a kernel do this:
Code:
make mrproper
make gkatt_bcm-perf_defconfig
make zImage
Then you can look in arch/arm/boot for a file called zImage, which is the kernel itself, ready to be used and abused.
Once you're done and want to clean up, just run make clean or make mrproper to erase all tracks of ever building.
Keep in mind, "mrproper" erases your ".config" file, so before you can build again, you have to issue "make gkatt_bcm-perf_defconfig".
My envsetup script will warn you of that, just incase you forget
Now, let's assume you want to build an Android recovery image!
Code:
cd ~/android/cm-10.1/
. build/envsetup.sh
lunch cm_gkatt-userdebug
The environment is now ready for you to build...
Code:
mka recoveryimage
In about 10 mins you'll have a full recovery.img in $OUT.
The neat thing about this is it builds the kernel inline with your build -- so you build a recovery AND a kernel at the same time.
This will save you a LOT of time testing kernels, since you don't have to manually unpack and repack the boot image after modifying the kernel.
To see your shiny new recovery.img file:
Code:
cd $OUT
KEEP IN MIND you CANNOT flash these images! Flashing them will result in a security error!
You can only fastboot boot these images. I'll post fastboot instructions shortly.​
How do I get help??
Well, first things first, ask on IRC.
I'm nearly always around on Freenode. Join #lg-optimus-g and ask if I'm around.
I go by the name IOMonster on IRC. When I'm at work, I'm IOMonster_work.
Please don't just ask to ask a question, ask your full question.
Don't PM me unless you ask first, it's weird to get 20 PM windows open on my IRC client and not have any idea who is who or what they want... basic courtesy please
If by chance/miracle I'm not on IRC, post here. Again, I will not answer questions related to this via PM on XDA. I like answering things publicly so that others can read the answer. Google doesn't index PM's (yet, at least haha), so it doesn't do anyone any good to help you over PM unless it's something private.​
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.​
Let me know if I missed anything!

Awesome work! How can we get the vendor files to build cm-10.1? For now, could we use the same as the OG ?

apascual89 said:
Awesome work! How can we get the vendor files to build cm-10.1? For now, could we use the same as the OG ?
Click to expand...
Click to collapse
Check http://github.com/TeamLGOG
The vendor files there should work fine for this device, minus the wlan props and any modem/DSP related firmware.
This phone is *very* similar to the OG/N4, it's just got a larger screen and different wlan chip (Broadcom instead of Qualcomm)
However, all that said, I've yet to build it for the phone-- I'm focused on getting it more unlocked right now.

thecubed said:
Check http://github.com/TeamLGOG
The vendor files there should work fine for this device, minus the wlan props and any modem/DSP related firmware.
This phone is *very* similar to the OG/N4, it's just got a larger screen and different wlan chip (Broadcom instead of Qualcomm)
However, all that said, I've yet to build it for the phone-- I'm focused on getting it more unlocked right now.
Click to expand...
Click to collapse
Hi there
I am interest in building E988 kernel which is international version of Optimus G Pro
would you mind tell me how to tweak the E988 source on this development ?
E988 is using gku-perf_defconfig
E988 is using different wlan chip vs ATT

hkfriends said:
Hi there
I am interest in building E988 kernel which is international version of Optimus G Pro
would you mind tell me how to tweak the E988 source on this development ?
E988 is using gku-perf_defconfig
E988 is using different wlan chip vs ATT
Click to expand...
Click to collapse
Have you tried gku_bcm-perf_defconfig ?
I have a feeling that might do the trick

thecubed said:
Have you tried gku_bcm-perf_defconfig ?
I have a feeling that might do the trick
Click to expand...
Click to collapse
yes, i tested in E988 source.. and it will hanged and stuck in fastboot screen (as last time, I try to compile BCM config (want a trick for a wrong driver)
anyway.. i will clone your kernel source first to see and will try using your source to compile with "gku-perf_defconfig"
I believe the E980 and E988 is the same kernel source, only config is different (i hope)
Edit: (Testing Case)
1) Using your source code and with gku-perf_defconfig =>
Fastboot boot <myboot.img> => reboot => then back to Fastboot mode
It seems wcnss_wlan (Qualcomm) has issue again
https://mega.co.nz/#!VI4S3RgK!SpgWgX5mUXrQFpYeE9oZlXbyVkImsIYz6J_CWWe9X5M
[ 5.528704 / 01-18 07:39:57.262] wcnss_wlan wcnss_wlan.0: WCNSS Power-up failed.
[ 5.535174 / 01-18 07:39:57.272] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 5.535449 / 01-18 07:39:57.272] init: cannot find '/system/bin/libbroadcast_server', disabling 'broadcast'
[ 5.536303 / 01-18 07:39:57.272] init: cannot find '/system/xbin/spritebud', disabling 'spritebud'
[ 5.536365 / 01-18 07:39:57.272] init: cannot find '/system/bin/rf4ce', disabling 'rf4ce'
[ 5.547504 / 01-18 07:39:57.282] wcnss_wlan triggered by userspace
2) Using your source code and with gku_bcm-perf_defconfig =>
Fastboot boot <myboot.img> => hanged => need press power button for 3sec and re-start in fastboot mode
then I fash back the stock image and then try to get last_kmsg...
but I get nothing due to hanged (i think)
[email protected]:/ # cat /proc/last_kmsg > /sdcard/last_kmsg.txt
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
/proc/last_kmsg: No such file or directory

thanks for all your work only one question how to get into fast boot

Got a small error but duno how to fix it here a build log\
build/core/Makefile:419: *** BOARD_FORCE_RAMDISK_ADDRESS has been deprecated. Use BOARD_MKBOOTIMG_ARGS.. Stop.
[email protected]:~/android/cm-10.1#
that's when tring to build recovery
This is when tring to build kernel
MK_FW firmware/audience-es325-fw.bin.gen.S
make[1]: *** No rule to make target `firmware/audience-es325-fw.bin', needed by `firmware/audience-es325-fw.bin.gen.o'. Stop.
make: *** [firmware] Error 2

Gotroot said:
Got a small error but duno how to fix it here a build log\
build/core/Makefile:419: *** BOARD_FORCE_RAMDISK_ADDRESS has been deprecated. Use BOARD_MKBOOTIMG_ARGS.. Stop.
[email protected]:~/android/cm-10.1#
that's when tring to build recovery
This is when tring to build kernel
MK_FW firmware/audience-es325-fw.bin.gen.S
make[1]: *** No rule to make target `firmware/audience-es325-fw.bin', needed by `firmware/audience-es325-fw.bin.gen.o'. Stop.
make: *** [firmware] Error 2
Click to expand...
Click to collapse
I got that same error this morning. Had to leave for work so couldn't really look into it.
Sent from my GT-I9505G using Tapatalk 4 Beta

apascual89 said:
I got that same error this morning. Had to leave for work so couldn't really look into it.
Sent from my GT-I9505G using Tapatalk 4 Beta
Click to expand...
Click to collapse
So, all that is because I just realized I didn't sync CM10.1, but just CM10 to my buildbox...
I'll update it all today, I just realized that when I set up my build dir I just did repo init -u .. -b jellybean instead of cm-10.1
oops!
Anyway, easy fix, and I'll have it out soon-ish today.

thecubed said:
So, all that is because I just realized I didn't sync CM10.1, but just CM10 to my buildbox...
I'll update it all today, I just realized that when I set up my build dir I just did repo init -u .. -b jellybean instead of cm-10.1
oops!
Anyway, easy fix, and I'll have it out soon-ish today.
Click to expand...
Click to collapse
No rush man, I don't want to take time away from you unlocking this beast!

Lmfao awesome!!!!!!

DUDE LOL still throwing back error after redoing my folers heres the error
When making recovery
build/core/base_rules.mk:130: *** gee-common/recovery: MODULE.TARGET.STATIC_LIBRARIES.librecovery_ui_geehrc already defined by device/lge/gee-common/recovery. Stop.
When making kernel
MK_FW firmware/audience-es325-fw.bin.gen.S
make[1]: *** No rule to make target `firmware/audience-es325-fw.bin', needed by `firmware/audience-es325-fw.bin.gen.o'. Stop.
make: *** [firmware] Error 2

I just pushed my (very minor) only correction needed to make this build with cm-10.1 sources.
Provided you have your build environment set up correctly, everything should build now (for recovery at least)

thecubed said:
I just pushed my (very minor) only correction needed to make this build with cm-10.1 sources.
Provided you have your build environment set up correctly, everything should build now (for recovery at least)
Click to expand...
Click to collapse
I tried the mka bootimage option and it gives me the following error:
LD drivers/usb/storage/ums-alauda.o
LD drivers/usb/storage/ums-cypress.o
LD drivers/usb/storage/ums-datafab.o
LD drivers/usb/storage/ums-freecom.o
LD drivers/usb/storage/ums-isd200.o
LD drivers/usb/storage/ums-jumpshot.o
LD drivers/usb/storage/ums-karma.o
LD drivers/usb/storage/ums-onetouch.o
LD drivers/usb/storage/ums-realtek.o
LD drivers/usb/storage/ums-sddr09.o
LD drivers/usb/storage/ums-sddr55.o
LD drivers/usb/storage/ums-usbat.o
LD drivers/usb/storage/built-in.o
LD drivers/usb/built-in.o
LD drivers/built-in.o
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/apascual89/android/cm-10.1/kernel/lge/geefhd'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
[email protected]:~/android/cm-10.1$
In the past I remember seeing that if I was trying to build with an unsupported toolchain.

I'm having a small issue as well so I killed ny whole env... and started from scratch
Sent from my LG-E980 using xda premium

I tried now to build the zImage and got the following error:
MK_FW firmware/audience-es325-fw.bin.gen.S
make[1]: *** No rule to make target `firmware/audience-es325-fw.bin', needed by `firmware/audience-es325-fw.bin.gen.o'. Stop.
make: *** [firmware] Error 2
[email protected]:~/android/cm-10.1/kernel/lge/geefhd$
Just reporting to let you know.

Ok even after thrown my env. away and starting from scratch im still getting the same error
make[1]: *** No rule to make target `firmware/audience-es325-fw.bin', needed by `firmware/audience-es325-fw.bin.gen.o'. Stop.
make: *** [firmware] Error 2

I'm not sure why you guys are getting those errors. I'm able to build the kernel just fine...
Maybe my repo is missing something that I have locally? I'll try re-syncing everything to a new dir and testing again later.

Awesome you got my error log just let me know I will keep hitting it I have nun but time....
Thanks fir the work
Sent from my LG-E980 using xda premium

Building Unlegacy Android

Hi all,
not sure if this is the correct place to post, please move it in case this should be in another forum.
Im planning on start building my own rom based on Unlegacy for my maguro. Havent found anything specific to this project so once im done i will document how to get it done so that others can use it as a reference.
Have been reading over the weekend and i think im quite clear how this works even if it would be the first time i do sth. like this in android world. So please bear with me !
I have contributed several times to the linux kernel and gentoo linux and developed for some other (closed source) projects many years ago which means im an old school guy and im completely disonnected from "modern" development.
I know how to build, patch, debug c and so on but i have almost zero knowledge about git and some of the other tools that are used nowadays. Furthermore i have almost no idea about android itself, im planning on reading more about it to at least know what im doing before getting messy.
Here my first questions, more to come im sure :
- first things first : is there documentation available somewhere specific to this project ?
- im syncing right now. So far it has downloaded 36 GB and repo says it is at 93 % ... is this normal ??? I know android projects are huge but this sounds to me like im doing sth. wrong. Isnt there a way to just sync what i need for tuna ? Am i supposed to tune the manifests to just sync what i need ?
- toolchain : i have seen while it synced several toolchains already. IIRC there were some problems with modern toolchains and gcc-4.7 should be used to avoid some problems with the buggy mmc. Is this still correct or can i just give gcc 5.x a go ? Im asking because thats the toolchain im using right now.
- kernel source : are there other more updated sources available apart from the ones in this tree ?
- build times : im used to long build times. Years ago when we built some huge c++ projects it took days to finish even with the huge buildfarm we had at our dispossal. What build times can i expect with a regular android build like this one ? I have a i7 with 8 cores at 3,5 MhZ and 16 GB Ram available and could even use another similar box with distcc if necessary.
Would really appreciate if someone could sched some light over this and let me have some tips / tricks to avoid further problems.
I have the feeling that some guides im reading are pointless because they are outdated.
Thanks !

Unlegacy Android follows and combines the OMAP4- and Grouper Android OpenSource Project which were created in late 2015 in order to maintain a clean, organized place for pure AOSP support for various OMAP4 and Grouper devices.
The goal is to provide stable and optimized releases of the recent Android versions for the supported devices.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt our changes.
The source is combined power from multiple devs, you won't find a newer kernel or device source for it.
Why there's no official thread yet? We are still preparing our source and some stuff around for best user experience. The source compiles as it is, no need to change anything for tuna.
You should be patient and wait until the stuff is "official official" available, our freetime is limited and we do our best to get things running.

Android-Andi said:
Unlegacy Android follows and combines the OMAP4- and Grouper Android OpenSource Project which were created in late 2015 in order to maintain a clean, organized place for pure AOSP support for various OMAP4 and Grouper devices.
The goal is to provide stable and optimized releases of the recent Android versions for the supported devices.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt our changes.
The source is combined power from multiple devs, you won't find a newer kernel or device source for it.
Why there's no official thread yet? We are still preparing our source and some stuff around for best user experience. The source compiles as it is, no need to change anything for tuna.
You should be patient and wait until the stuff is "official official" available, our freetime is limited and we do our best to get things running.
Click to expand...
Click to collapse
thanks, wasnt actually pushing to know how the current state of thing is, was more about knowing if im doing things correctly.
I have built succesfully a couple of N roms for my maguro and im learning how to cherrypick and reading more about the android frameworks.
thanks !

have just synced and got this when trying to build :
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
make[1]: *** No hay ninguna regla para construir el objetivo 'dtbs'. Alto.
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
make[1]: *** [/usr/src/droid/kernel/samsung/tuna/Makefile:1144: modules] Error 1
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
make[1]: *** [/usr/src/droid/kernel/samsung/tuna/Makefile:1144: modules_install] Error 1
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
[ 33% 9805/29540] target thumb C++: libLLVMCore <= external/llvm/lib/IR/LLVMContext.cpp^Cmake: *** [build/core/ninja.mk:149: ninja_wrapper]
no idea why it complains about dtbs or module support being disabled.
where is the kernel .config file stored by the way ?
any ideas ?
thanks !

thagringo said:
- im syncing right now. So far it has downloaded 36 GB and repo says it is at 93 % ... is this normal ??? I know android projects are huge but this sounds to me like im doing sth. wrong. Isnt there a way to just sync what i need for tuna ? Am i supposed to tune the manifests to just sync what i need ?
Click to expand...
Click to collapse
When building cyanogenmod I can reduce it to about 5GB with this repo init:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0 --depth=1 --groups=all,-notdefault,-device,-darwin,-x86,-mips,-exynos5,-intel,-eclipse,-device
b specifies the branch you want and means you don't get the whole tree.
The --groups excludes a bunch of stuff you don't want/need (mostly different platforms).
The depth command means that only the last version is checked out and not the whole history.
However, if you are creating a new ROM with this a base you might want the history.
Since this is a Developers forum, it would be nice if ROM posters actually put the build instructions in their posts and didn't just link to github and force you to search through 10s of different repos looking for info though.

opticyclic said:
When building cyanogenmod I can reduce it to about 5GB with this repo init:
b specifies the branch you want and means you don't get the whole tree.
The --groups excludes a bunch of stuff you don't want/need (mostly different platforms).
The depth command means that only the last version is checked out and not the whole history.
However, if you are creating a new ROM with this a base you might want the history.
Since this is a Developers forum, it would be nice if ROM posters actually put the build instructions in their posts and didn't just link to github and force you to search through 10s of different repos looking for info though.
Click to expand...
Click to collapse
Nice, thanks a lot !!
For now I have given up and I'm waiting for things to settle down.
Cheers mate !

I'm taking the same W&S Attitude about Building
thagringo said:
Nice, thanks a lot !!
For now I have given up and I'm waiting for things to settle down.
Cheers mate !
Click to expand...
Click to collapse
That is why I am taking the same wait and see attitude about building (though I AM actually running this on my toro-variant GNex on Tracfone; because it's unified, this same ROM will run on maguro).
Since then, I have grabbed AOSP 8.0 (latest branch) and I'm trying to compile (with new branch in place) and I'm running into a headache post-breakfast (breakfast is fine). Where things fall down is between brunch and lunch (in fact, it is during brunch where things fall down). I'm thinking that the falldown is because things are still fluid, so I'll keep the eyes peeled.

PGHammer said:
That is why I am taking the same wait and see attitude about building (though I AM actually running this on my toro-variant GNex on Tracfone; because it's unified, this same ROM will run on maguro).
Steps to take (from stock via Skipsoft Unified Toolkit):
1. Unlock and root (reboot following this step)
2. Flash TWRP 2.7.1.0 and reboot.
3. Upgrade TWRP to 2.8.7.0 and reboot.
4. Download both the firmware and GApps 7.1 pico (as is the case with GApps 6.0, nano is too large for any GNex) and push them to your phone, then force a reboot to recovery (which SHOULD be TWRP 2.8.7.0).
5. Install (in order) aosp_7.1_tuna2016-10-21 (latest as I type this) and open_gapps-arm-7.1-pico.zip. Wipe cache and reboot after the last install.
Click to expand...
Click to collapse
well, yes, i have been using 7.1 for a couple of months already but i was actually trying to build my own with the gcore stuff patches included.
cheers

DEV's build's Q&A discussion board

As the title says. This board is created for questions and answers pertaining to getting new ROM's and ports for our P9000.
THIS IS NOT A BUG REPORT DISCUSSION.
New Development only.
If you would like to see a new ROM for the P9000? Build it, and share it. Check out some of the guides, then ask some questions on building it.
I will be staying with Mediatek devices for the long term and encourage more people like me to start bringing some development love to them.
Thank you

Some useful guides.
https://www.youtube.com/watch?v=aF--LQDgg1M
http://source.android.com/source/initializing.html
Any guides to add? I'll be glad to add them.

Credits:
@Deepflex (Active) Vendor, Device, Kernel sources
@Jonny (Active) TWRP and multiple additions to Kernel source
@skeleton1911 (Active) Stock based ROM's
@leskal (ACTIVE) device and kernel commits
Please let me know of any credits I'm missing.

Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?

syncing AOKP MM. I enjoyed this rom in my samsung days.

something interesting to try for automating builds.
http://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018

electrofryed said:
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
Click to expand...
Click to collapse
Check the .mk files in the root of your device tree, I'm guessing you need to rename a reference in one of them from something like 'cm.mk' to 'candy.mk'

So far I've modified /AndroidProducts.mk cm.mk vendorsetup.sh I think I'm missing a file to modify. Just not sure which one. Unfortunately, since I didn't make a copy of the original Candy directory, I'll need to resync to get rid of my Troubleshooting changes. Good lesson. After each sync, make sure you make a backup of the original in case you forget the modifications you've made. Lol

I think I figured it out. My product name didn't match the vendorsetup.sh
Update: Nope. That didn't work. I've attached a screenshot of the changes I've made in case anyone wants to chime in.
Thank you

What lunch command are you using?

Jonny said:
What lunch command are you using?
Click to expand...
Click to collapse
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.

electrofryed said:
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
Click to expand...
Click to collapse
I recomend the brunch command as on official build guide of cm

Yeah. I tried brunch and "rainbowfarts" (recommended by AOKP. Lol. It stops when calling for maven 1.6 (I'm on 2.10). I think I need to find the file that will link my builds to my build environment path.

leskal said:
I recomend the brunch command as on official build guide of cm
Click to expand...
Click to collapse
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.

electrofryed said:
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
Click to expand...
Click to collapse
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command

leskal said:
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
Click to expand...
Click to collapse
Great guide!! I see a few big differences between this guide and some of the others. The biggest is the method of getting java 7 for 16.04. I've been using Oracle and open Java 8 the whole time.

Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh

Hello,
i started my first build-experience with downloading the cm13 sources and the p9000 sources form deepflex. Since yesterday i have an successful build cm_p9000-ota.zip package but after installation it ends in an bootloop!! I have no idea where to start searching for the mistake... I get no error massage while installing it.
Could someone give me a hint?

electrofryed said:
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Click to expand...
Click to collapse
You need to fix includes when building out of mtk build chain, or use other sources that already have this done

OK, i get it running!
But, is their a reason why "/android_device_elephone_p9000/mediatek_driver_nl80211.h" is missing in the repo? Sorry, but i am totally new and trying to understand how these builds work and what exactly is needed to build a bugles ROM.

Any AOSP / LineageOS based ROMs in development?

Not asking for an ETA, but just wondering what we can expect in the future.
As of now, the only custom ROM in the Development section is the OOS-based FreedonOS.
A lack of AOSP-based ROMs is the only thing holding me back from using this as my daily phone.

I believe several groups are working on their AOSP firmwares for this phone. It's still pretty new and nobody wants to release a crap product out of the gate.
I know one very popular group for sure is (they're dirty ?).

I'm hoping for lineage and aospa support. Pretty sure lineage will reuse their oneplus5 rom. It's basically the same phone just with another display. With aospa we'll have to wait until the Oreo update is out. I don't expect anything new from them before that.

I am especcially waiting for Ressurection Remix

Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.

GZOSP just added a dumpling section for devices so there's some hope for Validus. We'll have to wait for full development though since I don't think we'll have unified builds.

x111 said:
Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.
Click to expand...
Click to collapse
The device is what, 2 weeks old? You expect development to be at the level of a 3 year old device? You may need to lower your expectations a bit.
Sent from my Pixel XL using Tapatalk

I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Check with @darkobas, he got his kernel to boot.

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:

DocRambone said:
Check with @darkobas, he got his kernel to boot.
Click to expand...
Click to collapse
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Tiz92 said:
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:
Click to expand...
Click to collapse
Yes I got my device 2 days back

varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/

DocRambone said:
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/
Click to expand...
Click to collapse
Thank you buddy .will give this a try
EDIT: got stuck with this annoying error
Code:
INSTALL usr/include/asm-generic/ (35 files)
/home/varun/RR/kernel/oneplus/msm8998/scripts/Makefile.headersinst:55: *** Missing UAPI file /home/varun/RR/kernel/oneplus/msm8998/include/uapi/linux/ashmem.h. Stop.
make[2]: *** [linux] Error 2
make[2]: *** Waiting for unfinished jobs....
INSTALL usr/include/drm/ (21 files)
INSTALL usr/include/misc/ (1 file)
INSTALL usr/include/media/ (21 files)
make[1]: *** [headers_install] Error 2
make[1]: Leaving directory `/home/varun/RR/out/target/product/dumpling/obj/KERNEL_OBJ'
make: *** [sub-make] Error 2
make: Leaving directory `/home/varun/RR/kernel/oneplus/msm8998'
[ 36% 930/2537] target C: libc_openbs...tream-openbsd/lib/libc/string/strspn.c
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1

Maybe ask some of the big guys of LOS

varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
Nice to have you around... What device tree did you try use?

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe

dcd1182 said:
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe
Click to expand...
Click to collapse
Hi do you have a working device tree ? Mines messed up

jgcaap said:
Nice to have you around... What device tree did you try use?
Click to expand...
Click to collapse
I tried the NastyAndroidDevs device tree from lineage 15.0 branch