Database Users

[ROM][Unofficial][5.1.1] CyanogenMod 12.1

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*/
Introduction
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features (Device Specific)
LCD Color/Gamma Settings
LCD Adaptive Backlight
LCD Color Enhancement
LCD QCOM PostProcessing(PP) support
Disable Touch keys and enable NavigationBar
Set Vibrator Intensity
1+1 QuickBoot
Differences to CM11
Removed TrueDualBoot(TDB) support. And pls don't try to bring it back by using TDB enabled versions of CWM or TWRP. It's dead and will be replaced by GRUB4Android in March.
CM12 still supports Dualsystem the way Xiaomi designed it. That means that it can be installed to both System partitions but the userdata partition will be shared.
SDCARD filesystem detection You now can format your internal sdcard to whatever filesystem is supported by VOLD and the CM kernel. The only alternative that would make sense is F2FS though.
Improved Power consumption Use Xiaomi's MPDecision, thermald and libqc-opt together with QCOM's power HAL.
Added QCOM time services
Added Oppo QuickBoot
Use Xiaomi blobs I replaced some Nexus4 blobs with the originals from Xiaomi'S MIUIv5 ROM to prevent some unpredictable bugs
Encryption support another reason why TDB is dead now
Known Bugs
Bluetooth connection and Audio issues
Installation instructions
!ATTENTION!
There are two (annoying) problems with GoogleApps:
1) CM12 is huge and doesn't leave much space for GAPPS on MI2
2) recovery ignores errors in update.zip's which means even though it tells you the installation was successful it failed.
this means you have two options:
1) resize your system partition(recommended) this miflash package resizes your system partition without taking space from your data partition by removing the system2 partitions:
http://forum.xda-developers.com/mi-2/orig-development/flashtools-miflash4linux-recovery-qdl-t3036730
2) install very small gapps packages and check /tmp/recovery.log and the remaining space after the installation to make sure it was successful.
Click to expand...
Click to collapse
First time flashing CyanogenMod 12.1 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
IMPORTANT: if you use xposed - pls disable it and try again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download
DevHost
Changelog
Code:
20150730:
[changed] total rewrite
[changed] new kernel: CAF(LA.AF.1.1_rb1.18) + 3.4.108(upstream) + android-3.4(kernel/common)
[changed] support for merged partitions
[bug] some features like hw tunables are still missing
20140228:
[fixed] fix audio HAL by comparing values with MIUIv5
[changed] fix ACDBLoader
[changed] update WIFI config
[changed] update system.prop from CAF (should improve battery life a little bit)
[changed] rename CM perf profile properties for Xiaomi's thermald
[changed] use CM's default wallpaper
[changed] update kernel from mako
Older changelogs:
Code:
20140218:
[changed] set SELinux to Enforcing mode
[changed] disable flashing FMRadio FW
[fixed] Haptic Feedback for touch keys
[changed] disable ACDBLoader as an attempt to fix random call bugs
[fixed] attempt to fix Atmel touchscreen driver crash
Code:
20140217:
[new] F2FS support
[fixed] Installation on resized system partitions
[changed] switch to CAF HAL's and add FMRadio support
[changed] Update WLAN driver to LA.AF.1.1_rb1.12
Code:
20140216.
[new] Initial Release
Thanks To/Credits
Code:
* CyanogenMod
* Nexus 4 Maintainers
* QCOM for generic Sources
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2015-02-16
Last Updated 2015-07-30

First
Sent from my A0001

Oh wow, finally

You are just awesome thanks for your work

Thank you very much M1cha for you excellent work and dedication! I will try this rom immediately.
Can I ask you a question? Where did you learn to mess with the kernel and the firmwares? Did it took long for you to learn it? I have always wanted to mess with these things myself, but I always get overwhelmed with the required knowledge

_Roysten said:
Thank you very much M1cha for you excellent work and dedication! I will try this rom immediately.
Can I ask you a question? Where did you learn to mess with the kernel and the firmwares? Did it took long for you to learn it? I have always wanted to mess with these things myself, but I always get overwhelmed with the required knowledge
Click to expand...
Click to collapse
Since there's not much documentation for such things u just have to start doing it and learn everything by yourself.
Also, these projects are too big to study them or trying to find a task just for learning.
The best way is to find a project idea and then u have to work on it until u succeed

Thank you M1cha,
2bad no dualboot and xposed (yet).

Dualboot(the Xiaomi way) works, and TDB shouldn't be used anymore.(u have to wait for G4A).
The information about Xposed doesn't mean that Xposed isn't compatible(it should be), it just means that before reporting any crashes you should disable Xposed and check if u still have the same problem.

incall working , also quick-boot

SWADED said:
Thank you M1cha,
2bad no dualboot and xposed (yet).
Click to expand...
Click to collapse
Hi,
You're wrong ! TDB is working (even if it shoudln't be now, GRUB is coming thanks to @m11kkaa) and xposed is now available for Lollipop : http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Btw, thank you for your job michael ! :good:

[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?

softkey vibration doesn't work.
I reserve to test this build as a daily driver and report any issue tomorrow.
m1cha, you won't let me swap my mi2s and I'm so happy with this
thanks a lot for your work!!

thx you for you work!

acastrocab said:
[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?
Click to expand...
Click to collapse
I'm wondering the same
And thanks m11kkaa for your great work!!!
Sent from my MI 2S using XDA mobile app

m11kkaa said:
Dualboot(the Xiaomi way) works, and TDB shouldn't be used anymore.(u have to wait for G4A).
The information about Xposed doesn't mean that Xposed isn't compatible(it should be), it just means that before reporting any crashes you should disable Xposed and check if u still have the same problem.
Click to expand...
Click to collapse
xposed for lollipop generates a bootloop on your CM12.
working fine on Ivan's AOSP rom.
so, don't try to flash it over m1cha's CM12!!

Reserved
Sent from my MI 2S using Tapatalk

acastrocab said:
[Now that we dont have TDB (with kitkat i only used it a few times) is there any way to eliminate the system 1 and increase the system0 and sdcard partitions?
Click to expand...
Click to collapse
Yeah but u should wait g4a
mehdoux said:
Hi,
You're wrong ! TDB is working (even if it shoudln't be now, GRUB is coming thanks to @m11kkaa) and xposed is now available for Lollipop : http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Btw, thank you for your job michael ! :good:
Click to expand...
Click to collapse
Tdb is not supported anymore because cm policies ask for encryption support, and this feature would break tdb. About xposed we will not provide support or let users report bug if this fw is installed, because it breaks many things
Sent from my A0001

linuxxxx said:
Yeah but u should wait g4a
Tdb is not supported anymore because cm policies ask for encryption support, and this feature would break tdb. About xposed we will not provide support or let users report bug if this fw is installed, because it breaks many things
Sent from my A0001
Click to expand...
Click to collapse
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.

mehdoux said:
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.
Click to expand...
Click to collapse
It "just" replaces the runtime with another one with tons of hacks that will cause huge security issues, then apps will have tons of npe or other fc cuz xposed hacks them for these modules. So when u get a bug andnure running xposed the 80% of times it's xposed, the 20% is a real bug
Sent from my A0001

mehdoux said:
No ! I'm not saying that TDB is supported, I wrote that this ROM is working with TDB (even if it shoudln't be because G4A is coming) because I've tested it and it's true.
Concerning xposed, if it's not asking too much, what does this framework break ? Thank you.
Click to expand...
Click to collapse
Before anybody tries to use TDB, I explain why you shouldn't:
You won't be able to format or backup data from CM12 with a TDB-enabled Recovery.(it would backup a empty data folder). And if you will make a data backup of CM12 with a NON-TDB Recovery this backup will contain System1 and System2 data too which makes them really big.
And ofc, If you wipe Data for CM12, System1 and System2 data are gone too.
The reason is that CM12 ignores the data location set by CWM.

[Kernel+][kipper] Kali NetHunter for the Wileyfox Storm (3.1.0)

WARNING: These builds are currently untested! Proceed with caution, back up your boot partition before installing!
I'm looking for feedback from experienced users right now.
Welcome to the thread on Kali NetHunter for the Wileyfox Storm.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
The installer zip will add a few files (including busybox) to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
These Kali NetHunter builds are designed and tested for CyanogenMod 13.0.
DOWNLOAD
Current version: 3.1.0 (testing, 2016-04-29)
Download here: https://idlekernel.com/nethunter/kipper (testing) and https://idlekernel.com/nethunter/nightly (chroot)
Your device is: kipper (Wileyfox Storm)
Recommended install method: Use Official TWRP 3 for kipper
Install kernel-nethunter-kipper and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
You can actually only install the kernel if you want to take advantage of its features without having to install the rest of NetHunter!
BEFORE INSTALLING
Do not flash the NetHunter update or chroot zip with a fresh data partition!
Most ROMs will wipe it clean on the first boot if you haven't completed the Android Setup Wizard yet, there's no need to wipe your ROM or data to try it out. I do advise backing up your data partition before flashing the zip though.
(this should no longer be possible now with added installation checks)
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist due to other factors unrelated to NetHunter.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
If you would like to use another root method, or prefer systemless SuperSU, then simply remove the supersu folder from the installer zip and it will proceed without it.
FULL INSTALL STEPS
Boot into TWRP.
Flash kernel-nethunter-kipper and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Reboot into your ROM.
Open the NetHunter app
Let the NetHunter app finish setting everything up
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery. On some ROMs you may need to wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just reflash the kernel-nethunter-kipper zip and the ~60 MB update-nethunter-generic-armhf zip in TWRP.
RUNNING WIFI PENETRATION TESTS
The internal WiFi chipset of the Wileyfox Storm is not capable of running services which use monitor mode such as Wifite. For this, you will need to use a monitor mode capable WiFi adapter through a USB-C host adapter.
As for compatible adapters, I highly recommend the Alfa Networks AWUS036NEH (eBay) which uses the Ralink RT3070 chipset. There are currently no monitor mode supported Wireless-AC adapters available.
Once plugged in, you can run the command from Kali terminal to turn on your adapter:
[email protected]:~# ip link set wlan1 up
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better be kipper)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard & VNC - Google Keyboard, AOSP Keyboard, CM Keyboard do not work due to a depth bug, use Hacker's Keyboard as a workaround.
Terminal App - Full screen programs like nano or vi are unusable unless you use the resize command. (type resize when opening a new terminal window)
THE KERNEL
The NetHunter kernel for the Wileyfox Storm is based on CyanogenMod 13.0 nightly kernel sources.
It has the following changes:
F2FS added using Jaeguek Kim's latest kernel.org:f2fs-stable sources (available on system/data/cache!)
UKSM - Ultra Kernel Same-page Merging support
Compiled with -O2 optimizations using GCC Linaro 4.9 2016.02 aarch64 toolchain
Simple IO (SIO) scheduler as default IO scheduler (updated for modern kernels)
USB HID Gadget keyboard support
mac80211 packet injection support
Westwood, HTCP, or Cubic (default) TCP congestion algorithms (updated with bug fixes)
savoca's KCAL display color calibration driver
RTL-SDR, BT RFCOMM, and various WiFi OTG drivers enabled
NFS and CIFS client support with file caching
Running in SELinux Permissive mode
Additional drivers built in for the full Kali NetHunter experience
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the Wileyfox Storm, you can find the sources here: https://github.com/jcadduono/nethunter_kernel_kipper/tree/cm-13.0
See the Kali NetHunter installer source here: https://github.com/offensive-security/kali-nethunter
See the Kali NetHunter app source here: https://github.com/offensive-security/nethunter-app
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
XDA:DevDB Information
Kali NetHunter for the Wileyfox Storm, Kernel for the Wileyfox Storm
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/jcadduono/nethunter_kernel_kipper/tree/cm-13.0
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: 3.1.0
Stable Release Date: 2016-04-29
Created 2016-04-30
Last Updated 2016-04-29

Awesome, can you tell me how you done it because i tried to do it for my Meizu MX4 but... And i have a Wileyfox Storm too ^^
Sent from my MX4 using XDA-Developers mobile app

bobslesbricoleurs said:
Awesome, can you tell me how you done it because i tried to do it for my Meizu MX4 but... And i have a Wileyfox Storm too ^^
Sent from my MX4 using XDA-Developers mobile app
Click to expand...
Click to collapse
You just have to take the kernel sources of whatever ROM you're using and enable some features, apply a few small patches, then recompile the kernel and flash it with NetHunter installer.
See: https://github.com/offensive-security/kali-nethunter/wiki/Porting-Nethunter
I have no idea if this kernel works! No one has tested so far. Once I know it works, I will move it to our official NetHunter branch and it will make it into the next official release.
If you are competent enough to follow instructions, we're glad to help people port their devices in #nethunter on freenode IRC.
I can also review ports to help you find missing configs, broken patches, etc. and merge them into official if you are willing to maintain them!

I've a wileyfox maybe i can test
Sent from my MX4 using XDA-Developers mobile app
---------- Post added at 08:03 AM ---------- Previous post was at 07:47 AM ----------
Not boot
Sent from my MX4 using XDA-Developers mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:03 AM ----------
It's for android 5.1 or 6.0?
Sent from my MX4 using XDA-Developers mobile app

bobslesbricoleurs said:
I've a wileyfox maybe i can test
Sent from my MX4 using XDA-Developers mobile app
---------- Post added at 08:03 AM ---------- Previous post was at 07:47 AM ----------
Not boot
Sent from my MX4 using XDA-Developers mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:03 AM ----------
It's for android 5.1 or 6.0?
Sent from my MX4 using XDA-Developers mobile app
Click to expand...
Click to collapse
read first post...

Oops!
Hey,
I just gave this a go, and ended up sailing pretty close to bricking my Wileyfox Storm! I managed to re-flash cyanogenmod 13 and get it booting again though! Perhaps a stupid question, but is there a way to restore the stock Wileyfox kernel etc? I quite liked the setup they had, and I didn't think to back it up :-s
Also, I do think this would be really cool if it works! So keep up the good work!
---------- Post added at 03:31 PM ---------- Previous post was at 03:15 PM ----------
To answer my own question: http://forum.xda-developers.com/wil...to-flash-stock-images-brick-recovery-t3319617
Download the stock zip from the link given, and follow the instructions!

What about the wileyfox swift?

Who else has tried the ROM

Please links are dead it say error timeout. Please someone

arter97 kernel for OnePlus 3 running CyanogenMod 13

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
arter97 kernel for OnePlus 3 running CyanogenMod​
/* Details */
Latest Linaro LSK kernel fully merged
Adaptive LMK disabled
Built with latest Linaro GCC toolchain with latest Linux H.G linker
Built with O2 speed optimizations
Power-efficient workqueues enabled
Random driver backported from mainline Linux(12 times faster)
Westwood as default TCP network congestion control
Entropy hook on storage removed
Default file-system mount option with noatime
CFQ I/O scheduler as default(it's the fastest I/O scheduler available on 3.18 kernel)
NVIDIA's power-efficiency improvement commits applied
sdcardfs from Galaxy S7 ported(stable)
Supports f2fs-formatted system partition
/* Disclaimer */
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 kernel
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. Hard. A lot.
/* Warning */
Redistribution, modifying files used within this project's file or integrating with other projects are prohibited with no exceptions other than my projects.
Making mirrors, re-uploading to another servers are also prohibited with no exceptions.
/* Thanks to */
xboxfanj
TheCrazyLex
Thecrazyskull
/* Contact */
Twitter : @arter97
/* Notice */
This kernel will be updated accordingly to my new CyanogenMod 13 build, if it requires newly updated kernel
Support for other ROMs are not guaranteed and is not planned at the moment
To remove the kernel, wipe system partition and re-install the ROM
Disabling encryption(FDE) is highly recommended for better performance
/* Downloads and links */
arter97.com
XDA:DevDB Information
arter97 kernel for OnePlus 3, Kernel for the OnePlus 3
Contributors
arter97
Source Code: https://bitbucket.org/arter97/android_kernel_oneplus_msm8996
Kernel Special Features:
Version Information
Status: Nightly
Created 2016-08-14
Last Updated 2016-12-20

/* To kang or not to kang */
I prefer "open" to all stuffs, explicitly except for my personal kernels.
I've once used to use private Git repository for my kernels and just release the source-codes as a tarball,
which means that other developers who are interested in my kernel's changes would not get the specific changes they want while not violating XDA forum rules or GPL.
That was almost 3 years ago which by then, I was a newbie developer on XDA.
I was afraid other big developers merging all of my changes and I'll get buried down.
However, I've changed my mind and opened up my Git access to everyone after thinking my previous actions did not belongs to XDA's spirit.
That was a big move for myself of re-thinking what should be open.
Later down on the road as I gained more development skills, I've contributed into CyanogenMod and other's custom kernel and ROMs for fixing stuffs, introducing new concepts or improving performance.
During such process, there were quite a lot of occurrences where I was actually the first one to do those things.
For those who're familiar with "temasek ROM", you may know that after I became a contributor, temasek rose even more into the center of other AOSP ROMs' attention, as I was the first to introduce new exciting stuffs such as compiler changes or f2fs. And I quickly gained dozens of followers on my GitHub account.
And eventually, people *kang*ed my changes. Sometimes invalidating my authorship.
It surely is not a right thing to do, but I let it slide as it didn't matter that much. I believed that if my changes are good enough, it'd be better to end up with a larger user base rather than being a **** trying to hunt down every ROM developers who're doing it wrong.
Same story goes to my ROMs.
My real first popular ROM was back-to-n00t, which is a ported ROM from Galaxy S3 LTE to provide stable Touchwiz KitKat experience to the Galaxy S3 3G users.
I opened up everything to GitHub. And I even encouraged that other ROM developers to use my ROM as a base to work on their own ROM as I knew there are a lot of Touchwiz ROM cookers who're way better than me on modifying SystemUI or frameworks(via smali) BUT aren't too good on porting ROMs. I hoped that my ports can be a great base for others to work on their own modifications.
Now those spirits repeated on the Galaxy S6, I opened up everything about back-to-n0t3.
However, I do not do or believe those same things with the kernels.
There are far less kernel developers on XDA compared to ROM developers. ROMs are much more appealing for an "Android newbie" to go tweak. You can modify UI, enable some hidden settings and even port features from another devices.
So when ROMs gets copied off, users can easily distinguish if that was stolen or not.
Let’s say a well-known developer A ported S6 designs and features to the S4. Next day, less-known developer B uploads a ROM on XDA that claims to do the same thing. First thing that comes to the users’ mind would be ‘Is that guy a thief?’.
However, same thing cannot be said on the kernels as they work on a much lower level. You can’t distinguish individual custom kernels just by staring at your phone.
If a ROM developer choose to go use other’s custom kernel and integrate it into their ROM, it’s most likely that users won’t appreciate that custom kernel developer whose work powers that ROM. Let’s face it, not all users care about “Thanks to”, “Credits” sections, and let me tell you, those are the majority. Now some custom kernel developers might be OK with that. However, I’m not. Unlike most developers on XDA, I got fascinated to Android because it runs on Linux kernel. Modifying Linux kernel was the first thing I’ve done on my Android device, not modifying ROM. And I spent years and years on gaining information on Linux/Android kernels and tweaking, coding myself. While I don’t necessarily care users choosing to NOT use my kernel, I cannot stand that my kernel would be installed on one’s device which its owner don’t even know which kernel, which developer who made that kernel is. That is why I’m against with the idea of integrating custom kernels into custom ROMs. If you want your users to have a custom kernel, let them learn themselves what that kernel really is, what does it offers, and who developed it. “For the ease of flashing/installation” is not an excuse for me. Take yourself a few more minutes to download a kernel from the web, and a few more seconds to flash a secondary ZIP file from the recovery. Is that hard? Time-consuming? Absolutely not.
I hope everyone gets the idea why I'm sticking with the idea of "don't integrate my kernel into others".
Cheers.

/* Changelog */
2.0
Power saving patches from Pixel and AOSPA kernel
LA.HB.1.3.2-33900-8x96.0 CAF tag merged
Display on/off latency reduced (by TheCrazyLex)
Kernel now built with Cortex-A57 optimization (by TheCrazyLex)
Performance regression from power-efficient workqueue fixed (by TheCrazyLex)
Workqueue adjustments from francisfranco kernel
Wi-Fi drivers updated to LA.UM.5.5.r1-02200-8x96.0
f2fs merged from Linux 4.10 with the deadlock fix
1.9.1
Minor improvement for touch latency
Disable haptics for voice calls and video recordings (by sultan)
Wi-Fi power management tweaked
- Previous relaxation reverted as the stability issue seemed to be somewhere else
1.9
UI lags introduced with version 1.6 fixed
Wi-Fi power management relaxed to improve stability
Added Wi-Fi firmware from Pixel XL to improve stability
1.8
Touchscreen drivers updated from OnePlus 3T sources (lower latency)
Tri state key inconsistency fixed (by sultan)
1.7
Wi-Fi drivers updated
Wi-Fi BET tuned(TheCrazyLex)
Latest CyanogenMod 13 sources merged
1.6
Wi-Fi drivers updated
Wi-Fi configuration revamped to improve performance and stability
CPUSETS disabled to improve latency
1.5
ARM64 erratum fixes disabled to improve performance
Updated to Linux 3.18.43
Dozens of Google Pixel kernel commits merged to improve performance, smoothness and latency
CFQ upstreamed to Linux 4.9
BFQ disabled
Dirty COW vulnerability fixed
1.4
ADB issue on app installation fixed
Wi-Fi drivers reworked from CAF Android N sources
1.3
ro.adb.secure, ro.secure now set to 1
ADB rebuilt from Android N sources
Trigger TRIM on boot
1.2
Automatic TRIM(discard) now enabled
Many sultan's improvements merged
Switched to FSF GCC 6.2
1.1
GPU will now enter 133 MHz

Reserved 3
Reserved 3

Reserved 4
Reserved 4

Great work!
Thanks @arter97
__
v7
XDA Assist

back from vacation and directly bring up

Excellent work!!
thanks for coming up here

Great to see you here arter

Yay you are back

hoorah!

Kernel run great. Very smooth.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Can I flash this kernel over EX Kernel?
Sent from my ONEPLUS A3003 using Tapatalk

@arter97 is encryption supported out of the box?
Sent from my OnePlus 3 using XDA Labs

xNAPx said:
Can I flash this kernel over EX Kernel?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Dirty flash rom after coming from EX Kernel

Great work @arter97

Hey arter nice to see you here, remember you from old s3 days i'm looking forward to a great time with my op3 [emoji106]
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

great

stryker09 said:
@arter97 is encryption supported out of the box?
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Yes!
__
v7
XDA Assist

which kernel tuning app is recommended for this kernel?

[EOL][ROM][SANTONI][NOUGAT]Resurrection Remix [5.8.5][UNOFFICIAL][microG][OTA]

My Unoffical Resurrection Remix Nougat
(LuisROM) for Xiaomi Redmi 4X (Santoni)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is a unofficial Resurrection Remix Nougat V5.8.5 based on LineageOS.
This is a ROM that works on Xiaomi Redmi 4X (santoni) only! This ROM comes with a highly-customized kernel, as well as some other very custom modifications.
I will NOT provide support if you install a custom kernel!
Changelogs: http://luis-builds.de/downloads/lineageos/rr/Xiaomi_Redmi_4X_(santoni)/RR-N-Changelog.mkdn
Introduction
Hello Friends!
It's time to say goodbye to nougat. I am going to discontinue the development of the RR Nougat LuisROM for the oneplus3, oneplus5t, santoni and mido at the end of this month. Unfortunately, I do not have enough time to maintain two Custom ROMs for each device in my spare time. I will intensify my work on the oreo versions of LuisROMs that are already available. The time for the switch is now.
For the Samsung Galaxy Tabs and Notes (na1wifi, chagalllte, chagallwifi, klimtlte, klimtwifi) I will continue to offer the RR Nougat LuisROM at least for some more months.
I had troubles to find current builds for my devices so I decided to make regular builds for my devices. When my friends told me about similar problems, I extended the builds to include their devices as well. So these builds were and are mainly for my friends and me, but I finally decided to provide them also for public download.
Unofficial Resurrection Remix the ROM (LuisROMs) an awesome combination of performance, customization, power and the most new features, brought directly to your Device.
My Buildserver
My buildserver automatically creates a new nightly build every second day from the current sources (RR, LineageOS, AOSP) and my personal repositories, even if nothing has changed in the changelog. The RR Updater informs you about new OTA updates. You can also download my nightlys via the RR OTA Updater.
Notice
Sometimes I get a lot of help or feature requests from users of my LuisROMs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs . Please understand if I can not always answer directly.
ROM-Review from Koogly on YouTube:
ROM features:
Based off latest Resurrection Remix Oreo / LOS 15.1 sources
Latest security patches and sources
RR OTA Updater
Compatible with EX Kernel Manager
Fast fingerprint unlock
Signature Spoofing (microG Support)
Build in MIUI Camera
Build in Oneplus Gallery (OP3)
Many other misc. performance and stability improvements under the hood
Kernel: Linux 3.18.x Kernel from rainforce279 (clarity kernel) source with many mods other devs and me (thanks for your incredible work!)
Removed lots of excessive bloat (improves security and performance)
Improved stability (several bugs not listed here have been fixed)
Optimized for performance and battery life
Using Official XIAOMI Patch.
Based on CAF "LA.UM.6.6.r1-08300-89xx.0" for OREO
Camera rebase CAF TAG "LA.UM.5.6.r1-06300-89xx.0" for MIUI/Nougat
Video encode/decode rebased CAF TAG "LA.UM.5.6.r1-06900-89xx.0" for MIUI/Nougat
support Doubletap2Wake / Sweep2Wake Gesture.
KCAL colour control & Backlight Dimmer
added latest alucard, nightmare, darkness, cultivation, ironactive, clarity cpu Governors.
added Zen, SIO i/o scheduler (CFQ as Default).
set default compression zram to Lz4.
Support and updated F2FS Filesystem (only on AOSP Nougat/Oreo)
Overclocked CPU frequencies (BIG CPU upto 1.57GHz, LITTLE CPU upto 1.2GHz).
added custom hotplug AutoSMP and AIO (default core control by CAF)
added ExFat and NTFS Filesystem support
added TTL target Support
Boeffla Wakelock blocker driver V1.1.0
Compatible with systemless root
No placebo patches, features, or dangerous compiler "optimizations"
Many other misc. improvements not listed here
Sound control driver from @flar2 (elementalx) (You can use the Kernel Auditor app or the EX Kernel Manager app to control the speaker, headphone and mic gain. )
WireGuard support, a next generation secure VPN tunnel (more info)
Installation instructions:
Pre-installation:
TWRP of course (https://dl.twrp.me/santoni/)
Required firmware latest oreo firmware. Flash in TWRP before flashing ROM base (Download here!)
Magisk can also be used just make sure you flash it after a first successful boot (after passed setup screen)
First time installation:
Backup your data to PC, OTG flash drive
Flash recovery (TWRP) downloaded from above link and boot to recovery
Wipe system, data, cache and format data, then reboot to TWRP
Copy ROM base and Gapps, then flash them in TWRP
Reboot and enjoy
Update installation:
Download latest build with LuisROM RR Updater App (Settings > Configurations menu)
Boot to TWRP and make a backup
Flash updated ROM base
Reboot and enjoy
Download
R4X Santoni builds "RR-N-v5.8.5-2018XXXX-santoni-Luis.zip": http://luis-builds.de/downloads/lineageos/rr/Xiaomi_Redmi_4X_(santoni)/
R4X Santoni firmware: http://luis-builds.de/downloads/lineageos/rr/Xiaomi_Redmi_4X_(santoni)/Firmware/
R4X kernel updates/fixes: http://luis-builds.de/downloads/lineageos/rr/Xiaomi_Redmi_4X_(santoni)/LuisKERNEL/
My other devices: http://luis-builds.de/downloads/lineageos/rr/
Download OpenGapps: http://opengapps.org
Flash latest TWRP: https://dl.twrp.me/santoni/
Changelog
Official RR-Team: https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/nougat/CHANGELOG.mkdn
LineageOS: https://www.lineageoslog.com/14.1
Developer: http://luis-builds.de/downloads/lineageos/rr/Xiaomi_Redmi_4X_(santoni)/RR-N-Changelog.mkdn
Build: Latest RR-N-v5.8.5-2018XXXX-santoni-Luis-Changelog.txt
Telegram group:
https://t.me/rr_luisrom
Thanks To/Credits
Special thanks to Teams:
LineageOS team: https://www.lineageos.org
Resurrection Remix OS Team: http://www.resurrectionremix.com/
OMNI team https://omnirom.org/about/
SLIMROMS https://slimroms.org/#/about
topjohnwu (Magisk) https://forum.xda-developers.com/apps/magisk
Thanks to the best devs on earth:
francokernel (https://forum.xda-developers.com/member.php?u=3292224)
sultanxda (https://forum.xda-developers.com/member.php?u=4800121)
flar2 (https://forum.xda-developers.com/member.php?u=4684315)
nvertigo67 (URL="https://forum.xda-developers.com/member.php?u=4405529"]https://forum.xda-developers.com/member.php?u=4405529[/URL])
nathanchance (https://forum.xda-developers.com/member.php?u=6842057)
eng.stk (https://forum.xda-developers.com/member.php?u=3873953)
andip71 aka Lord Boeffla (https://forum.xda-developers.com/member.php?u=947981)
MSF Jarvis (https://forum.xda-developers.com/member.php?u=6552280)
zx2c4 for the wireguard vpn ROM Integration (https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635)
mcdachpappe (https://forum.xda-developers.com/member.php?u=7030109)
rainforce279 (https://forum.xda-developers.com/member.php?u=5250109)
Nik001 (https://forum.xda-developers.com/member.php?u=6569827)
mostafaz (https://forum.xda-developers.com/member.php?u=5175597)
and of course to all the supporters.
Thanks for the Sources/Blobs/Tweaks
Resurrection Remix OS (https://github.com/ResurrectionRemix)
LineageOS (https://github.com/LineageOS)
TheMuppets (https://github.com/TheMuppets)
TheScarastic (https://github.com/TheScarastic)
TeamButter (https://github.com/TeamButter)
My Sources/Blobs/Tweaks
FraEgg (me) (https://github.com/FraEgg)

Any review for this?

Wait for review and comparison between the official's

redzha21 said:
Wait for review and comparison between the official's
Click to expand...
Click to collapse
No Problem I have many users for my oneplus3 luis-builds (80.000 downloads/month) an now i am port some features from my oneplus 3 luis-builds to xiaomi redmi 4x. it is one of my personal device
Currently I'm trying to bring sultanxda's kernel thermal driver to the xiaomi. this has brought about 20% more battery power for oneplus 3.
See my oneplus3 threat: https://forum.xda-developers.com/on...3-op3t-unofficial-resurrection-remix-t3649591
Cu Frank

8224Freak said:
No Problem I have many users for my oneplus3 luis-builds (80.000 downloads/month) an now i am port some features from my oneplus 3 luis-builds to xiaomi redmi 4x. it is one of my personal device
Currently I'm trying to bring sultanxda's kernel thermal driver to the xiaomi. this has brought about 20% more battery power for oneplus 3.
See my oneplus3 threat: https://forum.xda-developers.com/on...3-op3t-unofficial-resurrection-remix-t3649591
Cu Frank
Click to expand...
Click to collapse
Wow great! Does the quick charge works?

Can I dirty flash it over the last official build?

Flashed ROM a while ago, everything is really stable and working nicely.
I've sent PR allowing performance cores to sleep when idle and enable Camera2 API (didn't notice, that it's already enabled, sorry).

akkowicz said:
Flashed ROM a while ago, everything is really stable and working nicely.
I've sent PR allowing performance cores to sleep when idle and enable Camera2 API (didn't notice, that it's already enabled, sorry).
Click to expand...
Click to collapse
No need to use camera2api enabler magisk module then?

edall said:
No need to use camera2api enabler magisk module then?
Click to expand...
Click to collapse
Nope, enabled by default, this is by far the best rom for santoni

akkowicz said:
Nope, enabled by default, this is by far the best rom for santoni
Click to expand...
Click to collapse
I'm gonna try it now. How's Snap Camera btw in comparison with Google Cam?

edall said:
I'm gonna try it now. How's Snap Camera btw in comparison with Google Cam?
Click to expand...
Click to collapse
I haven't tried it to be honest, OpenGapps(stock) removed the Snap Camera during installation.

akkowicz said:
I haven't tried it to be honest, OpenGapps(stock) removed the Snap Camera during installation.
Click to expand...
Click to collapse
Ok, I will then and report here. Are you on latest baseband v025 from 7.11.2 Global?

edall said:
Ok, I will then and report here. Are you on latest baseband v025 from 7.11.2 Global?
Click to expand...
Click to collapse
Yup, v025

Picture camera
Hi i just install this ROM and just know that there is no any option to save the picture from camera to sd card. Or i miss something?Anybody know how to save to sd card?thanks

How is battery backup ?

Do we get November security patch?
I love this rom. Installed yesterday and it's really snappy, maybe also due to latest firmware. Battery backup seems good to me. 30% left and almost 6h SOT, but didn't charge yet.
Cheers
Gesendet von meinem Redmi 4X mit Tapatalk

edall said:
I'm gonna try it now. How's Snap Camera btw in comparison with Google Cam?
Click to expand...
Click to collapse
I can include gcam into the ROM. What is the version of your gcam?
Cu Frank

tenoce said:
Can I dirty flash it over the last official build?
Click to expand...
Click to collapse
I think no. Make a Backup before make a dirty flash.
Cu Frank

8224Freak said:
I can include gcam into the ROM. What is the version of your gcam?
Cu Frank
Click to expand...
Click to collapse
I use this version with the settings attached in the post. It's the only way I don't have FC using GCam: https://forum.xda-developers.com/showpost.php?p=74150927&postcount=26
If anyone knows a better version I'm glad to try it of course.

tjengo said:
Do we get November security patch?
I love this rom. Installed yesterday and it's really snappy, maybe also due to latest firmware. Battery backup seems good to me. 30% left and almost 6h SOT, but didn't charge yet.
Cheers
Gesendet von meinem Redmi 4X mit Tapatalk
Click to expand...
Click to collapse
Every build has the last security patches from lineageos and RR.
Cu Frank

[KERNEL][CUSTOM] Eureka kernel for all variants of Galaxy A10 for android 10(Q) & 11(R) & 12(S) ROMs

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all,
this is the thread for a custom kernel i made for Samsung Galaxy A10.
The custom kernel has been named Eureka which is a greek work which means "I have found the solution". This multi-purpose kernel is the solution for battery, gaming, performance on our cheap A10. On creating this kernel, I believed that 1 kernel can be all of the above if properly tweaked!
As from Eureka R9.0, four kernel variants are available inside 1 same zip. This has been made possible using AROMA Installer.
Compatibility:
This kernel is compatible with AOSP GSIs/ROMs, OneUI2 and OneUI3. As from R9.0, there is only 2 variants of zip to download. One is called EMS and the other one is called HMP. Continue reading to learn more about them.
FEATURES:
* Disabled Samsung security features
* Enabled all governors + added other governors
* Overclocked CPU as follows:
BIG Cores: from 1560 MHz to 2288 MHz.​LIL Cores: from 1352 MHz to 1794 MHz.​* Underclocked CPU as follows:
BIG Cores: from 936 MHz to 208 MHz.​LIL Cores: from 839 MHz to 208 MHz.​* Added GPU thermal and voltage control
* Added latest boeffla wl blocker V 1.1.0 and disabled some wakelocks
* Network speed improvement
* Enable zram support and set default compressor as zstd.
* Switch to a lower charging voltage more quickly.
* GPU max frequency overclocked from 676 MHz to 1300 MHz
* Implemented Dynamic FSync 2.0
* Implemented a custom hotplug driver to enhance battery management
* Implemented Power Suspend driver
* High torch brightness on custom roms/gsis
* Has Spectrum support
* Automatic detection of magisk - If u are rooted, u don't need to flash magisk after kernel.
* Upstreamed kernel version from 4.4.177 to 4.4.302
* Built with Vortex Clang 14 toolchain with LTO. Reason: Better performance
* Support for EMS (Exynos Mobile Scheduler) added
Please read the changelog on github for full list of changes.
KNOWN ISSUES:
* Maybe ADB cannot be used at the same time as MTP
SOME MINOR TWEAKS FOR BEST GPU PERFORMANCE:
* Set GPU power policy to "always on"
* Set min and max GPU frequency to 1200/1300 MHz
* Disable GPU thermal manager to prevent GPU frequency from dropping
* Games don't require high CPU frequency because they depend more on GPU. You can therefore decrease CPU max frequencies to reduce heating of the device.
We have developed our own kernel manager called EKManager which is a fork of HkTweaks. It is compatible only with Eureka Kernels. You can download it from here:
LINK: Download EKManager app
Contact info:
Developers of Eureka Team:
* Telegram: @Chatur27, @Gabriel260BR and @roynatech
Channel for Eureka future updates:
* Telegram: https://t.me/eureka_kernel
Official discussion group for A10:
* Telegram: https://t.me/a10grp
I'm grateful to KineSight for designing the logo.
* Telegram: @Kinesight
Reference about EMS kernel:
Energy Aware Scheduling (EAS) gives the scheduler the ability to predict the impact of its decisions on the energy consumed by CPUs. EAS relies on an Energy Model (EM) of the CPUs to select an energy efficient CPU for each task. Allowing to save up battery even further. EMS aka Exynos Mobile Scheduler, is a fork of EAS for Exynos. We ported to our 4.4.y kernel. As written above, EMS kernel is good for battery saving. Some words from kernel official docs: - EAS operates only on heterogeneous CPU topologies (such as Arm big.LITTLE) because this is where the potential for saving energy through scheduling is the highest.
EMS kernel + pwrutilx governor is very good at battery saving according to our test.
Reference about HMP kernel:
It's just the stock scheduler that comes with stock kernel. Basically it's the normal kernel.
What kernel variant to flash once inside AROMA installer?
1) AOSP Legacy Q/R/S - If you are using an old Eureka ROM which was released before February 2022, choose this.
2) AOSP Q/R/S (New) - If you are using an Eureka ROM built as from February 2022, choose this.
3) OneUI 2 - For any OneUI 2 roms (stock/ports).
4) OneUI 3 - For any OneUI 3 roms (stock/ports).
Download link for A10 (Read above to know which version to download for your OS):
All releases of Eureka for Q/R/S ROMs/GSIs (including OneUI)
Source code for my kernel:
Kernel source on GitHub
If you love our work, thank us by donating. Your donation can help us rent a cloud sever to build kernels and roms faster
Link to PayPal: https://www.paypal.com/paypalme/chaturbaij

Noice :victory:

Primeaqua02 said:
Noice :victory:
Click to expand...
Click to collapse
Please vote for the poll at the top of the thread.
Will be great to have your feedbacks.
Thank you.

Does this work with Ultimate Q Rom?

keihjesus said:
Does this work with Ultimate Q Rom?
Click to expand...
Click to collapse
It works. Went on to try it out.

Good afternoon, everyone, I want to leave a review for EUREKA KERNEL 4.4.3, the update hasn't really changed anything, but the work of the RAM memory is different, applications often crash out of the RAM memory, , with update 4.4.3 I can use only 1 application, the rest crashes within a minute, I solved the problem by rolling back to version 4.4, Please fix the RAM, thanks a lot.

Zloemoloko1998 said:
Good afternoon, everyone, I want to leave a review for EUREKA KERNEL 4.4.3, the update hasn't really changed anything, but the work of the RAM memory is different, applications often crash out of the RAM memory, , with update 4.4.3 I can use only 1 application, the rest crashes within a minute, I solved the problem by rolling back to version 4.4, Please fix the RAM, thanks a lot.
Click to expand...
Click to collapse
Well, I didn't do anything with ram.
Kindly let me know which os you are using

Zloemoloko1998 said:
Good afternoon, everyone, I want to leave a review for EUREKA KERNEL 4.4.3, the update hasn't really changed anything, but the work of the RAM memory is different, applications often crash out of the RAM memory, , with update 4.4.3 I can use only 1 application, the rest crashes within a minute, I solved the problem by rolling back to version 4.4, Please fix the RAM, thanks a lot.
Click to expand...
Click to collapse
use ex kernel manager and enable zswap

Chatur27 said:
Well, I didn't do anything with ram.
Kindly let me know which os you are using
Click to expand...
Click to collapse
i use stock Android 10 Q one ui 2.0

Zloemoloko1998 said:
i use stock Android 10 Q one ui 2.0
Click to expand...
Click to collapse
I use ultimateQ ( which a debloated version of oneui 2.0) and I don't get any such issues.
I don't even need to enable zswap (except for high end games)

Is there any way to increase multi touch count/slots to 10 !
Update: I got stuck at samsung logo
Update 2 : magisk cause bootloop and to avoid that you should remove magisk from inside "Eureka_kernel/ramdisk" folder then flash it via recovery, it should work just fine..
Eureka kernel brings HUGE improvement in performance and gaming.
thank you @Chatur27 for the awesome support and for this awesome kernel.
Device : A105f 2GB ram version

D R A G O said:
Is there any way to increase multi touch count/slots to 10 !
Update: I got stuck at samsung logo
Device : A105f 2GB ram version
Click to expand...
Click to collapse
Force restart device. It will boot up normally.

dead link

blackisme said:
dead link
Click to expand...
Click to collapse
Hi, sorry about this.
Use this temporary link for the time being:
Galaxy A10 Kernel - Google Drive
drive.google.com
Thank you

Links doesn't work... Help :c

What's the difference between enforcing and permissive kernel?

Chatur27 said:
I use ultimateQ ( which a debloated version of oneui 2.0) and I don't get any such issues.
I don't even need to enable zswap (except for high end games)
Click to expand...
Click to collapse
Does it support volte? I have tried to install the selinux enforcing version but it won't boot up the permissive one is working fine but is there a way to change it to enforcing manually? And also(this is the last) did you flash the one ui version for ultimateq since it's a debloated stock?
Your kernal is doing awesome ....great job..keep up the good work.

AlexDreemurr said:
Links doesn't work... Help :c
Click to expand...
Click to collapse
Hi, sorry about this.
Use this temporary link for the time being:
Galaxy A10 Kernel - Google Drive
drive.google.com

Eshan786 said:
Does it support volte? I have tried to install the selinux enforcing version but it won't boot up the permissive one is working fine but is there a way to change it to enforcing manually? And also(this is the last) did you flash the one ui version for ultimateq since it's a debloated stock?
Your kernal is doing awesome ....great job..keep up the good work.
Click to expand...
Click to collapse
Volte is oneui rom feature. dont ask me about volte. Ty.
Enforcing version won't boot because your custom rom needs permissive. Change rom if you want enforcing SElinux

I flashed the 5.0 version (Permissive and Enforcing) but it won't boot... RR Q, only works the 4.4.1... Why? :S