hello
I have a problem with the creation of the manifest file for Sailfish os
in the documentation of sailfish os is that one should make it so :
You’ll have to create the local manifest yourself, which contains at least two repos: one for the kernel,
another for the device configuration. Find those CM device wiki, for Nexus 5 it would be http://wiki.
cyanogenmod.org/w/Hammerhead_Info inside the Source code table. Local manifest below will also
need pointing to correct branches - identify which one matches the default manifest branch.
Add the following content to $ANDROID_ROOT/.repo/local_manifests/$DEVICE.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/hammerhead"
name="CyanogenMod/android_device_lge_hammerhead"
revision="stable/cm-11.0" />
<project path="kernel/lge/hammerhead"
name="CyanogenMod/android_kernel_lge_hammerhead"
revision="stable/cm-11.0" />
</manifest>
Time to sync the whole source code, this might take a while:
HABUILD_SDK $
hadk
repo sync --fetch-submodules
that is my manifest named kenzo_mm.xml :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/kenzo"
name="CyanogenMod/android_device_xiaomi_kenzo"
revision="cm-13.0" />
<project path="kernel/xiaomi/msm8956"
name="CyanogenMod/android_kernel_xiaomi_msm8956"
revision="cm-13.0" />
</manifest>
as described is the file in the folder
/home/xxxxxxxx/ANDROID_ROOT/.repo/local_manifests/kenzo_mm.xml
when i try repo init or sync I get error message :
[Error02] repo-about-git-head-error-manifest-missing-or-unreadable-please-run-init
thanx 4 Help
greetz
I helped myself , I thank you for helping all who helped me
noobstyle1337 said:
I helped myself , I thank you for helping all who helped me
Click to expand...
Click to collapse
Hey man, I have the same issue, what's the fix?
Benjimaestro said:
Hey man, I have the same issue, what's the fix?
Click to expand...
Click to collapse
I have the manifest file pushed into the .repo folder and could then sync
but now I have the next problem I if
wants breakfast kenzo do then I have another error with the manifest file
I have also downloaded to github all things kenzo per zip download and pulled in $ home / android folder and could then run extract-file.sh what not hasnt
I bite me through
somehow it seems to be so easy in the tutorial but the capabilities are not steps you have to tinker immediately until it works .
totally frustrating for me
all manifests are bull**** I start again
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
did you set the path to the ndk/sdk
export NDK=<path>/android-ndk
export ANDROID_NDK=<path>/android-ndk
export ANDROID_HOME=<path.d/android-sdk-linux
might not be 100% correct since it's been awhile since I compiled anything for android
noobstyle1337 said:
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Hi, i've got the same error trying to breakfast the device. Did you find a way to fix this error ? Thanks you a lot !
I have fixed the problem . it was the roomservice.xml . manifest file . which is really huge and there is much to write
I also have the mount points fixed but the problem is the build that he believed break CM13 is supported not right i think
unfortunately I have no internet in the Moment, I change to o2 I germany 'm working on it maybe I find the error during build if I may give you the tip a look here in redmi note 3 forum to the manifest file which is to build ads of nougat . which helped a lot you need you can take the frameworks , security almost everything . you have to test it unfortunately if I have internet again I can even upload my manifest file
noobstyle1337 said:
unfortunately I have no internet in the Moment, I change to o2 I germany 'm working on it maybe I find the error during build if I may give you the tip a look here in redmi note 3 forum to the manifest file which is to build ads of nougat . which helped a lot you need you can take the frameworks , security almost everything . you have to test it unfortunately if I have internet again I can even upload my manifest file
Click to expand...
Click to collapse
Thank you a lot. I will try giving a look to nougat manifest waiting for your manifest.
View attachment roomservice.xml.tar.gz
here is the manifest file
repo init -u git://github.com/mer-hybris/android.git -b hybris-13.0
but I do not know if you also hybris repos add intended or whether to remain in the default xml so but it will run first
otyg said:
did you set the path to the ndk/sdk
export NDK=<path>/android-ndk
export ANDROID_NDK=<path>/android-ndk
export ANDROID_HOME=<path.d/android-sdk-linux
might not be 100% correct since it's been awhile since I compiled anything for android
Click to expand...
Click to collapse
I had the paths not set thanks
noobstyle1337 said:
View attachment 3880405
here is the manifest file
repo init -u git://github.com/mer-hybris/android.git -b hybris-13.0
but I do not know if you also hybris repos add intended or whether to remain in the default xml so but it will run first
Click to expand...
Click to collapse
Hi ! Did you managed to run without errors the breakfast command with your manifest ? I tried it, but unfortunately I got always the same error.
Thank you in advance
it runs without error one should manifest the add before the repo sync
** Don't have a product spec for: 'cm_kenzo'
noobstyle1337 said:
have again and start to point 5.4 everything works repo init has also but when I breakfast kenzo enter I get this error
including vendor/cm/vendorsetup.sh
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
Device kenzo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_xiaomi_kenzo
Default revision: stable/cm-13.0-ZNH0E
Checking branch info
Default revision stable/cm-13.0-ZNH0E not found in android_device_xiaomi_kenzo. Bailing.
Branches found:
cm-13.0
stable/cm-13.0-ZNH5Y
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
device/xiaomi/kenzo/BoardConfig.mk:185: device/qcom/sepolicy/sepolicy.mk: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
/bin/bash: prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
make: *** No rule to make target 'device/qcom/sepolicy/sepolicy.mk'. Stop.
** Don't have a product spec for: 'cm_kenzo'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
just saying...if thats the prob the solution is inside decive source,rename the "cm.mk" to "cm_kenzo.mk"...i had this prob lately and i solved it in that way :good:
Related
Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
InfinityFTW said:
Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
Click to expand...
Click to collapse
You need to clone device tree
Code:
cd android
cd device
mkdir htc
cd htc
git clone git://github.com/InfinityFTW/android_device_htc_pyramid.git -b jellybean pyramid
Then you need extract propietary files
Code:
cd pyramid
./extract-files.sh
And finally type
Code:
. build/envsetup.sh
lunch "select your device"
make -j4
Enviado desde mi X10i
Building error?
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
hey im trying to work my way thru the same thing...there is a lot of info out there, it takes forever to sort your way thru it..
so...first off, it helps us figure out problems with its output..do what it says.
sudo apt-get install schedtool
start there, then try again and see what comes up next
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
first of all
HTML:
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
there is a software missing install it next...
HTML:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
it has found pyramid/cm.mk required for building but your device is configured to use the common config of msm8660 cpu so its looking for
msm8660-common
in device folder
htc
therefore find the common config download it via zip rename the folder containing the files to
msm8660-common
copy and paste it in htc folder then follow the previuos commands... i will subscribe to this thread if you get any more errors post on this thread i will be happy to help
Thanks for everything, guys, and i have now attempted to build
i used otapackage, and it seems to have stopped. Here is the latest output:
Code:
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1956: error: undefined reference to 'msm_get_voc_session'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1961: error: undefined reference to 'msm_start_voice_ext'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1962: error: undefined reference to 'msm_set_voice_tx_mute_ext'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1982: error: undefined reference to 'msm_end_voice_ext'
collect2: ld returned 1 exit status
make: *** [/home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so] Error 1
[email protected]:~/android/system$
just the last few lines wont help post more of what happened before the breaking of the build
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
speed_bot said:
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
Click to expand...
Click to collapse
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
you dont need to delete and resync again instead do
PHP:
make clean
and
HTML:
make clobber
to delete all compiled files and if you have modified the source do
HTML:
git checkout
it will remove all local changes that was you can save time and bandwidth ...
---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------
InfinityFTW said:
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
Click to expand...
Click to collapse
propeitary files and just vendors for the device they cant break the build process///
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Racing19969 said:
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Click to expand...
Click to collapse
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
if thats the error your sources havent synced completely yet
It probably would not build, coz when it gives you to choose you will choose cm_* and it will build cm10.To buil PAC you need to choose pac_*
If I am not right please correct me.
Code:
Erachter system # lunch
You're building on Linux
Breakfast menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. mini_armv7a_neon-userdebug
5. mini_armv7a-userdebug
6. full_panda-userdebug
7. cm_a700-userdebug
8. cm_anzu-userdebug
9. cm_captivatemtd-userdebug
10. cm_crespo-userdebug
11. cm_crespo4g-userdebug
12. cm_coconut-userdebug
13. cm_d2att-userdebug
14. cm_d2mtr-userdebug
15. cm_d2spr-userdebug
16. cm_d2tmo-userdebug
17. cm_d2usc-userdebug
18. cm_d2vzw-userdebug
19. cm_encore-userdebug
20. cm_endeavoru-userdebug
21. cm_epicmtd-userdebug
22. cm_everest-userdebug
23. cm_evita-userdebug
24. cm_fascinatemtd-userdebug
25. cm_galaxysbmtd-userdebug
26. cm_galaxysmtd-userdebug
27. cm_grouper-userdebug
28. cm_haida-userdebug
29. cm_hallon-userdebug
30. cm_hercules-userdebug
31. cm_i777-userdebug
32. cm_i9100-userdebug
33. cm_i9100g-userdebug
34. cm_i9300-userdebug
35. cm_iyokan-userdebug
36. cm_jewel-userdebug
37. cm_maguro-userdebug
38. cm_mako-userdebug
39. mr1-staging
40. cm_mango-userdebug
41. cm_manta-userdebug
42. cm_mesmerizemtd-userdebug
43. cm_mint-userdebug
44. cm_n7000-userdebug
45. cm_n7100-userdebug
46. cm_n8000-userdebug
47. cm_n8013-userdebug
48. cm_p1c-userdebug
49. cm_p1l-userdebug
50. cm_p1n-userdebug
51. cm_p1-userdebug
52. cm_p3-userdebug
53. cm_p3100-userdebug
54. cm_p3110-userdebug
55. cm_p4-userdebug
56. cm_p4tmo-userdebug
57. cm_p4vzw-userdebug
58. cm_p4wifi-userdebug
59. cm_p5100-userdebug
60. cm_p5110-userdebug
61. cm_p930-userdebug
62. cm_p970-userdebug
63. cm_quincyatt-userdebug
64. cm_quincytmo-userdebug
65. cm_satsuma-userdebug
66. cm_skyrocket-userdebug
67. cm_smultron-userdebug
68. cm_stingray-userdebug
69. cm_su640-userdebug
70. cm_t769-userdebug
71. cm_tf101-userdebug
72. cm_tf201-userdebug
73. cm_tf300t-userdebug
74. cm_tf700t-userdebug
75. cm_toroplus-userdebug
76. cm_toro-userdebug
77. cm_urushi-userdebug
78. cm_vibrantmtd-userdebug
79. cm_ville-userdebug
80. cm_wingray-userdebug
81. pac_anzu-userdebug
82. pac_haida-userdebug
83. pac_mango-userdebug
84. pac_mint-userdebug
85. pac_smultron-userdebug
86. pac_urushi-userdebug
87. pac_zeus-userdebug
88. pac_zeusc-userdebug
89. pac_hercules-userdebug
90. pac_i9100-userdebug
91. pac_i9100g-userdebug
92. pac_quincyatt-userdebug
93. pac_skyrocket-userdebug
94. pac_cooper-userdebug
95. pac_grouper-userdebug
96. pa_crespo-userdebug
97. pa_grouper-userdebug
98. pa_maguro-userdebug
99. pa_toro-userdebug
100. pa_toroplus-userdebug
That shouldn't be a prob coz its just configuring hardware to software and pac is based on cm and aokp and aokp is inturn based on cm so I doubt this part causing problems in the future
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
InfinityFTW said:
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
Click to expand...
Click to collapse
ok see if the libhardware is working or not means like they patch the hardware to make the rom boot see if anybody has patched it
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
szl.kiev said:
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
Click to expand...
Click to collapse
Do I curl it into my device repo?
Sent from my GT-P3113 using Tapatalk 2
Hey guys,
I ran into a problem while trying to build CM10.1 for the i9100 from source.
this is the tutorial I am following http://wiki.cyanogenmod.org/w/Build_for_i9100
I managed to sync the sources, but when I try to run
Code:
breakfast i9100
I get the following EError Messages
Code:
[email protected]:~/android/system/cyanogenmod/cm-10.1_source$ breakfast i900
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/i900/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i900". Stop.
Device i900 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for i900 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
ls: cannot access device/*/i900/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i900". Stop.
** Don't have a product spec for: 'cm_i900'
** Do you have the right repo manifest?
I attached my "manifest.xml" from .repo
Is there anyone who had the same problem? I think I'm missing something.
Best regards mofeywalker
I am having trouble building a new checkout of the CM10.1 sources. I built CM10 successfully some months ago, but somehow, things have changed... I've checked out a completely fresh copy from git, into a fresh VM, just to eliminate chances I could've borked things on the previous CM build VM.
Code:
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (...).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_samsung_i9100 already exists
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
since i saw other guys (in the dev forum, where i can't post to at the moment) having the exact same issue:
do a "repo selfupdate" before you run breakfast!
after the selfupdate, do "repo sync"... and then try again with breakfast, all will be well
im using this
http://wiki.cyanogenmod.org/w/Build_for_hammerhead#Install_the_SDK
i have reached the step where i have to type $ breakfast hammerhead
i have tryed a couple of time but it keeps saying
Code:
[email protected]:~/android/system$ breakfast hammerhead
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hammerhead/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hammerhead". Stop.
Device hammerhead not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_hammerhead
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_lge_hammerhead. Bailing.
Branches found:
cm-11.0
stable/cm-11.0
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hammerhead/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hammerhead". Stop.
** Don't have a product spec for: 'cm_hammerhead'
** Do you have the right repo manifest?
[email protected]:~/android/system$
i have no idea what to do now, i have just finished the repo sync!
I need to add the SMSC95XX drivers to the Linux Kernel in an AOSP for the Moto-Z. Can someone tell me how one builds the Linux Kernel then the AOSP for the Moto-Z?
Thx,
Y-
YileKu said:
I need to add the SMSC95XX drivers to the Linux Kernel in an AOSP for the Moto-Z. Can someone tell me how one builds the Linux Kernel then the AOSP for the Moto-Z?
Thx,
Y-
Click to expand...
Click to collapse
Hello,
to include the driver download the kernel sources from here:
https://github.com/boulzordev/android_kernel_motorola_msm8996
and change
Code:
# CONFIG_USB_NET_SMSC95XX is not set to
to
Code:
CONFIG_USB_NET_SMSC95XX=Y
in "arch/arm64/configs/griffin_defconfig"
Something like
Code:
sed "/CONFIG_USB_NET_SMSC95XX/d" -i arch/arm64/configs/griffin_defconfig/griffin_defconfig && echo "CONFIG_USB_NET_SMSC95XX=y" >> arch/arm64/configs/griffin_defconfig/griffin_defconfig
should do the job ( run these inside the cloned kernel repo )
Moto-Z AOSP newbie
Thanks for the pointer. I can do that. I have built AOSP for the Nexus-6, but I have not built it for the Moto-Z Droid. Can someone point me to the general instructions on how to build for the Moto-Z?
CHeers,
Y-
Maybe can build MIUI for the Moto-Z?
rakee said:
Maybe can build MIUI for the Moto-Z?
Click to expand...
Click to collapse
Building miui has 2 way :
Building with rompatch and porting from similar device (Mi5 is good for for moto z) (it's not very common and certain way)
Here's patchrom link : https://github.com/MiCode/patchrom/branches
Patchrom latest version is marshmallow and it's too late to start building most of the people is updated to nuogat so they can't install MM kernel
But about second way (porting), I've tried this but no success to boot I got some errors on netlink uevent
So we need to wait for patchrom to get nougat update and I'll try porting it if I didn't buy new phone
rakee said:
Maybe can build MIUI for the Moto-Z?
Click to expand...
Click to collapse
I don't recognize 'MIUI' what is meant by this?
YileKu said:
I don't recognize 'MIUI' what is meant by this?
Click to expand...
Click to collapse
MIUI is a custom ROM from china
Any chance I can build a ROM for the Moto-Z from here https://source.android.com/source/building-kernels?
StarStorm said:
Hello,
to include the driver download the kernel sources from here:
https://github.com/boulzordev/android_kernel_motorola_msm8996
and change
Code:
# CONFIG_USB_NET_SMSC95XX is not set to
to
Code:
CONFIG_USB_NET_SMSC95XX=Y
in "arch/arm64/configs/griffin_defconfig"
Something like
Code:
sed "/CONFIG_USB_NET_SMSC95XX/d" -i arch/arm64/configs/griffin_defconfig/griffin_defconfig && echo "CONFIG_USB_NET_SMSC95XX=y" >> arch/arm64/configs/griffin_defconfig/griffin_defconfig
should do the job ( run these inside the cloned kernel repo )
Click to expand...
Click to collapse
Thanks StarStorm,
After making these changes, how does one build the ROM with the new kernel?
Y-
YileKu said:
Thanks StarStorm,
After making these changes, how does one build the ROM with the new kernel?
Y-
Click to expand...
Click to collapse
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
StarStorm said:
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
Click to expand...
Click to collapse
StarStorm,
Thanks for the direction. I am a bit of a newbie on this so I want to verify the steps:
1. Follow the instructions at https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484, up to the point you do the 'repo init'
2. Use the repo init command 'repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat' instead.
3. Add the following repos to my manifest: https://github.com/boulzordev/androi...torola_griffin and https://github.com/boulzordev/propri...torola_griffin
4. Skip the 'extract-files.sh' command
5. do a 'repo sync' command
6. Modify the linux kernel to include the driver
7. follow the instructions for building at: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t355148
thx,
Y-
YileKu said:
StarStorm,
Thanks for the direction. I am a bit of a newbie on this so I want to verify the steps:
1. Follow the instructions at https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484, up to the point you do the 'repo init'
2. Use the repo init command 'repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat' instead.
3. Add the following repos to my manifest: https://github.com/boulzordev/androi...torola_griffin and https://github.com/boulzordev/propri...torola_griffin
4. Skip the 'extract-files.sh' command
5. do a 'repo sync' command
6. Modify the linux kernel to include the driver
7. follow the instructions for building at: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t355148
thx,
Y-
Click to expand...
Click to collapse
Yep, looks good to me :good:
StarStorm said:
Yep, looks good to me :good:
Click to expand...
Click to collapse
I did the repo init command and I was looking to add the repos to the manifest. The only file I found was .repo/manifest.xml, it didn't seem obvious how to add the two repos above.
Y-
StarStorm said:
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
Click to expand...
Click to collapse
When I did the 'breakfast lineage_griffin-userdebug'
I get:
.......
* [new branch] cm-14.1 -> github/cm-14.1
Fetching projects: 100% (5/5), done.
Checking out files: 100% (52729/52729), done.
Syncing work tree: 100% (5/5), done.
Looking for dependencies in kernel/motorola/msm8996
Dependencies file not found, bailing out.
Looking for dependencies in external/bson
Dependencies file not found, bailing out.
Looking for dependencies in external/stlport
Dependencies file not found, bailing out.
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Looking for dependencies in packages/resources/devicesettings
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/android/system$
YileKu said:
When I did the 'breakfast lineage_griffin-userdebug'
I get:
.......
* [new branch] cm-14.1 -> github/cm-14.1
Fetching projects: 100% (5/5), done.
Checking out files: 100% (52729/52729), done.
Syncing work tree: 100% (5/5), done.
Looking for dependencies in kernel/motorola/msm8996
Dependencies file not found, bailing out.
Looking for dependencies in external/bson
Dependencies file not found, bailing out.
Looking for dependencies in external/stlport
Dependencies file not found, bailing out.
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Looking for dependencies in packages/resources/devicesettings
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
Did you add https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your manifest? What does your local manifest look like?
YileKu said:
I did the repo init command and I was looking to add the repos to the manifest. The only file I found was .repo/manifest.xml, it didn't seem obvious how to add the two repos above.
Y-
Click to expand...
Click to collapse
You aren't supposed to modify .repo/manifest.xml , add your local changes to .repo/local_manifests.xml ( with the same syntax as manifest.xml uses )
StarStorm said:
Did you add https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your manifest? What does your local manifest look like?
Click to expand...
Click to collapse
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/moto-z/lineage$ cat .repo/local_manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="1"
fetch="https://github.com/boulzordev/android_device_motorola_griffin" />
<remote name="2"
fetch="https://github.com/boulzordev/proprietary_vendor_motorola_griffin" />
</manifest>
[email protected]:~/moto-z/lineage$
YileKu said:
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/moto-z/lineage$ cat .repo/local_manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="1"
fetch="https://github.com/boulzordev/android_device_motorola_griffin" />
<remote name="2"
fetch="https://github.com/boulzordev/proprietary_vendor_motorola_griffin" />
</manifest>
[email protected]:~/moto-z/lineage$
Click to expand...
Click to collapse
Add something like this to your local manifest, right now you only defined from where you want to download the device tree and the vendor files, you also need to specify where you want them located
Code:
<project path="device/motorola/griffin" name="android_device_motorola_griffin" remote="1" />
<project path="vendor/motorola/griffin" name="proprietary_vendor_motorola_griffin" remote="1" />
StarStorm said:
Add something like this to your local manifest, right now you only defined from where you want to download the device tree and the vendor files, you also need to specify where you want them located
Code:
<project path="device/motorola/griffin" name="android_device_motorola_griffin" remote="1" />
<project path="vendor/motorola/griffin" name="proprietary_vendor_motorola_griffin" remote="1" />
Click to expand...
Click to collapse
Thanks that worked. I had to remove a duplicate path in roomservice.xml, then the sync and breakfast worked.
Y-
Thanks. Okay the build is working. I tried : 'cd kernel/motorola/msm8996'; make ARCH=arm64 CROSS_COMPILE=arm-linux-androideabi- menuconfig; /* enabled SMSC drivers to be in the kernel */; cd -; breakfast lineage_griffin-userdebug; brunch lineage_griffin-userdebug;" and get an error compiling setup.c. Any chance i can get the steps to configure, compile and include the kernel in an android build?
Thanks,
Y-