[ROM] Elix-R | V2.0.1 | 5.0 + 5.0.1 Hybrid | 12/07 | Fast | Simple | Elegant | - Nexus 6 Android Development

{
"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"
}
Elix-R V2.0 has been constructed from the ground up to bring you a revolutionary new experience. Based off the latest Google LRX21O Factory image all the ROM's
features and tweaks have been hand crafted into this ROM without any cherry picks, or any merges. There are several benefits to this one being is the ROM stays
true to Stock, NO BS, NO NOTHING. Another benefit is the ROM is rock solid virtually no bugs exist meaning no random crashes or speed bumps. Speed is a top priority
as well as it contains various optimizations to speed up the device as well as many small changes that give the ROM a speed boost. Lastly but not least is Simplicity.
The ROM has been custom themed with "Elixium UI" that brings an elegant and beautiful UI to the whole system. Hope you enjoy the ROM.
* Based Off LRX21O Factory Image
* Odexed (For Speed)
* Sensei Kernel
* Removed Forced Encryption
* Improved battery + Performance
* S2S and S2W
* Pre-Installed Gapps
* Incorporation of Elixium UI
* New UI_Tick sound
* Android 5.0.1 Merged (Hybrid 5.0.1 + 5.0)
* Android 5.0.1 Android Runtime merged for speed
* Roboto Condensed Font
* Awesome Wallpaper
* Pie Is Fixed
* Most Apps Up To Date
* Perfect harmony between performance and battery life.
* Tweaked System Transitions
* Debloated (Removed Uncommon Languages, Korean IME sorta apps, etc)
* Disabled Safe Media Volume
* Louder Tick + Lock Sounds
* Increased Wi-Fi Scan Interval
* Made Max Multiusers to 10 rather than 4
* Removed Battery Saving Mode Color
* Changed Default Settings (Usability)
* System Animations Optimizations
* Subtle Audio Optimizations
* LED When Charging + Low Battery
+ LOTS MORE
Download Elix-R V2.0.1 - Download
* NOTE - PLEASE UNMOUNT THE SYSTEM PARTITION BEFORE INSTALLING.
* NOTE - This ROM comes with an unencrypted kernel please flash an encrypted kernel if your system is encrypted before booting up the ROM (EX: Lean kernel).
* NOTE - If you have problems with signal please flash SuperSU (Right below ME).
* NOTE - If you would like ROOT please flash THIS afterwards.
* NOTE - If sprint is not working please flash THIS.
* NOTE - There is a weird bug when restoring from a google account. it causes the device to spazz out for 10 minutes while it stabilizes.
V2.0.1
First Release For SHAMU.!!!!
CREDITS
Google
Bigxie for his stock base ROM.
XileForce For his extensive patience and for being such a great tester.
RIPng for his kernel (Found HERE)
If I missed you please let me know so I can add you.
Donations are greatly appreciated but never required. If you would like to donate you can do so clicking the
link below my username or on Google Wallet to "[email protected]". Thanks and hope you enjoy the ROM.
​

​
​

Kernel Tweaking Starter Guide (Including Colors):
If you are having issues please notify RIPng ,The Kernel Dev, on his hangouts: [email protected]
This ROM comes pre packaged with the Sensei Kernel which allows for a variety of tweaking options.
The following can be done using your favorite kernel tweaking app. I use FauxClock.
Updating The Kernel:
Before we get started, you are going to want to make sure your kernel is the latest! RIPng, the developer of Sensei Kernel, frequently releases new builds so its highly likely the kernel packaged with the ROM is out of date. First go to your settings menu, then about phone, then look at the section titled "Kernel Version". You should see something like "3.10.61 ~SENSEI.R7". R7 is the version of the kernel. Now go to the kernel thread here: http://forum.xda-developers.com/nexus-6/development/kernel-sensei-kernel-t2956283 you will see in the title what version kernel is the current release. As of this writing it is R9 for example. To update the kernel, simply click the downloads link and find the latest version. Once downloaded just go into TWRP and flash the kernel. Do not wipe anything. You now have the latest Sensei Kernel
Clock Speed:
To begin I prefer to leave my max clock speed at the stock 2.649ghz, this is because I have a bin 5 CPU . Set min CPU as low as it can go. As of current release this is 300. For the adventurous you can try 2.88ghz. For people near or below bin 5, you will want the voltage for that frequency around 1155mVolts. If you really wanna over clock you can try 2.95ghz. Again I've found a voltage of ~1200mVolts to be sufficient for stability. I don't recommend attempting 3ghz unless you are above a bin 6.
To find your CPU binning run this command in terminal emulator:
su (enter)
cat /proc/cpu/msm_acpu_pvs (enter)
note that the number may be displayed at the beginning of the next line.
It will then display a number from 0-15. 15 being the best. Don't stress over it too much if you score low, its not the end of the world. It just means you need marginally more voltage to run each frequency.
Governor:
Most people will probably want to just leave this set to interactive. Its a really good governor that is being actively devolped by CAF and Google. Its "smarter" than OnDemand and generally considered to offer better battery life. If you want even more smoothness some consider OnDemand to provide a bit better performance, however you may get slightly worse battery life. This is because OnDemand ramps up to max frequency when there's is load put on the CPU and then slowly works its way down. Interactive scales through the frequencies on the way up and down which saves battery life but prevents it from jumping to max speed as fast if it is needed. Simms22 recommends using the OnDemand governor with "upthreshold" set to 98 and the sampling rate set to 15000. That is the default setting of the Trinity Kernel. Mistertac made the great suggestion of turning the max screen off frequency down to 600mhz if using the interactive governor. This will prevent any misbehaving apps from keeping CPU ramped up while screen is off and give better idle drain. The actual number you would have to type in would be 652800 for the screen off frequency. As of the latest update I recommend running the intelliactive governor, its basically an enhanced version of the interactive governor created by the brilliant faux123, it is designed to run with intelliplug, but works on mpdecision as well.
Hotplugging:
Next go to hot plugging section and disable MPDecision(make poor decision) and enable intelliplug. FauxClock allows you to further configure intelliplug. If you want more battery set it to Conservative (4) mode which will hotplug the CPU more conservatively and save you battery, essentially this means it will use less cores if it can. For most people, leaving it on Balanced (4) mode will be fine. If you want further battery savings you can set it to EcoPerformance (2) which will only use a max of 2 cores.
Voltage Control:
Next go to voltage control. I'm a Bin 5 and I can use a 24mVolt undervolt without becoming unstable. This means pretty much anyone can probably get away with this and its across the board battery savings so you may as well. Rember! Never set voltages to apply on boot until you have tested them for a few hours first! Most people can probably get away with a 36mVolt undervolt. Also remember that if you are running an over clock you may not want to undervolt. If you find yourself running into freezes or random reboots remove the undervolt!
I/O Settings:
For I/O scheduler select Deadline. As of the current available options Deadline is the best. I then proceeded to do a lot of benchmarking with different read ahead sizes. 1024 seems to be the optimal setting. Going larger degraded performance as did going lower. Newer builds of Sensei now include FIOPS scheduler which is widely regarded as one of the best for phones, so I suggest using that over deadline.
Color Control:
Next you may want to adjust Screen RGB. WrinkleFree over in the Lean Kernel thread did extensive testing with a professional grade $1000 screen calibration tool.
For the most truly color accurate screen at D6500K:
Red - 248
Green - 246
Blue - 255
If you prefer a slightly cooler screen and the tuning the iPhone uses which is D7400K:
Red - 237
Green - 235
Blue - 255
More info can be found about color calibration here: http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620
These settings are meant to be used as a starting point. Depending on your cpu binning and desires you will probably want to tweak these slightly to fit your needs. I'll add more as new features get added, I learn more, and I think of stuff to add Hope it helps someone!

Sweet...loved this ROM on my N5
Sent from my Nexus 6 using XDA Free mobile app

I guess I should flash this, right?

RIPng said:
I guess I should flash this, right?
Click to expand...
Click to collapse
Of course, your contributions are greatly appreciated

Zyxxeil said:
Of course, your contributions are greatly appreciated
Click to expand...
Click to collapse
I wish we could get non intrusive nav on this device already Something like PIE or how CM used to hide the nav on kitkat.

looks really neat! it'll be nice to have a ROM where i won't have to worry about GAPPS issues

great. cant wait to test this out. glad to see new work coming to the n6

RIPng said:
I wish we could get non intrusive nav on this device already Something like PIE or how CM used to hide the nav on kitkat.
Click to expand...
Click to collapse
But, but, but you have all that screen
tflogic said:
looks really neat! it'll be nice to have a ROM where i won't have to worry about GAPPS issues
Click to expand...
Click to collapse
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.

Zyxxeil said:
But, but, but you have all that screen
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.
Click to expand...
Click to collapse
I just like full screen without nav, it looks more elegant in my opinion. On another note, how often do you release new builds? I publish new kernel updates far too frequently to ask you to rebuild each time

Zyxxeil said:
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.
Click to expand...
Click to collapse
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?

tflogic said:
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?
Click to expand...
Click to collapse
Well since its based on factory Image I don't think you will ever have to.
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
For those who don't know, he coded this whole ROM blindly since he doesn't have a nexus 6, and took it from a non booting 100% stock rom to a fully featured port of his nexus 5 rom in one day. It was amazing progress. He was pushing a new build like every 15 minutes, mainly because it took 10 mins to upload each time or he would've pushed them faster

RIPng said:
I just like full screen without nav, it looks more elegant in my opinion. On another note, how often do you release new builds? I publish new kernel updates far too frequently to ask you to rebuild each time
Click to expand...
Click to collapse
Maybe once a week. I will update the ROM with your new kernel each build
tflogic said:
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?
Click to expand...
Click to collapse
I will always include gapps.
Xileforce said:
Well since its based on factory Image I don't think you will ever have to.
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
For those who don't know, he coded this whole ROM blindly since he doesn't have a nexus 6, and took it from a non booting 100% stock rom to a fully featured port of his nexus 5 rom in one day. It was amazing progress. He was pushing a new build like every 15 minutes, mainly because it took 10 mins to upload each time or he would've pushed them faster
Click to expand...
Click to collapse
Yup, Most of the framework was already layed out with the Nexus 5 build just needed to port it over.
Plus its the first ever ROM to use Google's Factory Image. If any of you guys are interested in just the Factory Image as a ROM just let me know (Be warned its 750+MB in size)

finally a rom without bugs!

First bug, my recents button isn't working

RIPng said:
First bug, my recents button isn't working
Click to expand...
Click to collapse
Hmmm...mine is.

any special install instructions? just tried to flash and got the following message:
Wiping - Be patient it takes awhile
unmount of /system failed. no such volume
mount: failed to mount /dev/block/platform/msm_sdc.1/by-name/system at /system: Device or resource busy
Enjoy!
Script succeeded: result was [Enjoy!]
I assumed nothing was flashed because i didn't see the standard "progress bars". i restored my nandroid because i wasn't sure the flash worked. thanks in advance for your help/feedback.

cortez.i said:
any special install instructions? just tried to flash and got the following message:
Wiping - Be patient it takes awhile
unmount of /system failed. no such volume
mount: failed to mount /dev/block/platform/msm_sdc.1/by-name/system at /system: Device or resource busy
Enjoy!
Script succeeded: result was [Enjoy!]
I assumed nothing was flashed because i didn't see the standard "progress bars". i restored my nandroid because i wasn't sure the flash worked. thanks in advance for your help/feedback.
Click to expand...
Click to collapse
Unmount system first.

Related

[Kernel][CAF/AOSP][Stable 1.1] Vindicator[UberTC6.0/Ofast/Strict-Alias/Graphite][5.1]

{
"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"
}
"I Don't Always Run Custom Kernels. But When I Do, I Run Vindicator"
-Worlds Most Interesting Man
Pushbullet Tag: vindicator-n7
You can also follow me on G+ if you would like:
[email protected]
Intro:
This is a kernel I developed alongside @Xileforce for Nexus 7 2013, this IS an offical Vindicator Kernel and follows the same ideals and guidelines as the Vindicator Kernel for Nexus 6. I hope you like it and I won't be offended if you hate it. All ideas are welcome and I'll try to help as best I can. If you wish to use this kernel in a rom , feel free! Although I would love it if you let me know just for my own curiosity.
Goal:
Keep kernel as lean as possible while adding certain, desirable features and optimizing for maximum performance and battery life. The default settings should be optimal for a balance of battery and performance without a need to tweak.
Disclaimer:
If your tablet blows up, its not my fault. If your tablet somehow gains perpetual battery life, I'll take full responsibility.
Features:
-Quanta Kernel Base
-Android 5.1
-Linux 3.4.107
-Updated to Android M source
-XZ Compression
-Upstreamed cpuidle
-35mhz cpu step
-Compiled With Uber Toolchain 6.0
-Compiled With Strict-Aliasing, Ofast, Graphite, And Loop Nest Optimizations
-Various Other Build Optimizations
-Kexec Hardboot/MultiRom
-UKM Built In And Modified. Just Install Synapse App.
-Hardware Floating Point Processing
-ZRam
-ZSMalloc
-Slimmed Down(Increased Size Is Due To Optimizations & UKM Not Bloat)
-Tons Of Debugging Removed
-Many Misc. Optimizations.
-MPDecision killed
-Mako Hotplug
-Adjustable Thermal
-IntelliActive/Intellidemand Governor Added
-BFQ IO Scheduler Added
-Tons Of IO Fixes/Performance Boosts
-Voltage Control
-Westwood TCP Algorithm
-Many Parts Pulled From Upstream
-Wake Gestures
-F2FS Support
-Init.D Support
-Potentially Something I Forgot...
-Battery Life Extender
Donations:
I do not require a donation, nor will I demand a donation, but any and all donations are appreciated. Especially when I release my OTA app for this kernel, it'll go towards the server cost.
Downloads:
Caf builds end in -cm
Aosp builds end in -aosp
[AFH] Kernel: https://www.androidfilehost.com/?w=files&flid=32021
Downloads also through pushbullet
Source:
http://github.com/Orbit-/Vindicator-flo-aosp
Credits: @zaclimon for an awesome Kernel Base
xileforce
Franco
Faux123
Linaro
Code Aurora Foundation
apb_axel
Google
Asus
If I Missed You Let Me Know!
FAQ
1. How Do I Enable Mako Hotplug?
To enable mako hotplug use your favorite kernel control app like faux or trickster. As of 1.8 it is the default hotplug. In trickster you have to turn off both mpdecision and intelliplug. In faux you need to simply select User Control in the Hotplug Section. The hotplug can be configured using Franko Kernel Updater App.
2. Does This Work With CM12 Theme Engine?
Yes, this works with CM12 Theme Engine and should work on all ROMs properly.
3. How Can I Force All 4 Cores Online All The Time?
First you must enable mako hotplug. Then you need to use Franco's kernel updater app or another app that allows you to tweak mako hotplug settings. In fku app select CPU manager then hotplug control. Change load threshold to 0. Additionally if you just want to make it use 4 cores more often. Lower this number below 80 as desired. This should also be possible to tweak via terminal however I've never used that method.
4. Does This Have D2W, S2W, etc?
Yes, they are include in this kernel.
5. Help! I think its making me bootloop!:
This may only apply to specific ROMs and I'm unsure of why it would change anything but users have reported this to fix the issue. If you are trying a fresh install of a ROM boot on stock kernel first, reboot, then install this kernel.
6. You Broke My Tablet! Fix It!:
It will be quite hard for me to figure out what is going on if you don't provide details and a log of what happened. To get a log use any file manager and navigate to proc/last_kmsg. I need this file for debugging.
7. What Kernel Tweaking App Should I Use?:
I now use Synapse as my goto app for kernel tweaking.
8. Why Add Zram? We Already Have plenty of Ram!
Zram was added in build 1.0 as an experiment of sorts to see how much is was actually being used. V 1.0 introduced a bunch of tweaks to the kernel that essentially make it use more ram in order to give better battery life and performance. Zram was put in place to offset this in a way.
9. What Is Strict Aliasing And Why Should I Care?:
One of the big things Linaro does with improving Android's performance is fixing violations of what's known as "the strict aliasing rule." A pointer is said to alias another pointer when they both refer to the same location of memory. This is OK and not an uncommon thing to do. The strict aliasing rule is that pointers of different types should never refer to the same location of memory (aka alias each other). Strict aliasing allows a compiler to make some assumptions when compiling and optimizing code that it otherwise couldn't. It's actually one of the biggest optimizations you can do and it is fairly hard to add which is why most people don't. Here's a nice read up on it http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html#benefits
10. Come on man. 35mhz is pointless bro!:
A common misconception is that if two frequencies run at the same voltage. They use equal power. In fact this couldn't be less true. The equation for power draw has four variables. Two of which are frequency and voltage. Essentially it is the frequency multiplied by the square of the voltage. Then you would take that and multiply it by a few other things such as capacitance. However that is irrelevant for our purposes as it will not effect the relative results. This means that 35mhz running at 500mv will use about 3x less power than 98mhz at 500mv. Now we say well what about compared to 300mhz? I can stably run that at around 650mv. Maybe slightly less. This equates to about 15x less power usage at 35mhz. Well now that we know that. Who cares? Its not like 35mhz will even get used. Its too low! I beg to differ. I would almost guarantee that if you are not running mpdecision 35 MHz will be within the top 3 most used frequencies. Most likely the top used below sleep. And every time it uses that over 300mhz you are saving 15x the power. Additionally 35mhz also runs at a cache frequency of 35mhz as opposed to 300mhz cache frequency and runs a lower bus speed/voltage saving additional power.
11. How Do I Use MultiRom???:
To use multi ROM first you must download the MultiRom App from the Gooogle Play Store. Open it. You should have MultiRom and recovery boxes checked. Click install, reboot etc. To install a ROM. Download a ROM you like, go to twrp, click advanced,MultiRom,add ROM. Select internal storage and the Your zip file. Flash it but don't reboot! After that go back and select "list ROMs" select the ROM u just flashed still and click flash zip and select your gapps,supersu etc. After that simple reboot and select your new ROM on boot use the MultiRom app to manage your ROMs.
More will be added as they come up and I think of them.
If anyone wants to be a beta tester, email me at [email protected]. I'll be looking at email tomorrow.
First!
Re: [Kernel] Vindicator [Linaro 5.1/Strict-Alias/Graphite][5.1][Beta-0.1]
jamcswain said:
If anyone wants to be a beta tester, email me at [email protected]. I'll be looking at email tomorrow.
Click to expand...
Click to collapse
I want to be a better tester. I have one question though. The ROM I'm running is cm based and I'm getting different colors. Can you include a caf based kernel please. An d which is the best app to change settings with cz trickster don't let me change sound control
Edit: other than that the kernel looks great man. Its good and fast I'll test battery life for you on my next charge
Sent from my Nexus 7
hypemanisus said:
I want to be a better tester. I have one question though. The ROM I'm running is cm based and I'm getting different colors. Can you include a caf based kernel please. An d which is the best app to change settings with cz trickster don't let me change sound control
Edit: other than that the kernel looks great man. Its good and fast I'll test battery life for you on my next charge
Sent from my Nexus 7
Click to expand...
Click to collapse
Yes a caf base is coming soon
https://play.google.com/store/apps/details?id=com.af.synapse
That's the app that's supported
Hell yeah! Heard many good things about this kernel. It's really great to see it being developed for our beloved Flo. Sweet!
Just a quick heads up... I'm getting a boot loop. Running latest OptiPop which is 5.1.1 r2 and I have data and cache partitions set to f2fs. Any help is appreciated.
You stoped me flashing. Maybe it's a ramdisk problem? Flash stock kernel when flash this one. Give a feedback after that
And first request. Please add BLX\BLE http://forum.xda-developers.com/showthread.php?t=2469261
FireBlast said:
You stoped me flashing. Maybe it's a ramdisk problem? Flash stock kernel when flash this one. Give a feedback after that
And first request. Please add BLX\BLE http://forum.xda-developers.com/showthread.php?t=2469261
Click to expand...
Click to collapse
I'll look into it. I'm about to release an update anyway. Aosp and caf now
Oh yeah. I was planning on adding that in
Been running great on DU...
Installed it since you posted...
Thanks
Sent from the "DOG" pound on my N7 2013
Will give it a whirl...
And thanks...
Will let you know how it goes...?
New builds:
Aosp:
https://www.androidfilehost.com/?fid=23991606952607277
Caf:
https://www.androidfilehost.com/?fid=23991606952607307
Changelog:
-Rebase to Quanta
-Add caf build too
-Squash bugs
-Add bluplug
-Add more governors
-Add bfq
-Add 3.10 ZRAM
Looks like cm didn't boot. I'll fix that real quick
Don't know if this a bug, but I can't seem to get the MHz (94) to stick using synapse.
Everything else OK so far. This in on the initial release...
Thanks again....
https://www.androidfilehost.com/?fid=23991606952607307
NEW CM BUILD. Last one didn't boot
SHABBYLEA said:
Don't know if this a bug, but I can't seem to get the MHz (94) to stick using synapse.
Everything else OK so far. This in on the initial release...
Thanks again....
Click to expand...
Click to collapse
There isn't a 94mhz step
jamcswain said:
There isn't a 94mhz step
Click to expand...
Click to collapse
OK...on opening syn the min freq is 918. If I move the slider to the extreme left it indicates 94mhz. I save & when I reopen syn, the freq is back to 918.
Not at all saying this is a problem with the kernel, just what I'm seeing with syn...
Thanks.

DISCONTINUED LiquidDeathOS [ROM] [official] [7.1.1] [n1awifi] [p600]

{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
About LD
Years after the death of LiquidSmooth, Sean Hoyt, (the LiquidSmooth lead dev) has returned to the ROM game, along with the Exynos5420 team, to bring greatness to our beloved Exynos5420 tablets (and note 3), out of the ashes of the fallen LiquidSmooth ROM. LiquidDeathOS is super optimized for the Exynos5420.
In fact right now it is so optimized that it won't even boot on non-exynos devices
LDO is AOSP based , and is only for Exynos devices
(it's even more optimized than cm).
Important info
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
What works:
Display/Brightness
Touchscreen
Audio
Wifi
S-Pen
Buttons/Lights
SDCard
USB Storage
GPS
Bluetooth
IR Blaster
Camera
OMS/substratum theme engine
What doesn't work:
The default wallpaper is from DU, it will be changed in time
Not in the list? Report below
How to install
1. Download ROM and Gapps and transfer to device
2. Boot into recovery (TWRP recommended)
3. Wipe the system, cache, data, and dalvik cache
4. Install ROM
5. Install Gapps
6. Install SuperSU
7. Reboot to system
Downloads
official releases
test Builds
Note: n1awifi is the same device as lt03wifi - the SM-P600
Contributors
@deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin @javelinanddart@tincho5588 @ShevT
Device Maintainers
@mosimchah @ZakooZ @Orion116
Source code
Kernel
Device Repos
Rom Source
XDA:DevDB Information
SM-P600 LiquidDeathOS Official, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LP bootloader
Based On: AOSP
Version Information
Status: Beta
Created 12-30-2016
Last Updated 3-23-2017
​
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control (not yet supported on Nougat)
GPU Voltage Control (not yet supported on Nougat)
GPU Governor Control (not yet supported on Nougat)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Credits
This post was written by @ZakooZ
This app is brought you by the exynos5420 developer team: @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588, @ShevT
Translators:
@ShevT - Russian
The following people deserve distinction for their major contribution:
@tincho5588, responsible for 80%+ of the code for the new features
@deadman96385, the main maintainer of the Deathly kernel and most of the remaining code
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
Helping the developers
You may have noticed there's 2 versions of this app, one ad-free for donators and one with ads.
You can help us by clicking ads you're interested in for the free version, or purchasing the donator version!
We will use the money generated by this app as common money for the developers of the team. It will be used to pay for our web-hosting (we own a gerrit server and a domain name, exynos5420.com). It will also be used to buy a new device if one of ours breaks.
Translating the App
You can also help us by translating the app to your language:
1. You can start by looking at the full english language file: Link
2. Then compare it to your unfinished language file. You can find it here, under values-xx/strings.xml, xx being your language abbreviation.
3. You can then fill-in the missing strings in your language file. Here's an example of what a proper update looks like.
4. Then you can submit your translation by using our gerrit. If you don't know how to use gerrit, just PM the translation to your favorite developer and he'll get it merged!
FAQ:]
Q Does this ROM support custom kernels?
A No.
Q Why doesn't this ROM support Xposed?
A Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports while using it as Xposed can cause a lot of bugs.
Q Alright, but I still want to flash Xposed, so which version do I need to install?
A Xposed is not yet available for nougat, however when it is ready you will need to use the version arm sdk 25.
Q Can I have an ETA for the next build?
A Yes, the next build will be Thursday evening (eastern time), unless if something goes wrong of course...
Q Do I need to provide a log if I'm reporting a bug?
A If you want it to be fixed faster (or at all) then yes, you should definitely provide a log.
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder in the internal storage.
Q Can the builds be dirty flashed over each other?
A Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs, also bugs may only be reported on a clean flash.
Q How do I get a logcat, and what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
just in case
mosimchah said:
just in case
Click to expand...
Click to collapse
Whow!
Another great rom for our device and the file is really sssmmaaaaall this time!
No unwanted stuff, debloated right out of the box. Just the way I like it..!
I like to see new liquidness coming back...
Will test it tonight and report later...
I'm really curious to the optimizations done in this rom/kernel.
I am really glad with what dedication you all write new code for this nevertheless a few years old device.
If only we had a few good guys like you from the beginning ...
But finaly I'm really happy not to sold my device to replace it with a buggy pixel tab, Lol!
2 things so far, The wifi is set to recongize 5ghz in GB rather then all( don't remember the code for 'all', I switched mine to US). And some apps will have outstretched videos after a couple of seconds ( one such app is watchESPN). but other then, very nice ROM. Smooth and no troubling installing.
This ROM looks like a real killer. I like the fact that it is optimized for our specific chip, and the configurabilitylooks sweet. What gapps package is recommended for this build? I usully go with open gapps nano, but I might try the aroma package once more. I like the "pick & play" aspect and the install ui. Anybody have input with the gapps. I think I am going to really like this ROM. Thanks again, guys! ;-DeanoD
This looks awesome, i will be waiting for an stable version
Right, just clean flashed and I chose Nano GApps.
There's a problem that's solvable. It appears that the built-in AOSP WebView might not be working properly. For instance:
Feynman Lectures app opens but does not load its main page
Lightning Browser opens, but gets stuck once the UI is visible.
GetTube opens, but crashes once the YouTube link is clicked
Lithium eReader catalog crashes
SwiftKey is usable, but accessing its main menu (likely the one where it uses WebView to go online) crashes the app
"Crashes", as in the app is frozen and stops responding and Android offers the app-kill popup.
After installing Android WebView from the Play Store, everything works perfectly again. Checked the IR, camera, played some games (Machinarium, Deus Ex GO, TWoM) and all appears working. And yes, this is a real minimal install, so no music player, no browser etc from the get go.
And thus, those moving in from that CM14 build, might not be able to wake up from home key, hide software buttons and be rooted from a default install. I don't mind the former two, so to get root, download and flash the zip from here:
https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
I'll do some further testing, will report with more findings or logs in a week or so.
ROM won't boot after 15 minutes. Stuck at Android boot screen. Suggestions?
hipocrazy said:
ROM won't boot after 15 minutes. Stuck at Android boot screen. Suggestions?
Click to expand...
Click to collapse
Did you flash any mods with the ROM? Make sure you wiped the system, cache, and dalvik cache before flashing
Pact said:
Right, just clean flashed and I chose Nano GApps.
There's a problem that's solvable. It appears that the built-in AOSP WebView might not be working properly. For instance:
Feynman Lectures app opens but does not load its main page
Lightning Browser opens, but gets stuck once the UI is visible.
GetTube opens, but crashes once the YouTube link is clicked
Lithium eReader catalog crashes
SwiftKey is usable, but accessing its main menu (likely the one where it uses WebView to go online) crashes the app
"Crashes", as in the app is frozen and stops responding and Android offers the app-kill popup.
After installing Android WebView from the Play Store, everything works perfectly again. Checked the IR, camera, played some games (Machinarium, Deus Ex GO, TWoM) and all appears working. And yes, this is a real minimal install, so no music player, no browser etc from the get go.
And thus, those moving in from that CM14 build, might not be able to wake up from home key, hide software buttons and be rooted from a default install. I don't mind the former two, so to get root, download and flash the zip from here:
https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
I'll do some further testing, will report with more findings or logs in a week or so.
Click to expand...
Click to collapse
Thanks for the feedback, I'll include webview with the next build
DeanoD said:
This ROM looks like a real killer. I like the fact that it is optimized for our specific chip, and the configurabilitylooks sweet. What gapps package is recommended for this build? I usully go with open gapps nano, but I might try the aroma package once more. I like the "pick & play" aspect and the install ui. Anybody have input with the gapps. I think I am going to really like this ROM. Thanks again, guys! ;-DeanoD
Click to expand...
Click to collapse
Aroma should work, I don't think anyone on the team has tested it though
mosimchah said:
Did you flash any mods with the ROM? Make sure you wiped the system, cache, and dalvik cache before flashing
Click to expand...
Click to collapse
No mods, not even gapps. I performed a factory reset prior to flashing. I did receive the e: unknown command error after flash.
Edit: followed the instructions in OP to the letter. ROM boots fine now!
First Impressions
For a first draft ROM, this looks solid, and runs very clean. Still trying to tweak the install but system settings refuses to open so far. Will re-install tomorrow. ;-Deano
DeanoD said:
For a first draft ROM, this looks solid, and runs very clean. Still trying to tweak the install but system settings refuses to open so far. Will re-install tomorrow. ;-Deano
Click to expand...
Click to collapse
Currently there are none of the usual customisation options that you would expect in custom ROMs, absolutely nothing, being able to wake the tablet by pushing the physical home button would be a nice start. I'm also finding that like some other ROMs I've had on this and other devices Titanium backup will fail to restore some backups, just doing the animation it does while restoring but never actually finishing (having to install the occasional app from the play store while TB was doing its thing to make it progress), I had no sign of that problem with the CM14.1 ROM.
Once they hit their stride with development things should progress nicely, LiquidSmooth was probably the best ROM I've used (at least on this device).
It has navbar customizations in the system UI tuner, app ops in the security settings, and one of the main features is the substratum theme engine, more features will be added soon, can you get a logcat for the titanium backup issue
Right now the plan is to iron out the reported bugs, and then focus on a lot more features, keep in mind, this is this literally our first release ever, don't expect it to have a ton of features on the very first release
Really impressed by this ROM. Amazing work guys!
mosimchah said:
It has navbar customizations in the system UI tuner, app ops in the security settings, and one of the main features is the substratum theme engine, more features will be added soon, can you get a logcat for the titanium backup issue
Click to expand...
Click to collapse
My first go at capturing something using Catlog is attached, TB trying to restore Adaway app & data for a while.
I have looked through pretty much the entire Settings interface and found no "system UI tuner" anywhere and no app that looks as though it would do any such thing, I have not removed a thing via TB or any other means.

[ROM][weekly][Official] AICP 12.1 [P600][n1awifi][7.1.2]

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, I will laugh at you. Hard. A lot.
*
*/
.
{
"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"
}
AICP​Android Ice Cold Project​
AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CM when it comes to hardware, drivers and some features.
If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!
The following will not be supported here:
Custom kernels (besides for prime)
Mods
Xposed
.
.
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRoms team
CarbonRom team
LiquidSmooth rom team
OmniRom team
Community
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
.
.
.
Note: n1awifi is the same device as lt03wifi - the SM-P600
[/SIZE]
Official Releases: http://dwnld.aicp-rom.com/?device=n1awifi
Official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Note: Here is the last official build https://www.androidfilehost.com/?fid=3700668719832236662
Gapps
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
test builds: https://www.androidfilehost.com/?w=files&flid=173061
kitkat bootloader kernel builds (the zip files are for all nougat roms): https://www.androidfilehost.com/?w=files&flid=173258
You tell...
​
ROMS should contain everything you need to enjoy Lollipop. You are not required to install any Add Ons, simply download the latest ROM, gapps, flash it, and go!
You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup - these can cause stability issues that are very hard to debug. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.
How to flash:
This ROM REQUIRES the Lollipop bootloader. See this post to learn how to update your bootloader.
1. Download ROM and Gapps and transfer to device
2. Boot into recovery (TWRP recommended)
3. Wipe the system, data, cache, and dalvik cache
4. Install ROM
5. Install Gapps
6. Reboot to system
ROM has gapps persistance in between dirty flashes
PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed.
You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. Zip gets saved under AICP_ota folder on your internal SDcard.
If you want to contribute to AICP or wanna see what is being worked on/merge feel free to visit our gerrit, link is at the bottom!!!
IceColdJelly AICP G+ community
kernel source
kitkat bootloader builds
device tree
ROM
gerrit
github
XDA:DevDB Information
[ROM][weekly][Official] AICP 12.1 [P600][n1awifi][7.1.2], ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
mosimchah, eyosen
ROM OS Version: 7.x Nougat
Kernel: Linux 3.4.x
ROM Firmware Required: LL bootloader
Based On: LineageOS
Version Information
Status: Stable
Created 2017-04-19
Last Updated 2017-12-14
​
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, the next official build will be on Thursday, around 5:40am (Eastern time).
Q. Does this ROM support custom kernels?
A. I support prime https://forum.xda-developers.com/ga...kernel-prime-kernel-p601-tw-lollipop-t3456312 .
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports while using it as Xposed can cause a lot of bugs.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You need to use the version arm sdk 25.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post..
Q. What TWRP versions are supported?
A. ShevT's. Check out this thread for the TWRP download.
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs, also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the system, cache, and dalvik cache, flash the ROM, gapps, and reboot.
Q. Will this work on the Kitkat bootloader?
A. Yes if you flash Prime kernel.
Using the ROM:
Q. How do I enable software buttons?
A. Settings->Navigation.
Q. Do I need to provide a log if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a log.
Q. How do I get a logcat, and what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control
GPU Voltage Control
GPU Governor Control
GPU Thermal - Control all thermal throttling points for the GPU (make your device run colder... or even hotter)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
This is a work in progress guide to getting great battery life
1. In Deathly Adiutor disable all the input boosters in the cpu section
2. Use the S-pen power saving mode
3. Set the vibration strength to zero (or close to zero) in the misc section
4. Set the default I/O scheduler to noop
5. Go to developer options and turn off the logger buffer sizes (you will have to turn this back on in order to get a logcat for bug reports)
6. Use the suspend actions in aicp extras and turn off the ota checker
7. Use greenify to enable aggressive doze and doze on the go, and use it to limit background apps
8. Turn off all animations in developer options
9. Disable fsync (risky, you could lose data if the system crashes)
=================================================================================================================
This is a work in progress guide to getting great Performance at the expense of battery life
1. Go to developer options and turn off the logger buffer sizes (you will have to turn this back on in order to get a logcat for bug reports)
2. turn off the ota checker in aicp extras
3. Use greenify to enable aggressive doze and doze on the go, and use it to limit background apps
4. Turn off all animations in developer options
5. Disable fsync (risky, you could lose data if the system crashes)
6. Use the input boosters
reserved
Firstly, many thanks for this and helping keep our tablets up to date. I am hopefully going to try flashing this later today.
Is this Rom pre-rooted or am i going to need to flash SuperSU?
Thanks again.
Tim047 said:
Firstly, many thanks for this and helping keep our tablets up to date. I am hopefully going to try flashing this later today.
Is this Rom pre-rooted or am i going to need to flash SuperSU?
Thanks again.
Click to expand...
Click to collapse
It's pre-rooted with magisk
Awesome work, thanks!
Is this as optimised for the P600 as LD was? Any summary of what makes this unique compared to Lineage?
Sent from my HTC 2PS6200 using Tapatalk
Finner42 said:
Awesome work, thanks!
Is this as optimised for the P600 as LD was? Any summary of what makes this unique compared to Lineage?
Click to expand...
Click to collapse
1. No,
2. Yes, way more features/customisations, mhl partially works, and is in some ways faster
This seems to be the best rom for p600, at the moment. :good:
It works with prime kernel v. 7.2 and has much more features than LOS and LD.
Substratum is also working and should be included as default system app and there is MagiskManager support, so that Safetynet is finally working.
There are only some minor bugs like:
- QS-Tile background is always translucent
- minor graphic glitches
- if Nougat Sidebar inside Settings menu is deactivated via AICP extras the back-button which replaces the menu-button doesn't work
- Ui is a little bit laggy
- screen mirroring doesn't work like on all other aosp roms
- Brightness-sensor is a little bit slow or not correctly calibrated
- Magisk Manager link in settings should be in the system category and not in the personalise category
Thank you mosimchah! :victory:
*update: graphic glitches and performance issues are prime kernel related. No issues with original AICP kernel. So don't flash prime kernel until the kernel gets an update!
Thanks again for yet another great upgrade! So far running great, the only issue I'm having is that the S-Pen button isn't working, which isn't a big deal for me.
s pen features ( cursor on the screen, palm rejection etc)
Does the features like palm rejection, the cursor that shows up when you hover your pen over the screen, and air command still work after rooting and installing Nougat? My Note 10.1 still has Lollipop on it and I am on the fence about installing Nougat
Sweet!!
M -- Once again, you have outdone yourself with this ROM. With full wipe and fresh install, it took barely 20 mins. And the settings will keep me happy for ages. My Wacom Feel Stylus is also performing fantastically. So far, not even a blip. I may be imagining this, but the screen res even seems smoother. Great work from the entire team that worked on this. ;-DeanoD
DeanoD said:
M -- Once again, you have outdone yourself with this ROM. With full wipe and fresh install, it took barely 20 mins. And the settings will keep me happy for ages. My Wacom Feel Stylus is also performing fantastically. So far, not even a blip. I may be imagining this, but the screen res even seems smoother. Great work from the entire team that worked on this. ;-DeanoD
Click to expand...
Click to collapse
Thanks, glad you like it
BenHaHaHa said:
Does the features like palm rejection, the cursor that shows up when you hover your pen over the screen, and air command still work after rooting and installing Nougat? My Note 10.1 still has Lollipop on it and I am on the fence about installing Nougat
Click to expand...
Click to collapse
Palm rejection works, no cursor, and you can install a separate app for air command, search the lineage thread for it
The first official build should be next Thursday
mosimchah said:
The first official build should be next Thursday
Click to expand...
Click to collapse
Could be instelled by OTA? I wanna try this ROM, but if I have to repeat the installation on Thursday I would wait for it.
Thanks for your job!!!
josveland said:
Could be instelled by OTA? I wanna try this ROM, but if I have to repeat the installation on Thursday I would wait for it.
Thanks for your job!!!
Click to expand...
Click to collapse
Just dirty flash the build... The ota might work for the next build, I'm not entirely sure though
Great Rom, so far everything is smooth. Love all the features.
Only problems I found are some audio glitches, mostly when locking/unlocking the screen while listening to music from the headphone jack.
BenHaHaHa said:
Does the features like palm rejection, the cursor that shows up when you hover your pen over the screen, and air command still work after rooting and installing Nougat? My Note 10.1 still has Lollipop on it and I am on the fence about installing Nougat
Click to expand...
Click to collapse
Some apps have their own floating cursors, but there isn't one built into the ROM (as far as I know). The kernel has the option to disable pen detection while the pen is inserted.
Air Command / S-notes etc are Touchwiz-only features. There are certainly some third-party apps to fill the gap, if you search for S-pen in the play store. The most popular ones seem to be the combination of CM S-Pen Add-On and Note Buddy.
EDIT: Sorry, I didn't notice that your comment already had a reply.

[KERNEL][7.x.x][SHAMU] * Simple Kernel * [r2 - 07/05]

{
"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"
}
​Simple Kernel - Shamu
Simple Kernel is a kernel for Shamu that aims to be just that; a simple kernel. I believe in having too much stuff that really doesn't contribute to a better user experience should not be added into a kernel, and that's the ideology that I built this kernel with. I present Simple Kernel. I hope you enjoy it!
Features:
Sourced from latest Shamu kernel release (nougat-mr-1.5) up to July's security patches.
Upstreamed to 3.10.107 - Thanks to @The Flash for his guide to upstreaming a kernel
Built with vanilla Linaro GCC 7.1.1 - Thanks to The Flash's gcc build tool I used
Upstream F2FS support
LZO Compressed kernel - fast decompression at boot time
Power Suspend power management - Thanks to @faux123 and @Yank555
Hotplugs: Intelliplug v4.0 & Mako Hotplug + Stock - Thanks to faux123 and @franciscofranco
CPU governors: Nightmare & ElementalX + Stock - Thanks to @Alucard24 and @flar2
I/O Schedulers: Zen & Row(just enabled it) + Stock - Thanks to @bbedward
Intellithermal v3 - configurable thermal management - Thanks to faux123 Adjustable max temp for stock thermal monitor - Thanks to franciscofranco
Simple GPU Algorithm - configurable way to improve stock msm_adreno_tz governor - Thanks to faux123
KCAL Color Control - Thanks to @savoca
Zen-Tune v4.5 - improves overall responsiveness - Thanks to @frap129
Power Efficient Work queues - can save some battery - Thanks to neilbrown
Disabled BCL (for now, was causing me issues)
No force-encrypt or dm-verity
Safe GCC Optimization flags for Shamu - (-O2, -mtune=cortex-a15, -marm, -mfpu=neon-vfp4, -pipe)
Some misc fixes and stuff here and there
No excess/magical optimizations or patches
Look at my commit log for full list for everything in the kernel
Changelog:
Just look at commit log. Make it easy.
Installation:
Download latest build
If on another kernel, flash your ROM's (or stock) boot img in TWRP Recovery. If coming from Simple Kernel, proceed to step 3.
Flash kernel in recovery
Wipe Cache/Dalvik-Cache
Reboot
Done
FAQ:
Q: There was a random reboot or some other issue! What do I do?
A: Pull logs, send them to me. Address issues publicly in thread so everyone can benefit/chip in.
Q: Can you add XYZ feature/patch?
A: Perhaps I can. I am always open to adding things, as long as it maintains the soul of the kernel. Giving me a place to find it also helps. You can also create a pull request on Github if you have the commits.
Q: How do I pull a log that you asked for?
A: I use (play store, free) Kernel Adiutor to pull logs. In KA, go to Settings -> Debugging -> Driver Message & -> Last kmsg. Send me the txt files created in /sdcard. Not doing this when bringing up an issue will result in loss of my support and is not good practice when asking for help.
Q: What is F2FS? How do I convert to it?
A: Googling will do you well, this gives a good overview of what is is. This thread might help you decide if it's right for you. Read my instructions in my TWRP w/F2FS thread to see basic conversion instructions.
Disclaimer:
I am not responsible for anything that happens to your device. Period.
External Thanks:
designapp.io for the logo
Download:
See second post
XDA:DevDB Information
Simple Kernel, Kernel for the Nexus 6
Contributors
Black_Hat01, Contributors listed by-contibution
Source Code: https://github.com/BlackHat01/SimpleKernel-Shamu
Kernel Special Features: F2FS, Linaro Compiled - Smooth, Simple & Stable
Version Information
Status: Stable
Current Stable Version: r2
Stable Release Date: 2017-07-05
Created 2017-07-02
Last Updated 2017-07-05
Download
Download latest build - r2
So far so good...
With six ROM 3.9
"Sent from the Dog Pound"
cujo6801 said:
So far so good...
With six ROM 3.9
"Sent from the Dog Pound"
Click to expand...
Click to collapse
Good to know :good:
Cool thanks
Sent from my Nexus 6 using Tapatalk
About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?
espionage724 said:
About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?
Click to expand...
Click to collapse
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.
Build r2 live
Build r2 is live with minor changes. Here's an overview of what's changed:
- Reverted Intellithermal and replaced it with franco's max temp tuner due to stability issues
- Merged latest July security patches from google
Happy flashing!
Black_Hat01 said:
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.
Click to expand...
Click to collapse
LZO is going to be the best available. Also, Intellithermal is outdated. I would stay away from it. May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).
apophis9283 said:
Also, Intellithermal is outdated. I would stay away from it.
Click to expand...
Click to collapse
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
apophis9283 said:
May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).
Click to expand...
Click to collapse
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.
Black_Hat01 said:
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.
Click to expand...
Click to collapse
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.
Screenshots
apophis9283 said:
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.
Click to expand...
Click to collapse
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
EDIT:
Looking at your setup, mine is quite similar, except of course the BCL switches. And currently affinity at 0 for testing.
Black_Hat01 said:
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
Click to expand...
Click to collapse
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c
apophis9283 said:
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
Click to expand...
Click to collapse
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
apophis9283 said:
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c
Click to expand...
Click to collapse
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.
Black_Hat01 said:
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.
Click to expand...
Click to collapse
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.
apophis9283 said:
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.
Click to expand...
Click to collapse
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.
Black_Hat01 said:
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.
Click to expand...
Click to collapse
Try RQ Affinity value = 1. If not I have another idea
apophis9283 said:
Try RQ Affinity value = 1. If not I have another idea
Click to expand...
Click to collapse
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
EDIT:
Guess the culprit would be intelli plug
Black_Hat01 said:
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
Click to expand...
Click to collapse
Feel free to PM me if you need anything.

[KERNEL][Q][AOSP/OneUI-2][R4][EOL] RAD Kernel [N950(F/N/FD)]

{
"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"
}
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.
I don't provide support for OneUI-pie & treble ROMs, asking me if I will ever do is just a waste of time.
INFO:
If you wonder what the hell RAD Kernel is... Then let me explain, RAD Kernel is a project oriented towards people who depend on their phone every day.
RAD Kernel is designed for maximum stability.
All kernel builds are thoroughly tested before Release.
As the title says RAD Kernel per se supports AOSP ROM(s), OneUI 2 ROM(s) and it's meant to be used with it for a better STABLE experience.
RAD Kernel will NOT work with any other ROMS except AOSP & OneUI-2 (i.e no OneUI-pie & treble support).
SUPPORTED DEVICES:
G950(N/F/FD)
G955(N/F/FD)
N950(F/FD)
FEATURES:
Linux 4.4.111
Compiled with Clang 9.
O3 optimizations.
Fast, smooth and great for Daily Use!
Permissive SE-Linux.
Boeffla Wakelock Blocker.
Interactive governor as Default.
Optimized Integer SQRT. for upto 3x faster operation.
Tuned Interactive governor for better balance between performance and battery.
CPU BIG up to 2314MHz.
CPU small up to 1690MHz.
GPU OC up to 572MHz
WireGuard.
Disabled CRC by default - 30% File system performance.
Fsync toggle enabled by default, can be changed in a kernel tweaker.
TCP congestion - bic as default.
Z-RAM enabled by default and set at 2592MB.
Z-RAM compression - lzo
HMP values tuned for better performance!
and the list goes on!
ROOT:
RAD Kernel DOES NOT come with pre-installed ROOT.
You can flash the latest MAGISK to get ROOT!
SUPPORT:
Telegram Group - Click here!
Telegram Channel - Click Here!
CREDITS:
Me, for developing without time and for the struggle to test new things.
Stricted for LineageOS development.
Dr.DoubtReaper for testing my kernel images.
Samsung Open Source for their Kernel source.
Topjohnwu for magisk!
Linus torvalds for Linux!
Thanks to anyone else who made this whole thing possible, you are part of it as well!
and all the people on GitHub whom i might have cherry-picked from!
XDA:DevDB Information
RAD Kernel for Exynos8895, Kernel for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
Live0verfl0w
Source Code: https://github.com/Exynos-nigg/RAD-8895
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4
Stable Release Date: 2021-01-07
Created 2020-10-05
Last Updated 2020-11-08
R4 (07/01/2021) [EOL]
BUGS:
DexOnPc is bugged, device wont be recognized (OneUI2 build only!)
DOWNLOADS:
Official Kernel Website - click here!
Google Drive - click here!
INSTALLATION:
NOTE! YOU NEED TO BE ALREADY ON AOSP/OneUI-2 ROM, BEFORE FLASHING THIS CUSTOM KERNEL
Download the provided zip for your device model.
Put the zip inside your storage.
Reboot to TWRP recovery.
Flash the zip and wait until it completes.
Reboot your device, and enjoy the Butter smooth experience.
CHANGELOGS:
R4(07/01/2021)
Added OneUI-2 support! (make sure to flash the OneUI-2 build)
Disabled logging and some debug stuff
Older changelogs below! =)
R3.5 HOTFIX(08/11/2020)
Unified installer zips!
Fix bootloop issues!
Switch from AK3 to AIK zips!
NOTE: This releases has no changes kernel side, but the installation zips have been changed!
NOTE: Sorry for the inconveniences caused because of the bootloops, this releases should (hopefully!) fix em =)
R3 (04/11/2020)
Disabled GFS (Gentle Fair Sleepers) for better UI performance!
Fix placebo tweaks blocker!
General optimizations!
Kill DVFS completely!
Remove excessive logging from decon, GPU drivers & touchscreen drivers!
Unified S8/S8+ kernel!
Set "westwood" as default TCP congestion algorithm!
NOTE: The kernel zips have different time labels on them because i did build them few days before but was just lazy to release them
R2 (13/10/2020)
Changed to Interactive on CPU!
Fixed sound not coming from earpiece!
Remove Audit dependency!
Enabled touch input booster!
Disabled Hotplug!
Change default IO scheduler to "deadline"!
Disable some logging!
This kernel build should be way smoother than R1!
R1 (05/10/2020)
Initial Release!
FAQ:​ (Read this before flashing the kernel and reporting bugs!)
Q. Gaming performace isnt good in this kernel!
A. Disable Samsung Hotplug from your preferred kernel tweaker app! Hotplug is disabled in builds from R2 onwards!
Q. Whats Fsync? should i disable it?
A. fsync transfers ("flushes") all modified in-core data of (i.e., modified buffer cache pages for) the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even after the system crashed or was rebooted. This includes writing through or flushing a disk cache if present. The call blocks until the device reports that the transfer has completed. It also flushes metadata information associated with the file (see stat(2)).
Too scientific, didnt read! : In layman terms disabling Fsync gives you better performance with the risk of a Data loss/corruption during a system crash!
Q. I cant Flash NFS injector, FDE.AI, MAGNETAR and other tweakers on this kernel!
A. I have added a in-built kernel blocker to block installation of these so called "AIO kernel tweakers". You shouldnt install these tweaks in my opinion! If you still want to use a Tweaker, i prefer you use KTweak though i wont be providing support for issues if u have flashed any mods or anything of this likeliness!
Q. I have an issue and i have reported it in the XDA thread, yet nobody replied to me.
A. I might be slow in responding for issues reported in the XDA thread, if u want me to reply more faster, report it in the Telegram support group!
Q. My phone gets HOT while using this kernel!?
A. Short answer: It's your own issue, fix it yourself. Nobody makes a kernel just to burn your hands.
Long answer:
* Install Termux app from Play Store * Enable screen rotation, open Termux in landspace mode * Type this command: su -c top -d 2 * A list of processes will appear and refresh with 2s interval. Find which process consumes the most CPU usage with [%CPU] column and the package name in ARGS column. You should see the culprit of your issue.
Reminder: There is no such thing as "I have nothing in background but the phone still heats up". There definitely something happen and 99% of the time it's some of the rogue apps running in background.
Thanks to Diep Quynh for finding this one out!
I've tried it and for some reason left top corner of the screen never responded to touch. Ex: I couldn't turn on wifi from quick toggles n back arrow in some apps as I couldn't make a touch on left corner...
I didn't collect logs as I immediately reverted back to old kernel.
arjun.reddy said:
I've tried it and for some reason left top corner of the screen never responded to touch. Ex: I couldn't turn on wifi from quick toggles n back arrow in some apps as I couldn't make a touch on left corner...
I didn't collect logs as I immediately reverted back to old kernel.
Click to expand...
Click to collapse
Could you tell me which rom and device please?
Me or any of my testers didnt find this issue.
Live0verfl0w said:
Could you tell me which rom and device please?
Me or any of my testers didnt find this issue.
Click to expand...
Click to collapse
I am on Resurrection Remix Q Using NOTE 8 (SM-950F). I will flash the kernel again n let you know if it's replicable.
Finally new kernel for my note 8
I'll give it a try
and post feedback after testing for few days
I have small question
which is better... EAS or HMP?
Thanks
Alastal said:
Finally new kernel for my note 8
I'll give it a try
and post feedback after testing for few days
I have small question
which is better... EAS or HMP?
Thanks
Click to expand...
Click to collapse
As a dev i really cant compare, but u can try it and decide for urself:good:
I have this weird bug with the earpiece still not working on the new version of the Kernel
I am using the Official HavocOS rom on my Galaxy Note 8
Alessandro2003 said:
I have this weird bug with the earpiece still not working on the new version of the Kernel
I am using the Official HavocOS rom on my Galaxy Note 8
Click to expand...
Click to collapse
Its a ROM issue, which has been already identified by the rom dev, u can join their telegram group to know this
New kernel build is up guys! =)
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Hotfix build is uploaded, sorry for the inconveniences caused by the bootloop issues =)
Excudent said:
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Click to expand...
Click to collapse
Hi mate!
1. hotplug is disabled cuz in my tests i found em to degrade performance and doesnt make much of a difference battery life wise, hence disabled and yes its a samsung implementation.
2. For OC u can pick ace2nutzers a2n kernel commits, i have tested em and it works
3. as for the undervolt, i havent tried em and probably wont be =)
4. Thanks very much, i dont need coffee or beers and stuff, u can hit the thanks button =)
Thanks and regards,
Stay Safe!
I am using this kernel on android 10 oneui
after i flashed the kernel i had weird issue concerning samsung clear case
when i close the case the screen turn on and when i open the case the screen turns off!
it acts in the opposite manner!
N950N supported?
is there any way to change to enforcing?!
Excudent said:
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Click to expand...
Click to collapse
But how? Can you share your settings?

Categories

Resources