when I do: "make otapackage" i have this error after some minutes
make: *** Nessuna regola per generare l'obiettivo "vendor/lge/thunderg/proprietary/lib/libril.so", necessario per "out/target/product/thunderg/system/lib/libril.so". Arresto.
Click to expand...
Click to collapse
How I can resolve it?
I've read Noejn HowTo.
you have to copy the libril.so to your target - the lib gets linked with some other libs so the lib is needed on this place before other libs can be compiled.
I've copied libril.so in out/target/product/thunderg/system/lib... Now i try again with "make otapackage"
For future, kindly set LC_MESSAGES=C in your environment for compiling. Getting compile error output in random languages is rather annoying if you need help.
dr.notor said:
For future, kindly set LC_MESSAGES=C in your environment for compiling. Getting compile error output in random languages is rather annoying if you need help.
Click to expand...
Click to collapse
/offtopic/
you back again doktornotor?
Sent from my LG-P500
Thank you! I've compiled fine CM7 and it works! But... How I can compile "Launcher2" from CM/Android sources?
EDIT: mmm package/apps/Launcher2
0x0v3rfl0w said:
Thank you! I've compiled fine CM7 and it works! But... How I can compile "Launcher2" from CM/Android sources?
EDIT: mmm package/apps/Launcher2
Click to expand...
Click to collapse
so a new cm7 is coming from u?
mathew3184 said:
so a new cm7 is coming from u?
Click to expand...
Click to collapse
I don't know... Maybe I'll create it only for me... i don't know...
Related
hi guys....i've downloaded the last kernel sources of franciscofranco 2.35.10 kernel....i've added the sippolo's workaround and then increase the HZ value of the kernel(set at 500) for my custom rom.....after i've done
Code:
make thunderg-perf_defconfig
make zImage -j4
it stuck at this error
Code:
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_ioctl_down’:
drivers/input/touchscreen/mcs6000_ts.c:430:6: error: implicit declaration of function ‘gpio_configure’
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_probe’:
drivers/input/touchscreen/mcs6000_ts.c:733:25: warning: unused variable ‘hw_ver’
drivers/input/touchscreen/mcs6000_ts.c:733:17: warning: unused variable ‘fw_ver’
make[3]: *** [drivers/input/touchscreen/mcs6000_ts.o] Errore 1
i don't understand why......i think it is a lib problem.....but seems that all libraries are imported!!!can anyone help me??? thnx in advice
Which toolchain?
Sent from my LG-P500 using XDA Premium App
lupohirp said:
hi guys....i've downloaded the last kernel sources of franciscofranco 2.35.10 kernel....i've added the sippolo's workaround and then increase the HZ value of the kernel(set at 500) for my custom rom.....after i've done
Code:
make thunderg-perf_defconfig
make zImage -j4
it stuck at this error
Code:
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_ioctl_down’:
drivers/input/touchscreen/mcs6000_ts.c:430:6: error: implicit declaration of function ‘gpio_configure’
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_probe’:
drivers/input/touchscreen/mcs6000_ts.c:733:25: warning: unused variable ‘hw_ver’
drivers/input/touchscreen/mcs6000_ts.c:733:17: warning: unused variable ‘fw_ver’
make[3]: *** [drivers/input/touchscreen/mcs6000_ts.o] Errore 1
i don't understand why......i think it is a lib problem.....but seems that all libraries are imported!!!can anyone help me??? thnx in advice
Click to expand...
Click to collapse
.35 kernel have new GPIO library, you should code sippolo's workaround into new driver, do not replace whole file.
mik_os said:
.35 kernel have new GPIO library, you should code sippolo's workaround into new driver, do not replace whole file.
Click to expand...
Click to collapse
Aaaaa i don't know that thanks now it works ;-) now the next step i'm ttying to port the acer liquid multitouch fix thanks mik
Sent from my LG-P500 using XDA App
If you can fix also the tethering and the random bugs
use pdanet for tethering
now i'm stucking at this error...((
arch/arm/mm/built-in.o: In function `__flush_icache_all':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/arch/arm/include/asm/cacheflush.h:402: undefined reference to `swapper_space'
arch/arm/mm/built-in.o: In function `____atomic_set_bit':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/arch/arm/include/asm/bitops.h:46: undefined reference to `swapper_space'
arch/arm/mm/built-in.o: In function `spin_unlock':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/include/linux/spinlock.h:324: undefined reference to `swapper_space'
mm/built-in.o: In function `sync_page':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/filemap.c:190: undefined reference to `swapper_space'
mm/built-in.o: In function `set_page_dirty':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/page-writeback.c:1181: undefined reference to `swapper_space'
mm/built-in.o:/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/page-writeback.c:1335: more undefined references to `swapper_space' follow
make: *** [.tmp_vmlinux1] Errore 1
Click to expand...
Click to collapse
seems another time a library problem... anyone can help me??
lupohirp said:
now i'm stucking at this error...((
seems another time a library problem... anyone can help me??
Click to expand...
Click to collapse
What have you patched?
It just says it's missing the swapper_space function header, it's not defined.
franciscofranco said:
What have you patched?
Click to expand...
Click to collapse
nothing franco....i've only added sippolo's workaround for base to port acer liquid multitouch fix and set kernel to 500hz i've worked only on mcs6000_ts......but it stuck at this error i don't know why!!! i think it is a library problem....something that is missing...but i don't know what are the libraries that i must install if it is this the problem!(
You downloaded the latest sources? Because I haven't compiled it, I just merged the patches, I might have forgot to apply something. In this case it says it misses the swapper_space reference.
http://lxr.free-electrons.com/source/mm/swap_state.c#L40
http://lxr.free-electrons.com/source/include/linux/mm.h#L771
http://lxr.free-electrons.com/source/include/linux/swap.h#L319
Add the swapper_space code to those files and compile again.
franciscofranco said:
You downloaded the latest sources? Because I haven't compiled it, I just merged the patches, I might have forgot to apply something. In this case it says it misses the swapper_space reference.
http://lxr.free-electrons.com/source/mm/swap_state.c#L40
http://lxr.free-electrons.com/source/include/linux/mm.h#L771
http://lxr.free-electrons.com/source/include/linux/swap.h#L319
Add the swapper_space code to those files and compile again.
Click to expand...
Click to collapse
yes franco i've downloaded latest sources! thanks now i'm going to add it and then try!
franco the swapper_space code that you posted is already there in the three files((
I dunno, I have to leave now, I'll look at it later.
I'm sorry to disappoint you, but there ain't a problem with the kernel, I just compiled it without any modification, just like it is in the sources and it compiles fine. Try to make clean and make distclean, then compile again.
franciscofranco said:
I'm sorry to disappoint you, but there ain't a problem with the kernel, I just compiled it without any modification, just like it is in the sources and it compiles fine. Try to make clean and make distclean, then compile again.
Click to expand...
Click to collapse
yeah franco i know.....i think it is a libraries problem on my linux distro.....but i have installe all the binutils and the header files yesterday also i have tried a dirty hack i tried to set CONFIG_SWAP=n in the thunderg_perf_defconfig configuration file....compiled succesfully but the phone doesn't started ...thanks anyway franco!
Hello I'm trying to compile cyanogenmod 7 with subskyper tass device to try to mantain this project update in line with the original philosophy: keep it 100% cyanogenmod without any tweaks
When I compile I face two errors that broke my compilation:
1-
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml:95: error: Resource at swap_volume_keys_orientation appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Errore 1
make: *** Eliminazione del file "out/target/common/obj/APPS/framework-res_intermediates/package-export.apk"
make: *** Attesa per i processi non terminati....
This one I commented out the line reguarding swap_volume_keys_orientation in file
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml
but when i continue...
2-
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/AndroidRuntime.o: in function android::gRegJNI:AndroidRuntime.cpp(.data.rel.ro+0x148): error: undefined reference to 'register_android_hardware_fm_fmradio(_JNIEnv*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Errore 1
make: *** Attesa per i processi non terminati..
Someone faced same problems?
Any ideas?
thanks a lot
Send PM With The Error To Subpsyke
t-r-e said:
Send PM With The Error To Subpsyke
Click to expand...
Click to collapse
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
mebitek said:
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
Click to expand...
Click to collapse
Best Luck Buddy Don't Give Up Early , We Look Forward To See Your Work As We Need To Keep Subpsyke Project Alive
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld:
Click to expand...
Click to collapse
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
coolsandie said:
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
Click to expand...
Click to collapse
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Now I have a signed zip to flash into my sgm.
It contains subskype cm7.2 tass device configuration and latest cm 7.2 sources update at 31-01-2012.
to check changes:
http://review.cyanogenmod.com/#q,status:open,n,z
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
Great news. Glückwunsch (don't know the english word at the moment).
Supercharger would be possibly good. Subpsyke said something to it but i don't rember clearly.
Keep up your work.
Sent from my GT-S5570 using xda premium
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
No not add anything. It s better. Completely clean
Inviato dal mio GT-S5570 usando Tapatalk
mebitek said:
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Click to expand...
Click to collapse
For the radio, I used my patch to add support for the bcm2xxx devices with proper seeking. It's on gerrit here: http://review.cyanogenmod.com/#change,10358
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
no no...no v6.
Just vanilla cm7...and thanks for the initiative and ABT!
dont add scripts..but maybe something from cm gerrit if u wish..but then it'll not be vanilla.
Has anyone already tried to build cyanmobile from source?I would try but squadzone is constantly updating his github so i should compile in the night...
and the meaning of the thread
dheeraj (dhlalit11) said:
and the meaning of the thread
Click to expand...
Click to collapse
The latest release had some problems for me so if someone had already compiled it i wanted to know his impressions before starting...:angel:
Hi guys...I've just built cyanmobile from source...I created on otapackage with the associated command...I'm waiting for someone wiser than me who could stop me worrying about possible bricks...As far as i know, having chosen the right repos, if something would go wrong, it wouldn't just boot...Am i right???...Waiting for your replies...
EDIT: Installed but not booting...Trying to compile again...
Recompiled and not booting again...I have a doubt: if i git clone the device configuration, do i have to extract also proprietary files?(i think not but i'm new on this so there could be differences)...Thanks for your help...
Asbusto said:
Recompiled and not booting again...I have a doubt: if i git clone the device configuration, do i have to extract also proprietary files?(i think not but i'm new on this so there could be differences)...Thanks for your help...
Click to expand...
Click to collapse
ask squadzone
Messi10 said:
ask squadzone
Click to expand...
Click to collapse
I finally made it...new ui is awesome!!!
Asbusto said:
Has anyone already tried to build cyanmobile from source?I would try but squadzone is constantly updating his github so i should compile in the night...
Click to expand...
Click to collapse
i cant, because i don know about how to build rom from source
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
sk806 said:
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
Click to expand...
Click to collapse
That is Samsung for ya. Maybe @g.lewarne could provide some insight
mikeyinid said:
That is Samsung for ya. Maybe @g.lewarne could provide some insight
Click to expand...
Click to collapse
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
sk806 said:
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
Click to expand...
Click to collapse
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
elesbb said:
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
Click to expand...
Click to collapse
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
sk806 said:
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
Click to expand...
Click to collapse
It is related to modules compiling from what I can gather. If I use Ktoonsez source, I don't get that error. However, I notice it doesn't compile any modules. I still get an Image in my boot directory. Do you? I think the kernel itself is safe to use. You could probably ignore this error.
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
sk806 said:
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
Click to expand...
Click to collapse
There are others I've seen using my commit (no credit) and didn't cherry-pick keeping the history. I believe the Image still flashes with or without though
I am having the same issue can you explain what was the issue ?
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
elesbb said:
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
Click to expand...
Click to collapse
Can you tell me what you did? I have the same error and i cant fix it ????
minealex2244 said:
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
Click to expand...
Click to collapse
Did you figure it out?
EncryptedCurse said:
Did you figure it out?
Click to expand...
Click to collapse
Uhm somehow. I used a script which ignored that error as your kernel image is already built and you shouldn't care about modules. But if you still want a fix then see my commit: https://github.com/minealex2244/AldeXus/commit/e89301766b3d251b285649a38ee4dea4f2871b99
This commit shows you what to remove (it may be the perfect fix or just an example of what you should do in your code).
Tell me if it helped.
Broken link
Hey, I'm having the same issue but I can't find your commit, could you please fix the link?. Thanks in advance.
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
LiL_Assassin said:
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
Click to expand...
Click to collapse
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Battlehero said:
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Click to expand...
Click to collapse
Sorry man my apologies. I am trying the kernel side of things not the actual rom
LiL_Assassin said:
Sorry man my apologies. I am trying the kernel side of things not the actual rom
Click to expand...
Click to collapse
What device variant do you have?
Battlehero said:
What device variant do you have?
Click to expand...
Click to collapse
My friend has c and I have I
LiL_Assassin said:
My friend has c and I have I
Click to expand...
Click to collapse
Upload the build and I'll have a gander.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
I sent you a pm.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
Though if the pm or this doesn't suit you. Here's an upload for you man. We could be doing things wrong.. But we would love the insight. (We think this is the furthest we have managed)
https://www.dropbox.com/sh/oaenmo464fxoycz/AAD1uk-18MaNp0fQVyyjTvPAa?dl=0