[Q] cm11 repo error sync - Android Q&A, Help & Troubleshooting

when i try to repo sync my cm11 build fro the s4 i get an error which is this
Syncing work tree: 78% (351/450) AndroidManifest.xml: needs merge
res/layout/installed_app_details.xml: needs merge
res/values/pa_arrays.xml: needs merge
res/values/pa_strings.xml: needs merge
res/xml/settings_headers.xml: needs merge
src/com/android/settings/applications/InstalledAppDetails.java: needs merge
error: you need to resolve your current index first
Syncing work tree: 100% (450/450), done.
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout 2dd150bc2a78e3af8cd83f00787fbd1754bdafb2
i recently tried cherry picking halo from AOSPA which im assuming why im getting the repo sync error BUT I was not able to....can somebody help me on how to fix the problem

Related

[Q] repo, AOSP, & make

I'm not sure if this is the place to ask this, but I've been playing with building AOSP over the past week. I've got everything synced, ccache, and have built it 4 times. But I have a few questions:
My process: First I "repo init -u <insert proper google url> -b android-4.2.1_r1.2" for the latest 4.2 branch as opposed to just "repo init -u <insert proper google url>" for the master branch, then I do a "repo sync", then I initiate the build "make clean -j9 otapackage".
Questions:
1. By doing repo init with the 4.2.1_r1.2 branch, when I build it, does that ensure that I am building from that branch? So you have to repo init for whatever branch you want to build and the make knows which branch to compile from?
2. If I repo init many branches, and sync those branches to my computer, I can do a make on them later without syncing, as long as I did the init command just before the make command? Of course, I may no longer be in sync with the main repository, but I'll still be building the code as it was previousely? I.e. there is no need to sync before each build as long as you are happy with the code currently on your machine?
3. How often do the branches change? It seems each day I sync and get new projects, etc.
4. Should I do "make -j1" instead of "make -j9"? The latter does the build in under an hour and the former make take several hours. Is it really likely that using multiple thread will cause errors? Could I check that by just compiling the code with "-j9" a few times in a row without a repo sync in order to compare the builds to see if they have the same md5 or something?
I'm still trying to figure out how to get my build to incorporate certain proprietary binaries that are not included in the AOSP. I know I can get these binaries from my phone, or from factory images, or elsewhere (I'm building for my Verizon galaxy nexus - toro). Can I just drop them into the flashable zip? Or is it better to incorporate them into your local code with modifications to the make files that will automate compiling them into the build and otapackage? I have been doing some research on that and think I am almost to the point where I know which make files to modify. Any clues or hints are greatly appreciated.
Also, is there a way to make the otapackage odexed? Or does the phone automatically make the odex files as you run all the apps? <-that's the impression I get after doing some reading.

[Q] Can't sync Liquidsmooth source

While trying to sync liquidsmooth after running init it goes on and all sudden it needs some manifest and wants me to repo init again..
I build carbon rom just fine so i know how to.

Repo sync and change of branches

Hi guys,
I regularly run into problems when I try to resync custom rom repos after a while. Sometimes the intended branch in a git repository changes, but a repo sync won't checkout the branch. Is this normal behaviour or a specific problem of my roms manifest?
D802 @ AOSPA 4.4

CM-13 compilation error: no rule to make target '/.txt'

Hello,
I've got this error a couple of days ago using cm-13 branch, so I redownloaded the source again using the stable branch (cm-13.0-ZNH0E), but I still get this error:
Code:
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
I get this error even if I try to compile for the emulator (m_e_arm-userdebug).
I've searched on google for days. I know that there are also other ppl that have this problem (here: http://forum.xda-developers.com/chef-central/android/rule-to-make-target-txt-t3329468), but he is using an exotic source tree, while I'm 100% clean from stable branch.
I've also created a thread on cyanogen forum (here: http://forum.cyanogenmod.org/topic/123259-cant-compile-cm130-for-mini-emulator-x86-userdebug/)
Anyone solved this problem?
I get that error too. Hope CM team would resolve the issue soon.
Update: Switched to stable/cm-13.0-ZNH2K branch and to master revision of cmsdk prebuilts - the problem is solved.

Errors syncing Cyanogenmod source and building rom.

I am trying to follow this guide:
Code:
https://wiki.cyanogenmod.org/w/Build_for_h901#What_you.E2.80.99ll_need
in order to build cyanogenmod for my H901, but after the initial repo sync "completed" without error, i follow the guide through breakfast and the the file extraction, and brunch fails to build all targets. after this, doing repo sync again gives me this:
Code:
Fetching projects: 99% (524/529) Fetching project CyanogenMod/android_hardware_qcom_display
Fetching project CyanogenMod/android_hardware_qcom_display
Fetching project CyanogenMod/android_hardware_qcom_display
fatal: Couldn't find remote ref refs/heads/cm-13.0
error: Cannot fetch CyanogenMod/android_kernel_lge_pplus
error: Exited sync due to fetch errors
I want to say this is due to the v10 not being a "supported device" for CM13 yet, as it is not listed on the lunch menu. but i was running the test builds in the dev section just fine, and i'm sure it's a fairly simple matter to pull the right stuff from git, but i'm a newbie to this kind of development.
After successfully building from source, i want to build a custom rom based on CM13 and keep the LG stock camera app, and the LGSignboard second screen function, and gain all the Cyanogenmod goodies too. any help or guidance with that quest would be appreciated.
I really hope someone can answer this for you.. :/
I think, you are trying to sync cm-13.0 branch of cyanogenmod lge_pplus kernel repo in your local manifest. But this is not there. Its only the cm-12.1 branch there: https://github.com/CyanogenMod/android_kernel_lge_pplus. For cm-13 you will need a different kernel source path. Hopefully there are already cm-13 roms for your device and with sources on github, where from you can sync?
Okay, that makes sense.
I was following a guide on CM wiki to build CM13 for the v10, why would that branch not be present on github if there is a guide to build from it?
I'll poke around github and xda for available kernel source.
Sent from my LG-H901 using XDA-Developers mobile app

Categories

Resources