yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] GeyerA:
Yes, you are right I should have posted the error right away....was at work. Anyhow, here we go

hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera.c: In function 'mm_camera_stop_zsl_snapshot':
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera.c:1612:23: error: 'value' is used uninitialized in this function [-Werror=uninitialized]
control.value = *value;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera.c:680:13: note: 'value' was declared here
int32_t value;
^
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'hw_module_t::dso' [-Wmissing-field-initializers]
};
^
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'hw_module_t::reserved' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'gralloc_module_t::perform' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'gralloc_module_t::lock_ycbcr' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'gralloc_module_t::reserved_proc' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::pmem_master' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::pmem_master_base' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::info' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::finfo' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::xdpi' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::ydpi' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:100:1: warning: missing initializer for member 'private_module_t::fps' [-Wmissing-field-initializers]
hardware/libhardware/modules/gralloc/gralloc.cpp:168:12: warning: unused parameter 'usage' [-Wunused-parameter]
static int gralloc_alloc_buffer(alloc_device_t* dev,
^
target thumb C++: gralloc.default <= hardware/libhardware/modules/gralloc/framebuffer.cpp
cc1: all warnings being treated as errors
make: *** [out/target/product/hammerhead/obj/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera.o] Error 1
make: *** Waiting for unfinished jobs....
[Android Software/Hacking General [Developers Only]] lichti1901:
Here you go ;)

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Software/Hacking General [Developers Only]] GeyerA:
Hi, I think I found a fix. Google is your friend; based on the comment from Metalspring

http://xdaforums.com/galaxy-nexus/general/howto-build-rom-linaro-toolchain-t1988315/page89

Just change the line in TARGET_linux-arm.mk from

-Wno-error=maybe-uninitialized
to
-Wno-error=uninitialized

Compiling right now.....let you know :)

Lichti, you are quicker as lightning....thanks, I will check right away....seems doing the same thing :)
[Android Software/Hacking General [Developers Only]] adinkwok:
He took them down :(. If you're still looking for one, try using sabermod 4.8.3
[Android Software/Hacking General [Developers Only]] JustArchi:
https://github.com/ArchiDroid/Toolchain
[Android Software/Hacking General [Developers Only]] DerRomtester:
Dont know if this is the right place to post this here.

Kernel is booting with linaro 4.9gcc and -O2

But kernel with linaro GCC 4.9 and -O3 is very unstable. Anyone knows whats wrong here?

Gesendet von meinem A0001
[Android Software/Hacking General [Developers Only]] Horizone:
Amazing work Archi :) What I don't understand is why don't google use at least some of these improvements? It's a big shame more rom developers don't include these :( <- Don't understand that either
[Android Software/Hacking General [Developers Only]] seadersn:
they will, in next release, they're reading forums everywhere, too :D maybe ;)
[Android Software/Hacking General [Developers Only]] jamieg71:
There's a plethora of info, in this thread, regarding your question. That being said, your post is somewhat ambiguous. What kind of issues are you having? Perhaps a browse of the thread may answer your question..
[Android Software/Hacking General [Developers Only]] DerRomtester:
My device: oneplus one

k

My issues are that the kernel is booting fine after i have flashed it on fastboot.

If i remove the usb cable the kernel wont boot.

If not it is booting up. But after removing usb cable it hard reboots and wont boot anymore.

Kmsg shows no errors or sth.
[Android Software/Hacking General [Developers Only]] kenzolo:
How can I avoid the error [-Werror=unused-parameter] ?

It appear in different folder not only in system/vold

system/vold/CommandListener.cpp:63:6: error: unused parameter 'argc' [-Werror=unused-parameter]

EDIT SOLVED
[Android Software/Hacking General [Developers Only]] frap129:
EDIT: nvm, stupid question
[Android Software/Hacking General [Developers Only]] Khaon:
[MENTION=5161352]JustArchi[/MENTION]

Hello, due to the introduction of this commit your patch v3 fails when applied.

EDITED : my bad, pasted a wrong url
[Android Software/Hacking General [Developers Only]] Synergy510:
It's very simple to apply JustArchi's commit even with CM's update. If you're doing "git cherry-pick <JustArchi's v3 SHA>" you will find an error, all you have to do is manually edit the file to complete the cherry pick. Compare CM's updated file with what JustArchi's commit adds and do it manually after you cherry-pick then save the file and run "git cherry-pick --continue"

Here's my arm-v7-a-neon.mk file for reference https://github.com/xsynergy510x/android_build/commit/29695fb0ffaf13233ae54e50e8db1681a840720c
[Android Software/Hacking General [Developers Only]] JustArchi:
Or just learn how to use git mergetool.
[Android Software/Hacking General [Developers Only]] mastero9017:
Trying switch to SM 4.10. I see that many makefiles are not prepared to 4.9.X+ I'm getting this error (AOSPA)

http://pastebin.com/h6xuWSFx

Any idea how to fix it?
[Android Software/Hacking General [Developers Only]] desalesouche:
more optimization?

http://review.cyanogenmod.org/#/c/72647/1

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

http://www.sqlite.org/draft/changes.html

testing archi build with sqlite updated to 3.8.6

if someone could make same kind of patch for sqlite 3.8.7 that looks better than 3.8.6...

http://www.sqlite.org/download.html

will feed back with 3.8.6.

regards
[Android Software/Hacking General [Developers Only]] whitdawg:
My first attempt at building Beanstalk using these optimizations. I'm a bit of a newb, so any help with this build error would be greatly appreciated. http://pastebin.com/MAxiQquw
[Android Software/Hacking General [Developers Only]] macs18max:
FYI. I tried the upper two commits as mentioned by JustArchi and built the rom in user mode.

I dont have superuser access at first but if I go to development option (tap 10 times on build number) and goto Root access and select apps or apps and adb

Bang!!! Rooted

Thanks Archi for this awesome mod.
[Android Software/Hacking General [Developers Only]] t4n017:
[MENTION=5161352]JustArchi[/MENTION],

do you know why even after picking your webp commit Play Store still glitchy? :confused:

I made clobber and cleaned ccache before building.
[Android Software/Hacking General [Developers Only]] JustArchi:
This commit has no outcome on glitched play store icons.

Compiler has.
[Android Software/Hacking General [Developers Only]] t4n017:
I know it isn't related with this commit and it's a bug on GCC.

I was refering to the libwebp commit you made.

My apologies for the off-topic, we can move to PM if you want to.
[Android Software/Hacking General [Developers Only]] JustArchi:
My Webp commit fixes playstore bug completely. I tested that. Standalone commit does not, upstream does.
[Android Software/Hacking General [Developers Only]] t4n017:
I picked the webp upstream not the standalone commit.

I don't know why it doesn't work here, I tried two times, both clean builds.

Paranoid Android built with Linaro 4.8 (your repo).

I'll keep trying, maybe is my fault.

Thanks anyway, keep up the good work!
[Android Software/Hacking General [Developers Only]] JustArchi:
No clue then, it worked for everyone who picked it so far.
[Android Software/Hacking General [Developers Only]] JustArchi:
https://github.com/ArchiDroid/android_external_webp/commits/cm-11.0-gcc

Make sure that your branch is the same.
[Android Software/Hacking General [Developers Only]] t4n017:
No, I picked the squashed one: https://github.com/JustArchi/android_external_webp/commit/36c6201fbb108d6b757f860e2cd57f3982191662
[Android Software/Hacking General [Developers Only]] JustArchi:
It should work regardless, but I prefer to have history.
[Android Software/Hacking General [Developers Only]] sparksco:
There is no official SM 4.10, so you must be using a unofficial one... 4.9.2 is the latest stable for kernel and 4.8.4 for KitKat Roms. I've also fixed high resource usage building SaberMod toolchains.
[Android Software/Hacking General [Developers Only]] mastero9017:
Someone tested this? [MENTION=5161352]JustArchi[/MENTION] opinion?
[Android Software/Hacking General [Developers Only]] seadersn:
it's just a compressor, it doesn't make the rom faster or better, only smaller in size. it's just a tool to make the output more size optimized. and that's good, always :D
[Android Software/Hacking General [Developers Only]] JustArchi:
As above.

In best-case-scenario, this will reduce memory footprint and I/O because all images will be smaller by a tiny bit.

However, I doubt in best-case above. Probably it only reduces size of the apps and other packages with images by a tiny bit. I'm pretty sure that Android doesn't keep images in "raw" form in memory, so any increase in performance or decrease in memory footprint is close to none.

Of course you can use it, but don't think that it will make things faster. It's like loading 1 image more/less compared to original resources.
[Android Software/Hacking General [Developers Only]] Sick1:
I build CM11 nightlies with JustArchi optimizations for myself to Oneplus One. Tried this and been using this pngcrush for a week now but havent notice any improvements. Rom is aprox 15mb:s smaller though.
[Android Software/Hacking General [Developers Only]] desalesouche:
png crush is not for improvement. i mentionned it simply cos it reduce size of rom , after 03 made it bigger...

i never mention that it would improve rom...if i use png , it is simply because my device can't afford big rom size.
[Android Software/Hacking General [Developers Only]] mastero9017:
Yes, but i was thinking about reducing reads/writes. 15mb should make great improvement.

Btw Poland just won with Germany
[Android Software/Hacking General [Developers Only]] marcomarinho:
Hi,

I know that this is a little bit of off-topic, but I really don't know why this happened :(

including ./vendor/widevine/Android.mk ...
build/core/tasks/kernel.mk:83: **********************************************************
build/core/tasks/kernel.mk:84: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:85: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:86: * BoardConfig.mk file *
build/core/tasks/kernel.mk:87: **********************************************************
make: *** No rule to make target `bacon'. Stop.

My ROM had inline kernel building, I inclued the TARGET_KERNEL_CONFIG under my device BoardConfig.mk. All is in the right place, so why this is happening :confused:
[Android Software/Hacking General [Developers Only]] bigsupersquid:
I had similar effects when I did the . build/envsetup.sh but forgot to lunch my device. It was trying to build generic-armv7a or something by default.
[Android Software/Hacking General [Developers Only]] marcomarinho:
Yes, for me now works :p And now had this problem:

make: *** No rule to make target `/var/lib/jenkins/workspace/euclidean-grouper/out/target/common/obj/JAVA_LIBRARIES/android_webview_java_intermediates/javalib.jar', needed by `/var/lib/jenkins/workspace/euclidean-grouper/out/target/common/obj/JAVA_LIBRARIES/webviewchromium_intermediates/classes-full-debug.jar'. Stop.
make: *** Waiting for unfinished jobs....

Why my problems are so hard to solve :(
[Android Software/Hacking General [Developers Only]] JustArchi:
Your problems are hardly connected with this commit at all.

As I stated in the OP, firstly, you must be experienced with building from source, applying gerrit patches and getting your ROM done from A to Z. Then you may experiment with this commit :).
[Android Software/Hacking General [Developers Only]] marcomarinho:
I already solved :p That problem wasn't related with this at all. I only needed to make some changes on webview, no big problem at all :p
[Android Software/Hacking General [Developers Only]] kenzolo:
sorry guys,what is the correct method to change the kernel flag when I compile the entire rom?

I want -o3 for rom and -o2 for the kernel...

Which line and which file I need to edit?

Here my files:

TARGET-linux-arm.mk

Makefile (kernel source)

device boardconfig.mk

Sorry if already asked but I can't find a good answer

Thanks in advance
[Android Software/Hacking General [Developers Only]] JustArchi:
Nothing, kernel flags are not stated in android_build, they're stated in android_kernel_vendor_device.

Example: https://github.com/ArchiDroid/android_kernel_samsung_smdk4412/blob/cm-11.0/Makefile#L565

Extra notice: Beware, changing kernel flags may have unknown not-yet-discussed problems :).
[Android Software/Hacking General [Developers Only]] lozohcum:
Can I apply "V3 for OmniROM" on AOSP source code?
[Android Software/Hacking General [Developers Only]] JustArchi:
You can apply V3 CM or Omni, it really doesn't matter, I included two versions only because I didn't want to create conflicts when you cherry-pick one commit for all ROMs.

Commit is exactly the same, CM version just includes "less", as some things are already included.
[Android Software/Hacking General [Developers Only]] noname55804:
Hey, i got a little bit confused, so i´ll ask my question which might have beeen answered before. After apllying your Optimisations can we still use the -O flags like O3 or are they unnecessary?
[Android Software/Hacking General [Developers Only]] JustArchi:
Read the commit and judge yourself.
[Android Software/Hacking General [Developers Only]] noname55804:
Ok after reading through it i assume that O3 compilation is already turned on, so no need to type it in the build command. Right?
[Android Software/Hacking General [Developers Only]] lozohcum:
What about this?

clang: error: the clang compiler does not support '-mfpu=neon-vfpv4'
[Android Software/Hacking General [Developers Only]] JustArchi:
Exactly what it says.

You tried passing -mfpu=neon to clang, and clang doesn't support it.
[Android Software/Hacking General [Developers Only]] lozohcum:
I replaced AOSP clang with CM clang and now it's fine.

Thanks
[Android Software/Hacking General [Developers Only]] bsw11:
Does anyone know of an Nexus 7 2013 Rom that uses this?

BSW Jedi KK Note 3
[Android Software/Hacking General [Developers Only]] noname55804:
Assuming that the "thanks" you gave me on this post means that I'm right [MENTION=5161352]JustArchi[/MENTION] ? :D
[Android Software/Hacking General [Developers Only]] irocevo:
I have been trying to build this for the nexus 7 2013 with carbon but I can't figure out this last error. Please help.

kernel/google/msm/net/sunrpc/svcauth_unix.c:531:2: warning: "gids" may be used uninitialized in this function
[-Wmaybe-uninitialized]
error, forbidden warning: svcauth_unix.c:531
make[4]: *** [net/sunrpc/svcauth_unix.o] Error 1

This is svcauth_unix.c (first line is 531)

for (i = 0 ; i < gids ; i++) {
int gid;
rv = get_int(&mesg, &gid);
err = -EINVAL;
if (rv)
goto out;
GROUP_AT(ug.gi, i) = gid;
}
[Android Software/Hacking General [Developers Only]] bigsupersquid:
you could maybe disable the warning (common solution, not a good as the next way)

or you could find where 'gids' is declared and initialize it to some value there, like 0.
[Android Software/Hacking General [Developers Only]] Khaon:
Hello,

didn't have the time to look more into it, but since a few days compiling with linaro 4.8.x or 4.9.x fail at boot. The kernel does boot but from logcat I could read memory execptions from some libs

I tried with linaro's 4.7.4 toolchains, it does work and boots.

I am building for an APQ8064 device( s600), does anyone else come accross that as well?
[Android Software/Hacking General [Developers Only]] JustArchi:
You need to modify your kernel's makefile.

Judging from path, it should be in kernel/google/msm/Makefile.

Basically you need to add -Wno-maybe-uninitialized to KBUILD_CFLAGS.

Example: https://github.com/ArchiDroid/lge-kernel-lproj/commit/cb081ed3941a57778eb55ef02c61dec2f60ef34d

As I said previously, kernel uses it's own set of flags and doesn't care about what's going on in android_build. Your error is connected with using more recent toolchain (e.g. 4.8 over 4.7), which forces some additional security checks.
[Android Software/Hacking General [Developers Only]] irocevo:
Thanks. I did that a couple hours ago. Builds almost done, can't wait to test flo out :) I'm building m7spr and flo with these optimizations now with GCC 4.8 and linaro 4.9 :)

edit:

I had to add Not booting kernel -> https://github.com/JustArchi/android...e4bfb3cff64de9 and https://github.com/JustArchi/android...90528feb0c9bdd

Now it works great. Ill make a thread in the Nexus 7 2013 (flo) forum later.

But here's a download link for carbon build if anyone is interested.

http://d-h.st/H1Y

Also replaced DSP Manager was replaced with Viper4Android :)

Thanks for the help :)
[Android Software/Hacking General [Developers Only]] :
@ JustArchi , can you please put in the OP how to use different toolchain for kernel

thanks
[Android Software/Hacking General [Developers Only]] seadersn:
TARGET_KERNEL_TOOLCHAIN = path/to/toolchain. or is it already mentioned somewhere...? sry then ;)
[Android Software/Hacking General [Developers Only]] shoey63:
Just cheat ;)

Rename arm-eabi.4.6 to something else, and put your toolchain of choice there and call it arm-eabi.4,6 :D
[Android Software/Hacking General [Developers Only]] frap129:
Currently working on adapting this to lollipop :D hope I get it working soon! Right now its mostly problems with clang

clang++: error: unknown argument: '-funsafe-loop-optimizations'
clang++: error: unknown argument: '-ftree-loop-im'
clang++: error: unknown argument: '-ftree-loop-ivcanon'
clang++: error: unknown argument: '-frename-registers'
clang++: error: unknown argument: '-frerun-cse-after-loop'
clang++: error: unknown argument: '-fgcse-sm'
clang++: error: unknown argument: '-fgcse-las'
clang++: error: unknown argument: '-fweb'
clang++: error: unknown argument: '-funsafe-loop-optimizations'
clang++: error: unknown argument: '-ftree-loop-im'
clang++: error: unknown argument: '-ftree-loop-ivcanon'
clang++: error: unknown argument: '-frename-registers'
clang++: error: unknown argument: '-frerun-cse-after-loop'
clang++: error: unknown argument: '-fgcse-sm'
clang++: error: unknown argument: '-fgcse-las'
clang++: error: unknown argument: '-fweb'
clang++: error: unknown argument: '-funsafe-loop-optimizations'
clang++: error: unknown argument: '-ftree-loop-im'
clang++: error: unknown argument: '-ftree-loop-ivcanon'
clang++: error: unknown argument: '-frename-registers'
clang++: error: unknown argument: '-frerun-cse-after-loop'
clang++: error: unknown argument: '-fgcse-sm'
clang++: error: unknown argument: '-fgcse-las'
clang++: error: unknown argument: '-fweb'
clang++: error: unknown argument: '-funsafe-loop-optimizations'
clang++: error: unknown argument: '-ftree-loop-im'
clang++: error: unknown argument: '-ftree-loop-ivcanon'
clang++: error: unknown argument: '-frename-registers'
clang++: error: unknown argument: '-frerun-cse-after-loop'
clang++: error: unknown argument: '-fgcse-sm'
clang++: error: unknown argument: '-fgcse-las'
clang++: error: unknown argument: '-fweb'

Sooooooo most of the optimizations

EDIT: More clang probs, at this point I feel like trying to compile a custom clang and trying to get it to work that way

EDIT 2: Fixed all the clang errors, now it just errors out when compiling external/stlport

---------- Post added at 07:02 PM ---------- Previous post was at 06:31 PM ----------

http://xdaforums.com/chef-central/android/guide-switching-to-custom-toolchain-t2927662
[Android Software/Hacking General [Developers Only]] sparksco:
I fixed this in 2013

https://github.com/SaberDroid/external_clang/commit/c8ee28aa8fa25d1a8f395f40d75c63c0ab2a9f1c
[Android Software/Hacking General [Developers Only]] KcLKcL:
I'm still syncing Lollipop source right now. Planning to adjust this into Lollipop as well. Please keep us posted here!

[MENTION=5051294]frap129[/MENTION] how did you manage to fix the clang errors?
[Android Software/Hacking General [Developers Only]] frap129:
Seriously Google needs to get with the program. Thanks for this link, I'll cherry-pick this asap.

Well, at first i removed all the problem flags, but now Im just gonna use the commit Paul linked above
[Android Software/Hacking General [Developers Only]] KcLKcL:
If someone manages to adapt this to Lollipop AOSP, please give us a cherry-pick. I think I have problems while merging this commit and fixing the conflicts, I'll probably will try again later though, now I got something to do now :(
[Android Software/Hacking General [Developers Only]] frap129:
Well, I got lollipop to build up untill this error

target thumb C++: libc <= bionic/libc/bionic/libc_init_dynamic.cpp
{standard input}: Assembler messages:
{standard input}:24: Error: selected processor does not support Thumb mode `mrc p15,0,r3,c13,c0,3'
make: *** [out/target/product/shamu/obj/SHARED_LIBRARIES/libc_intermediates/bionic/libc_init_dynamic.o] Error 1
make: *** Waiting for unfinished jobs....
[Android Software/Hacking General [Developers Only]] TheGeekyNimrod:
[MENTION=5161352]JustArchi[/MENTION] You are a beautiful genius. Some of us run brand spanking new devices. Some of us like to kick it old school. I'm one of the latter. While my current DD is the i747 (S3) I keep my SGH-i777 (S2 AT&T) around at all times. Mostly as a wifi device for my son to play games, watch YouTube, etc. I use it when going on long road trips because the battery life is much better than my S3.

I currently build LiquidSmooth and Carbon for the i777. Yesterday, for the first time since I started building from source, I cherry-picked a commit. This one. And I have to say it made that Carbon build the smoothest one I have built yet. I've learned along the way how to add toolchains to my build, and a few other things to give it more stability for such an aging device. But this time, on a balanced profile, I ran AnTuTu and achieved my highest score on that device to date. The only change in the builds from recently was adding this commit.

So thank you. It's awesome. It's wonderful. And you sir, deserve all the beers that XDA can buy.
[Android Software/Hacking General [Developers Only]] desalesouche:
[MENTION=5161352]JustArchi[/MENTION] will you work on android L version in same way? it might be too early gor such question?