Related
Some of you per'haps use Cyanogenmod nightly for S2 but their buidbot is out and no update since november, so I decided to compile it for me directly from the Repos it is long and needs a linux box so I decided to share it if you wants to update without compiling during ours.
It work well on mine, i Provide it without any warranty it's just extracted from cyanogenmod.com (see there for more details on the rom).
so : BACKUP before update !
Built on 12/09/11 : http://www.megaupload.com/?d=AWTI0B9Y
http://www.multiupload.com/72JF8PUMNX
I was ready to compile when I find on the CM forum somone who done it today :
latest build can be downloaded here:
http://codeworkx.de/...72011-galaxys2/
dont forget to install gapps
Click to expand...
Click to collapse
first tanks
include CWM?
superleeds27 said:
include CWM?
Click to expand...
Click to collapse
yes if you haven't already CM7 read this before : http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
This package does not includes google apps to flash separately (see the link above)
Great, thanks! I hope you don´t stop updating
per haps once a week since the build bot repaired...
any mirror pls ?
http://www.multiupload.com/72JF8PUMNX
Any known bugs with this release ?
I finally decided to leave stock (after having the device ~2 weeks) and wish to get something almost as stable as stock.
Thanks
Thanks for this
http://fitsnugly.euroskank.com/gigglebread/galaxys2/ ?
i've no info on it but seems to be an output compiled (that's the default name of the file when we excute the script) i've posted in first page a build from today tested and ok
Codeworkx posted a nightly on his site yesterday: http://codeworkx.de/wordpress/
Any apps available that make configuring Haptic Feedback easier?
Just build it: http://www.mediafire.com/?wn5i2mjbh2e2kl2
Whats changed since yesterdays build?
superleeds27 said:
Whats changed since yesterdays build?
Click to expand...
Click to collapse
This: http://review.cyanogenmod.com/#change,11072
Any easy to way to adjust Haptic Feedback, other than CM7 Settings?
Running Insanity 57, current to Dec 20 changelog. Forked if I can find the option to disable boot animation however, anyone know where it hides?
Cant you just delete the bootanimation.zip?
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
SaiyanGoku said:
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
adfurgerson said:
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
Click to expand...
Click to collapse
I'd suggest using the kernel you want since the beggining. Just Open up both files using winrar and delete boot.img from the GEE DU and replace it with the boot.img from the GEEB build that you like much.
Click to expand...
Click to collapse
so, does replacing the boot.img will do the job?
SaiyanGoku said:
so, does replacing the boot.img will do the job?
Click to expand...
Click to collapse
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
adfurgerson said:
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
Click to expand...
Click to collapse
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
jimbo77 said:
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
Click to expand...
Click to collapse
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
As stated earlier in the thread, No.
If you want to have HDR photos, you need to use a rom that's built on Mako/GEEB sources (like Vanir or PA or Carbon or Beanstalk or DU or 90% of the other roms on this forum.
CAF-based roms, including CM and Mokee use a completely different set of source code, so No, You Can Not add HDR to CM11 kernel.
If you want to learn about device development, sure, it might be possible. But just trying to Winzip Wizard everything into place is not going to accomplish Anything that you want it to.
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
jimbo77 said:
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
Click to expand...
Click to collapse
i learned C and C++ when i was in school. and about kernel coding, nothing yet.
i think i'm better using CM11 directly if ever wanted to switch from PA instead of nuking my phone experimenting on non-compatible kernels.
(i don't use HDR that often as post processing takes time and there isn't that much of a difference in image quality)
Hello,
This is a stock SeLinux permissive kernel and init.d activated for Samsung Galaxy Note Edge (N915F) for Lollipop 5.0.1.
There are inputs that is working also on N915FY.
The kernel was compiled from Samsung source LL_CIS kernel using Google toolcahin v4.8.
If you want to test it, please flash in cwm the attached file and report back. Please make a backup of your actual kernel (boot.img) befor flashing this one.
Special thanks to @Micky387 who advised me to update the source kernel (MH driverI), @Wuby986 for his support and guidance and @daxgirl for his advices.
My kernel source for N915F (N915FOXE1BOC6) is here.
Happy flashing.
PS. Kernel updated. Same functionality but some different info in "About".
Well you got further than I did .. Kept getting some driver file referenced so it would not complied.. Thanks for effort I hope you work it out soon.. Unfortunately I don't have time at the moment ..
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
micky387 said:
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
Click to expand...
Click to collapse
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
starbucks2010 said:
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
Click to expand...
Click to collapse
No need to flash module. The MHI module will be in the kernel so you have boot.img with all inside.
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
Wait one more day..
Or maybe earlier
Finally done.
Make backup of your actual kernel, flash the attached zip from post 1in cwm and please report back.I didn't check the init.d support but it should work.
Good, I'll try.
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Any chance that you would be willing to make this kernel compatible with the Sprint variety? Man.... I need my viper4android bro. Please. Lol
UpInTheAir said:
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Click to expand...
Click to collapse
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Well done mate ..... Yea
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Boot and works fine , nice one
Can this be used on N915FY as well?
I don't have any reports from N915FY users. You can try and tell us
Don't forget to make a backup first.
starbucks2010 said:
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Click to expand...
Click to collapse
Hey, no problem.
Just to clarify....
If you've made any (even minor) change to "Samsung" source, then you have to upload "your" complete source and link "your" source, not "Samsung" So if you've made the kernel permissive or even use a different toolchain or path, technically you have modified from original and is now "your" source If you use a custom defconfig, don't forget it too
github is well worth the pain I Google for answers all the time (how to do this and that), but still screw things up (sometimes majorly) now and then.
dubart said:
Can this be used on N915FY as well?
Click to expand...
Click to collapse
Using this kernel with a N915FY. Great job btw I can finally use viper audio which I've missed so much. Major props dude!
I'm gonna flash this on sprint variant either that or throw this device out my window
dinaps86 said:
I'm gonna flash this on sprint variant either that or throw this device out my window
Click to expand...
Click to collapse
Lol it booted just no data. Yaaayyy!!!
I see that there are other people who are interested in Selinux permissive kernels.
So, if you want, I can add selinux permissive to any samsung kernel as long as you provide me 2 files: your original kernel (boot.img) from the ROM you want to flash and the Kernel.tar.gz - source kernel from Samsung site. In order to get Kernel.tar.gz file you'll need to download the kernel source file (~ 1Gb) from Samsung site, open the archive and upload ONLY the Kernel.tar.gz (~ 100-150 Mb) and the readme file from the archive to some sharing site. Then, I'll try to compile that kernel for you.
There are also downsides. I cannot stay up to date will all new commits done to the kernel source so I'll compile your kernels only with info that I have at that date. If you fork the github and find kernel source updates, I can add them.
PS. I only set up a working PC with Ubuntu and Google toolchain v4.8. If you find any information that this setup is not suitable for compiling your kernel, then there is no point of providing me the above files.
Best regards.
OP updated with some Antutu screen shots.
Hi,
I would like to request some testers who are currently running stock MIUI to test the stock kernel. Feel free to comment below.
Instructions:
- You should be on CWM
- Download zip
- Flash kernel
- reboot
- cross your fingers
What to check:
- WLAN -> see if it works
Source:
https://github.com/emceethemouth/kernel_cancro/tree/mi-stock
WLAN:
git://codeaurora.org/platform/vendor/qcom-opensource/wlan/prima/
blah blah blah
Wifi not working after flashing the kernel.
Armin_van_buuren said:
Wifi not working after flashing the kernel.
Click to expand...
Click to collapse
Hold on I'm uploading a new one.
Edit:
Attachment updated
Wifi doesn't work, everything else does.
alphoz said:
Wifi doesn't work, everything else does.
Click to expand...
Click to collapse
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks to you, and all your hard work. I would also like to mention that the miband unlocking worked a lot better with your kernel than the MIUI stock one. Thanks again.
Wow. Thanks GNOME... Good to kernel for miui
Sent from my MI 3W using Tapatalk
Audahudi also build stock miui kernel. This also has same bugs, no WiFi, cit etc menu take while to open.
One bug I have doubt of is, whether all 4 cores work simultaneously. In my testing I saw most time 2 work, sometimes 3. Benchmarks also give scores like that. Also CPU performance control pro, which can set individual frequency of all cores could make 2 cores work together.
Any app you know which can monitor every core usage over period of time?
The 2nd bug is what I'm curious off, as I don't have WiFi lol.
Plus these miui kernel can be used in some custom Chinese KitKat ROMs. Iuni is 1 example, fiui I havent tested.
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Pepe.II said:
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Click to expand...
Click to collapse
That happened to me when I did all that.
I found no solution, so I left it.
@Pepe.II you should see the issues section, I'm always there.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/16
@Gnome
on what miui we should try stable or developer ?
Stable just to be safe.
Edit: @alexret, can you try the instructions on that misleading turorial but use my kernel source? Branch is mi-stable. I have a feeling it'll work
@Gnome anything with the bug I have doubt of?
@Gnome I tried to flash your kernel STX-MI-PRIMA-TEST-2015-06-24 from first post attachment.
Its only kernel, no modules included. This has a effect, that no modules are loaded while booting. When i try load module manually, it crashes with this message:
[email protected]:/ # insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)
Please, can you compile kernel with modules? Thanks
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Gnome said:
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Click to expand...
Click to collapse
As far as I understand it, you did not compile drivers as modules but compile them as part of the kernel?. Ok. But why, when I look in to kmesg log (/proc/kmesg), I find not a single mention about the WLAN. That's weird. Are you sure, that WLAN part is compiled correctly?
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Gnome said:
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Click to expand...
Click to collapse
Sorry, I only asking, because I do not understand how you work with drivers. Prima WLAN you set as a module but I do not see any module in a flashable zip. You assume that your kernel will use modules from stock MIUI kernel?
I do not criticize, just asking. if this sounds like criticism, so it is due to my poor English and i am sorry.
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