Related
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.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png
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
PS: The anime character "Haruhi Suzumiya" is copyright of its owner
PS: arise fix
Open up a file manager and go to the root folder. You need to have SuperSU installed for this
You'll see a folder called su, go to /su/su.d
In this folder create a text file, label it as "permissive.sh" and put the following code in
Code:
supolicy --live "permissive *"
Then save the file and go to recovery and flash arise and Dolby Atmos addons again and then reboot
It should now work
Stop reading my bs! Here's the download link
https://srv1.botstack.host:8000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
Or
http://srv1.botstack.host:9000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
This is a project that started as a kernel for my ROM and that is what it's going to be
It can be flashed on other ROMs too and I will gladly provide support however I can't guarantee results
Do note that this is a "secure" kernel. It has many of the security patches merged from CAF and selinux enforcing is forced with no way to go to permissive
What about v4a?
Get SuperSU and input these lines in a terminal
Code:
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
allow audioserver audioserver_tmpfs:file { read write execute };"
Wait for a few seconds, swipe away v4a from the recent apps list and launch it again. It should now work
Why isn't a thermal throttling tweak included inside this kernel?
Well in my usage the kernel is so fast that thermal throttling modifications are not needed. You can apply if you want
Currently known bugs?
Nothing
OMG you're copying boeffla!
Relax. I used boeffla's anykernel base as I was in a hurry and didn't have time to make my own zip. Also, boeffla's anykernel zip is one of the best around trust me
What are the features?
Too lazy to write, check back here in a few days but there are quite a lot of features you're gonna like
I'm a nerd, I support the GPL, I'm gonna take you down because you didn't release the source code and neither did you tell me whose toolchain you used!
Bro you need to take it easy
Toolchain: https://bitbucket.org/mdalexca/aarch64-linux-android-6.x
Kernel source: https://github.com/anupritaisno1/android_kernel_oneplus_msm8994_custom
I'll try it when there is ROM with new security patch. Looking forward to it!
NeoVsk said:
I'll try it when there is ROM with new security patch. Looking forward to it!
Click to expand...
Click to collapse
I don't care about other ROMs but I'm actively adding security patches into my kernel's source so relax
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
chxei said:
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
Click to expand...
Click to collapse
Not at all
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
NeoVsk said:
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
Click to expand...
Click to collapse
Known issue
anupritaisno1 said:
Known issue
Click to expand...
Click to collapse
Could you include fast charge in following builds?
NeoVsk said:
Could you include fast charge in following builds?
Click to expand...
Click to collapse
That was my mistake. I forked fast charging from halogenos without realizing that it never worked
This is something I sadly can't fix. You'll have to wait for halogenos devs to update this
Fast charge coming in next build like....
Camera bug fixed!
I don't usually gamble but when I do I buy note7
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
xarisCY said:
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
Click to expand...
Click to collapse
If you start the camera, my kernel fails to turn it off so the camera will be unavailable for use after the first time you use it and you'll have to reboot
I'm working on fixing this bug. Why are you interested in this bug?
Sorry, my mistake. I though was something different.. Sorry
Where can i download naruhi ROM?
Kernel has been updated
All known bugs squashed!
Seems cool but an enforcing only kernel has its downside for me. I'm not sure if arise works with an enforcing kernel, would love to see a permissive version as well.
anupritaisno1 said:
Kernel has been updated
All known bugs squashed!
Click to expand...
Click to collapse
Great job! But I'm still getting only about 700mA when charging
Although the Kernel make the ROM very smooth but it's not battery friendly.
playkish said:
Although the Kernel make the ROM very smooth but it's not battery friendly.
Click to expand...
Click to collapse
On my phone I can't find a difference between my kernel and stock
Also this is a cm kernel. Expect some general battery drain
That being said, I've really worked hard on wakelocks and doze
Hi got your quote on bens kernel page @anupritaisno1, could you explain me more about this kernel. I guess it will break the focus of my camera due to some new commits, etc as bens kernel v5 had done the same to me. Also, as im using bens RR Rom, will this have any bugs or side affects with that rom (i had flashed boeffla kernel and had to face a lot of problems on his rom such as the xposed modules becoming inactive or not performing after some time, etc.) and last main thing, idle battery drain
complied from https://github.com/therootlord/android_kernel_motorola_msm8953
not my code, just sharing because i keep seeing people complain about magisk mods
Features:
-F2FS bug fixed (can flash magisk modules on stock)
-not sure what else
Flash in twrp
TODO:
-kexec-hardboot
-disable force-decrypt
Stock NPS26.116-45 kernel zip: Link
This was my first kernel compilation, let me know if something isn't working
Extreme-Plus-Kernel-nrdgd-1.zip compiled on nov-18-2017 Link: Google Drive
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
UPDATE 2 - wifi fixed
Extreme-Plus-Kernel-nrdgd-2.zip compiled on nov-19-2017 Link: Google Drive
It boots with aex 7.x - to early to say more
Phazmos said:
It boots with aex 7.x - to early to say more
Click to expand...
Click to collapse
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Ae3NerdGod said:
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Click to expand...
Click to collapse
Didn't notice it was broken - us version here.
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Would you mind sharing the build sequence/commands?
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Phazmos said:
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
EXKM seems to work fine on AEX rom using the butterfly governor good battery life and smooth.
revengineer said:
Would you mind sharing the build sequence/commands?
Click to expand...
Click to collapse
i had to use his toolchain, and fix a few includes for it to work. im going to try different ones to try and figure out the lag, maybe thats not whats causing it but im new at this . been reading logs all day
smokinjoe2122 said:
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Click to expand...
Click to collapse
yeah, sorry. new at this. dont know if @geneticengineer wants me passing his old kernels he hasnt posted around either. if you can find his afh, he has a really old one on there thats way faster. im still learning, im working on pulling the stock modules and kernel to make a back to stock zip rn actually will post soon if you keep using it, it speeds up a tiny bit lol
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
planning kexec hardboot and disable force decrypt when i get the hang of this.
Phazmos said:
Just a note on kernels
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
actually i think i missed something in defconfig that enables the secondary processor, im also going to switch toolchains, expect a new kernel in a few days
Here's a link to GeneticEngineer's AFH-hosted original kernel from the TWRP thread. I don't think he'll mind it being reposted in this thread. This should tide people over until you can iron out the bugs in your build.
https://www.androidfilehost.com/?fid=745425885120765462
Thanks for picking up the baton and running with it, incidentally. I did ask GeneticEngineer to create a thread for his kernel but perhaps he missed the message.
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
i actually get those weird reboot to recovery bugs all the time on this device and 2 things fix it, booting to bootloader and picking "start" or a full restore
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
bishop0114 said:
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
Click to expand...
Click to collapse
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel).
bishop0114 said:
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Click to expand...
Click to collapse
A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Jleeblanch said:
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel). A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Click to expand...
Click to collapse
If you need someone to beta test it, let me know. It is the only reason I am not running stock.