Database Develop

[ROM] Unofficial Cyanogenmod 12.1 with CAF Kernel 3.4.0 [2015-09-09]

Code:
#include <std_disclaimer.h>
/*
* Your 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.
*/
This ROM is an unofficial build on CyanogenMod 12.1. Originaly (back in November 2014), the project was only about the kernel but I thought that a full ROM might a better.
So, why would you install this ROM ?
The main reason would be to upgrade significantly the kernel :
- get rid of the old LNX.LA.3.5.1 kernel base (from February 2014) and switch to a brand new LA.BF lollipop base
- to get a smoother experience of CyanogenMod
- to enjoy some CAF taste in all of his glory
- if you are an enthusiast
This ROM uses custom HALs so I'm not responsable of incompatibility with eventual custom kernels and I won't "Add support"
ROM Features :
- Based off latest generic CyanogenMod 12.1 nightly source
- OTA updates via built-in CMUpdater (LZMA Compressed)
- Vanilla CAF LA.BF.1.1.1.c5 display HAL (improved display performance)
- Vanilla CAF LA.BF.1.1.1.c5 media HAL (improved video performance)
- Vanilla CAF LA.BF.1.1.1.c5 audio HAL (improved audio performance)
- Latest Motorola LPB23.13-37 5.1 Vendor Files
- Latest kernel.org f2fs binaries
- Vanilla CAF LA.BF.1.1.1.c5 Media Codecs / Audio Policy / Bluetooth configs
- LZMA Compressed recovery images
- QCOM Bionic Optimizations
Kernel Features :
- Based off latest CAF LA.BF.1.1.1.c5 kernel source from Qualcomm
- As clean as possible, it matches CAF
- Vanilla CAF LA.BF.1.1.1.c5 Wi-Fi Prima driver (better wifi performance)
- Uses ZEN i/O Scheluder by default
- First Lollipop Overclock
- Underclocking
- Smartmax Governor
- My own akm8963 driver re-work for LPM/HBM mode
- The best is in comming
But, why is it in alpha ?:
It's in alpha state because not many people tested it and maybe there are some unknown bugs.
Speaking of bugs here they are :
Code:
[B]Known bugs[/B]
- 5 sec blackscreen at boot (doesn't affect bootime) [B][COLOR="red"][/COLOR]the first boot blackscreen is even longer so just wait and it will boot, builds or tested do not worry[/B]
- Offline charge is broken (same reason as blacksreen)
I released even if those bugs because they doesn't break the ROM experience itself (and because I wait for realeasing this ROM since ages)
They will, of course, fixed as soon as possible.
Download :
cm-12.1-20150909-UNOFFICIAL-h2o64-falcon.zip - 206.7 mo (AFH Mirror) #CHANGELOG
Old Downloads :
cm-12.1-20150827-UNOFFICIAL-h2o64-falcon.zip (AFH Mirror)
How to install ?
If you are coming from an official CM12.1 Nightlies you should dirty flash (flash my ZIP on top of your existing rom without too much issues). If you encounter any issues (report and) do the method detailled bellow.
1) Place ROM & Gapps in your virtual SD
2) Reboot in Bootloader Mode
3) Go to "Recovery" (Vol -) and confirm (Vol +)
4) Wipe Data/Factory Reset
5) Wipe Dalvik cache
6) Install the ROM zip
7) Install the Gapps zip
8) Install SuperSU zip
9) Reboot
Sources :
All repositories are on the cm-12.1-caf branch
device/motorola/falcon : https://github.com/h2o64/android_device_motorola_falcon
kernel/motorola/msm8226 : https://github.com/h2o64/kernel_msm
manifest and build instructions : https://github.com/h2o64/android_local_h2o64
Credits :
- CyanogenMod and its contributors
- CAF (aka Qualcomm)
- Motorola
XDA:DevDB Information
Unofficial Cyanogenmod 12.1 with CAF Kernel 3.4.0, ROM for the Moto G
Contributors
h2o64
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Alpha
Current Beta Version: 2015-09-09
Beta Release Date: 2015-09-09
Created 2015-08-27
Last Updated 2015-09-11

Changelogs
New build 20150616
Code:
- Initial release
Download :
cm-12.1-20150827-UNOFFICIAL-h2o64-falcon.zip (AFH Mirror)
Click to expand...
Click to collapse

@h2o64 Good work!

Flashhhh said:
@h2o64 Good work!
Click to expand...
Click to collapse
1000 posts YAY !

I'm not a fan of CM but my brain forces me to try this...

Can't try this ROM right now since I use my moto g as my daily driver but good to see some nice development going on!

pfufle said:
Can't try this ROM right now since I use my moto g as my daily driver but good to see some nice development going on!
Click to expand...
Click to collapse
It's fully stable, you just don't see 5 sec from the bootanimation.

I will install it and try it but I need to charge my Moto G Good job !!!

Damn, bootanimation doesnt show at all, i reflashed three times thinking something was wrong, and i lost patience thinking my phone turned off after google logo, but it booted. It works great btw, stable and all, and overall fast. Nice work. Now just remove the stupid cm theme engine and implement layers, and you have most custom unoffical cyanogenmod rom.

DeHuMaNiZeD said:
Damn, bootanimation doesnt show at all, i reflashed three times thinking something was wrong, and i lost patience thinking my phone turned off after google logo, but it booted. It works great btw, stable and all, and overall fast. Nice work. Now just remove the stupid cm theme engine and implement layers, and you have most custom unoffical cyanogenmod rom.
Click to expand...
Click to collapse
Yeah, the bootanimation bug is annoying, but you'll see that you get just a 5 sec blackscreen on reboots. It was just the first boot xD
Hmmm ... I don't think I will remove the CM Theme Engine : as I said, this project wasn't a ROM originally (I made a ROM to avoid HAL issues actually) I just wanted to make big background optimizations. So on the apparence/look part, I won't differ from CM.

My opinion (is still black screen after flashing). Just make optimizations and don't change the features or other things. To be just an optimized CM 12.1 ROM.

h2o64 said:
Yeah, the bootanimation bug is annoying, but you'll see that you get just a 5 sec blackscreen on reboots. It was just the first boot xD
Hmmm ... I don't think I will remove the CM Theme Engine : as I said, this project wasn't a ROM originally (I made a ROM to avoid HAL issues actually) I just wanted to make big background optimizations. So on the apparence/look part, I won't differ from CM.
Click to expand...
Click to collapse
Too bad, well i guess i'll stay with the stock theme then, because i seek for stability, and that's pretty rare nowadays.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
And we can expect updates on this project? I'm not asking for ETA, i just want to be shure this is not a one time thing

omg, thanks for this @h2o64.. gonna try it out...

Eurofighter_ty said:
My opinion (is still black screen after flashing). Just make optimizations and don't change the features or other things. To be just an optimized CM 12.1 ROM.
Click to expand...
Click to collapse
This 5 sec black screen will stay until I fixed SOL in MDSS.
DeHuMaNiZeD said:
Too bad, well i guess i'll stay with the stock theme then, because i seek for stability, and that's pretty rare nowadays.
And we can expect updates on this project? I'm not asking for ETA, i just want to be shure this is not a one time thing
Click to expand...
Click to collapse
All my working projects (AOSParadox, TWRP, or CM now) are getting continuous work and updates. I just don't like to post "empty" updates with an un-interessting changelog.
I just made the first stage of this project xD So much is about to come
Thanks for supporting

forgot to ask, if compile the kernel and use to latest nigtlies. it will be okay? @h2o64

hurtsky said:
forgot to ask, if compile the kernel and use to latest nigtlies. it will be okay? @h2o64
Click to expand...
Click to collapse
Sure

Oops
Forgot to add a kernel feature in the list
- My own akm8963 driver re-work for LPM/HBM mode
Click to expand...
Click to collapse

h2o64 said:
Forgot to add a kernel feature in the list
- My own akm8963 driver re-work for LPM/HBM mode
Click to expand...
Click to collapse
Dual sim working ? I mean this is cm so hopefully it is working .. But when I flashed it , it stays on black screen..... For almost 2 min

sachoosaini said:
Dual sim working ? I mean this is cm so hopefully it is working .. But when I flashed it , it stays on black screen..... For almost 2 min
Click to expand...
Click to collapse
Yes it should be supported
It's normal don't worry

Hi,
I installed all my apps about 30 apps and every app work without problems fc or other problems except one: Zonga - it's a music streaming app developed by Vodafone Romania and in other ROMs it's working but here it doesn't have sound and If I press play doesn't play from first I need to skip the track and the next one plays without music.
I will attach soon a logcat.

Zenfone 2 Recoveries [Z00A[[Z008][Z00D][TWRP][CM-RECOVERY]

RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE​
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom​
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source ​
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03

Niceeeeeeeeeeeeeeeee

Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.

Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.

jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk

This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)

Is there an easy way to update my TWRP? Any apps that can do this for me?

roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.

Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??

Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.

Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD

I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk

rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk

espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk

So what's the difference of this TWRP and TheSSJ TWRP?

jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)

Thread moved to proper forum

jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.

Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.

Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted

[KERNEL][6+] s1mple espresso

I don't like large threads. My old espresso needs an up, so where we go.
It's based on latest omap4 common by unlegancy-android with these changes:
Compiled with custom Linaro GCC by @Christopher83.
CPU underclocked to 200MHz and overclocked up to 1400MHz.
GPU overclocked up to 512MHz. (384 default)
Custom voltages based on user experience.
Touch boost from franco kernel. (default boost set to 1200MHz)
Mini-FAQ:
Q: It works on all ROMs? Nougat?
R: It should work on any recent ROM who use omap4 common by unlegancy-android.
Q: All variants?
R: Due compatibility issues it could be not work on some devices/combinations, test it.
If won't work, please provide the variant, ROM, TWRP and last_kmsg if possible.
Click to expand...
Click to collapse
Q: Is safe 1400MHz on espresso?
R: Yes, passed my stability tests without problems.
Q: Works with ramdisk mods? (Magisk)
R: Yes, by AnyKernel2.
Code:
Change CPU max clock:
# echo 'x' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
x = 1080000, 1200000, 1300000, 1400000
Change GPU max clock:
# echo 'x' > /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq/frequency_limit
x = 153600000, 384000000, 512000000
Make boot and system backup before installation, download.
XDA:DevDB Information
s1mple espresso, Kernel for the Samsung Galaxy Tab 2
Contributors
dcastro172, Android-Andi, Ziyan, Sam Nakamura
Source Code: https://github.com/dcastro172/android_kernel_ti_omap4
Kernel Special Features:
Version Information
Status: Testing
Created 2018-04-23
Last Updated 2018-05-05

NICE.....Test It Soon

Didn't work for me
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2

Skarni said:
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2
Click to expand...
Click to collapse
I checked these ROMs and they use omap4 common, should have worked, maybe a ramdisk issue, to be fair I just tested it with recent OmniROM MM and it's working fine, I will try these.

THANK YOUUU FINALLY A NEW KERNEL HERE...does it work on nougat Roms?

Skarni said:
Tried to install it over AICP and just boot looped.
Then I installed ResurectionRemix and installed the kernel and had the same results.
Used TWRP 3.2.0.0
Thanks for trying to give us something new for our old Tab2
Click to expand...
Click to collapse
I tested today with ResurectionRemix by @smart-t78 and works well, the first boot without s1mple taken so much time, then I switch off and powered on, it booted.
Enrico03 said:
THANK YOUUU FINALLY A NEW KERNEL HERE...does it work on nougat Roms?
Click to expand...
Click to collapse
Yeah, tested with latest Lineage 14.1, however, I found an issue about frequency scaling, it boots with max frequency of 300MHz :laugh:
But you can change it using adb/terminal later.

New build up :fingers-crossed:
Now it's compiled with custom Linaro GCC by @Christopher83
Added touch boost from franco kernel :highfive: (interactive governor only, configurable)
Removed 200MHz in attempt to fix frequency scaling issues
OP updated.

Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.

Skarni said:
Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.
Click to expand...
Click to collapse
Doesn't magisk hide solve the Netflix problem? It should actually...
(sorry for the OT)
-------------------------------
Thanks @dcastro172 a new custom kernel sounds like fun, would be very cool to have something more or less stable with this significant OC added, I'll need to check this out when I'm near to my p5110 soon.. :good:
Sent from my Nexus 7 using XDA Labs

Skarni said:
Installed latest OmniRom 6 booted and then installed S1mple kernel. Left it to boot for 1 hour and it never booted. turned off and tried again, not luck.
re-installed my AICP backup.
Might try it with Slim6 when I have some time, but would prefer an unrooted rom since I use netflix.
Click to expand...
Click to collapse
Did you try with Andi's builds or from official Omni website? espresso3g or wifi? It will only work with recent Andi's builds, I'm running it and works well.

Doesn't boot on latest lineageOS and needs restoring boot & system to get back a working device, here's a demsg.log....
https://drive.google.com/file/d/1cJFmLO-e4lKODHTDYCRNDJ7RfGZK50G0/view?usp=drivesdk

dcastro172 said:
Did you try with Andi's builds or from official Omni website? espresso3g or wifi? It will only work with recent Andi's builds, I'm running it and works well.
Click to expand...
Click to collapse
Yep! Used Andi's unofficlal: omni_espressowifi-6.0.1-20180414-2301.zip
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
Sam Nakamura said:
Doesn't magisk hide solve the Netflix problem? It should actually...
(sorry for the OT)
Click to expand...
Click to collapse
"OT response to close": Only been able to get netflix to work by sideloading on ROM that is unrooted no gapps .
Magisk 16 has been problematic for me. 14 was okay. I would use magisk 14 to root to enable OC on s1mple kernel.

Sam Nakamura said:
Doesn't boot on latest lineageOS and needs restoring boot & system to get back a working device, here's a demsg.log....
https://drive.google.com/file/d/1cJFmLO-e4lKODHTDYCRNDJ7RfGZK50G0/view?usp=drivesdk
Click to expand...
Click to collapse
Skarni said:
Yep! Used Andi's unofficlal: omni_espressowifi-6.0.1-20180414-2301.zip
Click to expand...
Click to collapse
There's something very important which I'm missing, probably a very stupid issue since it works on my P5110, I read the dmesg and didn't see much useful logs, tomorrow I will investigate more. Thanks guys.

dcastro172 said:
There's something very important which I'm missing, probably a very stupid issue since it works on my P5110, I read the dmesg and didn't see much useful logs, tomorrow I will investigate more. Thanks guys.
Click to expand...
Click to collapse
FYI, I have a P3113,

The newer (maybe 2018) are default libion and it is said not to flash any custom kernels as they are not compatible.... So is this the reason some people have some trouble?

Excellent! Finally a overclockable kernel for our devices! Thank you very much Mr. dcastro172! Will test and report here ASAP!

drunkbum said:
The newer (maybe 2018) are default libion and it is said not to flash any custom kernels as they are not compatible.... So is this the reason some people have some trouble?
Click to expand...
Click to collapse
Well, recent ROMs with updated repos from unlegancy/lineageos builds with standard libion by default, my fork will only work with standard libion, some outdated ROMs use TI's libion and will not work, I think it's not the issue since @Skarni tried with latest OmniROM from @Android-Andi (which use standard libion) and won't worked for his P3113 while my P5110 woks perfectly.
And the dmesg from @Sam Nakamura is not much useful why it's from his reboot after the bootloop, I thought it has a SELinux issue but it's not, however I looked at second line and it looks like an old official build:
Code:
<5>[ 0.000000] Linux version 3.0.101-gbb24628 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sat Dec 9 09:46:13 UTC 2017
I'm trying figure it by looking at unlegancy/lineageos commits if I'm missing something but no luck yet.

galoneta said:
Excellent! Finally a overclockable kernel for our devices! Thank you very much Mr. dcastro172! Will test and report here ASAP!
Click to expand...
Click to collapse
Make sure do a backup why people are running in boot issues, if you run in boot issue please take a "cat /proc/last_kmsg > /sdcard/kmsg.txt" in TWRP terminal.

dcastro172 said:
And the dmesg from @Sam Nakamura is not much useful why it's from his reboot after the bootloop, I thought it has a SELinux issue but it's not, however I looked at second line and it looks like an old official build:
Click to expand...
Click to collapse
Not sure why the log referenced this old build, as said before I'm actually on the latest official lineageOS build from 11th February 2018 as seen on the screenshot.
I gladly provide more logs if you tell me exactly what could be of use for you...
Edit: the referenced kernel version is the one included in TWRP, check the build dates from official twrp.me and the log reference....
https://dl.twrp.me/espressowifi/
Sent from my OnePlus 3T using XDA Labs

Sam Nakamura said:
Not sure why the log referenced this old build, as said before I'm actually on the latest official lineageOS build from 11th February 2018 as seen on the screenshot.
I gladly provide more logs if you tell me exactly what could be of use for you...
Edit: the referenced kernel version is the one included in TWRP, check the build dates from official twrp.me and the log reference....
https://dl.twrp.me/espressowifi/
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Oh, this should explain, but you was using a different kernel when you flashed it?

[KERNEL][STOCK] MyKernel by Rudy [41.3.A.2.192]

MyKernel-V1 by Rudy​
Introduction:
Hi all, long time no see. Because of the pandemic, I started to learn about kernel and working on stock kernel just to add some performance for our beloved XZ. This is intended just for my private use, I hope you guys enjoy it. The commit in my github is a little bit mess. but it's working stable for me. Any suggestion or advice will be greatly appreciated. ​
Features:
Built from latest sony stock firmware 41.3.A.2.192
Upstream to the latest CAF tag LA.UM.6.5.r1-11700-8x96.0
Built kernel module inside the kernel
Backport new vmalloc https://lkml.org/lkml/2018/10/19/786
LZO-RLE for zram
Cherry-pick patches from https://github.com/AdrianDC/kernel-sony-copyleft/
Cherry-pick performance patches from sod kernel
Built using android gcc 4.9 (I always get random reboot or cannot boot at all using linaro so I am using standard compiler)
Disable ric, dm-verity
How to Install:
I upload 2 versions of this kernel, one for you who want to use drmfix and one for TA POC by munjeni:
For drm fix just flash the zip in TWRP or just extract the boot.img and flash it with fastboot
For you who want to use TA POC use rootkernel to add your own TA.img to MyKernel.img and then flash it with fastboot
Downloads:
V1.1 (test):
MyKernel-V1.1-drmfix
MyKernel-V1.1-nodrmfix
V1:
MyKernel-V1-drmfix
MyKernel-V1-nodrmfix
Bonus:
This is thermal config that I use. I just change the frequency value to start throttle when the temperature hits 54°C, change the sensor to msm_therm and reduce the sampling to 100.
CustomThermalConfig
OriginalThermalConfig_41.3.A.2.192
Credits:
@kholk (https://github.com/sonyxperiadev/kernel/pull/2016)
@AdrianDC (https://github.com/AdrianDC/kernel-sony-copyleft/)
@ SOD Team (https://github.com/sonyxperiadev/kernel/)
@tobias.waldvogel and @serajr https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Everyone ​
XDA:DevDB Information
[KERNEL][STOCK] MyKernel by Rudy [41.3.A.2.192], Kernel for the Sony Xperia XZ
Contributors
Rudy
Source Code: https://github.com/rudcode/android_kernel_sony_msm8996/tree/stable
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: V1
Stable Release Date: 2020-04-07
Created 2020-04-07
Last Updated 2020-04-08

The device is randomly restarting itself, has deep sleep problem

Layns said:
The device is randomly restarting itself, has deep sleep problem
Click to expand...
Click to collapse
Okay, that's weird. I've been using it for the last 3 or 4 days and didn't have that problem. Do you have any other mod installed?
What version are you using? Fyi, I use the TA POC one.

Rudy said:
Okay, that's weird. I've been using it for the last 3 or 4 days and didn't have that problem. Do you have any other mod installed?
What version are you using? Fyi, I use the TA POC one.
Click to expand...
Click to collapse
I've used the Drmfix version, i'm using the stock .192 version not installed in any mode just magisk installed
I set it up via fastboot

Layns said:
I've used the Drmfix version, i'm using the stock .192 version not installed in any mode just magisk installed
I set it up via fastboot
Click to expand...
Click to collapse
Okay, today I've experienced random reboot too. Can you test this version? I am reverting all caf commit to see if there is any problem there.
MyKernel-v1.1-drmfix.zip
MyKernel-V1.1-nodrmfix.img

Rudy said:
Okay, today I've experienced random reboot too. Can you test this version? I am reverting all caf commit to see if there is any problem there.
MyKernel-v1.1-drmfix.zip
MyKernel-V1.1-nodrmfix.img
Click to expand...
Click to collapse
I've now installed the new version you've given, the drmfix version. I'll write if there's any trouble in a few days, thank you, good work :fingers-crossed:

Deleted

Sony xperia xz or premium rondom reboot is common issue.
delete

Rudy said:
Okay, today I've experienced random reboot too. Can you test this version? I am reverting all caf commit to see if there is any problem there.
MyKernel-v1.1-drmfix.zip
MyKernel-V1.1-nodrmfix.img
Click to expand...
Click to collapse
MyKernel-v1.1-drmfix.zip it seems work... I cant see random reboot for now.

Device got ram problem, overspending, so the device freezes.

Layns said:
Device got ram problem, overspending, so the device freezes.
Click to expand...
Click to collapse
You are right. it is not stable modified kernel!

Can you share a new v2 version of the kernel you created on github? :|

[Kernel][11.15.2020][4.14.205][F2FS] Dragonfly for LG G8 Korean / US

Dragonfly Kernel v1.5 for the LG G8 Korean / US
Introduce
First of all, I'd like to thank Metaphysics team for giving the first custom kernel of G8 USA. Unfortunately I'm using G8 - Korean and they haven't released version for the Korean variant yet. I had to learn how to build a kernel for myself based on their kernel source. However, I want to learn more so I decided to compile the kernel from LGE open source. Now, my kernel is quite stable to be released and shared to the G8 community. You can call it the Dragonfly kernel.
Main Features:
- Based on LGE open source LMG820N_Android_Q_v20r: http://opensource.lge.com/osSch/list?types=NAME&search=g820n
- Linux-Stable-Upstream included to latest 4.14.205
- Next-Gen CAF-Tag LA.UM.8.11.r1-02600-NICOBAR.0 merged
- Regular CAF-Tag for SD855 merged LA.UM.8.1.r1-16200-sm8150.0
- Compiled by ProtonClang 12.0.0 with -O3 speed optimizations
- No VLAs
- Magisk included
- F2FS support
EAS related features:
- EAS implementation patched up to latest CAF state
- Disable autogroups and use cgroups for more efficient task placement
- CPU input boost
File System related features:
- Include rapid GC by @arter97
Network related features:
- Wireguard Support (Details)
- Add new TCP congestion algorithm: BBR2, agilesd
Memory related features:
- Include zstd
Wakelock Blocker:
- Add Boeffla Wakelock Blocker v1.1.0
- The most common and safe wakelocks are blocked by default: qcom_rx_wakelock;wlan;wlan_wow_wl;wlan_extscan_wl;netmgr_wl;NETLINK
How to flash the Kernel:
- You can flash the kernel zip file via TWRP or Magisk
- You can also extract the new_boot.img to flash it via fastboot mode
Known bugs:
- You tell me
DOWNLOAD:
Download is located always in
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases
Important: Read after Download
Be sure to turn off Secure start-up before flash this kernel
Credits:
- Metaphysics kernel team: https://github.com/KamioRinn/Metaphysics_LGE_G820_Kernel
- SGCMarkus for his guide of building kernel and TWRP
- Erick G for bringing new TWRP to G8 which supports F2FS
- Jean Carlos Bencosme for adding / picking kernel features
- Kirisakura for his great kernels
- Sultanxda for his simple_lmk
- LGE for the kernel open source
- All other great kernel devs
Contributors
quantan
Source Code: https://github.com/anht3889/LGE_G820_Kernel_Caf
XDA:DevDB Information
Dragonfly, Kernel for the LG G8
Contributors
quantan
Kernel Special Features:
Version Information
Status: Stable
Created 2020-09-16
Last Updated 2020-11-14

Previous versions, e.g. v1.4, don't work with the new TWRP 3.4. Therefore, I use Anykernel from v1.5. I recommend you follow the steps below:
1. Install magisk patched stock boot.img
2. Install new TWRP 3.4 from Magisk Manager
3. Reboot to TWRP
4. Install Magisk and reboot to TWRP
5. Install Disable Verity zip file and reboot to TWRP
6. Install my kernel Dragonfly v1.5
For newer version, i.e. v1.6, you don't need to repeat all steps above. You just want to flash thew newest Dragonfly.
And good news to you guys, TWRP 3.4 supports F2FS so I decided to enable F2FS support in my kernel as well. To make F2FS, please follow these steps:
1. Install my kernel v1.5
2 .Reboot to TWRP 3.4
3. Change file system of /data to F2FS
4. Replace the attached modified fstab to support F2FS of /data
5. Reboot
Note: You will lose your data.
In case you don't know:
- TWRP-3.4.0.0-G820N.zip and fstab.alphaplus for G8 Korean
- TWRP-3.4.0.0-G820UM.zip and fstab.alphalm for G8 US
Give credits to Erick G and @SGCMarkus for bringing TWRP to our phones.

Changelog:
v1.5:
- Fix touch issues for TWRP
- Add Kcal
- Add KLapse v5.0
- Update to 4.14.205
- Update lze and add lzo-lre for Zram
- Use Anykernel
v1.4:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
v1.3:
- Merge tag 'LA.UM.8.11.r1-04300-NICOBAR.0'
- Add ntfs and exfat support
v1.1 - v1.2 - Intial kernel

Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB

tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Thank your for pointing it out. I just add exfat and ntfs support to v1.3. Enjoy it

tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Which exact Model do you use? Is there a specific german Model nesessary?

Deutschmann said:
Which exact Model do you use? Is there a specific german Model nesessary?
Click to expand...
Click to collapse
It doesn't work on any LG g8s models...

@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code

Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs

Eduxki said:
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Click to expand...
Click to collapse
I'll check if I can make a version for LG G8s tomorrow. However, I can't guarantee that it will work for G8s or not since I don't have that phone. @Eduxki Give me your model, e.g. LMG810EA, and your operator / country as well. Is Android 10 available for your phone now since this kernel is for Android 10

quantan said:
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
-...
Click to expand...
Click to collapse
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.

kimba99 said:
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
Click to expand...
Click to collapse
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.

quantan said:
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
Click to expand...
Click to collapse
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated

Thank you for your efforts. Is there a GSI suitable for g820?

kimba99 said:
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Click to expand...
Click to collapse
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
lufan said:
Thank you for your efforts. Is there a GSI suitable for g820?
Click to expand...
Click to collapse
Havoc, Bliss, Lineageos GSI should be good.

quantan said:
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
Havoc, Bliss, Lineageos GSI should be good.
Click to expand...
Click to collapse
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing

wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)

lufan said:
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
Click to expand...
Click to collapse
kimba99 said:
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
Click to expand...
Click to collapse
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test

quantan said:
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
Click to expand...
Click to collapse
I saw this link in TG channel. It has been tested. Twrp can't access it

@lufan Have you tried it. If not please try it to double check. The ramdisk from KR boot is working.