yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Rycon33:
Just another happy customer here.:):D

Thank you [MENTION=5161352]JustArchi[/MENTION] for this wonderful optimization that you shared with us.:highfive:

Only tried with the default GCC 4.7 on my Xperia SP running CM11 and my phone is already flying more smoothly than ever before.

Now building with GCC 4.7 on kernel and 4.8 on ROM.

Just want to mention that the commit I'm using is the one on your cm-11.0 branch(1125f60a15194e08fdf18feacefb47696647e05b) coz the one in the OP is giving me fatal error on cherry-pick.

Plus I also did the workaround(that many people mentioned here) on libhwcomposer error in hardware/qcom/display(&display-caf)/msm8960/libhwcomposer/Android.mk

-LOCAL_CFLAGS := $(common_flags) -DLOG_TAG=\"qdhwcomposer\"

+LOCAL_CFLAGS := $(common_flags) -DLOG_TAG=\"qdhwcomposer\" -Os

edit: just re-read and saw there's a better approach than above as mentioned from other users, removed inline before undefined function in hwc_utils.cpp

Thanks OP and everyone, I've read the entire 61 pages today and learned many things(I just learned self-compiling only last week btw).
[Android Software/Hacking General [Developers Only]] mastero9017:
I saw that many people switched to -Ofast flag and i'm a bit confused about what are you telling.

Also they are switching GPU flags the same way https://github.com/engstk/hammerhead-4.4.3/commit/5dcf1610ed03a47ee9039ce37ce8575532b2e4f3 with -ffast-math.

Can you tell us about switching other drivers flags and why it works?

Thanks, and i hope it will be interesting for everyone :)
[Android Software/Hacking General [Developers Only]] JustArchi:
I DON'T suggest using Ofast.

Things like wrongly rendered lockscreen effects and wrongly rendered battery circle are only TWO noticable issues, and I'm not even talking about what's going on inside.

You're using it on your own risk.
[Android Software/Hacking General [Developers Only]] micr0g:
Ok i think i have found the root of the problem (playstore graphical glitches and camera FC)

All this time my builds have been compiled with hybrid combination (Linaro 4.8 for androideabi and google's default 4.7 for eabi )

So this time i instead tried using Linaro 4.8 for both androideabi and eabi .

And now i have those problems as you have posted above.

So the solution is to use 4.7 for eabi?
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
You could compile the lot with UBERUTIL 's Sabermod 4.8 I don't have the play store graphical issue however this could be random as pointed out by JustArchi or its just linaro 4.8 that's affected.

So did you manage to compile now without having to change the flag to Os. The lens blur issue is present on Saber/Linaro/GCC 4.8 toolchains. If you can't live without the lens blur then its back to 4.7
[Android Software/Hacking General [Developers Only]] KcLKcL:
Nope, compiling with 4.7 eabi still gives me problem, like Lens Blur FC. Not sure about Play Store glitch because I used Google's GCC 4.8 (I always compile my kernel with 4.7 because it doesn't work with 4.8, idk why)
[Android Software/Hacking General [Developers Only]] micr0g:
I'm trying right now with SM 4.8 and ofcourse i can live without the lens blur,i've never use it,hehe!

[MENTION=4367925]KcLKcL[/MENTION] Linaro androideabi 4.8 and google's 4.7 eabi was my setup from 1st july and i never had this prob.
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
What are you building? on aosp and aospa lens blur not affected on hammerhead with 4.7 see here

https://github.com/AOSPA/android_de...mmit/c59abe28d38e1ec61964069b85ddc71724af2af4
[Android Software/Hacking General [Developers Only]] micr0g:
AOSPA, lens blur was the reason they revert back to 4.7 i think.
[Android Software/Hacking General [Developers Only]] KcLKcL:
I'm building CM on mako (N4), and yes, that's what I said. 4.8 gives me FC on Lens Blur, so I went back to 4.7 and everything went normal.
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
Ah ok I read it that you were still having lens blur problems on 4.7 :good:
[Android Software/Hacking General [Developers Only]] :
new sabermods :

arm-eabi-4.8

arm-eabi-4.9

arm-eabi-4.10

arm-androideabi-4.8

arm-androideabi-4.9

arm-androideabi-4.10

x86_64-linux-4.8

i686-linux-4.8

also including 2 linux-x86/host files

4.10 toolchains are from last month cause new build keeps failing , i'll try again later

have fun :laugh:

---------- Post added at 03:06 PM ---------- Previous post was at 02:55 PM ----------

i use sabermod arm-androideabi-4.8.4 for rom and sabermod arm-eabi-4.10 for kernel and don't have these issues
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
Thanks firebird11 i'm compiling a clean build just now with your arm-androideabi-4.8.4 and arm-eabi-4.10 toolchain. Has anyone that's having the playstore issue tried the new playstore 4.9.13

Edit: Still got the lens blur problem with arm-androideabi-4.8.4 and arm-eabi-4.10 toolchain, only affecting Nexus devices?

For anyone that thinks that this is a placebo, Switch runtime from dalvik to art and see how long it takes to optimise art on startup it's much quicker than it would normally take.

Thanks for this [MENTION=5161352]JustArchi[/MENTION]
[Android Software/Hacking General [Developers Only]] shoey63:
Tried the 2 linux-x86/host files but get this

i686-linux-g++: error: unrecognized command line option '-Wthread-safety'

Any way around it? Maybe [MENTION=2394329]sparksco[/MENTION] can help

Im on Ubuntu 14.04
[Android Software/Hacking General [Developers Only]] khusika:
btw, i got the playstore issue with gcc 4.8 both AOKP & BeanStalk from my build for Galaxy Wonder.
[Android Software/Hacking General [Developers Only]] Rycon33:
^^mate, try switching down to 4.7 gcc for kernel and retain 4.8 gcc for ROM. That is, if you haven't done so. That's my setup(on CM11 though.)

Edit: Guys, has anybody tried the new 4.9 sabermod? Anyway, I may give that a go, but later on weekends.

Tapatalked from my Xperia
[Android Software/Hacking General [Developers Only]] khusika:
yep, now im revert to the gcc 4.7, btw how to set the difference gcc version between rom and kernel at the same time when build rom?
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
Its only Linaro 4.8 that will give you the playstore issue Google GCC 4.8 shouldn't.

To use the Hybrid method there has been a couple of suggestions for doing this, I think I read in the thread rename the folder of the toolchain that you want to use to match the TARGET_GCC_VERSION :=

The other is tell it which toolchain to use for the kernel in BoardConfig which is the method I use like so ARM_EABI_TOOLCHAIN := $(ANDROID_BUILD_TOP)/prebuilts/gcc/linux-x86/arm/arm-eabi-4.9/bin
[Android Software/Hacking General [Developers Only]] t4n017:
There are many ways.

This is the one I use:

Line for Android toolchain (ROM) --> https://github.com/t4n017/android_build/blob/28e3de33e37d8413ab742fdf3dee5c81999d80d6/core/combo/TARGET_linux-arm.mk#L60

Line for Kernel toolchain --> https://github.com/t4n017/android_build/blob/28e3de33e37d8413ab742fdf3dee5c81999d80d6/core/tasks/kernel.mk#L151
[Android Software/Hacking General [Developers Only]] KcLKcL:
Exactly. A faster ART cache generation is the first thing I noticed after making a build with this commit.

And yeah, go back to 4.7 if you're on Nexus or you need Google Camera's Lens Blur Feature. It will not work with 4.8 Toolchains

I compile my ROM and kernel on my Nexus 4 with Linaro 4.7 and it's running fast!
[Android Software/Hacking General [Developers Only]] Rycon33:
Guys, just curious, when the ROM is built on different toolchain, do you clean wipe or just flash on top of the existing ROM? Or does it even matter either way? I personally do always clean wipe but if its fine dirty flashing then it saves a bit always re-logging in for all my online accts. TIA.
[Android Software/Hacking General [Developers Only]] KcLKcL:
Dirty flash or clean flash won't matter as the compiled files only affects system partition.

But make sure that you wipe dalvik cache.
[Android Software/Hacking General [Developers Only]] mastero9017:
So GCC 4.8 won't affect camera in 5 or not?
[Android Software/Hacking General [Developers Only]] KcLKcL:
5 what?

It will only affect Lens Blur. Lens Blur will not work. Anything else works fine.
[Android Software/Hacking General [Developers Only]] kidkoala_uk:
Yes it will lens blur will be broken on GCC 4.8 on nexus 5
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Strange issue here. Any ideas?

host C++: third_party_protobuf_protoc_host_gyp <= external/chromium_org/third_party/protobuf/src/google/protobuf/compiler/java/java_service.cc
host C++: third_party_protobuf_protoc_host_gyp <= external/chromium_org/third_party/protobuf/src/google/protobuf/compiler/java/java_string_field.cc
host C++: third_party_protobuf_protoc_host_gyp <= external/chromium_org/third_party/protobuf/src/google/protobuf/compiler/python/python_generator.cc
LD drivers/video/msm/built-in.o
LD drivers/video/built-in.o
/home/whiteneo/omni/kernel/sony/msm8960/Makefile:950: recipe for target 'drivers' failed
make[2]: *** [drivers] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/whiteneo/omni/kernel/sony/msm8960'
build/core/tasks/kernel.mk:177: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2
[Android Software/Hacking General [Developers Only]] desalesouche:
the error is more up

---------- Post added at 02:51 AM ---------- Previous post was at 02:20 AM ----------

hi. i could build for my device , huawei honor (u8860) with v3 without any problem thanks to good op.

i have one question what about cpu scorpion....? can you optimize for it also or is it not needed?

Edit: here is what i did for scorpion cpu...

edited in build/core/combo/arch/armv7-a-neon.mk

ifeq ($(strip $(TARGET_CPU_VARIANT)),scorpion)

arch_variant_cflags := -mcpu=cortex-a8

arch_variant_ldflags := -Wl,--fix-cortex-a8

else

and all went fine.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
You were right, but I still can't locate the exact reason for the problem.

I attached a log of around 900000 characters. :D Perhaps anyone can help me with the search. ^^

BTW, rename the file type to ".txt", I had to change the file type for the upload to work. It was even too large for pastebin. :/

Any help would be greatly appreciated. :)
[Android Software/Hacking General [Developers Only]] marcomarinho:
Hi,

I know that isn't related to JustArchi Optimization, but I need help :p

/bin/sh: 1: arm-eabi-gcc: not found
make[3]: *** [applets/applets.o] Error 127
make[2]: *** [applets_dir] Error 2
make[1]: *** [prepare] Error 2
make[1]: Leaving directory `/home/marco/purekat/external/busybox'
make: *** [busybox_prepare_full] Error 2
make: *** Waiting for unfinished jobs....

I had this error while building. Already searched everywhere, but didn't found any solution. For the ROM I used the Google 4.8 Toolchain, and for the kernel I used the Linaro Cortex A8 Optimized
[Android Software/Hacking General [Developers Only]] alwaysadeel:
I had this error on my Carbon build, so i switched to Omni's Busybox and it fixed the issue. CM made some changes in busybox.
[Android Software/Hacking General [Developers Only]] marcomarinho:
You saved my day :highfive: Thanks bro :good:
[Android Software/Hacking General [Developers Only]] t4n017:
I thought I screwed something.

I was using SaberMod 4.8 (androideabi) and Linaro 4.9 optimized for Cortex-A9 (eabi) on Paranoid Android.

I went back to GCC 4.8 and it seems to be working fine now (still building).
[Android Software/Hacking General [Developers Only]] marcomarinho:
fixed
[Android Software/Hacking General [Developers Only]] Vynikal:
As I see, there is an expert discussion, so I'll post there a problem.

I am using SaberMod 4.9 (eabi and android-eabi). I can't pass bootanimation. Last_kmsg attached. IMO can't mount EXT4 filesystem. Bug is on the ROM side, not kernel.

In last_kmsg should be something like this:

[ 50.549926] acc_open
[ 50.550140] acc_release
[ 74.503295] EXT4-fs (dm-0): mounted filesystem without journal. Opts:
[ 77.671844] EXT4-fs (dm-0): re-mounted. Opts:
[ 77.749420] EXT4-fs (dm-0): re-mounted. Opts:

But instead it boots forever.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Could anyone point me to a commit that allows compiling only the kernel with a custom toolchain, leaving the rom as it is? :)

Would love to build a Sabermod kernel but I keep getting errors with the Optimizations of this thread.

Btw, I'd prefer if the kernel was created automatically with the rom, letting me skip the manual kernel compilation. (Which gives me errors as well. :D)
[Android Software/Hacking General [Developers Only]] JustArchi:
Strange, I rebuilt my ROM today, not from scratch but with "new" busybox and didn't get any errors.

At the moment using Google's GCC 4.8 for both kernel and ROM.

So yeah I guess GCC 4.9 may be the reason.
[Android Software/Hacking General [Developers Only]] McDope:
Linus himself blamed GCC 4.9 for weird stuff (see http://lkml.iu.edu/hypermail/linux/kernel/1407.3/00650.html), so I would definitely use 4.8 or below for now.
[Android Software/Hacking General [Developers Only]] marcomarinho:
Don't think that's the reason. I set the right PATH (envsetup.sh) for kernel toolchain and that error gones :p
[Android Software/Hacking General [Developers Only]] sidneyk:
Just set TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.x.x in your device_*.mk file, substituting arm-eabi-4.8, for instance, to use a tool chain named arm-eabi-4.8. Just make sure your tool chain directories are following Android's naming conventions and make the number part of that variable match whatever number your tool chain has, I.e. 4.4.3, 4.6, 4.7, 4.8, etc. You may be able to set it in BoardConfig.mk instead, if preferred. I use the device-*.mk file myself. This works if you put your tool chains in the same directory as Android's prebuilts, either adding new ones or substituting existing ones, as long as the same naming convention is followed.
[Android Software/Hacking General [Developers Only]] alwaysadeel:
CM build does not have any problem. This error only popped in Carbon build that uses CM Busybox.
[Android Software/Hacking General [Developers Only]] marcomarinho:
Fixed
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Thank you! Didnt think it was that easy. :D

Can you confirm that compiling with Linaro or SaberMod increases performance? :)
[Android Software/Hacking General [Developers Only]] desalesouche:
Hi.all error are could find are here... they seem to be only kernel related...

http://pastebin.com/xw7QeHrL

i know there is change to do in kernel for gcc 4.8 and 4.9 to co compile properly...
[Android Software/Hacking General [Developers Only]] Rycon33:
In case WhiteNeo hasn't resolved it. Look at the fixes here -> https://github.com/LiquidSmooth-Devices/android_kernel_motorola_msm8960dt-common/commit/a465d392c84869a22866317a277b6dc3c3b241f2

Since you only have the two errors, f_qdss.c and hci_conn.c, edit only that two files mentioned from that commit.
[Android Software/Hacking General [Developers Only]] sidneyk:
I'm using Sabermod 4.8 for both rom and kernel with Omnirom on Asus tf101. Does feel snappier and maybe bit better benchmarks. Boots faster, after initial boot.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Thanks! I might try this later. :)
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Compiling Omnirom with Linaro 4.7 Toolchain and -O2 flag for thumb.

Build was nearly done when this error appeared.

target SharedLib: libandroid_runtime (/home/whiteneo/omni/out/target/product/tsubasa/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so)
hardware/qcom/display-caf/libhwcomposer/hwc_fbupdate.cpp:81: error: undefined reference to 'qhwc::configRotator(overlay::Rotator*, overlay::utils::Whf&, overlay::utils::Whf const&, overlay::utils::eMdpFlags const&, overlay::utils::eTransform const&, int const&)'
hardware/qcom/display-caf/libhwcomposer/hwc_fbupdate.cpp:88: error: undefined reference to 'qhwc::updateSource(overlay::utils::eTransform&, overlay::utils::Whf&, hwc_rect&)'
hardware/qcom/display-caf/libhwcomposer/hwc_fbupdate.cpp:196: error: undefined reference to 'qhwc::configMdp(overlay::eek:verlay*, overlay::utils::PipeArgs const&, overlay::utils::eTransform const&, hwc_rect const&, hwc_rect const&, MetaData_t const*, overlay::utils::eDest const&)'
collect2: error: ld returned 1 exit status
build/core/shared_library.mk:81: recipe for target '/home/whiteneo/omni/out/target/product/tsubasa/obj/SHARED_LIBRARIES/hwcomposer.msm8960_intermediates/LINKED/hwcomposer.msm8960.so' failed
make: *** [/home/whiteneo/omni/out/target/product/tsubasa/obj/SHARED_LIBRARIES/hwcomposer.msm8960_intermediates/LINKED/hwcomposer.msm8960.so] Error 1
make: *** Warte auf noch nicht beendete Prozesse...

I have no idea how to fix this, as the mentioned file (hardware/qcom/display-caf/libhwcomposer/hwc_fbupdate) doesnt even exist in the omni directory.. Please help. ^^
[Android Software/Hacking General [Developers Only]] Rycon33:
WhiteNeo, apply this commit-> https://github.com/SlimKangs/androi...mmit/3dbe819702c0363581851a882c8d540b2d6b4924

I think it was already mentioned last time also, hehehe.?

Tapatalked from my Xperia
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Thank you. :D

I wonder where you guys find all those commits. There should be an index of some kind. ^^

I didnt think this Linaro 4.8 fix could apply for my building issues, as I only changed -Os to -O2 in latest build. Thats why I was asking. :)

EDIT: I checked the file and I'm not sure if the commit really works for me.. These are the lines causing the error:

81: if(configRotator(mRot, info, origWhf, mdpFlags, orient, 0) < 0) {

88: updateSource(orient, info, sourceCrop);

195: if(configMdp(ctx->mOverlay, parg, orient, sourceCrop, displayFrame,
196: NULL, mDest) < 0) {

The lines don't seem to fit to the commit you linked to, as there is no "inline" prefix that could be removed.
[Android Software/Hacking General [Developers Only]] satyr007:
Hi, huge thanks Archi for this.

I built latest pure slimkat 6.9 for hammerhead with all flags using gcc 4.8, didn't touch kernel so its built with default toolchain... 4.7 probably :D.

https://mega.co.nz/#!E8cT0DTb!qFa4iWlrmmtMqYq5e5EFJeujJuO-GID_fH6RB59LRVc
[Android Software/Hacking General [Developers Only]] Rycon33:
[MENTION=5122093]WhiteNeo[/MENTION] , the other workaround is mentioned here -> http://xdaforums.com/showpost.php?p=53339308&postcount=423

Tapatalked from my Xperia
[Android Software/Hacking General [Developers Only]] WhiteNeo:
So you suggest using a local -Os cflag in the concerning section? A good idea actually! :good:

Could you show me how this works? :)
[Android Software/Hacking General [Developers Only]] DJLamontagneIII:
The commit he link earlier will fix that error without dropping down to -Os in the project https://github.com/SlimKangs/androi...mmit/3dbe819702c0363581851a882c8d540b2d6b4924... Basicly your errors are coming from libhwcomposer/hwc_fbupdate.cpp because its looking for those references in libhwcomposer/hwc_utils.cpp but can't find them with them inline.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Ahh, now I get it. The "inline" itself would not be an issue, but the other methods referencing it cause the compile issues.

I'll try that commit, then. :good:

By the way, sorry guys for my (most likely) pretty stupid questions. I'm quite new to all this compilation and flag stuff and I guess I still have to find my way around. ^^

EDIT: Build compiled successfully. Thanks for the help. :D

Next target: -O3 flags and Linaro 4.8 ^^
[Android Software/Hacking General [Developers Only]] JustArchi:
Actually it's nice to see people helping eachother, and it also benefits future questions through search option.

And if you're wondering, your issue is happening due to more aggressive optimizations on level O2 and higher.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
Okay.. In that case, I'll need your opinion. :) What do you think will be the easier next step for me, compiling thumb and kernel with O3, or both with Linaro 4.8?

Currently I'm using O2 and Linaro 4.7 for both.
[Android Software/Hacking General [Developers Only]] JustArchi:
It's very rare that O3 will cause any side effects if you have none with O2.

Compiler is whole another story.
[Android Software/Hacking General [Developers Only]] WhiteNeo:
So this error pops up after enabling O3 for thumb (leaving kernel on O2):

target thumb C: libwebp-decode <= external/webp/src/dec/../dsp/lossless.c
target thumb C: libwebp-decode <= external/webp/src/dec/../dsp/upsampling.c
target thumb C: libwebp-decode <= external/webp/src/dec/../dsp/upsampling_neon.c
external/webp/src/dec/../dsp/upsampling_neon.c: In function 'UpsampleBgraLinePairNEON':
external/webp/src/dec/../dsp/upsampling_neon.c:266:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
build/core/binary.mk:512: recipe for target '/home/whiteneo/omni/out/target/product/tsubasa/obj/STATIC_LIBRARIES/libwebp-decode_intermediates/../dsp/upsampling_neon.o' failed
make: *** [/home/whiteneo/omni/out/target/product/tsubasa/obj/STATIC_LIBRARIES/libwebp-decode_intermediates/../dsp/upsampling_neon.o] Error 1
make: *** Warte auf noch nicht beendete Prozesse...

Is this a bug in the toolchain?

EDIT: Build with O3 flag for kernel and O2 for thumb compiled successfully. Might try O3 for both now to see if I still get the same error.

EDIT2: I managed to work around this issue by setting a local -O2 flag in android/external/webp/src/dec/Android.mk

Let's see how this build moves on.. :good:

EDIT3: Build completed successfully! :D
[Android Software/Hacking General [Developers Only]] Sick1:
Hey,

Just dropping by to give you all some respect!! Compiled Simple Aosp rom,with Uberutils Sabermod 4.8.4 succesfully for the first time!

Also very much thanks to [MENTION=496333]kidkoala_uk[/MENTION] for pointing those few commits from VanirAosp git for the camera!

Peace
[Android Software/Hacking General [Developers Only]] desalesouche:
hi sir may i ask if you could optimize this for scorpion cpu?

in build scorpion cpu is = cortex-a8

i tested by the past th v1 and i couldn't finish build. but now with v3 the build is with no errors...and if some all is explained in op(how-to fix)

thank you...
[Android Software/Hacking General [Developers Only]] lichti1901:
Can you please post these commits here?

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Software/Hacking General [Developers Only]] Sick1:
http://xdaforums.com/showpost.php?p=54299588&postcount=606

Those just fixed my compile errors, but the lens blur fc is still happening, to which i think you were lookin for a fix :)
[Android Software/Hacking General [Developers Only]] Dri94:
have any roms officially merged this commit yet?
[Android Software/Hacking General [Developers Only]] marcomarinho:
Yes, a lots of ROMs had merged this commit
[Android Software/Hacking General [Developers Only]] desalesouche:
please can ou provide some names? thanks
[Android Software/Hacking General [Developers Only]] KcLKcL:
My Self-Compiled CyanogenMod 11 has this commit :)
[Android Software/Hacking General [Developers Only]] desalesouche:
my cm11 build also has archdroid commits.

i was meaning if some roms who already integrated this in their source?
[Android Software/Hacking General [Developers Only]] marcomarinho:
So what do you want to know? There are ROMs that had it, like mine:

PureKat
[Android Software/Hacking General [Developers Only]] desalesouche:
a new rom i didn't compile yet...^^

thank you sir may be i ask in wrong way, but you clearly understood me...xD :good: