I build SlimKat but no apks are compiled - SlimRoms Q&A

Hello,
I've built SlimKat for my device, I'm 100% sure my device tree is correct, I compared it to seceral other device trees from official github.
The problem is that the build has no apk files. It looks like full_base_telephony.mk and vendor/slim/config/common_full_phone.mk are not inclued. It's weird.
My device tree here
I run build by these commands:
. build/envsetup.sh
brunch jlo
Click to expand...
Click to collapse
I know some other people had this problem too, can you explan me what's wrong?

but rom compiled?
try:
Code:
. build/envsetup.sh
breakfast jlo
brunch jlo

Related

CM7 source?

Do any of you have the source of the latest CM7 release for the kindle fire. I want to get into rom development and want a rom source so I can study the source.
ragul40 said:
Do any of you have the source of the latest CM7 release for the kindle fire. I want to get into rom development and want a rom source so I can study the source.
Click to expand...
Click to collapse
Don't know if he keeps it up to date, but here:
https://github.com/whistlestop/CM7KF
I would just run:
Code:
repo init -u git://github.com/whistlestop/CM7KF.git -b
then repo sync

[Q] How to port a custom rom

I tried to port a custom rom but when I flashed the rom the phone didn't started
VanshKhanna said:
I tried to port a custom rom but when I flashed the rom the phone didn't started
Click to expand...
Click to collapse
You didn't mention how you tried to do it, or what problems you ran into so no one can tell you what you did wrong or provide a solution to the compilation error you might have faced.
'There's a lot of threads already available all over XDA for helping with this, so please use XDA or google search extensively.
iceyhotguy said:
You didn't mention how you tried to do it, or what problems you ran into so no one can tell you what you did wrong or provide a solution to the compilation error you might have faced.
'There's a lot of threads already available all over XDA for helping with this, so please use XDA or google search extensively.
Click to expand...
Click to collapse
Hii... can u help us to give a specific link for porting ROM from the source (i.e PACMAN, slimbean, etc) and keeping CM11 as a base.
I couldn't find the best page where I get all thing for my ROM.
Thanks in advance.!:good:
RIPPER said:
Hii... can u help us to give a specific link for porting ROM from the source (i.e PACMAN, slimbean, etc) and keeping CM11 as a base.
I couldn't find the best page where I get all thing for my ROM.
Thanks in advance.!:good:
Click to expand...
Click to collapse
k2wl's build CM from source is the best method, you just have to switch this line
HTML:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
with the github link to the source of any custom ROM you want.
Like for getting RR source it would be
HTML:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b kitkat1
All ROMs actually provide you with a method to port their ROMs for your phone in their manifest.
Like for example, you feel like compiling Resurrection it's https://github.com/ResurrectionRemix/platform_manifest
iceyhotguy said:
k2wl's build CM from source is the best method, you just have to switch this line
HTML:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
with the github link to the source of any custom ROM you want.
Like for getting RR source it would be
HTML:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b kitkat1
All ROMs actually provide you with a method to port their ROMs for your phone in their manifest.
Like for example, you feel like compiling Resurrection it's https://github.com/ResurrectionRemix/platform_manifest
Click to expand...
Click to collapse
Thanks man..this is a grrt help:good::good: I am working for beanstalk ROM. may be dis tym I will crack it.. thankk uuuuuuu
RIPPER said:
Thanks man..this is a grrt help:good::good: I am working for beanstalk ROM. may be dis tym I will crack it.. thankk uuuuuuu
Click to expand...
Click to collapse
Yup. Along with some rom specific changes. I am working on liquidsmooth v3.0.
Sent from my GT-I9082 using Tapatalk Pro.
##W4TCH0UT## said:
Yup. Along with some rom specific changes. I am working on liquidsmooth v3.0.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
I am not getting one thing though..k2wl mentioned we have to download 10-12 GB data for cm11 or other ROM. y so?? is the data soo huge?
RIPPER said:
I am not getting one thing though..k2wl mentioned we have to download 10-12 GB data for cm11 or other ROM. y so?? is the data soo huge?
Click to expand...
Click to collapse
Actually the more the folders, the more the data. So dats why. There are less folders in the beanstalk source than the cm source, so it will be about 10gb. I guess.
Sent from my GT-I9082 using Tapatalk Pro.
##W4TCH0UT## said:
Actually the more the folders, the more the data. So dats why. There are less folders in the beanstalk source than the cm source, so it will be about 10gb. I guess.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
is it resumable?? he mentioned REPO SYNC to be applied if it breaks.does it work.bcoz i need 2 days to download all the source
RIPPER said:
is it resumable?? he mentioned REPO SYNC to be applied if it breaks.does it work.bcoz i need 2 days to download all the source
Click to expand...
Click to collapse
Not resumable. You have to restart.
Sent from my GT-I9082 using Tapatalk Pro.
##W4TCH0UT## said:
Not resumable. You have to restart.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
I have to download from office then
RIPPER said:
is it resumable?? he mentioned REPO SYNC to be applied if it breaks.does it work.bcoz i need 2 days to download all the source
Click to expand...
Click to collapse
repo sync is soley there so you can resume.
you can break and close terminal at any time, when you use repo sync again, it will scan through your folder comparing everything what you have downloaded to the source folder on the git and then start downloading from where it left off
iceyhotguy said:
repo sync is soley there so you can resume.
you can break and close terminal at any time, when you use repo sync again, it will scan through your folder comparing everything what you have downloaded to the source folder on the git and then start downloading from where it left off
Click to expand...
Click to collapse
dats grrt..downloading. thanks.
u r alwys been a grrt help to m.:good:
hi
hi
The main differences between this ROM with ROM?
I used the method which is shown in this tutorial http://forum.xda-developers.com/showthread.php?t=1908008
And it gave me a bootloop the bootanimations stays for ever

Aosb 1.3.7[build from source]

Hi, I want to build This ROM for your devices, but I can't build with Quarx repo, anyone can help me to build it, I don't have this device, but I think that maybe u want it, and I have time to do it.
The problem came when I try to build the rom, because the terminal didn't recognize vendor files and some things in device tree, I don't know why, if anyone can help me about how to build it plz tell me I need to know how to put the repo of Quarx in the correct way in order to build it.
Thanks
Regards
@tonyt. Look if this can help
http://forum.xda-developers.com/showthread.php?t=1593117
no match
DiegoxG said:
@tonyt. Look if this can help
http://forum.xda-developers.com/showthread.php?t=1593117
Click to expand...
Click to collapse
Yes, but I need it for CM11, this thread is for CM9 and CM10 :/
tonyt. said:
Yes, but I need it for CM11, this thread is for CM9 and CM10 :/
Click to expand...
Click to collapse
Correct me if I'm wrong:
$ repo init -u git://github.com/Quarx2k/android.git -b cm-11.0
https://github.com/Quarx2k/proprietary_vendor_motorola/tree/cm-11.0
If you see the branches there's not any called kitkat but cm-11.0
Edit: or maybe https://github.com/Quarx2k/android_device_moto_jordan-common/tree/cm11.0-2.6.32
$ repo init -u git://github.com/Quarx2k/android.git -b cm11.0-2.6.32
I think it's the last one because it's specific about the Defy, its kernel is 2.6.32
Try
I´ll try again, because I try to use it but in the env didn't appear the device, thanks, i´ll try it.
tonyt. said:
I´ll try again, because I try to use it but in the env didn't appear the device, thanks, i´ll try it.
Click to expand...
Click to collapse
Maybe https://github.com/Quarx2k/android_d.../cm11.0-2.6.32
$ repo init -u git://github.com/Quarx2k/android.git -b cm11.0-2.6.32
I think it's the last one because it's specific about the Defy, which kernel is 2.6.32
Sorry for late editing
error manifest
DiegoxG said:
I think it's the last one because it's specific about the Defy, which kernel is 2.6.32
Sorry for late editing
Click to expand...
Click to collapse
"...revision cm11.0-2.6.32 in manifests not found"

[Kernel][Linaro] Stock KK kernel for Falcon

This is a near stock falcon 4.4.4 kernel built with the latest Linaro toolchain (Linaro GCC 4.9-2014.12) for all of those who prefer stock kernels and absolutely need those 10 extra points in Antutu
Differences from stock are just a few Cortex-A7 optimizations, F2FS patches from mainline 3.18 and linaro toolchain.
All credit goes to @bedalus, who started his kernel thread for Peregrine, fixed all the small bugs that made compiling with newer Linaro toolchains impossible and cherry picked all those F2FS patches.
Sources and tools used:
MotorolaMobilityLLC/kernel-msm
MotorolaMobilityLLC/vendor-qcom-opensource-wlan-prima
bedalus' patches
Christopher83's Linaro Toolchain
My repo, where all sources are merged
Changelog:
falcon_stock_4.4.4_linaro_4.9.3.zip
- stock kernel
- added necessary patches to make it compile with linaro
- some Cortex-A7 optimizations
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
The zip can be flashed with TWRP or CWM. Not flashable through fastboot.
Thanks @knizmi. I think stock users will appreciate this
Anyone tested? How the battery?
Wysłane z MOTO G
Dizzyrul3z said:
Anyone tested? How the battery?
Click to expand...
Click to collapse
This is the stock kernel, so the batttery is as good as with stock kernel (you really can´t make it much better in any way). These screenshots are taken after some 7 hours of sleep.
Works pretty good on XT1031. Nice work! Any chance you could make a build with the kexec hardboot patch to use it with multirom?
I immediately noticed a performance improvement after flashing this kernel. Thanks!
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
This is my preferred way to grab commits. Did you add my repo as a remote?
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
bedalus said:
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
Click to expand...
Click to collapse
Thanks a bunch, this should really make merging those patches easy!
bedalus said:
This is my preferred way to grab commits. Did you add my repo as a remote?
Click to expand...
Click to collapse
I have added your repo as a remote now. I was fighting with git last week quite a bit (never used that devil's tool before), but now I think I am getting used to it. For my first build I've just "patched" those files with gedit...
syrkles said:
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up, but compiling someone else's sources doesn't make me a dev
New version uploaded.
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
Thanks @bedalus.
amarc78 said:
Any chance you could make a build with the kexec hardboot patch to use it with multirom?
Click to expand...
Click to collapse
Sorry, the aim of this is to stay as close to stock as possible and only add optimizations/update drivers.
knizmi said:
For my first build I've just "patched" those files with gedit...
Click to expand...
Click to collapse
If you've got my repo as a remote you should be able to see my commits with
Code:
git log -- bedalus/moggy
depending on what you named your remote.
Once you see what commits you want, copy their hashes (the long string of letters/numbers) then
Code:
git cherry-pick *hash*
If there's a problem with the cherry-pick you can fix it manually with
Code:
git mergetool
or abort with [git cherry-pick --abort[/code]
I've installed meld as my mergetool. I'm using a debian derivative so I did
Code:
sudo apt-get install meld
That's a pretty comprehensive quick-start guide to cherry-picking from any remotes you've fetched.
Cannot downgrade to default stock.
can you make a zip with libs to go back.
everb00b said:
Cannot downgrade to default stock.
can you make a zip with libs to go back.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=2649763
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
amarc78 said:
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
Click to expand...
Click to collapse
You mean in the thread I've posted. I've thought that too at the beginning, but they are there separately, look for Stock Kernel Modules: [XT1032] - 4.4.2 | 4.4.3 | 4.4.4 | 4.4.4 (GPE) | 5.0.1 (GPE) | [XT1033] (Dual-SIM) - 4.4.4. You just have to flash two zips instead of one.
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Edit: never mind. They look the same.
amarc78 said:
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Click to expand...
Click to collapse
Not sure, you can try. If there is a problem you can always reflash stock /system, backup those modules and perhaps send them to @lost101
bedalus said:
If you've got my repo as a remote you should be able to see my commits
Click to expand...
Click to collapse
Thank you for the info again. You are very helpful.
Do I understand it correctly that I need to fetch your repo before I can start cherry-picking? Searching around the internet , it looks like it. I may give it a try one day, but for now I will stick with git am, which seems like the perfect tool to pick single commits from many repos.

CyanogenMod for Pixel v1

FIRST TEST BUILD OUT
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_google_seedmtk
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : [url]https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout[/URL]
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_seedmtk-2ndgen
NOTE TO TESTERS : Please try getting logcats for me since it is IMPOSSIBLE to do anything without even knowing why something is broken
MSF Jarvis said:
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_mediatek_sprout
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_sprout-2ndgen
I am currently negotiating for a server with one of my dear friends, and will commence builds as soon as I can wrangle one out from him
Everyone is welcome to help me out with this project. I tried getting @DHARMESH17 onto it but apparently it seems he's not very interested or dedicated to the cause.
And oh, almost forgot, here's a local manifest to prevent manually cloning things : https://github.com/TeamRedux/local_manifests/tree/cm-13.0-sprout
Click to expand...
Click to collapse
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom
DHARMESH17 said:
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom
Click to expand...
Click to collapse
I would like some proof of your ability with ROM compiling before I let you in on my server.
Ashiron said:
Give me full details.
Start to end.
100% success result
??
Click to expand...
Click to collapse
Details as in??
The kernel source has been imported to my Github and I have also set-up Continuous Integration on it through Travis-CI, build progress can be tracked here.
I would like to thank @akhilnarang whose ThugLife scripts have been used to compile the kernel inside the CI. I couldn't include your name in the commits, but the original copyright notice has been retained in the spirit of open source.
I have been informed through Google Plus that @DHARMESH17 has been in the hospital for some time now, and @faddat is currently in China, so the project has been put on hold for now.
Work will begin tomorrow
You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot
akhilnarang said:
You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot
Click to expand...
Click to collapse
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution
MSF Jarvis said:
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution
Click to expand...
Click to collapse
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM
akhilnarang said:
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM
Click to expand...
Click to collapse
Go ahead and try
MSF Jarvis said:
Go ahead and try
Click to expand...
Click to collapse
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app
akhilnarang said:
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )
I have got a server now, and will commence builds tomorrow. Stay tuned!
MSF Jarvis said:
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )
Click to expand...
Click to collapse
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app
akhilnarang said:
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)
MSF Jarvis said:
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)
Click to expand...
Click to collapse
Yep
Code:
PRODUCT_COPY_FILES := $(LOCAL_PATH)/kernel:kernel
Sent from my Nexus 5X using XDA-Developers mobile app
@akhilnarang, you free some night? I'll be needing help as far as I can see.
Anyways, ever had a problem with cts/apps/ctsVerifier throwing exceptions? My build refuses to start! Not to mention that repo is also being very hard on me, not syncing projects, throwing exceptions while unpacking and ****. Gonna rebase to nightly level, currently on snapshot 1.
Official TWRP now available : http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364
MSF Jarvis said:
I would like some proof of your ability with ROM compiling before I let you in on my server.
Click to expand...
Click to collapse
Bro still want proof LoL ??

Categories

Resources