Related
I did a little search but couldn't actually find a thing. Is there any kernel for 4.1.2 with Frandom module instead of Urandom?
Sent from my Galaxy Nexus
Anyone? I read around that frandom should give real improvement compared to urandom, but didn't actually notice much people talking about it!
Sent from my Galaxy Nexus
have a look at this MOD CrossBreeder,
Frandom support (Optional)
Click to expand...
Click to collapse
i'm on Amperific's Kernel [A.S.K.P-Build14] with CrossBreeder, and i must say its a killer combination, i havnt tried the Frandom though..
Peace,
LastForOne
lastforone said:
have a look at this MOD CrossBreeder,
i'm on Amperific's Kernel [A.S.K.P-Build14] with CrossBreeder, and i must say its a killer combination, i havnt tried the Frandom though..
Peace,
LastForOne
Click to expand...
Click to collapse
I had a look at it, but still isn't what I'm looking for.
It says frandom module still needs to be compiled from the kernel source, and I'm not good at it. I googled a little bit to have an idea about what compiling a module means but it seems too difficult for my experience (never compiled a thing ).
So maybe someone could briefly link me a to a tutorial or (and this would be way better) explain me how to do it...
That would really be appreciated..
Acording to this guy seems like an easy thing.. If one is used to compiling modules.. >>
https://github.com/Ryuinferno/frandom-android
Sent from my Galaxy Nexus
I'll have a look at it and get back to you...
EDIT: I'l just quote this.
You will need to ask your ROM developer to develop the kernel module for you and then place it in /system/lib/modules.
&
Advanced users can even try and load the frandom module built for other kernels if they don't have one readily available for their own kernel version using the Punchmod utility.
Click to expand...
Click to collapse
so as it says you can try the Punchmod but before you do that i'd recommend you to give a try to Amperific's Kernel [A.S.K.P-Build14] with CrossBreeder combo, you may not even need the frandom after that.
Thank you for your suggestion, but I'm looking for the frandom module alone.. In addition, I'm on 4.1.2 so I'm using old kernels!
I think I'll just try asking for someone to compile it for me, provided with the kernel sources.. Or in extremis I'll try compiling it myself..
Sent from my Galaxy Nexus
Jar3112 said:
Thank you for your suggestion, but I'm looking for the frandom module alone.. In addition, I'm on 4.1.2 so I'm using old kernels!
I think I'll just try asking for someone to compile it for me, provided with the kernel sources.. Or in extremis I'll try compiling it myself..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
GoodLuck with that ^^
After many tries, I managed to compile frandom for my kernel, though executing insmod gave an error:
[email protected]:/ $ su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # insmod frandom.ko
insmod: init_module 'frandom.ko' failed (Exec format error)
How can I troubleshoot this error? Maybe I should run the insmod command on the pc, using adb shell?
Sent from my Galaxy Nexus
Jar3112 said:
After many tries, I managed to compile frandom for my kernel, though executing insmod gave an error:
[email protected]:/ $ su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # insmod frandom.ko
insmod: init_module 'frandom.ko' failed (Exec format error)
How can I troubleshoot this error? Maybe I should run the insmod command on the pc, using adb shell?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I found something else.
After facing the error I executed dmesg and this was the output:
<3>[23304.409484] frandom: version magic '3..0..31-04244-g560d2c8-dirty SMP preempt mod_unload ARMv7 ' should be '3.0.31-04244-g560d2c8-dirty SMP preempt mod_unload ARMv7 '
I tried changing the extraversion in the kernel source makefile, but still couldn't find the right, what am i missing?
I swear after this I'm writing a noob-proof tutorial for compiling kernel modules.
That would surely help, considering the amount of difficulties I am facing trying this for the first time..
Sent from my Galaxy Nexus
Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####
Same error here. Ask if they solved it.
http://forum.xda-developers.com/galaxy-s5/help/kltechnduos-compile-error-t3134865
Unfortunatelly, still no reply on linked thread
Sent from my HTC One X using XDA Free mobile app
I have the same error, see if someone can help us
Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?
teemo said:
Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?
Click to expand...
Click to collapse
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app
milda25 said:
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?
teemo said:
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?
Click to expand...
Click to collapse
All errors is in my initial post. First error is error 1. Don't know if this errors depends one on second ...
Sent from my HTC One X using XDA Free mobile app
milda25 said:
Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####
Click to expand...
Click to collapse
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!
Are you doing forced sync?
These days we sometimes need to
repo sync --forced-sync
@bigtor_gj, @teemo Thanks for the tips, will try ASAP and send a feedback.
Sent from my HTC One X using XDA Free mobile app
biktor_gj said:
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!
Click to expand...
Click to collapse
Code:
target Java: org.cyanogenmod.platform.sdk (/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /home/rafitcu/Android/Cm12.1/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (02:02:04 (hh:mm:ss)) ####
No solved for me
Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.
Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app
da_reeseboy said:
Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.
Click to expand...
Click to collapse
milda25 said:
Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
You have given me an idea, I am testing a solution and so far it seems to work, if the compilation ends successfully, the share here.
Unfortunately, git reset --hard and repo sync --force-sync doesn't solved the problem. Still same error on same position of building
What java version is everyone using? Run java -version and put the results here.
Code:
[email protected]:~$ java -version
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
I switched from OpenJDK to Oracle's JDK... no difference. I just found the vm I started building on in July, untouched with no updates done. I will resync and try a build on it to see if its an update to one of the packages installed for building that is causing the issue.
...This will take some time...
http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?
teemo said:
http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?
Click to expand...
Click to collapse
Thank you for the responses - those are both along the lines of the issue. The first post never mentioned what he deleted tho. The second one is definitely related as I can make it further in my build before failing when I revert that commit, but it still fails.
As few posts as there are online about having this issue, I don't think a commit is directly causing it, otherwise there wouldn't be any successful builds from anyone for the last couple weeks. I think its related to a security update that a few of us did, and most of the devs don't update if its not broken lol. I should know this afternoon...
Edit: I mean its an incompatibility between the changes to cmsdk and some security update I did.
Hello.
This is a try to keep other thread clean. Please post everything regarding kerneldevelopment in this thread.
Github: Original Elephone P9000 Kernel
Github: Forked Kernel by vsrookie
Github: Forked Kernel by @BlueFlame4
In BlueFlames kernelsources are already commits. These commits, correct wrong includes. Without you can't compile the kernel.
Thank you!
greeting
vsrookie
@BlueFlame4
I compiled the kernel with another cmdline:
Code:
console=tty0 console=ttyMT0,921600n1 root=/dev/ram vmalloc=496M slub_max_order=0 slub_debug=O androidboot.hardware=mt6755 androidboot.verifiedbootstate=green bootopt=64S3,32N2,64N2 lcm=1-R63315_GWMD13752A_drv fps=5540 vram=29229056 printk.disable_uart=1 bootprof.pl_t=658 bootprof.lk_t=2992 boot_reason=4 androidboot.serialno=K7CUOZJRJBAERG5D androidboot.bootreason=wdt_by_pass_pwk gpt=1 usb2jtag_mode=0
This is taken from /proc/cmdline.
The resulting kmsg is something weired. http://grork.lohnadmin.de/kernel/lstkms.txt
greetings
vsrookie
Ps: @BlueFlame4
I've testes your kernel also. This one:
BlueFlame4 said:
Here's a testkernel. I am pretty sure it will not boot. If it crashes, please reboot into recovery and post /proc/last_kmsg here. I just repacked stock boot.img with p9000_defconfig kernel.
http://d-h.st/clHI
Click to expand...
Click to collapse
As expected it didnt boot. Here is the last_kmsg from this.
http://grork.lohnadmin.de/kernel/test.txt
It looks like there is any encoding problem, or?
greetings
vsrookie
It looks like the video driver is crashing:
Code:
BUG: failure at /homeproject3/25%/2000706_c238_dx-andrOid+alps/kdrnel-3.18/drivers.misc/mediat%k/video/mt6755/dirp3ys/ddp[manafer.c:1616/dpmgr_ah%ck_stAtus
BlueFlame4 said:
It looks like the video driver is crashing:
Code:
BUG: failure at /homeproject3/25%/2000706_c238_dx-andrOid+alps/kdrnel-3.18/drivers.misc/mediat%k/video/mt6755/dirp3ys/ddp[manafer.c:1616/dpmgr_ah%ck_stAtus
Click to expand...
Click to collapse
I compile it with another cmdline to see what happens. I will leave the "lcm"-Parameter.
Two lines above in the kmsg there is:
Code:
[0.617501] (7)Y12swapper/0][DISP][disp^lcm_prbe #219]EBROR:[email protected] EROR: aan't found lcm drIver*R63315_GWMD3752A_drv�in linux kerNel driver [ 0.607528] (7)[0:swapp%r/ ][DISP][disp_lcm_probe #029]ERROP:[email protected]@L ERROR!!!Fo LCM Driver defined
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Oddly enough the mt65xx_lcm_list.c is prebuilt as well as many other .c files which normally are not. Even every single LCM driver is prebuilt... I would say that Elephone wants to screw us but from my past experience with them it is more likely that they just have no clue what they are doing
Luckily we have other 6.0 sources (for example from Vernee) so we could reverse engineer them but I want to avoid that for now. I attached a new version of the kernel with a possible fix for the crash implemented. Let me know if it boots please
http://d-h.st/6hwF
BlueFlame4 said:
Oddly enough the mt65xx_lcm_list.c is prebuilt as well as many other .c files which normally are not. Even every single LCM driver is prebuilt... I would say that Elephone wants to screw us but from my past experience with them it is more likely that they just have no clue what they are doing
Luckily we have other 6.0 sources (for example from Vernee) so we could reverse engineer them but I want to avoid that for now. I attached a new version of the kernel with a possible fix for the crash implemented. Let me know if it boots please
http://d-h.st/6hwF
Click to expand...
Click to collapse
Yepp, just grep for project3. You will see all shipped drivers.
Your kernel dont boot. There is also a one line last_kmsg. Strange. Only ram console header, hw_status: 0, fiq step 0.
Did you compile with the original cmdline?
greetings
vsrookie
EDIT:
Compiled without lcm Parameter, also same problem. last_kmsg
I used the default cmdline, yeah. Essentially I just repacked the stock boot.img without changing anything else than the kernel.
BlueFlame4 said:
I used the default cmdline, yeah. Essentially I just repacked the stock boot.img without changing anything else than the kernel.
Click to expand...
Click to collapse
Hi.
I've a last_kmsg that is readable! It took even longer till crash.
What I've done:
I've setted up a user project3 and put the sources into a directory you have to create:
Code:
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/
Also you have to put the correct config_cmdline in your config. (look in second post).
Hope that will help other so that we have a running kernel.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Good job! Still weird that you have to use a static path but it is MediaTek code so everything is possible I tried to build lcm_list myself like so but then I get linker errors complaining for some "agold_lcm_power_down" symbol. When I grep for it, it is only found in the .shipped files so I think we have a dead end here and we somehow have to use the .shipped files.
What I am seeing from you log is that
Code:
[ 158.303970] (4)[1:init]init: Starting service 'md_monitor'...
[ 158.334455] (4)[264:logd.auditd]type=1400 audit(1469711965.478:374): avc: denied { open } for pid=5690 comm="md_monitor" path="/data/md_mon/mdlog_mon1_config" dev="mmcblk0p28" ino=1589251 scontext=u:r:md_monitor:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
[ 158.336867] (4)[1:init]init: Service 'md_monitor' (pid 5690) exited with status 1
[ 158.336890] (4)[1:init]init: Service 'md_monitor' (pid 5690) killing any children in process group
md_monitor crashes which is probably leading to the reboot. Could you boot it permissively (androidboot.selinux=permissive in cmdline) and see if that helps?
BlueFlame4 said:
Good job! Still weird that you have to use a static path but it is MediaTek code so everything is possible I tried to build lcm_list myself like so but then I get linker errors complaining for some "agold_lcm_power_down" symbol. When I grep for it, it is only found in the .shipped files so I think we have a dead end here and we somehow have to use the .shipped files.
What I am seeing from you log is that
Code:
[ 158.303970] (4)[1:init]init: Starting service 'md_monitor'...
[ 158.334455] (4)[264:logd.auditd]type=1400 audit(1469711965.478:374): avc: denied { open } for pid=5690 comm="md_monitor" path="/data/md_mon/mdlog_mon1_config" dev="mmcblk0p28" ino=1589251 scontext=u:r:md_monitor:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
[ 158.336867] (4)[1:init]init: Service 'md_monitor' (pid 5690) exited with status 1
[ 158.336890] (4)[1:init]init: Service 'md_monitor' (pid 5690) killing any children in process group
md_monitor crashes which is probably leading to the reboot. Could you boot it permissively (androidboot.selinux=permissive in cmdline) and see if that helps?
Click to expand...
Click to collapse
I am tested my kernel on cm with permissive selinux, same
Deepflex said:
I am tested my kernel on cm with permissive selinux, same
Click to expand...
Click to collapse
Hi.
Have you compiled your own, or is it stock? How did you compiled it. (Toolchain, cmdline, config?)
Thank you for reply.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Hi.
Have you compiled your own, or is it stock? How did you compiled it. (Toolchain, cmdline, config?)
Thank you for reply.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi.
In sources of CM
Hi!
Hi!
The last last_kmsg wasnt correct i think, but this is a really nice one.
Its readable and from boot.
last_kmsg
There are at least three really big problems with the kernel sources:
1. incorrect sources; you have to do too much to compile a kernel.
2. incomplete; at least three drivers are missing:
Code:
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/base/power/ppm_v1/src/mt_ppm_main.c
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/agold_pm_info/agold_pm_info.c
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/agold_hw_compatible/agold_hw_compatible.c
3. most drivers are compiled binaries
Cause this is fun to me, i ill go on!
greetings
vsrookie
vsrookie said:
Hi!
Hi!
The last last_kmsg wasnt correct i think, but this is a really nice one.
Its readable and from boot.
last_kmsg
There are at least three really big problems with the kernel sources:
1. incorrect sources; you have to do too much to compile a kernel.
2. incomplete; at least one driver is missing:
[CODEt/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/base/power/ppm_v1/src/mt_ppm_main.c
[/CODE]
3. most drivers are compiled binaries
Cause this is fun to me, i ill go on!
greetings
vsrookie
Click to expand...
Click to collapse
Welcome to the world of MediaTek! I had the same problems with a Kazam device I got at XDA DevCon a couple of years ago - the company sent me the source code to play with and it was horrendous, gave up on it in the end :laugh:
Sent from my Elephone P9000 using XDA Labs
Jonny said:
Welcome to the world of MediaTek! I had the same problems with a Kazam device I got at XDA DevCon a couple of years ago - the company sent me the source code to play with and it was horrendous, gave up on it in the end :laugh:
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
Thats not very encouraging. Maybe they will release some more infos or sources.... I dont give up... at least the hope!
greetings
vsrookie
PS: Why isnt this a Sony Phone!?
Unlock bootloader and try your kernel
Deepflex said:
Unlock bootloader and try your kernel
Click to expand...
Click to collapse
Hi.
At present i'm struggeling with lcmdriver. I have to find the correct initialization for it. I think if I find it, then its a little milestone.
Kernel want to boot, but screen fades out slowly with no kernelpanic.
So far, I've replaced many shipped drivers with sourcecode from other devices. Looks good till now.
kmsg will print proper messages without any other weird codecs.
Do you have sources for uboot?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Hi.
At present i'm struggeling with lcmdriver. I have to find the correct initialization for it. I think if I find it, then its a little milestone.
Kernel want to boot, but screen fades out slowly with no kernelpanic.
So far, I've replaced many shipped drivers with sourcecode from other devices. Looks good till now.
kmsg will print proper messages without any other weird codecs.
Do you have sources for uboot?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi!
Go to settings/about phone/and enable developer settings, after, go to developers settings and choose "Factory Unlock (unlocking the bootloader)"
Deepflex said:
Hi!
Go to settings/about phone/and enable developer settings, after, go to developers settings and choose "Factory Unlock (unlocking the bootloader)"
Click to expand...
Click to collapse
Hi. There is no option for that. Only "OEM UNLOCKING" (allow the bootloader to be unlocked).
Also if I use fastboot OEM unlock, I can't use volume up? Anyone tried to unlock bootloader?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)
ThePiGuy said:
I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)
Click to expand...
Click to collapse
Which branch of titan are you using?
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Which branch of titan are you using?
Click to expand...
Click to collapse
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
steadfasterX said:
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Click to expand...
Click to collapse
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device
ThePiGuy said:
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device
Click to expand...
Click to collapse
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Click to expand...
Click to collapse
I got them from github.com/cypheros/[reponame] and I obtained them by adding them to the local_manifest (with oreo-mr1-release as the revision) and repo syncing
steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
@steadfasterX, have I done something obviously wrong?
ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Click to expand...
Click to collapse
This kept causing the android build to fail. I'll see if I can build android using that zimage as a prebuilt kernel
FYI moving this to the Help & Troubleshooting section
ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.
sdembiske said:
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.
Click to expand...
Click to collapse
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
Just doing another build - if the error still appears, I'll post the full log. If it doesn't I'll indicate what I tried.
Thank you, appreciate it.
S.
ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.
sdembiske said:
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.
Click to expand...
Click to collapse
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well
ThePiGuy said:
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well
Click to expand...
Click to collapse
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
sdembiske said:
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
Click to expand...
Click to collapse
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it
ThePiGuy said:
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it
Click to expand...
Click to collapse
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.
sdembiske said:
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.
Click to expand...
Click to collapse
No worries
I think I asked enough of these questions when I was learning (including this exact one) so I absolutely don't mind answering them too
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
me too
Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it