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.
Related
NEWS :
Koush's bmlunlock (a simple IOCTL send to the bml device) is just out and can replace redbend_ua !
http://github.com/CyanogenMod/android_device_samsung_bmlunlock
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is WTFPL
Note : requirement are Java and Android source repo, already build.
Looks awesome!
I have a question though... why do you need to flash the kernel in an update.zip at boot?
As far as I know, the system will read the kernel at boot up time and load it into ram. It won't access the on-disk file again until the next boot. If that is true, then flashing while running should be 100% safe, right?
RyanZA it's an update.zip, not a ramdisk.
The point is getting an easy flashing method, requiring no computer.
And you don't even need to root your phone !
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?
FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
Click to expand...
Click to collapse
I don't think the signing tool works on android -- maybe it does? Anyway editing scripts on a phone seems a bit silly!
FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?
Click to expand...
Click to collapse
Nope actually this is not dumb at all
Yes the flashing part run in updater-script can be started manually.
In the script :
Code:
"redbend_ua", "restore", "zImage", "/dev/block/bml7"
The update.zip presented here mainly targets custom kernel creators in order to give them another way to distribute their work.
This is a working example of how to use redbend_ua programmatically, hopefully it may help new ideas coming. redbend_ua usage is not limited at all to kernel flashing.
PS : you can use this template with windows as well, you'll just need to translate the ulta-basic .sh to a .bat script, or do the signing part manually.
supercurio said:
Hey
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
Click to expand...
Click to collapse
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
is it correct?
thx
So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
supercurio said:
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is BSD anyway.
Note : requirement are Java and Android source repo, already build.
I'll add some documentation later.
Click to expand...
Click to collapse
dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Thats for the updater-script i believe. In most cases, theres a update-script in the zip's as well and the recovery picks that up in which case it doesn't need the binary and hence works.
Okay !
Answers hour
ykk_five said:
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
Click to expand...
Click to collapse
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
No further complication
Brantyr said:
So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!
Click to expand...
Click to collapse
Yes, to flash a complete ROM (several partitions) one more thing is needed.
On command line, redbend_ua accept only one command.
In order to run several commands successively (ie flash multiple partition like Odin does), you'll need to write them in a file.
The file /cache/ota/command should do the trick, but it's untested right now.
There may be other method to prevent rebooting after flashing (hacking the redbend_ua binary, finding the appropriate command line option or removing the reboot command temporary)
dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Right, many update.zip done today are made without knowing anything about how it really works
I studied a bit before creating mine, here is a walk-through this fairly undocumented process :
- recovery mounts /sdcard/
- recovery search for a default file named : META-INF/com/google/android/update-binary in the zip and runs it : see the source in bootable/recovery/install.c
- update-binary is actually updater in sources
- updater looks into the zip file to the script file named updater-script, update-script is obsolete
- updater then runs the commands listed in updater-script : here is the list of commands.
- then reboot
The only documentation I know for this command is the recovery/updater/install.c file itself
supercurio said:
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
Click to expand...
Click to collapse
ok,thx
but one more thing i want to know is, u said the path must be changed to the android repo, so do u mean the source code for the kernel like linux-xxx-2.xxx dir?
Thx
@ykk_five
Content of build-update-zip.sh v1 :
Code:
#!/bin/sh
DROID_HOME="/home/curio/dev/mydroid"
zip -r /tmp/update.zip META-INF/ redbend_ua zImage
java -jar \
$DROID_HOME/out/host/linux-x86/framework/signapk.jar \
$DROID_HOME/build/target/product/security/testkey.x509.pem \
$DROID_HOME/build/target/product/security/testkey.pk8 \
/tmp/update.zip update.zip
rm /tmp/update.zip
adb push update.zip /sdcard/
DROID_HOME="/home/curio/dev/mydroid" : you set here the directory of your Android AOSP directory.
See : http://source.android.com/source/download.html
Create an empty directory to hold your working files:
$ mkdir mydroid
$ cd mydroid
Run "repo init" to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest:
$ repo init -u git://android.git.kernel.org/platform/manifest.git
* If you would like to check out a branch other than "master", specify it with -b, like:
$ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
Click to expand...
Click to collapse
This is this mydroid directory
The one that contains Android git source home directory, and compiled files in the out/ subdir
many thx for ur detailed explanation, supercurio!
Thanks curio,
very helpful explanation!
Thanks supercurio for the template!
However, there is no need to spend many hours (depending on hardware and bandwidth) pulling down 100s of megabytes of source and compiling it all if all you want is to sign an update.zip with test keys (if you already have the zImage)!
Just google around for "signapk.jar test keys" and you will get there.
BTW: I know that koush, leshak and wesgamer have Samsung Galaxy S trees up at Github but are they fully merged with AOSP yet?
I'm planning to go build my own kernel for this beast to try to solve the mono FM radio mystery, but last time I checked around it was said that the SGS tree required the use of a custom toolchain to get it to work at all.
Any comments on this?
Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
About toolchain, you can use the one indicated by Samsung (CodeSourcery) but you'll face the big and ugly WakeLag.
I recommend you crosstool-ng or buildroot to build toolchains, with gcc 4.3.x march=arm mcpu=cortex-a8 mtune=cortex-a8 (no 4.4.x with march=armv7-v)
The building tutorial will be a part of the documentation I'll publish with my lagfix opensource release
Right now these info are too hard to find.
PS : I send you a mail with attached .config for ct-ng !
supercurio said:
Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
Click to expand...
Click to collapse
supercurio said:
PS : I send you a mail with attached .config for ct-ng !
Click to expand...
Click to collapse
Thanks for the info !
Sorry for my ignorance, but does this mean someone can package Froyo in an update.zip and we could update it directly on our phone without needing Samsung Kies or Odin?
@supercurio:
Thanks for this well working template.
In updater-script:
Code:
line 17: package_extract_dir("zImage", "zImage");
should be
Code:
package_extract_file("zImage", "zImage");
But it did work with package_extract_dir, for some reason, too.
Btw, could you send me the config for ct-ng ?
I'm also struggling with this wakelag.
How do I compile a rom with specific apps I want and exclude the ones I don't want?
Put the apps you want in system/app of the rom your compiling. Same thing for removing them. For removal just take them out of system/app. Hope this helps.
DINC|CM7|INCREDIKERNEL
Yeah, I know how to do that already, thanks for the reply! Actually, I want to compile from the source code via terminal. I have my own repository I'm using with some minor changes made to theme it a little. I just want to include specific apps in the compilation and was wondering what I had to do with my repository in order to achieve this?
Treken said:
Yeah, I know how to do that already, thanks for the reply! Actually, I want to compile from the source code via terminal. I have my own repository I'm using with some minor changes made to theme it a little. I just want to include specific apps in the compilation and was wondering what I had to do with my repository in order to achieve this?
Click to expand...
Click to collapse
You will need to edit the vendor tree. If you want it to add apps that are already compiled such as ones you have from the market then you can put them in with the proprietary files and then just add some lines in the inc.mk file or in the blobs mk file in the vendor tree to copy those files from where they are into out/target/product/inc/system/app/ (I'm going from memory there so double check the path) You can look through that inc.mk file to see how it copies other files and just use that same syntax.
Ah, now that sounds more promising. Thanks!
After following this tutorial I compiled CM9 for my r800x and everything works fine but since I first compiled I have edited the SystemUI sources. The problem is when I compile it doesn't compile the new sources. Anyone know what I'm doing wrong? Sorry if this is a noob question.
Extra information (not sure if important but might help find the cause):
Using Xubuntu 12.10
Oracle Java 6
I edited /frameworks/base/packages/SystemUI
I compiled for zeusc instead of zeus
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
http://source.android.com/source/initializing.html said:
export OUT_DIR_COMMON_BASE=<path-to-your-out-directory>
Click to expand...
Click to collapse
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Trooper_Max said:
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Click to expand...
Click to collapse
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
bandoncontortion said:
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
Click to expand...
Click to collapse
Cj360 made a zeusc version and uploaded it to fxp cm10 page. I've tested it and it works great
Sent from my Xperia Play (r800x)
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
bandoncontortion said:
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
Click to expand...
Click to collapse
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Changing the timestamp didn't do anything. I'll try deleting the already compiled files and recompile everything over again tomorrow. Also CM10 is a lot better in my opinion too so I'll try it now so hopefully it'll work and fix the problems I'm having.
Trooper_Max said:
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Click to expand...
Click to collapse
CM10 works good on zeusc. Haven't found any bugs and I added the changes to it's SystemUI and it compiled it for me and works great. Thanks for the help!
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.
We're in business; the kernel sources got released today.
GitHub - ztemt/NX669J-kernel: nubia NX669J Android 11 open source
nubia NX669J Android 11 open source. Contribute to ztemt/NX669J-kernel development by creating an account on GitHub.
github.com
They should be accompanied by other opensource bits shortly.
Good news!
The main question for me: will it be possible to make fp scanner working with unlocked bootloader? (or, at least, to use magisk-patched boot with re-locked bootloader)
I tried to make a kernal with this guide https://www.google.com/amp/s/www.ge...our-own-android-kernel-in-5-simple-steps/amp/ . i got to step 4. I can not find the correct name of config file to change the command needed to compile.
jokono421 said:
I tried to make a kernal with this guide https://www.google.com/amp/s/www.ge...our-own-android-kernel-in-5-simple-steps/amp/ . i got to step 4. I can not find the correct name of config file to change the command needed to compile.
Click to expand...
Click to collapse
Your best bet will be to use the config file found inside the phone, under /proc/config. Just put it in the kernel code under arch/arm64/configs
nice!
kereng77 said:
Your best bet will be to use the config file found inside the phone, under /proc/config. Just put it in the kernel code under arch/arm64/configs
Click to expand...
Click to collapse
jokono421 said:
I tried to make a kernal with this guide https://www.google.com/amp/s/www.ge...our-own-android-kernel-in-5-simple-steps/amp/ . i got to step 4. I can not find the correct name of config file to change the command needed to compile.
Click to expand...
Click to collapse
If you're rooted, check if you can access /proc/config.gz; unzip it to /yourkernelsource/.config
If i take apart the rom, i get config folder with 5-6 different files. All saying similar config. ,config/w, maxwellconfig, deconfg. i tried 3 or 4 but nothing. Although my laptop is only 4gb with linux running on windows. It might not be powerful enough to run.
Ok i got the config.gz out of proc and extracted. Will try so thankyou.
Was anyone able to flash a custom kernel on the RM6?