Related
Hi guys
Thought I should start a thread for various AOSP builds people are doing for their Sony Z5Compact. We can trouble shoot errors and generally take advantage of the way Sony encourage open source development for their devices.
Ill get the ball rolling. (see below)
AOSP NOUGAT 7.1
https://mega.nz/#!Jh5WxSYS!DkYHgBjtR...V6Vdxq11xMplcg
TWRP3.0.3
https://mega.nz/#!QhoBESZI!XzXzHvosc...X57GnZvRBEPoR4
AOSP NOUGAT
Installable .zip compiled with mm binaries: https://mega.nz/#!h8530CLS!vmwYkb4JBdx8YtOaqkETq84bFeR9wiz2KYIlNOWnFBM (as sony has not published N binaries yet.)
Nougat .img files for z5c: https://mega.nz/#!5h5gxYKI!AuCFTO6MV4J5rfMBK_A1Q4eOBr5ZoXQIG2wEW9Fffxg
AOSP MM BUILD for Z5C.
Android 6.1
New Build with Julys/Android N compatible binaries Build # MOB30W
Installable .zip: https://mega.nz/#!80BlACKS!hefd26xN36UPcgnGEfdp9BkPsZvjS3k4Bvzo3dmU9I8
Raw .img files: https://mega.nz/#!FoYTGQbT!8ifDpGlZSaXgsHo1_gLm-67YIdDo0-BW85hra5ZToVY
New Build as of 29/04/16 (untested as of yet) Ignore below list of what works as I havent flashed this to my phone yet.
https://mega.nz/#!MwJ3wSJb!6ALDvaSIPQK0kc8R6MU5mVhUmKKCzVovE54tLcNxTx0
Older MM build (.img files)
https://mega.nz/#!B5hhyYhT!Z1lMcwxHc3KC9lDRCwOcyImBXXLuHgqROZ76J5xArew
RECOMMENDED DO A FULL WIPE OF DATA AND SYSTEM BEFORE FLASHING. Have your old/stock system, recovery,boot.img saved on your pc, as TWRP is not supported in AOSP kernel.
Boots fine.
will load and use previous userdata from rooted sony stock. (but not recommended to dirty flash!)
Data connection was patchy
Camera works but is awful.
External and internal sd card detection/mounts fine, but the rom wants to re format your external sd card before it mounts.
Regards
Joeisgood99
@Joeisgood99, your links are missing the Mega decryption key.
Anyway, I compiled 5.1.1_r24 (latest Lollipop) from source and uploaded here:
https://mega.nz/#!1hZlFCoT!UIEBo9CjaYu0Eg-4CeVdRijchRqNwbErUZPL4qbhzRo
I have no Z5C so consider it fully UNtested.
Still no luck with my 6.0.0_r1 build
nilezon said:
@Joeisgood99, your links are missing the Mega decryption key.
Anyway, I compiled 5.1.1_r24 (latest Lollipop) from source and uploaded here:
https://mega.nz/#!1hZlFCoT!UIEBo9CjaYu0Eg-4CeVdRijchRqNwbErUZPL4qbhzRo
I have no Z5C so consider it fully UNtested.
Still no luck with my 6.0.0_r1 build
Click to expand...
Click to collapse
Thanks for that!
I have only made it about 19 mins in to 6.0.0_r1 build before it fails.
target thumb C: libmmcamera_interface_32 <= hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_thread.c
In file included from hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera.c:44:0:
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/../common/mm_camera_interface.h:98:21: error: 'MSM_CAMERA_MAX_USER_BUFF_CNT' undeclared here (not in a function)
int32_t buf_idx[MSM_CAMERA_MAX_USER_BUFF_CNT];
^
In file included from hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_interface.c:44:0:
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/../common/mm_camera_interface.h:98:21: error: 'MSM_CAMERA_MAX_USER_BUFF_CNT' undeclared here (not in a function)
int32_t buf_idx[MSM_CAMERA_MAX_USER_BUFF_CNT];
^
In file included from hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_channel.c:40:0:
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/../common/mm_camera_interface.h:98:21: error: 'MSM_CAMERA_MAX_USER_BUFF_CNT' undeclared here (not in a function)
int32_t buf_idx[MSM_CAMERA_MAX_USER_BUFF_CNT];
^
In file included from hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_thread.c:41:0:
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/../common/mm_camera_interface.h:98:21: error: 'MSM_CAMERA_MAX_USER_BUFF_CNT' undeclared here (not in a function)
int32_t buf_idx[MSM_CAMERA_MAX_USER_BUFF_CNT];
^
build/core/binary.mk:801: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera.o' failed
target thumb C: libmmcamera_interface_32 <= hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_sock.c
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:45:0:
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/../common/mm_camera_interface.h:98:21: error: 'MSM_CAMERA_MAX_USER_BUFF_CNT' undeclared here (not in a function)
int32_t buf_idx[MSM_CAMERA_MAX_USER_BUFF_CNT];
^
build/core/binary.mk:801: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_thread.o' failed
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_thread.o] Error 1
build/core/binary.mk:801: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_interface.o' failed
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_interface.o] Error 1
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c: In function 'mm_stream_write_user_buf':
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1046:21: error: dereferencing pointer to incomplete type
cont_buf->buf_cnt = my_obj->buf[buf->buf_idx].user_buf.bufs_used;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1047:46: error: dereferencing pointer to incomplete type
for (i = 0; i < (int32_t)cont_buf->buf_cnt; i++) {
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1048:25: error: dereferencing pointer to incomplete type
cont_buf->buf_idx = my_obj->buf[buf->buf_idx].user_buf.buf_idx;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1055:50: error: dereferencing pointer to incomplete type
for (i = 0; i < (int32_t)cont_buf->buf_cnt; i++) {
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1103:21: error: dereferencing pointer to incomplete type
cont_buf->buf_cnt = my_obj->buf[index].user_buf.bufs_used;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1104:46: error: dereferencing pointer to incomplete type
for (i = 0; i < (int32_t)cont_buf->buf_cnt; i++) {
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1105:25: error: dereferencing pointer to incomplete type
cont_buf->buf_idx = my_obj->buf[index].user_buf.buf_idx;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1112:50: error: dereferencing pointer to incomplete type
for (i = 0; i < (int32_t)cont_buf->buf_cnt; i++) {
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c: In function 'mm_stream_read_user_buf':
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1163:60: error: dereferencing pointer to incomplete type
frameID = (buf_info->buf->frame_idx - 1) * user_buf->buf_cnt;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1177:65: error: dereferencing pointer to incomplete type
my_obj->prev_timestamp = (timeStamp - (nsecs_t)(user_buf->buf_cnt * interval_nsec));
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1180:54: error: dereferencing pointer to incomplete type
interval_nsec = (nsecs_t)(ts_delta / user_buf->buf_cnt);
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1184:38: error: dereferencing pointer to incomplete type
for (i = 0; i < (int32_t)user_buf->buf_cnt; i++) {
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1185:54: error: dereferencing pointer to incomplete type
buf_info->buf->user_buf.buf_idx = user_buf->buf_idx;
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1186:49: error: dereferencing pointer to incomplete type
stream_buf = &my_obj->plane_buf[user_buf->buf_idx];
^
hardware/qcom/camera/QCamera2/stack/mm-camera-interface/src/mm_camera_stream.c:1204:49: error: dereferencing pointer to incomplete type
buf_info->buf->user_buf.bufs_used = user_buf->buf_cnt;
^
build/core/binary.mk:801: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_channel.o' failed
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_channel.o] Error 1
build/core/binary.mk:801: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_stream.o' failed
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/libmmcamera_interface_intermediates/src/mm_camera_stream.o] Error 1
#### make failed to build some targets (19:09 (mm:ss)) ####
Tried to fix it with this
https://git.geekli.st/pirej/kernel/commit/3b7ca4571409e0e38ae45afedf77afbf3099d801?view=parallel
or similar but didn’t work.
Thanks for your contribution!:good:
Joeisgood99 said:
Thanks for that!
I have only made it about 19 mins in to 6.0.0_r1 build before it fails.
Tried to fix it with this ... or similar but didn’t work.
Thanks for your contribution!:good:
Click to expand...
Click to collapse
I got similar errors.
You need to update the files in ./device/sony/kitakami/kernel-headers/ with files from the Sony kernel source code.
For example, replace:
https://github.com/sonyxperiadev/device-sony-kitakami/blob/master/kernel-headers/media/msmb_camera.h
with
https://github.com/Tommy-Geenexus/a...n_5.x/blob/master/include/media/msmb_camera.h
to get correct MSM_CAMERA_MAX_USER_BUFF_CNT definition.
You also need to add an header include to macaddrsetup.c to make it compile. See this pull request:
https://github.com/sonyxperiadev/macaddrsetup/pull/1
That's all I've got for now.
Edit:
This is the error I end up with:
Code:
No private recovery resources for TARGET_DEVICE suzuran
target Symbolic: init (out/target/product/suzuran/symbols/init)
target Unpacked: adbd (out/target/product/suzuran/obj/EXECUTABLES/adbd_intermediates/PACKED/adbd)
target StaticExecutable: healthd (out/target/product/suzuran/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd)
out/host/linux-x86/bin/checkpolicy: loading policy configuration from out/target/product/suzuran/obj/ETC/sepolicy_intermediates/policy.conf
device/qcom/sepolicy/common/init_shell.te:3:ERROR 'unknown type init_shell' at token ';' on line 16010:
#for accessing fmradio device node
allow init_shell fm_radio_device:chr_file { open read ioctl };
checkpolicy: error(s) encountered while parsing configuration
make: *** [out/target/product/suzuran/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
Edit2:
Possibly solution for sepolicy error:
https://github.com/alviteri/device-qcom-sepolicy/tree/test-m
Source: https://github.com/sonyxperiadev/device-qcom-sepolicy/pull/8
Edit3:
I got past the sepolicy errors, but face new problems.
Some definitions are missing:
Code:
target thumb C++: camera.msm8994_32 <= hardware/qcom/camera/QCamera2/HAL/QCamera2HWI.cpp
hardware/qcom/camera/QCamera2/HAL/QCamera2HWI.cpp: In member function 'int qcamera::QCamera2HardwareInterface::sendCommand(int32_t, int32_t&, int32_t&)':
hardware/qcom/camera/QCamera2/HAL/QCamera2HWI.cpp:3928:10: error: 'CAMERA_CMD_LONGSHOT_ON' was not declared in this scope
case CAMERA_CMD_LONGSHOT_ON:
^
hardware/qcom/camera/QCamera2/HAL/QCamera2HWI.cpp:3970:10: error: 'CAMERA_CMD_LONGSHOT_OFF' was not declared in this scope
case CAMERA_CMD_LONGSHOT_OFF:
^
etc ...
Awesome work @nilezon.
This thread is becoming a build diary for Sony aosp 6.0.0_r1.
I used the commits you pointed out. They fixed the issue, the build stooped 3 mins later with this error
target thumb C++: liboverlay_32 <= hardware/qcom/display/msm8994/liboverlay/overlayRotator.cpp
hardware/qcom/display/msm8994/liboverlay/overlayUtils.cpp: In function 'int overlay::utils::getMdpFormat(int, int)':
hardware/qcom/display/msm8994/liboverlay/overlayUtils.cpp:153:24: error: 'MDP_RGBA_8888_UBWC' was not declared in this scope
return MDP_RGBA_8888_UBWC;
^
hardware/qcom/display/msm8994/liboverlay/overlayUtils.cpp:155:24: error: 'MDP_RGB_565_UBWC' was not declared in this scope
return MDP_RGB_565_UBWC;
^
hardware/qcom/display/msm8994/liboverlay/overlayUtils.cpp:159:24: error: 'MDP_Y_CBCR_H2V2_UBWC' was not declared in this scope
return MDP_Y_CBCR_H2V2_UBWC;
^
target thumb C++: liboverlay_32 <= hardware/qcom/display/msm8994/liboverlay/overlayMdpRot.cpp
build/core/binary.mk:706: recipe for target 'out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/liboverlay_intermediates/overlayUtils.o' failed
make: *** [out/target/product/suzuran/obj_arm/SHARED_LIBRARIES/liboverlay_intermediates/overlayUtils.o] Error 1
make: *** Waiting for unfinished jobs....
target thumb C++: liboverlay_32 <= hardware/qcom/display/msm8994/liboverlay/overlayMdssRot.cpp
#### make failed to build some targets (21:25 (mm:ss)) ####
All these undeclared formats are declared in /devices/sony/kitakami/kernel-headers/linux/msm_mdp.h
but haven’t had a chance to even look at why info isn’t getting passed along yet. Has been a big family oriented weekend. Just sat down. Ill look in to your errors.
Thanks again!
Seems to be a problem with a broken make config, the kitakami settings are not being applied or reverting. The source is also missing a few defines, mainly around the camera it seems.
thx for your great work!
has anyone tested the 5.1.1. builds? are there any known issues?
can't use my phone without root and bloatware instead.
M!tch said:
thx for your great work!
has anyone tested the 5.1.1. builds? are there any known issues?
can't use my phone without root and bloatware instead.
Click to expand...
Click to collapse
Most are holding out for a way to keep DRM keys I think, slows down the trial and error process a bit.
M!tch said:
thx for your great work!
has anyone tested the 5.1.1. builds? are there any known issues?
can't use my phone without root and bloatware instead.
Click to expand...
Click to collapse
I compiled AOSP but couldn't get it to boot. Most likely something wrong with the pre-compiled kernel image.
does the build from the op work?
M!tch said:
does the build from the op work?
Click to expand...
Click to collapse
Don't know. I didn't test.
BUT, FreeXperia has published suzuran (Z5C) build for 5.1.1:
http://fxpblog.co/aosp/aosp-5-1/
http://uploaded.net/file/rg3ocwy3/from/ub0dtu
I don't know if they work either, but I guess they usually does?
I've tried flashing the images in the OP and it just hangs when sending system. Have waited 30 minutes and still nothing.
creebefu said:
I've tried flashing the images in the OP and it just hangs when sending system. Have waited 30 minutes and still nothing.
Click to expand...
Click to collapse
Did you flash with the sparse flag?
Code:
fastboot -S 256M flash system system.img
nilezon said:
Did you flash with the sparse flag?
Code:
fastboot -S 256M flash system system.img
Click to expand...
Click to collapse
That flashed okay, but rebooted and it ended up turning itself off after the Sony - Xperia screen.
For the others I'm literally just doing:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
etc.
Any other commands I should try?
creebefu said:
That flashed okay, but rebooted and it ended up turning itself off after the Sony - Xperia screen.
For the others I'm literally just doing:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
etc.
Any other commands I should try?
Click to expand...
Click to collapse
Hmm, I didn't know that you could flash a recovery image to an Xperia phone:
Code:
fastboot flash recovery recovery.img
I don't think there is any recovery partition.
nilezon said:
Hmm, I didn't know that you could flash a recovery image to an Xperia phone:
Code:
fastboot flash recovery recovery.img
I don't think there is any recovery partition.
Click to expand...
Click to collapse
That's strange as it was flashing fine, and says success.
I'll reset back to stock firmware, then try again without flashing recovery.
creebefu said:
That's strange as it was flashing fine, and says success.
I'll reset back to stock firmware, then try again without flashing recovery.
Click to expand...
Click to collapse
You do that, but I am sure it will not boot anyway.
I think it's something wrong with the pre-built kernel, but I'm not sure.
M!tch said:
does the build from the op work?
Click to expand...
Click to collapse
creebefu said:
I've tried flashing the images in the OP and it just hangs when sending system. Have waited 30 minutes and still nothing.
Click to expand...
Click to collapse
nilezon said:
You do that, but I am sure it will not boot anyway.
I think it's something wrong with the pre-built kernel, but I'm not sure.
Click to expand...
Click to collapse
Thanks for testing guys. I STILL don’t have a Z5C so Im kind of useless atm. I did nothing to alter the code for my build, just sync and make.
Maybe try flashing zombie boot.img (I’m assuming ramdisk is from 32.0.A.5.32/R4B or similar? ) to get aosp to build.
Ill change the op with update that building straight from source produces non bootable rom/or kernel.
Also re the recovery partition: This is new to me as I’m coming from HTC where there was a designated recovery partition however I’m sure that when you flash a recovery.img to a Sony phone
Code:
fastboot flash recovery fotatwrp.img
for example, you are flashing it to the FOTAKernel partition, which is empty on an unlocked xperia because it used to handle the OEM OTA's, but is wiped upon unlocking the phone. The only way you can boot from this partition is to have extract-elf-ramdisk compiled in your ramdisk.cpio (source code) https://github.com/Dees-Troy/extract_elf_ramdisk. Or you can just have the recovery in the boot.img and boot in to recovery via fastboot.
Sony veterans please correct me if I’m wrong.
Some info.
https://twrp.me/devices/sonyxperiaz.html
Joeisgood99 said:
Sony veterans please correct me if I’m wrong.
Some info.
https://twrp.me/devices/sonyxperiaz.html
Click to expand...
Click to collapse
Thats untrue for Xperia Z5C ... It already has new bootloader and here is your recovery partition:
/dev/block/bootdevice/by-name/recovery
See Z5C official sourcecode
Sent from my mint using XDA Free mobile app
nilezon said:
Don't know. I didn't test.
BUT, FreeXperia has published suzuran (Z5C) build for 5.1.1:
http://fxpblog.co/aosp/aosp-5-1/
http://uploaded.net/file/rg3ocwy3/from/ub0dtu
I don't know if they work either, but I guess they usually does?
Click to expand...
Click to collapse
the op says, the build is working. but i guess it's not confirmed yet because it refers to you.
is there any other source to get information about the builds from fxp?
I am starting this thread to bring up AOSP/CAF based roms to our device gt-i9192 s4 mini duos.
This thread is for developers only and only rom building and rom bring up questions and discussions are allowed in this thread.
Best way is post the building errors, logcats, source code tree links here so that we all can help each other to fix the errors while building or rom booting.
For those who are keen to learn fixing bugs should read following article by great developer pawitp
https://medium.com/@pawitp/investigating-and-fixing-an-android-rom-bug-685f3e2e3806
Generally for aosp rom bring up - you need 2 files in your device trees
Code:
aosp_serranodsdd.mk
AndroidProducts.mk
like in other devices
See following commit to make your tree compatible with aosp
Code:
https://github.com/pawitp/android_device_samsung_i9082/commit/e5bf34bdfb42394e562ae66e068367dec38a6459
like this i have created one for us
Code:
https://github.com/i9192/android_device_samsung_serranodsdd/blob/n/aosp_serranodsdd.mk
https://github.com/i9192/android_device_samsung_serranodsdd/blob/n/AndroidProducts.mk
some of aosp roms need special files for their bring up like
for cm - cm.mk
for omni - omni_device.mk
for broken - broken.mk
for tipsy - tipsy.mk
for PA - pa_device.mk
for krexus - krexus_device.mk
for purenexus - pure_device.mk
All those who are building can post their questions, queries , bugs on this thread...we will fix them together
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
yes i was working on it but its now in the queue , display was blank but i was getting the logcat.
now i m working to build AOSP 6.0 , i got a sepolicy denial so i fixed it with this commit https://github.com/FaArIsH/platform...mmit/e35f718c7939b0f178bd1869396a472daa404075
but now i m getting this error
Code:
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for qtitetherservice.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.seemp.health.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.auth.securesampleauthdaemon.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.qseeproxysample.
i have removed the line vendor/aosp/sepolicy from msm8930-common and its now finished building but i don't think it will boot becasue i skipped the sepolicy error
DarkFrenzy said:
yes i was working on it but its now in the queue , display was blank but i was getting the logcat.
now i m working to build AOSP 6.0 , i got a sepolicy denial so i fixed it with this commit https://github.com/FaArIsH/platform...mmit/e35f718c7939b0f178bd1869396a472daa404075
but now i m getting this error
Code:
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for qtitetherservice.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.seemp.health.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.auth.securesampleauthdaemon.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.qseeproxysample.
i have removed the line vendor/aosp/sepolicy from msm8930-common and its now finished building but i don't think it will boot becasue i skipped the sepolicy error
Click to expand...
Click to collapse
use permissive mode for now and use sonyaosp sepolicy for time being...it builds fine and as we use permissive mode you get rid of major denials for boot.
post your logcat here
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
My device is defective, I will be sending him to repair and as soon as pick it back I'll get to work with n preview (to help).
tioguda said:
My device is defective, I will be sending him to repair and as soon as pick it back I'll get to work with n preview (to help).
Click to expand...
Click to collapse
great
aosp-caf
For CAF sources, should I use the regular CM device tree or AOSP? I am trying CM tree except for the aosp_serranodsdd and AndroidProducts..mk files.
How do you fix this properly?
Code:
build/core/Makefile:46: *** Prebuilt apk found in PRODUCT_COPY_FILES: device/samsung/serrano-common/prebuilt/Eleven.apk:system/app/Eleven/Eleven.apk, use BUILD_PREBUILT instead!. Stop.
I deleted the line in serrano-common.mk because I can't figure out how to use build_prebuilt
I am also getting stuck at this error:
Code:
*** No rule to make target `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicymanager_intermediates/export_includes', needed by `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes'. Stop.
One more question. Is there a general guide on how to troubleshoot these "No rule to make target" errors? It drives me crazy that usually both files the error message is referring to are in the "out" folder and I have no idea where the original command line is or what to do. I am also trying a PA build and that one keeps dying on me as well with this type of error just on a different file.
csendre said:
For CAF sources, should I use the regular CM device tree or AOSP? I am trying CM tree except for the aosp_serranodsdd and AndroidProducts..mk files.
How do you fix this properly?
Code:
build/core/Makefile:46: *** Prebuilt apk found in PRODUCT_COPY_FILES: device/samsung/serrano-common/prebuilt/Eleven.apk:system/app/Eleven/Eleven.apk, use BUILD_PREBUILT instead!. Stop.
I deleted the line in serrano-common.mk because I can't figure out how to use build_prebuilt
I am also getting stuck at this error:
Code:
*** No rule to make target `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicymanager_intermediates/export_includes', needed by `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes'. Stop.
One more question. Is there a general guide on how to troubleshoot these "No rule to make target" errors? It drives me crazy that usually both files the error message is referring to are in the "out" folder and I have no idea where the original command line is or what to do. I am also trying a PA build and that one keeps dying on me as well with this type of error just on a different file.
Click to expand...
Click to collapse
for caf or aosp build use cm tree...you need to fix your tree for errors.
for prebuilt apk error use following commit in build folder. Apply this commmit and it should build prebuild apks copies properly during build
https://github.com/i9192/platform_build/commit/6ceb823426e5f8b20fd39862013c909d37b415e9
Click to expand...
Click to collapse
for libaudiopolicyservice_intermediates error you need to set
BOARD_USES_GENERIC_AUDIO := false
Click to expand...
Click to collapse
flag in your boardconfig.mk
No rule to make target means something is missing on your device tree to build that particular thing.YOu need to search for it.
Like for audiopolicyservice error i search github for
SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes
Click to expand...
Click to collapse
and in issues i found a thread disccussing something...there someone told that you need to set that flag to get rid of error.
https://github.com/hak86/android_device_huawei_p8litekirin/issues/7
Click to expand...
Click to collapse
you need to search on google,xda,github, for this ...sometimes you need to ask cm team on their developer channel on irc, sometimes you need to discuss things with developers of that particular rom over their official community page like on google plus or something else...most of the time you will get the answer...and look for commits from good developers...like cm team, pawitp, purenexus, krexus, screwdaosp. Their commits most of the time show us the way.
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
Sorry for the intrusion on the topic (I'm not developer), but wish you good luck in your intention. Remember that we have a device that is the last of its class: Good and Compact.
I could buy another model, but I opted for a new battery. Two years using S4 Mini. And I will continue. Until all give up it.
While there are developers, S4 Mini will remain alive.
ADR USR said:
Sorry for the intrusion on the topic (I'm not developer), but wish you good luck in your intention. Remember that we have a device that is the last of its class: Good and Compact.
I could buy another model, but I opted for a new battery. Two years using S4 Mini. And I will continue. Until all give up it.
While there are developers, S4 Mini will remain alive.
Click to expand...
Click to collapse
yes... last of it's class really...i am willing to go beyond to keep this device alive.
after iphone se i thought android oems will introduce smaller devices but still nothing...
and if i can boot up aosp 7.0 then i think ...arco and others who are working on cm14 afterwords will support this device too.
why these libs are not building (there are not in the zip file nor in the our dir) does android N doesnt need them ?
libOmx*
liboverlay.so
libstagefrighthw.so
and few others
DarkFrenzy said:
why these libs are not building (there are not in the zip file nor in the our dir) does android N doesnt need them ?
libOmx*
liboverlay.so
libstagefrighthw.so
and few others
Click to expand...
Click to collapse
as i can see new n preview build system somehow does not build libstagefrighthw.so but it build libstagefright.so only..but all zips for preview builds for all devices have libstagefrighthw.so...i am working on that since last two days to build libstagefrighthw.so from source..but i guess we have to use it as prebuild file from cm 13 roms.
as i have compared...audio,media,display folders are not changed much in n preview so i guess we can safely use that prebuilt binary from cm 13 tree
UPDATE_
found the issue...it looks like cm repos we use does not build libstagefrighthw lib...i will fix this issue soon
Trying to build tipsy rom and the build dies when it gets to the kernel with the following error
Code:
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[4]: *** [scripts/mod/empty.o] Error 2
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
SHIPPED scripts/genksyms/parse.tab.c
I checked the staging area and build tools are present in the usual /prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin folder, so probably the path is not set right, but where is this set, how do I check it?
csendre said:
Trying to build tipsy rom and the build dies when it gets to the kernel with the following error
Code:
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[4]: *** [scripts/mod/empty.o] Error 2
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
SHIPPED scripts/genksyms/parse.tab.c
I checked the staging area and build tools are present in the usual /prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin folder, so probably the path is not set right, but where is this set, how do I check it?
Click to expand...
Click to collapse
add this line to BoardConfigCommon.mk or BoardConfig.mk
Code:
# Kernel Toolchain
KERNEL_TOOLCHAIN := $(ANDROID_BUILD_TOP)/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin
KERNEL_TOOLCHAIN_PREFIX := arm-eabi-
@DarkFrenzy thanks, this worked! This seems to be a workaround though, shouldn't this path be defined somewhere in the build directory?
This reminds me, does anyone know a guide/list with commands/parameters that can be set in boardconfig and device make files? Also, how do you decide if a configuration should be set in boardconfig.mk, device.mk or another make file?
I am stuck again. Should I remove fileutils completely considering it is part of CM and not aosp? If so, how? If i just delete it, I get "no rule to make file" type errors.
Code:
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:19: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:35: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:39: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:43: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:50: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:84: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:95: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/SerialNumber.java:20: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/SerialNumber.java:46: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:19: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:30: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:31: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:32: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:33: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:34: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:35: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:40: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:56: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:64: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:72: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:79: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:38: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:39: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:60: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:50: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:83: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:94: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:19: The import cyanogenmod cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:20: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:51: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:53: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:64: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:65: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:66: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:67: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:79: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:85: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:102: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:120: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:122: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:134: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:40: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:41: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:51: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:62: FileUtils cannot be resolved
make: *** [/home/endre/tipsy/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
make: *** Waiting for unfinished jobs....
csendre said:
I am stuck again. Should I remove fileutils completely considering it is part of CM and not aosp? If so, how? If i just delete it, I get "no rule to make file" type errors.
Click to expand...
Click to collapse
Revert that commit https://github.com/CyanogenMod/andr...mmit/afc6bd83906e04b939a1ed8c35b31d02cd631c48
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
Revert that commit https://github.com/CyanogenMod/andr...mmit/afc6bd83906e04b939a1ed8c35b31d02cd631c48
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
That was the first thing I tried because I remembered I had the same errors with AOKP when it was merged, but here for some reason it didn't help
csendre said:
That was the first thing I tried because I remembered I had the same errors with AOKP when it was merged, but here for some reason it didn't help
Click to expand...
Click to collapse
U should delete this file if it's there in cmhw DisplayColorCalibration.java
Edit: now I remembered u should revert this commit
https://github.com/CyanogenMod/andr...mmit/d8a7052baa47785c616774f8e2e9acea6246b23a
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
U should delete this file if it's there in cmhw DisplayColorCalibration.java
Edit: now I remembered u should revert this commit
https://github.com/CyanogenMod/andr...mmit/d8a7052baa47785c616774f8e2e9acea6246b23a
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
Yes, this looks to be the one. I'll try this evening.
Hi,
I'm trying to compile my first kernel, more specifically for nethunter on cm13. I've grabbed (what I think is) the source files from github: https://github.com/CyanogenMod/android_kernel_htc_m7/tree/cm-13.0
I've then applied the mac802 patch from the nethuner wiki and have just managed to place the HID patch. When i tried to compile I get the below error, I had a quick Google and it seems to be related to video drivers which seem pretty important to me. Anyone have any ideas how to fix please or point me in the right direction? I've tried searching for the specific warning: info may blah blah blah but that didn't retrieve anything useful.
Code:
drivers/video/msm/msm_fb.c: In function 'msm_fb_commit_thread':
drivers/video/msm/msm_fb.c:2637: warning: 'info' may be used uninitialized in this function
error, forbidden warning: msm_fb.c:2637
scripts/Makefile.build:307: recipe for target 'drivers/video/msm/msm_fb.o' failed
make[3]: *** [drivers/video/msm/msm_fb.o] Error 1
scripts/Makefile.build:443: recipe for target 'drivers/video/msm' failed
make[2]: *** [drivers/video/msm] Error 2
scripts/Makefile.build:443: recipe for target 'drivers/video' failed
make[1]: *** [drivers/video] Error 2
Makefile:951: recipe for target 'drivers' failed
make: *** [drivers] Error 2
EDIT: Worked it out, 'info' was a variable that wasn't being assigned in the source.
I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.
DelicatePanda said:
I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.
Click to expand...
Click to collapse
Put this in your local_manifest/roomservice.xml file :
<project path="vendor/oneplus" name="TheMuppet/proprietary_vendor_oneplus" revision="lineage=15.1" />
Click to expand...
Click to collapse
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.
casual_kikoo said:
Put this in your local_manifest/roomservice.xml file :
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.
Click to expand...
Click to collapse
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1
DelicatePanda said:
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1
Click to expand...
Click to collapse
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed
casual_kikoo said:
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed
Click to expand...
Click to collapse
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:
DelicatePanda said:
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:
Click to expand...
Click to collapse
You have some problem with jack-server :
FAILED: setup-jack-server
/bin/bash -c "(prebuilts/sdk/tools/jack-admin install-server prebuilts/sdk/tools/jack-launcher.jar prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 2>&1 || (exit 0) ) && (JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G" prebuilts/sdk/tools/jack-admin start-server 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update server prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 4.11.ALPHA 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-4.32.CANDIDATE.jar 4.32.CANDIDATE || exit 47 )"
Jack server already installed in "/home/user/.jack-server"
Launching Jack server java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G -cp /home/user/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
Jack server failed to (re)start, try 'jack-diagnose' or see Jack server log
No Jack server running. Try 'jack-admin start-server'
No Jack server running. Try 'jack-admin start-server'
Click to expand...
Click to collapse
In the root of your Android build directory
Code:
prebuilts/sdk/tools/jack-admin start-server
and then, straight after starting jack-server, relaunch your build process.
Also, judging from the log, jack-server is launching with 2G of RAM, which is very low IMO. If you have a low end PC, check this XDA thread, which explains you how to use Google Cloud for free to build ROM.
If you still have issues with jack-server, check this build guide by @nathanchance : there is a part about jack-server memory's problem (Ctrl + F -> "Jack issues").
Also, check a look at this Google Groups thread, this might help you.
Concerning TheMuppets : to be honest with you, I don't know exactly where files come from, BUT looking at commit messages on their Github, you can see, among others, that fourkbomb is pushing to this organization; a quick Google Search, you find his Github profile, he's a member of LineageOS. Also, you'll find a lot of ROMs builders TheMuppet' repo, so nothing to worry about (their repos are on Github, so you can check by yourself ).
I'm having a problem building the device flame and I keep running into this issue on pixeldust
does anyone know how to solve this error?
Spoiler: flame error
bootable/recovery/Android.mk: error: "librecovery_ui_ext (SHARED_LIBRARIES android-arm64) missing librecovery_ui_pixel (STATIC_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build
and this problem on coral, I have a feeling it's using python3 rather than python2 but idk how I should go about solving that error.
Spoiler: coral error
FAILED: /android/pd/out/target/common/obj/all-event-log-tags.txt
/bin/bash -c "build/make/tools/merge-event-log-tags.py -o /android/pd/out/target/common/obj/all-event-l
og-tags.txt frameworks/av/media/utils/EventLogTags.logtags frameworks/base/core/java/android/app/EventLogTags.logtag
s frameworks/base/core/java/android/app/admin/SecurityLogTags.logtags frameworks/base/core/java/android/content/Even
tLogTags.logtags frameworks/base/core/java/android/net/EventLogTags.logtags frameworks/base/core/java/android/os/Eve
ntLogTags.logtags frameworks/base/core/java/android/speech/tts/EventLogTags.logtags frameworks/base/core/java/androi
d/webkit/EventLogTags.logtags frameworks/base/core/java/com/android/internal/app/EventLogTags.logtags frameworks/bas
e/core/java/com/android/internal/logging/EventLogTags.logtags frameworks/base/core/java/com/android/server/DropboxLo
gTags.logtags frameworks/base/core/java/org/chromium/arc/EventLogTags.logtags frameworks/base/packages/SystemUI/src/
com/android/systemui/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
frameworks/base/services/core/java/com/android/server/am/EventLogTags.logtags frameworks/base/services/core/java/co
m/android/server/policy/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/wm/EventLogTags.l
ogtags frameworks/ex/common/java/com/android/common/GoogleLogTags.logtags frameworks/native/services/surfaceflinger/
EventLog/EventLogTags.logtags frameworks/opt/telephony/src/java/com/android/internal/telephony/EventLogTags.logtags
packages/apps/Settings/src/com/android/settings/EventLogTags.logtags packages/apps/TimeZoneUpdater/src/main/com/andr
oid/timezone/updater/EventLogTags.logtags packages/services/Car/car-internal-lib/src/com/android/internal/car/EventL
ogTags.logtags packages/services/Car/tests/CarDeveloperOptions/src/com/android/car/developeroptions/EventLogTags.log
tags system/bt/EventLogTags.logtags system/core/liblog/event.logtags system/core/libsysutils/EventLogTags.logtags sy
stem/core/logcat/event.logtags system/core/logd/event.logtags system/core/storaged/EventLogTags.logtags system/memor
y/lmkd/event.logtags vendor/qcom/opensource/commonsys/system/bt/EventLogTags.logtags"
File "/android/pd/build/make/tools/merge-event-log-tags.py", line 51
except getopt.GetoptError, err:
^
SyntaxError: invalid syntax
13:44:43 ninja failed with: exit status 1
Also, has anyone here tried building shapeshift os yet?