Related
Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder
blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys
brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?
That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.
Hey,
I am trying to build CM for the first time and I have a quick question.
When I run ./extract-files.sh I am missing these 2 files -
remote object '/system/vendor/lib/egl/libplayback_adreno.so' does not exist
remote object '/system/vendor/lib/libtime_genoff.so' does not exist
I am running the latest CM build on my phone, so it's weird that these files don't exist...
Can I build CM without these?
Can I find them online and just put them is the proper place?
(I found libplayback_adreno over here - https://github.com/ModdedPA/proprietary_vendor_asus_flo/tree/master/proprietary/lib/egl
Does it matter that it is for a differnt device, or is the driver the same?)
Thank you
David 617 said:
Hey,
I am trying to build CM for the first time and I have a quick question.
When I run ./extract-files.sh I am missing these 2 files -
remote object '/system/vendor/lib/egl/libplayback_adreno.so' does not exist
remote object '/system/vendor/lib/libtime_genoff.so' does not exist
I am running the latest CM build on my phone, so it's weird that these files don't exist...
Can I build CM without these?
Can I find them online and just put them is the proper place?
(I found libplayback_adreno over here - https://github.com/ModdedPA/proprietary_vendor_asus_flo/tree/master/proprietary/lib/egl
Does it matter that it is for a differnt device, or is the driver the same?)
Thank you
Click to expand...
Click to collapse
Why don't you just repo it from the CM11 tree? And build it in a normal way.. repo sync etc and just brunch/lunch to compile the rom?
Grab the missing blobs from here https://github.com/TheMuppets/proprietary_vendor_htc. This is the repo that CM use and update.
nerotix said:
Why don't you just repo it from the CM11 tree? And build it in a normal way.. repo sync etc and just brunch/lunch to compile the rom?
Click to expand...
Click to collapse
Repo from the cm11 tree? Not sure what that means. If his current ROM doesn't have all of the proprietary files or the extract script is incorrect then running the extract script won't finish. He needs to pull them from the repo himself and add them. Or add the muppets repo to a local manifest so they are pulled when syncing.
task650 said:
Grab the missing blobs from here https://github.com/TheMuppets/proprietary_vendor_htc. This is the repo that CM use and update.
Click to expand...
Click to collapse
Thanks.
I was following the instructions from here - http://wiki.cyanogenmod.org/w/Build_for_m8
delete
task650 said:
Grab the missing blobs from here https://github.com/TheMuppets/proprietary_vendor_htc. This is the repo that CM use and update.
Click to expand...
Click to collapse
I have grabbed them from there but I'm not getting any kind of audio after booting up my build. any idea why?
linezero said:
I have grabbed them from there but I'm not getting any kind of audio after booting up my build. any idea why?
Click to expand...
Click to collapse
I had the same problem. What I did was that I commented out both of those files in proprietary.txt in the same directory where extract-files.sh resides, ran the extract-files.sh and manually downloaded libtime_genoff.so from TheMuppets repo to the appropriate directory in the source tree.
I left out the libplayback_adreno.so and the build was successful, and the sound is now all fine. I have no idea what the problem is, but this seems to fix it.
EDIT: I also just ran a diff between my current tree and the files on TheMuppets repo and everything is the same except EasyAccessService.apk with the extracted one having MD5 sum of 857e281624403b51937da8d4bf821769 and the one on the repo d3858ce10861106ae2bf90d554838445.
EDIT2: Hmm, seems like build looks for libtime_genoff.so under vendor/lib but the file ends up under /system/lib on device. Changing the path in proprietary.txt lets extract script to run fine, but then the build fails!
oxplot said:
I had the same problem. What I did was that I commented out both of those files in proprietary.txt in the same directory where extract-files.sh resides, ran the extract-files.sh and manually downloaded libtime_genoff.so from TheMuppets repo to the appropriate directory in the source tree.
I left out the libplayback_adreno.so and the build was successful, and the sound is now all fine. I have no idea what the problem is, but this seems to fix it.
EDIT: I also just ran a diff between my current tree and the files on TheMuppets repo and everything is the same except EasyAccessService.apk with the extracted one having MD5 sum of 857e281624403b51937da8d4bf821769 and the one on the repo d3858ce10861106ae2bf90d554838445.
EDIT2: Hmm, seems like build looks for libtime_genoff.so under vendor/lib but the file ends up under /system/lib on device. Changing the path in proprietary.txt lets extract script to run fine, but then the build fails!
Click to expand...
Click to collapse
mine was an issue with cyanogenmod source they have reverted the commit back. more over did you do lunch?
linezero said:
mine was an issue with cyanogenmod source they have reverted the commit back. more over did you do lunch?
Click to expand...
Click to collapse
brunch
When was the commit reverted? I don't see any recent ones related to this.
oxplot said:
brunch
When was the commit reverted? I don't see any recent ones related to this.
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/71827/
linezero said:
http://review.cyanogenmod.org/#/c/71827/
Click to expand...
Click to collapse
I see, but that doesn't fix the extract-files script.
Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....
hackerzrulez007 said:
Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....
Click to expand...
Click to collapse
Here is The Device tree :
https://github.com/armani-dev/android_device_xiaomi_armani
and here vender tree :
https://github.com/armani-dev/proprietary_vendor_xiaomi
Getting error while compiling AOSP with the armani device tree
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?
praveenpuglia said:
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?
Click to expand...
Click to collapse
these device tree won't work for cm12 ie lolipop
there are patch, which should be done before compiling rom
Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!
praveenpuglia said:
Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!
Click to expand...
Click to collapse
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.
kD said:
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.
Click to expand...
Click to collapse
What about using those device trees for cm12?
praveenpuglia said:
What about using those device trees for cm12?
Click to expand...
Click to collapse
As said earlier won't work
Actually OP need 1st step guide with current repo .... I think
Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Awesome!
kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
i do agree with jsevi83 pal even i tried with my noob knowledge now m bored
jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.
good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you
Any update ?
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
cm11noob10 said:
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
Click to expand...
Click to collapse
Any news on this awesome rom?
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
cm11noob10 said:
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
liam_davenport said:
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
cm11noob10 said:
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
Click to expand...
Click to collapse
What linux distro are you using?
liam_davenport said:
What linux distro are you using?
Click to expand...
Click to collapse
Ubuntu. I have problems running Arch in a VM without scaling issues.
cm11noob10 said:
Ubuntu. I have problems running Arch in a VM without scaling issues.
Click to expand...
Click to collapse
Try this: sudo apt-get install linux-headers-generic
liam_davenport said:
Try this: sudo apt-get install linux-headers-generic
Click to expand...
Click to collapse
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
If you get it working I could try my hand for the sailfish
YTSec said:
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
Click to expand...
Click to collapse
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
ChongoDroid said:
If you get it working I could try my hand for the sailfish
Click to expand...
Click to collapse
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
cm11noob10 said:
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
Click to expand...
Click to collapse
I'll give it a try tonight when I can, and see if I get anywhere. Would be nice to at least get the music detection working somehow.
U may need to use a newer kernel tree to compile I did but I also had to update toolchain its what I did
cm11noob10 said:
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
Click to expand...
Click to collapse
Have you been able to get it compile and boot?
Zehlek said:
Have you been able to get it compile and boot?
Click to expand...
Click to collapse
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
cm11noob10 said:
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
Click to expand...
Click to collapse
Maybe you and @joeeboogz can work together. It would be an awesome rom
U have to update toolchain to ur computer then compile and add zip to tree then add toolchain line to board config I think I forgot which file to edit
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
YTSec said:
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
Click to expand...
Click to collapse
do you have aoscp.mk in your device tree?
i came across this tread because i want to use a prebuilt kernel and im getting the error "ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/sixohtew/bliss/out/target/product/taimen/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it" and saw someone had a previous error.. im trying to build for taimen obv which is the pixel 2 xl and it has an aosp prebuilt kernel and my rom wont compile any other kernels so i was looking for some help