Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors
All d best little genius..
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Good luck bro!
OT: Mind I ask u why u changed ur name?
Sent from my LG-P500 using xda premium
andy572 said:
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Click to expand...
Click to collapse
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
mentalityx said:
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
Click to expand...
Click to collapse
You're right. But now i've already created them,so for the next time.
Bytecode said:
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Click to expand...
Click to collapse
dont know, the hw specs are the same - at least the same cpu/gpu and memory.
maybe only another camera^^
Building now
sooo... any news here?
Bytecode said:
Building now
Click to expand...
Click to collapse
Ha ha little bytecode is going again
Enjoy your build procedure well be waiting
Sent from my LG-P500 using xda premium
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
edit the Android.mk and remove that lib, its proprietary **** only
SWEATTAIMI said:
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
_Arjen_ said:
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
Click to expand...
Click to collapse
I'm getting really,really confused here
Adding vendor and device folder from andy gives me libskia ****,adding all from andy gives me framework ****,I don't know what to do here
Lemme basically explain: What files are needed for building/booting CAF ICS succesfully? Don't post stuff necessary for fixing bugs later
Thank you
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Bytecode said:
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
Click to expand...
Click to collapse
AOSP is not CAF, AOSP is not CM - each framework has its own code, it
has nothing to do with my changes, as you can see in my patches, its nothing
to make it "feel me like a phoenix"
To help you a bit:
some makefile variables cant be used in CAF, CM or AOSP and vice versa,
you have to look in relevant config variables ad what its used for,
than look in the source code if the name has changed or the variable
cant be used (or what ever).
_Arjen_ said:
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Click to expand...
Click to collapse
qcom repos are very needed to compile qcom related changes like audio/media.
Related
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
ztotherad said:
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
Click to expand...
Click to collapse
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
jt1134 said:
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
Click to expand...
Click to collapse
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
ztotherad said:
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
Click to expand...
Click to collapse
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
jt1134 said:
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
Click to expand...
Click to collapse
haha yeah, cause a few months back you said i had to sync the whole source.
it sounds like you've been working your ass off. lol
but that's definitely awesome. it makes it easier on us all.
Google has recently released the 3.10 linux kernel for Android. and CodeAurora has also got it. I was wondering if it's realistic to port in this phase. I tried to but I failed hard lol. Main reason to port the 3.10 series is that it should have a great battery life. I'm not sure whether it will run on KitKat since it's supposed to be for Android 5.0.
Links:
Google Kernel: https://android.googlesource.com/kernel/common.git/+/experimental/android-3.10
CodeAurora Kernel: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10
Anyone else attempted? If anyone could give me some more info about this I would be very happy!
Thread cleaned
How many times do we have to say it?
Keep this damn soap opera drama OFF XDA and stick to your Google +
How rude to bring all this crap in here to the OP's discussion
Next talk of secret kernels or banned members will be...trouble.
If you have no respect for XDA, then leave XDA...please!
Thank you for your cooperation
Friendly Neighborhood Senior Moderator
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
sorg said:
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
Click to expand...
Click to collapse
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
broodplank1337, what happens if you build a recovery and fastboot boot that?
xboxfanj said:
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
Click to expand...
Click to collapse
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
sorg said:
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
Click to expand...
Click to collapse
Yeah, there's a bunch of proprietary files specific to the SOC.
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
LLStarks said:
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
Click to expand...
Click to collapse
True. Caf does have some 3.10 device branches but none for 8960/8064, since those are not supported. Not sure why since they do support weaker chips such as 8226 and 8610. They do have some ramdisk changes for 3.10, but even with all that, I have no adb and no ramconsole on the optimus g (nexus 4).
Sent from my Optimus G using xda app-developers app
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
LLStarks said:
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
Click to expand...
Click to collapse
my s3 3.4-drm kernels supports it - patches came from here ==>
(s4 kernel is a WIP)
https://github.com/freedreno/kernel-msm/
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
LLStarks said:
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
Click to expand...
Click to collapse
We have offloaded all audio processing and mp3 decoding to the DSP. Thus allowing all 4 primary cores to sleep while playing audio. Media player app itself may use CPU cycles for UI updates when the screen is on. Working on WMA decoding...
Sent from my GT-I9505G using XDA Premium 4 mobile app
please make this kernel work with miui rom!
Hello everyone!
I present to you a paranoid android 3.99 port for our Xperia SP
Changelog:
V2: Device no longer hard reboots on bootanimation
V1: initial release
BUGS:
V2: Device doesn't boot (stuck on bootanimation and ADB offline)
V1: Device doesn't boot (hard reboot after 10 seconds of showing splash screen)
Download: PA_HUASHAN_V2
Now as you can see this ROM port is not booting but at least it doesn't do a hard reboot anymore! Currently I have no ADB access as it is listed as offline when doing: ADB devices of course I can't figure out the problem myself so I'm asking you guys for help. Since there is no logcat I know that it might be nasty to determine the problem and where the phone stops booting. I hope you guys can help me get this ROM to boot so we will finally have a working PA rom
thanks to: @-NickHalden- for his nice guide on how to port ROM's
@FXP for the base rom (cm10.2)
and the paranoid android team for the ROM that was ported (pa 3.99 from nexus 4)
Why don't you simply build from source?
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
I'm trying that as well but i'm having some issues getting these files working
<device>.adds
<device>.removes
pa_<device>.conf
pa_<device>.mk
If I could easily get/make these files a source build would already be here
Do you have a idea on how to create these files? or where I can get them?
for example for the .adds file I need something like this (this comes from nexus 4)
https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/mako.adds
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
kamarush said:
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
Click to expand...
Click to collapse
OK this is the .adds file I just made can you take a look at it?
huashan.adds
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
A long ago, i dont have see you on xda....
now you've back....great master
OK guys PA is currently building from source! now let's prepare to wait a long time xD
noahvt said:
OK this is the .adds file I just made can you take a look at it?
huashan.adds
Click to expand...
Click to collapse
This file will be almost the same as the cm dependencies. So this isn't good.
Levered said:
A long ago, i dont have see you on xda....
now you've back....great master
Click to expand...
Click to collapse
Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung
noahvt said:
OK guys PA is currently building from source! now let's prepare to wait a long time xD
Click to expand...
Click to collapse
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
I'm a huge fan of PA, I hope this one for our SP will progress nicely. Keep up the good work devs. Currently on CM coz stock is too laggy on my one.
Tapatalked from my Xperia P
noahvt said:
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
Click to expand...
Click to collapse
Just need to update/add pa_huashan to the pa vendor makefiles.
@kamarush
Remember you in developing the Xperia line 2011. Glad to see it with our Xperia SP. Some project in mind?
[QOUTE]Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung [/QUOTE]
Great, i really want rom by you. i hope you can make it soon..:good:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
noahvt said:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
Click to expand...
Click to collapse
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
MrSteve555 said:
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
Click to expand...
Click to collapse
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
noahvt said:
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
MrSteve555 said:
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
Click to expand...
Click to collapse
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
noahvt said:
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
MrSteve555 said:
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
Click to expand...
Click to collapse
Unfortunately it probably will have the freeze bug as it's based on the vendor blobs that bagyusz uses
Sent from my C5303 using XDA Free mobile app
This thread is NOT for general Q & A about using the kernel or configuring a specific version.
This thread IS for sharing source code or attempting to apply debugging to code changes.
In English: This is what a development thread really looks like. No downloads, No user manual.
Note to Mods: OT is welcome, so long as it is relevant to the kernel developer experience
Building the kernel 101:
A clean branch with only the build tools, ramdisks, and MacOS updates is at:
https://github.com/StarKissed/starkissed-kernel-trlte/tree/master
The stockish branch adds Linux patches, mainline updates, and SELinux mods
The deported branch is the customized version described in the OP feature list
You are going to need a few things, especially if building this kernel for MacOS.
GCC 4.7 (This is the version Samsung's documentation listed)
An updated mkbootimg (Must have DTS support)
A dtbtool (Included in the source, but only for Linux)
Insomnia (Not a requirement, but it will help you in the long run)
For MacOS, the tools are available from the following repositories:
https://github.com/StarKissed/android-toolchain-eabi-4.7
https://github.com/StarKissed/starkissed-build-tools
Let's jump ahead a moment for those of you who have built kernels and notice your boot.img is only around 11 MB while the versions you see listed here are all roughly 14 MB. This is where the new mkbootimg and dtbtool are necessary.
Attempting to retrieve the commandline arguments from the boot.img will not tell you one important piece:
Code:
./dtbtool -o dt.img -s 4096 -p ../scripts/dtc/ ../arch/arm/boot/dts/
chmod a+r dt.img
mkbootfs (ramdisk creation)
mkbootimg (mkbootimg params) --dt dt.img
This takes the DTSI that was built into a dtb as one of the first steps in the compile process and turns it into an image that is appended to the end of the boot.img. The dt.img just happens to be about 3 MB. (11 MB + 3 MB = 14 MB)
If you grabbed the original Samsung kernel source, you may notice that their default compile script directs the build to an "out" folder in the root of the kernel directory.
The obvious advantage to this is that their clean command runs into some errors, so the clean process is simply deleting the "out" folder and making a new one.
This doesn't work for a lot of the custom components you may want to add to your kernel, though. Some modifications, such as intelli-thermal, rely on a subdirectory that is referenced in the Makefile.
Building to this out folder will result in an error because it cannot find the output of that component, but building in the tree, or actual source, will also result in an error. The lesser of two evils is to fix in-tree builds.
Code:
Instructions for TRACE_INCLUDE_FILE in include/trace/define_trace.h say
"the path is relative to define_trace.h, not the file including it".
Fix in-tree compilation by making the path relative to define_trace.h.
What this means is that when you have a line that refers to the TRACE_INCLUDE_PATH or an include reference to a file that uses a relative location instead of a global, these need to be updated
The only two files that currently require updates in the stock source code are
Code:
drivers/scsi/ufs/ufs_test.c
#include -> #include "../sd.h"
and
Code:
drivers/video/msm/mdss/mdss_mdp_trace.h
#define TRACE_INCLUDE_PATH . -> #define TRACE_INCLUDE_PATH ../../drivers/video/msm/mdss/
If you want to be able to debug your kernel, you will need to enable last_kmsg.
Open up the arch/arm/configs/apq8084_sec_defconfig and add
Code:
CONFIG_SEC_DEBUG_NOCACHE_LOG_IN_LEVEL_LOW=y
CONFIG_PRINTK_PROCESS=y
CONFIG_SEC_DEBUG_LOW_LOG=y
More to come soon...
This is a great idea!
Looking fwd to seeing this thread take off...it will be very interesting for sure.
Sent from my SM-N910W8 using Tapatalk 2
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
I use git am -3 so that any issue defaults to a merge then git mergetool to resolve it.
Switching the index in the dtsi that was modified was the only change to show it that I remember needing.
https://github.com/StarKissed/stark...mmit/695abe187620acf513b33237042925d60a99f0c1
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
Im back too.
ktoonsez said:
Im back too.
Click to expand...
Click to collapse
right on
any thoughts my man?
friedrich420 said:
right on
any thoughts my man?
Click to expand...
Click to collapse
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
ktoonsez said:
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
Click to expand...
Click to collapse
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
friedrich420 said:
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
Click to expand...
Click to collapse
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
ktoonsez said:
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
Click to expand...
Click to collapse
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
I got lost in Freedom Wars for a bit. I need to figure out an issue with thermal then I'll be back
friedrich420 said:
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
Click to expand...
Click to collapse
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
ktoonsez said:
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
Click to expand...
Click to collapse
Unfortunately same bahavior my man..
friedrich420 said:
Unfortunately same bahavior my man..
Click to expand...
Click to collapse
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
EDIT:
The guy I am testing with has the "G".
ktoonsez said:
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
Click to expand...
Click to collapse
the F...
friedrich420 said:
the F...
Click to expand...
Click to collapse
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
twistedumbrella said:
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
Click to expand...
Click to collapse
I started with stock N910F ramdisk in version "C", version "D" went back to my original universal ramdisk you can try the "C" and see if anything changes:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014C.zip
friedrich420 said:
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
Click to expand...
Click to collapse
That is exactly what I just merged in so the "D" that wont boot for you is pretty much the same thing, lol. See what happens on the "C" version which is stock N910F ramdisk.
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918