yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] theesotericone:
There's a few guides here on XDA to set up the build environment for Mac. I'm sure someone here uses one to build so maybe they'll step up and help if you hit any snags. For now just get your build environment set up and sync Slim. Once that's done most of us can help with build specific errors as we've all had more than a few. Check posts 17 and 18 for getting loonybin set up in local_manifest after you lunch your device. It's really not as hard as people think. It's just a bunch of technical jargon you have to learn more than anything else.:cool:
[Android Builders Collective] ezio84:
You are right: after the repo init and the first sync, git won't download any local manifest, but only the default one (without any device specific repo).

The slim manifest is created automatically when you build for your device the first time, git downloads kernel and device specific folders during that step.

Or you can put those kernel and device lines in a new personal local manifest (like I did in mine) before you build the first time, there's no difference.

The loony bin repos aren't set by git instead, so you have to put them manually in the manifest.

It's really easy :D

http://xdaforums.com/showpost.php?p=58125974&postcount=2680

But I don't know if it's the same with a Mac without Linux.
[Android Builders Collective] paradoxiumwind:
anyone know why that kernel won't work with ezios 5.0.2 latest? (phone service stopped or something errors after bootup until phone reboots). Clean install / entire phone wipe install too
[Android Builders Collective] hooliganx:
ok guys. thanks.

now Im on a hard mission in family...

I'll be a father!!! ? ? ?

tomorrow we'll known if is a boy or a girl.

but... is a magical days. [emoji7]

my wife is very happy and inconsistent too. [emoji15]

but Im very happy and patience. [emoji6]

thanks all!

everyone in Slim Team and here in Collective Family!

will start read about gapps... Im a Brazilian boy and my English was learned with.. my self. [emoji16]

thanks! [emoji4][emoji111]

n5slim.ezio84-15.03.21layeredgapps.15.03.17

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

-----------------------------------------------------------
[Android Builders Collective] adl:
Wow! Congratulations. Hope everything is going fine.

Wish you and your family (yes!, it´s FAMILY now :D ) all the best!! :fingers-crossed:
[Android Builders Collective] ezio84:
If you have time try to flash it again and report back the complete error message, it could be easier to help you.

Niiiiiiiiiiiiice!!!!! :D:D:D:D:highfive:

So here we build roms and children too!!! :D :D

Congrats and best wishes to you and your family :highfive:
[Android Builders Collective] DroidIt!:
So if it's a boy will it be hooliganx jr? :p Seriously, congradulations, you get a new addition to the family and I get my 3rd N6 today which is aalmost as big as having a kid :D
[Android Builders Collective] yaatzek:
Congrats [MENTION=992878]hooliganx[/MENTION] ! Looks like instead of slim builds we have some family builds cooking :) my second build is on the way too here :)

This is much easier than compiling a rom ;)
[Android Builders Collective] TaRsY:
Thanks for the answer but with the help from kagwind I was able to make the local manifest, and synced well (after fixing a typo in it [emoji14]) . When I tried building I faced java problem, but succesfully eliminated the error. After that I tried te build again but after a while it gave me another error but I left home, cannot look after. It was something with out/host/linux-x86/bin/dtbtoolcm.

Tomorrow evening I'll try to figure out.
[Android Builders Collective] flushell:
Building for HTC One M8, but still some errors. Maybe someone can help with my problem.

My slim_manifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheLoonyBin/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="lp5.0" />
<project name="SlimRoms/device_htc_m8" path="device/htc/m8" remote="github" revision="lp5.0" />
<project name="SlimRoms/kernel_htc_msm8974" path="kernel/htc/msm8974" remote="github" revision="lp5.0" />
<project name="SlimRoms/device_qcom_common" path="device/qcom/common" remote="github" revision="lp5.0" />
<project name="SlimRoms/device_qcom_sepolicy" path="device/qcom/sepolicy" remote="github" revision="lp5.0" />
</manifest>

Error after some 15 minutes of compiling:

device/qcom/common/power/power.c: In function 'power_hint':
device/qcom/common/power/power.c:272:14: error: 'POWER_HINT_CPU_BOOST' undeclared (first use in this function)
case POWER_HINT_CPU_BOOST:
^
device/qcom/common/power/power.c:272:14: note: each undeclared identifier is reported only once for each function it appears in
device/qcom/common/power/power.c:273:14: error: 'POWER_HINT_SET_PROFILE' undeclared (first use in this function)
case POWER_HINT_SET_PROFILE:
^
device/qcom/common/power/power.c:282:14: error: 'POWER_HINT_AUDIO' undeclared (first use in this function)
case POWER_HINT_AUDIO:
^
build/core/binary.mk:697: recipe for target '/home/woftor/slimroms/out/target/product/m8/obj/SHARED_LIBRARIES/power.msm8974_intermediates/power.o' failed
make: *** [/home/woftor/slimroms/out/target/product/m8/obj/SHARED_LIBRARIES/power.msm8974_intermediates/power.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
[Android Builders Collective] ralpheboyo:
Congrats bro....!!!!! Children are the best gift in life!!!!

I have asked you so many times bro....join the group....even if it's just to chillax...no building required....and if you do end up building...another bonus....each team member I am 100% will help

1+1 Ultra~Slim
[Android Builders Collective] Rauch:
Of certainly be interested in learning. Let's me customize it a bit more, and remove some extras I don't like. Go for it!
[Android Builders Collective] hooliganx:
mannn!!!

have no words to describe how grateful I am to have met you all.

very very happy!

hope all other slim guys and slim collectives [emoji16] are fine in your real lifes.

miss [MENTION=4790322]kufikugel[/MENTION], [MENTION=5047159]Tylog[/MENTION], [MENTION=5131448]reS28raM[/MENTION] and many other.

happy moments. happy threads. good people.

[emoji8][emoji106]

n5slim.ezio84-15.03.21layeredgapps.15.03.17

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

-----------------------------------------------------------
[Android Builders Collective] Jax Teller:
Congrats my friend.

These are the best news anyone can hear.

We will make a group to learn how to change diapers. lol

---------- Post added at 10:29 PM ---------- Previous post was at 10:28 PM ----------

What is that group?[emoji4]
[Android Builders Collective] theesotericone:
It's pretty much a cooking/auto repair group that happens to build some ROMs on the side. lol PM [MENTION=264345]ralpheboyo[/MENTION] your gmail and I'll bet you get an invite.:cool:
[Android Builders Collective] ed33:
Hi ezio84 and others.

Is anyone else losing the function of thier power button? I clean flashed today and ive just lost function of power button again, lowering the volume to the lowest and back to highest volume restores the function of the power button.
[Android Builders Collective] Jax Teller:
Yeah, I know it.

I'm just teasing him to invite me. lol
[Android Builders Collective] expiredd:
I've tried to clone Uber toolchain repo from https://github.com/UBERTC but I'm getting 404 errors on init and sync.
[Android Builders Collective] theesotericone:
Unless you want to actually compile the toolchain there's no need for that. Read the header under Uber Toolchains in your link. Go to bitbucket and add the toolchains you want to use in your local manifest. I actually use these because [MENTION=5497766]aow1980[/MENTION] had the prebuilts up before Chet got them on bitbucket. I'm lazy but I'll change them up eventually. So use this as a template. Then just call the kernel toolchain in boardconfig and the ROM toolchain if you want to use that to in build/core/combo/TARGET_linux-arm.mk. Lines 56 and 57 should be what you need to change.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project name="aow1980/UberTC_arm-linux-androideabi-4.8" path="prebuilt/linux-x86/toolchain/UberTC_arm-linux-androideabi-4.8" remote="github" revision="master" />
<project name="aow1980/UberTC_arm-eabi-4.9" path="prebuilt/linux-x86/toolchain/UberTC_arm-eabi-4.9" remote="github" revision="master" />
<project name="flar2/ElementalX-N5" path="kernel/lge/ElementalX" remote="github" revision="ElementalX-2.00" />
<project name="Cl3Kener/UBER-L" path="kernel/lge/Uber-L" remote="github" revision="master" />

</manifest>
[Android Builders Collective] Juzman:
[MENTION=2033478]Yank555[/MENTION] With your latest build (Slim-hammerhead-5.0.2.alpha.1.0-UNOFFICIAL-20150320-1622) does Proximity Speaker work for you?

I know that it was in stock SlimLP builds, and worked on your previous build. I've done a clean flash (full wipe), and flashed latest build of yours however proximity speaker still isn't working. :/
[Android Builders Collective] endomatic:
Did you look in the phone app in settings?
[Android Builders Collective] Juzman:
FML. I checked *all* settings and missed that one!

I was going crazy, I *knew* it was there, just must have overlooked it. -.-

Need coffee.
[Android Builders Collective] RobbieL811:
Hey E. I added this to Slim. I didn't publish it b/c I was worried about legal stuff. When I tested it though, the only thing that got recorded was my voice unless I put the phone on speakerphone. Did you run into this?
[Android Builders Collective] theesotericone:
I'm pretty sure your OK with the legal aspect. It's what the user does with it that could have legal repercussions. But I for one would love to let ATT customer service know that I'm also recording the call.:cool:
[Android Builders Collective] DroidIt!:
Trust me, proximity speaker works on ALL [MENTION=2033478]Yank555[/MENTION] builds...well, N5 and N6 :)
[Android Builders Collective] RobbieL811:
Lol. I thought that was why CM removed it. B/c of legal stuff. Let's see if Ezio's port has the same problem as mine. I may possibly add it to my builds.
[Android Builders Collective] DroidIt!:
Ups...missed that one [emoji15] [emoji56]

---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------

Hiya Robbie...sooo, come here often? :)
[Android Builders Collective] randman2011:
Cooking, auto repair, and Android development! Sounds like my life!

---------- Post added at 10:33 PM ---------- Previous post was at 10:30 PM ----------

I'm curious exactly what you mean. My power button has been going out for a few weeks now and I just assumed it was hardware failure. Its sensitivity is incredibly low and I have to push it from the top down pretty hard to get it to register.
[Android Builders Collective] Juzman:
Haha.

Yeah I checked it about 4 times. I swear it wasn't there before. :p
[Android Builders Collective] ed33:
It's not hardware, next time yours does it try lowering and raising the volume from min to Max and see if the power button works again.
[Android Builders Collective] RobbieL811:
Every now and then. I check up on the thread.
[Android Builders Collective] ezio84:
I don't have to use that qcom repo with my nexus so i don't know it well, btw if you check the history on the slim github there are some CM commits like this one:

https://github.com/SlimRoms/device_qcom_common/commit/b4a5257c0ebf0b60fb33a2e744e0341b5a86d13a

It adds CM power profiles, but Slim doesn't have them for any device as far as i know. Power profiles are set through the framework and maybe other system components, for example:

http://review.cyanogenmod.org/#/c/64254/

That's why the build process errors out with undeclared functions like POWER_HINT_SET_PROFILE', they are missing in the frameworks_base code.

So, i think that the Slim qcom repo shouldn't have those commits. Try to revert at least these commits before building:

https://github.com/SlimRoms/device_qcom_common/commit/b4a5257c0ebf0b60fb33a2e744e0341b5a86d13a

https://github.com/SlimRoms/device_qcom_common/commit/93c69c0e9ef94cd203f5411e9289d67851e7ab91

https://github.com/SlimRoms/device_qcom_common/commit/179477c9ed64fcf8de70015d6023f91498b0d508

Or wait for someone else with more knowledge about this stuff, maybe [MENTION=4911350]RobbieL811[/MENTION] could help you better.

I don't have power button problems so can't help a lot.

But, if it's not an hardware issue, try to take a logcat while the power button isn't working. Ensure also it's not a kernel related problem if you're using an alternative one. And don't use xposed.

No legal problems, because i squashed into those commits this one too:

http://review.cyanogenmod.org/#/c/90224/

It adds a built-in blacklist for all countries where the call recording feature can't be used and automatically disable the feature ;)

And yes, to record the interlocutor's voice you need to enable the speakerphone, it works like in Kitkat times. It's an intended (constrained) behavior.
[Android Builders Collective] kantjer:
The ROM and kernel TC used when building SlimSaber is stored in "prebuilts/gcc/linux-x86/arm"

---------- Post added at 09:26 AM ---------- Previous post was at 09:22 AM ----------

No need to do that, it's already synced using the SlimSaber manifest (see my previous post for its location)
[Android Builders Collective] RobbieL811:
Yeah. I removed the block that they put on it for certain countries. I am in the US and I wanted it to work for me lol. I was j/w about the speakerphone thing. I wonder why they did that? Also, I didn't understand the other question about device_qcom_common.
[Android Builders Collective] ezio84:
Here's a (maybe) updated list about USA countries: http://lifehacker.com/5491190/is-it-legal-to-record-phone-calls

About the speakerphone, could it be an hardware limitation?
[Android Builders Collective] expiredd:
I guess then this should work:

# Kernel
BOARD_KERNEL_IMAGE_NAME := zImage-dtb
TARGET_KERNEL_SOURCE := kernel/oneplus/ak
TARGET_KERNEL_CONFIG := kernel/oneplus/ak/arch/arm/Kconfig
TARGET_KERNEL_CUSTON_TOOLCHAIN := arm-linux-androideabi-4.8
#BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1
ENABLE_GRAPHITE := true

Got this error:

make[3]: *** No rule to make target `kernel/oneplus/ak/arch/arm/Kconfig'. Stop.
make[2]: *** [kernel/oneplus/ak/arch/arm/Kconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/gmarco/android/slimsaber/kernel/oneplus/ak'
make: *** [/home/gmarco/android/slimsaber/out/target/product/bacon/obj/KERNEL_OBJ/.config] Error 2
[Android Builders Collective] kagwind:
May I ask what do you get if you run 'adb shell getprop persist.call_recording.src' ?

This does not seem right, should look like

TARGET_KERNEL_CONFIG := slim_hammerhead_defconfig

As I said, check kernel/oneplus/ak/arch/arm/configs for the file name.
[Android Builders Collective] kagwind:
I'm not sure whether it works, but you should try to set persist.call_recording.src to 4 and reboot.

Edit: I just found out this feature needs to be supported by devices, otherwise you could end up like ezio84 :p

IF YOU SOMEHOW BREAK THE LAW, IT IS NOT MY FAULT. :p
[Android Builders Collective] dcro95:
Hi everyone, I would to try to compile SlimRom. Do you have some links to simple howto ?

I plan to use a laptop with Debian.

Thanks.
[Android Builders Collective] Mikulec:
[MENTION=2095315]ezio84[/MENTION] I just noticed that after flashing your latest build from 23rd Google Fit stopped tracking my activity. Could it be because of that changes in google services you made?
[Android Builders Collective] ezio84:
Tried now, after adding that line in the build.prop i can't record the call (on mako) :p

Post 17-18-19

I don't know, [MENTION=1277872]dankoman[/MENTION] is the guy we must ask about this stuff :D
[Android Builders Collective] expiredd:
Indeed corrected my BoardConfig.mk to:

# Kernel
BOARD_KERNEL_IMAGE_NAME := zImage-dtb
TARGET_KERNEL_SOURCE := kernel/oneplus/ak
TARGET_KERNEL_CONFIG := ak_bacon_defconfig
TARGET_KERNEL_CUSTON_TOOLCHAIN := arm-linux-androideabi-4.8
ENABLE_GRAPHITE := true

Seems to be working now, gonna backup and flash it to check if kernel was built correctly into ROM :good:

Thank you all [MENTION=3306843]kantjer[/MENTION] [MENTION=3685904]ak[/MENTION] [MENTION=1228651]fusionjack[/MENTION] [MENTION=6048392]kagwind[/MENTION] [MENTION=2888538]letmedanz[/MENTION] [MENTION=5451511]theesotericone[/MENTION] [MENTION=2095315]ezio84[/MENTION] :highfive: :highfive:

Copying files...
Generating Makefiles...
Done!
Running finisher...

( (
)\ ) ( )\ ) )
(()/( )\( ) (()/( ) ( /( ( (
/(_)|(_)\ ( /(_))( /( )\()) ))\ )(
(_)) _((_) )\ '(_)) )(_)|(_)\ /((_|()\
/ __|| |(_)_((_)) / __|((_)_| |(_)(_)) ((_)
\__ \| || | ' \()\__ \/ _' | '_ \/ -_)| '_|
|___/|_||_|_|_|_| |___/\__,_|_.__/\___||_|

===========-Package complete-===========
zip : /home/gmarco/android/slimsaber/out/target/product/bacon/SlimSaber-bacon-5.0.2-20150326.zip
md5 : 0562334c791397613d5c2d2602e7993b
size: 214M
========================================
Total time elapsed: 15 minutes (909.705775053 seconds)
[Android Builders Collective] RobbieL811:
Ah! So it is illegal in some states. With the nexus, you don't have to put it on speakerphone to record the call? I have to or else all I will hear is myself.
[Android Builders Collective] ezio84:
Yes i have to put it on, it only records from your device microphone.

If you set AAC as audio format, the quality is quite good ;D
[Android Builders Collective] RobbieL811:
Ok. Thanks. I guess that this is probably the intended behavior. Like you said, there probably is hardware restrictions. There probably is no mic within the ear piece speaker.
[Android Builders Collective] pSyCh¤_O_O:
[MENTION=992878]hooliganx[/MENTION]

Congratulations!!![emoji323] [emoji323] [emoji322] [emoji322] [emoji322] [emoji64]

Get some rest while you still can [emoji12]

Wish you and your familly all the best bro...[emoji6]

Take care
[Android Builders Collective] expiredd:
Ok, flashed with no problems. But getting 1+ Android screen. Device not booting up. Any ideas? :crying:
[Android Builders Collective] Mikulec:
Looks like it was just a derp on the apps side, it started to work. :eek::silly:
[Android Builders Collective] kantjer:
I was planning on building SlimSaber with AK, this is a good reason to try.

Just started my first attempt. I will keep you updated.
[Android Builders Collective] expiredd:
Check my last post. ROM was built and I could flash it. However I got stuck into boot (1+ Android black and white screen).

I restored my backup while I figure how to fix it. I've no idea hehe :p
[Android Builders Collective] kantjer:
Flashing official ak.zip after failed boot would most likely also saved you
[Android Builders Collective] TJKV:
It isn't a hardware restriction really, as I have an app that does call recording (on your latest build for hh) of both parties without speakerphone. I'll send you the link to the app when I'm on the computer. It is from xda, also on play store as a paid app. Only thing is the app needs to set the kernel to permissive. If I were to guess, selinux fiddling will be required to get access to incoming voice stream. I used the app for a few days but uninstalled as I didn't want to be permissive. If you get the inbuilt recording working perfectly then I too will be very happy :p
[Android Builders Collective] ezio84:
*** SlimLP 1.0jUBERTC mod for

mako & hammerhead

***

:D

Download:

https://androidfilehost.com/?w=profile&uid=23578570567714195

(links on the right)

Changelog:

- CM Eleven, AudioFX and Terminal source sync

- Slim source sync

- UberTC source sync

- CM incall recorder:

(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.

Enable the speakerphone to record the interlocutor's voice too).

- Add prebuilt AdAway (latest xda version) (thanks [MENTION=2888538]letmedanz[/MENTION])

- New System Tools menu under Settings (SuperSu, AdAway, SlimCenter) (thanks [MENTION=2872010]rootSU[/MENTION] for the icons base)

Tips of the day:

The call recording feature couldn't be available in your country due to law restrictions. If you are sure that recording a call is permitted in your country but the feature is disabled by mistake, try to create a layer (overlay) that overwrite the "false" value (set to "true") in the res/values-mccXXX/config.xml files in the Dialer apk (<bool name="call_recording_enabled">true</bool>).

It must also overwrite the "false" value in the res/values/config.xml file (<bool name="call_recording_enabled">true</bool>).

Then load the overlay with the layers app and reboot.

I haven't tried it so i don't know if this is a working trick.

Other infos and links in the 6th post.

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] TJKV:
Okay found the link on my phone itself, here it is:

http://xdaforums.com/showthread.php?t=1441643

The op warns of distortions on hh but I got crystal clear recordings :)
[Android Builders Collective] expiredd:
That's another workaround.

I guess there's something with AK kernel compiling setup. I've really no knowledge. Dunno if someone could help us.
[Android Builders Collective] ezio84:
About the call recorder countries restriction: if you are sure that recording a call is permitted in your country but the feature is disabled by mistake, try to create a layer (overlay) that overwrite the "false" value (set to "true") in the res/values-mccXXX/config.xml files in the Dialer apk (<bool name="call_recording_enabled">true</bool>).

It must also overwrite the "false" value in the res/values/bools.xml file (<bool name="call_recording_enabled">true</bool>).

Then load the overlay with the layers app and reboot.

I haven't tried it so i don't know if this is a working trick.
[Android Builders Collective] Konsumhaus:
Does anyone know, why I can't get access to the Hotel Wlan Network where I am atm?

I'm on ezio84's latest Build.
[Android Builders Collective] kantjer:
Build is done and booted fine.

added this to my local_manifest.xml

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

And this is in my BoardConfig.mk

# Kernel
TARGET_KERNEL_SOURCE := kernel/oneplus/ak_kernel
TARGET_KERNEL_CONFIG := ak_bacon_defconfig
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1

Rest is all stock
[Android Builders Collective] expiredd:
Awesome ! building right nao!
[Android Builders Collective] angelcalibur:
New build again :

Now, you have the choice :

Build :

With Alucard Kernel build with Uber Toolchain :

Slim-jfltexx-5.0.2.UberLP.Alpha.1.0-Alucard.zip

With stock (CM) kernel build with Uber Toolchain:

Slim-jfltexx-5.0.2.UberLP.Alpha.1.0-UNOFFICIAL-20150324-1424.zip

Personaly, i choose Alucard kernel, a awesome kernel for good performance and batterie life!

This build (rom + kernel) was compile with the last uber toolchain 4.8 (rom) and 4.9(kernel).

if you have issu, send me the message here! ;)
[Android Builders Collective] kagwind:
Deleting that file should also work, I think.

Saw this on the main thread.
[Android Builders Collective] chikimonke:
Thanks man!

Look [MENTION=5180758]Natakranta[/MENTION] a thread I missed!
[Android Builders Collective] expiredd:
Compiled and booted for me but when I go to system info I see kernel is SlimKernel and not AK. Could you check yours?