Related
I have been sharing my CM7/CM9/CM10/CM10.1/CM10.2/CM11-based builds for several devices. MackayROM was first based on CyanogenMod sources, but I decided to move over to Omni as base for my ROM.
About Omni: Omni is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Disclaimer: 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.
If you run into errors, I may not be able to solve it!
If you know a solution to a problem, either upload it yourself to Gerrit Code Review or contact me through pm.
The ROM is based on Omni sources with the following changes:
-Mackay Kernel:
-Set of cherries picked from gerrit (differing by the day)
-Some additional patches I did myself to the source code
Feature request are OK, but remember:
1. I try to stay close to stock
2. I will not include additional apps, unless they can be build from source
3. The time I spend on features depends on how much I like them myself
Although it is possible to enable ART, this is not advisable:
-Takes long to convert from Dalvik to ART on first boot
-Needs more RAM
-Can cause soft reboots
But off course, YMMV -> light users may have better luck
Changelog of 27-Feb-2014
-Omni codebase of 26-Feb (e.g. new bootanimation )
-QS Ribbon is gone
-Custom kernels can be used only if specific for OmniROM => currently none
Full changelog of compared to stock Omni
Omni sources of 31-Jan-2013
All features compared to stock kernel:
Separate kernel thread: http://forum.xda-developers.com/showthread.php?t=2532813
-Mackay kernel:
-Christopher86's cortex-A8 optimized Linaro toolchain (January version)
-O3 optimization
-updated to linux kernel version 3.0.101
-SLQB memory allocator (default, should be slightly faster)
-XZ compression of kernel & initramfs
-396MB RAM
-SIOplus scheduler
-Added Lagfree governor
-ROW scheduler (tweaked, default scheduler)
-FIOPS scheduler (tweaked)
-XZ compression of kernel & initramfs
-many improvements to IO schedulers in general
-Deadline tuning (thanks to DerTeufel)
-Ondemand tuned (updated based on code of stratosk)
-SmartassV2 governor
-OndemandX governor
-Interactive governor (updated to android 3.4 code + fixes)
-Wheatley & Lulzactive governors
-Conservative tuned
-Call volume hack (use “Settings>Mackay Settings”* to set volumes)
-Reduced battery polling interval
-Fast charge (activate through “Settings>Advanced Settings”* or the QuickCharge toggle in MackayROM)
-WiFi PM_FAST mode selection (activate using “Settings>Mackay Settings”*)
-Battery life extender (set through “Settings>Mackay Settings”*)
-CustomVoltage (set using NSTools)
-USB OTG support (needs external power supply)
-1100-1400MHz OC steps
-Custom kernel splash (Thanks to Malcho)
-Updated charging logo to match open charger
-Disabled swap & zram
-Improve memcopy/memmove
-Improve the performance of memcpy and memmove
-Kill task closest in size to memory needed to free
-LOAD_FREQ (4*HZ+61) avoids loadavg Moire
-Entropy tweaks: http://lwn.net/Articles/489734/
-backport CPUIDLE from 3.5
-arm/crypto: Add optimized AES and SHA1 routines
-Unaligned CPU access
-Improvements to RWSEM code
-Improvements to binder code
-Improvements to tmpfs
-Added frandom (much faster random number generator)
-Updated to lowmemorykiller with PID whitelist (thanks to stratosk)
-Many parts of the code build as module to reduce effective kernel size
-Updated wifi driver to 5.90.195.114
-Updated GPU driver to DDK [email protected]
-Proportional Rate Reduction for TCP
-Introduce timer slack controller
-Zram patched
-Low RAM switch option (default off)
To see the additions on top of Omni, check github (additional patches are always shown on top):
Settings
OmniGears
Frameworks
Fresh install:
Can be flashed on top of any ROM:
-Do a factory reset
-Wipe /system
-Flash ROM
-Boot the phone
-Reboot recovery
-Flash gapps & superSU
-Reboot your phone
Update:
-Flash ROM
-Reboot your phone
(no wipes or other things needed, just flash & reboot)
-Custom kernels can be used only if specific for OmniROM => currently none
Credits:
-Omni team for in incredible job on the ROM base
-OmNomteam: great group of Omni fanatics
-teamhacksung/pawitp for making KitKat work on our ancient phone
-stratosk/DerTeufel/Mialwe for the inspiration I got from their kernels
-rootax for providing a high-speed server for high quality downloads
-Malcho for his kernel splash & bootanimation
Downloads:
Rootaxbox
For those who want to theme it even further, Bejda made a Mackay splash screen!
http://forum.xda-developers.com/showthread.php?t=2214468
XDA:DevDB Information
[KK 4.4.2][ROM]Mackay OMNI ROM, a ROM for the Samsung Galaxy S I9000
Contributors
kasper_h
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: Omni
Version Information
Status: Beta
Created 2013-12-15
Last Updated 2014-02-27
Known issues:
-Mackay Settings FC
-??? tell me!
Downloadin... Thankx a lot
Second here
Downloading...
Envoyé depuis mon GT-P5110 avec Tapatalk 4
Installed and rebooting....
rodman01 said:
Installed and rebooting....
Click to expand...
Click to collapse
+1
dirty flash on yesterdays cm11.0 nightly didn't worked for me...caused (soft) reboots after displaying the sim code entering screen a few seconds...next try is with full wipe.
Kasper, I know how much time and effort you put into making OMNI work with our devices. I just wanted to say a big thank you, for making this a real thing. You are awesome
rodman01 said:
dirty flash on yesterdays cm11.0 nightly didn't worked for me...caused (soft) reboots after displaying the sim code entering screen a few seconds...next try is with full wipe.
Click to expand...
Click to collapse
Did you read the instructions? First flash should be after a factory reset + /system wipe
I tried a dirty flash myself, resulting in a bootloop
Just out of curiosity, what was the problem?
Downloading and flashing...
BIG BIG THANK YOU...
ps: 0AY28610E29000713, I know it's not that much but thank you...
mformarcee said:
Kasper, I know how much time and effort you put into making OMNI work with our devices. I just wanted to say a big thank you, for making this a real thing. You are awesome
Click to expand...
Click to collapse
+++++++++++++++++++++ 1
jv.batista said:
Just out of curiosity, what was the problem?
Downloading and flashing...
BIG BIG THANK YOU...
Click to expand...
Click to collapse
You mean with the data connection?
I still don't know what the real problem is. If I build my kernel with the Omni build system, data won't work. If I build my kernel with the CM11 and replace the Omni-build kernel for this CM11-build kernel, data works.
There are several differences between Omni & CM11:
-ramdisk differences (but adjust Omni ramdisk to make it almost identical to CM11 does not help)
-kernel image itself (it is not the same size, even though it is build with exactly the same toolchain)
I have spend many-many hours on this, but haven't been able to find it. Therefore, I decided to take the simple approach of using the CM11-build kernel as a prebuilt kernel for my Omni builds.
kasper_h said:
Did you read the instructions? First flash should be after a factory reset + /system wipe
I tried a dirty flash myself, resulting in a bootloop
Click to expand...
Click to collapse
Yes I read it, but tried it anyways ...and my post/feedback was meant as a warning or tip for all others, not to try it without! Sorry for the confusion!
rodman01 said:
Yes I read it, but tried it anyways ...and my post/feedback was meant as a warning or tip for all others, not to try it without! Sorry for the confusion!
Click to expand...
Click to collapse
Don't worry, I actually like it when people post these things as people don't always read the instructions anyways so having some additional warnings throughout the thread are fine with me
no "Themes" option (snif, snif)
Factory reset, system wipe, flash rom, flash gapps, OK, no FC.
Envoyé depuis mon GT-P5110 avec Tapatalk 4
the only thing i noticed, beside the mackay settings fc was the broken layout in the sim unlock screen...
ps: swiftkey makes settings fc during configuration, I miss battery percentage and still have a 3 to 4 seconds lag when receiving a phone call until the screen lights up...
thanks!! i downloading now!!
Thank you Kasper, working fine here ! OMNI FTW !
jv.batista said:
ps: swiftkey makes settings fc during configuration,I miss battery percentage
Click to expand...
Click to collapse
1. It fcs during setup when you launch it from the app drawer but if you go into System Settings -> Language & input , and you check SwiftKey and enter it's settings from there, it works to be configured with no FC. I think Switfkey is not updated to Android 4.4.2 or has an issue I think. Then you can use the keyboard.
2. Go to System Settings -> Battery -> Battery indicator, and select your desired icon with percentage.
Also for those that want RAM status and Clear all button in Recents Apps Window (Long press Home button pop-up) You can find those settings in System Settings under Interface section, click More.
UNOFFICIAL CyanogenMod 12.1 for the Samsung Galaxy Nexus
Introduction
I first decided to put together this Lollipop ROM using the old graphics drivers for those of us who wished to try Lollipop, but needed full camera functionality (i.e. barcode scanner apps, or any other app that uses the camera API). At this point, it looks as if the camera has been fixed to work with the newer GPU drivers. I will continue to develop this ROM using the older drivers until all of the major kinks are worked out (both DDK and non-graphics related included) and we have a 100 percent stable release. You are welcome to try my build which does offer some unique features and will continue to be improved upon and synchronized with the CyanogenMod sources.
Please note that you can NOT use any other kernels with this ROM!! I have added a number of additional features to the kernel including custom voltage, fast charge, and color adjustment so hopefully that will satisfy enough for the time being.
I welcome any and all feedback, including bug reports and feature requests. The Galaxy Nexus is my main phone, and this ROM has been stable enough to be my daily driver since I began developing it several weeks ago.
Additional Features Specific to this ROM
F2FS support for /data and /cache. System must be ext4.
LegacyCamera app included (more stable and lots of features)
Lower screen brightness during boot sequence (/etc/init.d/96screendim)
Adjusted minfrees for better multitasking
Xposed for Lollipop compatible*
Specify maximum number of recent apps (ro.config.max_recents)
AppOps control for platform signed apps (ro.appops.show_platform)
Ability to turn off the display during the boot sequence
Support for UnifiedNlp
Volume keys can wake/boot phone from offline charger mode
Additional AppOps (read phone info/other accounts)
Less frequent notifications
Emergency Battery feature
More QS Tiles: Reboot/Recovery, Screenshot, Screen Off
Setting to disable Media Scanner on boot
Volume keys can wake/boot phone from offline charger mode
Expanded Notification Panel width in Landscape Orientation
Disable USER apps from the Applications Manager
Whitelist apps to prevent them from being killed
Recents Privacy: hide app content from appearing in recents cards*
Cell/Wifi scan AppOp
Wakelock Blocker
NEW: Alarm Blocker
NEW: Marshmallow bootanimation
CyanogenMod Features
Better AppOps, including the ability to block wakelocks and alarms.
Status bar mods (brightness control, weather, battery icon style, double-tap to sleep)
Navigation bar customizations
Button mods (volume wake, volume cursor)
Color/Gamma calibration
Battery light enable/disable
CyanogenMod DSP
Scramble for PIN layout on lockscreen
Advanced reboot menu
Charging LED ON/OFF
Theme Manager
Additional Quick Settings tiles (ADB over network, compass, profiles, NFC, hotspot, AudioFX, screen timeout)
More pattern lock sizes (3x3, 4x4, 5x5, 6x6)
and more!!!
Kernel Features
CPU frequency slots: 230-1632Mhz
CPU governors: dyninteractive, interactive, conservative, ondemand, ondemandplus, userspace, powersave, performance, ktoonservative, zzmoove
Min Screen On / Max Screen Off
I/O scheduler: row, zen, noop, deadline, cfq, sioplus
TCP congestion control: cubic, reno, bic, westwood, htcp
Fast Charge (with data transfer)
GPU Overclock (max 512MHz)
IVA Overclock
SmartReflex: Core, IVA, MPU
SmartReflex: Min calibrated voltages
Custom Voltages
Custom Regulator Voltages: VAUX3_6030, VAUX1_6030, VMMC, VANA, V2V1, VDAC, VCXIO, VUSIM, VMMC, VUSB
Color Settings (gamma offset, color multipliers)
I/O Accounting (see this post for more information).
Vibrator Intensity
Headphone Volume Boost
lowmemorykiller whitelist
Emergency Battery Reserve (see this post for details)
GPU governors (on3demand, activeidle, onoff, userspace)
Instructions
First flash:
Unlock & install a recovery
Wipe data & cache partitions
Flash CM-12.1
Install the Google Apps package
Reboot
Upgrade:
Make a backup in recovery
Flash CM-12.1
Install the Google Apps package
Reboot
If you are using F2FS, boot will hang for a bit longer on the Google Logo before animation starts.
Initial boot will take longer than it does with other 5.1 ROMS because this ROM is deodexed. My main reason for doing it this way is so that I can make modifications to individual framework files without having to flash the entire /system partition. The downside is that the initial boot after a wipe of the dalvik-cache will take marginally longer because it has to rebuild the caches for all of the system apps. If you do this while you still have a full compliment of user apps installed - i.e. after an upgrade, the boot sequence could take a REALLY long time - so be prepared for that. Personally, I feel that this is a small enough inconvenience and the benefits outweigh the drawbacks.
Downloads
Latest Build
cm-12.1-20151223-UNOFFICIAL-maguro.zip
Changelog: 12/23/2015
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
Recommended Apps
Dark Material - CM12 Theme UI (Awesome looking Dark Theme for CM12/12.1)
TouchControl (Custom wake gestures, i.e. dt2w, s2w, etc. Choose "Ponury Stock Modified" kernel module)
3C Toolbox
Trickster MOD Kernel Settings
AZ Screen Recorder - No Root
Tips / Recommendations
Bugs
Gesture typing doesn't work on stock keyboard but does work on Google Keyboard
Disclaimer
I'm not responsible for bricked devices (honestly, has anyone actually ever bricked a GNexus?), data loss, lack of rhythm and coordination. Please remember to ALWAYS make backups before you flash and if you are changing filesystems on /data, you will lose ALL DATA which includes everything on internal storage and the recovery will NOT give you any warning before it performs this highly destructive act, so just be aware! Thanks and enjoy!
Click to expand...
Click to collapse
Thanks To/Credits
Code:
[URL="http://www.cyanogenmod.org/"]CyanogenMod[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3390093"]MWisBest[/URL]
[URL="http://forum.xda-developers.com/member.php?u=2633638"]Ziyan[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3623306"]Dirty_Jerz[/URL]
[URL="http://forum.xda-developers.com/member.php?u=4608636"]bsmitty83[/URL]
[URL="https://github.com/Liquidsmooth"]LiquidSmooth[/URL]
[URL="https://github.com/slimroms"]SlimRoms[/URL]
[URL="https://github.com/omnirom"]omnirom[/URL]
XDA:DevDB Information
CyanogenMod 12 (UNOFFICIAL) ROM for the Samsung Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
zzpianoman
Source Code: https://github.com/zzpianoman
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.0.101
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-23
Last Updated 2015-09-15
Reserved
Previous Builds
10/7/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347832232"]cm-12.1-20151007-UNOFFICIAL-maguro.zip[/URL]
09/14/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347816180"]cm-12.1-20150914-UNOFFICIAL-maguro.zip[/URL]
08/13/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347793158"]cm-12.1-20150813-UNOFFICIAL-maguro.zip[/URL]
07/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347782153"]cm-12.1-20150727-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]*****UPDATE*****[/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=62160732&postcount=396"]cm-12.1-20150727-UNOFFICIAL-tuna_update1.zip[/URL]
07/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347776472"]cm-12.1-20150718-UNOFFICIAL-maguro.zip[/URL]
07/11/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347772069"]cm-12.1-20150711-UNOFFICIAL-maguro.zip[/URL]
06/26/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347765291"]cm-12.1-20150626-UNOFFICIAL-maguro.zip[/URL]
06/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347763431"]cm-12.1-20150622-UNOFFICIAL-maguro.zip[/URL]
06/12/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347758931"]cm-12.1-20150612-UNOFFICIAL-maguro.zip[/URL]
06/04/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952614713"]cm-12.1-20150604-UNOFFICIAL-maguro.zip[/URL]
05/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952610816"]cm-12.1-20150527-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]***UPDATE***[/B][/SIZE] - Flash in recovery over 5/27/2015 build
[URL="http://forum.xda-developers.com/showpost.php?p=61026999&postcount=291"]cm-12.1-20150527_UNOFFICIAL-zzpianoman_update1.zip[/URL] (Fix for Play Services FC)
05/15/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952604054"]cm-12.1-20150515-UNOFFICIAL-maguro.zip[/URL]
04/29/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952594303"]cm-12.1-20150429-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B][U]GCC 4.7 Kernel[/U][/B][/SIZE]
If your device requires a kernel that is compiled with GCC 4.7
(i.e. won't boot) then flash this kernel over the 4/29/2015 build.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3289957&d=1430412506"]cm-12.1-zzpianoman-kernel-gcc-4.7.zip[/URL]
[SIZE="3"][B][U]UPDATE - 5/4/2015[/U][/B][/SIZE] - Flash in recovery on top of 4/29 build.
[URL="http://forum.xda-developers.com/showpost.php?p=60534106&postcount=217"]cm-12.1-20150429_UNOFFICIAL-zzpianoman_update1.zip[/URL]
04/23/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96042739161892516"]cm-12.1-20150423-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]GPS FIX:[/U][/B][/SIZE] - (flash this over [B]ANY[/B] CM-12 build prior to
4/29/2015 to fix satellite GPS!!)
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3279981&d=1429903277"]cm-12-maguro_gps_fix.zip[/URL]
04/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96039337900114737"]cm-12.1-20150418-UNOFFICIAL-maguro.zip[/URL]
[URL="http://forum.xda-developers.com/showpost.php?p=60269013&postcount=124"]Update - 4/21/2015[/URL]
04/05/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934551453"]cm-12-20150405-UNOFFICIAL-maguro.zip[/URL]
03/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934547216"]cm-12-20150327-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 4/2/2015[/U][/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=59850356&postcount=406"]cm-12-20150327_UNOFFICIAL-update1[/URL]
03/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934545093"]cm-12-20150322-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 3/22/2015[/U][/B][/SIZE]
This update include a kernel compiled with gcc 4.7 to fix some
non-booting devices with eMMC bug. Flash this in recovery
[B]after[/B] you flash the ROM. All future builds will include this by default.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3225706&d=1427145252"]cm-12-20150322_UNOFFICIAL-maguro_update1.zip[/URL]
Reserved
Yeah!! I was waiting for a CM12 rom based on DDK 1.8 as I wanted my camera to function properly. I'll flash it in a few hours and report back. Thanks!
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Tolazace said:
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Click to expand...
Click to collapse
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Nope. Just clean flash this Rom + Gapps. Without Gapps still the same problem :/
Other LP roms works great (CM, FML, AOSP, Zmod, Dreams etc)
zzpianoman said:
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Click to expand...
Click to collapse
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Fenix46 said:
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Click to expand...
Click to collapse
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
So when can you upload fix kernel? I would test this CM
zzpianoman said:
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
Click to expand...
Click to collapse
So, the problem and the GCC 4.9, go safe with GCC 4.7 a user has just confirmed that it works. This issue and on all models with the old chip "VYL00M"... with the new chip "V3U00M" the kernel can be compiled fine with GCC 4.9 no bootloop
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Shortly! I'm working on it....
Forgive me, I'm used to working on the toro variant so this eMMC bug is all new to me!
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Here is the kernel compiled with gcc 4.7. Let me know if this works!!
Working ^^ Thanks a lot I take for testing ^^
Tolazace said:
Working ^^ Thanks a lot I take for testing ^^
Click to expand...
Click to collapse
Great! I'll add it to the OP.
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
armbold said:
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
Click to expand...
Click to collapse
The rom automatically crops the section of video where green line is present. Not a solution, but a nice workaround.
The CM sources have not yet been udated to 5.1 so we'll have to wait until sources are updated to CM12.1
After one day using:
Positive:
-Rom is smooth and fast
-Green Lines "gone" (don't see it)
-Offmode Charging work
-Lot of features
-1080p don't laggy
-DoubleTap2Wake work *.*
Negative:
-Free ram is ~200mb so if you open sms/gallery/browser and listen music - music player turn off and after back to homescreen launcher is restart
-When 3G is ON - phone little laggy
-Recent stack laggy and sometimes have a bug with app name
Rom is Great and when management Ram maybe can be better this Rom be a best lollipop rom o Gnex So I can't wait for next version
(sorry for english)
@zzpianoman Bug?
ALBIEL said:
@zzpianoman Bug?
Click to expand...
Click to collapse
What am I looking at here? Mobile data issue?
I am closing this thread as I no longer have valid download links available, I can't maintain this project anymore, and I'd like to make sure everyone understands that any links uploaded by other users cannot be confirmed to be unmodified. Proceed at your own risk!
This thread is for the N900W8 and N900T variants of the Galaxy Note 3.
You can find the other thread for N9005, N900A, N900P, N900V, N900R4, N900K, N900L, N900S, SC-01F, and SCL22 variants here.
idleKernel is a fork from Imoseyon's leanKernel starting at his v6.3 Touchwiz release.
It adds a few more features, escaping somewhat from the minimalist approach while still staying battery friendly.
It hopes to support many ROMs. You can request support for your ROM through private message or on this thread.
You can also find Imoseyon's leanKernel here, which still has ongoing development.
DOWNLOAD
Current version: 7.1.0 (2016-03-27)
Note that there are both SELinux Enforcing and SELinux Permissive versions.
If you are using a custom ROM or f2fs, you will need the permissive version.
All Note 5 ports are forced permissive, and have no enforcing version due to invalid SEPolicy.
TouchWiz 5.0 kernels cannot have their SELinux mode changed by any means, they are compiled as either enforcing or permissive.
idleKernel is also used in the Kali NetHunter project! For full idleKernel functionality in Kali NetHunter, flash one of the images here before flashing NetHunter.
Please be careful to download the right version for your actual phone model, not your ROM.
N9005: hlte-eur
N900A: hlte-att
N900W8: hlte-can
N900P: hlte-spr
N900R4: hlte-usc
N900T: hlte-tmo
N900V: hlte-vzw
N900K: hlte-ktt or hlte-kor
N900L: hlte-lgt or hlte-kor
N900S: hlte-skt or hlte-kor
SC-01F: hlte-dcm
SCL22: hlte-kdi
DOWNLOAD LINKS REMOVED
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 kernel zip/tar you downloaded
Your device model (N9005, etc)
A link to the XDA thread of the ROM you're having trouble with
Optional: A logcat during the duration of when the bug is happening
Optional: A `cat /proc/kmsg > /sdcard/kmsg.log` (su required) during the duration of when the bug is happening
You may be able to fix the bug by updating to the latest bootloader and modem for your device.
See: (Direct Download) Latest Bootloaders & Modems
FEATURES INCLUDED FROM LEANKERNEL
overclockable to 2.72GHz, but limited to 2.2GHz during boot
interactiveX V4 (screen_off_maxfreq), renamed back to interactive for compatibility
/sbin/lkconfig script (via terminal emulator, superuser required)
user adjustable panel temperature: -60 to 0, 0 is kernel default (via lkconfig & sysfs)
user adjustable panel colors: 0 to 4, 2 is kernel default (via lkconfig & sysfs)
fix for purple hue/push at low brightness (via panel temperature or panel colors)
cpufreq modified to play better with thermal-engine
compiled with stable Linaro GCC Cortex-A15 4.9 toolchain
built-in supersu and init.d support
DriveDroid compatibility for USB mass storage emulation
interactive governor updated to latest android source (but ondemand left default)
outdated Samsung code updated to later CodeAurora source (cpufreq, mdss, gpu, msm-bus, etc.)
cpufreq issues fixed
exFAT support
ram console enabled for /proc/last_kmsg for kernel crash debugging
FauxSound 3.0
default USB charge speed @ 1200mA
based on N900TUVUFOB6 (February 23, 2015)
IDLEKERNEL FEATURES
rebased on N900TUVUFOL1 (December 5, 2015) and SC01FOMUGOI4 (September 9, 2015)
updated to latest 3.4 Linux (currently 3.4.111)
tailored individually to support all variants of TouchWiz 5.0, CyanogenMod 12.1 & 13.0, SlimRom 5.1 & 6.0, and Note 5 Ports
ramdisk and kernel compressed with xz-crc
FauxSound updated to 3.6
CodeAurora fixes up until December 8, 2015
new IO schedulers available: sio, fiops (default)
new TCP congestion control available: westwood
cubic (default) TCP congestion algorithm updated to Linux 4.3 sources
f2fs full /system /data /cache support (except in enforcing mode TouchWiz)
f2fs updated to latest kernel.org Samsung sources
ext4 updated to latest kernel.org sources
performance governor included for benchmarking & games
adreno idler updated to latest arter97 sources (now with 27 MHz idle)
forced fast charge support by Yank555.lu
full sysfs & in rom vibration control with extended range
compiled with -O2 optimizations
some kernel errors and logging functions fixed
lkconfig rewritten and extended, renamed to ikconfig
support for KCAL advanced color control by savoca
USB mass storage toggle for external SDcard, open Terminal Emulator and type: ums on.
USB 3.0 is turned on if you add 3 to commands: mtp on 3, ptp on 3, ums on 3.
SuperSU uses system install method even on marshmallow, adjustable via ikconfig (set on first boot)
USB HID keyboard and MIDI gadget support (added in 6.7.1!)
INSTALLATION
You can flash idleKernel from Odin 3.x in AP slot using tar.md5 files.
You can also flash from TWRP 2.8.x.x using zip files.
CONFIGURATION OPTIONS
Open Android Terminal Emulator or adb shell, become superuser by typing su, press enter, and type /sbin/ikconfig (on most ROMs you can just type ik), press enter again.
Code:
[email protected]:/ $ su
[email protected]:/ # /sbin/ikconfig
idleKernel configurator (based on lkconfig by Imoseyon)
---
0) display current settings
1) panel temperature
2) panel color
3) cpu max frequency
4) cpu governor
5) gpu governor
6) tcp congestion control
7) io scheduler
8) mmc crc
9) supersu install method
10) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit): 0
current settings
----------------
1) panel temperature: 0
2) panel color: 2
3) cpu max frequency:
screen on: 2265600
screen off: 1267200
4) cpu governor: interactive
5) gpu governor: msm-adreno-tz
6) tcp congestion control: cubic
7) io scheduler:
internal memory: noop deadline row [sio] fiops
external sdcard: noop deadline row [sio] fiops
8) mmc crc: disabled
9) supersu install method: system
I recommend the app Kernel Adiutor for control over idleKernel if you are inexperienced in terminal usage, it's very well written and easy to use.
If you want to use the FauxSound controls, please consider buying FauxSound from the Play Store. It's the same developer that wrote the kernel side components to it.
If you want to use KCAL advanced color control, you will need to download the Color Control app from here.
USB 3.0 & MASS STORAGE
idleKernel 6.6.2+ comes with a terminal command called usb, with shortcuts mtp, ptp, and ums.
These commands don't work from adb as running them usually closes the adb session cancelling the command part way through.
They are meant to be run from Terminal Emulator as superuser. If it shows not found, go into Terminal Emulator options and uncheck "Verify PATH entries". There is a bug in Terminal Emulator that causes /sbin to be removed from path sometimes when using su. You could also prefix the commands with /sbin/.
Code:
[email protected]:/ # usb
Usage: usb [mtp|ptp|ums|status] [on|off]
Enables or disables MTP, PTP, and UMS USB modes.
mtp on/off turns on/off MTP mode
ptp on/off turns on/off PTP mode
ums on/off turns on/off UMS mode
default sets USB mode to default
-3, 3 activates USB 3.0, use with on
-i, info, status displays active USB mode
-h, help displays this information
-v, version displays version info
For more help & to report bugs contact <[email protected]>
[email protected]:/ # ums on 3
Disabling USB transfer protocols...
Unmounting SDcard from /storage/extSdCard...
SDcard unmounted successfully.
Activating USB 3.0 SuperSpeed mode...
Setting up dwc3 storage gadget lun...
Mounting /dev/block/mmcblk1 to lun...
Activating USB Mass Storage transfer mode...
Done. PLEASE USE EJECT MEDIA ON PC BEFORE TURNING OFF UMS!
[email protected]:/ # mtp on 3
Disabling dwc3 storage gadget lun...
Disabling USB transfer protocols...
Mount SDcard in Android? (y/n): y
Mounting SDcard to /storage/extSdCard...
Waiting for SDcard to be ready....
SDcard mounted successfully.
Activating MTP USB transfer mode...
Done.
[email protected]:/ # usb default
Disabling USB transfer protocols...
Deactivating USB 3.0 SuperSpeed mode...
Setting USB mode to default...
Done.
TEAM WIN RECOVERY PROJECT
You will probably notice that in the downloads area there is also a TWRP 2.8.7.0 download option.
It uses idleKernel instead of the kernel prebuilts from Omni.
MTP and USB Mass Storage R/W now works in recovery mode, allowing you to plug phone in and easily transfer zips and backups/restores to and from your phone and sdcard. It also fixes some file system bugs that caused ext4 broken backups that couldn't restore to f2fs partitions, and other small bugs like brightness adjustment not working.
On top of that it allows me to support TWRP for variants that aren't officially supported, such as the Japanese and Korean variants.
You can also use ikconfig in TWRP from adb, allowing you to fix settings like unstable CPU overclocks from recovery.
It also has a really cool boot splash and gold theme, that's cool too right?
GOING TO F2FS FILE SYSTEM
See step-by-step guide here:
http://forum.xda-developers.com/gal...ekernel-leankernel-fork-t3241582/post64014959
KNOWN ISSUES
Screen sometimes turns on while charging from PC. (wake event sent from PC?)
Some ROMs refuse to flash in TWRP idleKernel edition. (tell ROM maintainer to fix flash model assert or remove assert yourself)
Streaming audio may occasionally stutter when screen is off. (increase screen off max frequency using ikconfig)
exFAT and f2fs formatted SDcards don't work in CM13. (not a kernel issue, wait for CM team to fix it)
Aroma Installer doesn't work in TWRP idleKernel edition. (it's not compiled with LP driver support? flash original TWRP to use Aroma)
If you are affected by a new issue, please follow ALL of the instructions above and post in the thread or pm it to me.
ROM DEVELOPERS
You have my permission to include idleKernel in your ROM. By doing so, I recommend that you give me the permission to try to work with users on your ROM thread to fix bugs that may possibly be kernel related. On important idleKernel updates, I may visit your thread and notify users of the changes and give them a link back to this thread.
You may also recompile idleKernel with your own changes, and give it a different name if desired. Credit to me is not necessary, but you must keep a branch with the complete source code on a publicly visible site like GitHub, and link to that from your thread. I have a guide in the post underneath this on how to do that.
If you wish to change the default settings of ikconfig when distributing the kernel in your ROM, the easiest way would be to mount /data in your recovery flash script, check for existence of /data/data/idlekernel, if it doesn't exist, create it and write values to a file for every setting you wish to change. Valid files are:
Code:
/data/data/idlekernel/paneltemp - values: -60 to 0 (default 0)
/data/data/idlekernel/panelcolor - values: 0 to 4 (default 2)
/data/data/idlekernel/scaling_max_freq - values in Hz: 652800, 883200, 1267200, 1574400, 2265600 (default), 2496000, 2726400
/data/data/idlekernel/screen_off_maxfreq - values in Hz: 652800, 883200, 1267200 (default), 1574400, 2265600
/data/data/idlekernel/cpu_governor - values: ondemand, interactive (default), performance
/data/data/idlekernel/gpu_governor - values: msm-adreno-tz (default), powersave, performance, simple_ondemand
/data/data/idlekernel/tcp_congestion_control - values: cubic (default), westwood, reno
/data/data/idlekernel/io_scheduler_internal - values: noop, deadline, row, sio (default), fiops
/data/data/idlekernel/io_scheduler_external - values: noop, deadline, row, sio (default), fiops
/data/data/idlekernel/use_spi_crc - values: Y, N (default)
/data/data/idlekernel/supersu - values: SYSTEMLESS=detect/true/false (default)
XDA:DevDB Information
idleKernel, Kernel for the T-Mobile Samsung Galaxy Note 3
Contributors
jcadduono, Imoseyon, arter97, faux123
Source Code: https://github.com/jcadduono/idleKernel-note3
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 7.1.0
Stable Release Date: 2016-03-27
Created 2015-11-05
Last Updated 2018-07-12
Reserved
EVER WANTED TO MAKE YOUR OWN KERNEL FORK?
jcadduono's GitHub forking crash course
1. Make an account on GitHub!
2. Use the fork button @ https://github.com/jcadduono/idleKernel-note3 or any other repository
3. In your terminal emulator, cd to the location you want your repository.
4. git clone https://github.com/YOUR_USERNAME/idleKernel-note3.git
(optionally add folder name after that command to change it to something other than idleKernel-note3)
5. cd idleKernel-note3
6. git remote add jc https://github.com/jcadduono/idleKernel-note3.git
(this will allow you to send commits to me, cherry-pick commits from me, or pull new commits from me!)
7. git fetch jc
(do this whenever you want updated commits from me to be available to you for cherry-picking or merging)
8. Be sure to set your git author information too, for proper commit info!
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
git config --global push.default simple
(that last one just removes a warning message whenever you push commits to github)
9. Whenever you want to pull all the latest and greatest commits from me all at once, run:
git fetch jc
git merge jc
I don't recommend doing that though, because if our branches diverge too much our commits might become incompatible or you might not want some of my changes.
The best way to do it would be to:
git fetch jc
git log jc/X
Replace X with ik-touchwiz/ik-cm12.1/ik-slim5.1, that will show you all of my commits.
For every new commit you want, cherry-pick one at a time to make sure each goes successfully.
git cherry-pick <hash from git log jc/X>
10. Now whenever you make changes to your fork, and you are satisfied with them, you can do:
git add .
(that adds every changed file to the next git commit)
or
git add <file>
then
git diff HEAD
(this is optional, but I recommend looking over everything you changed to make sure it makes sense and you can find extra whitespace or typos!)
11. Once you are satisfied with the changes you've made, you can commit them to the branch history.
git commit -m "made some great change that you detail here"
12. To put your new commits up on GitHub, all you have to do is:
git push
13. If you want to send that commit to me as well, you can do:
git push jc
TIPS
Made a mistake and committed it already? You can time travel through git history using the rebase command!
git rebase -i HEAD~X
Replace X with how far back in commit history you want to edit, trust me time travel is a bad idea.
Just change pick to drop and Ctrl+X Y enter, git will make that commit disappear forever like it never happened.
You can also use various other words like reword to change the message of a commit, etc.
In order for GitHub to accept rebases, you have to add -f to git push, but only if you are changing history you've already pushed to GitHub.
If you've already pushed a commit to GitHub and want to undo it, you can do:
git log
git revert xxxxxx
Replace xxxxxx with the hash of the commit you want undone.
If you haven't pushed to GitHub yet, using git rebase is fine for undoing or rewording commits.
Any time you want to see all the changes from one of my commits, you can use
git show xxxxxxxx
Replace xxxxxxxx with the hash from git log jc/X or even your own git log.
It pipes a nice scrollable colored diff through `less`
If you want to stop it from asking for your GitHub username when you push, in idleKernel-note3 directory do:
nano .git/config
Find a line that looks like:
url = https://github.com/......
Add before github.com so it looks like this:
url = https://[email protected]/...
Now press Ctrl+X Y enter to save.
Nice to see the new thread. I tried 6.5.0 on CM12.1, and it ran great on an N900T. Seems very fast and stable. No problems other than the 100% brightness bug mentioned in the first post.
Battery life was really good. Woke up to 99% battery (about 0.1% drain per hour) over around 6.5 hours, and I had a call during that time, so the notification light was running for a while. Stock CM12.1 battery drain was about 0.2% per hour for me (after my fixes).
Ran antutu benchmark, and the results were good (around 46.3k without overclocking), which is very similar to what I got with the stock CM kernel (46.2k). The newest leankernel 5.2 that just came out got about 44.9k. Spreadsheet with detailed results is attached.
frequentc said:
Nice to see the new thread. I tried 6.5.0 on CM12.1, and it ran great on an N900T. Seems very fast and stable.
No problems other than the 100% brightness bug mentioned in the first post, which I just double checked isn't in the stock CM kernel. Do you know if it's in the latest leankernel? I just installed it, but I don't remember noticing if it had that problem or not.
Battery life was really good. Woke up to 99% battery (about 0.1% drain per hour) over around 6.5 hours, and I had a call during that time, so the notification light was running for a while. Stock CM12.1 battery drain was about 0.2% per hour for me (after my fixes).
Ran antutu benchmark, and the results were good (around 46.3k without overclocking), which is very similar to what I got with the stock CM kernel (46.2k). The newest leankernel 5.2 that just came out got about 44.9k. Spreadsheet with detailed results is attached.
Click to expand...
Click to collapse
Interesting, some improvements could be from the -O2 flag used, or even the version of gcc used to compile. I see Linaro released a GCC 5.1 compiler now and I'm currently compiling with Christopher83's 4.9 toolchain. May or may not see a small improvement moving to GCC 5.1. I'm not too interested in trying to get a toolchain build environment going, so I'll just hope Christopher83 can make some time to release new toolchains soon.
Also, storage IO results, mmm, reason I went with SIO as the main scheduler was it seemed to be great with many storage IO threads while still being minimal and battery friendly. Looks like it's succeeding there.
In any case, all results are pretty close and probably can't be tested in real life scenarios, and are bound to vary between bench so I can't say for sure how much more performance you could possibly get out of idleKernel.
jcadduono said:
Interesting, some improvements could be from the -O2 flag used, or even the version of gcc used to compile. I see Linaro released a GCC 5.1 compiler now and I'm currently compiling with Christopher83's 4.9 toolchain. May or may not see a small improvement moving to GCC 5.1. I'm not too interested in trying to get a toolchain build environment going, so I'll just hope Christopher83 can make some time to release new toolchains soon.
Also, storage IO results, mmm, reason I went with SIO as the main scheduler was it seemed to be great with many storage IO threads while still being minimal and battery friendly. Looks like it's succeeding there.
In any case, all results are pretty close and probably can't be tested in real life scenarios, and are bound to vary between bench so I can't say for sure how much more performance you could possibly get out of idleKernel.
Click to expand...
Click to collapse
Using This baby on Darklord 5.1.1....So far, video flickering...Darkera fix that with some advice from Carlos(shinto kernel creator).My device is N900W8 on Darklord Rom.I download the hlt-can 6.5.1.I will like to send you the logcat,but dont know how...
alek889 said:
Using This baby on Darklord 5.1.1....So far, video flickering...Darkera fix that with some advice from Carlos(shinto kernel creator).My device is N900W8 on Darklord Rom.I download the hlt-can 6.5.1.I will like to send you the logcat,but dont know how...
Click to expand...
Click to collapse
upload them to Mega and post back the link
I'm getting very minimal deep sleep (less than 5% deep sleep even when screen off). Details:
Variant: N900W8
Kernel: idleKernel-hlte-can-6.5.2-cm12.1.zip and idleKernel-hlte-can-6.5.1-cm12.1.zip
Rom: https://plus.google.com/communities/106599804742834944713 (CM12.1 based)
Wakelock: NfcService:mRoutingWakeLock (keeps device awake 80% of the time, doesn't happen on the stock rom. NFC is not toggleable in settings, on stock rom as well as ik).
I'll try with another CM12 variant tomorrow, probably temasek, to confirm if this is a CM issue or one specific to the ROM that I'm using, or perhaps with n900w8. Let me know if there's anything else I can do to help. In actual usage, this kernel is excellent. Great on battery, and very smooth. Would be nice to fix the wakelock issue.
Edit: It seems like on the stock kernel (temasek kernel), nfc switches to off in setting s if i try to toggle it, but in ik, it never switches to off (and maybe keeps trying to toggle it on?).
ammarr said:
I'm getting very minimal deep sleep (less than 5% deep sleep even when screen off). Details:
Variant: N900W8
Kernel: idleKernel-hlte-can-6.5.2-cm12.1.zip and idleKernel-hlte-can-6.5.1-cm12.1.zip
Rom: https://plus.google.com/communities/106599804742834944713 (CM12.1 based)
Wakelock: NfcService:mRoutingWakeLock (keeps device awake 80% of the time, doesn't happen on the stock rom. NFC is not toggleable in settings, on stock rom as well as ik).
I'll try with another CM12 variant tomorrow, probably temasek, to confirm if this is a CM issue or one specific to the ROM that I'm using, or perhaps with n900w8. Let me know if there's anything else I can do to help. In actual usage, this kernel is excellent. Great on battery, and very smooth. Would be nice to fix the wakelock issue.
Edit: It seems like on the stock kernel (temasek kernel), nfc switches to off in setting s if i try to toggle it, but in ik, it never switches to off (and maybe keeps trying to toggle it on?).
Click to expand...
Click to collapse
:/ weird, I can try compiling kernel without any nfc support. I don't have this issue and the N900W8 is my device as well. I did have to turn off google wifi scanning though because that also gave me 80% awake time.
I see nfc in cm settings menu, and when I try to turn it on, it just greys it out and disables the option at off. I never have NfcService running either.
@ammarr I was having the same problem with the stock CM kernel. Removing the /system/app/NfcNci folder fixed the problem for me. You'll no longer see NFC as an option under settings. My system now enters deep sleep like 99% of the time.
frequentc said:
@ammarr I was having the same problem with the stock CM kernel. Removing the /system/app/NfcNci folder fixed the problem for me. You'll no longer see NFC as an option under settings. My system now enters deep sleep like 99% of the time.
Click to expand...
Click to collapse
Seems to have fixed the issue for me. Thanks for the suggestion!
ammarr said:
Seems to have fixed the issue for me. Thanks for the suggestion!
Click to expand...
Click to collapse
@jcadduono - thanks for a new kernel for us to play with! So far it runs great for me (2nd day). Just wanted to mention two little things: I tried terminal emulator but it does not have all the options to control the kernel, tried kernel auditor but it does not keep my settings after reboot, so far faux kernel control app seems to work the best for me. Otherwise so far it seems running great, thank you!
Hey guys, i havr a n900w8 on temasek 5.1.1 cm12.1. The 6.4.7 version works flawlessly.. But when I flash 6.5.3... I get stuck on starting apps screen and the phone never actually boots... Please help
Sent from my SM-N900W8 using XDA Free mobile app
flint777 said:
Hey guys, i havr a n900w8 on temasek 5.1.1 cm12.1. The 6.4.7 version works flawlessly.. But when I flash 6.5.3... I get stuck on starting apps screen and the phone never actually boots... Please help
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
are you using version from selinux_permissive folder, and have you tried rebooting to see if 3 boots or so gets past it
jcadduono said:
are you using version from selinux_permissive folder
Click to expand...
Click to collapse
Yup! permissive
Sent from my SM-N900W8 using XDA Free mobile app
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
jcadduono said:
are you using version from selinux_permissive folder, and have you tried rebooting to see if 3 boots or so gets past it
Click to expand...
Click to collapse
https://idlekernel.com/cm12.1/
Sent from my SM-N900W8 using XDA Free mobile app
flint777 said:
Yup! permissive
Sent from my SM-N900W8 using XDA Free mobile app
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
https://idlekernel.com/cm12.1/
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, lucky for you I also have an N900W8 so I will try out https://idlekernel.com/cm12.1/selin...1_11/idleKernel-hlte-can-6.5.3-cm12.1.tar.md5 with temasek's cm12.1 and see if I can find the issue later today. I need to get some chair hunting done.
jcadduono said:
Ok, lucky for you I also have an N900W8 so I will try out https://idlekernel.com/cm12.1/selin...1_11/idleKernel-hlte-can-6.5.3-cm12.1.tar.md5 with temasek's cm12.1 and see if I can find the issue later today. I need to get some chair hunting done.
Click to expand...
Click to collapse
Alright! Good lookin out bro
Sent from my SM-N900W8 using XDA Free mobile app
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
denny02ng said:
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I found it in the op
denny02ng said:
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
The download links are in the first post. Please read.
cuezaireekaa said:
The download links are in the first post. Please read.
Click to expand...
Click to collapse
Did you even read my question? Off course I read the op, but if you click on the note 5 ports link the latest 6.5.4 is not listed in the download links.
Sent from my SM-N920C using Tapatalk
*Disclaimer
*By flashing this Kernel , you automatically void your warranty!
* If your phone breaks, blows up or runs away from you, do not cry to me!
* Do not ask for ETAs!!
*Kernel Features
Compiled, Optimized and Power By aarch64-linux-gnu-gcc (GCC) 8.2.1
-O3 & -Ofast (Highest GCC optimization level)
Compiled with DragonTC Clang version 9.0.0-20190120 (based on LLVM 9.0.0svn)
Optimizing with Polly - Polyhedral optimizations for LLVM
Automatic OpenMP code generation
O3 -mcpu=kryo -mtune=kryo
CPU OC to 2112 Ghz for sliver core
CPU OC to 2592 GHz for Gold core
Memory Optimized
Graphite Optimization
Upstreamed to 4.4.174, Thanks nathanchance for maintaining the android-linux-stable repo
Latest Google february security patch
Kernel modules disabled
CPU Input Boost
Dynamic Stune Boost
Boost ddr bandwidth on screen wakeup
Performance Mode Enable
Latest WireGuard VPN snapshot
Wake gestures and vibration control ( DT2W, S2W, S2S)
EAS, schedutil, and idle governor updates
New EAS Patch from latest integration branch
Westwood tunables
Dynamic Fsync control
KCAL advanced color control
CPU governors: performance, schedutil
Wakelock blocker
Slimbus enhancement
I/O schedulers: cfq, bfq, sio, zen, fiops, maple, deadline, noop, tripndroid, anxiety
ZRAM with upstream improvements
Global Wi-Fi MAC randomization disabled by default
Kernel low memory killer with OOM reaper to fix memory issues
Updated CFQ I/O scheduler with upstream patches
Force fast charge
USB Fast charge
Simple GPU Algorithm
Overclock for GPU to 750 mhz max
Lowmemorykiller Backport from 4.9 Kernel
ZRAM implementation updated from kernel/common and new compression algorithm ZSTD
Simple Gpu Agorithm
Gpu Boost
Adreno Idler
Backlight Dimmer
Backlight Max Brightness
Randomized Mac address
Fingerprint Unlock boost
DTS Audiowizard Kernel Side support (use DTS Headphone X Mod)
And Many More
*Download
*ElixirKernel Github Release
*Android File Host Download
*Source
*ElixirKernel Source
*Credit To All Developers
*Google
*nathanchance
*Sultan Alsawaf
*msfjarvis
*flar2
*tbalden
*frap129
*osm0sis > AnyKernel2
*faux123
*kdrag0n
*joshuous
*neobuddy89
*franciscofranco
* Freak07
*To All Developer that I forgot
*And of course, thank you for your love and support!
Have Fun & Enjoy the Kernel
About to flash, thank you!
Sent from my Pixel 2 XL using Tapatalk
Thank you for the kernel my friend, it's up and running. Couple of questions if I may.
1. The min CPU frequencies are running at:
748MHz on the little cluster
806MHz on the big cluster
Is that by design due to the over clocking??
2. During installation in twrp, the output read that "this is an unsupported configuration" however, it flashed and is running fine.
Just looking for a little clarification is all my friend. Thanks again for the kernel. I enjoy trying out new stuff :good:
Badger50 said:
Thank you for the kernel my friend, it's up and running. Couple of questions if I may.
1. The min CPU frequencies are running at:
748MHz on the little cluster
806MHz on the big cluster
Is that by design due to the over clocking??
2. During installation in twrp, the output read that "this is an unsupported configuration" however, it flashed and is running fine.
Just looking for a little clarification is all my friend. Thanks again for the kernel. I enjoy trying out new stuff :good:
Click to expand...
Click to collapse
You would still get 10hr SOT?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
You would still get 10hr SOT?
Click to expand...
Click to collapse
Probably, but it never hurts to ask :laugh:
Badger50 said:
Probably, but it never hurts to ask :laugh:
Click to expand...
Click to collapse
You can set to lower iddle frequency in CPU boost setting. Those setting is work great for me. As performance wise and battery. Thanks
ZION959 said:
You can set to lower iddle frequency in CPU boost setting. Those setting is work great for me. As performance wise and battery. Thanks
Click to expand...
Click to collapse
Much obliged. And what about the installation thing in twrp?
Badger50 said:
Much obliged. And what about the installation thing in twrp?
Click to expand...
Click to collapse
I will double check and fixed it tomorrow when I have time. It should flash fine . Just some minor issue . Thanks
ZION959 said:
I will double check and fixed it tomorrow when I have time. It should flash fine . Just some minor issue . Thanks
Click to expand...
Click to collapse
Not a big deal my friend. It flashes and runs just fine. Thanks again for the clarification :good:
Badger50 said:
Not a big deal my friend. It flashes and runs just fine. Thanks again for the clarification :good:
Click to expand...
Click to collapse
The flags " Completely unsupported OS configuration" is because you still on 8.1.0 correct.
here is the codes that check for it before you flash
Code:
# Warn user of their support status
android_version="$(file_getprop /system/build.prop "ro.build.version.release")";
security_patch="$(file_getprop /system/build.prop "ro.build.version.security_patch")";
case "$android_version:$security_patch" in
"9:2018-11-05") support_status="a supported";;
"8.1.0"*|"P"*|"9"*) support_status="an unsupported";;
*) die "Completely unsupported OS configuration!";;
esac;
ui_print "•"; ui_print " • You are on $android_version with the $security_patch security patch level! This is $support_status configuration...";
ZION959 said:
The flags " Completely unsupported OS configuration" is because you still on 8.1.0 correct.
here is the codes that check for it before you flash
Click to expand...
Click to collapse
I flashed a few hours ago and got the same error. I am on Havoc with the latest firmware and February vendor.
ZION959 said:
The flags " Completely unsupported OS configuration" is because you still on 8.1.0 correct.
here is the codes that check for it before you flash
Click to expand...
Click to collapse
No he is on latest monthly stock update for sure.
ZION959 said:
The flags " Completely unsupported OS configuration" is because you still on 8.1.0 correct.
here is the codes that check for it before you flash
Click to expand...
Click to collapse
Nope. I'm on February 9.0
Badger50 said:
"this is an unsupported configuration"
Click to expand...
Click to collapse
ZION959 said:
The flags " Completely unsupported OS configuration" is because you still on 8.1.0 correct.
here is the codes that check for it before you flash
Click to expand...
Click to collapse
Code:
# Warn user of their support status
android_version="$(file_getprop /system/build.prop "ro.build.version.release")";
security_patch="$(file_getprop /system/build.prop "ro.build.version.security_patch")";
case "$android_version:$security_patch" in
[COLOR="RoyalBlue"]"9:2018-11-05") support_status="a supported";;[/COLOR]
[COLOR="royalblue"]"8.1.0"*|"P"*|"9"*) support_status="an unsupported";;[/COLOR]
*) die "Completely unsupported OS configuration!";;
esac;
ui_print "•"; ui_print " • You are on $android_version with the $security_patch security patch level! This is $support_status configuration...";
His post says "an unsupported configuration" not "Completely unsupported OS configuration". Based on your code it seems 8.1.0, P, and 9 (non November 2018) will trigger the unsupported message; and only 9 on November 2018 security patch will trigger the supported message. This code is not updated probably.
I have smooth n good memory management looking forward for battery
After installing this Kernel it Shows model: asus_x00qd under system instead of p2xl that Breaks some stuff For me....
PsychOlli said:
After installing this Kernel it Shows model: asus_x00qd under system instead of p2xl that Breaks some stuff For me....
Click to expand...
Click to collapse
Where is that Asus info at? Thanks
Edit : it relate to dts driver. Will fixed it next update
First of all, thanks for the amazing Kernel. It really stands out from others by having more features.
ZION959 said:
Where is that Asus info at? Thanks
Edit: it relates to its driver. Will fix it next update
Click to expand...
Click to collapse
I think the "ASUS" things is related to DTS:HPX mod which is needed to be changed because of the mod's functionality. Anyway, I really thank you for including the dts commits.
:good:
v3.6 is up some minor issues fixed. Enjoy!!!
*GCC Version Download
*ElixirKernel Github Release
*Android File Host Download
*DragonTC Clang 9.0 Version Download
Compiled with DragonTC Clang version 9.0.0-20190120 (based on LLVM 9.0.0svn)
Optimizing with Polly - Polyhedral optimizations for LLVM
Automatic OpenMP code generation
O3 -mcpu=kryo -mtune=kryo
*Android File Host (DTC Clang 9.0) Download
Enjoy!!!
Thanks! Just to bring to your attention kernel number was not updated to 3.6, still showing 3.5.
Optimized LineageOS 18.1
brought to you by the Jflte DevConnection Team
DISCLAIMER
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!
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.
FEATURES
Based on Official LineageOS 18.1 - Android 11
Latest Security Updates integrated
Improved Speed, Stability, RAM usage & Battery drain
Powered by Buffcore Kernel - some / most / all of the following may or may not be hooked up yet.
Many, many more - install and see for yourself!
Buffcore 10
set config_hz to 300
add intelliplug
tweak our touch boost
add color control tweak
stop lowclocks from defconfig
build with gzip
quickwakeup - the kernel can semi-wakeup and decide if needs to end suspend or return to suspend with losing
doze
fully optimized toolchain flags
reduced sleep timeout
dynamic file syncing - early_suspend and dyn_fsync by default
print to dmesg log when a suspend gets broken
sdfat enabled
fastcharge implemented (up to 1900 ac / 1600 usb)
bcmhd wakelocks for rx and tx halved
libmemcopy and libstring sped up
io readahead to 1024k
power efficient work queues
voltage tweaking user interface
faster vmstat
autosmp hotplugging replacement
mmc crc disabled
allow for lower cpu voltage
reduce swapiness
optimize divide / multiply by power of 2
added tcp optimization options
set westwood default
optimize cbfillrect function
reduce wifi wakelock times
nohz: reduce overhead under high-freq idling patterns
SUPPORTED DEVICES
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-i9507 (jtfddxx)
GT-i9508 (jfltezm)
SCH-I545 (jfltevzw) VERIZON USERS: since your Bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 (jflteusc)
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your Bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-l337Z (jfltecri)
SGH-M919 (jfltemo)
SGH-S970G (TracFone / Straight Talk)
SM-S975L (TracFone / Straight Talk)
SPH-L720 (jfltespr)
SPH-l720T (jflterefreshspr)
jfltezm - China Mobile
jfltetfnatt
jfltetfntmo
Do 'getprop ro.bootloader' in Terminal Emulator or through ADB shell to find out which Bootloader you have.
DOWNLOADS
Optmized LineageOS 18.1: Google Drive
GApps: Open GApps / Open GApps A11 (Test Builds) or BitGApps or MindTheGApps
Official TWRP Recovery: HERE
JDCTeam TWRP Recovery: HERE
TWRP Recovery Loki Patched: HERE
Magisk: HERE
GAPPS
You can use Pico or Nano Open GApps / Open GApps A11 (Test Build) or BitGApps or MindTheGApps
Be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
TWRP
You can use either the latest and recommended Official TWRP Recovery or JDCTeam Recovery to flash the ROM.
If you have a variant with a locked but exploitable Bootloader like AT&T and Verizon then use the TWRP Recovery Locki Patched by mattgyver.
SAMSUNG GALAXY S4 UNIFIED GUIDES & COLLECTION
You can follow the well-explained steps to install a ROM, find and download the latest Bootloader & Modem for your variant from the S4 Unified Guides & Collection thread by Retrial.
JDCTEAM UNIVERSE
You can find the total work of JDCTeam over the years HERE.
SOURCE CODE
Avaible at JDCTeam GitHub
CREDITS
Side - Lead Developer / The Boss
Buff99 - Minor Developer / Major Meddler
JDC Team
LineageOS
OpenGapps
JDCTeam
Buff - Buff99
Chibbo - Chibbo
Creeper - Creeper36
Diego Monaco - alucard_24
Dimitris Katikaridis - side
Franck Rohée - franzyroy
George Mantratzis - Retrial
Ray Daley - gadget!
Jim Silverlock - Jsilver73
Marco Zanin - -+BB+-
Matthew Booth - MattBooth
Mattia D'Alleva - AntaresOne
Mike Atkins - FernBch
Oliver - angelcalibur
Paul Harris - hawkerpaul
Paul Keith - javelinanddart
SalimPS - SalimPS
Simeon Ivanov - smstiv
Stefano Meroni - smeroni68
Yannis Menexes - SkL*
Vasileios Moisiadis - vmroot
You are welcome to join the Official JDC Team chat/test group in Slack
reserved
reserved
reserved
Long live side da great
Thanks @side for making Android 11 for our jf this long.
Side you are the king baby
Superb audio quality for USB (UAC 44.1kHz 32bit) and Bluetooth (LDAC).
Noop I/O scheduler is not bad for audio (BFQ has disappeared).
I found two "Android Services Library" system apps in this ROM. One is "android.ext.services" and the other is "com.google.android.ext.services". Is this normal?
zyhk said:
Superb audio quality for USB (UAC 44.1kHz 32bit) and Bluetooth (LDAC).
Noop I/O scheduler is not bad for audio (BFQ has disappeared).
I found two "Android Services Library" system apps in this ROM. One is "android.ext.services" and the other is "com.google.android.ext.services". Is this normal?
Click to expand...
Click to collapse
https://source.android.com/devices/architecture/modular-system/extservices thats ext.services
the com.google.android.ext.services is Gapps related
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
still found a few gapps
side said:
https://source.android.com/devices/architecture/modular-system/extservices thats ext.services
the com.google.android.ext.services is Gapps related
Click to expand...
Click to collapse
Sorry. I confirmed that "com.google.android.ext.services" came from "BiTGApps-arm-11.0.0-R19_signed" (I have installed this and Magisk 21.1 on this ROM). I was able to disable "com.google.android.ext.services" without problems.
side said:
{
"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"
}
Optimized LineageOS 18.1 for the Samsung Galaxy S4 (Qualcomm variants)
Brought to you by the Jflte DevConnection Team
DISCLAIMER
Code:
* Your warranty is now void.
< Well lets face it, your warranty has been void for 3+ years now.. Samsung don't care about you. Who do? JDCTeam. >
* 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!
* 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.
FEATURES
Based on Official LineageOS 18.1 - Android 11_r19
Latest Security Updates integrated
Improved Speed, Stability, RAM usage & Battery drain
Powered by Buffcore Kernel - some / most / all of the following may or may not be hooked up yet.
Code:
[B][COLOR="DarkOrange"]Buffcore 10[/COLOR][/B]:
set config_hz to 300
add intelliplug
tweak our touch boost
add color control tweak
stop lowclocks from defconfig
build with gzip
quickwakeup - the kernel can semi-wakeup and decide if needs to end suspend or return to suspend with losing doze
fully optimized toolchain flags
reduced sleep timeout
dynamic file syncing - early_suspend and dyn_fsync by default
print to dmesg log when a suspend gets broken
sdfat enabled
fastcharge implemented (up to 1900 ac / 1600 usb)
bcmhd wakelocks for rx and tx halved
libmemcopy and libstring sped up
io readahead to 1024k
power efficient work queues
voltage tweaking user interface
faster vmstat
autosmp hotplugging replacement
mmc crc disabled
allow for lower cpu voltage
reduce swapiness
optimize divide / multiply by power of 2
added tcp optimization options
set westwood default
optimize cbfillrect function
reduce wifi wakelock times
nohz: reduce overhead under high-freq idling patterns
Many, many more - install and see for yourself!
SUPPORTED DEVICES
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-i9507 (jtfddxx)
GT-i9508 (jfltezm)
SCH-I545 (jfltevzw) VERIZON USERS: since your Bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 (jflteusc)
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your Bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-l337Z (jfltecri)
SGH-M919 (jfltemo)
SGH-S970G (TracFone / Straight Talk)
SM-S975L (TracFone / Straight Talk)
SPH-L720 (jfltespr)
SPH-l720T (jflterefreshspr)
jfltezm - China Mobile
jfltetfnatt
jfltetfntmo
Do 'getprop ro.bootloader' in Terminal Emulator or through ADB shell to find out which Bootloader you have.
DOWNLOADS
Optmized LineageOS 18.1: Google Drive
JDCTeam TWRP Recovery: HERE
TWRP Recovery Loki Patched: HERE
Aroma Addon: HERE
GAPPS
You can use Pico or Nano Open GApps or BiTGApps
TWRP
You can use either the latest and recommended JDCTeam Recovery or the latest Unified Official TWRP Recovery to flash the ROM.
If you have a variant with a locked but exploitable Bootloader like AT&T and Verizon then use the TWRP Recovery Locki Patched by mattgyver.
AROMA ADDON
You can multiple times flash the Addon Aroma to add or remove apps-mods, change bootanimations and contain debug tools.
You can find it HERE.
INSTALLATION GUIDES - COLLECTION LATEST BOOTLOADERS & MODEMS - AND A LOT MORE
You can follow the well-explained steps, find and download the latest Bootloader & Modem for your variant from the S4 Unified Guides/Collection thread by Retrial which contains:
COMPLETE GUIDE FOR THE BEST CLEAN INSTALL OF STOCK OR CUSTOM ROM FROM SCRATCH
COMPLETE GUIDE TO CLEAN INSTALL A CUSTOM ROM NOT FROM SCRATCH
COMPLETE GUIDE TO DIRTY INSTALL OVER YOUR CUSTOM ROM
COLLECTION FOR ALL VARIANTS WITH THE LATEST FIRMWARE - BOOTLOADERS & MODEMS - TWRP - GAPPS - ROOT SOLUTION - PIT FILES - SAMSUNG USB DRIVER - ODIN - USEFUL APPS - RECOMMENDED ROMS
JDCTEAM UNIVERSE
You can find the total work of JDCTeam over the years HERE.
SOURCE CODE
Avaible at JDCTeam GitHub
CREDITS
Side - Lead Developer / The Boss
Buff99 - Minor Developer / Major Meddler
JDCTeam
LineageOS
OpenGapps
JDCTeam
Buff - Buff99
Chibbo - Chibbo
Creeper - Creeper36
Diego Monaco - alucard_24
Dimitris Katikaridis - side
Franck Rohée - franzyroy
George Mantratzis - Retrial
Ray Daley - gadget!
Jim Silverlock - Jsilver73
Marco Zanin - -+BB+-
Matthew Booth - MattBooth
Mattia D'Alleva - AntaresOne
Mike Atkins - FernBch
Oliver - angelcalibur
Paul Harris - hawkerpaul
Paul Keith - javelinanddart
SalimPS - SalimPS
Simeon Ivanov - smstiv
Stefano Meroni - smeroni68
Yannis Menexes - SkL*
Vasileios Moisiadis - vmroot
You are welcome to join the Official JDCTeam chat/test group in Slack
Click to expand...
Click to collapse
Many thanks to side and team for android 11 on Galaxy s4.
Magisk 21.1 does not install. Any help much appreciated.
stuie1952 said:
Many thanks to side and team for android 11 on Galaxy s4.
Magisk 21.1 does not install. Any help much appreciated.
Click to expand...
Click to collapse
Ok. Got it. Change bin extension to zip. Simple as!!
Really nice work and Rom from thr JDC Team!
Unfortunately I experience some bugs:
Bluetooth does not reliably enable from the quick settings (automatically turns off again)
- for WiFi, sometimes networks are not found and an empty list is shown . switching to flight mode and back resolves this.
Awesome release. I like this one far better than [JDCTeam] Optimized LineageOS17.1 v8.0 (... mainly because I experienced random crashes with it).
The phone feels a lot faster running this ROM compared to the above mentioned, however I already encountered some small issues:
> Google Maps latest version (from Google Playstore) seem to have an issue with Android 11, therefore had to downgrade manually to 10.54.0 (https://www.apkmirror.com/apk/google-inc/maps/maps-10-54-0-release/) to fix the issue.> Similar issue was encountered with latest "Vanced Youtube" release - something about Google Play Services not being supported on this device. A downgrade to to 15.33.34 fixed it.> Android 11 seems to have removed global "Immersive Mode" and now its up to apps to implement it? Is there an app that still works (don't care if its per app basis or global as long as it works) ? Anyways, please try to bring it back Q.Q> Home Screen "Search" feature does literally nothing.> I can't seem to find screen pixel shutdown feature (was it called screen dimming or smth?) that was available in LineageOS17.1 v8.0 for AMOLED screens, then again its not a mandatory feature, but I appreciated that extra battery life.> Battery Charging statistics on lock screen seems to be missing too unlike LOS17.1 It was useful to know if my charging cables were faulty.
I did experience some random restarts, but can't confirm if it was the ROM problem or it was me messing with ADB , experimenting to transfer ~10GB of data via USB and Wireless at the same time, so maybe I overloaded something by attempting that among other things xD
I didn't experience Bluetooth or Wi-Fi issues so far, seems way more reliable than the LineageOS17.1.
Furthermore, I did use the "Aroma Installer 10" and I can say that the Magisk Manager is either bugged or the latest version simply doesn't allow to Install Magisk automatically anymore - it allowed only downloads and even then the magisk.zip threw errors upon flashing via TWRP. Manually downloading Magisk v21.1 from https://github.com/topjohnwu/Magisk/releases and flashing it did work tho ;]
Anyways, keep up the awesome work! I'm a big fan of all Optimized LineageOS releases
basti_b24 said:
Really nice work and Rom from thr JDC Team!
Unfortunately I experience some bugs:
Bluetooth does not reliably enable from the quick settings (automatically turns off again)
- for WiFi, sometimes networks are not found and an empty list is shown . switching to flight mode and back resolves this.
Click to expand...
Click to collapse
I experienced this too. My other small issues are,
USB OTG memories cannot be used (but I can use USB DAC's)
Bluetooth aptX codec's default sampling freq. is 48kHz (changeable to 44.1kHz after connected), while SBC&AAC's default are 44.1kHz.
Greetings I have this room for daily use since it left and I can notice that it loses the wifi and is less strong than normal the other detail is in wassap the voice and audio and group calls presents a failure nop works well that alone would be important to solve those two things rest is beautiful androit 11 congratulations
This rom works flawlessly on my Samsung Galaxy S4 SGH-M919...I have 2 great suggestions....the Ambient Display when Notifications arrive and the Always On Display...I like those two.
Spotted a weird bug with the quick settings panel:
The icons just disappear sometimes. They do come back if you expand it further. I though it was just dark mode thing, but same behavior happens with light mode too. I noticed the bug started to happen once I edited (added more buttons) the quick settings panel.
-- EDIT
I fixed it or more probably caused it via "SystemUI Tuner" by enabling "QS Fancy Animation" setting.
Hey guys!
maybe I'm really blind, but I can't find any ARM Gapps for Android 11...
any suggestion or (better a) link?
thank you.