[3.18.140][EAS][O/Pie][GESTURES]Chimera Kernel[FINAL]

[GuestK00277]

Installed Chimera on land Havoc 2.4 because of Google drive not working issue.
Now the charging speed is good but phone heating extremely, around 48 and 49 degree. Any solution?

Try dieD Kernel
https://drive.google.com/drive/folders/1QLP6UpWMUO_Em0aWtTaL1FAN7UNpdwTa

 

[drjmvgami]

Try dieD Kernel
https://drive.google.com/drive/folders/1QLP6UpWMUO_Em0aWtTaL1FAN7UNpdwTa

It's for Land? Can I flash on Havoc OS?

 

[Unlucky01]

It's for Land? Can I flash on Havoc OS?

I am on Land with Havoc official and I do not have any problems.

 

[drjmvgami]

I am on Land with Havoc official and I do not have any problems.

Yeah, flashed it and works without problem. Google drive also working.
But the battery heating issue is not solved. Reached 49 while charging. Do you have such problem?
Don't know how to solve...

 

[Sudhakar_k]

Hey do I have to install the magisk, after flashing the kernel or before flashing the kernel?

Also does this kernel works smooth with DOT OS?

How is the charging speed?

How is the pubg performance? Any lag?

How is the standby drain?

Sent from my Redmi 3S using Tapatalk

Anyone please?

Sent from my Redmi 3S using Tapatalk

 

[Unlucky01]

Yeah, flashed it and works without problem. Google drive also working.
But the battery heating issue is not solved. Reached 49 while charging. Do you have such problem?
Don't know how to solve...

Solution in my case is putting phone on marble windowsill. But I will agree that phone is overheating between 20 and 60 % of battery.

 

[drjmvgami]

Solution in my case is putting phone on marble windowsill. But I will agree that phone is overheating between 20 and 60 % of battery.

Yes ,btwn 20 to 60 or 70, at the time when charging at highest strength, around 1700 mAh.
This must be phone side issue, having in every kernel.

 

[GuestK00277]

Hey do I have to install the magisk, after flashing the kernel or before flashing the kernel?

Also does this kernel works smooth with DOT OS?

How is the charging speed?

How is the pubg performance? Any lag?

How is the standby drain?

FLASH your rom, set it up !
Then after a. reboot ,
Flash Kernel !
Flash Magisk !

For some roms where force encryption is enabled, flashing Magisk / Kernel directly after flashing rom.zip, puts you in boot loop !

So better flash the Kernel.zip / Magisk.zip after 1st reboot ! and clean Cache/Dalvik Cache and then boot to system

Charing Speed is good , but has heating issues on some Roms

Very Low standby drain, if you use default settings and don't tweak using Kernel Aduitor, i get ~ 7 hrs sot , Night Drain <=1%

 

[Sudhakar_k]

FLASH your rom, set it up !
Then after a. reboot ,
Flash Kernel !
Flash Magisk !

For some roms where force encryption is enabled, flashing Magisk / Kernel directly after flashing rom.zip, puts you in boot loop !

So better flash the Kernel.zip / Magisk.zip after 1st reboot ! and clean Cache/Dalvik Cache and then boot to system

Charing Speed is good , but has heating issues on some Roms

Very Low standby drain, if you use default settings and don't tweak using Kernel Aduitor, i get ~ 7 hrs sot , Night Drain <=1%

Thanks a lot for helping me, highly appreciate it
Also I'm running the DOT OS Android Pie, I kinda facing a lot of heating issue even at this time whole posting this message although I'm not really using anything else.

Do you suggest using kernel auditor and tweak settings a bit or Just flash completely Other New ROM, To avoid heating issue at the same time reasonable battery backup?

Thanks in Advance![emoji3]

Sent from my Redmi 3S using Tapatalk

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

Also which ROM are you currently running? And which one you suggest?

Sent from my Redmi 3S using Tapatalk

 

[GuestK00277]

Thanks a lot for helping me, highly appreciate it
Also I'm running the DOT OS Android Pie, I kinda facing a lot of heating issue even at this time whole posting this message although I'm not really using anything else.

Do you suggest using kernel auditor and tweak settings a bit or Just flash completely Other New ROM, To avoid heating issue at the same time reasonable battery backup?

Thanks in Advance![emoji3]

Sent from my Redmi 3S using Tapatalk

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

Also which ROM are you currently running? And which one you suggest?

wait for 2-3 charging cycles ie from 100 - 1 % and then decide Battery life and heating issues ! Try using Naptime app , without root good one ..

Try asking the dev of rom and other users about the heating issue , it is not good approach to directly change Kernel, do run some tests on default kernel !
Chimera is one of the Best kernels available though .

I am on Havoc 2.4, Super smooth, stable for daily usage !

 

[Ash225]

How can i increase the volume during calls its really low. Currently i m on Siberia Os with the latest version of this kernel.

 

[drjmvgami]

Thanks a lot for helping me, highly appreciate it
Also I'm running the DOT OS Android Pie, I kinda facing a lot of heating issue even at this time whole posting this message although I'm not really using anything else.

Do you suggest using kernel auditor and tweak settings a bit or Just flash completely Other New ROM, To avoid heating issue at the same time reasonable battery backup?

Thanks in Advance![emoji3]

Sent from my Redmi 3S using Tapatalk

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

Also which ROM are you currently running? And which one you suggest?

Heating issue is there with Chimera in Redmi 3s. Mine heats upto 49 c. while charging. On stock ROM it goes around 45. But Chimera charges phone faster at high speed. It charges at around 1700 1800 mAh while on stock kernel I get around 1500 mAh.
Seems like this kernel unlocks charging cap so it heats more than stock kernel

---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------

Heating issue is there with Chimera in Redmi 3s. Mine heats upto 49 c. while charging. On stock ROM it goes around 45. But Chimera charges phone faster at high speed. It charges at around 1700 1800 mAh while on stock kernel I get around 1500 mAh.
Seems like this kernel unlocks charging cap so it heats more than stock kernel

I am on Havoc 2.4 pie

 

[dhananjay2015]

Heating issue is there with Chimera in Redmi 3s. Mine heats upto 49 c. while charging. On stock ROM it goes around 45. But Chimera charges phone faster at high speed. It charges at around 1700 1800 mAh while on stock kernel I get around 1500 mAh.
Seems like this kernel unlocks charging cap so it heats more than stock kernel

---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------


I am on Havoc 2.4 pie

Edit threshold temp in thermal-engine.conf file found in etc folder inside vendor. Like mine never goes beyond 36 at max 37

 

[drjmvgami]

Edit threshold temp in thermal-engine.conf file found in etc folder inside vendor. Like mine never goes beyond 36 at max 37

Which of the lines to edit? Can you post edited file?
Btw you are also on redmi 3s land?

 

[dhananjay2015]

Which of the lines to edit? Can you post edited file?
Btw you are also on redmi 3s land?

Yeah

 

[drjmvgami]

Yeah

Thanks will give it a try

 

[taicracker]

RESERVED
CHANGELOG

v6r3

upstreamed to v3.18.138
compiled with updated toolchain
Update AnyKernel2

OLD LOGS

v6r2

fix mdss kernel panics caused by klapse_push

v6

Added KLapse support
Upstreamed to 3.18.136

v5.2_r3

Fix major EAS bug where cost data wasn't dynamically calculated in the previous build
Build with Graphite flags
Increase minimum brightness
Remove Nethunter/HID support

v5.2_r2 rebased

Upstreamed to 3.18.132
Merged LA.UM.7.6.r1-04000-89xx.0
Remove -dirty append in Kernel version
Fixed DT2W v2 implementation
Disable DT2W v2 by default(Can be enabled via KA)
Add Haptic Feedback to S2W
Remove useless features

v5.2_r2

Merged 3.18.131
Fix Schedutil not being applied upon boot

v5.2

Upstreamed to 3.18.126
Merged LA.UM.7.6.r1-03400-89xx.0
Revamp EAS Model
Compile with BootlinTC+Graphite

v5.1r3

Rebased to <insert latest CAF tag here>
Upstreamed to 3.18.124
Tweaked spectrum and init config
Removed Alucard and Darkness governors
Fixed Max GPU clock in spectrum not being applied (tenks @parvezch boi)

v5.1r2

Fixed Vendor Mismatch on all ROMs

v5.1

Upstreamed to 3.18.122
Rebased to LA.UM.7.6.2.r1-03200-89xx.0
Removed Interactive Governor
Fixed Vendor Mismatch Issue
Compiled with DragonTC 8.0
Cross Compiled with Linaro 7.3.1
Tweaked Spectrum configs
schedutil is the default governor now

v5.0r2

Upstreamed to 3.18.120
Merged [Insert Latest CAF Tag here]
Rebase Non treble to TeamReloaded

v5.0

Added EAS support
removed wakelock triggers
Enabled Adreno Idler(I forgot to enable it in the defconfig F)
Added CPU Boost
Removed Lisi
Removed Electron
Upstreamed to 3.18.116
Switched DT2W to half screen by default
Added Performance profile in spectrum
Adjusted frequencies in spectrum profiles
Switched to schedutil governors in spectrum profiles

V4.1

Added Android P sGSI support
Upstreamed to V3.18.14
Spectrum Profile Fixed
Added FIOPS IOSCHED
Enabled NOOP IOSCHED
Enabled BFQ IOSCHED(In non-treble)
Added Lisi Governor
Added Electron Governor
Fixed Kernel Version

V4

INTEGRATE TREBLE AND NON TREBLE BUILDS INTO ONE ZIP
Upstreamed to v3.18.113
Rebased Treble source
Spectrum Profiles Added
Compiled with DTC 7.0 Clang TC
Re-Added KCAL

V3.0(Includes Treble)

Switched base kernel source
Add Haptic feedback for DT2W V2
Add S2W back
Disabled S2S in S2W
Downstreamed to 3.18.71(only in non treble build)
Remove exfat as no longer needed
Add UC and OC frequency table

V2.1

Upstreamed to 3.18.104
Add Voltage Control For Little Cores
Add Faux Sound Control
Add SDFAT Support
Fix Kernel Version in Settings
Disabled S2W(Since working to implement t2s)

V2.0-r2

Fix Stability Issues in some ROMs
Remove Overclock for battery performance and stability
Switched Base Source

V2.0

Switched to Rebased kernel
Wireguard VPN Support added
QC2.0 (Should work, Extensive Testing still needed)
Switched to DyWN's & bawaviki's OC
CD-ROM Emulation added
Sweep2Sleep added
KCAL Removed(Due to some problems, Will re-add soon)

v1.2r2

Upstreamed to 3.18.102

V1.2

Added Wakelock triggers
Added Voltage Control
Dt2w v1.0 --> v2.0 thanks to tanish2k09

V1.1

Fixed Kernel Aduitor problems
Added dt2w
Fixed governers not showing up

V1.0

Initial build

Hello. Help me The kernel port you made for Xiaomi Redmi 3s for my device is also the Snap 430 chipset.
Please help me make a kernel like this ([3.18.138] [EAS] [O / Pie] [GESTURES] Chimera Kernel [V6r3]) for my device (Nokia 6) my device with the same chip set Remi 3s, I unlocked the bootloader. and currently running Android 8.1. I can provide you with the boot file or what you need on my phone. Thanks very much. Please.....:highfive::highfive::highfive:

 

[cristihan]

Thanks @rupanshji for your extraordinary work. I flashed Chimera Kernel on SyberiaOS in my Redmi S3 (screenshot attached). It works perfectly so far. I am very pleased with all the tweaks and exceptional battery usage. Because I am living in a country where listening to phones is a "national sport" of our authorities (attached analysis), I use SnoopSnitch app to know when all this happens. In order for this application to work, outside the root, the kernel needs to have the DIAG_CHAR device driver enabled. As the SnoopSnitch developers say: "The kernel needs to have the DIAG_CHAR device driver enabled and the /dev/diag character device must be present. The driver can be found under drivers/char/diag/ in the MSM kernel source." So far from all of the ROMs I've just tried only "xiaomi.eu_multi_HM3SHM3X_V10.1.1.0.MALCNFI_v10-6.0" latest stable for Redmi S3 developed by Xiaomi.eu team have this driver enabled. On this ROM when running command in Terminal "ls -l /dev/diag" I get "crw-rw ---- system qcom_diag 244, ...." what's OK for SnoopSnitch app to work. With Chimera Kernel when run in Terminal "ls -l /dev/diag" I get "crw-rw ---- system vendor_qti_diag 244, ..." and SnoopSnitch is not working.
I checked in your GitHub and on "android_kernel_xiaomi_msm8937/drivers/char/diag/diagchar.h" appears "diag: Handle data ready notification properly".
In official Xiaomi GitHub for the Redmi S3 kernel at "Xiaomi_Kernel_OpenSource/drivers/char/diag/diagchar.h" appears "diag: HDLC changes for splitting the data stream" ... I think there in "diagchar.h" is the difference. Is there any possibility that this driver, DIAG_CHAR device driver to be enabled in future Kernel build? ... or a patch that enable this driver via TWRP?

 

[rupanshji]

Thanks @rupanshji for your extraordinary work. I flashed Chimera Kernel on SyberiaOS in my Redmi S3 (screenshot attached). It works perfectly so far. I am very pleased with all the tweaks and exceptional battery usage. Because I am living in a country where listening to phones is a "national sport" of our authorities (attached analysis), I use SnoopSnitch app to know when all this happens. In order for this application to work, outside the root, the kernel needs to have the DIAG_CHAR device driver enabled. As the SnoopSnitch developers say: "The kernel needs to have the DIAG_CHAR device driver enabled and the /dev/diag character device must be present. The driver can be found under drivers/char/diag/ in the MSM kernel source." So far from all of the ROMs I've just tried only "xiaomi.eu_multi_HM3SHM3X_V10.1.1.0.MALCNFI_v10-6.0" latest stable for Redmi S3 developed by Xiaomi.eu team have this driver enabled. On this ROM when running command in Terminal "ls -l /dev/diag" I get "crw-rw ---- system qcom_diag 244, ...." what's OK for SnoopSnitch app to work. With Chimera Kernel when run in Terminal "ls -l /dev/diag" I get "crw-rw ---- system vendor_qti_diag 244, ..." and SnoopSnitch is not working.
I checked in your GitHub and on "android_kernel_xiaomi_msm8937/drivers/char/diag/diagchar.h" appears "diag: Handle data ready notification properly".
In official Xiaomi GitHub for the Redmi S3 kernel at "Xiaomi_Kernel_OpenSource/drivers/char/diag/diagchar.h" appears "diag: HDLC changes for splitting the data stream" ... I think there in "diagchar.h" is the difference. Is there any possibility that this driver, DIAG_CHAR device driver to be enabled in future Kernel build? ... or a patch that enable this driver via TWRP?

I am not very sure but CONFIG_MSM_MHI may be enabled for it in land_defconfig. Unfortunately your situation is very specific and I can't add it it to the public builds however, You may build the kernel yourself! Hit me up on telegram if you face trouble ( t.me/rupansh )

 

[cristihan]

I am not very sure but CONFIG_MSM_MHI may be enabled for it in land_defconfig. Unfortunately your situation is very specific and I can't add it it to the public builds however, You may build the kernel yourself! Hit me up on telegram if you face trouble ( t.me/rupansh )

Thank you @rupanshji for your prompt answer. I'll contact you on the Telegram.