Hi everyone,
I'm trying to build stock AOSP for sailfish, but it keeps stopping at this point:
Code:
[ 12% 10854/89294] //external/vixl:libvixld-arm clang++ src/aarch32/disasm-aarch32.cc
full log here:
https://pastebin.com/3G87RbLX
Does anyone have any idea what's causing this?
Related
I am trying to figure out how to port the recently released 3.4.10 kernel to CM10.1 for our device (One XL evita). I am able to build CM10.1 from source and I am able to build standalone kernels.
So far I've build CM10.1 with the HTC linux 3.4.10 kernel sources in place of the CM10.1 kernel sources at kernel/htc/msm8960 and the build completed with no errors but the device won't boot. The screen won't even turn on. I knew it obviously wasn't going to be this simple but I am stuck on how to proceed.
The CyanogenMod "porting intro"
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
seems to indicate that you should be able to get CM up and running with any kernel. Can anyone give me some pointers on what the basic requirements are for a kernel to boot?
vanja_z said:
I am trying to figure out how to port the recently released 3.4.10 kernel to CM10.1 for our device (One XL evita). I am able to build CM10.1 from source and I am able to build standalone kernels.
So far I've build CM10.1 with the HTC linux 3.4.10 kernel sources in place of the CM10.1 kernel sources at kernel/htc/msm8960 and the build completed with no errors but the device won't boot. The screen won't even turn on. I knew it obviously wasn't going to be this simple but I am stuck on how to proceed.
The CyanogenMod "porting intro"
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
seems to indicate that you should be able to get CM up and running with any kernel. Can anyone give me some pointers on what the basic requirements are for a kernel to boot?
Click to expand...
Click to collapse
We're already working on it....
h8rift said:
We're already working on it....
Click to expand...
Click to collapse
H8 I know you guys are always hard at work on the ROM but I'm trying to learn about the process by having a go myself. You never know, If I get up to speed I may be able to help you guys out. I'm not expecting to just get a perfect kernel up and running, I'm just hoping to build something that I can boot and play around with.
Do you have any advice? Is there a set pathway to getting a kernel up and running or a checklist of things that need to be in place? Is there any way to debug the kernel when it won't boot?
So the kernel is booting but not turning the screen on. I've attached the last_kmsg.
This is a summary of the errors that I've found.
Code:
pm8xxx-regulator pm8xxx-regulator.5: Failed to find supply ext_5v
Failed to create debugfs directory
pm8xxx_vreg_probe: regulator_register failed: 8921_usb_otg, rc=-517
pm8xxx_vreg_probe: error for 8921_usb_otg, rc=-517
pm8xxx_vreg_probe: regulator_register failed: 8921_hdmi_mvs, rc=-517
pm8xxx_vreg_probe: error for 8921_hdmi_mvs, rc=-517
LED trigger bkl_trigger failed to register (-17)
fail to get slimbus logical address -6
pm_qos_param: network_latency setup failed
[BATT][BMS] r_sense=10,i_test=0,v[failure=2000
[SMD][PKT] smd_pkt_open: DATA5_CNTL open failed -19
smem_alloc failed ch=34
smem_alloc failed ch=35
...
binder: t->buffer binder_alloc_buf fail
binder: 157:544 transaction failed 29201, size 80-4
mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=0
Warning: unable to open an initial console.
Code:
WARNING: at /scr1/cm/system/kernel/htã/msm8960/fs/proc/generic.c:493 proc_register+0x148/0x1a8()
proc_dir_entry '/proc/emmc' already rdgistered
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock.c:185 clk_enable+0x58/0x210()
dsi1_s_p_clk: Don't call enable on unprepared clocks
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock-local.c:313 __branch_disable_reg+0x120/0x138()
dsi1_byte_clk status stuck at 'on'
WARNING: at /scr1/cm/system/kernel/htc/msm8960/fs/sysfs/dir.c:368 sysfs_add_one+0x7c/0x9c()
sysfs: cannot create duplicate filename '/dev/char/10:1'
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock-local.c:313 __branch_disable_reg+0x120/0x138()
dsi1_byte_clk status stuck at 'on'
I'm getting this build error when trying to compile CM-11.0. When this error occurs, I can try compiling again (brunch hammerhead) and the error will go away but pop up in another section as you can see in the pastebin. I've setup another directory where I re-synced the stock cm-11.0 repo and was able to complete the build. Upon installing the phone failed to boot, so I'm not sure what happened there (I think it was my proprietary files). The only changes I've made to the stock cm version are I've forked frameworks_base, apps_Settings, and the android manifest. I've been able to compile with the forks in the past, but when I forked the android manifest that's when this error started popping up.
Windows 8.1
VMWare : Ubuntu 13.10
Java : Initially was using Oracle version 7 but switched to openjdk 6 to try and troubleshoot
http://pastebin.com/rcPuGnXT
Solved: I've solved this issue but don't know why it was occurring in the first place. It was due to my lack of understanding of repo and git. When I was fetching and and merging the upstream changes, I wasn't committing and pushing those back to my forked repo. Once I did that everything went back to normal.
Sony uploaded the binaries for multiple Xperia devices, among others the Z3: http://developer.sonymobile.com/open-devices/list-of-devices-and-resources/
The build instructions can be found here: http://developer.sonymobile.com/ope...uild-aosp-nougat-for-unlocked-xperia-devices/
Does this mean, we can build AOSP now? I'd like to try out myself, but I won't have access to my PC for a couple of days. Has anyone else tried building and flashing it?
Edit: The Nougat binaries seem to point to the Marshmallow ones. Is this right? Pinging @jerpelea.
cypressious said:
Sony uploaded the binaries for multiple Xperia devices, among others the Z3: http://developer.sonymobile.com/open-devices/list-of-devices-and-resources/
The build instructions can be found here: http://developer.sonymobile.com/ope...uild-aosp-nougat-for-unlocked-xperia-devices/
Does this mean, we can build AOSP now? I'd like to try out myself, but I won't have access to my PC for a couple of days. Has anyone else tried building and flashing it?
Edit: The Nougat binaries seem to point to the Marshmallow ones. Is this right? Pinging @jerpelea.
Click to expand...
Click to collapse
I think that the good binaries, if you read, you can see that behind "Download AOSP Nougat (Android 7.0) binaries" it read please download Android 6.0.1.
Dumping insights as I try to build it myself.
If you get the error "unknown target -j", try setting the number of parallel processes via environment variable:
Code:
export MAKEFLAGS='-j8'
If you get Out of memory crashes with jack, try the tip from https://android.googlesource.com/platform/prebuilts/sdk/+/master/tools/README-jack-server.md:
Code:
jack-admin stop-server
export ANDROID_JACK_VM_ARGS="-Xmx4g -Dfile.encoding=UTF-8 -XX:+TieredCompilation"
Built the Rom, tried flashing it via fastboot which failed with "FAILED (remote: size too large)" and the phone was stuck on the Sony logo. I finally managed to boot into flash mode and reflash N Preview 4.
Next, I added
Code:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2143289344
to the BoardConfig.mk in /device/sony/leo and built again. Now I was able to flash system.img.
cypressious said:
Built the Rom, tried flashing it via fastboot which failed with "FAILED (remote: size too large)" and the phone was stuck on the Sony logo. I finally managed to boot into flash mode and reflash N Preview 4.
Next, I added
Code:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2143289344
to the BoardConfig.mk in /device/sony/leo and built again. Now I was able to flash system.img.
Click to expand...
Click to collapse
so, did it work? is the rom stable?
brenosabino said:
so, did it work? is the rom stable?
Click to expand...
Click to collapse
It's stable, but RIL and camera are mostly broken. The issues are discussed here: https://github.com/sonyxperiadev/camera/pull/20#issuecomment-244609398
Four days ago, Sony Developers posted the ZIP of Android 7.1 binaries for Xperia X devices. Knowing that X and Z devices shared the ZIP of Android 6.0.1 binaries, it will be possible to use this on our Z3 device? This is the link: http://developer.sonymobile.com/dow...oftware-binaries-for-aosp-nougat-android-7-1/
if there is interest I can make a build with GApps pre installed?
Would it be possible to build android 8.0 now for this?? Via the oreo build instructions?? https://developer.sonymobile.com/op...-build-aosp-oreo-for-unlocked-xperia-devices/
Edit: well just noticed kernel 4.4, so guess not, sad
Hey Guys,
Has anyone managed to build a user target GSI?
Meaning not a userdebug system build?
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
david3709 said:
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
Click to expand...
Click to collapse
What software tools are you using to build your ROM?
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
david3709 said:
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
Click to expand...
Click to collapse
david3709 said:
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
Click to expand...
Click to collapse
Using newer ROMs on older devices is going to cause lag, that is normal. The problem is not the ROM, the problem is your hardware wasn't designed to use newer, more demanding software.
yes, you are right, that is why i want to try android PIE, the reason for building AOSiP Pie is i want to do more practice, after more try, i can really build my own custom rom, right now what i only can do now is to rebuild some custom rom.