[ROM/Kernel][6.0.1][Uber 5.2.1/Archi 5.2] [CM-Optimised] INAZUMA R4
- Thread starter zeeshanhussain12
- Start date
Oh come on ! He's saying clearly that its R6 , how are saying its R7 ?
Sent from my Moto E using Tapatalk
Hey buddy i think u need not have to ask this question couz this i a clean kernel and gives unblevable battery backup along wiyh performance ( highy cousomizable) so if op adds wake controls ill no longer be clean and battery effecient.("for those who have power button problm use volume key to wake. D2w or s2w eats more than 30% overnight").
Can you tell me how you are getting a nice battery backup?
What's your kernel settings can you tell me?
And in which rom you are using this kernel?
Lastly thanks zee for a nice kernel........
Hmm see this. One thing i would like 2 say older builds of rom and newer builds of kernel both's combination is just mind blowing...and ill tell u that my phone and battery both are 2 year + old.
Attachments
Ohh man extremely nice backup.
But which version of inazuma kernel you are using?
And what's your kernel version?
Please Update the kernel.
One of the best kernel which gives best battery backup....
One of the best kernel which gives best battery backup....
hey I am in trouble..i flashed cm 13 on my phone and it was normally working fine ..after that i went ahead to install the firmware for xt1022 back frm here http://xdaforums.com/showthread.php?t=2755857 ..and i after that ..i was not able to boot into my recovery at all..and i installed twrp after that and was able to flash cm13 again ..but their is this new problem i cant solve...my normal powerup doesnt work..it boots in recovery on it on..if i restart simply my device will go into recovery ...for getting into the system..i have to select the factory option frm the bootloader..and it works like normal power option....can u help me out? is the problem cause of downgrading frm cm13 to lollipop..or did i do somethng wrong please help..
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
20
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you.*/
I present to you my own kernel which has been built with many optimizations and tweaks. This kernel will work ONLY on Marshmallow roms(Not for stock roms) only.The main aim is to provide a stable kernel with optimizations.
I hope you all will like it
Kernel Features :
- Updated to latest cm-13.0 Sources
- Compiled With Custom ARCHI 5.2 Toolchain
- Additional many optimization flags
- Compiled With Cortex A7 Tweaks
- ARM v7 Optimizations
- LMK tweaks
- Disabled Gentle Fair Sleepers
- Disabled CRC check
- Reduced Swappiness from 60 to 40
- Set ReadAhead to 512
- Reclaimed RAM from Loggers.
- Enabled pipe flag
- Added SmartMax/LionHeart Govs
- Added Xperience/DanceDance Govs
- Optimized Slub
- PowerSuspend 1.5
- Cleaned Up some dead code
- Tweak mount options for all partitions
- Many more things (Check my github)
DOWNLOAD :
Grab it here
#ROM infos on the 4th post, be sure to check it
PLEASE DONT MIRROR LINKS
I Would like to say thanks to @ashwin007 for Cm bringup. Also a big thanks to @rainforce279 @TechnoAnder
@vatsal @faux123 @adarsh1998 and many more
XDA:DevDB Information
[ROM/Kernel][6.0.1][Uber 5.2.1/Archi 5.2] [CM-Optimised] INAZUMA R4, ROM for the Moto E
Contributors
zeeshanhussain12
Source Code: https://github.com/zeeshanhussain/inazuma-mm-new
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader with twrp
Based On: CyanogenMod
Version Information
Status: Beta
Beta Release Date: 2016-01-09
Created 2016-01-09
Last Updated 2016-02-169So here's the surprise
Hello folks,
I am using my own optimised builds since initial phase of CM13. Rom and kernel are both build with Uber 5.2.1 and few more optimisations on the kernel (It's same like in the first post). The Uber Toolchain developer said due to new neon optimisations in Uber toolchains, the battery life has increased by 25%. Well using since a long time, I almost get 6hrs+ SOT(Ofcourse will vary with you) and a mindblowing performance. So I am going to provide weekly Uber CM13 builds with optimisations(It is somewhat close to pf-cm by Diamond Bond). The people interested, could use it
, It will stay really close to CM and few picks here and there. I would really appreciate feedbacks I am using the build posted and it's really rock stable.
Download :-
All optimised buildshttps://www.androidfilehost.com/?w=files&flid=47307
Bugs:-
you tell me
Installation :-
A clean wipe is mandatory.
Wipe cache,dalvik cache, system, data
Flash the zip
Flash gapps ( I use slim zero gapps)
Reboot, Enjoy!
FAQ:-
Differences between UBERTC and other Toolchains
Changelog for the 1st December Toolchain updates
Regards9Kernel Update R2
INAZUMA R2 BUILD UP
DOWNLOAD
CHANGELOG
Code:*Git Rebased * Build with uber gcc 5.2.1 a074da6 Add my Automated build script 7ae77c1 Fix Build 9c82a7f Fix compilation Errors 314b4cb Revert "timerfd: add alarm timers" 6e77ba4 Config : Sync with latest changes 7e36149 mach-msm: cpufreq: cleanup f84840b workqueue: Added null check and warning 26a58be sched: Fix race in idle_balance() ddd8877 mm: add cma pcp list 8a995ff idr: Backport from upstream 812cb5b security: force SELinux permissive mode f6d9070 LCD_KCAL: Color control driver for msm8x10/mdp3 55db7b9 deadline: Allow 0ms deadline latency, increase the read speed a5bd5f7 sched: Add sysinterface for GENTLE_FAIR_SLEEPERS 102dbbb sync: make complete dynamic_fsync. 0631742 fs/dyn_sync_cntrl: dynamic sync control 5ede347 condor: config: Enable optimized SHA-1 439b47e cfq-iosched: fix the setting of IOPS mode on SSDs e949b81 block: Make CFQ default to IOPS mode on SSDs 848e1ca Fix Derp 0822bed Makefile: Optimizer arm flags 856d7d4 timerfd: add alarm timers 2515a2d rbtree: Backport from 3.10 1837234 fix compilation error c7c30f9 cpufreq: zzmoove: scaling/zz_get_next_freq: f60439c cpufreq: zzmoove: Fix lcd notifier and powersuspend compile issues - added missing part! 0a0da6d cpufreq: zzmoove: Fix lcd notifier and powersuspend compile issues due to a merge derp in 1.0 beta cddca5e cpufreq: zzmoove: fix store_inputboost_typingbooster_cores undeclared here c657e75 cpufreq: zzmoove: updated to the latest v1.0 beta8 4be6a96 cpufreq: Add Impulse, Smartmax, Yankactive, Zzmoove Governor 206aee1 block: Add SIO, VR, ZEN I/O schedulers 7018651 Alucard : Enable it by default 0a81cdc Alucard : Tune Alucard e593fe9 Drivers : Remove Intellimm for now 823d003 Makefile : use std=gnu89 6a13625 Add support for Msm8610 (Condor and otus) 825c9c0 Initial porting of Intellimm from nexus devices f1eb5e7 Alucard : Use get_cpu_idle_time 3e58c7d Alucard : fix build d84652c Alucard: update to latest version 7e428ce Disable Alucard by default 02e1964 Mach-msm : Add Alucard Hotplug ac02b08 dont add automatically generated file 056311a Update Local version And much more check my github :)7Reserved
F.A.Q. - Read this before complaining!
1. My phone exploded, HELP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on hastebin.com and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. This kernel works on Y or X rom?
A: Works on all CM13 based roms. Not for stock roms!!
3. OMG BATTERY SUCKZ, ITZ DEAD IN 45 MINUTES, HELP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. How do I flash this?
A: Read the OP, theres a reason why I added instructions on it.
5. What is a data loss? Did I just had one?
A: Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection.
6. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.7
