Database Users

Guide to build cm10 needed

Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys

Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).

quetzalcoatl2435 said:
Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).
Click to expand...
Click to collapse
Hi. Correct me if I'm wrong, but I guess that the official CM repositories doesn't have branches later than CM7 for the olympus. You have to get them somewhere else for CM9 and later.

Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus

kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
I used "generic_olympus-userdebug" for the lunch command and afterwards the "cm_olympus-userdebug" appears among the options.
---------- Post added at 08:38 PM ---------- Previous post was at 08:30 PM ----------
quetzalcoatl2435 said:
Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus
Click to expand...
Click to collapse
Ooops, read too fast, my apologies...
I forked vendor, device and kernel repositories from CyanogenMod-Atrix github, but these are pre-alpha repos with known (and unknown) bugs. (BTW, though it compiles fine, the recovery won't install the resulting zip on my Atrix, still figuring out what's wrong)

ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.

kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
I'm not sure how to use the default.xml file in the link that quetzalcoatl2435 gave us, but in my case I created a local_manifest.xml file (from here) with the extra repos I needed and copied to .repo/local_manifest directory in the source tree root.
EDIT:
I think I got it, someone who really knows please confirm: instead of the deffault CM repo init, issue this: repo init -u git://github.com/epinter/android.git -b jb-olympus-new. Is that right?

OK for the time being i'm going to start rebuilding my repo again. i scratched everything so have to download the JB repo now. anyone with more info to using the Default.xml file or where it should be placed? Thanks guys
After looking at the Default.xml it seems he just added the Atrix to the list so i would assume i will copy paste and rerun repo sync? should i copy first then run repo sync or no?
All i have to say is thank you Verizon LTE with unlimited data and free tether LOL.

Don't use jb-olympus-new. That's for the new kernel and does not have the proprietary files included. You need to search for and add them manually.
Use this:
repo init -u git://github.com/epinter/android.git -b jb-olympus
repo sync
Assuming you've already installed all pre-requisites correctly, next do:
. build/envsetup.sh
lunch cm_olympus-userdebug
brunch olympus
Sent from my MB860 using xda app-developers app

kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.

kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
Just curious. Is this ROM going to be public?

quetzalcoatl2435 said:
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.
Click to expand...
Click to collapse
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git

Xerox98 said:
Just curious. Is this ROM going to be public?
Click to expand...
Click to collapse
How about you read the other threads before asking?

mapkel said:
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git
Click to expand...
Click to collapse
No need to add android_device_motorola_olympus.git to jb-olympus-new. It's already included by epinter. You only need to add the vendor files.
BTW, I was talking about the jb-olympus branch, not the jb-olympus-new branch.
The new branch is not for daily use (yet).

Thanks you guys. I had a github time out earlier so will be starting fresh here soon.
Sent from my Galaxy Nexus using xda app-developers app

And the countdown begins..... I have another 8gb of ram i removed thinking it was causing Build issues for my Gnex (turns out it was missing some blobs...oops) i'll be putting that back in before i start building. Going to start with a clone copy of this rom, Anyone know what happens with the new kernel and this? Yes i know it's alpha but i'm testing so that's what i need to focus on.

ok guys i went over this a few times and I found a few errors that i was able to fix by installing packages that were missing (13.04 64-bit btw). But i'm stuck on this one. anyone have any idea? this is after the Brunch olympus command. After more hunting on google seems i might need (sudo apt-get install libxml2-utils) so starting the Brunch again we'll see.

ravilov said:
How about you read the other threads before asking?
Click to expand...
Click to collapse
? I have pritty well read every post in the Atrix forum. I just wanted to know if this ROM would be made public when ready, so that there is another CM10 rom apart from Epinters.

this is from epinter's source. The first post says that i'm building this for fun and to help out if i can, and at some point down the road MAYBE be a public rom, my skills are limited and i don't feel at this stage that i'm rdy to release a ROM to the public, that's not saying i won't..just not soon. As for now i'm thinking i should be building this on 12.04 LTS because i keep running into Compiling errors... now i've got another one that's im trying to figure out.

Anyone have any idea's what i'm missing now lol.

Porting ROMs

How does one port ROMs to another phone? I'm looking to try and port Xylon to the Find 5.
Sent from my X909 using xda app-developers app

it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.

if you are building from source:
Find the 4.2.2 source code of the ROM you want to port
Get the manifest.
Add the CM10.1 device/kernel tree and proprietary libs in the .repo/local_manifest/roomservice.xml
sync all the repos
(do whatever the source might need you to set up: EG paranoid android, need you to setup your device properly in vendor/pa/* files)
compile. Fix any problems(maybe missing files, etc)
you could try a non-4.2.2-based ROM to port, but you'll run into more incompatibility issues to fix

mbh87 said:
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
Click to expand...
Click to collapse
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app

newbcake said:
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
No, build from source since it's available.

mbh87 said:
No, build from source since it's available.
Click to expand...
Click to collapse
You mean Oppo's source or AOSP from Google? I presume AOSP
Sent from my X909 using xda app-developers app

assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build

paperWastage said:
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
Click to expand...
Click to collapse
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]

newbcake said:
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
Click to expand...
Click to collapse
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first

paperWastage said:
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
Click to expand...
Click to collapse
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.

Well, I removed the HTC lines from manifest.xml (maybe not a good idea?) but anyway, it finished syncing after.

mbh87 said:
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Click to expand...
Click to collapse
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.

paperWastage said:
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
Click to expand...
Click to collapse
Understood. I'm syncing up the Cm10 now. Thanks!
Is is best to do this all on Linux, Mac, or Windows?

It isn't possible to do it on windows so one of the other two.

mbh87 said:
It isn't possible to do it on windows so one of the other two.
Click to expand...
Click to collapse
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app

newbcake said:
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup

paperWastage said:
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
Click to expand...
Click to collapse
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.

newbcake said:
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
Click to expand...
Click to collapse
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file/line might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast/lunch & mka

paperWastage said:
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast & mka
Click to expand...
Click to collapse
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.

newbcake said:
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
Click to expand...
Click to collapse
you could source the log for errors
or just run the compile script again and again.... the scheduler will continue building other packages, but it'll come to a point where it can't build anything else without that broken package.... and hence, the error in the log will be obvious(since everything else is already built, no logs from them)
it should be an error-free compile, but sometimes things could happen (a small tweak in package/A gives some problems when compiling with package/B)
I would say, most likely there's some build package incompatibility in your system.

Compiling i605

I can't get past this error
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/i605/omni_i605.mk]]: "device/samsung/l900/full_i605.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/i605/omni_i605.mk]]: "device/samsung/l900/full_i605.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_i605'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
real 0m0.122s
user 0m0.042s
sys 0m0.089s

apophis9283 said:
I can't get past this error
Click to expand...
Click to collapse
Do you have vendorsetup.sh in your /device/samsung/l900/ folder? If not, create it and put this in it:
Code:
add_lunch_combo omni_i605-userdebug
Do you have full_i605.mk in your device tree? Also, omni_i605.mk and i605.mk?

I had to put the i605 make file in the l900 folder. Doesnt make sense. After all that I got it to compile but no boot.
Sent from my SCH-I605 using Tapatalk 2

Also if l900 is important to build i605 then why doesnt it pull it when I brunch and pulls everything else?

apophis9283 said:
Also if l900 is important to build i605 then why doesnt it pull it when I brunch and pulls everything else?
Click to expand...
Click to collapse
Because nobody did a device bringup yet, so the compiler doesn't know that it needs some common stuff as well.
After examining the Omni repo: how can it pull i900 when the device tree does not exist in the Omni tree yet?
https://github.com/omnirom/

chasmodo said:
Because nobody did a device bringup yet, so the compiler doesn't know that it needs some common stuff as well.
After examining the Omni repo: how can it pull i900 when the device tree does not exist in the Omni tree yet?
https://github.com/omnirom/
Click to expand...
Click to collapse
Im looking at omniroms github. Android device samsung l900 is there and does have a kit kat tag. Its l900 not i900
l900 is Sprints note 2. i605 is Verizons Note 2. If having to put the i605 make file in the l900 folder is whats causing it not to boot, that means its compiling for l900 even though I want it to compile for i605. Something may be borked in build. No reason for i605 to depend on l900. Somethings just not right
Sent from my SCH-I605 using Tapatalk 2

apophis9283 said:
Its l900 not i900
Click to expand...
Click to collapse
Oh...sorry, I thought it was i900.
Anyway, you've got to create your l605 device tree and put all the l900-common references (if they exist) in it: take a look at n7100 or n7000 tree at Omni Github and you'll see what I'm talking about. There's no way for compiler to know what to do unless you tell it.

chasmodo said:
Oh...sorry, I thought it was i900.
Anyway, you've got to create your l605 device tree and put all the l900-common references in it: take a look at n7100 or n7000 tree at Omni Github and you'll see what I'm talking about. There's no way for compiler to know what to do unless you tell it.
Click to expand...
Click to collapse
My i605 folder looks identical to the way n7100 is setup. Its weird, It screams to have full_i605.mk put in the l900 device folder. It shoudlnt be doing this. Somethings borked.
All this over a typo. I found it. Compiling now without a l900 folder

In omni_i605.mk
Change
# Inherit device configuration
$(call inherit-product, device/samsung/l900/full_i605.mk)
change it to
# Inherit device configuration
$(call inherit-product, device/samsung/i605/full_i605.mk)

@apophis9283 I saw your post about No cell/data on the i605 nightly.. was that your build? SlimROM seems to have a working AOSP 4.4.2. Is there any chance that something from their project might help get OmniROM up and running on i605?
I would be willing to work on this, but have no experience or idea where to start.
Thanks.

travisn000 said:
@apophis9283 I saw your post about No cell/data on the i605 nightly.. was that your build? SlimROM seems to have a working AOSP 4.4.2. Is there any chance that something from their project might help get OmniROM up and running on i605?
I would be willing to work on this, but have no experience or idea where to start.
Thanks.
Click to expand...
Click to collapse
Data works on cm and aokp so far. I just havent looked any further into it yet. I got data on aokp by using cms device tree so i never isolated the actual problem. Omni requires an omni make file in the devices tree. So just need to pull in cms trees and make adjustments so omni will compile it
Sent from my SCH-I605 using Tapatalk 2

I quit messing with it. That roomservice file is annoying.
Sent from my SCH-I605 using Tapatalk 2

apophis9283 said:
I quit messing with it. That roomservice file is annoying.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
..does that mean pulling from the other projects won't work, or just won't work without ALOT of work? I don't know what the roomservice file is.. :?

I wanted to use a local manifest. Well when I tried to compile of course there were going to be errors but omnis response is to create the roomservice file. So its hard to tell what i may need to change around. The way aokp handles it is a million times better
Sent from my SCH-I605 using Tapatalk 2

Media-Caf Error

So now I am getting the below error while compiling Omni ROM:
hardware/qcom/media-caf/mm-video/vidc/venc/src/video_encoder_device.cpp:2450:17: error: 'struct venc_entropycfg' has no member named 'longentropysel'
Full Log:
http://hastebin.com/kudarekaqo.vhdl
Please help me in killing this last error

https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.

tilal6991 said:
https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.
Click to expand...
Click to collapse
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3

matrixzone said:
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
Click to expand...
Click to collapse
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.

tilal6991 said:
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
Click to expand...
Click to collapse
thanks man. How to see the code change from gerrit, checking the code change in github is very easy

Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.

chasmodo said:
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
Click to expand...
Click to collapse
In this particular case - look at the files changed by the commit and pull up the commit history for one of them - saves a lot of time.

Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.

Entropy512 said:
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
Click to expand...
Click to collapse
Also qcom devices that has "TARGET_QCOM_MEDIA_VARIANT := caf" in BoardConfig
I said that cause there are qcom devices that can work with no caf repos tbh..
An example would be Sony fusion3 devices.....
They worked on our android-4.4 branches perfectly fine prior to the qcom-4.4_2.7 merge
And fusion3 OmniROM/CyanogenMod Nightlies don't use any of the caf repos tbh . Though AOKP does

[HELP][Redmi Note 4G]ROM/Kernel assistance/queries

Hi all,
For all who just started developing for Redmi Note 4G, is compiling your very first ROM/Kernel and faced errors/need help/do not know what to do(for Redmi Note 4G only though sorry), or just have any questions about compiling ROM/Kernel for Redmi Note 4G, here is where it all goes! NOTE: Of course please do read through Android's ROM/Kernel tutorial and starting guide such as Beginner's tutorial, ROM build Tutorial, or CyanogenMod's ROM/Kernel tutorials such as Beginner's Porting Tutorial first, before you ask a question here as those tutorials addresses many basic questions that are likely to be repeatedly asked here. Do feel free to PM me too! I'll be glad to help because I've realized there is a heavy lack of help on ROM/Kernel building around when I just started myself, so I understand how difficult it is to solve everything yourself.

Trying to compile Kernel
I was trying compile kernel with a few custom governers but I am running into silly errors .I am using Xiaomi's kernel source.
I am following this guide. http://forum.xda-developers.com/showthread.php?t=2486098
Building on Ubuntu in a virtual machine.
Code:
[email protected]:~/android/kernel/Xiaomi_Kernel_OpenSource-dior-kk-oss/Xiaomi_Kernel_OpenSource-dior-kk-oss$ make ARCH=arm CROSS_COMPILE=/home/shubhamkarande/toolchains/arm-eabi-4.7/bin/arm-eabi- > compileLog
make: *** empty variable name. Stop.
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.

shubhamkarande said:
I was trying compile kernel with a few custom governers but I am running into silly errors .I am using Xiaomi's kernel source.
I am following this guide. http://forum.xda-developers.com/showthread.php?t=2486098
Building on Ubuntu in a virtual machine.
Code:
[email protected]:~/android/kernel/Xiaomi_Kernel_OpenSource-dior-kk-oss/Xiaomi_Kernel_OpenSource-dior-kk-oss$ make ARCH=arm CROSS_COMPILE=/home/shubhamkarande/toolchains/arm-eabi-4.7/bin/arm-eabi- > compileLog
make: *** empty variable name. Stop.
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
Click to expand...
Click to collapse
I am new to this coding so I have unbuntu 14 64 bit so from where should I start from
Sent from my HM NOTE 1LTEW using Tapatalk

suhasgta said:
I am new to this coding so I have unbuntu 14 64 bit so from where should I start from
Sent from my HM NOTE 1LTEW using Tapatalk
Click to expand...
Click to collapse
I don't have an idea why this is happening, you should probably download the full Android source tree and then compile with 'make -j16 bootimage', that way everything is more organised and safe from errors. Also it ensures the latest updates/bug fixes from Google/Cyanogenmod etc

You could also try the part source method by Philz: http://forum.xda-developers.com/android/development/huide-how-to-compile-philz-touch-6-t2862706 It's for compiling recoveries but works for kernel as well, it can save you several GBs of disk space but still ensure the latest updates/bug fixes

haoyangw said:
You could also try the part source method by Philz: http://forum.xda-developers.com/android/development/huide-how-to-compile-philz-touch-6-t2862706 It's for compiling recoveries but works for kernel as well, it can save you several GBs of disk space but still ensure the latest updates/bug fixes
Click to expand...
Click to collapse
How should a guy who is new to all this start I am sorry for troubling u again
Sent from my HM NOTE 1LTEW using Tapatalk

[/COLOR]
suhasgta said:
How should a guy who is new to all this start I am sorry for troubling u again
Sent from my HM NOTE 1LTEW using Tapatalk
Click to expand...
Click to collapse
You should follow a guide written of some elite devs on XDA. Just Google.
Sent from my HM NOTE 1LTE using Tapatalk

shubhamkarande said:
[/COLOR]
You should follow a guide written of some elite devs on XDA. Just Google.
Sent from my HM NOTE 1LTE using Tapatalk
Click to expand...
Click to collapse
Thank you I will
Sent from my HM NOTE 1LTEW using Tapatalk

suhasgta said:
How should a guy who is new to all this start I am sorry for troubling u again
Sent from my HM NOTE 1LTEW using Tapatalk
Click to expand...
Click to collapse
Here are some tutorials you should read(that's where I learnt to start, I started only this year XD): http://wiki.cyanogenmod.org/w/Build_for_a5 and http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_buildingDo note if you wish to download cm12.0 source code, you should use the command:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-12.0
instead of this(used int the tutorial): 'repo init -u https://github.com/CyanogenMod/android.git -b cm-12.1'. Before you do a 'repo sync', go to the directory where you did repo init and go to '.repo' and create a folder called 'local_manifests'. Then create a file called 'dior.xml'. Open the file and paste the following into it:
Code:
Also, instead of 'breakfast a5', you should do 'lunch cm_dior-eng', and instead of 'brunch a5', you should do 'make -j4 otapackage'. Also AVOID the './extract-files.sh' command and the './get-prebuilts' command, the local_manifest xml takes care of that and prebuilt apps are no longer used in CM12 and above.

@haoyangw What is the size of the complete CM source? I am low on bandwidth.Just 30GB a month.

shubhamkarande said:
@haoyangw What is the size of the complete CM source? I am low on bandwidth.Just 30GB a month.
Click to expand...
Click to collapse
I guess it's around 14gb
Sent from my HM NOTE 1LTEW using Tapatalk

If I'm not wrong around 20(at least for me)

haoyangw said:
If I'm not wrong around 20(at least for me)
Click to expand...
Click to collapse
How much is your data limit
Sent from my HM NOTE 1LTEW using Tapatalk

@suhasgta
It's 30 GB per month.After that,the speed drops drastically.
 @haoyangw Can I use this compressed source?
http://forum.xda-developers.com/android/development/source-cyanogenmod-source-highly-t3069473

shubhamkarande said:
@suhasgta
It's 30 GB per month.After that,the speed drops drastically.
@haoyangw Can I use this compressed source?
http://forum.xda-developers.com/android/development/source-cyanogenmod-source-highly-t3069473
Click to expand...
Click to collapse
Mines 75 gb but 50 is used already this month so I can't download it this month and this thing looks to be fake I don't but just my gut feeling
Sent from my HM NOTE 1LTEW using Tapatalk

suhasgta said:
Mines 75 gb but 50 is used already this month so I can't download it this month and this thing looks to be fake I don't but just my gut feeling
Sent from my HM NOTE 1LTEW using Tapatalk
Click to expand...
Click to collapse
Even I thought the same. I am thinking of syncing the source the way everyone on XDA does it. This will also ensure periodic builds for our devices.
Sent from my HM NOTE 1LTE using Tapatalk

That compressed source is outdated, it's for cm10.2(jellybean 4.3), so forget about it XD

I'm quite sure it won't reach 30GB because repo downloads compressed sources as well, just that the sources are not that compressed, so it should use about 14GB

Hey, I have finally managed to synced the complete source :highfive: but unable to build a working tree due to some stupid errors.
Code:
Fetching projects: 99% (527/532) Fetching project android_hardware_qcom_media
Fetching project android_hardware_qcom_media
Fetching project android_hardware_qcom_media
Fetching projects: 100% (532/532), done.
Syncing work tree: 2% (11/532) error: Your local changes to the following files would be overwritten by checkout:
admin/AppRestrictionEnforcer/Application/src/main/res/layout/fragment_setup_profile.xml
admin/AppRestrictionEnforcer/Application/tests/src/com/example/android/apprestrictionenforcer/tests/SampleTests.java
admin/BasicManagedProfile/Application/src/main/res/layout/fragment_setup_profile.xml
background/JobScheduler/Application/tests/AndroidManifest.xml
background/JobScheduler/Application/tests/src/com/example/android/jobscheduler/tests/SampleTests.java
build.gradle
connectivity/network/BasicNetworking/Application/tests/src/com/example/android/basicnetworking/tests/SampleTests.java
connectivity/network/NetworkConnect/Application/tests/src/com/example/android/networkconnect/tests/SampleTests.java
connectivity/network/NetworkConnect/template-params.xml
connectivity/nfc/BeamLargeFiles/Application/tests/AndroidManifest.xml
connectivity/nfc/BeamLargeFiles/build.gradle
connectivity/nfc/CardEmulation/Application/tests/AndroidManifest.xml
connectivity/nfc/CardReader/Application/tests/AndroidManifest.xml
connectivity/sync/BasicSyncAdapter/Application/src/main/java/com/example/android/basicsyncadapter/SyncAdapter.java
connectivity/sync/BasicSyncAdapter/Application/tests/src/com/example/android/basicsyncadapter/tests/SampleTests.java
content/WidgetData/Application/tests/AndroidManifest.xml
content/contacts/BasicContactables/Application/tests/src/com/example/android/basiccontactables/tests/SampleTests.java
content/documentsUi/StorageClient/Application/src/main/java/com/example/android/storageclient/StorageClientFragment.java
content/documentsUi/StorageClient/Application/tests/src/com/example/android/storageclient/tests/SampleTests.java
content/documentsUi/StorageClient/README.md
content/documentsUi/StorageClient/template-params.xml
media/BasicMediaRouter/Application/tests/src/com/example/android/basicmediarouter/tests/SampleTests.java
media/Camera2Basic/Application/tests/AndroidManifest.xml
media/Camera2Basic/Application/tests/src/com/example/android/camera2basic/tests/SampleTests.java
media/HdrViewfinder/template-params.xml
media/MediaBrowserService/Application/src/main/AndroidManifest.xml
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/MediaNotificationManager.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/MusicService.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/PackageValidator.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/model/MusicProvider.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/BitmapHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/LogHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/MediaIDHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/QueueHelper.java
media/MediaBrowserService/Application/src/main/res/drawable-hdpi/ic_notification.png
media/MediaBrowserService/Application/src/main/res/values/strings.xml
media/MediaBrowserService/Application/src/main/res/values/styles.xml
media/MediaBrowserService/template-params.xml
media/MediaRouter/Application/tests/AndroidManifest.xml
media/MediaRouter/Application/tests/src/com/example/android/mediarouter/tests/SampleTests.java
notification/BasicNotifications/Application/tests/src/com/example/android/basicnotifications/tests/SampleTests.java
notification/LNotifications/Application/tests/AndroidManifest.xml
notification/MessagingService/template-params.xml
renderScript/BasicRenderScript/Application/tests/src/com/example/android/basicrenderscript/tests/SampleTests.java
renderScript/BasicRenderScript/template-params.xml
renderScript/RenderScriptIntrinsic/Application/tests/src/com/example/android/renderscriptintrinsic/tests/SampleTests.ja
error: The following untracked working tree files would be overwritten by checkout:
admin/DeviceOwner/Application/.gitignore
admin/DeviceOwner/Application/README-fragmentview.txt
admin/DeviceOwner/Application/README-singleview.txt
admin/DeviceOwner/Application/proguard-project.txt
admin/DeviceOwner/Application/src/main/AndroidManifest.xml
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/DeviceOwnerFragment.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/DeviceOwnerReceiver.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/InstructionFragment.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/MainActivity.java
admin/DeviceOwner/Application/src/main/res/drawable-hdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-mdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-xhdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-xxhdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/layout/activity_main_real.xml
admin/DeviceOwner/Application/src/main/res/layout/fragment_device_owner.xml
admin/DeviceOwner/Application/src/main/res/layout/fragment_instruction.xml
admin/DeviceOwner/Application/src/main/res/values/strings.xml
admin/DeviceOwner/Application/src/main/res/xml/device_owner_receiver.xml
admin/DeviceOwner/build.gradle
admin/DeviceOwner/buildSrc/build.gradle
admin/DeviceOwner/gradle/wrapper/gradle-wrapper.jar
admin/DeviceOwner/gradle/wrapper/gradle-wrapper.properties
admin/DeviceOwner/gradlew
admin/DeviceOwner/gradlew.bat
admin/DeviceOwner/screenshots/1-main.png
admin/DeviceOwner/screenshots/icon-web.png
admin/DeviceOwner/settings.gradle
admin/DeviceOwner/template-params.xml
admin/NfcProvisioning/Application/.gitignore
admin/NfcProvisioning/Application/README-fragmentview.txt
admin/NfcProvisioning/Application/README-singleview.txt
admin/NfcProvisioning/Application/proguard-project.txt
admin/NfcProvisioning/Application/src/main/AndroidManifest.xml
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/NfcProvisioningFragment.java
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/ProvisioningValuesLoader.java
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/TextWatcherWrapper.java
admin/NfcProvisioning/Application/src/main/res/drawable-hdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-mdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-xhdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-xxhdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/layout/fragment_nfc_provisioning.xml
admin/NfcProvisioning/Application/src/main/res/values/strings.xml
admin/NfcProvisioning/Application/tests/src/com/example/android/nfcprovisioning/tests/SampleTests.java
admin/NfcProvisioning/build.gradle
admin/NfcProvisioning/buildSrc/build.gradle
admin/NfcProvisioning/gradle/wrapper/gradle-wrapper.jar
admin/NfcProvisioning/gradle/wrapper/gradle-wrapper.properties
admin/NfcProvisioning/gradlew
admin/NfcProvisioning/gradlew.bat
admin/NfcProvisioning/nfcprovisioning.txt
admin/NfcProvisioning/screenshots/1-main.png
admin/NfcProvisioning/screenshots/icon-web.png
admin/NfcProvisioning/settings.gradle
admin/NfcProvisioning/template-params.xml
connectivity/bluetooth/BluetoothAdvertisements/Application/.gitignore
connectivity/bluetooth/BluetoothAdvertisements/Application/proguard-project.txt
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/AndroidManifest.xml
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/bluetoothadvertisements/AdvertiserFragment.java
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/bluetoothadvertisements/Constants.java
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/
Aborting
Syncing work tree: 6% (32/532) error: The following untracked working tree files would be overwritten by checkout:
src/compatibility/4.4/android-4.4-cdd.xhtml
src/compatibility/5.0/android-5.0-cdd.html
Please move or remove them before you can switch branches.
Aborting
Syncing work tree: 100% (532/532), done.
developers/samples/android/: discarding 23 commits
docs/source.android.com/: discarding 2 commits
error: developers/samples/android/: platform/developers/samples/android checkout 5aa1d659c86cf7851d85d33108e4c761a02cf817
error: docs/source.android.com/: platform/docs/source.android.com checkout cfd98ed5e9570d76b5a50d77e51318211777dcfb
What should I do? :/

shubhamkarande said:
Hey, I have finally managed to synced the complete source :highfive: but unable to build a working tree due to some stupid errors.
Code:
Fetching projects: 99% (527/532) Fetching project android_hardware_qcom_media
Fetching project android_hardware_qcom_media
Fetching project android_hardware_qcom_media
Fetching projects: 100% (532/532), done.
Syncing work tree: 2% (11/532) error: Your local changes to the following files would be overwritten by checkout:
admin/AppRestrictionEnforcer/Application/src/main/res/layout/fragment_setup_profile.xml
admin/AppRestrictionEnforcer/Application/tests/src/com/example/android/apprestrictionenforcer/tests/SampleTests.java
admin/BasicManagedProfile/Application/src/main/res/layout/fragment_setup_profile.xml
background/JobScheduler/Application/tests/AndroidManifest.xml
background/JobScheduler/Application/tests/src/com/example/android/jobscheduler/tests/SampleTests.java
build.gradle
connectivity/network/BasicNetworking/Application/tests/src/com/example/android/basicnetworking/tests/SampleTests.java
connectivity/network/NetworkConnect/Application/tests/src/com/example/android/networkconnect/tests/SampleTests.java
connectivity/network/NetworkConnect/template-params.xml
connectivity/nfc/BeamLargeFiles/Application/tests/AndroidManifest.xml
connectivity/nfc/BeamLargeFiles/build.gradle
connectivity/nfc/CardEmulation/Application/tests/AndroidManifest.xml
connectivity/nfc/CardReader/Application/tests/AndroidManifest.xml
connectivity/sync/BasicSyncAdapter/Application/src/main/java/com/example/android/basicsyncadapter/SyncAdapter.java
connectivity/sync/BasicSyncAdapter/Application/tests/src/com/example/android/basicsyncadapter/tests/SampleTests.java
content/WidgetData/Application/tests/AndroidManifest.xml
content/contacts/BasicContactables/Application/tests/src/com/example/android/basiccontactables/tests/SampleTests.java
content/documentsUi/StorageClient/Application/src/main/java/com/example/android/storageclient/StorageClientFragment.java
content/documentsUi/StorageClient/Application/tests/src/com/example/android/storageclient/tests/SampleTests.java
content/documentsUi/StorageClient/README.md
content/documentsUi/StorageClient/template-params.xml
media/BasicMediaRouter/Application/tests/src/com/example/android/basicmediarouter/tests/SampleTests.java
media/Camera2Basic/Application/tests/AndroidManifest.xml
media/Camera2Basic/Application/tests/src/com/example/android/camera2basic/tests/SampleTests.java
media/HdrViewfinder/template-params.xml
media/MediaBrowserService/Application/src/main/AndroidManifest.xml
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/MediaNotificationManager.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/MusicService.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/PackageValidator.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/model/MusicProvider.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/BitmapHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/LogHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/MediaIDHelper.java
media/MediaBrowserService/Application/src/main/java/com/example/android/mediabrowserservice/utils/QueueHelper.java
media/MediaBrowserService/Application/src/main/res/drawable-hdpi/ic_notification.png
media/MediaBrowserService/Application/src/main/res/values/strings.xml
media/MediaBrowserService/Application/src/main/res/values/styles.xml
media/MediaBrowserService/template-params.xml
media/MediaRouter/Application/tests/AndroidManifest.xml
media/MediaRouter/Application/tests/src/com/example/android/mediarouter/tests/SampleTests.java
notification/BasicNotifications/Application/tests/src/com/example/android/basicnotifications/tests/SampleTests.java
notification/LNotifications/Application/tests/AndroidManifest.xml
notification/MessagingService/template-params.xml
renderScript/BasicRenderScript/Application/tests/src/com/example/android/basicrenderscript/tests/SampleTests.java
renderScript/BasicRenderScript/template-params.xml
renderScript/RenderScriptIntrinsic/Application/tests/src/com/example/android/renderscriptintrinsic/tests/SampleTests.ja
error: The following untracked working tree files would be overwritten by checkout:
admin/DeviceOwner/Application/.gitignore
admin/DeviceOwner/Application/README-fragmentview.txt
admin/DeviceOwner/Application/README-singleview.txt
admin/DeviceOwner/Application/proguard-project.txt
admin/DeviceOwner/Application/src/main/AndroidManifest.xml
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/DeviceOwnerFragment.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/DeviceOwnerReceiver.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/InstructionFragment.java
admin/DeviceOwner/Application/src/main/java/com/example/android/deviceowner/MainActivity.java
admin/DeviceOwner/Application/src/main/res/drawable-hdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-mdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-xhdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/drawable-xxhdpi/ic_launcher.png
admin/DeviceOwner/Application/src/main/res/layout/activity_main_real.xml
admin/DeviceOwner/Application/src/main/res/layout/fragment_device_owner.xml
admin/DeviceOwner/Application/src/main/res/layout/fragment_instruction.xml
admin/DeviceOwner/Application/src/main/res/values/strings.xml
admin/DeviceOwner/Application/src/main/res/xml/device_owner_receiver.xml
admin/DeviceOwner/build.gradle
admin/DeviceOwner/buildSrc/build.gradle
admin/DeviceOwner/gradle/wrapper/gradle-wrapper.jar
admin/DeviceOwner/gradle/wrapper/gradle-wrapper.properties
admin/DeviceOwner/gradlew
admin/DeviceOwner/gradlew.bat
admin/DeviceOwner/screenshots/1-main.png
admin/DeviceOwner/screenshots/icon-web.png
admin/DeviceOwner/settings.gradle
admin/DeviceOwner/template-params.xml
admin/NfcProvisioning/Application/.gitignore
admin/NfcProvisioning/Application/README-fragmentview.txt
admin/NfcProvisioning/Application/README-singleview.txt
admin/NfcProvisioning/Application/proguard-project.txt
admin/NfcProvisioning/Application/src/main/AndroidManifest.xml
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/NfcProvisioningFragment.java
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/ProvisioningValuesLoader.java
admin/NfcProvisioning/Application/src/main/java/com/example/android/nfcprovisioning/TextWatcherWrapper.java
admin/NfcProvisioning/Application/src/main/res/drawable-hdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-mdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-xhdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/drawable-xxhdpi/ic_launcher.png
admin/NfcProvisioning/Application/src/main/res/layout/fragment_nfc_provisioning.xml
admin/NfcProvisioning/Application/src/main/res/values/strings.xml
admin/NfcProvisioning/Application/tests/src/com/example/android/nfcprovisioning/tests/SampleTests.java
admin/NfcProvisioning/build.gradle
admin/NfcProvisioning/buildSrc/build.gradle
admin/NfcProvisioning/gradle/wrapper/gradle-wrapper.jar
admin/NfcProvisioning/gradle/wrapper/gradle-wrapper.properties
admin/NfcProvisioning/gradlew
admin/NfcProvisioning/gradlew.bat
admin/NfcProvisioning/nfcprovisioning.txt
admin/NfcProvisioning/screenshots/1-main.png
admin/NfcProvisioning/screenshots/icon-web.png
admin/NfcProvisioning/settings.gradle
admin/NfcProvisioning/template-params.xml
connectivity/bluetooth/BluetoothAdvertisements/Application/.gitignore
connectivity/bluetooth/BluetoothAdvertisements/Application/proguard-project.txt
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/AndroidManifest.xml
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/bluetoothadvertisements/AdvertiserFragment.java
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/bluetoothadvertisements/Constants.java
connectivity/bluetooth/BluetoothAdvertisements/Application/src/main/java/com/example/android/
Aborting
Syncing work tree: 6% (32/532) error: The following untracked working tree files would be overwritten by checkout:
src/compatibility/4.4/android-4.4-cdd.xhtml
src/compatibility/5.0/android-5.0-cdd.html
Please move or remove them before you can switch branches.
Aborting
Syncing work tree: 100% (532/532), done.
developers/samples/android/: discarding 23 commits
docs/source.android.com/: discarding 2 commits
error: developers/samples/android/: platform/developers/samples/android checkout 5aa1d659c86cf7851d85d33108e4c761a02cf817
error: docs/source.android.com/: platform/docs/source.android.com checkout cfd98ed5e9570d76b5a50d77e51318211777dcfb
What should I do? :/
Click to expand...
Click to collapse
Did you make any important changes? If you didn't then just do this:
Code:
repo forall -vc "git reset --hard"
And do repo sync again, it will now work