yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] ezio84:
My source is non-caf, so for a non-caf device the fast way is to repo init the lp5.0 slim source and then add my local manifest (Click) and the vendor blobs lines for the specific device. Then repo sync again and you are ready to build.

With a caf device like the d802 (right?) the best way is to manually cherry-pick the commits, because the code is quite different (mostly in the frameworks_base folder). The build and the vendor folders can be cloned from my git, the code is the same for all devices.

Otherwise you could build another caf rom, check post 2 and 10 of this thread (they are both built by [MENTION=264345]ralpheboyo[/MENTION] and [MENTION=3306843]kantjer[/MENTION] for the Bacon).

No specific battery optimizations in my build, just ubertc and the CM fix ;D
[Android Builders Collective] Mikulec:
Nicely said :good:, couldnt agree more.
[Android Builders Collective] expiredd:
Heya! I'm looking for an updated build guide.

Would like to build my own [MENTION=1228651]fusionjack[/MENTION] SlimSaber builds and try to get customize them. However I'm a bit lost on where to start. I would like to try different build-chains.

I've only found this: http://xdaforums.com/showpost.php?p=55178446&postcount=77
[Android Builders Collective] TaRsY:
Really thank you. D802 is caf device (although kernel is non-caf, but as I can see Rashed97 is worikng on it for the 5.1 https://github.com/lg-devs/android_kernel_lge_msm8974-caf/commits/lge-lp5.1). I think G2 is not the best device choice to build for (especially for beginners like me and right before 5.1 drop and lg lp kernel source release)

I'll look into this and also contact g2 devs for device specific help, but first I have to reinstall ubuntu, latest nvidia driver broke all the things yesterday (bring intel and nvidia graphics together with optimus and attached external screen...)
[Android Builders Collective] ralpheboyo:
Hi guys....was just messing around with CM and built a rom for bacon with all the CM crap stripped out....if interested you can dl and test drive....

(It's pretty much the same as my ultra slim...just used CM as base this time....US & UK English only )....

https://basketbuild.com/devs/ralpheeee88/Bacon/Ultra Slim CM
[Android Builders Collective] ezio84:
Slimsaber has its own default manifest, so you can repo init it without going through the slim one:

https://github.com/SlimSaber/platform_manifest

To cherry-pick and add some customized stuff, yes you can follow my guide.
[Android Builders Collective] angelcalibur:
sup guys!

i have issus again with PNG Optimisation...

here is the issu :

Optimizing PNGs to Shrink ROM Size

/bin/bash: systemimage-squisher : commande introuvable

build/core/Makefile:992: recipe for target 'systemimage-squisher' failed

make: *** [systemimage-squisher] Error 127

make: *** Attente des tâches non terminées....

chunk 0: type 0 start 0 len 5562378

chunk 1: type 2 start 5562378 len 1284864

chunk 2: type 0 start 6224005 len 1915

Construct patches for 3 chunks...

patch 0 is 210 bytes (of 5562378)

patch 1 is 567453 bytes (of 661627)

patch 2 is 179 bytes (of 1915)

chunk 0: normal ( 0, 5562378) 210

chunk 1: deflate ( 5562378, 1370104) 567453 (null)

chunk 2: normal ( 6932482, 2046) 179

#### make failed to build some targets (06:59 (mm:ss)) ####

i have install the package named pngquant but i have this issus again.

i have reboot computer after instal...

But i just made installclean and rebuild, without make clobber, ccache -C etc...

do you think the issu i have is du too this?
[Android Builders Collective] Riddlah:
I've seen the chunk stuff come up on a single package when I've used a makeclean but not fail on that part. Do you have the four commits? I believe the finisher script is also required to for the squisher script.
[Android Builders Collective] angelcalibur:
no sure riddlah bout the commit...

do you have the link?

or maybee the simple for me is to erase the commit.

because i'am not really interresting in png optimisation... :p
[Android Builders Collective] danarama:
Hey [MENTION=1228651]fusionjack[/MENTION]

Can you confirm something to me please?

I created settings icons for RRO layers. Someone using slimsaber asked me to theme the new Mobile icon in settings. It looks the same as ic_settings_cell_standby which is already themed in my themes. Is it called ic_settings_cellular in you rom? I'm asking because I can make a copy of the icon with the new name in my theme. However, i have had to do this a few times with other icons in other roms and this may cause an issue for themers down the line as my themes for example seem to be ballooning up.

I'm just wondering, if it is the same as ic_settings_cell_standby, would you consider renaming it in your source to that please? That would kill 2 icons with one one stone
[Android Builders Collective] Riddlah:
It should also help to reduce the size of the zip after its finished. Here are the four commits I've used for it:

Build:

Squisher - https://github.com/Riddlah/android_build/commit/201cd4e65cb2ad4a68f5331306eb0152cee6c95f

Finisher - https://github.com/Riddlah/android_build/commit/f1b9dd22d68380a608be9292369f459f73823540

Vendor/Slim:

Squisher - https://github.com/Riddlah/vendor_slim/commit/aca3061a6f015b6196e80a940429e54b04e179c2

Finisher - https://github.com/Riddlah/vendor_slim/commit/df82a7806e1892b18ccc524d46046ab29b0922ea
[Android Builders Collective] angelcalibur:
thx riddlah! ;)

i'am gonna watch it! :o
[Android Builders Collective] Mikulec:
Any comparison CM vs Slim? :angel:
[Android Builders Collective] kagwind:
OK. I finished my temporary goal of porting SlimActions.

The work consists of two parts:

1. My initial intention was porting SlimActions to [MENTION=2033478]Yank555[/MENTION] 's NavRing feature. This actually follows SlimKat's code centralization, which put all actions together and exposed them via Shortcuts, Tiles, Navbar/Navring buttons, Hardware buttons later. Eventually it should serve the same way it did.

2. I also put back some missing features (mostly the ones I use) into SlimActions, including quicksettings panel, smart pulldown, power menu, screen off. The Screenshot SlimShortcut is also fixed. This is based on [MENTION=1277872]dankoman[/MENTION] and [MENTION=4911350]RobbieL811[/MENTION] 's porting.

Those who are interested can look into my github:

frameworks_base

packages_apps_Settings

Known issues: silent mode shortcut is not working as intended.

Actually, setting silent mode by using audiomanager is buggy in lp5.0, which seems to be fixed in lp5.1, so I'll just leave it there. Once we are updated to 5.1, those features should work correctly. The reason is the Zenmode (Priority notification) introduced in Lollipop, which interferes the ringer mode. Google should really keep it together.

You still can use Tile to control that, which uses a work-around method.

OT: I don't have Roms to release atm since I use Code_Blue during compiling. eng.stk doesn't like his kernel packed in Roms and I respect that.
[Android Builders Collective] ezio84:
Amazing work mate! Thanks a lot.

I'll try to pick your commits, having slim actions also in navbar and ring is really nice.
[Android Builders Collective] fusionjack:
it is different vector drawable: res/drawable/ic_settings_cellular.xml

this is the same with the cm one. i'll try to check if i can use ic_settings_cell_standby drawable...so that you don't need to theme for that new drawable.
[Android Builders Collective] kagwind:
I should tone down my statement a bit.:p It's not completely there yet.

Code in navbar and navring still needs to be changed. But eventually it should.
[Android Builders Collective] fusionjack:
if i may give my opinion, actually you don't need to port shortcut for last-app, screenshot and torch if you expose the slim actions as a shortcut. this means any slim actions can be used as a shortcut.
[Android Builders Collective] ezio84:
It's a great step anyway :D
[Android Builders Collective] kagwind:
It's true.

But torch was ported by others ( I think it's Robbie), I just fixed the broken screenshot, and last-app... it was in kk4.4, so I just slipped it in as well, trying to figure out how it works. Because I was not sure whether there were some situations that they would be needed. (And I don't want CoS being too lonely there :silly: )

And It's also for learning and for fun. :D
[Android Builders Collective] fusionjack:
you can follow my guide to build slimsaber: http://xdaforums.com/showpost.php?p=54562517&postcount=14104

other than that, like cherry-picking or other, you can follow [MENTION=2095315]ezio84[/MENTION] guide :)
[Android Builders Collective] expiredd:
Can't thank your post ! already reached 8 likes for today sorry.

I would like to change default kernel built into ROM, trying to find some examples of this.
[Android Builders Collective] ralpheboyo:
CM over the last week's I noticed where pushing real hard on Gerrit....with 12S round the corner i.e. 27th March...their Gerrit is still on fire....

Also if you notice .....or.....take a look at where cherry picks are originating from.....you might be surprised....

SLIM is SLIM....

1+1 Ultra~Slim

---------- Post added at 18:55 ---------- Previous post was at 18:48 ----------

A HUGE THANK YOU to [MENTION=2888538]letmedanz[/MENTION] who will be taking over the thread....due to my work commitments it's been very hard for me to keep up....

You all know his approach and quality.....enough said.....

Rest assured the rest of the group are very much active behind the scenes.....

1+1 Ultra~Slim
[Android Builders Collective] ezio84:
After an headache due to some code differences and a record permission in the dialer manifest i was missing, here's the ported CM call recording feature :D

https://github.com/ezio84/packages_apps_Dialer/commit/d4c3786d320a33e4575a0e72b426a62c0eeb17c4

https://github.com/ezio84/packages_apps_InCallUI/commit/d03d2b4266ee1bacf01e7ee623b4bd370411f7ae

https://github.com/ezio84/packages_services_Telecomm/commit/9398cb8dd8e0a54aca2c284d59d589b21d48e7ac

https://github.com/ezio84/packages_...mmit/59c2aed6fb0b09ad37c8769fa692310d3255c70f

https://github.com/ezio84/frameworks_base/commit/7399e458a006a1ae99b42e6d4713e863a89e31f1

EDIT 27 MAr 2015: fix commit for the Dialer: https://github.com/ezio84/packages_...mmit/90970c5043a8c6acfa8fbebcc3c10e8b6aef5c84

In the dialer settings, under the call settings menu, you can set the audio format. During a call, tap on the three dots at the top right to start or stop the recording. In the dialer history expand a call entry, tap on Details and there you can play the recording. The files are stored under /sdcard/CallRecordings.
[Android Builders Collective] paradoxiumwind:
I ended up wiping my phone and doing a clean install with one of ezios latest builds and now the middle soft button works, so there's that. whenever I try to flash the latest franco kernel or elemental x kernel though, it says the phone service has stopped over and over after bootup, how come they don't work with it?
[Android Builders Collective] bobby janow:
Is there a way you could make a zip of the aosp dialer so that it would replace the google one in roms that insist on using stock google? Replacing it with the apk does not work. If it's not possible it will save me much time searching.
[Android Builders Collective] puldag:
Have the same issue with [MENTION=5131448]reS28raM[/MENTION] custom Slim ROM. I decided to not flash any custom kernels.
[Android Builders Collective] ezio84:
When you flash custom kernels, ensure they are not for CM based roms only.

Code blue and AK should be fine for example (@hooliganx is trying some of them).

A zip would overwrite the apk as you did it manually, and set the correct permissions (rw-, r--, r--).

The problem is also that some features are handled not only by the dialer apk, like you can see in those call recorder commits: the code is in the framework and other telephony services.
[Android Builders Collective] Jax Teller:
Latest Franco and ElementalX kernel are for 5.1, not 5.0.2.

Maybe that's a reason for your problem.
[Android Builders Collective] SteveMurphy:
[MENTION=264345]ralpheboyo[/MENTION], absolutely best wishes to you. None of us would be lurking/building/flashing these custom Slim flavors without your thread. So once again thank you!

[MENTION=2888538]letmedanz[/MENTION], so thankful for you agreeing to keep the shop open!
[Android Builders Collective] Soufiansky:
Can't wait for SlimRoms :p
[Android Builders Collective] DroidIt!:
Helllooo [MENTION=2095315]ezio84[/MENTION] and [MENTION=2888538]letmedanz[/MENTION]...so, did some flashing today and both of your builds are running good. No problems at all that I can see on either build :)
[Android Builders Collective] ralpheboyo:
....When we have such great people in the thread / community....such great builders....and such positivity.... it's simply a joy ( and till this day....the first thing I do when I switch on the pc is check the thread....and guess what the last thing I do before pc shut down.....;).....so from my perspective.......I for one am so grateful and thankful....!!!!...

1+1 Ultra~Slim
[Android Builders Collective] theesotericone:
Well said. It's a great little community here. I can't remember a single instance of a Mod coming in to clean this thread. Which is rare when I'm involved.:D
[Android Builders Collective] sykopompos:
Oh, we can change that.... ?
[Android Builders Collective] bobby janow:
You can say that again.
[Android Builders Collective] letmedanz:
Thanks for the cool intro [MENTION=264345]ralpheboyo[/MENTION] ;)

It's only a different name at the top of the thread.

What started off as just a general discussion on the seriously awesome Slim Hammerhead thread, evolved into this fantastic community.

We learned a lot from that thread & the awesome members of the Slim Team, who guided us through the very basics of everything Slim, Android, Linux etc :D

The joy of having been able to get our builds was too good to keep to ourselves & we decided to start a thread based purely on sharing knowledge, to help anyone to any extent that they wanted.

And of course, to have a cool hangout as well ;)

Pretty quickly, we had some big names & power hitters join in and were very open to sharing what they already knew.

We never expected this to be a runaway hit as it has turned out to be & we are all extremely grateful to everyone who has ever participated in this thread, in a small or big way to keep the spirit going.

This was one of the main differentiators we wanted here in comparison to almost all the other threads on XDA.

Many of us have become great friends & we probably spend more time talking to each other every day more than we would with the 'offline' family.. lol

Just so you know we have some fantastic chefs in case you want some exotic recipes & some masters at auto repairs amongst other specialties.. haha ..

At the heart of this thread in the very start were [MENTION=2640853]Garrykd[/MENTION], [MENTION=264345]ralpheboyo[/MENTION], [MENTION=2095315]ezio84[/MENTION], [MENTION=842211]Grondinm[/MENTION] and yours truly. We miss you Marc

Of course now there are many of you who keep this thread engaged & share some awesome stuff which is just brilliant.

A special shout out to our super friendly neighborhood mod [MENTION=4775688]GermainZ[/MENTION] for being ever so patient & helpful with any help we needed.

Thanks to everyone once again. Hope you all learn and share & keep this thread enjoyable for eternity ;)
[Android Builders Collective] puldag:
ElementalX 2.10 was working flawlessly since latest slim custom updates. So I don't think it's kernel fault. Or maybe it is, but not that being CM based. But I am very surprised, that AK is on hammerhead. I remember him on Galaxy Nexus, than he bought one+1.. Thanks for advice.
[Android Builders Collective] Mikulec:
The mods dont have guts to come to our "territory". :p

---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------

@DroidIt! where is your picture for today? So that [MENTION=2095315]ezio84[/MENTION] can make a new build for us. :angel:
[Android Builders Collective] angelcalibur:
SlimUberLP New release:

24/03/2015 :

-update with last slim source (nothing really merge for the moment)

-change name release

-build rom with last uber toolchain source 3-22-15

-build stock kernel with last uber toolchain source 3-22-15

i have issus when i want to add the kernel (flash failed) but i will find the solution.

here is the link :

Slim-jfltexx-5.0.2.UberLP.Alpha.1.0-UNOFFICIAL-20150324-1424.zip
[Android Builders Collective] expiredd:
Dear devs,

[MENTION=1228651]fusionjack[/MENTION],

I'm trying to custom build SlimSaber with AK kernel as kernel. However I'm a bit lost.

First of all should I modify

.repo/manifests/default.xml

or

platform_manifest/default.xml

Then to build rom with custom kernel should I remove the following manifest lines:

<project path="external/kernel-headers" name="platform/external/kernel-headers" groups="pdk-cw-fs" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" groups="pdk" clone-depth="1" />

And add:

<project name="anarkia1976/AK-OnePone" path="kernel/oneplus/msm8974" remote="github" revision="cm-12.0-skull-evo-official" />

or

<project name="anarkia1976/AK-OnePone" path="kernel/oneplus/ak_kernel" remote="github" revision="cm-12.0-skull-evo-official" />

If this is correct what's the next config to modify to setup kernel is picked from "kernel/oneplus/ak_kernel" directory.
[Android Builders Collective] letmedanz:
As far as possible, do not make changes to the default manifest.

Always the local_manifest or slim_manifest in the local manifests folder.

There is tutorial i've written for building with custom kernels.

Should be on page 2 of this thread
[Android Builders Collective] paradoxiumwind:
well that seems to be true for franco but elementalx has "Android 5.0.1/5.0.2 (Lollipop): ElementalX-N5-2.10" which is the one I tried and got the same error messages.
[Android Builders Collective] TaRsY:
If I intit the slim repo and starty my first sync does it only download the non device specific parts of the code? I opened the manifest.xml but no device project found.

This means there's no local manifest file, I have to create one for myself?

If so, based on [MENTION=2095315]ezio84[/MENTION]'s local_manifest I can do it for the d802 including the repos I forked to cherry-pick the commits later.

Am I doing right or I miss something? You are talking about editing slim_manifest but no local manifest folder here.

https://github.com/TaRsY?tab=repositories
[Android Builders Collective] expiredd:
I'm following your updated guide for on post #1447,

I've created local_manifests (dir didn't exist) in in .repo dir and added local_manifest.xml file with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="anarkia1976/AK-OnePone" path="kernel/oneplus/ak" remote="github" revision="cm-12.0-skull-evo-official" />
</manifest>

However I'm trying to find which is the correct BoardConfig.mk to edit:

find . -name "Board*"
./device/generic/mini-emulator-x86_64/BoardConfig.mk
./device/generic/mini-emulator-x86/BoardConfig.mk
./device/generic/x86/BoardConfig.mk
./device/generic/x86_64/BoardConfig.mk
./device/generic/arm64/BoardConfig.mk
./device/generic/mips/BoardConfig.mk
./device/generic/mini-emulator-armv7-a-neon/BoardConfig.mk
./device/generic/armv7-a-neon/BoardConfig.mk
./device/generic/mini-emulator-arm64/BoardConfig.mk
./device/generic/mini-emulator-mips/BoardConfig.mk
./build/tools/device/BoardConfig.mk.template
./build/target/board/generic_x86_64/BoardConfig.mk
./build/target/board/generic/BoardConfig.mk
./build/target/board/generic_arm64/BoardConfig.mk
./build/target/board/generic_x86/BoardConfig.mk
./build/target/board/generic_armv5/BoardConfig.mk
./build/target/board/generic_mips64/BoardConfig.mk
./build/target/board/generic_mips/BoardConfig.mk
./hardware/qcom/msm8x26/BoardConfigCommon.mk
./hardware/qcom/msm8x84/BoardConfigCommon.mk
./hardware/qcom/msm8x74/BoardConfigCommon.mk

I got totally lost (excuse me, it's first time for me doing this). I don't know which device is [MENTION=1228651]fusionjack[/MENTION] using in his ROM, maybe I'm misunderstanding something.

However I found this:

grep -r "BOARD_KERNEL_IMAGE_NAME" *
build/core/tasks/kernel.mk:ifneq ($(BOARD_KERNEL_IMAGE_NAME),)
build/core/tasks/kernel.mk:	TARGET_PREBUILT_INT_KERNEL_TYPE := $(BOARD_KERNEL_IMAGE_NAME)
build/core/tasks/kernel.mk:ifeq ($(BOARD_KERNEL_IMAGE_NAME),)
build/core/tasks/kernel.mk: $(error "Please set BOARD_KERNEL_IMAGE_NAME to uImage")
build/core/tasks/kernel.mk: $(error "Please set BOARD_KERNEL_IMAGE_NAME to Image")
[Android Builders Collective] kagwind:
None of the above. You should edit the file in the specific device folder.

Something like this.

In your case you might need to edit the source as well.

Local manifest is supposed to be created for yourself. A guide can be read here.

I think you also need proprietary files. Check post #18.
[Android Builders Collective] expiredd:
Yeah I had to start ROM compilation once to get the "bacon" device folder fetched and created.
[MENTION=3685904]ak[/MENTION] kernel directory got also cloned but I don't know which is the default kernel config.

I can't find toolchains in ROM/kernel directory structure. Both are by default compiled with Uber toolchain now, however I think it should be good to compile both with the exact same toolchain.
[Android Builders Collective] kagwind:
Check arch/arm/configs/ under the kernel diretory.
[Android Builders Collective] paradoxiumwind:
Hopefully this is appropriate enough for here, but what full stock google GApps are people using with ezio's LP 5.0.2 builds? I was using PA Gapps up until now but they seem to have stopped doing it, is there an alternative that is just as up to date with a full google apps install like the PA one?

Thanks,

para
[Android Builders Collective] hooliganx:
http://xdaforums.com/showthread.php?t=2792842

[GAPPS][5.0/4.4] Official Slim GApps & Custom GApps

n5slim.ezio84-15.03.21layeredgapps.15.03.17

code.blue.r884rd.1.16v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Android Builders Collective] gladi8r:
http://xdaforums.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

:D:good:
[Android Builders Collective] ralpheboyo:
Am really wondering ....if we were to make a video on how to setup and build your own gapps from DK's Git/Source....how many would do it....I keep saying this....I cannot believe such a low number do build their own gapps....incomprehensible ...standard gapps build takes less than 45 secs....

1+1 Ultra~Slim
[Android Builders Collective] theesotericone:
You can define the kernel source, deconfig, and toolchain in device/"your device maker"/"your device name"/BoardConfig.mk.

So for my N5 it's device/lge/hammerhead/BoardConfig.mk

I have two kernels I build with. The stock Slim kernel and Elemental. I just comment out the lines for whatever one I'm not using for the build. Thanks to [MENTION=5497766]aow1980[/MENTION] for clearing that up for me a month or so back.:cool:

TARGET_KERNEL_SOURCE := kernel/lge/ElementalX
TARGET_KERNEL_CONFIG := elementalx_defconfig
TARGET_KERNEL_CUSTON_TOOLCHAIN := arm-cortex_a15-linux-gnueabihf-linaro_4.9.1-2014.07
#TARGET_KERNEL_SOURCE := kernel/lge/hammerhead
#TARGET_KERNEL_CONFIG := slim_hammerhead_defconfig
#TARGET_KERNEL_CUSTON_TOOLCHAIN := UberTC_arm-eabi-4.9-master
[Android Builders Collective] hooliganx:
I don't know how to build [emoji15] [emoji37]

but, if I learn... and if is easy... I can learn.

I use Mac. this is a problem? [emoji85]

n5slim.ezio84-15.03.21layeredgapps.15.03.17

code.blue.r884rd.1.16v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------