yashsingh1/xdaforums huggingface dataset:
[Android] dastin1015:
Both normally to get all the necessary proprietary files.

Personally I make unzip scripts and pull from CM9 and stock ROMs without the need of hooking my device up to the computer.

私のEVO 3Dから送信される。
[Android] CallMeVentus:
#define LOGD

"I have to go. It's just....they really need me." - Sora
[Android] djsubtronic:
Where do you put that line?
[Android] CallMeVentus:
You didn't show me the file , so I can't really tell you where , just put those below the other #define lines

"I have to go. It's just....they really need me." - Sora
[Android] djsubtronic:
Sorry I meant in general, cuz I seen this error happen at various times. I had found a workaround but not sure if it really worked, and I'm starting from scratch now.

So as I understand it goes directly into the source code of the file throwing the error?
[Android] Whippopotamus:
Ok, so I've just been trying to build this for armv6-vfp (Galaxy Ace), I got a device tree from ICS which was written by "MaclawStudios" (previously GalaxyICS), and I have managed to get past all the errors I've come across so far fine on my own, however, I now have this issue:

target thumb C: libc_common <= bionic/libc/bionic/semaphore.c
In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,
from bionic/libc/bionic/semaphore.c:33:
bionic/libc/private/bionic_atomic_arm.h:54:4: warning: #warning Rebuilding this source file in ARM mode is highly recommended for performance!! [-Wcpp]
bionic/libc/private/bionic_atomic_arm.h: In function '__sem_dec':
bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'
bionic/libc/private/bionic_atomic_arm.h: In function '__sem_trydec':
bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'
bionic/libc/private/bionic_atomic_arm.h: In function 'sem_post':
bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'
make: *** [out/target/product/cooper/obj/STATIC_LIBRARIES/libc_common_intermediates/bionic/semaphore.o] Error 1

All I have worked out is that on line 51, the __ATOMIC_CLOBBER is first defined with "r3", then later on in the __bionic_cmpxchg function, __ATOMIC_CLOBBERS "cc" is called, which I know makes the 'r3cc' error, because I changed the values and it changed accordingly, however, I don't know if they need to be split up or somehow (it does say list of clobbered registers when ATOMIC_CLOBBER is first defined), or if its a problem due to it not building in "ARM mode" - I guess I could be missing something from one of the arm makefiles, but I've had a look and I can't see anything, and I can't work out how it figured out whether its in arm mode anyway... lunch tells me:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=cooper
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.0.0-12-generic-x86_64-with-Ubuntu-11.10-oneiric
HOST_BUILD_TYPE=release
BUILD_ID=WHIPPO
OUT_DIR=out
============================================

Which seems fine to me...

Anyone have any ideas? :/

Edit: I think I've fixed it now, I think a missing dalvik file caused the problem... no idea how though! :)

Edit 2: The problem is still there, any suggestions?
[Android] ktempleton:
You need to get a boot.img and put it in that file
[Android] arbliss:
Can you expand on that? I guess I was reading

make: *** No rule to make target `out/target/product/d2usc/kernel', needed by `out/target/product/d2usc/boot.img'. Stop.

make: *** Waiting for unfinished jobs....

as saying that boot.img needs d2usc/kernel, meaning it couldn't find it. But I need to find a d2usc/boot.img on github or something?
[Android] ktempleton:
i have another machine building cm 10 i got that error and grabed a boot.img and put it in your case out/target/product/d2usc.. do you have a zip of a rom that you flash on your phone? if you do you can open it up and grab the boot.img from there..or if you can find a rom to download
[Android] emwno:
Quick question, where do I add a built boot.img to the source to make the compiling skip creating it? (testing out sme stuff)
[Android] ktempleton:
Did that get you moving along?
[Android] mg2195:
Anywhere you want...but you have to edit your device.mk to to recognize the location and copy it to the proper out directory....
[Android] arbliss:
Haven't done it yet, but i've got a cm10 i built i can grab the boot.img from. i'll give it a shot here. thank you! do i have to edit the device.mk?

EDIT: I am successfully building. Didn't do "exactly" what you said to do, but instead of the boot.img i grabbed the kernel from cm10 and moved it over. Pretty much the same solution, so I appreciate your help! It's building now, we'll see how it goes ; )
[Android] rubervalrfl:
This part already changed, changed the branch.

$ Cd working_directory

$ Repo init-b android-4.2_r1

$ Repo sync

Now is android-4.2_r1_

https://android.googlesource.com/platform/manifest/+/android-4.2_r1_
[Android] alteredlikeness:
I have a few issues with compiling PA (JB 4.1.2) for the Moto Edison, maybe someone has had similar issues or can point me in the right direction?? I have posted in the PA thread, but still have not figured it out...

First and foremost, my phone thinks it's a tablet - I can only see a corner of the actual UI at any time, and it's taking 768x1366 screenshots (my phone is supposed to be hdpi 540x960). PA Preferences don't help (that's why I think it might not be a PA specific issue) - is there somewhere to look in frameworks or elsewhere to set the actual device size? or maybe some of my device/vendor files are not getting included?

Other major issues which I noticed are:

- touch screen sensors are way off (might be related to the extra-large UI issue)

- wi-fi not working (hangs on scanning)

- capacitive soft keys not working

- no audio in phone calls

- no camera

It's still in the very early stages of development, but I was hoping someone with experience would see my issues and say "Hey, look in so-and-so, or check the whatchamacallit.." :D Thanks in advance..
[Android] rubervalrfl:
In fact, when it occurred to me it was because he had not executing the command. / Extract-files, which is inside the folder device, but device.mk have to be right too.
[Android] arbliss:
I did extract proprietary files using ./extract-files.sh, but my repo was definitely _r1

Not _r1_ . but it was building good before I left, so we shall see!
[Android] cbucz24:
OK, i'll rephrase this..maybe im asking wrong

in the OP it states "Change all references in your device repo from frameworks/base to frameworks/native"....

Ive looked everywhere, and I think I may have found it but im just not sure...

In the actual ./repo folder there is:

local_manifest.xml

manifest.xml

project.list

and a bunch of folders...looking in the manifest.xml and the other ones, there is a line

<project path="frameworks/base" name="CyanogenMod/android_frameworks_base" />

am I supposed to find all references similar to this and change to

<project path="frameworks/native" name="CyanogenMod/android_frameworks_base" />
[Android] mg2195:
Isn't the whole point of PA to make your phone look like its a tablet? edit: after re-readin i realise i misread this part...i now see your saying that not the whole screen is on the actuall screen...idk about that...something with wrong resolution maybe? -idk about a fix though...gotta be something in one of your device.mk files that points to resolution

Anyways...as for touch, if its like my infuse the issue will be located in frameworks/base/services/input...two files need to be edited, a couple pages back I listed the exact changes but they are hidden by some hide tags...so just look for a post by me that has a "button" that displays show...click on that button

The capacitive buttons are related to the hardware keys layout...forget the file that lists it but I think its either located in the device tree or kernel tree

No audio in phone called sounds like a ril issue...does audio work at all for anything else like music?

Camera...probably need some special configurations in your device tree/device.mk to get camera working...

WiFi...probably a WiFi driver issue...

That's the best I can help...I've never used or compiled PA...
[Android] mg2195:
i was right about my theory about having to edit the frameworks/base/core/res/res/values/config.xml for the missing overlay resources...but as you discovered cyanogenmod doesnt even have those resources...your best bet to add support for those is to find out which rom your device tree was used to compile...and check there frameworks/base/core/res/res/values/config.xml

th reason i know my theory was right is because in the process of making my own custom based rom i was able to add the reboot resources for my overlays in the corresponding frameworks files...(for the reboot options overlay i had to edit arrays.xml and strings.xml using cm10 as a reference)
[Android] kevin130:
frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: warning: missing initializer for member 'audio_policy_service_ops::open_output_on_module' [-Wmissing-field-initializers]

frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: warning: missing initializer for member 'audio_policy_service_ops::open_input_on_module' [-Wmissing-field-initializers]

make: *** [/home/kevin/CyanogenMod10.1/out/target/product/shooter/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioPolicyService.o] Error 1

make: *** Waiting for unfinished jobs....

Please and Thank you
[Android] Xistance:
After successfully building 4.2.1 CM for my device(I9001) it didn't boot. It got stuck on the kernel splash screen. My guess is that there is some changes I need to make to the ramdisk but I am not sure what to do as even after adding some changes all I got was a black screen after the splash. Any help on this? Thanks.
[Android] bobpantsspongesquare:
You're asking about building Cyanogenmod in an AOSP thread. Maybe try going to the CM website and asking them. Cyanogenmod is based off of AOSP but it isn't AOSP.
[Android] cbucz24:
You at least need to learn about logcat, make it your friend.

Power the device on, and start the log, it will show you what its getting stuck on.
[Android] CptanPanic:
Is there a way to build just a certain app? For example I just want to rebuild NfcNci.apk?
[Android] Kayant:
If you have already build the rom then you can use the mmm command. For example I make changes to in settings and just want to rebuild settings it will be mmm packages/apps/Settings.
[Android] Xistance:
I know at least that much. Logcat, ddms/android monitor, none of them work.
[Android] kevin130:
frameworks/av/media/libstagefright/colorconversion/SoftwareRenderer.cpp: In member function 'void android::SoftwareRenderer::render(void const*, size_t, void*)':

frameworks/av/media/libstagefright/colorconversion/SoftwareRenderer.cpp:153:70: error: too few arguments to function

frameworks/av/media/libstagefright/colorconversion/SoftwareRenderer.cpp:158:56: error: 'struct ANativeWindow' has no member named 'lockBuffer'

frameworks/av/media/libstagefright/colorconversion/SoftwareRenderer.cpp:256:67: error: too few arguments to function

make: *** [/home/kevin/CyanogenMod10/out/target/product/shooter/obj/STATIC_LIBRARIES/libstagefright_color_conversion_intermediates/SoftwareRenderer.o] Error 1

make: *** Waiting for unfinished jobs....

uhhhh lol im kinda at a stump.
[Android] mg2195:
Just out of curiosity...has anyone gotten the "android.com.phone.process has crashed" error? I may have gotten that error popup wrong..but its something like that. As soon as I boot the phone up with 4.2 it displays that error non-stop, as soon as you press OK to close it it will pop up again making it impossible to do anything...

I've been looking at log cats and if I can recall correctly it said something about a missing class with com.android.internal.telephony.iccprovider

I've tried many different things and nothing seems to work. There is a dev in my infuse section that has gotten past that bug, but he won't respond to ANY of my PMs...so if anyone has any info it would be great...I'll try and link the logcat later...

LOGCAT
[Android] Roladriz:
make <name of package> works too

cd packages/apps/Settings
make Settings
[Android] triptosyll:
No, hes technically asking about building cm, in a compiling thread. The tiltle does not state aosp, and lots of people have asked for and recieved help for other sources here... :p

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

Then ur having kernel problems I believe. Logcat wont show anything before a certain point in the boot process. There is some kind of log that will tell u whats going on before that point, but cant remember what it is. Never had to use it.

---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------

U know mg, I have had the problem before, but never attacked it from the debugging angle. Just changed my rom. The funny thing is, ive had it happen outta nowhere. Have a certain ROM on my phone for weeks, then wake up one morning to that error message and problem. Its funky indeed. Tho I have no helpful insight, sorry. :confused:
[Android] mg2195:
I think the log you are refernig to as last dmsg or kmsg...

Anyways, finally got an answer from the dev by posting in his thread instead of pming...well kinda, at least enough to get me going :) basically I need to merge a few patches into frameworks/opt/telephony and edit a line in my boardconfig...something about ICS ril and without the patches the phone is essentially looking for something that doesn't exist...attempting a build if it fixes the problem ill let out guys know what I did exactly :)
[Android] CptanPanic:
I am having a new problem. I can use adb when regular booted, but if I do adb reboot bootloader, to get to bootloader, adb cannot find the device anymore. This is with a Nexus 4, and I was previously able to use adb in bootloader, as I did it to root. Note I also tried having seperate lines for each ATTRS{idProduct} in the udev rules.

51-android-rules

SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0660", OWNER="myuser"

Nov 30 11:24:53 desktop-ubuntu kernel: [ 1039.762272] usb 2-1.7: USB disconnect, device number 14
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.050819] usb 2-1.7: new high-speed USB device number 15 using ehci_hcd
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.143937] usb 2-1.7: New USB device found, idVendor=18d1, idProduct=4ee2
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.143942] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.143944] usb 2-1.7: Product: Nexus 4
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.143947] usb 2-1.7: Manufacturer: LGE
Nov 30 11:24:57 desktop-ubuntu kernel: [ 1044.143949] usb 2-1.7: SerialNumber: XXXX
Nov 30 11:24:57 desktop-ubuntu mtp-probe: checking bus 2, device 15: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7"
Nov 30 11:24:57 desktop-ubuntu mtp-probe: bus: 2, device: 15 was an MTP device
Nov 30 11:25:44 desktop-ubuntu kernel: [ 1090.641281] usb 2-1.7: USB disconnect, device number 15

<adb reboot bootloader>

Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.674514] usb 2-1.7: new high-speed USB device number 16 using ehci_hcd
Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.773640] usb 2-1.7: New USB device found, idVendor=18d1, idProduct=4ee0
Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.773645] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.773647] usb 2-1.7: Product: Android
Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.773650] usb 2-1.7: Manufacturer: Google
Nov 30 11:25:48 desktop-ubuntu kernel: [ 1094.773652] usb 2-1.7: SerialNumber: XXXXX
Nov 30 11:25:48 desktop-ubuntu mtp-probe: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7"
Nov 30 11:25:48 desktop-ubuntu mtp-probe: bus: 2, device: 16 was not an MTP device
[Android] Roladriz:
Wondering if anyone has seen this before or knows how to fix?

frameworks/opt/telephony/src/java/com/android/internal/telephony/Phone.java:133: cannot find symbol
symbol : variable NETWORK_MODE_LTE_WCDMA
location: interface com.android.internal.telephony.RILConstants
int NT_MODE_LTE_WCDMA = RILConstants.NETWORK_MODE_LTE_WCDMA;
^

http://pastebin.com/0wfj7XnK

EDIT: Resync solved the problem. :)
[Android] AntiBillOS:
Please help find best choise for fix this problem (then builds gallery2):

http://pastebin.com/1gNDQUrV

Because i just delete (package/apps/gallery2) now.

#Sorry i dont translate last on log:

Ошибка - mean Error.

2. And can you help me fix next error? (its small. I past it here):

target thumb C++: libaudioflinger <= frameworks/av/services/audioflinger/AudioPolicyService.cpp
frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported
frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported
frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: sorry, unimplemented: non-trivial designated initializers not supported
frameworks/av/services/audioflinger/AudioPolicyService.cpp:1571:5: warning: missing initializer for member 'audio_policy_service_ops::open_input_on_module' [-Wmissing-field-initializers]
make: *** [/home/antibillos/android/jb/out/target/product/haida/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioPolicyService.o] Error 1
[Android] Albinoman:
Could someone help me fix this error http://paste.ubuntu.com/1403622/

Im building 4.2 AOSP for the verizon s3.
[Android] skywalker1162:
Hey guys I'm running into a problem here . I am syncing the repo of aokp from the main source . I leave it on for the night but when I see it in the morning it is stuck on receiving objects : 27% and this is the second time this happened although I can't say for sure why it happens . It just gets stuck there . Can anyone help me in this . Thanks

Skydragon Team
[Android] antonio8297:
After sync of jellybam suorce it say to me not found the "default.XML" and delete all.

Why????
[Android] triptosyll:
Kill the sync with 'CTRL' and 'c' and then do repo sync again. It should pick up where it left off. If not try again. I had problems like that about 5 times before mine sould completely sync. Cept mine would hang at 98%. Frustrating, it is.
[Android] Albinoman:
Any ideas anyone...
[Android] mg2195:
Just as the error says...you need a product name in the .mk file it has listed
[Android] Albinoman:
In d2-common or product-config? I don't know where I would add it to either of those.

Edit: Fixed it
[Android] DragunKorr:
Built 4.2.1 pure aosp for pyramid yet three drivers will not build for me

copybit.msm8660 \

gralloc.msm8660 \

hwcomposer.msm8660 \

Its in my msm8660.mk

and my libhardware is in place

Any help on this issue would surely be appreciated!
[Android] dastin1015:
The qcom/display in 4.2.1 is for 8960 devices. You need to use the CM one ad label it as qcom/display_legacy
[Android] andy572:
can anybody help me with my problem written in this forum?

http://xdaforums.com/showthread.php?t=2026783

i think its a mounting problem, but not sure.
[Android] AntiBillOS:
Any idea?
[Android] andy572:
Seems as its mixed code (C mixed in C++) there - most it is a "struct" inside a C++ method or Class without 'extern "C"'

surrounded.
[Android] DragunKorr:
Thanks still same issue maybe I don't have board configuration right!

Still not building my three files lol
[Android] EFFELEFFE:
Thanks for your tut, it worked great for me !
[Android] mg2195:
I believe what dastin was saying is that your issue is beyond your device tree and is located in the actual hardware/qcom areaish and he was telling you to pull cms and put it there

I had to do a similar thing to get touch working for me...had to edit two files in frameworks/services/input to match cm SL I could get touch (legacy touch)

*****************

On another note...anyone experience an unknown baseband with your compiled aosp? Any idea how to fix it? That's the only thing keeping my ROM unusable for the masses...baseband is unknown which results in no service...any help/tips are appreciated...I've been comparing the source with cm and have yet to find a fix...
[Android] DragunKorr:
Well we have cm booted

WiFi

Data

SD

Display

I just need my three files to build

And I will be at the same point!

Sorry just need to get her booted! Thanks
[Android] ktempleton:
I had the unknown baseband issue on a pacman build I just flashed my radio again.
[Android] mg2195:
i tried that earlier with heimdall and still had the issue...
[Android] Albinoman:
Can anyone help me with this error? I have my kernel in /kernel/samsung/d2

make: *** No rule to make target `out/target/product/d2vzw/kernel', needed by `out/target/product/d2vzw/boot.img'. Stop.
[Android] DragunKorr:
Board config is incorrect
[Android] Albinoman:
I have TARGET_KERNEL_SOURCE set to kernel/samsung/d2
[Android] DragunKorr:
Put a kernel file in out/ target/ product/Samsung

After fail

No make clean

Get the build going why you fix your config
[Android] Albinoman:
Ok I put a kernel in /out/target/product/d2vwz/kernel (had to make a kernel folder... Didn't have one)

New error
[Android] mg2195:
Why fix the config? because its the proper way...

you need to have this in your config

PRODUCT_COPY_FILES += \
device/samsung/d2/prebuilt/kernel:kernel

edit according to your setup...this part is the location of the prebuilt kernel "device/samsung/d2/prebuilt/kernel" this is the location for it to be copied in the out directory ":kernel"

seems like you may have a bad kernel/it was damaged when copying/moving -thats just my guess