I downloaded A700FD Android 6.0 kernel source from Samsung open source website，I compiled in ubuntu and put it into boot.img and brush into，But I found that wifi could not be opened. Check the log and found the error: wlan: disagrees about version of symbol module_layout。Can you tell me the solution? Please
Related
I'm trying to port firefox os(B2G) to my device (HTC Desire HD). While building it stops because of error at libgui in SurfaceTextureClient.cpp
last few lines of build log
Code:
target thumb C++: libgui <= frameworks/base/libs/gui/SurfaceTextureClient.cpp
frameworks/base/libs/gui/SurfaceTextureClient.cpp: In member function 'virtual int android::SurfaceTextureClient::setUsage(uint32_t)':
frameworks/base/libs/gui/SurfaceTextureClient.cpp:500: error: 'GRALLOC_USAGE_EXTERNAL_ONLY' was not declared in this scope
frameworks/base/libs/gui/SurfaceTextureClient.cpp:505: error: 'GRALLOC_USAGE_EXTERNAL_BLOCK' was not declared in this scope
make: *** [out/target/product/ace/obj/SHARED_LIBRARIES/libgui_intermediates/SurfaceTextureClient.o] Error 1
and the full build log is here
I think this happens because of the build system doesn't build
Code:
hardware/qcom/display/libgralloc/
before building
Code:
frameworks/base/libs/gui/
How can I tell the B2G build system to do that? Or is there any other way to get around this without breaking(like can't see anything) the build?
Here is my B2G manifest file.
I know this belongs in the developer forum but I still can't post in it
In your device blobs you are telling it to make hardware/com/display or display_legacy or the like correct? One way to at least get past this error and possibly get either further clues or have it compile would be to just add the header to this file or reference it as a dependency in your frameworks/base makefiles. These are just some ideas. Its hard without knowing where you are pulling these from (cm repo, Google, linaro, b2g, or whatever) so I can look at the code and makefiles. But normally this sort of thing will be an adjustment needed to your makefiles. Its just finding which, or if its simply a missing statement like this in your device makefiles TARGET_QCOM_DISPLAY_VARIANT := legacy
Pacman for the 3vo CDMA
Compile kernel from source,but wifi won't work!
I tried to compile the android kernel from source, my device is E330S, OS is Ubuntu 15.04 x64, version of toolchains is 4.7.
I downloaded the source code of 4.4 from opensource.samsung.com firstly, and follew the instructions of compiling. I got the zImage and packed it into boot.img, flashed it into my phone. All things work well except wifi, the button is unable to be checked, and no configuration file was created in /data/misc/wifi. I change the code to 5.0 and flash the kernel, the device won't boot. Finally i tried to use the code of arter from bitbucket.org/arter97/android_kernel_samsung_msm8974.git, but it won't work either.
The KitKat is the only one that works, i have copied all the *.ko into /system/lib/moduels, but the lsmod shows no modules is installed, .
I am a beginner of compiling the android kernel, is there any tips i missed?
anyone knows?
edited (solution): I forgot I had another thread on this same basic topic. You have to merge AOSP + Device Sources + Hardware Drives and set it up to build the sources.
https://forum.xda-developers.com/android/software/toolbox-c-struct-define-toolname-tool-s-t3568409
If I try to compile my own customize 'toolbox' binary for example, I can't find the headers anywhere in the toolchains or included headers. I can search them down from Google sources but I gave up after tools.h. I have a feeling this is NOT the way I am supposed to be doing it.
Is there a shared library on my device that I pull off to get these headers? (lib?????.so).. Where do I get headers for Android/log.h and cutils properties.h and selinux.h ??? Or are we not supposed to compile these binaries on a Ubuntu machine? (do I compile them on the device itself?)
ediit: (here's compiling it another way, obviously I can make a hack easily but working with Android is so much harder.)
arm-linux-gnueabi-gcc -static -march=armv8-a toolbox.c -o toolbox
toolbox.c:6:25: fatal error: android/log.h: No such file or directory
compilation terminated.
edit, solved i think
I think it's stand alone toolchain not defined. If that's not the answer, it's a fun answer so I'm playing with that. If I don't have the answer I will pass the question up, download sources and start trying to compile Android proper. (which is my new goal now, I want open source phone and I want to compile my own OS 100%, besides the closed sources, it's so exciting!!) ~so much for sleep
Kernel compilation error '"aarch64-linux-android-gcc" is not allowed to be used.'
I'm building the kernel with LineageOS 17.1 / Android 10 r31 however the build process errors out during kernel compilation.
Specifically with:
Code:
"aarch64-linux-android-gcc" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
make[3]: *** [/home/saltoin/android/lineageos-17.1/kernel/samsung/universal8895/scripts/Makefile.build:153: scripts/mod/devicetable-offsets.s] Error 1
Following the link says that any host tools in PATH won't be allowed to be used during compilation. However, `aarch64-linux-android-gcc` is not from my path but supplied by the build tools. Unless I'm mistaken in that assumption.
Regardless, exporting TEMPORARY_DISABLE_PATH_RESTRICTIONS=true allows aarch64-linux-android-gcc.
Unless I'm missing something, I don't believe I should be getting this error.
Thoughts?
Hello there, have you found any solution?
TEMPORARY_DISABLE_PATH_RESTRICTIONS=true doesn't work in the config file. What do you mean by export? Thanks in advance for help.
Build System Changes for Android.mk Writers
As a temporary measure, you can set TEMPORARY_DISABLE_PATH_RESTRICTIONS=true in your environment to temporarily turn off the error checks and allow any tool to be used (with logging).
I'm trying to build the kernel for my Poco M3 from https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lime-q-oss and I'm getting errors like
In file included from techpack/camera/drivers/cam_req_mgr/cam_req_mgr_core.c:15:
./techpack/camera/drivers/cam_utils/cam_trace.h:18:10: fatal error: 'cam_req_mgr_core.h' file not found
#include "cam_req_mgr_core.h"
In file included from techpack/display/pll/dsi_pll_10nm.c:16:
In file included from techpack/display/pll/pll_trace.h:109:
./include/trace/define_trace.h:89:10: fatal error: './pll_trace.h' file not found
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
I was able to remove `#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)` from lots of places and fixed the .h from the cam files and other stuff, but I get thousands of ` undefined reference to `__tracepoint_rdev_return_int'` and other things related to trace, probably because I disable those trace includes.
Why Xiaomi releases a broken kernel source and is there an official place where I can get a working kernel source?
PS: I'm documenting the entire process of building a kernel and flashing and doing crazy stuff, so if you help me you're helping the community. Thanks!