Database Info

[DEV][PORT] FirefoxOS to S3 i9300

[Issue Building][B2G] Porting FirefoxOS tto the S3 i9300
Hi,
I am a working Porting FirefoxOS to the S3 i9300, but i have a problem with the gralloc_module.cpp, so this is the log:
Code:
b2g/application.ini
b2g/libnspr4.so
target thumb C++: gralloc.i9300 <= hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp: In function 'int gralloc_lock(const gralloc_module_t*, const native_handle_t*, int, int, int, int, int, void**)':
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:386: error: 'GRALLOC_USAGE_YUV_ADDR' was not declared in this scope
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp: At global scope:
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: error: 'gralloc_module_t' has no non-static data member named 'getphys'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::info'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::finfo'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::xdpi'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::ydpi'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::fps'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::enableVSync'
make: *** [out/target/product/i9300/obj/SHARED_LIBRARIES/gralloc.i9300_intermediates/gralloc_module.o] Error 1
real 1m57.225s
user 1m53.015s
sys 0m23.001s
> Build failed! <
Build with |./build.sh -j1| for better messages
If all else fails, use |rm -rf objdir-gecko| to clobber gecko and
Could some help me with this? I like continue with the Port but i can't find a patch to solve this. The repo where there are all the files of the Port is this
https://github.com/Droid2Fox.
The repo that has the library wrong is this:
https://github.com/Droid2Fox/android_hardware_samsung
I work with the ICS branch, not with the Jellybeam.
Thanks

Ok from what your error says I think the lines you need to pay attention to in the error is the following lines.
Code:
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: error: 'gralloc_module_t' has no non-static data member named 'getphys'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::info'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::finfo'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::xdpi'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::ydpi'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::fps'
hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:480: warning: missing initializer for member 'private_module_t::enableVSync'
In your build folder look in hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp and look at line 480 of that file. Now without being able to look at that file I can not tell you anymore about it. But that is what i read from your error.

Re: [Issue Building][B2G] Porting FirefoxOS tto the S3 i9300
This is the file that has the issue:
https://github.com/Droid2Fox/androi...exynos4/hal/libgralloc_ump/gralloc_module.cpp
Do you know any idea of how to do it work?
Thanks
Sent from my GT-I9300 using xda app-developers app

Gioyik said:
I am a working Porting FirefoxOS to the S3 i9300, but i have a problem with the gralloc_module.cpp, so this is the log:
Click to expand...
Click to collapse
This reply might seem insulting, but it's impossible for me to know what previous knowledge the original poster has...
Do you understand the errors and warnings that the compiler is generating? What have you done already in order to try and diagnose the errors/warnings? What were the results (if any?)
Are you a developer who is fluent with c++, or are you only looking for someone to provide patches to make things work for you?
Thanks
Gary

Hi,
I understand the warnings that generates the compiler, and i am trying to declare those functions, but i am not good with C++. I create a patch for the Cammerawrapper.cpp before, but for this i don't understand so much how to fix it. I have been some changes, i can declare some functions but it continues giving problems with other functions that are not declared. I found this:
http://git.linaro.org/gitweb?p=peop...b;hb=24a9e234b68b3f44f0f0dbe7dc7efc8f0d57808d
It's good, it solve the 80% not the 100% of the issue, because it fails again because the 'GRALLOC_USAGE_YUV_ADDR' is not declared.
So, i post this in XDA, because i know that there are a lot of devs that knows too much than me about this, and possibly someone has a solution for this. I am not rude and i don't like that other do the work for me, it's only a Post to ask if someone pass for this before and got a solution.
Thanks for you're answers.

Gioyik said:
Hi,
I understand the warnings that generates the compiler, and i am trying to declare those functions, but i am not good with C++. I create a patch for the Cammerawrapper.cpp before, but for this i don't understand so much how to fix it. I have been some changes, i can declare some functions but it continues giving problems with other functions that are not declared. I found this:
http://git.linaro.org/gitweb?p=peop...b;hb=24a9e234b68b3f44f0f0dbe7dc7efc8f0d57808d
It's good, it solve the 80% not the 100% of the issue, because it fails again because the 'GRALLOC_USAGE_YUV_ADDR' is not declared.
So, i post this in XDA, because i know that there are a lot of devs that knows too much than me about this, and possibly someone has a solution for this. I am not rude and i don't like that other do the work for me, it's only a Post to ask if someone pass for this before and got a solution.
Thanks for you're answers.
Click to expand...
Click to collapse
or you could just build aosp ics and copy whatever the error says it cannot build into the b2g out...

Re: [Issue Building][B2G] Porting FirefoxOS tto the S3 i9300
Yes could be a solution. I will try. Thanks.
Sent from my GT-I9300 using xda app-developers app

Note: This is not a question or helping post, this is for Devs interested in continue with the Port of FirefoxOS to i9300
Hi,
My name is Giovanny, and i was trying to make the Port of FirefoxOS to S3 i9300. I have some work ready and some patches ready to build some parts of the port but i can't cotinue making it, because i have some problems compiling that i can resolve myself. I am not a great Android Developer, i know somethings but i am not an expert. For that reason i like share my work with XDA, if there's a Dev interested in make the Port succesfull. This is my Organization account in GIthub:
https://github.com/Droid2Fox
There, i have all the sources ready to start building the Port, it has problem building thats bad for me, because i don't know how to resolve it. If you're interested in continue with the Port you can follow those steps:
Steps:
Clone the repo: https://github.com/Droid2Fox/B2G
Into the repo directory run in the terminal: ./config.sh i9300
When it finishes the download of sources: ./build.sh
And flash with the finally package
For more information visit:
https://developer.mozilla.org/en-US...lug=Mozilla/Firefox_OS/Building_Boot_to_Gecko
https://developer.mozilla.org/en-US...Firefox_OS/Preparing_for_your_first_B2G_build
What's the problem with the Port:
Problems with galloc library
Problems when compile ./test.....js
Possibly other problems
I know that someone can do it more easier, i have some time ago doing this but i can't resolve all the problems, for that reason i decide that other Devs interested can complete this.
Thanks so much, i will be reading if someone is working on it.

Merged the two "firefox i9300" threads (both started by the same person in the same section) together.

[Completed] ROM build from source error

Hi there,
I have an error when compiling Android Open Source Bam(AOSB) for Xperia SP(huashan)
target thumb C++: libqdutils <= hardware/qcom/display-caf/libqdutils/profiler.cpp hardware/libhardware_legacy/audio/AudioPolicyManagerBase.cpp:3794:28: error: 'AUDIO_FORMAT_FLAC' was not declared in this scope build/core/binary.mk:432: recipe for target '/home/AndroidNoob69/android/aosb/out/target/product/huashan/obj/STATIC_LIBRARIES/libaudiopolicy_legacy_intermediates/AudioPolicyManagerBase.o' failed make: *** [/home/AndroidNoob69/android/aosb/out/target/product/huashan/obj/STATIC_LIBRARIES/libaudiopolicy_legacy_intermediates/AudioPolicyManagerBase.o] Error 1 make: *** Waiting for unfinished jobs....
I have no idea what causes this. Please advise what I need to do to fix this.
Thanks.
Sent my Paranoid Xperia P

Hi!
2 things.....1, this is your 3rd thread on this subject. XDA assist is not a help desk, we're simply here to give direction to new members. You are not new.
And 2, if Bam is what I think it is....that developer and ROM has been banned from XDA. No threads are allowed on the subject and no ROM postings of it, or ROMs based on it. If your talking about something different... Mt apologies.... But point number one still stands.
Thread closed.

[Q&A] Guide on building Lollipop for the OnePlus One

Q&A for Guide on building Lollipop for the OnePlus One
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Guide on building Lollipop for the OnePlus One. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

./extract-files.sh on CM11S
Does ./extract-files.sh will do the right thing if you are on CM11S ?
Because it is sait there : wiki.cyanogenmod.org/w/Build_for_bacon
That you need to have a build of the same branch running on your phone (which is obiously not the case here...)

Kppqju77 said:
Does ./extract-files.sh will do the right thing if you are on CM11S ?
Because it is sait there : wiki.cyanogenmod.org/w/Build_for_bacon
That you need to have a build of the same branch running on your phone (which is obiously not the case here...)
Click to expand...
Click to collapse
Yes, it will work if you're running CM11S on your phone as far as I know. You can try and report back.

me too. video play can't work . it will reboot when click to play video.

Any idea why do I get it? I followed a guide.
make[1]: Entering directory `/home/malwin/cm/kernel/oneplus/msm8974'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
Edit : I've checked settings and "Enable loadable module support is checked.
It also bothers my why revision="cm-11.0" of connectivity project is used to build cm12?
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

[Q&A] [GUIDE] How to Build CM11 for the HTC One M8 (082714)

Q&A for [GUIDE] How to Build CM11 for the HTC One M8 (082714)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to Build CM11 for the HTC One M8 (082714). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Just saying thanks for this. CM12 (5.0.2) build is running great. Synced to CM12 repos as instructed. No bugs (yet)!

CM12 builds have started to fail
I keep getting hung up here on CM12 builds.
Any ideas why? Still using the same steps from OP.
LZ4 arch/arm/boot/compressed/piggy.lz4
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/user/android/system/kernel/htc/msm8974'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 22m47.514s
user 69m54.278s
sys 11m47.943s

placebo_domingo said:
I keep getting hung up here on CM12 builds.
Any ideas why? Still using the same steps from OP.
LZ4 arch/arm/boot/compressed/piggy.lz4
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/user/android/system/kernel/htc/msm8974'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real22m47.514s
user69m54.278s
sys11m47.943s
Click to expand...
Click to collapse
What os are you building on? I had this issue while building DU for my flo (I build on Mac osx) and found that I had to install the lz4 binaries through homebrew and then all was golden. Either way, your computer is looking for the lz4c executable and it isn't there

Shamestick said:
What os are you building on?
Click to expand...
Click to collapse
I was using Ubuntu 14.04. I ended up switching to Fedora 20 and I was able to build using that. Glad to know that answer though.

Isn't CM still suffering from speaker distortion and bluetooth issues, since CM 11? I'd consider using CM, but my understanding is that it just doesn't work flawlessly, for one reason or another, on these phones.

Don't know about Bluetooth but the speaker issues got much better around 1/7. Before that, random buzzing sounds. Awful.

[rom][aospa][unofficial][7.2.2][bacon]

I have almost finished compiling the ROM but need some help with an error then it'll be ready.
Here's what's happening when I build it:
[ 0% 90/18970] Docs droiddoc: out/target/common/docs/api-stubs
DroidDoc took 16 sec. to write docs to out/target/common/docs/api-stubs
[ 0% 91/18970] Compiling SDK Stubs: out/target/common/o...IBRARIES/android_stubs_current_intermediates/classes.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[ 0% 93/18970] Building with Jack: out/target/common/ob...LIBRARIES/framework_intermediates/with-local/classes.dex
FAILED: /bin/bash out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex.rsp
Out of memory error (version 1.2-rc4 'Carnac' (298900 f95d7bdecfceb327f9d201a1348397ed8a843843 by [email protected])).
GC overhead limit exceeded.
Try increasing heap size with java option '-Xmx<size>'.
Warning: This may have produced partial or corrupted output.
[ 0% 93/18970] Compiling SDK Stubs with Jack: out/targe...BRARIES/android_stubs_current_intermediates/classes.jack
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Build failed!
Total time elapsed: 10 minutes (652.687489167 seconds)
I cannot seem to locate the java heap size parameter file to modify it. A little info will help out. If not I'll figure it out on my own soon and have the latest build ready for flashing. Thanks.

Official? Oh please...

SirSoviet said:
Official? Oh please...
Click to expand...
Click to collapse
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?

Techie Android said:
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?
Click to expand...
Click to collapse
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.

SirSoviet said:
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.
Click to expand...
Click to collapse
Okay I was not aware of that being the case. I understood official to mean it was unmodified and built from the source. I'll change it to unofficial since I'm not connected to AOSPA. Thank you for pointing that out.

placeholder threads are not allowed on xda where are the moderators when we need them?
Read the RULES NEXT TIME!!!!

Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?

Techie Android said:
Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?
Click to expand...
Click to collapse
Rules are rules.. There was no trash talk, the only poor attitude is yours. I hope you'll resolve this here as well as with any future posts you make..
I've already reported this thread, lets keep this respectful until everything gets fixed..
Thanks

Thread moved to Q&A section at this moment, if later the ROM is released, please report it to Mod Team and we will move it back to develop section.
And please be reminded to keep the discussion as civil as you can.