Help with CM10.2 Development
- Thread starter doomboss
- Start date
flashallthetime
Senior Member
- Dec 28, 2012
- 499
- 235
ADB says HWComposer is missing but hwcomposer.tegra is in lib/hw.
Also nvcpl...txt is missing. Nvcpl is in my product_packages list. The .apk is there but no driver.txt
The audioerrors are in my New Build fixed.
So there are 299 errors left
Nvcpl driver text is also missing in all my Roms, so you can pretty much cross that off the to do list, only 298 errors to go
. If it was easy to build from scratch, everyone would do it, just keep going at it and in time you'll have it conquered:thumbup::thumbup:
You're doing an amazing job
Sent on my Moto X
tpaine
Senior Member
- Aug 18, 2012
- 525
- 130
Nvcpl driver text is also missing in all my Roms, so you can pretty much cross that off the to do list, only 298 errors to go
You're doing an amazing job
Thanks for all your work.
(tpaine steps back, cheering on the project from the sidelines)
- Thread starter
- #51
Isn't SELinux for Android 4.4??? Oh well i actually don't know
I compared the egl folder on your build with superhansi's, and there are some files missing. Anyway, im not being so helpful right now......
By the way, how did you check the logcat with blackscreen??
Plug your device to your PC and then you can run "adb logcat" in terminal on your PC.
Reboot your device and then you can see the logcat-output in your terminal (hope you know what i mean, my english is not very good).
Btw.: At the moment i think there are 2 big mistakes in my rom :
- PR_SET_NO_NEW_PRIVS failed - (a SELinux command for a 3.5 Kernel, but i can't find 3.5 android-kernelsources)
- could not load library "libnvos.so" needed by "libEGL_tegra.so" - (libnvos.so is in my proprietary-blobs.txt and also in the vendor/nvidia/proprietary folder. So what?)
- could not load library "libsensors.base.so" needed by "sensors.kai.so" - (a new error that i see the first time now after i fixed a missing lightsensor file, i think i can handle that)
There are a lot more errors and warnings, but i think they are not necessary for now. Correct me or give me some hints. I'm thankfull for ever comment.
Here is my logcat-bootlog:
Reboot your device and then you can see the logcat-output in your terminal (hope you know what i mean, my english is not very good).
Btw.: At the moment i think there are 2 big mistakes in my rom :
- PR_SET_NO_NEW_PRIVS failed - (a SELinux command for a 3.5 Kernel, but i can't find 3.5 android-kernelsources)
- could not load library "libnvos.so" needed by "libEGL_tegra.so" - (libnvos.so is in my proprietary-blobs.txt and also in the vendor/nvidia/proprietary folder. So what?)
- could not load library "libsensors.base.so" needed by "sensors.kai.so" - (a new error that i see the first time now after i fixed a missing lightsensor file, i think i can handle that)
There are a lot more errors and warnings, but i think they are not necessary for now. Correct me or give me some hints. I'm thankfull for ever comment.
Here is my logcat-bootlog:
- Thread starter
- #54
Yeah, that is fixed...
...but now
So it is still a lot of work to do
Maybe you should post your logcat to XDA as well
- Thread starter
- #55
Hmmmm, Do you know if the compiler use all those lib files (or files with .so at the end) load from the vendor folder or from the device folder??? im still confused by where the compiler load all the required files from.....
All the libs and so files loaded from vendor folder. you must run "extract-files.sh" from device folder to copy all necessary propirietary files to vendor folder and then start compiling.
when the build is done you see it in logcat if everything is ok. if not (like the libsensors files) you must edit your "propieritary-files.txt" and "setup-makefiles.sh" files in device folder and start the hole thing again, and again, and again...
For now i think it will be a neverending story
Another build is ready. I will try it now and we will see what next is missed.
when the build is done you see it in logcat if everything is ok. if not (like the libsensors files) you must edit your "propieritary-files.txt" and "setup-makefiles.sh" files in device folder and start the hole thing again, and again, and again...
For now i think it will be a neverending story
Another build is ready. I will try it now and we will see what next is missed.
Last edited:
- Thread starter
- #57
Im getting these error while building the ROM:
{
File "/home/bio/CM10.1/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot mtd boot"
make: *** [/home/bio/CM10.1/out/target/product/A2109A/cm_A2109A-ota-9bdcee725f.zip] Error 1
}
@O@ What is this error about??????
{
File "/home/bio/CM10.1/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot mtd boot"
make: *** [/home/bio/CM10.1/out/target/product/A2109A/cm_A2109A-ota-9bdcee725f.zip] Error 1
}
@O@ What is this error about??????
- Thread starter
- #58
All the libs and so files loaded from vendor folder. you must run "extract-files.sh" from device folder to copy all necessary propirietary files to vendor folder and then start compiling.
when the build is done you see it in logcat if everything is ok. if not (like the libsensors files) you must edit your "propieritary-files.txt" and "setup-makefiles.sh" files in device folder and start the hole thing again, and again, and again...
For now i think it will be a neverending story
Another build is ready. I will try it now and we will see what next is missed.
Ok, i was just making sure
I have everything ready on those folder already, but I am just getting error when compiling.Keep going and don't stop!!!!!
- Thread starter
- #60
wow man!!!!! things are going good for you!!!!! ;D
cant wait to see your build ready Ok so i think i figured out why im getting that error. I have the right recovery.fstab on the device folder, but when i compile the ROM, it just keep using the prebuilt one from cm folder for some reason...... So I guess will need to build the recovery first to solve this error. However, there are some problem with the recovery because i didn't build it before. But in order to build the recovery, i need to have a built kernel........ I am having trouble with the kernel building step
I will bother you later about your kernel building process hehe
Last edited:
