Database Users

[Q] CM Git Repository

Hello all. I am trying to checkout the CM source from the git repository.
When I try to run the initial sync by running 'repo sync' I get an error after a couple hours of downloading. Looks like it has downloaded everything as there is 3.4G under the .repo folder and another 2 gigs in the /android/system folder. Also, the scripts says if fetched 100% (215/215). The error is:
Syncing work tree: 72% (155/215) error: revision master in CyanogenMod/android_packages_apps_CMParts not found
It then fails and dies. Quite a bit of the system source is in the tree, but the vendor branch is gone, so I can't even start working on it.
I have never used git before, so I am kinda lost in it. anyone wanna give me a hand?

Please post questions in General section.

cbusillo said:
Hello all. I am trying to checkout the CM source from the git repository.
When I try to run the initial sync by running 'repo sync' I get an error after a couple hours of downloading. Looks like it has downloaded everything as there is 3.4G under the .repo folder and another 2 gigs in the /android/system folder. Also, the scripts says if fetched 100% (215/215). The error is:
Syncing work tree: 72% (155/215) error: revision master in CyanogenMod/android_packages_apps_CMParts not found
It then fails and dies. Quite a bit of the system source is in the tree, but the vendor branch is gone, so I can't even start working on it.
I have never used git before, so I am kinda lost in it. anyone wanna give me a hand?
Click to expand...
Click to collapse
i've never looked at the CM source, but post a link to the repo and Ill see what I can get tonight.

If downloading the source tree to compile and work on porting CM to Epic doesn't belong in the development forum, what does?
I found the problem; there is no longer a master revision in the CMParts project, it was renamed to froyo. After initializing the repo, you have to manually change the revision in the .repo/manifest.xml

[Q] *Building CM from source on Snow Leopard*

Hello all,
i'm using this guide http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vision_(Mac) on the cyanogenmod wiki to build for my mt4g. I successfully built it a couple times with no issues, but the last couple days i've been running into a wall at the end of the build. I completely wiped out the working drive and re-init repo and everything. All steps go fine until I make bacon, then near the end of the build I get this
Code:
Target ram disk: out/target/product/glacier/ramdisk.img
target Dex: core-junit
Copying: out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/classes.jar
Copying: out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/noproguard.classes.jar
target Prelink: libutils (out/target/product/glacier/symbols/system/lib/libutils.so)
libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned long) != 8
libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned long) != 8
libelfcopy: Warning: Location lists in .debug_info section aren't in ascending order!
libelfcopy: Warning: Range lists in .debug_info section aren't in ascending order!
libelfcopy: Warning: Range lists in .debug_ranges section start at 0x318
Copying: out/target/common/obj/APPS/QuickSearchBox_intermediates/classes.jar
target Prelink: libwpa_client (out/target/product/glacier/symbols/system/lib/libwpa_client.so)
target Non-prelinked: libnetutils (out/target/product/glacier/symbols/system/lib/libnetutils.so)
target Prelink: libhardware (out/target/product/glacier/symbols/system/lib/libhardware.so)
target Prelink: libssl (out/target/product/glacier/symbols/system/lib/libssl.so)
target Prelink: libjpeg (out/target/product/glacier/symbols/system/lib/libjpeg.so)
ASSERTION FAILURE external/elfcopy/elfcopy.c:932: [ranges[i].start >= last_end]
make: *** [out/target/product/glacier/symbols/system/lib/libjpeg.so] Error 1
make: *** Deleting file `out/target/product/glacier/symbols/system/lib/libjpeg.so'
libelfcopy: Warning: Range lists in .debug_info section aren't in ascending order!
make: *** Waiting for unfinished jobs....
MacBook-Pro:android jam$ /CODE]
any ideas? this is driving me nuts! thanks for the guide peeps!

Are you trying to patch in anything from gerrit?

nope
I wish, that would be easier to figure out. Just a straight pull from source.

Unfortuately I dont have an answer for you then. The nightlies are building so it should work.
How did you "clean everything out"?
make clean
mka bacon

i deleted the disk image used for the working dir. and started over. and yeah i tried make clean.

then I'm out of ideas. Sorry man. Hopefully someone else comes along with more knowledge of it.

I tried setting up my SnowLeopard Macbook to compile AOSP and decided to give up. There are simply too many hacks/patches needed to get SnowLeopard to play nicely to compile AOSP. I am not sure about the CM build tree, but I assume CM follows AOSP, so they should be similar in setup.
My suggestion, get Parallel Desktop, install Ubuntu-64, download all the necessary libraries/tools, compile, done...
I wasted 2 days trying to get my SnowLeopard to compile AOSP, then I wised up and used Parallel+Ubuntu, then I was able to compile AOSP in 3 hours, after that, I downloaded MT4G Kernel source from HTC, compiled that in an hour... (BTW, if you decide to use Parallel, I suggest you make the virtual harddisk size to at least 20GB, I made a mistake allocating only 16 GB, but for AOSP+HTC Kernel, I ran out of space, had to use GParted to extend my virtual disk, wasted 1/2 hour there)
AOSP version 2.3 (GingerBread) and beyond requires ubuntu-64 anyways, so this is future proofing anyways...

faux123 said:
I tried setting up my SnowLeopard Macbook to compile AOSP and decided to give up. There are simply too many hacks/patches needed to get SnowLeopard to play nicely to compile AOSP. I am not sure about the CM build tree, but I assume CM follows AOSP, so they should be similar in setup.
My suggestion, get Parallel Desktop, install Ubuntu-64, download all the necessary libraries/tools, compile, done...
I wasted 2 days trying to get my SnowLeopard to compile AOSP, then I wised up and used Parallel+Ubuntu, then I was able to compile AOSP in 3 hours, after that, I downloaded MT4G Kernel source from HTC, compiled that in an hour... (BTW, if you decide to use Parallel, I suggest you make the virtual harddisk size to at least 20GB, I made a mistake allocating only 16 GB, but for AOSP+HTC Kernel, I ran out of space, had to use GParted to extend my virtual disk, wasted 1/2 hour there)
AOSP version 2.3 (GingerBread) and beyond requires ubuntu-64 anyways, so this is future proofing anyways...
Click to expand...
Click to collapse
Thanks for the advice, I've spent a few days myself trying aosp first, then CM. I actually did get a few working roms out of my mac from the cm source until about a week ago. Then i started to get the errors above. It's like they changed something in the source that no longer agrees with the tools or os installed. I'll give the parallel + ubuntu a shot. But i have a quick question for you. Did you actually get a working aosp build for mt4g? Flashed and all features working?

conclusion
Well i gave the parallels desktop a shot and it was super easy to setup,build environment setup fine and repo sync'd .. except i couldn't get adb to list my device. I searched and tried all kinds of rules (i.e. 51.android.rules) and no go. So, I decided to go back to the dual boot option. I tried to get 10.10 installed, but when I try to boot the ubuntu cd from rEFIt menu, i get
1.
2.
Select CD-Rom Boot Option.... or something like that
then I restart into osx
I tried a couple different discs and nothing. So, I went back to 10.4 and all is fine now.
I also kept searching for the rules for glacier and found them here http://wiki.cyanogenmod.com/index.php?title=Udev#MyTouch_4G
With that, I may try VirtualBox in the future, or some other free VM, but for now, I'm working with dual boot and trying to build an AOSP rom. Thanks for the help guys!

Sorry to resurrect an old thread, but for the sake of anyone who finds this thread by searching I thought I'd add that I've developed fix that allows CM7 to be built on OS X 10.6. I've submitted it to the AOSP gerrit: https://review.source.android.com/#change,22597

Help for Compile CyanogenMod ?

Please help me to Compile CyanogenMod in Ubuntu 11.10. I am following all the instructions mentioned in below link, but failed twice to complete the sync process:
http://wiki.cyanogenmod.com/wiki/HTC_Wildfire:_Compile_CyanogenMod_(Linux)
The step to sync is not completing: "repo sync -j16"
Sometime, the script stops or there is no progress for long period of time (around 30 min.). Then I stop and restart above step and it continue to progress, but after 1-2 hrs, again stop somewhere. Am I doing something wrong. I am having 4Mbps speed broadband which I think is not bad speed.
Can anyone tell me how much of data will be downloaded in above sync step ?
I had installed Ubuntu using Wibu tool which is installing it on my "C:" drive and I had allocated 20GB space for it. But, after above step multiple times, it says disk is full. That means 20GB space is filled completely. I have not installed anything else other than ANDROID SDK, ECLIPSE, JAVA and GIT which is necessary for android development.
I am new to android development and all the help will be appreciated.
Thanks

After so many days of waiting, no reply from any developer here. I think I should have put this request on Development Section.
Moderator, can you please shift this thread in Developer Section so that I can get some help on android rom development to be started ?

Sorry for not seeing this thread earlier. I'm no dev, but I'm sure you could use CMC (CyanogenMOD Compiler) to compile it. When downloading cyanogenmod sources, I think its roughly 20GB of data to sync. You'll probably need to repartiton more of your hard-drive for Ubuntu.

Justice™ said:
Sorry for not seeing this thread earlier. I'm no dev, but I'm sure you could use CMC (CyanogenMOD Compiler) to compile it. When downloading cyanogenmod sources, I think its roughly 20GB of data to sync. You'll probably need to repartiton more of your hard-drive for Ubuntu.
Click to expand...
Click to collapse
Thank you very much. I'll repartition my hard drive now so that i can allocate at least 50GB for Ubuntu

I need a little bit of help porting crDroid 6 to the sm-t350

I need a little bit of help portingh crDroid 6 to the sm-t350. Nubianprince started then got pulled away by work. I have initalized the crdroid repo, but i when i run repo sync i think it only downloaded like, 300 mb. i do have an android pie enviroment, does repo link resources? i dont know what is going on there. I will upload my roomservice.xml. I had to remove a couple lines from the original and manually clone them because it keeped giving me an error. the original is here https://github.com/Nubianprince/local_manifests/blob/master/crdroid-ten.xml .
Currently i am using this device tree: https://github.com/Nubianprince/android_vendor_samsung_gt58wifi most custom roms i see are using this: https://github.com/Valera1978/android_device_samsung_gtaxlwifi . I have not seen any non sm-5xx devices using it though, so i hesitate to switch. i worked out a a couple errors of things being defined twice, and then built. but i think i am missing something as the build fails with this: FAILED: ninja: 'out/target/product/gt58wifi/root/init.usb.configfs.rc', needed by 'out/target/product/gt58wifi/ramdisk-recovery.cpio', missing and no known rule to make it
Is there a "quick fix" to provide this file? I am not actually sure what i am missing, or what creates it.
Any help would be appreciated.

This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.

nubianprince said:
This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.
Click to expand...
Click to collapse
Yes, it does make sense. I just don't know enough about the android environment to know where the file, or what is pointing to it, would / should be.

Okay. I believe there is a missing, or many many missing makefiles. I found the file and manually copied it to out, and then the build fails with another missing file. Rinse and repeat, there are a ton of files not being put where they should be. Now what to do with that information, i am not sure ??. I tried including a couple of the make files from android 9, but they didn't make any difference.
oh yeah, and if i do lunch instead of brunch it fails with a different file missing: FAILED: ninja: 'out/target/product/gt58wifi/system/addon.d/50-lineage.sh', needed by 'out/target/product/gt58wifi/verified_assembled_framework_manifest.xml', missing and no known rule to make it

it makes no sense adding files to the "out" folder, fix the issues in your "device" folder check your device.mk file

Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.

lividhen99 said:
Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.
Click to expand...
Click to collapse
What device tree are you using, do you have it on Github?

nubianprince said:
What device tree are you using, do you have it on Github?
Click to expand...
Click to collapse
I am just using the device trees (ten branch) on your GitHub. I haven't made any changes that have gotten me anywhere so i haven't committed my local changes to my GitHub.

That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I have been away for a while and haven't followed along, but the last week I spent compiling ROMs. I also tried compiling Android 10 using "stock" lineageos gt58wifi and I got stuck at the logo as well. I also tried another device from the msm8916 repository and got stuck at the logo.
The "stock" gt58wifi build, as we all know, has problems with audio, bluetooth, smart cover, etc, etc in all versions 14.1, 15.0, 16.0 and won't even boot with 17.1.
When I first compiled it, it would fail due an error with a config.xml file. I submitted a patch, like others, but haven't seen anything yet.
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/pulls

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I'm working on SM-T560NU 17.1. It too was stuck at the boot logo. I built an eng build and found it was the hardware vibrator that was getting stuck in a loop. If you remove the vibrator hal from
/device/samsung/msm8916-common/manifest.xml
that should work on the SM-T350 because both platforms share the same msm8916 code?
I did build SM-T350 with 17.1 and was stuck at boot logo and gave up. However, I have not rebuilt it knowing this new information. I will try again with the above change in a few days?

So, as retiredtab has said, he got android 10 booting. But it has all the issues android 9 did: no camera, sound, Bluetooth, or Hal sensor (sort of, it can turn the device on but not off). The system ui is also a little funny on crdroid, not sure about lineage. I don't know how to fix these issues, or where the roots of the problems may lay. Do you have any suggestions for learning more about the android source code? I feel like the aosp docs are good, but you kind of have to know what you're looking for.

I think part of the problem with the SM-T350 is that there has never been a fully working build since day 1. Lineageos 14 had problems to begin with and they were never fixed and got carried over to 15, 16 and now 17. If stock Lineageos 16 was fully working, then getting it to work on 17 would be less of a challenge.
The most likely problem to no audio, camera, bluetooth etc is the Samsung proprietary blobs are not in the correct directories or the configuration blob files are pointing to the wrong directory.
When I face this problem, I find it helpful to look at a working roomservice.xml file and do comparisons.
If there is no working roomservice.xml like "stock" lineageos 14, 15, and 16 for the SM-T350, then I look at similar models. For example, the T550 is the bigger brother and it helps to look through it's roomservice.xml file for hints.
Remember that a compiler mainly checks for syntax errors, not semantic. If you make a typo, a compiler will flag that as an error, but if you write correct syntax, but put a file or files in directory ABC instead of XYZ, the compiler won't say anything.
Another thing that might help is doing a logcat of a working build and comparing it to a non working build. There might be a very obvious error message like "can't find audio.hw.msm8916 in directory /device/samsung/msm8916" or something like that.
Learning how to use tools like meld and diff help tremendously in finding file and directory differences in case you put the blobs in the wrong place. See
https://www.tecmint.com/compare-find-difference-between-two-directories-in-linux/
I used meld when troubleshooting the stuck at boot logo.
If you are a visual learner, I found the following youtube channel helping in learning the overall process of building ROMs.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos

I think we have lineage 16 fully working. I think the part I'm having trouble with here is the difference between where the files are read from in Android Q vs P.
If I understood what you said incorrectly, please say so.

HELP!!! please!! compile bootable systemd msm-3.18 arm kernel

hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors

Duhjoker said:
hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors
Click to expand...
Click to collapse
You should go to IRC #sailfishos-porters, there you will find help from Jolla developers and from community

well i guess theres no help any where. the folks at telegram completely ignore me and are rude as f and if you say any thing about it they say you ate spamming for and claim you are the rude one. ive been ganged up on several times. irq doesnt seem to have enough people to help and i feel all hope is lost at this point.
on the other hand i have built a the whole rom completely and several times over but i cant get it installed and dont know how to see if the kernel works

ok im gonna keep trying to get help from here. I have gotten more help and made it farther in my abilities because of the help and info from this place than any other. Thank you
So this is where i am at. i have compiled Halium\Ubuntu touch several times over and worked it out with no compilation errors and including all of my sources.
But i cannot get it to ssh or telnet. I have followed all of the installation documents and i can see that its pulling the system.img and rootfs to data. i have entered my password on prompt its generated and pushed the rsa keys and every thing. but no go
i have checked the dmsg and kmsg after the attempts and no errors are reported.
so now im trying to go the route of the V20. I have an arm ubuntu 18.04 rootfs that i have unzipped and built up on the 2nd partition of my external sd. i installed every thing needed to build a kernel and any thing else i might need. i have msm-fb-refresher compiled and installed. I also have dev sys and proc mounted bound and and have made the devices using MAKEDEV. But when i try to build the kernel on my aristo 2 in the chroot i get these weird graphics characters and i have to restart my terminal to get my characters back.
in the mean time i compiled the kernel on my pc and had the modules installed to the chroot outside the android device and used update-initramfs to create an initrd.img exteacted it and made a boot.img that i put in the boot directory and installed to laf.
it will not boot stiil from laugh and goes to bootloader. but if i tell the chroot to reboot i get the error system cannot reboot with systemD as init cannot operate.

ok well still no help at any of the halium/ubuntu touch forums or telegram. But the bot said there was no kernel errors.
i have been looking at the lg v20 native ububtu mate rootfs and also the ectracted boot.img contents and i just dont know what it is thats causing it not to boot