yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] limjh16:
no... you use this while building your ROM... If you are end-user, this is of no use to you
[Android Software/Hacking General [Developers Only]] Ahmed-Iraq:
Ok, iwant also ask u can i change status bar icon from left to right coz when i select arabic language all icon change to left and i hate this thing

أرسلت من GT-I9300 بإستخدام تاباتلك
[Android Software/Hacking General [Developers Only]] limjh16:
And... How is that relevant to this thread? Please ask in your device's Q&A. I do not know what you are asking anyways, sorry
[Android Software/Hacking General [Developers Only]] desalesouche:
Hi sir any idea about MM version? even experimental? Thanks
[Android Software/Hacking General [Developers Only]] Ophidian_DarkCore:
mm stuff is on the cm-13.0 branch. cherry it all
[Android Software/Hacking General [Developers Only]] adriansticoid:
[MENTION=6586967]doesntexits[/MENTION] do you think it's beneficial for our device of you incluce these commits in our ROMs?
[Android Software/Hacking General [Developers Only]] doesntexits:
Oh yeah, they're optimized GCC flags for compiling

I'll try with it later
[Android Software/Hacking General [Developers Only]] Mohanadmohamedd:
Would this work with an S6 Running the Alexis ROM? :p
[Android Software/Hacking General [Developers Only]] pipyakas:
Do I have to cherry the v4.1 commit before all the mm commits?
[Android Software/Hacking General [Developers Only]] Ophidian_DarkCore:
if you looked at them, it would obviously conflict to all hell. so no of course not. dont.

https://github.com/ArchiDroid/android_build/commits/cm-13.0?page=2

git cherry-pick f25e437..3f7debf
[Android Software/Hacking General [Developers Only]] limjh16:
Hey all,

Before you flame me I know MM commits for this optimisation is here

However I want to optimise my kernel, like Archi did here and here. Is there a MM version of these optimisations for kernel? I would appreciate your help :)

Edit: Figured I should tell, that I tried applying those commits and changing it for my device, which worked back in LP but not now in MM. I have already tried cherry picking them and didn't work.
[Android Software/Hacking General [Developers Only]] neonkat:
i have used this with lp roms and it used to work perfectly but i want to use this with kernel only.

i am having only kernel source(mm).how can i use this when i only have kernel source?is that possible?i saw the mm commit but idk how it use it with kernel sources.
[Android Software/Hacking General [Developers Only]] INT3NSE07:
Waiting for these optimizations to become compatible with AOSP. Imagine the possibilities. :p
[Android Software/Hacking General [Developers Only]] Ophidian_DarkCore:
compatible or merged? these can be applied to aosp roms
[Android Software/Hacking General [Developers Only]] pipyakas:
[deleted]
[Android Software/Hacking General [Developers Only]] forid200:
Kinda wish Google decided optimise the backend themselves and include it in AOSP. Then we wouldn't need to apply these optimisations ourselves, and all Android users would have a better experience.
[Android Software/Hacking General [Developers Only]] PWn3R:
Hey Archi - I used your version of the CM13 optimizations, and I made a build today after merging them. For some reason, my build came out about half the size it should e (251.8MB instead of about 448ish). Any idea what might've happened? The build finishes, and I don't see any errors.
[Android Software/Hacking General [Developers Only]] PWn3R:
Did you ever figure this out? I'm having the same problem now.
[Android Software/Hacking General [Developers Only]] Lonelyskatter12:
No sadly , I decided to use another mod, until the dev fixes bluetooth
[Android Software/Hacking General [Developers Only]] mobiusm:
What do you use?
[Android Software/Hacking General [Developers Only]] PWn3R:
So neither of you have fixed this? [MENTION=5161352]JustArchi[/MENTION] - you have any thoughts here? I even got medieval and put -g in the cflags in that file and the main BT ones to try to fix.

Original flags changes were made in system/bt/core/Android.mk
[Android Software/Hacking General [Developers Only]] insestito:
work on marshmallow?¿
[Android Software/Hacking General [Developers Only]] PWn3R:
So - I'm not one to give up on a problem and I hope to fix this for the betterment of everyone who wants to use these optimizations.

I am STILL getting the Bluetooth Share has stopped non stop. I've tried putting -Os and -g as flags in EVERY BDROID_CFLAGS (that might not be exactly the variable, but the one that you update to fix this problem based on the fix in the OP) in EVERY file in the entire build directory. NO DICE.

Here's a tombstone dump file (sorry if that's not the right lingo, I'm not a pro dev here).

https://drive.google.com/open?id=0B6BaDxaggle2UkUwc2R1QmJJYlk

And this is the logcat of the crash on the device. I suspect this is the SAME problem that EVERYONE who's tried this and can't get it to work after changing the Bluetooth flags and then gave up. Can someone help us? :)

Logcat is this: ( I can post the whole logcat if you want)

--------- beginning of crash

07-07 13:27:41.217 12511 12511 F DEBUG :

07-07 13:27:41.217 12511 12511 F DEBUG : Tombstone written to: /data/tombstones/tombstone_05

07-07 13:27:44.679 13466 13493 F libc : Fatal signal 7 (SIGBUS), code 1, fault addr 0xac98f9be in tid 13493 (BT Service Call)

07-07 13:27:44.781 12511 12511 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

07-07 13:27:44.781 12511 12511 F DEBUG : CM Version: 'unknown'

07-07 13:27:44.781 12511 12511 F DEBUG : Build fingerprint: 'google/shamu/shamu:6.0.1/MOB30M/2862625:user/release-keys'

07-07 13:27:44.781 12511 12511 F DEBUG : Revision: '0'

07-07 13:27:44.781 12511 12511 F DEBUG : ABI: 'arm'

07-07 13:27:44.781 12511 12511 F DEBUG : pid: 13466, tid: 13493, name: BT Service Call >>> com.android.bluetooth <<<

07-07 13:27:44.781 12511 12511 F DEBUG : signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0xac98f9be

07-07 13:27:44.800 12511 12511 F DEBUG : r0 aeb98300 r1 00000005 r2 00000000 r3 b334b010

07-07 13:27:44.800 12511 12511 F DEBUG : r4 ac98f9ba r5 b36bed04 r6 00000005 r7 ac98f9ba

07-07 13:27:44.800 12511 12511 F DEBUG : r8 00000000 r9 aea7fd7c sl aea7fd78 fp 00000001

07-07 13:27:44.800 12511 12511 F DEBUG : ip fffff418 sp aea7fd40 lr b47e3637 pc b36948f4 cpsr 20000030

07-07 13:27:44.806 12511 12511 F DEBUG :

07-07 13:27:44.806 12511 12511 F DEBUG : backtrace:

07-07 13:27:44.806 12511 12511 F DEBUG : #00 pc 000048f4 /system/lib/libbluetooth_jni.so

07-07 13:27:44.807 12511 12511 F DEBUG : #01 pc 000066c9 /system/lib/libbluetooth_jni.so

07-07 13:27:44.807 12511 12511 F DEBUG : #02 pc 00043493 /system/lib/hw/bluetooth.default.so

07-07 13:27:44.807 12511 12511 F DEBUG : #03 pc 00042fa3 /system/lib/hw/bluetooth.default.so

07-07 13:27:44.807 12511 12511 F DEBUG : #04 pc 0012278d /system/lib/hw/bluetooth.default.so

07-07 13:27:44.807 12511 12511 F DEBUG : #05 pc 00121455 /system/lib/hw/bluetooth.default.so

07-07 13:27:44.807 12511 12511 F DEBUG : #06 pc 0012267d /system/lib/hw/bluetooth.default.so

07-07 13:27:44.807 12511 12511 F DEBUG : #07 pc 0005167d /system/lib/libc.so (_ZL15__pthread_startPv+32)

07-07 13:27:44.807 12511 12511 F DEBUG : #08 pc 00018721 /system/lib/libc.so (__start_thread+8)
[Android Software/Hacking General [Developers Only]] kogone:
This is from the BoardConfig of angler (nexus 6p)

TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_ABI := arm64-v8a
TARGET_CPU_ABI2 :=
TARGET_CPU_VARIANT := cortex-a53

TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv7-a-neon
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi
TARGET_2ND_CPU_VARIANT := cortex-a7

when i watch the rom being built with htop, i notice that the arm toolchains are being used at times.

however, when i build the kernel from source (not through mka bootimg), it's only necessary to export the location of an aarch64 kernel toolchain.

can someone explain this?
[Android Software/Hacking General [Developers Only]] faizauthar12:
This is my opinion

Even you're 64 bit

You also need to make 32 bit stuff ...

That's why arm toolchain will be used for 32 bit libs / files
[Android Software/Hacking General [Developers Only]] kogone:
So it must be ROM related and not for the kernel.
[Android Software/Hacking General [Developers Only]] bigsupersquid:
so when i added vynikal's squashed commit he pieced together for mm from justarchi's repo to my cm13 build, using uber 5.3 toolchains, i got the evil com.android.bt has stopped, Bluetooth share had stopped etc.

adding -Os to system/bt/Android.mk CFLAGS didn't solve it but i tracked my issue to packages/apps/Bluetooth/jni, added -Os to that directory's Android.mk CFLAGS as well, and now I'm good on BT.

testing it out, i needed the -Os in both those places together to make it work.

just fyi, maybe it'll help you and or others too since i hadn't seen reference to doing anything with the packages/apps/Bluetooth on my searching.

patches, specifically:

packages/apps/Bluetooth
commit d58f68c6f364eedc8771de1204d9a45073df2f82
Author: bigsupersquid <scrubbed>
Date: Sun Jul 10 20:49:52 2016 -0500

-Os jni

Change-Id: Iafb2af0773bc093633483403e6bda7680130cf43

diff --git a/jni/Android.mk b/jni/Android.mk
index 68ca6e7..d973978 100644
--- a/jni/Android.mk
+++ b/jni/Android.mk
@@ -33,6 +33,7 @@ LOCAL_SHARED_LIBRARIES := \
LOCAL_MULTILIB := 32

#LOCAL_CFLAGS += -O0 -g
+LOCAL_CFLAGS += -Os

LOCAL_MODULE := libbluetooth_jni
LOCAL_MODULE_TAGS := optional

system/bt
commit 604eeb7c5a84c0fc4e1ecdda368271bc122c2a51
Author: bigsupersquid <scrubbed>
Date: Sun Jul 10 20:51:08 2016 -0500

-Os

Change-Id: I9e4440b575c0b269dbb291ba0b34834a2a686e5c

diff --git a/Android.mk b/Android.mk
index b398132..dfdb788 100644
--- a/Android.mk
+++ b/Android.mk
@@ -38,7 +38,8 @@ bdroid_CFLAGS += \
-Wno-unused-parameter \
-Wunused-but-set-variable \
-UNDEBUG \
- -DLOG_NDEBUG=1
+ -DLOG_NDEBUG=1 \
+ -Os

include $(call all-subdir-makefiles)
[Android Software/Hacking General [Developers Only]] PWn3R:
Thanks for the information - I had tried doing everything with the bdroid flags or whatever it is in the system/bt directory. That didn't work. I've got a build running with your flag change on it right now. If it works I owe you several internets as do the rest of the people having this issue!

---------- Post added at 10:40 PM ---------- Previous post was at 09:50 PM ----------

Confirmed. Thank you!!!!!!
[Android Software/Hacking General [Developers Only]] DorianX:
Deleted...

Enviado desde mi Nexus 6P mediante Tapatalk
[Android Software/Hacking General [Developers Only]] evildog1:
all source code not found with 404 error.

ROM devs can't use your optimization
[Android Software/Hacking General [Developers Only]] sagarshah1729:
Bro sorry for quoting your old post..I am getting the same error as you are getting while booting.. Took logcat and got the same Audio system error..Can you help me fixing it?
[Android Software/Hacking General [Developers Only]] Mata99:
I have bootloop, can someone help me please?
[Android Software/Hacking General [Developers Only]] Mata99:
Can anyone put the link of ART fix please?
[Android Software/Hacking General [Developers Only]] puturaya20:
Link eror for cm 11

https://github.com/JustArchi/android_build/commit/1125f60a15194e08fdf18feacefb47696647e05b
[Android Software/Hacking General [Developers Only]] Mata99:
I have this problem

matteo@matteo-SATELLITE-U920T ~/mako/build $ git remote add 32 -f git@github.com:Vynikal/android_build.git && git cherry pick 6af9a30f748153bf9bcab533dbaa7c964113aff2
Aggiornamento di 32
Da github.com:Vynikal/android_build
* [nuovo branch] caf/cm-12.0 -> 32/caf/cm-12.0
* [nuovo branch] caf/cm-12.1 -> 32/caf/cm-12.1
* [nuovo branch] cm-10.1 -> 32/cm-10.1
* [nuovo branch] cm-10.2 -> 32/cm-10.2
* [nuovo branch] cm-11.0 -> 32/cm-11.0
* [nuovo branch] cm-12.0 -> 32/cm-12.0
* [nuovo branch] cm-12.1 -> 32/cm-12.1
* [nuovo branch] cm-13-flags -> 32/cm-13-flags
* [nuovo branch] cm-13.0 -> 32/cm-13.0
* [nuovo branch] cm-9.0.0 -> 32/cm-9.0.0
* [nuovo branch] cm-9.1.0 -> 32/cm-9.1.0
* [nuovo branch] donut -> 32/donut
* [nuovo branch] eclair -> 32/eclair
* [nuovo branch] froyo -> 32/froyo
* [nuovo branch] froyo-stable -> 32/froyo-stable
* [nuovo branch] gb-release-7.2 -> 32/gb-release-7.2
* [nuovo branch] gingerbread -> 32/gingerbread
* [nuovo branch] gingerbread-release -> 32/gingerbread-release
* [nuovo branch] ics -> 32/ics
* [nuovo branch] ics-release -> 32/ics-release
* [nuovo branch] jellybean -> 32/jellybean
* [nuovo branch] jellybean-release -> 32/jellybean-release
* [nuovo branch] jellybean-stable -> 32/jellybean-stable
* [nuovo branch] mr1.1-staging -> 32/mr1.1-staging
* [nuovo branch] qcril -> 32/qcril
* [nuovo branch] shipping/cm-11.0 -> 32/shipping/cm-11.0
* [nuovo branch] stable/cm-10.2 -> 32/stable/cm-10.2
* [nuovo branch] stable/cm-11.0 -> 32/stable/cm-11.0
* [nuovo branch] stable/cm-11.0-XNF8Y -> 32/stable/cm-11.0-XNF8Y
* [nuovo branch] stable/cm-11.0-XNF9X -> 32/stable/cm-11.0-XNF9X
* [nuovo branch] stable/cm-11.0-XNG2S -> 32/stable/cm-11.0-XNG2S
* [nuovo branch] stable/cm-11.0-XNG3C -> 32/stable/cm-11.0-XNG3C
* [nuovo branch] stable/cm-12.0-YNG1T -> 32/stable/cm-12.0-YNG1T
* [nuovo branch] stable/cm-12.0-YNG1TA -> 32/stable/cm-12.0-YNG1TA
* [nuovo branch] stable/cm-12.0-YNG3C -> 32/stable/cm-12.0-YNG3C
* [nuovo branch] stable/cm-12.0-YNG4N -> 32/stable/cm-12.0-YNG4N
* [nuovo branch] stable/cm-12.1-YOG3C -> 32/stable/cm-12.1-YOG3C
* [nuovo branch] stable/cm-12.1-YOG4P -> 32/stable/cm-12.1-YOG4P
* [nuovo branch] stable/cm-12.1-YOG7D -> 32/stable/cm-12.1-YOG7D
* [nuovo branch] stable/cm-13.0-ZNH0E -> 32/stable/cm-13.0-ZNH0E
* [nuovo branch] staging/caf/themes/cm-12.0 -> 32/staging/caf/themes/cm-12.0
* [nuovo branch] staging/cm-12.0-caf -> 32/staging/cm-12.0-caf
* [nuovo branch] staging/cm-12.1 -> 32/staging/cm-12.1
fatal: Commit pick sconosciuto
[Android Software/Hacking General [Developers Only]] HaoZeke:
Hey any idea about this? Using Uber 4.9 for both toolchain and kernel. No other funny business. honami, cm-12.1
[Android Software/Hacking General [Developers Only]] faizauthar12:
Disable graphite
[Android Software/Hacking General [Developers Only]] HaoZeke:
So I disabled the flags in the archidroid.mk like so

But, even after make clobber and ccache -C I got the same error... Help?
[Android Software/Hacking General [Developers Only]] neonkat:
https://github.com/kenzo-tree/android_build/commit/27a05cf88628d371362e15b89058eba8d1649963
[Android Software/Hacking General [Developers Only]] HaoZeke:
Hey, I'm sorry, I know everyone is being very helpful but even with this cherry-picked and after make clobber and ccache -C

Its the same isn error, in art
[Android Software/Hacking General [Developers Only]] neonkat:
strange,some of the graphite flags give ice with uber tc,i disabled those sets and got it fixed.i would recommend you to disablee some other graphite flags and check with uber or use some other toolchain.(linaro tc builds by DespairFactor are also good)
[Android Software/Hacking General [Developers Only]] HaoZeke:
Could you please point me towards those?

I don't know if it's related but by removing the	dex/quick/dex_file_method_inliner.cc \

file from Android.mk in the art compiler and recompiling gives the following error
[Android Software/Hacking General [Developers Only]] PWn3R:
Disable the graphite looping stuff in the ArchiDroid.mk file
[Android Software/Hacking General [Developers Only]] roshan2989:
anyone have kit kat achi optimization patches,seems like the link in OP shows not found..anyone?
[Android Software/Hacking General [Developers Only]] #Henkate:
Hello!

Can someone post a detailed review about this? I would like to know your opinions about these optimizations.

Thank you!

Have a nice day!

Robert.
[Android Software/Hacking General [Developers Only]] carefreeway:
It's very bad that [MENTION=5161352]JustArchi[/MENTION] removed links on github to Android "Kitkat" 4.4.4 patches. 5.0/5.1 (mdpi or lower on extra large screens) needs 512MB and 4.4 needs only 340MB at a minimum. My device (8" 1024x768) has only 463MB.

http://source.android.com/compatibility/5.0/android-5.0-cdd.html#heading=h.q4aoj3xvrlxe

http://source.android.com/compatibility/4.4/android-4.4-cdd.xhtml#section-7.6.1
[Android Software/Hacking General [Developers Only]] #Henkate:
Hi there!

I have got the same problem. I tried UBERTC 4.9 (even 4.8), HyperToolchain 4.9 (SaberxLinaro) and keep getting this error. With AOSP 4.8 I don't have this problem.

May I know if you've fixed this problem and if yes, how you did it?

Thank you!

Have a nice day!

Robert.
[Android Software/Hacking General [Developers Only]] HaoZeke:
Well I have for now given up on custom tool chains
[Android Software/Hacking General [Developers Only]] Adromir:
This commit has one disadvantage. Either it works or it doesn't. For use with Ubertoolchains I recommend this commit: https://github.com/UBERMALLOW/build/commit/704918b282c3fad0e17d6a8c6547d970f4b1120b it's from the guys who develop the Uber toolchains and you can disable them on a module basis
[Android Software/Hacking General [Developers Only]] rpdroky:
Here , just ignore the changes in armv7-a-neon.mk
[Android Software/Hacking General [Developers Only]] PWn3R:
Any of you guys try to adapt this to 7.0/7.1?
[Android Software/Hacking General [Developers Only]] pipyakas:
Is there anything like this for nougat? Im also using ubertc

If not then can I enable -o3 and graphite without the whole optimization commit?
[Android Software/Hacking General [Developers Only]] Adromir:
You can find the recent (nougats) Optimizations here: https://github.com/UBERROMS/build/commits/master
[Android Software/Hacking General [Developers Only]] carefreeway:
I've got a bootloop after compilation of CM-11.0 (4.4.4 is the best variant for 0.5 GB RAM device) with AOSP's arm-linux-androideabi-4.9 and arm-eabi-4.8. I did a lot of tests and find out that the cause of the bootloop is CM's 11.0 system. Kernel does work without any problems. Any hints how to solve this problem? Extracts from my local_manifest.xml:

<remote name="aosp"
fetch="https://android.googlesource.com"
review="android-review.googlesource.com" />
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" clone-depth="1" remote="aosp" revision="refs/tags/android-7.1.1_r6" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" clone-depth="1" remote="aosp" revision="refs/tags/android-7.1.1_r6" />

And also some changes I did to the default config:

project build/
diff --git a/core/combo/TARGET_linux-arm.mk b/core/combo/TARGET_linux-arm.mk
index 3497662..8e2c0a4 100644
--- a/core/combo/TARGET_linux-arm.mk
+++ b/core/combo/TARGET_linux-arm.mk
@@ -108,11 +108,14 @@ TARGET_GLOBAL_CFLAGS += \
-ffunction-sections \
-fdata-sections \
-funwind-tables \
- -fstack-protector \
+ -fstack-protector-strong \
-Wa,--noexecstack \
-Werror=format-security \
+ -Wno-error=unused-parameter \
-D_FORTIFY_SOURCE=2 \
-fno-short-enums \
+ -no-canonical-prefixes \
+ -fno-canonical-system-headers \
$(arch_variant_cflags) \
-include $(android_config_h) \
-I $(dir $(android_config_h))
@@ -121,7 +124,7 @@ TARGET_GLOBAL_CFLAGS += \
# We cannot turn it off blindly since the option is not available
# in gcc-4.4.x. We also want to disable sincos optimization globally
# by turning off the builtin sin function.
-ifneq ($(filter 4.6 4.6.% 4.7 4.7.%, $(TARGET_GCC_VERSION)),)
+ifneq ($(filter 4.6 4.6.% 4.7 4.7.% 4.8 4.8.% 4.9 4.9.%, $(TARGET_GCC_VERSION)),)
TARGET_GLOBAL_CFLAGS += -Wno-unused-but-set-variable -fno-builtin-sin \
-fno-strict-volatile-bitfields
endif
@@ -140,9 +143,12 @@ TARGET_GLOBAL_LDFLAGS += \
-Wl,-z,noexecstack \
-Wl,-z,relro \
-Wl,-z,now \
+ -Wl,--build-id=md5 \
-Wl,--warn-shared-textrel \
-Wl,--fatal-warnings \
-Wl,--icf=safe \
+ -Wl,--hash-style=gnu \
+ -Wl,--no-undefined-version \
$(arch_variant_ldflags)

TARGET_GLOBAL_CFLAGS += -mthumb-interwork

diff --git a/core/llvm_config.mk b/core/llvm_config.mk
index 18e689e..7df30c3 100644
--- a/core/llvm_config.mk
+++ b/core/llvm_config.mk
@@ -15,6 +15,7 @@ endef

CLANG_CONFIG_EXTRA_CFLAGS := \
-D__compiler_offsetof=__builtin_offsetof \
+ -Qunused-arguments

CLANG_CONFIG_UNKNOWN_CFLAGS := \
-funswitch-loops
[Android Software/Hacking General [Developers Only]] carefreeway:
Does anybody still have this patch?
[Android Software/Hacking General [Developers Only]] haoyangw:
Not sure if this approach is similar but I've tried this and it worked for me. Basically what it does is it forces ART to be compiled with GCC 4.8, so you need to have gcc 4.8 as well. Link: https://github.com/haoyangw/android_art/commits/gcc4.8 You need the last 3 commits
[Android Software/Hacking General [Developers Only]] carefreeway:
I have a success! I built Cyanogenmod 11.0 ROM without bootloops with gcc-4.9. I removed the following flags:

-Wl,--build-id=md5 \
-Wl,--hash-style=gnu \

in the file build/core/combo/TARGET_linux-arm.mk

And it turned out well. I used gcc sources from Google AOSP, which are used to build the latest Androids (7.1.2_r6).
[Android Software/Hacking General [Developers Only]] JustArchi:
You declare variant in lunch command. I.e. instead of lunch cm_i9300-userdebug you type cm_i9300-user.

If you ask me, I'm always building with target user. It's nothing major but first boot is much faster due to odexed build, we're getting rid from some debug modules, and it can't hurt in any way, apart from the fact that ADB is disabled by default (in userdebug it's enabled).

This is a "nice to have" feature because it makes things better for no cost. Deodexed builds are good for stock ROMs, when you're modding various APKs and other things, in AOSP, it's ultra rare that someone overwrites system apk, and even if he does so, it's one extra step of removing .odex file and wiping dalvik cache (not required always as well).

Also, notice that all official builds are odexed, at least by Samsung and Google in nexus line. Comparing user and userdebug in terms of performance will probably end up as a tie, but in odexed build, opening apps, booting process and runtime itself can improve, more or less.
[Android Software/Hacking General [Developers Only]] fabiotasa2:
Awesome work!!
[Android Software/Hacking General [Developers Only]] McDope:
build/core/main.mk was exactly what I was searching, thanks [MENTION=4328678]metalspring[/MENTION] :)

Just trying to better understand the build process ...
[Android Software/Hacking General [Developers Only]] shoey63:
It seems cm11 doesn't like to be 'odexed' - setup wizard FC's straight away:p Probably not surprising, as it is not AOSP.

I'll rebuild with 'userdebug' and report back.

Edit: at least it boots ;)
[Android Software/Hacking General [Developers Only]] McDope:
Had similiar result, got it to boot one time but was very laggy.
[Android Software/Hacking General [Developers Only]] JustArchi:
No issues on Omni nightly here, everything is butter smooth and no problems when built as user variant. Perhaps you could take a logcat so we could look into the issue.
[Android Software/Hacking General [Developers Only]] xenon92:
Just continuing on reporting this as I searched the thread and found others faced this issue as well. I compiled Carbon ROM for Galaxy Grand GT-i9082 and I faced graphics corruption too in play store 4.8.19. Didn't try older play store. I have read all your posts.

Image

I thought something might have gone bad during my build so I made a clean build, but same issue.

Then I removed the flags and compiled again with only O3 flag, and corruption is gone now. I understand it would be difficult to find the flag causing this issue, but nonetheless, I reported.

Used Linaro 4.8 from linaro releases 2014-03.
[Android Software/Hacking General [Developers Only]] JustArchi:
Yeah definitely it's the matter of some flag, but finding out which is faulty is going to take ages. Maybe you can help me guys, so we can find out and fix it :).
[Android Software/Hacking General [Developers Only]] sparksco:
Thanks, I committed the change that fixed graphite for SaberMod, but I know many people have used it on Linaro as well...