Database Develop

Sound problems with self-compiled JB/CM10 "Hackfest" ROM

Hello,
This is my first post on XDA and because of this I can't post in the Dev thread (although it's there that I would have asked this question).
I have followed the instructions to build the JB/CM10 "Hackfest" ROM from Benee's Github repo - and everything went well, the ROM's .zip file was properly built. Flashed it, booted up, etc.
It's working.. except the sound! I can't play anything. The logcat (attached) shows some errors (when trying to preview and select a different ring tone):
Code:
E/AudioTrack(1257): Could not get audio output for stream type 1
E/SoundPool(1257): Error creating AudioTrack
I didn't make any changes to the source files before compiling (fixed the error with the volume keys, and enabled the Torch (as per ICS instructions, because it didn't work in the "official" build). I was expecting to get the same thing with the "official" build, maybe except some optimizations.
So, is there anything else that I need to do/add/change, after synching Benee's sources, before building?
Thanks,
Alex
PS: this is my first time building a ROM, so..

I think there is an audio fix in Eagleblood ICS thread...maybe that can help you. :good:
Sent from my LG-P990hN using xda premium

JasonBourne.Qc said:
I think there is an audio fix in Eagleblood ICS thread...maybe that can help you. :good:
Sent from my LG-P990hN using xda premium
Click to expand...
Click to collapse
There was an audio problem initially with the JB/CM10 build, but it was fixed by Pastime1971. I checked, and I have those patches (they're in Benee's repo, already merged), so it should be OK from this point of view.
Last night I just did a "make cobbler" and restarted the build, and this morning it was not finished (no .zip file), and it stopped with apparently no error. I'll have to check what happened - in the mean time I "brunch 990" again over it just to see if it "continues" this time.
To sum up:
- install build environment (Debian 64bit VM, android-sdk, build tools + libraries, repo binary, etc)
- sync Benee's repo - all done
- add .repo/local_manifest.xml with just the vendor files (from Owen94's repo) && repo sync
- fix the Settings.System.VOLUME_KEY_CURSOR_CONTROL errors
- cd vendor/cm && ./get-prebuilts && cd ../../ && clear && . build/envsetup.sh && brunch p990
- wait for output
Is there anything else that I missed? Adding any other vendor files, files, patches or something like that in the repo? Or maybe I have to add anything else to the .zip after the build?
PS: yes, I double checked the ROM build instructions, and I don't seem to have missed any step, but maybe there is something so obvious that is not written there, and I don't know about

Solved!
I have update the .repo/local_manifest.xml with the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vendor_lge" path="vendor/lge" remote="vork" revision="ics"/>
</manifest>
replacing Owain's repo, and after a re-build, it appears to be working (that, or pure luck!)

[Q] Problem building solana for the first time

I'm trying to build cm10.1 for the first time. I picked solana as my target since I have one laying around not doing anything useful.
I set up my build environment (ubuntu 11.10, jdk6) and all that seemed to go ok. I initialized my repo and started syncing it and went to bed. When I got up this morning that looked like it had gone ok too, but when I tried to build no joy:
[email protected]:~/android$ lunch cm_solana-userdebug
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/motorola/solana/cm.mk]]: "vendor/motorola/solana/solana-vendor.mk" does not exist. Stop.
Device solana not found. Attempting to retrieve device repository from CyanogenMod Github (http:\\github.com/CyanogenMod).
Found repository: android_device_motorola_solana
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_motorola_solana already exists
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/motorola/solana/cm.mk]]: "vendor/motorola/solana/solana-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_solana'
** Do you have the right repo manifest?
Can anyone help? There's a build tutorial on the solana dev forum but its for AOKP and doesn't really help.
One thing that seems fishy to me is when I type just 'lunch' the list of targets only has 33 entries on it
Thanks!

Porting AOSP from source

ok, i'm trying to port and boot the AOSP source from google for 4.1.2 JB x86, first of all, i follow the next guide to build my own compiling machine http://forum.xda-developers.com/showthread.php?t=2762390 but i download in the step 12 the repo of google AOSP (repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r2.1 & repo sync)
Start the enviroment with: . build/envsetup.sh
and download download the source from motorola to get some propertary files http://sourceforge.net/projects/razr-i.motorola/files/LATAM/9.8.2I-50_SML-29/
now, the git have some instructions like you see in the README file inside the source, this say:
1. Create a workspace containing "vanilla" JB release from Google.
Done
Click to expand...
Click to collapse
ou may need to apply the following change in build repo to prevent the build from aborting when unexpected user tag is found on some modules:
[SOURCE] diff --git a/core/base_rules.mk b/core/base_rules.mk
index 3c11673..ecf611d 100644
--- a/core/base_rules.mk
+++ b/core/base_rules.mk
@@ -99,7 +99,7 @@ ifneq ($(filter $(LOCAL_MODULE_TAGS),user),)
$(warning * PRODUCT_PACKAGES section of)
$(warning * build/target/product/core.mk)
$(warning * )
- $(error user tag detected on new module - user tags are only supported on legacy modules)
+ $(warning user tag detected on new module - user tags are only supported on legacy modules)
endif
endif [/SOURCE]
i'm trying to do this step, but nothings seems happen...
The second step says that all we need is overlaying the Motorola repos on top of the AOSP repos, but in the Terminal i don't know some commands ('cause always i work on Windows ).
i need just a little help in here, i'm tryin to compare both sources, but in windows i've a tool called WINMERGE, in linux i don't know if we have something like that. I don't wanna overlay the repos, i want to compare the files and re-write the AOSP source with some parts of the motosource and get AOSP software with motorola hardware working.
thks to all, sorry for my bad english, i don't use translator

I always used meld. Meld is an 2to3 way comparing tool, that compares folders (date), files (versions) and text. It is almost like winmerge, just a little bit different. U can look it up in the app store of whatever ubuntu/linux version you have.
As for the defferences between aosp and moto. There are a number of differences. The most can be located in the system/core where moto has changed the behavior of how init works and some x86 implementations (especially pixelflinger). The next BIG thing is the bionic (libc). It has many x86 implementations and i am not sure if u can overlay them without trouble into aosp source.
Good luck!

Hazou said:
I always used meld. Meld is an 2to3 way comparing tool, that compares folders (date), files (versions) and text. It is almost like winmerge, just a little bit different. U can look it up in the app store of whatever ubuntu/linux version you have.
Click to expand...
Click to collapse
yeah, i'm using meld, it's amazig 'cause i can copy the files from one to another place, by the way, i'm using Ubuntu 14.04, with JVM 1.70 but 've some errors in the moment to build ...
As for the defferences between aosp and moto. There are a number of differences. The most can be located in the system/core where moto has changed the behavior of how init works and some x86 implementations (especially pixelflinger). The next BIG thing is the bionic (libc). It has many x86 implementations and i am not sure if u can overlay them without trouble into aosp source.
Good luck!
Click to expand...
Click to collapse
yeah, i see the both codes and check the changes, in some lines the works of moto it's amazing, but whe need more dev's to check all the changes to implement for porting ROMS
Lenovo has recently provided a software update which upgrades Android to version 4.3 for the k900, so i'm going to download the repo AOSP from google and later try to port 4.3

Help me compile and build a Lollipop kernel (currently BlissPop preferable)

I want to compile a kernel for lollipop, but I always get somekind of error... Can this be cause of toolchain that I use or cause sources from GitHub arent good? Do u have any recomendation on stable, working source, and toolchain that goes along with it? I compiled cm11 rom, but couldn't compile just a kernel... Do u have any nice tutorials on that, ones that i found arent working for me...
i tried with this toolchain gcc/linux-x86/arm/arm-eabi-4.6 from tutorial source.android.com/source/building-kernels.html

download the kernel source. in this tutorial we will use the cm-12.1 cyanogen kernel.
Code:
git clone -b cm-12.1 https://github.com/CyanogenMod/lge-kernel-p880
there now is a folder in your home 'lge-kernel-p880'
download a toolchain. for now i prefer the google aosp toolchain because i am not knowing the code of the cyanogen kernel. compiling with other toolchains and recenter releases (for example 4.9 5.0 5.1 5.1 and 6.0 needs a few changes and fixes in the coding else it will not complete compiling)
Code:
git clone -b aosp-4.8-arm-eabi https://github.com/ArchiDroid/Toolchain toolchain
now that u have both u are ready to compile.
in terminal cd to the downloaded source.
Code:
cd lge-kernel-p880
set some things up and start compiling
Code:
export ARCH=arm
export CROSS_COMPILE=/home/[B]yourubuntu-username[/B]/toolchain/bin/arm-eabi-
make cyanogenmod_x3_defconfig
start compiling
Code:
make -j4
Now sit back, relax, and watch the code! Or you could read a book, watch ****, count your fingers, play with your toes...
If you have an error during the waterfall of code, find the part where it actually says *error* (you'll probably have to scroll upwards) and search it on Google or post it here.
If you manage to get something that says "the kernel zImage is ready" or something like that, that means you've made it!
You have officially compiled your own kernel from source! Now you need to put it in a flashable zip with the .ko files.
As i dont know what .ko files cyanogenmod compiles u should find this out yourself.
it is probably listed in the end of the terminal when the compiling is finished
hope this will bring u further then you are now.

mistercheese said:
download the kernel source. in this tutorial we will use the cm-12.1 cyanogen kernel.
Code:
git clone -b cm-12.1 https://github.com/CyanogenMod/lge-kernel-p880
there now is a folder in your home 'lge-kernel-p880'
download a toolchain. for now i prefer the google aosp toolchain because i am not knowing the code of the cyanogen kernel. compiling with other toolchains and recenter releases (for example 4.9 5.0 5.1 5.1 and 6.0 needs a few changes and fixes in the coding else it will not complete compiling)
Code:
git clone -b aosp-4.8-arm-eabi https://github.com/ArchiDroid/Toolchain toolchain
now that u have both u are ready to compile.
in terminal cd to the downloaded source.
Code:
cd lge-kernel-p880
set some things up and start compiling
Code:
export ARCH=arm
export CROSS_COMPILE=/home/[B]yourubuntu-username[/B]/toolchain/bin/arm-eabi-
make cyanogenmod_x3_defconfig
start compiling
Code:
make -j4
Now sit back, relax, and watch the code! Or you could read a book, watch ****, count your fingers, play with your toes...
If you have an error during the waterfall of code, find the part where it actually says *error* (you'll probably have to scroll upwards) and search it on Google or post it here.
If you manage to get something that says "the kernel zImage is ready" or something like that, that means you've made it!
You have officially compiled your own kernel from source! Now you need to put it in a flashable zip with the .ko files.
As i dont know what .ko files cyanogenmod compiles u should find this out yourself.
it is probably listed in the end of the terminal when the compiling is finished
hope this will bring u further then you are now.
Click to expand...
Click to collapse
Ty for help, i tried it, it worked, i guess it was the toolchain the first time...
After that i compiled euphoria kernel, but with uber 5.2 which didnt work for cm kernel...
I had to change some < > to " ", why are sources set with wrong ones, or am i making some mistake?
I replaced only zImage with euphoria zImage in anykernel .zip, can something go wrong when i do it like that?

(SOLVED) Need help building LOS16

Hi,
I'm try building LOS16 for oxygen. I have used this wiki https://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html, but as brunch I have used lineage_16.0 and Ihave (I think I have) cloned all needed files from https://github.com/eva0034.
Than I have extracted the vendor blobs via ./extrcat-files.sh from my oxygen device.
When starting with 'breakfast oxygen' I get theses error messages:
[email protected]:~/android/system$ breakfast oxygen
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_oxygen".
15:35:13 dumpvars failed with: exit status 1
Device oxygen not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for oxygen not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_oxygen".
15:35:15 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_oxygen".
15:35:16 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_oxygen'
** Do you have the right repo manifest?
What is missing and why this: 'Device oxygen not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).' ??
Pls help

Hey. The linage-16 repository is missing the Oxygen device. Nobody leads him. One of the options to change the branch mido or tissot.

RedHat76 said:
Hey. The linage-16 repository is missing the Oxygen device. Nobody leads him. One of the options to change the branch mido or tissot.
Click to expand...
Click to collapse
What does it mean ? I can use a mido or tissot rom on my oxygen ?
Or how should/can I change the branch ?

I just told you that there is no branch of oxygen in the lineage. What to do next? I dont know. It can take a branch from mido from the repository and edit it. I am not a professional in this.

RedHat76 said:
I just told you that there is no branch of oxygen in the lineage. What to do next? I dont know. It can take a branch from mido from the repository and edit it. I am not a professional in this.
Click to expand...
Click to collapse
ah, OK, thx anyway